Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000008SDZa&sfdc.override=1 project_key: SOA The Wise SOAPClient currently uses a properties file to specify configuration values like a working directory. These are not subject to property substitution like everything we have in our XML configuration files. Please move the properties into XML configuration (perhaps in the Action configuration in jboss-esb.xml) so our customers will have a consistent substitution mechanism.
Attached is a customer-provided fix, well documented and easy to read. Please consider this as we build an implementation.
Attachment: Added: customer_fix.zip
Tom Cunningham <tcunning> updated the status of jira JBESB-3765 to Resolved
Tom Cunningham <tcunning> made a comment on jira JBESB-3765 Incorporate fix. Read in a wise-config property from the configTree that contains wise-property elements. Subsitute based on values provided.
Tom Cunningham <tcunning> updated the status of jira JBESB-3765 to Closed
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: There was some inconsistency when using the WISE SOAPClient. The client used a properties file to specify configuration values in the same way as a working directory. Because of this, properties could not be substituted like in other XML configuration files. The user can now provide values in the file which will substitute the properties correctly.
JBossESB schema does not support wise-config and wise-property elements
Disregard - misconfiguration
The configuration is not implemented properly. This snippet <property name="wise-config"> <wise-property name="wise.tmpDir" value="/home/jpechane/workspace/soa/tests/quickstarts/webservice_consumer_wise_inline_properties/build/tmp"/> <wise-property name="wise.forceImportObject" value="true"/> <wise-property name="wise.keepGeneratedSources" value="true"/> <wise-property name="wise.wsImporter.verbose" value="true"/> </property> is translated into Breakpoint hit: "thread=pool-34-thread-1", org.jboss.soa.esb.actions.soap.wise.SOAPClient.<init>(), line=198 bci=51 pool-34-thread-1[1] print config config = "<action EndPointName="HelloWorldPort" SOAPAction="sayHello" action="soapui-client-action" class="org.jboss.soa.esb.samples.quickstart.webservice_consumer_wise_inline_properties.SOAPClientAction" get-payload-location="helloworld-request-parameters" serviceName="HelloWorldWS" set-payload-location="helloworld-response" wsdl="http://127.0.0.1:8080/Quickstart_webservice_consumer_wise_inline_properties/HelloWorldWS?wsdl"> <wise-property name="wise.tmpDir" value="/home/jpechane/workspace/soa/tests/quickstarts/webservice_consumer_wise_inline_properties/build/tmp"/> <wise-property name="wise.forceImportObject" value="true"/> <wise-property name="wise.keepGeneratedSources" value="true"/> <wise-property name="wise.wsImporter.verbose" value="true"/> </action>" It means that the line ConfigTree[] wiseConfig = config.getChildren("wise-config"); will alway receive no element
Verified in SOA-P 5.3.ER4
Employee 'felias' has left the company.