Gregory, > While adding xsd support to the web plugin, I realised that the ejb > plugin has a nice util class for versions, holding DTDs and XSDs > references. I'd need the same thing for the web plugin; its currently > a bunch of methods on the plugin itself, not the nicest. > Some time ago I also added a couple of custom jelly tags, in the web > plugin itself. (I specifically remember that I wrote the > ConditionalElementTag, dunno about the MergeTag - actually I'm have no > clue how other plugins handle merging right now - maybe we should > synch them).
Yesterday I thought about this. Maybe an xdoclet-plugins specific Tag-library. > > Please have a look at those tags. How about promoting this to xdoclet > ? (the EjbVersion class, which could renamed in XmlDocVersion or > something; and the tags) If we gather I flexible approach I am ok on this. > > Also about dtd/xsd, pls disregard my last question, since I found an > example of how to handle this in the ejb plugin. I'm a bit puzzled by > the <x:replaceNamespace> necessary after the root element, though. > Isn't there a simpler way for all this? I needed "replaceNamespace" because I needed to support for DTD versions, xml elements in default namespace (empty) and for XSD version, the xml nodes needed to be in "http://java.sun.com/xml/ns/j2ee"; namespace. As jelly works with a xml-pipeline (ie, SAX ContentHandler), it parses the script with a SAX parser and then "runs" the script with a "ContentHandler" writer, this was the only I made to make empty namespaces "source" script, to gain a namespace when needed. replaceNamespace in DTD versions does nothing, I mean when fromURI and toURI are the same, it just does nothing, otherwise, It applies http://java.sun.com/xml/ns/j2ee"; namespace to all inner nodes. > BTW, Diogo, what's the status of the ejb plugin, roughly? What's > supported, what not? Maybe we should make a couple of jira issues + > roadmap to be able to followup? Well, I've navigating through xdoclet-1.2.3 cvs snapshot (several months ago), and I have been copying its behaviour. ejb-jar.xml is almost complete. Interfaces are in the same state as when I started before - they are the next. ClassPK is empty generated class yet. I'll try to make all xdoclet1 available generating plugins before move to server specific descriptors. I am +1 on such a roadmap on jira - shot them, you're the ones with more ejb experience that I do - I guess. Regards Diogo ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ xdoclet-plugins-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xdoclet-plugins-interest
