> Now that I think again, the problem is not that the class is not found. The > error says "java.lang.IllegalArgumentException: Object: > com.xxx.entities.XyzEntity@3a18c1 is not a known entity type" which is > coming from EclipseLink in WebLogic. > > But I wonder why making a trivial change (as it seems) in POM file should > make this behave differently. I gotta be an issue in JPA. So out of this > list's scope.
I think there must be some additional difference(s) between the "working" and "not working" state that you have simply not found -- but not necessarily in the Jar files you are producing now, perhaps in some other piece/component. If you sort it out, come back and give us more details, if for no reason other than to benefit future Google searchers who run into similar problems with EclipseLink. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
