> Don't know if this has been discussed or not, but what do we think about > having ConfigTasks that could be used to provide further configuration > information that might not belong inside a particular SubTask? > > For instance: > > <jboss ...> > <jbosscmp> > <defaults datasource="" datasourcemapping="" createtable="" > removetable="" ... /> > </jbosscmp> > </jboss> > > Otherwise, <jboss ...> is gonna keep growing as developers want to add > more > and more attributes configurable by the build. > > Reference > http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?k ey > =X > DT-140 for an issue where the user wants something that is in the defaults > element of jbosscmp-jdbc.xml to be settable from the jboss SubTask. > > If this ConfigTask doesn't make sense, should I suggest to the user that > he > use a combination of the jbosscmp-jdbc-defaults.xml merge point and Ant > copy > filters? > > Or, just keep growing the JBoss SubTask?
Imho we should have separate jbosscmp/jbossdd/jbossblabla subtasks instead of a giant jboss subtask for all jboss-ejb stuff. Imho for the time being, just let the subtask grow and grow :-) Ara. ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
