-
1. Re: xml out of war-file
norman.richards Apr 27, 2005 10:37 AM (in response to jean-francois2)You can specify an alt-dd on your application.xml, but that just shifts the replacement burden one deployment descriptor higher.
If you deploy in exploded format, swapping out web.xml files is easy. -
2. Re: xml out of war-file
jean-francois2 Apr 28, 2005 4:34 AM (in response to jean-francois2)thx for your help !!!
Now i'm a lot futher. -
3. Re: xml out of war-file
briankardell Jun 3, 2005 4:39 PM (in response to jean-francois2)This is actually sort of a common problem... But: Do you really need 50 different web.xml's - and if so - why? Usually the solution to this problem, in my experience, is that just because something can be set up with web.xml doesn't always mean that that is the only - or best way to accomplish.
-
4. Re: xml out of war-file
wtff Jul 16, 2005 1:06 PM (in response to jean-francois2)I aggree that the alt-dd mechanism is a fantastic featute. It is of big value in certain situations. For example when an application needs to be deployed to several machines, each time with a different configuration or profile.
My problem is that I believe JBoss is ignoring the alt-dd element. I had run tests with previous versions of jboss and also checked the 4.0.2 codebase. The J2eeModuleMetaData class parses the alt-dd element and returns the url configured within this element via a method called getAlternativeDD().
This method is not being invoked by any other jboss class.
I read a wiki doc which hinted that JBoss 5 will support alt-dd elements via it's virtual filesystem approach.
Are there any plans to add support for the alt-dd element to the 4.x branch?
This is an awefully usefull feature and I'm missing it a lot in Jboss. ;)
Thanks
Sascha