July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1206) test for jndi binding isn't unbound during remove if jndi name and data-source name are different

by Stefano Maestri (JIRA)

test for jndi binding isn't unbound during remove if jndi name and data-source name are different ------------------------------------------------------------------------------------------------- Key: AS7-1206 URL: https://issues.jboss.org/browse/AS7-1206 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Stefano Maestri Fix For: 7.1.0.CR1 -- 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: (AS7-1202) test for enable datasource

by Stefano Maestri (JIRA)

test for enable datasource -------------------------- Key: AS7-1202 URL: https://issues.jboss.org/browse/AS7-1202 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1200) test case for xa datasource persistence to xml

by Stefano Maestri (JIRA)

test case for xa datasource persistence to xml ---------------------------------------------- Key: AS7-1200 URL: https://issues.jboss.org/browse/AS7-1200 Project: Application Server 7 Issue Type: Sub-task Reporter: Stefano Maestri Fix For: 7.1.0.CR1 -- 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: (AS7-1290) add cls/clear command

by Alexey Loubyansky (JIRA)

add cls/clear command --------------------- Key: AS7-1290 URL: https://issues.jboss.org/browse/AS7-1290 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.1.Final Add a command to clear the terminal. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1166) Quit the CLI on EOF

by Marek Schmidt (JIRA)

Quit the CLI on EOF ------------------- Key: AS7-1166 URL: https://issues.jboss.org/browse/AS7-1166 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.0.0.CR1 Reporter: Marek Schmidt jboss-admin.sh should behave more like a shell and terminate on EOF (ctrl-D) The current behavior is quite counter-intuitive and trying to do e.g. echo "deploy foo.war" | ./jboss-admin.sh --connect leads the CLI into an infinite-loop generating infinite number of prompts. -- 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-1312) Invalid class in deployment causes deployment to fail

by Stuart Douglas (JIRA)

Invalid class in deployment causes deployment to fail ----------------------------------------------------- Key: AS7-1312 URL: https://issues.jboss.org/browse/AS7-1312 Project: Application Server 7 Issue Type: Bug Reporter: Stuart Douglas If jandex fails to process a class the whole deployment blow up. This should really just log a warning. -- 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: (AS7-1308) :jndi-view in domain mode on profile returns success

by Heiko Rupp (JIRA)

:jndi-view in domain mode on profile returns success ---------------------------------------------------- Key: AS7-1308 URL: https://issues.jboss.org/browse/AS7-1308 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.0.0.Final Reporter: Heiko Rupp Assignee: John Bailey Doing :jndi-view on /profile=default/subsystem=naming gives: [domain@localhost:9999 subsystem=naming] :jndi-view { "outcome" => "success", "result" => "Jndi view is only available in runtime mode." } This makes no sense, as the outcome is not a view on the JNDI-tree, but a failure description. That operation should return failure instead. -- 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: (AS7-1309) Port numbers are not correctly displayed in console

by Heiko Braun (JIRA)

Port numbers are not correctly displayed in console --------------------------------------------------- Key: AS7-1309 URL: https://issues.jboss.org/browse/AS7-1309 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.0.0.Final Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.1.Final i.e. the multicast ports -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1297) Weld claims to be able to inject Principal, but throws RuntimeException("not implemented") at runtime

by Craig Ringer (JIRA)

Weld claims to be able to inject Principal, but throws RuntimeException("not implemented") at runtime ----------------------------------------------------------------------------------------------------- Key: AS7-1297 URL: https://issues.jboss.org/browse/AS7-1297 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld, Security Affects Versions: 7.0.0.Final, 7.1.0.Alpha1 Environment: Windows 7 x64, JDK 6 and 7 both tested. JBoss AS 7.0.0 release, and Jboss AS 7.1.0.Alpha1 nightly build 2011-07-15. Reporter: Craig Ringer Assignee: Stuart Douglas In JBoss AS 7, Weld claims to be able to inject instances of java.security.Principal. CDI archives that try to inject it do not fail at deployment time with unsatisfied dependencies. Instead, they fail later, at runtime, when injection is attempted. At this point a runtime exception indicating that principal injection isn't supported is thrown. This prevents user code, or external frameworks like Seam 3 Security, from providing their own producers for javax.security.Principal without requiring a qualifier to be used. If JBoss AS 7's weld integration doesn't support container managed security yet (perhaps because container managed security is not supported in JBoss AS 7 at all yet?) then it should not offer an injection point for the security principal. Backtrace when calling toString() on an injected proxy for a Principal: Caused by: java.lang.RuntimeException: not implemented at org.jboss.as.weld.services.bootstrap.WeldSecurityServices.getPrincipal(WeldSecurityServices.java:53) at org.jboss.weld.bean.builtin.ee.PrincipalBean$PrincipalCallable.call(PrincipalBean.java:48) at org.jboss.weld.bean.builtin.ee.PrincipalBean$PrincipalCallable.call(PrincipalBean.java:34) at org.jboss.weld.bean.builtin.CallableMethodHandler.invoke(CallableMethodHandler.java:50) at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:62) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125) at org.jboss.weld.security.Principal$1263393769$Proxy$_$$_Weld$Proxy$.toString(Principal$1263393769$Proxy$_$$_Weld$Proxy$.java) -- 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: (AS7-1304) Resource Adapter configuration corrupts standalone.xml

by Andrew Wheeler (JIRA)

Resource Adapter configuration corrupts standalone.xml ------------------------------------------------------ Key: AS7-1304 URL: https://issues.jboss.org/browse/AS7-1304 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.0.0.Final Environment: Linux Reporter: Andrew Wheeler Assignee: Jesper Pedersen Priority: Critical When defining a resource adapter in the standalone.xml which includes a config-property it is overwriten by the server which modifies the config-properties in a manner which prevents the server from booting on the next restart >From standalone: <resource-adapter> <archive> jackrabbit-jca.rar </archive> <transaction-support> XATransaction </transaction-support> <connection-definitions> <connection-definition class-name="org.apache.jackrabbit.jca.JCAManagedConnectionFactory" jndi-name="java:/jcr/ConnectionFactory" enabled="true" use-java-context="true" pool-name="jackrabbit" use-ccm="true"> <config-property name="HomeDir">${jboss.server.data.dir}/jackrabbit</config-property> <config-property name="ConfigFile">${jboss.server.data.dir}/jackrabbit/jackrabbit.xml</config-property> </connection-definition> </connection-definitions> </resource-adapter> The config-property then becomes in the overwritten standalone.xml: <config-property>(HomeDir => /opt/jboss7/standalone/data/jackrabbit)</config-property> this causes the server to fail to parse standalone.xml and subsequently does not start on the next restart with the following error: ERROR [stderr] Exception in thread "Controller Boot Thread" java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration Also, the JCA connector is not getting the correct parameters, so the resource throws an exception: WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (http--127.0.0.1-8080-6) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Failed to create session: Unable to access a repository with the following settings: org.apache.jackrabbit.repository.conf: ("ConfigFile" => "/opt/jboss7/standalone/data/jackrabbit/jackrabbit.xml") org.apache.jackrabbit.repository.home: ("HomeDir" => "/opt/jboss7/standalone/data/jackrabbit") Perhaps the repository you are trying to access is not available at the moment. This error is thrown by Jackrabbit as it cannot access the configuration file. I'm guessing that it has trouble parsing the string passed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
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