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
, 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 moni
Do you know if there's a way to tell if it's in a jar file?
> -Original Message-
> From: Hani Suleiman [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 09, 2004 12:40 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [OS-webwork] XWork, Webwork and reloading xml
>
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 singlet
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:
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 probl
is instead
kept in a Map of classloader -> 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 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 this
gt; Subject: Re: [OS-webwork] XWork, Webwork and reloading xml
>
>
>
> On Monday 08 March 2004 16:21, Jason Carreira wrote:
> > Note that if you set this flag the same check will be done for all
> > validation files and conversion property files, although
> not for text
On Monday 08 March 2004 16:21, Jason Carreira wrote:
> Note that if you set this flag the same check will be done for all
> validation files and conversion property files, although not for text
> bundles (complain to Sun, it's their PropertyResourceBundle).
I needed to have some way of reloading
It doesn't actually re-parse the configuration XML file every time. The
ConfigurationManager calls provider.needsReload() on every
ConfigurationProvider to see if that config provider thinks it needs to
reload (so any custom ConfigurationProvider can implement this in its
own way). The XmlConfigura
11 matches
Mail list logo
