ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS ------------------------------------------------------------------------------------------------------------------------ Key: JBDS-2446 URL: https://issues.jboss.org/browse/JBDS-2446 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public(Everyone can see) Components: Integration Platform Affects Versions: 5.0.0.GA-SOA Environment: RHEL 6.1 java version "1.6.0_25" SOA-P 5.0 Reporter: William Siqueira Assignee: Neil Wallace Priority: Critical Fix For: 5.0.4.GA-SOA When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way. When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually <?xml version="1.0"?> <jbossesb parameterReloadSecs="5" xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc... xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trun... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem... <services> <service category="c1" description="d1" name="s1"> <actions> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client"> <property name="wsdl" value="someWsdl"/> <property name="SOAPAction" value="noAction"/> <property name="endpointUrl" value="http://host/servername"> <http-client-property name="file" value="httpclient.properties" /> </property> </action> </actions> </service> </services> </jbossesb> Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited) <?xml version="1.0"?> <jbossesb parameterReloadSecs="5" xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc... xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trun... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem... <services> <service category="c1" description="d1" name="s1-edited"> <actions> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client"> <property name="wsdl" value="someWsdl"/> <property name="SOAPAction" value="noAction"/> <property name="endpointUrl" value="http://host/servername"/> </action> </actions> </service> </services> </jbossesb> One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine.