July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBLOGGING-59) Report which provider was selected in LoggingProviders

by Dan Allen (JIRA)

Report which provider was selected in LoggingProviders ------------------------------------------------------ Key: JBLOGGING-59 URL: https://issues.jboss.org/browse/JBLOGGING-59 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Dan Allen Assignee: David Lloyd Priority: Minor JBoss Logging should log a message to identify which logging provider it selected. This report ack would be helpful for developers when they are getting the logging system and classpath setup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-879) missing resource for description infinispan.container.default-cache

by Michal Linhard (JIRA)

missing resource for description infinispan.container.default-cache ------------------------------------------------------------------- Key: AS7-879 URL: https://issues.jboss.org/browse/AS7-879 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.0.Beta3 Reporter: Michal Linhard Priority: Minor LocalDescriptions.properties is missing description for infinispan.container.default-cache when you run ./standalone.sh -server-config clustering-standalone.xml and in jboss-admin do: /subsystem=infinispan/cache-container=web:read-operation-description(name=add) you get java.util.MissingResourceException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBLOGGING-48) @Message should be declared @Documented

by Pete Muir (JIRA)

@Message should be declared @Documented --------------------------------------- Key: JBLOGGING-48 URL: https://jira.jboss.org/browse/JBLOGGING-48 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Pete Muir Assignee: David Lloyd This means the annotation and it's value will appear in the javadoc - obiviously useful for someone exploring the javadoc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
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: (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

[JBoss JIRA] Created: (JBMESSAGING-1884) ClientTransaction alters wire format

by Kevin Conner (JIRA)

ClientTransaction alters wire format ------------------------------------ Key: JBMESSAGING-1884 URL: https://issues.jboss.org/browse/JBMESSAGING-1884 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.8.SP1 Reporter: Kevin Conner Assignee: Justin Bertram JBMESSAGING-1786 changed the format of ClientTransaction to include a recovery flag, unfortunately this breaks the wire protocol with older clients. The versions containing this problem are - 1.4.0 SP3 CP11, CP12, CP13 - 1.4.6 GA SP1 - 1.4.7 GA - 1.4.8 GA - 1.4.8 SP1 Attached to this issue is a diff, made against the current Branch_1_4, which addresses the issue. Older clients should still be able to talk to the newer server but will not be able to take advantage of the fix for JBMESSAGING-1786. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (AS7-967) Upgrade Hibernate Validator to 4.2.0.beta2

by Juergen Zimmermann (JIRA)

Upgrade Hibernate Validator to 4.2.0.beta2 ------------------------------------------ Key: AS7-967 URL: https://issues.jboss.org/browse/AS7-967 Project: Application Server 7 Issue Type: Feature Request Components: Modules Affects Versions: 7.0.0.Beta3 Reporter: Juergen Zimmermann HV 4.2 provides the pretty effective method failFast(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (AS7-1292) Cleanup xsd names for server config

by Wolfgang Knauf (JIRA)

Cleanup xsd names for server config ----------------------------------- Key: AS7-1292 URL: https://issues.jboss.org/browse/AS7-1292 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.0.0.Final Reporter: Wolfgang Knauf Assignee: Jason Greene Priority: Minor Fix For: 7.0.1.Final >From a conversation on the dev mailing list beetween me and Brian: >>> [Wolfgang] If my understanding is correct, the naming of the server config xsd >>> files is confusing, because a "jboss-7_0.xsd" will be something >>> different than "jboss_6_0.xsd". >>> >> >> [Brian] Yep. Kind of a big DOH!! moment. Looking at the jboss-metadata project >> where these deployment descriptor dtds/xsds come from, I see no >> jboss_6_0.xsd, just jboss_6_0.dtd. And no 7_0 xsd or dtd. But still, >> it's a naming conflict that's bound to bite us unless fixed. >> >> I recommend these server config xds all be renamed to >> jboss-as-XXX_1_0.xsd. They all have an xmlns of >> urn:jboss:domain:XXX:1.0, not 7.0, which IMO is fine since they may get >> revved independently of community AS releases. >> > > > [Wolfgang} Is there something more I should do - e.g. filing a JIRA issue? Or will > it be fixed by "miracle" ;-) or has someone this already on his todo list ? > [Brian] If you could file a JIRA and assign it to me, Fix Version 7.0.1.Final, I'd appreciate it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

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