Hi,
Hmm... It worked for me on a standalone openJPA testcase against derby DB.
As you are running on WLS and against oracle DB, I created a testcase with
similar environment.
http://n2.nabble.com/file/n4432179/EJBTestCase.zip EJBTestCase.zip
Please download the attached zip file. Modify build
Hello,
I'm afraid I misunderstand something.
Russell Collins wrote:
>
> Therefore the objects that are going into the Set collection need to
> implement the Comparable interface to be inserted.
>
Why is that so?
java.util.Set does not require the inserted type to implement Comparable.
Sets
Nope .. it didnt work. Does this need some property in persistence.xml also ?
My new entity looks like this now
CampaignTarger.class
@ManyToOne(targetEntity=Campaign.class, fetch = FetchType.LAZY )
@JoinColumn(name = "campaign_Ref" ,nullable=true)
@ForeignKey(deleteAction=ForeignKeyAction.NULL)
I think what you need is equivalent of @MappedSuperclass annotation in XML
..which I dont know.. :(
If you can , annoate Cat like below , it would work.
@MappedSuperclass
public class Cat {
Hope this will narrow down your search
- H
--
View this message in context:
http://n2.nabble.com/
Thomas,
When you run your application in JSE, that is, outside an application server,
you usually should configure the persistence.xml to use entity manager
transactions instead of JTA. Please change "transaction-type" attribute like
below and see whether anything changed:
Cheers,
Milosz
>
I've been trying to determine how to call an Oracle 11g stored object that
returns a REF CURSOR.
So far, I've tried to create a stored function the returns a SYS_REFCURSOR
and also a stored procedure that uses an OUT parameter of type
SYS_REFCURSOR.
Regardless how I attempt to perform this actio
Hi Himadri,
Can you try to set deleteAction=ForeignKeyAction.NULL on the foreignkey
which will nullify the local column when the parent row is deleted.
@Entity
public class EntityA {
...
@ManyToOne(targetEntity=EntityB.class,fetch=FetchType.LAZY)
@JoinColumn(name="EntityBId", nullable=t
Well thanks for your opinion ..
Id is the primary key which is a String not Long or int (Obviously with
millions of records , i wouldnt want to have primary key within boundary of
long or int ) and all tables of my application has the same kind of id
column ...Isnt it better and more clear than
Hi,
My application is an EJb3.0 running on WL10.3
My requirement is that in OneToMany Relationship , if the Entity is
deleted , Entity should not be deleted and should be set to null .
When I try to delete One , I get integrity constraint violation exception.
I used to get the same behaviour
