> well the new construct is from the "newInstance" on jrmp and it decides
what
> container to take.
>
> 1 however it doesn't work with the deployer (do a testbean try)
> 2 it breaks everyone that is out there with jrmp12/jrmp13 settings.
>
> rickard, the deployer is really f*cked up with this.. I don't know what
> changed and at this point I don't really want to spend the night cleaning
it
> up.
>
> Please Rickard, pay more attention as you commit or at least use the
> testbeans to make sure your stuff is not breaking everywhere....
>
> ok no binary for now guys, it's too messy, we need to iron this out
Shit, I realize now that I committed too much. I was working simultaneously
on a JRMP CI that works with both 1.2 and 1.3, and it got commited at the
same time as everything else. As some of you have noticed all you have to do
is change the container conf. from "jrmp13" or "jrmp12" to simply "jrmp"
since it now handles both cases. I will clean this up on monday.
Terribly sorry anout this screwup :-(
regards,
Rickard
