4:21 a.m.
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Fix For: EJB 3.0 RC10 - FD
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:02 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=all ]
Nicolas Leroux updated EJBTHREE-791:
------------------------------------
Attachment: EJBTHREE-791.patch
Hi I encounter this problem as well and came up with the following patch to fix this issue
(and a NPE when use the non jta transaction manager, may be there is another open bug, I
will have a look). I am attaching a patch file.
I hope it will help.
Nicolas
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Fix For: EJB 3.0 RC10 - FD
Attachments: EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:04 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=comments#action_12354544 ]
Nicolas Leroux commented on EJBTHREE-791:
-----------------------------------------
The patch is for the version svn tagged version EJB_RC9_Patch_1.
Nicolas
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Fix For: EJB 3.0 RC10 - FD
Attachments: EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:22 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=all ]
Nicolas Leroux updated EJBTHREE-791:
------------------------------------
Attachment: EJBTHREE-791.patch
Same with log.debug instead of log.info
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Fix For: EJB 3.0 RC10 - FD
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:22 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=comments#action_12354547 ]
Nicolas Leroux commented on EJBTHREE-791:
-----------------------------------------
Note that this patch has also been submitted for the issue EJB-665.
The patch is to apply to the svn version tagged EJB3_RC9_Patch_1.
I have used eclipse to create the patch.
Let me know if you have a problem with the patch.
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Fix For: EJB 3.0 RC10 - FD
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:15 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=all ]
Nicolas Leroux updated EJBTHREE-791:
------------------------------------
Attachment: EJBTHREE-791.patch
Same but with typo fixed in the error message: EntityManager must be accessed within a
transaction.
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Fix For: EJB 3.0 RC10 - FD
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch, EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:29 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=all ]
Nicolas Leroux updated EJBTHREE-791:
------------------------------------
Attachment: EJBTHREE-791.patch
Same but without the unused import.
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Fix For: EJB 3.0 RC10 - FD
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch, EJBTHREE-791.patch,
EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:07 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=all ]
Carlo de Wolf updated EJBTHREE-791:
-----------------------------------
Fix Version/s: AS 4.2.0 CR2
(was: AS 4.2.0 CR1)
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Fix For: AS 4.2.0 CR2
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch, EJBTHREE-791.patch,
EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:01 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=all ]
Carlo de Wolf updated EJBTHREE-791:
-----------------------------------
Fix Version/s: AS 4.2.0 GA
(was: AS 4.2.0 CR2)
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Fix For: AS 4.2.0 GA
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch, EJBTHREE-791.patch,
EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:52 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=all ]
Carlo de Wolf updated EJBTHREE-791:
-----------------------------------
Fix Version/s: Branch_4_2
(was: AS 4.2.0 GA)
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Fix For: Branch_4_2
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch, EJBTHREE-791.patch,
EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:02 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=all ]
Carlo de Wolf updated EJBTHREE-791:
-----------------------------------
Fix Version/s: (was: AS 4.2.1)
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch, EJBTHREE-791.patch,
EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:04 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=comments#action_12367010 ]
Carlo de Wolf commented on EJBTHREE-791:
----------------------------------------
EJB3 JPA 6.2.1.2:
In a Java EE environment, if this element is not specified, the default is JTA.
EJB3 JPA 6.2.1.2:
A transaction-type of JTA assumes that a JTA data source will be provided—either as
specified by the jta-data-source element or provided by the container.
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch, EJBTHREE-791.patch,
EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:04 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=comments#action_12367025 ]
Nicolas Leroux commented on EJBTHREE-791:
-----------------------------------------
Hi, the problem is not to default to JTA or not. The problem is that it is quite
impossible to use the RESOURCE_LOCAL transaction type.
I completely agree with the fact that it should default to JTA.
However, if you define:
{code}
<persistence-unit transaction-type="RESOURCE_LOCAL">
</persistence-unit>
{code}
I think you should be able to use it as such.
The problem comes from this bit of code:
{code}
if ("RESOURCE_LOCAL".equals(xml.getTransactionType()))
{code{
it should be:
{code}
if (PersistenceUnitTransactionType.RESOURCE_LOCAL.equals(xml.getTransactionType()))
{code}
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch, EJBTHREE-791.patch,
EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:41 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=comments#action_12367106 ]
Emmanuel Bernard commented on EJBTHREE-791:
-------------------------------------------
Nicolas is right: explicit use of RESOURCE_LOCAL have to be supported.
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch, EJBTHREE-791.patch,
EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:57 a.m.
New subject: [JBoss JIRA] Assigned: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=all ]
Carlo de Wolf reassigned EJBTHREE-791:
--------------------------------------
Assignee: Carlo de Wolf
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Assigned To: Carlo de Wolf
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch, EJBTHREE-791.patch,
EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:59 a.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=all ]
Carlo de Wolf resolved EJBTHREE-791.
------------------------------------
Fix Version/s: AS 5.0.0.Beta3
AS 4.2.3.GA
AS 4.2.2.GA
AS 4.2.1.GA
AS 4.2.0 GA
Resolution: Done
Fixed in rev 59350
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Assigned To: Carlo de Wolf
Fix For: AS 5.0.0.Beta3, AS 4.2.3.GA, AS 4.2.2.GA, AS 4.2.1.GA, AS 4.2.0 GA
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch, EJBTHREE-791.patch,
EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:41 p.m.
New subject: [JBoss JIRA] Closed: (EJBTHREE-791) Deployment fail on non JTA persistence unit
[ http://jira.jboss.com/jira/browse/EJBTHREE-791?page=all ]
Carlo de Wolf closed EJBTHREE-791.
----------------------------------
Deployment fail on non JTA persistence unit
-------------------------------------------
Key: EJBTHREE-791
URL: http://jira.jboss.com/jira/browse/EJBTHREE-791
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Emmanuel Bernard
Assigned To: Carlo de Wolf
Fix For: AS 5.0.0.Beta3, AS 4.2.3.GA, AS 4.2.2.GA, AS 4.2.1.GA, AS 4.2.0 GA
Attachments: EJBTHREE-791.patch, EJBTHREE-791.patch, EJBTHREE-791.patch,
EJBTHREE-791.patch
<persistence-unit>
<!-- no jta-datasource defined -->
</persistence-unt>
and
<persistence-unit transaction-type="RESOURCE_LOCAL">
<!-- no jta-datasource defined -->
</persistence-unt>
Seems to fail with
WARN [ServiceController] Problem starting service
persistence.units:ear=jblogApp.ear,jar=jblogBeans.jar,unitName=jblog
java.lang.RuntimeException: You have not defined a jta-data-source for a JTA enabled
persistence context named: jblog
(2) should work
(1) is very much expected from a usability POV. basically, if no jta-datasource is
defined, we should expect a default transaction-type of RESOURCE_LOCAL
Note that you might want to let the persistence provider test such compatibility issues,
since it has more contextual information than the container (ie knows the meaning of the
proprietary properties)
Max can you confirm that my description match your bug.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6016
days inactive
6428
days old
16 comments
4 participants
participants (4)
-
Carlo de Wolf (JIRA) -
Emmanuel Bernard (JIRA)
-
Emmanuel Bernard (JIRA) -
Nicolas Leroux (JIRA)