3 Replies Latest reply: May 21, 2012 11:32 AM by Steffen Krause RSS

address rewrite

S Bapat Newbie

The JBossWS user guide discusses Address rewrite in the Configuration section, to configure dynamically the value of the <soap:address> element in the wsdl. Is there a similar functionality for jbossws-cxf configuration?

 

Currently in the jbossws-cxf.xml, the value of the jaxws:endpoint address attribute is taken as is and put in the wsdl. Is there any way to dynamically generate the address including the port and http/s at runtime?

 

Also, setting the address to http://@jboss.bind.address@:8080/test does not work, it is always taken literally.

 

Thanks

  • 1. address rewrite
    Alessio Soldano Master

    Regarding setting the auto rewrite from spring based configuration, I just created a jira (https://issues.jboss.org/browse/JBWS-3200) to incorporate / test the additions coming from Apache CXF 2.3.2 on that topic (https://issues.apache.org/jira/browse/CXF-2770)

  • 2. Re: address rewrite
    dlaprade Newbie

    I am having the same issue with the <soap:address ..> not getting updated based upon the deployment.  I added the META-INF/stack-agnostic-jboss-beans.xml:

     

    <bean name="WSServerConfig" class="org.jboss.webservices.integration.config.ServerConfigImpl">

        <property name="mbeanServer"><inject bean="WSMBeanServerLocator" property="mbeanServer"/></property>

     

     

        <property name="webServiceHost">jbossws.undefined.host</property>

     

        <property name="modifySOAPAddress">true</property>

     

     

        <!--

          <property name="webServiceSecurePort">8443</property>

        -->

      </bean>

  • 3. Re: address rewrite
    Steffen Krause Newbie

    Ok, did this ever get resolved? I'm using JBossAS 6.1 right now and I'm facing the exact same issue.

     

    Reading the above mentioned issues (one created in JBossWS and the other in Apache CXF) it seems to me that the problem originated from Apache CXF and was resolved with the release of CXF 2.3.2. Now I tried to upgrade my JBossAS 6.1 to the next JBossWS version hoping that it incorporated the CXF coming to find out that JBossWS 3.4.1 was the last release that allowed for installation into pre-AS7 JBossAS instances. 4.0 up to 4.0.2 seem to be focused on AS7 only.

     

    Can somebody tell me how I can fix the problem described in this discussion without having to install AS7?

     

    Thanks,

     

    Kimba