Uploaded image for project: 'JBoss Enterprise SOA Platform'
  1. JBoss Enterprise SOA Platform
  2. SOA-2931

EBWS incompatible with SOAPProxy

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 5.0.2
    • Fix Version/s: 5.2.0 GA
    • Component/s: JBossESB
    • Labels:
    • Environment:

      Any supporting ESB

    • Steps to Reproduce:
      Hide

      The problem is very easy to reproduce. Start with the webservice_proxy_basic quickstart, then add the text that follows. You'll find that you can toggle either service on or off and run one service at a time. If you try to un-comment both, you'll get the above error at deploy time.

      • To jboss-esb.xml:
        <!--
        <service category="test" description="test" invmScope="GLOBAL" name="test">
        <actions inXsd="/request.xsd"
        mep="RequestResponse" outXsd="/request.xsd" webservice="true">
        <action class="org.jboss.soa.esb.actions.SystemPrintln" name="log">
        <property name="message" value="test"/>
        </action>
        </actions>
        </service>
        -->

      To root of deployment (request.xsd):
      <xs:schema version="1.0" targetNamespace="http://www.jboss.org/sayHi" xmlns:x1="http://www.jboss.org/sayHi" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
      <xs:element name="sayHi" type="x1:sayHi"/>
      <xs:complexType name="sayHi">
      <xs:sequence>
      <xs:element name="arg0" type="xs:string" minOccurs="1"/>
      </xs:sequence>
      </xs:complexType>
      </xs:schema>

      Show
      The problem is very easy to reproduce. Start with the webservice_proxy_basic quickstart, then add the text that follows. You'll find that you can toggle either service on or off and run one service at a time. If you try to un-comment both, you'll get the above error at deploy time. To jboss-esb.xml: <!-- <service category="test" description="test" invmScope="GLOBAL" name="test"> <actions inXsd="/request.xsd" mep="RequestResponse" outXsd="/request.xsd" webservice="true"> <action class="org.jboss.soa.esb.actions.SystemPrintln" name="log"> <property name="message" value="test"/> </action> </actions> </service> --> To root of deployment (request.xsd): <xs:schema version="1.0" targetNamespace="http://www.jboss.org/sayHi" xmlns:x1="http://www.jboss.org/sayHi" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <xs:element name="sayHi" type="x1:sayHi"/> <xs:complexType name="sayHi"> <xs:sequence> <xs:element name="arg0" type="xs:string" minOccurs="1"/> </xs:sequence> </xs:complexType> </xs:schema>
    • Affects:
      Documentation (Ref Guide, User Guide, etc.)
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Don't deploy the two service types in the same deployment.

      Show
      Don't deploy the two service types in the same deployment.
    • Release Notes Text:
      Hide
      https://issues.jboss.org/browse/SOA-2931

      User could not have both EBWS and SOAPProxy deployment types on the same deployment. This was because the EsbWebServiceDeployer created a list of publishers which was used to initialise the publishers property in the EsbDeployment, via EsbDeployer and EsbMetaData. Unfortunately EsbMetaData returned an unmodifiable list which Configuration.create nevertheless attempted to modify leading to a java.lang.UnsupportedOperationException. The code has now been changed and, as a result, users can now have two different deployment types on the same deployment.
      Show
      https://issues.jboss.org/browse/SOA-2931 User could not have both EBWS and SOAPProxy deployment types on the same deployment. This was because the EsbWebServiceDeployer created a list of publishers which was used to initialise the publishers property in the EsbDeployment, via EsbDeployer and EsbMetaData. Unfortunately EsbMetaData returned an unmodifiable list which Configuration.create nevertheless attempted to modify leading to a java.lang.UnsupportedOperationException. The code has now been changed and, as a result, users can now have two different deployment types on the same deployment.
    • Release Notes Docs Status:
      Documented as Resolved Issue

      Description

      When configuring an .esb, it appears the user cannot have both an EBWS and SOAPProxy. You can use either-- commenting out the compliment-- and it will work. When both are uncommented, the user gets the following error at deployment time:

      --------------------------------------------------------------------------------------------------------------------------------------
      Deployment "jboss.esb.vfszip:/path_to_deployment/Quickstart_webservice_proxy_basic.esb/" is in error due to the following reason(s): java.lang.UnsupportedOperationException
      ---------------------------------------------------------------------------------------------------------------------------------------

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ldimaggio Len DiMaggio
                  Reporter:
                  rick_wagner Rick Wagner
                  Writer:
                  David Le Sage
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: