Ok ...
I guess my question is, why can't we have an "ejbcreate" in
the home interface? Is the container looking for a "create"
method specifically?
Thanks,
Craig H.
-----Original Message-----
From: Subrahmanyam Allamaraju
To: [EMAIL PROTECTED]
Sent: 5/20/00 4:00 PM
Subject: Re: Home Interface Question
- The home's "create" does more than just delegating the creation
request to
the implementation object's "ejbCreate."
- You implement ejbXXX methods as part of the bean's contract with the
container. The remaining methods are part of the bean's contract with
the
client. Some of the client's calls may result in the container invoking
the
ejbXXX methods - but the client does not see these methods directly.
Cheers
Subbu
----- Original Message -----
From: "Craig Herder" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, May 20, 2000 1:20 PM
Subject: Home Interface Question
> Hi,
>
> Can someone explain why the home interface has a "create"
> method, and not an "ejbcreate"? (I know the "create" maps
> to "ejbcreate")
>
> TIA,
>
>
> Craig H.
>
>
========================================================================
===
> 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".
>
>
========================================================================
===
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".
===========================================================================
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".
