it is part of the ejb spec.
all fields must be public so they can be directly manipulated by the container.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Sean P.
> McNamara
> Sent: Thursday, November 09, 2000 12:10 PM
> To: Orion-Interest
> Subject: Problems with CMP PrimKey...
>
>
>
> OK... I've made some progress on this, but it's left me with a few
> more questions. First, I should say that I'm running 1.3.8, which
> AFAIK is the latest stable release.
>
> The problem with my descriptor is that it didn't include a
> <field-name> element inside each <cmp-field>, adding that let me move
> further, but then I was told that it couldn't find the attribute "ssn"
> (my primkey field) in the class.
>
> It turns out that it wasn't finding it since the attribute was
> private. Does this mean that all my attributes in a CMP bean need to
> be public? If so, I'm not sure why, since reflection since JDK1.2
> allows you to view private attributes based on security properties.
>
> Can anyone shed some light on this?
>
> Thanks!
>
>
> Sean P. McNamara writes:
> >
> > Hi All-
> >
> > I'm new to Orion Server, and am in the process of developing a sample
> > application to test out CMP.
> >
> > The problem I'm having is that although I've defined a
> > primary-key-class and primkey-field, I receive errors that the
> > primkey-field is not a CMP field, even though the descriptor is set up
> > that way.
> > ...
> > And when starting the server, they error that is displayed is:
> >
> > Auto-deploying
> > /home/tank/OrionProjects/ResumeManager/rel/ResumeManager-ejb.jar (No
> > previous deployment found)... Error compiling
> > file:/home/tank/OrionProjects/ResumeManager/rel/ResumeManager-ejb.jar:
> > The specified primkey-field 'ssn' was not found among the cmp-fields
> > for the bean com.soma.axon.ejb.entity.Employee
>
>
> --
> Sean P. McNamara <[EMAIL PROTECTED]>
> SOMA Technologies, Inc. <[EMAIL PROTECTED]>
> <[EMAIL PROTECTED]>
> <[EMAIL PROTECTED]>
>
>
