> I'm only using EntityBeans for generation of > StrutsForms, and I'm > marking it up with Hibernate tags as well to get an > ActionForm and VO. > Then I'm basically throwing it away after that.
Ugly ugly... ;) > > > 1. Mark up a POJO with Hibernate and Struts > Tags. > > > 2. The POJO will be used by Hibernate as and > there > > > will be no > > > additional class generated. > > > 2. The StrutsForm can be generated from this > POJO. > > > > > > So since I *really* want to implement this > > > functionality - where do I > > > dig in and make it possible? Here's an initial > stab > > > at it: > > > > > > 1. Make the strutsform a possible subtask of > > > hibernate doclet, or > > > possibly webdoclet. Basically, allow it to be > run > > > on a POJO rather than > > > an EntityBean only. > > > 2. Make the @struts.form related tags not > depend on > > > @ejb tags. > > > > > > Furthermore, it would be great to be able to > > > indicate which > > > getter/setters get used for Hibernate, and which > > > ones get used for > > > Struts. This might be possible using the > > > @struts.form-field tag. I > > > tried playing with it a little and it seemed > that > > > the only way to make > > > it work was to put a @struts.form name="" and > then @struts.form > > > form-name="" - otherwise they wouldn't generate. > > > > > > Any advice would be great. I'm trying to get > this > > > done ASAP, and I'm > > > way over my head here - but I don't want to > resort > > > to writing a > > > ValidatorForm and POJO by hand. I will if I > have > > > to, but I'd rather > > > extend Xdoclet. > > > > Well, only problem with strutsform is that in > original > > design it generates bulk data setters for the > > DataObject classes. ( or mybe it was changed > > meanwhile? ) > > > > I don't believe it has this anymore - just > getters/setters. It still does this. If you generate data object... > > You may look at the <beanfinfo/> subtask - it > allows > > generation of beaninfo for another class - used to > > generate bean info for DataObjects , but tags are > on > > entity bean. > > > > Ugh, entity beans - I don't want those. It was another point - <beaninfo/> generates beaninfo for the class where it located, but has possibility to generate for anothe class name, using properties of defining class. The same approach can be done for <strutsform/> - generate form with properties, and also buld setter for the defining class. regards, ===== Konstantin Priblouda ( ko5tik ) Freelance Software developer < http://www.pribluda.de > < play java games -> http://www.yook.de > < render charts online -> http://www.pribluda.de/povray/ > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ------------------------------------------------------- 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
