Transformation XML problem.

Hello!
I have very easy java code for transform XML document (sorry, for print out XML without changes):
parser = new DOMParser();
parser.setPreserveWhitespace(false);
// parser input XML file
xmlURL = createURL(args[0]);
parser.parse(xmlURL);
xml = parser.getDocument();
// print the transformed document
xml.print(System.out);
But if I have DTD in XML then JDK write many errors: SIGBUS 10* bus error
If XML does not contains DTD then java code work successfuly.
I use JDK 1.2.2, xmlparserv2 for Sun Solaris

Try turning off your JIT.
I've only ever seen core dumps when it was a JIT problem.

Similar Messages

Transform XML Problem

Hello,
my java application can generate one raw xml document, then i use javax.xml.transform.TransformerFactory and Transformer to transform with one stylesheet.
The problem is that the final xml document has some strange letters inside. for example,
in the raw xml:
entspannt-ironischer Thriller mit genial verwobener Story. USA 2003. 102 Min.
in the result xml:
entspannt-ironischer Thriller mit genial verwobener Story.
USA 2003. 102 Min.
another prolem is that there are �, �, � in both xml documents. if i open the xml file in xml spy, i can read �,�,� properly, but if i open them in other editors, it will not be shown properly.
i am not sure where the problem should be. just dont know how to do further. if any one has the same experience, please help me to solve .
Thanks a lot.

ok.
I have solved the problem with �, �,�. i just put the encoding attribute in the stylesheet.

Transforming XML/XSLT : CDATA problem

Hi!
I have a problem transforming xml with XSLT using the API javax.xml.
The result is correct until I have a CDATA section in my xml document.
The transforming process encodes all the & < > (special characters) it finds in.
This occurs problem for the follow of my treatement because the content of my CDATA is already encoded.
For example, this xml code :
<?xml version='1.0' encoding="ISO-8859-1" ?>
<article>
<article-contenu><![CDATA[Accent : é Signe : <]]></article-contenu>
</article>
produces in my output :
Accent : &eacute; Signe : &lt;
This is my java code :
TransformerFactory tFactory = TransformerFactory.newInstance();
Source xmlSource = new StreamSource(readerXml);
Source xslSource = new StreamSource( fileXsl );
// Generate the transformer.
Transformer transformer = tFactory.newTransformer(xslSource);
// Perform the transformation, sending the output to the response.
transformer.transform(xmlSource, new javax.xml.transform.stream.StreamResult(sw));
How can I tell the transformer not to do that?
Thanks for your answers!

I am having a similar problem. I have enclosed my text data in my xml file like this:
<![CDATA[<b>Hello World!</b>]]>
My select statement in my XSLT sheet is as follows:
<xsl:value-of select="." disable-output-escaping="yes"/>
I have tried setting xsl:output to text, to html, and to xml. The <, >, and & get converted to xhtml entities.
Where should I begin to troubleshoot? If the Xalan xslt jars? My stylesheet. My xml doc? Java code?
Any feedback welcome.

Problem Transforming XML to JSF tags

I have a fealing there is something I don't know here,
I am transforming XML into a JSP that include tags from taglib http://java.sun.com/jsf/html (prefix="h")
This is an section from my stylesheet
<xsl:template name="forename">
<h:inputText>
<xsl:attribute name="value">#{abyss.myCustomer.forename}</xsl:attribute>
</h:inputText>
</xsl:template>
which transforms my XML to exactly what I expect if a was writting it directly as a jsp
<h:inputText value="#{abyss.myCustomer.forename}"></h:inputText>
but it still looks like this after it is rendered in the browser, and not like
<input type="text" name="dataCapture:j_id_id199" value="Customer Name" />
which is how it looks if I cut and paste the result of the transformation into a jsp, and run that by itself
Does anyone have any idea was the <h:inputText does not evaluate the tag in the browser after the transformation ?
Edited by: OB1 on Nov 23, 2007 1:46 PM
Edited by: OB1 on Nov 23, 2007 2:43 PM

Unfortunatly I do, my jsp is
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core_rt" %>
<%@ taglib prefix="x" uri="http://java.sun.com/jstl/xml_rt" %>
<%@ taglib prefix="h" uri="http://java.sun.com/jsf/html" %>
<%@ taglib prefix="f" uri="http://java.sun.com/jsf/core" %>
<html>
<c:set value="${abyss.myBusinessServicePath}" var="xmldocpath"></c:set>
<c:import url="${xmldocpath}" var="xmldoc"/>
<c:import url="/xsl/transform.xsl" var="xslt"/>
<x:transform xml="${xmldoc}" xslt="${xslt}"/>
</html>

Problem transforming XML/XSL Using Xalan

Hi, I am using the xalan apis to transform XML/XSL in a servlet..My servlet code is like...
response.setContentType("text/html; charset=UTF-8");
// Output goes in the response stream.
PrintWriter out = response.getWriter();
boolean environmentOK = (new org.apache.xalan.xslt.EnvironmentCheck()).checkEnvironment (out);
try
TransformerFactory tFactory = TransformerFactory.newInstance();
// Get the XML input document and the stylesheet.
Source xmlSource = new StreamSource("D:\\DATA\\jrun\\test\\test.xml");
Source xslSource = new StreamSource("D:\\DATA\\jrun\\test\\test.xsl");
// Generate the transformer.
Transformer transformer = tFactory.newTransformer(xslSource);
// Perform the transformation, sending the output to the response.
transformer.transform(xmlSource, new StreamResult(out));
I am getting the error ..
javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: org.xml.sax.SAXException: Namespace not supported by SAXParserjavax.xml.transform.TransformerConfigurationException
That's why I have added the line..
boolean environmentOK = (new org.apache.xalan.xslt.EnvironmentCheck()).checkEnvironment (out);
But that gives me the following error diagnostic information...
ERROR.version.DOM=ERROR attempting to load DOM level 2 class: java.lang.NoSuchMethodException
I have put all the 3 required classes, xml-apis.jar, xercesImpl.jar and xalan.jar in my application servers classpath..
Please let me know what I am doing wrong..and how this can be fixed.
Thanks
Surajit

hey Surajit
Your code is unable to create a transformer from a factory instance.
I would check why it is not creating the Transformer.On my win32 system i usee two forward slashes..to identify the file path
D://xyz//abc....instead of D:\\...i wonder if thats one reason why your code is not able to create a transformer based on the StreamSource u create for the file paths.
Code i use..that works
javax.xml.transform.TransformerFactory tFactory =
                                                            javax.xml.transform.TransformerFactory.newInstance();
                                                  javax.xml.transform.Source xmlSource = new javax.xml.transform.stream.StreamSource                              (xmlInputSource);
                                             javax.xml.transform.Source xslSource = new javax.xml.transform.stream.StreamSource
                                   (xslInputSource);
                                                                                                    // Generate the transformer.
                                                            javax.xml.transform.Transformer transformer = tFactory.newTransformer(xslSource);
                                                                                               // Perform the transformation, sending the output to the response.
                                                            transformer.transform(xmlSource,new javax.xml.transform.stream.StreamResult(out));
                                                                                                    I used jaxp-1.2 with tomcat 4.1.12
Hope that helps.

XSL Transformation enconding problem?

Hi everybody.
I have a strange problem with JDev 9.0.2.829 concerning XSL Transformation:
I just tried to make the step from JDev 3.2.3 to 9i, imported my existing project and set up JDev 9 for use with XalanJ2 and Xerces2. Everything works fine except:
If I transform XML data to HTML that contains characters with an ASCII code >127 the whole string appears multiple times (2x or 3x) in the generated HTML.
The data is read from an Oracle DB with UTF8 encoding, all my stylesheets and JSPs are UTF-8 encoded. JDev9 is set to use UTF-8 encoding.
No compilation errors, no warnings.
The same code and stylesheets work perfectly in JDev 3.2.3, deployed into Topmcat 4.0.4 and IBM WebSphere 3.5.4.
What am I missing?
Thanks in advance!
Ralf Steppacher

OK, I found the culprit.
The JSPWriter is broken and produces the faulty output when fed with UTF-8 encoded character data. The problem disappears when all character data is buffered in a ByteArrayOutputStream first (without a special encodung schema given) and then written as a string through the JSPWriter.
Ralf

How to include the first row of detail in every xquery transformed xml?

I am dealing with a XML file,where i need to publish to different BS.
First node will be a common node node which contains vital info,second node goes to one BS and third goes to another BS.
*<header></header>*
*<details></details> (they are unbounded, but the first detail tag which comes in the input file is a mandatory tag in such a way that it needs to be included in every transformed message)*
*<trailer></trailer>*
We need to apply x query transformation on it in such a way:
*</header></header>*
*<1st detail></1st detail>*
*<detail></detail> (2nd row of detail in input file)* -------------------------> Goes to BS1
*<trailer></trailer>..*
*<header></header>*
*<1st detail></1st detail>*
*<detail></detail> (3rd row of detail in input file)* ----------------------------->Goes to BS2
*<trailer></trailer>*..
And so on.
Now, the problem is how to include the first row( *1st detail* ) of detail in every xquery transformed xml?

are you looping of this input with a for each?
/yourdata/details[1] should return always the first detail element.
or before the for each do an assing of this first detail element to "generic_details_var"
and use this var in every looping iteration (in an assign or as input for xquery)

Help Please ! -- transform XML to HTML using xslt tag in JSP

Hello,
I have problem to do XSL transform in JSP.
I have an XSL : test.xsl
I have an XML : test.xml
In JSP I have:
<x:xslt media="html" xml="test.xml">
<x:stylesheet media="html" uri="test.xsl" />
</x:xslt>
But It doesn't work the way it suppose to. What is wrong in my code ? I followed the URL http://e-docs.bea.com/wls/docs81/xml/xml_apps.html
Thanks in advance,
Christina

Basically:
    try{
      //Setting up parameters.
      xml=new StreamSource(new File(xmlInput));
      xsl=new StreamSource(new File(xslInput));
      baos=new ByteArrayOutputStream();
      htmlResult=new StreamResult(baos);
      //Transform input(xml, xsl) onto html output.
      TransformerFactory tfactory=TransformerFactory.newInstance();
      Transformer transformer=tfactory.newTransformer(xsl);
      transformer.transform(xml, htmlResult);
      baos.writeTo(out);
      //System.err.println(htmlResult.getOutputStream().toString());
    catch(...){
    }I havent tested and I havent use this for a while, but I hope this can serve as a staring point.
Regards,
OO

Transforming XML Data with XSLT in a servlet

Trying to transform XML data using XSLT. The following code works fine outside of a servlet. But in a servlet it gives the following error :
* Transformer Factory error
javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: org.xml.sax.SAXException: Namespace not supported by SAXParser
javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: org.xml.sax.SAXException: Namespace not supported by SAXParser
     at org.apache.xml.utils.DefaultErrorHandler.fatalError(DefaultErrorHandler.java:257)
     at org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:813)
     at TransformationApp.XSLTTransformServlet.MyTransform(XSLTTransformServlet.java:79)
     at TransformationApp.XSLTTransformServlet.doGet(XSLTTransformServlet.java:39)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
     at org.apache.tomcat.core.Handler.service(Handler.java:287)
     at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
     at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:812)
     at org.apache.tomcat.core.ContextManager.service(ContextManager.java:758)
     at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213)
     at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
     at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
     at java.lang.Thread.run(Thread.java:484)
Several articles hinted at setting the factory namespace attribute to TRUE. I have tried that but same results. Here is the code :
static Document document;
DocumentBuilderFactory factory =
DocumentBuilderFactory.newInstance();
//factory.setNamespaceAware(true);
//factory.setValidating(true);
try {
File stylesheet = new File(argv[0]);
File datafile = new File(argv[1]);
DocumentBuilder builder = factory.newDocumentBuilder();
document = builder.parse(datafile);
// Use a Transformer for output
TransformerFactory tFactory =
TransformerFactory.newInstance();
StreamSource stylesource = new StreamSource(stylesheet);
Transformer transformer = tFactory.newTransformer(stylesource);
DOMSource source = new DOMSource(document);
StreamResult result = new StreamResult(System.out);
transformer.transform(source, result);
} catch (TransformerConfigurationException tce) {
// Error generated by the parser
System.out.println ("\n** Transformer Factory error");
System.out.println(" " + tce.getMessage() );
// Use the contained exception, if any
Throwable x = tce;
if (tce.getException() != null)
x = tce.getException();
x.printStackTrace();
} catch (TransformerException te) {
// Error generated by the parser
System.out.println ("\n** Transformation error");
System.out.println(" " + te.getMessage() );
// Use the contained exception, if any
Throwable x = te;
if (te.getException() != null)
x = te.getException();
x.printStackTrace();
} catch (SAXException sxe) {
// Error generated by this application
// (or a parser-initialization error)
Exception x = sxe;
if (sxe.getException() != null)
x = sxe.getException();
x.printStackTrace();
} catch (ParserConfigurationException pce) {
// Parser with specified options can't be built
pce.printStackTrace();
} catch (IOException ioe) {
// I/O error
ioe.printStackTrace();
Any help would be greatly appreciated.

I don't know that this is true, but i think the problem is the classpath.
The runtime has his own parser. This parser is befor your xalan.lib in the classpath and the
parser from the runntime don't support namespace.
Try Tomcat 4.
Regard Dietmar

Failed transformation xml-rfc to rfc

Hi,
I have to scenario rfc to jdbc sync, SAP MI <-> XI, but when I executed the rfc, i don´t have problem in SXMB-MONI, but returned the dump in MI " Failed transformation xml-rfc to rfc". What happen?
Tks.

The error isnt logged in SMXB_MONI because it happens in Adapter Engine, which is in java stack (and SXMB_MONI is in abap stack). Therefore you won't be able to see the error there.
Go to Runtime WorkBench, Message Monitoring and check the errored message there. Open the details screen and check the Audit Log for futher information about the error you got.
Regards,
Henrique.

Transforming XML source to (X)HTML StreamResult outputs long comment

Hi,
I'm using javax.xml.transform.* to transform XML data into an XHTML page. The XML data represents a document (contains information about headers, paragraphs, related pages, etc.) and an XSL file is used to properly transform that data into an XHTML compatible file. All transformations go just as they should, however, the XHTML output contains a very lenthy comment about elements and attributes concerning HTML. Obviously, I do not want this comment in my final output. As a side note: I'm using a StreamSource(File) for the XML data source, a StreamSource(File) for the XSL file and a StreamResult(HttpServletResponse.getOutputStream()) for the HTML output. I'm not sure wether the problem is with using a StreamResult directly (rather than a SAXResult), or because I'm outputting directly to the servlet output stream. All input and output is in UTF-8, and the HttpServletResponse has been configured using setCharacterEncoding("UTF-8") and setContentType("text/html").
Everything works fine, except I get this stinkin' long comment, which I want gone.
Thanks,
Yuthura

I get the following result.html file (properly transformed and displayed in my browser, except for the comment):




















































 ... (more to come)

How can I transform XML-DB to Relational DB?

How can I transform XML-DB to Relational DB?
I want to transform Oracle 9i XML-DB to Oracle 8i R-db
please tell me how to do this .
thank you

hi
good
its idoc_xml or idoc_xml_transform
go through the below link hope it ll help you to solve your problem
Check with below link :
Re: IDOCS_OUTPUT_IN_XML_FORMAT -- IDOCS_OUTPUT_TO_FILE
Re: any function module to write-xml schema of a idoctype to an internal table
/people/michal.krawczyk2/blog/2005/11/13/xi-how-to-check-your-idocs-on-a-web-page-from-sapgui -> this will help you
thanks
mrutyun^

Transform XML and display xsl:message

Hi,
I have a simple method to transform XML. My XSLT has <xsl:message> to help debugging while transforming. How do I access the messages to System.out.printLn?
public static Document transformXML(Document xmlDoc, Document xslDoc) throws XMLHelperException {
          try {
               TransformerFactory factory = TransformerFactory.newInstance();
               Transformer transformer = factory.newTransformer(new DOMSource(xslDoc));
               DOMResult result = new DOMResult();
               transformer.transform(new DOMSource(xmlDoc), result);
               org.w3c.dom.Node resultNode = result.getNode();
               if (resultNode instanceof Document) return (Document)resultNode;
               else return result.getNode().getOwnerDocument();
          } catch (TransformerConfigurationException ex) {
               throw new XMLHelperException("Unable to perform transform " + ex.getLocationAsString(), ex);
          } catch (TransformerException ex) {
               throw new XMLHelperException("Unable to perform transform " + ex.getLocationAsString(), ex);
     }thanks for the help.
Edited by: bonekrusher on Mar 8, 2008 2:27 PM
Edited by: bonekrusher on Mar 8, 2008 2:27 PM

public class XForm {
     public static void main(String[] args) throws Exception {
          InputStream xslStream = null;
          InputStream xmlStream = null;
          try {
               TransformerFactory tf = TransformerFactory.newInstance();
               xslStream = new BufferedInputStream(new FileInputStream(args[1]));
               Transformer t = tf.newTransformer(new StreamSource(xslStream));
               tf.setErrorListener(new ErrorListener() {
                    public void error(TransformerException ex) throws TransformerException {
                         ex.printStackTrace();
                    public void fatalError(TransformerException ex) throws TransformerException {
                         ex.printStackTrace();
                    public void warning(TransformerException ex) throws TransformerException {
                         ex.printStackTrace();
               xmlStream = new BufferedInputStream(new FileInputStream(args[0]));
               t.transform(new StreamSource(xmlStream), new StreamResult(System.out));
          } catch (Exception e) {
               e.printStackTrace();
          } finally {
               if (xslStream != null)
                    xslStream.close();
               if (xmlStream != null)
                    xmlStream.close();
<test>
     <sample try="yes">
          a
     </sample>
</test>
<xsl:transform version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xalan="http://xml.apache.org/xalan">
     <xsl:template match="/">
          <xsl:message terminate="no">got here</xsl:message>
          <xsl:apply-templates/>
     </xsl:template>
     <xsl:template match="*|@*">
          <xsl:copy>
               <xsl:apply-templates/>
          </xsl:copy>
     </xsl:template>
</xsl:transform>

IOError in IE but not in Firefox (possible crossdomain.xml problem)

Yesterday, I hopefully debugged a problem that is occuring for our application in IE but not in Firefox.
It has to do with accessing remote content from a separate domain.
In every aspect it APPEARS to be a crossdomain.xml issue but the fact that this issue only arrises in IE is what has prompted me to post here.
We have a solution in the works (bureaucratically speaking) but I want to double check here.
Our application is on domain "a.domain".
It access an xml file on "b.domain/xml/".
And finally (this is the tricky part) it also accesses an xml file at "b.domain/forwardingPath/" which is actually forwarded to "c.domain/xml/".
The crossdomain.xml is located at "b.domain/crossdomain.xml".
The request for "b.domain/xml/anXMLFile.xml" works without any problem.
The request for "b.domain/forwardingPath/anotherXMLFile.xml" succeeds in Firefox but not in IE (remember, the ACTUAL request is forwarded to "c.domain/xml/anotherXMLFile.xml").
In IE I get an IOError.
I believe we need an appropriate crossdomain.xml file also located at "c.domain/crossdomain.xml" and have put in that request. What I want to confirm is whether this understanding is correct. I am not a server-side person at all. It's all elves and fairies to me. And then finally, why the hell is this behavior inconsistent between IE and Firefox? Is the Firefox version of flash player violating its own security standards?!
I am cross-posting this at stack overflow. http://stackoverflow.com/questions/7395931/ioerror-in-ie-but-not-in-firefox-possible-cross domain-xml-problem

I've pinged our developers about this and here's what they have to say:
"We did some work for the plugin around redirects andhence the correct behavior on Firefox.
AFAIK, on IE we don't get notified of the redirect and can't participate in making security decisions during redirect scenarios. This behavior is out of our control.
There is a workaround documented in the AS3docs here: http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/system/LoaderCont ext.html#checkPolicyFile
Here is the pertinent paragraph:
Be careful with checkPolicyFile if you are downloading anobject from a URL that may use server-side HTTP redirects. Policy files arealways retrieved from the corresponding initial URL that you specify inURLRequest.url. If the final object comes from a different URL because of HTTPredirects, then the initially downloaded policy files might not be applicableto the object's final URL, which is the URL that matters in security decisions.If you find yourself in this situation, you can examine the value ofLoaderInfo.url after you have received a ProgressEvent.PROGRESS orEvent.COMPLETE event, which tells you the object's final URL. Then call theSecurity.loadPolicyFile() method with a policy file URL based on the object'sfinal URL. Then poll the value of LoaderInfo.childAllowsParent until it becomes true."
Chris

[svn:fx-trunk] 10229: Fixes for some transform effects problems.

Revision: 10229
Author:   [email protected]
Date:     2009-09-14 08:43:43 -0700 (Mon, 14 Sep 2009)
Log Message:
Fixes for some transform effects problems.
- We were not animating the postLayout properties in some cases where we should have, effectively pinning the object in place. We now animate those properties whenever applyChangesPostLayout is true.
- A copy/paste error meant that we did not animate the scaleZ property in cases where we should have.
- A problem in the transform code means that using a null transform center is not the same as a transform center which uses the transformX/Y/Z properties of the target object. We now force the creation/use of a transform center in all cases to avoid that problem.
QE notes: This breaks about a dozen tests in the transform effects area, but I believe the new results are correct and the tests/bitmaps should be changed.
Doc notes: None
Bugs: sdk-23177
Reviewer: Hans
Tests run: checkintests, Mustella transform effects
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-23177
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransform.as

Transformation XML problem.

Similar Messages

Maybe you are looking for