--- "Inger, Matthew" <[EMAIL PROTECTED]> wrote: > I missed the following: > > <component > classname="org.generama.VelocityTemplateEngine"/> > <component > classname="org.generama.JellyTemplateEngine"/> > > Personally, I find the new task exremely difficult > to use, > and troubling that I would have to know that i need > to include > velocity and jelly to use the hibernate module.
Stricktly speaking, you do not need velocity template engine to run hibernate ( just copy-paste remainder in my project ) > That should all > be transparent, as I could personally care less what > templating > engine is needed to run. I just know that i want to > run hibernate. Well, hibernate plugin said that it missed dependent component... Though pico container could be improved to report component which is really missing > Shouldn't the hibernate plugin automatically > add/register the > other components? no. it's in pico philosofy that component does not know anything about container. ( and this does not depend on it ) > Better yet, why is there not a > <hibernate-doclet> > task, which could extend <xdoclet> task, and > automatically add the > appropriate components on it's own? because xdoclet is a task which just run plugins. ( and neither knows nor assumes anything about them. ) so it registers some basics ( qdox parser, writer mapper ) and starts container. >I'd be willing > to write this > task (it shouldn't be difficult, but the only thing > is I'm not sure > what all the parameters to the Hibernate component > are, so the task > might end up being somewhat incomplete): > > <hibernate-doclet destdir="abc"> > <fileset ... /> > </hibernate-doclet> I do not see advantage in such task. Components are just sufficient. And not everybody has just hibernate generation - on some projects I have 5-7 different plugins running over same parsed files. > would end up being the equivalent of: > > <xdoclet> > <fileset ... /> > <component > classname="org.generama.VelocityTemplateEngine"/> > <component > classname="org.generama.JellyTemplateEngine"/> > <component > classname="org.xdoclet.plugin.hibernate.HibernateMappingPlugin" > destdir="mappings2"/> > </xdoclet> > > Each attribute on "hibernate-doclet" would translate > to an attribute on the > component. I just don't know what the right > attributes are. Well, you could look them up in source. ( though to be successfull, you'll have to checkout at least generama & xdoclet-2 ( maybe qdox ) - everything living on codehaus.org regards, ===== ----[ Konstantin Pribluda ( ko5tik ) ]---------------- Zu Verstärkung meines Teams suche ich ab Sofort einen Softwareentwickler[In] für die Festanstellung. Arbeitsort: Mainz Skills: Programieren, Kentnisse in OpenSource-Bereich ----[ http://www.pribluda.de ]------------------------ __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
