December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6164) IE9: Pages bar doesn't have gradient background

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6164?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-6164: ----------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.CR1) > IE9: Pages bar doesn't have gradient background > ----------------------------------------------- > > Key: AS7-6164 > URL: https://issues.jboss.org/browse/AS7-6164 > Project: Application Server 7 > Issue Type: Sub-task > Components: Console > Reporter: Heiko Braun > Fix For: 7.3.0.Alpha1 > > -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5432) TransactionRolledbackLocalException doesn't reference the originating runtime-exception

by Barnabas Bodnar (JIRA)

[ https://issues.jboss.org/browse/AS7-5432?page=com.atlassian.jira.plugin.s... ] Barnabas Bodnar commented on AS7-5432: -------------------------------------- New pull requests: https://github.com/jbossas/jboss-as/pull/3719, https://github.com/jbossas/jboss-as/pull/3718 > TransactionRolledbackLocalException doesn't reference the originating runtime-exception > --------------------------------------------------------------------------------------- > > Key: AS7-5432 > URL: https://issues.jboss.org/browse/AS7-5432 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP) > Reporter: Barnabas Bodnar > Assignee: jaikiran pai > Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) > > > If a runtime-exception thrown by an EJB v2.x application leads to javax.ejb.TransactionRolledbackLocalException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(...)), the TransactionRolledbackLocalException doesn't reference the originating exception (either as getCause() or as getCausedByException()). > The originating exception gets in org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE lost: the javax.ejb.EJBTransactionRolledbackException catched here does still contain it, it will, however, not be propagated to the javax.ejb.TransactionRolledbackLocalException created here. > This behavior also deviates from that in the case of a locally started transaction: the wrapping javax.ejb.EJBException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(...)) is thrown unchanged to the caller (s. org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE) and it references the originating exception both as getCause() and as getCausedByException(). -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-952) JBossWrapper only checks directly wrapped objects in unwrap/isWrapperFor

by James Livingston (JIRA)

[ https://issues.jboss.org/browse/JBJCA-952?page=com.atlassian.jira.plugin.... ] James Livingston updated JBJCA-952: ----------------------------------- Description: The JavaDoc for the JDBC Wrapper class (http://docs.oracle.com/javase/6/docs/api/java/sql/Wrapper.html) says unwrap() should 1) return itself or a proxy when the reicever implements the interface 2) return the wrapped object or a proxy when the wrapped object implements the interface 3) call the wrapped object's unwrap() method if the receiver is a wrapper 4) other throw a SQL exception JBossWrapper only does 2 and 4. This means that is you have a WrappedConnectionJDK6 which wraps another wrapper which wraps OracleConnection, there you cannot get to the OracleConnection. was: The JavaDoc for the JDBC Wrapper class (http://docs.oracle.com/javase/6/docs/api/java/sql/Wrapper.html) says unwrap() should 1) return itself or a proxy when the reicever implements the interface 2) return the wrapped object or a proxy when the wrapped object implements the interface 3) call the wrapp object's unwrap() method if the receiver is a wrapper 4) other throw a SQL exception JBossWrapper only does 2 and 4. This means that is you have a WrappedConnectionJDK6 which wraps another wrapper which wraps OracleConnection, there you cannot get to the OracleConnection. > JBossWrapper only checks directly wrapped objects in unwrap/isWrapperFor > ------------------------------------------------------------------------ > > Key: JBJCA-952 > URL: https://issues.jboss.org/browse/JBJCA-952 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Reporter: James Livingston > Assignee: Jesper Pedersen > > The JavaDoc for the JDBC Wrapper class (http://docs.oracle.com/javase/6/docs/api/java/sql/Wrapper.html) says unwrap() should > 1) return itself or a proxy when the reicever implements the interface > 2) return the wrapped object or a proxy when the wrapped object implements the interface > 3) call the wrapped object's unwrap() method if the receiver is a wrapper > 4) other throw a SQL exception > JBossWrapper only does 2 and 4. > This means that is you have a WrappedConnectionJDK6 which wraps another wrapper which wraps OracleConnection, there you cannot get to the OracleConnection. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-952) JBossWrapper only checks directly wrapped objects in unwrap/isWrapperFor

by James Livingston (JIRA)

James Livingston created JBJCA-952: -------------------------------------- Summary: JBossWrapper only checks directly wrapped objects in unwrap/isWrapperFor Key: JBJCA-952 URL: https://issues.jboss.org/browse/JBJCA-952 Project: IronJacamar Issue Type: Bug Components: JDBC Reporter: James Livingston Assignee: Jesper Pedersen The JavaDoc for the JDBC Wrapper class (http://docs.oracle.com/javase/6/docs/api/java/sql/Wrapper.html) says unwrap() should 1) return itself or a proxy when the reicever implements the interface 2) return the wrapped object or a proxy when the wrapped object implements the interface 3) call the wrapp object's unwrap() method if the receiver is a wrapper 4) other throw a SQL exception JBossWrapper only does 2 and 4. This means that is you have a WrappedConnectionJDK6 which wraps another wrapper which wraps OracleConnection, there you cannot get to the OracleConnection. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6068) jar file system is broken again (regression)

by Alvin Thompson (JIRA)

[ https://issues.jboss.org/browse/AS7-6068?page=com.atlassian.jira.plugin.s... ] Alvin Thompson commented on AS7-6068: ------------------------------------- The enhancement which implemented the "use-physical-code-source" attribute (AS7-308) specifically states that it does not fix this issue, but I'll give it a try sometime when I have some free time. > jar file system is broken again (regression) > -------------------------------------------- > > Key: AS7-6068 > URL: https://issues.jboss.org/browse/AS7-6068 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.1.Final > Reporter: Alvin Thompson > Assignee: JBoss SET > Priority: Critical > > Similar to issue JBAS-7882, you cannot bundle a security provider in a WAR/EAR, because JBOSS's jar file system becomes confused when there are JARs nested in other JARs/WARs/EARs, which is pretty much always. > This was supposedly fixed in previous versions, but it's back in 7. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6225) MessagingSubsystemParser swallows exceptions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6225?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6225: ---------------------------------- Attachment: AS7-6225.patch > MessagingSubsystemParser swallows exceptions > -------------------------------------------- > > Key: AS7-6225 > URL: https://issues.jboss.org/browse/AS7-6225 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, JMS > Affects Versions: 7.1.3.Final (EAP) > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Attachments: AS7-6225.patch > > > In numerous places, MessagingSubsystemParser calls ParseUtils.missingRequired but does not throw the returned exception. > I'll attach a patch showing all the places where Intellij reported this. I'd just send a pull request, but when I run with this patch, the messaging module testsuite has failures and I don't have time today to investigate. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6225) MessagingSubsystemParser swallows exceptions

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6225: ------------------------------------- Summary: MessagingSubsystemParser swallows exceptions Key: AS7-6225 URL: https://issues.jboss.org/browse/AS7-6225 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JMS Affects Versions: 7.1.3.Final (EAP) Reporter: Brian Stansberry Assignee: Jeff Mesnil In numerous places, MessagingSubsystemParser calls ParseUtils.missingRequired but does not throw the returned exception. I'll attach a patch showing all the places where Intellij reported this. I'd just send a pull request, but when I run with this patch, the messaging module testsuite has failures and I don't have time today to investigate. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6068) jar file system is broken again (regression)

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6068?page=com.atlassian.jira.plugin.s... ] Stuart Douglas edited comment on AS7-6068 at 12/19/12 8:38 PM: --------------------------------------------------------------- There is a flag in jboss-deployment-structure.xml that allows you to change the code base from a vfs:// URL to the physical URL, via the use-physical-code-source attribute. For bouncycastle bundled in a war the code would look something like: {code} <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1"> <deployment> <resources> <resource-root path="WEB-INF/lib/bouncycastle.jar" use-physical-code-source="true"/> </resources> </deployment> </jboss-deployment-structure> {code} Does this resolve the problem? was (Author: swd847): There is a flag in jboss-deployment-structure.xml that allows you to change the code base from a vfs:// URL to the physical URL, via the use-physical-code-source attribute. For bouncycastle bundled in a war the code would look something like: [code] <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1"> <deployment> <resources> <resource-root path="WEB-INF/lib/bouncycastle.jar" use-physical-code-source="true"/> </resources> </deployment> </jboss-deployment-structure> [code] Does this resolve the problem? > jar file system is broken again (regression) > -------------------------------------------- > > Key: AS7-6068 > URL: https://issues.jboss.org/browse/AS7-6068 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.1.Final > Reporter: Alvin Thompson > Assignee: JBoss SET > Priority: Critical > > Similar to issue JBAS-7882, you cannot bundle a security provider in a WAR/EAR, because JBOSS's jar file system becomes confused when there are JARs nested in other JARs/WARs/EARs, which is pretty much always. > This was supposedly fixed in previous versions, but it's back in 7. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6068) jar file system is broken again (regression)

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6068?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on AS7-6068: ------------------------------------- There is a flag in jboss-deployment-structure.xml that allows you to change the code base from a vfs:// URL to the physical URL, via the use-physical-code-source attribute. For bouncycastle bundled in a war the code would look something like: [code] <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1"> <deployment> <resources> <resource-root path="WEB-INF/lib/bouncycastle.jar" use-physical-code-source="true"/> </resources> </deployment> </jboss-deployment-structure> [code] Does this resolve the problem? > jar file system is broken again (regression) > -------------------------------------------- > > Key: AS7-6068 > URL: https://issues.jboss.org/browse/AS7-6068 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.1.Final > Reporter: Alvin Thompson > Assignee: JBoss SET > Priority: Critical > > Similar to issue JBAS-7882, you cannot bundle a security provider in a WAR/EAR, because JBOSS's jar file system becomes confused when there are JARs nested in other JARs/WARs/EARs, which is pretty much always. > This was supposedly fixed in previous versions, but it's back in 7. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-5935) Add support for cross-site replication of Infinispan caches via RELAY2

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/AS7-5935?page=com.atlassian.jira.plugin.s... ] Paul Ferraro updated AS7-5935: ------------------------------ Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.CR1) > Add support for cross-site replication of Infinispan caches via RELAY2 > ---------------------------------------------------------------------- > > Key: AS7-5935 > URL: https://issues.jboss.org/browse/AS7-5935 > Project: Application Server 7 > Issue Type: Feature Request > Components: Clustering > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 7.3.0.Alpha1 > > > Proposed AS7 configuration of $SUBJECT was discussed in Palma clustering meeting. > https://community.jboss.org/wiki/DesignForCrossSiteReplication > https://docs.jboss.org/author/display/ISPN/Cross+site+replication -- 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

13 years, 4 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 December 2012