Both Ian's and our company seem to be confused wether your licence allows for this kind of manipulations.
Test code: XMLStream Reader parser = input Factory.create XMLStream Reader( new String Reader( xml ) ); parser.next(); // read the START document...
Hello, We've recently made a switch from building WS clients in JBoss WS to using Axis2. Endpoint Config; import org.extensions.policy.annotation. For a start, it looks like Sandesha2 [1.3] is not fully compatible with Axis2 [1.5], so I don't know how much of the problem is really a fault of my code vs. I installed Sandesha2 as outlined, with the exception that I did not change my $AXIS2_HOME/conf/axis2file (it already has RMPhase's in the phase orders). Configuration Context; import org.apache.axis2.context. Configuration Context Factory; import org.apache.sandesha2.client. Axis Fault: RM handler was not able to find WS-RM message in the payload 2009-12-10 ,933 ERROR [Axis2 Task] Fault Manager - org.apache.axis2. Addressing Constants; import org.apache.axis2.client. Phase.invoke(Phase.java:334) at org.apache.axis2.engine. Axis Engine.invoke(Axis Engine.java:251) at org.apache.axis2.engine. Axis Engine.receive(Axis Engine.java:160) at org.apache.sandesha2.workers. Sender Worker.check For Sync Responses(Sender Worker.java:707) at org.apache.sandesha2.workers. Validating Stream Reader - org.apache.sandesha2.i18n.resource::handle Get Object(soap Env Not Set) - Sandesha2 Internal Error: SOAP envelope is not set. Axis Fault(Axis Fault.java:430) at org.apache.axis2.transport. Transport Utils.create SOAPMessage(Transport Utils.java:118) ... After bit more investigation, it looks like the XML requests being sent to the JBoss AS are different.
MF file is missing the Import-Package section with external classes that Aspose Cells requires. Once, we will have some fix or update for you, we will let you know asap.
In my environment adding these packages make my code work: There are probably more packages that need to be listed as I only use a small portion of the Aspose Cells functionality. We have logged your comment in our database for consideration. For plans relating to other Aspose components like Aspose. Slides etc, you need to post your query in their respective forums. Group ID=15 Spring Source's Bundlor tool (which is similar to the mentioned bnd) generated the following Import-Package attribute: Import-Package: image.codec.jpeg;resolution:="optional",n.media.imageio.plugins.tiff;resolution:="optional",javax.crypto;reso lution:="optional",javax.crypto.spec;resolution:="optional",geio;resolution:="optional",javax.imageio.metadata;resolution:="optio nal",javax.imageio.stream;resolution:="optional",javax.media.jai;reso lution:="optional",javax.print;resolution:="optional",javax.ribute;resolution:="optional",javax.print.attribute.standard;resoluti on:="optional",javax.security.cert;resolution:="optional",p arsers;resolution:="optional",org.apache.tools.zip;resolution:="optio nal",org.provider;resolution:="optional",org.dom4j;r esolution:="optional",org.dom4j.io;resolution:="optional",org.dom4j.t ree;resolution:="optional",org.w3c.dom;resolution:="optional",.sax;resolution:="optional"Not knowing internals of Aspose Cells I intentionally specified all imported packages to be optional.
The Bnd Tool ( should be able to help figure out which packages need to be imported. May be library experts can immediately tell which of these imported packages will be used in any given scenario and therefore not be optional. We have logged your comments in our database against this issue for investigation.
Regards, Jens Hi Jens, Thanks for your additional information. Once, there is some fix or update for you, we will let you know asap.
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.
Regards, Jens Hi Jens, Thanks for your posting and using Aspose. We have logged your comments in our database for consideration. Please give us more details about your problems with new cells version. For use in OSGi we need some additional metadata (such as Import-Package, Export-Package, Bundle-Symbolic Name, Bundle-Version) in the manifest file (META-INF/Manifest. There are two alternatives for dealing with this situation:1) Vendor-provided OSGi metadata Due to the steadyly growing acceptance it might make sense that you provide OSGi metadata in your standard distribution. There is just a minor legal issue: We have to modify your jar files by enriching the manifest file as described above.