Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <10723139.post@talk.nabble.com>
Date: Mon, 21 May 2007 10:20:02 -0700 (PDT)
From: "James.Strachan" <james.strachan@gmail.com>
To: open-jpa-dev@incubator.apache.org
Subject: Re: the pain of post processing bytecode (another beg for a simple
 reflection/cglib alternative like hibernate)
In-Reply-To: <7262f25e0705170819i8a52d61x7f772ccca97ab6dc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <10660986.post@talk.nabble.com>
 <7262f25e0705170819i8a52d61x7f772ccca97ab6dc@mail.gmail.com>


Patrick Linskey-2 wrote:
> 
>> How hard is it to add a reflection/cglib type alternative to the upfront
>> bytecode generation (like hibernate does) to save us from the
>> development-time pain?
> 
> Not particularly hard. There are a few APIs that would break for some
> cases,  but it's even pretty straightforward to do a subclassing
> approach for property-based access type without losing much
> performance -- the only cost in that configuration is with
> persistent-new instances.
> 
> -Patrick
> 

Awesome - can't wait for it to be supported :)

Should I raise a JIRA?

-- 
James
-------
http://macstrac.blogspot.com/

-- 
View this message in context: http://www.nabble.com/the-pain-of-post-processing-bytecode-%28another-beg-for-a-simple-reflection-cglib-alternative-like-hibernate%29-tf3770760.html#a10723139
Sent from the open-jpa-dev mailing list archive at Nabble.com.