Kodo on jboss-3.0.0RC1

Has anyone gotten KodoJDO to successfully deploy on jboss-3.0.0RC1? It
seems that it deploys ok, but does not register any kodo object under the
name "java:/kodo" or whatever jndi name you have specified in the
kodo-services.xml file. Below is my kodo-services.xml file. Does anyone
see any problems?
Thanks,
-Chris
<?xml version="1.0" encoding="UTF-8"?>
<server>

<classpath codebase="lib" archives="*"/>
<mbean code="org.jboss.resource.ConnectionFactoryLoader"
name="jboss.jca:service=ConnectionFactoryLoader,name=Kodo">
<attribute name="JndiName">kodo</attribute>
<depends optional-attribute-name="ResourceAdapterName">
jboss.jca:service=RARDeployment,name=KodoJDO
</depends>
<depends optional-attribute-name="ConnectionManagerFactoryLoaderName">
jboss.jca:service=ConnectionManagerFactoryLoader,name=MinervaNoTransCMFactory
</depends>

<attribute name="ManagedConnectionFactoryProperties">
LicenseKey=<insert your own>
MinPool=0
MaxPool=10
ConnectionDriverName=org.hsqldb.jdbcDriver
ConnectionURL=jdbc:hsqldb:hsql://localhost:1476
ConnectionUserName=sa
ConnectionPassword=
DictionaryName=com.solarmetric.kodo.impl.jdbc.schema.dict.HSQLDictionary
WarnOnPersistentTypeFailure=true
</attribute>
<attribute name="ConnectionManagerProperties">
MinSize=0
MaxSize=10
BlockingTimeoutMillis=5000
IdleTimeoutMinutes=30
CleanupIntervalMinutes=10
MaxIdleTimeoutPercent=1.0
</attribute>
<attribute name="PrincipalMappingClass">
org.jboss.resource.security.ManyToOnePrincipalMapping
</attribute>
<attribute name="PrincipalMappingProperties">
</attribute>
</mbean>
</server>

Chris-
Sorry for the long delay in responding. The problem is that the JBoss
people have completely changed the configuration format for resource
adaptor -service.xml files between 3.0.0beta and 3.0.0RC1, and there is
no documentation on it as of yet (see my posting on the thread "NPE when
calling getConnection() with JBoss").
I'll work on making a working example for 3.0.0RC1.
Chris West <[email protected]> wrote:
Has anyone gotten KodoJDO to successfully deploy on jboss-3.0.0RC1? It
seems that it deploys ok, but does not register any kodo object under the
name "java:/kodo" or whatever jndi name you have specified in the
kodo-services.xml file. Below is my kodo-services.xml file. Does anyone
see any problems?
Thanks,
-Chris
<?xml version="1.0" encoding="UTF-8"?>
<server>

<classpath codebase="lib" archives="*"/>
<mbean code="org.jboss.resource.ConnectionFactoryLoader"
name="jboss.jca:service=ConnectionFactoryLoader,name=Kodo">
<attribute name="JndiName">kodo</attribute>
<depends optional-attribute-name="ResourceAdapterName">
jboss.jca:service=RARDeployment,name=KodoJDO
</depends>
<depends optional-attribute-name="ConnectionManagerFactoryLoaderName">
jboss.jca:service=ConnectionManagerFactoryLoader,name=MinervaNoTransCMFactory
</depends>

<attribute name="ManagedConnectionFactoryProperties">
LicenseKey=<insert your own>
MinPool=0
MaxPool=10
ConnectionDriverName=org.hsqldb.jdbcDriver
ConnectionURL=jdbc:hsqldb:hsql://localhost:1476
ConnectionUserName=sa
ConnectionPassword=
DictionaryName=com.solarmetric.kodo.impl.jdbc.schema.dict.HSQLDictionary
WarnOnPersistentTypeFailure=true
</attribute>
<attribute name="ConnectionManagerProperties">
MinSize=0
MaxSize=10
BlockingTimeoutMillis=5000
IdleTimeoutMinutes=30
CleanupIntervalMinutes=10
MaxIdleTimeoutPercent=1.0
</attribute>
<attribute name="PrincipalMappingClass">
org.jboss.resource.security.ManyToOnePrincipalMapping
</attribute>
<attribute name="PrincipalMappingProperties">
</attribute>
</mbean>
</server>--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Kodo Java Data Objects Full featured JDO: eliminate the SQL from your code

Similar Messages

NPE when calling getConnection() with JBoss 3.0.0RC1

I'm getting the following exception only when I'm using JBoss 3.0.0RC1.
No problem with earlier version of JBoss 3.0, so this maybe a JBoss
issue.
However, I can't debug this without knowing what URL Kodo is trying
to look up. My guess is getTransaction() is trying to look up the
transaction
manager and is passing a null URL string.
20:19:54,715 ERROR [STDERR] java.lang.NullPointerException
20:19:54,725 ERROR [STDERR] at
javax.naming.InitialContext.getURLScheme(Init
ialContext.java:227)
20:19:54,725 ERROR [STDERR] at
javax.naming.InitialContext.getURLOrDefaultIn
itCtx(InitialContext.java:276)
20:19:54,735 ERROR [STDERR] at
javax.naming.InitialContext.lookup(InitialCon
text.java:350)
20:19:54,745 ERROR [STDERR] at
com.solarmetric.kodo.ee.JNDIManagedRuntime.ge
tTransaction(JNDIManagedRuntime.java:36)
20:19:54,755 ERROR [STDERR] at
com.solarmetric.kodo.ee.EEFactoryHelper.getPe
rsistenceManager(EEFactoryHelper.java:102)
20:19:54,755 ERROR [STDERR] at
com.solarmetric.kodo.impl.jdbc.ee.EEPersisten
ceManagerFactory.newPersistenceManager(EEPersistenceManagerFactory.java:148)
20:19:54,765 ERROR [STDERR] at
com.solarmetric.kodo.impl.jdbc.ee.JDOConnecti
onFactory.getConnection(JDOConnectionFactory.java:89)
20:19:54,775 ERROR [STDERR] at
com.solarmetric.kodo.impl.jdbc.ee.JDOConnecti
onFactory.getConnection(JDOConnectionFactory.java:70)

Yan-
The JBoss people have seen it fit to change the mechanism for
configuring Resource Managers between 3.0.0 beta and 3.0.0 RC1, as per
http://www.jboss.org/online-manual/HTML/ch03.html:
Access to Resource Managers
THIS CHAPTER IS PRIMARILY RELEVANT TO JBOSS 3 (RABBITHOLE) VERSIONS
BEFORE RC1
THE MBEANS FOR CONFIGURING DATASOURCES/ADAPTERS IN RC1 ARE COMPLETELY
DIFFERENT FROM THOSE DESCRIBED HERE. FOR DESCRIPTIONS OF EACH ATTRIBUTE,
CONSULT THE GENERATED JMX-API DOCUMENTATION.
I am going to work on putting together an example working configuration,
but it is difficult without any documentation or useful examples. In the
meantime, you may want to manually bind a PersistenceManagerFactory into
JNDI and just use that.
Yan Or <[email protected]> wrote:
JCA. See my other postings "kodo.jar and systems.pref".
Interestingly, with the earlier version of JBoss 3.0.0, it works
even though I didn't package system.prefs with the .rar file, so
I'm guessing it uses a default value?
I also tried looking up "java:/TransactionManager" in the same
method where getConnection() was called and I was able to
find the object.
Patrick Linskey wrote:
Yan,
It's looking up the pref called 'tm-location' (which we set to
'java:/TransactionManager' in our default system.prefs).
Are you deploying via JCA or JNDI?
-Patrick
Yan Or <[email protected]> writes:
I'm getting the following exception only when I'm using JBoss 3.0.0RC1.
No problem with earlier version of JBoss 3.0, so this maybe a JBoss
issue.
However, I can't debug this without knowing what URL Kodo is trying
to look up. My guess is getTransaction() is trying to look up the
transaction
manager and is passing a null URL string.
20:19:54,715 ERROR [STDERR] java.lang.NullPointerException
20:19:54,725 ERROR [STDERR] at
javax.naming.InitialContext.getURLScheme(Init
ialContext.java:227)
20:19:54,725 ERROR [STDERR] at
javax.naming.InitialContext.getURLOrDefaultIn
itCtx(InitialContext.java:276)
20:19:54,735 ERROR [STDERR] at
javax.naming.InitialContext.lookup(InitialCon
text.java:350)
20:19:54,745 ERROR [STDERR] at
com.solarmetric.kodo.ee.JNDIManagedRuntime.ge
tTransaction(JNDIManagedRuntime.java:36)
20:19:54,755 ERROR [STDERR] at
com.solarmetric.kodo.ee.EEFactoryHelper.getPe
rsistenceManager(EEFactoryHelper.java:102)
20:19:54,755 ERROR [STDERR] at
com.solarmetric.kodo.impl.jdbc.ee.EEPersisten
ceManagerFactory.newPersistenceManager(EEPersistenceManagerFactory.java:148)
20:19:54,765 ERROR [STDERR] at
com.solarmetric.kodo.impl.jdbc.ee.JDOConnecti
onFactory.getConnection(JDOConnectionFactory.java:89)
20:19:54,775 ERROR [STDERR] at
com.solarmetric.kodo.impl.jdbc.ee.JDOConnecti
onFactory.getConnection(JDOConnectionFactory.java:70)
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Kodo Java Data Objects Full featured JDO: eliminate the SQL from your code

JBoss 4.0.0RC1/3.2.3 - JDeveloper 10g - ADF UIX

While I realize that JDeveloper has only been tested (to one degree or another) with JBoss 3.2.X, I decided to try and publish to JBoss 4.X after failing with 3.2.X. (The results are the same for either server version).
I have a simple master-detail page off of which I have a create action on the detail section. The primary key is a DBSequence number that goes against a table with an insert trigger defined and a sequence for that field.
The create action opens an input form for creating a new record. In the emdedded OC4J, everything works just fine. Depsite following the developer's review paper on deploying to both standalone OC4J and JBoss, it fails completely. Errors are different, but I thought I would start with JBoss since this equates to our development environment:
When the create button is selected to initiate the action, the input form comes up but in the place where I would expect to see a temporary sequence value in the primary key field, the value is blank and the Execute button on this form does not activate. In addition, JBoss error log (both JBoss 3.2.3 and JBoss 4.0.0RC1 (and DR4)) displays the following (just showing a fragment):
2004-07-28 10:37:34,315 ERROR [org.jboss.web.localhost.Engine] StandardContext[paros]null
java.lang.ClassCastException
     at oracle.jbo.uicli.uix.PrimitiveTypes.getArray(PrimitiveTypes.java:122)
     at oracle.jbo.uicli.uix.JUCtrlAdaptValueBindingRef._adapt(JUCtrlAdaptValueBindingRef.java:106)
     at oracle.jbo.uicli.uix.JUCtrlAdaptValueBindingRef._adapt(JUCtrlAdaptValueBindingRef.java:96)
     at oracle.jbo.uicli.uix.JUCtrlAdaptValueBindingRef.access$4000071(JUCtrlAdaptValueBindingRef.java:40)
     at oracle.jbo.uicli.uix.JUCtrlAdaptValueBindingRef$CompositeModel.get(JUCtrlAdaptValueBindingRef.java:219)
     at org.apache.commons.el.ArraySuffix.evaluate(ArraySuffix.java:218)
     at org.apache.commons.el.ComplexValue.evaluate(ComplexValue.java:145)
     at org.apache.commons.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:263)
     at org.apache.commons.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:190)
     at oracle.jsp.el.OracleExpressionEvaluator.evaluate(Unknown Source)
     at oracle.jsp.el.OracleExpression.evaluate(Unknown Source)
     at oracle.cabo.ui.expl.ELBoundValue._evaluate(Unknown Source)
     at oracle.cabo.ui.expl.ELBoundValue.getValue(Unknown Source)
     at oracle.cabo.ui.collection.DataObjectListNodeList.getDataObjectList(Unknown Source)
     at oracle.cabo.ui.collection.DataObjectListNodeList.size(Unknown Source)
     at oracle.cabo.ui.BaseUINode.getIndexedChildCount(Unknown Source)
     at oracle.cabo.ui.BaseRenderer.getVisibleIndexedChildCount(Unknown Source)
     at oracle.cabo.ui.laf.base.xhtml.ColumnRenderer._startRowMode(Unknown Source)
     at oracle.cabo.ui.laf.base.xhtml.ColumnRenderer.render(Unknown Source)
     at oracle.cabo.ui.BaseUINode.render(Unknown Source)
     at oracle.cabo.ui.BaseUINode.render(Unknown Source)
     at oracle.cabo.ui.BaseRenderer.renderChild(Unknown Source)
     at oracle.cabo.ui.BaseRenderer.renderIndexedChild(Unknown Source)
     at oracle.cabo.ui.laf.base.xhtml.ColumnGroupRenderer._renderVisibleIndexedChildren(Unknown Source)
     at oracle.cabo.ui.laf.base.xhtml.ColumnGroupRenderer.render(Unknown Source)
     at oracle.cabo.ui.BaseUINode.render(Unknown Source)
     at oracle.cabo.ui.BaseUINode.render(Unknown Source)
     at oracle.cabo.ui.BaseRenderer.renderChild(Unknown Source)
     at oracle.cabo.ui.BaseRenderer.renderIndexedChild(Unknown Source)
Has anyone been at all successful using ADF-UIX from JDeveloper 10g and JBoss of any version? (Note I have followed the steps to install ADF Runtime, setvars, etc).
Thanks
Ray

Yes. I have no problem with jdeveloper10g and jboss-3.2.3.
Niether on my note with both linux, win, nor on production server with linux.
Carefully look where do you install ADF Runtime (server defualt), and what server do you start (default is all). Simply change startup server to default or, copy jboss-3.2.3/server/default/deploy/bc4j.ear to jboss-3.2.3/server/all/deploy/

Jboss kodo-service.xml deploy problem

Hi,
I'm trying to deploy kodo-service.xml in jboss-3.0.0RC1 and get this error:
2002-06-11 13:48:06,030 ERROR [org.jboss.deployment.MainDeployer] could
not start deployment
:file:/D:/jbossrc1/server/default/deploy/kodo-service.xml
java.lang.AbstractMethodError
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.<init>(JDBCPersistenceManagerFactory.java:153)
at
com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory.<init>(EEPersistenceManagerFactory.java:53)
at
com.solarmetric.kodo.impl.jdbc.ee.JDOConnectionFactory.<init>(JDOConnectionFactory.java:41)
I get the same error using the default kodo-service.xml file included with
the downloaded package.
Any ideas?
Thanks!
Jesper

Note that neither Kodo JDO 2.3.0 beta nor Kodo JDO 2.2.5 does not exhibit
the 1.4 problem.
-Patrick
On 6/11/02 8:07 AM, "Jesper Ladegaard" <[email protected]> wrote:
Okay,
I can see from some other post it\'s a Java 1.4 problem.
/Jesper
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com

KODO & JBoss configuration question

Hi!
I deployed KODO on JBoss 3.2.1 and it seems to work fine. However, the
configuration properties I set do not show up on JBoss JMX management
console.
When I click on jboss.jca --> name=KodoJDO,service=RARDeployment, I get
the properties for the connection I have configured. Or not. The properties
that are displayed do not reflect the ones I have set. I have in kodo-
ds.xml e.g.
<config-property name="StatementCacheMaxSize"
type="int">0</config-property>
<config-property name="EnableQueryExtensions"
type="java.lang.Boolean">true</config-property>
but on the jboss MBean inspector these are shown as 70 and false,
respectively. On the MBean inspector e.g. the ConnectionDriverName seems to
be empty (although it is defined in the kodo-ds.xml file). Am I looking in
the wrong place or doing something else wrong or is this a but in KODO or
JBoss?
Here is my kodo-ds.xml file in its entirety:
<?xml version="1.0" encoding="UTF-8"?>
<connection-factories>
<tx-connection-factory>
<jndi-name>persistencemanagertehdas</jndi-name>
<adapter-display-name>KodoJDO</adapter-display-name>
<config-property name="LicenseKey"
type="java.lang.String">MY LICENSE KEY</config-property>
<config-property name="PersistenceManagerFactoryClass"
type="java.lang.String">com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory</config-
property>
<config-property name="ConnectionDriverName"
type="java.lang.String">com.mysql.jdbc.Driver</config-property>
<config-property name="ConnectionUserName"
type="java.lang.String">myusername</config-property>
<config-property name="ConnectionPassword"
type="java.lang.String">myspassword</config-property>
<config-property name="ConnectionURL"
type="java.lang.String">jdbc:mysql://localhost/mydb</config-property>
<config-property name="StatementCacheMaxSize"
type="int">0</config-property>
<config-property name="EnableQueryExtensions"
type="java.lang.Boolean">true</config-property>
</tx-connection-factory>
</connection-factories>
-Antti

Are you not seeing the changes in Kodo runtime? Note that you can
access many of these fields programatically:
import com.solarmetric.kodo.impl.jdbc.*;
import com.solarmetric.kodo.runtime.*;
JDBCConfiguration conf = (JDBCConfiguration)
((PersistenceMaangerImpl) pm).getConfiguration ();
Antti Karanta wrote:
>
>
Hi!
I deployed KODO on JBoss 3.2.1 and it seems to work fine. However, the
configuration properties I set do not show up on JBoss JMX management
console.
When I click on jboss.jca --> name=KodoJDO,service=RARDeployment, I get
the properties for the connection I have configured. Or not. The
properties that are displayed do not reflect the ones I have set. I have
in kodo- ds.xml e.g.
<config-property name="StatementCacheMaxSize"
type="int">0</config-property>
<config-property name="EnableQueryExtensions"
type="java.lang.Boolean">true</config-property>
but on the jboss MBean inspector these are shown as 70 and false,
respectively. On the MBean inspector e.g. the ConnectionDriverName seems
to be empty (although it is defined in the kodo-ds.xml file). Am I
looking in the wrong place or doing something else wrong or is this a
but in KODO or JBoss?
Here is my kodo-ds.xml file in its entirety:
<?xml version="1.0" encoding="UTF-8"?>
<connection-factories>
<tx-connection-factory>
<jndi-name>persistencemanagertehdas</jndi-name>
<adapter-display-name>KodoJDO</adapter-display-name>
<config-property name="LicenseKey"
type="java.lang.String">MY LICENSE KEY</config-property>
<config-property name="PersistenceManagerFactoryClass"
type="java.lang.String">com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory</config-
property>
<config-property name="ConnectionDriverName"
type="java.lang.String">com.mysql.jdbc.Driver</config-property>
<config-property name="ConnectionUserName"
type="java.lang.String">myusername</config-property>
<config-property name="ConnectionPassword"
type="java.lang.String">myspassword</config-property>
<config-property name="ConnectionURL"
type="java.lang.String">jdbc:mysql://localhost/mydb</config-property>
<config-property name="StatementCacheMaxSize"
type="int">0</config-property>
<config-property name="EnableQueryExtensions"
type="java.lang.Boolean">true</config-property>
</tx-connection-factory>
</connection-factories>
-Antti
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com

JBoss

Hi,
I configure jboss-4.0.0RC1 in my linux server. Is it possible to communicate with tomcat. Because one of my clinet server contains j2sdk/ tomcat ...and j2ee.jar file also available.
I get confused why he has done this configuration. And all the war file is deployed under jboss/ ...default/ deploy/ folder.

Yes, [JBoss was retired (TA24962)|http://support.apple.com/kb/TA24962], and (FWIW) [here are the generic JBoss installation instructions|http://docs.jboss.org/jbossas/jboss4guide/r4/html/ch01.html].

Deployement problem in jboss for rar

Hi all,
I may be wrong to post this messsage in this form, sorry. I am new to JCA. I tried to deploy the hello world rar (ibm example for jca) in jboss but it failed, the following is the execption i am getting at the time of deployement
14:19:40,953 ERROR [MainDeployer] Could not initialise deployment: file:/C:/jbos
s-4.0.0RC1/server/default/deploy/hw-ds.xml
org.jboss.deployment.DeploymentException: Could not parse dd; - nested throwable
: (org.xml.sax.SAXParseException: A pseudo attribute name is expected. )
at org.jboss.deployment.XSLSubDeployer.findDd(XSLSubDeployer.java:255)
at org.jboss.deployment.XSLSubDeployer.init(XSLSubDeployer.java:188)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:727)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:664)
at org.jboss.deployment.MainDeployer.addDeployer(MainDeployer.java:267)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
Incompletely deployed packages:
org.jboss.deployment.DeploymentInfo@4b279edb { url=file:/C:/jboss-4.0.0RC1/serve
r/default/deploy/hw-ds.xml }
deployer: org.jboss.deployment.XSLSubDeployer@178655
status: null
state: FAILED
watch: file:/C:/jboss-4.0.0RC1/server/default/deploy/hw-ds.xml
altDD: null
lastDeployed: 1124959780953
lastModified: 1124959779093
mbeans:
What i did was
1. created/compiled all the class files (Connection, ConnectionFactory, Records....)
2. created the jar file hw.jar
3. created deployement descriptor META-INF/ra.xml
4. created the rar file hw.rar
5. created hw-ds.xml (i may miss some thing in this file deployment sepcfic to jboss)
<?xml version="1.0" encoding="UTF-8">
<connection-factories>
<no-tx-connection-factory>
<jndi-name>HW</jndi-name>
<rar-name>hw.rar</rar-name>
<connection-definition>
javax.resource.cci.ConnectionFactory
</connection-definition>
</no-tx-connection-factory>
</connection-factories>
i may miss something in this file... please help me what i am missing to run this application
thanks in advance
baiju

Hi Baiju,
Give a chance to add a final question mark ("?") in the first line of your xml datasource definition file, like this:
<?xml version="1.0" encoding="UTF-8"?>
HTH,
-Brice.

Difference in JBOSS/Tomcat

Hi,
I worked with Tcomat and jboss. I find in the client linux machine that contains two folder such as jboss-3.2.2RC1_tomcat-4.1.24 and jboss-4.0.0RC1.
I am unable understand the structure of jboss-3.2.2RC1_tomcat-4.1.24 . I hope instead of tomcat we can use this one. It it is then how to start and how to change the port number in server.xml file.
Please let me know the difference between these two.

Hi,
I like to know is it "jboss-3.2.2RC1_tomcat-4.1.24 " is like and Tomcat 5.0.

JDOUserExceptions and JBoss commits

Using Kodo and JBoss quite a few of my mistakes are detected at commit
time, causing Kodo to throw a JDOUserException. This is caught and
hidden by jboss, resulting in a stack trace of the sort shown below.
I can view the JDOUserException by catching it in my debugger (Eclipse),
but I'd also like to log it somehow.
Is there a way of logging every JDOUserException?
javax.transaction.RollbackException Unable to commit, tx=XidImpl
[FormatId=257, GlobalId=QUADROPHENIA//309, BranchQual=]
status=STATUS_ROLLEDBACK Stack Trace:
* org.jboss.tm.TxCapsule.commit(TxCapsule.java:393)
* org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:73)
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:201)
* org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60)
Thanks,
Tom

Using Kodo and JBoss quite a few of my mistakes are detected at commit
time, causing Kodo to throw a JDOUserException. This is caught and
hidden by jboss, resulting in a stack trace of the sort shown below.
I can view the JDOUserException by catching it in my debugger (Eclipse),
but I'd also like to log it somehow.
Is there a way of logging every JDOUserException?
javax.transaction.RollbackException Unable to commit, tx=XidImpl
[FormatId=257, GlobalId=QUADROPHENIA//309, BranchQual=]
status=STATUS_ROLLEDBACK Stack Trace:
* org.jboss.tm.TxCapsule.commit(TxCapsule.java:393)
* org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:73)
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:201)
* org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60)
Thanks,
Tom

Reading properties in kodo.rar

Hi guys,
There seems to be a stalemate between Kodo and JBoss on reading properties of type Boolean or
Integer. I haven't been able to configure Optimistic, RetainValues, etc. using either
kodo-service.xml or ra.xml. The issue as Marc has explained it to all the world is that JBoss won't
read properties other than String properties. They should fix this, but they have lot of other
chickens to fry. In the meantime, wouldn't it be fairly easy for Kodo to provide a workaround?
Provide overloaded String methods for each of the property methods that take int and boolean? Then
the property could be set as a string. The JCA rar approach to deploying Kodo in JBoss or any EJB
container is just too nice to allow it to slip from your grip, in my opinion.
David Ezzio

emmm ... however .. it is my bug :) ...
it does work ... however in another place process of reading proeprty goes through SystemResource...

Toplink compared to its competitors and futur of this product in O/R domain

I am sincerely disappointed by the evolution of TopLink whereas I have been in favour of this product for several years at important customers.
1- New version 10.1.3 (10.0.3 included) has been in beta for almost 3 years!
2- patch corrects only the bugs without any evolution on the level of the functionalities, all the new functionalities are in the 10.1.3 which does not manage to leave. By way of comparison of the product as KODO JDO brings in each patch: New features + Notable Exchanges + Bugfixes 3.4.0 - 3.3.4 - 3.3.3 - 3.3.2 - 3.3.1 - 3.3.0 -! I AM JEALOUS OF KOKO CUSTOMERS
You can see KOKO evolution on 2005 at : http://www.solarmetric.com/Software/Documentation/3.4.0/docs/relnotes.html
3- Other editors (KODO+COCOBASE+JBOSS) start to set up beta versions EJB 3.0 with very very complete documenatation and product. Whereas Toplink provides only examples (tutorial) over OC4J (10.1.3 preview in beta since 3 years!) . No real toplink (bata vversion) of Documentation or Product. Like KODO 4 @ : http://www.solarmetric.com/Software/beta/4.0.0EA/
+ Real and Rich documentation @ : http://www.solarmetric.com/Software/Documentation/4.0.0EA/docs/
4- 4 10.1.3 preview Toplink brings functionalities JCA, JAXP but not much of things on the level of mapping O/R: updateAll, cacheEviction, returning, java.util.logging. These functionalities already available on the others concurrent product do not make me any more dream !
I hope that it other evolutions (not announced) on Object/Relational scope ?
5- does Oracle have still wants to really invest in O/R mapping. There is much marketing, much of mediatic show (Eclipse, GlassFish, EJB3 lead) but not much of technical evolutions compared to competitors.
Thank you to product management make a factual answer because I am a real customer, I am really in favour of the product for 5 years. But I am really disappointed when I see new small actors (KODO...) much better doing?

I am sincerely disappointed by the evolution of
TopLink whereas I have been in favour of this product
for several years at important customers. I am sorry to hear about your disappointment. Hopefully I can provide some insight into where we are with TopLink. It is a critical part of our J2EE/EJB infrastructure providing its classic POJO persistence as well as EJB 2.1 CMP/BMP, and now our preview support of EJB 3.0 persistence.
1- New version 10.1.3 (10.0.3 included) has been in
beta for almost 3 years! As an integrated part of the Oracle Application Server we ship in coordination with the overall release. I understand your frustration and we are working hard to ensure we have a high quality 10.1.3 AS release as well as a first rate persistence solution.
2- patch corrects only the bugs without any evolution
on the level of the functionalities, all the new
functionalities are in the 10.1.3 which does not
manage to leave. By way of comparison of the product
as KODO JDO brings in each patch: New features +
Notable Exchanges + Bugfixes 3.4.0 - 3.3.4 - 3.3.3 -
3.3.2 - 3.3.1 - 3.3.0 -! I AM JEALOUS OF KOKO
CUSTOMERS
You can see KOKO evolution on 2005 at :
http://www.solarmetric.com/Software/Documentation/3.4.
0/docs/relnotes.htmlOur patch-sets are just that. Patches to fix issues important to our customers. They are not new feature releases. As an independent product (prior to the Oracle acquisition) we also had many smaller releases but we were also not well integrated with any container. This integration providing better diagnostics, management, and out of the box support requires us to integrate with the container. I believe you will find Kodo will start to feel this as BEA starts to deliver an integrated persistence solution that may compete with TopLink's complete solution.
Note: This does not mean that we are not supporting other containers. We do extensive testing across non-Oracle databases and application servers to ensure that we continue to work well there as well.
3- Other editors (KODO+COCOBASE+JBOSS) start to set
up beta versions EJB 3.0 with very very complete
documenatation and product. Whereas Toplink provides
only examples (tutorial) over OC4J (10.1.3 preview in
beta since 3 years!) . No real toplink (bata
vversion) of Documentation or Product. Like KODO 4 @
: http://www.solarmetric.com/Software/beta/4.0.0EA/
+ Real and Rich documentation @ :
http://www.solarmetric.com/Software/Documentation/4.0.
0EA/docs/At the time of our EJB 3.0 preview we had the best support available for both within the container as well as outside the container. This was primarily documented through how-to's. As we move towards our release (post 10.1.3) that implements the complete specification, which is not yet final, we will be delivering more complete and formal documentation.
The feedback I had received on our how-to's has been excellent to date. It does require more updates now with our 10.1.3 release to address additional functionality we will be providing in the EJB 3.0 persistence areas.
4- 4 10.1.3 preview Toplink brings functionalities
JCA, JAXP but not much of things on the level of
mapping O/R: updateAll, cacheEviction, returning,
java.util.logging. These functionalities already
available on the others concurrent product do not
make me any more dream !
I hope that it other evolutions (not announced) on
Object/Relational scope ?If you look at the list of new features in 10.1.3 here you will see that we have also invested heavily in improvements to our core ORM.
updateAll = UpdateAllQuery
cacheEviction = cache invalidation/expiration (time-to-live) as well as cache coordination mode using invalidation
returning= we have a returning policy for use with triggers and stored procs
logging = we have updated our logging infrastructure to use java.util.logging
Many of these and others have been available in our earlier previews as well. We have a dedicated team here focused both on ORM as well as OXM (including JCA). I would estimate that 75% of our efforts have been on enhanced ORM functionality.
>
5- does Oracle have still wants to really invest in
O/R mapping. There is much marketing, much of
mediatic show (Eclipse, GlassFish, EJB3 lead) but not
much of technical evolutions compared to
competitors.I believe with 10.1.3 we raise the bar of ORM persistence solutions. The new ORM functionality and improved mapping editors will provide existing users new features they have been asking for as well as help grow the developer community. Our community edition of TopLink in GlassFish delivers core ORM persistence to those projects where the full licensed product is not required as well as providing these customers a seamless upgrade to the full solution when they wish to.
As this release comes out we will be updating our collateral and I will strive to ensure our continued leadership and investment in ORM functionality is reflected.
>
Thank you to product management make a factual answer
because I am a real customer, I am really in favour
of the product for 5 years. But I am really
disappointed when I see new small actors (KODO...)
much better doing?I hope you find this helpful. I would be more than happy to discuss this further. This does make it clear that we need to be more vocal and clear about our work as well as getting the 10.1.3 release out the door. I appreciate the feedback and will try to address these concerns directly.
Doug Clarke
Principal Product Manager
Oracle TopLink

JBOSS 3.2 & Kodo.rar

Hello all,
I have a problem with jboss 3.2 & Kodo JCA. I can't deploy this product .
exist any example the configuration file ?
Carlos.-

Carlos-
Check out:
http://solarmetric.com/Support/Newsgroups/news/article.php?id_article=%3Cpan.2003.05.06.17.40.54.720806%40solarmetric.com%3E&grp_id=1
If this isn't working for you, can you post any error messages you are
seeing?
In article <b9gddk$oe9$[email protected]>, Carlos Miranda wrote:
>
Hello all,
I have a problem with jboss 3.2 & Kodo JCA. I can't deploy this product .
exist any example the configuration file ?
Carlos.---
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Example of Kodo 3.0.0 running on Jboss 3.2.2

Has anyone gotten Kodo 3.0.0 to run on JBoss 3.2.2 using XA transactions?
If so, can anyone provide a sample with sample config files that got it to
work?
Everything I try is giving me errors. I've gone through the docs, tried to
set it up as described, but I still get errors about transaction problems.
If someone has already gotten it to work, it would be nice if I could see
a working example.
Thank you!
-joel

Joel-
I don't have an example handy, but if you post any errors you are
getting, we might be able to provide some hints as to where to look for
the problem.
A couple of tips:
1. Use the "oracle-xa-ds.xml" file (included in the JBoss distribution) as
a template for your Oracle datasource configuration.
2. Make sure the DataSourceMode property is set to "enlisted", as per:
http://docs.solarmetric.com/manual.html#ref_guide_dbsetup_thirdparty_enlist
In article <brkqql$mdd$[email protected]>, Joel Shellman wrote:
Has anyone gotten Kodo 3.0.0 to run on JBoss 3.2.2 using XA transactions?
If so, can anyone provide a sample with sample config files that got it to
work?
Everything I try is giving me errors. I've gone through the docs, tried to
set it up as described, but I still get errors about transaction problems.
If someone has already gotten it to work, it would be nice if I could see
a working example.
Thank you!
-joel--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Kodo 3.2.0RC1 Now Available

All,
Kodo 3.2.0RC1 is now available. Feel free to download it at:
http://www.solarmetric.com/jdo/Evaluate/
There are a number of exciting new features in 3.2.0RC1, as well as a number
of fixes to bugs found during the beta period:
* Many new JDO 2 preview features
* Single string JDOQL
* Named queries
* Optional managed inverses
* Improved eager fetching
* Many other new features and bugfixes
You can find the release notes at:
http://www.solarmetric.com/Software/Documentation/3.2.0RC1/docs/relnotes.html
As this is a release candidate, please report any issues that you find to
the Kodo
beta newsgroup (solarmetric.kodo.beta).
Good luck, and enjoy!
-Greg
SolarMetric
www.solarmetric.com

Using a class indicator will typically be faster. We added the
subclass-join capability largely to support legacy schemas that don't
have an indicator.
-Patrick
Alex Roytman wrote:
How would you compare performance of fetching vertically mapped class
hierarchy using subclass-join indicator (outer joins) vs traditional fetch
based on class indicator? I often seen poor performance with outer joins
especially if you have several of them and some inner joins as well. In some
cases UNION ALL worked much better
"Greg Campbell" <[email protected]> wrote in message
news:ch2tfg$mp2$[email protected]..
All,
Kodo 3.2.0RC1 is now available. Feel free to download it at:
http://www.solarmetric.com/jdo/Evaluate/
There are a number of exciting new features in 3.2.0RC1, as well as a
number
of fixes to bugs found during the beta period:
* Many new JDO 2 preview features
* Single string JDOQL
* Named queries
* Optional managed inverses
* Improved eager fetching
* Many other new features and bugfixes
You can find the release notes at:
http://www.solarmetric.com/Software/Documentation/3.2.0RC1/docs/relnotes.html
As this is a release candidate, please report any issues that you find to
the Kodo
beta newsgroup (solarmetric.kodo.beta).
Good luck, and enjoy!
-Greg
SolarMetric
www.solarmetric.com

Kodo 3.3.0RC1 Available

All,
Kodo 3.3.0RC1 is now available. Feel free to download it at:
http://solarmetric.com/jdo/beta/3.3.0RC1/
There are a number of exciting new features in 3.3.0RC1:
* New JDO 2 preview features, including Single Field Identity
* Finer grained control over timed cache invalidation
* Improvements to the Kodo workbench
* Support for Apache Derby
* Support for JMX 1.2
* Performance enhancements to the Remote PersistenceManager capability
* Many other new features and bugfixes
You can find the release notes at:
http://www.solarmetric.com/jdo/Documentation/3.3.0RC1/docs/relnotes.html
As this is a beta release, please report any issues that you find to the
Kodo beta newsgroup (solarmetric.kodo.beta).
Good luck, and enjoy!
-Greg
SolarMetric
www.solarmetric.com

Could you please elaborate on
"Added ability to insert raw SQL into a given kodo.jdbc.sql.Row. This is
useful for performing server side functions to generate values for custom
field mappings"
Would it allow to add a snippet of SQL to insert/update statement.
Specifically I am interested to set certain columns to null using NULL
literal rather then null parameter or call to setNull() in prepared
statement
ex: update employee set fname=?, lname=?, address = NULL where id=?
note how address = NULL sets address to null using NULL literal rather then
Is it possible to do now?
"Greg Campbell" <[email protected]> wrote in message
news:cvmiqb$vlv$[email protected]..
All,
Kodo 3.3.0RC1 is now available. Feel free to download it at:
http://solarmetric.com/jdo/beta/3.3.0RC1/
There are a number of exciting new features in 3.3.0RC1:
* New JDO 2 preview features, including Single Field Identity
* Finer grained control over timed cache invalidation
* Improvements to the Kodo workbench
* Support for Apache Derby
* Support for JMX 1.2
* Performance enhancements to the Remote PersistenceManager capability
* Many other new features and bugfixes
You can find the release notes at:
http://www.solarmetric.com/jdo/Documentation/3.3.0RC1/docs/relnotes.html
As this is a beta release, please report any issues that you find to the
Kodo beta newsgroup (solarmetric.kodo.beta).
Good luck, and enjoy!
-Greg
SolarMetric
www.solarmetric.com

Kodo on jboss-3.0.0RC1

Similar Messages

Maybe you are looking for