July 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2706) Verify that we can run on the IBM JVM with OpenJDK

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2706?page=com.atlassian.jira.plugin.... ] Michael Musgrove closed JBTM-2706. ---------------------------------- Resolution: Done The job name is narayana-ibm-jvm and the tests are passing > Verify that we can run on the IBM JVM with OpenJDK > -------------------------------------------------- > > Key: JBTM-2706 > URL: https://issues.jboss.org/browse/JBTM-2706 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > We need to set up a CI job that runs the JTS tests using the OpenJDK orb -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2706) Verify that we can run on the IBM JVM with OpenJDK

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2706: -------------------------------------- Summary: Verify that we can run on the IBM JVM with OpenJDK Key: JBTM-2706 URL: https://issues.jboss.org/browse/JBTM-2706 Project: JBoss Transaction Manager Issue Type: Sub-task Components: JTS Affects Versions: 5.3.3.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.later We need to set up a CI job that runs the JTS tests using the OpenJDK orb -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2705) Investigate alternatives to encoding recovery data in RecoveryCoordinator IORs

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2705?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2705: ----------------------------------- Parent: JBTM-2110 Issue Type: Sub-task (was: Task) > Investigate alternatives to encoding recovery data in RecoveryCoordinator IORs > ------------------------------------------------------------------------------ > > Key: JBTM-2705 > URL: https://issues.jboss.org/browse/JBTM-2705 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > During JTS resource enlistment we create a RecoveryCoordinator IOR and embed recovery information in the ObjectKey part. This is not a portable solution since we need to use ORB vendor specific APIs to modify the ObjectKey. It would be preferable if we could use something that is in the CORBA specs that will work for all ORBs such as Portable Intercpeors (http://www.omg.org/cgi-bin/doc?ptc/2001-03-04). > Note that there is no current solution for IBM orb. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2705) Investigate alternatives to encoding recovery data in RecoveryCoordinator IORs

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2705: -------------------------------------- Summary: Investigate alternatives to encoding recovery data in RecoveryCoordinator IORs Key: JBTM-2705 URL: https://issues.jboss.org/browse/JBTM-2705 Project: JBoss Transaction Manager Issue Type: Task Components: JTS Affects Versions: 5.3.3.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next During JTS resource enlistment we create a RecoveryCoordinator IOR and embed recovery information in the ObjectKey part. This is not a portable solution since we need to use ORB vendor specific APIs to modify the ObjectKey. It would be preferable if we could use something that is in the CORBA specs that will work for all ORBs such as Portable Intercpeors (http://www.omg.org/cgi-bin/doc?ptc/2001-03-04). Note that there is no current solution for IBM orb. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2704) Compensations framework cannot instantiate bean from ear archive

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2704?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Gytis Trikleris created pull request #47 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > 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)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2704) Compensations framework cannot instantiate bean from ear archive

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2704?page=com.atlassian.jira.plugin.... ] Work on JBTM-2704 started by Gytis Trikleris. --------------------------------------------- > 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)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2704) Compensations framework cannot instantiate bean from ear archive

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2704?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2704: ---------------------------------- Forum Reference: https://developer.jboss.org/message/959371#959371 (was: https://developer.jboss.org/message/959371#959371, https://developer.jboss.org/thread/271273, https://developer.jboss.org/message/960078) > 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)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2704) Compensations framework cannot instantiate bean from ear archive

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2704?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2704: ---------------------------------- Forum Reference: https://developer.jboss.org/thread/271273, https://developer.jboss.org/message/960078 > 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)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2704) Compensations framework cannot instantiate bean from ear archive

by Jive JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2704?page=com.atlassian.jira.plugin.... ] Jive JIRA Integration updated JBTM-2704: ---------------------------------------- Forum Reference: https://developer.jboss.org/message/959371#959371, https://developer.jboss.org/thread/271273, https://developer.jboss.org/message/960078 (was: https://developer.jboss.org/thread/271273, https://developer.jboss.org/message/960078) > 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)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2704) Compensations framework cannot instantiate bean from ear archive

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2704: ------------------------------------- Summary: 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 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)

7 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2016