Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-discussion] Problem during deployment of Protege Plugin

Timothy Redmond tredmond at
Mon Dec 13 17:54:24 PST 2010

I knew that I had lost track of this e-mail.  I don't know the answer 
but I have seen things like this before.  My reply rambles a bit because 
I don't have a solution for you yet.

This looks like a case of the class 
doing some magic with class loaders which is not working with the OSGi 
environment.  One of the indicators of this is that it is indicating 
that it is using the sun.misc.Launcher$AppClassLoader class loader.  
This is probably the system class loader.  The class loaders for the 
bundles (Protege plugins) would print out as something like

    (org.apache.felix.framework.ModuleImpl$ModuleClassLoader) 11.0

Your WstxInputFactory class probably loads correctly in the bundle context.

It might help to find the source for the  This might tell you how to either 
pre-register the WstxInputFactory or to change the class loader that the 
FactoryLocator is using.  I don't think that this class is a standard 
java thing.  I noticed that the source in [1] does not correspond to the 
code that you are running.  This is probably the next step in debugging 
and I suspect this source can be found in the axis 2 project.  If you 
find it send it and I will see if this helps.

Another tool that can be helpful is the attached org.protege.osgi.debug 
plugin.  Dump it in the plugins directory and start Protege.  You can 
then see what bundles are able to load which classes.  There are some 
instructions on how to use this tool here [2].  In particular you can 
double check that your bundle can load the WstxInputFactory class.



On 12/10/2010 07:06 AM, Götz Fabian wrote:
> Hello everyone,
> I'm experiencing some trouble during deployment of a Protege plugin. Building and running it (using the Ant script) works flawlessly in Eclipse. However, when I copy the resulting jar file into the plugins folder of Protege and launch it, the following exception is thrown twice:
> Requested factory com.ctc.wstx.stax.WstxInputFactory cannot be located.  Classloader =sun.misc.Launcher$AppClassLoader at 546b97fd
> 	at
> 	at
> 	at
> 	at
> 	at$
> 	at Method)
> 	at
> 	at
> 	at
> 	at org.apache.axis2.util.XMLUtils.toOM(
> 	at org.apache.axis2.util.XMLUtils.toOM(
> 	at org.apache.axis2.deployment.DescriptionBuilder.buildOM(
> 	at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(
> 	at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(
> 	at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(
> 	at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(
> 	at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(
> 	at org.apache.axis2.client.ServiceClient.configureServiceClient(
> 	at org.apache.axis2.client.ServiceClient.<init>(
> com.ctc.wstx.stax.WstxInputFactory is included in a supplied jar, which you can also find here:
> Other classes are successfully loaded from this jar file, with the exception of WstxInputFactory.
> Has anyone experienced a similar problem? Is there some magic in the class/bundle loading of Protege?
> Thank you for any kind of help or advice!
> Götz
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at
> Instructions for unsubscribing:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: org.protege.osgi.debug.jar
Type: application/x-java-archive
Size: 1441857 bytes
Desc: not available
URL: <>

More information about the protege-discussion mailing list