It looks like the new JDBC drivers is buggy as well. Now my calls to the
database throw an exception
java.sql.SQLException: [Macromedia][SQLServer JDBC Driver][SQLServer]Line 1:
Incorrect syntax near '{'.
This code works fine without the service pack and in JRun 3.1.
final String query =
"{ CALL wss_Create_PositionMarker(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?, ?, ?) }";
try
{
// set up statement
//
stmt = conn.prepareCall(query);
// initialize parameters.
...
...
..
rset = stmt.executeQuery();
}
catch()
{
}
I wasted lot of time with the JSP compiler bug, now that is fixed they broke
some thing else. Its been very frustrating trying to migrate to Jrun 4.0.
Thye added some version dependency and I cant not use the JRun 4.0 JDBC
libraries with SP1. Now we cannot even finish migration efforts and wait
till SP1 release.
Ravi
-----Original Message-----
From: Ravi Vedire [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 10, 2002 4:02 PM
To: JRun-Talk
Subject: RE: JSP compilation error in Jrun 4.0
Thanks Eric,
That was very helpful. The problem I was trying to solve was getting impeded
by a bug in JSP compiler in JRun 4.0. And as you mentioned it looks like it
is fixed in JRun 4 SP1. After installing SP1 the it did not take me long to
figure out the cause for the original issue and fix it.
Any idea when SP1 will be officially released?
Thanks,
Ravi
-----Original Message-----
From: Eric Anderson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 10, 2002 10:14 AM
To: JRun-Talk
Subject: RE: JSP compilation error in Jrun 4.0
Ravi,
Have you tried the beta of JRun 4 service pack 1. I set up a simple sample
of what you are trying to do ( I think ) and it works in JRun 4 sp1.
You can get more information on how to get the beta here:
http://webforums.macromedia.com/jrun/today.cfm#57
I have included what I did in this email. If it is radically different from
what you are doing let me know.
package com.test;
public abstract class Foo {
public void test() {
}
}
<%@ page import="com.test.Foo"%>
<%!
public class Foo2 extends jrun.jsp.runtime.HttpJSPServlet, com.test.Foo
{
public void test2(int ifoo )
{
ifoo = 0;
}
}
%>
<%!
public Foo2 test = new Foo2();
%>
Eric
-----Original Message-----
From: Ravi Vedire [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 10, 2002 11:36 AM
To: JRun-Talk
Subject: RE: JSP compilation error in Jrun 4.0
After reviewing all the code, the only thing I can attribute the
compilation errors to extending a Java class in JSP.
<%!
public class customSiteLocatorMgr extends com.dpd.wssjsp.SiteLocatorMgr
{
public void foo(int ifoo )
{
ifoo = 0;
}
}
%>
<%!
public customSiteLocatorMgr siteLocatorMgr = new customSiteLocatorMgr();
%>
The above strip down version of the code does not give me the same error,
but it also does not work. We get a 500 NULL error.
"Extends" -- Directs the translation process to extend the generated servlet
className. This technique is not to be used lightly as it prevents the JSP
engine from doing some things on your behalf. Then goes on to recommend tag
libraries as a better solution.
Would some one please enlighten me on the limitations/downside of using
extends in JSP.
Thanks,
Ravi
-----Original Message-----
From: Baker, Ed [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 10, 2002 7:51 AM
To: JRun-Talk
Subject: RE: JSP compilation error in Jrun 4.0
Ravi,
Our error was a simple syntax error (an extra semi-colon). I forget the
error message text but it was a basic syntax error. It's not related to
your error message.
-Ed
-----Original Message-----
From: Ravi Vedire [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 09, 2002 7:20 PM
To: JRun-Talk
Subject: RE: JSP compilation error in Jrun 4.0
Ed,
Looks like size is not the issue in my case. After stripping down some, the
generated java file (in failed compile case) is much smaller than the java
files generated by the working JSP files.
Did you get similar error message for your syntax error? (like the one
listed at the bottom of this e-mail).
Thanks,
Ravi
-----Original Message-----
From: Baker, Ed [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 09, 2002 1:27 PM
To: JRun-Talk
Subject: RE: JSP compilation error in Jrun 4.0
We had a compilation error on a JSP file when we switched from 3.1 to 4.0.
The file had a syntax error which did not fail under 3.1. So 4.0 was
correct in reporting the error. I don't know if this will help you but I
thought it worth mentioning.
-Ed Baker
-----Original Message-----
From: Ravi Vedire [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 09, 2002 3:04 PM
To: JRun-Talk
Subject: JSP compilation error in Jrun 4.0
Hi All,
We are getting the following JSp compilation error when JRun 4.0 tries to
compiles some of our JSP files. However the same JSP files work with JRun
3.1.
On the web I found some references to the size of the JSP and Java class
file size limitations of the JVM, as the cause for this error. One of the
solutions proposed was to re-architect the JSP.
Before we go and re-architect all the JSP code, I wanted to find out if any
one else encountered this issue with JRun 4.0 and what did they top resolve
it.
Thanks a lot in advance
Ravi
500 (class: jrun__C150__applicant2ejsp13, method: _jspService signature:
(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletRespo
nse;)V) Illegal target of jump or branch
(class: jrun__C150__applicant2ejsp13, method: _jspService signature:
(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletRespo
nse;)V) Illegal target of jump or branch
______________________________________________________________________
Get the JRun Web Application Construction Kit - the only book written specifically for
JRun developers.
http://www.amazon.com/exec/obidos/ASIN/0789726009/houseoffusion
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
