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
|
Title: sealing violation with XSLTC
- sealing violation with XSLTC Schreier, Balz
- Re: sealing violation with XSLTC Joaquín Sánchez Jiménez
- RE: sealing violation with XSLTC Schreier, Balz
- Re: sealing violation with XSLTC Joaquín Sánchez Jiménez
- Schreier, Balz