[Tomcat Integration Development] New message: "Re: Deployment of on-demand web applications"
by Brian Stansberry
JBoss development,
A new message was posted in the thread "Deployment of on-demand web applications":
http://community.jboss.org/message/522117#522117
Author : Brian Stansberry
Profile : http://community.jboss.org/people/bstansberry@jboss.com
Message:
--------------------------------------------------------------
I don't mind continuing to debate the overall approach a bit; it's mostly a discussion of priorities. But IMHO the hooks in the Mapper class are a useful feature, whether or not we prioritize using them in M2. Having them in a JBoss Web release this week lets us go either way for M2. The rest of the implementation is in AS trunk itself, where the cutoff is 2 weeks later.
Bela's point about 2 mechanisms for delayed deployment is a good one. The critical thing is getting the server ready to handle requests ASAP; you can offload heavy non-critical stuff off the main thread. But if you do that, JBoss Web needs to know about the webapps that will be coming on later, otherwise the server isn't really "ready to handle requests". The Mapper stuff I did provides the hooks to make that doable. A user request triggers the deploy if the background thread hasn't gotten to it yet. Some simple coordination logic in the "activator" ensures it the activation only happens once.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/522117#522117
14 years, 7 months
[Tomcat Integration Development] New message: "Re: Deployment of on-demand web applications"
by Brian Stansberry
JBoss development,
A new message was posted in the thread "Deployment of on-demand web applications":
http://community.jboss.org/message/522110#522110
Author : Brian Stansberry
Profile : http://community.jboss.org/people/bstansberry@jboss.com
Message:
--------------------------------------------------------------
> emuckenhuber wrote:
>
> There will be something like a on-demand feature, which basically only registers a profile without activating it. However if someone actually decides to include the 'admin-console' profile in his configuraiton, it will get activated. So this on-demand context activator would also have to support that this profile is getting activated when starting AS (the ordering can be controlled if neccessary). I guess that should be no problem?
Are you asking about a case analogous to what would happen if in the current setup, deploy/ included both admin-console-activator-jboss-beans.xml and admin-console.war? When playing with this yesterday morning I did that by accident a couple times and it worked fine (for reasons I understand and can go into if you're interested -- basically the code detects it and handles it easily enough.)
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/522110#522110
14 years, 7 months
[Tomcat Integration Development] New message: "Re: Deployment of on-demand web applications"
by Bela Ban
JBoss development,
A new message was posted in the thread "Deployment of on-demand web applications":
http://community.jboss.org/message/522100#522100
Author : Bela Ban
Profile : http://community.jboss.org/people/bela@jboss.com
Message:
--------------------------------------------------------------
The current profiles are not going to cut it; they're much too coarse grained. And we don't want to end up with a permutation of useful profiles, e.g. if you want web + clustering, you're going to have to create a new profile, or remove lots of crap (web services, IIOP) from 'all'.
Fine grained services (not related to the 'all', 'default' etc profiles) are the way to go: include all the stuff in a coarse grained profile, and then select which 'services' (for lack of a better word) you want at start time, e.g.
./run.sh -c all +service WEB +service CLUSTERING -service EJB
runs JBoss with only web clustering (no EJB clustering).
IIRC this is planned for JBoss anyway...
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/522100#522100
14 years, 7 months
[Tomcat Integration Development] New message: "Re: Deployment of on-demand web applications"
by Brian Stansberry
JBoss development,
A new message was posted in the thread "Deployment of on-demand web applications":
http://community.jboss.org/message/522085#522085
Author : Brian Stansberry
Profile : http://community.jboss.org/people/bstansberry@jboss.com
Message:
--------------------------------------------------------------
Stan, can you create a blocker JIRA for M3 for revisting the set of profiles we ship? M3 is when some ProfileService changes will be in to make it easier to preconfigure a bunch of profiles. It's a PITA now; doing it for M2 (beyond trivial stuff like dropping admin-console from default) will waste a lot of time on something that will be thrown away.
Let me be blunt here. My main motivation to spend a day working the above (which I'd say is about 50% of the effort to complete it altogether) is that a 38 second start time for the default profile in M2 just totally sucks. 20-25 secs we were seeing before admin-console was added back in is reasonable progress. 38 seconds sucks.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/522085#522085
14 years, 7 months
[Tomcat Integration Development] New message: "Re: Deployment of on-demand web applications"
by Bill Burke
JBoss development,
A new message was posted in the thread "Deployment of on-demand web applications":
http://community.jboss.org/message/522080#522080
Author : Bill Burke
Profile : http://community.jboss.org/people/bill.burke@jboss.com
Message:
--------------------------------------------------------------
> mailto:remy.maucherat@jboss.com wrote:
>
> VDF integration is done for all metadata (tlds, web.xml, web-fragment.xml). Configuration (server.xml and context.xml) reimplementation is waiting on prfile service. Cleanup has been done to remove a hard JMX dependency with the mapper. Integration can then be moved over gradually to the embedded API.
>
> The "ugly ass" standalone code will remain as a casual testing capability (Jean-Frédéric loves it). Sorry you dislike it, but it is mature and it works quite well, so I don't really have plans to delete it for the time being.
I want deeper integration. For example, it would make my life so much easier if I could instantiate instances of servlets and filters within my JAX-RS deployer for JBossWeb to consume and deploy. But I guess thats another different discussion...
Yeah, the "ugly ass" code I meant was all the JMX stuff.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/522080#522080
14 years, 7 months