OC4J  XML Taglib Bug

With the OC4J XML Taglib, an XML document may be parsed and transformed
with the parsexml and transform tags.
<XML:transform href="catalog.xsl"
               fromXMLObjName = "XMLDocument" >
  <XML:parsexml  resource = "catalog.xml"
               toXMLObjName = "XMLDocument" > </XML:parsexml>           
</XML:transform>   If parsexml does not have a empty space in parsexml tags an error gets generated.
With
<XML:parsexml resource = "catalog.xml"
toXMLObjName = "XMLDocument" ></XML:parsexml>
error gets generated:
javax.servlet.jsp.JspException: Error applying stylesheet catalog.xsl Start of root element expected.

Hi Vohra,
I am also getting same error message, how did you resolved the issue?
When org.apache.xalan.xslt.Process java pacakage is called with xml file and xsl file as parameters getting following error.
XML-22108: (Error) Invalid Source - URL format is incorrect.
XML-22000: (Fatal Error) Error while parsing XSL file (no protocol: /usr/tmp/test.xsl).
Exception in thread "main" java.lang.NullPointerException
     at oracle.xml.parser.v2.DOMLocator.getPublicId(DOMLocator.java:101)
     at org.apache.xml.utils.DefaultErrorHandler.printLocation(DefaultErrorHandler.java:341)
     at org.apache.xalan.xslt.Process.main(Process.java:1091)
Kindly help me out to resolve the issue.
Thanks and Regards,
[email protected]
Vijay

Similar Messages

  • Problem with  Jdeveloper Embedded OC4J  XML parsing

    Hi all,
    I am having a problem getting jdeveloper to work well. If I use jdeveloper to build the WAR file for my app and I deploy to Tomcat, the app runs fine with no error.
    However, if I try to run my app within the jdeveloper, I get this error -
    08/06/10 19:11:10 com.ibatis.dao.client.DaoException: Error while configuring DaoManager. Cause: java.lang.RuntimeException: XML Parser Error. Cause: oracle.xml.parser.v2.XMLDOMException: invalid character [ in name
    Caused by: java.lang.RuntimeException: XML Parser Error. Cause: oracle.xml.parser.v2.XMLDOMException: invalid character [ in name
    08/06/10 19:11:10 at com.ibatis.dao.engine.builder.xml.XmlDaoManagerBuilder.buildDaoManager(XmlDaoManagerBuilder.java:112)
    08/06/10 19:11:10 at com.ibatis.dao.client.DaoManagerBuilder.buildDaoManager(DaoManagerBuilder.java:47)
    I have tried to turn off XML parsing within Jdeveloper but no luck. I don't understand why jdeveloper will be trying to implicitly parse the XML doc, and wont even do it well.
    Is there a way I can turn off Embedded OC4J XML parsing ? and let it just use the parser in the application ? I mean Tomcat works fine with this application.
    Please help !

    I think maybe you use wrong adf lib when deploying your project to the OC4J.
    You can update your oc4j in the jdev.[JDEV->Tools->ADF Runtime Installer-> Standalone OC4J].
    Good luck
    Hart

  • JSP TagLib Bug

    I took my taglib's and tried to move them
              over to get them working on 6.0.
              I now get an error:
              Parsing of JSP File '/showdate.jsp' failed:
              /showdate.jsp(1): Error in using tag library uri='date' prefix='/date.tld':
              There is no setter method for property 'datestring', for Tag class
              'com.almaer.taglib.date.ShowDateTag'
              probably occurred due to an error in /showdate.jsp line 1:
              <%@ taglib uri="/date.tld" prefix="date" %>
              However I do have a setDatestring() method. I have tried various taglibs
              that are in production working fine.
              Is this a known bug? Has anyone else run into this?
              I also find that precompile=true in weblogic.xml doesn't seem to do anything
              Who does the QA for this? ;)
              Dion
              Dion Almaer | [email protected]
              CustomWare | http://www.customware.com
              

    Thank you. I changed my setter to be setFoo() and have the attribute foo in
              my tag and it worked. For some reason some values don't work in there. I
              haven't worked out
              if the problem is a) having a variable x and then having a setX() or whether
              it has something to do with the properties of the name that you call it.
              Crazy.
              Dion
              "newsgroups.bea.com" <[email protected]> wrote in message
              news:[email protected]...
              > I encountered this problem several times. I don't know why. The setter
              > method is exactly there. Finally I changed the spelling of the properties
              > and setter method to solve this problem. It worked. I think there are some
              > words cannot be used as names of properties. It should be a bug of WL 6.0
              >
              > "Dion Almaer" <[email protected]> ¼¶¼g©ó¶l¥ó
              > news:[email protected]...
              > > I took my taglib's and tried to move them
              > > over to get them working on 6.0.
              > >
              > > I now get an error:
              > >
              > > Parsing of JSP File '/showdate.jsp' failed:
              > >
              >
              > --------------------------------------------------------------------------
              > --
              > > ----
              > >
              > > /showdate.jsp(1): Error in using tag library uri='date'
              > prefix='/date.tld':
              > > There is no setter method for property 'datestring', for Tag class
              > > 'com.almaer.taglib.date.ShowDateTag'
              > > probably occurred due to an error in /showdate.jsp line 1:
              > > <%@ taglib uri="/date.tld" prefix="date" %>
              > >
              >
              > --------------------------------------------------------------------------
              > --
              > > ----
              > >
              > >
              > > However I do have a setDatestring() method. I have tried various
              > taglibs
              > > that are in production working fine.
              > > Is this a known bug? Has anyone else run into this?
              > >
              > > I also find that precompile=true in weblogic.xml doesn't seem to do
              > anything
              > > :)
              > > Who does the QA for this? ;)
              > >
              > > Dion
              > > -------------------------------------------------------------
              > > Dion Almaer | [email protected]
              > > CustomWare | http://www.customware.com
              > >
              > >
              > >
              > >
              > >
              >
              >
              

  • Web.xml + taglib

    I am getting the following error when I compile my project. The project has both an http session listener and a taglib. This error comes when I have a <%@ taglib....%> directive in a JSP page. Any suggestions?
    Error(29,12): Invalid element 'listener' in content of 'web-app', expected elements '[servlet-mapping, session-config, mime-mapping, welcome-file-list, error-page, taglib, resource-env-ref, resource-ref, security-constraint, login-config, security-role, env-entry, ejb-ref, ejb-local-ref]'.

    Have you found a solution to your problem.
    I've been removing the <listener> tag entries from the web.xml file when I'm compiling the jsp's because I get the same error. I have listeners for the construction of listeners and the application context. I have to re-insert them back into the web.xml file and make the file read only to execute the project. Pain in the you know what :) if not does anyone else have a solution to this. I'm using JDev 9.0.2 and upgrading to 9.0.3 is not a solution...
    Thanks
    Will

  • Parsing String to XML Attribute bug

    Hello!
    I'm trying to convert String to org.w3c.dom.Document with javax.xml.parsers.DocumentBuilder, but when I check my XML Document after creating, I find that all the Attributes are like "" or "&#xa; ". Does anyone have some idea why that problem is and how it can be solved?
    Thanks a lot!
    Svigi

    There are lots of bug reports about Java 5's built-in XML parser screwing up on attribute values. Try forcing Java to use the current version of Xerces (download it) instead of whatever it has built in, if that seems to apply to you. On the other hand it's possible that the bug is in your code too.

  • Ejb-jar.xml generation bug?

    Hi,
    I noticed that TopLink seems to forget the tag <primkey-field> and put java.lang.Object instead of Integer in the tag <prim-key-class>?
    Is this an error from me?
    Vlad

    Hi,
    For a JEE5 EJB module, rather than using EJBGen, you can use WLS specific annotations for configuring common settings. If you follow the link below, you can see a list of supported EJB annotations. Disregard the fact that the documentation section title is WebLogic Kodo Annotations. That is incorrect and I've filed a bug for it.
    http://edocs.bea.com/wls/docs103/ejb30/annotations.html#wp1438036.
    Unfortunately, we don't yet support setting all weblogic-ejb-jar.xml configuration values via annoations so in some cases a weblogic-ejb-jar.xml is still required.
    You can hand edit your weblogic-ejb-jar.xml and the example you posted below should work fine.
    - Matt

  • Escape XML.vi bug?

    When I convert an empty 2D array of I32 to XML using Flatten To XML then run it through the Escape XML.vi the ouput string contains NULLs.
    It seems that the tags with no actual value in between causes a NULL (\00) character to be produced between the tags. Is this right or is it a bug?
    Test by sending the constant "" through the "Escape XML.vi" that comes with LabVIEW 6.1.

    Yes, this is a bug. The problem is in xml.llb\EscapeChars.vi. The problem is that when the XML In string is empty the while loop still runs once...which produces 0, the default value for a U8. This \00 is now added in between the val tags. To fix this VI just add a case to the case structure for 0 and pass the array straight through.
    This bug will be fixed in the next version of LV.

  • XML Comments Bug

    hey fellas
    I have almost wrapped up my project except for one stupid bug that am getting. I'm using Oracle XML parser for Java.9.0
    I am trying to add some xml comments in the output .xml file but it is giving trouble.
    My code:
    ====
    Comment comment =xmldocument.createComment("mary had a lazy lamb");
    xmldocument.appendNode(comment);
    =====
    Now comments are being added in the output xml file. BUT GUESS WHAT, Instead of putting the string like a usual comment in xml like -
    <!-- mary had a lazy lamb -->
    It is putting it like -
    <?#comment mary had a lazy lamb comments?> (exact code)
    This, inadverantly throws an error when I open the file using a browser.
    How to over come this.
    Thanks

    Hi Francine
    Thanks for the response.
    I am extremely sorry for writting incorrect code in my original post but I am using
    =======
    xmldocument.appendChild(comment);
    ========
    and not appendNode(comment);
    The program works fine and shows no error at run time.
    But the output file that is generated [using transform] shows the xml comment code as -
    <?#comment comments comments?> (exact code)
    and not as desired -
    <!-- comments -->
    It would be great if you can test and suggest something.
    Earlier I started with Crimson parser, then shifted to Xerces and finally to ODK XML parser. Both Crimson and Xerces give comment as desired but ODK API is giving the above undesired comment which cannot be interpreted correctly by the web browser. [ODK is preferable 'cuz of its superior processing speed].
    Thanks once again and anticipating a positive response from you.

  • XML Export Bug - Any workarounds?

    Before we go any further, I am running 5.0.3 and I HAVE created a bug report, but since I'm not expecting a new release (bug fix) in the next couple of days/weeks I was hoping the community here might have a workaround or know if there is something I am doing to cause this.
    I'm creating a new project with DSLR 1080p/25 settings.   I've also tried other 1080p/25 settings and it makes no difference.
    I import lots of DSLR 1080p/25 footage (from Canon DSLRs) and several audio only files from a Zoom, recorded at 48Khz.  All footage shows in the project correctly (1080p/25) and the footage shows at 48Khz.  So far so good.
    Drop the footage and audio on to a sequence and export to XML and send to PluralEyes. 
    Now, I've been using PluralEyes with FCP for a while and it's an excellent product - I really can't recommend it enough, and their tech support is also 1st class.  So, with this in mind, it was rather odd that the version for Premiere Pro wasn't syncing as well as the FCP version.  Following a few emails back and forth with Singular Software (PluralEyes) it turns out that some of the files (the audio files) are being exported to the XML file incorrectly.  They are being exported with a rate of 29.97 and not 25.  Not only is the frame rate incorrect, but the duration is set to match 29.97 and not 25.
    Here are some extracts from the XML:
    PPro Exported as :
    <rate>
    <timebase>30</timebase>
    <ntsc>TRUE</ntsc>
    </rate>
    <duration>252824</duration>
    <timecode>
    Should have been:
    <rate>
    <timebase>25</timebase>
    </rate>
    <duration>210897</duration>
    I am wondering if there is anything I could have done to cause this, maybe in the way I imported files or created projects / sequences etc, or if anyone knows of any work around to force PP to correctly interpret these files? 

    The Interpret Footage Option is disabled....

  • Xml finder bugs

    This happened in WLI 7.0.2
    I wanted to post a generic xml when task became ready. I wanted to do this for
    each task in current and future templates that other people in my group will design.
    I had written the xml and it was in my local drive.
    I tried to use the xml finder functionality for adding the xml to publish into
    the repository. It imports but garbles up the xml into a binary string. Due to
    this the original contents of the xml are lost.
    I have tried all kinds of ways to get an xml imported into the repository but
    it does not work. looks like the XML finder has bugs and it does not work.
    Has anyone encountered this issue?
    Thanks
    puneet

    This happened in WLI 7.0.2
    I wanted to post a generic xml when task became ready. I wanted to do this for
    each task in current and future templates that other people in my group will design.
    I had written the xml and it was in my local drive.
    I tried to use the xml finder functionality for adding the xml to publish into
    the repository. It imports but garbles up the xml into a binary string. Due to
    this the original contents of the xml are lost.
    I have tried all kinds of ways to get an xml imported into the repository but
    it does not work. looks like the XML finder has bugs and it does not work.
    Has anyone encountered this issue?
    Thanks
    puneet

  • XML Document from XML Schema Bug

    When an XML document is generated from an XML Schema the XML document does not have all the elements specified in the XML Schema. The XML document only has the root element.
    1. Register an XML Schema.
    2. Create an XML document with File>New>General>XML>XML Document from XML Schema. The "Generate only Required Elements" is unchecked.
    3. The XML document has only the root element.
    In JDeveloper 10.1.3 all the elements in the XML Schema get generated.

    Also, the component palette for the XML document generated from the XML Schema does not list all the elements in the XML Schema, only the root element is listed. Even if elements are specified as required in the XML Schema with minOccurs="1" and the "Generate only Required Elements" checkbox is selected only the root element gets generated.

  • [CS3][CS4][VB] XML, Markup - bug or next "cool" feature ?

    hi
    could anybody please check how it works in JS or AS - what do you get in XML structure - what is tagged - when you try to MarkUp character containing InLine graphic ? or Text object containing only one "character" - InLine graphics
    something like this:
    Set myPageItem = myText.PageItems.Item(a)
    Set myChar = myPageItem.Parent
    With myChart.AssociatedXMLElements.Item(1).Parent.XMLElements.Add("qqq")
         Call .Markup(myChar)
    End With
    robin
    www.adobescripts.co.uk

            Ok, I figured out the problem.  I had read that snippet before and tried it and it didn't work.  I then Dim'd artitem as a compoundpathitem instead of pathitem and it worked on the first iteration of the for each loop.   One the second trip through there was an invalid cast exception..but it had upsized the art!   So I just added try/catch to handle the error and it works!
    For future reference, anyone that reads this will need to add a reference to the CS4(or whichever version) type library COM object, change the hard coded file paths and it should convert from AI to SVG and Scale it up or down by replacing the 125,125 in the scale matrix by whatever percentage you'd like.   The Userinteractionlevel disables any warnings so that it runs automatic.
    Thanks again Carlos...while you didn't give me the exact code I needed, you pointed me at what I had previously dismissed due to a different error.
    -Mark
            Dim illusapp As New Illustrator.Application
            Dim illusdoc As Illustrator.Document
            Dim scalematrix As Illustrator.Matrix
            Dim artitem As Illustrator.CompoundPathItem
            Dim svgOpt = new illustrator.ExportOptionsSVG
            svgOpt.DTD = Illustrator.AiSVGDTDVersion.aiSVG1_0    
            illusapp.UserInteractionLevel = Illustrator.AiUserInteractionLevel.aiDontDisplayAlerts
                illusdoc = illusapp.Open("c:\test\test.ai")
                scalematrix = illusapp.GetScaleMatrix(125,125)
                Try
                    For Each artItem In illusapp.ActiveDocument.PageItems
                        artitem.Transform(scalematrix)
                    Next
                Catch
                End Try
                illusdoc.Export("C:\test\test.svg",Illustrator.AiExportType.aiSVG,svgopt)
                illusdoc.Close

  • Auto update of OC4J xml configuration files with JDev

    When using JDeveloper with source control (such as ClearCase), Is there a way to configure JDev to prompt the user to check-out the ejb-jar.xml, orion-ejb-jar.xml, web.xml, or application.xml files when JDev needs to update them but finds them to be read-only?
    I have found that if these xml files are not checked-out (read-only) and JDev needs to update them (such as when a new EJB is created), JDev does not notify the user that it cannot update them and it does not prompt the user to check them out of source control. Developers often forget that they need to manually check-out these XML files and perform an "update" on them, thus creating configuration problems.
    Please advise.
    Thank you.
    Matt Burton

    Matt,
    Not yet. We have similar requirements for other areas of JDeveloper. This is certainly on the list of enhancements.
    David Brown
    SCM Product Management

  • FOR ORACLE XML TEAM -- XML TOOLS BUG FIXING POLICY/RESPONSE TIME/RELEASE SCHEDULE

    Hi,
    The release of Oracle XML tools and utilities by Oracle XML team is a significant milestone and is definitely appreciated. However, as part of a large organization, some factors need to be clarified before using these utilities in production softwares.
    I have noticed that XML parsers and other utilities are now coming as part of other softwares like JDeveloper etc. Following are my questions to the Oracle XML team and urgent and prompt reply will be greatly appreciated.
    1. What is the XML tools support policy. Is it only OTN? Can we buy support? Are these utilities supported if large organizations have corporate server licenses. I have read at the XML site the XDK is fully and freely supported by Oracle Word Wide support. What does this mean?
    2. What is the release schedule for the XML tools?
    3. What is the response time?
    Once again, your help and prompt reply will be appreciated.
    Thanks.

    As you noted many of the Oracle XDK components are production. This means that if your company has an Oracle Server Support contract you will get the corresponding level of support for the production XDK components.
    If you don't have one, then OTN is your support resource. We will also have standalone support agreements in the future which you can purchase through the Oracle Store. The response time would be the same as for the server.
    There is not a specific release schedule for components on OTN as they have different development schedules.
    Oracle XML Team
    null

  • XML Portal Bug ??!!

    Hi, I'm writing this XML and XSL code and it's running perfectly on "XMLSPY" but when i use it on Oracle portal I receive the error the page could not be displayed
    plz fine the XML and XSL file hereunder:
    -----XML-----
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <?xml-stylesheet type="text/xsl" href="C:\WINNT\Profiles\sitel_em\Desktop\test.xsl"?>
    <dataset>
    <headlines code="PRESS/FR" language="">
    <headline storyid="999153468nL30462124" date="30 Aug 2001" time="08:37" lang="EN">
    <code>[G][RNP][PGE][PMF][EMK][FR][PRESS][LEN][RTRS][PRESS/FR]</code>
    <text>PRESS DIGEST - France - Aug 30</text>
    </headline>
    <headline storyid="999067370nL29426422" date="29 Aug 2001" time="08:43" lang="EN">
    <code>[G][RNP][PGE][PMF][EMK][FR][PRESS][LEN][RTRS][PRESS/FR]<VOWG.DE><EAUG.PA><FMTX.LN><SOGN.PA><FTE.PA><LYOE.PA><EDF.UL></code& gt;
    <text>PRESS DIGEST - France - August 29</text>
    </headline>
    <headline storyid="998890909nL27416527" date="27 Aug 2001" time="07:43" lang="EN">
    <code>[G][RNP][PGE][PMF][EMK][FR][PRESS][LEN][RTRS][PRESS/FR]<CRLP.PA><MRK.N><PHA.N><BAYG.DE><EAUG.PA><FTE.PA><TMM.PA><TECF.PA&gt ;<LAFP.PA></code>
    <text>PRESS DIGEST - France - Aug 27</text>
    </headline>
    <next_headline storyid="998891005nL2463852"/>
    </headlines>
    <headlines code="SPO FR AND" language="">
    <headline storyid="999158007n0948512" date="30 Aug 2001" time="09:53" lang="EN">
    <code>[SPO][RNP][DNP][PSP][EMK][GB][IT][FR][SOCC][LEN][RTRS]</code>
    <text>Soccer-Blanc arrives but move to United still not finalised</text>
    </headline>
    <headline storyid="999145169nN29197209" date="30 Aug 2001" time="06:19" lang="EN">
    <code>[SPO][AUF][RNP][DNP][PSP][EMK][TENN][US][BE][AU][HR][BR][CZ][CH][ES][RU][FR][JP][SE][DE][EC][IT][WEU][EUROPE][LEN][RTRS]</code>
    <text>UPDATE 3-Tennis-Treble chasing Rafter sprints through</text>
    </headline>
    <headline storyid="999126109nN29285117" date="30 Aug 2001" time="01:01" lang="EN">
    <code>[SPO][RNP][DNP][PSP][EMK][TENN][US][FR][WEU][EUROPE][ES][LEN][RTRS]</code>
    <text>Tennis-Clement wins battle of the giant-killers</text>
    </headline>
    <next_headline storyid="999126105nAX2242321"/>
    </headlines>
    <headlines code=".PAFR" language="">
    <headline storyid="999160767nL30307903" date="30 Aug 2001" time="10:39" lang="FR">
    <code>[FA][FB][DNP][PMF][STX][FR][WEU][EUROPE][LFR][RTRS][.PAFR]<ORA.PA><FTE.PA><ACCP.PA><STM.PA><CGEP.PA></code>
    <text>La Bourse de Paris hisite avant la BCE, pataquhs sur France Tel</text>
    </headline>
    <headline storyid="999156701nL30458520" date="30 Aug 2001" time="09:31" lang="FR">
    <code>[FA][DNP][PMF][STX][FR][WEU][EUROPE][LFR][RTRS][.PAFR]<FTE.PA><ORA.PA><CARR.PA><ACCP.PA><CGEP.PA></code>
    <text>La Bourse de Paris en bref - Ouverture en repli de 0,16%</text>
    </headline>
    <session_id>fDpk9U-048Yng6*jaZCOEvkIqUBPF3JPmvM*D8n-KaN9p</session_id>
    </headlines>
    </dataset>
    ------XSL-----
    <?xml version="1.0"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/TR/WD-xsl">
    <xsl:template match="/">
    <html>
    <link rel="stylesheet" type="text/css" href="c:\files\projects\reuters files\reuters xsl\reuters.css">
    <body>
    <!-- <xsl:variable name="session" select="dataset/headlines/session_id"/> -->
    <table>
    <th>Revue de presse</th>
    <th>Sport</th>
    <th>Bourse de Paris</th>
    <th>Business</th>
    <th>Politique</th>
    <th>Monde</th>
    </table>
    <xsl:for-each select="dataset/headlines">
    <xsl:if test=".[@code='PRESS/FR']">
    <a name="part1">
    <h3>Revue de presse</h3>
    <table>
    <xsl:for-each select="headline">
    <tr><td class="DATENEWS">
    <xsl:value-of select="@date"/>
    <xsl:value-of select="@time"/>
    </td><td class="NEWS">
    <a >
    <xsl:attribute name="href"> http://ri2.rois.com/ppppp/CTIB/RI3APINEWS?TEXT=<xsl:value-of select="@storyid"/>
    </xsl:attribute>
    <xsl:value-of select="text"/>
    </a></td></tr>
    </xsl:for-each>
    </table>
    </a>
    </xsl:if>
    <xsl:if test=".[@code='SPO FR AND']">
    <a name="part2">
    <h3>Sport</h3>
    <table>
    <xsl:for-each select="headline">
    <tr><td class="DATENEWS">
    <xsl:value-of select="@date"/>
    <xsl:value-of select="@time"/>
    </td><td class="NEWS">
    <a >
    <xsl:attribute name="href"> http://ri2.rois.com/ppppp/CTIB/RI3APINEWS?TEXT=<xsl:value-of select="@storyid"/>
    </xsl:attribute>
    <xsl:value-of select="text"/>
    </a>
    </td></tr>
    </xsl:for-each>
    </table>
    </a>
    </xsl:if>
    <xsl:if test=".[@code='.PAFR']">
    <a name="part3">
    <h3>Bourse de Paris</h3>
    <table>
    <xsl:for-each select="headline">
    <tr><td class="DATENEWS">
    <xsl:value-of select="@date"/>
    <xsl:value-of select="@time"/>
    </td><td class="NEWS">
    <a >
    <xsl:attribute name="href"> http://ri2.rois.com/ppppp/CTIB/RI3APINEWS?TEXT=<xsl:value-of select="@storyid"/>
    </xsl:attribute>
    <xsl:value-of select="text"/>
    </a>
    </td></tr>
    </xsl:for-each>
    </table>
    </a>
    </xsl:if>
    <xsl:if test=".[@code='JOUR']">
    <a name="part4">
    <h3>Business</h3>
    <table>
    <xsl:for-each select="headline">
    <tr><td class="DATENEWS">
    <xsl:value-of select="@date"/>
    <xsl:value-of select="@time"/>
    </td><td class="NEWS">
    <a >
    <xsl:attribute name="href"> http://ri2.rois.com/ppppp/CTIB/RI3APINEWS?TEXT=<xsl:value-of select="@storyid"/>
    </xsl:attribute>
    <xsl:value-of select="text"/>
    </a>
    </td></tr>
    </xsl:for-each>
    </table>
    </a>
    </xsl:if>
    <xsl:if test=".[@code='POL FR AND']">
    <a name="part5">
    <h3>Politique</h3>
    <table>
    <xsl:for-each select="headline">
    <tr><td class="DATENEWS">
    <xsl:value-of select="@date"/>
    <xsl:value-of select="@time"/>
    </td><td class="NEWS">
    <a >
    <xsl:attribute name="href"> http://ri2.rois.com/ppppp/CTIB/RI3APINEWS?TEXT=<xsl:value-of select="@storyid"/>
    </xsl:attribute>
    <xsl:value-of select="text"/>
    </a>
    </td></tr>
    </xsl:for-each>
    </table>
    </a>
    </xsl:if>
    <xsl:if test=".[@code='G FR AND']">
    <a name="part6">
    <h3>Monde</h3>
    <table>
    <xsl:for-each select="headline">
    <tr><td class="DATENEWS">
    <xsl:value-of select="@date"/>
    <xsl:value-of select="@time"/>
    </td><td class="NEWS">
    <a >
    <xsl:attribute name="href"> http://ri2.rois.com/ppppp/CTIB/RI3APINEWS?TEXT=<xsl:value-of select="@storyid"/>
    </xsl:attribute>
    <xsl:value-of select="text"/>
    </a>
    </td></tr>
    </xsl:for-each>
    </table>
    </a>
    </xsl:if>
    </xsl:for-each>
    </body>
    </link>
    </html>
    </xsl:template>
    </xsl:stylesheet>
    Plz advice and if you want i will send you by mail the complete document
    Best Regards

    Your XML file seems not well-formed. Would you send the document?

Maybe you are looking for