Cedric,
That may indeed turn out to be necessary. Perhaps a 'home' method
could be used.
I was just thinking about your point regarding EJB QL, and it struck
me that if your entity has a composite primary key (primkey-field is
not specified in deployment descriptor), then you can't write an
EJB QL query for it.
Say my primary key type has two fields (abc and xyz). I can't write:
select object(o) from MyObject o where abc = ?1.abc and xyz = ?2.xyz
I knew that EJB QL was somewhat constrained, but being unable to write
EJB QL for findByPrimaryKey is perhaps surprising!
Cedric Beust wrote:
>>From: A mailing list for Enterprise JavaBeans development
>>[mailto:[EMAIL PROTECTED]]On Behalf Of Evan Ireland
>>
>
>>You can't change the signature. However you can simply create
>>another finder findByPrimaryKeyWithLog.
>>
>
> It should probably not start with "findBy", unless you want to write your own
> EJB QL for it. The best way would probably to write a wrapper function that
> logs the call and then calls findByPrimaryKey().
>
> --
> Cedric
>
>
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
