What happened to the ..\client\jnet.jar file in JBoss 4.0.x?

[spoonman464]

I have a stand-alone Java client that needs to be able to get an initial JNDI context. It worked fine in JBoss 3.2.x but no longer works when I run it against a JBoss 4.0.x server. The trouble is that at runtime, my client cannot get an initial context because of the NoClassDefNotFoundError which happens when trying to find javax.net.SocketFactory.

In JBoss 3.2.x, the \client folder had a file called jnet.jar which contained a class definition for javax.net.SocketFactory.

In JBoss 4.0.x, the \client folder does NOT contain a jnet.jar file. Also, I looked into ALL of the JARs in the \client folder and cannot find one that has a class definition for javax.net.SocketFactory.

Finally, when I try to use the version 3.2.x jnet.jar with the version 4.0.x client JARs, I get an error about not being the correct version. So, I have to ask, "What happened to the ..\client\jnet.jar file in JBoss 4.0.x?"

[starksm64]

jboss-4.0.x requires a 1.4.x vm which bundles the javax.net.* and so the jnet.jar is not needed.

[spoonman464]

It turns out that the client application is forced to use a 1.3.x JVM for some architectural reasons that I can't change. So, we'll stick with JBoss 3.2.x until we grow out of our old JVM.

Thanks, Scott.

Spoon