For example Document doc =getFromInstance(); doc.toString() is returning the correct Document on standalone
Whereas on tomcat it is returning null. On Mon, 18 Oct 2004 12:21:45 -0400, Brian Minchau <[EMAIL PROTECTED]> wrote: > > > Sudhakar, > > 1. Xerces is an XML parser. Xalan is not an XML parser. > 2. There is no comparison to be made. > 3. Xerces is not an XSLT processor. Xalan is an XSLT processor, and it can > be invoked through the JAXP API. > 4. I don't understand the question. > > ---------- > Brian Minchau > XSLT Development, IBM Toronto > e-mail: [EMAIL PROTECTED] > > IndianAtTech > <[EMAIL PROTECTED] > il.com> To > [EMAIL PROTECTED] > 10/18/2004 11:57 cc > AM > Subject > XERCES Vs XALAN > Please respond to > xalan-dev > > > > > Hi All, > > 1. I would like to know the differences between Xalan Vs Xerces parsers > 2. Similarities of Xerces with Xalan. > 3. How JAXP can be integrated with Xalan/erces Parsers > 4. What is the default API used by API?? It it Xerces/Xalan or any thing > else > > The reason behind asking this question is, the API that we have > developed using jdk1.4.2 has passed all the test cases on standalone > application. When we try to deploy the same API on tomcat it is > raising exceptions at some instances. > > Regards > Sudhakar > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
