[jbossts-issues] [JBoss JIRA] (JBTM-3332) Add constructor to HornetqObjectStoreAdaptor to support named bean lookup.

[Miloslav Žežulka (Jira)]

     [ https://issues.redhat.com/browse/JBTM-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Miloslav Žežulka updated JBTM-3332:
-----------------------------------
    Description: 
When retrieving reference to the Object Store, Narayana can do a named bean lookup; more specifically, the store manager [searches for the bean|https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/objectstore/StoreManager.java#L94] named _communicationStore._

Part of the _initStore_ procedure referenced in the link is [class loading|https://github.com/jbosstm/narayana/blob/f370005e0959ad2c1e799d6ec7d7dfcb9035304a/common/classes/com/arjuna/common/internal/util/ClassloadingUtility.java#L112]. As can be decucted from the code, when we try to classload a named bean, the implementation looks for a very specific constructor containing exactly one parameter and the type of such parameter must end with _EnvironmentBean_.

Problem arises (as already noted in the quickstart [ArjunaJTA/object_store|https://github.com/jbosstm/quickstart/blob/master/ArjunaJTA/object_store/src/main/java/org/jboss/narayana/jta/quickstarts/HornetqStoreExample.java]) when we wish to use HornetqObjectStoreAdaptor as our communication store as no such constructor currently exists.

  was:
When retrieving reference to the Object Store, Narayana can do a named bean lookup, more specifically the store manager searches for the bean named _communicationStore_ : [https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/objectstore/StoreManager.java#L94]

Part of the _initStore_ procedure referenced in the link is [class loading|https://github.com/jbosstm/narayana/blob/f370005e0959ad2c1e799d6ec7d7dfcb9035304a/common/classes/com/arjuna/common/internal/util/ClassloadingUtility.java#L112]. As can be decucted from the code, when we try to classload a named bean, the implementation looks for a very specific constructor containing exactly one parameter and the type of such parameter must end with _EnvironmentBean_.

Problem arises (as already noted in the quickstart [ArjunaJTA/object_store|https://github.com/jbosstm/quickstart/blob/master/ArjunaJTA/object_store/src/main/java/org/jboss/narayana/jta/quickstarts/HornetqStoreExample.java]) when we wish to use HornetqObjectStoreAdaptor as our communication store as no such constructor currently exists.



> Add constructor to HornetqObjectStoreAdaptor to support named bean lookup.
> --------------------------------------------------------------------------
>
>                 Key: JBTM-3332
>                 URL: https://issues.redhat.com/browse/JBTM-3332
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>            Reporter: Miloslav Žežulka
>            Assignee: Miloslav Žežulka
>            Priority: Minor
>
> When retrieving reference to the Object Store, Narayana can do a named bean lookup; more specifically, the store manager [searches for the bean|https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/objectstore/StoreManager.java#L94] named _communicationStore._
> Part of the _initStore_ procedure referenced in the link is [class loading|https://github.com/jbosstm/narayana/blob/f370005e0959ad2c1e799d6ec7d7dfcb9035304a/common/classes/com/arjuna/common/internal/util/ClassloadingUtility.java#L112]. As can be decucted from the code, when we try to classload a named bean, the implementation looks for a very specific constructor containing exactly one parameter and the type of such parameter must end with _EnvironmentBean_.
> Problem arises (as already noted in the quickstart [ArjunaJTA/object_store|https://github.com/jbosstm/quickstart/blob/master/ArjunaJTA/object_store/src/main/java/org/jboss/narayana/jta/quickstarts/HornetqStoreExample.java]) when we wish to use HornetqObjectStoreAdaptor as our communication store as no such constructor currently exists.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)