Title: sealing violation with XSLTC
xalan is shipped with dynamo 5.6.1, not as an extra jar, it has been merged with atg stuff into a single jar.
that jar does have a manifest file, but sealed is not set, means false...
 
I moved the code into a component being independent on any J2EE application, maybe this solves the problem.
 
other ideas?
 
cheers
balz
-----Original Message-----
From: Joaquín Sánchez Jiménez [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 28. Oktober 2003 09:38
To: Schreier, Balz; [EMAIL PROTECTED]
Cc: Schreier, Balz
Subject: Re: sealing violation with XSLTC

See in ATG Dynamo server lib if it has some version of xalan or xerces. Extract its MANIFEST files and see if Sealed comes with value set to True. If yes, you can replace ATG Dynamo library with your xalan/xerces version.
 
Bye.

----- Original Message -----
Sent: Tuesday, October 28, 2003 9:31 AM
Subject: RE: sealing violation with XSLTC

it runs on an ATG Dynamo 5.6.1 app server, implemented in a servlet which belongs to a certain J2EE application.
Honestly I don't know whether ATG has this possibility to configure MANIFEST attribute Sealed...i will check this one.
 
cheers
balz
-----Original Message-----
From: Joaquín Sánchez Jiménez [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 28. Oktober 2003 09:29
To: Schreier, Balz; [EMAIL PROTECTED]
Cc: Schreier, Balz
Subject: Re: sealing violation with XSLTC

Where is running this code?
 
For example, I have this problem under IAS 903 (Oracle APP Server). This may be because you have some JAR file with the MANIFEST attribute Sealed set to True.
 
Bye.
----- Original Message -----
Sent: Tuesday, October 28, 2003 9:13 AM
Subject: sealing violation with XSLTC

hi,

I have the following problem and hope to find somebody giving me any help:

I have a static xml file for tests, and a static xsl file which needs 3 input parameters.
The code calling the XSLTC looks like this:

                        String key = "javax.xml.transform.TransformerFactory";
                        String value = "org.apache.xalan.xsltc.trax.TransformerFactoryImpl";
                        java.util.Properties props = System.getProperties();
                        props.put(key, value);
                        System.setProperties(props);
            Source xmlSource = new StreamSource(new FileInputStream(new File("..here the path...")));
            Source xslSource = new StreamSource(new FileInputStream(new File("..here the path...")));
            TransformerFactory tFactory = TransformerFactory.newInstance();
            Templates translet = tFactory.newTemplates(xslSource);           

            Transformer transformer = translet.newTransformer();
            transformer.setParameter("fullgearurl", fullgearurl);
            transformer.setParameter("newscode", newscode);
            transformer.setParameter("newslbl", newslbl);

until here, it is running ok, but the following line rises a "java.lang.SecurityException: sealing violation":


            transformer.transform(xmlSource, new StreamResult(out));

does anybody know why?

the three jars for xsltc (xalan.jar, xercesImpl.jar and xml-apis.jar) are all in the classpath for the application.


thanks for any hints,
cheers
balz schreier

Reply via email to