> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Joel Riedesel

> Ahhh, but I'm not hearing that it shouldn't work or can't work.  Only
> a "probably not going to work".  I would much prefer a reason that
> it will or won't work according to the EJB specification.

Put yourself in ejbc's shoes for a minute (yes, it's quite a stretch :-)).

You are introspecting a LocalHome and looking for methods matching a certain
naming convention.  All methods that throw RemoteExceptions are
automatically excluded from this introspection, so ejbc will miss them.  And
conversely for remote interfaces and methods that do not throw
RemoteExceptions.

Since Java doesn't allow you to have identical methods with different throw
signatures, ejbc will end up with an incomplete view of the picture and will
probably let you know that it expected certain methods but couldn't find
them.

> I want to write code elegantly (reuse in many cases) and also do the
> right thing when it comes to whether I want to use the remote or the
> local object I am trying to access.  If I were not going to an EJB world,
> I'd be spending my energy working on the whole dynamic-proxy thing to
> clean this up.

Dynamic Proxies won't help you there (besides, they're useless for EJB 2.0
CMP).

> Sounds interesting.  Where does EJBGen come from?

Me :-)

> If I didn't have to worry about scalability, everything would simply use
> the remote interfaces.  Period.  But my boss would probably fire me
> then when our product didn't scale.  Thus the need to also have local
> interfaces.

I am still a bit puzzled by the fact that you seem to be using similar
methods both locally and remotely.  Typically, remote methods will be on
stateless session beans and will be used to invoke operations.  Then the
stateless session bean will mostly make calls on Entity bean accessors.
Different semantics, different localities.

> So, how would an entity bean in one VM/AS directly talk to another entity
> bean in another VM/AS?

You would need to go through remote interfaces to do that.  Either directly
between Entity beans, or indirectly through SLSB.

> Does this support local entity beans now as well as CMP 2.x?

Yes.

> Last time I looked at WebLogic it at least didn't have the local
> entity bean support.

We've had it since 6.1 (a couple of weeks after PFD2 came out).

--
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".

Reply via email to