from 11G, weblogic use ecliplselink as it's default jpa solution, anyone can tell me is native toplink is still be supported in weblogic 12c?
Yes, TopLink is still supported, certified and is considered the default provider in WLS, but what version do you mean and what API are you using?
You might want to checkout the TopLink datasheet and documentation though, as EclipseLink provides the core persistence used underneath TopLink.
Related
I would like to migrate to Eclipse link and JPA 2.1 on IBM WAS server and DB2. Could you please advice the sets need to be followed? If anyone used before, please explain to us what are the things to have cared?
I am going through the document - https://developer.ibm.com/wasdev/docs/can-i-use-jpa-2-1-on-websphere-application-server/
If you want JPA 2.1 I'd strongly suggest to migrate to WebSphere Liberty (preferably) , as it fully supports that and you already have license for that if you have WAS 8.5, or migrate to tWAS 9.0. On WAS 8.5.x you will have to disable JPA scanning, use application-managed persistence, create shared liberary.... not really worth.
In addition to server settings changes you will have to migrate your app from OpenJPA to EclipseLink. There is free Eclipse plugin - WebSphere_Application_Server_Migration_Toolkit that you can configure to scan your application sources for OpenJPA -> EclipseLink migration.
But also for WAS 8.5.x -> WebSphere Liberty migration ;-)
it seems jboss AS 7.1 supports ejb 2.1.Our ejb 2.1 based application is deployed on jboss 5 AS. We are migrating it to jboss7.1. but i want to know what are the additional configurations required to run ejb 2.1 without any errors?
EJB2 is still supported in AS7.x, the issue might be that AS7 is a new implementation and some of the tuning options and configuations are not available for AS7 - especially the EntityBean CMP.
There are some added for EAP6 (based on AS7) you might download the unsupported version.
Wildfly (the successor of JBossAS) will not continue to support EJB2 EntityBeans because EJB3.2 declare it as optional.
Note EJB2 session beans are still supported but I recommend to upgrade it to EJB3 this should faily simple.
You might keep the EJB2 interfaces to provide an interface for EJB2 clients, but I expect effort for the client as well as the lookup Strings changed.
If the appliation should be kept for the future I would recommend to migrate to EJB3
I am trying to use EclipseLink 2.5 in my GlassFish 3.1.2.2 but it seems that its not working properly.
So What are the supported versions of JPA does EclipseLink 2.5 support ?
I am restricted to use JPA 2.0 till the moment.
EclipseLink 2.5 is implementation of JPA 2.1 specification. Because JPA 2.1 (what's new) is more or less superset of JPA 2.0, it is possible to use EclipseLink 2.5 and limit usage to features available in JPA 2.0.
GlassFish 3.1.2.2 was shipped with EclipseLink 2.3.2 (which is implementation of JPA 2 specification), so it is rather easy try is EclipseLink version source of problems. Likely not - but new bugs are of course always possible. Also then issue is not directly connected to supported JPA specification version.
In eclipse ,I am trying to upgrade my JPA from 1.0 to 2.0 (EJB project). I have made changes in the library and using eclipselink also but when I am again creating a project it is not giving an option of JPA 2 in faclets to select
any one have some idea whats the problem
It will depend on the version of Eclipse, and the weblogic plugin (OEPE) you are using. Without the correct connectors Eclipse is only aware that WebLogic server can run JPA1.0.
Perhaps try the latest version of OEPE pack here and point it at your workspace.
You also need to make sure the version of WebLogic you are using supports JPA2- you have tagged the question as weblogic 10.x which only supports JPA2.0 in 10.3.4 and later, and may require you to patch weblogic to enable the support.
I"m trying to create a Java EE project using a mongo database. I am unable to find any good working examples.How do you correctly set up JPA for the project?
Java EE 6 (or in JPA 2.0 as an part of it) does not have any defined support for MongoDB or for NoSQL databases in general.
That's why how it is done depends fully from JPA provider implementation. If you use EclipseLink, maybe you can try to follow example given in this blog post and present further questions about what exactly is not working.
Hey you should at least check out Arun Gupta's blog post on this at https://blogs.oracle.com/arungupta/entry/java_ee_6_and_nosql. Gupta is the Oracle Java EE Evangelist and this entry covers using EclipseLink for a JPA connection to MongoDB and deploying to Glassfish. If you search his blog, there is also an earlier entry on how to use the Java driver included with MongoDB in a Java EE project. I haven't tried the example with an EntityManager but am thinking about doing so.