You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Michael Vorburger (JIRA)" <ji...@apache.org> on 2008/07/02 19:49:44 UTC
[jira] Created: (OPENJPA-651) Disable dangerous "fallback
enhancement", make openjpa.RuntimeUnenhancedClasses=unsupported the default
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
Affects Versions: 1.1.0
Reporter: Michael Vorburger
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@Sun.COM) 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.
[jira] Updated: (OPENJPA-651) Disable dangerous "fallback
enhancement", make openjpa.RuntimeUnenhancedClasses=unsupported the default
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Russell updated OPENJPA-651:
----------------------------------
Description:
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).
was:
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@Sun.COM) 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).
Coincident with this change being made, the message should be very explicit how to enable runtime subclassing if that's what users want.
> 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.1.0
> Reporter: Michael Vorburger
>
> 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.
[jira] Commented: (OPENJPA-651) Disable dangerous "fallback
enhancement", make openjpa.RuntimeUnenhancedClasses=unsupported the default
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718163#action_12718163 ]
Michael Dick commented on OPENJPA-651:
--------------------------------------
Pursuant to the vote [1] on the dev mailing list I'm planning on turning subclassing off by default in trunk. 1.3.x may follow shortly.
[1] http://n2.nabble.com/-VOTE--Turn-off-enhancement-by-subclassing-as-the-default-tp1616140p1616140.html
> 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
>
> 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.
[jira] Resolved: (OPENJPA-651) Disable dangerous "fallback
enhancement", make openjpa.RuntimeUnenhancedClasses=unsupported the default
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (OPENJPA-651) Disable dangerous "fallback
enhancement", make openjpa.RuntimeUnenhancedClasses=unsupported the default
Posted by "Michael Vorburger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631759#action_12631759 ]
Michael Vorburger commented on OPENJPA-651:
-------------------------------------------
No reactions to this in months... at least document this, see the OPENJPA-650 ?
> 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
> Affects Versions: 1.1.0
> Reporter: Michael Vorburger
>
> 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@Sun.COM) 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.
[jira] Updated: (OPENJPA-651) Disable dangerous "fallback
enhancement", make openjpa.RuntimeUnenhancedClasses=unsupported the default
Posted by "Michael Vorburger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Vorburger updated OPENJPA-651:
--------------------------------------
Component/s: kernel
jpa
> 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
> Affects Versions: 1.1.0
> Reporter: Michael Vorburger
>
> 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@Sun.COM) 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.
[jira] Updated: (OPENJPA-651) Disable dangerous "fallback
enhancement", make openjpa.RuntimeUnenhancedClasses=unsupported the default
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated OPENJPA-651:
---------------------------------
Affects Version/s: (was: 2.0.0)
2.0.0-M1
2.0.0-M2
Fix Version/s: (was: 2.0.0)
2.0.0-M3
> 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-M1, 2.0.0-M2
> Reporter: Michael Vorburger
> Assignee: Michael Dick
> Fix For: 2.0.0-M3
>
>
> 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.
[jira] Assigned: (OPENJPA-651) Disable dangerous "fallback
enhancement", make openjpa.RuntimeUnenhancedClasses=unsupported the default
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick reassigned OPENJPA-651:
------------------------------------
Assignee: Michael Dick
> 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
>
> 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.
[jira] Updated: (OPENJPA-651) Disable dangerous "fallback
enhancement", make openjpa.RuntimeUnenhancedClasses=unsupported the default
Posted by "Kevin Sutter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Sutter updated OPENJPA-651:
---------------------------------
Component/s: UnenhancedClasses
> 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.1.0
> Reporter: Michael Vorburger
>
> 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@Sun.COM) 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.
[jira] Updated: (OPENJPA-651) Disable dangerous "fallback
enhancement", make openjpa.RuntimeUnenhancedClasses=unsupported the default
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick updated OPENJPA-651:
---------------------------------
Affects Version/s: 2.0.0
1.0.3
1.2.1
> 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
>
> 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.