Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 17806 invoked from network); 2 Jun 2006 17:02:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Jun 2006 17:02:13 -0000 Received: (qmail 19822 invoked by uid 500); 2 Jun 2006 17:02:12 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 19294 invoked by uid 500); 2 Jun 2006 17:02:10 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 19283 invoked by uid 99); 2 Jun 2006 17:02:10 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jun 2006 10:02:10 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [63.71.228.76] (HELO smtpedge1.uspto.gov) (63.71.228.76) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jun 2006 10:02:08 -0700 Received: from EMFSERVER1 (emfserver1.uspto.gov [10.240.6.74]) by smtpedge1.uspto.gov (Tumbleweed MailGate) with ESMTP id A2A71E01653A for ; Fri, 2 Jun 2006 13:01:24 -0400 (EDT) Received: from 10.112.161.154 by EMFSERVER1 with ESMTP (Tumbleweed Email Firewall SMTP Relay (Email Firewall v6.2.0)); Fri, 02 Jun 2006 13:04:06 -0400 X-Server-Uuid: A4AFE6A8-ACB5-4096-9177-6557516E3F90 Received: from exchange3.uspto.gov ([10.112.171.193]) by uspto-smtp-1.uspto.gov with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Jun 2006 13:01:40 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: IBATIS CHAR FIELD NULL VALUES- Urgent help required Date: Fri, 2 Jun 2006 13:01:39 -0400 Message-ID: <8AED8A2865F7064989119502BD85729D79EF29@EXCHANGE3.uspto.gov> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IBATIS CHAR FIELD NULL VALUES- Urgent help required Thread-Index: AcaGZgZezVGtaewAQEmEp2xigYDBbAAACvyw From: "Krishnamoorthi, Sruthi (Raytheon)" To: user-java@ibatis.apache.org X-OriginalArrivalTime: 02 Jun 2006 17:01:40.0715 (UTC) FILETIME=[37C60BB0:01C68666] X-WSS-ID: 689EB00C19S1410534-01-01 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C68666.37AE1D0A" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------_=_NextPart_001_01C68666.37AE1D0A Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable String type =20 Thanks,=20 Sruthi Krishnamoorthi=20 703-562-9732(Work)=20 537 A - (Raytheon) Location=20 -----Original Message----- From: Clinton Begin [mailto:clinton.begin@gmail.com] Sent: Friday, June 02, 2006 1:00 PM To: user-java@ibatis.apache.org Subject: Re: IBATIS CHAR FIELD NULL VALUES- Urgent help required What Java type are you trying to map to the CHAR field? On 6/2/06, Krishnamoorthi, Sruthi (Raytheon) < = = Sruthi.Krishnamoorthi@uspto.gov> wrote:=20 I have a char field which carries null value.=20 The samething with varchar field also. when I pass null values it was throwing sql exception as incompatible = column types. Then for varchar field i add #centerNo:VARCHAR# and same = for DAte field #priorityDt:DATE#.=20 When I did same for CHAR #parentPatentNo:CHAR# I got error that inserted = value too large for a column Then I tried #parentPatentNo:CHAR(10)# Now it says incompatable type column. =20 INSERT INTO PATENTED_CASE (PC_PATENT_NO,PATENT_APPLICATION_NO,FILING_DT, = PATENT_ISSUE_DT, INVENTION_TITLE_TX, TECHNOLOGY_CENTER_NO, = APPLICATION_PRIORITY_DT, REISSUE_PARENT_PATENT_NO, INVENTOR_QT, = LAST_MODIFIED_USER_ID,LAST_MODIFIED_TS, ART_UNIT_NO)=20 VALUES(#patentNo#, #patentApplNo#, #filingDt#, #issueDt#, #title#, = #centerNo:VARCHAR#, #priorityDt:DATE#, #parentPatentNo:CHAR(10)#, = #inventorQt#, #lastModifiedUserId#, sysdate, #artUnitNo#) Could you please provide me a solution very urgently. Thanks, Sruthi Krishnamoorthi 703-562-9732(Work) 537 A - (Raytheon) Location -----Original Message----- From: Morone, Bill [mailto: = Morone.Bill@pennmutual.com] Sent: Friday, June 02, 2006 11:20 AM To: user-java@ibatis.apache.org; lmeadors@apache.org Subject: RE: When returning mutiple objects and transforming "directly to xml Larry, I will take a better look at the source when I have the time. We can = talk. Thanks. I had to tell my manager about the change in stance regarding the xml = moving forward. She was not happy (I sold her on the xml instead of = having java value objects --get rid of a layer -- it is only a semantic = difference between a java value object and an xml one, right?).=20 Anyway. Onward -----Original Message----- From: larry.meadors@gmail.com [mailto: larry.meadors@gmail.com]On Behalf = Of Larry Meadors Sent: Friday, June 02, 2006 10:56 AM To: user-java@ibatis.apache.org Subject: Re: When returning mutiple objects and transforming "directly=20 to xml I can help you build a row handler to do the transformation if you need some help (though I suspect you won't), just contact me off-list, and we can work on it - shouldn't take more than a few minutes to=20 "rough it in", then you can refine it. Larry On 6/2/06, Morone, Bill < Morone.Bill@pennmutual.com> wrote: > > > Gentlemen:=20 > > I do thank you and believe you have a fine thing going. Like I said I > created a very clean little design that basically uses the xml objects > emitted by iBATIS and transforms them anyway you want (great for = little=20 > docs). I'd like to see stuff move a little forward -- I'll help!!! > > > Bill > > > > > -----Original Message----- > From: Clinton Begin [mailto: = clinton.begin@gmail.com] > Sent: Friday, June 02, 2006 9:45 AM > To: user-java@ibatis.apache.org > Subject: Re: When returning mutiple objects and transforming "directly = to=20 > xml > > > Hi Bill, > > It will probably go away in version 3.0. We'd never remove a feature = from > the current major version. It will continue to be supported in 2.0. >=20 > In it's place we'll likely either suggest or build-in second stage xml > support, for turning classes, beans and maps into XML. That will = allow you > to map them to domain objects AND convert them to XML. Plus, there = are=20 > already a number of XML libraries that support exactly that. The = current > implementation creates too much complexity in the implementation, yet = offers > little additonal value over the formerly described approach.=20 > > Don't worry though, we'll always help you upgrade. Even if it doesn't = exist > in 3.0, we'll have a suggested upgrade path that shouldn't leave you > floundering. > > Cheers, > Clinton=20 > > > > > On 6/2/06, Morone, Bill < Morone.Bill@pennmutual.com> wrote: > > Larry, > > > > Really? I think it bears great merit. I little expansion would make = it=20 > really practical. In fact hearing of its departure has me a little = worried. > > > > Does this mean the resultClass=3D"xml" is going away? > > > > I created a little (restlet front-end) framework that translates the = xml=20 > output for web services. I extended ArrayList to deal with the > "non-webformedness" of the queryForObject "list of little docs" = situation > and it works great. > > > > Our system is scheduled to go into production in October -- what are = the=20 > future plans for the xml stuff -- I assume we'll have to subclass to = extend. > Will your superclass stuff stay the same? > > > > Bill Morone > > > > > > -----Original Message-----=20 > > From: larry.meadors@gmail.com [mailto: larry.meadors@gmail.com]On = Behalf > > Of Larry Meadors > > Sent: Thursday, June 01, 2006 4:45 PM=20 > > To: user-java@ibatis.apache.org > > Subject: Re: When returning mutiple objects and transforming = "directly > > to xml > > > >=20 > > On 6/1/06, Morone, Bill < Morone.Bill@pennmutual.com> wrote: > > > Coming soon, right? > > > > On the contrary, going away. > > > > I'd suggest processing the results of the query manually to create = XML > > with a row handler if you really need to create xml results. > > > > Larry > > This message, including any attachments, is intended only for the=20 > recipient(s) > > named above. It may contain confidential and privileged information. = If > you have > > received this communication in error, please notify the sender = immediately > and=20 > > destroy or delete the original message. Also, please be aware that = if you > are not > > the intended recipient, any review, disclosure, copying, = distribution or > any > > action or reliance based on this message is prohibited by law.=20 > > > > > > > This message, including any attachments, is intended only for the > recipient(s) > named above. It may contain confidential and privileged information. = If you=20 > have > received this communication in error, please notify the sender = immediately > and > destroy or delete the original message. Also, please be aware that if = you > are not > the intended recipient, any review, disclosure, copying, distribution = or any=20 > action or reliance based on this message is prohibited by law. > > > This message, including any attachments, is intended only for the = recipient(s) named above. It may contain confidential and privileged information. If = you have=20 received this communication in error, please notify the sender = immediately and destroy or delete the original message. Also, please be aware that if = you are not the intended recipient, any review, disclosure, copying, distribution or = any=20 action or reliance based on this message is prohibited by law. ------_=_NextPart_001_01C68666.37AE1D0A Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
String=20 type
 

Thanks,
Sruthi Krishnamoorthi
703-562-9732(Work)
537 A -=20 (Raytheon) Location

-----Original Message-----
From: Clinton Begin=20 [mailto:clinton.begin@gmail.com]
Sent: Friday, June 02, 2006 = 1:00=20 PM
To: user-java@ibatis.apache.org
Subject: Re: = IBATIS=20 CHAR FIELD NULL VALUES- Urgent help required

What = Java=20 type are you trying to map to the CHAR field?


On 6/2/06, Krishnamoorthi, Sruthi (Raytheon) <=20 Sruthi.Krishnamoorthi@uspto.gov> wrote:
I=20 have a char field which carries null value.
The samething with = varchar=20 field also.
when I pass null values it was throwing sql exception = as=20 incompatible column types. Then for varchar field i add = #centerNo:VARCHAR#=20 and same for DAte field  #priorityDt:DATE#.
When I did = same=20 for CHAR #parentPatentNo:CHAR# I got error that inserted value too = large for=20 a column
Then I tried
#parentPatentNo:CHAR(10)#
Now it says = incompatable type column.


<insert = id=3D"PatentedCaseTblInsert"=20 parameterClass=3D"PatentedCase">
INSERT INTO PATENTED_CASE=20 (PC_PATENT_NO,PATENT_APPLICATION_NO,FILING_DT, PATENT_ISSUE_DT,=20 INVENTION_TITLE_TX, TECHNOLOGY_CENTER_NO, APPLICATION_PRIORITY_DT,=20 REISSUE_PARENT_PATENT_NO, INVENTOR_QT,=20 LAST_MODIFIED_USER_ID,LAST_MODIFIED_TS, ART_UNIT_NO) =
VALUES(#patentNo#,=20 #patentApplNo#, #filingDt#, #issueDt#, #title#, #centerNo:VARCHAR#,=20 #priorityDt:DATE#, #parentPatentNo:CHAR(10)#, #inventorQt#,=20 #lastModifiedUserId#, sysdate,=20 #artUnitNo#)
</insert>


Could you please provide = me a=20 solution very urgently.

Thanks,
Sruthi=20 Krishnamoorthi
703-562-9732(Work)
537 A - (Raytheon)=20 Location


-----Original Message-----
From: Morone, Bill = [mailto:=20 Morone.Bill@pennmutual.com]
Sent: Friday, June 02, 2006 11:20 = AM
To: user-java@ibatis.apache.org;=20 lmeadors@apache.org
Subject: = RE:=20 When returning mutiple objects and transforming "directly
to=20 xml


Larry,

I will take a better look at the source = when I=20 have the time. We can talk. Thanks.

I had to tell my manager = about=20 the change in stance regarding the xml moving forward. She was not = happy (I=20 sold her on the xml instead of having java value = objects  --get=20 rid of a layer -- it is only a semantic difference between a java = value=20 object and an xml one, right?).

Anyway. = Onward

-----Original=20 Message-----
From: larry.meadors@gmail.com = [mailto:larry.meadors@gmail.com]On = Behalf=20
Of Larry Meadors
Sent: Friday, June 02, 2006 10:56 AM
To: = user-java@ibatis.apache.org
Subject:=20 Re: When returning mutiple objects and transforming "directly
to = xml


I can help you build a row handler to do the = transformation=20 if you
need some help (though I suspect you won't), just contact = me=20 off-list,
and we can work on it - shouldn't take more than a few = minutes=20 to
"rough it in", then you can refine = it.

Larry


On=20 6/2/06, Morone, Bill <Morone.Bill@pennmutual.com= >=20 wrote:
>
>
> Gentlemen:
>
> I do = thank you=20 and believe you have a fine thing going. Like I said I
> = created a=20 very clean little design that basically uses the xml objects
> = emitted=20 by iBATIS and transforms them anyway you want (great for little =
>=20 docs). I'd like to see stuff move a little forward -- I'll=20 help!!!
>
>
> = Bill
>
>
>
>
>=20 -----Original Message-----
> From: Clinton Begin [mailto: = clinton.begin@gmail.com]
>=20 Sent: Friday, June 02, 2006 9:45 AM
> To: user-java@ibatis.apache.org
>=20 Subject: Re: When returning mutiple objects and transforming = "directly to=20
> xml
>
>
> Hi Bill,
>
> It = will=20 probably go away in version 3.0.  We'd never remove a = feature=20 from
> the current major version.  It will continue = to be=20 supported in 2.0.
>
> In it's place we'll likely either = suggest=20 or build-in second stage xml
> support, for turning classes, = beans and=20 maps into XML.  That will allow you
> to map them to = domain=20 objects AND convert them to XML.  Plus, there are
> = already=20 a number of XML libraries that support exactly that.  The=20 current
> implementation creates too much complexity in the=20 implementation, yet offers
> little additonal value over the = formerly=20 described approach.
>
> Don't worry though, we'll = always help=20 you upgrade.  Even if it doesn't exist
> in 3.0, = we'll have=20 a suggested upgrade path that shouldn't leave you
>=20 floundering.
>
> Cheers,
> Clinton=20
>
>
>
>
> On 6/2/06, Morone, Bill = <Morone.Bill@pennmutual.com= >=20 wrote:
> > Larry,
> >
> > Really? I think = it=20 bears great merit. I little expansion would make it
> really=20 practical. In fact hearing of its departure has me a little = worried.
>=20 >
> > Does this mean the resultClass=3D"xml" is going=20 away?
> >
> > I created a little (restlet = front-end)=20 framework that translates the xml
> output for web services. = I=20 extended ArrayList to deal with the
> "non-webformedness" of = the=20 queryForObject "list of little docs" situation
> and it works=20 great.
> >
> > Our system is scheduled to go into=20 production in October -- what are the
> future plans for the = xml=20 stuff -- I assume we'll have to subclass to extend.
> Will = your=20 superclass stuff stay the same?
> >
> > Bill=20 Morone
> >
> >
> > -----Original = Message-----=20
> > From: larry.meadors@gmail.com = [mailto:larry.meadors@gmail.com]On=20 Behalf
> > Of Larry Meadors
> > Sent: Thursday, = June 01,=20 2006 4:45 PM
> > To: user-java@ibatis.apache.org
>=20 > Subject: Re: When returning mutiple objects and transforming=20 "directly
> > to xml
> >
> >
> = > On=20 6/1/06, Morone, Bill <Morone.Bill@pennmutual.com= >=20 wrote:
> > > Coming soon, right?
> >
> = > On=20 the contrary, going away.
> >
> > I'd suggest = processing=20 the results of the query manually to create XML
> > with a = row=20 handler if you really need to create xml results.
> = >
> >=20 Larry
> > This message, including any attachments, is = intended only=20 for the
> recipient(s)
> > named above. It may = contain=20 confidential and privileged information. If
> you have
> = >=20 received this communication in error, please notify the sender=20 immediately
> and
> > destroy or delete the original = message. Also, please be aware that if you
> are not
> = > the=20 intended recipient, any review, disclosure, copying, distribution = or
>=20 any
> > action or reliance based on this message is = prohibited by=20 law.
> >
> = >
>
>
>  This=20 message, including any attachments, is intended only for the
> = recipient(s)
> named above. It may contain confidential and = privileged=20 information. If you
> have
> received this = communication in=20 error, please notify the sender immediately
> and
> = destroy or=20 delete the original message. Also, please be aware that if = you
> are=20 not
> the intended recipient, any review, disclosure, copying, = distribution or any
> action or reliance based on this = message is=20 prohibited by law.
>
>
>
This message, = including any=20 attachments, is intended only for the recipient(s)
named above. = It may=20 contain confidential and privileged information. If you have =
received=20 this communication in error, please notify the sender immediately=20 and
destroy or delete the original message. Also, please be aware = that if=20 you are not
the intended recipient, any review, disclosure, = copying,=20 distribution or any
action or reliance based on this message is=20 prohibited by=20 law.





------_=_NextPart_001_01C68666.37AE1D0A--