4 Replies Latest reply on Oct 15, 2013 12:47 PM by howardl815

    Using old jaxrpc on Jboss EAP 6.1




      We are in the middle of migrating from WebLogic to JBoss EAP 6.1, and we ran into a problem with one of our old jaxrpc based web service package from Bloomberg to work with JBoss. We get Linkage error whenever it reaches the line where we actually call their web service implementation. (We generate source code and jar file from the ant tag they gave us which uses jaxrpc)


      <target name="wscompile" depends="ws-init" description="generates JAX-RPC stubs, ties, serializers, and WSDL files used in bloomberg data license clients and services">
      <java classname="com.sun.xml.rpc.tools.wscompile.Main" fork="true" maxmemory="128m" failonerror="true">
      <arg value="-gen:client" />
      <arg value="-f:documentliteral,wsi" />
      <arg line="-d ${generated.build.dir}" />
      <arg line="-nd ${generated.xml.dir}" />
      <arg line="-s ${generated.java.dir}" />
      <arg line="-mapping ${generated.xml.dir}/jaxrpc-mapping.xml" />
      <arg value="-keep" />
      <arg value="-verbose" />
      <arg value="-Xprintstacktrace" />
      <arg value="${dlws.config.dir}/dlps.xml" />
      <classpath refid="wscompile.classpath" />
      <sysproperty key="com.sun.net.ssl.internal.www.protocol" value="${ssl.protocol}" />
      <sysproperty key="javax.net.ssl.keyStore" value="${ssl.keystore}" />
      <sysproperty key="javax.net.ssl.keyStorePassword" value="${ssl.keystore.pass}" />
      <sysproperty key="javax.net.ssl.keyStoreType" value="${ssl.keystore.type}" />
      <target name="wscompile-build" depends="wscompile" description="generates jar file of all the jax-rpc client generated classes from bloomberg wsdl">
      <jar basedir="${generated.java.dir}" destfile="${lib.dir}/bbws-client-src.jar" />
      <jar basedir="${generated.build.dir}" destfile="${lib.dir}/bbws-client.jar" />


      Does JBoss EAP 6.1 support jax rpc?


      Thanks for any help.

        • 1. Re: Using old jaxrpc on Jboss EAP 6.1

          Yes, JBoss EAP 6.1 supports JAXRPC.

          Which exception are you actually getting?

          • 2. Re: Using old jaxrpc on Jboss EAP 6.1

            Hi Alessio,


            We are getting Linkage error.


            [Server:ha-server-1] 16:36:20,903 WARN  [org.jboss.modules] (Thread-1678 (HornetQ-client-global-threads-1650353406))

            Failed to define class com.bloomberg.datalic.dlps.PerSecurityWS_Service_Impl in Module "deployment.framework.ear:main"

            from Service Module Loader: java.lang.LinkageError: Failed to link com/bloomberg/datalic/dlps/PerSecurityWS_Service_Impl


            PerSecurityWS_Service_Impl is Bloomberg's class, and we are getting this error. I suspected maybe EAP 6.1 wasn't compatible with jaxrpc spec 1.1 Bloomberg is using to generate this class?

            • 3. Re: Using old jaxrpc on Jboss EAP 6.1

              I would blame a dependency configuration issue. Can you provide more details? the full exception stacktrace, any interesting log, the deployment structure (how your ear is, which libs it includes if any, which jboss modules dependencies it declares if any, etc)


              JBoss EAP 6.1 passed the EE certification requirements / tests, including jaxrpc sections.

              • 4. Re: Re: Using old jaxrpc on Jboss EAP 6.1



                The ant target Bloomberg gave us uses the sun jaxrpc library (jaxrpc-api.jar, jaxrpc-impl.jar, jaxrpc-spi.jar. It's spec 1.1). Should we use JBoss's jaxrpc implementation library instead of these? Does JBoss support jaxrpc-api.jar, jaxrpc-impl.jar, jaxrpc-spi.jar?