Skip to Main Content
Forums

Java Database Connectivity (JDBC)

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

JDBC Invalid column index exception

Alok PattnaikSep 24 2014 — edited Oct 15 2014

Hi,

I have passed the string as

stmt.setString(3, entry.getValue().toString());

stmt.setString(2, entry.getValue().toString());

stmt.setString(1, entry.getValue().toString());

for SQL Query   SELECT M.TXREFNO,M.PROCESSDATE WHERE  F.PROCESSID=? AND ( M.COUNTRYCODE IN (?) OR M.COUNTRYCODE IS NULL )  AND (M.TXREFNO=?)

but its showing Invalid column index Exception.

Please share your feedback.

Comments

B of Carbon
LOL - I didn't think about the forum message area having trouble displaying my XML XSLT problem
It seemed to mix the code with the site XML.

Oh brother

The deal is this.

The XML XSLT transform was working and now it is not and I think it has something to do with
the HTTP links for either the Oracle core and/or XML TAGLIBs. Either that or the W3.org has
outdated XSLT http links.

Anyone know if changes have been made to any of these taglib links?
This in the JSP

<!--

<%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>

<c:import url="HoursWorked.xml" var="xmlHoursWorked" charEncoding="windows-1252"/>
<c:import url="./HoursWorked3.xsl" var="xslt" charEncoding="windows-1252"/>
<x:transform xml="${xmlHoursWorked}" xslt="${xslt}" />

-->

This in the XSL

<!--

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

-->


And the other JSP having the same problem.

<!--

<%@ page contentType="text/html;charset=windows-1252"
import="java.util.List, qsbqar.XMLHandler, org.w3c.dom.NodeList,
javax.xml.transform.*, javax.xml.transform.stream.*,
org.w3c.dom.Node, oracle.xml.parser.v2.*, java.io.File,
java.io.FileReader " %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
<xsl:param name="employeeID" value="2"/>
<%session.setAttribute("employee_ID", request.getParameter("consultantID")); %>

<c:import url="HoursWorked.xml" var="xmlHoursWorked" charEncoding="windows-1252"/>
<c:import url="./HoursWorked4.xsl" var="xslt" charEncoding="windows-1252"/>
<x:transform xml="${xmlHoursWorked}" xslt="${xslt}">
<x:param name="employeeID" value="${sessionScope.employee_ID }"/>
</x:transform>

-->

Edited by: B of Carbon on Dec 19, 2010 12:25 AM
B of Carbon
I've been fooling around with the transform by running the XSL file that references my XML file.

I am unable to get to the details in the tags.
I've got a problem with JDeveloper's directory structure and the XSL DOM language parser.
I really never know what the value of my match should be....

<xsl:template match="catalog">

If I place the XML and XSL in the public html directory which appears as Web Content in the Application Navigator
that means they should be at the same level in that directory.

What am I missing on these template matches versus the directory structure of JDeveloper?
I don't see a way to configure any of this through an XML mapping document.

XML usage was a lot smoother in Visual Studio for my .NET apps.
JDeveloper has me going in circles. I think they use mapping to virtual directories but that is not clear.
I end up guessing at how to connect to things usually.
Typically the tutorials don't adequately address path setup or other configuration issues.
When you are trying to learn XSL the last thing you need is the IDE adding to the confusion
over where your relative path begins and where the parser is looking for an XML let alone its tags in the DOM tree structure.
It should not be this difficult.

Brian

Edited by: B of Carbon on Dec 19, 2010 9:41 PM

Edited by: B of Carbon on Dec 19, 2010 9:54 PM
1 - 2
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Oct 22 2014
Added on Sep 24 2014
#database-connectivity-discussions, #jdbc
1 comment
88 views