[jira] [Commented] (OPENEJB-2120) JPA 2.1 Support
[ https://issues.apache.org/jira/browse/OPENEJB-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978722#comment-14978722 ] Romain Manni-Bucau commented on OPENEJB-2120: - I see, if you can use a jpa 2.0 persistence.xml then using em = injectedEntityManager.unwrap(HibernateEntityManagerType.class) you can use jpa 2.1 with em. > JPA 2.1 Support > --- > > Key: OPENEJB-2120 > URL: https://issues.apache.org/jira/browse/OPENEJB-2120 > Project: OpenEJB > Issue Type: Wish > Components: general >Reporter: Pascal Knüppel >Assignee: Romain Manni-Bucau > Labels: jpa21 > > It would be really great if support for JPA 2.1 was provided. Is there any > chance that support for this api level will come soon? > In order to keep my Unit-Tests alive I need to downgrade all the requests to > the database to jpa 2.0 which makes working on my project very difficult... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OPENEJB-2120) JPA 2.1 Support
[ https://issues.apache.org/jira/browse/OPENEJB-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978703#comment-14978703 ] Romain Manni-Bucau commented on OPENEJB-2120: - [~CaptGoldfish] sorry I dont get your issue. Share a project on github to make it clearer maybe? > JPA 2.1 Support > --- > > Key: OPENEJB-2120 > URL: https://issues.apache.org/jira/browse/OPENEJB-2120 > Project: OpenEJB > Issue Type: Wish > Components: general >Reporter: Pascal Knüppel >Assignee: Romain Manni-Bucau > Labels: jpa21 > > It would be really great if support for JPA 2.1 was provided. Is there any > chance that support for this api level will come soon? > In order to keep my Unit-Tests alive I need to downgrade all the requests to > the database to jpa 2.0 which makes working on my project very difficult... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OPENEJB-2120) JPA 2.1 Support
[
https://issues.apache.org/jira/browse/OPENEJB-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978718#comment-14978718
]
Pascal Knüppel commented on OPENEJB-2120:
-
my problem is that I am not using tomee, just openejb-core and openejb-junit in
version 4.7.2. These are the latest versions if I am not mistaken. The JPA
support reaches only 2.0 here not 2.1. And your comment ("you needed to unwrap
entity manager to use new features") let me think that there is a way to
upgrade the JPA support in these versions. Did I misunderstand you?
> JPA 2.1 Support
> ---
>
> Key: OPENEJB-2120
> URL: https://issues.apache.org/jira/browse/OPENEJB-2120
> Project: OpenEJB
> Issue Type: Wish
> Components: general
>Reporter: Pascal Knüppel
>Assignee: Romain Manni-Bucau
> Labels: jpa21
>
> It would be really great if support for JPA 2.1 was provided. Is there any
> chance that support for this api level will come soon?
> In order to keep my Unit-Tests alive I need to downgrade all the requests to
> the database to jpa 2.0 which makes working on my project very difficult...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OPENEJB-2121) Add the possibility of running OpenEJB in debug mode with suspend=n
alberto gori created OPENEJB-2121: - Summary: Add the possibility of running OpenEJB in debug mode with suspend=n Key: OPENEJB-2121 URL: https://issues.apache.org/jira/browse/OPENEJB-2121 Project: OpenEJB Issue Type: Improvement Components: container system Reporter: alberto gori Priority: Minor the debug string in org.apache.openejb.config.RemoteServer is hardcoded: "-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=" It would be nice if at least suspend=y would be customizable. Otherwise when you run mvn tomee:debug you have to wait until the server is listening on port 5005, and then attach the remote debugger to continue the startup process. This results in a waste of time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OPENEJB-2120) JPA 2.1 Support
[ https://issues.apache.org/jira/browse/OPENEJB-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978672#comment-14978672 ] Pascal Knüppel commented on OPENEJB-2120: - sorry for my late response. Could you give an example how I can do this without breaking JTA-management? I reached a point where the lack of support for jpa 2.1 gets not just annoying but makes testing some things nearly impossible... and thats all because of that stupid oracle xmltype that I have to use... xmltype and jpa 2.0 do not get along very well... > JPA 2.1 Support > --- > > Key: OPENEJB-2120 > URL: https://issues.apache.org/jira/browse/OPENEJB-2120 > Project: OpenEJB > Issue Type: Wish > Components: general >Reporter: Pascal Knüppel >Assignee: Romain Manni-Bucau > Labels: jpa21 > > It would be really great if support for JPA 2.1 was provided. Is there any > chance that support for this api level will come soon? > In order to keep my Unit-Tests alive I need to downgrade all the requests to > the database to jpa 2.0 which makes working on my project very difficult... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OPENEJB-2121) Add the possibility of running OpenEJB in debug mode with suspend=n
[ https://issues.apache.org/jira/browse/OPENEJB-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978626#comment-14978626 ] Romain Manni-Bucau commented on OPENEJB-2121: - A workaround is to set the system property java.opts with the option you want and use tomee:run > Add the possibility of running OpenEJB in debug mode with suspend=n > --- > > Key: OPENEJB-2121 > URL: https://issues.apache.org/jira/browse/OPENEJB-2121 > Project: OpenEJB > Issue Type: Improvement > Components: container system >Reporter: alberto gori >Priority: Minor > > the debug string in org.apache.openejb.config.RemoteServer is hardcoded: > "-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=" > It would be nice if at least suspend=y would be customizable. Otherwise when > you run mvn tomee:debug you have to wait until the server is listening on > port 5005, and then attach the remote debugger to continue the startup > process. This results in a waste of time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OPENEJB-2120) JPA 2.1 Support
[ https://issues.apache.org/jira/browse/OPENEJB-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978779#comment-14978779 ] Pascal Knüppel commented on OPENEJB-2120: - Thank you so much. It is working > JPA 2.1 Support > --- > > Key: OPENEJB-2120 > URL: https://issues.apache.org/jira/browse/OPENEJB-2120 > Project: OpenEJB > Issue Type: Wish > Components: general >Reporter: Pascal Knüppel >Assignee: Romain Manni-Bucau > Labels: jpa21 > > It would be really great if support for JPA 2.1 was provided. Is there any > chance that support for this api level will come soon? > In order to keep my Unit-Tests alive I need to downgrade all the requests to > the database to jpa 2.0 which makes working on my project very difficult... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
