Jared Fucci

Greenhorn
+ Follow
since Mar 06, 2012
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
In last 30 days
0
Forums and Threads

Recent posts by Jared Fucci

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.
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.
I think I see what the problem might be related to. The way this project is building with maven, it's making multiple files with the same name in the META_INF folder(i.e. spring.schemas, spring.handlers, etc) It looks like these contain the schema locations and the handler locations. It looks like when spring starts, it checks for spring.handlers and spring.schemas and maps them, but it looks like it's just grabbing the first one it sees and continues on.

Is it supposed to make multiple .schema and .handler files and spring should look through all of them? or should something be combining these into 1 file?
12 years ago
Anyone have any suggestions? Or any other information needed that will shed some light on this?
12 years ago
Thanks for the response and sorry, I should have looked at that code better before posting. Those were some attempts to try to fix it, thinking older versions of things activemq might work better with or something. And I removed spring.tx because some other dependency brings it in as well and I thought there might be an issue with that. I made the changes you suggested in the POM file shown below, and I couldn't do the XSDs without a version because it failed to find them. I actually have the xsd files in the project because of a security issue here at work. So I know I have the right versions, so I just changed those back, but I left your other changes, and I get the exact same error



12 years ago
I've had an issue for days and I can't find any information on this issue. I have searched this site the best I could and couldn't find anything that fixed my problem.

I have a project with multiple modules in it a core, data-services, and messaging. It's a stand alone java jar that is a topic subscriber for JMS. The main class is in Core, and the data-services handles database transactions, and messaging handles listening on a spring jms container for messages, validates, and passes the data on to data-services.

Data-services as a stand alone project works fine, builds fine, all tests works, etc. Messaging(with core) works fine without data services(with the passing off to data-services commented out of course) it connects to the active mq topic, waits, catches messages like it should and I just display them to the console to make sure I got what I wanted, etc. But when I put these three modules under the main project and build the main project through maven, which builds the projects in the following order:

[INFO] Reactor build order:
[INFO] NextGenSwakSubscriber
[INFO] Hibernate Data-Services
[INFO] JMS Messaging Services
[INFO] Core Jar Module

The build is fine, but when I start the app and spring starts up I get this error:



Now if I remove this dependency, it doesn't have this issue, well until it needs an activemq class in a later bean, then of course I get a classnotfound, but it looks like there is some issue with activeMQ and spring.

<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.4.1</version>
</dependency>

The xml it's blowing up on is:


Here is the main pom on the parent project if that will help, atleast give an idea of the versions I am using and what frameworks:


Can anyone point me in the right direction on this? I am at a complete loss and I have deadlines rapidly approaching.
12 years ago