Nabble - OpenJPA Users

RE: Deployment

2009-07-04T08:55:15Z

Thanks Ravi,

I found that if I added my classes to the persistence.xml it all works fine
but I thought I didn't have to do that, or am I mistaken.

Regards

Chris

-----Original Message-----
From: Ravi Palacherla [mailto:ravi.palacherla@...]
Sent: Sunday, 5 July 2009 1:32 AM
To: users@...; cnd@...
Subject: RE: Deployment

Hi Chris,

There are two ways to enhance classes.

1) Build time enhancement

Here is a link for build time enhancement:

http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_pc
_enhance_build

Ant task for that is

http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_in
tegration_enhance

2) Run time enhancement.

http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_pc
_enhance_runtime

If you did build time enhancement then
Decompile your class file and see if the class implements PersistenceCapable
?

If it implements PersistenceCapable that means the class is enhanced.

Regards,
Ravi.

-----Original Message-----
From: C N Davies [mailto:cnd@...]
Sent: Saturday, July 04, 2009 3:49 AM
To: users@...
Subject: Deployment

I'm having an issue when running my application in that OpenJPA is
complaining my class has not been enhanced but the class looks fine to me,
can anyone see if I am missing something stupid please.

Here is the top of the stack trace:

<openjpa-1.2.0-r422266:683325 nonfatal user error>
org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance
"com.trm.core.Currency@cf3539" to PersistenceCapable failed. Ensure that it
has been enhanced.

FailedObject: com.trm.core.Currency@cf3539

<openjpa-1.2.0-r422266:683325 nonfatal user error>
org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance
"com.trm.core.Currency@cf3539" to PersistenceCapable failed. Ensure that it
has been enhanced.
FailedObject: com.trm.core.Currency@cf3539

I am wondering if is because of how I am using the objects. Basically the
code is loading some data from a file, depending on some configuration the
code will try to create the appropriate objects and then persist them. In
order to make the code abstract, the code loads the data then creates a
generic object and calls it setters to populate the data. Hence when the
EntityManager is called to persist the object it I am passing it a generic
object since I can't cast the object to the it's actual class at run time.
From the stack trace it seems that OpenJPA knows the correct class type so I
don't understand why it is complaining.

Here is my class:

@Entity

@Table(name="currency")

public class Currency implements Serializable

{

/**

*

*/

private static final long serialVersionUID = 1L;

@Id

// @GeneratedValue(strategy=GenerationType.AUTO)

private String isocode;

private String name;

private String country;

public Currency(){

}

/**

* @param isocode the isocode to set

*/

public void setIsocode(String isocode) {

this.isocode = isocode;

}

/**

* @return the isocode

*/

public String getIsocode() {

return isocode;

}

/**

* @param name the name to set

*/

public void setName(String name) {

this.name = name;

}

/**

* @return the name

*/

public String getName() {

return name;

}

/**

* @param country the country to set

*/

public void setCountry(String country) {

this.country = country;

}

/**

* @return the country

*/

public String getCountry() {

return country;

}

Thanks for any advice.

Chris

RE: Deployment

2009-07-04T08:32:08Z

Hi Chris,

There are two ways to enhance classes.

1) Build time enhancement

Here is a link for build time enhancement:
http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_pc_enhance_build

Ant task for that is
http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_integration_enhance

2) Run time enhancement.
http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_pc_enhance_runtime

If you did build time enhancement then
Decompile your class file and see if the class implements PersistenceCapable ?

If it implements PersistenceCapable that means the class is enhanced.

Regards,
Ravi.

-----Original Message-----
From: C N Davies [mailto:cnd@...]
Sent: Saturday, July 04, 2009 3:49 AM
To: users@...
Subject: Deployment

I'm having an issue when running my application in that OpenJPA is
complaining my class has not been enhanced but the class looks fine to me,
can anyone see if I am missing something stupid please.

Here is the top of the stack trace:

<openjpa-1.2.0-r422266:683325 nonfatal user error>
org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance
"com.trm.core.Currency@cf3539" to PersistenceCapable failed. Ensure that it
has been enhanced.

FailedObject: com.trm.core.Currency@cf3539

<openjpa-1.2.0-r422266:683325 nonfatal user error>
org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance
"com.trm.core.Currency@cf3539" to PersistenceCapable failed. Ensure that it
has been enhanced.
FailedObject: com.trm.core.Currency@cf3539

I am wondering if is because of how I am using the objects. Basically the
code is loading some data from a file, depending on some configuration the
code will try to create the appropriate objects and then persist them. In
order to make the code abstract, the code loads the data then creates a
generic object and calls it setters to populate the data. Hence when the
EntityManager is called to persist the object it I am passing it a generic
object since I can't cast the object to the it's actual class at run time.
From the stack trace it seems that OpenJPA knows the correct class type so I
don't understand why it is complaining.

Here is my class:

@Entity

@Table(name="currency")

public class Currency implements Serializable

{

/**

*

*/

private static final long serialVersionUID = 1L;

@Id

// @GeneratedValue(strategy=GenerationType.AUTO)

private String isocode;

private String name;

private String country;

public Currency(){

}

/**

* @param isocode the isocode to set

*/

public void setIsocode(String isocode) {

this.isocode = isocode;

}

/**

* @return the isocode

*/

public String getIsocode() {

return isocode;

}

/**

* @param name the name to set

*/

public void setName(String name) {

this.name = name;

}

/**

* @return the name

*/

public String getName() {

return name;

}

/**

* @param country the country to set

*/

public void setCountry(String country) {

this.country = country;

}

/**

* @return the country

*/

public String getCountry() {

return country;

}

Thanks for any advice.

Chris

Deployment

2009-07-04T02:48:58Z

I'm having an issue when running my application in that OpenJPA is
complaining my class has not been enhanced but the class looks fine to me,
can anyone see if I am missing something stupid please.

Here is the top of the stack trace:

<openjpa-1.2.0-r422266:683325 nonfatal user error>
org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance
"com.trm.core.Currency@cf3539" to PersistenceCapable failed. Ensure that it
has been enhanced.

FailedObject: com.trm.core.Currency@cf3539

<openjpa-1.2.0-r422266:683325 nonfatal user error>
org.apache.openjpa.persistence.ArgumentException: Attempt to cast instance
"com.trm.core.Currency@cf3539" to PersistenceCapable failed. Ensure that it
has been enhanced.
FailedObject: com.trm.core.Currency@cf3539

I am wondering if is because of how I am using the objects. Basically the
code is loading some data from a file, depending on some configuration the
code will try to create the appropriate objects and then persist them. In
order to make the code abstract, the code loads the data then creates a
generic object and calls it setters to populate the data. Hence when the
EntityManager is called to persist the object it I am passing it a generic
object since I can't cast the object to the it's actual class at run time.
From the stack trace it seems that OpenJPA knows the correct class type so I
don't understand why it is complaining.

Here is my class:

@Entity

@Table(name="currency")

public class Currency implements Serializable

{

/**

*

*/

private static final long serialVersionUID = 1L;

@Id

// @GeneratedValue(strategy=GenerationType.AUTO)

private String isocode;

private String name;

private String country;

public Currency(){

}

/**

* @param isocode the isocode to set

*/

public void setIsocode(String isocode) {

this.isocode = isocode;

}

/**

* @return the isocode

*/

public String getIsocode() {

return isocode;

}

/**

* @param name the name to set

*/

public void setName(String name) {

this.name = name;

}

/**

* @return the name

*/

public String getName() {

return name;

}

/**

* @param country the country to set

*/

public void setCountry(String country) {

this.country = country;

}

/**

* @return the country

*/

public String getCountry() {

return country;

}

Thanks for any advice.

Chris

Re: PostgreSQL inet or cidr data types

2009-07-04T10:14:36Z

On Fri, Jul 3, 2009 at 8:56 PM, Vasil <vvangelovski@...> wrote:

>
> But that fails when the DDL executes because it tries to give it a length
> in
> the column definition:
> address cidr(255) NOT NULL
>

I don't know if this will help but you could try setting the length to -1.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@...

PostgreSQL inet or cidr data types

2009-07-03T17:56:00Z

Is there a way to use postgres' inet or cidr data types with openjpa?
I've tried the obvious:

@Column( nullable=false, columnDefinition="cidr" )
private String address;

But that fails when the DDL executes because it tries to give it a length in the column definition:
address cidr(255) NOT NULL

RE: Auto Generate table

2009-07-03T13:57:20Z

Hi Chris,

Can you please try to run mapping tool against your entities.

Here is more info about mapping tool:

http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_mapping_mappingtool_examples

Info on Ant task for mapping tool :
http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_integration_mappingtool

Regards,
Ravi.

-----Original Message-----
From: C N Davies [mailto:cnd@...]
Sent: Friday, July 03, 2009 1:37 PM
To: Judes Tumuhairwe; users@...
Subject: RE: Auto Generate table

Thanks Judes.

I already have:

<property name="openjpa.jdbc.SynchronizeMappings"
value="buildSchema(ForeignKeys=true)"/>

Bizarre.

Chris

From: Judes Tumuhairwe [mailto:judethecutedude@...]
Sent: Saturday, 4 July 2009 5:32 AM
To: users@...; cnd@...
Subject: Re: Auto Generate table

See [1] for a complete example. But in short, you need to add the following
property to your persistence.xml properties

<property name="openjpa.jdbc.SynchronizeMappings"
value="buildSchema(ForeignKeys=true)"/>

[1] http://plunchete.wordpress.com/2007/05/06/using-openjpa/

-Judes

On Fri, Jul 3, 2009 at 6:16 AM, C N Davies <cnd@...> wrote:

Hi,

What do I need to set to have tables automatically generated by OpenJPA?

Thanks

Chris

RE: Auto Generate table

2009-07-03T12:36:54Z

Thanks Judes.

I already have:

<property name="openjpa.jdbc.SynchronizeMappings"
value="buildSchema(ForeignKeys=true)"/>

Bizarre.

Chris

From: Judes Tumuhairwe [mailto:judethecutedude@...]
Sent: Saturday, 4 July 2009 5:32 AM
To: users@...; cnd@...
Subject: Re: Auto Generate table

See [1] for a complete example. But in short, you need to add the following
property to your persistence.xml properties

<property name="openjpa.jdbc.SynchronizeMappings"
value="buildSchema(ForeignKeys=true)"/>

[1] http://plunchete.wordpress.com/2007/05/06/using-openjpa/

-Judes

On Fri, Jul 3, 2009 at 6:16 AM, C N Davies <cnd@...> wrote:

Hi,

What do I need to set to have tables automatically generated by OpenJPA?

Thanks

Chris

Re: Auto Generate table

2009-07-03T12:31:52Z

See [1] for a complete example. But in short, you need to add the following
property to your persistence.xml properties

<property name="openjpa.jdbc.SynchronizeMappings" value="buildSchema"/>

[1] http://plunchete.wordpress.com/2007/05/06/using-openjpa/

-Judes

On Fri, Jul 3, 2009 at 6:16 AM, C N Davies <cnd@...> wrote:

> Hi,
>
>
>
> What do I need to set to have tables automatically generated by OpenJPA?
>
>
>
> Thanks
>
>
>
> Chris
>
>

Auto Generate table

2009-07-03T06:16:39Z

Hi,

What do I need to set to have tables automatically generated by OpenJPA?

Thanks

Chris

Webapp restart problem

2009-07-02T10:33:41Z

Hey all, when I (re)deploy my application to Tomcat (using the manager app
to stop/start the app) it fails with this exception:

Caused by: <openjpa-1.2.1-r752877:753278 nonfatal general error>
org.apache.openjpa.util.GeneralException: JAR entry META-INF/persistence.xml
not found in /opt/tomcat/webapps/myapp/WEB-INF/lib/app.jar
at sun.net.www.protocol.jar.JarURLConnection.connect(Unknown Source)
at sun.net.www.protocol.jar.JarURLConnection.getInputStream(Unknown
Source)
at java.net.URL.openStream(Unknown Source)
at
org.apache.openjpa.lib.util.J2DoPrivHelper$39.run(J2DoPrivHelper.java:826)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.openjpa.lib.meta.URLMetaDataIterator.getInputStream(URLMetaDataIterator.java:67)
at
org.apache.openjpa.lib.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:318)
at
org.apache.openjpa.lib.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:295)
at
org.apache.openjpa.lib.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:268)
at
org.apache.openjpa.persistence.PersistenceProductDerivation$ConfigurationParser.parse(PersistenceProductDerivation.java:509)
at
org.apache.openjpa.persistence.PersistenceProductDerivation.parseResources(PersistenceProductDerivation.java:359)
at
org.apache.openjpa.persistence.PersistenceProductDerivation.load(PersistenceProductDerivation.java:326)
at
org.apache.openjpa.persistence.PersistenceProductDerivation.load(PersistenceProductDerivation.java:161)
at
org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:77)
at
org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:109)
at
org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:53)
at javax.persistence.Persistence.createFactory(Persistence.java:171)
... 33 more

A complete restart of Tomcat fixes the problem and it starts fine, so the
persistence.xml file is there. Anyone seen this sort of thing?

Thanks.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@...

UserException: You did not name the factory class with the required property openjpa.BrokerFactory

2009-07-02T01:09:59Z

Dear all,

I face a problem when I try to make a flat executable JAR of an application that uses OpenJPA.
My configuration files work perfectly on an application server

It seams that some JAR are missing but in my pom.xml I specifie the following dependencies:

<dependency>
<groupId>org.apache.openjpa</groupId>
<artifactId>openjpa-persistence</artifactId>
<version>1.2.1</version>
</dependency>
<dependency>
<groupId>org.apache.openjpa</groupId>
<artifactId>openjpa-persistence-jdbc</artifactId>
<version>1.2.1</version>
<scope>runtime</scope>
</dependency>

Do you have any idea of what is the problem?

Thanks for your help,

Nicolas

Here stands the stack trace.

Exception in thread "main" org.springframework.beans.factory.BeanCreationExcepti
on: Error creating bean with name 'prmGeneratedProcessesDao': Injection of persi
stence methods failed; nested exception is org.springframework.beans.factory.Bea
nCreationException: Error creating bean with name 'gpEntityManagerFactory' defin
ed in class path resource [daoContext.xml]: Invocation of init method failed; ne
sted exception is <openjpa-1.2.1-r752877:753278 fatal user error> org.apache.ope
njpa.persistence.ArgumentException: Could not invoke the static newInstance meth
od on the named factory class "<<openjpa-1.2.1-r752877:753278 fatal user error>
org.apache.openjpa.util.UserException: You did not name the factory class with t
he required property openjpa.BrokerFactory. Normally this property defaults app
ropriately; have you forgotten to include all the OpenJPA jars in your classpath
?>".
at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc
essor.postProcessPropertyValues(PersistenceAnnotationBeanPostProcessor.java:324)

at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.populateBean(AbstractAutowireCapableBeanFactory.java:998)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:472)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getOb
ject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr
y.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe
an(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.
preInstantiateSingletons(DefaultListableBeanFactory.java:429)
at org.springframework.context.support.AbstractApplicationContext.finish
BeanFactoryInitialization(AbstractApplicationContext.java:728)
at org.springframework.context.support.AbstractApplicationContext.refres
h(AbstractApplicationContext.java:380)
at org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139)
at org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83)
at com.caceis.tacos.computations.Main.startLimitsJob(Main.java:70)
at com.caceis.tacos.computations.Main.main(Main.java:51)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creati
ng bean with name 'gpEntityManagerFactory' defined in class path resource [daoCo
ntext.xml]: Invocation of init method failed; nested exception is <openjpa-1.2.1
-r752877:753278 fatal user error> org.apache.openjpa.persistence.ArgumentExcepti
on: Could not invoke the static newInstance method on the named factory class "<
<openjpa-1.2.1-r752877:753278 fatal user error> org.apache.openjpa.util.UserExce
ption: You did not name the factory class with the required property openjpa.Bro
kerFactory. Normally this property defaults appropriately; have you forgotten t
o include all the OpenJPA jars in your classpath?>".
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.initializeBean(AbstractAutowireCapableBeanFactory.java:1338)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getOb
ject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr
y.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe
an(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:164)
at org.springframework.orm.jpa.EntityManagerFactoryUtils.findEntityManag
erFactory(EntityManagerFactoryUtils.java:99)
at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc
essor.findNamedEntityManagerFactory(PersistenceAnnotationBeanPostProcessor.java:
488)
at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc
essor.findEntityManagerFactory(PersistenceAnnotationBeanPostProcessor.java:470)
at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc
essor$PersistenceElement.resolveEntityManager(PersistenceAnnotationBeanPostProce
ssor.java:599)
at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc
essor$PersistenceElement.getResourceToInject(PersistenceAnnotationBeanPostProces
sor.java:570)
at org.springframework.beans.factory.annotation.InjectionMetadata$Inject
edElement.inject(InjectionMetadata.java:192)
at org.springframework.beans.factory.annotation.InjectionMetadata.inject
Methods(InjectionMetadata.java:117)
at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc
essor.postProcessPropertyValues(PersistenceAnnotationBeanPostProcessor.java:321)

... 17 more
Caused by: <openjpa-1.2.1-r752877:753278 fatal user error> org.apache.openjpa.pe
rsistence.ArgumentException: Could not invoke the static newInstance method on t
he named factory class "<<openjpa-1.2.1-r752877:753278 fatal user error> org.apa
che.openjpa.util.UserException: You did not name the factory class with the requ
ired property openjpa.BrokerFactory. Normally this property defaults appropriat
ely; have you forgotten to include all the OpenJPA jars in your classpath?>".
at org.apache.openjpa.kernel.Bootstrap.newBrokerFactory(Bootstrap.java:7
0)
at org.apache.openjpa.persistence.PersistenceProviderImpl.getBrokerFacto
ry(PersistenceProviderImpl.java:102)
at org.apache.openjpa.persistence.PersistenceProviderImpl.createContaine
rEntityManagerFactory(PersistenceProviderImpl.java:142)
at org.apache.openjpa.persistence.PersistenceProviderImpl.createContaine
rEntityManagerFactory(PersistenceProviderImpl.java:53)
at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.cr
eateNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:224)
at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPro
pertiesSet(AbstractEntityManagerFactoryBean.java:291)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1369)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
... 34 more
Caused by: <openjpa-1.2.1-r752877:753278 fatal user error> org.apache.openjpa.pe
rsistence.ArgumentException: You did not name the factory class with the require
d property openjpa.BrokerFactory. Normally this property defaults appropriately
; have you forgotten to include all the OpenJPA jars in your classpath?
at org.apache.openjpa.kernel.Bootstrap.getFactoryClass(Bootstrap.java:15
3)
at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:111)

at org.apache.openjpa.kernel.Bootstrap.newBrokerFactory(Bootstrap.java:6
2)
... 41 more

UserException: You did not name the factory class with the required property openjpa.BrokerFactory

2009-07-02T01:09:15Z
Dear all, I face a problem when I try to make a flat executable JAR of an application that uses OpenJPA. My configuration files work perfectly on an application server It seams that some JAR are missing but in my pom.xml I specifie the following dependencies: org.apache.openjpa openjpa-persistence 1.2.1 org.apache.openjpa openjpa-persistence-jdbc 1.2.1 runtime Do you have any idea of what is the problem? Thanks for your help, Nicolas Here stands the stack trace. Exception in thread "main" org.springframework.beans.factory.BeanCreationExcepti on: Error creating bean with name 'prmGeneratedProcessesDao': Injection of persi stence methods failed; nested exception is org.springframework.beans.factory.Bea nCreationException: Error creating bean with name 'gpEntityManagerFactory' defin ed in class path resource [daoContext.xml]: Invocation of init method failed; ne sted exception is org.apache.ope njpa.persistence.ArgumentException: Could not invoke the static newInstance meth od on the named factory class "< org.apache.openjpa.util.UserException: You did not name the factory class with t he required property openjpa.BrokerFactory. Normally this property defaults app ropriately; have you forgotten to include all the OpenJPA jars in your classpath ?>". at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc essor.postProcessPropertyValues(PersistenceAnnotationBeanPostProcessor.java:324) at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory.populateBean(AbstractAutowireCapableBeanFactory.java:998) at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:472) at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory$1.run(AbstractAutowireCapableBeanFactory.java:409) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory.createBean(AbstractAutowireCapableBeanFactory.java:380) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getOb ject(AbstractBeanFactory.java:264) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr y.getSingleton(DefaultSingletonBeanRegistry.java:222) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe an(AbstractBeanFactory.java:261) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean (AbstractBeanFactory.java:185) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean (AbstractBeanFactory.java:164) at org.springframework.beans.factory.support.DefaultListableBeanFactory. preInstantiateSingletons(DefaultListableBeanFactory.java:429) at org.springframework.context.support.AbstractApplicationContext.finish BeanFactoryInitialization(AbstractApplicationContext.java:728) at org.springframework.context.support.AbstractApplicationContext.refres h(AbstractApplicationContext.java:380) at org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139) at org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:83) at com.caceis.tacos.computations.Main.startLimitsJob(Main.java:70) at com.caceis.tacos.computations.Main.main(Main.java:51) Caused by: org.springframework.beans.factory.BeanCreationException: Error creati ng bean with name 'gpEntityManagerFactory' defined in class path resource [daoCo ntext.xml]: Invocation of init method failed; nested exception is org.apache.openjpa.persistence.ArgumentExcepti on: Could not invoke the static newInstance method on the named factory class "< org.apache.openjpa.util.UserExce ption: You did not name the factory class with the required property openjpa.Bro kerFactory. Normally this property defaults appropriately; have you forgotten t o include all the OpenJPA jars in your classpath?>". at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory.initializeBean(AbstractAutowireCapableBeanFactory.java:1338) at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473) at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory$1.run(AbstractAutowireCapableBeanFactory.java:409) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory.createBean(AbstractAutowireCapableBeanFactory.java:380) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getOb ject(AbstractBeanFactory.java:264) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistr y.getSingleton(DefaultSingletonBeanRegistry.java:222) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBe an(AbstractBeanFactory.java:261) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean (AbstractBeanFactory.java:185) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean (AbstractBeanFactory.java:164) at org.springframework.orm.jpa.EntityManagerFactoryUtils.findEntityManag erFactory(EntityManagerFactoryUtils.java:99) at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc essor.findNamedEntityManagerFactory(PersistenceAnnotationBeanPostProcessor.java: 488) at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc essor.findEntityManagerFactory(PersistenceAnnotationBeanPostProcessor.java:470) at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc essor$PersistenceElement.resolveEntityManager(PersistenceAnnotationBeanPostProce ssor.java:599) at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc essor$PersistenceElement.getResourceToInject(PersistenceAnnotationBeanPostProces sor.java:570) at org.springframework.beans.factory.annotation.InjectionMetadata$Inject edElement.inject(InjectionMetadata.java:192) at org.springframework.beans.factory.annotation.InjectionMetadata.inject Methods(InjectionMetadata.java:117) at org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProc essor.postProcessPropertyValues(PersistenceAnnotationBeanPostProcessor.java:321) ... 17 more Caused by: org.apache.openjpa.pe rsistence.ArgumentException: Could not invoke the static newInstance method on t he named factory class "< org.apa che.openjpa.util.UserException: You did not name the factory class with the requ ired property openjpa.BrokerFactory. Normally this property defaults appropriat ely; have you forgotten to include all the OpenJPA jars in your classpath?>". at org.apache.openjpa.kernel.Bootstrap.newBrokerFactory(Bootstrap.java:7 0) at org.apache.openjpa.persistence.PersistenceProviderImpl.getBrokerFacto ry(PersistenceProviderImpl.java:102) at org.apache.openjpa.persistence.PersistenceProviderImpl.createContaine rEntityManagerFactory(PersistenceProviderImpl.java:142) at org.apache.openjpa.persistence.PersistenceProviderImpl.createContaine rEntityManagerFactory(PersistenceProviderImpl.java:53) at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.cr eateNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:224) at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPro pertiesSet(AbstractEntityManagerFactoryBean.java:291) at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1369) at org.springframework.beans.factory.support.AbstractAutowireCapableBean Factory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335) ... 34 more Caused by: org.apache.openjpa.pe rsistence.ArgumentException: You did not name the factory class with the require d property openjpa.BrokerFactory. Normally this property defaults appropriately ; have you forgotten to include all the OpenJPA jars in your classpath? at org.apache.openjpa.kernel.Bootstrap.getFactoryClass(Bootstrap.java:15 3) at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:111) at org.apache.openjpa.kernel.Bootstrap.newBrokerFactory(Bootstrap.java:6 2) ... 41 more

Cascade deletion problem

2009-07-01T16:48:26Z
While doing an orphan deletion, does the DB Foreign key constraint on delete, causes Optimistic locking exception in OpenJPA? If this is correct, can somebody help us out with the solution? Any help is highly appreciated.

Thanks,
JP

Detached state causing illegal state exception

2009-07-01T16:44:18Z
Hi,

We have added a detached state configuration in the persistence.xml to update empty fields as well. It works file for all the domains except one. The configuration is same across domains and the only change we can see is at the DAO level. The DAO for the domain which we using does not have an annotation @Repository where in all the other DAOs have this.

If this is not the cause, can somebody help us with the problem? since this is causing whole app to fail.

Thanks,
JP

Re: did pass params - Attempt to insert null into a non-nullable column

2009-07-01T14:19:10Z
Thanks for the quick reply, Rick.

Eventually I found out it was about the datasource config:

in such case(using Tomcat), the my.war/WEB-INF/classes/META-INF/persistence.xml
1. should not specify any database info but the datasource id (specified in /tomcat/conf/openejb.xml), as
<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
<jta-data-source>contextDS</jta-data-source>

if specifying the database info, like
<property name="openjpa.ConnectionURL"
value="jdbc:mysql://localhost:3306/ejb"/>
<property name="openjpa.ConnectionDriverName"
...
then the following error found:

<openjpa-1.2.1-r752877:753278 fatal user error> org.apache.openjpa.persistence.ArgumentException: A connection could not be obtained for driver class "com.mysql.jdbc.Driver" and URL "jdbc:mysql://localhost:3306/ejb". You may have specified an invalid URL.
org.apache.openjpa.jdbc.schema.DataSourceFactory.newConnectException(DataSourceFactory.java:256)
org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(DataSourceFactory.java:242)
org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:692)
org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:790)
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.setContext(JDBCStoreManager.java:136)
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.setContext(JDBCStoreManager.java:120)
org.apache.openjpa.kernel.DelegatingStoreManager.setContext(DelegatingStoreManager.java:78)
org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:309)
org.apache.openjpa.kernel.AbstractBrokerFactory.initializeBroker(AbstractBrokerFactory.java:216)
org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:190)
org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:142)
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:192)
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:56)
org.apache.openejb.persistence.JtaEntityManagerRegistry.getEntityManager(JtaEntityManagerRegistry.java:105)
org.apache.openejb.persistence.JtaEntityManager.getEntityManager(JtaEntityManager.java:61)
org.apache.openejb.persistence.JtaEntityManager.persist(JtaEntityManager.java:97)
...

2. create and place up openejb.xml and open-ejb-jar.xml in the same METTA-INF folder, companied with persistence.xml, then the created entity bean and its data can be found/accessed in run time (in debug), but it's not persisted in database.

openejb-jar.xml
<dep:environment>
<dep:moduleId>
<dep:groupId>myEJB</dep:groupId>
<dep:artifactId>EJB</dep:artifactId>
<dep:version>2.0</dep:version>
<dep:type>car</dep:type>
</dep:moduleId>
</dep:environment>
<name:cmp-connection-factory>
<name:pattern>
<name:groupId>console.myTX</name:groupId>
<name:artifactId>myTX</name:artifactId>
</name:pattern>
</name:cmp-connection-factory>

data info in openejb.xml as:
<Resource id="myTX" type="DataSource">
JdbcDriver com.mysql.jdbc.Driver
...
</Resource>
<Resource id="myNOTX" type="DataSource">
JdbcDriver com.mysql.jdbc.Driver
....
</Resource>

the persistence.xml:
<persistence-unit name="aUnit" >
<jta-data-source>myTX</jta-data-source>
<non-jta-data-source>myNOTX</non-jta-data-source>
...

so, my question became, how to specify the datasource out of /tomcat/conf/?

Thanks in advance.

--
John

Rick Curtis wrote:

John -

It looks like you annotated your Person.id to be unique, but you didn't
specify a value... I'm assuming that you're using an AI column for your id.
I see you're running on MySQL, so try adding the annotation
@GeneratedValue(strategy=GenerationType.IDENTITY) to your id column. If that
doesn't work, please post a snippet of your Entity/mapping file(s).

-Rick

On Wed, Jul 1, 2009 at 12:44 PM, John_canada <john_woo@canada.com> wrote:

>
> Hi,
>
> I deployed openejb.war in tomcat, and tested a web app which used ejb3;
> it's
> very simple: a servlet called a stateless bean, which created an entity as
> following:
>
> session bean:
> @PersistenceContext(unitName="aUnit",type =
> PersistenceContextType.TRANSACTION)
> private EntityManager manager;
>
> Person p = new Person(name, address);
> manager.persist(p);
> manager.flush();
>
> the persistence.xml:
> <persistence-unit name="aUnit" transaction-type="JTA">
>
> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
> <jta-data-source>myTX</jta-data-source>
> <non-jta-data-source>myNOTX</non-jta-data-source>
> <class>ejb.Person</class>
> ...
>
> openejb.xml:
> <Resource id="myTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> JdbcUrl jdbc:mysql://localhost:3306/a
> UserName root
> Password aaa
> </Resource>
>
> <Resource id="myNOTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> JdbcUrl jdbc:mysql://localhost:3306/a
> UserName root
> Password aaa
> JtaManaged false
> </Resource>
>
> However, I got the following error when executing manager.flush();
> org.apache.openjpa.lib.jdbc.ReportingSQLException: Attempt to insert null
> into a non-nullable column: column: ID table: PERSON in statement [INSERT
> INTO person (person_id, address, name) VALUES (?, ?, ?)] {prepstmnt 6240623
> INSERT INTO person (person_id, address, name)
> VALUES (?, ?, ?)
> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> state=23000]
>
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:192)
>
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:57)
>
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:866)
>
>
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1504)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:151)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:120)
>
>
> org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingPreparedStatementManagerImpl.java:82)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:89)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:72)
>
>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:543)
>
>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:105)
>
>
> org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:59)
>
>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89)
>
>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:655)
>
>
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010)
> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908)
> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1679)
>
> org.apache.openjpa.kernel.DelegatingBroker.flush(DelegatingBroker.java:989)
>
>
> org.apache.openjpa.persistence.EntityManagerImpl.flush(EntityManagerImpl.java:592)
>
>
> org.apache.openejb.persistence.JtaEntityManager.flush(JtaEntityManager.java:130)
> ejb.HelloBean.createPerson(HelloBean.java:31)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:597)
>
>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158)
>
>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141)
>
>
> org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:122)
>
>
> org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:221)
>
>
> org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:174)
>
>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217)
>
>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77)
>
>
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:281)
> $Proxy46.createPerson(Unknown Source)
> test.HelloServlet.doGet(HelloServlet.java:31)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>
>
> It's obvious, from
> INSERT INTO person (person_id, address, name)
> VALUES (?, ?, ?)
> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> state=23000]
>
> the parms values were taken, but did not pass/forward to database - this
> should not be in ejb3 package.
>
> Can anyone tell how to fix it?
>
> Thanks
> --
> John
> --
> View this message in context:
> http://n2.nabble.com/did-pass-params---Attempt-to-insert-null-into-a-non-nullable-column-tp3190581p3190581.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>

Re: did pass params - Attempt to insert null into a non-nullable column

2009-07-01T14:18:25Z
Thanks for the quick reply, Rick.

Eventually I found out it was about the datasource config:

in such case(using Tomcat), the my.war/WEB-INF/classes/META-INF/persistence.xml
1. should not specify any database info but the datasource id (specified in /tomcat/conf/openejb.xml), as
<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
<jta-data-source>contextDS</jta-data-source>

if specifying the database info, like
<property name="openjpa.ConnectionURL"
value="jdbc:mysql://localhost:3306/ejb"/>
<property name="openjpa.ConnectionDriverName"
...
then the following error found:

<openjpa-1.2.1-r752877:753278 fatal user error> org.apache.openjpa.persistence.ArgumentException: A connection could not be obtained for driver class "com.mysql.jdbc.Driver" and URL "jdbc:mysql://localhost:3306/ejb". You may have specified an invalid URL.
org.apache.openjpa.jdbc.schema.DataSourceFactory.newConnectException(DataSourceFactory.java:256)
org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(DataSourceFactory.java:242)
org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:692)
org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:790)
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.setContext(JDBCStoreManager.java:136)
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.setContext(JDBCStoreManager.java:120)
org.apache.openjpa.kernel.DelegatingStoreManager.setContext(DelegatingStoreManager.java:78)
org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:309)
org.apache.openjpa.kernel.AbstractBrokerFactory.initializeBroker(AbstractBrokerFactory.java:216)
org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:190)
org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:142)
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:192)
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:56)
org.apache.openejb.persistence.JtaEntityManagerRegistry.getEntityManager(JtaEntityManagerRegistry.java:105)
org.apache.openejb.persistence.JtaEntityManager.getEntityManager(JtaEntityManager.java:61)
org.apache.openejb.persistence.JtaEntityManager.persist(JtaEntityManager.java:97)
...

2. create and place up openejb.xml and open-ejb-jar.xml in the same METTA-INF folder, companied with persistence.xml, then the created entity bean and its data can be found/accessed in run time (in debug), but it's not persisted in database.

openejb-jar.xml
<dep:environment>
<dep:moduleId>
<dep:groupId>myEJB</dep:groupId>
<dep:artifactId>EJB</dep:artifactId>
<dep:version>2.0</dep:version>
<dep:type>car</dep:type>
</dep:moduleId>
</dep:environment>
<name:cmp-connection-factory>
<name:pattern>
<name:groupId>console.myTX</name:groupId>
<name:artifactId>myTX</name:artifactId>
</name:pattern>
</name:cmp-connection-factory>

data info in openejb.xml as:
<Resource id="myTX" type="DataSource">
JdbcDriver com.mysql.jdbc.Driver
...
</Resource>
<Resource id="myNOTX" type="DataSource">
JdbcDriver com.mysql.jdbc.Driver
....
</Resource>

the persistence.xml:
<persistence-unit name="aUnit" >
<jta-data-source>myTX</jta-data-source>
<non-jta-data-source>myNOTX</non-jta-data-source>
...

so, my question became, how to specify the datasource out of /tomcat/conf/?

Thanks in advance.

--
John

Rick Curtis wrote:

John -

It looks like you annotated your Person.id to be unique, but you didn't
specify a value... I'm assuming that you're using an AI column for your id.
I see you're running on MySQL, so try adding the annotation
@GeneratedValue(strategy=GenerationType.IDENTITY) to your id column. If that
doesn't work, please post a snippet of your Entity/mapping file(s).

-Rick

On Wed, Jul 1, 2009 at 12:44 PM, John_canada <john_woo@canada.com> wrote:

>
> Hi,
>
> I deployed openejb.war in tomcat, and tested a web app which used ejb3;
> it's
> very simple: a servlet called a stateless bean, which created an entity as
> following:
>
> session bean:
> @PersistenceContext(unitName="aUnit",type =
> PersistenceContextType.TRANSACTION)
> private EntityManager manager;
>
> Person p = new Person(name, address);
> manager.persist(p);
> manager.flush();
>
> the persistence.xml:
> <persistence-unit name="aUnit" transaction-type="JTA">
>
> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
> <jta-data-source>myTX</jta-data-source>
> <non-jta-data-source>myNOTX</non-jta-data-source>
> <class>ejb.Person</class>
> ...
>
> openejb.xml:
> <Resource id="myTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> JdbcUrl jdbc:mysql://localhost:3306/a
> UserName root
> Password aaa
> </Resource>
>
> <Resource id="myNOTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> JdbcUrl jdbc:mysql://localhost:3306/a
> UserName root
> Password aaa
> JtaManaged false
> </Resource>
>
> However, I got the following error when executing manager.flush();
> org.apache.openjpa.lib.jdbc.ReportingSQLException: Attempt to insert null
> into a non-nullable column: column: ID table: PERSON in statement [INSERT
> INTO person (person_id, address, name) VALUES (?, ?, ?)] {prepstmnt 6240623
> INSERT INTO person (person_id, address, name)
> VALUES (?, ?, ?)
> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> state=23000]
>
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:192)
>
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:57)
>
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:866)
>
>
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1504)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:151)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:120)
>
>
> org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingPreparedStatementManagerImpl.java:82)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:89)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:72)
>
>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:543)
>
>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:105)
>
>
> org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:59)
>
>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89)
>
>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:655)
>
>
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010)
> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908)
> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1679)
>
> org.apache.openjpa.kernel.DelegatingBroker.flush(DelegatingBroker.java:989)
>
>
> org.apache.openjpa.persistence.EntityManagerImpl.flush(EntityManagerImpl.java:592)
>
>
> org.apache.openejb.persistence.JtaEntityManager.flush(JtaEntityManager.java:130)
> ejb.HelloBean.createPerson(HelloBean.java:31)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:597)
>
>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158)
>
>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141)
>
>
> org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:122)
>
>
> org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:221)
>
>
> org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:174)
>
>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217)
>
>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77)
>
>
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:281)
> $Proxy46.createPerson(Unknown Source)
> test.HelloServlet.doGet(HelloServlet.java:31)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>
>
> It's obvious, from
> INSERT INTO person (person_id, address, name)
> VALUES (?, ?, ?)
> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> state=23000]
>
> the parms values were taken, but did not pass/forward to database - this
> should not be in ejb3 package.
>
> Can anyone tell how to fix it?
>
> Thanks
> --
> John
> --
> View this message in context:
> http://n2.nabble.com/did-pass-params---Attempt-to-insert-null-into-a-non-nullable-column-tp3190581p3190581.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>

Re: did pass params - Attempt to insert null into a non-nullable column

2009-07-03T04:30:00Z
All,

I came across to get the solution, as following:

1. for J2EE env, the persistence must use JNDI;
2. the openejb.xml, must use tag <connection> instead of Resource.

Hope this can be helpful when using openejb over openjpa.

--
John

John_canada wrote:

Thanks lots Mike.

Actually what I wanted was to simply specify a connection in persistence.xml, if can not, then specifying in openejb-jar.xml (or openejb.xml, in same META-INF folder).

the pesistence.xml as
<persistence-unit name="aUnit" >
<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>

<class>ejb.Person</class>
<properties>
<property name="openjpa.ConnectionURL" value="jdbc:mysql://localhost:3306/aa"/>
<property name="openjpa.ConnectionDriverName" value="com.mysql.jdbc.Driver"/>
<property name="openjpa.ConnectionUserName" value="root"/>
<property name="openjpa.ConnectionPassword" value="pass"/>
<property name="openjpa.Log" value="DefaultLevel=INFO, SQL=TRACE"/>
...

The db info is correct (tested in dos command prompt). however, it when trying to connect via calling entity bean, I still got:
javax.ejb.EJBException: The bean encountered a non-application exception; nested exception is:
<openjpa-1.2.1-r752877:753278 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: There were errors initializing your configuration: <openjpa-1.2.1-r752877:753278 fatal user error> org.apache.openjpa.util.UserException: A connection could not be obtained for driver class "com.mysql.jdbc.Driver" and URL "jdbc:mysql://localhost:3306/aa". You may have specified an invalid URL.
at org.apache.openjpa.jdbc.schema.DataSourceFactory.newConnectException(DataSourceFactory.java:256)
at org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(DataSourceFactory.java:242)
at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:692)
...

Was this (connection issue) in jpa package or in ejb package?

--
John

Michael Dick wrote:

At least some of this will be better handled by the OpenEJB / Tomcat folks
and we can certainly cross post the question on their mailing list(s) if
needed.

From an OpenJPA point of view you should be able to specify the connection
properties (openjpa.ConnectionURL, openjpa.ConnectionDriverName, etc.) or
use a jta-data-source in persistence.xml. If you use a jta-data-source then
the only requirement is that the value you provide (ie contextDS) is
available in JNDI. Usually a datasource will be bound to a location like
jdbc/${my datasource name} (coming from a WebSphere background, but I
believe this is fairly common), Tomcat might expect a similar context root -
would have to check Tomcat's doc to be sure.

The error you're getting can indicate a lot of things though :
1. The ConnectionURL is incorrect
2. The UserID & Password aren't correct
3. There's a firewall blocking port 3306
4. MySQL is configured to only accept remote connections to the ejb database
(pretty unlikely, but you could do this).

To eliminate those as possibilities, can you try connecting directly to the
database (ie no JPA / Tomcat / etc)? If you can connect then it's likely
that something is getting in the way.

If you'd rather pursue the JNDI path (ie your questions about openejb.xml
and datasource configuration) then you / we will have to re-post on
users@openejb for expert advice.

-mike

On Wed, Jul 1, 2009 at 4:14 PM, John_canada <john_woo@canada.com> wrote:

>
> Thanks for the quick reply, Rick.
>
> Eventually I found out it was about the datasource config:
>
> in such case(using Tomcat), the
> my.war/WEB-INF/classes/META-INF/persistence.xml
> 1. should not specify any database info but the datasource id (specified in
> /tomcat/conf/openejb.xml), as
>
> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
> <jta-data-source>contextDS</jta-data-source>
>
> if specifying the database info, like
> <property name="openjpa.ConnectionURL"
> value="jdbc:mysql://localhost:3306/ejb"/>
> <property name="openjpa.ConnectionDriverName"
> ...
> then the following error found:
>
> <openjpa-1.2.1-r752877:753278 fatal user error>
> org.apache.openjpa.persistence.ArgumentException: A connection could not be
> obtained for driver class "com.mysql.jdbc.Driver" and URL
> "jdbc:mysql://localhost:3306/ejb". You may have specified an invalid URL.
>
>
> org.apache.openjpa.jdbc.schema.DataSourceFactory.newConnectException(DataSourceFactory.java:256)
>
>
> org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(DataSourceFactory.java:242)
>
>
> org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:692)
>
>
> org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:790)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.setContext(JDBCStoreManager.java:136)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.setContext(JDBCStoreManager.java:120)
>
>
> org.apache.openjpa.kernel.DelegatingStoreManager.setContext(DelegatingStoreManager.java:78)
> org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:309)
>
>
> org.apache.openjpa.kernel.AbstractBrokerFactory.initializeBroker(AbstractBrokerFactory.java:216)
>
>
> org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:190)
>
>
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:142)
>
>
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:192)
>
>
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:56)
>
>
> org.apache.openejb.persistence.JtaEntityManagerRegistry.getEntityManager(JtaEntityManagerRegistry.java:105)
>
>
> org.apache.openejb.persistence.JtaEntityManager.getEntityManager(JtaEntityManager.java:61)
>
>
> org.apache.openejb.persistence.JtaEntityManager.persist(JtaEntityManager.java:97)
> ...
>
> 2. create and place up openejb.xml and open-ejb-jar.xml in the same
> METTA-INF folder, companied with persistence.xml, then the created entity
> bean and its data can be found/accessed in run time (in debug), but it's
> not
> persisted in database.
>
> openejb-jar.xml
> <dep:environment>
> <dep:moduleId>
> <dep:groupId>myEJB</dep:groupId>
> <dep:artifactId>EJB</dep:artifactId>
> <dep:version>2.0</dep:version>
> <dep:type>car</dep:type>
> </dep:moduleId>
> </dep:environment>
> <name:cmp-connection-factory>
> <name:pattern>
> <name:groupId>console.myTX</name:groupId>
> <name:artifactId>myTX</name:artifactId>
> </name:pattern>
> </name:cmp-connection-factory>
>
> data info in openejb.xml as:
> <Resource id="myTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> ...
> </Resource>
> <Resource id="myNOTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> ....
> </Resource>
>
> the persistence.xml:
> <persistence-unit name="aUnit" >
> <jta-data-source>myTX</jta-data-source>
> <non-jta-data-source>myNOTX</non-jta-data-source>
> ...
>
> so, my question became, how to specify the datasource out of /tomcat/conf/?
>
> Thanks in advance.
>
> --
> John
>
>
>
> Rick Curtis wrote:
> >
> > John -
> >
> > It looks like you annotated your Person.id to be unique, but you didn't
> > specify a value... I'm assuming that you're using an AI column for your
> > id.
> > I see you're running on MySQL, so try adding the annotation
> > @GeneratedValue(strategy=GenerationType.IDENTITY) to your id column. If
> > that
> > doesn't work, please post a snippet of your Entity/mapping file(s).
> >
> > -Rick
> >
> > On Wed, Jul 1, 2009 at 12:44 PM, John_canada <john_woo@canada.com>
> wrote:
> >
> >>
> >> Hi,
> >>
> >> I deployed openejb.war in tomcat, and tested a web app which used ejb3;
> >> it's
> >> very simple: a servlet called a stateless bean, which created an entity
> >> as
> >> following:
> >>
> >> session bean:
> >> @PersistenceContext(unitName="aUnit",type =
> >> PersistenceContextType.TRANSACTION)
> >> private EntityManager manager;
> >>
> >> Person p = new Person(name, address);
> >> manager.persist(p);
> >> manager.flush();
> >>
> >> the persistence.xml:
> >> <persistence-unit name="aUnit" transaction-type="JTA">
> >>
> >>
> >>
> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
> >> <jta-data-source>myTX</jta-data-source>
> >> <non-jta-data-source>myNOTX</non-jta-data-source>
> >> <class>ejb.Person</class>
> >> ...
> >>
> >> openejb.xml:
> >> <Resource id="myTX" type="DataSource">
> >> JdbcDriver com.mysql.jdbc.Driver
> >> JdbcUrl jdbc:mysql://localhost:3306/a
> >> UserName root
> >> Password aaa
> >> </Resource>
> >>
> >> <Resource id="myNOTX" type="DataSource">
> >> JdbcDriver com.mysql.jdbc.Driver
> >> JdbcUrl jdbc:mysql://localhost:3306/a
> >> UserName root
> >> Password aaa
> >> JtaManaged false
> >> </Resource>
> >>
> >> However, I got the following error when executing manager.flush();
> >> org.apache.openjpa.lib.jdbc.ReportingSQLException: Attempt to insert
> null
> >> into a non-nullable column: column: ID table: PERSON in statement
> [INSERT
> >> INTO person (person_id, address, name) VALUES (?, ?, ?)] {prepstmnt
> >> 6240623
> >> INSERT INTO person (person_id, address, name)
> >> VALUES (?, ?, ?)
> >> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> >> state=23000]
> >>
> >>
> >>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:192)
> >>
> >>
> >>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:57)
> >>
> >>
> >>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:866)
> >>
> >>
> >>
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1504)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:151)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:120)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingPreparedStatementManagerImpl.java:82)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:89)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:72)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:543)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:105)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:59)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:655)
> >>
> >>
> >>
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
> >> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010)
> >>
> >> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908)
> >> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1679)
> >>
> >>
> >>
> org.apache.openjpa.kernel.DelegatingBroker.flush(DelegatingBroker.java:989)
> >>
> >>
> >>
> org.apache.openjpa.persistence.EntityManagerImpl.flush(EntityManagerImpl.java:592)
> >>
> >>
> >>
> org.apache.openejb.persistence.JtaEntityManager.flush(JtaEntityManager.java:130)
> >> ejb.HelloBean.createPerson(HelloBean.java:31)
> >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>
> >>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>
> >>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >> java.lang.reflect.Method.invoke(Method.java:597)
> >>
> >>
> >>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158)
> >>
> >>
> >>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141)
> >>
> >>
> >>
> org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:122)
> >>
> >>
> >>
> org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:221)
> >>
> >>
> >>
> org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:174)
> >>
> >>
> >>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217)
> >>
> >>
> >>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77)
> >>
> >>
> >>
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:281)
> >> $Proxy46.createPerson(Unknown Source)
> >> test.HelloServlet.doGet(HelloServlet.java:31)
> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> >>
> >>
> >> It's obvious, from
> >> INSERT INTO person (person_id, address, name)
> >> VALUES (?, ?, ?)
> >> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> >> state=23000]
> >>
> >> the parms values were taken, but did not pass/forward to database - this
> >> should not be in ejb3 package.
> >>
> >> Can anyone tell how to fix it?
> >>
> >> Thanks
> >> --
> >> John
> >> --
> >> View this message in context:
> >>
> http://n2.nabble.com/did-pass-params---Attempt-to-insert-null-into-a-non-nullable-column-tp3190581p3190581.html
> >> Sent from the OpenJPA Users mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/did-pass-params---Attempt-to-insert-null-into-a-non-nullable-column-tp3190581p3191855.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>

Re: did pass params - Attempt to insert null into a non-nullable column

2009-07-02T06:54:06Z
Thanks lots Mike.

Actually what I wanted was to simply specify a connection in persistence.xml, if can not, then specifying in openejb-jar.xml (or openejb.xml, in same META-INF folder).

the pesistence.xml as
<persistence-unit name="aUnit" >
<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>

<class>ejb.Person</class>
<properties>
<property name="openjpa.ConnectionURL" value="jdbc:mysql://localhost:3306/aa"/>
<property name="openjpa.ConnectionDriverName" value="com.mysql.jdbc.Driver"/>
<property name="openjpa.ConnectionUserName" value="root"/>
<property name="openjpa.ConnectionPassword" value="pass"/>
<property name="openjpa.Log" value="DefaultLevel=INFO, SQL=TRACE"/>
...

The db info is correct (tested in dos command prompt). however, it when trying to connect via calling entity bean, I still got:
javax.ejb.EJBException: The bean encountered a non-application exception; nested exception is:
<openjpa-1.2.1-r752877:753278 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: There were errors initializing your configuration: <openjpa-1.2.1-r752877:753278 fatal user error> org.apache.openjpa.util.UserException: A connection could not be obtained for driver class "com.mysql.jdbc.Driver" and URL "jdbc:mysql://localhost:3306/aa". You may have specified an invalid URL.
at org.apache.openjpa.jdbc.schema.DataSourceFactory.newConnectException(DataSourceFactory.java:256)
at org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(DataSourceFactory.java:242)
at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:692)
...

Was this (connection issue) in jpa package or in ejb package?

--
John

Michael Dick wrote:

At least some of this will be better handled by the OpenEJB / Tomcat folks
and we can certainly cross post the question on their mailing list(s) if
needed.

From an OpenJPA point of view you should be able to specify the connection
properties (openjpa.ConnectionURL, openjpa.ConnectionDriverName, etc.) or
use a jta-data-source in persistence.xml. If you use a jta-data-source then
the only requirement is that the value you provide (ie contextDS) is
available in JNDI. Usually a datasource will be bound to a location like
jdbc/${my datasource name} (coming from a WebSphere background, but I
believe this is fairly common), Tomcat might expect a similar context root -
would have to check Tomcat's doc to be sure.

The error you're getting can indicate a lot of things though :
1. The ConnectionURL is incorrect
2. The UserID & Password aren't correct
3. There's a firewall blocking port 3306
4. MySQL is configured to only accept remote connections to the ejb database
(pretty unlikely, but you could do this).

To eliminate those as possibilities, can you try connecting directly to the
database (ie no JPA / Tomcat / etc)? If you can connect then it's likely
that something is getting in the way.

If you'd rather pursue the JNDI path (ie your questions about openejb.xml
and datasource configuration) then you / we will have to re-post on
users@openejb for expert advice.

-mike

On Wed, Jul 1, 2009 at 4:14 PM, John_canada <john_woo@canada.com> wrote:

>
> Thanks for the quick reply, Rick.
>
> Eventually I found out it was about the datasource config:
>
> in such case(using Tomcat), the
> my.war/WEB-INF/classes/META-INF/persistence.xml
> 1. should not specify any database info but the datasource id (specified in
> /tomcat/conf/openejb.xml), as
>
> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
> <jta-data-source>contextDS</jta-data-source>
>
> if specifying the database info, like
> <property name="openjpa.ConnectionURL"
> value="jdbc:mysql://localhost:3306/ejb"/>
> <property name="openjpa.ConnectionDriverName"
> ...
> then the following error found:
>
> <openjpa-1.2.1-r752877:753278 fatal user error>
> org.apache.openjpa.persistence.ArgumentException: A connection could not be
> obtained for driver class "com.mysql.jdbc.Driver" and URL
> "jdbc:mysql://localhost:3306/ejb". You may have specified an invalid URL.
>
>
> org.apache.openjpa.jdbc.schema.DataSourceFactory.newConnectException(DataSourceFactory.java:256)
>
>
> org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(DataSourceFactory.java:242)
>
>
> org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:692)
>
>
> org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:790)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.setContext(JDBCStoreManager.java:136)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.setContext(JDBCStoreManager.java:120)
>
>
> org.apache.openjpa.kernel.DelegatingStoreManager.setContext(DelegatingStoreManager.java:78)
> org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:309)
>
>
> org.apache.openjpa.kernel.AbstractBrokerFactory.initializeBroker(AbstractBrokerFactory.java:216)
>
>
> org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:190)
>
>
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:142)
>
>
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:192)
>
>
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:56)
>
>
> org.apache.openejb.persistence.JtaEntityManagerRegistry.getEntityManager(JtaEntityManagerRegistry.java:105)
>
>
> org.apache.openejb.persistence.JtaEntityManager.getEntityManager(JtaEntityManager.java:61)
>
>
> org.apache.openejb.persistence.JtaEntityManager.persist(JtaEntityManager.java:97)
> ...
>
> 2. create and place up openejb.xml and open-ejb-jar.xml in the same
> METTA-INF folder, companied with persistence.xml, then the created entity
> bean and its data can be found/accessed in run time (in debug), but it's
> not
> persisted in database.
>
> openejb-jar.xml
> <dep:environment>
> <dep:moduleId>
> <dep:groupId>myEJB</dep:groupId>
> <dep:artifactId>EJB</dep:artifactId>
> <dep:version>2.0</dep:version>
> <dep:type>car</dep:type>
> </dep:moduleId>
> </dep:environment>
> <name:cmp-connection-factory>
> <name:pattern>
> <name:groupId>console.myTX</name:groupId>
> <name:artifactId>myTX</name:artifactId>
> </name:pattern>
> </name:cmp-connection-factory>
>
> data info in openejb.xml as:
> <Resource id="myTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> ...
> </Resource>
> <Resource id="myNOTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> ....
> </Resource>
>
> the persistence.xml:
> <persistence-unit name="aUnit" >
> <jta-data-source>myTX</jta-data-source>
> <non-jta-data-source>myNOTX</non-jta-data-source>
> ...
>
> so, my question became, how to specify the datasource out of /tomcat/conf/?
>
> Thanks in advance.
>
> --
> John
>
>
>
> Rick Curtis wrote:
> >
> > John -
> >
> > It looks like you annotated your Person.id to be unique, but you didn't
> > specify a value... I'm assuming that you're using an AI column for your
> > id.
> > I see you're running on MySQL, so try adding the annotation
> > @GeneratedValue(strategy=GenerationType.IDENTITY) to your id column. If
> > that
> > doesn't work, please post a snippet of your Entity/mapping file(s).
> >
> > -Rick
> >
> > On Wed, Jul 1, 2009 at 12:44 PM, John_canada <john_woo@canada.com>
> wrote:
> >
> >>
> >> Hi,
> >>
> >> I deployed openejb.war in tomcat, and tested a web app which used ejb3;
> >> it's
> >> very simple: a servlet called a stateless bean, which created an entity
> >> as
> >> following:
> >>
> >> session bean:
> >> @PersistenceContext(unitName="aUnit",type =
> >> PersistenceContextType.TRANSACTION)
> >> private EntityManager manager;
> >>
> >> Person p = new Person(name, address);
> >> manager.persist(p);
> >> manager.flush();
> >>
> >> the persistence.xml:
> >> <persistence-unit name="aUnit" transaction-type="JTA">
> >>
> >>
> >>
> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
> >> <jta-data-source>myTX</jta-data-source>
> >> <non-jta-data-source>myNOTX</non-jta-data-source>
> >> <class>ejb.Person</class>
> >> ...
> >>
> >> openejb.xml:
> >> <Resource id="myTX" type="DataSource">
> >> JdbcDriver com.mysql.jdbc.Driver
> >> JdbcUrl jdbc:mysql://localhost:3306/a
> >> UserName root
> >> Password aaa
> >> </Resource>
> >>
> >> <Resource id="myNOTX" type="DataSource">
> >> JdbcDriver com.mysql.jdbc.Driver
> >> JdbcUrl jdbc:mysql://localhost:3306/a
> >> UserName root
> >> Password aaa
> >> JtaManaged false
> >> </Resource>
> >>
> >> However, I got the following error when executing manager.flush();
> >> org.apache.openjpa.lib.jdbc.ReportingSQLException: Attempt to insert
> null
> >> into a non-nullable column: column: ID table: PERSON in statement
> [INSERT
> >> INTO person (person_id, address, name) VALUES (?, ?, ?)] {prepstmnt
> >> 6240623
> >> INSERT INTO person (person_id, address, name)
> >> VALUES (?, ?, ?)
> >> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> >> state=23000]
> >>
> >>
> >>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:192)
> >>
> >>
> >>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:57)
> >>
> >>
> >>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:866)
> >>
> >>
> >>
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1504)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:151)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:120)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingPreparedStatementManagerImpl.java:82)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:89)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:72)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:543)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:105)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:59)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:655)
> >>
> >>
> >>
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
> >> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010)
> >>
> >> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908)
> >> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1679)
> >>
> >>
> >>
> org.apache.openjpa.kernel.DelegatingBroker.flush(DelegatingBroker.java:989)
> >>
> >>
> >>
> org.apache.openjpa.persistence.EntityManagerImpl.flush(EntityManagerImpl.java:592)
> >>
> >>
> >>
> org.apache.openejb.persistence.JtaEntityManager.flush(JtaEntityManager.java:130)
> >> ejb.HelloBean.createPerson(HelloBean.java:31)
> >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>
> >>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>
> >>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >> java.lang.reflect.Method.invoke(Method.java:597)
> >>
> >>
> >>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158)
> >>
> >>
> >>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141)
> >>
> >>
> >>
> org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:122)
> >>
> >>
> >>
> org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:221)
> >>
> >>
> >>
> org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:174)
> >>
> >>
> >>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217)
> >>
> >>
> >>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77)
> >>
> >>
> >>
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:281)
> >> $Proxy46.createPerson(Unknown Source)
> >> test.HelloServlet.doGet(HelloServlet.java:31)
> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> >>
> >>
> >> It's obvious, from
> >> INSERT INTO person (person_id, address, name)
> >> VALUES (?, ?, ?)
> >> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> >> state=23000]
> >>
> >> the parms values were taken, but did not pass/forward to database - this
> >> should not be in ejb3 package.
> >>
> >> Can anyone tell how to fix it?
> >>
> >> Thanks
> >> --
> >> John
> >> --
> >> View this message in context:
> >>
> http://n2.nabble.com/did-pass-params---Attempt-to-insert-null-into-a-non-nullable-column-tp3190581p3190581.html
> >> Sent from the OpenJPA Users mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/did-pass-params---Attempt-to-insert-null-into-a-non-nullable-column-tp3190581p3191855.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>

Re: did pass params - Attempt to insert null into a non-nullable column

2009-07-01T18:51:07Z
At least some of this will be better handled by the OpenEJB / Tomcat folks
and we can certainly cross post the question on their mailing list(s) if
needed.

From an OpenJPA point of view you should be able to specify the connection
properties (openjpa.ConnectionURL, openjpa.ConnectionDriverName, etc.) or
use a jta-data-source in persistence.xml. If you use a jta-data-source then
the only requirement is that the value you provide (ie contextDS) is
available in JNDI. Usually a datasource will be bound to a location like
jdbc/${my datasource name} (coming from a WebSphere background, but I
believe this is fairly common), Tomcat might expect a similar context root -
would have to check Tomcat's doc to be sure.

The error you're getting can indicate a lot of things though :
1. The ConnectionURL is incorrect
2. The UserID & Password aren't correct
3. There's a firewall blocking port 3306
4. MySQL is configured to only accept remote connections to the ejb database
(pretty unlikely, but you could do this).

To eliminate those as possibilities, can you try connecting directly to the
database (ie no JPA / Tomcat / etc)? If you can connect then it's likely
that something is getting in the way.

If you'd rather pursue the JNDI path (ie your questions about openejb.xml
and datasource configuration) then you / we will have to re-post on
users@openejb for expert advice.

-mike

On Wed, Jul 1, 2009 at 4:14 PM, John_canada <john_woo@...> wrote:

>
> Thanks for the quick reply, Rick.
>
> Eventually I found out it was about the datasource config:
>
> in such case(using Tomcat), the
> my.war/WEB-INF/classes/META-INF/persistence.xml
> 1. should not specify any database info but the datasource id (specified in
> /tomcat/conf/openejb.xml), as
>
> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
> <jta-data-source>contextDS</jta-data-source>
>
> if specifying the database info, like
> <property name="openjpa.ConnectionURL"
> value="jdbc:mysql://localhost:3306/ejb"/>
> <property name="openjpa.ConnectionDriverName"
> ...
> then the following error found:
>
> <openjpa-1.2.1-r752877:753278 fatal user error>
> org.apache.openjpa.persistence.ArgumentException: A connection could not be
> obtained for driver class "com.mysql.jdbc.Driver" and URL
> "jdbc:mysql://localhost:3306/ejb". You may have specified an invalid URL.
>
>
> org.apache.openjpa.jdbc.schema.DataSourceFactory.newConnectException(DataSourceFactory.java:256)
>
>
> org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(DataSourceFactory.java:242)
>
>
> org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:692)
>
>
> org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:790)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.setContext(JDBCStoreManager.java:136)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.setContext(JDBCStoreManager.java:120)
>
>
> org.apache.openjpa.kernel.DelegatingStoreManager.setContext(DelegatingStoreManager.java:78)
> org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:309)
>
>
> org.apache.openjpa.kernel.AbstractBrokerFactory.initializeBroker(AbstractBrokerFactory.java:216)
>
>
> org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:190)
>
>
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:142)
>
>
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:192)
>
>
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:56)
>
>
> org.apache.openejb.persistence.JtaEntityManagerRegistry.getEntityManager(JtaEntityManagerRegistry.java:105)
>
>
> org.apache.openejb.persistence.JtaEntityManager.getEntityManager(JtaEntityManager.java:61)
>
>
> org.apache.openejb.persistence.JtaEntityManager.persist(JtaEntityManager.java:97)
> ...
>
> 2. create and place up openejb.xml and open-ejb-jar.xml in the same
> METTA-INF folder, companied with persistence.xml, then the created entity
> bean and its data can be found/accessed in run time (in debug), but it's
> not
> persisted in database.
>
> openejb-jar.xml
> <dep:environment>
> <dep:moduleId>
> <dep:groupId>myEJB</dep:groupId>
> <dep:artifactId>EJB</dep:artifactId>
> <dep:version>2.0</dep:version>
> <dep:type>car</dep:type>
> </dep:moduleId>
> </dep:environment>
> <name:cmp-connection-factory>
> <name:pattern>
> <name:groupId>console.myTX</name:groupId>
> <name:artifactId>myTX</name:artifactId>
> </name:pattern>
> </name:cmp-connection-factory>
>
> data info in openejb.xml as:
> <Resource id="myTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> ...
> </Resource>
> <Resource id="myNOTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> ....
> </Resource>
>
> the persistence.xml:
> <persistence-unit name="aUnit" >
> <jta-data-source>myTX</jta-data-source>
> <non-jta-data-source>myNOTX</non-jta-data-source>
> ...
>
> so, my question became, how to specify the datasource out of /tomcat/conf/?
>
> Thanks in advance.
>
> --
> John
>
>
>
> Rick Curtis wrote:
> >
> > John -
> >
> > It looks like you annotated your Person.id to be unique, but you didn't
> > specify a value... I'm assuming that you're using an AI column for your
> > id.
> > I see you're running on MySQL, so try adding the annotation
> > @GeneratedValue(strategy=GenerationType.IDENTITY) to your id column. If
> > that
> > doesn't work, please post a snippet of your Entity/mapping file(s).
> >
> > -Rick
> >
> > On Wed, Jul 1, 2009 at 12:44 PM, John_canada <john_woo@...>
> wrote:
> >
> >>
> >> Hi,
> >>
> >> I deployed openejb.war in tomcat, and tested a web app which used ejb3;
> >> it's
> >> very simple: a servlet called a stateless bean, which created an entity
> >> as
> >> following:
> >>
> >> session bean:
> >> @PersistenceContext(unitName="aUnit",type =
> >> PersistenceContextType.TRANSACTION)
> >> private EntityManager manager;
> >>
> >> Person p = new Person(name, address);
> >> manager.persist(p);
> >> manager.flush();
> >>
> >> the persistence.xml:
> >> <persistence-unit name="aUnit" transaction-type="JTA">
> >>
> >>
> >>
> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
> >> <jta-data-source>myTX</jta-data-source>
> >> <non-jta-data-source>myNOTX</non-jta-data-source>
> >> <class>ejb.Person</class>
> >> ...
> >>
> >> openejb.xml:
> >> <Resource id="myTX" type="DataSource">
> >> JdbcDriver com.mysql.jdbc.Driver
> >> JdbcUrl jdbc:mysql://localhost:3306/a
> >> UserName root
> >> Password aaa
> >> </Resource>
> >>
> >> <Resource id="myNOTX" type="DataSource">
> >> JdbcDriver com.mysql.jdbc.Driver
> >> JdbcUrl jdbc:mysql://localhost:3306/a
> >> UserName root
> >> Password aaa
> >> JtaManaged false
> >> </Resource>
> >>
> >> However, I got the following error when executing manager.flush();
> >> org.apache.openjpa.lib.jdbc.ReportingSQLException: Attempt to insert
> null
> >> into a non-nullable column: column: ID table: PERSON in statement
> [INSERT
> >> INTO person (person_id, address, name) VALUES (?, ?, ?)] {prepstmnt
> >> 6240623
> >> INSERT INTO person (person_id, address, name)
> >> VALUES (?, ?, ?)
> >> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> >> state=23000]
> >>
> >>
> >>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:192)
> >>
> >>
> >>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:57)
> >>
> >>
> >>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:866)
> >>
> >>
> >>
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1504)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:151)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:120)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingPreparedStatementManagerImpl.java:82)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:89)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:72)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:543)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:105)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:59)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72)
> >>
> >>
> >>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:655)
> >>
> >>
> >>
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
> >> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010)
> >>
> >> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908)
> >> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1679)
> >>
> >>
> >>
> org.apache.openjpa.kernel.DelegatingBroker.flush(DelegatingBroker.java:989)
> >>
> >>
> >>
> org.apache.openjpa.persistence.EntityManagerImpl.flush(EntityManagerImpl.java:592)
> >>
> >>
> >>
> org.apache.openejb.persistence.JtaEntityManager.flush(JtaEntityManager.java:130)
> >> ejb.HelloBean.createPerson(HelloBean.java:31)
> >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>
> >>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >>
> >>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >> java.lang.reflect.Method.invoke(Method.java:597)
> >>
> >>
> >>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158)
> >>
> >>
> >>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141)
> >>
> >>
> >>
> org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:122)
> >>
> >>
> >>
> org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:221)
> >>
> >>
> >>
> org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:174)
> >>
> >>
> >>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217)
> >>
> >>
> >>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77)
> >>
> >>
> >>
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:281)
> >> $Proxy46.createPerson(Unknown Source)
> >> test.HelloServlet.doGet(HelloServlet.java:31)
> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> >> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> >>
> >>
> >> It's obvious, from
> >> INSERT INTO person (person_id, address, name)
> >> VALUES (?, ?, ?)
> >> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> >> state=23000]
> >>
> >> the parms values were taken, but did not pass/forward to database - this
> >> should not be in ejb3 package.
> >>
> >> Can anyone tell how to fix it?
> >>
> >> Thanks
> >> --
> >> John
> >> --
> >> View this message in context:
> >>
> http://n2.nabble.com/did-pass-params---Attempt-to-insert-null-into-a-non-nullable-column-tp3190581p3190581.html
> >> Sent from the OpenJPA Users mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/did-pass-params---Attempt-to-insert-null-into-a-non-nullable-column-tp3190581p3191855.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>

Re: did pass params - Attempt to insert null into a non-nullable column

2009-07-01T14:14:31Z
Thanks for the quick reply, Rick.

Eventually I found out it was about the datasource config:

in such case(using Tomcat), the my.war/WEB-INF/classes/META-INF/persistence.xml
1. should not specify any database info but the datasource id (specified in /tomcat/conf/openejb.xml), as
<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
<jta-data-source>contextDS</jta-data-source>

if specifying the database info, like
<property name="openjpa.ConnectionURL"
value="jdbc:mysql://localhost:3306/ejb"/>
<property name="openjpa.ConnectionDriverName"
...
then the following error found:

<openjpa-1.2.1-r752877:753278 fatal user error> org.apache.openjpa.persistence.ArgumentException: A connection could not be obtained for driver class "com.mysql.jdbc.Driver" and URL "jdbc:mysql://localhost:3306/ejb". You may have specified an invalid URL.
org.apache.openjpa.jdbc.schema.DataSourceFactory.newConnectException(DataSourceFactory.java:256)
org.apache.openjpa.jdbc.schema.DataSourceFactory.installDBDictionary(DataSourceFactory.java:242)
org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:692)
org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:790)
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.setContext(JDBCStoreManager.java:136)
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.setContext(JDBCStoreManager.java:120)
org.apache.openjpa.kernel.DelegatingStoreManager.setContext(DelegatingStoreManager.java:78)
org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:309)
org.apache.openjpa.kernel.AbstractBrokerFactory.initializeBroker(AbstractBrokerFactory.java:216)
org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:190)
org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:142)
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:192)
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:56)
org.apache.openejb.persistence.JtaEntityManagerRegistry.getEntityManager(JtaEntityManagerRegistry.java:105)
org.apache.openejb.persistence.JtaEntityManager.getEntityManager(JtaEntityManager.java:61)
org.apache.openejb.persistence.JtaEntityManager.persist(JtaEntityManager.java:97)
...

2. create and place up openejb.xml and open-ejb-jar.xml in the same METTA-INF folder, companied with persistence.xml, then the created entity bean and its data can be found/accessed in run time (in debug), but it's not persisted in database.

openejb-jar.xml
<dep:environment>
<dep:moduleId>
<dep:groupId>myEJB</dep:groupId>
<dep:artifactId>EJB</dep:artifactId>
<dep:version>2.0</dep:version>
<dep:type>car</dep:type>
</dep:moduleId>
</dep:environment>
<name:cmp-connection-factory>
<name:pattern>
<name:groupId>console.myTX</name:groupId>
<name:artifactId>myTX</name:artifactId>
</name:pattern>
</name:cmp-connection-factory>

data info in openejb.xml as:
<Resource id="myTX" type="DataSource">
JdbcDriver com.mysql.jdbc.Driver
...
</Resource>
<Resource id="myNOTX" type="DataSource">
JdbcDriver com.mysql.jdbc.Driver
....
</Resource>

the persistence.xml:
<persistence-unit name="aUnit" >
<jta-data-source>myTX</jta-data-source>
<non-jta-data-source>myNOTX</non-jta-data-source>
...

so, my question became, how to specify the datasource out of /tomcat/conf/?

Thanks in advance.

--
John

Rick Curtis wrote:

John -

It looks like you annotated your Person.id to be unique, but you didn't
specify a value... I'm assuming that you're using an AI column for your id.
I see you're running on MySQL, so try adding the annotation
@GeneratedValue(strategy=GenerationType.IDENTITY) to your id column. If that
doesn't work, please post a snippet of your Entity/mapping file(s).

-Rick

On Wed, Jul 1, 2009 at 12:44 PM, John_canada <john_woo@canada.com> wrote:

>
> Hi,
>
> I deployed openejb.war in tomcat, and tested a web app which used ejb3;
> it's
> very simple: a servlet called a stateless bean, which created an entity as
> following:
>
> session bean:
> @PersistenceContext(unitName="aUnit",type =
> PersistenceContextType.TRANSACTION)
> private EntityManager manager;
>
> Person p = new Person(name, address);
> manager.persist(p);
> manager.flush();
>
> the persistence.xml:
> <persistence-unit name="aUnit" transaction-type="JTA">
>
> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
> <jta-data-source>myTX</jta-data-source>
> <non-jta-data-source>myNOTX</non-jta-data-source>
> <class>ejb.Person</class>
> ...
>
> openejb.xml:
> <Resource id="myTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> JdbcUrl jdbc:mysql://localhost:3306/a
> UserName root
> Password aaa
> </Resource>
>
> <Resource id="myNOTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> JdbcUrl jdbc:mysql://localhost:3306/a
> UserName root
> Password aaa
> JtaManaged false
> </Resource>
>
> However, I got the following error when executing manager.flush();
> org.apache.openjpa.lib.jdbc.ReportingSQLException: Attempt to insert null
> into a non-nullable column: column: ID table: PERSON in statement [INSERT
> INTO person (person_id, address, name) VALUES (?, ?, ?)] {prepstmnt 6240623
> INSERT INTO person (person_id, address, name)
> VALUES (?, ?, ?)
> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> state=23000]
>
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:192)
>
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:57)
>
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:866)
>
>
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1504)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:151)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:120)
>
>
> org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingPreparedStatementManagerImpl.java:82)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:89)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:72)
>
>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:543)
>
>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:105)
>
>
> org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:59)
>
>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89)
>
>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:655)
>
>
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010)
> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908)
> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1679)
>
> org.apache.openjpa.kernel.DelegatingBroker.flush(DelegatingBroker.java:989)
>
>
> org.apache.openjpa.persistence.EntityManagerImpl.flush(EntityManagerImpl.java:592)
>
>
> org.apache.openejb.persistence.JtaEntityManager.flush(JtaEntityManager.java:130)
> ejb.HelloBean.createPerson(HelloBean.java:31)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:597)
>
>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158)
>
>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141)
>
>
> org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:122)
>
>
> org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:221)
>
>
> org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:174)
>
>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217)
>
>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77)
>
>
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:281)
> $Proxy46.createPerson(Unknown Source)
> test.HelloServlet.doGet(HelloServlet.java:31)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>
>
> It's obvious, from
> INSERT INTO person (person_id, address, name)
> VALUES (?, ?, ?)
> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> state=23000]
>
> the parms values were taken, but did not pass/forward to database - this
> should not be in ejb3 package.
>
> Can anyone tell how to fix it?
>
> Thanks
> --
> John
> --
> View this message in context:
> http://n2.nabble.com/did-pass-params---Attempt-to-insert-null-into-a-non-nullable-column-tp3190581p3190581.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>

Re: did pass params - Attempt to insert null into a non-nullable column

2009-07-01T11:31:11Z
John -

It looks like you annotated your Person.id to be unique, but you didn't
specify a value... I'm assuming that you're using an AI column for your id.
I see you're running on MySQL, so try adding the annotation
@GeneratedValue(strategy=GenerationType.IDENTITY) to your id column. If that
doesn't work, please post a snippet of your Entity/mapping file(s).

-Rick

On Wed, Jul 1, 2009 at 12:44 PM, John_canada <john_woo@...> wrote:

>
> Hi,
>
> I deployed openejb.war in tomcat, and tested a web app which used ejb3;
> it's
> very simple: a servlet called a stateless bean, which created an entity as
> following:
>
> session bean:
> @PersistenceContext(unitName="aUnit",type =
> PersistenceContextType.TRANSACTION)
> private EntityManager manager;
>
> Person p = new Person(name, address);
> manager.persist(p);
> manager.flush();
>
> the persistence.xml:
> <persistence-unit name="aUnit" transaction-type="JTA">
>
> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
> <jta-data-source>myTX</jta-data-source>
> <non-jta-data-source>myNOTX</non-jta-data-source>
> <class>ejb.Person</class>
> ...
>
> openejb.xml:
> <Resource id="myTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> JdbcUrl jdbc:mysql://localhost:3306/a
> UserName root
> Password aaa
> </Resource>
>
> <Resource id="myNOTX" type="DataSource">
> JdbcDriver com.mysql.jdbc.Driver
> JdbcUrl jdbc:mysql://localhost:3306/a
> UserName root
> Password aaa
> JtaManaged false
> </Resource>
>
> However, I got the following error when executing manager.flush();
> org.apache.openjpa.lib.jdbc.ReportingSQLException: Attempt to insert null
> into a non-nullable column: column: ID table: PERSON in statement [INSERT
> INTO person (person_id, address, name) VALUES (?, ?, ?)] {prepstmnt 6240623
> INSERT INTO person (person_id, address, name)
> VALUES (?, ?, ?)
> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> state=23000]
>
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:192)
>
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:57)
>
>
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:866)
>
>
> org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1504)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:151)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:120)
>
>
> org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingPreparedStatementManagerImpl.java:82)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:89)
>
>
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:72)
>
>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:543)
>
>
> org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:105)
>
>
> org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:59)
>
>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89)
>
>
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72)
>
>
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:655)
>
>
> org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010)
> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908)
> org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1679)
>
> org.apache.openjpa.kernel.DelegatingBroker.flush(DelegatingBroker.java:989)
>
>
> org.apache.openjpa.persistence.EntityManagerImpl.flush(EntityManagerImpl.java:592)
>
>
> org.apache.openejb.persistence.JtaEntityManager.flush(JtaEntityManager.java:130)
> ejb.HelloBean.createPerson(HelloBean.java:31)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:597)
>
>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158)
>
>
> org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141)
>
>
> org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:122)
>
>
> org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:221)
>
>
> org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:174)
>
>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217)
>
>
> org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77)
>
>
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:281)
> $Proxy46.createPerson(Unknown Source)
> test.HelloServlet.doGet(HelloServlet.java:31)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>
>
> It's obvious, from
> INSERT INTO person (person_id, address, name)
> VALUES (?, ?, ?)
> [params=(long) 2201, (String) any address, (String) name]} [code=-10,
> state=23000]
>
> the parms values were taken, but did not pass/forward to database - this
> should not be in ejb3 package.
>
> Can anyone tell how to fix it?
>
> Thanks
> --
> John
> --
> View this message in context:
> http://n2.nabble.com/did-pass-params---Attempt-to-insert-null-into-a-non-nullable-column-tp3190581p3190581.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>

did pass params - Attempt to insert null into a non-nullable column

2009-07-01T10:44:42Z
Hi,

I deployed openejb.war in tomcat, and tested a web app which used ejb3; it's very simple: a servlet called a stateless bean, which created an entity as following:

session bean:
@PersistenceContext(unitName="aUnit",type = PersistenceContextType.TRANSACTION)
private EntityManager manager;

Person p = new Person(name, address);
manager.persist(p);
manager.flush();

the persistence.xml:
<persistence-unit name="aUnit" transaction-type="JTA">
<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
<jta-data-source>myTX</jta-data-source>
<non-jta-data-source>myNOTX</non-jta-data-source>
<class>ejb.Person</class>
...

openejb.xml:
<Resource id="myTX" type="DataSource">
JdbcDriver com.mysql.jdbc.Driver
JdbcUrl jdbc:mysql://localhost:3306/a
UserName root
Password aaa
</Resource>

<Resource id="myNOTX" type="DataSource">
JdbcDriver com.mysql.jdbc.Driver
JdbcUrl jdbc:mysql://localhost:3306/a
UserName root
Password aaa
JtaManaged false
</Resource>

However, I got the following error when executing manager.flush();
org.apache.openjpa.lib.jdbc.ReportingSQLException: Attempt to insert null into a non-nullable column: column: ID table: PERSON in statement [INSERT INTO person (person_id, address, name) VALUES (?, ?, ?)] {prepstmnt 6240623
INSERT INTO person (person_id, address, name)
VALUES (?, ?, ?)
[params=(long) 2201, (String) any address, (String) name]} [code=-10, state=23000]
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:192)
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:57)
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:866)
org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269)
org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1504)
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:151)
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:120)
org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingPreparedStatementManagerImpl.java:82)
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:89)
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:72)
org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:543)
org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:105)
org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:59)
org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89)
org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72)
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:655)
org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010)
org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908)
org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1679)
org.apache.openjpa.kernel.DelegatingBroker.flush(DelegatingBroker.java:989)
org.apache.openjpa.persistence.EntityManagerImpl.flush(EntityManagerImpl.java:592)
org.apache.openejb.persistence.JtaEntityManager.flush(JtaEntityManager.java:130)
ejb.HelloBean.createPerson(HelloBean.java:31)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:158)
org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:141)
org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:122)
org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:221)
org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:174)
org.apache.openejb.core.ivm.EjbObjectProxyHandler.businessMethod(EjbObjectProxyHandler.java:217)
org.apache.openejb.core.ivm.EjbObjectProxyHandler._invoke(EjbObjectProxyHandler.java:77)
org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:281)
$Proxy46.createPerson(Unknown Source)
test.HelloServlet.doGet(HelloServlet.java:31)
javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

It's obvious, from
INSERT INTO person (person_id, address, name)
VALUES (?, ?, ?)
[params=(long) 2201, (String) any address, (String) name]} [code=-10, state=23000]

the parms values were taken, but did not pass/forward to database - this should not be in ejb3 package.

Can anyone tell how to fix it?

Thanks
--
John

Open JPA 1.2 - getting error "The related type has unjoined subclasses"

2009-07-01T09:43:08Z

I have the following abstract class with property sysProp on it.

@Table(name="DDB_System")
@Inheritance(strategy=InheritanceType.TABLE_PER_CLASS)
@Entity(name="System")
public abstract class System
.....................................
@Column(name="sysProp1",length=1024)
@Basic
private String sysProp1;

System also has multiple subclasses, each with properties of their own:

@Table(name="ComputerSystem") ** This has multiple concrete
subTypes**
@Inheritance(strategy=InheritanceType.TABLE_PER_CLASS)
@DiscriminatorValue(value="ComputerSystem")
@Entity(name="ComputerSystem")
public class ComputerSystem extends System
.....................................
@Column(name="csProp1",length=1024)
@Basic
private String csProp1;

and

@DiscriminatorValue(value="OperatingSystem")
@Entity(name="OperatingSystem")
public class OperatingSystem extends System
.....................................
@Column(name="osProp1",length=1024)
@Basic
private String osProp1;

I have another entity that is directly related to the "System" abstract
class.

@Table(name="A")
@Entity(name="A")
public class A
........................
@ManyToOne
@PrimaryKeyJoinColumn(name="SOURCEID",referencedColumnName="OID")
private System Source;

When I try to query over this relationship and include a property from the
abstract class, it fails:

"select m from A m where m.Source.sysProp1 = 'z'"
Caused by: <openjpa-1.2.0-r422266:683325 fatal user error>
org.apache.openjpa.persistence.ArgumentException: Cannot join across
"A.Source". The related type has unjoined subclasses.
at org.apache.openjpa.jdbc.meta.strats.RelationStrategies.unjoinable(
RelationStrategies.java:53)

If I change the query to include a property from one of the subTypes, it
fails because it doesn't know about that property:
"select m from A m where m.Source.osProp1 = 'z'"
Caused by: <openjpa-1.2.0-r422266:683325 nonfatal user error>
org.apache.openjpa.persistence.ArgumentException: An error occurred while
parsing the query filter "select m from A m where m.Source.osProp1 = 'z'".
Error message: No field named "osProp1" in class "class System".
at
org.apache.openjpa.kernel.exps.AbstractExpressionBuilder.parseException(
AbstractExpressionBuilder.java:118)

An archived post
(http://mail-archives.apache.org/mod_mbox/openjpa-users/200711.mbox/%3CBLU121-W4364476C3E2522DB2CE52D818A0@...%3E)
said to add the @Type annotation to relationship property. When I changed
it to the following, both queries worked as expected:
@ManyToOne
@PrimaryKeyJoinColumn(name="SOURCEID",referencedColumnName="OID")
@Type(OperatingSystem.class)
private System Source;

My problem is that this lets me set one concrete subType, but I have more
than one. Is there a way to set multiple. Any query going to the other
subType still won't work:
"select m from A m where m.Source.csProp1 = 'z'"

Thanks,

Jeff Awe
Email: jtawe@...
Dept: ELH Phone: 507-253-1955 T/L: 553-1955

Re: State Management, changed properties on detached object not saving

2009-07-01T08:47:48Z
On Wed, Jul 1, 2009 at 10:39 AM, ljnelson <ljnelson@...> wrote:

>
> You need to follow this pattern when merging:
>
> final X newThing = em.merge(oldThing);
>
> ...and then "throw out" oldThing, since it is effectively no longer valid.
>
>
The merge is effectively the end of the "operational transaction" so I don't
really care that the original is no good. What I'm doing is this:

get managed entity X
detach X by closing em
edit properties of X
get new em
begin em transaction
merge X
commit em transaction
walk away

What's done at "edit properties" is not sent to the database on commit.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@...

Re: State Management, changed properties on detached object not saving

2009-07-02T16:23:21Z
You might want to also take a look at the openjpa.AutoDetach property.

You can use this to ensure entities are detached on commit, for example.

Daryl Stultz wrote:

On Wed, Jul 1, 2009 at 3:58 PM, Daryl Stultz <daryl@6degrees.com> wrote:

> Is there a way to detach a single entity instance without closing the em?
>

Re: State Management, changed properties on detached object not saving

2009-07-01T13:06:17Z
On Wed, Jul 1, 2009 at 3:58 PM, Daryl Stultz <daryl@...> wrote:

> Is there a way to detach a single entity instance without closing the em?
>

I see I can cast my em to OpenJPAEntityManager. Should I use detachCopy,
evict, or detach (which is in the code but not the JavaDocs)? Documentation
is a little thin.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@...

Re: State Management, changed properties on detached object not saving

2009-07-01T12:58:41Z
On Wed, Jul 1, 2009 at 3:18 PM, Daryl Stultz <daryl@...> wrote:

>
>
> I don't know yet if the above test represents the problem my application is
> having

Yes! That's it! In a "web transaction" I retrieved an entity, set my
properties and ended the web transaction which closed the em. Then in the
next web transaction I hit the save button which gets an new em and does the
merge. Which doesn't work. I threw in a em.close() before setting my
properties and it works now. I just don't like doing that - my em might need
to lazy load some stuff later. Is there a way to detach a single entity
instance without closing the em?

Thanks Mike! You were a great help!

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@...

Re: State Management, changed properties on detached object not saving

2009-07-01T12:18:03Z
On Wed, Jul 1, 2009 at 2:11 PM, Michael Dick <michael.d.dick@...>wrote:

> Hi Daryl,
>
> Here's what I've run and I think it does what you're trying to do.

Thanks for working on this Mike. Your example is good - it's interesting
that it can be sent to the database just by begin/commit as you've shown.
You didn't do quite what I want do. Here's what I want:

MyEntity entity = em.find(MyEntity.class, entityId);
entity.setProperty(20);
assertEquals(6, getValueFromDb(entityId)); // default is 6
assertTrue(em.contains(entity));
// after save, it's the same
entity.save();
assertEquals(20, getValueFromDb(entityId));
assertTrue(em.contains(entity));
// simulate new web transaction (Force detach)
em = getEntityManagerForNewWebTransaction();
assertFalse(em.contains(entity));
entity.setProperty(30);
entity.save();
assertFalse(em.contains(entity)); // entity is not the merged instance
assertEquals(30, getValueFromDb(entityId));

This actually works, to my surprise. Trying to make it look like your
example, I eliminated some problem code. Here's a version that fails on the
last line:

MyEntity entity = em.find(MyEntity.class, entityId);
entity.setProperty(20); // setting this does not automatically update DB
assertEquals(6, getValueFromDb(entityId)); // default is 6
// after save, it's the same
entity.save();
assertEquals(20, getValueFromDb(entityId));
*entity.setProperty(30);*
// simulate new web transaction
em = getEntityManagerForNewWebTransaction();
entity.save(); // does not write new value
assertEquals(30, getValueFromDb(entityId)); // FAILS!!!

I don't know yet if the above test represents the problem my application is
having, but the difference is that the property was set while the entity was
still attached to the old em. Is that expected behavior? If I move the bold
line after em is replaced, it works.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@...

Re: State Management, changed properties on detached object not saving

2009-07-01T11:11:55Z
Hi Daryl,

Here's what I've run and I think it does what you're trying to do. FWIW I've
been using 1.2.2-SNAPSHOT for this test and it's passing for me:

@Test
public void testDetachUpdateMergeCommit() {
EntityManager em = emf.createEntityManager();

Person p = em.find(Person.class, 1);
em.close(); // force detach

em = emf.createEntityManager();
assertFalse(em.contains(p));
p.setIntProperty(new Integer(10));

Person p2 = em.merge(p);
assertFalse(em.contains(p));
assertTrue(em.contains(p2));

// No updates have been flushed to the database yet.
assertEquals(2, getPropertyFromDB());

// commit a transaction to write to db.
em.getTransaction().begin();
em.getTransaction().commit();

// after transaction commits the database will have the new value.
assertEquals(10, getPropertyFromDB());
}

-mike

On Wed, Jul 1, 2009 at 11:28 AM, Daryl Stultz <daryl@...> wrote:

> On Wed, Jul 1, 2009 at 12:17 PM, Michael Dick <michael.d.dick@...
> >wrote:
>
> > What does myEntity.getEntityManager() return and how is that set into
> your
> > entity (ie is your code managing it, or are getting it from OpenJPA) ?
> >
>
> I'm using a thread local variable. I've written a variation of the unit
> test
> that replaces the save() method with direct factory/em handling and
> em.merge
> calls to eliminate the possibility of bad logic in my save() method as well
> as my thread local handling. It didn't make any difference. I can post the
> other version if you like.
>
>
> --
> Daryl Stultz
> _____________________________________
> 6 Degrees Software and Consulting, Inc.
> http://www.6degrees.com
> mailto:daryl@...
>

Re: State Management, changed properties on detached object not saving

2009-07-01T09:28:24Z
On Wed, Jul 1, 2009 at 12:17 PM, Michael Dick <michael.d.dick@...>wrote:

> What does myEntity.getEntityManager() return and how is that set into your
> entity (ie is your code managing it, or are getting it from OpenJPA) ?
>

I'm using a thread local variable. I've written a variation of the unit test
that replaces the save() method with direct factory/em handling and em.merge
calls to eliminate the possibility of bad logic in my save() method as well
as my thread local handling. It didn't make any difference. I can post the
other version if you like.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@...

Re: State Management, changed properties on detached object not saving

2009-07-01T09:17:03Z
What does myEntity.getEntityManager() return and how is that set into your
entity (ie is your code managing it, or are getting it from OpenJPA) ?

On Wed, Jul 1, 2009 at 10:51 AM, Daryl Stultz <daryl@...> wrote:

> On Wed, Jul 1, 2009 at 11:43 AM, Michael Dick <michael.d.dick@...
> >wrote:
>
> > The
> > PesistenceContext can be thought of as the state of a set of entities in
> > memory (sort of a L1 cache). When the PersistenceContext is flushed your
> > changes will go to the database. When the transaction is committed
> they'll
> > be committed in the DataBase.
>
>
> (Please see other post for p-code of general pattern.) I *am* committing
> the
> transaction but the values (that should have been copied to the merged
> instance I ignored) are not written to the db.
>
> --
> Daryl Stultz
> _____________________________________
> 6 Degrees Software and Consulting, Inc.
> http://www.6degrees.com
> mailto:daryl@...
>

Re: State Management, changed properties on detached object not saving

2009-07-01T08:51:09Z
On Wed, Jul 1, 2009 at 11:43 AM, Michael Dick <michael.d.dick@...>wrote:

> The
> PesistenceContext can be thought of as the state of a set of entities in
> memory (sort of a L1 cache). When the PersistenceContext is flushed your
> changes will go to the database. When the transaction is committed they'll
> be committed in the DataBase.

(Please see other post for p-code of general pattern.) I *am* committing the
transaction but the values (that should have been copied to the merged
instance I ignored) are not written to the db.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@...

Re: State Management, changed properties on detached object not saving

2009-07-01T08:43:38Z
Hi Daryl,

Some comments based on your post (selected snippets below) :

// push into managed context and replace instance
> entity = em.merge(entity);
> // I thought an update on object would be live to DB, but it's not
>
> The update is not live to the DB. What you've done here is merge a detached
instance into the PersistenceContext - not into the DB. The
PesistenceContext can be thought of as the state of a set of entities in
memory (sort of a L1 cache). When the PersistenceContext is flushed your
changes will go to the database. When the transaction is committed they'll
be committed in the DataBase.

The remaining issues look like they happen because the entity is trying to
manage itself. As Laird indicated em.merge(myEntity) doesn't add myEntity to
the PersistenceContext, it creates a new copy of myentity. The new copy is
part of the PersistenceContext, but myEntity is not.

-mike

On Wed, Jul 1, 2009 at 9:39 AM, ljnelson <ljnelson@...> wrote:

>
> On Wed, Jul 1, 2009 at 10:03 AM, Daryl Stultz (via Nabble) <
> ml-user+140370-1665331873@...<ml-user%2B140370-1665331873@...>
> <ml-user%2B140370-1665331873@...<ml-user%252B140370-1665331873@...>
> >
> > wrote:
>
> > To be a little more clear, entity.save() looks like this:
> >
> > EntityManager em = getEntityManager();
> > boolean alreadyInTransaction = em.getTransaction().isActive();
>
> if (! alreadyInTransaction) em.getTransaction().begin();
>
> if (getId() == null) em.persist(this);
>
> else em.merge(this);
> >
> if (! alreadyInTransaction) em.getTransaction().commit();
>
>
> I have to admit to only cursorily (is that a word?) scanning this, but
> remember that merge() has a return value, and the return value supersedes
> the value you passed into it.
>
> You need to follow this pattern when merging:
>
> final X newThing = em.merge(oldThing);
>
> ...and then "throw out" oldThing, since it is effectively no longer valid.
>
> Given that you are merge()ing "this", that might be difficult. :-D
>
> I hope that helps at least somewhat. Good luck.
>
> Best,
> Laird
>
> --
> View this message in context:
> http://n2.nabble.com/State-Management%2C-changed-properties-on-detached-object-not-saving-tp3188832p3189415.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>

Re: State Management, changed properties on detached object not saving

2009-07-01T07:39:18Z
On Wed, Jul 1, 2009 at 10:03 AM, Daryl Stultz (via Nabble) <ml-user%2B140370-1665331873@...> wrote:
To be a little more clear, entity.save() looks like this:

EntityManager em = getEntityManager();
boolean alreadyInTransaction = em.getTransaction().isActive();
if (! alreadyInTransaction) em.getTransaction().begin();
if (getId() == null) em.persist(this);
else em.merge(this);
if (! alreadyInTransaction) em.getTransaction().commit();

I have to admit to only cursorily (is that a word?) scanning this, but remember that merge() has a return value, and the return value supersedes the value you passed into it.

You need to follow this pattern when merging:

final X newThing = em.merge(oldThing);

...and then "throw out" oldThing, since it is effectively no longer valid.

Given that you are merge()ing "this", that might be difficult. :-D

I hope that helps at least somewhat. Good luck.

Best,
Laird

Re: State Management, changed properties on detached object not saving

2009-07-01T07:02:36Z
On Wed, Jul 1, 2009 at 8:59 AM, Daryl Stultz <daryl@...> wrote:

> Hello,
>

To be a little more clear, entity.save() looks like this:

EntityManager em = getEntityManager();
boolean alreadyInTransaction = em.getTransaction().isActive();
if (! alreadyInTransaction) em.getTransaction().begin();
if (getId() == null) em.persist(this);
else em.merge(this);
if (! alreadyInTransaction) em.getTransaction().commit();

The manual states:

The merge method returns a managed copy of the given detached entity. *Changes
> made to the persistent state of the detached entity are applied to this
> managed instance. *

I am assuming that the changes should be flushed to the database upon
commit. I think my unit test shows that this is not happening. That seems
highly unlikely, so if someone could prove me wrong, that would be great.

--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:daryl@...