Allow to specify jars for wsimport goal in Maven plugin

[glassfishrobot]

The wsimport tool accepts both .wsdl and .jar files. The jars normally contain a shared schemas and corresponding generated classes along with META-INF\sun-jaxb.episode file. This allows separate compilation and reuse of a common schema between multiple projects without copying xsd files around.

Unfortunately the current Maven plugin does not allow to specify jars in a same way and only supports the wsdl files as an input. The attached patch removes such limitation and it simply adds resolved project dependencies to the list of arguments passed to wsimport tool.

Another important change is a catalog resolver that is capable of resolving schema files from classpath as it is used in maven-jaxb2-plugin plugin and described at https://maven-jaxb2-plugin.dev.java.net/docs/guide.html#Catalogs

Environment

Operating System: All Platform: All

Affected Versions

[current]

[glassfishrobot]

Reported by euxx@java.net

[glassfishrobot]

euxx@java.net said: Created an attachment (id=16) Patch to support separate schema generation and resolving catalogs from classpath

[glassfishrobot]

tdrury@java.net said: Created an attachment (id=21) patch to read META-INF/sun-jaxb.episode from dep jars

[glassfishrobot]

tdrury@java.net said: euxx's patch worked nicely, but didn't include the reading of episode files. My patch should be applied after euxx's patch and it will copy META-INF/sun- jaxb.episode files from dependent jars into the target folder giving them names based on the jar, then add these episodes as binding files (-b).

[glassfishrobot]

atrajano said: This should also support the notion of copying the WSDL resources as well for those occassions we need to refer to the object via the wsdlLocation annotation parameter in @WebService or @WebServiceProvider

[glassfishrobot]

d3atiq said: Hi,

I am working on a project where the XSDs and WSDLs are given by an external standardizing entity and I need to implement both a web service that conforms to the given WSDL and a XML file processor that receives the same XML in a file. I have already succeeded in creating an artifact that contains the generated JAXB2 mappings of the XSDs and it contains an embedded sun-jaxb.episode. Now I am trying to create the web service skeletons from the WSDLs with the maven-jaxws-plugin and I would like to depend on the other artifact rather than include the XSDs again in this project. The way I see, this bug fix would be what I need to be able to do this modularization in my project, if the plugin already had the correction. Is there some Maven repository that contains a public beta version of the plugin where these patches are applied? If so, which repository and which version? I would like to avoid having to build an in-house version of the plugin to be able to modularize my web service artifacts.

[glassfishrobot]

File: jaxws-maven-plugin.patch Attached By: euxx@java.net

[glassfishrobot]

File: tim1.diff Attached By: tdrury@java.net

[glassfishrobot]

This issue was imported from java.net JIRA JAX_WS_COMMONS-44