> -----Original Message----- > From: James Cook [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 19, 2003 7:42 PM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] Xdoclet support for WebWork > > > I am using xdoclet to generate my views.properties file, > although I am leaning towards not going this route. In the > back of my head I feel that I am coupling my views to tightly > with my action. I suppose there has to be a coupling > somewhere (views.properties), but it is just so damn convenient. > > Three questions: > > 1. Is there a way to output the XML version rather than > views.properties? 2. Is there a way to merge in global > handlers (i.e. CATASTROPHIC=screwed.jsp)? 3. Is there a way > to do CommandDriven handlers? > > #3 above is the only one that is critical... > > >
I don't think so, but I'm interested in making this possible for Xwork. What I was thinking was something like this: /** * * @xwork.alias name="alias1" * @xwork.param name="foo" value="fooVal" * @xwork.result name="success" type="chain" * @xwork.result.param resultname="success" name="actionName" value="bar" */ These could be applied either at the class level, in which case they would default to a method name of "execute" or at the method level, in which case they could apply to that method for the alias. I'm not sure how you can define higher level structures, like packages with namespaces. I assume you'd need a merge file with the package declaration w/ namespace, interceptor definitions, global-results, etc. Jason ------------------------------------------------------- This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
