Hide Forgot
Affects: Documentation (Ref Guide, User Guide, etc.) Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000006GiMq&sfdc.override=1 Steps to Reproduce: 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> Workaround: Workaround Exists Workaround Description: Don't deploy the two service types in the same deployment. project_key: SOA 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 ---------------------------------------------------------------------------------------------------------------------------------------
Link: Added: This issue Cloned from SOA-2931
Link: Added: This issue is related to JBESB-3573
Link: Added: This issue duplicates JBESB-3573
Link: Added: This issue related JBESB-3573
This is not an issue for 5.1 as the microcontainer deployment has been rewritten
Not a bug in 5.1.0