David,

I was hoping you were going to say that, as it seemed wrong. Although,
the stacktrace leads me to believe that the initial VM classloader is at
work here, and thus the reason why I even tried using the command line.
I tried it in server/default/lib and JBOSS_HOME/lib, but no luck either
way. Here is what I get when I start Jboss without the command line
classpath entry to the jar but with the jar in either location mentioned
above:

    [spawn]      [java] java.lang.ClassNotFoundException:
com.betweenmarkets.jboss.BMIDeploymentSorter
    [spawn]      [java]         at
java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    [spawn]      [java]         at
java.security.AccessController.doPrivileged(Native Method)
    [spawn]      [java]         at
java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    [spawn]      [java]         at
java.lang.ClassLoader.loadClass(ClassLoader.java:297)
    [spawn]      [java]         at
java.lang.ClassLoader.loadClass(ClassLoader.java:253)
    [spawn]      [java]         at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
    [spawn]      [java]         at java.lang.Class.forName0(Native
Method)
    [spawn]      [java]         at
java.lang.Class.forName(Class.java:120)
    [spawn]      [java]         at
org.jboss.deployment.scanner.URLDeploymentScanner.setURLComparator(URLDe
ploymentScanner.java:101)
    [spawn]      [java]         at
java.lang.reflect.Method.invoke(Native Method)
    [spawn]      [java]         at
org.jboss.mx.capability.ReflectedMBeanDispatcher.setAttribute(ReflectedM
BeanDispatcher.java:186)
    [spawn]      [java]         at
org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:44
5)
    [spawn]      [java]         at
org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.ja
va:482)
    [spawn]      [java]         at
org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:
356)
    [spawn]      [java]         at
org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator
.java:208)
    [spawn]      [java]         at
org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:15
3)
    [spawn]      [java]         at
org.jboss.system.ServiceController.install(ServiceController.java:194)
    [spawn]      [java]         at
java.lang.reflect.Method.invoke(Native Method)
    [spawn]      [java]         at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
spatcher.java:284)
    [spawn]      [java]         at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
    [spawn]      [java]         at
org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
    [spawn]      [java]         at $Proxy3.install(Unknown Source)
    [spawn]      [java]         at
org.jboss.deployment.SARDeployer.create(SARDeployer.java:206)
    [spawn]      [java]         at
org.jboss.deployment.MainDeployer.create(MainDeployer.java:637)
    [spawn]      [java]         at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:512)
    [spawn]      [java]         at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:481)
    [spawn]      [java]         at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:465)
    [spawn]      [java]         at
java.lang.reflect.Method.invoke(Native Method)
    [spawn]      [java]         at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
spatcher.java:284)
    [spawn]      [java]         at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
    [spawn]      [java]         at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:314)
    [spawn]      [java]         at
org.jboss.system.server.ServerImpl.start(ServerImpl.java:216)
    [spawn]      [java]         at org.jboss.Main.boot(Main.java:142)
    [spawn]      [java]         at org.jboss.Main$1.run(Main.java:375)
    [spawn]      [java]         at java.lang.Thread.run(Thread.java:484)

Note that I am launching it from an Ant target rather than running the
shell or batch script in bin. Here is what the script does:

                <java fork="true" dir="${jboss.home}/bin"
classname="org.jboss.Main">
                        <jvmarg value="-Xms256m"/>
                        <jvmarg value="-Xmx256m"/>
                        <jvmarg value="-Xincgc"/>
                        <arg value="${jboss.server.name}"/>
                        <!-- the server namespace 'default', 'bmi', etc
-->
                        <classpath>
                                <pathelement
path="${apacheXerces.class.path}"/>
                                <pathelement
path="${jboss.home}/bin/run.jar"/>
                                <pathelement
path="${bmiRoot}/BuildTools/sun/jdk1.3/lib/tools.jar"/>
                        </classpath>
                </java>

> -----Original Message-----
> From: David Jencks [mailto:[EMAIL PROTECTED]] 
> Sent: Tuesday, October 08, 2002 4:59 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] Adding a custom DeploymentSorter
> 
> 
> It's not expected by me.  Unless you have modified the jboss 
> startup code to explicitly instantiate your sorter, putting 
> the jar in server/[conf]/lib should work.  Only put things in 
> $JBOSS_HOME/lib that are needed for the boot process. 
> Anything mentioned in server/[conf]/conf/jboss-service.xml
> should be found if it is in server/[conf]/lib
> 
> david jencks
> 
> On 2002.10.08 17:27:56 -0400 James Higginbotham wrote:
> >  I have created a custom deployment sorter and found that I 
> had to add 
> > the jar to my classpath on the command line, rather than 
> using -L or 
> > the bootstrap finding it automatically in JBoss 3.0.0 within the 
> > $JBOSS_HOME/lib dir. Is this an expected thing, or am I missing a 
> > step? Wanted to confirm this step was the appropriate one before we 
> > add it to our installation wizard.
> >  
> > Thanks,
> > James
> > 
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> 
> > <HTML><HEAD><TITLE>Message</TITLE>
> > <META http-equiv=Content-Type content="text/html; 
> charset=us-ascii"> 
> > <META content="MSHTML 6.00.2719.2200" name=GENERATOR></HEAD> <BODY>
> > <DIV><SPAN class=626132521-08102002><FONT face=Arial 
> size=2>&nbsp;I have
> > created 
> > a custom deployment sorter and found that I had to add the jar to my
> > classpath 
> > on the command line, rather than using -L or the bootstrap 
> finding it 
> > automatically in JBoss 3.0.0 within the $JBOSS_HOME/lib 
> dir. Is this an
> > expected 
> > thing, or am I missing a step? Wanted to confirm this step was the
> > appropriate 
> > one before we add it to our installation wizard. 
> </FONT></SPAN></DIV>
> > <DIV><SPAN class=626132521-08102002><FONT face=Arial 
> > size=2></FONT></SPAN>&nbsp;</DIV>
> > <DIV><SPAN class=626132521-08102002><FONT face=Arial 
> > size=2>Thanks,</FONT></SPAN></DIV>
> > <DIV><SPAN class=626132521-08102002><FONT face=Arial 
> > size=2>James</FONT></SPAN></DIV></BODY></HTML>
> > 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf 
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED] 
> https://lists.sourceforge.net/lists/listinfo/j> boss-user
> 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to