• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

EclipseLink 2.4.2 Unmarshalling null strings to empty strings("")

 
Jared Fucci
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have been racking my brain for almost a week now and can't figure this out. I am starting to hold up QA testing now and possibly having to push back the project, desprate for help.

We switching from Weblogic 10.3.5 to 12.1.2 and in doing so a part of JAXB broke. for some reason, null strings are being unmarshalled to "" instead of staying null. This is causing checks for null in various endpoints to become invalid.

.xsd


Generated Object:


SOAP Request:


When we get into the endpoint the values are no longer null, they are "". I tracked this down to between the SAXUnmarshaller and DOMReader classes in EclipseLink. I verified that when it's in XMLUNmarshaller it has a valid xml string with null values that it passes into SAXUnmarshaller. SaxUnmarshaller and DOMReader then parses it and sends back to XMLUnmarshaller and the values went from null to "".

I have tried various global data bindings, I have tried reverting back to the olf RI JAXB implementation on the server, I have tried to use my own JAXB implementation in the project and still i get the same error. I read that there was an issue with EclipseLink and this early in WebLogic 12.1.1 but that it was corrected with EclipseLink 2.3.3, we are currently running EclipseLink 2.4.2 and still have this issue.

The EclipseLink documentation for 2.4.0 says that for Null Handling that null should pass right through but it doesn't happen, it USED to when we were on 10.3.5.

Can anyone help me understand what is going on here? or what I could do to fix this? or some setting that must be set somewhere? I am all out of ideas. Any help would be greatly appreciated.
 
Jared Fucci
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
UPDATE:

Just in case anyone comes across this with the same issue. The issue, for some reason, was log4j. We were using log4j version 1.2.17. I swapped it out to 2.3 and everything works now. I don't know why or how this effected it but it's good now.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic