Plugin for what those methods mean.
| Access | Constructor and Description |
|---|---|
| public |
| Modifier and Type | Method and Description |
|---|---|
| private static void | |
| public List | getCustomizationURIs()
Overrides com. Returns the list of namespace URIs that are supported by this plug-in as schema annotations. |
| public String | getOptionName()
Implements abstract com. Gets the option name to turn on this add-on. |
| public String | getUsage()
Implements abstract com. Gets the description of this add-on. |
| public boolean | isCustomizationTagName(String nsUri, String localName)
Overrides com. Checks if the given tag name is a valid tag name for the customization element in this plug-in. This method is invoked by XJC to determine if the user-specified customization element is really a customization or not. |
| public boolean | run(Outline model, Options opt, ErrorHandler errorHandler)
Implements abstract com. Run the add-on. |
| PluginImpl | back to summary |
|---|---|
| public PluginImpl() | |
| checkAndInject | back to summary |
|---|---|
| private static void checkAndInject(Collection<? extends CustomizableOutline> outlines) | |
| getCustomizationURIs | back to summary |
|---|---|
| public List Overrides com. Doc from com. Returns the list of namespace URIs that are supported by this plug-in as schema annotations. If a plug-in returns a non-empty list, the JAXB RI will recognize these namespace URIs as vendor extensions (much like "http://java.sun.com/xml/ns/jaxb/xjc"). This allows users to write those annotations inside a schema, or in external binding files, and later plug-ins can access those annotations as DOM nodes. See http://java.sun.com/webservices/docs/1.5/jaxb/vendorCustomizations.html for the syntax that users need to use to enable extension URIs.
| |
| getOptionName | back to summary |
|---|---|
| public String getOptionName() Implements abstract com. Doc from com. Gets the option name to turn on this add-on. For example, if "abc" is returned, "-abc" will turn on this plugin. A plugin needs to be turned on explicitly, or else no other methods of will be invoked.
Starting 2.1, when an option matches the name returned
from this method, XJC will then invoke
| |
| getUsage | back to summary |
|---|---|
| public String getUsage() Implements abstract com. Doc from com. Gets the description of this add-on. Used to generate a usage screen.
| |
| isCustomizationTagName | back to summary |
|---|---|
| public boolean isCustomizationTagName(String nsUri, String localName) Overrides com. Doc from com. Checks if the given tag name is a valid tag name for the customization element in this plug-in. This method is invoked by XJC to determine if the user-specified customization element is really a customization or not. This information is used to pick the proper error message.
A plug-in is still encouraged to do the validation of the customization element in the
| |
| run | back to summary |
|---|---|
| public boolean run(Outline model, Options opt, ErrorHandler errorHandler) Implements abstract com. Doc from com. Run the add-on.
This method is invoked after XJC has internally finished
the code generation. Plugins can tweak some of the generated
code (or add more code) by using Note that this method is invoked only when a is activated.
| |