Com ctc wstx sr validatingstreamreader
We have experimented with generating OSGi metadata on our own using Spring Source's Bundlor tool.
Could you please confirm that we are allowed to follow this path for production?
We are not sure what's the problem you are facing by using the recent version of aspose.cells with OSGi?
Best regards, Jens Hi, Thanks for your posting and using Aspose.
Thread Pool Executor$Task(Unknown Source) at concurrent. Thread Pool Executor$Worker.run(Unknown Source) at JBoss WS client request (works) And this almost works; if I change the reply To address (through TCPMON) to " instead of " I get a response instead of an error.
Endpoint Reference; import org.apache.axis2.client. To effectively use Aspose in an OSGi environment we would need to make the Aspose jar file OSGi aware.
2009-12-10 ,384 INFO [main] Service Deployer - Deploying Web service: - file:/D:/opt/axis2-1.5/repository/services/2009-12-10 ,776 ERROR [Axis2 Task] Fault Manager - org.apache.axis2.
Configuration Context; import org.apache.axis2.context. Configuration Context Factory; import org.apache.sandesha2. Sandesha2Constants; import org.apache.sandesha2.client. Sandesha Client; import org.apache.sandesha2.client. Sandesha Client Constants; import org.apache.sandesha2 Axis Fault: The endpoint reference (EPR) for the Operation not found is and the WSA Action = at org.apache.axis2.engine.
For the used APIs of Woodstox, we are afraid currently you have to expose all used packages to OSGi enviornment.Configuration Context Factory.create Configuration Context(Configuration Context Factory.java:64) at org.apache.axis2.context.Configuration Context Factory.create Configuration Context From File System(Configuration Context Factory.java:180) at org.apache.axis2.client.We would not be touching and of the class files, we just need to add a few new entires to the manifest file.However, it is a complicated task for us and we are afraid we cannot finish it very soon.