What does the reloading mean really? That you can compile an action and Webwork will
notice that it changed and update the class?
How is this different from what the container would do if I tell it to detect changes
to my classes? That it only reloads the changed class?
Cheers,
Dick Zetterberg
Not all containers support reloading of random classes. Resin does,
Orion will only reload modified servlets or filters.
Secondly, reloading the entire webapp can be quite slow if you have
complex init on startup servlets. My 'hack' would just reload all
actions, rather than the entire webapp.
Subject: Re: [OS-webwork] action reloading
Not all containers support reloading of random classes. Resin does,
Orion will only reload modified servlets or filters.
Secondly, reloading the entire webapp can be quite slow if you have
complex init on startup servlets. My 'hack' would just reload
I had this working briefly in ww 1.3 but it broke due to some other
change. I'll spend some time and try to get it going again.
James Cook said:
What about reloading the configuration contexts? For example, if a
change to xwork.xml or components/xml also triggers a reload?
-Original
environment is configured.
Cheers,
Dick Zetterberg
[EMAIL PROTECTED]
- Original Message -
From: Hani Suleiman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, November 06, 2003 2:40 PM
Subject: Re: [OS-webwork] action reloading
Not all containers support reloading
Hani,
I'd like to see this included in 2.0 as well. Can you give me a brief
understanding how this works? Does WebWork use it's own classoader?
-Pat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Hani Suleiman
Sent: Tuesday, November 04, 2003 9:16 PM
- Original Message -
From: Hani Suleiman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, January 22, 2003 6:58 PM
Subject: Re: [OS-webwork] Action reloading
This does seem possibly currently by plugging in a bunch of custom
*Configuration classes. I'll try and work
while(true) {
hani++;
}
You are my hero!
Justen Stepka
- Original Message -
From: Hani Suleiman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, January 22, 2003 6:58 PM
Subject: Re: [OS-webwork] Action reloading
This does seem possibly currently by plugging in a bunch
This is a good idea. Something like how you can get struts-config.xml
to reload in struts.
On Wednesday, January 22, 2003, at 05:13 PM, Justen Stepka wrote:
s there a way to get the actions.xml to reload too?
---
This SF.net email is
Config file reloading is a totally different ballpark than Action
reloading. However, it is part of the planned configuration overhaul in
XWork.
--Erik
---
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT
This does seem possibly currently by plugging in a bunch of custom
*Configuration classes. I'll try and work on it in the next few days and will
hopefully post an addon that can be used with webwork 1.3 to enable dynamic
reloading of *.properties and *.xml files.
Quoting Justen Stepka [EMAIL
Hani Suleiman wrote:
- It ONLY reloads actions. It specifically does not reload any classes
outside of the defined packages for actions.
- It relies on the location of webwork.properties to determine what the
jar/directory where actions exist
- No extra configuration is required beyond changing
12 matches
Mail list logo
