[jira] Resolved: (AMQ-2193) The ActiveMQ Web Console does not work out of box when deployed in the ServiceMix 4 container

["Dejan Bosanac (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQ-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac resolved AMQ-2193.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3.0
         Assignee: Dejan Bosanac

This was a problem with older versions of PAX.

There's a guide, that instructs how to integrate web console with the ServiceMix

http://activemq.apache.org/osgi-integration.html#OSGiIntegration-Webconsole

More improvements will be added for new 6.0 console.

> The ActiveMQ Web Console does not work out of box when deployed in the ServiceMix 4 container
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2193
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2193
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.2.0
>            Reporter: Joe Luo
>            Assignee: Dejan Bosanac
>             Fix For: 5.3.0
>
>
> The ActiveMQ Web Console does not work out of box when deployed within the ServiceMix 4 OSGI container. For more details, please have a look at the Fuse Forum post: [http://fusesource.com/forums/thread.jspa?threadID=749&tstart=0]
> So there are two problems here:
> 1. The jstl.jar and standard.jar are required to run the JSP page in the container but the two jars are not in the AMQ web console war file "WEB-INF\lib" directory. 
> 2. The PAX web and web extender bundles that installed by the "web-core" and "web" features from the servicemix 4 feature list does not support the JSP .tag files (JSP2 spec). See related PAX issues: [http://tinyurl.com/cbztny] and [http://tinyurl.com/ccah47]. As a workaround, people have to manually install the latest SNAPSHOT PAX Web and PAX Web Extender bundles from ops4j snapshot repository [http://repository.ops4j.org/mvn-snapshots/org/ops4j/pax/] to get around the problem.
> In a non-OSGI environment. all classes and tag libs that required from jstl.jar and standard.jar are contained in jsp-api jar and it is loaded when the AMQ is started. Hence, it is no need to put the two jars into the war file to deploy. However, in the ServiceMix 4 container, the two jars will have to be either placed in the war or deployed as individual OSGI bundles. 
> I did some tests to convert the jstl.jar into OSGI bundle and list all the packages to be exported in it's manifest file, it seems working fine. However, I could not get standard.jar working even after converted it to an OSGI bundle and deployed into the SMX4 container. It looks like eventually I have to put at least the standard.jar into the web console war "WEB-INF\lib" directory to be deployed to the container using PAX "war" deployer.
> Another difficulty is that we will have to wait for the OPS4J to release PAX Web and PAX Web extender jars with the latest fix as a non-snapshot release. Otherwise, people will always need to manually download those jars and deployed into the SMX4 container to get around the problem #2.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.