Matt Raible wrote:
My POJO was just that, a plain old java object that didn't extend
anything. However, today I discovered that it had to extend EntityBean
and I had to use @ejb tags in order to generate a struts.form from it.
That's the part that smells to me ;-)
No argument from me about entity beans smelling! :)) We don't use them.
Cool. That same concept, of course, could be extended to generate whatever you wanted from a POJO... so generate your entity bean if you want too.this class to generate a StrutsForm, complete with struts.validation tags as specified, and then to generate the JSP and .properties file based on your strutsgen tool.
I believe there will be some duplication between the hibernate objectsYup, we use BeanUtils.copyProperties extensively for transferring forms to data objects. I've written several Converter implementations and registered them to handle custom object or specialized type conversions too. Works sufficiently well for our purposes.
and my struts forms - but that's how it should be - one for the UI and
one for the data tier. Hopefully I can use BeanUtils.copyProperties to
get information back and for the between the two.
It'll work! :)have to modify 3 different classes to add 1 stinkin' column. So I'm generally trying to improve the method I've used in the past, and I'm hoping that by using one class, I can generate these 3 classes by adding one new getter/setter. It might work, it might not - there's only one way to find out!
You might have to write a custom tag handler to wrap any complex logic that cannot be accomplished with the builtin tag langauge. Use my strutsgen code for examples of that.
Erik
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
