2 Replies Latest reply on Nov 25, 2005 10:05 AM by borje.jonsson

    Changed webservice context behavior in 4.0.3?

    borje.jonsson

      Hello,

      When i tried to migrate an application to Jboss 4.03 from 4.0.2 I saw that my webservices was deployed at another context path from before.

      I expose sessionbeans as webservices. The are created with wscompile and packaged in an ear-file.

      Any idea how i can specify the context path of my webservices?

      4.0.3:


      14:58:14,395 INFO [TomcatDeployer] deploy, ctxPath=/security-ejb, warUrl=.../tmp/deploy/legolas.ear-security-ejb.jar-ws2166.war/


      4.0.2:

      14:53:23,426 INFO [TomcatDeployer] deploy, ctxPath=/legolas/security-ejb, warUrl=.../tmp/deploy/legolas.ear-security-ejb.jar-ws2134.war/



      /Börje Jonsson


        • 1. Re: Changed webservice context behavior in 4.0.3?
          anders.hedstrom

          In your EJB's jboss.xml file.

          ex.

          <?xml version="1.0" encoding="UTF-8"?>
          
          <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd">
          
          <jboss>
           <enterprise-beans>
           <session>
           <ejb-name>MySLSB</ejb-name>
           <port-component>
           <port-component-name>SLSBWS</port-component-name>
           <port-component-uri>/ws/*</port-component-uri>
           </port-component>
           </session>
           </enterprise-beans>
          </jboss>



          Cheers
          //Anders

          • 2. Re: Changed webservice context behavior in 4.0.3?
            borje.jonsson

            Thank yoy for the tip, but this only works for the first session bean. If i have several session beans with the first part of the uri the same in all beans, only the last bean is visible.
            Example:

             ....
             <ejb-name>SecurityBean</ejb-name>
             <port-component>
             <port-component-name>SecurityService</port-component-name>
             <port-component-uri>/ws/secutity/*</port-component-uri>
             </port-component>
             ...
            


            and

             ....
             <ejb-name>TrackingBean</ejb-name>
             <port-component>
             <port-component-name>TrackingService</port-component-name>
             <port-component-uri>/ws/tracking/*</port-component-uri>
             </port-component>
             ...
            


            only the last deployed webservice is possible to use. The first service is deployed, but gives an error on invocation.

            /Börje