Issue Details (XML | Word | Printable)

Key: GLASSFISH-11402
Type: Bug Bug
Status: Resolved Resolved
Resolution: Incomplete
Priority: Critical Critical
Assignee: ramapulavarthi
Reporter: ahutatatong
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Glassfish regenerates wsdl (even contract-first is used) when deploying EAR where EJB's contain version numbers (seperated by point) in its filename

Created: 07/Jan/10 07:37 AM   Updated: 02/Sep/10 04:37 PM   Resolved: 02/Sep/10 04:37 PM
Component/s: web_services
Affects Version/s: 9.1.1
Fix Version/s: V3

Time Tracking:
Not Specified

File Attachments: 1. Text File ear-post-processor.tar.gz (13 kB) 11/Jan/10 08:36 AM - ahutatatong


Operating System: All
Platform: All

Issuezilla Id: 11,402
Participants: ahutatatong, Hong Zhang and ramapulavarthi

 Description  « Hide

Due to version numbers (e.g. xxx-1.0-SNAPSHOT.jar) in EJBs, glassfish
regenerates the wsdl files (i assume it switches to code-first). Besides some
other problems that occur during the generation (which is off the topic), all
ws:at declarations are lost.

The wsdl file viewed via ?wsdl starts with:

<!-- Published by JAX-WS RI at RI's version is JAX-
WS RI -->

<!-- Generated by JAX-WS RI at RI's version is JAX-

After removing the point in the filename (eg. xxx-1-0-SNAPSHOT.jar) everything
works fine.

The resulting wsdl then starts only with:

<!-- Published by JAX-WS RI at RI's version is JAX-
WS RI -->

as expected.

In order to get things running again, i have to change the versionnumber of all
included ejbs!

Hong Zhang added a comment - 07/Jan/10 08:09 AM

assign to webservices team for initial evaluation

ahutatatong added a comment - 11/Jan/10 08:36 AM

Created an attachment (id=4154)
Maven Plugin that changes the version layout (replaces dots with minus)

ahutatatong added a comment - 11/Jan/10 08:41 AM

For those facing the same problem, i attached a plugin that can be used as part of the build cycle in order to remove the dots in
the resulting ear file. It is crucial that the plugin is executed after the package life-cycle, as it needs the original ear
(actually it would work with any jar/zip file) in order to do its work.

Here is the usage:


ramapulavarthi added a comment - 02/Sep/10 04:37 PM

I appreciate for attaching post processor plugin. But, I can't understand the
issue. Please attach a deployable artifact or maven project to reproduce the