April 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2662) Export org.jboss.tm, has 1, private references [org.jboss.logging]

by Amos Feng (JIRA)

Amos Feng created JBTM-2662: ------------------------------- Summary: Export org.jboss.tm, has 1, private references [org.jboss.logging] Key: JBTM-2662 URL: https://issues.jboss.org/browse/JBTM-2662 Project: JBoss Transaction Manager Issue Type: Sub-task Reporter: Amos Feng Assignee: Amos Feng -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2660) multiple jars provide the same package:javax/transaction

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2660?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2660: --------------------------------- the SPI one should try to be solved by making sure the SPI version we use doesn't expose in JTA 1.1 so that should be solved in that project. > multiple jars provide the same package:javax/transaction > -------------------------------------------------------- > > Key: JBTM-2660 > URL: https://issues.jboss.org/browse/JBTM-2660 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > [WARNING] Bundle org.jboss.narayana.osgi:narayana-osgi-jta:bundle:5.3.3.Final-SNAPSHOT : Split package, multiple jars provide the same package:javax/transaction > Use Import/Export Package directive -split-package:=(merge-first|merge-last|error|first) to get rid of this warning > Package found in [Jar:jboss-transaction-api_1.2_spec, Jar:jboss-transaction-api_1.1_spec] > Class path [Jar:., Jar:org.osgi.core, Jar:org.osgi.compendium, Jar:jbosgi-metadata, Jar:jboss-transaction-api_1.2_spec, Jar:jta, Jar:common, Jar:arjuna, Jar:jconsole, Jar:jboss-transaction-spi, Jar:jboss-connector-api_1.5_spec, Jar:jboss-transaction-api_1.1_spec, Jar:narayana-jts-integration, Jar:jboss-logging, Jar:artemis-journal, Jar:artemis-commons, Jar:jboss-logmanager, Jar:netty-all, Jar:commons-beanutils, Jar:commons-collections, Jar:guava, Jar:artemis-native, Jar:spring-tx, Jar:aopalliance, Jar:spring-aop, Jar:spring-asm, Jar:spring-beans, Jar:spring-context, Jar:spring-expression, Jar:spring-core, Jar:commons-logging] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2659) narayana-osgi-jta build bundle warings

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2659?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2659: ---------------------------- Issue Type: Bug (was: Task) > narayana-osgi-jta build bundle warings > -------------------------------------- > > Key: JBTM-2659 > URL: https://issues.jboss.org/browse/JBTM-2659 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > There are three warning when building the bundle. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2661) Unknown directive cardinality: in Require-Capability

by Amos Feng (JIRA)

Amos Feng created JBTM-2661: ------------------------------- Summary: Unknown directive cardinality: in Require-Capability Key: JBTM-2661 URL: https://issues.jboss.org/browse/JBTM-2661 Project: JBoss Transaction Manager Issue Type: Sub-task Reporter: Amos Feng Assignee: Amos Feng [WARNING] Bundle org.jboss.narayana.osgi:narayana-osgi-jta:bundle:5.3.3.Final-SNAPSHOT : Unknown directive cardinality: in Require-Capability, allowed directives are effective:,resolution:,filter:, and 'x-*'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2660) multiple jars provide the same package:javax/transaction

by Amos Feng (JIRA)

Amos Feng created JBTM-2660: ------------------------------- Summary: multiple jars provide the same package:javax/transaction Key: JBTM-2660 URL: https://issues.jboss.org/browse/JBTM-2660 Project: JBoss Transaction Manager Issue Type: Sub-task Reporter: Amos Feng Assignee: Amos Feng [WARNING] Bundle org.jboss.narayana.osgi:narayana-osgi-jta:bundle:5.3.3.Final-SNAPSHOT : Split package, multiple jars provide the same package:javax/transaction Use Import/Export Package directive -split-package:=(merge-first|merge-last|error|first) to get rid of this warning Package found in [Jar:jboss-transaction-api_1.2_spec, Jar:jboss-transaction-api_1.1_spec] Class path [Jar:., Jar:org.osgi.core, Jar:org.osgi.compendium, Jar:jbosgi-metadata, Jar:jboss-transaction-api_1.2_spec, Jar:jta, Jar:common, Jar:arjuna, Jar:jconsole, Jar:jboss-transaction-spi, Jar:jboss-connector-api_1.5_spec, Jar:jboss-transaction-api_1.1_spec, Jar:narayana-jts-integration, Jar:jboss-logging, Jar:artemis-journal, Jar:artemis-commons, Jar:jboss-logmanager, Jar:netty-all, Jar:commons-beanutils, Jar:commons-collections, Jar:guava, Jar:artemis-native, Jar:spring-tx, Jar:aopalliance, Jar:spring-aop, Jar:spring-asm, Jar:spring-beans, Jar:spring-context, Jar:spring-expression, Jar:spring-core, Jar:commons-logging] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2659) narayana-osgi-jta build bundle warings

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2659?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2659: ---------------------------- Fix Version/s: 5.next > narayana-osgi-jta build bundle warings > -------------------------------------- > > Key: JBTM-2659 > URL: https://issues.jboss.org/browse/JBTM-2659 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > There are three warning when building the bundle. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2659) narayana-osgi-jta build bundle warings

by Amos Feng (JIRA)

Amos Feng created JBTM-2659: ------------------------------- Summary: narayana-osgi-jta build bundle warings Key: JBTM-2659 URL: https://issues.jboss.org/browse/JBTM-2659 Project: JBoss Transaction Manager Issue Type: Task Reporter: Amos Feng Assignee: Amos Feng There are three warning when building the bundle. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2658) Implement JMS integration classes for MessageListener

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2658?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2658: ------------------------------------- Thanks Alexis, I look forward to reading more about your proposal and hopefully working with you to share it with the community. > Implement JMS integration classes for MessageListener > ----------------------------------------------------- > > Key: JBTM-2658 > URL: https://issues.jboss.org/browse/JBTM-2658 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.3.2.Final > Reporter: Alexis Hassler > Priority: Minor > > The new JMS integration classes are working fine with a Publisher or a simple Consumer, but not with MessageListener. It would be nice to be able to implement something like a MDB without JavaEE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2658) Implement JMS integration classes for MessageListener

by Alexis Hassler (JIRA)

[ https://issues.jboss.org/browse/JBTM-2658?page=com.atlassian.jira.plugin.... ] Alexis Hassler commented on JBTM-2658: -------------------------------------- Hi Tom, It's not related to Artemis at all but to the org.jboss.narayana.jta.jms package, and to this previous ticket : https://issues.jboss.org/browse/JBTM-2616 OK, I'll start a discussion on the forum. > Implement JMS integration classes for MessageListener > ----------------------------------------------------- > > Key: JBTM-2658 > URL: https://issues.jboss.org/browse/JBTM-2658 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.3.2.Final > Reporter: Alexis Hassler > Priority: Minor > > The new JMS integration classes are working fine with a Publisher or a simple Consumer, but not with MessageListener. It would be nice to be able to implement something like a MDB without JavaEE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2658) Implement JMS integration classes for MessageListener

by Alexis Hassler (JIRA)

[ https://issues.jboss.org/browse/JBTM-2658?page=com.atlassian.jira.plugin.... ] Alexis Hassler commented on JBTM-2658: -------------------------------------- I've already done some code to try it. I've added a MessageListenerProxy for that. It has an impact on the ConnectionProxy class because it has to instantiate a SessionProxy even if the transaction has not started yet. > Implement JMS integration classes for MessageListener > ----------------------------------------------------- > > Key: JBTM-2658 > URL: https://issues.jboss.org/browse/JBTM-2658 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.3.2.Final > Reporter: Alexis Hassler > Priority: Minor > > The new JMS integration classes are working fine with a Publisher or a simple Consumer, but not with MessageListener. It would be nice to be able to implement something like a MDB without JavaEE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 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 April 2016