As part of my recent adventures in testsuite housecleaning, I saw that the testsuite jrmp-invoker target isn't executed during a testsuite run. The target runs a set of EJB2 tests with the JRMPInvoker replacing UnifiedInvoker.
Any particular reason those aren't executed? If yes, any other good coverage of JRMPInvoker in the testsuite? If no, can we chuck the JRMPInvoker from AS 5 and require use of UnifiedInvoker? :-)
As part of the testsuite cleanup, I got the jrmp-invoker target to run properly so if we want to keep JRMPInvoker we can add the target to the regular testsuite run.
Further to all of the above, there is no "pooled-invoker" target that performs the same tests with the PooledInvoker. Same questions re: other coverage or dropping PooledInvoker apply.
If we delete the JRMPInvoker, how does JBoss4 talk to JBoss5 and vice versa
(other than using Corba? :-)
For AS 4 talking to AS 5, use the UnifiedInvoker.
For AS 5 talking to AS 4, keep the JRMP/pooled client classes. That assumes if the AS 4 distributions don't export them in client jars that can be brought into an AS 5 classpath without causing conflicts with other stuff.