RE: CMP 2.0

[Randahl Fink Isaksen]

Title: RE: CMP 2.0

You are right, Matt, but I am afraid I consider that irrellevant. When the developer deploys his application on Orion, he should not worry about how Orion builds the beans and whether it uses the JDK or anything else in the process of doing so - he should just expect it to do its work and should an error occur along the way he should *certainly* expect it to report back to him. Anything else is a serious bug which makes it _very_ hard to develop bug free applications.

 

Yours

 

Randahl

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Matt Simmerson
Sent: 1. marts 2001 14:54
To: Orion-Interest
Subject: RE: CMP 2.0

But its java that compiles, not Orion.

-----Original Message-----
From: Randahl Fink Isaksen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 01, 2001 9:19 AM
To: Orion-Interest
Subject: RE: CMP 2.0

As I just posted, Jeff. The error was due to the fact that I had declared my
primary keys as Integer but I returned the primitive type int from my
ejbCreate methods. As soon as I changed this, everything worked fine. I am
(to put it mildly) very surprised that Orion did _not_ give me a compile
time error when I deployed - it just crashed instead or ran without working
correctly.
Yes I know who introduced the bug, but since I think Orion is a magnificent
piece of software I would never had expected it to NOT report this compile
time error.

Randahl

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Schnitzer
Sent: 1. marts 2001 02:42
To: Orion-Interest
Subject: RE: CMP 2.0

?

I have all my transactional behavior defined as NotSupported and I use
EJB 2.0 container managed relationships without issue.  I don't
currently need transactions for what I'm doing.

Randahl, have you examined the contents of the database tables and the
orion-ejb-jar.xml closely?

Jeff

-----Original Message-----
From: Tim Drury [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 28, 2001 8:34 AM
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]
<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.
>
>
>