Petri Wessman wrote:
On Friday 05 December 2003 17:53, Jason Carreira wrote:
Actually, there is a way to do that. With JBoss 3.2.x, if you package your
war inside an .ear and place the following as jboss-app.xml in the ear
META-INF directory, JBoss will use a separate classloader for the
, December 08, 2003 6:12 AM
To: [EMAIL PROTECTED]
Subject: Spam:Re: Spam:[OS-webwork] Xwork and hot redeploy
Petri Wessman wrote:
On Friday 05 December 2003 17:53, Jason Carreira wrote:
Actually, there is a way to do that. With JBoss 3.2.x, if
you package
your
war inside an .ear
On Dec 8, 2003, at 6:12 AM, Craig Raw wrote:
This seems to work, but I need to perform further testing to be sure.
I am, I admit, confused as to the reason of the reload property. Why
would you not want to reload the configuration. Performance reasons?
Yep, enabling this causes the timestamp
On Friday 05 December 2003 17:53, Jason Carreira wrote:
As far as being able to have the one Xwork.jar and have multiple
configurations, that's a good idea... Please add a Jira issue. I've
always hated that Singleton, so we can look at how to get rid of it. In
the meantime, is it possible to
), but this would
be a major undertaking.
Jason
-Original Message-
From: Craig Raw [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2003 9:53 AM
To: [EMAIL PROTECTED]
Subject: Spam:[OS-webwork] Xwork and hot redeploy
Hi,
I have encountered what is to me a serious usability issue
Jason Carreira wrote:
webwork.configuration.xml.reload=true
In your webwork.properties to tell it to check and automatically reload
XML configuration files (this includes the xwork.xml file and any other
included xwork configuration files, validation.xml files, and type
conversion .properties
