openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dick <michael.d.d...@gmail.com>
Subject Re: [jira] Commented: (OPENJPA-952) Utilize Sun JDK's Attach API to dynamically load the OpenJPA enhancer agent
Date Thu, 05 Mar 2009 16:37:30 GMT
Whether any strategy is suitable for production use depends on one's QA
environment, so I won't add to the debate there.

I think there's value in having multiple entry points to the PCEnhancer.
Some developers will prefer maven's plugin, some prefer an eclipse plugin,
and others will not want to mess with it at all.

Making it easy for new users to get over the enhancement hurdle is as
important as compiling with JDBC 4 I think we get more questions about
enhancement on the mailing lists than any other topic. They're both barriers
to getting new devs or users involved.

Just my $0.02 on the vigorous debate ;-)

-mike


On Thu, Mar 5, 2009 at 9:27 AM, Rick Curtis <curtisr7@gmail.com> wrote:

>
> Pinaki -
>
> To get this back on track....
>
> The deep interest in dynamic runtime enhancement comes from the fact that
> our default enhancement strategy(subclassing) has a multitude of problems.
> This change will give us another option for out of the box enhancement and
> I
> think it will be the nail in the coffin for subclassing enhancement.
>
> I'd also like to state that no one in their right mind should use this
> method of enhancement in a production environment. :-)
>
> -Rick
>
>
>
> Pinaki Poddar wrote:
> >
> > Hi Kevin,
> >   > So, where is the value add for compiling with JDK6?
> >   I did give a chance to change the topic in this vigorous debate of
> > whether we need more transparency of enhancement than what we have now :)
> >
> >   For JDK6 support, I thought it is something that you will love to have
> > for OpenJPA. It gives you access to the compiler. That may help to
> bolster
> > interface based domain model support in OpenJPA or several places it uses
> > Proxy classes. The other area to look into is whether we can derive more
> > value from new JDBC 4 features.
> >   But we are forking the thread...
> >
> >
> >
> > Kevin Sutter wrote:
> >>
> >> On Wed, Mar 4, 2009 at 8:58 AM, Pinaki Poddar <ppoddar@apache.org>
> wrote:
> >>
> >>>
> >>> However, given that we have some reasonably transparent (imo) mechanics
> >>> already in place, if advanced expertise of bytecode/classloading is
> >>> focused
> >>> elsewhere (say, the longstanding issue of making OpenJPA compile with
> >>> JDK6
> >>> -- OPENJPA-5) -- it perhaps will add more value.
> >>
> >>
> >> Interesting comment.  So, where is the value add for compiling with
> JDK6?
> >> Most of our users are using the binary drops of OpenJPA.  Having OpenJPA
> >> built with JDK5 works just fine for this case.  And, for the development
> >> people that attempt to build OpenJPA, having multiple versions of the
> JDK
> >> available seems to be very common place.  I, myself, have at least half
> >> dozen different versions of the IBM and Sun JDKs available in my
> >> development
> >> environment.
> >>
> >> Are there specific features or enhancements that come about from moving
> >> to
> >> JDK 6 for our build environment?  From what I know, there are no glaring
> >> performance improvements like we experienced when moving from JDK4 to
> >> JDK5.
> >> I don't disagree that it would be nice to be buildable with JDK 6, but
> >> there
> >> doesn't seem to be a huge advantage for pushing for this feature.
> >>
> >> Comments are welcome.  :-)
> >> Kevin
> >>
> >>
> >>>
> >>>
> >>> --
> >>> View this message in context:
> >>>
> http://n2.nabble.com/-jira--Created%3A-%28OPENJPA-952%29-Utilize-Sun-JDK%27s-Attach-API-to-dynamically-load-the-OpenJPA-enhancer-agent-tp2417786p2423343.html
> >>> Sent from the OpenJPA Developers mailing list archive at Nabble.com.
> >>>
> >>>
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/-jira--Created%3A-%28OPENJPA-952%29-Utilize-Sun-JDK%27s-Attach-API-to-dynamically-load-the-OpenJPA-enhancer-agent-tp2417786p2430131.html
> Sent from the OpenJPA Developers mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message