Hello Magnus,
 
i studied this ATM-example and compared it with the ejb-2.0-specification.
I don't understand the dependent-class "LogEntry": Is it a dependent object
class or a dependent value class ?
 
9.4.3 of the spec tells us for
a dependent object class:
    - can be the value of a cmr-field
    - cannot be the value of a cmp-field
    - must not be serializable
a dependent value class:
    - can be the value of a cmp-field
    - cannot be the value of a cmr-field
    - mus bei serializable
 
In the ATM-example, the LogEntry-Class is serializable and a Collection of
LogEntries is a cmp-fields as well as a cmr-field.
In my opinion a cmp-field cannot be a cmr-field. Tell me if i am wrong.
Kind regards

Heinz Häußler
Eurocopter Deutschland GmbH
D/KDC
Postfach 13 53
86603 Donauwörth
Tel.: +49 (0) 906 / 71-4431
Fax.: + 49 (0) 906 / 71-4100
Mail: mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> 
Home: http:\\www.eurocopter.com <http://www.eurocopter.com/>  

-----Ursprüngliche Nachricht-----
Von: Magnus Rydin [mailto:[EMAIL PROTECTED]]
Gesendet am: Donnerstag, 21. September 2000 12:05
An: Orion-Interest
Betreff: RE: How to use EJB2.0 on Orion


Well, its basically my fault. 
The ATM has been running EJB 2.0 since the night it was implemented in
Orion, 
I just thought I should do an effort to document the application before
putting it up there for public access. 
Anyway, as previously said, its now available at 
http://www.orionserver.com/orion/applications/atm.ear
<http://www.orionserver.com/orion/applications/atm.ear>  
Please notice that it will change over time, whenever a new part of EJB 2.0
or Servlet 2.3 is implemented. 
WR 

> -----Original Message----- 
> From: Christian Sell [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ] 
> Sent: den 20 september 2000 21:41 
> To: Orion-Interest 
> Subject: Re: How to use EJB2.0 on Orion 
> 
> 
> >I have been sending this mail for quite 
> >some time but to no avail. 
> 
> well, maybe there IS no avail. Not many of us have done EJB 
> 2.0 yet, and as 
> far as the orion core team goes, I hope (!!) they are busy writing 
> documentation for the basic stuff (and improving orion in 
> their spare time). 
> 
> regards 
> 
> 


Reply via email to