> Is the best way to deal with this to make a jboss-standard-mbean.j in > vendor with this new convention?
A merge point in the standard-mbean.j I would think. Then you can add the jboss specific stuff as another template. > Should I also write a jboss subtask of jmxDoclet to use this template? if all it is is template changes, it shouldn't be required. > I'd kind of like to leave the string OBJECT_NAME in mbean.j for use with > jboss 2.4: it seems like a reasonable convention to me in any case. > > And now for another question... > > I've wondered about generating dynamic mbeans from annotated code. When I > write a dynamic mbean by hand, I put the invoke and metadata methods in the > class itself. Is there any way to add code to an existing file and compile > the modified file rather than the original? Another possibility is to have > the dynamic mbean extend the original class, so if modifying the original > file is too hard I could do that instead. > > Has anyone tried to do this? not I. But the guys from OpenJMX might have something in mind, Jerome - are you on this list? cheers dim _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
