[jbosstools-issues] [JBoss JIRA] (JBDS-2446) ESB Editor removes "http-client-property" property

[Brian Fitzpatrick (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746028#comment-12746028 ] 

Brian Fitzpatrick commented on JBDS-2446:
-----------------------------------------

It's definitely SOA-P tooling that you're bumping up against. We're in the process of getting a better handle on some of the SOA-P tools again now that we have a few more folks to work on it. But Slava is still our best hope in the short term. :) He's been helping us out when we've needed tweaks to the ESB editor. 
                
> ESB Editor removes "http-client-property" property
> --------------------------------------------------
>
>                 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: SOA Tooling / 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: Douglas Palmer
>
> 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/schemas/xml/jbossesb-1.3.1.xsd"
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.1.xsd http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.1.xsd">
>  <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/schemas/xml/jbossesb-1.3.1.xsd"
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.1.xsd http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.3.1.xsd">
>  <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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira