[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-users] need help urgently with WebLogic 10.3.5
|
I believe WebLogic 12.1.1 is shipped with a version of TopLink that includes
EclipseLink 2.3.2. I am not aware of any changes to the mechanism for updating
jars that are part of WebLogic's core.
BTW: The recommended approach to update the EclipseLIn version for recent
versions of WebLogic is the shared library approach described in this blog:
http://buttso.blogspot.com/2011/07/plugging-in-later-version-of.html
There are an increasing number of Oracle apps that run on WebLogic that use
TopLink/EclipseLink. They are tested with the version shipped with WebLogic.
Obviously changing the boot classpath for WebLogic changes the version that is
used by the whole system. While TopLink/EclipseLink is backward compatible,
changes to the version will affect whether you are running with the tested
config. As the delta between the shipped version and the version you are using
grows, so the the potential for problems. The shared library approach will
avoid replacing the version used by the core of WebLogic.
-Tom
On 21/12/2011 8:11 AM, Nathan Drew wrote:
Thanks for the extra info.
Now that WebLogic "12c" aka. 12.1.1 (when will they ever sort out the
versioning?) that has recently been released on 1st December - what
version is shipped with that? Do you know if there's a better way to do
things in this release or if you're left with the below options?
Kind Regards
Nathan
-----Original Message-----
From: eclipselink-users-bounces@xxxxxxxxxxx
[mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of Michael
O'Brien
Sent: 20 December 2011 17:05
To: EclipseLink User Discussions
Cc: michael.f.obrien@xxxxxxxxxxxxxxx
Subject: Re: [eclipselink-users] need help urgently with WebLogic 10.3.5
Nathan, Sankarsan,
Just to help you guys out some more. There are several methods
you can choose from when you wish to downgrade the EclipseLink JPA 2.0
provider in WebLogic 10.3.5.0 involving container or application managed
persistence contexts. The following wiki page was written for WebLogic
10.3.3.0 for users that wished to upgrade to JPA 2.0 before Java EE 6
support arrived in WebLogic 10.3.4.0 on 15 Jan 2011. You can use the
page as a reference if you wish to use an older version than the 2.1
version of EclipseLink shipped in the modules directory on the server.
Out of the box in 2011, WebLogic 10.3.5.0 is enabled for JPA 1.0
and JSF 1.2 for backwards compatibility against Java EE 5 apps (which
will help you out). When you deploy a JPA 2.0 or JSF 2.0 enabled EAR or
create a server reference in Eclipse - the JPA 2.0
com.oracle.jpa2support_1.0.0.0_2-0.jar is prepended to the classpath -
this is when the server becomes fully Java EE 6 enabled (the 2.0
persistence.xml XSD, 2.0 weaving/instrumentation and 2.0 dependency
injection).
http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic
In your 10.3.5.0 case (you sort of have the same issue as a user that
wishes to upgrade to EclipseLink 2.3), you may want to take the JPA 1.0
/ EclipseLink 2.1 default configuration and just replace the
[org.eclipse.persistence_1.1.0.0_2-1.jar] in the modules directory with
a renamed [eclipselink.jar] from a previous or later release - this is
highly "not recommended" but it works and is used by development.
http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#2011011
5:_JPA_2.0_using_EclipseLink_on_WebLogic_10.3.4.0
Copy/rename
http://www.eclipse.org/downloads/download.php?file=/rt/eclipselink/relea
ses/2.3.2/eclipselink-2.3.2.v20111125-r10461.zip
This...
D:\opt\eclipselink\eclipselink-2.3.2.v20111125-r10461\eclipselink\jlib\e
clipselink.jar
Into...
D:\opt\wls10350_oepe111172\modules\org.eclipse.persistence_1.1.0.0_2-1.j
ar
I second Tom, you should try to use the latest version of eclipselink
2.3.2 or the 2.1 that ships with WebLogic.
thank you
Michael O'Brien
-----Original Message-----
From: eclipselink-users-bounces@xxxxxxxxxxx
[mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of Nathan Drew
Sent: December 20, 2011 04:11
To: EclipseLink User Discussions
Subject: Re: [eclipselink-users] need help urgently
We experienced the same issue for the opposite case - when trying to use
a newer version than what was installed with WebLogic - (10.3.4 in our
case) doesn't provide a nice way to do this other than a hack - you have
to add a PRE_CLASSPATH=/path/to/your/eclipselink.jar inside the
startWebLogic.sh script. Add that at the top and it should help but even
then, Tom is right - you should consider using a newer version as trying
to get support for out dated versions of anything is tricky.
The above should mean that any classes inside the eclipselink jar that
you set will take precedence over any same name classes in the built in
JAR. If the problem is the same as we were seeing, you get classloader
issues with the wrong version of the eclipselink classes that your code
is weaved/compiled against?
Kind Regards
Nathan
-----Original Message-----
From: eclipselink-users-bounces@xxxxxxxxxxx
[mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of Tom Ware
Sent: 16 December 2011 14:51
To: eclipselink-users@xxxxxxxxxxx
Subject: Re: [eclipselink-users] need help urgently
Why are you using EclipseLink 1.1.0? That version is very old. For the
most part, applications written for 1.1.0 should work with later
versions of EclipseLink with little or no change.
What problem are you seeing?
The following blog provides some advice about how to plug in a later
version of EclipseLink into WebLogic. In theory, the same process
should work for plugging in earlier versions as well. (but the optimal
solution is still to upgrade your EclipseLink version.)
-Tom
On 16/12/2011 9:41 AM, sankarsan padhy wrote:
Hi,
I am deploying my ear file to the weblogic 1.3.5.0 . My application
uses eclipselink 1.1.0 version and this is mentioned in my
persistent.xml file. But during deployment, weblogic is using 2.0
version of eclipselink and due to which my application is failing to
deploy.
Your kind and urgent help will be much appreciated.
Thanks
Sankarsan
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
