I would check to make sure that the version used at run time matches (or
is more recent) than the version used at compile time.
It looks like somebody is calling somebody with an argument of a type
that the called method does not expect and can not map to anything that
it knows.
Perhaps the version provided at run-time is older than the one used at
compile time.
I could be wrong but that is something that can happen with provided
libraries.
Ron
On 12/07/2012 8:37 AM, Pimentel, Robert wrote:
Just out of curiosity, why are you using provided, or optional, and not runtime
scope?
-----Original Message-----
From: Amir Gheibi [mailto:[email protected]]
Sent: Wednesday, July 11, 2012 5:04 PM
To: Maven Users List
Subject: RE: Dependency entry changes runtime
Thanks mate. Still Identical MANIFEST(!) and when I compared the JARs with a
tool (BeyondCompare) I could only see one difference which is maven directory
under META-INF directory.
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.
-----Original Message-----
From: Wayne Fay [mailto:[email protected]]
Sent: July-11-12 12:33 PM
To: Maven Users List
Subject: Re: Dependency entry changes runtime
OK so back up.
First, leave the dependency out of A and run "mvn clean package". Set that jar
file aside (rename it and move it out of target or clean will remove it.)
Now add the dependency and run "mvn clean package". Set that jar file aside
like you did before.
Now use some tool to unzip both and compare the contents. Surely there is a
difference you simply have not accounted for yet.
Wayne
On Wed, Jul 11, 2012 at 1:34 PM, Amir Gheibi <[email protected]> wrote:
Here is A's Manifest entry which as I mentioned, is identical in both scenarios.
Manifest-Version: 1.0
Built-By: bm03043
Build-Jdk: 1.6.0_18
Created-By: Apache Maven 3.0.4
Archiver-Version: Plexus Archiver
Extension-List: entities
entities-Extension-Name: com.xxx.entities
-----Original Message-----
From: Wayne Fay [mailto:[email protected]]
Sent: July-11-12 11:13 AM
To: Maven Users List
Subject: Re: Dependency entry changes runtime
Runtime environment is a "Weblogic 10.3.3" in which "B" is registered as an
Optional Package (Library) and there is an extension entry in A's MANIFEST that refers to it
(that's how A finds B in runtime).
I compared A's JAR file in both scenarios and I don't see any difference
whatsoever except the POM file within the Maven directory, which as far as I
understand, doesn't have any effect on runtime.
Why would the dependency entry change runtime behavior?
Didn't you already answer your own question? The answer is the
MANIFEST entry. If you check, the MANIFEST entry will (should) only
appear when the dependency is added with runtime scope.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�� [��X��ܚX�KK[XZ[
� \�\��][��X��ܚX�PX]�[��\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[
� \�\��Z[ X]�[��\X�K�ܙ�B
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
