Hi,
After spending some time with the xwork/oscore code, I find that what you say is not wrong, but it
is broken in this case. The problem is in FileManager, which stores a reference to the file and its
last modified timestamp as you say, to check if it needs reloading later. Before storing
Jason Carreira schrieb:
Well, that code is really there for the case where you do have exploded
war files, you're editing them, and you want the changes to be picked
up...
Tell me, will each redeployment get its own classloader? I'm planning on
refactoring so that the configuration is not a
]
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, Craig Raw wrote
...
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 what you say
, 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, Craig Raw wrote
