Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

CLONE - Webservice fails with ; nested exception is: org.xml.sax.SAXException: Invalid element in mkmr78s01urv.RateReply - HighestSeverity

Description

We are having the same issue as the ticket LDEV-1642, except ours is with the Fedex Rate WSDL. It seems however that we are having another issue of the wsdl not generating the stubs correctly. When specifying one of the nested elements we get the error "No matching Method for setWebauthenticationdetail(java.util.HashMap) found for l1uslcvi2iiq.RateRequest"

Here is the code we are using:

ShipRequest = StructNew(); ShipRequest.ClientDetail = StructNew(); ShipRequest.WebAuthenticationDetail = StructNew(); //ShipRequest.WebAuthenticationDetail.UserCredential.Key = "testing"; //ShipRequest.WebAuthenticationDetail.UserCredential.Password = "password"; TransactionDetail = StructNew(); TransactionDetail.CustomerTransactionId ="java sample"; ShipRequest.TransactionDetail = TransactionDetail; ShipRequest.Version = StructNew(); ShipRequest.Version.ServiceId = 'crs'; ShipRequest.Version.Major = '22'; ShipRequest.Version.Intermediate = '0'; ShipRequest.Version.Minor = '0'; var blah = createObject('webservice', 'https://gist.githubusercontent.com/Yamaha32088/2d9f3dba6e59be5971408b955a941d9c/raw/7baf5dbfb6a8d7e131c628e4729f2c4f795843ac/fedex.wsdl') dump(blah.getRates(ShipRequest));

If you run the code above as-is then you get the nested exception error. If you uncomment the two commented out lines you get the error saying the setWebAuthenticaionDetail does not exist.

Looks like this may also be related to this issue https://luceeserver.atlassian.net/browse/LDEV-1501 I made a comment referencing this issue

Environment

None

Attachments

2
  • 02 May 2018, 04:48 pm
  • 02 May 2018, 04:45 pm

Activity

Show:

Michael Offner 21 May 2024 at 19:59

this part of the project is deprecated and only get security fixes, sorry.

Michael Offner 11 June 2018 at 15:04

if you habe an other issue please raise an other ticket, we should have not addressed multiple independent issues in one ticket.

Brandon Brown 13 May 2018 at 23:47

or I have a fix for the "No matching Method for setWebauthenticationdetail(java.util.HashMap) found for l1uslcvi2iiq.RateRequest" should I split this into another issue and push up the fix? I am still having trouble with "; nested exception is: org.xml.sax.SAXException: Invalid element in mkmr78s01urv.RateReply - HighestSeverity" I am guessing it is because Lucee isn't handling enumeration types correctly. Here is the relevant lines from the WSDL:

<xs:simpleType name="NotificationSeverityType"> <xs:restriction base="xs:string"> <xs:enumeration value="ERROR"/> <xs:enumeration value="FAILURE"/> <xs:enumeration value="NOTE"/> <xs:enumeration value="SUCCESS"/> <xs:enumeration value="WARNING"/> </xs:restriction> </xs:simpleType>

If I try to set one of the enumerated values inside of the web service request struct it will throw an error saying the method doesn't exist.

Brandon Brown 7 May 2018 at 12:33

that is odd, maybe it is setup on my end or something, I changed versions of Lucee and still got it, removed all Apache rewrites thinking it might be a redirect but I still received two emails. Not really sure what else to check at this point. Either way the initial issue still exists, I guess the double requests can be ignored for now if you can't reproduce it and maybe I can figure out if it is something on my end causing it to happen.

Pothys - MitrahSoft 7 May 2018 at 06:31

Hi ,

I changed the webservice to pointing out local which contains above code but I received mail at once. Anyway confirm about the issue.

Fixed

Details

Assignee

Reporter

Priority

Labels

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

Affects versions

Created 2 May 2018 at 16:44
Updated 21 May 2024 at 19:59
Resolved 21 May 2024 at 19:59

Flag notifications