'less' (lt) - sign in a xsql query
How to escape a < or > sign in a query?
I got the error: Invalid Character in name.
Thomas
Simply typing "Test <test> test" into a frame and exporting that yields
<ParaStyle:Body>Test \<test\> test
and reading it back into ID gives the expected result.
Similar Messages
-
Using '(' and less than operator in an xsql page sql query
Dear All,
I tried to use left parenthesis '(' and less than operator in an sql query through an xsql page, it doesn't let to use them.
Do you know how to use those in an xsql page?
Thanks for your help.
MustafaFollowing is the xsql page that I tried to run:
<?xml version="1.0"?>
<xsql:query xmlns:xsql="urn:oracle-xsql" connection = "bib" rowset-element="bib" row-element="book">
(SELECT year,title,last,first,' ' as affiliation,publisher,price
FROM book,author
WHERE year=2001 and bookid=parentid
UNION
SELECT year,title,last,first,affiliation,publisher,price
FROM book,editor
WHERE year=2001 and bookid=parentid)
INTERSECT
(SELECT year,title,last,first,' ' as affiliation,publisher,price
FROM book,author
WHERE publisher='Publisher1' and bookid=parentid
UNION
SELECT year,title,last,first,affiliation,publisher,price
FROM book,editor
WHERE publisher='Publisher1' and bookid=parentid)
</xsql:query>
This is the error message generated after running:
<ERROR>java.sql.SQLException: ORA-01009: missing mandatory parameter</ERROR>
When I remove the parentheses it works but this results in a different result set.
Can anybody tell me the reason?
Thanks,
Mustafa
null -
XMLElement not returning XML with xsql:query
I am trying to use a select statement containing XMLElement, XMLAgg and XMLForest functions from a xsql servlet.
<page xmlns:xsql="urn:oracle-xsql" connection="HOM_WISP">
<xsql:query row-element="" rowset-element="STATEMENT">
SELECT
XMLElement("GROUP", XMLAttributes(gst_group AS GSTGroup,
display_group AS DisplayGroup),
XMLAgg(
XMLElement("PAYMENTDETAIL",
XMLForest(phase_type,
contract_num,
mark_block,
cut_permit,
destination,
stratum_code,
species_code,
sort_code,
truck,
back_haul,
uom_desc,
uom_code,
gst_exempt_flag,
pay_deduct_desc,
actual_rate,
gst_registrant_num,
load_count,
quantity,
volume,
earnings)))).getClobVal() as PAYMENTITEM
FROM ws_cntr_statement_vw
GROUP BY gst_group, display_group
</xsql:query>
</page>
When XML is returned only the out most XML as follows the inner elements are text. I truncated the output but you can see that GROUP and PAYMENTDETAIL are not elements but text. I want them all to be elements.
<page>
<STATEMENT><PAYMENTITEM><GROUP GSTGROUP="1_GST" DISPLAYGROUP="2_RETRO"><PAYMENTDETAIL><PHASE_TYPE>Purchasing</PHASE_TYPE><CONTRACT_NUM>3346</CONTRACT_NUM><MARK_BLOCK>GA500B-0001</MARK_BLOCK><DESTINATION>LC</DESTINATION><STRATUM_CODE>18</STRATUM_CODE><SPECIES_CODE>SP</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>-9.32</ACTUAL_RATE><GST_REGISTRANT_NUM>R102090347</GST_REGISTRANT_NUM><LOAD_COUNT>1</LOAD_COUNT><QUANTITY>28440</QUANTITY><VOLUME>36.68</VOLUME><EARNINGS>-265.06</EARNINGS></PAYMENTDETAIL></GROUP></PAYMENTITEM><PAYMENTITEM><GROUP GSTGROUP="1_GST" DISPLAYGROUP="4_CNTRPAY"><PAYMENTDETAIL><PHASE_TYPE>ADV/REC NO CONTRACT</PHASE_TYPE><UOM_DESC>flat</UOM_DESC><UOM_CODE>FL</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><PAY_DEDUCT_DESC>PAY 12 ADVANCE RECOVERY ES4922</PAY_DEDUCT_DESC><ACTUAL_RATE>32644.87</ACTUAL_RATE><GST_REGISTRANT_NUM>R123330532</GST_REGISTRANT_NUM><EARNINGS>-32644.87</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>FIREWOOD/STUMPAGE ALL BLOCKS</PHASE_TYPE><UOM_DESC>flat</UOM_DESC><UOM_CODE>FL</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><PAY_DEDUCT_DESC>FIREWOOD LOAD # 151819</PAY_DEDUCT_DESC><ACTUAL_RATE>25</ACTUAL_RATE><GST_REGISTRANT_NUM>R123083735</GST_REGISTRANT_NUM><EARNINGS>-25</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>SB#2 PAY RD USE</PHASE_TYPE><UOM_DESC>flat</UOM_DESC><UOM_CODE>FL</UOM_CODE><GST_EXEMPT_FLAG>1</GST_EXEMPT_FLAG><PAY_DEDUCT_DESC>ROAD USE ES4208 BLOCK 9</PAY_DEDUCT_DESC><ACTUAL_RATE>898.1</ACTUAL_RATE><EARNINGS>898.1</EARNINGS></PAYMENTDETAIL></GROUP></PAYMENTITEM><PAYMENTITEM><GROUP GSTGROUP="1_GST" DISPLAYGROUP="1_ORIGINAL"><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0026</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>FED</DESTINATION><STRATUM_CODE>01</STRATUM_CODE><SPECIES_CODE>FI</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>19.5</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>14</LOAD_COUNT><QUANTITY>498300</QUANTITY><VOLUME>579.54</VOLUME><EARNINGS>9716.85</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0026</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>06</STRATUM_CODE><SPECIES_CODE>FI</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>19.5</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>33</LOAD_COUNT><QUANTITY>1096770</QUANTITY><VOLUME>1300.24</VOLUME><EARNINGS>21387.07</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0026</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>13</STRATUM_CODE><SPECIES_CODE>LO</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>19.5</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>84</LOAD_COUNT><QUANTITY>3219510</QUANTITY><VOLUME>3990.95</VOLUME><EARNINGS>62780.68</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0026</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>21</STRATUM_CODE><SPECIES_CODE>MX</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>19.5</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>2</LOAD_COUNT><QUANTITY>71030</QUANTITY><VOLUME>91.4</VOLUME><EARNINGS>1385.09</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0026</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>PUL</DESTINATION><STRATUM_CODE>16</STRATUM_CODE><SPECIES_CODE>LO</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>18</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>3</LOAD_COUNT><QUANTITY>104980</QUANTITY><VOLUME>173.46</VOLUME><EARNINGS>1889.64</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0030</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>06</STRATUM_CODE><SPECIES_CODE>FI</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>19.5</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>15</LOAD_COUNT><QUANTITY>514800</QUANTITY><VOLUME>610.27</VOLUME><EARNINGS>10038.64</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0030</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>18</STRATUM_CODE><SPECIES_CODE>SP</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>19.5</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>1</LOAD_COUNT><QUANTITY>35740</QUANTITY><VOLUME>46.43</VOLUME><EARNINGS>696.93</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>2731</CONTRACT_NUM><MARK_BLOCK>ES4334-0030</MARK_BLOCK><CUT_PERMIT>334</CUT_PERMIT><DESTINATION>PUL</DESTINATION><STRATUM_CODE>16</STRATUM_CODE><SPECIES_CODE>LO</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>18</ACTUAL_RATE><GST_REGISTRANT_NUM>R104985114</GST_REGISTRANT_NUM><LOAD_COUNT>3</LOAD_COUNT><QUANTITY>100280</QUANTITY><VOLUME>165.68</VOLUME><EARNINGS>1805.04</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>3350</CONTRACT_NUM><MARK_BLOCK>ES4922-0026</MARK_BLOCK><CUT_PERMIT>922</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>06</STRATUM_CODE><SPECIES_CODE>FI</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>37</ACTUAL_RATE><GST_REGISTRANT_NUM>R123330532</GST_REGISTRANT_NUM><LOAD_COUNT>5</LOAD_COUNT><QUANTITY>197320</QUANTITY><VOLUME>233.92</VOLUME><EARNINGS>7300.84</EARNINGS></PAYMENTDETAIL><PAYMENTDETAIL><PHASE_TYPE>Logging</PHASE_TYPE><CONTRACT_NUM>3350</CONTRACT_NUM><MARK_BLOCK>ES4922-0027</MARK_BLOCK><CUT_PERMIT>922</CUT_PERMIT><DESTINATION>LC</DESTINATION><STRATUM_CODE>21</STRATUM_CODE><SPECIES_CODE>MX</SPECIES_CODE><UOM_DESC>tonne</UOM_DESC><UOM_CODE>MT</UOM_CODE><GST_EXEMPT_FLAG>0</GST_EXEMPT_FLAG><ACTUAL_RATE>37</ACTUAL_RATE><GST_REGISTRANT_NUM>R123330532</GST_REGISTRANT_NUM><LOAD_COUNT>1</LOAD_COUNT><QUANTITY>38920</QUANTITY><VOLUME>50.08</VOLUME><EARNINGS>1440.04</EARNINGS></PAYMENTDETAIL><Sorry I guess I haven't explained very well. When I am issuing the SELECT statement which uses XMLElement I have to convert output to string in order to have a column alais PAYMENTITEM. It is then not reconnized as XML in the
xsql:query call
If I do not assign a alias to query I get following error
oracle.xml.sql.OracleXMLSQLException: Character ',' is not allowed in an XML tag
If I assign without using getClobVal() I get this error
oracle.xml.sql.OracleXMLSQLException: Conversion to String failed
If I then use the getClobVal() to assign column alias it appears as if entire result set is now a string then <> tag delimiters are now show with "<" signs instead. -
Hi,
I'm having a problem with the following simple XSQL document:
<?xml version="1.0"?>
<xsql:query connection="xsqltest" xmlns:xsql="urn:oracle-xsql">
SELECT concat(concat(forename, ' '), surname) AS Name
, d.name AS Department
FROM emp, dept d
WHERE emp.dept_no = d.id
ORDER BY surname
</xsql:query>When I transform this using the command line xsql, it produces the following (as expected):
<?xml version = '1.0'?>
<ROWSET>
<ROW num="1">
<Name>Cindy Delight</Name>
<Department>Accounting</Department>
</ROW>
<ROW num="2">
<Name>Adrian Rue</Name>
<Department>Product Development</Department>
</ROW>
<ROW num="3">
<Name>Dwight Dweeb</Name>
<Department>Accounting</Department>
</ROW>
</ROWSET>However, when I access the same page through my browser, the output is:
<?xml version = '1.0'?>
<xsql:query>
SELECT concat(concat(forename, ' '), surname) AS Name
, d.name AS Department
FROM emp, dept d
WHERE emp.dept_no = d.id
ORDER BY surname
</xsql:query>(this is the same as the input document, except the namespace declaration has been stripped out, making the XML invalid).
I've tried including other xsql tags in the same document (e.g. xsql:include-xsql), these seem to work fine. Also, if I change the connect details, XSQL fails as expected, so it would appear xsql is being invoked by Tomcat (.xsql is mapped to the servlet), and XSQL successfully connecting to the database.
My setup is slightly unusual: I'm trying to use XSQL 1.0.4.1 with MySQL 3.23.32 using the mm.mysql 2.0.4 JDBC drivers. This is running on Tomcat 3.2.1 with JDK 1.3 (OJVM 1.2.330). But, since it works with the command line xsql, I'm at a loss as to why it's misbehaving through the servlet engine only... any ideas?
SteveHmm,
Even more confusing - the same .xsql document works fine with WebToGo - so I guess this is a Tomcat problem, somehow... Just can't understand why xsql:include-xsql works and xsql:query doesn't.
Steve -
Object types return hex characters with xsql:query
How do I use xsql servlet to return an object which contains street address etc. as a character string and not a hexadecimal string. If I use the following ddl and implement the following xsql, I get the following results.
CREATE TYPE address_objtyp AS object
(street VARCHAR(30),city VARCHAR(30),state VARCHAR(2));
CREATE SEQUENCE employees_seq START WITH 105 INCREMENT BY 1;
CREATE TABLE employees(
id NUMBER(4) CONSTRAINT emp_pkId PRIMARY KEY,
first_name VARCHAR(30),
last_name VARCHAR(30),
address address_objtyp);
INSERT INTO employees VALUES (
103, 'Fred', 'Couples',
address_objtyp('9201 Park St', 'Alexandria', 'VA'));
<?xml version="1.0"?>
<xsql:query null-indicator="yes" connection="demo"
allow-client-style="yes" xmlns:xsql="urn:oracle-xsql">
select * from employees
</xsql:query>
<?xml version="1.0" ?>
- <ROWSET xsql-timing="20">
- <ROW num="1">
<ID>103</ID>
<FIRST_NAME>Fred</FIRST_NAME>
<LAST_NAME>Couples</LAST_NAME>
- <ADDRESS>
<STREET>0x39323031205061726B205374</STREET>
<CITY>0x416C6578616E64726961</CITY>
<STATE>0x5641</STATE>
</ADDRESS>
</ROW>
</ROWSET>
I'm using the most recent jdbc thin driver (ojdbc14.jar) that is for jdk 1.4. I'm using a 9.0.1 db, and I'm using xdk for java 9.2.0.3. So I thought that the thin driver is not capable, so I tried the oci driver, and find another set of problems.
I get the following error:
Oracle XDK Java 9.2.0.3.0 Production
XSQL-017: Unexpected Error Occurred
java.lang.UnsatisfiedLinkError: no ocijdbc8 in java.library.path
Now why does XDK insist to look for ocijdbc8 if I only have ocijdbc9.dll installed on my client? The config file only allows oci8 in the dburl specification, which is probably why XDK insists to look for ocijdbc8, but I CANNOT specify oci9, which would make sense to me, although it's most likely not a valid specification.
<connection name="9ic">
<username>scott</username>
<password>tiger</password>
<dburl>jdbc:oracle:oci8:@</dburl>
<driver>oracle.jdbc.OracleDriver</driver>
<autocommit>true</autocommit>
</connection>
And lastly documentation that comes with ojdbc14.jar indicates to now use a different specification for the jdbc thin driver. Instead of the usual
<dburl>jdbc:oracle:thin:@host:port:sid</dburl>
it recommends
<dburl>jdbc:oracle:thin:@//host:port/service</dburl>
however this does not work with XDK 9.2.0.3. Any ideas why not?
By the way if I use SQL*Plus and select * from employees, I get the desired result in SQL*Plus, which suggests to me that I DO need the oci driver for XSQL Servlet. So how do I get XSQL Servlet 9.2.0.3 to use the oci 9 driver. I know how to set wrapper.path in the servlet config file to find ocijdbc9.dll, but XSQL Servlet still wants to find ocijdbc8.
I sense that there is a bug hidden somewhere in the XDK kit.
Steve.How do I use xsql servlet to return an object which contains street address etc. as a character string and not a hexadecimal string. If I use the following ddl and implement the following xsql, I get the following results.
CREATE TYPE address_objtyp AS object
(street VARCHAR(30),city VARCHAR(30),state VARCHAR(2));
CREATE SEQUENCE employees_seq START WITH 105 INCREMENT BY 1;
CREATE TABLE employees(
id NUMBER(4) CONSTRAINT emp_pkId PRIMARY KEY,
first_name VARCHAR(30),
last_name VARCHAR(30),
address address_objtyp);
INSERT INTO employees VALUES (
103, 'Fred', 'Couples',
address_objtyp('9201 Park St', 'Alexandria', 'VA'));
<?xml version="1.0"?>
<xsql:query null-indicator="yes" connection="demo"
allow-client-style="yes" xmlns:xsql="urn:oracle-xsql">
select * from employees
</xsql:query>
<?xml version="1.0" ?>
- <ROWSET xsql-timing="20">
- <ROW num="1">
<ID>103</ID>
<FIRST_NAME>Fred</FIRST_NAME>
<LAST_NAME>Couples</LAST_NAME>
- <ADDRESS>
<STREET>0x39323031205061726B205374</STREET>
<CITY>0x416C6578616E64726961</CITY>
<STATE>0x5641</STATE>
</ADDRESS>
</ROW>
</ROWSET>
I'm using the most recent jdbc thin driver (ojdbc14.jar) that is for jdk 1.4. I'm using a 9.0.1 db, and I'm using xdk for java 9.2.0.3. So I thought that the thin driver is not capable, so I tried the oci driver, and find another set of problems.
I get the following error:
Oracle XDK Java 9.2.0.3.0 Production
XSQL-017: Unexpected Error Occurred
java.lang.UnsatisfiedLinkError: no ocijdbc8 in java.library.path
Now why does XDK insist to look for ocijdbc8 if I only have ocijdbc9.dll installed on my client? The config file only allows oci8 in the dburl specification, which is probably why XDK insists to look for ocijdbc8, but I CANNOT specify oci9, which would make sense to me, although it's most likely not a valid specification.
<connection name="9ic">
<username>scott</username>
<password>tiger</password>
<dburl>jdbc:oracle:oci8:@</dburl>
<driver>oracle.jdbc.OracleDriver</driver>
<autocommit>true</autocommit>
</connection>
And lastly documentation that comes with ojdbc14.jar indicates to now use a different specification for the jdbc thin driver. Instead of the usual
<dburl>jdbc:oracle:thin:@host:port:sid</dburl>
it recommends
<dburl>jdbc:oracle:thin:@//host:port/service</dburl>
however this does not work with XDK 9.2.0.3. Any ideas why not?
By the way if I use SQL*Plus and select * from employees, I get the desired result in SQL*Plus, which suggests to me that I DO need the oci driver for XSQL Servlet. So how do I get XSQL Servlet 9.2.0.3 to use the oci 9 driver. I know how to set wrapper.path in the servlet config file to find ocijdbc9.dll, but XSQL Servlet still wants to find ocijdbc8.
I sense that there is a bug hidden somewhere in the XDK kit.
Steve. -
Lower case tag names in XSQL query
XSQL queries appear to default all column tag names to upper case, even when you specifically use lower case characters. Is there any way to get them into lower case?
For example,
<?xml version="1.0"?>
<test connection="devel" xmlns:xsql="urn:oracle-xsql">
<xsql:query rowset-element="" row-element="" null-indicator="yes">
select 'hello' as hi from dual
</xsql:query>
</test>
Results in,
<?xml version="1.0" ?>
<test>
<HI>hello</HI>
</test>
I would really like to get <HI> to <hi>...
thanks.You can also preserve case by putting quotes around the column alias:
For example,
<?xml version="1.0"?>
<test connection="devel" xmlns:xsql="urn:oracle-xsql">
<xsql:query rowset-element="" row-element="" null-indicator="yes">
select 'hello' as "hi"
, 'Hello' as "Hi"
, 'HELLO' as "HI"
from dual
</xsql:query>
</test>
This way you can also get mixed case. -
Encoding issue with " " Less than sign
Hello Experts,
I am working on Receiver Webservice scenario where I am facing issue with "<" less than sign. SAP XI system automatically replace it with "<" sign. I can see the changed value in Audit log of communication channel.
Web service is not able to accept the data and I can see error message in audit log
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAPEXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 573). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type._
When I check the payload in audit log I can see the XML structure properly but as I open it in Notepad I can see character code "<" instead of u201Cless than <u201D symbol.
Audit log XML file is as given below
<?xml version="1.0" encoding="utf-8" ?>
- <ns1:TurnaroundDetail xmlns:ns1="http://isotrak.com/webservices">
<ns1:sessionid>3f2f2592-39d5-456e-8cf2-5d7ee81402c8</ns1:sessionid>
<ns1:data><Request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><TurnaroundDetail><PlannedJobDepartureDatesFrom="2011-03-01T12:01:23.00" To="2011-03-01T12:07:10.00"/><DepotReference DepotReference="EASTLEIGH"/><DepotReference DepotReference="CHANDLERS"/></TurnaroundDetail></Request></ns1:data>
</ns1:TurnaroundDetail>
When I open it in notepad I can see converted value
<?xml version='1.0' encoding='utf-8'?>
<TurnaroundDetail xmlns='http://isotrak.com/webservices'><sessionid>dcc4adcd-ce8f-403d-a1cf-01fcc5aab066</sessionid><data><Request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><TurnaroundDetail><PlannedJobDepartureDatesFrom="2011-03-02T08:28:29.00" To="2011-03-02T08:38:09.00"/><DepotReference DepotReference="EASTLEIGH"/><DepotReference DepotReference="CHANDLERS"/></TurnaroundDetail></Request></data></TurnaroundDetail>
I hope this is not caused due to AnonymizerBean configured in receiver SOAP comm channel.
anonymizer.acceptNamespaces http://isotrak.com/webservices ''
anonymizer.encoding ISO-8859-1 (also tried utf-8)
anonymizer.quote ''
Could you please suggest if I can get rid of "<" character and get < less than sign? Or it is obvious behaviour by SAP XI system w.r.t Encoding and Receiver end needs to decode this character?
Note: As per Web service requirement whole XML data to be processed by webservice is populated in single Data field. As here we are populating whole XML data file in one field named data
Thanks in advance.
Vinit.Simply typing "Test <test> test" into a frame and exporting that yields
<ParaStyle:Body>Test \<test\> test
and reading it back into ID gives the expected result. -
Error Writing Less Than Sign with FileAdapter
Hello.
Looking at the Flow Trace I can that the input variable of the FileAdapter is being populated correctly (XML tags). When looking at the file's contents though, the result of the less than sign is its character entity: '<';.
Is there a way to force it to print the less than sign? Also, why does it write the character entity for the less than sign and not the greater than sign?
Thanks.
Edited by: oracleistheway on May 24, 2013 6:32 AMHi Arik. Thank you for that information but it is not working. I think it is not working because the DOE feature is done during an XSL process.
I was able to get my desired result by creating a native file and Delimited type. I then selected File contains only one record and had it delimited by Single Space and no optional delimiter.
Thank you all for looking at this thread.
Edited by: oracleistheway on May 26, 2013 10:33 AM -
XSQL bug when using CURSOR in xsql:query SELECT statement?
Hi there,
When I tested with different XSQL pages, I found out that if I
did not involve any XSQL pages that contain "CURSOR", I received
data correctly and when I shut down Tomcat, Oracle DB server did
NOT create any dump file (???). However, as long as I involve a
XSQL page which contains "CURSOR", even I received data
correctly, but when I shut down my Tomcat, Oracle DB server
created a dump file (???).
for example, if I involve xsql:query like:
<xsql:query>
SELECT emp_name,
emp_id
CURSOR( SELECT emp_address
from address a
where a.emp_id = b.emp_id)
FROM employee b
</xsql:query>
Once, I involve this xsql page, when I shut down Tomcat, Oracle
dB will create a dump file on the server.
Even when I run this xsql page from
oracle.xml.xsqlXSQLCommandLine, Oracle dB server still create a
dump file on the server.
Any idea for help ?
Thanks,Hi,
Is this what you are trying:
try {
Statement *stmt = conn->createStatement("SELECT ename AS aaaaaaaaaaaaaaa FROM emp");
ResultSet *rs = stmt->executeQuery ();
vector<MetaData> md = rs->getColumnListMetaData ();
int numCols = md.size ();
cout<< "Number of columns :" << numCols << endl;
string *colName = new string [numCols];
int type = (int ) malloc (numCols);
for (int i = 0; i < numCols; i++ ) {
int ptype = md [ i ].getInt (MetaData::ATTR_PTYPE);
if ( ptype == MetaData::PTYPE_COL ) {
colName[ i ] = md[ i ].getString (MetaData::ATTR_NAME);
cout<<"Column Name :" << colName[ i ] << endl;
delete[] colName;
stmt->closeResultSet (rs);
conn->terminateStatement (stmt);
catch (SQLException &ex) {
cout<<ex.getMessage()<<endl;
}The above snippet works correctly for me.
Rgds.
Amogh -
XSQL query output as parameter for next xsql query
Hi,
Is it possible to use the output of one xsql query as input parameter for the next xsql query in the same file. I am trying to retreive an id from the query and use it in the next one. I cannot combine all the queries into one, since I intend to make the first query a database function that returns the id I am looking for. I am looking for something like this
<xsql:query>
select '1000' as myid
from dual
</xsql:query>
<xsql:query>
select add1,ro1
from table1
where id = {@myid}
</xsql>
I need the id returned by the first query to be used in the second one. Eventually my first query will be a stored procedure that validates the users rights and on sucess return the following tag <myid> 1000 <myid>.
Please let me know , how I can achieve my goal of validating a user's priveleges and then executing the second query.
Thanks
PadmajaHi ,
Thanks for the response.This works if the first query is a select .
If the first query was a call to a db procedure that returned the <myid>100<myid> would this still work?
<xsql:set-page-param name="myid">
<xsql:include-owa>
xyz;
</xsql:include-owa>
</xsql:set-page-param>
<xsql:include-param name="myid"/>
<xsql:query>
select name from mytable where id={@myid}
</xsql:query>
I have to use include-owa as the db procedure xyz does some cookie validations and then returns an id based on that. The procedure xyz returns an xml tag of form <myid>100<myid>
This does not work as the value of myid is not available to the second query.
Thanks
Padmaja -
Some of the xsql-query tag attributes in an XSQL page are only available in the XSQL page, not in the Query tag from the component palette.
1. Create a XSQL page.
2. Add a Query (xsql-query) tag from the Component Palette. The Query lists some xsql-query tag attributes.
3. In the XSQL page, the xsql-query tag lists some additional attributes such as page-param, date-format and error-statement that are not listed in the Query frame when the Query tag is selected from the component pallette.Correction.
3. In the XSQL page, the xsql-query tag lists some additional attributes such as bind-params, date-format and error-statement that are not listed in the Query frame when the Query tag is selected from the component pallette. -
Some of the xsql-query tag attributes in an XSQL page are only available in the XSQL page, not in the Query tag from the component palette.
1. Create a XSQL page.
2. Add a Query (xsql-query) tag from the Component Palette. The Query lists some xsql-query tag attributes.
3. In the XSQL page, the xsql-query tag lists some additional attributes such as page-param, date-format and error-statement that are not listed in the Query frame when the Query tag is selected from the component pallette.Correction.
3. In the XSQL page, the xsql-query tag lists some additional attributes such as bind-params, date-format and error-statement that are not listed in the Query frame when the Query tag is selected from the component pallette. -
XSQL new feature suggestion: transform="url" for xsql:query
To the Oracle XML developers:
I'd like to suggest adding the transform="url" attribute/feature to the <xsql:query> action.
This would allow one to transform and/or apply XSLT conditional logic to the posted XML before it reaches the <xsql:query> action. A couple of key areas where I think this would be very useful are:
1. handling multiple HTML parameters of the same name.
Currently, the only way to handle this in an <xsql:query> action is to call a Java program via <xsql:action> that can parse the rowified parameters of the same name, then transform it in a format suitable for the <xsql:query>.
2. verifying user session login status for password protected XSQL pages.
If one could use XSLT to check user authentication BEFORE the <xsql:query> action you could display a login page if the user is not authenticated.
Since the transform="url" feature is already available for other tags (<xsql:update>, <xsql:delete>, etc) I would think adding this to the <xsql:query> action would not require extensive coding from the Oracle XML development team, and yet this simple but powerful feature could help us users to develop pure XML solutions that don't require calls to external Java actions.
MichaelThere would also be able to simply add the "perspective"as in Photoshop, probablyeasier to develop and integrate the interface.
-
xsql:query - Is there a character limit on the SQL contained in the tag?
Is there a limit to the length of the SQL contained in the
<xsql:query> tag ?
I've been very successful with short queries using xsql:query
tags, however, for longer queries they seem to fail the XML
Syntax check using JDeveloper 3.2.3.
The resulting error from the XSQLServlet is XSQL-005 page is not
well formed with the following:
XML-0201: (Fatal Error) Expected name instead of .
XML-0122: (Fatal Error) '=' missing in attribute.
XML-0125: (Fatal Error) Attribute value should start with quote
(Posted example 10/16/01)Hello Bill,
>> … to our apex environment (9.2)
The following might give you some more information on your possible situation -
Re: Is there a maximum number of characters allowed in PL/SQL Anonymous Blo
ORA-06550 recieved when trying to modify existing page after 3.1 Apex upg
Regards,
Arie. -
I am getting an error when running an xsql:query. I can run simple queries, so it is not a connection porblem. The xml parses in jDeveloper10g so it appears to not be ill-formed XML. I have tried containing the SQL statement in CDATA tags, and tried replacing < and > with their entity references < and & gt; and I have tried both at the same time.
The Query is as follows
<page xmlns:xsql="urn:oracle-xsql" connection="V7Test">
<xsql:query fetch-size="100" max-rows="-1" null-indicator="no" tag-case="lower">
<![CDATA[
select
ts_jobs.job_number,
sum(ts_jobs.period_hours),
ts.period_end_date
from
etr.etr_timesheet_days ts_days,
etr.etr_timesheet_hours ts_hours,
etr.etr_timesheet_jobs ts_jobs,
etr.etr_timesheets ts
where
ts_hours.hours != 0
and (
(nvl(ts_jobs.corrected_id,0) = 0
and nvl(ts_hours.corrected_id,0) = 0
and ts.date_sent_to_pmjcap >=ts_hours.date_entered)
or (ts.date_sent_to_pmjcap < ts_hours.date_corrected)
and ts_days.timesheet_day_id = ts_hours.timesheet_day_id
and (
(ts_days.period_date in ('01-JAN-03','02-JAN-03','03-JAN-03')
and ts.period_end_date = '03-JAN-03')
or (ts_days.period_date in ('27-DEC-03','28-DEC-03','29-DEC-03','30-DEC-03','31-DEC-03')
and ts.period_end_date = '02-JAN-04')
and ts_days.timesheet_id = ts.timesheet_id
and ts_jobs.timesheet_job_id = ts_hours.timesheet_job_id
and (
(ts_jobs.job_number in (9719003,9849003,9849001,9719001))
or (ts_jobs.job_number in (9719333,9849333,9849334,9719334))
or (ts_jobs.job_number in (9719004,9849004,9719009,9849009))
or (ts_jobs.job_number in (9719444,9849444,9849445,9719445))
and ts.timesheet_id = ts_jobs.timesheet_id
and ts.employee_number = '050405'
and exists
(select
emp_clock,
date_incurred
from
asi_apps.vw00plw
where
substr(job_number,-8) = ts_jobs.job_number
and date_incurred = ts.period_end_date
and emp_clock = lpad('050405',6,0)
group by
ts_jobs.job_number,
ts.period_end_date,
ts_hours.hours
]]>
</xsql:query>
The Error I get is as follows
<?xml version="1.0" encoding="windows-1252" ?>
- <!--
| Uncomment the following processing instruction and replace
| the stylesheet name to transform output of your XSQL Page using XSLT
<?xml-stylesheet type="text/xsl" href="YourStylesheet.xsl" ?>
-->
- <page>
<error>oracle.xml.sql.OracleXMLSQLException: Character ')' is not allowed in an XML tag name.</error>
</page>
I think it is parsing a '<' as a tag delimiter.
Anyone have a similiar problem? a workaround?
regards,
BillI found the answer. The problem is the selected 'column' sum(ts_jobs.period_hours). Apparently, the XSQL servlet attempts to assign the value 'sum(ts_jobs.period_hours)' directly to an XML element.total_hours. That fails.
The work-around is to use an alias. This code works
sum(ts_jobs.period_hours) total_hours,
A fix to the XSQL servlet would be in order, perhaps adding a CDATA container around 'columns' that are are normal SQL functions.
regards,
Bill
Maybe you are looking for
-
I have silverlight why are you telling me to download the pluggin?
''duplicate - locking - https://support.mozilla.com/en-US/questions/901798'' I just tried to look at Netflixs. At first your site told me to download flashdrive which I have the latest version. I went back in to bring up netflix again and now your si
-
Two calculations are required for a single condition type
Hello Experts, I have a requirement to calculate the VAT conditon type in a pricing procedure...like in one case ( If TAX Indicator set to "0,1,2" at sales order header level) tax should be calculate on PR00 & 3 other condition types....in second c
-
Usage Meter Not showing under My Services
ANyone else have this problem? I log into my account; switch to the My Services Tab and then hit the Green B and all I see is "BundleComponent". Would be nice to know when I am reaching my limit....
-
Errror: DDE server:Photoshop exe-Fatal Application Exit
I am receiving the following error: DDE server:Photoshop exe-Fatal Application Exit window the specified module cannot be found>c\program files (x86)\common files\adobe\adobe version que\cs3\client\3.1.0\versioncue.dll i have CS3 master collection us
-
BB8520 Application Loader Was Unable Connect With Your Device .
Hi , I am upgrade my bb8520 using bd program , but untill reconnecting to jvm it come up applicayion loader was unable connect with your device . please reconect your device , enter the password , if required , and click retry . but the phone is runn