July 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-561) Not intuitive error message: WELD-000069 An interceptor must have at least one binding, but Foo has none

by Marcin Zajaczkowski (JIRA)

Not intuitive error message: WELD-000069 An interceptor must have at least one binding, but Foo has none -------------------------------------------------------------------------------------------------------- Key: WELD-561 URL: https://jira.jboss.org/browse/WELD-561 Project: Weld Issue Type: Task Components: Interceptors and Decorators Affects Versions: 1.0.1.Final Reporter: Marcin Zajaczkowski Priority: Trivial WELD-000069 error message (without debug message) is not very intuitive. DEBUG org.jboss.weld.Reflection - WELD-000602 interface net.sf.perf4cdi.api.Perf4jProfiled is not declared @Target(TYPE, METHOD) or @Target(TYPE) ERROR org.jboss.weld.exceptions.DeploymentException: WELD-000069 An interceptor must have at least one binding, but net.sf.perf4cdi.Perf4jProfiledInterceptor has none at org.jboss.weld.bean.InterceptorImpl.<init>(InterceptorImpl.java:71) at org.jboss.weld.bean.InterceptorImpl.of(InterceptorImpl.java:55) at org.jboss.weld.bootstrap.AbstractBeanDeployer.createInterceptor(AbstractBeanDeployer.java:255) at org.jboss.weld.bootstrap.BeanDeployer.createBeans(BeanDeployer.java:106) at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:151) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:377) at org.jboss.weld.mock.MockServletLifecycle.beginApplication(MockServletLifecycle.java:121) at org.jboss.weld.mock.TestContainer.startContainer(TestContainer.java:85) at org.jboss.weld.test.harness.AbstractStandaloneContainersImpl.deploy(AbstractStandaloneContainersImpl.java:40) at org.jboss.testharness.AbstractTest.deployArtifact(AbstractTest.java:103) at org.jboss.testharness.AbstractTest.beforeClass(AbstractTest.java:206) at org.jboss.weld.test.AbstractWeldTest.beforeClass(AbstractWeldTest.java:57) -- 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

15 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (WELD-544) Use org.jboss.spec.javax.interceptor instead of the current Interceptors 1.1 API artifact

by Marius Bogoevici (JIRA)

Use org.jboss.spec.javax.interceptor instead of the current Interceptors 1.1 API artifact ----------------------------------------------------------------------------------------- Key: WELD-544 URL: https://jira.jboss.org/browse/WELD-544 Project: Weld Issue Type: Feature Request Components: Infrastructure Affects Versions: 1.0.1.Final Reporter: Marius Bogoevici Priority: Critical Fix For: 1.0.2.CR1 -- 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

15 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (CDITCK-170) TransactionalObserversTest uses bean managed transactions and cannot test propagation

by Marius Bogoevici (JIRA)

TransactionalObserversTest uses bean managed transactions and cannot test propagation ------------------------------------------------------------------------------------- Key: CDITCK-170 URL: https://jira.jboss.org/browse/CDITCK-170 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Marius Bogoevici org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest uses two BMT stateless beans: DogAgent and DogTrainer. However,when a BMT business method is invoked, the existing transaction is suspended, therefore the observer methods will be executed outside the scope of the transaction in which the event has been fired. Also, when the transaction is rolled back b/c of the observer setting the flag during commit(), we expect the commit method to throw a RollbackException. -- 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

15 years, 7 months

3
11
0 / 0

[JBoss JIRA] Created: (CDITCK-94) Route serialization/deserialization through SPI

by Pete Muir (JIRA)

Route serialization/deserialization through SPI ----------------------------------------------- Key: CDITCK-94 URL: https://jira.jboss.org/jira/browse/CDITCK-94 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Infrastructure Reporter: Pete Muir Fix For: 1.1.0.CR1 This allows a porting package to mirror the behavior of an app server which may provide special behavior here. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (CDITCK-171) Tests using JSF components must include JSF metadata

by Marius Bogoevici (JIRA)

Tests using JSF components must include JSF metadata ----------------------------------------------------- Key: CDITCK-171 URL: https://jira.jboss.org/browse/CDITCK-171 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR1 Reporter: Marius Bogoevici Fix For: 1.0.2.Final If no JSF metadata is present for a WAR, in form of web.xml and/or a faces-config.xml file, the container may not provide the JSF features for that particular deployment (i.e. JSF APIs and libraries) that the test expects. Currently affected tests org.jboss.jsr299.tck.tests.implementation.simple.definition.SimpleBeanDefinitionTest org.jboss.jsr299.tck.tests.implementation.simple.definition.EnterpriseBeanNotDiscoveredAsManagedBeanTest -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-165) Bug in org.jboss.jsr299.tck.tests.context.NormalContextTest # testSameNormalScopeBeanInjectedEverywhere

by Gurkan Erdogdu (JIRA)

Bug in org.jboss.jsr299.tck.tests.context.NormalContextTest # testSameNormalScopeBeanInjectedEverywhere ------------------------------------------------------------------------------------------------------- Key: CDITCK-165 URL: https://jira.jboss.org/browse/CDITCK-165 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.2.CR1 Reporter: Gurkan Erdogdu In this method, this tests tries to compare the session context instance equality. I think this is not correct. Normal scoped beans returns "Proxy" for actual instances. In SimpleBeanA and SimpleBeanB bean instances, @Inject SimpleBeanZ z, may return a different proxy instances that represents the same SimpleBeanZ contextual instance. In OWB, we return different proxy instances for normal scoped beans, therefore instanceOfA.getZ() == instanceOfB.getZ( ) --> False, because we return different proxy instances for instanceOfA.getZ() and instanceOfB.getZ() that both of them represents the same z instance. Test may be updated to compare some instance variables of z instance. -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-169) PersistenceContextInjectionTest is using an invalid isOpen() call

by Marius Bogoevici (JIRA)

PersistenceContextInjectionTest is using an invalid isOpen() call ----------------------------------------------------------------- Key: CDITCK-169 URL: https://jira.jboss.org/browse/CDITCK-169 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.2.CR1 Reporter: Marius Bogoevici Fix For: 1.0.2.Final, 1.1.0.CR1 org.jboss.jsr299.tck.tests.implementation.simple.resource.persistenceContext.PersistenceContextInjectionTest: The Java EE resource producer field pattern is tested by a couple of methods. During the test, the EntityManager.isOpen() method is used for testing, but calling isOpen() from within the test method is invalid, because the EntityManager is transaction-scoped and not application-managed, and the call happens outside the scope of a JTA transaction. Proposed solution: inject the produced EM in an EJB and perform the check from within a transaction. -- 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

15 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (WELD-473) required meta-annotations for a qualifier specified differently in spec and API

by Wolfgang Frech (JIRA)

required meta-annotations for a qualifier specified differently in spec and API ------------------------------------------------------------------------------- Key: WELD-473 URL: https://jira.jboss.org/jira/browse/WELD-473 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Environment: n/a Reporter: Wolfgang Frech The specification and the API documentation differ on the required and optional meta-annotations of a qualfiier. JSR-299, 2.3.2 Defining new qualfier type specifies @Target(METHOD, FIELD, PARAMETER, TYPE} ("is") @Retention(RUNTIME) ("is") @Qualifier, but only optional ("may") API-Doc of Qualifier specifies @Qualifier @Retention(RUNTIME) @Documented (optional, typical) @Target optional, but various element types as targets possible Both agree on Retention only. As a third source I might have a look at the code and the implemented validity check. I have not so far. I am a bit fussy about this because a missing @Target of my first custom scope messed up the proxying. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (WELDX-70) Automate testing of archetypes

by Steven Boscarine (JIRA)

Automate testing of archetypes ------------------------------ Key: WELDX-70 URL: https://jira.jboss.org/jira/browse/WELDX-70 Project: Weld Extensions Issue Type: Task Components: Archetypes Affects Versions: Archetypes 1.0.0-BETA1 Reporter: Steven Boscarine Assignee: Steven Boscarine This may be a difficult and funky task. I haven't been able to find examples of people automating maven calls. This may be a very pioneering task if done in Java. I do it presently with a shell script. Here's what needs to happen: An archetype needs to be built from source. (mvn clean install) A project needs to be created from the archetype. (mvn archetype:generate -DartifactId=myproject) The project's tests need to be run. (mvn clean test -f myproject/pom.xml) -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (WELD-489) Update the jsf dependency version in weld-api-bom to 2.0

by Adam Warski (JIRA)

Update the jsf dependency version in weld-api-bom to 2.0 -------------------------------------------------------- Key: WELD-489 URL: https://jira.jboss.org/jira/browse/WELD-489 Project: Weld Issue Type: Task Components: Infrastructure Affects Versions: 1.0.1.Final Reporter: Adam Warski Currently it's 1.2_13, and the newest version of the api is 2.0.2-FCS. The version of the bom is 1.0-SP1 -- 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, 8 months

2
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues July 2010