But care must be taken not to overuse it. Putting a lot of properties from different classes will lead to an uncontrollable mess.
I also have another idea. We already have merge points, so you really don't need to put a deployment tag like create-table in your source. But to use it you need to create a separate file, mostly per class. So what do you think about extending the tag search mechanism as below: Instead of putting jboss:create-table in com.foo.MyBean, put <property name="com.foo.MyBean|jboss:create-table" value="true"/> in build.xml. For a method: name="com.foo.MyBean.methodName|jboss:blabla". Combined with a separate properties file to hold properties you have a better way of specifying deployment-oriented tags like create-table. We can also add a <property/> element in ejbdoclet/webdoclet/etc Tasks, so a property is where it is actually used. The only thing that concerns me is we have different ways to do things and people may misuse/overuse some of them or get confused. Anyway, after all I think putting a lot of properties is not a good idea; it's not scalable for a big project with a lot of classes. maybe seeing create-table in the source is a better idea?! Thoughts? Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-user- > [EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] > Sent: Thursday, October 04, 2001 4:25 PM > To: Dmitri Colebatch; [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [Xdoclet-user] Re: [Xdoclet-devel] using ant properties in tags > > Wow! What a good idea! > This lets XDoclet users configure the outcome of XDoclet on the > build.xml level, right? > > I recommend people using this feature put the properties in a separate > properties file, and having Ant read that in. That way, the > configuration is moved out even one level furter, namely to a > properties file. For the Ant users who are not familiar with this > technique: > > <property file="jboss.properties"/> > > And the contents of the jboss.properties file would be: > > jboss.create.table=true > jboss.remove.table=true > jboss.tuned.updates=true > jboss.read.only=false > > > That way, the values can be altered without having to edit the > build.xml file. > > <aslak/> > > ----- Original Message ----- > From: Dmitri Colebatch <[EMAIL PROTECTED]> > Date: Thursday, October 4, 2001 1:19 pm > Subject: [Xdoclet-devel] using ant properties in tags > > > I've just committed a change that lets you use ant properties in tag > > values. THere's a pretty simple example in Account: > > > > * @jboss:table-name "account" > > * @jboss:create-table "${jboss.create.table}" > > * @jboss:remove-table "${jboss.remove.table}" > > * @jboss:tuned-updates "${jboss.tuned.updates}" > > * @jboss:read-only "${jboss.read.only}" > > > > where the corresponding values are defined in the build.xml > > > > <!-- These are here to test the use of properties in @tags --> > > <property name="jboss.create.table" value="true" /> > > <property name="jboss.remove.table" value="true" /> > > <property name="jboss.tuned.updates" value="true" /> > > <property name="jboss.read.only" value="false" /> > > > > Jason - let me know if this does the trick > > > > cheers > > dim > > > > > > _______________________________________________ > > Xdoclet-devel mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel > > > > > _______________________________________________ > Xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
