jBoss 2.0 is (bugs aside) EJB 1.1 compliant, so the fields must be
public. It is likely that the next major version of jBoss will be 2.0
compliant, but in order to support private CMP fields you need to drag in
a lot more of the 2.0 spec which replaces parts of the 1.1 spec, so we
could not allow private CMP fields while remaining 1.1 compliant. So I
would not expect the jBoss 2.0 behavior to change.
Aaron
On Tue, 19 Sep 2000, Tobias wrote:
> Hi there!
> A short while ago we had a discussion here, why the Beans CMP fields
> have to be declared public. The short answer is: because ejb 1.1 spec
> requires you to do so. That might be the case, because the container
> should be able to read/write the fields.
>
> If you have a look at the ejb 2.0 specs (public draft) the above
> requirement is gone now. Instead the container should use the set/get
> methods now.
> Which method is jBoss using right now ?
> Is this subject to change ?
>
> Greets,
>
> Tobias
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
