Project referenced by the classpath does not exist

The project: <project name> which is referenced by the classpath, does not exist. error in Eclipse

Resolution

Right click on the project from project explorer >> select build path >> configure build path >> a popup window will appear. Go to project tab and check the entry of project if that project is not in your eclipse project explorer then remove the project and apply the changes. 

Now build the project again.

Failed to collect dependencies mule-core-ee:jar:3.8.4

Few times I faced this issue, while working with Mule 3.8.4. When I Googled I found people are talking about the Mulesoft Enterprise Edition access to download these dependencies for project, but I don't think we need nexus EE access to download these dependencies specially when we are working with Mule 3. Here the problem is something different and your POM might have some additional dependencies which is not available on public nexus repository and due to that this dependency is not getting resolved.

Failed to collect dependencies at com.mulesoft.muleesb:mule-core-ee:jar:3.8.4: Failed to read artifact descriptor for com.mulesoft.muleesb:mule-core-ee:jar:3.8.4: Could not transfer artifact com.mulesoft.muleesb:mule-core-ee:pom:3.8.4 from/to Central (http://repo1.maven.org/maven2/): Failed to transfer file http://repo1.maven.org/maven2/com/mulesoft/muleesb/mule-core-ee/3.8.4/mule-core-ee-3.8.4.pom with status code 501

Resolution:

To resolve this in Mule 3 Anypoint studio, create a new fresh maven project and build it. If this newly created project successfully build then your other project where you are facing this issue will work. Match the project POM.xml file with new project pom and see the dependencies.

Example POM.xml file.

Custom Dispatcher flush rule setup | acs commons

Create a custom dispatcher flush rule for your content, which an author can trigger using UI, without any involvement of developer and DevOps person. This is a single click activity for an author to invalidate the dispatcher cache.

For this ACS-commons provide a powerful which we need to configure in our AEM author instance. Here are the steps to set up the custom dispatcher flush using acs-commons.

 

Step 1: Log in to AEM instance.

Step 2: Download the acs-commons latest version from acs official site and install the acs-commons package in your AEM instance using AEM package manager [http://localhost:4502/crx/packmgr].

Step 3: After the successful installation of acs-commons, browse to AEM tools section. http://localhost:4502/miscadmin. 

Step 4: Now create a dispatcher flush page to set up your dispatcher configuration. Below is the screenshot.

1. Click on the Dispatcher Flush directory from the left rail.

2. Click on the new button from the menu bar, and select the option, New Page. As soon as you click on the New Page option a new window will appear. As highlighted below.

3. Put the Title and Name for the page. e.g. custom dispatcher flush

4. Click on the create button.

5. This will create a custom-dispatcher-flush page under the Dispatcher Flush directory.

Custom dispatcher flush

Step 5: Open this newly created "custom dispatcher flush" page. To open double click on the page name. Our custom dispatcher flush page will look like as below.

Note: In the above screenshot we could see under the Active Dispatcher Flush Agent there is no active dispatcher flush replication agent is showing.

Step 6: Click on the Edit option from next to the Dispatcher Flush Configuration. Once we click on Edit, the configuration settings option will appear. Here we have to set the following;

1. Flush method - We need to specify whether we want to invalidate the caching or completely delete the caching from the dispatcher server.

2. Paths to flush - We will list all the path and pages which we want to invalidate or delete from the dispatcher server.

Step 7: Now we have to enable the Dispatcher Flush agent queue on AEM author. [http://localhost:4502/etc/replication/agents.author/flush.html]. If the AEM instance is already configured with dispatcher then we need not do anything extra in this case, just verify the Dispatcher Flush agent from the above-mentioned path. 

In case the dispatcher Flush is not setup then configure the following in properties in the configuration setting.

1. Edit the Dispatcher Flush settings. Click on the Edit button from the below screen.

2. Enabled - Check enabled option.

3. Move to the transport tab and set the following

a. URI - URL of the dispatcher server.

b. User - a transport user name

c. Password - password of transport user

Our dispatcher configuration is set, now using the Test Connection option we can verify the configuration setting and ensure everything is fine. 

Step 8: We have done with our custom dispatcher setup.

Step 9: Now go back to your custom dispatcher page which we had created in Step 4. Open the page and see the changes. In the dispatcher flush page now we could see Flush paths on Dispatcher button and Dispatcher Flush under Active Dispatcher Flush Agent.

Step 10: Click on Flush Paths on the Dispatcher button highlighted in red to invalidate and delete the caching from the dispatcher server. Below is the screenshot. After triggering the flush go and validate the status of the cached content.

 

Dispatcher flush

References:

Adobe consulting services: 

https://adobe-consulting-services.github.io/acs-aem-commons/features/dispatcher-flush-ui/index.html