Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » Toplink to eclipselink upgrade issue(unable to upgrade the eclipselink project )
Toplink to eclipselink upgrade issue [message #659805] Tue, 15 March 2011 12:34 Go to next message
No real name is currently offline No real name
Messages: 4
Registered: March 2011
Junior Member
I have upgrade the toplink to eclipselink using the rename packing and run the project. i am getting the following exception.

Internal exception: Exception [EclipseLink-25008] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.XMLMarshalException
Exception Description: A descriptor with default root element project was not found in the project
at com.amdocs.persistence.dlinfra.ToplinkVersionSpecific.loadPr oject(ToplinkVersionSpecific.java:160)
at com.amdocs.persistence.dlinfra.DLContextFactory.getToplinkPr oject(DLContextFactory.java:256)
at com.amdocs.persistence.dlinfra.DLContextFactory.initServerSe ssion(DLContextFactory.java:121)
at com.amdocs.persistence.dlinfra.DLContextFactory.<init>(DLContextFactory.java:82)
at com.amdocs.persistence.dlinfra.DLContextFactory.getInstance( DLContextFactory.java:388)
at com.amdocs.vad.dl.toplink.DLToplinkAbstract.connect(DLToplin kAbstract.java:21)
at com.amdocs.vad.dl.order.toplink.OrderDLImpl.connect(OrderDLI mpl.java:84)
at com.amdocs.vad.jdbc.ToplinkProvider.connect(ToplinkProvider. java:75)
at com.amdocs.vad.util.tools.ServerSupport.activate(ServerSuppo rt.java:923)
at com.amdocs.vad.ejb.mdb.AbstractMDB.ejbCreate(AbstractMDB.jav a:74)
at com.amdocs.vad.ejb.mdb.order.CancelOrderRequestMDB.ejbCreate (CancelOrderRequestMDB.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ejb.container.manager.MessageDrivenManager.createBe an(MessageDrivenManager.java:305)
at weblogic.ejb.container.pool.MessageDrivenPool.createBean(Mes sageDrivenPool.java:174)
at weblogic.ejb.container.pool.Pool.createInitialBeans(Pool.jav a:299)
at weblogic.ejb.container.manager.MessageDrivenManager.start(Me ssageDrivenManager.java:578)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.md ManagerStart(MessageDrivenBeanInfoImpl.java:1334)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.de ployMessageDrivenBeans(MessageDrivenBeanInfoImpl.java:1314)
at weblogic.ejb.container.deployer.EJBDeployer.deployMessageDri venBeans(EJBDeployer.java:1669)
at weblogic.ejb.container.deployer.EJBDeployer.deployMessageDri venBeansUsingModuleCL(EJBDeployer.java:1446)
at weblogic.ejb.container.deployer.MDBServiceImpl.startService( MDBServiceImpl.java:69)
at weblogic.server.ServiceActivator.start(ServiceActivator.java :96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java: 64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)


The deployment xml lokks as below

<project>
<project-name>vadtoplink19_8</project-name>
<login>
<database-login>
<platform> org.eclipse.persistence.internal.databaseaccess.OraclePlatfo rm </platform>
<driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
<connection-url>jdbc:odbc:Vad12_7</connection-url>
<user-name>irisb1_4</user-name>
<password>75BB9BC4FF108BA1386D1A7FEBE9A17A</password>
<uses-native-sequencing>false</uses-native-sequencing>
<sequence-preallocation-size>50</sequence-preallocation-size >
<sequence-table>SEQUENCE</sequence-table>
<sequence-name-field>SEQ_NAME</sequence-name-field>
<sequence-counter-field>SEQ_COUNT</sequence-counter-field>
<should-bind-all-parameters>false</should-bind-all-parameters >
<should-cache-all-statements>false</should-cache-all-statements >
<uses-byte-array-binding>true</uses-byte-array-binding>
<uses-string-binding>false</uses-string-binding>
<uses-streams-for-binding>false</uses-streams-for-binding>
<should-force-field-names-to-upper-case>false</should-force-field-names-to-upper-case >
<should-optimize-data-conversion>true</should-optimize-data-conversion >
<should-trim-strings>true</should-trim-strings>
<uses-batch-writing>false</uses-batch-writing>
<uses-jdbc-batch-writing>true</uses-jdbc-batch-writing>
<uses-external-connection-pooling>false</uses-external-connection-pooling >
<uses-external-transaction-controller>false</uses-external-transaction-controller >
<type>org.eclipse.persistence.sessions.DatabaseLogin</type >
</database-login>
</login>
<descriptors>
<descriptor>
<java-class>com.amdocs.vad.dl.message.LoggingRecord</java-class >
<tables>
<table>LOGGING_TABLE</table>
</tables>
<primary-key-fields>
<field>LOGGING_TABLE.SEQ_LOGGING</field>
</primary-key-fields>
<descriptor-type-value>Normal</descriptor-type-value>
<sequence-number-field>LOGGING_TABLE.SEQ_LOGGING</sequence-number-field >
<sequence-number-name>SEQ_LOGGING</sequence-number-name>
<identity-map-class> org.eclipse.persistence.internal.identitymaps.SoftCacheWeakI dentityMap </identity-map-class>
<remote-identity-map-class> org.eclipse.persistence.internal.identitymaps.SoftCacheWeakI dentityMap </remote-identity-map-class>
<identity-map-size>100</identity-map-size>
<remote-identity-map-size>100</remote-identity-map-size>
<should-always-refresh-cache>false</should-always-refresh-cache >
<should-always-refresh-cache-on-remote>false</should-always-refresh-cache-on-remote >
<should-only-refresh-cache-if-newer-version>false</should-only-refresh-cache-if-newer-version >
<should-disable-cache-hits>false</should-disable-cache-hits >
<should-disable-cache-hits-on-remote>false</should-disable-cache-hits-on-remote >
<alias>LoggingRecord</alias>

Re: Toplink to eclipselink upgrade issue [message #660821 is a reply to message #659805] Mon, 21 March 2011 14:45 Go to previous messageGo to next message
Gordon Yorke is currently offline Gordon Yorke
Messages: 77
Registered: July 2009
Member
What deployment artifacts are you using? sessions.xml file? are you using JPA or entirely native EclipseLink?

Can you provide the entire exception stack trace including the "caused by" section that has the EclipseLink stack
Re: Toplink to eclipselink upgrade issue [message #660826 is a reply to message #660821] Mon, 21 March 2011 15:38 Go to previous messageGo to next message
No real name is currently offline No real name
Messages: 4
Registered: March 2011
Junior Member
In Toplink 9 we are using deployment.xml no session.xml file .

I converted the depolyment.xml as specified in
http://wiki.eclipse.org/EclipseLink/Examples/MigratingFromOr acleTopLink

we are using following method to read the deployment xml file

org.eclipse.persistence.sessions.factories.XMLProjectReader. read(deployment.xml).

The read method throwing following exception
Internal exception: Exception [EclipseLink-25008] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.XMLMarshalException
Exception Description: A descriptor with default root element project was not found in the project

The depolyment xml looks as below
---------------------------------------------
<?xml version = '1.0' encoding = 'UTF-8'?>
<project>
<project-name>vadtoplink19_8</project-name>
<login>
<database-login>
<platform> org.eclipse.persistence.internal.databaseaccess.OraclePlatfo rm </platform>
<driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
<connection-url>jdbc:odbc:Vad12_7</connection-url>
<user-name>irisb1_4</user-name>
<password>75BB9BC4FF108BA1386D1A7FEBE9A17A</password>
<uses-native-sequencing>false</uses-native-sequencing>
<sequence-preallocation-size>50</sequence-preallocation-size >
<sequence-table>SEQUENCE</sequence-table>
<sequence-name-field>SEQ_NAME</sequence-name-field>
<sequence-counter-field>SEQ_COUNT</sequence-counter-field>
<should-bind-all-parameters>false</should-bind-all-parameters >
<should-cache-all-statements>false</should-cache-all-statements >
<uses-byte-array-binding>true</uses-byte-array-binding>
<uses-string-binding>false</uses-string-binding>
<uses-streams-for-binding>false</uses-streams-for-binding>
<should-force-field-names-to-upper-case>false</should-force-field-names-to-upper-case >
<should-optimize-data-conversion>true</should-optimize-data-conversion >
<should-trim-strings>true</should-trim-strings>
<uses-batch-writing>false</uses-batch-writing>
<uses-jdbc-batch-writing>true</uses-jdbc-batch-writing>
<uses-external-connection-pooling>false</uses-external-connection-pooling >
<uses-external-transaction-controller>false</uses-external-transaction-controller >
<type>org.eclipse.persistence.sessions.DatabaseLogin</type >
</database-login>
</login>
<descriptors>
<descriptor>
<java-class>com.amdocs.vad.dt.Rms_Po_Asn_Timeout</java-class >
<tables>
<table>RMS_PO_ASN_TIMEOUT</table>
</tables>
<primary-key-fields>
<field>RMS_PO_ASN_TIMEOUT.ORDER_SEQ_NO</field>
<field>RMS_PO_ASN_TIMEOUT.TIMEOUT_TYPE</field>
</primary-key-fields>
<descriptor-type-value>Normal</descriptor-type-value>
<identity-map-class> org.eclipse.persistence.internal.identitymaps.SoftCacheWeakI dentityMap </identity-map-class>
<remote-identity-map-class> org.eclipse.persistence.internal.identitymaps.SoftCacheWeakI dentityMap </remote-identity-map-class>
<identity-map-size>100</identity-map-size>
<remote-identity-map-size>100</remote-identity-map-size>
<should-always-refresh-cache>false</should-always-refresh-cache >
<should-always-refresh-cache-on-remote>false</should-always-refresh-cache-on-remote >
<should-only-refresh-cache-if-newer-version>false</should-only-refresh-cache-if-newer-version >
<should-disable-cache-hits>false</should-disable-cache-hits >
<should-disable-cache-hits-on-remote>false</should-disable-cache-hits-on-remote >
<alias>Rms_Po_Asn_Timeout</alias>
<copy-policy>
<descriptor-copy-policy>
<type>org.eclipse.persistence.internal.descriptors.CopyPolicy </type>
</descriptor-copy-policy>
</copy-policy>
<instantiation-policy>
<descriptor-instantiation-policy>
<type> org.eclipse.persistence.internal.descriptors.InstantiationPo licy </type>
</descriptor-instantiation-policy>
</instantiation-policy>
<query-manager>
<descriptor-query-manager>
<existence-check>Check cache</existence-check>
</descriptor-query-manager>
</query-manager>
<event-manager>
<descriptor-event-manager empty-aggregate="true"/>
</event-manager>

<query-keys>
<query-key>
<name>timeout_type</name>
<field-name>RMS_PO_ASN_TIMEOUT.timeout_type</field-name>
<type>org.eclipse.persistence.mappings.querykeys.DirectQueryKey </type>
</query-key>
<query-key>
<name>timeout_ind</name>
<field-name>RMS_PO_ASN_TIMEOUT.timeout_ind</field-name>
<type>org.eclipse.persistence.mappings.querykeys.DirectQueryKey </type>
</query-key>
<query-key>
<name>sys_creation_date</name>
<field-name>RMS_PO_ASN_TIMEOUT.sys_creation_date</field-name >
<type>org.eclipse.persistence.mappings.querykeys.DirectQueryKey </type>
</query-key>

</query-keys>

<mappings>

<database-mapping>
<attribute-name>order_seq_no</attribute-name>
<read-only>false</read-only>
<get-method-name>getOrder_seq_no</get-method-name>
<set-method-name>setOrder_seq_no</set-method-name>
<field-name>RMS_PO_ASN_TIMEOUT.ORDER_SEQ_NO</field-name>
<type>org.eclipse.persistence.mappings.DirectToFieldMapping </type>
</database-mapping>



Re: Toplink to eclipselink upgrade issue [message #661912 is a reply to message #660826] Mon, 28 March 2011 10:06 Go to previous message
James Sutherland is currently offline James Sutherland
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member

Your deployment xml file is quite old. You need to first upgrade it to the TopLink 10.1.3 format, before upgrading to EclipseLink.

(download 10.1.3 and load and store the project).


James : Wiki : Book : Blog : Twitter
Previous Topic:MOXy - xlink reference to previously marshalled objects
Next Topic:How To modify Eclipselink JPA 2.0 connection retry behaviour
Goto Forum:
  


Current Time: Fri Aug 29 14:29:47 EDT 2014

Powered by FUDForum. Page generated in 0.02585 seconds