Stern, Michael W wrote:
> Ok, I have figured out how to use the _extends(). I am able to produce
> the results I desired. However, I am still facing a challenge in
> externalizing the configuration. Currently my PluginImpl just hardcoded
> some 'if' logic to set the _extends() to a hardcoded class definition.
> I believe the plug-in should allow for a more dynamic usage.
Yeah, that would be nice.
> Ideally I would like to use my existing xpath notation in an external
> binding (.xjb) file, to set the option for a given complex type. If
> that is not feasible, I would at least like to use the external binding
> file to configure my plug-in manually. Can you please provide some
> examples of how to do the external configuration, and specifically how
> the pattern matching is used to trigger a plug-in customization?
I think you can look at some of the existing plugins (like see
code-injector plugin) for how to recognize cusotmizations.
> I would be more than willing to contribute my plug-in to the commons
> project.
Cool! Let me know your java.net user id so that we can add you as a
developer with a commit access.
> Additionally, the collection-setter-injector.jar is missing from the
> commons page
> (https://jaxb2-commons.dev.java.net/collection-setter-injector/). I
> would find this plug-in very useful, and was hoping it could get hosted
> along with the existing usage guide.
Thank you for volunteering to fix this! Sounds like the first thing
you'd want to do after a commit access is to update www/index.html.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com