September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1774) STM artifactId name potentially ambiguous?

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1774?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1774: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done 5844f1858ee1c2a40447c97e52fd78702397554f > STM artifactId name potentially ambiguous? > ------------------------------------------ > > Key: JBTM-1774 > URL: https://issues.jboss.org/browse/JBTM-1774 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System, STM > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.0.0.M5 > > > Most modules that a user is expected to build and use (e.g. XTS, ArjunaCore, the JTA/JTS uber jars) use an aggregate nominative part of the group plus a module-centric name to differentiate them. > The problem such that it is, can be seen cleanest in JBTM-1769 (https://github.com/jbosstm/narayana/commit/8ec2ab2375e3efb67489e7702f20c4...). Here the user is suggested to build :core to build STM which is ambiguous in context with the rest of the project in particular ArjunaCore. > Can the artifactId be changed to stm-core? or just stm? -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1774) STM artifactId name potentially ambiguous?

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1774?page=com.atlassian.jira.plugin.... ] Tom Jenkinson edited comment on JBTM-1774 at 9/30/13 5:02 AM: -------------------------------------------------------------- Resolved in: https://github.com/jbosstm/narayana/commit/5844f1858ee1c2a40447c97e52fd78... was (Author: tomjenkinson): 5844f1858ee1c2a40447c97e52fd78702397554f > STM artifactId name potentially ambiguous? > ------------------------------------------ > > Key: JBTM-1774 > URL: https://issues.jboss.org/browse/JBTM-1774 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System, STM > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.0.0.M5 > > > Most modules that a user is expected to build and use (e.g. XTS, ArjunaCore, the JTA/JTS uber jars) use an aggregate nominative part of the group plus a module-centric name to differentiate them. > The problem such that it is, can be seen cleanest in JBTM-1769 (https://github.com/jbosstm/narayana/commit/8ec2ab2375e3efb67489e7702f20c4...). Here the user is suggested to build :core to build STM which is ambiguous in context with the rest of the project in particular ArjunaCore. > Can the artifactId be changed to stm-core? or just stm? -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1940) Server-side XTS handlers not added if @WebService#portName is missing

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1940?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1940: -------------------------------- Priority: Minor (was: Major) > Server-side XTS handlers not added if @WebService#portName is missing > --------------------------------------------------------------------- > > Key: JBTM-1940 > URL: https://issues.jboss.org/browse/JBTM-1940 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M5 > > > To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails with: > {code} > "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" > {code} > The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1940) Server-side XTS handlers not added if @WebService#portName is missing

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1940?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1940: -------------------------------- Assignee: Gytis Trikleris (was: Paul Robinson) > Server-side XTS handlers not added if @WebService#portName is missing > --------------------------------------------------------------------- > > Key: JBTM-1940 > URL: https://issues.jboss.org/browse/JBTM-1940 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M5 > > > To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails with: > {code} > "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" > {code} > The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1940) Server-side XTS handlers not added if @WebService#portName is missing

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1940?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1940: -------------------------------- Comment: was deleted (was: Added test in https://github.com/jbosstm/narayana/pull/468) > Server-side XTS handlers not added if @WebService#portName is missing > --------------------------------------------------------------------- > > Key: JBTM-1940 > URL: https://issues.jboss.org/browse/JBTM-1940 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails with: > {code} > "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" > {code} > The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1940) Server-side XTS handlers not added if @WebService#portName is missing

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1940?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1940: -------------------------------- Comment: was deleted (was: This doesn't seem to be happening anymore. Not sure if it was fixed by one of Gytis' recent commits. We can re-open if we see it again.) > Server-side XTS handlers not added if @WebService#portName is missing > --------------------------------------------------------------------- > > Key: JBTM-1940 > URL: https://issues.jboss.org/browse/JBTM-1940 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails with: > {code} > "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" > {code} > The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1940) Server-side XTS handlers not added if @WebService#portName is missing

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1940?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1940: -------------------------------- Description: To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails with: {code} "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" {code} The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. was: To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails due to "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. > Server-side XTS handlers not added if @WebService#portName is missing > --------------------------------------------------------------------- > > Key: JBTM-1940 > URL: https://issues.jboss.org/browse/JBTM-1940 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails with: > {code} > "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" > {code} > The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1940) Server-side XTS handlers not added if @WebService#portName is missing

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1940?page=com.atlassian.jira.plugin.... ] Paul Robinson reopened JBTM-1940: --------------------------------- > Server-side XTS handlers not added if @WebService#portName is missing > --------------------------------------------------------------------- > > Key: JBTM-1940 > URL: https://issues.jboss.org/browse/JBTM-1940 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails with: > {code} > "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" > {code} > The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1940) Server-side XTS handlers not added if @WebService#portName is missing

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1940?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1940: -------------------------------- Description: To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails due to "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. was:Remove portName or targetNameSpace attributes from one of the test services in the TXFramework suite. You will see that deployment fail > Server-side XTS handlers not added if @WebService#portName is missing > --------------------------------------------------------------------- > > Key: JBTM-1940 > URL: https://issues.jboss.org/browse/JBTM-1940 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails due to "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" > The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1940) Server-side XTS handlers not added if @WebService#portName is missing

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1940?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1940: -------------------------------- Description: Remove portName or targetNameSpace attributes from one of the test services in the TXFramework suite. You will see that deployment fail (was: Try removing portName attribute from one of the test services in the TXFramework suite. You will see that deployment fails.) > Server-side XTS handlers not added if @WebService#portName is missing > --------------------------------------------------------------------- > > Key: JBTM-1940 > URL: https://issues.jboss.org/browse/JBTM-1940 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > Remove portName or targetNameSpace attributes from one of the test services in the TXFramework suite. You will see that deployment fail -- 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

10 years, 8 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 September 2013