February 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-510) Support for Portlet 2.0

by Neil Griffin (JIRA)

Support for Portlet 2.0 ----------------------- Key: WELD-510 URL: https://jira.jboss.org/jira/browse/WELD-510 Project: Weld Issue Type: Feature Request Affects Versions: 1.0.1.Final Reporter: Neil Griffin There are some folks trying to use the PortletFaces Bridge for JSF 2.0 + Portlet 2.0 in Glassfish V3, but Weld is causing an issue. Original Post: http://www.portletfaces.org/community/forums/-/message_boards/message/430... Here is a simple stacktrace of the problem: Caused by: java.lang.IllegalStateException: Weld doesn not support using JSF in an non-servlet environment at org.jboss.weld.jsf.JsfHelper.getModuleBeanManager(JsfHelper.java:119) at org.jboss.weld.jsf.WeldPhaseListener.initiateSessionAndConversation(WeldPhaseListener The code for the bridge API is here: http://svn.portletfaces.org/svn/portletfaces/bridge/org.portletfaces.brid... The code for the bridge IMPL is here: http://svn.portletfaces.org/svn/portletfaces/bridge/org.portletfaces.brid... And the code for a sample portlet is here: http://svn.portletfaces.org/svn/portletfaces/portlets/sample/jsf-2.0-job-... -- 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

11 years, 11 months

12
36
0 / 0

[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

3
4
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

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

2
4
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

3
6
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, 1 month

6
10
0 / 0

[JBoss JIRA] Created: (WELD-537) More details to WELD-000072 Managed bean declaring a passivating scope must be passivation capable.

by Nicklas Karlsson (JIRA)

More details to WELD-000072 Managed bean declaring a passivating scope must be passivation capable. --------------------------------------------------------------------------------------------------- Key: WELD-537 URL: https://jira.jboss.org/browse/WELD-537 Project: Weld Issue Type: Feature Request Components: Class Beans (Managed and Session) Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson The error message should be more detailed, currently ManagedBean.initializeAfterBeanDiscovery can have multiple conditions that set the passivationCapableBean to false (non-serializable interceptors etc) but it's hard to tell exactly what is wrong. -- 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, 1 month

5
8
0 / 0

[JBoss JIRA] Created: (WELD-580) Around-Invoke Interceptors with wrong signature should cause DefinitionException

by Aslak Knutsen (JIRA)

Around-Invoke Interceptors with wrong signature should cause DefinitionException -------------------------------------------------------------------------------- Key: WELD-580 URL: https://jira.jboss.org/browse/WELD-580 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.1.Final Reporter: Aslak Knutsen Around-invoke methods have the following signature: Object <METHOD>(InvocationContext) throws Exception Interceptors that does not follow that should cause a DefinitionException. In current impl they are registered, enabled but can not be resolved on Bean lookup. -- 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, 1 month

7
17
0 / 0

[JBoss JIRA] Created: (WELD-687) Refactoring InstantiatorFactory to allow per-deployment configuration

by Marius Bogoevici (JIRA)

Refactoring InstantiatorFactory to allow per-deployment configuration --------------------------------------------------------------------- Key: WELD-687 URL: https://jira.jboss.org/browse/WELD-687 Project: Weld Issue Type: Feature Request Affects Versions: 1.1.0.Beta1 Reporter: Marius Bogoevici Fix For: 1.1.0.Beta2 InstantiatorFactory is currently using static fields for storing the enabled/disabled status for unsafe instantiators, as well as the instantiator that should be used. In a shared library scenario, the instantiator factory will be enabled if at least one of the deployed applications contains the META-INF/org.jboss.weld.enableUnsafeProxies resource. -- 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, 1 month

6
14
0 / 0

[JBoss JIRA] Created: (WELD-571) Interceptors not working for dependent scoped beans when using InjectionTarget

by Francois Swiegers (JIRA)

Interceptors not working for dependent scoped beans when using InjectionTarget ------------------------------------------------------------------------------ Key: WELD-571 URL: https://jira.jboss.org/browse/WELD-571 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: Francois Swiegers When creating an intercepted bean of dependent scope using an InjectionTarget, the interceptor is not active. -- 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, 1 month

5
18
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues February 2011