XML having a JSP as XSL stylesheet ...

Hi,
In WLS 5.1 SP6, I have a XML which uses as XSL stylesheet a JSP served by WebLogic (<?xml/stylesheet href="style.jsp?order=3"?>
It appears that, when I try to pass more than one parameter to my JSP (i.e. "style.jsp?order=3&value=1"), the XML page does not "recognize" it anymore ... I have to pack all my parameters in a single string, pass it to my JSP and then parse it, which is quite ugly. Has somebody an explanation for this ? Thanks

Perhaps you need to encode the '&' in the stylesheet processing instruction.
<?xml/stylesheet href="style.jsp?order=3&value=1"?>
"Stephane Jantzen" <[email protected]> wrote in message
news:3a6ff593$[email protected]..
>
Hi,
In WLS 5.1 SP6, I have a XML which uses as XSL stylesheet a JSP served byWebLogic (<?xml/stylesheet href="style.jsp?order=3"?>
>
It appears that, when I try to pass more than one parameter to my JSP(i.e. "style.jsp?order=3&value=1"), the XML page does not "recognize" it
anymore ... I have to pack all my parameters in a single string, pass it to
my JSP and then parse it, which is quite ugly. Has somebody an explanation
for this ? Thanks
>

Similar Messages

XML forms error: Error applying XSL stylesheet to XML

hi,
I created XML forms for news and 2 weeks ago everything was working right, but today when i try to see a preview of the project i get this error:
XML - Forms
<b>Error applying XSL stylesheet to XML</b>
com.sapportals.wcm.WcmException: com.sap.engine.lib.xml.util.NestedException: Variable '$Sap' has not been bound to a value
at com.sapportals.wcm.service.pipeline.Pipeline.handle(Pipeline.java:284)
at com.sapportals.wcm.service.pipeline.XSLTPipeline.handle(XSLTPipeline.java:118)
at com.sapportals.wcm.service.xmlforms.transformation.Transformer.pipeIt(Transformer.java:133)
at com.sapportals.wcm.service.xmlforms.transformation.Transformer.transform(Transformer.java:105)
at com.sapportals.wcm.service.xmlforms.transformation.Transformer.transform(Transformer.java:77)
at com.sapportals.wcm.service.xmlforms.transformation.HtmlGenerator.getHtmlStream(HtmlGenerator.java:122)
at com.sapportals.wcm.service.xmlforms.transformation.Transformation.render(Transformation.java:391)
I really don't know where this come from is there somebody that can help me?
i tried to change the paths of the project cause i also got this:
<b>java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key xmsg_project_not_exist</b>
at java.util.ResourceBundle.getObject(ResourceBundle.java:326)
at java.util.ResourceBundle.getObject(ResourceBundle.java:323)
at java.util.ResourceBundle.getString...
Hope that somebody can give me some help. Please it is urgent we have to deploy the site this week.
thanks a lot in advance.
Regards,
MJ

Hi All,
Anybody could find the cause for this?
I'm also facing the same problem now when I try to see the preview for Edit Form. It's working fine with RederList Form. Earlier everything was fine. If somebody has got the solution for this, pls help me out. This is very urgent. Thankyou very much in advance.
Thanks & BR,
Ram Marni.
[email protected]

XML data not displayed with XSL

I have just started learning XML so bear with me. I have a xml document that I created and want to use a stylesheet to display it in html but it doesn't seem to be working. Here is the xml file:
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="XSL\myXSL.xsl" type="text/xsl"?>
<GstBk:Book xmlns:GstBk="http://www.testurl.com">
<GstBk:Guest>
<GstBk:Address>
<GstBk:Name>John Doe</GstBk:Name><GstBk:From>Anywhere USA</GstBk:From>
</GstBk:Address>
</GstBk:Guest>
</GstBk:Book>
And here is the xsl document:
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:GstBk="http://www.testurl.com"
version="1.0"
>
<xsl:template match="GstBk:Book">
<html>
<head>
<title>Guest Book</title>
</head>
<body>
<xsl:apply-templates />
</body>
</html>
</xsl:template>
<xsl:template match="GstBk:Guest">
Name = <xsl:value-of select="GstBk:Name" />
</xsl:template>
</xsl:stylesheet>
But the only data I get on the browser is:
Name =
Can anyone see something wrong with my files? I have downloaded examples from the net and they seem to work. I even compared them to my files and can't see anything obviously different. Any ideas?
Thanks

<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
                xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:GstBk="http://www.testurl.com">
   <xsl:template match="GstBk:Book">
      <html>
         <head>
            <title>Guest Book</title>
         </head>
         <body>
            <xsl:apply-templates />
         </body>
      </html>
   </xsl:template>
   <xsl:template match="GstBk:Guest">
      Name = <xsl:value-of select="GstBk:Address/GstBk:Name" />
   </xsl:template>
</xsl:stylesheet>This style sheet with the xml you provided works for me. I use Xalan 2.1.0 for the transformation with the command line: java org.apache.xalan.xslt.Process -in your.xml -xsl your.xsl
and I get this for the output:
<html xmlns:GstBk="http://www.testurl.com">
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Guest Book</title>
</head>
<body>
      Name = John Doe
</body>
</html>If you still see a different result, let me know what your environment is.

Error applying XSL stylesheet to XML

Hi,
after installed SPS 21 into portal we are facing an issue:
A contentadministrator wants to publish a new newsfact in portal, but get the following error message:
Error applying XSL stylesheet to XML:
com.sapportals.wcm.WcmException: com.sap.engine.lib.xml.util.NestedException: Variable '$system_config_activateClipboard' has not been bound to a value
     at com.sapportals.wcm.service.pipeline.Pipeline.handle(Pipeline.java:284)
Hope that somebody can give me some help.
thanks a lot in advance.
Regards,
Edwin

Hi Lorcan,
You help solved our issue, thanks a lot.
After generate the existing xml project with the Forms builder in the Content Management,
the contentadministratoris able to produce a new newsfact without errors
Regards, edwin
Posts: 123
Registered: 11/29/04
Forum Points: 346
Solved problem (10)
Very helpful answer (6)
Helpful answer (2)
   Re: Error applying XSL stylesheet to XML
Posted: Apr 19, 2010 11:13 AM    in response to: Edwin Theuns           Reply
Hi Edwin,
You need to recompile the xml forms project and that should resolve the issue. Unfortunately there is no alternative solution in such a scenario.
Regards,
Lorcan.

How to create a Layout Template of XSL Stylesheet (XML) type

Hello,
I am new to OBIEE. I need to generate layout template to be of XSL Stylesheet (XML) format. ( output report to be in XML format )
Please share if anybody know How to create a Layout Template of XSL Stylesheet (XML) type for BI Publisher.
Waiting for your reply

Look at this, for example.
http://xlspe.com/news.php?item.15.1

Xsl/stylesheet transformation problem in soap response(usinf xmlx-tags.tld)

Hi,
I have problem in transforming the soap response using xmlx-tags.tld.....
I was not able to read the <EmpName> value from the returned xml...
The stylesheet / xsl does not return any elements if I use other then "/" in match
attribute : <xsl:template match="/">
here is my soap call and stylesheet in JSP:
<x:xslt media="html">
<x:xml>
<ws:soap ttl="360000">
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
... making soap call here...
</soap:Body>
</soap:Envelope>
</ws:soap>
</x:xml>
<x:stylesheet media="html">
<xsl:stylesheet version='1.0' xmlns:xsl='http://www.w3.org/1999/XSL/Transform'>
<xsl:output method="xmll" omit-xml-declaration="no"
doctype-public="-//W3C//DTD HTML 4.0 Transitional//EN" indent="yes" />
<xsl:template match="GetEmpResult">
<html>
<body>
Result: <B>Symbol <xsl:value-of select="EmpName"/></B>
</body
</html>
</xsl:stylesheet>
</x:stylesheet>
</x:xslt>
the SOAP response looks like this:
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<GetEmpResponse xmlns="http://ws.cdyne.com/">
<GetEmpResult>
<EmpID>string</EmpID>
<EmpName>string</EmpName>
<SalAmount>decimal</SalAmount>
<Error>boolean</Error>
</GetEmpResult>
</GetEmpResponse>
</soap:Body>
</soap:Envelope>
I tried all the possibilities of template matches, but not succeeded....
Can somebody help me the correct <xsl:template> to access EmpName from the above
SOAP responses...
regards
Vijay

Hi,
Dynamic xslt are not quite supported in OSB, there are some approaches that may be helpful for your case though...
Have a look at these...
http://atheek.wordpress.com/2011/12/21/using-xalanevaluate-to-parametrize-xpath/
http://beatechnologies.wordpress.com/2010/12/01/dynamic-xquery-in-oracle-service-bus/
Let me know how you go...
Cheers,
Vlad

Howto add static text in xsl stylesheet

Hi,
I'am having problems trying to write a static text to a fixed length file using the file adapter.
I'am using the FlatStructure sample provided.
When I run the sample, there's no problem... But when I remove the mapping from tns:State <-> fix:State (in addr1Toaddr2.xsl) and change the fix:State to a static text (Set Text option in right mouse popup menu) then this text will NOT show up in the written fixed length file.
My addr1Toaddr2.xsl looks like this:
<?xml version="1.0" encoding="windows-1252"?>
<?oracle-xsl-mapper

<mapSources>
<source type="XSD">
<schema location="file://D:/OraBPELPM_2/integration/bpelpm/orabpel/samples/tutorials/121.FileAdapter/FlatStructure/address-csv.xsd"/>
<rootElement name="Root-Element" namespace="http://xmlns.oracle.com/pcbpel/demoSchema/csv"/>
</source>
</mapSources>
<mapTargets>
<target type="XSD">
<schema location="file://D:/OraBPELPM_2/integration/bpelpm/orabpel/samples/tutorials/121.FileAdapter/FlatStructure/address-fixedLength.xsd"/>
<rootElement name="Root-Element" namespace="http://xmlns.oracle.com/pcbpel/demoSchema/fixedLength"/>
</target>
</mapTargets>

?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://xmlns.oracle.com/pcbpel/demoSchema/csv" xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd" xmlns:fix="http://xmlns.oracle.com/pcbpel/demoSchema/fixedLength" xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap" xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc" exclude-result-prefixes="xsl xsd tns nxsd fix ldap xp20 bpws ora orcl">
<xsl:template match="/">
<fix:Root-Element>
<xsl:for-each select="/tns:Root-Element/tns:Address">
<fix:Address>
<fix:Name>
<xsl:value-of select="tns:Name"/>
</fix:Name>
<fix:Street>
<xsl:value-of select="concat(tns:Street1,' ',tns:Street2)"/>
</fix:Street>
<fix:City>
<xsl:value-of select="string('C2345678901')"/>
</fix:City>
<fix:State>
<xsl:text disable-output-escaping="no">D2345678901
</xsl:text>
</fix:State>
<fix:Country>
<xsl:value-of select="string('E234567')"/>
</fix:Country>
</fix:Address>
</xsl:for-each>
</fix:Root-Element>
</xsl:template>
</xsl:stylesheet>
Note:
The construct "<xsl:value-of select="string('E234567')"/>" is my 'patch'to write a static text.
Can you tell me what I'am doing wrong? Or is this a bug...
greetings,
Jan.

Hi ,
I am assuming you are using Oracle JDeveloper XSL Mapper for designing the XSL. Currently , our XSL Mapper has a limitation due to that whenever you add any static text to target node in mapper, it adds an extra "\n" with that static text. And so our Native format translator doesn't find the definition for that and that's why it doesn't get printed in the file.
Workaround [although little painful] is remove those extra "\n" after you finish your XSL design.
We are working to fix this issue asap.
HTH.
Thanks,
Rakesh

Unused xml tags being printed in xsl transformation

Hi,
I'm just starting out with xslt, and I am have a small problem with unused data being added into the html output from an xsl transformation. The data set is very small and the transdorm is not complicated, but when I do a
<xsl:template match="aa/bb/cc">
<title><xsl:value-of select"."/></title>
</xsl:template>
cc will be used as the title, but aa/bb/dd and aa/bb/ee will be printed to the output stream directly after the </title> as standard text.
<title>cc</title>ddee
I have include the xml, the transform and the html source recieved at the end of this mail.
Any help would be appreciated.
Cheers
Simon
<webpage>
<project>
    <title>Katrin</title>
    <version>Version 1.0</version>
    <start_date>01/01/2003</start_date>
</project>
</webpage>
<xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:fo="http://www.w3.org/1999/XSL/Format">
    <xsl:output method="html"/>
    
    <xsl:template match="/">
        <html>
            <head>
                <xsl:apply-templates mode="head"/>
            </head>
            
            <body>
                <xsl:apply-templates/>
            </body>
        </html>
    </xsl:template>
    
    <xsl:template match="webpage/project/title" mode="head">
        <title><xsl:value-of select="."/></title>
    </xsl:template>
    
    <xsl:template match="webpage/project/title">
        <h1><xsl:value-of select="."/></h1>
    </xsl:template>
    <xsl:template match="webpage/project/version">
        <div align="right" style="font-size : 8pt; font-family : Times serif; padding-top : 4; padding-bottom : 4; color : red"><xsl:value-of select="."/></div>
    </xsl:template>
    <xsl:template match="webpage/project/start_date">
        <div align="left" style="font-size : 8pt; font-family : Times serif; padding-top : 4; padding-bottom : 4; color : blue"><xsl:value-of select="."/></div>
    </xsl:template>
</xsl:stylesheet>
<html xmlns:fo="http://www.w3.org/1999/XSL/Format">
   <head>
      <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Katrin</title>Version 0.101/01/2003</head>
   <body>
      <h1>Katrin</h1>
      <div align="right" style="font-size : 8pt; font-family : Times serif; padding-top : 4; padding-bottom : 4; color : red">Version 0.1</div>
      <div align="left" style="font-size : 8pt; font-family : Times serif; padding-top : 4; padding-bottom : 4; color : blue">01/01/2003</div>
   </body>
</html>

You had a couple of errors in your xsl. It should read something like:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:template match="*|/"><xsl:apply-templates/></xsl:template>
<xsl:template match="text()|@*"><xsl:value-of select="."/></xsl:template>
<xsl:template match="*|/">
<html>
<head><title>Greeting</title></head>
<body>Words of greeting:
<b><i><u><xsl:value-of select="greeting"/></u></i></b>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
This produces the result you are looking for:
<html>
<head>
<title>Greeting</title>
</head>
<body>Words of greeting:
<br>
<b>
<i>
<u>Hello World.</u>
</i>
</b>
</body>
</html>
null

How can i include javascript functions in my xsl stylesheet

Dear all,
i want to write a small java script function in my stylesheet. i am using oracles xml parser.
i used the <xsl:script inplements-prefix...> tag but of no use.
what is the right way of doing this

I would like this too, as it would save a lot of time using icons in the form of icon fonts.

Can i view an xsl stylesheet? My message log is formatted and I can't read it.

I have found a message log in My Downloads. When I try to read it, it's an xsl stylesheet. What is this? Why is it in this format, and can I convert it so I can read it? Thanks--need details--I don't know much about computers!

An XSL stylesheet usually contains layout rules for an XML data file, but not actual data. Maybe what you found is actually the XML data file, which refers to the XSL style sheet?
If it doesn't help to open it in a Firefox tab, try opening it in Internet Explorer or Microsoft Excel. Both have some capability to decode XML.

Xml/html to jsp - problem with quotes in attribute values

I am trying to convert a static html document into a jsp using an xsl stylesheet, but run into problems trying to use the jsp expression syntax inside of attribute values.
Here is a sample of the source file:
<input type="text" name="firstName" value=""/>
Here is what I want the resulting jsp file to look like:
<input type="text" name="firstName" value="<jsp:expression>customer.getField("firstName") </jsp:expression>">
Here is what part of my stylesheet looks like:
<xsl:template match="input">
<xsl:copy>
<xsl:copy-of select="@type"/>
<xsl:copy-of select="@name"/>
<xsl:attribute name="value">
<xsl:text disable-output-escaping="yes"><jsp:expression></xsl:text>
<xsl:text disable-output-escaping="yes">customer.getField(</xsl:text>
<xsl:text disable-output-escaping="yes">"</xsl:text>
<xsl:value-of select="@name"/> ")
<xsl:text disable-output-escaping="yes">")</xsl:text>
<xsl:text disable-output-escaping="yes"></jsp:expression></xsl:text>
</xsl:attribute>
</xsl:copy>
</xsl:template>
The problem i have is with the <%= customer.getField("firstName") %>. I have tried several different ways of inserting the double quotes around firstName, but no matter what I try, it always uses the entity reference instead of actually putting the " character. The jsp container will not accept the entity.
I am assuming that the problem is with trying to place double quotes inside of an attribute value. Any ideas how to get around this?
Thanks
David

Which App Server are you using?
You should just be able to escape the double quotes.
If that doesn't work, it's a bug in the app-server.
Alternatively, you can use single quotes around the
attribute value.
Hope that helps,
AlexSorry, I'm an idiot. By escaping you meant the unicode character escape "\u0022". I had not tried that. However, once i realized what you meant, I tried it, and it worked. Thanks for your help.
David

Portability problem for XSL stylesheet

Hi,
I created a xsl stylesheet and a java program which just do the normal xml transformation. however, they works fine in my windows XP environment, but once i move them to my Red hat (linux) environment, they stop working... why this happening? from the exception error, the problem occurs when the stylesheet is loaded. some friends suggest that i should try to use different xslt processors, but how should i do this in the run time?
(I am currently using Xerces2.6.2 to vaildate xml file and do the transformation)
Thanks for any help

You should look at the stacktrace from the exception and fix your problem based on what you see there.
Or you could post it here so we don't have to guess...

Accessing lookup table from XSL stylesheet

HI Gentlemen,
Given two XMLTYPE tables: a Master and a Lookup. The Lookup table consists merely of {key, value} pairs. I am about to display Master table contents--subtrees selected from one big XMLTYPE column. The display process is governed by an appropriate XSL stylesheet. Master table elements have data only in their attributes. For example: <time U="2"/> which means that the value of the Unit attribute is 2, meaning "Minute" according to the Lookup table.
My question is: Does anybody of you know a fast and safe method to SELECT from the Master AND Lookup (inner join, as in a pure relational environment), thereby REPLACING the key value with its MEANING (textual interpretation). This would be extremely important as numeric codes do not have meaning to the user. User-friendly behavior requires that all important information be displayed at once. (Note that I have nothing against modifying my stylesheet to query the Lookup table as well, if no straightforward master-detail querying technique exists.)
Please give me an idea if you have.
Thank you in advance, kind regards:
Miklos HERBOLY

HI odie,
Here is the stuff you requested. I admit, it is fairly abundant, but you will see the structure and the main points. Some of the elements are multiple-occurrence, hence the XMLTABLE() solution was no good because of the large number of generated rows. The stylesheet would be ideal to display embedded "nested collections".
Please let me know if you have anything for me.
Thanks, regards
Miklos
HERE ARE THE XMLTYPE MASTER TABLE CONTENTS. TABLE IS NON-SCHEMA-BASED.
=====================================================================
SQL> select * from z;
XML_DOCUMENT
<?xml version="1.0" encoding="WINDOWS-1252"?>
<?xml-stylesheet type="text/xsl" href="file://c:/XSL/ziffer.xsl"?>
<ehd:ehd xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:ehd/go/001" xmlns:ehd="urn:ehd/001" ehd_versio
n="1.20">
<ehd:header>
<ehd:id EX="E7F454A3-0F6E-460e-A495-BBBBBBBBBBB3" RT="1.2.276.0.76.3.1.1"/>
<ehd:version_nbr V="1"/>
<ehd:document_type_cd V="851"/>
<ehd:service_tmr V="2006-07-01..2007-12-31"/>
<ehd:origination_dttm V="2006-05-03"/>
<ehd:provider>
<ehd:provider.type_cd V="KV" S="1.2.276.0.76.5.104" SV="1.0"/>
<ehd:person>
<ehd:id EX="3223" RT="2.3.5.3.T.e.s.t" RTV="1.10"/>
<ehd:person_name>
<ehd:nm>
<ehd:GIV V="Hans"/>
<ehd:PFX V="von"/>
<ehd:FAM V="Mustermann"/>
</ehd:nm>
</ehd:person_name>
<ehd:organization.nm V="KV Hessen"/>
<ehd:addr>
<ehd:STR V="Ottostr."/>
<ehd:HNR V="12"/>
<ehd:ZIP V="50859"/>
<ehd:CTY V="Köln"/>
</ehd:addr>
<ehd:telecom V="tel:030-4005-2121 begin_of_the_skype_highlighting 030-4005-2121 end_of_the_skype_highlighting begin_of_the_skype_highlighting 030-4005-2121 end_of_the_skype_highlighting"/>
</ehd:person>
<ehd:organization>
<ehd:id EX="46" RT="1.2.276.0.76.5.233"/>
</ehd:organization>
</ehd:provider>
<ehd:interface>
<ehd:id EX="SDEBM" RT="1.2.276.0.76.5.109" RTV="1.0"/>
<ehd:interface.nm V="Gebührenordnungsstammdatei / Satzart 851"/>
<ehd:version V="01.30"/>
</ehd:interface>
</ehd:header>
<ehd:body>
<gnr_liste>
<gnr V="01700V" USE="46" USE-DOMAIN="1.2.276.0.76.5.233" VT="2006-05-03">
<allgemein>
<gueltigkeit>
<service_tmr V="2006-07-01.."/>
<effective_tmr V="2006-07-01.."/>
</gueltigkeit>
<legende>
<kap_bez V="1.7" DN="Gesundheits- und Früherkennungsuntersuchungen, Mutterschaftsvorsorge, Empfängnisregelun
g und Schwangerschaftsabbruch (vormals Sonstige Hilfen)">
<bereich V="II" DN="Arztgruppenübergreifende allgemeine Leistungen"/>
<kapitel V="1" DN="Allgemeine Leistungen"/>
<abschnitt V="7" DN="Gesundheits- und Früherkennungsuntersuchungen, Mutterschaftsvorsorge, Empfängnisregel
ung und Schwangerschaftsabbruch (vormals Sonstige Hilfen)"/>
</kap_bez>
<kurztext V="Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a."/>
<langtext V="Grundpauschale für Fachärzte für Laboratoriumsmedizin, Mikrobiologie und Infektionsepidemiologi
e, Transfusionsmedizin und ermächtigte Fachwissenschaftler der Medizin für die Erbringung von Laborleistungen gemäß den
Richtlinien des Gemeinsamen Bundesausschusses über die ärztliche Betreuung während der Schwangerschaft und nach der En
tb indung (Mutterschafts-Richtlinien) und/oder der Richtlinien des Gemeinsamen Bundesausschusses zur Empfängnisregelung
und zum Schwangerschaftsabbruch bei Probeneinsendung, "/>
<quittungstext V="Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a."/>
</legende>
<anmerkungen_liste>
<anmerkung V="Die Leistung nach der Nr. 01100 ist nicht berechnungsfähig, wenn Sprechstunden vor 07:00 Uhr o
der nach 19:00 Uhr stattfinden oder Patienten zu diesen Zeiten bestellt werden."/>
<anmerkung V="Im Rahmen der unvorhergesehenen Inanspruchnahme des Vertragsarztes ist die Leistung nach der N
r. 01100 auch dann nur einmal berechnungsfähig, wenn es sich um eine Gruppenbehandlung handelt."/>
<anmerkung V="Die Leistung nach der Nr. 01100 ist ausschließlich bei kurativer Behandlung berechnungsfähig."
/>
</anmerkungen_liste>
<leistungsinhalt>
<komplex V="OBLIGAT">
<leistung V="Persönlicher Arzt-Patienten-Kontakt im organisierten Not(fall)dienst"/>
</komplex>
<komplex V="FAKULTATIV">
<leistung V="Beratung und Behandlung bis zu 10 Minuten Dauer,"/>
<leistung V="2...Beratung und Behandlung bis zu 10 Minuten Dauer,"/>
<leistung V="3...Beratung und Behandlung bis zu 10 Minuten Dauer,"/>
</komplex>
<komplex V="FAKULTATIV">
<leistung V="In Anhang 1 aufgeführte Leistungen,"/>
</komplex>
</leistungsinhalt>
<bewertung_liste>
<bewertung V="5595" U="1" U-DOMAIN="1.2.276.0.76.5.236">
<leistungserbringerart V="1" S="1.2.276.0.76.5.234" SV="1.02"/>
<leistung_typ V="GL"/>
</bewertung>
<bewertung V="2797.5" U="1" U-DOMAIN="1.2.276.0.76.5.236">
<leistungserbringerart V="2" S="1.2.276.0.76.5.234" SV="1.02"/>
<leistung_typ V="GL"/>
</bewertung>
</bewertung_liste>
<zeitbedarf_liste>
<zeit V="21" U="2" U-DOMAIN="1.2.276.0.76.5.238">
<leistung_typ V="AL"/>
</zeit>
</zeitbedarf_liste>
<pruefzeit V="1" U="2" U-DOMAIN="1.2.276.0.76.5.238">
<zeitprofilart V="3" S="1.2.276.0.76.5.228" SV="1.00"/>
</pruefzeit>
<rlv V="0" S="1.2.276.0.76.5.241" SV="1.00"/>
<leistungsgruppe V="10" S="1.2.276.0.76.5.227" SV="1.00"/>
</allgemein>
<bedingung>
<fachgruppe_liste V="true">
<versorgungsbereich V="2" S="1.2.276.0.76.5.237" SV="1.01">
<fachgruppe V="110" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="111" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="112" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="303" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="357" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="501" S="1.2.276.0.76.5.114" SV="1.00"/>
<fachgruppe V="532" S="1.2.276.0.76.5.114" SV="1.00"/>
</versorgungsbereich>
</fachgruppe_liste>
<anzahlbedingung_liste>
<bezugsraum V="1" U="7" U-DOMAIN="1.2.276.0.76.5.226">
<anzahl V="1"/>
</bezugsraum>
</anzahlbedingung_liste>
<abr_best V="je Behandlungsfall mit Auftragsleistung(en) der Abschnitte 1.7.4 und/oder 1.7.5"/>
</bedingung>
<regel>
<ausschluss_liste>
<bezugsraum V="1" U="7" U-DOMAIN="1.2.276.0.76.5.226">
<gnr_liste V="false">
<gnr V="12220" DN="Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a."/>
<gnr V="12225" DN="Grundpauschale für Vertragsärzte aus nicht in der Nr. 12220 aufgeführten Arztgruppen
bei Probeneinsendung"/>
</gnr_liste>
</bezugsraum>
</ausschluss_liste>
</regel>
<kv V="46" S="1.2.276.0.76.5.233" SV="1.01">
<kennzeichen>
<arztpraxis V="1"/>
</kennzeichen>
<kv_bewertung_liste>
<kv_bewertung V="100" U="1" U-DOMAIN="1.2.276.0.76.5.236">
<leistungserbringerart V="2" S="1.2.276.0.76.5.234" SV="1.02"/>
</kv_bewertung>
<kv_bewertung V="150" U="1" U-DOMAIN="1.2.276.0.76.5.236">
<leistungserbringerart V="1" S="1.2.276.0.76.5.234" SV="1.02"/>
</kv_bewertung>
</kv_bewertung_liste>
</kv>
<vdx>
<gkv_kontenart_liste>
<gkv_kontenart V="530" S="1.2.276.0.76.5.258"/>
<gkv_kontenart V="463" S="1.2.276.0.76.5.258"/>
</gkv_kontenart_liste>
</vdx>
</gnr>
</gnr_liste>
</ehd:body>
</ehd:ehd>
1 Zeile wurde ausgewählt.
SQL> spool off
==========================
HERE IS THE XQUERY COMMAND
==========================
<?xml version="1.0" encoding='windows-1252'?>

<page xmlns:xsql="urn:oracle-xsql" connection="gksconnection">
<xsql:query xmlns:xsql="urn:oracle-xsql">
SELECT XMLQuery('xquery version "1.0";
declare namespace n1="urn:ehd/001";
declare namespace n2="urn:ehd/go/001";
let $i := /n1:ehd/n1:body/n2:gnr_liste/n2:gnr
where $i[@n2:V = "01700V"]
return $i'
PASSING xml_document
RETURNING CONTENT)
FROM z
</xsql:query>
</page>
======================
HERE IS THE STYLESHEET - relevant part only
======================
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:ehd="urn:ehd/001" xmlns:pe="urn:ehd/go/001">
<xsl:output method="html"/>
<xsl:template match="pe:gnr">
<html>
<head>
<title>EBM Ziffer</title>
<style type="text/css">
table
border-collapse:collapse;
table, td, th
border:1px solid black;
</style>
</head>
<body style="font-family:verdana;color:black">
<h2><xsl:text>Ziffer: </xsl:text>
<xsl:value-of select="@V"/>
</h2>
<table border="1">
<tr>
<td><xsl:text>KV</xsl:text></td>
<td><xsl:value-of select="@USE"/></td>
</tr>
<tr>
<td><xsl:text>Gültigkeit</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:gueltigkeit/pe:service_tmr/@V"/></td>
</tr>
<tr>
<td><xsl:text>Bezeichnung Kapitel</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/@V"/>
<xsl:text> </xsl:text>
<xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Bereich</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:bereich/@V"/>
<xsl:text> </xsl:text>
<xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:bereich/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Kapitel</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:kapitel/@V"/>
<xsl:text> </xsl:text>
<xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:kapitel/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Abschnitt</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:abschnitt/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Unterabschnitt</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:uabschnitt/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Block</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kap_bez/pe:block/@DN"/></td>
</tr>
<tr>
<td><xsl:text>Kurztext</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:kurztext/@V"/></td>
</tr>
<tr>
<td><xsl:text>Langtext</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:langtext/@V"/></td>
</tr>
<tr>
<td><xsl:text>Langtext (Fortsetzung)</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:langtext_continued/@V"/></td>
</tr>
<tr>
<td><xsl:text>Quittungstext</xsl:text></td>
<td><xsl:value-of select="pe:allgemein/pe:legende/pe:quittungstext/@V"/></td>
</tr>
</table>

<h4><xsl:text>Anmerkungen</xsl:text></h4>
<table border="1">
<xsl:for-each select="pe:allgemein/pe:anmerkungen_liste/pe:anmerkung">
<tr>
<td><xsl:value-of select="@V"/></td>
</tr>
</xsl:for-each>
</table>

<h4><xsl:text>Leistungsinhalt</xsl:text></h4>
<table border="1" >
<tr>
<th><xsl:text>Komplex</xsl:text></th>
<th><xsl:text>Leistung</xsl:text></th>
</tr>
<xsl:for-each select="pe:allgemein/pe:leistungsinhalt/pe:komplex">
<tr>
<td><xsl:value-of select="@V"/></td>
<td>
<xsl:for-each select="pe:leistung">
<xsl:value-of select="@V"/>
</xsl:for-each>
</td>
</tr>
</xsl:for-each>
</table>

<h4><xsl:text>Bewertungen</xsl:text></h4>
<table border="1">
<tr>
<th><xsl:text>Bewertung</xsl:text></th>
<th><xsl:text>Einheit</xsl:text></th>
<th><xsl:text>Gebührenordnung</xsl:text></th>
<th><xsl:text>Leistungserbringerart</xsl:text></th>
<th><xsl:text>Leistungstyp</xsl:text></th>
<th><xsl:text>Versorgungsgebiet</xsl:text></th>
</tr>
<xsl:for-each select="pe:allgemein/pe:bewertung_liste/pe:bewertung">
<tr>
<td><xsl:value-of select="@V"/></td>
<td><xsl:value-of select="@U"/></td>
<td><xsl:value-of select="pe:gebuehrenordnung/@V"/></td>
<td><xsl:value-of select="pe:leistungserbringerart/@V"/></td>
<td><xsl:value-of select="pe:leistung_typ/@V"/></td>
<td><xsl:value-of select="pe:versorgungsgebiet/@V"/></td>
</tr>
</xsl:for-each>
</table>

<h4><xsl:text>Zeitbedarfliste</xsl:text></h4>
<table border="1">
<tr>
<th><xsl:text>Zeit</xsl:text></th>
<th><xsl:text>Einheit</xsl:text></th>
<th><xsl:text>Leistungstyp</xsl:text></th>
</tr>
<xsl:for-each select="pe:allgemein/pe:zeitbedarf_liste/pe:zeit">
<tr>
<td><xsl:value-of select="@V"/></td>
<td><xsl:value-of select="@U"/></td>
<td><xsl:value-of select="pe:leistung_typ/@V"/></td>
</tr>
</xsl:for-each>
</table>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
=====================================
THE REQUESTED SAMPLE LOOKUP TABLE FOR TIME UNITS
=====================================
<keytabs>
−
<keytab S="1.2.276.0.76.5.238" SN="S_KBV_ZEITEINHEIT" SV="1.00">
<key V="1" DN="Sekunde" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="2" DN="Minute" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="3" DN="Stunde" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="4" DN="Tag" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="5" DN="Woche" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="6" DN="Monat" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="7" DN="Quartal" S="1.2.276.0.76.5.238" SV="1.00"/>
<key V="8" DN="Jahr" S="1.2.276.0.76.5.238" SV="1.00"/>
</keytab>
</keytabs>
==================================================================================================
And this is, from an earlier trial with XMLTABLE() what I become when stylesheet is commented out. Only for your information here!
Due to the three "Anmerkung" three rows were generated. What is this notation? I got it when
executing the XSQL sheet without stylesheet. Produced by the browser.
I can not find any info in the whole web.
==================================================================================================

<page>
<ROWSET>
<ROW num="1">
<ZIFFER>01700V</ZIFFER>
<GUELTIGKEIT>2006-07-01..</GUELTIGKEIT>
<KAP_NR>1.7</KAP_NR>
<KAP_BEZ>
Gesundheits- und Früherkennungsuntersuchungen, Mutterschaftsvorsorge, Empfängnisregelun g und Schwangerschaftsabbruch (vormals Sonstige Hilfen)
</KAP_BEZ>
<BEREICH_NR>II</BEREICH_NR>
<BEREICH>Arztgruppenübergreifende allgemeine Leistungen</BEREICH>
<KAPITEL_NR>1</KAPITEL_NR>
<KAPITEL>Allgemeine Leistungen</KAPITEL>
<ABSCHNITT>
Gesundheits- und Früherkennungsuntersuchungen, Mutterschaftsvorsorge, Empfängnisregel ung und Schwangerschaftsabbruch (vormals Sonstige Hilfen)
</ABSCHNITT>
<KURZTEXT>
Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a.
</KURZTEXT>
<LANGTEXT>
Grundpauschale für Fachärzte für Laboratoriumsmedizin, Mikrobiologie und Infektionsepidemiologi e, Transfusionsmedizin und ermächtigte Fachwissenschaftler der Medizin für die Erbringung von Laborleistungen gemäß den Richtlinien des Gemeinsamen Bundesauss
</LANGTEXT>
<QUITTUNGSTEXT>
Grundpauschale für Fachärzte für Laboratoriumsmedizin u.a.
</QUITTUNGSTEXT>
<ANMERKUNG>
Die Leistung nach der Nr. 01100 ist nicht berechnungsfähig, wenn Sprechstunden vor 07:00 Uhr oder nach 19:00 Uhr stattfinden oder Patienten zu diesen Zeiten bestellt werden.
</ANMERKUNG>
</ROW>
<ROW num="2">
<ZIFFER>01700V</ZIFFER>
</ROW>
</ROWSET>
</page>

JSP vs XSL

We are trying to decide whether to use JSPs or XML/XSL for the user
          interface for our application. It is a large-scale application - large
          online shopping site - and need to do all coding in 6 weeks. One question
          we have is whether it is more expedient ot use JSPs or XSL for the
          presentation. Is one or the other more difficult to pick up, etc.
          Dennis Pagano
          Noospherics Technologies Inc.


That depends on your talent pool. Remember that JSP are automatically compiled
          into servlets and can be used to produce XML instead of HTML. This XML can then
          be formatted before being sent to the client.
          JSP are for the most part easier to work with (in terms of compilation and
          deployment, not to mention a bunch of code that gets produced for you
          automatically).
          But, if you have some experienced servlet programmers who never used JSP, I
          would skip the learning curve to meet the deadline(tm).
          My 2c,
          Guy
          In weblogic.developer.interest.jsp Dennis Pagano <[email protected]> wrote:
          > True, but there are two ways to create the pages - one whereby a servlet
          > creates xml representation of data and applies xsl to create a page. The
          > other where I write a JSP and refer to beans of data. My question is which
          > is easier to pick up - faster to become productive, and more likely to
          > deliver results quickly.
          > Guy Tal <[email protected]> wrote in message
          > news:[email protected]...
          >> I think you're comparing apples and oranges. XSL can be used to format XML
          >> data. JSP can be used to embed Java code in your HTML pages. They are not
          >> competing technologies.
          >>
          >> Guy
          >>
          >> In weblogic.developer.interest.jsp Dennis Pagano
          > <[email protected]> wrote:
          >> > We are trying to decide whether to use JSPs or XML/XSL for the user
          >> > interface for our application. It is a large-scale application - large
          >> > online shopping site - and need to do all coding in 6 weeks. One
          > question
          >> > we have is whether it is more expedient ot use JSPs or XSL for the
          >> > presentation. Is one or the other more difficult to pick up, etc.
          >>
          >> > Dennis Pagano
          >> > Noospherics Technologies Inc.
          >>
          >>

XSL-1009: Attribute 'xsl:version' not found in 'xsl:stylesheet'

I'm just starting to test XML in Oracle 8.1.7 for NT, and received the following error while testing the Oracle provided "xslsample" procedure. I modified the "iden.xls" stylesheet and added version="1.0", but still receive the same error.
execute xslsample('C:\XML\Sample','family.xml','iden.xsl','family.out','errors.txt');
Parsing XML document C:\XML\Sample/family.xml
Parsing XSL document C:\XML\Sample/iden.xsl
The id is16777216
The id is16777217
XSL Root element information
Qualified Name: xsl:stylesheet
Local Name: stylesheet
Namespace: http://www.w3.org/XSL/Transform/1.0
Expanded Name: http://www.w3.org/XSL/Transform/1.0:stylesheet
A total of 1 XSL instructions were found in the stylesheet
BEGIN xslsample('C:\XML\Sample','family.xml','iden.xsl','family.out','errors.txt'); END;
ERROR at line 1:
ORA-20100: Error occurred while processing: XSL-1009: Attribute 'xsl:version'
not found in 'xsl:stylesheet'.
ORA-06512: at "SCOTT.XSLPROCESSOR", line 22
ORA-06512: at "SCOTT.XSLPROCESSOR", line 346
ORA-06512: at "SCOTT.XSLSAMPLE", line 59
ORA-06512: at line 1
null

There is a bug in the demo stylesheet. In iden.xsl the line:
<xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">should instead be:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

XML having a JSP as XSL stylesheet ...

Similar Messages

Maybe you are looking for