XSQL Problem : NoSuchMethodError

After installing the XDK (for Java) and setting up the XSQL environment I get the following problem when starting the XSQL-demo .
I'm using Java JDK1.3 and Tomcat 3.2.1. and JDBC-Lib classes12.zip.
Can anybody help?
Thanks Thomas
Location: /xsql/home/homecontent.xsql
Internal Servlet Error:
java.lang.NoSuchMethodError
     at oracle.xml.xsql.XSQLConfigManager.reloadConfigFile(XSQLConfigManager.java:481)
     at oracle.xml.xsql.XSQLConfigManager.insureConfigurationIsLoaded(XSQLConfigManager.java:191)
     at oracle.xml.xsql.XSQLPageManager.getPage(XSQLPageManager.java:73)
     at oracle.xml.xsql.XSQLPageRequestImpl.getXSQLPage(XSQLPageRequestImpl.java:454)
     at oracle.xml.xsql.XSQLPageProcessor.process(XSQLPageProcessor.java:80)
     at oracle.xml.xsql.XSQLServlet.doGet(XSQLServlet.java:60)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404)
     at org.apache.tomcat.core.Handler.service(Handler.java:286)
     at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
     at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
     at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
     at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:210)
     at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
     at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
     at java.lang.Thread.run(Thread.java:484)

After moving from Tomcat 3.2.1 to Tomcat 3.2.4 the problem disappeared,

Similar Messages

Include xsql problem with mulitbyte characters

I have an xml file containing chinese and korean UTF-8 that has a xsl applied to it then output NO PROBLEM.
Now I want to apply another xsl before passing on to the final xsl so I used include-xsql in the main xsql file.
Works fine as long as the source xml contains english.
Problem is that if I do this all the non-ascii characters are turned into ??????
So somewhere there must be a conversion being performed but the source is utf-8 and I though by default all xml stuff was utf-8 so where/why is the conversion happening and how can I avoid it.
Rob

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.

FOP and XSQL problem

Hi All
I am using XDK 10 and FOP 20.5, see my previous post - it all works fine.
However I have found a weird thing and that is that the .xsql file is executed twice when using FOP, but only once when using a normal XSLT stylesheet.
Anyone else noticed that?
TIA
Richard

I figured out the problem. The version of Acrobat Reader 6.0 that I am using seems to load the document again if it does not display properly the first time round. I have got XSQL file caching on, but I disabled caching on my browser. This effectively overrides the XSQL file caching of the xsql servlet.
Regards
Richard

Custom Tag problem - NoSuchMethodError at MyAttInfo

I am having the following problem when trying to use a taglibrary in my web
 application. Does anybody know why I am having this problem?
 Thanks,
 Ozzie Gurkan
 Mon Jan 08 16:55:30 GMT+05:00 2001: <WebAppServletContext-mims> resolving
 taglib uri '/mims/taglib' to taglib-location /WEB-INF/tlds/taglib.tld:
 Mon Jan 08 16:55:30 GMT+05:00 2001:<E> <WebAppServletContext-mims> Servlet
 failed with Exception
 java.lang.NoSuchMethodError
 at weblogic.servlet.jsp.MyAttInfo.<init>(StandardTagLib.java:34)
 at
 weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:280)
 at
 weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:1
 46)
 at
 weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
 at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
 at
 weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3739)
 at
 weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3495)
 at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3356)
 at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
 at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
 at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1425)
 at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:825)
 at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
 at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
 at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
 at
 weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
 at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:265)
 at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
 at
 weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:18
 1)
 at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 :118)
 at
 weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
 l.java:154)
 at
 com.manheim.mims.core.control.web.MainServlet.doGet(MainServlet.java:67)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 :123)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 l.java:761)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 l.java:708)
 at
 weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
 Manager.java:252)
 at
 weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
 at
 weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)


My entire application works great on my Win2000 machine, so I don't think I
 am having problems with my setup of the taglib/JSP referencing. I have this
 same application running now on Jboss, Orion, and Weblogic on Win2000.
 Any other ideas?
 Thanks,
 Ozzie Gurkan
 "MKH" <[email protected]> wrote in message
 news:[email protected]...
 > It is likely that the method name is a bit screwey
 >
 > How is it defined as in your TLD file and how are you calling it in your
 > JSP?
 >
 > Is there a corresponding set<TLDMethodName> in your Java class?
 >
 >
 > "Ozzie Gurkan" <[email protected]> wrote in message
 > news:[email protected]...
 > > I am having the following problem when trying to use a taglibrary in my
 > web
 > > application. Does anybody know why I am having this problem?
 > >
 > > Thanks,
 > > Ozzie Gurkan
 > > Mon Jan 08 16:55:30 GMT+05:00 2001: <WebAppServletContext-mims>
 > resolving
 > > taglib uri '/mims/taglib' to taglib-location /WEB-INF/tlds/taglib.tld:
 > >
 > > Mon Jan 08 16:55:30 GMT+05:00 2001:<E> <WebAppServletContext-mims>
 Servlet
 > > failed with Exception
 > >
 > > java.lang.NoSuchMethodError
 > >
 > > at weblogic.servlet.jsp.MyAttInfo.<init>(StandardTagLib.java:34)
 > >
 > > at
 > > weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:280)
 > >
 > > at
 > >
 >
 weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:1
 > > 46)
 > >
 > > at
 > > weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
 > >
 > > at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
 > >
 > > at
 > > weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3739)
 > >
 > > at
 > > weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3495)
 > >
 > > at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3356)
 > >
 > > at
 > weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
 > >
 > > at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
 > >
 > > at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1425)
 > >
 > > at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:825)
 > >
 > > at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
 > >
 > > at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
 > >
 > > at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
 > >
 > > at
 > > weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
 > >
 > > at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:265)
 > >
 > > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
 > >
 > > at
 > >
 >
 weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:18
 > > 1)
 > >
 > > at
 > >
 >
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 > > :118)
 > >
 > > at
 > >
 >
 weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
 > > l.java:154)
 > >
 > > at
 > > com.manheim.mims.core.control.web.MainServlet.doGet(MainServlet.java:67)
 > >
 > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 > >
 > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 > >
 > > at
 > >
 >
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 > > :123)
 > >
 > > at
 > >
 >
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 > > l.java:761)
 > >
 > > at
 > >
 >
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 > > l.java:708)
 > >
 > > at
 > >
 >
 weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
 > > Manager.java:252)
 > >
 > > at
 > >
 >
 weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
 > >
 > > at
 > > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
 > >
 > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
 > >
 > >
 > >
 >
 >

My Apache Jserve Classpath for XSQL Problems

Operating System
Architecture x86
Name Windows NT
Version 5.0
Java Virtual Machine
JVM Compiler symcjit
Vendor Sun Microsystems Inc.
Class Path D:\apache\ApacheJServ\ApacheJServ.jar D:\Program Files\Oracle\JDeveloper 3.0\lib\servlet.jar D:\Oracle_XDK\servlet\xsql\lib\oraclexsql.jar D:\Oracle_XDK\servlet\xsql\lib\classes111.zip D:\Oracle_XDK\servlet\xsql\lib\xmlparserv2.jar D:\Oracle_XDK\servlet\xsql\lib\oraclexmlsql.jar D:\Oracle_XDK\servlet\xsql\lib
Class Format Version 46.0
Version 1.2.2
General Configurations
Logging Enabled ( D:\apache\ApacheJServ\logs\jserv.log )
Allowed IP Addresses [127.0.0.1/127.0.0.1]
Maximum Connections 5
Authentication Disabled
Bindaddress localhost/127.0.0.1
Challenge Size 5
Port 8007
Back to menu
Copyright (c) 1997-99 The Java Apache Project.
All rights reserved.
null

I believe the problem is with the directory in your CLASSPATH which has spaces in it "Program Files" and "Oracle JDeveloper".
Apache JServ may not be handling the path names in a way that spaces are allowed.

Some XSQL problems,

Dear all,
I tried to test XSQL, but I found some problems:
1.) I succesfully established a Database connection (Postgresql), but it is not visible in the Connection field of XSQL TAQ dialog windows (e.g., Query). What is wrong?
2.) Default encoding of my Java platform is "Windows-1250". All automatically generated XML files by JDev includes:
<?xml version = '1.0' encoding = 'windows-1250'?>
However this encoding is not supported by OC4J server, so I could not test my XSQL example. Is there any config file to change the automatically generated encoding attribute in JDev?
Thanks a lot for any help,
Best regards
Jacek

In JDev 9.0.3 we've improved our support in XML files for encodings. In 9.0.3 you can do Tools | Preferences... and in the "Environment" panel set your desired default encoding.
9.0.3 Developer's Preview is now available here for download on OTN.
In 9.0.2, you cannot set it globally and our support for editing the different encodings was not great.
I'd recommend downloading 9.0.3 Developer's Preview and giving that a spin for the best development experience.

AddBatch problems (NoSuchMethodError)

I have a JDBC applet that works fine using appetviewer, but when using a browser the folowing error gets written to the java console:
Exception occurred during event dispatching:
java.lang.NoSuchMethodError: java/sql/Statement: method addBatch(Ljava/lang/String;)V not found
i am using JDK1.3 and Oracle 8.1.6.
Below is my batch update code:
try {
con.setAutoCommit(false);
stmt = con.createStatement();
stmt.addBatch("INSERT INTO CUSTOMERS VALUES (CUSTOMERID_IDX.NEXTVAL,'" + TITLE + "','" + FORENAME + "','" + SURNAME + "','" + ADDRESS1 + "','" + ADDRESS2 + "','" + ADDRESS3 + "','" + ADDRESS4 + "','" + POSTCODE + "')");
stmt.addBatch("INSERT INTO ORDERS VALUES (ORDERID_IDX.NEXTVAL,SYSDATE,'" + TPRICE + "',CUSTOMERID_IDX.CURRVAL)");
stmt.addBatch("INSERT INTO PAYMENT VALUES (PAYMENTID_IDX.NEXTVAL,'" + PMETHOD + "','" + CNUMBER + "','" + INUMBER + "',ORDERID_IDX.CURRVAL)");
stmt.addBatch("INSERT INTO ORDER_LINE VALUES ('" + TP + "','" + LEVEL1 + "','" + QUAN1 + "','" + PRICE1 + "',ORDERID_IDX.CURRVAL)");
stmt.addBatch("INSERT INTO ORDER_LINE VALUES ('" + TP1 + "','" + LEVEL2 + "','" + QUAN2 + "','" + PRICE2 + "',ORDERID_IDX.CURRVAL)");
int [] updateCounts = stmt.executeBatch();
con.commit();
con.setAutoCommit(true);
stmt.close();
con.close();
} catch(BatchUpdateException b) {
System.out.println("SQLState: " + b.getMessage());
//return;
} catch(SQLException ex) {
System.out.println("SQLStateSQL: " + ex.getMessage());
thanxs in advance

I assume your browser is using JDK 1.1.
In general, if you want to compile JDBC code that runs under JDK 1.1 you need to use the 1.1 Java Compiler. Such code will also continue to run under JDK 1.2 or later (provided the all the classes and their methods conrinue to exists).
The converse does not hold. Specifically, if you use JDK 1.2 or later then your JDBC program may not run under JDK 1.1 (even though it would compile just fine under 1.1).
This happens whenever you use a method that is in the JDK 1.2 or later java.sql interfaces but not in in the JDK 1.1 java.sql interface. In JDK 1.1 such a method is bound to the Oracle implementation and is forward compatible. In JDK 1.2 such a method is bound to the java.sql interface and thus not backwards compatible.
To sum it up: you must use caution when using different Java versions. In general, you should compile with the lowest version (such as 1.1) if you want to run the same class files under several versions (such as 1.1 and 1.3).

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.

XSQL: problems using id-attribute-column

Hi,
I want to use id-attribute-column to put the records from a specific column in an attribute of an generated element of the same xsql:query. It works, but the query returns not only the attibutevalue in the attribute, bit also in an element.
How can I get rid o that extra element.
Can you please help me with this?
Greetings, Martijn

The attribute "id" is set properly but isn't shown in html
because there is no html-element corresponding to UIColumn.

XSQL Command-Line, parameters with blanks

Is it possible to use XSQL Command-Line with parameters containing blanks (space characters).
In an URL parameter spaces can be encoded with "+" or "%20", but this does'nt seem to work with XSQL Command-Line parameters.
-- Peter

I can't make this work on Unix (solaris), but I can see it is a shell script problem, not a XSQL problem.
The normal syntax for Unix shell script would be
$ script.sh foo="one two"
but the standard Oracle-supplied xsql unix shell script sets environment and passes all command-line parameters to the java program with
oracle.xml.xsql.XSQLCommandLine $*
and thereby the quotes disappear.
The problem is not really big, since I could just do
oracle.xml.xsql.XSQLCommandLine test.xsql "foo=one two"
after setting classpath. Anyway, if anybody knows how to make the xsql script work with quoted parameters, let me know.
-- Peter

Maximum Open Cursors Exceeded problem in XSQL

Hi,
We are processing an XSQL page by calling XSQLRequest.process() programatically within our application. Within the XSQL page there are several queries which involve multiple nested CURSOR expressions... when the query returns enough rows we are running into the error "ORA-00604: error occurred at recursive SQL level 1 ORA-01000: maximum open cursors exceeded".
When searching this forum I have seen many (old) postings regarding this error and a bug in the XDK... seems like it was some time ago, but while we set about improving the structure of our XSQL page (or increasing the max open cursor init parameter currently at 500 or both) can anyone confirm that this bug no longer exists?
Also, any general suggestions on working around this limit rather than increasing it? We have considered splitting up our queries into smaller queries (and merging the results via XSLT) and closing cursors during the session explicitly by issuing commits within the XSQL page... but any better ideas?
Thanks,
Bob

I have found this max open cursors problem to be related to Statement object not being closed. This presents a problem for the use of PreparedStatements, because they are only useful if you can keep them open and resuse them. However, in doing so, each iteration through the PreparedStatement creates another open cursor in the databse rather than reusing the previous one. A work around I discovered by reading about REF CURSORS and I use in JDBC is as follows:
Assuming a previously prepared PreparedStatement pstmt and a ResultSet rset-
while (rset.next()) {
rset.close();
// This line closes the cursor in the database
// but does not require you to re-prepare the
// PreparedStatement. Don't ask me why--ask the
// Oracle API guys.
rset.getStatement().close();
// make ready for GC
rset = null;

Problem with xsql:query

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?
Steve

Hmm,
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

Problem in using XSQL-session and connecting database

Hello
Let me explain clearly. We have some data entry screens for which we want to use session with time out option. Normally in Servlet, we use to create a session with max age option. Then everytime the browser call the servlet we use to check for session.isnew(). If it is new session then we will forward the page to Relogin (because session is timed out) or we proced with further action.
In XSQLServlet, how will do this. Do I have to create my own servlet extended from XSQLServlet ? Override the Service method and write about the session part and call
super(). Here only I am getting confused. In servlet mapping we have given for every .XSQL call run the XSQLServlet. How will I override this ?
And also we have problem with user id and password. We don't want to use the same id (system id as defined in XSQLConfig.xml) for every database connection. We want to define only the connection information like SID, Server, Port number. But user id and password should be dynamic. How can I achieve this ?
Please help us on solving these problem. Thanks.
Lakshmi
null

You'll need to implement your own classes that implement the:
oracle.xml.xsql.XSQLConnectionManagerFactory
and
oracle.xml.xsql.XSQLConnectionManager
to change the way XSQL handles connections. Using this mechanism, you should be able to implement any alternative connection scheme you choose.
If you run into problems implementing these interfaces, give us a shout here in the forum.

XDK 9.0.2.0.C XSQL parameter visibility problem

Dear Steven,
I consider this as a serious bug:
When one set XSQL page or XSQL session page parameter it
become visible in page/request/session or otherwise only after
the following round trip to the client.
In other words, it is not present in the incoming XML to xslt to
process.
Thank you,
David

David,
I just re-tested with 9.0.2C and things are working as they
should. For example, the following XSQL page:
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="test.xsl"?>
<page xmlns:xsql="urn:oracle-xsql" connection="demo">
<xsql:set-page-param name="page-param" value="1"/>
<xsql:set-session-param name="sess-param" value="2"/>
<xsql:set-stylesheet-param name="sheet-param" value="3"/>
<xsql:include-param name="page-param"/>
<xsql:include-param name="sess-param"/>
</page>referencing the following stylesheet:
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:param name="sheet-param"/>
<xsl:template match="/">
 <html><body>
 <xsl:value-of select="$sheet-param"/>
 <xsl:value-of select="/page/sess-param"/>
 <xsl:value-of select="/page/page-param"/>
 </body></html>
</xsl:template>
</xsl:stylesheet>shows an HTML page with the expected "321" the first request.
If you are talking about cookies, then you are correct that the
cookies you set this request are not visible until the next
request (which is the standard way cookies work), however, you
can use the new XSQL 9.0.2C feature to "see" the cookie value
immediately by adding the immediate="yes"] attribute to
your <xsql:set-cookie> action.
If I've misunderstood your problem, please post a testcase that
illustrates the issue. Thanks.

Problem with SQLJ ? NoSuchMethodError

Hi,
I wrote an application which makes use of sqlj and jdbc; it works fine on my local machine. But after deploying to the application server 9.0.2 the following error message occurs as soon as a jsp tries to invoke a method in a class file:
java.lang.NoSuchMethodError at packagePCDAT.PCDATDB.getUserLocation(PCDATDB.sqlj:69) at packagePCDAT.PCDATTools.getParamToType(PCDATTools.sqlj:65) at pcdat_select__suchparam._jspService(_pcdat__select__suchparam.java:68) [SRC:pcdat_select_suchparam.jsp:34] at com.orionserver[Oracle9iAS (9.0.2.3) Containers for J2EE].http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) at oracle.jsp.runtimev2.JspPageTable.compileAndServe(JspPageTable.java:508) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:255) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:407) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:330) at javax.servlet.http.HttpServlet.service(HttpServlet.java:336) at com.evermind[Oracle9iAS (9.0.2.3) Containers for J2EE].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:66) at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:284) at com.evermind[Oracle9iAS (9.0.2.3) Containers for J2EE].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:539) at com.evermind[Oracle9iAS (9.0.2.3) Containers for J2EE].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:285) at com.evermind[Oracle9iAS (9.0.2.3) Containers for J2EE].server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:231) at packagePCDAT.CommandPCDAT.performTask(CommandPCDAT.java:625) at packagePCDAT.CommandPCDAT.doGet(CommandPCDAT.java:648) at javax.servlet.http.HttpServlet.service(HttpServlet.java:244) at javax.servlet.http.HttpServlet.service(HttpServlet.java:336) at com.evermind[Oracle9iAS (9.0.2.3) Containers for J2EE].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:66) at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:284) at com.evermind[Oracle9iAS (9.0.2.3) Containers for J2EE].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:539) at com.evermind[Oracle9iAS (9.0.2.3) Containers for J2EE].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:285) at com.evermind[Oracle9iAS (9.0.2.3) Containers for J2EE].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:771) at com.evermind[Oracle9iAS (9.0.2.3) Containers for J2EE].server.http.AJPRequestHandler.run(AJPRequestHandler.java:170) at com.evermind[Oracle9iAS (9.0.2.3) Containers for J2EE].server.http.AJPRequestHandler.run(AJPRequestHandler.java:72) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:802) at java.lang.Thread.run(Thread.java:484)
For example the "getUserLocation" method looks like this:
public String[] getUserLocation(javax.servlet.http.HttpServletRequest request)
String user = request.getUserPrincipal().getName();
String location = "";
String[] userArray = new String[2];
if(request.isUserInRole("kunde") || request.isUserInRole("users")) {
if(user!=null)
user = user.substring(user.indexOf("/")+1);
try
getConnection();
#sql { SELECT USER_LOCATION INTO :location FROM USERS WHERE USER_ID = :user };
userArray[0] = user;
userArray[1] = location;
catch (Exception e)
e.printStackTrace();
userArray[0] = user;
userArray[1] = location;
return userArray;
It would be great if someone could help me out.
Greetings

Hi
Can you please specify following
a) Your Oracle database version. According to the required software, it should be Oracle9i or above.
b) Your Oracle Client version. This is needed if your database is installed on a different machine and you are trying to access the database from a different machine.
Kindly specify your client version. Oracle client version must be compatible with database version.
I tried to run and install the sample in my configuration and everything goes through fine. Here is my environment
Database version : Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Client : Oracle 9.0.1
Please let us know the above settings so that we can identify the exact place of the problem.
Regards
OTN Team@IDC

XSQL Problem : NoSuchMethodError

Similar Messages

Maybe you are looking for