[
https://issues.jboss.org/browse/JBTM-1821?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1821:
-------------------------------------
Conversation with Gytis on a potential solution:
pfrobinson: whilst you are at it, can you have a quick check to see if you can add modules
to the classloader in that phase too?
[12:06pm] gytist: you mean dependencies like org.jboss.xts?
[12:10pm] pfrobinson: yeah
[12:10pm] pfrobinson: I want to scan for the use of @Transactional and then add the
org.jboss.jts depenedency to the deployment
[12:10pm] gytist: I think it is, some of the subsystems automatically add dependencies
[12:11pm] pfrobinson: yeah, that was my thoughts too
[12:11pm] pfrobinson: for example, if persistence.xml is present, you add the jpa deps
[12:11pm] gytist: I saw it when I was researching my issue on Monday
[12:11pm] gytist: need to find it again
[12:12pm] gytist: grep for this class WSDependenciesProcessor
[12:12pm] gytist: that's what you need
[12:12pm] pfrobinson: great, thanks
Make @Transactional work without specifying the "org.jboss.jts
export services" dependency
------------------------------------------------------------------------------------------
Key: JBTM-1821
URL:
https://issues.jboss.org/browse/JBTM-1821
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: JTA
Reporter: Paul Robinson
Assignee: Paul Robinson
Priority: Critical
Fix For: 5.0.0.M4
Currently all deployments that use @Tranactional should have a MANIFEST.MF containing
"Dependencies: org.jboss.jts export services".
We should find a better approach to activating these interceptors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira