Problem with SQLData implementation

Question

Hi,
I am facing a problem while retrieving an ARRAY.
I am using jdbc thin driver 8.1.7.1 (patched version) to connect to the 9i Database(9.0.1.2.0).
Code:
public class Employee implements SQLData
     public int iEmpNumber;
     public String strName;
     Address[] objEmpAddress;
     String sql_type="APPS.EMPLOYEE";
     public Employee()
     public String getName()
          return strName;
     public Employee(int iEmpNumber,String strName,Address[] objEmpAddress)
          try
               this.iEmpNumber=iEmpNumber;
               this.strName=strName;
               this.objEmpAddress=objEmpAddress;
          }catch(Exception e){}
     public String getSQLTypeName() throws SQLException
     return sql_type;
     public void readSQL(SQLInput stream, String typeName)
     throws SQLException
          sql_type =typeName ;
          iEmpNumber = stream.readInt();
          strName = stream.readString();
          Array b=stream.readArray();
****Here I am getting b as null**********************************
Object[] d=(Object[])b.getArray();
          Address[] e=new Address[d.length];
          for(int i=0;i<d.length;i++)
               e=(Address)d[i];
          objEmpAddress=e;
     public void writeSQL(SQLOutput stream)
     throws SQLException
          try{
          OracleConnection conn=(OracleConnection)DriverManager.getConnection ("jdbc:oracle:thin:@nandini:1510:crp","sadas", "asd");
          stream.writeInt(iEmpNumber);
          stream.writeString(strName);
          ArrayDescriptor desc = ArrayDescriptor.createDescriptor("APPS.ADDTABLE",conn);
          ARRAY a=new ARRAY(desc,conn,objEmpAddress);
          stream.writeArray(a);
          }catch(Exception e){ System.out.println("Exception Occured in writeSQL of Employee"+e);}
Any suggestion would be greatly helpful.
Thanks and Regards,
Ramesh Jetty.

Answer 1

Hi Curt,
I could do that also but this would sort of defeat the purpose of taking advantage
of using the DB Control in Workshop. The DB Control is supposed to take care
all of the DB connection logic for us.
Bao.
"Curt Smith" <[email protected]> wrote:
>
That tact I would have take wuold have packaged the std logic to get
initialcontext
and lookup on my other conn pool JNDI name. I can't imagine why this
tact would
fail.
What's your thoughts?
curt