Publishing a Webservice with Lucee. No longer accepting an array of components.

Description

We were publishing a webservice that accepted an argument which was an array of components. This was done by setting the type to the component name with square brackets at the end (vehicle_request[])like so:

 

The actual objects in the array were similar to this:

So, when sending a soap request like this:

exampleSoap.xml

We would expect a result such as:

success.xml

This works completely fine in Lucee versions 5.2.9.40 and earlier.

However after upgrading lucee to 5.3.1.102 we receive this error message:

error.xml

 

Has the way lucee handles webservices like this changed and thus our way depreciated? Should we be doing this a different way now or is this indeed a bug?

Environment

Windows

Attachments

5

Activity

Michael Offner 
6 April 2020 at 09:25

java.lang.ClassCastException@3f0fa81f

at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)

at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)

at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)

at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:609)

at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1782)

at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2967)

at com.sun.org.ap

Michael Offner 
27 March 2020 at 17:32

Michael Offner 
6 September 2019 at 19:50

after moving the functionality to an extension, it no longer works…

Fixed

Details

Assignee

Reporter

Priority

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Created 26 May 2019 at 23:57
Updated 9 April 2020 at 16:25
Resolved 9 April 2020 at 16:25