RE: Xalan initialization changed.

2005-03-10 Thread Scott Cantor
> I need more info, can you compile with debug to see what concrete line > is invoking the class forName. I don't find any reference in Init, > some reference in XPath related transformations but that's normal. It's line 216. The problem is probably that when it loads the classes for the Transform

Re: Xalan initialization changed.

2005-03-10 Thread Raul Benito
I need more info, can you compile with debug to see what concrete line is invoking the class forName. I don't find any reference in Init, some reference in XPath related transformations but that's normal. Regards, p.s. I will try to have a little example to run on 1.5, but right now If I change t

RE: Xalan initialization changed.

2005-03-09 Thread Scott Cantor
No luck so far. When I try it with 1.5, I get this trace (leaving out the parts before this library starts up): java.lang.NoClassDefFoundError: org/apache/xml/utils/PrefixResolver at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:164) at org.a

RE: Xalan initialization changed.

2005-03-09 Thread Scott Cantor
> I want to known, If someone experiments any performance change(either > increase or decrease) or any error with the changes. And this is > target for Scott if it is now possible to run xml-sec cvs in java 1.5 > without xalan(not doing any xpath transformation of course). Thanks, Raul, I will de

Xalan initialization changed.

2005-03-09 Thread Raul Benito
Hi, I have just commit in CVS, some changes the way xalan is initialized and used. Before this, xalan was initialized(register the FuncHere function, etc...) at Init.init() and used to search the Elements to sign/verify in IdResolver. Now, after the changes xalan is only initialized the first ti