On Fri, 17 Nov 2000, marc fleury wrote:
> ... ok maybe it is a real bug then...
>
> a bug we didn't see in testing? it seems pretty obvious though...
>
> will check, can you open a bugzilla for this?
Sure.
I've got one other idea here, first. I'm writing some simple beans
based on code from the O'Reilly EJB book. So, for my User entity
bean, I'm using a UserPK class. Here's a snippet from my ejb-jar.xml:
<entity>
<description>
This bean represnts a user.
</description>
<ejb-name>UserBean</ejb-name>
<home>ejbeans.UserHome</home>
<remote>ejbeans.User</remote>
<ejb-class>ejbeans.UserBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>ejbeans.UserPK</prim-key-class>
<reentrant>False</reentrant>
<cmp-field> <field-name>mId</field-name> </cmp-field>
<cmp-field> <field-name>mFirstName</field-name> </cmp-field>
<cmp-field> <field-name>mLastName</field-name> </cmp-field>
No where do I mention that the mId is the primary key. Do I need to
do this somewhere? I could see this causing a problem. If jBoss
doesn't know that mId is the primary key, maybe it just sets it to
null?
BTW, the UserPK object is just a wrapper around an int.
-Dave
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
