Bug 843636 - SOAPClient <xs:any> handling needs improvement
Summary: SOAPClient <xs:any> handling needs improvement
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.3.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-26 20:18 UTC by tcunning
Modified: 2025-02-10 03:20 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:20:23 UTC
Type: Enhancement
Embargoed:

Attachments (Terms of Use)
xs:any reproducer (804.35 KB, application/zip)
2012-07-27 12:09 UTC, Robert Balent 		no flags Details
Server xs:any parse exception log (2.95 KB, text/x-log)
2012-07-27 12:10 UTC, Robert Balent 		no flags Details
View All

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.
Note You need to log in before you can comment on or make changes to this bug.