> Do you mean for the client to call A.ejbCreate() to return the B,
> or do you
> mean to create an A and then call some other method, like A.createNewB()
> which happens to return a B. That might be more reasonable, though I am
> still afraid this stuff is highly dependent on the app server
> implementation
> of the client side stubs.
none. But it is in reality the version 2. A.ejbCreate () creates "B" but
does NOT return it. "A" keeps it in one of its instance variable and then
the client may call something like A.giveMeTheByouJustCreated (). It could
be B' handle BTW. Where would be the stub problem in this case?
> Another possibility would be to make use of something like the strategy
> pattern where you always create the same type of EJB, but it delegates
> processing of certain methods to an embedded object which is created based
> upon a parameter in the create method. This gets you out of any odd stuff
> with the interfaces and casting. It probably requires the bean
> to be a BMP
> bean since the strategy object is sort of a dependent object, but
> a BMP bean
> might be easier to understand.
OK. You are right. But, in this case, we may loose flexibility from the
client side i.e. we may use this scheme if we do not need to have specific
action from the client side
Thank you for your help. Things are a lot clearer now.
Cheers,
Sacha
===========================================================================
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".
