]
Tom Fennelly closed JBESB-1329.
-------------------------------
Resolution: Done
Fixed
Collections (unbounded xs:elements) can't be first element in
xs:sequence
-------------------------------------------------------------------------
Key: JBESB-1329
URL:
http://jira.jboss.com/jira/browse/JBESB-1329
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.2.1
Environment: JBoss 4.2.GA
Reporter: Per-Anders Backstrom
Assigned To: Tom Fennelly
Fix For: 4.2.1 CP2
Collections can't be the first element in a xs:sequence or else the OGNL-mapping will
fail.
I have narrowed the bug down to the org.jboss.internal.soa.esb.soap.OGNLUtils class and
the getOGNLExpression() method.
The bug is easily reproduced, in the soapui-client test-cases, in file
orderprocessing/OrderProcessingSchema.xsd, just see to that the
element name "lineItems" gets positioned first in complexType named
"order".
Btw, collections are asserted in OGNLUtils.java by checking for the first occurrence of a
comment-string containing "1 or more repetitions" at the parent node of the
actual element, but as far as I can see my collections are always commented with
"Zero or more repetitions". If the first comment is rather "Optional",
e.g the collection isn't first element in the parent node, this assertion would
probably fail anyway?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: