- Original Message -
From: "Jeff Schnitzer" [EMAIL PROTECTED]
To: "Orion-Interest" [EMAIL PROTECTED]
Sent: Monday, December 11, 2000 4:57 PM
Subject: RE: EJB2.0 Generated class uncompilable
FYI, as a workaround, you can make bidirectional relationships work by
m
- Original Message -
From: "Tim Drury" [EMAIL PROTECTED]
To: "Orion-Interest" [EMAIL PROTECTED]
Sent: Friday, December 08, 2000 5:39 PM
Subject: RE: EJB2.0 Generated class uncompilable
Since your bean is called "Foo" I'm going to guess
that it is a tr
;
}
and so on for Identity, and all other fields
HTH
JP
-Original Message-
From: Peter Pontbriand [mailto:[EMAIL PROTECTED]]
Sent: Lunes, 11 de Diciembre de 2000 13:38
To: Orion-Interest
Subject: Re: EJB2.0 Generated class uncompilable
- Original Message -
From: "Tim Drury&qu
EJB2.0 DTD _is_ specified in ejb-jar.xml ...
ejb-jar.xml is:
-
?xml version="1.0"?
!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_2_0.dtd"
P.Pontbriand
Canlink Interactive Technologies Inc.
In EJB 2.0 gets/sets are declared abstract.
The container implements them for you.
-tim
-Original Message-
From: Juan Lorandi (Chile) [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 11, 2000 1:42 PM
To: Orion-Interest
Subject: RE: EJB2.0 Generated class uncompilable
geez
:[EMAIL PROTECTED]]
Sent: Monday, December 11, 2000 10:43 AM
To: Orion-Interest
Subject: RE: EJB2.0 Generated class uncompilable
I don't think we've ever cleared up whether
this is needed or not:
in ejb-jar.xml:
entity
cmp-version2.x/cmp-version
...
Your bar ejb seems to reference
Since your bean is called "Foo" I'm going to guess
that it is a trivial "Hello World" bean. Why don't
you post the bean code and the ejb-jar.xml (don't
attach/zip/etc - just dump it)?
-tim
-Original Message-
From: Peter Pontbriand [mailto:[EMAIL PROTECTED]]
Sent: Friday, December
I've been using EJB2.0 beans (including container managed relationships)
with considerable success for several months now. It works (mostly).
Don't give up :-)
I haven't seen that particular error message, but I have noticed that
occasionally Orion screws up the deployment and forgets to
- Original Message -
From: "Peter Pontbriand" [EMAIL PROTECTED]
We've just written our first pair of 2.0-spec EJBs and are experiencing
some
really strange problems deploying them. Orion 1.4.4 auto-generates the DB
tables for these beans, but then spits out the following message for
use autoupdate or find it in
http://www.orionserver.com/orion/orion.jar
use at own risk! (actually, 1.4.4 is VERY stable)
-Original Message-
From: Serge Knystautas [mailto:[EMAIL PROTECTED]]
Sent: Viernes, 08 de Diciembre de 2000 20:48
To: Orion-Interest
Subject: Re: EJB2.0 Generated
Take the version you have and do:
cd $ORION_HOME
java -jar autoupdate.jar
This will pull down the latest released build from Orion. Pretty sweet
feature.
Scott Stirling
West Newton, MA
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Serge
Knystautas
You might want to go to:
http://www.orionsupport.com
And grab the simple EJB 2.0 sample...
Jim
--On Friday, December 08, 2000 4:02 PM -0500 Peter Pontbriand
[EMAIL PROTECTED] wrote:
Hello All.
We've just written our first pair of 2.0-spec EJBs and are experiencing
some really strange
12 matches
Mail list logo
