[Design of JBoss/Tomcat Integration] - Re: Tomcat Deployer is wrong in JBoss Head
by adrian@jboss.org
anonymous wrote :
| Remy Maucherat [04/Dec/07 06:07 PM] I propose postponing this until after AS 5 (since this tree is supposed to be more or less stable, and the current code works perfectly well). This would most likely include using a new infrastructure to process server.xml and META-INF/context.xml webapp configuration (maybe merged into jboss-web.xml).
|
The purpose of the change is to split the Tomcat deployer into two parts.
Whether this is done physically or logically is a different question.
The first stage is just to get something in place that knows how to parse
{jboss}-web.xml and create the MBeans.
The second stage is getting the infrastructure to satisfy the dependencies
of those MBeans.
The main aim is that the MBeans that represent web deployments
and connectors should not be started until their dependencies are satisified.
Currently it is the Tomcat Deployer itself that has these dependencies.
Without this change, we have to promote other services (clustering/jca/etc.)
to earlier in the deployment process just so we can parse a web.xml
This has knock on affects into other services and causes all sorts of problems.
If there was a real physical split then we could start Tomcat "on-demand"
when the first deployment with a web application appears, but that
is additional functionality to the basic problem.
We'll eventually need something like this anyway, because we want to
run the deployers in "off-line mode". i.e. just do the parsing and dependency
checking without creating any real services.
This is so we can validate configuration in a management console
without having to boot the whole server to check if it is reasonable.
Postponing the resolution of the problem to after 5.0.0 is not acceptable.
This issue has been open for 6 months with nothing being done about it.
I'll do it myself if necessary. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110474#4110474
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110474
18 years, 1 month
[Design of JBoss jBPM] - Re: Improvig timer
by kukeltje
please checkout cvs.... initial version checked in late last night (03:30, so not getting old..... ;-))
also some testcases but small issues remain (will make a jira issue for this tonight)
- Only date, no Calendar yet and String will never be suported by me (due toformatting things)
- a minus for an old style due date is now possible but leads to duedates in the past.... suggestion on how to handle these? e.g. throw an error
- only on timer, not on task due date yet
- not tested in combination with repeats
oh and btw...
- '65 years - 2 hours - 10 minutes' does not work nor with plusses. I did not know that
- duration does not take leapyears into account. +65 years does miss 16 days (in my case ;-)), but this was already the case and not caused by me (might even be a java issues)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110468#4110468
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110468
18 years, 1 month