You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2007/06/22 17:16:33 UTC
[jira] Commented: (AMQ-1281) Better WAR building for the WebConsole
[ https://issues.apache.org/activemq/browse/AMQ-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39473 ]
James Strachan commented on AMQ-1281:
-------------------------------------
Thanks for the patches! I've committed most of the patch.
I wasn't sure about enabling the default (JNDI based) option though; JNDI doesn't always work & folks often get port conflicts; so its a bit more fiddley to use.
So I think I'd rather the JNDI stuff be an option; but not the default - and using a local one in the binary distro should be the default when running the 'activemq' script (or use the embedded one when running _mvn jetty:run_ from inside activemq-web-console).
> Better WAR building for the WebConsole
> --------------------------------------
>
> Key: AMQ-1281
> URL: https://issues.apache.org/activemq/browse/AMQ-1281
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Environment: any
> Reporter: Mario Siegenthaler
> Attachments: webconsole-patch.txt
>
>
> The webconsole can be deployed in any webcontainer and is also started by default within the broker. However the building and configuration process is unclear.
> * To resolve that issue I added some documentation about how to run the war in an external servlet container and changed some default setting. Also I changed the version that is started within the broker to the invm version instead of the 'custom' configuration that was previously included in the assembly/src/release/webapp/WEB-INF.
> * The maven jetty:run on the web-console project will still start up the embedded version, but I fixed the bug that caused it to leak sessions (switched to the spring-2.0 syntax for the configuration file).
> * I removed some JARs from the WEB-INF/lib of the war because they should be provided by the servlet container. This affects some specifications (JMX, JMS), the activation-jar and, most important, the activemq-core jar.
> I hope this does the job and makes the deployment experience for the users easier.
> Note: I had some problems putting together the patch as my subversion (or my inability to communicate with it) insisted on leaving out some files I created :) I think they're all in now, but I'm not sure. So if anything is missing... :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.