[jboss-dev] Unified invokers in Branch_4_2
Dimitris Andreadis
dimitris at jboss.org
Wed Jan 17 10:03:47 EST 2007
We've switched to the unified invoker (jboss-remoting 2.0.0.GA) for the
EJB containers in JBossAS Branch_4_2.
For backwards compatibility, conf/standardjboss.xml contains both the
new unified and the old rmi invoker-proxy-binding definitions, but the
default now is the unified ones.
This change and the move to the Arjuna TS is causing a lot of failures
in the testsuite, so any help is appreciated.
If you search for 'rmi-invoker' in testsuite/resources there are quite a
few references to it, so a question is whether we should switch those as
well or let them test the old rmi invokers.
While there, I've also noticed that jboss head doesn't have rmi-invoker
definitions in conf/standardjboss.xml, and
org.jboss.metadata.SessionMetadata / EntityMetaData for some reason
default to the rmi-invoker for clustered setups, so I suppose this has
been forgotten there?
public static final String DEFAULT_STATEFUL_INVOKER =
"stateful-unified-invoker";
public static final String DEFAULT_CLUSTERED_STATEFUL_INVOKER =
"clustered-stateful-rmi-invoker";
public static final String DEFAULT_STATELESS_INVOKER =
"stateless-unified-invoker";
public static final String DEFAULT_CLUSTERED_STATELESS_INVOKER =
"clustered-stateless-rmi-invoker";
public static final String DEFAULT_ENTITY_INVOKER_PROXY_BINDING =
"entity-unified-invoker";
public static final String
DEFAULT_CLUSTERED_ENTITY_INVOKER_PROXY_BINDING =
"clustered-entity-rmi-invoker";
Cheers
/Dimitris
More information about the jboss-development
mailing list