Guys,
We're all wrong here...
(or maybe it is the 01h:33m in the morning influencing me here?) but...
it all goes down to this line:
ci =
(ContainerInvoker)cl.loadClass(conf.getContainerInvoker()).newInstance();
in ContainerFactory.java, where we're trying to create a new instance of a
Container Invoker WITHOUT ANY PARAMETERS INTO THE CONSTRUCTOR...
If you go take a look at both the container invokers, (1.2 & 1.3) you'll
notice that THEY BOTH now have ONE constructor that takes one
ContainerInvoker parameter...
.newInstance () isn't going to cut it!...
Hugo
----- Original Message -----
From: "Tobias Frech" <[EMAIL PROTECTED]>
To: "jBoss Developer" <[EMAIL PROTECTED]>
Sent: Friday, December 08, 2000 10:10 PM
Subject: Re: [jBoss-Dev] NPE's in the new jBoss CVS
> Hi guys!
> I am sorry to havt to tell you there still seems to be a bug. (A brain
> bug perhaps ;-) ). When using
> org.jboss.ejb.plugins.jrmp13.server.JRMPContainerInvoker I still get
> [Container factory] org.jboss.ejb.DeploymentException: Missing or
> invalid Container Invoker (in jboss.xml or standardjboss.xml)
> [Container factory] at
> org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:737)
> [Container factory] at
> org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:243)
>
> Huog reported using jrmp instead of jrmp13 works. Looks the same to me
> up to now. But I am not sure what the drawbacks are using just jrmp on a
> 1.3 system.
>
> Tobias
>
> marc fleury wrote:
> >
> > Ok it is done.
> >
> > Several things came out of this experience.
> >
> > First of all IRC is really very very cool, just great I encourage you
guys
> > to go there on #jboss.org it just rocks!
> > Juha spotted the real bug (I was going in circles and he made it happen
:)
> > Hugo tested it and it works.
> >
> > So it is commited,
> >
> > thanks
> >
> > marc
> >
> > |-----Original Message-----
> > |From: [EMAIL PROTECTED]
> > |[mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> > |Sent: Friday, December 08, 2000 12:21 PM
> > |To: jBoss Developer
> > |Subject: RE: [jBoss-Dev] NPE's in the new jBoss CVS
> > |
> > |
> > |I am on it
> > |
> > |marc
> > |
> > ||-----Original Message-----
> > ||From: [EMAIL PROTECTED]
> > ||[mailto:[EMAIL PROTECTED]]On Behalf Of Hugo Jos� Pinto
> > ||Sent: Friday, December 08, 2000 11:38 AM
> > ||To: jBoss Developer
> > ||Subject: [jBoss-Dev] NPE's in the new jBoss CVS
> > ||
> > ||
> > || All,
> > ||
> > || Andy fixed the logger, so I tried to run the testsuite again...
And
> > ||Oooa! new NPE. This one I can't trace - it's probably rickard's
> > |underground
> > ||matter... :)
> > ||
> > || Here it is:
> > ||
> > || while running locktest (or any other test in the suite):
> > ||
> > ||_____________________________________________
> > ||
> > ||Welcome to the lock test v0.1
> > ||_____________________________________________
> > ||
> > ||Deploying the bean...done!
> > ||java.lang.NullPointerException
> > || at org.jboss.proxy.Proxy.newProxyInstance(Proxy.java:17)
> > || at org.jboss.proxy.ProxyProxy.readResolve(ProxyProxy.java:83)
> > || at java.lang.reflect.Method.invoke(Native Method)
> > || at
> > ||java.io.ObjectStreamClass.invokeMethod(ObjectStreamClass.java:1615)
> > || at
> > |java.io.ObjectInputStream.readObject(ObjectInputStream.java:393)
> > || at
> > |java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
> > || at java.rmi.MarshalledObject.get(MarshalledObject.java:138)
> > || at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:299)
> > || at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:279)
> > || at javax.naming.InitialContext.lookup(InitialContext.java:350)
> > || at org.jboss.test.lock.test.Main.go(Main.java:65)
> > || at org.jboss.test.lock.test.Main.main(Main.java:31)
> > ||
> > ||...And on the server side:
> > ||
> > ||[Default] JBoss PRE-2.1 Started
> > ||[J2EE Deployer Default] Module locktest.jar is not running
> > ||[J2EE Deployer Default] Destroying application locktest.jar
> > ||[J2EE Deployer Default] Deploy J2EE application:
> > ||file:/C:/doco/jbosstest/bin/../
> > ||deploy/locktest.jar
> > ||[J2EE Deployer Default] Create application locktest.jar
> > ||[J2EE Deployer Default] install module locktest.jar
> > ||[J2EE Deployer Default] Starting module locktest.jar
> > ||[Container factory]
> > ||Deploying:file:/C:/doco/jboss/tmp/deploy/Default/locktest.ja
> > ||r/ejb1001.jar
> > ||[Verifier] Verifying
> > ||file:/C:/doco/jboss/tmp/deploy/Default/locktest.jar/ejb1001
> > ||.jar
> > ||[Container factory] Deploying EnterpriseEntity
> > ||[Container factory] JRMP 1.2.2 CI initialized
> > ||[JAWS] Table 'EnterpriseEntity' already exists
> > ||[Bean Cache] Cache policy scheduler started
> > ||[Container factory] Deployed application:
> > ||file:/C:/doco/jboss/tmp/deploy/Default
> > ||/locktest.jar/ejb1001.jar
> > ||[J2EE Deployer Default] J2EE application:
> > ||file:/C:/doco/jbosstest/bin/../deploy/
> > ||locktest.jar is deployed.
> > ||
> > ||Strange thing I noticed is that JBoss is using, as default, the 1.2.2
JRMP
> > ||Container invoker.. Should'nt it be 1.3?
> > ||
> > ||Hope this somehow helps...
> > ||
> > ||Hugo
>
