Java to idl compiler

Hi,
Can somebody tell me the link for javatoidl compiler? I have tried the following (I missed the complete URL) but its not there.
developer earlyAccess jdk12 idltojava.html
Zulfi.

Langauge might be a barrier Language is not the problem. The problem is your attitude.
for me but I fully
understand your aims and obj. And u will never achieve
your goal. My relationship is serialized with Java. If
u are against any community member , u are indirectly
rather actually against the binding force i.e java.Blah blah blah. What a bunch of nonsense. I'm against people who are so incompetent or lazy that they need and expect the forum members to do everything for them. Simple as that. This is not frickin' Lord of the Rings here dude.
Your unholy activities will never oust me from this
forum and I will continue exploring, practicing and
spreading the message of java.It's Java. It's just software. It's not a religion. Get over yourself.
However it will surely
annoy u and belittle u so much that u wont be able to
intrigue against any other community member. And that
would be your greatest defeat.Um, sure, whatever.
(Rolls eyes so hard he can see his own brain.)
Thats the end of this chapter.Doubtful.

Similar Messages

How to track the information/error of java code while compiling.

Hi,
I want all the information or errors of java code during compilation.
So that I can use this information or I can show these errors with different style.
How to get the java syntax errors?

Hi,
I want all the information or errors of java code
during compilation.
So that I can use this information or I can show these
errors with different style.
How to get the java syntax errors?Redirect the STDOUT/STDERR from the the JAVA/JAVAC command to a file is one way...
For instance at the commmand line:
javac myClass.java > STDOUT.txt 2> STDERR.txt (Works for Unix variants or Windows OS's)
Then you can do what ever you want with the data contained in the files.
Hope this helps

BUG in WLE IDL compiler

Hi,
I want to report a bug in the WLE5.0 IDL compiler. It occurs in the
generated stub, skeleton and implementation files (*c,*s and _i)
files. Here is a description of the problem:
Say we have the following IDL:
Filename:filewithmoduleM1.idl
module M1 {
#include "BoundaryClasses\CORBA\Types\M1Complex.idl"
interfaceService {
boolean method1 (
interface Factory {
Service findService ();
The IDL compiler loses track of the Module M1 and does not scope the
interfaces inside the module. Henck even if we register a factory called
APSBalReporting::Factory it is registered as Factory. The problem gets
more interesting if we have another module that includes the first as
shown below:
Filename:filewithmoduleM2.idl
#include filewithmoduleM1.idl
module M2 {
#include "BoundaryClasses\CORBA\Types\M1Complex.idl"
interface Service {
boolean method2 (
interface Factory {
Service findService ();
Here it thinks that Service and Factory are the ones for module M1 and
so generates the return type as M1::Factory and M1::Service instead of
M2::Factory and M2::Service.
The IDL compiler used to work fine with code such as the above
previously.
Please let me know if you have any feedback for this bug and if any of
you have tried it.
Thanks,
Raman Ramesh
678-358-3581
mailto:[email protected]
www.cicube.com

BEA customers who need this problem corrected must use WLE 5.1. A patch to WLE 5.0
or WLE 5.0.1 is not available.
Wendell MacKenzie wrote:
We received a patch that fixed this problem under WLE 5.01. There were problems
back porting the fix into the 5.0 release. Talk to Tom Hegadorn.
Mary Ann Slavin wrote:
Actually that is Clarify CASE 162819 not a Clarify CR number. That particular
problem has been corrected in WLE 5.1. This problem cannot be patched in WLE
5.0.1, so if you have encountered this problem, you should upgrade to WLE 5.1
and it is corrected as part of the base product, no patch required.
MAS
Wendell MacKenzie wrote:
You have 2 choices:
- upgrade to Version 5.1 (which includes CR162819)
- obtain the patch from BEA support for CR162819 to fix a bug in the IDL
compiler
that caused Module and Interface scope names to work incorrectly. Also,
where
nesting of IDL #includes exceeded 1 level deep, this caused problems.
You will have to install the patch onto version 5.01.
Regards,
Wendell MacKenzie
Ram Ramesh wrote:
Hi,
I want to report a bug in the WLE5.0 IDL compiler. It occurs in the
generated stub, skeleton and implementation files (*c,*s and _i)
files. Here is a description of the problem:
Say we have the following IDL:
Filename:filewithmoduleM1.idl
module M1 {
#include "BoundaryClasses\CORBA\Types\M1Complex.idl"
interfaceService {
boolean method1 (
interface Factory {
Service findService ();
The IDL compiler loses track of the Module M1 and does not scope the
interfaces inside the module. Henck even if we register a factory called
APSBalReporting::Factory it is registered as Factory. The problem gets
more interesting if we have another module that includes the first as
shown below:
Filename:filewithmoduleM2.idl
#include filewithmoduleM1.idl
module M2 {
#include "BoundaryClasses\CORBA\Types\M1Complex.idl"
interface Service {
boolean method2 (
interface Factory {
Service findService ();
Here it thinks that Service and Factory are the ones for module M1 and
so generates the return type as M1::Factory and M1::Service instead of
M2::Factory and M2::Service.
The IDL compiler used to work fine with code such as the above
previously.
Please let me know if you have any feedback for this bug and if any of
you have tried it.
Thanks,
Raman Ramesh
678-358-3581
mailto:[email protected]
www.cicube.com

Java is a Compiler or Interpreter?

Java is a Compiler or Interpreter?

If you mean the executable called "java" that comes with the jre, it is actually both... it's an interpreter that compiles parts of the code it's interpreting to machine code to make it run faster.

Java(FX) Property Compiler

Hi!
We implemented a small Java(FX) Property Compiler which enables you to use a powerful PropertyHint-annotation. The "compiler" is implemented as an Post-"Java Compiler"-Bytecode-Modification-Tool (using asm-4).
Here are 3 small example so you can get the idea.
First Example
public class Case1 {
    @PropertyHint public String one;
    public enum Two { Zero, One, Two }
    @PropertyHint public Two two;
}If you compile this class with Java Compiler and the Property Compiler you get the following byte-code-equivalent (I used Java Decompiler to reflect the code):
public class Case1
public String one;
public Two two;
private SimpleObjectProperty<Two> _twoField;
private SimpleStringProperty _oneField;
@Property(writeable=true, name="two", dataSignature="Lde/chimos/property/test1/Case1$Two;", dataSignatureGeneric="", humanReadableName="")
public final ObjectProperty<Two> twoProperty()
    if (this._twoField == null)
      this._twoField = new SimpleObjectProperty(this, "two");
    return (ObjectProperty)this._twoField;
private final Two _getTwo()
    return (Two)twoProperty().getValue();
@XmlElement
public Two getTwo()
    return _getTwo();
private final void _setTwo(Two value)
    twoProperty().setValue(value);
public void setTwo(Two value)
    _setTwo(value);
@Property(writeable=true, name="one", dataSignature="Ljava/lang/String;", dataSignatureGeneric="", humanReadableName="")
public final StringProperty oneProperty()
    if (this._oneField == null)
      this._oneField = new SimpleStringProperty(this, "one");
    return (StringProperty)this._oneField;
private final String _getOne()
    return (String)oneProperty().getValue();
@XmlElement
public String getOne()
    return _getOne();
private final void _setOne(String value)
    oneProperty().setValue(value);
public void setOne(String value)
    _setOne(value);
public static enum Two
    Zero, One, Two;
}The fields "public String one" and "public Two two" are still in there to keep the Java Compiler (representing the first pass of the compiling process) working. It is possible to configure the Property Compiler via a setting called "dummyFields".
All references to these fields (dummy fields) are replaced by getter and setter calls. As you can see in the next example.
Second Example
This is what you type and compile:
public class Main {
     * @param args the command line arguments
    public static void main(String[] args)
        Case1 case1 = new Case1();
        case1.one = "Test";
        case1.two = Case1.Two.Two;
        System.out.println("case1.one = "+case1.one);
        System.out.println("case1.two = "+case1.two);
        Case3 case3 = new Case3();
        System.out.println("case3.one = "+case3.one);
        case3.update();
        System.out.println("case3.one = "+case3.one);
        Case4 case4 = new Case4();
        case4.one = Case4.One.Two;
        System.out.println("case4.one = "+case4.one);
        case4.one = Case4.One.Zero;
        System.out.println("case4.one = "+case4.one);
        Case5 case5 = new Case5();
        case5.one = Case5.One.Two;
        System.out.println("case5.one = "+case5.one);
}This is what you really get (reflected via Java Decompiler):
public class Main
public static void main(String[] args)
    Case1 case1 = new Case1();
    case1.setOne("Test");
    case1.setTwo(Case1.Two.Two);
    System.out.println("case1.one = " + case1.getOne());
    System.out.println("case1.two = " + case1.getTwo());
    Case3 case3 = new Case3();
    System.out.println("case3.one = " + case3.getOne());
    case3.update();
    System.out.println("case3.one = " + case3.getOne());
    Case4 case4 = new Case4();
    case4.setOne(Case4.One.Two);
    System.out.println("case4.one = " + case4.getOne());
    case4.setOne(Case4.One.Zero);
    System.out.println("case4.one = " + case4.getOne());
    Case5 case5 = new Case5();
    case5.setOne(Case5.One.Two);
    System.out.println("case5.one = " + case5.getOne());
}Amazing, right?
Third Example
In case you provide a getter or setter it is used automatically:
public class Case5 {
    public enum One { Zero, One, Two }
    @PropertyHint public One one;
    public One getOne()
        System.out.println("Case5.getOne()");
        if(one == One.Two)
            return One.Zero;
        return one;
}This is what you get (reflected via Java Decompiler):
public class Case5
public One one;
private SimpleObjectProperty<One> _oneField;
public One getOne()
    System.out.println("Case5.getOne()");
    if (_getOne() == One.Two)
      return One.Zero;
    return _getOne();
@Property(writeable=true, name="one", dataSignature="Lde/chimos/property/test1/Case5$One;", dataSignatureGeneric="", humanReadableName="")
public final ObjectProperty<One> oneProperty()
    if (this._oneField == null)
      this._oneField = new SimpleObjectProperty(this, "one");
    return (ObjectProperty)this._oneField;
private final One _getOne()
    return (One)oneProperty().getValue();
private final void _setOne(One value)
    oneProperty().setValue(value);
public void setOne(One value)
    _setOne(value);
public static enum One
    Zero, One, Two;
Sourcecode and documentation
We published the code as LGPL. The project an more examples are available on http://code.google.com/p/java-property-compiler/source/browse/
The first draft of documentation is still work in progress (Gerrit is currently working on the documentation).
IDE integration
The Eclipse-integration is done via an ant-builder. It works but is not perfect. Apart from the fact that the configuration requires some mouse clicks, you have to manually activate the "auto,clean" trigger. We would like to implement a real builder-plugin. Can anyone help us?
We tried a Netbeans-integration via "-post-compile", etc.. But that does not work properly. If you try to debug a project which uses the Property Compiler, the post-compiled byte-code is simply ignored and you run the unprocessed bytecode. Any idea?
JavaFX-Tree Chart
There is another project called "javafx-treechart": http://code.google.com/p/javafx-treechart/wiki/TreeChart
Gerrit will write about it as soon as the documentation is online.
Regards, Niklas
Edited by: Niklas on 28.11.2011 16:23

Hi all!
Thank you for your responses and comments!
Sorry for the late response. I am in Australia on vacation at the moment (just visited Brisbane and Whitsundays - and I am going to visit Sydney tomorrow :-).
@zonski:
Lombok is really a masterpiece. I had a look at the code. They use AST and (if I'm not mistaken) byte code manipulation too. I think we can learn a lot from Lombok.
The IDE integration of Lombok is kind of black magic - my personal point of view. I simply don't like those Eclipse API interceptions which are implemented in the Eclipse agent. I rather stick to standard interfaces - like a custom Eclipse-Builder, etc... (I still don't know the Netbeans-way, but I am going to figure that out).
This is one of the reasons why I decided to use the (awesome) Lombok source code as inspiration, but not to use my resources at hand to extend Lombok itself.
Further reasons:
a) We developed a different annotation philosophy (not implemented yet but we are going too).
b) I developed a small "deterministic destructor" mechanism based on byte-code manipulation and some (important) variable assignment restrictions - to keep performance up and avoid side effects. We want to provide an annotation for this mechanism.
We probably stick to byte code-manipulation. Not sure if we use AST (makes IDE integration very hard - see Jonathan Giles' comment).
@bouye:
I understand the concerns regarding "manual code tweaking", but I really hate the property boilerplate code - it results in unreadable source code. Our implementation still allows custom implementations of getter and setter in case you want to tweak your code. We extended our concept to allow even more flexibility (not implemented yet).
@Richard Bair:
I agree, developers might be confused if the know plain java and have no idea about the magic going on. But this is a matter of documentation and communication. If you know the concepts and the tools the code is easier to read.
I agree with you that Java really needs native property support. The annotation solutions are just placeholder solutions.
@Jonathan Giles:
IDE support is definitely an issue. That’s the reason why I want to stick to byte code manipulation. You can integrate the required build steps in Eclipse easily (still not sure about Netbeans). Using AST requires a lot of black magic as you can see in the Lombok source code.
Actually I had absolutely no debugging issues with our approach if we talk about Eclipse. If there is a way to hook into the Netbeans build process properly it shouldn't be a problem either. Of course the injected code needs to be crafted and tested carefully (no surprises policy).
The next version of our post-compiler will be splitted in two parts. The first part can be used within the regular build process and does a lot of modification (probably based on the ASM tree API). The second part gets called from a class loader and performs some final tweaks, e.g. dropping unnecessary fields (based on the fast ASM core API). In case the loaded class file did not pass the first part (detected while loading), it is entirely processed within the loading sequence. This should avoid surprises. The post-compiler can be restricted to specific namespaces.
Our current big commercial project is going to depend heavily on the post-compiler. We decided to provide the post-compiler as open source as we want to contribute to the Java community.
I'll keep you posted!
Niklas

Getting java code to compile on unix/linux

I have been using borland JBuilder to run and compile my java code. Recently i tried moving the code to a linux machine in which i have downloaded the JDK to. My classes only use standard java classes with the exception of a jbcl.jar file which has a class that one of my classes relies on. It turns out when i try to run my class i get error messages because it cant find the jar file. Where should I put this jar file? by the way in my class i use the statement: where jbcl.layout is the class i need.
import jbcl.layout.*;

another question. In my class I use the statement
import jbcl.layout.*;
so all i need to do is add the jbcl.jar to my class
path? is my import statement correctIf it compiles in your IDE, then it's correct. You shouldn't have to change anything at all in your source code to use a different compiler or to compile on a different platform. You just have set up the proper environment and parameters--tell it which .java files to compile, which jars or directories to search for classes in (classpath), etc. For IDEs you do that with the Preferences or Options menu item. For command line compilation you do this with command line arguments, config files (a la build.xml for ant), or environment variables (although relying on the CLASSPATH env var is generally a bad idea).

Java.io.IOException: Compiler failed executable.exec

I m trying to deploy a EAR file which has a single EJB.
It deploys fine but when i try to start it it throws the exception trac
ebelow.
Any ideas on how to solve ? I ve put Jrockit javac in path, set BEA_HOME
and tried a few other things with no luck.
Any ideas ?
/s
Unable to deploy EJB: hello_ejb_wls9.jar from hello_ejb_wls9.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvo
ker.java:435)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:
295)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:
303)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:284)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:470)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:439)
at
weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:436)
The server compiler and ejb compiler are set as javac in the options.

Hi,
I think you are not creating that ear correctly.
Could you check the following points ?
1. make sure all the files you need are there
2. make sure folder hierararchy is ok
If that's cool: And its still doesnt work:
Export your example ear from weblogic and use that one
Regards
Anilkumar kari

Java 2 SDK compilator for beginners

Hi to all here.
I am really sorry to disturb you all,
I am beginner in Java and I need to download Java 2 SDK compilator in order to compile my homeworks. I went lost in all the reliese EE, SE and so on I saw in Sun homepage.
Which one is the right one ?
I have Windows Vista Home edition in my computer.
Thanks for helping me.
Flavio

Download and install a Java SE 6 JDK for your Windows platform which is available here:
http://java.sun.com/javase/downloads/index.jsp
If you want some GUI Application you may choose the version containing NetBeans, if you only want the compiler and runtime environment install the first option (JDK 6 Update 4).
Edited by: mezler on Feb 20, 2008 2:13 PM

Simple Java created with compilation errors.

Hi,
While I am using Oracle for many years (currently 9.2.0.6.0) I am completely new to Java in the database.
I found a very simple example to get started (please see SQL*Plus dump below) ... but I get a compilation error. Can anyone tell what I am doing wrong?
SQL> CREATE OR REPLACE AND COMPILE JAVA SOURCE NAMED Fibonacci AS
2 public class Fibonacci
3 {
4 public static int fib (int n)
5 {
6 if (n == 1 || n == 2)
7 return 1;
8 else
9 return fib(n - 1) + fib(n - 2);
10 }
11 }
12 /
Warning: Java created with compilation errors.
SQL> show errors java source Fibonacci
No errors.
SQL>
(It must be a simple thing, the example I found seems correct, but what about grants, settings etc.)
Thanks in advance,
Stefan

Stefan,
I cannot see anything in your code that would cause a compilation error. However, according to the example in the "Oracle 9i SQL Reference", it looks like you need to enclose the name in double quotes, as in:
CREATE OR REPLACE AND COMPILE JAVA SOURCE NAMED "Fibonacci" AS ...Alternatively (and this is the way I do it), you could compile the class outside of the database, and load the compiled class file. Just create a file called "Fibonacci.java" (that contains your java code), compile it, and then use the "loadjava" tool to load the "Fibonacci.class" file into the database. Please refer to the Oracle 9i Java Developer's Guide for more details.
Good Luck,
Avi.

IDL compiler crashes when......

Hi,
I've found that the IDL compiler crashes when trying to compile an idl that contains
a declaration similar to the following:
struct S {
union U switch(long) {
case 1:
long a;
case 2:
short b;
} y;
The crash occurs with both NT and Solaris 8 versions of Tuxedo 8.0's $TUXDIR/bin/idl
that I've tried.
Any ideas?
Thanks,
Dave.

Dave,
Looks strange... I suggest that you open a case with BEA support.
Regards,
Peter.
David Watson wrote:
Hi,
I've found that the IDL compiler crashes when trying to compile an idl that contains
a declaration similar to the following:
struct S {
union U switch(long) {
case 1:
long a;
case 2:
short b;
} y;
The crash occurs with both NT and Solaris 8 versions of Tuxedo 8.0's $TUXDIR/bin/idl
that I've tried.
Any ideas?
Thanks,
Dave.

Getting one java program to compile another

Was wondering if anyone knew if it is possible ot get one java program to compile another .java file and capture any errors.

public static void RunCommand( String theCommand ) throws Exception
Runtime runtime = Runtime.getRuntime();
System.out.println( "Running Command " + theCommand ) ;
Process process = runtime.exec(theCommand);
String s = null ;
BufferedReader stdInput = new BufferedReader(new InputStreamReader(process.getInputStream()));
BufferedReader stdError = new BufferedReader(new InputStreamReader(process.getErrorStream()));
// read the output from the command
System.out.println("Here is the standard output of the command:\n");
while ((s = stdInput.readLine()) != null) {
System.out.println(s);
// read any errors from the attempted command
System.out.println("Here is the standard error of the command (if any):\n");
while ((s = stdError.readLine()) != null) {
System.out.println(s);

Support of Query newQuery(java.lang.Object compiled)

The implementation of the Query newQuery(java.lang.Object compiled)
method doesn't copy the Class of the candidate instances but it should
ad the documentation says :
"All of the settings of the other Query are copied to this Query, except
for the candidate Collection or Extent."
Thanks.

You can't query on a blob column.

Orbix idl compiler errors

Environment:
Orbix 3.01 (with 2 patches...)
Weblogic 5.1
Jdk1.3
NT sp 6
I ran ejbc -idl to generate the interfaces for a simple bean. Boy did
it generate a bunch of files.
When I run the Orbix idl command I get the following:
C:\projects\idl\com\xelus\soa\ping>idl -Ic:\projects\idl Ping.idl
IDL Compiler: Ping.idl
Pragma ID: bad format ID ( must be of type IDL, DCE or LOCAL format ).
20: Warning : identifier Exception clashes with keyword
Pragma ID: bad format ID ( must be of type IDL, DCE or LOCAL format ).
Pragma ID: bad format ID ( must be of type IDL, DCE or LOCAL format ).
Pragma ID: bad format ID ( must be of type IDL, DCE or LOCAL format ).
I am guessing that the BEA product supports a more recent version of the
IDL spec than that in the Orbix product.
Are there flags that I can add the to ejbc command to make the idl more
friendly to the Orbix idl compiler? Is there a minimum Orbix revision
that I have to be at to work with the idl generated by ejbc -idl?
I also did this with a simple rmi interface as well and found similar
errors though many fewer idl files!
thanks for any help,
don.

I have sp3 installed and the flag was not recognized by ejbc. Do I have to wait for 5.1.1?
thanks,
don.
Eduardo Ceballos wrote:
Try -idlNoValueTypes... this is an experimental option. Should work, provided your Remote interface reduces reasonably (usably) without value types.
Don Schaefer wrote:
Environment:
Orbix 3.01 (with 2 patches...)
Weblogic 5.1
Jdk1.3
NT sp 6
I ran ejbc -idl to generate the interfaces for a simple bean. Boy did
it generate a bunch of files.
When I run the Orbix idl command I get the following:
C:\projects\idl\com\xelus\soa\ping>idl -Ic:\projects\idl Ping.idl
IDL Compiler: Ping.idl
Pragma ID: bad format ID ( must be of type IDL, DCE or LOCAL format ).
20: Warning : identifier Exception clashes with keyword
Pragma ID: bad format ID ( must be of type IDL, DCE or LOCAL format ).
Pragma ID: bad format ID ( must be of type IDL, DCE or LOCAL format ).
Pragma ID: bad format ID ( must be of type IDL, DCE or LOCAL format ).
I am guessing that the BEA product supports a more recent version of the
IDL spec than that in the Orbix product.
Are there flags that I can add the to ejbc command to make the idl more
friendly to the Orbix idl compiler? Is there a minimum Orbix revision
that I have to be at to work with the idl generated by ejbc -idl?
I also did this with a simple rmi interface as well and found similar
errors though many fewer idl files!
thanks for any help,
don.

Visibroker - java - IDL Compilation

Hi;
I am using the trial version of Visibroker 5.2.1 to develop a CORBA 2.4 compliant client Application.
After compiling the IDL File using idl2java command, I tried to compile
the stub java files using javac *.java command. It throws lot of errors.
The main error is:
"can not resolve the symbol class MethodPointer"
"package portable"
"new org.omg.CORBA.portable.MethodPointer"
I had put three .jar file namely lm.jar,vbsec.jar,vbjorb.jar in the classpath and I am running the machine in Windows 2000 Machine.
Can anyboby kindly answer what could be the possible reason ???
Thanks.

You have to use "idl to java" compiler bundled with Visibroker instead of JDK one.

Urgent,java Error when compiling class file for jsp

Hi!
Reference to statement is ambbiguous,both class java.sql.statement in java.sql and class.java.beans.statement in java beans match.
this is my file . When i comment the java.import.bean headre it does compile but my server is not able to recognize the class file.,Cud someone help me.
THis is my source file
package dbmg;
//import java.beans.*;
import java.sql.*;
import javax.servlet.*;
import javax.servlet.http.*;
public class DbBean
Connection con;
ResultSet rs;
String sql;
boolean queryType;
int edited;
public DbBean() throws Exception
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
con = DriverManager.getConnection("jdbc:odbc:Forums");
public void setQueryType(String s)
queryType=s.equalsIgnoreCase("select");
public void setSql(String s)
sql = s;
synchronized public void processRequest(HttpServletRequest req) throws
Exception
if (queryType)
Statement stmt=con.createStatement();
rs=stmt.executeQuery(sql);
else
PreparedStatement ps=null;
ps=con.prepareStatement(sql);
int count=0;
String sqlParam,paramValue;
boolean set=true;
while (set)
count++;
sqlParam="param"+String.valueOf(count);
     if (sqlParam==null)
          set=false;
          continue;
paramValue=req.getParameter(sqlParam);
     if (paramValue==null)
set=false;
continue;
          else
               paramValue=paramValue.trim();
try
               ps.setString(count,paramValue);
          catch(Exception ex)
               set=false;
               continue;
try
edited=ps.executeUpdate();
catch(SQLException e)
edited=0;
public Connection getConnection()
return con;
public ResultSet getResultSet()
return rs;
public int stored()
return edited;
public void closeCon() throws Exception
con.close();
rs = null;

No need of commenting your import statement. Whenever there is ambiguity, you can use full class name (with package).
Like,
java.sql.Statement stmt=con.createStatement();
Now there is no ambiguity.
Sudha

Java to idl compiler

Similar Messages

Maybe you are looking for