> So the question about Xdoclet generation of > views.properties made me think about Xdoclet generation of > Xwork.xml. It seems like this would be difficult, since > much of the package definition is outside the scope of > the action and crosses several action classes. Is there a > good way to do this?
Have a look at how the generation for struts-config.xml works. It's quite the same dilemna. > Could we define the package definitions outside the action > classes, then use them as merge points, and add the action > definition into the package? You can have a sort of "template delegation" meaning you would have a "global template" for xwork and an "action template" called from the "global template" for each action. > Anyone developed any Xdoclet plugins? I've written some (the MX4J one and altered the BEA one for WLS7 support). If you already have a DTD or a schema, have a look at XDoclet2 that generates most of the work for you. BTW, how will webwork2 work? will it use the xwork.xml file or another one? I will probably use WW2 on a project of mine, and could contribute on XDoclet support for WW2... Jerome. ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
