> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
> Sent: Monday, August 14, 2000 12:50 AM
> To: jBoss Developer
> Subject: Re: [jBoss-Dev] unification of method maps
>
>
> Hi!
>
> marc fleury wrote:
> > compared to what RMH and I had written I find the current
> method lookup for
> > invocation
> >
> > 1- ugly!
>
> Why is it ugly?
because
>
> > 2- buggy
>
> What is buggy?
I have to work on it, any change to the methods we need to see (like "most"
of the EJB methods :) we need to do that in several places. pain but where
is the gain?
> > 3- fast?
>
> Yes, since the lookup is O(1). What is the alternative?
>
> > Ok rickard, don't get all locked up... what is the reason
> behind the 2 maps
> > one in invoker/container.
>
> One maps the remote MI to EJB invocations, and one maps EJB invocations
> to bean methods. Two different maps.
MI comes from EJB methods, by definition... will look, these sounds
redundant.
> > Is the only reason for this structure the "speed" because if it
> is it seems
> > to me we have other issues... <grin>
>
> What is the other issue? (Call me!)
>
> > In any case the real case is can we unify the 2 maps?
> JRMPContainerInvoker
> > and Container)...
>
> No, they have different purposes. Why do you want to unify them? What is
> the issue?
hard to maintain... real need?
marc
>
> /Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
