Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 843636

Summary: SOAPClient <xs:any> handling needs improvement
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: tcunning
Component: JBossESBAssignee: Nobody <nobody>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.3.0 GACC: soa-p-jira
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:20:23 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
xs:any reproducer
none
Server xs:any parse exception log none

Description tcunning 2012-07-26 20:18:28 UTC 
Description of problem:

In SOA-P 5.3, SOAPClient introduced <xs:any/> handling, but requires a well-formed XML string by the user.      This could be improved by handling the object and clearing up confusion in the OGNL parameter naming (in SOAPClientService.injectParameters, the OGNL expression for the embedded comment is the same as the enclosing element when you get to handling the comment).
Comment 1 Robert Balent 2012-07-27 12:09:34 UTC 
Created attachment 600756 [details]
xs:any reproducer

Attaching reproducer. Copy reproducer to quickstarts directory and run:

ant deploy
ant runtest
Comment 2 Robert Balent 2012-07-27 12:10:08 UTC 
Created attachment 600757 [details]
Server xs:any parse exception log
Comment 4 Red Hat Bugzilla 2025-02-10 03:20:23 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.