Look at the custom sockets test case. This is exactly what is done but the ejbs are deployed before the customized JRMPInvoker and so the exception results.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Bill Burke" <[EMAIL PROTECTED]> To: "Scott. Stark@Jboss. Org" <[EMAIL PROTECTED]> Cc: "Jboss-Dev" <[EMAIL PROTECTED]> Sent: Tuesday, March 12, 2002 9:34 AM Subject: custom sockets bug > Scott, > > I don't think this is a bug. > > 1. Define a Customer JRMPInvoker with your custom factory in a service xml > file. > 2. in jboss.xml of your ejb, use the tags <home-invoker> and <bean-invoker> > to override the default JRMPInvoker > > The BeanMetaData class uses the following mbean name as the default invoker > "jboss:service=invoker,type=jrmp" > > Regards, > > > Bill > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
