XSQL Apache XSQL Demo errors on helloworld

Hello I am trying to get the XSQL demos to work on Apache 1.3.20 and Jserv 1.1.1. THe examples just display the SQL statement no results returned.
Here is my Jserv properties file
ApJservAction .xsql
wrapper.classpath=C:\Program Files\Apache JServ 1.1.1\ApacheJServ.jar
wrapper.classpath=c:\jsdk2.0\lib\jsdk.jar
wrapper.classpath=C:\OraHome\jdbc\lib\classes111.zip
wrapper.classpath=C:\OraHome\jdbc\lib\classes12.zip
#wrapper.classpath=C:\xsql\lib\oraclexmlsql.jar
wrapper.classpath=C:\xsql\lib\oraclexsql.jar
wrapper.classpath=C:\xsql\lib\xmlparserv2.jar
wrapper.classpath=C:\xsql\xdk\admin
My Jser config
#ApJServAction .jsp /servlets/org.gjt.jsp.JSPServlet
#ApJServAction .gsp /servlets/com.bitmechanic.gsp.GspServlet
#ApJServAction .jhtml /servlets/org.apache.servlet.ssi.SSI
#ApJServAction .xml /servlets/org.apache.cocoon.Cocoon
ApJServAction .xsql /servlets/oracle.xml.xsql.XSQLServlet
My database iS Oracel 8.1.6. I have no problems performing XSQL taks from the command line XSQL ulity but over Apache only the SQL statment shows.
My directory for XDK is C:\xsql. If I chnge the XMLConfig connection it will not connect so it can see the file.
Any help would be great ?
Thanks
Aaron

What DB version? What does your table look like (datatype-wise for the columns) ?

Similar Messages

XSQL-007 Database connection error.

I got following message when click sample heloworld.xsql:
Oracle XSQL Servlet Page Processor 0.9.9.1 (Technology Preview)
XSQL-007: Cannot acquire a database connection to process page.
Invalid Oracle URL specified: OracleDriver.connect
We're using RH Linux 6.1, Apache Tomcat 3.1 Beta and XSQL 0.9.9.1. The database connection string in XSQLConfig.xml is:
<connection name="demo">
<username>scott</username>
<password>tiger</password>
<dburl>jdbc:oracle:jdbc:@home:1521:home</dburl>
<driver>oracle.jdbc.driver.OracleDriver</driver>
</connection>
null

<dburl> as posted is incorrect.
A sample that is correct for the JDBC thin
driver is:
<connection name="demo">
<username>scott</username>
<password>tiger</password>
<dburl>jdbc:oracle:thin:@localhost:1521:xml</dburl>
<driver>oracle.jdbc.driver.OracleDriver</driver>
</connection>
Note "jdbc:oracle:thin" and not "jdbc:oracle:jdbc"
hope this helps.

XSQL class not found error

HI Gentlemen,
I tried to execute the following:
xsql ziffer.xsql ziff=01700with no output file and one parameter. I always got the following:
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/i18n/util/LocaleMapperWell, this jar does not have it, true. But in my CLASSPATH there is an orai18n-mappig.jar, and this has it (I listed the contents). All settings are made according to Oracle's description in a note. Now I am blurred, why xsql does not use this other jar? When I go with
java oracle.xml.xsql.XSQLCommandLine ziffer.xsqlit works fine but I can not supply a parameter to ziffer.xsql. Can anyone help me?
Thank you very much,
kind regards:
Miklos HERBOLY
Edited by: mh**** on Jun 13, 2011 11:25 PM

Hi Jochen,
I'm working with Tomcat 4.0.3, FOP 20.0.3 and XDK 9.2.0.1.0, too.
I've copied all the jar-files into tomcat/common/lib. I think that you can't use the MessageHandler in fop20.0.3. I'm using the following serializer:
package diva.xml.xsql.serializers;
import org.w3c.dom.Document;
import java.io.PrintWriter;
import oracle.xml.xsql.*;
import org.apache.fop.apps.*;
import org.apache.log.*;
import org.apache.log.format.*;
import org.apache.log.output.io.*;
import org.apache.avalon.*;
import java.io.*;
public class XSQLFOP203Serializer implements XSQLDocumentSerializer {
private static final String PDFMIME = "application/pdf";
private static final String CONFPATH = "/usr/local/fop/conf/userconfig.xml";
public void serialize(Document doc, XSQLPageRequest env) throws Throwable {
try {
// Open user config file
File userConfigFile = new File(CONFPATH);
Options options = new Options(userConfigFile);
// First make sure we can load the driver
Driver FOPDriver = new Driver();
// Setup logging
Hierarchy hierarchy = Hierarchy.getDefaultHierarchy();
PatternFormatter formatter = new PatternFormatter("[%{priority}]: %{message}\n%{throwable}" );
LogTarget target = null;
target = new StreamTarget(System.out, formatter);
hierarchy.setDefaultLogTarget(target);
Logger log = hierarchy.getLoggerFor("fop");
log.setPriority(Priority.INFO);
FOPDriver.setLogger(log);
// Then set the content type before getting the reader/
env.setContentType(PDFMIME);
FOPDriver.setRenderer(FOPDriver.RENDER_PDF);
FOPDriver.setOutputStream(env.getOutputStream());
FOPDriver.render(doc);
catch (Exception e) {
// Cannot write PDF output for the error anyway.
// So maybe this stack trace will be useful info
e.printStackTrace(System.err);
Hope this helps
Uwe

XSQL und BEA Weblogic ERROR:XSQL-013

We develop an web-application using XSQL to generate XML, which is further transformed via XSL to HTML or PDF.
As IDE we use JDeveloper 9.0.3.1.
Running and debugging in JDeveloper works fine.
We deploy the application as war-file on bea weblogic 7.2.
When starting the xsql-servlet / calling the xsql file we get the following error:
Oracle XSQL Servlet Page Processor 9.0.3.0.0 (Production)
XSQL-013: XSQL Page URI is null or has an invalid format.
XSQLConfig is located in:
WEB-INF\classes\XSQLConfig.xml</li>
XSQLConfig remains untouched and holds the right connection (OCI)
<connection name="KimOci">
<username>...</username>
<password>...</password>
<dburl>jdbc:oracle:oci8:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=...)(PORT=...)))(CONNECT_DATA=(SID=...)))</dburl>
<driver>oracle.jdbc.driver.OracleDriver</driver>
</connection>
XSQL-File starts with
<?xml version = "1.0" encoding = "ISO-8859-1"?>
<page xmlns:xsql="urn:oracle-xsql" connection="KimOci">
<xsql:include-request-params/>
<xsql:include-param name="ImageUrl"/>
<xsql:include-param name="BaseUrl"/>
<xsql:include-param name="LocalUrl"/>
<xsql:query max-rows="-1" null-indicator="no" tag-case="lower" rowset-element="global" row-element="date">
select ...
Whats wrong or missing?
Thanks

Trying to check whats going on within the XSQL-Prozessor we tried the programmatic approach.
First step is to call XSQL from within an action /jsp .
<%
String baseUrl = request.getScheme()
+ "://"
+ request.getServerName()
+ ":"
+ request.getServerPort()
//+ "/"
+ request.getContextPath()
+ "/"
URL pageUrl = new URL(baseUrl+"report/untitled2.xsql");
XSQLRequest req = new XSQLRequest(pageUrl);
PrintWriter of = new PrintWriter( new FileOutputStream("./report.xml"));
PrintWriter ef = new PrintWriter( response.getOutputStream());
Hashtable params = new Hashtable(0);
req.process(params, of, ef );
%>
But still there is an error.
This time we got:
Oracle XSQL Programmatic Page Processor 9.0.3.0.0 (Production) XSQL-005: XSQL page is not well-formed. XML parse error at line 2, char 1 Expected 'EOF'
The code of untitled2.xsql
<?xml version = "1.0" encoding = "ISO-8859-1"?>
<page xmlns:xsql="urn:oracle-xsql" connection="KimOci">
<amen>leer</amen>
</page>

Error: XSQL-005: XSQL page is not well-formed

I am tring to execute the following simple query:
<?xml version="1.0"?>
<xsql:query connection="rio" xmlns:xsql="urn:oracle-xsql">
select user from dual
</xsql:query>
using XSQL with Sun's JavaWebServer2.0 and am getting the following error:
Oracle XSQL Servlet Page Processor 1.0.4.1 (Production)
XSQL-005: XSQL page is not well-formed.
XML parse error at line 2, char 1
Expected 'EOF'.
Running the XML syntax check in JDeveloper shows no errors. Any ideas of where the configuration may have gone wrong?
Thanks,
Claire
null

Steve,
Actually any file name (even if the file does not exist) is returning the same error.
I tried using Web-to-Go and I am getting the following error:
"WTG-10109: Web-to-go could not locate requested URL
Web-to-go could not locate requested URL /xsql/index.html"
I have my test .xsql files in a c:/xsql/xtest folder and am calling them through http://localhost:8080/xsql/xtest/message.xsql for the JWS and trying http://localhost:7070/xsql/index.html (WTG)to see the index.html, but no joy..
Any other ideas?
Thanks,
Claire
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Steve Muench ([email protected]):
Do you maybe have two versions of this file? One that JDev is checking and the other that the web server is reading?
Try renaming the file you think that the XSQL Servlet is serving, then re-request it through the browser with the OLD name. Do you now get an error like "unable to locate file?" or do you still see the parse error?<HR></BLOCKQUOTE>
null

Problem testing XSQL Servlet, XSQL-0007

Hi,
I'm testing the XSQL Servlet, as a lot of people do. I installed
it on Apache Web Server with JRUN servlet engine, following the
Release Notes, but it does not work at all. I get the following
message, when I try to run helloworld.xslq:
Oracle XSQL Servlet Error
XSQL-0007: XML Parsing error on requested page
<2,1>: Expected EOF
I checked it several times but it seems to be right, exactly as
in the release notes.
I read here that other people (SHankar) had the same problem, but
your answer did not solve it:
: : Oracle XML Team wrote:
: : : I presume by XML source code, you are referring to
the .xsql
: : : source code. If that is the case then you have not
: registered
: : : the XSQL servlet to that extension in the web server you
are
: : : using. Check out that section of the installation
: : instructions.
Please, tell me what can I do to start testing it, since I can
test nothing, it does not work.
Regards,
Esteban
null

Oracle XML Team wrote:
: The only thing that can cause
: this error is if the page you
: are requesting is not a well-formed
: XML document.
: Oracle XML Team
: http://technet.oracle.com
: Oracle Technology Network
I'm requesting the page that you provide as a demo:
helloworld.xsql
I checked it and it is a well-formed XML document.
Anyway, other examples that you provide with the xsqlservlet zip
file don't work either.
null

Xsql CURSOR XSQL-017

Hi everybody.
I have a problem when I try to run a xsql with my browser.
I type: http://hostaix433/TremaDesa/XSQL/SEst1.xsql and I get the next message :
Oracle XDK Java 9.2.0.6.0 Production
XSQL-017: Unexpected Error Occurred
java.lang.NoClassDefFoundError: java/util/Map
at
at oracle.jdbc.driver.OracleConnection.addClassMapEntry(OracleConnection.java:2849)
at oracle.jdbc.driver.OracleConnection.addDefaultClassMapEntriesTo(OracleConnection.java:2843)
at oracle.jdbc.driver.OracleConnection.initializeClassMap(OracleConnection.java:2529)
at oracle.jdbc.driver.OracleConnection.ensureClassMapExists(OracleConnection.java:2523)
at oracle.jdbc.driver.OracleConnection.getTypeMap(OracleConnection.java:2829)
at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:5849)
at oracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java:765)
at oracle.xml.sql.dataset.OracleXMLDataSetExtJdbc.getColumnTypeObject(OracleXMLDataSetExtJdbc.java:494)
at oracle.xml.sql.core.OracleXMLConvert.createColNames(OracleXMLConvert.java:1100)
at oracle.xml.sql.core.OracleXMLConvert.getXML(OracleXMLConvert.java:848)
at oracle.xml.sql.query.OracleXMLQuery.getXMLDOM(OracleXMLQuery.java:361)
at oracle.xml.sql.query.OracleXMLQuery.getXMLDOM(OracleXMLQuery.java:308)
at oracle.xml.xsql.actions.XSQLQueryHandler.handleAction(XSQLQueryHandler.java:246)
at oracle.xml.xsql.XSQLDocHandler.getDocument(XSQLDocHandler.java:149)
at oracle.xml.xsql.XSQLPageProcessor.process(XSQLPageProcessor.java:140)
at oracle.xml.xsql.XSQLServlet.doGet(XSQLServlet.java:60)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:499)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456)
at org.apache.jserv.JServConnection.run(JServConnection.java:294)
at java.lang.Thread.run(Thread.java)
My xsql file :
<xsql:query connection="bddesa2_trema" xmlns:xsql="urn:oracle-xsql">
SELECT idse, nombre, modoacceso, nombrepc,
CURSOR ( SELECT idbus, nombre, puerto, dirdatos, idse
FROM bus
WHERE bus.idse = subestacion.idse ) as buses
FROM subestacion WHERE subestacion.nombre = 'SubTrema'
</xsql:query>
I get the error message ONLY when I use de CURSOR statement.
Somebody could help me?
Thanks in advanced
Diego Robatto

Please refer to the section:Using the CURSOR Operator for Nested Rowsets
https://myswat.swarthmore.edu/xsql/java/xsql/relnotes.html#ID2602

Character problems with xsql:include-xsql reparse="yes"

I have a problem retrieving XML-fragments from CLOB columns.
Danish ISO-8859-1 characters (aelig, oslash, aring) are returned as "?" from Apache/Jserv when using xsql:include-xsql reparse="yes".
My platform is Solaris9/Oracle-9.2.0.2/XDK-9.2.0.4.
Database characterset is we8iso8859p1.
I'm using the Apache/Jserv that comes with Oracle 9.2.0.1.
Steps to reproduce problem:
-- Table data:
create table tab1 (id number,clob_col clob);
insert into tab1 values(1, '<x>fxe</x>');
/*inserted characters are aelig(230), oslash(248), aring(229)*/
commit;
-- test.xsql:
<?xml version="1.0" encoding="ISO-8859-1"?>
<testdata xmlns:xsql="urn:oracle-xsql" connection="pnrtest">
<xsql:include-xsql reparse="yes" href="inc.xsql" />
</testdata>
-- inc.xsql:
<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="unquote_clob_col.xsl"?>
<xsql:query
xmlns:xsql="urn:oracle-xsql"
connection="pnrtest"
tag-case="lower"
>
select clob_col
from tab1
</xsql:query>
-- unquote_clob_col.xsl:
<xsl:stylesheet
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:output method="xml" indent="yes" omit-xml-declaration="no" encoding="ISO-8859-1"/
<xsl:include href="identity.xsl"/>
<xsl:template match="clob_col">
<clob_col>
<xsl:value-of select="." disable-output-escaping="yes"/>
</clob_col>
</xsl:template>
</xsl:stylesheet>
-- identity.xsl:

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:template match="node()|@*">

<xsl:copy>

<xsl:apply-templates select="@*|node()"/>
</xsl:copy>
</xsl:template>
</xsl:stylesheet>
-- Notes:
Running test.xsql works fine with XSQL command-line, but FAILS through Apache/Jserv (danish characters are returned as "?").
inc.xsql works fine through XSQL command-line and Apache/Jserv, problem only happens with xsql:include-xsql reparse="yes" (e.g. test.xsql).
xsql:include-xml works fine, but I cannot use this, bca. in my real business case I'm selecting more than one row from the database.
I've checked and double-checked my jserv.properties several times, and believes it to be correct.
The xsql:include-xsql reparse="yes" technique works fine in our Solaris9/Oracle-8.1.7/iAS-1.0.2.2 environment.
Any suggestions ?
-- Peter ([email protected])

If I put the following line in jserv.properties:
wrapper.env=LANG=en_US.ISO8859-1
the problem with xsql:include-xsql reparse="yes" seems to go away.
Really strange, since Oracle products in my experience normally only uses NLS_LANG, not LANG.
Also, we're accessing several databases with different charactersets from the same ApacheJserv installation, so I don't understand why LANG (or NLS_LANG) should be set to a particular value.
Can anybody explain ?
-- Peter

Xsql:include-xsql problem

I am attempting to include an authentication widget into each page of a site I am working on using the following code:
<?xml version="1.0"?>
<datapage connection="myDB" xmlns:xsql="urn:oracle-xsql">
<xsql:include-xsql href="authenticate.xsql?xapi_version=1&co_num=106&username=useruser&password=password"/>
</datapage>
The included page is as follows:
<?xml version="1.0"?>
<auth connection="myDB" xmlns:xsql="urn:oracle-xsql">
<xsql:include-owa>
BEGIN
XAPI.Test('{@xapi_version}','{@co_num}','{@username}','{@password}');
END;
</xsql:include-owa>
</auth>
I have tried the xsql:include-xsql tag with the reparse attribute set to both 'yes' and the default value but each time I attempt to access the page I receive the following error:
XSQL-005: XSQL page is not well-formed.
XML parse error at line 3, char 67
Expected ';'.
I cannot source the reason for this error because if I access the page to be included direct (with parameters on the query string) it works fine. Any help would be greatly appreciated.
thanks-->cristian
null

This bug was fixed in XSQL 1.0.4.3, the latest production release that is part of the XDK for Java 8.1.7.1 download here on OTN.

Org.apache.jasper.JasperException: Error: Attempt to clear a buffer that's

Hi,
All I am trying to do is execute a <jsp:forward page=""/> commend. The page I am refering to does exists and three other pages that have the same commend are able to forward to the said page with little issue. All the pages are in the same directory and the path indicator to them is correct. Any help in this matter will be highly appreciated.
org.apache.jasper.JasperException: Error: Attempt to clear a buffer that's already been flushed
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
     at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
     at java.lang.Thread.run(Thread.java:534)

jsp:forward always flushes the buffer before proceeding.
Do you have a statement in your jsp like out.flush() before your use jsp:forward? If you do, try removing it

Exception in thread "main" org.apache.axis2.AxisFault: Error in extracting

I am getting this exception when I call the web service from the client. Please help me here.
Exception in thread "main" org.apache.axis2.AxisFault: Error in extracting message properties
     at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:70)
     at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
     at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
     at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
     at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:427)
     at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
     at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
     at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
     at com.ttdev.ss.SecureServiceStub.concat(SecureServiceStub.java:182)
     at com.ttdev.ss.SecureClient.main(SecureClient.java:29)
Caused by: org.apache.rampart.RampartException: Error in extracting message properties
     at org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:386)
     at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:61)
     at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:64)
     ... 9 more
Caused by: org.apache.ws.security.WSSecurityException: Error in converting SOAP Envelope to Document; nested exception is:
     java.lang.UnsupportedOperationException: TODO
     at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:161)
     at org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:272)
     ... 11 more
Caused by: java.lang.UnsupportedOperationException: TODO
     at org.apache.axiom.om.impl.dom.DocumentImpl.setStandalone(DocumentImpl.java:415)
     at org.apache.axiom.om.impl.builder.StAXOMBuilder.createDocument(StAXOMBuilder.java:190)
     at org.apache.axiom.om.impl.builder.StAXOMBuilder.<init>(StAXOMBuilder.java:105)
     at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.<init>(StAXSOAPModelBuilder.java:167)
     at org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:130)
     ... 12 more
Client WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="SecureService"
targetNamespace="http://ttdev.com/ss"
xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200512"
xmlns:wsp="http://www.w3.org/Submission/2006/SUBM-WS-Policy-20060425"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://ttdev.com/ss"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurityutility-1.0.xsd">
<wsdl:types>
<xsd:schema targetNamespace="http://ttdev.com/ss">
<xsd:element name="concat">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="s1" type="xsd:string"/>
<xsd:element name="s2" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="concatResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="r" type="xsd:string">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
<wsdl:message name="concatResponse">
<wsdl:part name="parameters" element="tns:concatResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="concatRequest">
<wsdl:part name="parameters" element="tns:concat">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="SecureService">
<wsdl:operation name="concat">
<wsdl:input message="tns:concatRequest">
</wsdl:input>
<wsdl:output message="tns:concatResponse">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="SecureServiceSOAP" type="tns:SecureService">
<wsp:PolicyReference URI="#p1" wsdl:required="true"/>
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="concat">
<soap:operation soapAction="http://ttdev.com/ss/NewOperation"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SecureService">
<wsdl:port name="p1" binding="tns:SecureServiceSOAP">
<soap:address location="http://localhost:8080/ss/p1"/>
</wsdl:port>
</wsdl:service>
<wsp:Policy wsu:Id="p1">
<sp:AsymmetricBinding>
<wsp:Policy>
<sp:InitiatorToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/12/securitypolicy/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:WssX509V3Token10/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:InitiatorToken>
<sp:RecipientToken>
<wsp:Policy>
<sp:X509Token sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/12/securitypolicy/IncludeToken/Never">
<wsp:Policy>
<sp:WssX509V3Token10/>
</wsp:Policy>
</sp:X509Token>
</wsp:Policy>
</sp:RecipientToken>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:TripleDesRsa15/>
</wsp:Policy>
</sp:AlgorithmSuite>
</wsp:Policy>
</sp:AsymmetricBinding>
<sp:Wss10>
<wsp:Policy>
<sp:MustSupportRefEmbeddedToken/>
<sp:MustSupportRefIssuerSerial/>
</wsp:Policy>
</sp:Wss10>
<sp:SignedParts>
<sp:Body/>
</sp:SignedParts>
<sp:EncryptedParts>
<sp:Body/>
</sp:EncryptedParts>
<sp:EncryptedElements>
<sp:XPath>
//*[local-name()='Signature']
</sp:XPath>
</sp:EncryptedElements>
<sp:SignedSupportingTokens>
<wsp:Policy>
<sp:UsernameToken sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/12/securitypolicy/IncludeToken/AlwaysToRecipient"/>
</wsp:Policy>
</sp:SignedSupportingTokens>
</wsp:Policy>
</wsdl:definitions>

I think you are asking this question not only on the wrong section but also on the wrong website.
The error you are refering to is a Axis2 specific exception, you might get the best answer by posting your question to the Axis2 mailing list:
http://axis.apache.org/axis2/java/core/mail-lists.html
BTW your exception "java.lang.UnsupportedOperationException: TODO"
=> looks like you have some comment left over in your Web-Service invokation. Actually your WSDL has no Method "TODO" so where should this call route to? I guess you should debug your code that invokes the call. Is there really a method TODO.
I am also a bit confused with "Client Side WSDL" actually only the server does create a WSDL file, client only reads it (maybe you have some code generator that uses the WSDL to generate some code .. but the client has no WSDL).
Further you should post a complete working example that can be run by somebody else, espacially with such a specific problem. Otherwise I am afraid hardly anybody will push you to the right direction.
Sebastian

Can I use XSQL pages & XSQL Servlet for oracle 7.3 ?

Can I use XSQL pages & XSQL Servlet
for oracle 7.3 or not?,if it is possible
please give me reply.
Thanks.
Ramesh Nallapu.

Can I use XSQL pages & XSQL Servlet
for oracle 7.3 or not?,if it is possible
please give me reply.
Thanks.
Ramesh Nallapu.
null

"Apache.exe - Application Error" while shutting down Apache

Hi All,
Though this is not a show stopper bug, I am not sure whether this may result any error situation or not.
System: Windows XP SP3
Application: Oracle Apps 11.5.10.2 (RUP6) single node Vision instance.
Directories:
D:\orclapps\orclappsappl
D:\orclapps\orclappscomn
D:\orclapps\orclappsdata
D:\orclapps\orclappsdb\9.2.0
D:\orclapps\orclappsora\8.0.6
D:\orclapps\orclappsora\iAS --> Apache\Apache\Apache.exe
Issue: When I initiate "Oracle Apache Server ORCLAPPS_erp" service shutdown either in Windows Service window or from command prompt using adstpall.cmd, System is showing below error alert and then service getting stopped(purpose achieved). As such I dont see any problem with that. But I would like to fix it to avoid any problems it might cause for which I may not trace out to its root.
Error:"Apache.exe - Application Error" The instruction at 0x####### referenced memory at 0x####### . The memory could not be "read".
From below note I understood such bugs can be avoided by upgrading Apache version 2.0.43. Right now the one came along with vision instance is vesion 1.3 (according to Readme.txt file from Apache\Apache directory.). But I am cue less how to upgrade Apache, whether any Patch exists from Oracle to do this or not. Or, I should not change Apache from apps instance. Even if I can do, how I can do it? Or its nothing to do with Apache version. I am totally confused.
https://issues.apache.org/bugzilla/show_bug.cgi?id=11997#c3
Please advise.
Thanks.

Hi;
XP is not certified platform so its hard to find answer.Thatswhy I suggest use certified platform, also see:
http://www.geekstogo.com/forum/topic/4911-memory-could-not-be-written/
Regard
Helios

XSQL/XSL help (iPlanet): Error processing XSLT stylesheet

hello-
i am running XSQL and XSL pages on an iPlanet web server and i am receiving the following error:
XSQL-011: Error processing XSLT stylesheet: /xslt/page/xsl_page.xsl
XSL-1002: Error while processing include XSL file (\xslt\util\other_xsl.xsl (The system cannot find the path specified)).
here's the deal: other_xsl.xsl (the one it says it can't find) is there in the right place, but the web server is not looking from the document root (which IS set correctly on the web server). it is looking for the file starting at the current directory.
for example, the server is processing /xslt/page/xsl_page.xsl. it is then looking for the include file using this path: /xslt/page/XSLT/UTIL/other_xsl.xsl --- instead of the correct /xslt/util/other_xsl.xsl.
the include statement uses the full path starting from the web root (<xsl:include href="/xslt/util/other_xsl.xsl"/>)
any help would be appreciated.

thanks for the response. the /xslt/util directory is browsable by the web server, and using relative paths does work (that is one of the ways i discovered what was going on in the first place), but i am rebuilding a machine and redeploying an exisiting application-- the intention is to not re-write any code.
the part that is most confusing is that the current code/directory structure works on the current box, but not on my rebuilt box. i have gone through every config file with a fine tooth comb. it appears that the current box and my build are set up exactly the same-- but, like i said, on one it reads the include-path from the document root, on the other from the current directory.
so confusing.

8i EE, corba helloworld demo error

Hi
Machine: PII 300, 128Mb, Red Hat 6.0, 8.1.5 + patch 81501, KDE,
user: oracle
I'm trying to make the corba helloworld demo in
javavm/demo/examples/corba/basic but i can't seem to compile the
idl file.
(I have installed patch 81501, and corrected the typo in
idl2java (TMP=))
It seems that the idl2java is going around in circles...
Question:
How can i resolve this.
Question:
If i want to write some java application, what jdk do i have to
install? (or is it already installed?)
Thanks in advance
Bart De Lathouwer
Aigis, Belgium
null

Hi,
This error usually shoots up due to the incompatibility with the dependecies. Can you please summarise how you went on compiling the application. Meanwhile, I'm trying to simulate same scenario with the GreeterEJB and the Converter examples.
Regards
Raj

XSQL Apache XSQL Demo errors on helloworld

Similar Messages

Maybe you are looking for