Xsl:include msg - document following root element must be well-formed

I am getting the following message when I try to execute a transaction that takes an XML file & transforms it.  The message is:
"[ERROR]: XSLTransform error: javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: org.xml.sax.SAXParseException: The markup in the document following the root element must be well-formed."
The transaction loads an xml input file, and then transforms it.  The transformation stylesheet does some formatting to the xml.  The stylesheet has an include in it that adds an element to the output. 
Input XML data
<?xml version="1.0" encoding="UTF-8"?>
<Rowset>
    <Row>
        <ItemNo>00000000001884304</ItemNo>
        <ItemDesc>Test Item Description</ItemDesc>
    </Row>
</Rowset>
Expected output:
<?xml version="1.0" encoding="UTF-8"?>
<Item>
    <Items ItemDesc="Test Item Description" RawItemNo="00000000001884304" dotties="...................." editedItemNo="1884304" supernova="**********" />
</Item>
If I point the <xsl:include to a web folder on a test box, it will read & translate the data into the expected output.  However, when I have both the initial stylesheet and the include stylesheet in the same Web folder in MII, I get the above message.  If the URL is any different, it generates an IO error. 
The initial stylesheet is
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" >
<xsl:output method="xml" />
<xsl:include href="http://myserver:myport/XMII/CM/foldername/testcalls_2.xsl"/>
<xsl:variable name="wrkitem" select="//ItemNo"/>
<xsl:template match="Row">
     <xsl:call-template name="RowEdit"/>
</xsl:template>
<xsl:template name="RowEdit" match="Row">
      <Item>
     <xsl:element name="Items" use-attribute-sets="RowChange">
           </xsl:element>
       </Item>
</xsl:template>
<xsl:attribute-set name="RowChange">
     <xsl:attribute name="RawItemNo">
           <xsl:value-of select="//ItemNo"/>
     </xsl:attribute>
     <xsl:attribute name="editedItemNo">
          <xsl:call-template name="removeLeadingZeros">
               <xsl:with-param name="originalString" select="$wrkitem"/>
          </xsl:call-template>
     </xsl:attribute>
     <xsl:attribute name="ItemDesc">
               <xsl:value-of select="//ItemDesc"/>
     </xsl:attribute>
     <xsl:attribute name="dotties">
          <xsl:call-template name="dots">
                     <xsl:with-param name="count" select="20"/>
              </xsl:call-template>
     </xsl:attribute>
     <xsl:attribute name="supernova">
          <xsl:call-template name="stars">
          </xsl:call-template>
     </xsl:attribute>
</xsl:attribute-set>
  <xsl:template name="dots">
        <xsl:param name="count" select="1"/>
      <xsl:if test="$count > 0">
        <xsl:text>.</xsl:text>
        <xsl:call-template name="dots">
          <xsl:with-param name="count" select="$count - 1"/>
        </xsl:call-template>
      </xsl:if>
  </xsl:template>
<xsl:template name="removeLeadingZeros"> 
  <xsl:param name="originalString"/> 
  <xsl:choose> 
    <xsl:when test="starts-with($originalString,'0')"> 
      <xsl:call-template name="removeLeadingZeros"> 
        <xsl:with-param name="originalString"> 
          <xsl:value-of select="substring-after($originalString,'0' )"/> 
        </xsl:with-param> 
      </xsl:call-template> 
    </xsl:when> 
    <xsl:otherwise> 
      <xsl:value-of select="$originalString"/>
    </xsl:otherwise> 
  </xsl:choose> 
</xsl:template>
</xsl:stylesheet>
and the stylesheet being called by the xsl:include -
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template name="stars" match="Item">
<Stars>
     <xsl:element name="BBB">
          <xsl:text>**********</xsl:text>
     </xsl:element>
</Stars>
</xsl:template>
</xsl:stylesheet>
FYI, both of the stylesheets above are in the same folder on the WEB tab in MII.  The full name (properties tab) is:
foldername/WEB/Test/stylesheet.xsl
Also, I am able to browse & view each of them in IE.  The url they are at is:
http://server:port/XMII/CM/foldername/test/stylesheet.xsl
Both stylesheets appear to be well-formed.
If I use any other syntax other than the full URL, the error it generates is an IO Exception on the included stylesheet.  The markup message above makes me believe that it is at least attempting to handle the included stylesheet. 
In the Link editor of the xsl Transformation Incoming tab, there are two assignments being made.
1.  Transform property
object= xsl_transformation_0
property=Transform
expression="db://foldername/WEB/Test/stylesheet.xsl" (this is the initial, not included stylesheet)
Link type=Assign Value
2.  Input property
object= xsl_transformation_0
property=Input
Expression=testitems_0.XmlContent
Link type=Assign XML
Running MII 12.0
Thoughts?  Any input appreciated.

In the first one you have two namespaces both with the same prefix.
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" and xmlns:xsi="http://xxxxxx/webservices/sites/"
Thanks,
Gaurav Jain
Flex SDK Team
http://www.gauravj.com/blog

Similar Messages

  • The markup in the document following the root element must be well-formed.

    I have my XML root element that looks like this:
    <DataResponseOfListOfSite xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www
    .w3.org/2001/XMLSchema" xmlns="http://xxxxxx/webservices/sites/">
    and I get the error "The markup in the document following the root element must be well-formed."
    If I use this it works fine:
    <DataResponseOfListOfSite xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www
    .w3.org/2001/XMLSchema" xmlns:xsi="http://xxxxxx/webservices/sites/">
    Does anyone know why I have to have the xmlns:xsi="" instead of just xmlns=""
    If I paste this XML into any validator, it says that its good, so I dont know why Flex is complaining about it.

    In the first one you have two namespaces both with the same prefix.
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" and xmlns:xsi="http://xxxxxx/webservices/sites/"
    Thanks,
    Gaurav Jain
    Flex SDK Team
    http://www.gauravj.com/blog

  • The markup in the document preceding the root element must be well-formed

    Hi,
    Each time I add some library, something serious happens to my NetBeans5.5 and Tomcat 5.5.17. This time I added jsf-facelets.jar and now nothing is being deployed. I m getting following exception
    javax.servlet.ServletException: Error Parsing /Dept.jsp: Error Traced[line: 1] The markup in the document preceding the root element must be well-formed.
         javax.faces.webapp.FacesServlet.service(FacesServlet.java:202)
    Is there any special procedure to follow to add libraries?
    Plz help.

    Facelets is XHTML. XHTML is XML-HTML. XML require strict well-formness of the tags. I.e. every tag should be correctly nested and closed.
    I would say, read the Facelets Developer Documentation: http://www.google.com/search?q=facelets+developer+documentation

  • Warnings about root element must be well-formed

    Hey, I just downloaded and am getting running with FlexMetrics.  I'm running this from the ant taskdef.  When I run it, I get what looks to be valid and fine XML reports generated, but I also get a bunch of warnings, each of which reads:
    [flex-metrics] Oct 25, 2010 11:54:00 AM de.bokelberg.flex.parser.AS3Scanner$XMLVerifier verify [flex-metrics] WARNING: The markup in the document preceding the root element must be well-formed. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Error HandlerWrapper.java:195) [flex-metrics] com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrappe r.java:174) [flex-metrics] com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.jav a:388)
    The taskdef element is pretty standard:
    <taskdef name="flex-metrics" classname="com.adobe.ac.pmd.metrics.ant.FlexMetricsAntTask" classpath="${flexpmd.libs}/flex-pmd-metrics-ant-task-${flexpmd.version}.jar">
        <classpath>
            <pathelement location="${flexpmd.libs}/flex-pmd-files-${flexpmd.version}.jar" />
            <pathelement location="${flexpmd.libs}/flex-pmd-metrics-${flexpmd.version}.jar" />
            <pathelement location="${flexpmd.libs}/as3-plugin-utils-${flexpmd.version}.jar" />
            <pathelement location="${flexpmd.libs}/as3-parser-${flexpmd.version}.jar" />
            <pathelement location="${flexpmd.libs}/as3-parser-api-${flexpmd.version}.jar" />
            <pathelement location="${flexpmd.libs}/commons-lang-2.4.jar" />
            <pathelement location="${flexpmd.libs}/flex-pmd-ruleset-api-${flexpmd.version}.jar" />
            <pathelement location="${flexpmd.libs}/pmd-4.2.5.jar" />
            <pathelement location="${flexpmd.libs}/dom4j-1.6.1.jar"/>
        </classpath>
    </taskdef>
    References to this look like this:
    <flex-metrics sourcedirectory="${home.project}\src" outputfile="${deploy.dir}/metrics/project.javancss.xml" />
    So I'm not doing anything weird or crazy with it.  I get that error message repeated 42 times.  I can't really seem to correlate that number with anything in my project, i.e. we've got more than 42 mxml files (59 of them), we've got more than 42 AS3 files, etc.  So I'm not really sure what it's hitting 42 times to come up with that error.
    Any ideas on what this might indicate would be greatly appreciated!

    My working theory is that it chokes on instances of the Vector Object (http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/Vector.html) but I have yet to verify that conclusively.

  • TLD Error:The markup in the document preceding the root element must...

    Hello, I am new to using the Tag Libraries, i am getting the following error which seems to be in my treeTag.tld file, I am pasting the error message and the treeTag.tld at the bottom of this message. Any help is much appreciated.
    Apache Tomcat/4.0.1 - HTTP Status 500 - Internal Server Error
    type Exception report
    message Internal Server Error
    description The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request.
    exception
    org.apache.jasper.JasperException: XML parsing error on file /TreeTag/treeTag.tld: (line 5, col 1): The markup in the document preceding the root element must be well-formed.
         at org.apache.jasper.parser.ParserUtils.parseXMLDocument(ParserUtils.java:218)
         at org.apache.jasper.compiler.TagLibraryInfoImpl.parseTLD(TagLibraryInfoImpl.java:283)
         at org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:219)
         at ***************************************************
    Here is my treeTag.tld file
    <!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">
    - <taglib>
         <tlibversion>1.1</tlibversion>
         <jspversion>1.1</jspversion>
         <shortname>Tree taglib</shortname>
         <uri>http://www.servletsuite.com/servlets/treetag</uri>
         <info>Tree tags</info>
         - <tag>
              <name>createTree</name>
              <tagclass>com.cj.tree.createTree</tagclass>
              <bodycontent>JSP</bodycontent>
              <info>Creates HTML-based tree view</info>
         </tag>
         - <tag>
              <name>addNode</name>
              <tagclass>com.cj.tree.addNode</tagclass>
              <bodycontent>JSP</bodycontent>
              <info>adds node</info>
              - <attribute>
                   <name>code</name>
                   <required>true</required>
                   <rtexprvalue>true</rtexprvalue>
              </attribute>
         </tag>
    </taglib>
    Regards,
    Navin Pathuru.

    You might make sure - if you havent already - that you are using the must up to date jsp version

  • The markup must be well-formed.

    Hi,
    I am beginer in SAX and Java.
    I am tring to read Information from not well formed XML File.
    When I try to use SAX or DOM Parser then I have this error:
    The markup in the document following the root element must be well-formed.
    My XML File looks like this:
    <format type="filename" t="13241">0;W650;004;AG-Erzgeb</format>
    <format type="driver" t="123412">001;023</format>
    Can I force SAX or DOM to parse not well-formed XML files?
    Thank you for your help.
    Haythem
    Edited by: Haythem on Mar 23, 2010 3:52 AM

    Thank you it helps.
    I used ByteArrayInputStream and InputStream to add <root>... </root> for the file on the fly and it is well formed now.
    String rootB ="<wrapper>";
         String rootE= "</wrapper>";
         Vector<InputStream> v = new Vector<InputStream>();
         byte[] bArray = rootB.getBytes();
         byte[] eArray = rootE.getBytes();
         ByteArrayInputStream baisB = new ByteArrayInputStream(bArray);
         ByteArrayInputStream baisE = new ByteArrayInputStream(eArray);
         InputStream fisFile = new FileInputStream(file);
         v.addElement( baisB );
         v.addElement( fisFile );
         v.addElement( baisE );
         InputStream combined = new SequenceInputStream(v.elements());
            Document doc = docBuilder.parse (combined);....
    Edited by: Haythem on Mar 25, 2010 4:15 AM
    Edited by: Haythem on Mar 25, 2010 4:17 AM
    Edited by: Haythem on Mar 25, 2010 4:18 AM

  • Geting a "must be well-formed" error in a JSP

    I have a JSP file and it compiles and runs just fine, but JSC gives me the following error:
    There are errors in the project.
    You must resolve these problems.
    results.jsp:1: The markup in the document preceding the root element must be well-formed.
    on this line in the JSP (Line 1 of file)
    <%@page import="com.phonebook.User" %>
    Not sure why or how to fix it or what JSC is expecting...

    <%@page import="com.phonebook.User" %>
    should be after the root element declaration
    and the syntax for xml is<jsp:directive.page import="className"/>
    or import=package.Class

  • Document not well formed

    Hi-
    one of the things i liked about java is it had a stack trace
    that went to the moon and it helped
    you find where your error is.
    if i run my code in PHP IDE it is well formed enough and
    spits out the right result.
    If i upload it to my webhost set to shared environment it
    keeps coming up document not well formed.
    I dont really understand what code causes this message as
    there is no line number.
    I tried to make sure my xml started with the xml tag and had
    a root and closing tags.
    Does flex 3 offer any more insight with diagnostic messages
    as to where the problems may
    surface from? the message seems to indicate "url loader on
    complete" .
    where would you look if you got a url loader on complete?
    i am really stuck. it is frustrating to see it work in php
    and then not on the web host :-)
    (error msg. below)
    thanks for any assistance,
    jim
    [RPC Fault faultString="Error #1088: The markup in the
    document following the root element must be well-formed."
    faultCode="Client.CouldNotDecode" faultDetail="null"]
    at mx.rpc.http::HTTPService/
    http://www.adobe.com/2006/flex/mx/internal::processResult()[C:\dev\enterprise_bali\framewo rks\mx\rpc\http\HTTPService.as:856
    at mx.rpc::AbstractInvoker/
    http://www.adobe.com/2006/flex/mx/internal::resultHandler()[C:\dev\enterprise_bali\framewo rks\mx\rpc\AbstractInvoker.as:165
    at
    mx.rpc::Responder/result()[C:\dev\enterprise_bali\frameworks\mx\rpc\Responder.as:48]
    at
    mx.rpc::AsyncRequest/acknowledge()[C:\dev\enterprise_bali\frameworks\mx\rpc\AsyncRequest. as:82]
    at
    DirectHTTPChannel.as$139::DirectHTTPMessageResponder/completeHandler()[C:\dev\enterprise_ bali\frameworks\mx\messaging\channels\DirectHTTPChannel.as:359]
    at
    flash.events::EventDispatcher/flash.events:EventDispatcher::dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at flash.net::URLLoader/flash.net:URLLoader::onComplete()

    Hi-
    i think i found out why i couldnt get my code to work. the
    local machine had different things enabled that werent
    enabled on the web host for PHP. i asked the admin to enable
    PHP 5 includes the XSL extension by default and can be
    enabled by adding the argument --with-xsl[=DIR].
    it looks suspicious.
    thanks,
    jim

  • Xjc throwing exception that "document not well formed"

    I have the following DTD file given in the sample code saved as item.dtd
    <?xml version='1.0' encoding='utf-8'?>
    <!-- Simple DTD -->
    <!ELEMENT item_list (item_info*)>
    <!ELEMENT item_info (name, price)>
    <!ELEMENT name (#PCDATA)>
    <!ELEMENT price (#PCDATA)>
    and the following xjs file as given in the sample code
    saved as item.xjs
    <xml-java-binding-schema>
    <element name="item_list" type="class" root="true"/>
    <element name="item_info" type="class"/>
    </xml-java-binding-schema>
    now from command prompt when I run the following command, it throws the following error.
    c:\Some-folder\ xjc item.dtd item.xjs
    the EXCEPTION thrown is :
    The markup in the document preceding the root element must be well-formed. line 4 of item.dtd
    The FULL TRACE is(if anybody is interested to see).. PLEASE HELP ME OUT.
    Thanks
    Gagan
    TRACE STARTS HERE:
    parsing a schema...
    The markup in the document preceding the root element must be well-formed.
    line 4 of item.dtd
    Exception in thread "main" ::file:///C:/RBML/xml-java/item.dtd:file:///C:/RBML/x
    ml-java/item.dtd:file:///C:/RBML/xml-java/item.dtd:4:3:The markup in the document preceding the root element must be well-formed.

    NO i dont think so..
    as you could see the code pasted in the first instance. the only diffrence is that you are using double quotes.(I tried that as well)
    I hope you are referring to item.dtd file not item.xjs file
    Thanks
    Gagan

  • Xjc ,dtd, xjs giving problem "document not well formed"

    I have started the thread again.
    Anyway.
    I have an item.dtd file (same as in sample tutorial).. I have reduced some components to simplify..when it was not working
    item.dtd file:
    <!ELEMENT ITEM (NAME)>
    <!ELEMENT NAME (#PCDATA)>
    item.xjs file:
    <xml-java-binding-schema>
    <element name="ITEM" type="class" root="true"/>
    </xml-java-binding-schema>
    when i run from command prompt:
    C:\RBML\xjc item.dtd item.xjs
    It throws up an error
    The markup in the document preceding the root element must be well-formed. line 1 of item.dtd
    I am not able to understand the error..how it can be rectified.
    PLEASE HELP..!
    I have tried adding the following line to item.dtd but doesnot work
    <?xml version="1.0" encoding ="utf-8"?>
    I had also tried removing redundant spaces and blank lines.
    PLEASE HELP
    Thanks
    Gagan

    I'm have done the same for schemas.But giving the error as
    "[ERROR] Unexpected <xml-java-binding-schema> appears at line 1 column 26
    line 1 of item.xjs"
    my xjs file is
    "<xml-java-binding-schema>
    <element name="item_list" type="class" root="true"/>
    <element name="item_info" type="class"/>
    </xml-java-binding-schema>"
    andmy schema is
    "<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <xsd:element name="item_list">
    <xsd:complexType>
         <xsd:sequence>
              <xsd:element name="item_info" maxOccurs="unbounded">
                   <xsd:complexType>
                        <xsd:sequence>
                             <xsd:element name="name" type="xsd:string"/>
                             <xsd:element name="price" type="xsd:decimal"/>
                        </xsd:sequence>
                   </xsd:complexType>
         </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>".
    Pls help me

  • JDOMException: root element required in a well-formed document

    Ok, my XML file looks something like this:
    <?xml version="1.0" ?>
    <this>
    <that></that>
    </this>
    ... and my Java code to build a JDOM object model from the XML file (Xerces-parsed) looks somethings like this:
    Document theDoc;
    SAXBuilder theBuilder;
    InputSource = theSource;
    theBuilder = new SAXBuilder("org.apache.xerces.parsers.SAXParser");
    theDoc = builder.build(theSource);
    Now, when I compile and run, I get a JDOMException that looks something like this:
    org.jdom.JDOMException: Error on line 1 of document : The root element is required in a well-formed document.
    What's up with that?

    (1) Thanks for taking the time. I'm not sure how I could make more than one root element. All I know is, in my XML file, the element tag that comes right after the <? xml version="1.0" ?> line has the same name as the very last tag in the file (with a "/" added before the name). There are no other elements in the file with that name, so I figure that makes it (ie. <this></this>) the root element of my document. N'est pas?
    (2) I have some more info since I originally posted:
    I added the following line:
    "System.err.println(e.getCause());"
    ... to the catch() area that throws the JDOMException - like follows:
    try {
    theCurrentDocument = builder.build( docFile ); // builder is an object created with <i>builder = new SAXBuilder("org.apache.xerces.parsers.SAXParser");</i>
    docType_CurrentDoc = theCurrentDocument.getDocType();
    root_CurrentDoc = theCurrentDocument.getRootElement();
    catch( org.jdom.JDOMException e ) {
    System.err.println(e); // Caused the original JDOMException from my first post
    System.err.println(e.getCause()); // Line I added since my first post
    The amended code above produced an extra line of output to the console:
    "java.security.AccessControlException: access denied (java.io.FilePermission \myfile.xml read)"
    Which I take to mean that I have to sign my applet. Is there any way around doing that? Because I don't want to if I don't have to.

  • Org.xml.sax.SAXParseException: Document root element is missing.

    Hi,
    I am trying to get the portal login id from a weblogic server based application from iplaet portal server.
    I get this follwoing error
    org.xml.sax.SAXParseException: Document root element is missing.
    at com.sun.xml.parser.Parser.fatal(Parser.java:2817)
    at com.sun.xml.parser.Parser.fatal(Parser.java:2805)
    at com.sun.xml.parser.Parser.parseInternal(Parser.java:493)
    at com.sun.xml.parser.Parser.parse(Parser.java:284)
    at com.sun.xml.tree.XmlDocument.createXmlDocument(XmlDocument.java:226)
    at com.iplanet.portalserver.util.XMLParser.<init>(XMLParser.java:70)
    at com.iplanet.portalserver.naming.share.NamingResponseParser.<init>(NamingResponseParser.java:33)
    at com.iplanet.portalserver.naming.share.NamingResponse.parseXML(NamingResponse.java:74)
    at com.iplanet.portalserver.naming.WebtopNaming.updateNamingTable(WebtopNaming.java:174)
    at com.iplanet.portalserver.naming.WebtopNaming.getNamingProfile(WebtopNaming.java:155)
    at com.iplanet.portalserver.naming.WebtopNaming.getServiceURL(WebtopNaming.java:57)
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:534)
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:520)
    at com.iplanet.portalserver.session.Session.getSession(Session.java:414)
    at jsp_servlet.__eatonPortalLogin._jspService(__eatonPortalLogin.java:155)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    <May 19, 2004 9:01:12 AM EDT> <Error> <HTTP> <101017> <[ServletContext(id=4873279,name=ematrix,context-path=/ematrix)] Root cause of ServletException
    com.iplanet.portalserver.session.SessionException
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:539)
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:520)
    at com.iplanet.portalserver.session.Session.getSession(Session.java:414)
    at jsp_servlet.__eatonPortalLogin._jspService(__eatonPortalLogin.java:155)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    Any help/pointers will be appreciated.
    Ashish

    Just for anyone else who hits this problem: I encountered the same issue with an XML document that XMLSpy claims is quite well formed. I opened the document in a hex editor, and there at the from was a three-byte byte order marker - the marker that I believe the UTF-8 standard says is optional. I removed these three bytes, and the file was parsed correctly.
    In this case, the XML file was created using a Microsft DOM (save).
    My solution is to make the java parser - as I use it - a tad more robust: Open the file and create an input stream - a pushback input stream. Read the first three bytes; if they are NOT a BOM, then push those bytes back. Now - in any case - give the stream to the parser to read.
    try {
    // Open file for reading.
    f = new File(path);
    FileInputStream fis = new FileInputStream(f);
    PushbackInputStream pis = new PushbackInputStream(fis);
    byte[] buf = new byte[3];
    pis.read(buf, 0, 3);
    if (! (buf[0] == 0x00EF) && (buf[1] == 0x00BB) && (buf[2] == 0x00BF) ) {
         pis.unread(buf, 0, 3);
    builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
    doc = builder.parse(pis);
    catch (Exception x) {
         x.printStackTrace();
    }

  • xsl:include in XSL Workshop

    I am trying to use <xsl:include> for some proxy stylesheet. I use the form
    <xsl:include href="filename.xsl" />
    I get the following error when process the stylesheet:
    'Bad URI found while including/importing file: no protocol: filename.xsl'
    Currently I am just working with the workshops, I have not deployed the xsl stilesheets yet to the server.
    Everything works as expected in XMLSpy.
    Does anybody have an example of a working <xsl:include>?

    what about putting that file in the respository? or set up the XMLDIR and put it there? I have never done it but just a though.
    Ben

  • Document type declaration for root element type "web-app" must end with ' '

    I am attempting to deploy an application (.war file) using the Sun Access Manager Agent installed, (Reference http://docs.sun.com/app/docs/doc/819-3201/6n5eht3k4?a=view -near the bottom) and I get this error:
    Error loading deployment descriptors for ajacs Line 3 Column 19 -- The document type declaration for root element type "web-app" must end with '>'.
    Here is the relavent code:
    <!DOCTYPE web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
    http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <web-app>
    <filter>
    <filter-name>Agent</filter-name>
    <filter-class> com.sun.identity.agents.filter.AmAgentFilter </filter-class>
    </filter>
    <filter-mapping>
    <filter-name>Agent</filter-name>
    <url-pattern>/*</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>INCLUDE</dispatcher>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>ERROR</dispatcher>
    </filter-mapping>
    <display-name>AJACS</display-name>
    <welcome-file-list>
    <welcome-file>frameSet.jsp</welcome-file>
    </welcome-file-list>
    etc...
    Now, when I remove the parts that http://docs.sun.com/app/docs/doc/819-3201/6n5eht3k4?a=view said to add, it deploys just like it used to deploy- just fine with no errors. However, I add that code and it breaks.
    Note: The code was a straight copy/paste, so if there is any error in the code, it is because it's written incorrectly on the Sun doc website.
    Any help would be MUCH appreciated. Thanks!

    Well, if that was pasted on one line, it would be:
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
    So it's supposed to be that way. I just tried it with the extra quotes, and no dice...

  • Org.xml.sax.SAXParseException: Document root element "taglib", must match D

    hi
    using tomcat 4
    and jdf1.5
    i am getting bellow error
    org.xml.sax.SAXParseException: Document root element "taglib", must match DOCTYPE root "null".

    Check your web.xml once again.

Maybe you are looking for

  • I keep getting this message:  Adobe Photoshop CC 2014 has stopped working.  A problem caused the program to stop working correctly.  Then it shuts down the program.

    I keep getting this message when I try to open my new Adobe Photoshop.  The main screen comes on and a box for the tutorials then this.  "Adobe Photoshop CC 2014 has stopped working.  A problem caused the program to stop working correctly."  When I s

  • Airplay - Video to TV and audio to wireless speakers.

    My house is Apple House...  MAC Pros, iPads, iPods, Iphones, Apple TV, etc...for every member of our family.  I have a choice between moving away from Apple to Sonos for audio or make Airplay work logically.  Which is streaming audio to speakers when

  • How to create an Editable report?

    I want to generate one report using BEx Analyser as my client’s requirement. What the client’s requirement is, when he refreshes the query, he wants the query to be get refreshed and another user-editable sheet need to be get created. And the calcula

  • Server 4.0.3 unable to log in

    I have just installed the update server app 4.0.3 When it installed all my users were missing, and i am no longer able to join the server on a client computer. I have rebuilt my DNS and restarted all my services. I am running a MacMini (10.10.2) serv

  • Exporting to quicktime & error

    2 questions: I have a 95-minute FCP project, which I broke into two parts, and the first 50-min part still tops out at over 11 GB when I export Quicktime movie. I do want the best possible resolution for my purposes. Do I need to break it down to 20-