[
http://jira.codehaus.org/browse/MAXISTOOLS-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MAXISTOOLS-22:
--------------------------------------
Component/s: wsdl2java
Description:
Regarding sourceDependency option for wsdl2java:
1) Add support for extracting wsdl file from a .war (instead of .jar)
2) Add support for using a wsdl file directly from a dependency (an attachment)
3) Inherit version of dependency from project dependencies.
1) We package our other module (containing the wsdl file) as a war, not a jar.
The "jar" extension is hardcoded, and it might be nice to be able to specify a
war in the sourceDependency definition instead.
2) In fact, I've now attached our wsdl file directly as an attachment to the
project, so the dependency looks like:
{code:xml}
<groupId>com.group</groupId>
<artifactId>artifact</artifactId>
<version>1.0</version>
<classifier>wsdl</classifier>
<type>wsdl</type>
{code}
I've altered the DefaultWSDL2JavaPlugin to find this in the local repository
rather than extracting from a jar.
3) It's a bit incongruous to then specify the wsdl2java dependency as
{code:xml}
<sourceDependency>
com.group:artifact:1.0:/dir/file.wsdl
</sourceDependency>
{code}
The configuration would be better as:
{code:xml}
<sourceDependency>
<groupId>com.group</groupId>
<artifactId>artifact</artifactId>
<fileInArchive>/dir/file.wsdl</fileInArchive>
</sourceDependency>
{code}
... and the version1.0 would be inherited from the project dependencies.
I've implemented a hacked workaround (to issue 2 only) locally so that we can
work in our preferred manner, but I'm sure someone with more ability and
dedication can do much better!
was:
Regarding sourceDependency option for wsdl2java:
1) Add support for extracting wsdl file from a .war (instead of .jar)
2) Add support for using a wsdl file directly from a dependency (an attachment)
3) Inherit version of dependency from project dependencies.
1) We package our other module (containing the wsdl file) as a war, not a jar.
The "jar" extension is hardcoded, and it might be nice to be able to specify a
war in the sourceDependency definition instead.
2) In fact, I've now attached our wsdl file directly as an attachment to the
project, so the dependency looks like:
<groupId>com.group</groupId>
<artifactId>artifact</artifactId>
<version>1.0</version>
<classifier>wsdl</classifier>
<type>wsdl</type>
I've altered the DefaultWSDL2JavaPlugin to find this in the local repository
rather than extracting from a jar.
3) It's a bit incongruous to then specify the wsdl2java dependency as
<sourceDependency>
com.group:artifact:1.0:/dir/file.wsdl
</sourceDependency>
The configuration would be better as:
<sourceDependency>
<groupId>com.group</groupId>
<artifactId>artifact</artifactId>
<fileInArchive>/dir/file.wsdl</fileInArchive>
</sourceDependency>
... and the version1.0 would be inherited from the project dependencies.
I've implemented a hacked workaround (to issue 2 only) locally so that we can
work in our preferred manner, but I'm sure someone with more ability and
dedication can do much better!
> maven-axistools-plugin wsdl2java sourceDependency improvement suggestions
> -------------------------------------------------------------------------
>
> Key: MAXISTOOLS-22
> URL: http://jira.codehaus.org/browse/MAXISTOOLS-22
> Project: Maven 2.x Axis Tools Plugin
> Issue Type: New Feature
> Components: wsdl2java
> Reporter: Mike Laurie
> Priority: Minor
>
> Regarding sourceDependency option for wsdl2java:
> 1) Add support for extracting wsdl file from a .war (instead of .jar)
> 2) Add support for using a wsdl file directly from a dependency (an
> attachment)
> 3) Inherit version of dependency from project dependencies.
> 1) We package our other module (containing the wsdl file) as a war, not a
> jar. The "jar" extension is hardcoded, and it might be nice to be able to
> specify a war in the sourceDependency definition instead.
> 2) In fact, I've now attached our wsdl file directly as an attachment to the
> project, so the dependency looks like:
> {code:xml}
> <groupId>com.group</groupId>
> <artifactId>artifact</artifactId>
> <version>1.0</version>
> <classifier>wsdl</classifier>
> <type>wsdl</type>
> {code}
> I've altered the DefaultWSDL2JavaPlugin to find this in the local repository
> rather than extracting from a jar.
> 3) It's a bit incongruous to then specify the wsdl2java dependency as
> {code:xml}
> <sourceDependency>
> com.group:artifact:1.0:/dir/file.wsdl
> </sourceDependency>
> {code}
> The configuration would be better as:
> {code:xml}
> <sourceDependency>
> <groupId>com.group</groupId>
> <artifactId>artifact</artifactId>
> <fileInArchive>/dir/file.wsdl</fileInArchive>
> </sourceDependency>
> {code}
> ... and the version1.0 would be inherited from the project dependencies.
> I've implemented a hacked workaround (to issue 2 only) locally so that we can
> work in our preferred manner, but I'm sure someone with more ability and
> dedication can do much better!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
