Xslt question (114.XSLTTransformations)

the xslt in this sample has the following for the buyers and sellers streets:
<street><xsl:value-of select="a:address/a:street1"/> <xsl:value-of select="a:address/a:street2"/>
There is a space between the value of street1, and street2, however the result is in the format:
<street>Bridge Parkway1600</street>
and the space has been removed.
could someone explain why the space is being ignored? I can add other characters, e.g. " -" and i then see both the space and minus symbol.
Toby

Hi Toby,
I had a similar problem, my case was opposite, but I think it trims all the space , anyways if there is a new line then that is not trimmed. my suggestion is to use nbsp; instead of space, and also use any text like this and it should work fine
<xsl:text> </xsl:text>
It should work fine.
Let me know how you went.
Cheers
Sandeep

Similar Messages

XML/XSLT question

At the moment my java servlet just takes content from an ArrayList and populates html blocks that get concatenated and thrown to the client as a html page. This is not the best way to do things because the java code and html vocabulary is interspersed.
In a bid to seperate the presentation(html code) from the logic(java code) I am turning to XSLT. From my research this takes as input an XML file that contains the content. But how do you insert the content? Is there a standard way? When the tranformation from XML to html is complete, how do you hand back the resulting html page within the java application? Thanks in advance.

One solution would be to use a JSP. It can retrieve the ArrayList from the Servlet and use it to build HTML. At least that way the mixture of HTML and Java is minimized in the source form. (Behind the scenes, the JSP is turned into a Servlet, so the mixture is still there, it is just not as visible.)
Another choice is to use DOM or JDOM to create the Html content using Element objects to create tags. The main advantage of that over doing "
...out.println( "<h1>...</h1>);
is that it makes sure the closing tags match, and empty tags are properly coded.
In answer to your direct question, there is no standard for how to code data into XML so you can run an XSLT transform to convert it into HTML. It also mixes Java logic and XML in the same file. You need to choose your poison.
Dave Patterson

XSLT question

Hi all,
Need help on reading attribute value of XML field in XSLT mapping .
Part of source code, where we want to read attribute actionCode value i.e., "Accepted".
<ResponseCriteria actionCode="Accepted">
                                   <ChangeStatus>
                                        <Code>Position Opening was created</Code>
                                        <ReasonCode/>
                                        <Reason>PositionID assiggned - 10939</Reason>
                                        <Description/>
                                   </ChangeStatus>
                              </ResponseCriteria>
We are able to reach till the location with below code in XSLT,
<xsl:value-of select="//*[local-name()='ResponseCriteria']"/>
This code is giving us values of Code & Reason fields.
How to get the values of attribute actionCode?? any ideas........

Rahul has correctly pointed that xsl:value-of can also be used to retrieve the value of attributes of XML elements.
<xsl:value-of select="@actioncode"/> -

XSLT question, Parameters from itab

Hi Experts,
I'm using the following code in my abap program:
TYPE-POOLS: abap.
TYPES: BEGIN OF line_type,
vartag   TYPE string,
varvalue TYPE string,
END OF line_type.
TYPES: itype TYPE TABLE OF line_type.
DATA: gt_source_itab TYPE abap_trans_srcbind_tab,
      gs_source_wa   TYPE abap_trans_resbind.
DATA: line TYPE line_type.
DATA: itab TYPE itype.
DATA: output_stream TYPE xstring.
clear line.
line-vartag   = 'tagname'.
line-varvalue = 'value'.
APPEND line TO itab.
GET REFERENCE OF itab INTO gs_source_wa-value.
gs_source_wa-name = 'TAG'.
APPEND gs_source_wa TO gt_source_itab.
TRY.
    CALL TRANSFORMATION z_cd_xsl
      SOURCE (gt_source_itab)
      RESULT XML output_stream.
In my Transformation I'm having trouble using the right expression in the select-attribute of xslt-element "xsl:with-param".
<xsl:transform version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:sap="http://www.sap.com/sapxsl"
>
<xsl:include sap:name="Z_INCLUDE_UDKXML"/>

<xsl:template match="/">
<xsl:call-template name="udk_nachrichtenAnfang">
               <xsl:with-param name="NachrAnf_MesBez" select=<Don't know what to do here> />
There are no syntactic errors (rest of the corresponding code is in the include). If i just set the select attribute with plain text, it works. But I want to use the value from my abap variable "varvalue".
I tried select='$LINE-VARVALUE', select="//TAG/VARVALUE", select="VARVALUE" and several others, didn't work.
I'm guessing I'll need some XPATH expression to access the serialized asXML deep structure, but I can't figure it out
Regards, Lukas

Check this code.....
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
<xsl:strip-space elements="*"/>
<xsl:template match="/">
    <TAG>
      <xsl:apply-templates select="//TAG/item"/>
    </TAG>
</xsl:template>
<xsl:template match="TAG/item">
    <item>
      <VARTAG>
        <xsl:value-of select="VARTAG"/>
      </VARTAG>
      <VARVALUE>
        <xsl:value-of select="VARVALUE"/>
      </VARVALUE>
    </item>
</xsl:template>
</xsl:transform>

Dreamweaver, XSLT question

I'd like to duplicate a node. The duplicate has to be placed as the first child of the root. The original node has to remain intact.
Is this possible with XSLT in Dreamweaver?

I'd like to duplicate a node. The duplicate has to be placed as the first child of the root. The original node has to remain intact.
Is this possible with XSLT in Dreamweaver?

A XSLT question?

How to use XSLT to transform several XML files, then generate one output file?
I have one xsl file and many XML files, and I want to transform XML files to just one output file.
How to do it?
Waiting for your reply. Thank you.


<xsl:variable name="doc1" select="document('foo.xml')"/>

<xsl:for-each select="$doc1">
<xsl:apply-templates select="schema"/>
</xsl:for-each>
In fact the string defining the name of the document is taken from the 'higher-level' XML document rather than being a constant value

XSLT Question: xsl:for-each select="//MYELEMEMT[1]"

Hi everybody,
does anybody know, what [1] means?
Thanks Regards Mario

Check this:
http://www.w3schools.com/xpath/xpath_examples.asp
<i>select the First book Node
The following example selects only the first book node under the bookstore element:
xmlDoc.selectNodes("/bookstore/book[0]")
If you have IE 5 or higher you can try it yourself
Note: IE5 and later has implemented that [0] should be the first node, but according to the W3C standard it should have been [1]!!
A Workaround!
To solve the [0] and [1] problem in IE5+, you can set the SelectionLanguage to XPath.
The following example selects only the first book node under the bookstore element:
xmlDoc.setProperty "SelectionLanguage", "XPath"
xmlDoc.selectNodes("/bookstore/book[1]")</i>
Regards
Stefan

Xslt transformation rules for BPEL

Hi there,
Can anyone advise where I can find the xslt transformation rules for BPEL. I am unable to find the mentioned file "114.XSLTTransformations".
Best regards!
Linda

I installed the BPEL process manager and find the 114.XSLTTransformations tutorial project, but the sample xslt file is for a specific xml file but not for a general bpel file, which doesn't help with my problem.
For instance, if I want to transform a bpel file to other formats using xslt, how to handle "partner link" structure of bpel?
Best regards,
Linda

Any way to generate a single quote (') with XSLT?

Hi:
I guess this is really an XSLT question. I'm using the Transform() method of an XMLType variable to apply a style sheet. The XML in the variable is just something simple like
<TBL>
<LAST_NAME>LIKE|JONES</LAST_NAME>
<FIRST_NAME>=|MARY</FIRST_NAME>
<AGE>=|50</AGE>
</TBL>
I am trying to get a stylesheet to transform something like the above into SQL such as
Select * from foo where LAST_NAME like 'JONES'
and FIRST_NAME ='MARY'
and AGE = 50But to do this, I need to generate the single quotes around the search terms and I can't get anything but LAST_NAME LIKE 'JONES'. Is there a way to do this? For now I am generating a ~ and replacing ~ for ' throughout the generated SQL text but that's a pretty sorry solution.
I thought that something like <xsl:text disable-output-escaping="yes">&</xsl:text> was going to work but then found out it has been deprecated. I was thinking character-map might work but that's an XSLT 2.0 thing and apparently 10g is on XSLT 1.0? In any case, it had no idea what I was trying to do with a character map.
So, am I overlooking an obvious way to get my stylesheet to insert apostrophes?
Thanks.

It's 10.2.0.4.
Here's the procedure that accepts the XML/XSL clobs and tries to produce a SQL statement.
PROCEDURE GetSQLQueryFromXML(XMLClob in CLOB, XSLStylesheet in CLOB,
            SQLQuery out CLOB, status out integer) IS
    -- Define the local variables
xmldata               XMLType; -- The XMLType format of the XML to transform
xsldata               XMLType; -- The XMLType format of the stylesheet to apply
sqlQuery_XMLType      XMLType; -- The XMLType format of the SQL query.
v_SQLQuery            Clob;     -- Holds XML Clob before translating ~ to '
BEGIN
status := -1; -- Initially unsuccessful
-- Get the XML document using the getXML() function defined in the database.
-- Since XMLType.transform() method takes XML data as XMLType instance,
-- use the XMLType.createXML method to convert the XML content received
-- as CLOB into an XMLType instance.
xmldata := XMLType.createXML(XMLClob);
-- Get the XSL Stylesheet using the getXSL() function defined in the database.
-- Since XMLType.transform() method takes an XSL stylesheet as XMLType instance,
-- use the XMLType.createXML method to convert the XSL content received as CLOB
-- into an XMLType instance.
xsldata := XMLType.createXML(XSLStylesheet);
-- Use the XMLtype.transform() function to get the transformed XML instance.
-- This function applies the stylesheet to the XML document and returns a transformed
-- XML instance.
sqlQuery_XMLType := xmldata.transform(xsldata);
-- Return the transformed XML instance as a CLOB value.
v_SQLQuery := sqlQuery_XMLType.getClobVal();
-- Change tildas to apostrophes. Currently unable to get an XSLT transformation
-- to insert single quotes, so we're inserting ~ instead. Now we need to
-- translate all ~s to 's in our query.
SQLQuery := translate(to_char(v_SQLQuery),'~','''');
status := 1; -- Everything went fine to get here
EXCEPTION
WHEN OTHERS THEN
    raise_application_error
    (-20102, 'Exception occurred in GetSQLQueryFromXML :'||SQLERRM);
END GetSQLQueryFromXML;The XML it works off of is
    someXML CLOB :=
    to_clob('<?xml version="1.0" encoding="windows-1252" ?>
<variable table_name="SOME_PERSON_TABLE" query_type="PERSON">
<item>
    <fieldName><![CDATA[PERSON_KEY]]></fieldName>
    <criteria><![CDATA[=]]></criteria>
    <fieldType><![CDATA[Integer]]></fieldType>
    <value><![CDATA[123456789]]></value>
</item>
<item>
    <fieldName><![CDATA[LAST_NAME]]></fieldName>
    <criteria><![CDATA[=]]></criteria>
    <fieldType><![CDATA[String]]></fieldType>
    <value><![CDATA[DOE]]></value>
</item>
<item>
    <fieldName><![CDATA[FIRST_NAME]]></fieldName>
    <criteria><![CDATA[=]]></criteria>
    <fieldType><![CDATA[String]]></fieldType>
    <value><![CDATA[JOHN]]></value>
</item>
<item>
    <fieldName><![CDATA[MIDDLE_NAME]]></fieldName>
    <criteria><![CDATA[-]]></criteria>
    <fieldType><![CDATA[String]]></fieldType>
    <value />
</item>
<item>
    <fieldName><![CDATA[SUFFIX]]></fieldName>
    <criteria><![CDATA[-]]></criteria>
    <fieldType><![CDATA[String]]></fieldType>
    <value />
</item>
</variable>');And the corresponding XSLT that should translate it is:
myStylesheet CLOB :=
to_clob('<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">


<xsl:output method="text" omit-xml-declaration="yes" indent="no"/>


<xsl:variable name="apos">~</xsl:variable>
<xsl:template match="/">
    select * from
    <xsl:value-of select="variable/@table_name"/>
    where 1=1
    <xsl:for-each select="variable/child::node()">
      <xsl:choose>
        
        <xsl:when test="./value/text()[normalize-space(.)]">
        
          AND <xsl:value-of select="./fieldName"/>
          <xsl:text> </xsl:text>
          <xsl:value-of select="./criteria"/>
          <xsl:text> </xsl:text>
          <xsl:choose>
            <xsl:when test="string(./fieldType)=''String''">
              <xsl:copy-of select="$apos" />
              <xsl:value-of select="./value"/>
              <xsl:copy-of select="$apos" />
            </xsl:when>
            <xsl:when test="string(./fieldType)=''Clob''">
              <xsl:copy-of select="$apos" />
              <xsl:value-of select="./value"/>
              <xsl:copy-of select="$apos" />
            </xsl:when>
            <xsl:otherwise>
              <xsl:value-of select="./value"/>
            </xsl:otherwise>
          </xsl:choose>
        </xsl:when>
      </xsl:choose>
    </xsl:for-each>
</xsl:template>
</xsl:stylesheet>');Basically if the VALUE element has a value then the fieldType is checked. If fieldType is String or Clob then we'll need the apostrophes. For now I'm putting in tildas and changing them later.

Xsl schema import from within a wsdl file

I have a namespace conflict issue validating a bpel process.
The message error is as follow:
[bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:19:80: src-resolve.4.2: Error resolving component 'tns2:InvocationContext'. It was detected that 'tns2:InvocationContext' is in namespace 'http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns2:InvocationContext' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
[bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:20:76: src-resolve.4.2: Error resolving component 'tns1:SMSMessageETO'. It was detected that 'tns1:SMSMessageETO' is in namespace 'http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns1:SMSMessageETO' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
I've already seen this kind of error in other posts, but this was encountered with xsd files. In my case, I'm trying to use complexTypes defined in a schema, defined itself in a WSDL file. The needed file (SMSSenderEnablerSEI) is referenced in the bpel.xml file.
// Here the BPEL file (SMSMulticast2.bpel)
<pre>

<process name="SMSMulticast2" targetNamespace="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" suppressJoinFailure="yes" xmlns:tns="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:nsxml0="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:nsxml1="http://com.osa.mdsp.enabler.sei/PimEnabler:DirectService/2004/V1.0">
     
     
     
     
     <partnerLinks>
          
          <partnerLink name="client" partnerLinkType="tns:SMSMulticast2" myRole="SMSMulticast2Provider"/>
          <partnerLink name="SMSEnabler" partnerLinkType="nsxml0:SMSSenderEnablerRemoteLink" partnerRole="SMSSenderEnablerRemoteProvider"/>
          <partnerLink name="PIMEnabler" partnerLinkType="nsxml1:PimDirectServiceEnablerSEIImplLink" partnerRole="PimDirectServiceEnablerSEIImplProvider"/>
     </partnerLinks>
     
     
     
     
     <variables>
          
          <variable name="smsmultiRequest" messageType="tns:SMSMulticast2RequestMessage"/>
          
          <variable name="smsmultiResponse" messageType="tns:SMSMulticast2ResponseMessage"/>
          <variable name="count" type="xsd:integer"/>
          <variable name="contactRequest" messageType="nsxml1:retrieveContactRequest"/>
          <variable name="smsRequest" messageType="nsxml0:sendSMSRequest"/>
          <variable name="smsResponse" messageType="nsxml0:sendSMSResponse"/>
          <variable name="contactResponse" messageType="nsxml1:addContactResponse"/>
     </variables>
     
     
     
     
     
     <sequence name="main">
          
          <receive name="receiveInput" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiRequest" createInstance="yes"/>
          
          <assign name="setProperties">
               <copy>
                    <from expression="5"></from>
                    <to variable="count"/>
               </copy>
               <copy>
                    <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMSISDN"></from>
                    <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:senderAddress"/>
               </copy>
               <copy>
                    <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMessage"></from>
                    <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:content"/>
               </copy>
          </assign>
          <while name="foreach" condition="bpws:getVariableData('count') > 0"><sequence><invoke name="invoke-1" partnerLink="SMSEnabler" portType="nsxml0:SMSSenderEnablerRemote" operation="sendSMS" inputVariable="smsRequest" outputVariable="smsResponse"/>
                    <assign name="decrease"><copy>
                              <from expression="bpws:getVariableData('count') - 1"></from>
                              <to variable="count"/>
                         </copy>
                    </assign>
               </sequence>
          </while>
          
          <reply name="sendResult" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiResponse"/>
     </sequence>
</process>
// Here the WSDL file: SMSSenderEnablerSEIWrapper.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
     name="SMSSenderEnablerSEI"
targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
     xmlns="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
     xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
     <xsd:schema
          elementFormDefault="qualified"
          targetNamespace="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
          xmlns="http://www.w3.org/2001/XMLSchema"
          xmlns:tns="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
          <xsd:complexType name="InvocationContext">
          <xsd:sequence>
          <xsd:element
          maxOccurs="unbounded"
          name="properties"
          nillable="true"
          type="xsd:string"/>
          </xsd:sequence>
          </xsd:complexType>
          <xsd:complexType name="EnablerException">
          <xsd:sequence>
          <xsd:element name="errorMessage" nillable="true" type="xsd:string"/>
          <xsd:element name="errorCode" type="xsd:int"/>
          </xsd:sequence>
          </xsd:complexType>
          <xsd:element name="EnablerException" nillable="true" type="tns:EnablerException"/>
          </xsd:schema>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
               xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
               xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
<xsd:element name="sendSMS">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sendSMSReturn" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotification">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
<xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotificationResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sendSMSWithNotificationReturn" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSToAlias">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
<xsd:element name="serviceId" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSToAliasResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sendSMSToAliasReturn" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotificationToAlias">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
<xsd:element name="serviceId" nillable="true" type="xsd:string"/>
<xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotificationToAliasResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element
name="sendSMSWithNotificationToAliasReturn"
nillable="true"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
               xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
               xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
               <xsd:complexType name="SMSMessageETO">
<xsd:sequence>
<xsd:element name="content" nillable="true" type="xsd:string"/>
<xsd:element name="earliestDeliveryTime" nillable="true" type="xsd:dateTime"/>
<xsd:element name="expiryDate" nillable="true" type="xsd:dateTime"/>
<xsd:element name="priority" nillable="true" type="xsd:string"/>
<xsd:element name="recipient" nillable="true" type="xsd:string"/>
<xsd:element name="senderAddress" nillable="true" type="xsd:string"/>
<xsd:element name="contentSentEncoding" nillable="true" type="xsd:string"/>
<xsd:element name="smsContentSentInGsm7Bits" type="xsd:boolean"/>
<xsd:element name="smsContentSentInUcs2" type="xsd:boolean"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
               xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
               xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<xsd:complexType name="SMSException">
<xsd:sequence>
<xsd:element name="errorCode" type="xsd:int"/>
<xsd:element name="message" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="SMSException" nillable="true" type="tns4:SMSException"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="sendSMSRequest">
<wsdl:part element="impl:sendSMS" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSToAliasResponse">
<wsdl:part element="impl:sendSMSToAliasResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="EnablerException">
<wsdl:part element="tns2:EnablerException" name="fault"/>
</wsdl:message>
<wsdl:message name="sendSMSToAliasRequest">
<wsdl:part element="impl:sendSMSToAlias" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationToAliasRequest">
<wsdl:part element="impl:sendSMSWithNotificationToAlias" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationToAliasResponse">
<wsdl:part
element="impl:sendSMSWithNotificationToAliasResponse"
name="parameters"/>
</wsdl:message>
<wsdl:message name="SMSException">
<wsdl:part element="tns4:SMSException" name="fault"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationResponse">
<wsdl:part element="impl:sendSMSWithNotificationResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationRequest">
<wsdl:part element="impl:sendSMSWithNotification" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSResponse">
<wsdl:part element="impl:sendSMSResponse" name="parameters"/>
</wsdl:message>
<wsdl:portType name="SMSSenderEnablerRemote">
<wsdl:operation name="sendSMS">
<wsdl:input message="impl:sendSMSRequest" name="sendSMSRequest"/>
<wsdl:output message="impl:sendSMSResponse" name="sendSMSResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotification">
<wsdl:input
message="impl:sendSMSWithNotificationRequest"
name="sendSMSWithNotificationRequest"/>
<wsdl:output
message="impl:sendSMSWithNotificationResponse"
name="sendSMSWithNotificationResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
<wsdl:operation name="sendSMSToAlias">
<wsdl:input message="impl:sendSMSToAliasRequest" name="sendSMSToAliasRequest"/>
<wsdl:output
message="impl:sendSMSToAliasResponse"
name="sendSMSToAliasResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotificationToAlias">
<wsdl:input
message="impl:sendSMSWithNotificationToAliasRequest"
name="sendSMSWithNotificationToAliasRequest"/>
<wsdl:output
message="impl:sendSMSWithNotificationToAliasResponse"
name="sendSMSWithNotificationToAliasResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding
name="SMSSenderEnablerRemoteSoapBinding"
type="impl:SMSSenderEnablerRemote">
<wsdlsoap:binding
style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sendSMS">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotification">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSWithNotificationRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSWithNotificationResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sendSMSToAlias">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSToAliasRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSToAliasResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotificationToAlias">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSWithNotificationToAliasRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSWithNotificationToAliasResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SMSSenderEnablerRemoteService">
<wsdl:port
binding="impl:SMSSenderEnablerRemoteSoapBinding"
name="SMSSenderEnablerRemote">
<wsdlsoap:address
location="http://localhost:8888/Simulateur/services/SMSSenderEnablerRemote?wsdl"/>
</wsdl:port>
</wsdl:service>
<plnk:partnerLinkType name="SMSSenderEnablerRemoteLink">
<plnk:role name="SMSSenderEnablerRemoteProvider">
<plnk:portType name="impl:SMSSenderEnablerRemote"/>
</plnk:role>
</plnk:partnerLinkType>
</wsdl:definitions>
Is that possible to reuse (in a BPEL file) schemas types defined in a wsdl file with Oracle PM? Could you give me a hint to solve this problem?
Many Thanks
Guillaume

You need to use the XSLT before you do assignment to achieve this, to
change the message to the correct namespace.
Please refer to sample at
"orabpel\samples\tutorials\114.XSLTTransformations" which talks about
how to use XSLT transformation.
And please refer to
"orabpel\samples\tutorials\121.FileAdapter\ComplexStructure" sample
especially "InvToPo.xslt" which talks about doing transformations
between 2 structures pointing to different namespaces.

DRQ: Make B1 client resolve HTTP links from within body of internal message

Hi,
Request for a feature within the B1 client - when displaying an internal message, have the client pick up any text with "http://" and treat it as a web hyperlink - when clicked on, launch a browser for that site. This functionality already exists when using Link type UDF fields.

You need to use the XSLT before you do assignment to achieve this, to
change the message to the correct namespace.
Please refer to sample at
"orabpel\samples\tutorials\114.XSLTTransformations" which talks about
how to use XSLT transformation.
And please refer to
"orabpel\samples\tutorials\121.FileAdapter\ComplexStructure" sample
especially "InvToPo.xslt" which talks about doing transformations
between 2 structures pointing to different namespaces.

XSL file include problem.

Hi Friends,
We are facing problem while include our file inside XSL.
we have code like below
<xsl:for-each select="givingLanding/briefPageInclude">
                              <xsl:variable name="pageUrl" select="pageUrl" />
                                   <xsl:choose>
                                        <xsl:when test="not($pageUrl = '') ">
                                             
                                             <xsl:text disable-output-escaping="yes"><#include file="</xsl:text>
                                             <xsl:value-of disable-output-escaping="yes" select="pageUrl" />
                                             <xsl:text disable-output-escaping="yes">"></xsl:text>
                                        </xsl:when>
                                   </xsl:choose>
                         </xsl:for-each>Here we tried two ways two attach file but none of them attach the given file. ( here it will render XSL --> XHTML output)
Can anybody have idea how to include file ? ( in such loop structure)
Thanks

It's a little hard to quess what you're trying to do based on the XSLT you posted.
You can't xsl:include a document whose URL is determined at run time in XSLT. The normal pattern is to generate the stylesheet using XSLT to insert the path, then apply that generated stylesheet.
In XSLT2 you can fetch a document whose URL is determined at run time, and operate on that, if that's what you're trying to do. See the [document function|http://www.w3.org/TR/xslt#document]
XSLT questions are better asked on the [Mulberry XSL list |http://www.mulberrytech.com/xsl/xsl-list/].

ORA-13516

Hi
SQL> select snap_interval from dba_hist_wr_control;
SNAP_INTERVAL
+40150 00:00:00.0Can anybody please explain me what is "+40150" in above snap interval ?
Can i understand from above output that snapshot interval is set to zero ?
because of above setting when i m exec dbms_workload_repository.create_snapshot i m getting below error
SQL> EXEC DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT;
BEGIN DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT; END;
ERROR at line 1:
ORA-13516: AWR Operation failed: INTERVAL Setting is ZERO
ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 99
ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 122
ORA-06512: at line 1

Handle:      user511621
Status Level:      Newbie
Registered:      May 24, 2006
Total Posts:      467
Total Questions:      114 (109 unresolved)
so many questions & so few answers.
Can anybody please explain me what is "+40150" in above snap interval ?when all else fails, Read The Fine Manual
http://download.oracle.com/docs/cd/E11882_01/server.112/e17110/statviews_4071.htm#REFRN23462

Question about JSP, XSLT and JDOM

hi, folks. Let's say within page1.jsp, i have <jsp:include page="page2.jsp" flush="true"> On the other hand, i have a servlet helper class which queries the database, then converts the ResultSet object into a JDOM Document object. My question is i want to make the transformed output of the JDOM Document and XSLT template to be a partial content of the page2.jsp page. How can i get this done properly? I have no problem of doing the transformation, but just dont know how to concatenate the output with the rest content of page2.jsp. Hope i clearly explained the question. Any advice is greatly appreciated.
//code fragment on page2.jsp
<td valign="top" width="788">
    <font size="3"><br>
        <p>
       //i want put the transformed results here
       </p>
     </font>
</td>

this is a fragment of my testing program, which transform direct to response output stream. but i dont want put this bounch of java code within page2.jsp. do i some other way around to get it done?
Document myDocument = createDocument();
               TransformerFactory tFactory = TransformerFactory.newInstance();
            // Make the input sources for the XML and XSLT documents
            org.jdom.output.DOMOutputter outputter = new org.jdom.output.DOMOutputter();
            org.w3c.dom.Document domDocument = outputter.output(myDocument);
            javax.xml.transform.Source xmlSource = new javax.xml.transform.dom.DOMSource(domDocument);
            StreamSource xsltSource = new StreamSource(new FileInputStream("d:/tomcat/webapps/project/car.xsl"));
        //Make the output result for the finished document
            StreamResult xmlResult = new StreamResult(response.getOutputStream());
            //StreamResult xmlResult = new StreamResult(System.out);
        //Get a XSLT transformer
        Transformer transformer = tFactory.newTransformer(xsltSource);
        //do the transform
            transformer.transform(xmlSource, xmlResult);

XSLT, XML Question???

I've recently found that I can use XSLT to transform XML docs into SQL using x-path... Is there any documentation out there referencing a transformation using x-query???? I've searched the web but have not seem much on this...
Any direction would be greatly appreciated.

XSLT doesn't use XQuery. So it's not surprising you haven't found much documentation about using XQuery in XSLT. You might want to direct questions like this one to an XSLT forum rather than a Java forum.

Xslt question (114.XSLTTransformations)

Similar Messages

Maybe you are looking for