July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1112) EJB annotation processing DUP fails to find annotations from classes belonging to jars in .ear/lib

by jaikiran pai (JIRA)

EJB annotation processing DUP fails to find annotations from classes belonging to jars in .ear/lib -------------------------------------------------------------------------------------------------- Key: AS7-1112 URL: https://issues.jboss.org/browse/AS7-1112 Project: Application Server 7 Issue Type: Bug Components: EJB Environment: AS7 upstream (June 24 2011) Reporter: jaikiran pai Assignee: jaikiran pai Consider the following deployment: {code} .ear | |--- lib/lib.jar | |--- ejb.jar {code} If ejb.jar contains: {code} @Stateless public class MyBean implements SomeInterface { } {code} and the lib/lib.jar contains the interface: {code} @Remote public interface SomeInterface { ... } {code} then the BusinessViewAnnotationProcessor complains about missing index for the SomeInterface class: {code} 09:05:28,739 WARN [org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor] (MSC service thread 1-2) Could not read annotations on EJB interface blah.blah.SomeInterface {code} Please see the referenced forum thread for the details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (AS7-1181) CDI interceptors enabled randomly

by Jozef Hartinger (JIRA)

CDI interceptors enabled randomly --------------------------------- Key: AS7-1181 URL: https://issues.jboss.org/browse/AS7-1181 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Affects Versions: 7.0.0.CR1 Reporter: Jozef Hartinger Priority: Critical Fix For: 7.0.0.Final A CDI interceptor does not seem to be enabled every time a CDI application is deployed. To reproduce: 1.) Clone https://github.com/seam/compatibility/tree/arquillian-1.0.0.CR1 2.) Set JBOSS_HOME to point to JBoss AS 7 CR1 installation 3.) run mvn clean test -Darquillian=jbossas-managed-7 -Dtest=EnableInterceptorStressTest The EnableInterceptorStressTest executes a simple interceptor testcase (EnableInterceptorTest) 20 times. Out of these 20 deployments, the test fails 6 - 13 times (the number varies randomly). -- 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-1146) Source bundle build problems

by Richard Achmatowicz (JIRA)

Source bundle build problems ---------------------------- Key: AS7-1146 URL: https://issues.jboss.org/browse/AS7-1146 Project: Application Server 7 Issue Type: Bug Components: Build System Affects Versions: 7.0.0.CR1 Environment: GitHub, Linux Reporter: Richard Achmatowicz Assignee: Jason Greene Fix For: 7.0.0.Final The source bundle for AS 7.0.0.CR1 tag obtained from GitHub does not build correctly. Jason indicated that "the problem is that build is configured to include the git hash in the binaries so that we can track down where it came from. If you don't have a git repo though it won't work. So we need to add some kind of workaround for this scenario " Steps to reproduce: 1. Navigate https://github.com/jbossas/jboss-as/ 2. Switch tags to 7.0.0.CR1 3. Download the zip source bundle for 7.0.0.CR1 4. Unzip and build it with maven via .build.sh install -Dmaven.test.skip=true The build is unsuccessful and I see the following: [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [1.188s] [INFO] JBoss Application Server: Parent Aggregator ....... FAILURE [0.323s] [INFO] JBoss Application Server: Protocol Utilities ...... SKIPPED [snip] [INFO] JBoss Application Server Test Suite: Smoke Tests .. SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4.832s [INFO] Finished at: Wed Jun 29 09:57:06 EDT 2011 [INFO] Final Memory: 59M/434M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0:create (default) on project jboss-as-parent: Cannot get the revision information from the scm repository : [ERROR] Exception while executing SCM command. UnsupportedOperationException [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :jboss-as-parent -- 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-1245) Allow sub-directories under deployment folder

by Ramesh Reddy (JIRA)

Allow sub-directories under deployment folder --------------------------------------------- Key: AS7-1245 URL: https://issues.jboss.org/browse/AS7-1245 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.CR1 Reporter: Ramesh Reddy Currently deploying artifacts to sub-folders under "deployments" directory under standalone mode does not seem function correctly. -- 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

[JBoss JIRA] Created: (AS7-1244) File system deployment scanner does not handle sub directories of the deployments directory correctly

by Stuart Douglas (JIRA)

File system deployment scanner does not handle sub directories of the deployments directory correctly ----------------------------------------------------------------------------------------------------- Key: AS7-1244 URL: https://issues.jboss.org/browse/AS7-1244 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.0.0.CR1 Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.0.0.Final -- 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-1228) Resource injection does not work for servlets defined in a different module

by Stuart Douglas (JIRA)

Resource injection does not work for servlets defined in a different module --------------------------------------------------------------------------- Key: AS7-1228 URL: https://issues.jboss.org/browse/AS7-1228 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.CR1 Reporter: Stuart Douglas Assignee: Stuart Douglas -- 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-1243) Picketbox is added to the deployment with export=true

by Stuart Douglas (JIRA)

Picketbox is added to the deployment with export=true ----------------------------------------------------- Key: AS7-1243 URL: https://issues.jboss.org/browse/AS7-1243 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.0.0.CR1 Reporter: Stuart Douglas Assignee: Stuart Douglas -- 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-1226) Doubled word in exception message

by Martin Vecera (JIRA)

Doubled word in exception message --------------------------------- Key: AS7-1226 URL: https://issues.jboss.org/browse/AS7-1226 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.0.0.CR1 Reporter: Martin Vecera Priority: Minor I had broken EAR deployment and I received the following error which is expected. IMHO there should be only one "class" word in the error message. Caused by: java.lang.RuntimeException: Error getting reflective information for class >>class<< org.jboss.test.TaskHelper at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:70) at org.jboss.as.ejb3.deployment.processors.dd.EjbConcurrencyProcessor.checkMethodOverrides(EjbConcurrencyProcessor.java:109) at org.jboss.as.ejb3.deployment.processors.dd.EjbConcurrencyProcessor.deploy(EjbConcurrencyProcessor.java:86) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 5 more -- 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

[JBoss JIRA] Created: (JBRULES-3036) org.antlr.runtime.CommonToken cannot be cast to org.drools.lang.DroolsToken

by Anibal Marques (JIRA)

org.antlr.runtime.CommonToken cannot be cast to org.drools.lang.DroolsToken --------------------------------------------------------------------------- Key: JBRULES-3036 URL: https://issues.jboss.org/browse/JBRULES-3036 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Anibal Marques Assignee: Mark Proctor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2243) Transaction problems, possible bug in ApplicationExceptionComponentMetaDataLoaderFactory

by Benoit Heinrich (JIRA)

Transaction problems, possible bug in ApplicationExceptionComponentMetaDataLoaderFactory ---------------------------------------------------------------------------------------- Key: EJBTHREE-2243 URL: https://issues.jboss.org/browse/EJBTHREE-2243 Project: EJB 3.0 Issue Type: Bug Components: transactions Affects Versions: EJB3_1 1.0.3 Environment: JBoss AS 6.0.0.Final Reporter: Benoit Heinrich I think I've found a possible bug with transaction attributes management in jboss 6.0.0 Final. The problem appears when using the @TransactionAttribute annotation on an EJB bean with the @Interceptors. When using that it seems that the @TransactionAttribute annotation is ignored. By removing the @Interceptors annotation it works and the right transaction attribute is used. More details available in the jboss forum link. Cheers, /Benoit -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011