Return-Path: Delivered-To: apmail-jakarta-struts-user-archive@apache.org Received: (qmail 56775 invoked from network); 19 Jul 2002 16:47:06 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 19 Jul 2002 16:47:06 -0000 Received: (qmail 14094 invoked by uid 97); 19 Jul 2002 16:47:08 -0000 Delivered-To: qmlist-jakarta-archive-struts-user@jakarta.apache.org Received: (qmail 14062 invoked by uid 97); 19 Jul 2002 16:47:07 -0000 Mailing-List: contact struts-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list struts-user@jakarta.apache.org Received: (qmail 14050 invoked by uid 98); 19 Jul 2002 16:47:07 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <003f01c22f43$a862b270$c12810ac@jny.com> From: "hemant" To: "Struts Users Mailing List" References: <001801c22e85$5e16dd40$c12810ac@jny.com><3D37278B.3010808@cyberspaceroad.com><007e01c22ea8$0b3373e0$c12810ac@jny.com> <3D37CCDB.5080506@cyberspaceroad.com> <1027082507.1171.49.camel@linux> Subject: Re: Setter Methods not being called in nested:iterate scenario Date: Fri, 19 Jul 2002 12:45:14 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Aaron Many Thanks for the Monkey Struts example on your site. It was terrific. The Manager bashing is quite appropriate too. I am currently working for one right now :D Anyway.. going by the Monkey See, Monkey Code principle, any examples on the whole "wrapping it into LazyList and providing a class definition of the child bean" example for me to see* ? Why do I need to wrap it in the first place and it looks as if every wrapped collection has to be in some bean for the setters to work. Correct me If Iam wrong. Regards hemant ----- Original Message ----- From: "Arron Bates" To: "Struts Users Mailing List" Sent: Friday, July 19, 2002 8:41 AM Subject: Re: Setter Methods not being called in nested:iterate scenario :+( > FYI > > This isn't a "nested tags" issue at all, but a nested bean-in-a-list > issue which Struts had a long time before I wrote the nested tags. > > They're only guilty of making something quite complex very easy to do. > :) > > Wrap your collections in org.apache.commons.collections.LazyList, > provide a class definition of your child bean and it'll be sweet and > ready to do without any other effort, even in the reset() method. > > > Arron. > > > On Fri, 2002-07-19 at 18:24, Adam Hardy wrote: > > Wrong! > > I'll eat my hat if you haven't been gotcha'd by the nested tags gotcha. > > If your form is in the request, it (and its beans content) will have > > disappeared after displaying your page, and the new form bean on > > instantiation for a new request (incoming submit) will not contain the > > beans, because it ain't been thro' your Action yet. You need to do it in > > your reset() or put your form in the session scope. Everybody on the > > list has heard this once a week since the invention of nested tags, I > > reckon - sorry folks. You can apologise too Hemant, unless you ain't > > been gotcha'd. Coz it's all in the archives. > > > > hemant wrote: > > > > >Adam > > >Thanks for responding.. > > > > > >The Actionform (rangesform) itself is my root and I have a collection > > >reference "collectionOfPairs" in "rangesform", replete with getter/setter > > >methods. > > > > > >The collectionOfPairs is instantiated and populated. If not, I would not be > > >seeing the page with the correct data. right? > > > > > >As I said earlier, the getters work, the setters do not work. All this > > >inspite of having the bean in the form. > > > > > >Thanks > > >hemant > > > > > > > > >----- Original Message ----- > > >From: "Adam Hardy" > > >To: "Struts Users Mailing List" > > >Sent: Thursday, July 18, 2002 4:39 PM > > >Subject: Re: Setter Methods not being called in nested:iterate scenario :+( > > > > > > > > > > > > > > >>nested tags / indexed properties / nested beans gotcha. You have to > > >>instantiate the beans yourself in the form reset() if you want to > > >>capture the indexed properties. > > >> > > >> > > >>[this answer was automated, virtually] > > >> > > >>hemant wrote: > > >> > > >> > > >>>Comrades, > > >>> > > >>>I am trying to Iterate over a Collection of Collections of ValueObjects > > >>> > > >>> > > >and after some real painful experimentation (With VA 3.5.3 + Apache Tomcat + > > >Poolman ), I got the page to come up properly :). So far so good. I went out > > >and celebrated for a few minutes... > > > > > > > > >>>The getter methods seem to work fine. But the user data is not being > > >>> > > >>> > > >captured on Submit :( > > > > > > > > >>>Please throw some light on this... > > >>> > > >>>Here is the snippet from my JSP. > > >>> > > >>> > > > > > > > > >>> > > >>> > > >>> > > > > > > > > >>> > > >>> > > >>> > >>> > > >>> > > >type="com.xxx.operations.mplanning.mpi.util.ValueObjectPair"> > > > > > > > > >>> > > >>> > > >>>................... > > >>>................... > > >>> > > >>> > > >>> > > >>> Description > > >>> > >>> > > >>> > > >property="twVo.description"/> > > > > > > > > >>> > > >>> > > >>> > > >>> > > >>>For some reason, the setter Method of setDescription(String xyz) is not > > >>> > > >>> > > >being called. > > > > > > > > >>>Please help... > > >>> > > >>> > > >>>Many Thanks for Your Time > > >>> > > >>>Regards > > >>>hemant > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >> > > >>-- > > >>To unsubscribe, e-mail: > > >> > > >> > > > > > > > > > > > >>For additional commands, e-mail: > > >> > > >> > > > > > > > > > > > > > > > > > >-- > > >To unsubscribe, e-mail: > > >For additional commands, e-mail: > > > > > > > > > > > > > > > > > > > > -- > > To unsubscribe, e-mail: > > For additional commands, e-mail: > > > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > -- To unsubscribe, e-mail: For additional commands, e-mail: