• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Kodo 3.2.2 on Jboss 4.0.5.GA

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can any one provide some information on Kodo 3.2.2 implementation on Jboss 4.0.5.GA.
It will be the big help, like if you provide some examples or links.

I can provide data on the difficulties what I am facing now.

Thanks in advance.

Shridhar Bhat
 
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Shridhar,

Welcome to JavaRanch


Can any one provide some information on Kodo 3.2.2 implementation on Jboss 4.0.5.GA.



I guess Kodo is BEA System's implementation of Sun's Enterprise JavaBeans Persistence 3.0 (JPA)? I personally havent configured JBoss to use any other JPA implementation other than the default Hibernate. But is there any specific reason for using 4.0.5 GA instead of the latest stable version of JBoss-4.2.2 GA?

I can provide data on the difficulties what I am facing now.



Yes, please provide more details so that if anyone else has experience on configuring Kodo, they will be able to help.
 
Shridhar Bhat
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We have the product which uses Kodo 3.2.2 and running on WL 8.1 and WAS 6.0. Now we are porting the same application to Jboss.

Configurations on Jboss 4.0.5.GA

1. Kodo-jdo.rar file in the //deploy directory
2. Modified the ra.xml inside rar file with Proper Connection Factory Names.
3. Created the -ds.xml files.
4. Kodo.properties files were placed in the //conf folder.
Sample -ds files

mssql-xa-dsn-ds.xml
<?xml version="1.0" encoding="UTF-8"?>
<connection-factories>
<tx-connection-factory>
<jndi-name>jdo/DSN</jndi-name>
<adapter-display-name>KodoJDO</adapter-display-name>
<rar-name>kodo-jdo.rar</rar-name>
<connection-definition>javax.resource.cci.ConnectionFactory</connection-definition>
<config-property name="LicenseKey" type="java.lang.String">xxxx-xxxx-xxxx-xxxx-xxxx</config-property>
<config-property name="ConnectionFactoryName">java:/xa-data-source</config-property>
<config-property name="TransactionMode" type="java.lang.String">managed</config-property>
</tx-connection-factory>
</connection-factories>


mssql-xa-cf-ds.xml
<datasources>
<xa-datasource>

<jndi-name>xa-data-source</jndi-name>
<track-connection-by-tx/>
<isSameRM-override-value>true</isSameRM-override-value>
<xa-datasource-class>com.microsoft.jdbcx.sqlserver.SQLServerDataSource</xa-datasource-class> -->

<xa-datasource-property name="ServerName">MachineName</xa-datasource-property>
<xa-datasource-property name="DatabaseName">DataBaseName</xa-datasource-property>
<xa-datasource-property name="SelectMethod">cursor</xa-datasource-property>

<user-name>sa</user-name>
<password>sa</password>

<!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
<metadata>
<type-mapping>MS SQLSERVER2000</type-mapping>

</metadata>
</xa-datasource>

</datasources>
 
Shridhar Bhat
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Place the -ds files in the deploy directory. We have both xa and non xa transactions. create the respective files.
U can get from //JCA folder of Jboss Docs.

Now I am able to get the data after querying from the client.
Not able to insert the data. it is throwing the error like

Attempt to update the sequence table "JDO_SEQUENCE" failed. The sequence table is typically created when you run the mappingtool's refresh action on any datastore identity class. If you have not run the mappingtool but want to create the sequence table, run:
java kodo.jdbc.schema.DBSequenceFactory -action add
at kodo.util.DataStoreException.newSerializableInstance(DataStoreException.java:74)
at kodo.util.DataStoreException.writeReplace(DataStoreException.java:61)
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:324)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:882)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
at java.lang.Throwable.writeObject(Throwable.java:648)
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:324)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:795)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1294)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:299)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)


Please provide some inputs on the same. Thanks a lot for your query as well the suggestions
 
Shridhar Bhat
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
EDIT THE CONNECTION FACTORY WITH DRIVER AND CONNECTIONFACTORY2NAME INFORMATIONS
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic