t: Tuesday, March 09, 2004 12:40 PM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] XWork, Webwork and reloading xml
In this case I'd say xwork is broken. The solution is for it to not
bother monitoring files that are in jars.
On Mar 9, 2004, at 11:53 AM,
> configuration...
Would that help?
-Original Message-----
From: Craig Raw [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 09, 2004 11:54 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] XWork, Webwork and reloading xml
Hi,
After spending some time with the xwork/oscore code, I find
that w
Jason
-----Original Message-
From: Craig Raw [mailto:[EMAIL PROTECTED]
Sent: Monday, March 08, 2004 7:37 AM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] XWork, Webwork and reloading xml
Hi,
I have run into issues surrounding xwork and the reloading of
classes using hot deploy. My
deployment en
Hi,
I have run into issues surrounding xwork and the reloading of classes using hot deploy. My
deployment environment is JBoss, where I am sharing the webwork/xwork libraries between ears (to
keep the ear file size down) and using a separate loader repository for each ear (to keep the
configura
What order are your filters listed in web.xml? The gzip filter should be listed before sitemesh in
web.xml so it performs its compression after page decoration.
hth,
Craig
Samuel Mota wrote:
Hi,
This is a little OT but I hope someone from Opensymphony can help me on this.
I'm testing the Gzip f
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 applic
Hi,
I have encountered what is to me a serious usability issue with XWork. I
am using it deployed in a .war in Jboss, where hot redeploy greatly
reduces update times during the development process. To reduce the size
of the created .war files, I store the xwork/webwork jars in the JBoss
server
