January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3419) JBossWeb::ssl element in connector settings should check for vaultified strings

by Anil Saldhana (JIRA)

Anil Saldhana created AS7-3419: ---------------------------------- Summary: JBossWeb::ssl element in connector settings should check for vaultified strings Key: AS7-3419 URL: https://issues.jboss.org/browse/AS7-3419 Project: Application Server 7 Issue Type: Feature Request Components: Web Affects Versions: 7.1.0.CR1 Reporter: Anil Saldhana Assignee: Jean-Frederic Clere Fix For: 7.1.0.Final Currently, the passwords in the ssl element of the connector settings are in clear text. https://community.jboss.org/wiki/JBossAS7SecuringPasswords describes very simple ways of checking whether a string is of the vault format and invoking the vault to get the decrypted string value. -- 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

12 years, 8 months

3
13
0 / 0

[JBoss JIRA] (AS7-3441) Selection models with KeyProviders break form data binding

by Heiko Braun (JIRA)

Heiko Braun created AS7-3441: -------------------------------- Summary: Selection models with KeyProviders break form data binding Key: AS7-3441 URL: https://issues.jboss.org/browse/AS7-3441 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.Alpha1 See JPA Metrics > PersistenceUnitList. -- 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

12 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBSER-119) Ensure compatibility with Trove

by Christian Effertz (JIRA)

Ensure compatibility with Trove ------------------------------- Key: JBSER-119 URL: https://jira.jboss.org/jira/browse/JBSER-119 Project: JBoss Serialization Issue Type: Thirdparty Change Affects Versions: 1.0.3 GA Reporter: Christian Effertz Assignee: Clebert Suconic Fix For: 1.1.0 Beta The version of [Trove|http://trove4j.sourceforge.net] that is shipped with the latest version of JBoss Serialization is quite old. Trove has had a major release since it was bundled last time for Version 1.0.3 and seems to be facing a next major version 3.0. As it is stated in their release notes that they had some performance improvements and Bug Fixes I would assume that JBoss Serialization would profit in terms of stability and performance if using the newer versions. I will give it a try in our dev system, but it would be more comforting to get a statement if your testsuite turned green if using the newer version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] (AS7-3500) Add org/w3c/dom/views to the javax.api module

by Robert Reimann (JIRA)

Robert Reimann created AS7-3500: ----------------------------------- Summary: Add org/w3c/dom/views to the javax.api module Key: AS7-3500 URL: https://issues.jboss.org/browse/AS7-3500 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.1.0.CR1b Reporter: Robert Reimann Please add the org/w3c/dom/views path to the javax.api module. {code} <path name="org/w3c/dom/views"/> {code} -- 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

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1291) UserTransaction not exposed in JDNI

by Juergen Zimmermann (JIRA)

UserTransaction not exposed in JDNI ----------------------------------- Key: AS7-1291 URL: https://issues.jboss.org/browse/AS7-1291 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.0.0.Final Environment: 7.1.0.Alpha1 Jenkins build 1402 Reporter: Juergen Zimmermann Assignee: John Bailey In JBoss 6 UserTransaction was exposed in JNDI named as java:comp/UserTransaction. Thus an Arquillian test method could be encapsulated in one single transaction: * lookup() the UserTransaction * begin() inside @Before * commit() inside @After Unfortunately, JBoss 7 doesn't have a JNDI entry for UserTransaction. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

8
11
0 / 0

[JBoss JIRA] (AS7-3380) Changing MDB configuration in jboss-ejb3.xml causes ClassCastException

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-3380: ------------------------------------- Summary: Changing MDB configuration in jboss-ejb3.xml causes ClassCastException Key: AS7-3380 URL: https://issues.jboss.org/browse/AS7-3380 Project: Application Server 7 Issue Type: Bug Reporter: Ondřej Chaloupka Assignee: jaikiran pai I did change of destination of mdb queue in jboss-ejb3.xml file in following way: https://github.com/ochaloup/jboss-as/commit/5a0501387821994b6a94ddb508f6f... But during deployment I get exception: java.lang.ClassCastException: org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData cannot be cast to org.jboss.metadata.ejb.jboss.ejb3.JBossGenericBeanMetaData {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."mdb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."mdb.jar".PARSE: Failed to process phase PARSE of deployment "mdb.jar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] Caused by: java.lang.ClassCastException: org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData cannot be cast to org.jboss.metadata.ejb.jboss.ejb3.JBossGenericBeanMetaData at org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.merge(MessageDrivenBeanMetaData.java:353) at org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:85) at org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:36) at org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.merge(EnterpriseBeansMetaData.java:73) at org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.createMerged(EnterpriseBeansMetaData.java:52) at org.jboss.metadata.ejb.spec.EjbJarMetaData.merge(EjbJarMetaData.java:175) at org.jboss.metadata.ejb.spec.EjbJarMetaData.createMerged(EjbJarMetaData.java:668) at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:125) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] ... 5 more {code} -- 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

12 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-1701) Add a --help command line switch to jboss-admin

by Thomas Diesler (JIRA)

Add a --help command line switch to jboss-admin ----------------------------------------------- Key: AS7-1701 URL: https://issues.jboss.org/browse/AS7-1701 Project: Application Server 7 Issue Type: Feature Request Components: CLI Reporter: Thomas Diesler Assignee: Alexey Loubyansky $ bin/jboss-admin.sh --help '--help' is not a valid operation name. I would have like to see that $ bin/jboss-admin.sh --connect is valid. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-9072) High level commands for common standalone mode tasks

by Brian Stansberry (JIRA)

High level commands for common standalone mode tasks ---------------------------------------------------- Key: JBAS-9072 URL: https://issues.jboss.org/browse/JBAS-9072 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta3 Identify and implement the high level commands we want to support for a standalone mode server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
10
0 / 0

[JBoss JIRA] Created: (AS7-1034) ignore persistence unit definitions that have PersistenceUnitTransactionType = RESOURCE_LOCAL

by Scott Marlow (JIRA)

ignore persistence unit definitions that have PersistenceUnitTransactionType = RESOURCE_LOCAL --------------------------------------------------------------------------------------------- Key: AS7-1034 URL: https://issues.jboss.org/browse/AS7-1034 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.0.0.Beta3 Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
3
0 / 0

[JBoss JIRA] (AS7-3388) remove references to extended persistence context when passivating

by Scott Marlow (JIRA)

Scott Marlow created AS7-3388: --------------------------------- Summary: remove references to extended persistence context when passivating Key: AS7-3388 URL: https://issues.jboss.org/browse/AS7-3388 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow 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

12 years, 8 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012