January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2591) unable to find PropertyEditor when deploying a SAR with BigDecimal attribute

by Radim Hanus (Created) (JIRA)

unable to find PropertyEditor when deploying a SAR with BigDecimal attribute ---------------------------------------------------------------------------- Key: AS7-2591 URL: https://issues.jboss.org/browse/AS7-2591 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.2.Final Environment: jdk1.6.0._29 Reporter: Radim Hanus when deploying a sar with mbean attribute of java.math.BigDecimal type following warning appears in log: 14:14:11,010 WARN [org.jboss.as.deployment.service] (MSC service thread 1-1) Unable to find PropertyEditor for type class java.math.BigDecimal and BigDecimal attribute value from jboss-service.xml descriptor is not set into mbean -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
13
0 / 0

[JBoss JIRA] Created: (JBAS-5515) Failed to load users/passwords/role files

by Heiko Braun (JIRA)

Failed to load users/passwords/role files ----------------------------------------- Key: JBAS-5515 URL: http://jira.jboss.com/jira/browse/JBAS-5515 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Heiko Braun Fix For: JBossAS-5.0.0.CR1 21:25:41,277 ERROR [UsersRolesLoginModule] Failed to load users/passwords/role files java.io.IOException: No properties file: users.properties or defaults: defaultUsers.properties found at org.jboss.security.auth.spi.Util.loadProperties(Util.java:366) at org.jboss.security.auth.spi.UsersRolesLoginModule.loadUsers(UsersRolesLoginModule.java:186) at org.jboss.security.auth.spi.UsersRolesLoginModule.createUsers(UsersRolesLoginModule.java:200) at org.jboss.security.auth.spi.UsersRolesLoginModule.initialize(UsersRolesLoginModule.java:127) When executing one-test: [junit] Running org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 2.421 sec [junit] Test org.jboss.test.ws.jaxws.samples.context.WebServiceContextEJBTestCase FAILED -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
5
0 / 0

[JBoss JIRA] (AS7-2874) Transaction rollback does not work for raw sql and bean managed transaction

by Ondřej Chaloupka (Created) (JIRA)

Transaction rollback does not work for raw sql and bean managed transaction --------------------------------------------------------------------------- Key: AS7-2874 URL: https://issues.jboss.org/browse/AS7-2874 Project: Application Server 7 Issue Type: Bug Reporter: Ondřej Chaloupka Assignee: Stuart Douglas Transaction rollback for bean managed transaction and raw sql does not work properly. After UPDATE data is written to DB and rollback does not cause returns to previous state. Test for this could be checked on: https://github.com/ochaloup/jboss-as/commits/JBQA-5453-test-migration-tx-... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
4
0 / 0

[JBoss JIRA] (AS7-2945) Change the domain model paths system to not use services

by David Lloyd (Created) (JIRA)

Change the domain model paths system to not use services -------------------------------------------------------- Key: AS7-2945 URL: https://issues.jboss.org/browse/AS7-2945 Project: Application Server 7 Issue Type: Enhancement Components: Domain Management Reporter: David Lloyd Assignee: Brian Stansberry Fix For: Open To Community Using services for path references has two distinct disadvantages: * It makes it difficult or impossible to detect changes (the only way to change a path is to restart the service) * If a path consumer is not a service, it is difficult to use path values What we should have instead is have a registration mechanism so that when a path is used, the reference is tracked in the model. This lets us detect backreferences in the event where a path is to be deleted. This would also enable us to send a notification when a path is changed, so that changing a path also causes an update or "refresh" on all referencing domain attributes. This way, for example, if I change the base path for the log directory, all the log handlers can automatically be updated as well as part of the same operation, using their existing update logic. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-2335) Need to be able to query all filesystem paths from management interface

by Stan Silvert (Created) (JIRA)

Need to be able to query all filesystem paths from management interface ----------------------------------------------------------------------- Key: AS7-2335 URL: https://issues.jboss.org/browse/AS7-2335 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.1.0.Alpha1 Reporter: Stan Silvert Assignee: Brian Stansberry For deployment scanners, we have a relative-to attribute with the following description {code} "relative-to" => { "type" => STRING, "description" => "Reference to a filesystem path defined in the \"paths\" section of the server configuration.", "required" => false, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" {code} However, there is nothing in the management interface that will return all the paths including the built-in ones like jboss.server.base.dir. I need the list of all paths to be able to give the user a drop-down in the console. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] (AS7-2723) ApplicationServerService creates path services for paths that are listed as configurable

by Brian Stansberry (Created) (JIRA)

ApplicationServerService creates path services for paths that are listed as configurable ---------------------------------------------------------------------------------------- Key: AS7-2723 URL: https://issues.jboss.org/browse/AS7-2723 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.2.Final, 7.0.1.Final, 7.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.CR1 In ApplicationServerService.start() // Add environment paths AbsolutePathService.addService(ServerEnvironment.HOME_DIR, serverEnvironment.getHomeDir().getAbsolutePath(), serviceTarget); AbsolutePathService.addService(ServerEnvironment.SERVER_BASE_DIR, serverEnvironment.getServerBaseDir().getAbsolutePath(), serviceTarget); AbsolutePathService.addService(ServerEnvironment.SERVER_CONFIG_DIR, serverEnvironment.getServerConfigurationDir().getAbsolutePath(), serviceTarget); AbsolutePathService.addService(ServerEnvironment.SERVER_DATA_DIR, serverEnvironment.getServerDataDir().getAbsolutePath(), serviceTarget); AbsolutePathService.addService(ServerEnvironment.SERVER_LOG_DIR, serverEnvironment.getServerLogDir().getAbsolutePath(), serviceTarget); AbsolutePathService.addService(ServerEnvironment.SERVER_TEMP_DIR, serverEnvironment.getServerTempDir().getAbsolutePath(), serviceTarget); The xsd says these are configurable but if the services are set here, they aren't. Likely fix is to change the xsd to reflect reality. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
5
0 / 0

[JBoss JIRA] (AS7-2989) TS: Database switch (in datasources)

by Ondrej Zizka (Created) (JIRA)

TS: Database switch (in datasources) ------------------------------------ Key: AS7-2989 URL: https://issues.jboss.org/browse/AS7-2989 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka Fix For: 7.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8695) Deployment repository garbage collection

by Brian Stansberry (JIRA)

Deployment repository garbage collection ---------------------------------------- Key: JBAS-8695 URL: https://jira.jboss.org/browse/JBAS-8695 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 The deployment repository is only loosely coupled to the domain model; i.e. users can add content to the repo and then have a problem or decide to not execute a deployment plan with the result that the deployment is not used in the model. Or they can remove the deployment from the model via an update, which doesn't remove it from the repo (in case the update needs to be rolled back.) Effect of this is unreferenced deployment content can accumulate in the repo, so we need a gc utility that can be used to clean it out. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBBUILD-701) Configure jboss-parent to deploy full project sources as part of each release

by Paul Gier (JIRA)

Configure jboss-parent to deploy full project sources as part of each release ----------------------------------------------------------------------------- Key: JBBUILD-701 URL: https://issues.jboss.org/browse/JBBUILD-701 Project: JBoss Build System Issue Type: Enhancement Components: JBoss Parent POM Reporter: Paul Gier Assignee: Paul Gier Fix For: JBoss Parent POM - 7 For each JBoss project release, the full source zip should be deployed along with the other artifacts. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1893) JDBC cache store configuration improvements

by Manik Surtani (JIRA)

JDBC cache store configuration improvements ------------------------------------------- Key: AS7-1893 URL: https://issues.jboss.org/browse/AS7-1893 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Manik Surtani Assignee: Paul Ferraro Fix For: 7.1.0.Beta1 The current <jdbc-store ...> element isn't quite explicit enough to differentiate between the 3 types of JDBC cache stores Infinispan has to offer. <string-keyed-jdbc-store ... >, <binary-keyed-jdbc-store ... > and <mixed-keyed-jdbc-store ... > may be better. Similarly, <bucket-table> and <entry-table> expose implementation details. <binary-keyed-table ...> and <string-keyed-table ... > may be better. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
15
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 January 2012