« Back to General Discussion - All Versions

cvp 4.1 vxml server - missing xalan.jar

Combination View Flat View Tree View
Threads [ Previous | Next ]
Just noticed that my vxml server doesn't have a xalan.jar file - it's always been there before. This is causing problems trying to compile custom java in Eclipse.

Is this a defect? Shouldn't it be there? Can I use the xalan.jar from Studio 4.0?

update -The version of cvp that's missing the xalan.jar file is cvp 7

what was the error you're getting when you compile? JAXP, the java XML/XSLT libraries are part of the core Java language since java 1.4.2. JAXP 1.3 XSL Transformations use xalan xsltc for implementation of methods in the Java API, but the implementation packages of the xalan.jar are in the core sdk. Check the compatibility guide: http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150.html#xsltXpath. Seems to say you can use xalan.jar from apache without package conflicts because of new package naming. I think that means if you use a xalan package name in a custom element, it won't be found in the sdk. So, try xalan.jar in the classpath, assuming you need some extension in xalan that isn't implemented in the javax.xml of the sdk.

Janine,

Just to follow up on what Brien was saying, CVP uses standard Java APIs for XML parsing. Which actual XML parser implementation - Xalan or Crimson or your own - does not matter.

As far as custom code is concerned, the only required library is framework.jar. The other libraries that a custom code requires will depend on your own code. Xalan, as well as any other third party library, is not required to create custom elements, unless your code specifically needs it.

Regards,
Michael