December 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-358) InjectionPoint parameter on disposer method is null

by David Allen (JIRA)

InjectionPoint parameter on disposer method is null --------------------------------------------------- Key: WELD-358 URL: https://jira.jboss.org/jira/browse/WELD-358 Project: Weld Issue Type: Bug Components: Producers (Methods, Fields and Disposers) Affects Versions: 1.0.0.GA Reporter: David Allen Adding a parameter of type InjectionPoint on a disposer method should inject the corresponding meta-data for the place where the bean had been injected; for the bean being destroyed. See http://www.seamframework.org/Community/DisposingAndInjectionPointIntegrat... and the Weld test org.jboss.weld.tests.producer.method.DisposalMethodInjectionPointTest. -- 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, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (WELD-374) Provide sane toString() for classes

by Pete Muir (JIRA)

Provide sane toString() for classes ----------------------------------- Key: WELD-374 URL: https://jira.jboss.org/jira/browse/WELD-374 Project: Weld Issue Type: Feature Request Reporter: Pete Muir Priority: Critical Fix For: 1.0.1.CR1 Currently these vary in quality, some providing good info (e.g. WeldClassImpl), some too little (e.g. WeldFieldImpl) and some are just crazy. In general, the approach should be to delegate the toString to the Names class (see toString(Class<?> rawType, Set<Annotation> annotations, Type[] actualTypeArguments) for a good one). -- 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, 10 months

4
11
0 / 0

[JBoss JIRA] Created: (WELD-617) Can not find beans when deploying compressed Archive to Tomcat

by Aslak Knutsen (JIRA)

Can not find beans when deploying compressed Archive to Tomcat -------------------------------------------------------------- Key: WELD-617 URL: https://jira.jboss.org/browse/WELD-617 Project: Weld Issue Type: Bug Components: Servlet Container Support Affects Versions: 1.0.1.Final Reporter: Aslak Knutsen When deploying a compressed Archive on Tomcat, WebAppBeanDeploymentArchive.scan fails to find and classes. In WebAppBeanDeploymentArchive.scan we try to get the File object representation of the WEB-INF/classes directory so we can recursively scan for classes, but in Tomcat this is a URL to jndi backed by a DirContext. WebAppBeanDeploymentArchive.scan { // inside scan File webInfClasses = Servlets.getRealFile(servletContext, WEB_INF_CLASSES); { // inside getRealFile String realPath = servletContext.getRealPath(path); realPath == null URL resourcePath = servletContext.getResource(path); resourcePath == jndi:/localhost/test/WEB-INF/classes } webInfClasses == null } End result is no classes are found. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

5
9
0 / 0

[JBoss JIRA] Created: (WELD-691) Add tests for Tomcat 7

by Pete Muir (JIRA)

Add tests for Tomcat 7 ---------------------- Key: WELD-691 URL: https://jira.jboss.org/browse/WELD-691 Project: Weld Issue Type: Feature Request Components: Servlet Container Support Affects Versions: 1.1.0.Beta1 Reporter: Pete Muir Fix For: 1.1.0.Beta2 Need to run Servlet Tests on Tomcat 7 container -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

5
5
0 / 0

[JBoss JIRA] Created: (WELD-493) Convert weld-core-tests test suite to use Arquillian

by Aslak Knutsen (JIRA)

Convert weld-core-tests test suite to use Arquillian ---------------------------------------------------- Key: WELD-493 URL: https://jira.jboss.org/jira/browse/WELD-493 Project: Weld Issue Type: Task Components: Testing Infrastructure (Mocks and Harness Integration) Reporter: Aslak Knutsen Assignee: Aslak Knutsen Rewrite the weld-core-test suite to use Arquillian. src/test/ -> rewrite to use Arquillian src/main/ -> move to Arquillian weld container -- 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, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (WELD-702) Invalid url Patterns for class org.jboss.weld.tests.scope.RemoteClient: [*].at org.glassfish.apf.AnnotationInfo@73fce83e

by sreekanth manga (JIRA)

Invalid url Patterns for class org.jboss.weld.tests.scope.RemoteClient: [*].at org.glassfish.apf.AnnotationInfo@73fce83e ------------------------------------------------------------------------------------------------------------------------ Key: WELD-702 URL: https://jira.jboss.org/browse/WELD-702 Project: Weld Issue Type: Bug Components: Testing Infrastructure (Mocks and Harness Integration) Environment: Linux,Glassfish v3.1 Reporter: sreekanth manga Priority: Minor This issue seems to be glassfish specific issue.Couple of tests are failing with non glassfish supported use of annotaion @WebServlet.. 1)In the test, org.jboss.weld.tests.scope.RemoteScopeTest, there is a servlet by name RemoteClient using the annotation "@WebServlet("*")". 2)In the test resource.EMFFactoryTest, there are 3 servlets EMFConsumerTest1, EMFConsumerTest2, EMFConsumerTest3 which uses the annotation @WebServlet("emfconsumer") with out a leading "/" . As per discussion in weld dev alias, this syntax is supported is vendor specific feature of JBoss. Glassfish server log: ================ #|2010-10-04T20:28:02.679+0530|SEVERE|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=15;_ThreadName=Thread-1;|Exception while deploying the app [jsr88-637718205897341632]|#] [#|2010-10-04T20:28:02.745+0530|SEVERE|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=15;_ThreadName=Thread-1;|Exception while deploying the app [jsr88-637718205897341632] : Invalid url Patterns for class org.jboss.weld.tests.scope.RemoteClient: [*].at org.glassfish.apf.AnnotationInfo@73fce83e Invalid url Patterns for class org.jboss.weld.tests.scope.RemoteClient: [*].at org.glassfish.apf.AnnotationInfo@73fce83e at org.glassfish.apf.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:367) at org.glassfish.apf.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:375) at org.glassfish.apf.impl.AnnotationProcessorImpl.processAnnotations(AnnotationProcessorImpl.java:289) at org.glassfish.apf.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:195) at org.glassfish.apf.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:134) at com.sun.enterprise.deployment.archivist.Archivist.processAnnotations(Archivist.java:611) at com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:460) at com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:447) at com.sun.enterprise.deployment.archivist.Archivist.readRestDeploymentDescriptors(Archivist.java:423) at com.sun.enterprise.deployment.archivist.Archivist.readDeploymentDescriptors(Archivist.java:398) at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:263) at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:272) at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:233) at com.sun.enterprise.deployment.archivist.ApplicationFactory.openArchive(ApplicationFactory.java:165) at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:171) at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:85) at com.sun.enterprise.v3.server.ApplicationLifecycle.loadDeployer(ApplicationLifecycle.java:729) at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:671) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:343) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:239) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:351) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:360) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:375) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1080) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:101) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1229) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1218) at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:375) at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:209) at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166) at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:234) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:824) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:721) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1014) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:220) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57) at com.sun.grizzly.ContextTask.run(ContextTask.java:69) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:530) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:511) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalArgumentException: Invalid url Patterns for class org.jboss.weld.tests.scope.RemoteClient: [*]. at com.sun.enterprise.deployment.annotation.handlers.WebServletHandler.processAnnotation(WebServletHandler.java:191) at com.sun.enterprise.deployment.annotation.handlers.WebServletHandler.processAnnotation(WebServletHandler.java:118) at com.sun.enterprise.deployment.annotation.handlers.AbstractWebHandler.processAnnotation(AbstractWebHandler.java:121) at com.sun.enterprise.deployment.annotation.handlers.WebServletHandler.processAnnotation(WebServletHandler.java:68) at org.glassfish.apf.impl.AnnotationProcessorImpl.process(AnnotationProcessorImpl.java:344) ... 45 more |#] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (CDITCK-175) Tests from org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor should be separated

by Marius Bogoevici (JIRA)

Tests from org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor should be separated -------------------------------------------------------------------------------------------------------------- Key: CDITCK-175 URL: https://jira.jboss.org/browse/CDITCK-175 Project: CDI TCK Issue Type: Bug Reporter: Marius Bogoevici The package contains a few tests that exercise deployment errors due to invalid intercepted class definitions. The tests must be separated (perhaps in individual packages) in order to make sure that the test cases run in isolation (since there are multiple sources of errors, the deployment will fail if at least one is satisfied, but we want to test all). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-347) META-INF/beans.xml not sufficient to activate CDI in WAR

by Dan Allen (JIRA)

META-INF/beans.xml not sufficient to activate CDI in WAR -------------------------------------------------------- Key: WELD-347 URL: https://jira.jboss.org/jira/browse/WELD-347 Project: Weld Issue Type: Bug Components: GlassFish Integration Affects Versions: 1.0.0.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 1.0.1.CR1 In GlassFish V3, if a WAR is deployed containing WEB-INF/classes/META-INF/beans.xml, CDI does not get activated (no beans are detected). Activation only happens if the WAR contains WEB-INF/beans.xml. I'm not sure why GlassFish V3 is having a problem finding beans.xml in the META-INF directory of the WAR classpath. I can't tell if it is a problem in Weld or a problem in GlassFish V3 somewhere. -- 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

13 years

3
5
0 / 0

[JBoss JIRA] Created: (CDITCK-176) Decorator Elements in beans.xml use <decorator> not <class>

by Pete Muir (JIRA)

Decorator Elements in beans.xml use <decorator> not <class> ----------------------------------------------------------- Key: CDITCK-176 URL: https://jira.jboss.org/browse/CDITCK-176 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR2 Reporter: Pete Muir Fix For: 1.0.2.CR3 Affected tests: testPassivationCapableBeanWithNonPassivatingDecoratorBeanConstructorFails(org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingBeanConstructor.DecoratorWithNonPassivatingBeanConstructorTest) testPassivationCapableBeanWithNonPassivatingInitializerInDecoratorFails(org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInitializerMethod.DecoratorWithNonPassivatingInitializerMethodTest) testPassivationCapableBeanWithNonPassivatingDecoratorInjectedFieldFails(org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInjectedField.DecoratorWithNonPassivatingInjectedFieldTest) testEnterpriseBeanWithNonPassivatingDecoratorFails(org.jboss.jsr299.tck.tests.context.passivating.broken.enterpriseBeanWithNonPassivatingDecorator.EnterpriseBeanWithNonPassivatingDecoratorTest) testDecoratorListedTwiceInBeansXmlNotOK(org.jboss.jsr299.tck.tests.decorators.definition.broken.decoratorListedTwiceInBeansXml.DecoratorListedTwiceInBeansXmlTest) testNonExistantDecoratorClassInBeansXmlNotOK(org.jboss.jsr299.tck.tests.decorators.definition.broken.nonExistantClassInBeansXml.NonExistantDecoratorClassInBeansXmlTest) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[JBoss JIRA] Created: (WELD-707) Intercepted bean method notifyAll() cannot be declared final

by Adam Warski (JIRA)

Intercepted bean method notifyAll() cannot be declared final ------------------------------------------------------------ Key: WELD-707 URL: https://jira.jboss.org/browse/WELD-707 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.0.Beta1 Reporter: Adam Warski This started showing up after upgrading from M4 to M5, so to Weld 1.1.0. I'm using weldx, and as per the conversation on IRC with Pete this may be the cause. Exact message: WELD-001504 Intercepted bean method [method] public final native pl.softwaremill.service.organization.OrganizationService.notifyAll() (intercepted by pl.softwaremill.cdiext.transaction.TransactionalInterceptor) cannot be declared final -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2010