On 2002.02.14 22:01:12 -0500 Dmitri Colebatch wrote:
> > 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.
>
After looking for a while I don't see exactly how to do this. I want to
add:
import javax.management.ObjectName;
import org.jboss.util.ObjectNameFactory;
to the imports and
<XDtClass:ifHasClassTag tagName="jmx:mbean" paramName="name">
//default object name
public static final ObjectName OBJECT_NAME =
ObjectNameFactory("<XDtClass:classTagValue tagName="jmx:mbean"
paramName="name"/>");
</XDtClass:ifHasClassTag>
to the class body. I'd like to control this by either a sub-task in
JMXDoclet or a parameter to the mbeaninterface sub task.
I haven't located any examples of doing exactly this... as far as I can
tell when there is a vendor specific output it goes into a vendor specific
file using a vendor specific template and subtask.
I don't quite see the point in using a merge file/point since the only way
I can see to control this would be to include the merge based on the
subtask parameter that I would be using for including /excluding the
snippets above. If there are vendor specific inclusions, why not just
include the whole thing.
Have I missed something big here?
Thanks
david jencks
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
