> 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
The imports should be taken care of automatically - assuming the imports are also in
the implementation class. Any classes imported
into the class, will also be imported into the interface (using the
<XDtClass:importedList
currentClass="<XDtClass:fullClassName/>"/> tag).
> <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.
So controlling it via the presense or absense of a file int he merge directory isn't
acceptable?
> 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.
Do really need to control it? Maybe I'm missing something in what you're after, but
the way I see it you basically want to use this
for the JBoss build, and maintain the JBoss coding standards (caching the
OBJECT_NAME). So in your case, I still see that a merge
point in the mbean.j template, you then put the above snippet in a merge file.
like I said, maybe I'm missing something, but that seems to fit the requirements
cheesr
dim
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
