August 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBJCA-647) JBossTS 4.15.3.Final

by Jesper Pedersen (JIRA)

JBossTS 4.15.3.Final -------------------- Key: JBJCA-647 URL: https://issues.jboss.org/browse/JBJCA-647 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.2.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-646) JBossTS 4.15.3.Final

by Jesper Pedersen (JIRA)

JBossTS 4.15.3.Final -------------------- Key: JBJCA-646 URL: https://issues.jboss.org/browse/JBJCA-646 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-645) PicketBox 4.0.1

by Jesper Pedersen (JIRA)

PicketBox 4.0.1 --------------- Key: JBJCA-645 URL: https://issues.jboss.org/browse/JBJCA-645 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.2.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-644) Track component updates

by Jesper Pedersen (JIRA)

Track component updates ----------------------- Key: JBJCA-644 URL: https://issues.jboss.org/browse/JBJCA-644 Project: IronJacamar Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.2.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-620) PicketBox 4.0.0.CR1

by Jesper Pedersen (JIRA)

PicketBox 4.0.0.CR1 ------------------- Key: JBJCA-620 URL: https://issues.jboss.org/browse/JBJCA-620 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-642) Use metadata from JDBC connection

by Jesper Pedersen (JIRA)

Use metadata from JDBC connection --------------------------------- Key: JBJCA-642 URL: https://issues.jboss.org/browse/JBJCA-642 Project: IronJacamar Issue Type: Task Components: JDBC Affects Versions: 1.0.1.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Use the metadata from the JDBC connection (getDatabaseProductName() and getDatabaseProductVersion()) for the ManagedConnectionMetaData fields. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-641) Too eager configuration of resource adapter components

by Jesper Pedersen (JIRA)

Too eager configuration of resource adapter components ------------------------------------------------------ Key: JBJCA-641 URL: https://issues.jboss.org/browse/JBJCA-641 Project: IronJacamar Issue Type: Bug Components: Deployer Affects Versions: 1.0.1.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Blocker Fix For: 1.0.2.Final, 1.1.0.Alpha1 If a resource adapter contains multiple components of the same type - like ManagedConnectionFactory'ies - the deployer will try and configure components that there is no configuration for in the <resource-adapter> element. We should ignore all components that there is no configuration for instead. The activator should fail in this scenario. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBLOGGING-51) jboss-logging-spi in OSGI

by luca stancapiano (JIRA)

jboss-logging-spi in OSGI ------------------------- Key: JBLOGGING-51 URL: https://issues.jboss.org/browse/JBLOGGING-51 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: felix Reporter: luca stancapiano Assignee: David Lloyd I'ld like jboss-logging-spi be a OSGI bundle so it can be installed in all OSGI repositories. Actually I tested it with felix. To do it it is enough add this plugin configuration in the pom.xml:  <plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <version>2.1.0</version> <extensions>true</extensions> <configuration> <instructions> <Bundle-DocURL>http://community.jboss.org/wiki/JBossCommonProject</Bundle-DocURL> <Export-Package> ${project.groupId}.*;version=${project.version};-split-package:=error </Export-Package> </instructions> </configuration> </plugin> and modify the <packaging> row from 'jar' to 'bundle' so: <packaging>bundle</packaging> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1021) infinispan subsystem config schema - isolation attribute allows unsupported isolation modes

by Michal Linhard (JIRA)

infinispan subsystem config schema - isolation attribute allows unsupported isolation modes ------------------------------------------------------------------------------------------- Key: AS7-1021 URL: https://issues.jboss.org/browse/AS7-1021 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.0.Beta3 Reporter: Michal Linhard the isolation enumeration schema supports definiton of these additional transaction isolation modes SERIALIZABLE READ_UNCOMMITTED from what I know there's no plan to support these isolation modes in Infinispan. Shouldn't we disable them in schema to avoid confusion ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8836) org.jboss.test.web.test.RootContextUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.web.test.RootContextUnitTestCase ----------------------------------------------- Key: JBAS-8836 URL: https://issues.jboss.org/browse/JBAS-8836 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 6.0.1 org.jboss.test.web.test.RootContextUnitTestCase.testRootContextEAR org.jboss.test.web.test.RootContextUnitTestCase.testRootContextWAR 2011-01-24 05:41:05,869 DEBUG [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (RMI TCP Connection(606)-10.16.93.209) Linking security/securityMgr to JNDI name: java:/jaas/jboss-web-policy 2011-01-24 05:41:05,869 ERROR [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (RMI TCP Connection(606)-10.16.93.209) ENC setup failed: javax.naming.NameAlreadyBoundException: securityMgr at org.jnp.server.NamingServer.bind(NamingServer.java:209) [:5.0.5.Final] at org.jnp.server.NamingServer.bind(NamingServer.java:167) [:5.0.5.Final] at org.jnp.server.NamingServer.bind(NamingServer.java:167) [:5.0.5.Final] at org.jnp.interfaces.NamingContext.bind(NamingContext.java:652) [:5.0.5.Final] at org.jnp.interfaces.NamingContext.bind(NamingContext.java:613) [:5.0.5.Final] at org.jboss.util.naming.Util.bind(Util.java:105) [jboss-common-core.jar:2.2.17.GA] at org.jboss.util.naming.Util.bind(Util.java:91) [jboss-common-core.jar:2.2.17.GA] at org.jboss.web.deployers.AbstractWarDeployment.linkSecurityDomain(AbstractWarDeployment.java:836) [:6.0.1-SNAPSHOT] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.access$200(TomcatDeployment.java:85) [:6.0.1-SNAPSHOT] at org.jboss.web.tomcat.service.deployers.TomcatDeployment$EncListener.lifecycleEvent(TomcatDeployment.java:437) [:6.0.1-SNAPSHOT] at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [:] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3823) [:] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.1-SNAPSHOT] at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.1-SNAPSHOT] at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.1-SNAPSHOT] at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.1-SNAPSHOT] at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.1-SNAPSHOT] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
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 2011