As far as I can see:
You can get at the Jetty war deployer via JBoss JMX Agent - so you should be able
to just deploy a war.
However, since this has been deployed separately from the corresponding ejb.jar,
the J2EEDeployer will not be able to set up optimised intra-vm calls - so things
will go slower (probably not a problem in development).
A problem I foresee with doing this is that Jetty will probably end up with the
same war deployed twice. Once from the ear and once by itself.
The next release of jboss-jetty will hopefully expose internal Jetty MBeans to the
JBoss JMX agent. I expect this will allow you to go in and e.g. stop and remove
running webapps/servlets, so that you will be able to work around this problem.
anyone ?
Jules
P.S.
If this is a load of rubbish - it's way past my bedtime.
Nathan Coast wrote:
> Hi,
>
> in order to speed up the time to build & redeploy a large application originally
> deployed in an ear file, is it possible to deploy a component - ejb.jar or
> web.war? Or will this only work if the ejbs / web components were originally
> deployed individually?
>
> Cheers
> Nathan
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
