Return-Path: Delivered-To: apmail-commons-user-archive@www.apache.org Received: (qmail 95364 invoked from network); 22 Feb 2009 22:15:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Feb 2009 22:15:58 -0000 Received: (qmail 67305 invoked by uid 500); 22 Feb 2009 22:15:54 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 67229 invoked by uid 500); 22 Feb 2009 22:15:54 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 67218 invoked by uid 99); 22 Feb 2009 22:15:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Feb 2009 14:15:54 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ahhughes@gmail.com designates 209.85.142.186 as permitted sender) Received: from [209.85.142.186] (HELO ti-out-0910.google.com) (209.85.142.186) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Feb 2009 22:15:45 +0000 Received: by ti-out-0910.google.com with SMTP id j3so1061649tid.10 for ; Sun, 22 Feb 2009 14:15:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=pmSazHuqaI4bhqwAB//Iv2pKCBXMRBWHGAudZ8GTtBs=; b=NSuexfKYLIDyfcllAPyJ80T39+D+6uvd68KiSJ64rHH5frEXDpzfvnhYPO+olRvr55 mtzZ7Dio3WxdICQc45NNhRxn6vCsZurCJE8qLP3QrHMNhJh6YcISledMMaSjqUMdd43B CsETVgrfusDFltZ67PujF//SIiAtFIseIQJpU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=vyjdNWLny7oNyBJZqqhuJ2F80C1SJUZvQBvNrt1AFnpgU28A33Z0JCeRaOZbpZWiOq StWIdI7A+UWnCpVoNFUdf+04olCdr8gS2IDpI+OYPAQiBmYkyRQ91cwPAiT3JWp+xlqq ZYIQvJ4vbGqZg5G+xe8Wl5bby3y2rUjuyagkA= MIME-Version: 1.0 Received: by 10.110.3.15 with SMTP id 15mr4818694tic.0.1235340923322; Sun, 22 Feb 2009 14:15:23 -0800 (PST) In-Reply-To: <49A05E54.4050607@cyberspaceroad.com> References: <49A05E54.4050607@cyberspaceroad.com> Date: Mon, 23 Feb 2009 08:45:23 +1030 Message-ID: <5f528cf40902221415s2b50de0cua4a244527cf78ad0@mail.gmail.com> Subject: Re: [beanutils] converting HTTP params into an arbitrary object model From: Andrew Hughes To: Commons Users List Content-Type: multipart/alternative; boundary=001485f4225ee940980463893832 X-Virus-Checked: Checked by ClamAV on apache.org --001485f4225ee940980463893832 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I have no idea if this suits your needs, but JXPath has a HTTP Request expression parser. So you can then 'pick' out of the http request/session... etc whatever you want using an XPath expression. http://commons.apache.org/jxpath/users-guide.html#Servlet_Contexts On Sun, Feb 22, 2009 at 6:34 AM, Adam Hardy < ahardy.struts@cyberspaceroad.com> wrote: > I have spent a day researching and prototyping with various open-source > options available which facilitate converting an HTTP request's parameters > into an object model of javabeans in a JPA persistence framework. > > I don't want to re-invent the wheel and I was quite confident that > BeanUtils could handle it all, but I have now come across some areas where I > need to code it myself. > > I just wanted to ask BeanUtils developers what the future holds in terms of > my aims, as I'll take that as guidance on how much to code around BeanUtils > and how much to compromise to get what I need, when there's a strong chance > of being able to ditch the code I'll have to write now, to replace it with > ideally just a couple of calls to BeanUtils. > > The main thing I have to work around is the inability of a custom Converter > to know what class of entity beans belong in a list or set. If the Converter > could see the entity bean owning the list (the parent in the parent-child > entity relationship), then in Java 1.5+ it could work out by reflection how > it has been parameterized with generics and which child entity bean belongs > in the list. > > Just in case you were going to point me to OGNL to do this, thanks but I've > been there and have some other issues with that. > > Best regards > Adam > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@commons.apache.org > For additional commands, e-mail: user-help@commons.apache.org > > --001485f4225ee940980463893832--