I had a go with struts xdoclet tags, the advantages aren't that great but it does help keeping the mapping information in the same file. Given there are no real cross container issues relating to the struts-config file then its not as useful as webdoclet tags. The other problem is that i think you can only have one mapping per class and you end up having to merge the rest. But the principle of having the mapping stuff in the class does make sense to me.

hibernate is something else altogether, hibernatedoclet is a great help. Having you relationships defined in the class saves darting around several files, and also generating the xml means that it undergoes preliminary validation.

Maven. I just haven't had the silly amount of time required to get anything going with this.

Mark

On 27 Jun 2004, at 23:13, Rick Reumann wrote:

Andy Akins wrote:

but I'm fairly new to Maven but have coded two simple struts
apps with
it - and XDoclet is brand new to me. I'm looking to combine
all of the
above (and eventually Hibernate - but that's for a later day).

I don't see what advantage using XDoclet with Struts is? If someone can show me how it helps I'd love to see it. On this one project I inherited, it uses XDoclet with Struts and it makes things worse. For example, I like having a nice config file that I can modify (strut-config), yet with XDoclet, the struts config action mappings are generated by action mapping definitions defined at the top of the actual Action opbjects. That makes no sense to me. Now in order to change a return value, you have to modify source code versus just modifying a config file. I can see the benefit for XDoclet in other projects (ie EJB code generation) but for Struts I still haven't found where it helps, but I'm willing to be enlightened:)


--
Rick

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to