Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Visual Age for Java Data Access Beans

4 posts in General Discussion (old) Last posting was on 2000-03-01 13:44:47.0Z
Darrell Fuller Posted on 2000-02-25 13:08:03.0Z
Newsgroups: sybase.public.easerver
From: "Darrell Fuller" <dfuller@partnerware.com>
Subject: Visual Age for Java Data Access Beans
Date: Fri, 25 Feb 2000 07:08:03 -0600
Lines: 36
X-Newsreader: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
NNTP-Posting-Host: smtp.partnerware.com 38.197.109.2
Message-ID: <347_TNzjNL5f$GA.274@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:1904
Article PK: 131224

I recently posted a message that deals with an issue using the Data Access
Beans that are found in Visual Age for Java using ASA 6.02. Any numeric
field other than integer raises an exception when an used by the
Data Access Beans. I'm including a message from an IBM rep that explains
what the Access Beans are attempting to do. Can anyone tell me how the
Metadata is resolved in the jdbc tables stored within ASA?
I'm thinking I might be able to resolve this issue by modifying values in
these tables.

Also, can someone explain better what the IBM Rep is telling me?

Thanks again,
dfuller@partnerware.com

IBM Response

The Select bean changed the way it determines if a field is searchable in
Fixpack 1.1 and in VAJ 3.0.

The Select bean is attempting to determine if the columns in the query are
searchable. For each column it is using the
java.sql.ResultSetMetaData.getColumnTypeName() method to match against the
information provided by java.sql.DatabaseMetaData.getTypeInfo().

We expect to find a match between the columnTypeName provided in the
ResultSetMetaData and the typeNames returned by Database.getTypeInfo(). If
we don't, the symptom is a null pointer exception.

Can you check what your JDBC driver is returning for these methods? I'm
assuming that there is a datatype in your query for which there is no
corresponding entry in the information provided by getTypeInfo.


Johan Compagner Posted on 2000-02-29 14:36:30.0Z
Newsgroups: sybase.public.easerver
From: "Johan Compagner" <joco@wxs.nl>
Subject: Re: Visual Age for Java Data Access Beans
Date: Tue, 29 Feb 2000 15:36:30 +0100
Lines: 46
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
NNTP-Posting-Host: mail.schuttesystems.nl 195.86.84.23
Message-ID: <347_Vcv4vMsg$GA.297@forums.sybase.com>
References: <347_TNzjNL5f$GA.274@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:1903
Article PK: 131225

Did you run that script that 'installs' the meta data for JDBC access?

After installation you must run a script file that can be found in the
JDBC driver download i think.

That updates tables for meta data access.

"Darrell Fuller" <dfuller@partnerware.com> wrote in message news:TNzjNL5f$GA.274@forums.sybase.com...
> I recently posted a message that deals with an issue using the Data Access
> Beans that are found in Visual Age for Java using ASA 6.02. Any numeric
> field other than integer raises an exception when an used by the
> Data Access Beans. I'm including a message from an IBM rep that explains
> what the Access Beans are attempting to do. Can anyone tell me how the
> Metadata is resolved in the jdbc tables stored within ASA?
> I'm thinking I might be able to resolve this issue by modifying values in
> these tables.
>
> Also, can someone explain better what the IBM Rep is telling me?
>
> Thanks again,
> dfuller@partnerware.com
>
> IBM Response
>
> The Select bean changed the way it determines if a field is searchable in
> Fixpack 1.1 and in VAJ 3.0.
>
> The Select bean is attempting to determine if the columns in the query are
> searchable. For each column it is using the
> java.sql.ResultSetMetaData.getColumnTypeName() method to match against the
> information provided by java.sql.DatabaseMetaData.getTypeInfo().
>
> We expect to find a match between the columnTypeName provided in the
> ResultSetMetaData and the typeNames returned by Database.getTypeInfo(). If
> we don't, the symptom is a null pointer exception.
>
> Can you check what your JDBC driver is returning for these methods? I'm
> assuming that there is a datatype in your query for which there is no
> corresponding entry in the information provided by getTypeInfo.
>
>
>
>
>


Darrell Fuller Posted on 2000-03-01 13:02:51.0Z
Newsgroups: sybase.public.easerver
From: "Darrell Fuller" <dfuller@partnerware.com>
Subject: Re: Visual Age for Java Data Access Beans
Date: Wed, 1 Mar 2000 07:02:51 -0600
Lines: 62
X-Newsreader: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
NNTP-Posting-Host: smtp.partnerware.com 38.197.109.2
Message-ID: <347_PkVlU83g$GA.202@forums.sybase.com>
References: <347_TNzjNL5f$GA.274@forums.sybase.com> <347_Vcv4vMsg$GA.297@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:1902
Article PK: 131223

Yes, I did run the script..
I can connect with JConnect and I do not have this problem using Straight
JDBC. I'm trying to track down this problem from the IBM Data Access Beans.
I'm hoping someone might have run into this problem or might have a
different idea that will help me convince IBM that it is their problem.

Darrell

Johan Compagner wrote in message ...
>Did you run that script that 'installs' the meta data for JDBC access?
>
>After installation you must run a script file that can be found in the
>JDBC driver download i think.
>
>That updates tables for meta data access.
>
>"Darrell Fuller" <dfuller@partnerware.com> wrote in message
news:TNzjNL5f$GA.274@forums.sybase.com...
>> I recently posted a message that deals with an issue using the Data
Access
>> Beans that are found in Visual Age for Java using ASA 6.02. Any numeric
>> field other than integer raises an exception when an used by the
>> Data Access Beans. I'm including a message from an IBM rep that explains
>> what the Access Beans are attempting to do. Can anyone tell me how the
>> Metadata is resolved in the jdbc tables stored within ASA?
>> I'm thinking I might be able to resolve this issue by modifying values in
>> these tables.
>>
>> Also, can someone explain better what the IBM Rep is telling me?
>>
>> Thanks again,
>> dfuller@partnerware.com
>>
>> IBM Response
>>
>> The Select bean changed the way it determines if a field is searchable in
>> Fixpack 1.1 and in VAJ 3.0.
>>
>> The Select bean is attempting to determine if the columns in the query
are
>> searchable. For each column it is using the
>> java.sql.ResultSetMetaData.getColumnTypeName() method to match against
the
>> information provided by java.sql.DatabaseMetaData.getTypeInfo().
>>
>> We expect to find a match between the columnTypeName provided in the
>> ResultSetMetaData and the typeNames returned by Database.getTypeInfo().
If
>> we don't, the symptom is a null pointer exception.
>>
>> Can you check what your JDBC driver is returning for these methods? I'm
>> assuming that there is a datatype in your query for which there is no
>> corresponding entry in the information provided by getTypeInfo.
>>
>>
>>
>>
>>
>
>


Robert Waywell Posted on 2000-03-01 13:44:47.0Z
Newsgroups: sybase.public.easerver
From: "Robert Waywell" <rwaywell@sybase.com>
Subject: Re: Visual Age for Java Data Access Beans
Date: Wed, 1 Mar 2000 08:44:47 -0500
Lines: 84
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
NNTP-Posting-Host: rwaywell-pc.sybase.com 172.31.141.35
Message-ID: <347_yaa8YT4g$GA.295@forums.sybase.com>
References: <347_TNzjNL5f$GA.274@forums.sybase.com> <347_Vcv4vMsg$GA.297@forums.sybase.com> <347_PkVlU83g$GA.202@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:1901
Article PK: 131222

You might want to open a case with tech support for this one. My
understanding of the information you included from IBM support is that there
appears to be a mismatch between the datatype names returned by getTypeInfo
and the datatype found when trying to retrieve the numeric column. If we can
verify this, then it will require a fix from engineering.

--
-------------------------------------------------------
Robert Waywell
Sybase
Please Respond to Newsgroups

ASA Downloads: http://sdn.sybase.com/sdn/mec/mec_down.stm

Darrell Fuller wrote in message ...
>Yes, I did run the script..
>I can connect with JConnect and I do not have this problem using Straight
>JDBC. I'm trying to track down this problem from the IBM Data Access
Beans.
>I'm hoping someone might have run into this problem or might have a
>different idea that will help me convince IBM that it is their problem.
>
>Darrell
>
>Johan Compagner wrote in message ...
>>Did you run that script that 'installs' the meta data for JDBC access?
>>
>>After installation you must run a script file that can be found in the
>>JDBC driver download i think.
>>
>>That updates tables for meta data access.
>>
>>"Darrell Fuller" <dfuller@partnerware.com> wrote in message
>news:TNzjNL5f$GA.274@forums.sybase.com...
>>> I recently posted a message that deals with an issue using the Data
>Access
>>> Beans that are found in Visual Age for Java using ASA 6.02. Any numeric
>>> field other than integer raises an exception when an used by the
>>> Data Access Beans. I'm including a message from an IBM rep that
explains
>>> what the Access Beans are attempting to do. Can anyone tell me how the
>>> Metadata is resolved in the jdbc tables stored within ASA?
>>> I'm thinking I might be able to resolve this issue by modifying values
in
>>> these tables.
>>>
>>> Also, can someone explain better what the IBM Rep is telling me?
>>>
>>> Thanks again,
>>> dfuller@partnerware.com
>>>
>>> IBM Response
>>>
>>> The Select bean changed the way it determines if a field is searchable
in
>>> Fixpack 1.1 and in VAJ 3.0.
>>>
>>> The Select bean is attempting to determine if the columns in the query
>are
>>> searchable. For each column it is using the
>>> java.sql.ResultSetMetaData.getColumnTypeName() method to match against
>the
>>> information provided by java.sql.DatabaseMetaData.getTypeInfo().
>>>
>>> We expect to find a match between the columnTypeName provided in the
>>> ResultSetMetaData and the typeNames returned by Database.getTypeInfo().
>If
>>> we don't, the symptom is a null pointer exception.
>>>
>>> Can you check what your JDBC driver is returning for these methods? I'm
>>> assuming that there is a datatype in your query for which there is no
>>> corresponding entry in the information provided by getTypeInfo.
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>