[Babeldoc-devel] JMX Scanner

[Michael A. <mic...@ze...>]

Hi,

Has anybody deployed the JMX Scanner recently?  I've successfully gotten
it deployed, but when the received document is placed into the pipeline,
it causes a CNF Exception, and I can't make out why. Here is the stack
trace:
21:14:42,606 INFO  [AsynchronousFeeder] Processing document...
21:14:42,933 INFO  [SyncPipelineStageProcessor] PipelineStage name:
entry
21:14:42,994 ERROR [ResourceLoader] [ResourceLoader.getClass] Error when
trying to load: com.babeldoc.core.pipeline.stage.NullPipelineStage
java.lang.ClassNotFoundException: Unexpected error during load of:
com.babeldoc.core.pipeline.stage.NullPipelineStage,
msg=com/babeldoc/core/pipeline/PipelineStage
        at
org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:196)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:141)
        at com.babeldoc.core.ResourceLoader.getClass(Unknown Source)
        at
com.babeldoc.core.service.ServiceFactory.getServiceClass(Unknown Source)
        at com.babeldoc.core.Type.getTypeClass(Unknown Source)


Is there some special config for the pipeline or the scanner that needs
to be included?  Any other tips/hints/suspicions that will be useful? 
Perhaps it's not JBoss at all, and I'm just configuring incorrectly. 
I've got scanner/config.properties, feeder/config.properties and
pipeline/config.properties files in the babeldoc.sar directory, and the
scanner config is definitely making it into JBoss, because the scanner
that is being loaded comes from the scanner/config.properties.

This is a dir listing of the babledoc.sar directory:
bash-2.05b$ dir
babeldoc_babelfish.jar   babeldoc-scanner.jar   commons-collections.jar 
commons-net.jar   META-INF
babeldoc_conversion.jar  babeldoc_soap.jar      commons-dbcp.jar        
commons-pool.jar  pipeline
babeldoc_core.jar        babeldoc_sql.jar       commons-digester.jar    
csv19.jar         poi.jar
babeldoc_crypto.jar      babeldoc_web.jar       commons-discovery.jar   
feeder            scanner
babeldoc_gui.jar         babeldoc_xslfo.jar     commons-httpclient.jar  
journal.log       velocity.jar
babeldoc_init.jar        commons-beanutils.jar  commons-lang.jar        
junit.jar
babeldoc_j2ee.jar        commons-cli.jar        commons-logging.jar     
log4j.jar

It occured to me that it may be because JBoss is using it's own
classloader, but if the classloader can load com.babeldoc.core.Type,
then why can't it load com.babeldoc.core.pipeline.PipelineStage?

Cheers...


MikeA