Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 74076 invoked from network); 29 Oct 2002 19:57:47 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 29 Oct 2002 19:57:47 -0000 Received: (qmail 18066 invoked by uid 97); 29 Oct 2002 19:58:25 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 17937 invoked by uid 97); 29 Oct 2002 19:58:24 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 17851 invoked by uid 50); 29 Oct 2002 19:58:23 -0000 Date: 29 Oct 2002 19:58:23 -0000 Message-ID: <20021029195823.17834.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 13896] - populate fails with mapped properties X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13896 populate fails with mapped properties craig.mcclanahan@sun.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From craig.mcclanahan@sun.com 2002-10-29 19:58 ------- The order in which properties from the Map are processed is the order of keys in the Map, and is therefore dependent on the Map's implementation of the keys() method. It is therefore not appropriate for BeanUtils to make any attempt at guaranteeing a processing order. Further, attempting to do as you ask would likely require two passes through the Map, which would reduce performance for ALL users even if their apps did not depend on order. The BeanUtils.populate() and BeanUtils.copyProperties() methods are specifically designed to populate a *single* destination bean, not an entire tree. I would suggest that you factor your processing to set up the properties for each Article into a separate Map, that populates them in a loop, and adds them to the Test instance that should contain them. If you're doing all of this based on XML input, you might also explore using the Digester package to process your input document and instantiate the appropriate bean instances for you. -- To unsubscribe, e-mail: For additional commands, e-mail: