>> I added the right mappings for some of the
>> EJBObject methods so that the call through stateless container goes
>> through and lands on the right invoker (the one that loops).
>
> This is good and bad. You just undid some of the stuff I changed in the
> last major update.
<snip>
Dear,
Here I am talking about the mappings from the EJBObject methods *calls* ie
the functionality that was missing in stateless and stateful. I mostly
copied what was done from the Entity Container stuff. So that was easy it
was mostly wiring since the stuff you had already done there.
Now if you are talking about the mapping variables themselves, that I really
don't care, it's "repackaging". We need to redefine "update" ;-).
> > It fixes a few bugs in Bugzilla.
>
> Yes
(listen I understated the "few" in the above sentence)
> > But most importantly the TestBeans.jar stateless bean test from
> Bugzilla now
> > runs with no problem ;-)... and yes it does run from
> ejb-jar.xml alone...
>
> This is good :-)
yup
hey, don't worry your stuff is good, we are REALLY there, just 2-3 weeks
worth of work and we are there. Just let the dogs roam free on your code
and you will see, it will be worth it.
marc
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
