October 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-204) TCK Harness property configuration broken

by Sivakumar Thyagarajan (JIRA)

TCK Harness property configuration broken ----------------------------------------- Key: CDITCK-204 URL: https://issues.jboss.org/browse/CDITCK-204 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Sivakumar Thyagarajan As per http://docs.jboss.org/cdi/tck/reference/latest/en-US/html/test-harness-co..., a custom ConfigurationBuilder or an implementation of the SPI class such as org.jboss.jsr299.tck.spi.Beans could be provided by the TCK executor through a system property specifying the FQCN of the implementation class. However while trying to plug in a custom Beans SPI implementation or a ConfigurationBuilder using the system property, the default PropertiesBasedConfigurationBuilder seems to collate [1] all the properties file in the classpath and include the default implementations (bundled in the porting package or harness) as well. > [testng] Exception in thread "main" java.lang.IllegalArgumentException: More than one implementation of Beans specified by org.jboss.jsr299.tck.spi.Beans, not sure which one to use! > [testng] at org.jboss.testharness.properties.PropertiesManager.getClassValue(PropertiesManager.java:159) > [testng] at org.jboss.testharness.properties.PropertiesManager.getInstanceValue(PropertiesManager.java:169) > [testng] at org.jboss.testharness.impl.PropertiesBasedConfigurationBuilder.getInstanceValue(PropertiesBasedConfigurationBuilder.java:62) This prevents configuration of the TCK to use a custom SPI class implementation and/or ConfigurationBuilder. The only workaround seems to be providing a modified version of the existing porting package class and ensuring that it is loaded ahead. [1] [1] http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (CDITCK-220) BuiltInBeansTest.testUserTransactionBean()

by David Blevins (JIRA)

BuiltInBeansTest.testUserTransactionBean() ------------------------------------------ Key: CDITCK-220 URL: https://issues.jboss.org/browse/CDITCK-220 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: David Blevins We're passing this test, but wanted to drop a note that it should be updated. We just need to update this bean like so: {code} @Stateful @TransactionManagement(BEAN) public class UserTransactionInjectedBean implements UserTransactionInjectedBeanLocal { @Inject transient UserTransaction userTransaction; public UserTransaction getUserTransaction() { return userTransaction; } } {code} Only @Stateful session bean explicitly marked as @TransactionManagement(BEAN) are allowed to get UserTransaction via lookup or injection, the EJB TCK tests cover this pretty well. In OpenEJB we have deploy-time checks for this if @Resource is used to get a UserTransaction and we'd like to expand that checking to properly cover @Inject injection as well. Even though we are currently injecting that object and passing the test, it's a "false" pass and at runtime that UserTransaction object is hardwired to throw exceptions if used by a non-CMT bean. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (CDITCK-51) Support EEJB environment in harness

by Pete Muir (JIRA)

Support EEJB environment in harness ----------------------------------- Key: CDITCK-51 URL: https://jira.jboss.org/jira/browse/CDITCK-51 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Infrastructure Affects Versions: 1.0.0.GA Reporter: Pete Muir Fix For: 1.1.0.CR1 -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-42) Investigate using dependency:copy-dependencies rather than dependency:copy as it looks in the reactor

by Pete Muir (JIRA)

Investigate using dependency:copy-dependencies rather than dependency:copy as it looks in the reactor ----------------------------------------------------------------------------------------------------- Key: CDITCK-42 URL: https://jira.jboss.org/jira/browse/CDITCK-42 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Infrastructure Reporter: Pete Muir Fix For: 1.0.0.CR3 -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (CDITCK-223) EnterpriseBeanLifecycleTest.testCreateSFSB

by David Blevins (JIRA)

EnterpriseBeanLifecycleTest.testCreateSFSB ------------------------------------------ Key: CDITCK-223 URL: https://issues.jboss.org/browse/CDITCK-223 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: David Blevins This test is good except the last part where it checks for Serializable as an interface: {code} // Verify that the instance returned is a proxy by checking for all local interfaces assert getCurrentConfiguration().getBeans().isProxy(stadtInstance); Set<Class> interfaces = new HashSet<Class>(Arrays.asList(stadtInstance.getClass().getInterfaces())); Class c = stadtInstance.getClass(); Class[] cs = c.getInterfaces(); assert interfaces.contains(KleinStadt.class); assert interfaces.contains(SchoeneStadt.class); assert interfaces.contains(Serializable.class); {code} It isn't valid to check Serializable is a business local interface. Remote proxies are required to be serializable, but there's no explicit requirement for local proxies. Most vendors may do that for internal purposes (makes supporting passivation easier), but that's not something CDI needs to worry about. Our proxies actually are serializable -- they just don't implement the interface directly. It's done through another internal interface that takes care of a few other details, so this assert fails. On that note, we should probably change these asserts to: {code} // Verify that the instance returned is a proxy by checking for all local interfaces assert getCurrentConfiguration().getBeans().isProxy(stadtInstance); assert stadtInstance instanceof KleinStadt; assert stadtInstance instanceof SchoeneStadt; {code} Probably CDI doesn't need to care about the details on how the vendor ensures a proxy is assignable to the business local interfaces. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (WELD-845) Do not bundle slf4j static logger binding in weld-servlet.jar

by Kariem Hussein (JIRA)

Do not bundle slf4j static logger binding in weld-servlet.jar ------------------------------------------------------------- Key: WELD-845 URL: https://issues.jboss.org/browse/WELD-845 Project: Weld Issue Type: Feature Request Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.1.0.Final Reporter: Kariem Hussein Bundling a static logger implementation with the weld-servlet.jar generates a warning that would not be necessary. The weld-servlet.jar (_uber jar_) is still (or arguably more) useful without the binding. Opened this ticket as [requested by Pete|http://seamframework.org/Community/Slf4jBindingInWeldservletjar#comm...] in response to a forum thread. This could be done similar to WELDSE-12 (requested in [this comment|https://issues.jboss.org/browse/WELDSE-12?focusedCommentId=125079...]). Assumed that WELDX and it successor SOLDER are not the right projects for this request. Related forum posts: * [slf4j Binding in weld-servlet.jar|http://seamframework.org/Community/Slf4jBindingInWeldser...] * [slf4j StaticLoggerBinder - This code should have never made it into the jar|http://seamframework.org/Community/Slf4jStaticLoggerBinderThisCodeSho...] * [Weld SE and slf4j|http://seamframework.org/Community/WeldSEAndSlf4j] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
6
0 / 0

[JBoss JIRA] (CDITCK-235) Add tests for BM injection into container event observers

by Jozef Hartinger (Created) (JIRA)

Add tests for BM injection into container event observers --------------------------------------------------------- Key: CDITCK-235 URL: https://issues.jboss.org/browse/CDITCK-235 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.4.Final Reporter: Jozef Hartinger Fix For: 1.1.0.CR1 {quote}Service providers may have observer methods, which may observe any event, including any container lifecycle event, and obtain an injected BeanManager reference.{quote} It's probably a failure to inject BeanManager in BeforeBeanDiscovery which causes https://issues.apache.org/jira/browse/TOMEE-33 Currently, the TCK tests the BM injection for the following types of events: * AfterBeanDiscovery * AfterDeploymentValidation We should extend the coverage and test every kind of container lifecycle event (BeforeBeanDiscovery, ProcessAnnotatedType, ...). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDRAD-30) There is no org.jboss.weld.environment.tomcat.WeldLifecycleListener in weld-servlet

by hantsy bai (JIRA)

There is no org.jboss.weld.environment.tomcat.WeldLifecycleListener in weld-servlet ----------------------------------------------------------------------------------- Key: WELDRAD-30 URL: https://issues.jboss.org/browse/WELDRAD-30 Project: Weld Archetypes Issue Type: Bug Reporter: hantsy bai I created a web project from jsf-weld-servlet archetype, and uncommented the following in META-INF/context.xml, when I started tomcat, it threw exceptions   I exploered the weld-servlet jar file, I can not find this class. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-911) Shared dependent instance injection with circular reference through decorator

by Christian Bauer (JIRA)

Shared dependent instance injection with circular reference through decorator ----------------------------------------------------------------------------- Key: WELD-911 URL: https://issues.jboss.org/browse/WELD-911 Project: Weld Issue Type: Bug Components: Scopes & Contexts Affects Versions: 1.1.1.Final Reporter: Christian Bauer CDI spec section 6.4 says about @Dependent that "No injected instance of the bean is ever shared between multiple injection points." The following test shows that the same instance of @Dependent Foo is shared between multiple injection points, one in TestDecoratorInjection, the other in BarDecorator. {code} import org.jboss.weld.environment.se.Weld; import org.jboss.weld.environment.se.WeldContainer; import javax.annotation.PostConstruct; import javax.decorator.Decorator; import javax.decorator.Delegate; import javax.enterprise.inject.Any; import javax.inject.Inject; import javax.inject.Singleton; @Singleton public class TestDecoratorInjection { public static final Weld weld = new Weld(); public static final WeldContainer weldContainer = weld.initialize(); public static void main(final String[] args) throws Exception { weldContainer.instance().select(TestDecoratorInjection.class).get().test(); } @Inject Foo foo; // Dependent instance of TestDecoratorInjection void test() { foo.test(); } public static class Foo { @PostConstruct void init() { System.out.println("INIT FOO"); } @Inject Bar bar; // Dependent instance of Foo void print() { System.out.println("FOO"); } void test() { bar.print(); } } public static interface Bar { void print(); } public static class BarImpl implements Bar { @Override public void print() { System.out.println("Bar"); } } @Decorator public static abstract class BarDecorator implements Bar { @Inject @Delegate @Any Bar delegate; @Inject Foo foo; // Dependent instance of what?! @Override public void print() { foo.print(); } } } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (WELD-760) Duplicate interceptor: More than one jar

by Robson Saraiva Ximenes (JIRA)

Duplicate interceptor: More than one jar ---------------------------------------- Key: WELD-760 URL: https://jira.jboss.org/browse/WELD-760 Project: Weld Issue Type: Bug Components: Weld SPI Affects Versions: 1.0.1.Final Environment: Just Weld 1.0.1.Final Reporter: Robson Saraiva Ximenes Assignee: Marius Bogoevici I'm getting the following error when I try to use my Interceptor: Duplicate interceptor class definition... The entire description for this issue was related here: http://seamframework.org/Community/AnotherInterceptorProblem -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues October 2011