Hi,
> This is because of the classpath changes that scott made. The jaxp parser
> jars have been moved from lib to lib/ext.
>
> Where is your MBean loaded from, jboss.jcml or jboss.conf? If it is
> jboss.conf, then you will need to add the jaxp.jar and
> crimson.jar's to the
> archive list.
It is loaded from jboss.jcml.
>
> Don't know if that helps, but I found that when I am using the XML
> configuration for the Log4jService, it will complain about these too.
>
> If this happens from inside jboss.jcml, and both of these files
> are actually
> in the lib/ext directory, then something else is wrong. Unfortunatly the
> bootstrap classloading that goes on is still a little bit of a mistery to
> me.
>
> SAX, DOM, Whatever.
>
> If you still have files other than jmxri.jar in your output/jboss-*/lib
No it is clean.
> directory then you should probably re-build with something like this from
> the build module:
>
> ./build.sh clean release
>
> Or just remove everything in output/jboss-*/lib and:
>
> ./build.sh
>
> Which will install all the correct files. Let me know a little more about
> where this MBean is loaded and if any of this helps.
jboss.jcml:
<mbean code="com.abc.TestFileLoader"
name="HubMethods:service=TestFileLoader">
<attribute name="ConfigFile">test.xml</attribute>
</mbean>
jboss.conf
<MLET CODE = "org.jboss.util.ClassPathExtension" ARCHIVE="hm-jmx.jar"
CODEBASE="../../lib/ext/">
<ARG TYPE="java.lang.String" VALUE="/Projects/etc/conf/">
</MLET>
I will try to look at other MBeans and how they can parse XML documents...
I am out for the day, it will be for tomorrow...
Thanks.
Vincent.
>
> --jason
>
>
> On Tue, 14 Aug 2001, Vincent Harcq wrote:
>
> > Hi,
> > I build OK.
> > I run OK except for one custom MBean. This is due to xml
> changes I guess.
> > I receive an exception java.lang.NoClassDefFoundError: org/w3c/dom/Node
> > On the line of my MBean that do DOMBuilder builder = new DOMBuilder();
> > This class is coming from JDOM.
> >
> > I try adding this to jboss.conf
> > <MLET CODE = "org.jboss.util.ClassPathExtension" ARCHIVE="hm-jmx.jar"
> > CODEBASE="../../lib/ext/">
> > <ARG TYPE="java.lang.String" VALUE="../../../etc/conf/">
> > <ARG TYPE="java.lang.String" VALUE="../../lib/ext/crimson.jar">
> > </MLET>
> > without success.
> >
> > It worked when xml stuffs was in lib/
> >
> > Should I not use JDOM but pure sax instead ?
> >
> > Regards.
> > Vincent.
> >
> >
> > > -----Message d'origine-----
> > > De : Jason Dillon [mailto:[EMAIL PROTECTED]]
> > > Envoye : lundi 13 aout 2001 8:04
> > > A : [EMAIL PROTECTED]
> > > Cc : Dev JBoss
> > > Objet : RE: new build system
> > >
> > >
> > > > That is a problem that will come again, I want to be sure
> to understand:
> > > > If you add a new link in CVSROOT/modules for jboss-all, a
> Check Out is
> > > > needed ? an Update is not enough ?
> > >
> > > Yes. Checkout is the only time that CVS will pay any attention to the
> > > CVSROOT/modules file. The exact module name you used is lost
> > > after that and
> > > all CVS has to work on is the data in CVS/Root &
> CVS/Repository. Update
> > > simply checks the files (and sub-directories) of modules which it has
> > > previouly checked out and has CVS/* files for.
> > >
> > > It is safe to run a checkout over an existing workspace,
> though you might
> > > get some silly warnings. Just be sure to update afterwards
> for the full
> > > effect.
> > >
> > > > Or is it only a problem when running first Check Out and
> > > killing it in the
> > > > middle (over a 56k phone line, it will happen to others
> than me I bet) ?
> > > > I will make clean CO at work (adsl hehe) and let you know
> how far I go.
> > >
> > > Checkout over an existing workspace *should not* consume that much BW.
> > >
> > > --jason
> > >
> > >
> >
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> >
>
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
