May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-927) create test cases for datasource management operations

by Stefano Maestri (JIRA)

create test cases for datasource management operations ------------------------------------------------------ Key: AS7-927 URL: https://issues.jboss.org/browse/AS7-927 Project: Application Server 7 Issue Type: Task Components: JCA Reporter: Stefano Maestri Assignee: Stefano Maestri 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (AS7-883) Properties file based repository of users for domain management.

by Darran Lofthouse (JIRA)

Properties file based repository of users for domain management. ---------------------------------------------------------------- Key: AS7-883 URL: https://issues.jboss.org/browse/AS7-883 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (AS7-882) Verify invalid password behaviout for Digest auth (Domain Management)

by Darran Lofthouse (JIRA)

Verify invalid password behaviout for Digest auth (Domain Management) --------------------------------------------------------------------- Key: AS7-882 URL: https://issues.jboss.org/browse/AS7-882 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse 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

15 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-9032) @EJB injection with same "name" on two different fields leads to DuplicateServiceException

by jaikiran pai (JIRA)

@EJB injection with same "name" on two different fields leads to DuplicateServiceException ------------------------------------------------------------------------------------------ Key: JBAS-9032 URL: https://issues.jboss.org/browse/JBAS-9032 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Environment: JBoss AS7 master, JBoss AS 7.0 Beta1 Reporter: jaikiran pai Consider this servlet (or any other component): {code} public class MyServlet extends HttpServlet { @EJB (name="simpleName", beanName="SomeEJB") private SomeEJB bean; @EJB (name="simpleName", beanName="SomeEJB") private SomeEJB beanAgain; ... } {code} Notice that both the @EJB injection points expect the bean to be injected from bean in ENC at java:comp/env/simpleName. This however, leads to exception during deployment with the following message: {code} 16:06:43,846 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."myejbapp.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."myejbapp.war".INSTALL: Failed to process phase INSTALL of deployment "myejbapp.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.naming.context.java.module.myejbapp.myejbapp.env/simpleName is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:143) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (AS7-904) @Resource injection of Java EE Managed Bean fails

by jaikiran pai (JIRA)

@Resource injection of Java EE Managed Bean fails ------------------------------------------------- Key: AS7-904 URL: https://issues.jboss.org/browse/AS7-904 Project: Application Server 7 Issue Type: Bug Components: EE Reporter: jaikiran pai Assignee: jaikiran pai @Resource injection within any component, for a Java EE Managed Bean, currently fails with: {code} org.jboss.as.server.deployment.DeploymentUnitProcessingException: Can't handle @Resource for ENC name: foo.bar/field since it's missing a lookup value and isn't of any known type {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (LOGTOOL-15) Sources get generated in the target/classes directory with maven

by James Perkins (JIRA)

Sources get generated in the target/classes directory with maven ---------------------------------------------------------------- Key: LOGTOOL-15 URL: https://issues.jboss.org/browse/LOGTOOL-15 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Fix For: 1.0.0.Beta6 The sources should be created in target/generated-sources, but get created in the target/classes directory if the target on the compiler is not set to 1.6. See if there is a way to always generate sources in a default directory rather than relying on the target version being set. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
4
0 / 0

[JBoss JIRA] Closed: (JBBUILD-655) Wrong checksum on jboss maven repository

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/JBBUILD-655?page=com.atlassian.jira.plugi... ] Paul Gier closed JBBUILD-655. ----------------------------- Assignee: Paul Gier Fix Version/s: Repository Support 2010 Resolution: Done The Nexus routing rules are configured now so that everything under "org/jboss" must come from the jboss repositories. > Wrong checksum on jboss maven repository > ---------------------------------------- > > Key: JBBUILD-655 > URL: https://issues.jboss.org/browse/JBBUILD-655 > Project: JBoss Build System > Issue Type: Bug > Components: Artifact Repositories > Reporter: Fabricio Lemos > Assignee: Paul Gier > Fix For: Repository Support 2010 > > > Some POMs are with the wrong checksum on Jboss Maven Repository, which causes artifactory to reject those POMs if validation is on. > Here a few examples of artifactory output: > jboss: Downloaded 'http://repository.jboss.org/nexus/content/groups/public/org/jboss/weld/we...' with return code: 200. > (o.a.r.v.i.PomInterceptor:78) - Failed to transform pom file > java.io.IOException: Checksum policy 'GEN_IF_ABSENT' rejected the artifact 'weld-api-bom-1.0-SP1.pom'. Checksums info: [ChecksumInfo{type=SHA-1, original='11c59ba0129c15a2966adf7b993552ac0e38f5db', actual='a682982a8c581b327c79b6ef5dd239005cf4d30b'}, ChecksumInfo{type=MD5, original='645ce7c04f2650ec80b54ace02b4c1b9', actual='1f00ec3b8241348739fbb1544b53aef5'}] > (o.a.r.HttpRepo :196) - jboss: Downloaded 'http://repository.jboss.org/nexus/content/groups/public/org/jboss/weld/we...' with return code: 200. > [ERROR] (o.a.r.v.i.PomInterceptor:78) - Failed to transform pom file > java.io.IOException: Checksum policy 'GEN_IF_ABSENT' rejected the artifact 'weld-core-bom-1.0.1-Final.pom'. Checksums info: [ChecksumInfo{type=SHA-1, original='05c018953796d43baaec6b7b526883116fb4ba4c', actual='9c1d4f3ba941405a2717081d29e2b542934a69d7'}, ChecksumInfo{type=MD5, original='98167a84f872b7d2ab07c4826269cff5', actual='de063cceee5e38a7b0b9b8d82930aebb'}] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7427) AS won't boot with sun jmx enabled

by Jonathan Halliday (JIRA)

AS won't boot with sun jmx enabled ---------------------------------- Key: JBAS-7427 URL: https://jira.jboss.org/jira/browse/JBAS-7427 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Environment: sun jdk6, fedora, AS trunk r96005 Reporter: Jonathan Halliday Assignee: David Lloyd Fix For: JBossAS-6.0.0.Alpha1 [jhalli jboss-6.0.0-SNAPSHOT]$ export JAVA_OPTS="-Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false" [jhalli jboss-6.0.0-SNAPSHOT]$ bin/run.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/output/jboss-6.0.0-SNAPSHOT JAVA: /usr/local/jdk1.6.0_16/bin/java JAVA_OPTS: -Dprogram.name=run.sh -server -Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.net.preferIPv4Stack=true CLASSPATH: /home/jhalli/IdeaProjects/jboss/jbossas_trunk/build/output/jboss-6.0.0-SNAPSHOT/bin/run.jar:/usr/local/jdk1.6.0_16/lib/tools.jar ========================================================================= Failed to initalize plugin: org.jboss.logging.logmanager.LoggerPluginImpl@214a55f2, cause: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") ... Failed to initalize plugin: org.jboss.aop.util.logging.SystemOutLoggerPlugin@5c1ae90c, cause: java.lang.AbstractMethodError -- 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

15 years, 1 month

3
11
0 / 0

[JBoss JIRA] Created: (JBAS-9308) Either implement or remove DomainUpdateListener

by Brian Stansberry (JIRA)

Either implement or remove DomainUpdateListener ----------------------------------------------- Key: JBAS-9308 URL: https://issues.jboss.org/browse/JBAS-9308 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Blocker Fix For: 7.0.0.CR1 The DomainUpdateListener stuff in controller-client got disabled in the move to the detyped API. It needs to either be implemented properly or removed from the API. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBCL-84) Extend the ClassLoadingMetaData filtered package semantics

by Adrian Brock (JIRA)

Extend the ClassLoadingMetaData filtered package semantics ---------------------------------------------------------- Key: JBCL-84 URL: https://jira.jboss.org/jira/browse/JBCL-84 Project: JBoss ClassLoader Issue Type: Feature Request Components: MetaData Reporter: Adrian Brock Currently the ClassLoadingMetaData has some includedPackages and excludedPackages metadata. This is just a comma seperated list of explicit package names. This metadata should be extended to make it more flexible. e.g. using globing <classloader> <excluded type="glob">com.foo.*</included> or explicitly naming the filter <classloader> <excluded class="com.foo.MyClassFilter>...</excluded> -- 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

15 years, 1 month

2
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 May 2011