[
https://issues.apache.org/jira/browse/AXIS2-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681862#action_12681862
]
Mark Stickel commented on AXIS2-2633:
-------------------------------------
The correct configuration in order to get the JiBX bindingfile property (or any
property, for that matter) read in by the wsdl2code plugin should be like this:
<plugin>
...
<configuration>
<packageName>com.foo</packageName>
<databindingName>jibx</databindingName>
<wsdlFile>${project.build.sourceDirectory}/../wsdl/foo.wsdl</wsdlFile>
<options>
<property>
<name>bindingfile</name>
<value>${project.build.sourceDirectory}/../jibx/foo-binding.xml</value>
</property>
</options>
</configuration>
</plugin>
For reference, see here (Properties is near the bottom of the page):
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
> axis2-wsdl2code-maven-plugin missing extension option "bindingfile" for JiBX
> ----------------------------------------------------------------------------
>
> Key: AXIS2-2633
> URL: https://issues.apache.org/jira/browse/AXIS2-2633
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Tools
> Affects Versions: 1.2
> Environment: all platforms
> Reporter: Armin Ehrenfels
> Assignee: Jochen Wiedmann
>
> axis2-wsdl2code-maven-plugin doesn't support extension options such as
> "-Ebindingfile" for JiBX.
> SUGGESTION:
> 1. in the plugin configuration, introducing an additional option
> <extensionOptions>, similar to namespaceURIs, like this:
>
> <extensionOptions>
> <extensionOption>
> <name>xxx</name>
> <value>yyy</value>
> </extensionOption>
> ...
> </extensionOptions>
> 2. in the mojo, for each extension option adding the name/value pair to
> optionsMap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
