July 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-114) Implement test for assertion 6.7.4 tb using a filter to check for the exception

by Pete Muir (JIRA)

Implement test for assertion 6.7.4 tb using a filter to check for the exception ------------------------------------------------------------------------------- Key: CDITCK-114 URL: https://jira.jboss.org/jira/browse/CDITCK-114 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Reporter: Pete Muir Fix For: 1.1.0.CR1 It's very hard to test the exception from the client, as there is not even a requirement that the server send a particular error page. However a servlet, installed as the outer most filter, should be able to find the exception is thrown. I don't know how you check if a new transient conversation is created. -- 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, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (CDITCK-109) Rewrite all conversation tests to be remote JSF tests

by Pete Muir (JIRA)

Rewrite all conversation tests to be remote JSF tests ----------------------------------------------------- Key: CDITCK-109 URL: https://jira.jboss.org/jira/browse/CDITCK-109 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Reporter: Pete Muir Fix For: 1.0.1.GA, 1.1.0.CR1 This is needed because the conversation context is not actually active in other requests, and also Conversation is not available -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (CDITCK-143) Bug in SimpleLifecycleTest

by Gurkan Erdogdu (JIRA)

Bug in SimpleLifecycleTest -------------------------- Key: CDITCK-143 URL: https://jira.jboss.org/jira/browse/CDITCK-143 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu MEthods : testBeanCreateInjectsDependenciesAndInvokesInitializerToInstantiateInstance testCreateReturnsSameBeanPushed Those methods test CreationalContext#push. But implementation does not require to support push method according to specification. -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (CDITCK-116) Typo in dd-override-report

by Jozef Hartinger (JIRA)

Typo in dd-override-report -------------------------- Key: CDITCK-116 URL: https://jira.jboss.org/jira/browse/CDITCK-116 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.GA Reporter: Jozef Hartinger Priority: Trivial The document says "Deployment Descripters overriden by the TCK" while it should say "Deployment Descriptors overriden by the TCK" -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (CDITCK-140) TCK uses cyclic @PostConstruct calls which is forbidden by JSR-250

by Mark Struberg (JIRA)

TCK uses cyclic @PostConstruct calls which is forbidden by JSR-250 ------------------------------------------------------------------ Key: CDITCK-140 URL: https://jira.jboss.org/jira/browse/CDITCK-140 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Reporter: Mark Struberg from JSR-250-1.1.MREL section 2.5: "The PostConstruct annotation is used on a method that needs to be executed after dependency injection is done to perform any initialization. This method MUST be invoked before the class is put into service." Which I read as "may only get used by others after the @PostConstruct annotated method did run". This is backed by the following example public BeanA { private @Inject BeanB b; private int x = 0; public int getX() { return x; } @PostConstruct void init() { x = b.getX()+7; } } public BeanB { private @Inject BeanA a; private int x = 0; public int getX() { return x; } @PostConstruct void init() { x = a.getX()+9; } } which value do a.x and b.x get finally? This would simply be non-deterministic - and therefore forbidden by the JSR-250 spec. Such kind of circular @PostConstruct method calls happen e.g. in CircularDependencyTest Pig -> Food -> Pig -- 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, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (CDITCK-134) Injection point not on a passivation capable bean

by Pete Muir (JIRA)

Injection point not on a passivation capable bean ------------------------------------------------- Key: CDITCK-134 URL: https://jira.jboss.org/jira/browse/CDITCK-134 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Reporter: Gurkan Erdogdu Fix For: 1.0.2.CR1 org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingBeanConstructor org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInitializerMethod org.jboss.jsr299.tck.tests.context.passivating.broken.decoratorWithNonPassivatingInjectedField These packages tests decorator injection points to check if they are passivation capable dependency or not, however the injection point is not on a passivation capable bean -- 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, 8 months

3
12
0 / 0

[JBoss JIRA] Created: (WELD-269) Registration of a custom implementation of the Decorator interface fails

by Jozef Hartinger (JIRA)

Registration of a custom implementation of the Decorator interface fails ------------------------------------------------------------------------ Key: WELD-269 URL: https://jira.jboss.org/jira/browse/WELD-269 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Assignee: Marius Bogoevici Fix For: 1.0.0.CR2 org.jboss.jsr299.tck.tests.decorators.custom.CustomDecoratorTest.testCustomImplementationOfDecoratorInterface() -- 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, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (CDITCK-120) Seems a bug in DependentContextTest

by Gurkan Erdogdu (JIRA)

Seems a bug in DependentContextTest ----------------------------------- Key: CDITCK-120 URL: https://jira.jboss.org/jira/browse/CDITCK-120 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu org.jboss.jsr299.tck.tests.context.dependent.DependentContextTest belows test methods directly use Bean#create method to create actual bean instances. But this method must not be used directly, instead of BeanManager#getReference must be used. Therefore tests are failed. Methods ----------------- testDependentScopedDecoratorsAreDependentObjectsOfBean testDependentScopedInterceptorsAreDependentObjectsOfBean -- 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, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (WELD-563) Using an InterceptorBinding with other targets than {TYPE} or {TYPE, METHOD} should result in a deployment exception

by Marius Bogoevici (JIRA)

Using an InterceptorBinding with other targets than {TYPE} or {TYPE,METHOD} should result in a deployment exception ------------------------------------------------------------------------------------------------------------------- Key: WELD-563 URL: https://jira.jboss.org/browse/WELD-563 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.1.Final Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 1.1.0.BETA1 The exception should be thrown during validation. -- 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, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (WELDX-117) Add support for generic producer methods

by Pete Muir (JIRA)

Add support for generic producer methods ---------------------------------------- Key: WELDX-117 URL: https://jira.jboss.org/browse/WELDX-117 Project: Weld Extensions Issue Type: Feature Request Reporter: Pete Muir Fix For: 1.0.0.Alpha3 -- 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, 9 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues July 2010