Very nice work with the DynamicConfigurator Erik. Thanks a zillion! Bye-bye BCEL ;-)
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Erik > Hatcher > Sent: 27. april 2002 22:27 > To: Ara Abrahamian; [EMAIL PROTECTED] > Subject: Re: [Xdoclet-devel] Ant's new DynamicConfigurator > > > > Can you elaborate on this XMLCatalog thing? > > Its just a simple Ant datatype, but provides DTD/entity resolution > capabilities allowing them to be resolved from a specified > classpath (rather > than simply Ant's classpath). Here is the URL to the source code: > > <http://cvs.apache.org/viewcvs/jakarta-ant/src/main/org/apache/too > ls/ant/typ > es/XMLCatalog.java?annotate=1.9> > > I'm thinking a similar datatype should exist (yes, refactoring > XMLCatalog to > have a parent class to hold the common pieces makes sense!) to accept all > the classpath stuff and at first allow for a properties file to be listed > giving name/classname associations. This could allow <ejbjar>, > for example, > to be extended by a vendor by providing a JAR with the properties file and > the associated class files for the implementation. How <ejbjar> finds out > about the associations is not something I've completely worked out, but > probably not auto-discovered initially - perhaps with a simple > pluginref="..." attribute that could list the defined datatype id. I also > considered the idea of system properties being used to provide > the mappings, > which would allow things to be more "auto discovered" but that feels a bit > hack-ish. Not sure yet. Gotta decide soon if Ant's <serverdeploy>, > <ejbjar>, and <condition> tasks will get refactored to support it. > > I want to be gentle with how this is implemented in Ant's core/optional > tasks so as to not abuse this feature too much given that I had to beg to > get it in! :) > > > Actually in 2-3 days or so the MODULE_REFACTORING_BRANCH will be > > functional and you'll be able to play with it. It's actually cool and I > > think it'll be great if Ant could do something like that too ;-) > > There is not enough time to get that kind of feature added fully > though, and > its also important enough to do right the first time. Ant2 will fully > support a pluggable architecture. Ant 1.x will have to get by with us > roughing it in somehow. > Well, we'll use our homegrown deployment descriptors in META-INF/xdoclet.xml to map logical subelement names to classes in the meanwhile. Like this: <subtask name="webxml" implementation-class="xdoclet.modules.web.WebXmlSubTask" parent-task-class="xdoclet.web.WebDocletTask" /> Aslak > Erik > > > > _______________________________________________ > Xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
