openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (OPENJPA-651) Disable dangerous "fallback enhancement", make openjpa.RuntimeUnenhancedClasses=unsupported the default
Date Sun, 09 Aug 2009 17:44:14 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Dick resolved OPENJPA-651.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

I've changed the default to unsupported for trunk (2.0.0). I'm less sanguine about changing
it in 1.3.x but I could be persuaded to make the change there too. 

For 1.2.x and older I think we need to keep the current setting - to avoid breaking existing
apps. 

> Disable dangerous "fallback enhancement", make openjpa.RuntimeUnenhancedClasses=unsupported
the default
> -------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-651
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-651
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: jpa, kernel, UnenhancedClasses
>    Affects Versions: 1.0.3, 1.1.0, 1.2.1, 2.0.0
>            Reporter: Michael Vorburger
>            Assignee: Michael Dick
>             Fix For: 2.0.0
>
>
> As discussed on the email thread 'Disable dangerous "fallback enhancement" how?' on users@openjpa.apache.org
(e.g. on http://markmail.org/message/5e2yfcp3w3vhmrob?q=Disable+dangerous+%22fallback+enhancement%22+how%3F+list:org%2Eapache%2Eopenjpa%2Eusers),
I hereby suggest that by default, OpenJPA behaves as if openjpa.RuntimeUnenhancedClasses=unsupported
was explicitly configured. 
> (Copy/paste) The fact that https://issues.apache.org/jira/browse/OPENJPA-293 is still
an Open New Feature, with five open sub-tasks (so technically this development was never finished,
yet it's automatically activated and shows up in the official doc) and in e.g. https://issues.apache.org/jira/browse/OPENJPA-444
(and may be others?) there are bug reports which are probably only due to this, may support
my point of view?
> Craig (Craig.Russell@...) appears to support this proposed Improvement (judging from
his email lundi, 23. juin 2008 21:33 in same thread).
> I'd love to see this in 1.1.1. May be due to backward compatibility you jugde it would
be safer to put this in 1.2.0 only? - Or is too late and impossible to change this default
now? Hope not!
> PS: Workaround for 1.1.0 is openjpa.RuntimeUnenhancedClasses=unsupported (undocumented,
see https://issues.apache.org/jira/browse/OPENJPA-650).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message