[
https://issues.jboss.org/browse/JBTM-2704?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-2704:
-------------------------------------
No, just link to the docs is fine. But you should work on adding the docs for this before
moving onto something else. And when I say, the "this" - I mean the particular
issue we are discussing now. You just need to add the chapter for compensations into the
docs, put "This is not complete" reference the docs issue JBTM-2680 and then add
the note specific to this thing. Next time I will mention to add the docs PR before
marking as ready to merge
Compensations framework cannot instantiate bean from ear archive
----------------------------------------------------------------
Key: JBTM-2704
URL:
https://issues.jboss.org/browse/JBTM-2704
Project: JBoss Transaction Manager
Issue Type: Bug
Components: Compensations
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Fix For: 5.next
BeanManagerUtil is using CDI BeanManager to instantiate classes from the deployment to be
used by the compensations framework. It works fine with war and jar archives, because all
deployment classes are accessible for the root bean manager. However, ear archives have
multiple bean managers and some classes cannot be accessed.
Martin Kouba has provided a workaround for this on Weld forum by using weld-core to get
the correct bean manager.
It would be better to find a solution for this without adding a direct dependency on
weld-core and instead injecting the correct bean manager once by the subsystem. However,
if that is not possible, we should use the provided workaround.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)