August 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1) Deployment overlay feature does not work if a leading / is present on the overlay path

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFCORE-1: ---------------------------------------------- Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1129836|https://bugzilla.redhat.com/show_bug.cgi?id=1129836] from NEW to POST > Deployment overlay feature does not work if a leading / is present on the overlay path > -------------------------------------------------------------------------------------- > > Key: WFCORE-1 > URL: https://issues.jboss.org/browse/WFCORE-1 > Project: WildFly Core > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 1.0.0.Alpha1 > Reporter: Lyle Wang > Assignee: Stuart Douglas > Fix For: 1.0.0.Alpha2 > > Attachments: wmq.jmsra.rar > > > According to WFLY-1359[1], we should be able to add a jar for an existing deployment. > Testing against WildFly 8.1.0 Final, the deployment-overlay feature reports errors on adding a new .jar for a .rar resource adapter deployment. > [1] - https://issues.jboss.org/browse/WFLY-1359 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1) Deployment overlay feature does not work if a leading / is present on the overlay path

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFCORE-1: ---------------------------------------------- Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1110635|https://bugzilla.redhat.com/show_bug.cgi?id=1110635] from NEW to POST > Deployment overlay feature does not work if a leading / is present on the overlay path > -------------------------------------------------------------------------------------- > > Key: WFCORE-1 > URL: https://issues.jboss.org/browse/WFCORE-1 > Project: WildFly Core > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 1.0.0.Alpha1 > Reporter: Lyle Wang > Assignee: Stuart Douglas > Fix For: 1.0.0.Alpha2 > > Attachments: wmq.jmsra.rar > > > According to WFLY-1359[1], we should be able to add a jar for an existing deployment. > Testing against WildFly 8.1.0 Final, the deployment-overlay feature reports errors on adding a new .jar for a .rar resource adapter deployment. > [1] - https://issues.jboss.org/browse/WFLY-1359 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-43) Clean up Base64

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-43?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-43: -------------------------------- Description: The Base64 implementation has been split out of PasswordUtils some additional steps are needed to finish cleaning it up: - - Look at switching to input and output streams instead of the custom iterators it is using. - Consider the ByteStringBuilder from SASL - As potentially more visible ensure clearer method names. - Ensure adequate javadoc and cross referencing of standards supported. e.g. If we implement an RFC ensure the number is referenced. - Testing of each variant - Consider optional support, e.g. decoding a padded String - Go beyond testing we can decode what we encode and ensure pre-encoded values can be handled adequately. Any other clean up here that seems relevant. was: The Base64 implementation has been split out of PasswordUtils some additional steps are needed to finish cleaning it up: - - Look at switching to input and output streams instead of the custom iterators it is using. - Consider the ByteStringBuilder from SASL - As potentially more visible ensure clearer method names. - Ensure adequate javadoc and cross referencing of standards supported. - Testing of each variant - Consider optional support, e.g. decoding a padded String - Go beyond testing we can decode what we encode and ensure pre-encoded values can be handled adequately. Any other clean up here that seems relevant. > Clean up Base64 > --------------- > > Key: ELY-43 > URL: https://issues.jboss.org/browse/ELY-43 > Project: WildFly Elytron > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Utils > Reporter: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > The Base64 implementation has been split out of PasswordUtils some additional steps are needed to finish cleaning it up: - > - Look at switching to input and output streams instead of the custom iterators it is using. > - Consider the ByteStringBuilder from SASL > - As potentially more visible ensure clearer method names. > - Ensure adequate javadoc and cross referencing of standards supported. > e.g. If we implement an RFC ensure the number is referenced. > - Testing of each variant > - Consider optional support, e.g. decoding a padded String > - Go beyond testing we can decode what we encode and ensure pre-encoded values can be handled adequately. > Any other clean up here that seems relevant. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-43) Clean up Base64

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-43: ----------------------------------- Summary: Clean up Base64 Key: ELY-43 URL: https://issues.jboss.org/browse/ELY-43 Project: WildFly Elytron Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Utils Reporter: Darran Lofthouse Fix For: 1.0.0.Beta1 The Base64 implementation has been split out of PasswordUtils some additional steps are needed to finish cleaning it up: - - Look at switching to input and output streams instead of the custom iterators it is using. - Consider the ByteStringBuilder from SASL - As potentially more visible ensure clearer method names. - Ensure adequate javadoc and cross referencing of standards supported. - Testing of each variant - Consider optional support, e.g. decoding a padded String - Go beyond testing we can decode what we encode and ensure pre-encoded values can be handled adequately. Any other clean up here that seems relevant. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3731) org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor should not register a Synchronization if the transaction was rolled back

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-3731?page=com.atlassian.jira.plugin.... ] Scott Marlow reassigned WFLY-3731: ---------------------------------- Assignee: Scott Marlow (was: David Lloyd) > org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor should not register a Synchronization if the transaction was rolled back > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-3731 > URL: https://issues.jboss.org/browse/WFLY-3731 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: JBoss AS7 7.2.0.Final, 8.0.0.Final, 8.1.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.2.0.CR1, 9.0.0.CR1 > > > http://fpaste.org/125252/ shows what happens when the transaction has already been rolled back (). > {quote} > WFLYEJB0458: Failure in caller transaction.: java.lang.IllegalStateException: No transaction is running > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple.getTransactionImple(TransactionSynchronizationRegistryImple.java:228) > {quote} > Test case is available via https://github.com/scottmarlow/wildfly/tree/transactiontimeout_clientut -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3731) org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor should not register a Synchronization if the transaction was rolled back

by Scott Marlow (JIRA)

Scott Marlow created WFLY-3731: ---------------------------------- Summary: org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor should not register a Synchronization if the transaction was rolled back Key: WFLY-3731 URL: https://issues.jboss.org/browse/WFLY-3731 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 8.1.0.Final, 8.0.0.Final, JBoss AS7 7.2.0.Final Reporter: Scott Marlow Assignee: David Lloyd Fix For: 8.2.0.CR1, 9.0.0.CR1 http://fpaste.org/125252/ shows what happens when the transaction has already been rolled back (). {quote} WFLYEJB0458: Failure in caller transaction.: java.lang.IllegalStateException: No transaction is running at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple.getTransactionImple(TransactionSynchronizationRegistryImple.java:228) {quote} Test case is available via https://github.com/scottmarlow/wildfly/tree/transactiontimeout_clientut -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3730) JPA container should check for STATUS_ROLLEDBACK

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-3730?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-3730: ------------------------------- Description: See ISE thrown in http://fpaste.org/125260. Also see test case on https://github.com/scottmarlow/wildfly/tree/transactiontimeout_clientut A related concern is shown in http://fpaste.org/125252 which comes from org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation was: See ISE thrown in http://fpaste.org/125252/ (note that status==4 is STATUS_ROLLEDBACK and status==0 is STATUS_ACTIVE) Also see test case on https://github.com/scottmarlow/wildfly/tree/transactiontimeout_clientut > JPA container should check for STATUS_ROLLEDBACK > ------------------------------------------------ > > Key: WFLY-3730 > URL: https://issues.jboss.org/browse/WFLY-3730 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Affects Versions: JBoss AS7 7.2.0.Final, 8.0.0.Final, 8.1.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.2.0.CR1, 9.0.0.CR1 > > > See ISE thrown in http://fpaste.org/125260. > Also see test case on https://github.com/scottmarlow/wildfly/tree/transactiontimeout_clientut > A related concern is shown in http://fpaste.org/125252 which comes from org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3730) JPA container should check for STATUS_ROLLEDBACK

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-3730?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-3730: ------------------------------- Description: See ISE thrown in http://fpaste.org/125252/ (note that status==4 is STATUS_ROLLEDBACK and status==0 is STATUS_ACTIVE) Also see test case on https://github.com/scottmarlow/wildfly/tree/transactiontimeout_clientut was: See ISE thrown in http://fpaste.org/125229/14079353 (note that status=4 is STATUS_ROLLEDBACK) Also see test case on https://github.com/scottmarlow/wildfly/tree/transactiontimeout_clientut > JPA container should check for STATUS_ROLLEDBACK > ------------------------------------------------ > > Key: WFLY-3730 > URL: https://issues.jboss.org/browse/WFLY-3730 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Affects Versions: JBoss AS7 7.2.0.Final, 8.0.0.Final, 8.1.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.2.0.CR1, 9.0.0.CR1 > > > See ISE thrown in http://fpaste.org/125252/ (note that status==4 is STATUS_ROLLEDBACK and status==0 is STATUS_ACTIVE) > Also see test case on https://github.com/scottmarlow/wildfly/tree/transactiontimeout_clientut -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3336) Injection of SpringBean into EJB doesn't work if Spring is installed as static module

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3336?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed WFLY-3336. ----------------------------- Resolution: Rejected > Injection of SpringBean into EJB doesn't work if Spring is installed as static module > ------------------------------------------------------------------------------------- > > Key: WFLY-3336 > URL: https://issues.jboss.org/browse/WFLY-3336 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.1.0.CR1 > Reporter: Tomas Repel > Assignee: David Lloyd > > If you inject SpringBean into EJB using SpringBeanAutowiringInterceptor and the Spring core jars are available as static module, the injection doesn't work. > Reproducer: > https://github.com/trepel/WFLY-3336-Reproducer -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3336) Injection of SpringBean into EJB doesn't work if Spring is installed as static module

by Tomas Repel (JIRA)

[ https://issues.jboss.org/browse/WFLY-3336?page=com.atlassian.jira.plugin.... ] Tomas Repel edited comment on WFLY-3336 at 8/13/14 9:24 AM: ------------------------------------------------------------ Thank you [~swd847], adding annotations="true" to jboss-deployment-structure.xml and creating jandex.idx file for spring-context.jar works. The SpringBeanAutowiringSupport doesn't have to be used. This issue can be closed. was (Author: trepel): Thank you [~swd847], adding annotations="true" to jboss-deployment-structure.xml and creating jandex.idx file for spring-context.jar works. The SpringBeanAutowiringSupport doesn't have to be used. You may close this issue. > Injection of SpringBean into EJB doesn't work if Spring is installed as static module > ------------------------------------------------------------------------------------- > > Key: WFLY-3336 > URL: https://issues.jboss.org/browse/WFLY-3336 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.1.0.CR1 > Reporter: Tomas Repel > Assignee: David Lloyd > > If you inject SpringBean into EJB using SpringBeanAutowiringInterceptor and the Spring core jars are available as static module, the injection doesn't work. > Reproducer: > https://github.com/trepel/WFLY-3336-Reproducer -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2014