Hi Nayyer ,

We using aspose metafiles every time after couple minutes on Jboss6 started  .
Problem isn't that the file is not on the classpath , but it has a problem with parsing this xml file

Caused by: java.net.MalformedURLException
        at java.net.URL.<init>(URL.java:601) [:1.6.0_23]
        at java.net.URL.<init>(URL.java:464) [:1.6.0_23]
        at java.net.URL.<init>(URL.java:413) [:1.6.0_23]
        at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) [xercesImpl.jar:6.0.0.Final]
        at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) [xercesImpl.jar:6.0.0.Final]
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [xercesImpl.jar:6.0.0.Final]
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [xercesImpl.jar:6.0.0.Final]
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) [xercesImpl.jar:6.0.0.Final]
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) [xercesImpl.jar:6.0.0.Final]
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) [xercesImpl.jar:6.0.0.Final]
        at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source) [xercesImpl.jar:6.0.0.Final]
        at com.aspose.metafiles.License.byte(SourceFile:406) [:].

We think that one problem could be that the Aspose.License.BlackList.xml doesn't have header .

<?xml version="1.0" encoding="UTF-8"?>

We are using xerces and saxon as you can see in the log . And I can't add this header in to your xml because of checking signature .

Hello Lukas,

As far as I have understood from your description, you have attempted to re-deploy the application using new .jar file and after waiting for couple of minutes, still you are able to see this problem ?

More along, regarding Aspose.License.BlackList.xml, we are looking into the details of this problem and will get back to you soon. We are really sorry for this inconvenience.

---

Nayyer Shahbaz
Support Developer, Aspose Sialkot Team
About Us
Contact Us

Keep in touch! We're on Twitter and Facebook

Yes ,exactly as you wrote .

We restart server when we deploy app.  Only we deploy war instead of jar .

But we are almost sure that add this header into this xml should help .

When we add this header in to this xml we , got error that checksum was incorrect , so that mean Saxon finally parse this xml but value is different .

Thanks

Hello Lukas,

Sorry for the delay. We hope to share the solution shortly. Please spare us little time. We are sorry for the delay and inconvenience.

---

Nayyer Shahbaz
Support Developer, Aspose Sialkot Team
About Us
Contact Us

Keep in touch! We're on Twitter and Facebook

Hello Lukas,

Thanks for your patience.

The header is not required in XML file because we don't use such headers in Aspose.License.BlackList.xml of any other product as well. In fact this issue occurred because of a broken script, which placed Aspose.License.BlackList.xml into incorrect directory within jar, so the product was not able to read it. More along, when we have removed Aspose.License.BlackList.xml from /com/aspose/metafiles/resources directory, Aspose.Metafiles for Java is throwing same exception as you have specified earlier.

The checksum error is occurring because once you have modified the XML file in signed jar, it does not match with the signature present inside it. Please try using the updated product version and in case you still face any problem, please do let us know. We are sorry for this delay and inconvenience

---

Nayyer Shahbaz
Support Developer, Aspose Sialkot Team
About Us
Contact Us

Keep in touch! We're on Twitter and Facebook