Toplink Essentials Development

I'm curious as to who owns the development for this? I understand that Oracle donated the implementation to the Glassfish project, so is it maintained by the Glassfish team or by Oracle? Or by both (i.e. has it been forked?) Can someone please explain what the relationship is between the two groups, specifically with regards to the release lifecycle (i.e. what's the process). Thanks!

TopLink Essentials is an opensource project lead by Oracle. There are committers on the project from SUN and Oracle and other companies as well.
Glassfish publishes schedules and milestones that TopLink Essentials follows. The builds that get shipped with Oracle products (ie 10.1.3.1 uses TopLink Essentials for JPA) are taken directly from Glassfish and run through full product testing before being released.
I hope I was able to answer your questions.
Peter

Similar Messages

How to verify OC4J uses Oracle Toplink 10.x and not Toplink Essentials

Hi,
We dont want to use the default JPA provider "Toplink *Essentials*" that comes with OC4J. Rather we want to use Oracle Toplink 10.x
I downloaded [Oracle Toplink 10.x|http://www.oracle.com/technology/software/products/ias/htdocs/1013topsoft.html] and followed the installation instructions:- http://www.oracle.com/technology/products/ias/toplink/doc/10131/install/install.html#CHDBBIFB
When i deploy my EJB 3.0 appliation and invoke a JPA Entity, i can see the server log:- NOTIFICATION TopLink, version: Oracle TopLink Essentials - 2.0.1 (Build b09d-fcs (12/06/2007))
Do i have to do any other configuration/setting to ensure that i use Oracle Toplink and not Toplink Essentials in OC4J?
Thanks in Advance,
Prashant Tejura
Edited by: user1186295 on May 26, 2009 10:33 AM

rashant,
Hi, there are currently the following providers to choose from - you may want to consult your rep for any details on moving from 10.1.3.4 to 10.1.3.5.
1) TopLink or EclipseLink using EclipseLink JPA - the RI for JPA for WebLogic, OC4J and GlassFish
- EclipseLink JPA is focus of all current JPA development as part of EclipseLink and TopLink
2) Another open-source JPA implementation like OpenJPA or Hibernate
Deprecated:
3) TopLink using TopLink JPA - replaced by (1) TopLink using EclipseLink JPA
4) TopLink using TopLink Essentials JPA - replaced by (1) TopLink using EclipseLink JPA
Changes to server.xml as follows:
http://wiki.eclipse.org/EclipseLink/Examples/JPA/OC4J_Web_Tutorial#Modify_server.xml
<shared-library name="oracle.persistence" version="1.0" library-compatible="true">
          <code-source path="../../../eclipselink/eclipselink.jar"/>
          <code-source path="../../../eclipselink/javax.persistence_*.jar"/>
          <import-shared-library name="oracle.jdbc"/>
     </shared-library>
Changes to persistence.xml as follows: (container-managed JTA datasource)
http://wiki.eclipse.org/EclipseLink/Examples/JPA/OC4J_Web_Tutorial#Persistence.xml
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="example" transaction-type="JTA">
<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
<jta-data-source>jdbc/OracleDS</jta-data-source>
<class>org.eclipse.persistence.example.jpa.server.business.Cell</class>
<properties>
<property name="eclipselink.target-server" value="OC4J"/>
<property name="eclipselink.logging.level" value="FINEST"/>
</properties>
</persistence-unit>
</persistence>
You should see output similar to the following in your server log:
http://wiki.eclipse.org/EclipseLink/Examples/JPA/OC4J_Web_Tutorial#Console_Output
[EL Finest]: 2009-02-26 14:04:34.464--ServerSession(8634980)--Thread(Thread[HTTPThreadGroup-4,5,HTTPThreadGroup])--Begin deploying Persistence Unit example; state Predeployed; factoryCount 1
[EL Info]: 2009-02-26 14:04:34.542--ServerSession(8634980)--Thread(Thread[HTTPThreadGroup-4,5,HTTPThreadGroup])--EclipseLink, version: Eclipse Persistence Services - ***
[EL Fine]: 2009-02-26 14:04:35.213--Thread(Thread[HTTPThreadGroup-4,5,HTTPThreadGroup])--Detected Vendor platform: org.eclipse.persistence.platform.database.oracle.Oracle10Platform
[EL Config]: 2009-02-26 14:04:35.26--ServerSession(8634980)--Connection(5230779)--Thread(Thread[HTTPThreadGroup-4,5,HTTPThreadGroup])--Connected: jdbc:oracle:thin:@//1y.yyy.yy.yy:1521/ORCL
     User: SCOTT
     Database: Oracle Version: Oracle Database 11g Release 11.1.0.0.0 - Production
     Driver: Oracle JDBC driver Version: 10.1.0.5.0
[EL Finest]: 2009-02-26 14:04:35.385--UnitOfWork(5746770)--Thread(Thread[HTTPThreadGroup-4,5,HTTPThreadGroup])--PERSIST operation called on: org.eclipse.persistence.example.jpa.server.business.Cell@9107088( id: null state: null left: null right: null parent: null references: null).
[EL Fine]: 2009-02-26 14:04:35.807--ClientSession(5748500)--Connection(6653899)--Thread(Thread[HTTPThreadGroup-4,5,HTTPThreadGroup])--INSERT INTO EL_CELL (ID, STATE, TSEQ, RIGHT_ID) VALUES (?, ?, ?, ?)
     bind => [551, null, null, null]
thank you
/michael
www.eclipselink.org

Toplink Essentials in Jdeveloper 10.1.3.1: production or experientment?

Dear All,
i have a question about the toplink essentials bundled with the jdeveloper 10.1.3.1 production release.
Is this version of production quality or just for experientment?
is it stable enough to developer application on top of it ??
thanks.

Dear Shay,
Thank you.
Then i can persuade my colleague to use it to develop our small, new application.
BTW, will oracle provide official support if there is any problem related to toplink essentials
in 10.1.3.1? my company sign contract and pay for technical support.(through metalink)
thank you.

What are the difference between TopLink and TopLink Essentials...?

What are the difference between TopLink, TopLink Essentials, EclipseLink and TopLink Essentials-GlassFish?
What is the difference of their functions?
Edited by: qkc on Nov 21, 2009 10:52 AM

Difference between TopLink and ToPLink Essentials:
TopLink Essentials are the reference implementation (RI) of JPA, is an open source effort that is licensed under the Common Development and Distribution License (CDDL) v1.0. It can be freely downloaded and used under the terms of this license agreement. This means, you can only use it for the management of persistence and orm with Java EE and Java SE. The binary distribution of TopLink consist of 2 jars:
* toplink-essentials-agent.jar: contains Java Persistence API; XML Schemas and TopLink essentials implementation
* toplink-essentials.jar: contains java agent class requires in a standolane Java SE application
In addition to TopLink Essentials that makes the JPA implementation alive, Oracle offers its Oracle TopLink product (10.1.3) that contains an earlier preview binary of JPA and also offers developers additional object-relational capabilities, object-XML mapping (JAXB), non-relational mapping using Java 2.0 Connector Architecture (JCA).
Let's wait other person to answer these questions.

Crucial question about Toplink Essentials JPA in OC4J 10.1.3.3

Hi all!
I'm developing an EJB 3.0 service which will be deployed to an OracleAS 10.1.3.3 and even after I've read lots of docs and articles, I still got an unanswered question:
I know JPA leaves concurrent data access to the application's responsibility (or the vendor implementation's), that Oracle explicitly recommends using @Version to enable JPA's standard optimistic locking and also that Toplink Essentials JPA is OC4J's default persistence provider for EJB 3.0 modules. Considering this last important fact, what will be the default locking mode assumed by Toplink Essentials if I don't use @Version?
Looking at Toplink Essentials JPA extensions doc preview for OC4J 11g (http://www.oracle.com/technology/products/ias/toplink/jpa/resources/toplink-jpa-extensions.html), I found that I can use @OptimisticLocking to define the locking policy when defining an entity and use a lock type that doesn't require me to define a @Version field. But that annotation doesn't exist in version 10.1.3.3. Is there another way to define locking policy and type (on global or per entity basis) in version 10.1.3.3?
Any help will be really welcome!
TIA,
Eduardo.

Quoting Mr. Doug Clarke:
"Eduardo,
The only way to ensure that concurrent writers to the database don't overwrite one another is to either lock optimistically or pessimistically (i.e.: SELECT ... FOR UPDATE). Both of these approaches are supported by Oracle TopLink as well as TopLink Essentials. If neither is used then no locking is applied and the last writer will succeed leaving the database in a potentially corrupted state. Also note that minimal writes are used so each thread only updates the columns it changes so the resulting state of the database could be a combination of the two concurrent writes. Users of JPA are strongly recommended to use optimistic locking to ensure concurrent writing scenarios do not produce unexpected result in their database.
Our JPA implementation in 10.1.3.3 is TopLink Essentials which is the Open Source references implementation of JPA derived from Oracle TopLink developed in GlassFish. This edition of TopLink only has support for JPA's @Version annotation as you noted. This approach does require a dedicated column in the database table for comparison on write to detect changes made since this thread's version of the original data was read.
In Oracle TopLink 11g we have implemented JPA 1.0 in our product. This means that full capabilities of TopLink are available through JPA along with some custom annotations to assist in configuring them. This includes the additional optimistic locking policies provided for schemas where adding version columns is not possible. These capabilities are not included in TopLink Essentials. Customers can access these capabilities in the 11gR1 technology previews as well as in the new Eclipse Persistence Services Project "EclipseLink" which is the full functionality of Oracle TopLink developed as an open source solution. Oracle TopLink 11g and its distribution of EclipseLink are not yet available in a supported release."

Toplink support for JPA vs. Toplink Essentials

I think I read that Toplink has some support for EJB3/JPA as does Toplink Essentials.
What is the difference in features?
If one has a 10.1.3 app server license, should Toplink be used instead of Toplink Essentials for EJB3/JPA applications?
Does the Mapping Workbench produce JPA object-relational mapping annotations or XML?
Thank you.
Richard Catlin

Hi Robert,
I'm not sure which comments you were directing specifically to Dali vs. JDeveloper but I'll try and address them from a Dali perspective. I do want to point out that Dali is at 0.5 and so it is still under development.
yes you get a basic 1:1 entity from your databasetables...When generating Entities from tables, Dali will generate 1:1 and 1:many relationships based on database FK constraints.
@temporary annotations are not inserted if you have a Date oder Calendar type.Also when generating Entities from tables Dali will generate an instance variable of java.sql.Date for a database date column. java.sql.Date does not require an @Temporal annotation.
What's missing right now is a problem marker for missing @Temporal on java.util.Date and java.util.Calendar.
If you want to rename attributes or methods it's a lot of manual work to do... because >@Column annoations are not inserted, if they do not exist because of >dbname=attributenameThere is a bugzilla bug opened for this refactoring support. https://bugs.eclipse.org/bugs/show_bug.cgi?id=136333 Fortunately in Dali if you rename a class or attribute (field/getter) and your explicit or default mappings are broken you will get a problem marking on the attribute and in the Problems view so you can fix it rather than finding out at runtime.
generics are not inserted in the returnvalues of the methods...Generated Entities do use generics correctly e.g.:
public class Publisher implements Serializable {
     @OneToMany(mappedBy="publisher")
     private Set<Title> titles;
     public Set<Title> getTitles() {
          return this.titles;
     public void setTitles(Set<Title> titles) {
          this.titles = titles;
...--Shaun

Toplink Essentials final in Embedded OC4J - When?

Hi,
As far as i know (please correct me if I am wrong), the current release of JDeveloper (10.1.3.x) works with old Toplink Essentials version that covers an early draft of the JPA specs.
My question is: when will the final version of Toplink Essentials be available in the Embedded version of the OC4J server? What about the standalone OC4J version and the complete Oracle Application server itself?
Thanks in advance,
George

Complete EJB 3.0 implementation is planned for version 10.1.3.1
We are hoping to get a developer preview out on OTN of 10.1.3.1 soon.

Unable to deploy Web App using JPA TopLink Essentials in Tomcat5.5.17

Hi All,
I am trying to deploy a Web App ( used Top Link Essentials ) to Tomcat and i am getting the following Error..
I am strating tomcat using -javaagent:/Path/To/spring-agaent.jar
Dec 14, 2006 9:52:46 AM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already. Could not load oracle.toplink.essentials.internal.weaving.ClassDetails. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
java.lang.IllegalStateException
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1238)
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        at oracle.toplink.essentials.internal.weaving.TopLinkWeaver.transform(TopLinkWeaver.java:84)
        at org.springframework.orm.jpa.persistenceunit.ClassFileTransformerAdapter.transform(ClassFileTransformerAdapter.java:56)
        at sun.instrument.TransformerManager.transform(TransformerManager.java:122)
        at sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:155)
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
        at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1812)
        at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:866)
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1319)
        at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        at java.lang.Class.getDeclaredConstructors0(Native Method)
        at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
        at java.lang.Class.getConstructor0(Class.java:2671)
        at java.lang.Class.newInstance0(Class.java:321)
        at java.lang.Class.newInstance(Class.java:303)
        at org.apache.myfaces.application.ApplicationImpl.createComponent(ApplicationImpl.java:396)
        at com.sun.faces.config.ConfigureListener.verifyObjects(ConfigureListener.java:1438)
        at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:509)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4187)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
        at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:608)
        at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:535)
        at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470)
        at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
        at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
        at org.apache.catalina.core.StandardService.start(StandardService.java:450)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432) Thanks
Sateesh

Spring 2.0 provides custom support for TopLink Essentials in Tomcat out-of-the-box. You should follow the instructions here: http://static.springframework.org/spring/docs/2.0.x/reference/orm.html#orm-jpa-setup-lcemfb-tomcat
Essentially, Spring provides a custom class loader for Tomcat and doesn't use an agent.
--Shaun

How to use (toplink essentials)JPA with EJB 2.1 spec in oc4j 10.1.3.2

I have an application that uses EJB 2.1 spec with SLSB (no entity beans) and uses DAO pattern with hibernate2 for persistence. I want to replace hibernate with toplink-essentials (JPA). I cannot upgrade the EJB spec version as we use some thirdparty beans. The application uses DAO pattern so I should be able to hook in a new toplink DAO impl. What I am struggling with is how do I get hold of the EntityManagerFactory in my EJB 2.1 SLSB. Also I need CMT with XA transactions as our application interacts with jms and database using MDBs and SLSBs.
Prantor

You should be able to use Persistence.createEntityManagerFactory(<your-persistence-unit-name>, properties), and create your EntityManager from that.
To have TopLink integrated with JTA, in your persistence.xml (or properties) you need to use a JTA DataSource, and set the ServerPlatform for your JEE server.

Strange classloader experience with toplink-essentials on Oc4j-10.1.3.3.0

Hi,
I am teaching classes at the Eotvos University/Budapest on a topic where OC4J has been used for 2 years. Students use jdeveloper (regularly updated) to create webapps with EJB3.0+toplink backends. They test their projects first with the JDeveloper embedded OC4J, but after that they deploy it on a central server running standalone OC4J.
Students make quite an intensive and versatile use of the OC4J server, a noteworthy stress-test you may find interesting! The server is a Ubuntu Linux with JDK_1.5.0_14.
1. The first known issue is that after about 10 projects are deployed (small class projects 3-4 EJBs, 3-4 JSP-s each), oc4j regularl goes into a "runaway" mode, i.e. the CPU utilization of the JVM process goes up to 99-100%. Static web content is still available, but all applications stop responding. I can state pretty safely that the applications deployed are fairly harmless and it is not even necessary to run them to make this happen. I.e. after 10-15 apps are depoyed it is enough to start the admin-client.jar or the admin console to experience this problem. (The applications have no problem individually: last year after these issues occurred, we installed them individually for grading and nothing like this happened).
Let me point out that SO FAR this happened with Oc4j-10.1.3.1 and Oc4j-10.1.3.2 only, and this was the main reason we swithed to Oc4j-10.1.3.3.0
2. Another issue that exists both with the earlier versions and 10.1.3.3.0 is that applications need to include the toplink-essentials.jar explicitely if they use EJB3.0 entities. It appears to me that this should not be neessary as there are default definitions for that in config/server.xml (a shared-library definition for toplink-essentials), and in config/system-application.xml (a corresponding import-shared-library tag), but still their applications cannot be deployed because of the follwing error:
Deploy error: Deploy error: Operation failed with error:
HiĂˇnyzĂł osztĂˇly: oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider
FĂĽggĹ' osztĂˇly: com.evermind.server.ejb.persistence.PersistenceUnitManagerImpl
BetĂ¶ltĹ': oc4j:10.1.3
KĂłdforrĂˇs: /opt/oc4j_101330/j2ee/home/lib/oc4j-internal.jar
(On our machines, JDK displays some errors in Hungarian: HiĂˇnyzĂł osztĂˇly=Missing class; FĂĽggĹ' osztĂˇly=Dependent class; BetĂ¶ltĹ'=Loader; KĂłdforrĂˇs=Code source.)
To fix this issue, we used a workaround, i.e. their orion-application.xml is regularly extended with something like:
<library path="/opt/oc4j/toplink/jlib/toplink-essentials.jar"/>
And this solved the problem. Can you explain this?
3. Now, with 10.1.3.3.0 this did not help much either. Although the toplink-essentials.jar was found, another nasty exception happened in the server still during deployment:
Caused by: java.lang.NoSuchMethodException: oracle.toplink.essentials.platform.server.oc4j.Oc4jPlatform.<init>(oracle.toplink.essentials.internal.sessions.DatabaseSessionImpl)
at java.lang.Class.getConstructor0(Class.java:2678)
at java.lang.Class.getConstructor(Class.java:1629)
at oracle.toplink.essentials.internal.ejb.cmp3.EntityManagerSetupImpl.updateServerPlatform(EntityManagerSetupImpl.java:309)
Apparently a class in toplink-essentials.jar (version 2, build 41, i.e. the one that comes with oc4j) cannot properly invoke a the constructor of another class IN THE SAME JAR.
I checked everything, even unzipped and checked the class signatures, and also made sure that there is no other toplink-essentials.jar in the classpath. Still the error remained.
FInally, I tried to add the above libary tag to $OC4J_HOME/config/apllication.xml instead of the applications local orion-application.xml, and - voila!!! - it WORKS now!
Can you explain all this to me? From the documentation the location of the <library> tag in the descriptor files should not amke any difference, but still it seems to do.
Regards: Arpad Bakay

Seems to be a bug. That was the response from Oracle support (Metalink)
Response:
Your issue seems to be related to bug 5594702 - Abstract: EJB30 ENTITY BEAN WITH @ID AND @COLUMN ANNOTATION FAILS TO DEPLOY ON AIX.
There is an issue with the IBM JDK/JRE 1.5's processing of annotations.
Links:
http://www.theserverside.com/discussions/thread.tss?thread_id=37764
http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?forum=367&thread=112543&cat=10
When processing annotations it returns boolean values as false.
Work-around:
Fully specify the @Column annotation's boolean values. If insertable and updatable are set to false (which will happen due to this bug) then TopLink sets the PK
mapping to read-only and the exception seen is expected.
Note: nullable attribute of the @Colmun is not used in the EJB3/JPA preview of 10.1.3.0 If the customer MUST override the default column name then they should use:
@Column(name="column-name", insertable=true, updatable=true)
If they do not wish to override the default column name then simply do not use an @Column annotation.
It can be deleted or commented out in the JDev generated code.
There are two reported annotation processing issues with the AIX JVM. One was fixed in SR1 and the other is fixed
in SR3 (due out Oc 11 - today). Upgrading to these more recent JVM releases may also address this issue.
RECOMMENDED SOLUTIONS:
1. Upgrade the IBM AIX JVM to SR3.
OR
2. Fix all generated @Column annotations as described above

Problems with Toplink Essentials on OracleAS 10.1.3.1 / OC4J 10.1.3.2

Hi, all.
I successfully installed OracleAS 10.1.3.0 and applied patch 5906151 to update do OAS 10.1.3.1 and OC4J 10.1.3.2, running on both Windows and AIX.
I deployed a j2ee app (ejb-jar and ear/war separatelly) on both. My application runs very well on Windows platform, but fails on AIX.
In order to get my app running with EJB 3.0, JPA and Toplink, I had to copy toplink-essentials.jar to $ORACLE_HOME/j2ee/home/applib/ directory.
On AIX I was getting the following error:
exception occurred during method invocation: javax.ejb.EJBException:
   java.lang.RuntimeException: javax.ejb.EJBException: oracle.toplink.essentials.exceptions.ValidationException
          Exception Description: Error encountered when building the @NamedQuery [MyClass.findAll]
             from entity class [class oracle.toplink.essentials.internal.ejb.cmp3.metadata.queries.MetadataNamedQuery].
         Internal Exception: java.lang.IllegalStateException: ClassLoader "myApp.root:0.0.1"
           (from in /oracle/product/10.1.3.0/j2ee/OC4J_1/applications/myApp/):
This loader has been closed and should not be in use.;
But I found a known issue on Metalink [Note:427650.1] (bug 5928776) - https://metalink.oracle.com/metalink/plsql/f?p=130:14:11405609768040641618::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,427650.1,1,1,1,helvetica
I replaced the toplink-essentials.jar and toplink-essentials-agent.jar as stated on the metalink for the version build 41, and tested. And later for the latest build 58.
But I am getting another error message:
Exception [TOPLINK-46] (Oracle TopLink Essentials - 2.0 (Build b58-rc1 (08/05/2007))): oracle.toplink.essentials.exceptions.DescriptorException
Exception Description: There should be one non-read-only mapping defined for the primary key field [MY_TABLE.MY_FIELD].
Descriptor: RelationalDescriptor(xyz.MyClass --> [DatabaseTable(MY_TABLE)])
Runtime Exceptions:
; nested exception is: javax.persistence.PersistenceException: Exception [TOPLINK-0] (Oracle TopLink Essentials - 2.0 (Build b58-rc1 (08/05/2007))): oracle.toplink.essentials.exceptions.IntegrityException
Descriptor Exceptions:
---------------------------------------------------------Does anyone have any idea about this issue?

Seems to be a bug. That was the response from Oracle support (Metalink)
Response:
Your issue seems to be related to bug 5594702 - Abstract: EJB30 ENTITY BEAN WITH @ID AND @COLUMN ANNOTATION FAILS TO DEPLOY ON AIX.
There is an issue with the IBM JDK/JRE 1.5's processing of annotations.
Links:
http://www.theserverside.com/discussions/thread.tss?thread_id=37764
http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?forum=367&thread=112543&cat=10
When processing annotations it returns boolean values as false.
Work-around:
Fully specify the @Column annotation's boolean values. If insertable and updatable are set to false (which will happen due to this bug) then TopLink sets the PK
mapping to read-only and the exception seen is expected.
Note: nullable attribute of the @Colmun is not used in the EJB3/JPA preview of 10.1.3.0 If the customer MUST override the default column name then they should use:
@Column(name="column-name", insertable=true, updatable=true)
If they do not wish to override the default column name then simply do not use an @Column annotation.
It can be deleted or commented out in the JDev generated code.
There are two reported annotation processing issues with the AIX JVM. One was fixed in SR1 and the other is fixed
in SR3 (due out Oc 11 - today). Upgrading to these more recent JVM releases may also address this issue.
RECOMMENDED SOLUTIONS:
1. Upgrade the IBM AIX JVM to SR3.
OR
2. Fix all generated @Column annotations as described above

Accessing the Session in Toplink Essentials

I try access session by this way:
http://ontoplink.blogspot.com/2007/01/accessing-session-in-toplink-essentials.html
and get exception:
(Oracle TopLink Essentials - 2.0 (Build b41-beta2 (03/30/2007))): oracle.toplink.essentials.exceptions.ValidationException
Exception Description: Could not find the session with the name [my_name] in the session.xml file []
Is session.xml needed for this ? I hope not, because it requires project.xml and it maybe require some another... All what I need is:
session.getEventManager().addListener(myEventListener);
to force toplink switch database schema in listener preLogin method. In Hibernate, it can be done by one line in config file.
Lumir

OK, I tried obtain session BEFORE creating EntityManagerFactory and EntityManager.
Now when obtaining it AFTER creating EMF and EM, it works.
But this not solve problem with change db schema, because AFTER create EMF and EM, session is logged in and EventListener preLogin isn't called.
Can anyone point me, how to change db schema ? I know it for connection defined using toplink.jdbc.* properties, but not for JNDI:
public class ToplinkSessionCustomizer implements SessionCustomizer
public void customize(Session session) throws Exception
          if(jdbcUrl == null)
               // JDBC URL is not set, assume JNDI lookup
               JNDIConnector connector = (JNDIConnector) session.getLogin().getConnector();
               connector.setLookupType(JNDIConnector.STRING_LOOKUP);
               // 1. Not works, cause NPE
               // at oracle.toplink.essentials.descriptors.ClassDescriptor.verifyTableQualifiers(ClassDescriptor.java:3518)
               session.getDatasourcePlatform().setTableQualifier(schema);
               SessionEventAdapter preLoginEventListener = new SessionEventAdapter()
               // Listen for preLogin events
                    public void preLogin(SessionEvent event)
                    event.getSession().getLogin().setTableQualifier("myschema");
               // 2. Not works, eventManager is null, cause NPE !
               session.getEventManager().addListener(preLoginEventListener);
          else
// This works OK
               DatabaseLogin login = session.getLogin();
               login.useOracleThinJDBCDriver();
               login.setDatabaseURL(jdbcUrl);
               login.setUserName(userName);
               login.setPassword(password);
               login.setTableQualifier(schema);
     }

Toplink Essentials: how can I not to auto persist computed/virtual column

Tags: Toplink Essentials, JPA, virtual columns
Hi All,
This appears to be a newbie question. But I cannot get it solved.
First, my system is Eclipse + TOPlink essentials.
My relational db table has a computed column. It is derived from a column of the same table.
create table WINE(
WINE_NAME VARCHAR2(25),
WINE_STORAGE_DATE DATE,
VINTAGE AS (EXTRACT(YEAR FROM WINE_STORAGE_DATE))
In my JAVA entity, I would like to map VINTAGE into a "auto-generated" field. In this way, when I update relational db table, VINTAGE won't be in the JPA generated INSERT statement, but I can query the VINTAGE into my java entity/object.
I tried the following JPA annotation in my java entity class.
@Entity
public class Wine implements Serializable {
@GeneratedValue private Integer VINTAGE;
I can query db table -- VINTAGE flows from db table to my java object. But when I update table ( I left VINTAGE un-specified ), I get the following error:
Internal Exception: java.sql.SQLException: ORA-54013: INSERT operation disallowed on virtual columns
Error Code: 54013
Call: INSERT INTO WINE(WINE_NAME, WINE_STORAGE_DATE, VINTAGE) VALUES (?, ?, ?)
bind => PinotNoir, 2003-01-05 00:00:00.0, null
Any suggestions on what annotation tage I should use to tell the JPA Provider not to include VINTAGE in the auto-generated INSERT statement?
Thank you very much.
Jing
Edited by: user11935396 on Sep 25, 2009 1:36 PM
Edited by: user11935396 on Sep 25, 2009 1:37 PM

I am not sure if your annotation @GeneratedValue is proper. According to javadoc "Provides for the specification of generation strategies for the values of primary keys. The GeneratedValue annotation may be applied to a primary key property or field of an entity or mapped superclass in conjunction with the Id annotation."
I would rather try to annotate VINTAGE as @Column(insertable=false, updatable=false)

Replacing Oracle Toplink with TopLink Essentials

Is it possible to force OC4J to use TopLink Essentials by default
instead of Oracle TopLink?

Hi
Replace your toplink jars in your server with the new
jars. it should pick up automatically
Regards,
RaghavendraHi,
I am trying to use the latest version of Toplink Essentials with the embedded OC4J in JDeveloper 10.1.3.
Can you please be more specific?
Which JAR files must be replaced?
Thanks in advance,
George

TopLink Essentials: Using spring session scope on the EntityManagerFactory

Hi,
In one of our projects we are trying to utilize the 2nd level cache of TopLink Essentials. The server code is using the Spring (2.0.7) and is deployed to a web container. We are using a Java client and serializes every object between the client and the server.
When a client is started a lot of "static/common" data is read from the server. The first client started will therefor pay some extra performance cost, but additional clients should hopefully be able to perform better due to the cache. Most of the static data is accessed not using JPQL and should therefor not bypass the cache.
If we configure the EntityManagerFactory using default Spring scoping (singleton) it seems like we are not able to utilize the cache. We can see from the log files that each time a client is started a lot of SQL is executed towards the database (Oracle).
<bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
    <property name="dataSource" ref="dataSource" />
    <property name="jpaVendorAdapter">
      <bean class="org.springframework.orm.jpa.vendor.TopLinkJpaVendorAdapter">
        <property name="showSql" value="false" />
        <property name="generateDdl" value="$repository{toplink.generateDdl}" />
        <property name="database" value="$repository{toplink.database}" />
      </bean>
    </property>
    <property name="jpaProperties">
      <props>
        <prop key="toplink.weaving">static</prop>
        <prop key="toplink.logging.level">FINEST</prop>
      </props>
    </property>
</bean>When we changes the scoping to spring session the behavior is very different. Then we can see that the first client generates a lot of SQL towards the database and pays a startup cost, while subsequently clients seems to be able to utilize the cache.
<bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean" scope="session">
    <aop:scoped-proxy />
    <property name="dataSource" ref="dataSource" />
    <property name="jpaVendorAdapter">
      <bean class="org.springframework.orm.jpa.vendor.TopLinkJpaVendorAdapter">
        <property name="showSql" value="false" />
        <property name="generateDdl" value="$repository{toplink.generateDdl}" />
        <property name="database" value="$repository{toplink.database}" />
      </bean>
    </property>
    <property name="jpaProperties">
      <props>
        <prop key="toplink.weaving">static</prop>
        <prop key="toplink.logging.level">FINEST</prop>
      </props>
    </property>
</bean>Having read the documentation of the spring session scope I'm having a hard time explaining this behavior. As I understand it the EntityManagerFactory will be stored in the HTTP session resulting in a new EntityManagerFactory for each session. I cannot understand how this may result in that we are able to utilize the 2nd level cache? What are the relationship between the EntityManagerFactory and the 2nd level cache?
Is this an accepted way of configuring the EntityManagerFactory or will there be a downside?
I hope someone are able to explain this behavior for me:-)
Best regards,
Rune

Hi Rune,
To understand the shared cache behavior you actually need to understand more about what TopLink Essentials does than what Spring does. When a new factory is created, TopLink Essentials actually just proxies the server session with a factory instance, so the same server session is used. This is why you are seeing the same cache used across multiple factories of the same session.
In the first case, if you are not using JPQL then what are you using to load the data and why are you thinking that it will not bypass the cache?
Using a factory instance for each session is not what I would recommend doing as there are some additional costs associated with establishing a factory (even though the session already exists). The first way should be the correct way, I am just not sure what the circumstances are that are causing your cache to not be warmed. You may want to post more details about that so people can better help you out with that angle.
-Mike

Toplink Essentials Development

Similar Messages

Maybe you are looking for