Actually, I found that when I used "rebuild" on my code instead of
"make" then everything deployed fine with the primary key class. But I
still wanted to know what the correct path was, since it seemed to work
both ways. Thanks for the info. I'm a little confused as to why it
worked correctly when I used the primitive parameters - I'll have to spend
some time with the verifier. :)
Aaron
On Mon, 11 Sep 2000, Ole Husgaard wrote:
> Hi,
>
> It should be the primary key class. There is really no difference to any
> other user defined primary key class.
> I've done this with String and int and have had no problems.
> To make life a bit easier, I sometimes define an extra finder method
> findById() that takes the primitive type as an argument.
>
> For portability I currently do not use primitive primary keys at all.
> But I hope this will change...
>
> Strange, I've had no problems with this.
> Are you sure you remembered to change the primary key everywhere
> (home.findByPrimaryKey(), bean.ejbFindByPrimaryKey() return type,
> ejb-jar.xml, etc.) ?
>
>
> Best Regards,
>
> Ole Husgaard.
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
