Using groovy console with an instance running using a context path about aem-groovy-console HOT 7 CLOSED

Please provide additional details on the error you are experiencing.

from aem-groovy-console.

So assume that your CQ instance is running on org.apache.felix.http.context_path="/foo", then all links should be prefixed with "/foo". Having a look at your console.js (and testing your cool tool in an instance running with context path), I mentioned that these prefix is missing in: console.js line 113, line line 179 and line 197. This results in an 404 for any action made.

from aem-groovy-console.

Thanks. I will review and investigate a possible solution.

from aem-groovy-console.

Since CQ 5.3 there is CQ.shared.HTTP.getContextPath(). See http://dev.day.com/docs/en/cq/current/widgets-api/index.html?class=CQ.shared.HTTP.

from aem-groovy-console.

Dirk, I have made a few changes to support context paths, but I am not sure how best to test in CQ. Can you describe how to configure a local CQ instance running with a context path so I can verify the changes? Thanks and sorry for the delayed response.

from aem-groovy-console.

Create a node in the following structure:
/
/apps
/apps/foo
/apps/foo/config
/apps/foo/config/org.apache.felix.http
[jcr:primaryType = sling:OsgiConfig]
[org.apache.felix.http.context_path = "/context"]

Afterwards your application is reachable through the given contextpath.

from aem-groovy-console.

I revviewed the code you commited and it looks good so far, thanks for applying these changes.

from aem-groovy-console.