[Sandeep Khanna]

I am using the WebSphere 6 connector to configure connection to a local WebSphere 6 install.

I have the following in the Optional JVM arguments:
-Xmx512M -Duser.language=en -Duser.region=US -Djava.awt.headless=true -Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl

My gnome-system-monitor shows that WebSphere 6 does startup with IBM JVM and the above arguments but WebSphere 6 still seems to be trying to create the Apaxhe Xalan XSLT processor:

Caused by: javax.xml.transform.TransformerException: Could not find function: replace
[4/10/06 17:12:10:153 EDT] 00000022 SystemErr R at org.apache.xalan.processor.XSLTAttributeDef.processEXPR(XSLTAttributeDef.java:768)
[4/10/06 17:12:10:153 EDT] 00000022 SystemErr R at org.apache.xalan.processor.XSLTAttributeDef.processValue(XSLTAttributeDef.java:1404)
[4/10/06 17:12:10:153 EDT] 00000022 SystemErr R at org.apache.xalan.processor.XSLTAttributeDef.setAttrValue(XSLTAttributeDef.java:1600)
[4/10/06 17:12:10:153 EDT] 00000022 SystemErr R at org.apache.xalan.processor.XSLTElementProcessor.setPropertiesFromAttributes(XSLTElementProcessor.java:338)
[4/10/06 17:12:10:153 EDT] 00000022 SystemErr R at org.apache.xalan.processor.XSLTElementProcessor.setPropertiesFromAttributes(XSLTElementProcessor.java:263)
[4/10/06 17:12:10:153 EDT] 00000022 SystemErr R at org.apache.xalan.processor.ProcessorTemplateElem.startElement(ProcessorTemplateElem.java:76)
[4/10/06 17:12:10:153 EDT] 00000022 SystemErr R at org.apache.xalan.processor.StylesheetHandler.startElement(StylesheetHandler.java:598)
[4/10/06 17:12:10:153 EDT] 00000022 SystemErr R at com.ibm.debug.xdi.jaxp.xalan.interpreted.DebugStylesheetHandler.startElement(DebugStylesheetHandler.java:290)
[4/10/06 17:12:10:155 EDT] 00000022 SystemErr R at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
[4/10/06 17:12:10:155 EDT] 00000022 SystemErr R at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
[4/10/06 17:12:10:155 EDT] 00000022 SystemErr R at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
[4/10/06 17:12:10:155 EDT] 00000022 SystemErr R at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
[4/10/06 17:12:10:155 EDT] 00000022 SystemErr R at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
[4/10/06 17:12:10:155 EDT] 00000022 SystemErr R at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
[4/10/06 17:12:10:155 EDT] 00000022 SystemErr R at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
[4/10/06 17:12:10:155 EDT] 00000022 SystemErr R at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
[4/10/06 17:12:10:155 EDT] 00000022 SystemErr R at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
[4/10/06 17:12:10:156 EDT] 00000022 SystemErr R at org.apache.xalan.templates.StylesheetRootProxy.<init>(StylesheetRootProxy.java:63)
[4/10/06 17:12:10:156 EDT] 00000022 SystemErr R at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:824)

It should have used the Saxon XSLT processor which is put on WebSphere 6 classpath by configuring the connector “Paths->Append to Classpath” property to contain the folder containing the Saxon8 Jars.

Also does anyone know how to make an EAR override js.jar bundled in over the one provided with WebSphere 6 and is on it’s protected classloader.

Any ideas?

–Sandeep Khanna

[Riyad Kalla]

It should have used the Saxon XSLT processor which is put on WebSphere 6 classpath by configuring the connector “Paths->Append to Classpath” property to contain the folder containing the Saxon8 Jars.

Try and use the “prepend” Box and see if that helps, I’m not sure why it’s not picking it up and changing the values. To double check that your arguments are right you will need to launch WebSphere externally and make sure that atlesat works first.

Also does anyone know how to make an EAR override js.jar bundled in over the one provided with WebSphere 6 and is on it’s protected classloader.

No idea.

[Author]

Posts