RE: [OS-webwork] Exception handler proposal
If this functionality exists it MUST be part of the webapp framework. As far as I am concerned, I prefer a WW2-centric approach. In this viewpoint, you could consider taking advantage of the fully functionnal framework to handle exceptions. You could forward DIRECTLY to an action, manage different result types (action, jsp, velocity,...), and so on. Cheers. Richard HALLIER Chef de projet [EMAIL PROTECTED] 01.40.12.41.52 www.uniclick.org UNICLICK -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Hani Suleiman Envoye : samedi 1 novembre 2003 04:30 A : [EMAIL PROTECTED] Objet : Re: [OS-webwork] Exception handler proposal Err, why on earth would you want this in webwork? What's wrong with the exception handlers you can specify in web.xml, which work exactly as described below? On Oct 31, 2003, at 10:18 PM, Jason Carreira wrote: Nope... Interesting idea... Post a Jira issue for it... -Original Message- From: Fred Lamuette [mailto:[EMAIL PROTECTED] Sent: Friday, October 31, 2003 3:00 PM To: [EMAIL PROTECTED] Subject: [OS-webwork] Exception handler proposal Is there an exception handler mechanism in xwork ? Something like : global-exception type=mypack.ApplicationException action=myExceptionHandlerAction/ that could redirect exceptions inherited from mypack.ApplicationException to the myExceptionHandlerAction action ? Cheers. Richard HALLIER Chef de projet [EMAIL PROTECTED] 01.40.12.41.52 www.uniclick.org UNICLICK --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
[OS-webwork] Textarea Tag and Value Stack Problems
I updated the version of WW2 I'm using for development to the latest version in CVS last night. I immediately noticed two issues. 1) When a webwork:textarea tag is rendered in my page, it contains the value $parameters.nameValue. For some strange reason the variable in the velocity template is not getting evaluated. I hadn't taken the time to look at the templates before last night. It seems that all the other ui tags use the same variable reference and have not had problems in my jsp. 2) I have code that iterates over a list of lists. Previously, I could use the notation that[0], that[1], to access objects in the list when inside an iterator. That doesn't seem to work now. Has the that keyword changed? Scott Delap [EMAIL PROTECTED] --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
[OS-webwork] Old wounds!
I don't mean to open up old wounds, but what exactly was the reasoning behind deprecating the *Aware in ww 1.3? Would anyone be terribly upset if they were undeprecated in 1.3.1? Does anyone care? --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Textarea Tag and Value Stack Problems
1) I believe all UI tags are now evaluated against the value stack, so you need to quote your values. 2) that is changed to top --- Scott Delap [EMAIL PROTECTED] wrote: I updated the version of WW2 I'm using for development to the latest version in CVS last night. I immediately noticed two issues. 1) When a webwork:textarea tag is rendered in my page, it contains the value $parameters.nameValue. For some strange reason the variable in the velocity template is not getting evaluated. I hadn't taken the time to look at the templates before last night. It seems that all the other ui tags use the same variable reference and have not had problems in my jsp. 2) I have code that iterates over a list of lists. Previously, I could use the notation that[0], that[1], to access objects in the list when inside an iterator. That doesn't seem to work now. Has the that keyword changed? Scott Delap [EMAIL PROTECTED] --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Old wounds!
i believe it was suggested that everyone start using the ActionContext threadlocal to get what previously gotten by the Aware interfaces.. why using ActionContext instead of Aware is another question :) Hani Suleiman wrote: I don't mean to open up old wounds, but what exactly was the reasoning behind deprecating the *Aware in ww 1.3? Would anyone be terribly upset if they were undeprecated in 1.3.1? Does anyone care? --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Old wounds!
Francisco Hernandez wrote: i believe it was suggested that everyone start using the ActionContext threadlocal to get what previously gotten by the Aware interfaces.. Yup, that was it. why using ActionContext instead of Aware is another question :) Because it's easier and less verbose? /Rickard --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Old wounds!
Alright then, it can stay deprecated. I'll close the bugs asking for it to be undeprecated in a day or two, provided nobody complains. On Nov 1, 2003, at 4:01 PM, Rickard Öberg wrote: Francisco Hernandez wrote: i believe it was suggested that everyone start using the ActionContext threadlocal to get what previously gotten by the Aware interfaces.. Yup, that was it. why using ActionContext instead of Aware is another question :) Because it's easier and less verbose? /Rickard --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Old wounds!
Removing the interfaces would break many old applications so that should probably never be done. (Since those are the applications using WW1). So, since the interfaces will not be removed, then the deprecation might instead be removed so you don't get the annoying warnings all the time (or rather, you can turn on the deprecation warnings and not be flooded with warnings you already know about). Cheers, Dick [EMAIL PROTECTED] - Original Message - From: Hani Suleiman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, November 01, 2003 10:04 PM Subject: Re: [OS-webwork] Old wounds! Alright then, it can stay deprecated. I'll close the bugs asking for it to be undeprecated in a day or two, provided nobody complains. On Nov 1, 2003, at 4:01 PM, Rickard Öberg wrote: Francisco Hernandez wrote: i believe it was suggested that everyone start using the ActionContext threadlocal to get what previously gotten by the Aware interfaces.. Yup, that was it. why using ActionContext instead of Aware is another question :) Because it's easier and less verbose? /Rickard --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Old wounds!
Dick Zetterberg wrote: Removing the interfaces would break many old applications so that should probably never be done. (Since those are the applications using WW1). So, since the interfaces will not be removed, then the deprecation might instead be removed so you don't get the annoying warnings all the time (or rather, you can turn on the deprecation warnings and not be flooded with warnings you already know about). I suppose you meant turn off the deprecation warnings. /Rickard --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Old wounds!
Well, the deprecation serves as a marker to indicate 'this is not a recommended approach', sure it'll never go away (nothing deprecated in the JDK has gone away either), but it's still worth having in if the official line is that it's a discouraged set of interfaces. On Nov 1, 2003, at 5:15 PM, Rickard Öberg wrote: Dick Zetterberg wrote: Removing the interfaces would break many old applications so that should probably never be done. (Since those are the applications using WW1). So, since the interfaces will not be removed, then the deprecation might instead be removed so you don't get the annoying warnings all the time (or rather, you can turn on the deprecation warnings and not be flooded with warnings you already know about). I suppose you meant turn off the deprecation warnings. /Rickard --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Exception handler proposal
It would be nice to be able to specify an error page based on URI pattern. eg any error that occurs with a uri matching /action/flight* gets forwarded/redirected to the action flightError. - Original Message - From: Fred Lamuette [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, November 01, 2003 9:44 AM Subject: RE: [OS-webwork] Exception handler proposal If this functionality exists it MUST be part of the webapp framework. As far as I am concerned, I prefer a WW2-centric approach. In this viewpoint, you could consider taking advantage of the fully functionnal framework to handle exceptions. You could forward DIRECTLY to an action, manage different result types (action, jsp, velocity,...), and so on. Cheers. Richard HALLIER Chef de projet [EMAIL PROTECTED] 01.40.12.41.52 www.uniclick.org UNICLICK -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Hani Suleiman Envoye : samedi 1 novembre 2003 04:30 A : [EMAIL PROTECTED] Objet : Re: [OS-webwork] Exception handler proposal Err, why on earth would you want this in webwork? What's wrong with the exception handlers you can specify in web.xml, which work exactly as described below? On Oct 31, 2003, at 10:18 PM, Jason Carreira wrote: Nope... Interesting idea... Post a Jira issue for it... -Original Message- From: Fred Lamuette [mailto:[EMAIL PROTECTED] Sent: Friday, October 31, 2003 3:00 PM To: [EMAIL PROTECTED] Subject: [OS-webwork] Exception handler proposal Is there an exception handler mechanism in xwork ? Something like : global-exception type=mypack.ApplicationException action=myExceptionHandlerAction/ that could redirect exceptions inherited from mypack.ApplicationException to the myExceptionHandlerAction action ? Cheers. Richard HALLIER Chef de projet [EMAIL PROTECTED] 01.40.12.41.52 www.uniclick.org UNICLICK --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Old wounds!
To Rickard: I was not very clear, but what I was trying to say was that I want to turn on deprecation in the sense that I want to tell my IDE to warn me when I'm using deprecated stuff. Right now I have that switch off, because it is useless since I only see alot of warnings that I do not care about. To Hani: Ok, you're reasoning makes sense, so leave them in then. Best regards, Dick Zetterberg [EMAIL PROTECTED] - Original Message - From: Hani Suleiman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, November 01, 2003 11:26 PM Subject: Re: [OS-webwork] Old wounds! Well, the deprecation serves as a marker to indicate 'this is not a recommended approach', sure it'll never go away (nothing deprecated in the JDK has gone away either), but it's still worth having in if the official line is that it's a discouraged set of interfaces. On Nov 1, 2003, at 5:15 PM, Rickard Öberg wrote: Dick Zetterberg wrote: Removing the interfaces would break many old applications so that should probably never be done. (Since those are the applications using WW1). So, since the interfaces will not be removed, then the deprecation might instead be removed so you don't get the annoying warnings all the time (or rather, you can turn on the deprecation warnings and not be flooded with warnings you already know about). I suppose you meant turn off the deprecation warnings. /Rickard --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Old wounds!
Maybe add somthing to the deprecation messages that suggest what you should be using instead? On Sat, 1 Nov 2003, Hani Suleiman wrote: Well, the deprecation serves as a marker to indicate 'this is not a recommended approach', sure it'll never go away (nothing deprecated in the JDK has gone away either), but it's still worth having in if the official line is that it's a discouraged set of interfaces. On Nov 1, 2003, at 5:15 PM, Rickard Öberg wrote: Dick Zetterberg wrote: Removing the interfaces would break many old applications so that should probably never be done. (Since those are the applications using WW1). So, since the interfaces will not be removed, then the deprecation might instead be removed so you don't get the annoying warnings all the time (or rather, you can turn on the deprecation warnings and not be flooded with warnings you already know about). I suppose you meant turn off the deprecation warnings. /Rickard --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- Joseph B. Ottinger http://enigmastation.com IT Consultant[EMAIL PROTECTED] J2EE Editor - Java Developer's Journal [EMAIL PROTECTED] --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] Old wounds!
I thought there is a clear message there now. I'll go through and ensure it spells out exactly what should be used. On Nov 1, 2003, at 6:23 PM, Joseph Ottinger wrote: Maybe add somthing to the deprecation messages that suggest what you should be using instead? On Sat, 1 Nov 2003, Hani Suleiman wrote: Well, the deprecation serves as a marker to indicate 'this is not a recommended approach', sure it'll never go away (nothing deprecated in the JDK has gone away either), but it's still worth having in if the official line is that it's a discouraged set of interfaces. On Nov 1, 2003, at 5:15 PM, Rickard Öberg wrote: Dick Zetterberg wrote: Removing the interfaces would break many old applications so that should probably never be done. (Since those are the applications using WW1). So, since the interfaces will not be removed, then the deprecation might instead be removed so you don't get the annoying warnings all the time (or rather, you can turn on the deprecation warnings and not be flooded with warnings you already know about). I suppose you meant turn off the deprecation warnings. /Rickard --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- Joseph B. Ottinger http://enigmastation.com IT Consultant[EMAIL PROTECTED] J2EE Editor - Java Developer's Journal [EMAIL PROTECTED] --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
Re: [OS-webwork] JSP page exceptions
Title: Message I want to specify different error pages depending on what "section" of my site they occur in (ie name space). This is similar to JSP's error page directive but also able to be used with my own application exceptions thrown from actions. The servlet error page mechanism only allows you to specify a mapping between an Exception type and an error page. This could be used to send all exceptions to an action that "remapped" the exception to a more specific error page based on the request uri. But I agree with the previous posts that a WW2 specific framework to handle this mapping would be more useful. - Original Message - From: Michal Mosiewicz To: [EMAIL PROTECTED] Sent: Saturday, October 25, 2003 8:46 AM Subject: Re: [OS-webwork] JSP page exceptions - Original Message - From: Jason Carreira To: [EMAIL PROTECTED] Sent: Friday, October 24, 2003 5:37 PM Subject: RE: [OS-webwork] JSP page exceptions I think this may be JSP implementation specific... where are the errors occuring and what are you seeing/ getting? There is an "error-page" mechanism in JSDK to display errors via customized pages. The same mechanism may beused for all (Servlet/IO/Runtime)(Exception/Error)s. -- Mike
Re: [OS-webwork] Anyone working on Spring Framework Integration?
Cameron - I'm using the latter approach, although this is with 1.3, and I've unfortunately been lazy and haven't looked into WW2 yet. But I assume an ActionInvocation is similar to an Action? In 1.3, I have a SpringActionFactoryProxy that checks to see if the Action is defined in the Spring configuration. If it doesn't find the Action, then the JavaActionFactory eventually loads the Action (which is good so that you don't have to configure Action's that don't need resources from the Spring container). I also use the Hibernate interceptors, and everything works well, and the Webwork files aren't polluted with any Spring stuff. I think this sounds similar to what you suggested below, so I'd say go for the latter. Rob On Sat, 01 Nov 2003, Cameron Braid ([EMAIL PROTECTED]) wrote: Is anyone working on integration between Xwork and the Spring Framework. I have managed to create a webwork interceptor that allows a xwork action to make use of any spring bean by creating a simple mapping. However, I would like a better soloution that uses spring as the action facory.. And I would like to do this without duplication of configuration in both xwork.xml and applicationContext.xml One main reason that I want to use spring is to take advantage of its AOP framework, and most specifically the Hibernate Transaction Interceptor. Therefore I would like to declare the transactional attributes for the action methods within spring, with a refrence to the xwork action. I woule like to still use WebWork's interceptors as normal - timing, logging, params, chain, etc.. because they have different semantics to spring. One way that I think this is possible is to create : Spring Objects : a spring action factory bean, configured with the action namespace and name and the transactional attributes this factory would lookup the action config for the classname and construct the action, wrap it in a proxy, attaching the interceptors. WebWork Objects SpringServletDispatcher - to call ActionProxyFactory.setFactory(new SpringActionProxyFactory()) SpringActionProxyFactory - to override createActionInvocation to use a SpringActionInvocation SpringActionInvocation - to override createAction - to delegate to WebApplicationContextUtils.getWebApplicationContext(servletContext).getBean(beanName) to use the factory within spring to contruct this action. This way the xwork.xml file remains untouched and all that is needed is a bean entry in applicationContext.xml that defines each action's transactional attributes. Something like : bean id=defaultActionTransactionAttributes class=com.datacodex.spring.beans.PropertiesFactoryBean property name=properties props prop key=executePROPAGATION_REQUIRED/prop /props /property /bean bean id=admin.SpringAction class=WebworkActionFactoryBean property name=actionvalue/admin/SpringAction/value/property property name=transactionManagerref local=transactionManager//property property name=transactionAttributesref local=defaultActionTransactionAttributes//property /bean I am open to suggestions for other ways to do this. Anyone have any thoughts / ideas ? Cameron -- Any damn fool can write code that a computer can understand... The trick is to write code that humans can understand. [Martin Fowler http://www.martinfowler.com/distributedComputing/refactoring.pdf] --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
