RE: CMP 2.0

[Randahl Fink Isaksen]

Title: RE: CMP 2.0

Thanks, Tim

 

I just dived into chapter 16 (Transactions) and it is clear that there is definately important stuff there which needs to be taken into consideration to avoid errors. However, it turned out that the reason for the problem I described was the fact that I had declared my primary key classes as "Integer" and in the create methods returned "int" - as soon as that was corrected, everything work fine.

I must say that I am a bit surprised this fault was not discovered by Orion on compile time !!???!!?

 

Thanks again

Randahl

 

 -----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tim Drury
Sent: 28. februar 2001 17:34
To: Orion-Interest
Subject: RE: CMP 2.0

I've been out for a few days, so it this has been answered,
sorry for the repost.

This sounds like you didn't set the transactional behavior
in ejb-jar.xml as "required".  There is no default behavior
in the spec so it is up to the container to decide what
the default behavior is.  I know in Weblogic, transactions
default to "supports" (I think).  In any event, the entities
are not stored in the database unless you mark them
as "required".  Orion may be doing the same thing.

-tim

> -----Original Message-----
> From: Randahl Fink Isaksen [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 26, 2001 5:29 AM
> To: Orion-Interest
> Subject: CMP 2.0
>
>
> Would somebody please confirm that they have been able to use CMP 2.0
> relationships on Orion, that they have seen them get stored
> in the database
> AND brought back into main memory correctly after a restart
> of the server.
>
> When I create a relationship it works fine until I restart -
> I simply can't
> make Orion restore my relationships from the keys it stores
> in the database.
> If I try the getX() / method of a cmr property it works - but after a
> restart it returns null.
>
>
> R.
>
>
>