glassfish
  1. glassfish
  2. GLASSFISH-11402

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

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Incomplete
    • Affects Version/s: 9.1.1
    • Fix Version/s: V3
    • Component/s: web_services
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      11,402

      Description

      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 http://jax-ws.dev.java.net. RI's version is JAX-
      WS RI 2.1.3.1-hudson-749-SNAPSHOT. -->

      <!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-
      WS RI 2.1.3.1-hudson-749-SNAPSHOT. –

      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 http://jax-ws.dev.java.net. RI's version is JAX-
      WS RI 2.1.3.1-hudson-749-SNAPSHOT. -->

      as expected.

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

        Activity

        Hide
        Hong Zhang added a comment -

        assign to webservices team for initial evaluation

        Show
        Hong Zhang added a comment - assign to webservices team for initial evaluation
        Hide
        ahutatatong added a comment -

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

        Show
        ahutatatong added a comment - Created an attachment (id=4154) Maven Plugin that changes the version layout (replaces dots with minus)
        Hide
        ahutatatong added a comment -

        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:

        <plugin>
        <groupId>de.afb.maven</groupId>
        <artifactId>ear-post-processor</artifactId>
        <executions>
        <execution>
        <id>postProcess</id>
        <phase>install</phase>
        <goals>
        <goal>postProcess</goal>
        </goals>
        <configuration>
        <targetDirectory>$

        {project.build.directory}

        </targetDirectory>
        <nameOfEar>$

        {project.build.finalName}

        .$

        {project.packaging}

        </nameOfEar>
        </configuration>
        </execution>
        </executions>
        </plugin>

        Show
        ahutatatong added a comment - 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: <plugin> <groupId>de.afb.maven</groupId> <artifactId>ear-post-processor</artifactId> <executions> <execution> <id>postProcess</id> <phase>install</phase> <goals> <goal>postProcess</goal> </goals> <configuration> <targetDirectory>$ {project.build.directory} </targetDirectory> <nameOfEar>$ {project.build.finalName} .$ {project.packaging} </nameOfEar> </configuration> </execution> </executions> </plugin>
        Hide
        ramapulavarthi added a comment -

        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
        problem.

        Show
        ramapulavarthi added a comment - 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 problem.

          People

          • Assignee:
            ramapulavarthi
            Reporter:
            ahutatatong
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: