July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1247) Messaging Configuration not support all setings defined in jboss-messaging.xsd schema file.

by Tomaz Zupan (JIRA)

Messaging Configuration not support all setings defined in jboss-messaging.xsd schema file. ------------------------------------------------------------------------------------------- Key: AS7-1247 URL: https://issues.jboss.org/browse/AS7-1247 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.0.0.CR1 Environment: Windows 7 x64 Java 1.6.25 x64 JBoss 7.0.0 CR1 - standalone-preview Reporter: Tomaz Zupan Assignee: Clebert Suconic Only settings included in standalone-preview.xml configuration file are supported. If some other settings from jboss-messaging.xsd schema file are included, org.jboss.as.controller.persistence.ConfigurationPersistenceException exception is thrown while the JBoss server is starting. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

5
10
0 / 0

[JBoss JIRA] Created: (AS7-1258) required xa-data-source-properties is missing from add operation description

by Alexey Loubyansky (JIRA)

required xa-data-source-properties is missing from add operation description ---------------------------------------------------------------------------- Key: AS7-1258 URL: https://issues.jboss.org/browse/AS7-1258 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.0.0.CR1 Reporter: Alexey Loubyansky Assignee: Stefano Maestri xa-data-source-properties property is required by add operation but is missing from the operation description. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1164) add jdbc-driver : documentation incomplete or misleading

by Heiko Rupp (JIRA)

add jdbc-driver : documentation incomplete or misleading -------------------------------------------------------- Key: AS7-1164 URL: https://issues.jboss.org/browse/AS7-1164 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.CR1 Reporter: Heiko Rupp I want to add a jdbc driver to a profile. The driver has been uploaded to /deployment [domain@localhost:9999 subsystem=datasources] pwd /profile=default/subsystem=datasources [domain@localhost:9999 subsystem=datasources] ./jdbc-driver=postgres9:add(driver-name=postgres9,deployment-name=postgresql-9.0-801.jdbc4.jar,driver-class-name=org.postgresql.Driver) { "outcome" => "failed", "failure-description" => {"domain-failure-description" => "Operation handler failed: java.util.NoSuchElementException: No child 'driver-module-name' exists"}, "rolled-back" => true } Documentation says: [domain@localhost:9999 jdbc-driver=h2] :read-operation-description(name=add) { "outcome" => "success", "result" => { "operation-name" => "add", "description" => "Adds a new JDBC driver service", "attributes" => { "driver-name" => { "description" => "The symbolic name of this driver used to reference it in the register", "type" => STRING, "required" => true }, "deployment-name" => { "description" => "The name of the deployment unit from which the driver was loaded, if it was loaded from a deployment", "type" => STRING }, "driver-module-name" => { "description" => "The name of the module from which the driver was loaded, if it was loaded from the module path", "type" => STRING }, "module-slot" => { "description" => "The slot of the module from which the driver was loaded, if it was loaded from the module path", "type" => STRING }, "driver-class-name" => { "description" => "The fully qualified class name of the driver's implementation of java.sql.Driver", "type" => STRING }, "driver-major-version" => { "description" => "The driver's major version number", "type" => INT }, "driver-minor-version" => { "description" => "The driver's minor version number", "type" => INT }, "jdbc-compliant" => { "description" => "Whether or not the driver is JDBC compliant", "type" => BOOLEAN } } } } Here, only the driver-name is required. For driver-module-name it says "if loaded from module", which I read as "optional". Obviously from above error message, this is not optional -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
10
0 / 0

[JBoss JIRA] Created: (JBAS-9427) org.jboss.test.jbossmessaging.test.XAResourceUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.jbossmessaging.test.XAResourceUnitTestCase --------------------------------------------------------- Key: JBAS-9427 URL: https://issues.jboss.org/browse/JBAS-9427 Project: Legacy JBoss Application Server 6 Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMS (HornetQ) Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 6.1.0 Tests affected: org.jboss.test.jbossmessaging.test.XAResourceUnitTestCase These tests have been failing for a while since the last HornetQ upgrade and IIRC is a test configuration issue. I'll confirm. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBLOGGING-68) Include LICENSE.txt in META-INF directories of binaries

by Pete Muir (JIRA)

Include LICENSE.txt in META-INF directories of binaries ------------------------------------------------------- Key: JBLOGGING-68 URL: https://issues.jboss.org/browse/JBLOGGING-68 Project: JBoss Logging Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 3.0.0.Beta5-jboss-logging Reporter: Pete Muir Assignee: David Lloyd Priority: Minor This helps users when analysing the licensing requirements for clearance to use a library. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
3
0 / 0

[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

13 years, 5 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

13 years, 5 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

13 years, 5 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

13 years, 5 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

13 years, 5 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011