Why does this include lib/ext... it doesn't really give you any clues (short
of the debug lines about libraries being loaded. Also how does the client/*
come into play for the server?
I fixed these isses, and thought I had things working, but now I am having
some trouble with Hypersonic, it hangs (or is it the last bit that I see)
when the server starts.
Let me know about that build.sh problem, I don't like things like that
laying around.
--jason
On Tue, 31 Jul 2001, Scott M Stark wrote:
> The loading of the lib/ext directory jars into the server classpath is done by this
> ClassPathExtension MLET entry in jboss.conf:
>
> <!-- Place the config directory in the classpath -->
> <MLET CODE = "org.jboss.util.ClassPathExtension" ARCHIVE="jboss.jar"
>CODEBASE="../../lib/ext/">
> <ARG TYPE="java.lang.String" VALUE="./">
> </MLET>
>
> The "./" value is resolved relative to the org.jboss.util.ClassPathExtension
>codesource
> location, so its jar needs to be in the lib/ext directory. Has this been changed?
>
> > I almost have the server starting up from a release done off the the
> > jboss_buildmagic branch, but I can't seem to get past some class loading
> > issues.
> >
> > I get to about here:
> >
> > [Info] Java version: 1.3.1,Sun Microsystems Inc.
> > [Info] Java VM: Java HotSpot(TM) Server VM 1.3.1-b24,Sun Microsystems Inc.
> > [Info] System: Linux 2.4.7,i386
> > [Shutdown] Shutdown hook added
> > [ConfigurationService] Could not create MBean
> > DefaultDomain:service=Naming(org.jboss.naming.NamingService)
> > java.lang.NoClassDefFoundError: org/jnp/server/MainMBean
> > at java.lang.ClassLoader.defineClass0(Native Method)
> > at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
> >
> > and don't get much further. I did have one problem with the WebService
> > throwing a NullPointerException because I forgot to include some resource
> > files, but I have resolved that.
> >
> > My question is how does the MLet that is responsible for classloading
> > actually find out about lib/ext/*. There certainly is a
> > lib/ext/jnpserver.jar which contains:
> >
> > org/jnp/server/Main.class
> > org/jnp/server/MainMBean.class
> > org/jnp/server/NamingServer.class
> > org/jnp/server/NamingServer_Stub.class
> > org/jnp/interfaces/Naming.class
> > org/jnp/interfaces/NamingParser.class
> > org/jnp/interfaces/java/javaURLContextFactory.class
> > org/jnp/interfaces/NamingContext.class
> > org/jnp/interfaces/NamingContextFactory.class
> > org/jnp/interfaces/NamingEnumerationImpl.class
> > org/jnp/interfaces/jnp/jnpURLContextFactory.class
> > META-INF/
> > META-INF/MANIFEST.MF
> >
> > From looking at log/server.log there are Add library: debug lines for each
> > .jar under lib/ext. Where is the ClassPathExtention bean that loads these?
> > Why does it appear as if it has been loaded but the class still can not be
> > found.
> >
> > Any help would be much appreciated. If it helps to actually see the
> > problem, try building/running it:
> >
> > cvs -z3 get -r jboss_buildmagic jboss-all
> > cd jboss-all/build
> > ./build.sh configure
> > ./build.sh -Djavadoc-generated-already=true
> > cd output/jboss-2.5alpha-DEV/bin
> > ./run.sh
> >
> > Perhaps you can see something that is wrong right away. I am just getting
> > frustrated with it at the moment. =(
> >
> > --jason
> >
> >
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
