It looks like you cannot specify a mode while creating a package in crx package manager. but if you are creating a package externally, e.g. through a maven plugin - you can specify in filter.xml if the content should be merged. //filter.xml<?xml version="1.0" encoding="UTF-8"?><workspaceFilter versi...

what is your use case? I am not sure if one workflow can run on two instances - most probably no. but if you are looking to get some kind of feedback from one instance to another; that can be achieved. e.g. you can have a servlet on author instance that does what you want, then have a workflow on pu...

Hi bsloki, thank for help.I resolved this issue by going to crx-quickstart\launchpad\config\org\apache\felix\jaas\Configuration\factory and replacing the config files with a valid config set from another environment.

How to add the config manually? can not login to felix console.

Hello,I accidently deleted a configuration from felix console from this section - Apache Felix JAAS Configuration factory.Now I am not able to log in to /system/console. Getting the following error in logs- *INFO* [qtp337226887-36] org.apache.sling.extensions.webconsolesecurityprovider.internal.Slin...

HttpMethodDirector warning is just a warning, should not be cause of the failure.are there any error messages in server logs?try upload/install the same package manually through package manager.

here is a code sample-servlet registration: https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/bundle/src/main/java/com/adobe/acs/commons/replication/dispatcher/impl/DispatcherFlusherServlet.java servlet call: https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/ma...

the correct way to access the servlet registered by resourceTypes would be something like the following-localhost:4502/<path-to-a-resource-with-resourcetype-services-powerproxy>.groups the following code in powerproxy.jsp should call the servlet- <form name="frm" method="post" action="<c:out value="...

You may need to change how you are accessing the servlet, Please see this - https://sling.apache.org/documentation/the-sling-engine/servlets.html#example-registration-by-resource-type-etc

this happened with me once, in my case the custom tags were defined in a shared library jar that was deployed saparately and happened to be missing from publish. you may want to track down which files provide support for your custom tags and make sure they are available in publish.