• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Tim Cooke
  • Devaka Cooray
  • Ron McLeod
  • Jeanne Boyarsky
  • Liutauras Vilda
  • paul wheaton
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
  • Tim Holloway
  • Martijn Verburg
  • Frits Walraven
  • Himai Minh

Converting XML to HTML using WebSphere 3.5

Ranch Hand
Posts: 82
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I need to convert XML to HTML using XSL. We are using WebSphere 3.5 (JDK 1.2.2). Reading WebSphere documentation I understand that WebSphere uses Xalan XML processor, but for conversion examples WebSphere refers to Xalan documentation.
To get Xalan documentation I downloaded Xalan, installed and tested one sample Java application, which converts XML to HTML and it works fine.
So far so good ....
When I try to compile the same application using WebSphere JDK install files I am getting class not found error for the following:
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.stream.StreamResult;
import javax.xml.transform.stream.StreamSource;
Looks like some kind of classpath is missing, but I could not figure out which path is missing. I am able to import javax.servlet.* ok.
Do I need to put any jar files from Xalan in WesSphere classpath?
Any help is appreciated.
Posts: 11962
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Could it be that you downloaded a newer version than WebSphere is using? Maybe the API has changed since so might want to check which version of Xalan your WebSphere is using and try to locate the javadocs for that particular version of Xalan.
I yam what I yam and that's all that I yam - the great philosopher Popeye. Tiny ad:
the value of filler advertising in 2021
    Bookmark Topic Watch Topic
  • New Topic