|This is still failing because the ProxyFactory is doing everything |in create |while the JRMPInvoker is not registering itself until start. When we had |init/start, services were not usable until start. The setup of the invokers |and interceptors should be delayed until the ProxyFactory.start(). Is |there a reason this isn't being done now?
no, marcf | |----- Original Message ----- |From: "Scott M Stark" <[EMAIL PROTECTED]> |To: <[EMAIL PROTECTED]> |Sent: Tuesday, March 12, 2002 6:37 PM |Subject: Re: [JBoss-dev] Deploy Order Broken? | | |> |> So we guarentee depth first traversal of the contents during deployment? |> I changed the deployment to an ejb-jar that contained the sar and this |> might work as the service is deployed first but it is not being found by |> the container setup. I'll look into why. |> |> 18:35:12,718 INFO [MainDeployer] Starting deployment of package: |> file:/D:/usr/l |> ocal/src/cvsroot/Main/jboss-all/testsuite/output/lib/jrmp-comp.jar |> 18:35:12,828 INFO [JRMPInvoker] JRMP Invoker MBean online |> 18:35:13,109 INFO [JRMPInvoker] creating |> 18:35:13,390 INFO [JRMPInvoker] created |> 18:35:13,609 INFO [EjbModule] Creating |> 18:35:13,656 INFO [EjbModule] Deploying StatelessSession |> 18:35:13,656 INFO [EjbModule] Deploying StatefulSession |> 18:35:14,156 ERROR [StatelessSessionContainer] Exception in service |lifecyle |> operation: create |> java.lang.RuntimeException: homeInvoker is null: |> jboss:service=invoker,type=jrmp |> ,socketType=CompressionSocketFactory |> at |> org.jboss.proxy.ejb.ProxyFactory.setupInvokers(ProxyFactory.java:188) |> |> |> ----- Original Message ----- |> From: "marc fleury" <[EMAIL PROTECTED]> |> To: "Scott M Stark" <[EMAIL PROTECTED]>; |> <[EMAIL PROTECTED]> |> Sent: Tuesday, March 12, 2002 6:14 PM |> Subject: RE: [JBoss-dev] Deploy Order Broken? |> |> |> > |One testcase that is now failing is |> > |org.jboss.test.jrmp.test.CustomSocketsUnitTestCase. |> > |See bug #529006. The testcase deploys a sar with a custom JRMPInvoker |> > |configuration and the sar includes the testcase ejbs that need the |> > |customized |> > |invoker. This also fails if deployed as an ear that includes the sar |and |> > |ejbs. |> > |> > the packaging is reversed, the way this works is that the thing that is |> > needed needs to be inside. |> > |> > in other words, if your beans need the sar, then package a jar with all |> the |> > beans, and include the sar in it. |> > |> > not the other way around, try that it should work. |> > |> > marcf |> > |> > |> > |> |> |> _______________________________________________ |> Jboss-development mailing list |> [EMAIL PROTECTED] |> https://lists.sourceforge.net/lists/listinfo/jboss-development |> | | |_______________________________________________ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
