Return-Path: Delivered-To: apmail-jakarta-turbine-dev-archive@apache.org Received: (qmail 30622 invoked from network); 3 Dec 2002 22:32:43 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 3 Dec 2002 22:32:43 -0000 Received: (qmail 9368 invoked by uid 97); 3 Dec 2002 22:33:51 -0000 Delivered-To: qmlist-jakarta-archive-turbine-dev@jakarta.apache.org Received: (qmail 9335 invoked by uid 97); 3 Dec 2002 22:33:50 -0000 Mailing-List: contact turbine-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Turbine Developers List" Reply-To: "Turbine Developers List" Delivered-To: mailing list turbine-dev@jakarta.apache.org Received: (qmail 9303 invoked by uid 98); 3 Dec 2002 22:33:50 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Intake problem Date: Tue, 3 Dec 2002 16:25:42 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Intake problem Thread-Index: AcKbGZI0LeD/t9JlQWSp4rAhjarjygAAXBcg From: "Quinton McCombs" To: "Turbine Developers List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N In the logic to determine if a field is set, it makes two checks. 1) Does the key exist? 2) Is the value of the key something other than an empty string? In my case, test #1 passes. The second test fails but I am trying to set the value to an empty string. I would think that in the case of a form only mapping to some of the attributes of an object, it wouold not be an issue. As long as the group used on the form did not map a field to the attribute, it would not even enter the loop where the attributes are set. Evern if the group did map that field, as long as the field was not used on the form, the first test would fail. Is this working for anyone else? It seems odd that no one using intake is having this problem. =20 -----Original Message----- From: Chris K Chew [mailto:chris@fenetics.com]=20 Sent: Tuesday, December 03, 2002 4:22 PM To: Turbine Developers List Subject: RE: Intake problem It seems to me an implication would be in cases where people have multiple forms to populate a single object, like in a wizard. I think it might be nice to have a switch in the -----Original Message----- > From: John McNally [mailto:jmcnally@collab.net] > Sent: Tuesday, December 03, 2002 3:10 PM > To: Turbine Developers List > Subject: Re: Intake problem > > > It is a problem with the fact that intake treats an empty string as an > unset value. I'm not sure the implications of changing this behavior. > > john mcnally > > On Tue, 2002-12-03 at 13:37, Quinton McCombs wrote: > > I have noticed a small problem with intake after migrating to T2.2=20 > > RC2. It appears that I can not set a string field to null if it=20 > > already had a value. Here are a few snippets from my configuration=20 > > files.... > > > > intake.xml - > > > > > > > > > > Maximum Length is=20 > > 50 > > Alphabetic = > > Value Required > > > > > > > > > > schema.xml - > > > > > > > > > > > >

> > > > > > My form is initially populated with data from the Person object. =20 > > The field "FirstName" has a value. I then delete the value from the > > field and submit the form. > > > > After I get the intake tool and retreive the group, I look at the=20 > > value of group.get("FirstName").getValue(). It is null. I load my=20 > > object > > (person) from database to make modifications to it. The value of > > person.getFirstName() is "John". All is well so far. > > > > This line of code executes to update my persistent object with data from > > the group: group.setProperties(person); > > > > After this line of code executes, person.getFirstName() is "John". > > > > Other fields that were changed to non-null values were set properly=20 > > during the execution of the method. > > > > After looking through the code a little, I found that > > Field.setProperty(Object) will nto eexcute the setter method unless > > Field.isSet() returns true. Is this a defect or is there something=20 > > that I need to change in the way I am using intake? > > > > > > -- > To unsubscribe, e-mail:=20 > > For additional commands, e-mail:=20 > -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: