January 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELDX-52) Support Servlet injection on Jetty

by Pete Muir (JIRA)

Support Servlet injection on Jetty ---------------------------------- Key: WELDX-52 URL: https://jira.jboss.org/jira/browse/WELDX-52 Project: Weld Extensions Issue Type: Feature Request Components: Servlet Containers Reporter: Pete Muir Priority: Critical Fix For: Servlet Containers 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

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-215) Deployment issues with numberguess example

by Christian Bauer (JIRA)

Deployment issues with numberguess example ------------------------------------------ Key: WELD-215 URL: https://jira.jboss.org/jira/browse/WELD-215 Project: Weld Issue Type: Bug Components: Examples Affects Versions: 1.0.0.CR1 Reporter: Christian Bauer Priority: Minor The CR1 release has the following issues with /examples/wicket/numberguess: 1. There is an empty org/jboss/webbeans/examples/ directory in the src/ folder. 2. slf4j is completely missing in the WAR, neither API nor implementation is deployed. 3. The main Weld JARs are also missing, only weld-wicket.jar is being deployed. 4. After copying slf4j, log4j, and weld-servlet.jar, I get this exception on startup: Oct 19, 2009 4:17:20 PM org.apache.catalina.core.StandardContext filterStart SEVERE: Exception starting filter wicket.numberguess-example org.apache.wicket.WicketRuntimeException: There is no application attached to current thread main at org.apache.wicket.Application.get(Application.java:179) at org.jboss.weld.wicket.BeanManagerLookup.getBeanManager(BeanManagerLookup.java:76) at org.jboss.weld.wicket.WeldApplication.<init>(WeldApplication.java:39) at org.jboss.weld.examples.wicket.SampleApplication.<init>(SampleApplication.java:5) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72) at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:49) at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:678) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:108) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3800) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4450) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:987) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:909) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:495) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:583) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) (Which is btw the same I get in my own weld-wicket test app after upgrading from webbeans 10-day-old-SVN trunk.) -- 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

14 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (WELDX-36) Dependence on portlet-api due to scanning of a class

by Pete Muir (JIRA)

Dependence on portlet-api due to scanning of a class ---------------------------------------------------- Key: WELDX-36 URL: https://jira.jboss.org/jira/browse/WELDX-36 Project: Weld Extensions Issue Type: Bug Components: Wicket support Reporter: Pete Muir Fix For: Wicket 1.0.0.BETA2 -- 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

14 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (WELD-387) Conversation exceptions not thrown

by Nicklas Karlsson (JIRA)

Conversation exceptions not thrown ---------------------------------- Key: WELD-387 URL: https://jira.jboss.org/jira/browse/WELD-387 Project: Weld Issue Type: Bug Components: Conversations Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson Assignee: Nicklas Karlsson Fix For: 1.0.1.CR1 "If the propagated conversation cannot be restored, the container must associate the request with a new transient conversation and throw an exception of type javax.enterprise.context.NonexistentConversationException from the restore view phase of the JSF lifecycle" and "If the container rejects a request, it must associate the request with a new transient conversation and throw an exception of type javax.enterprise.context.BusyConversationException from the restore view phase of the JSF lifecycle" -- 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

14 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-348) Conversation implementation is not context-aware

by Nicklas Karlsson (JIRA)

Conversation implementation is not context-aware ------------------------------------------------ Key: WELD-348 URL: https://jira.jboss.org/jira/browse/WELD-348 Project: Weld Issue Type: Bug Components: Conversations Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson Assignee: Nicklas Karlsson Priority: Minor Fix For: 1.0.1.CR1 The spec says "If any method of Conversation is called when the conversation scope is not active, a ContextNotActiveException is thrown" this is not the case currently. ConversationImpl needs a reference to the current conversation scope (or lookup it) in order to check the active state on entry There is apparently no TCK coverage for this yet? -- 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

14 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-403) Activate session scope after call to HttpSession.invalidate()

by steven verborgh (JIRA)

Activate session scope after call to HttpSession.invalidate() ------------------------------------------------------------- Key: WELD-403 URL: https://jira.jboss.org/jira/browse/WELD-403 Project: Weld Issue Type: Feature Request Components: Scopes & Contexts Affects Versions: 1.0.0.GA Reporter: steven verborgh Attachments: session_invalidate.tar.bz2 When calling HttpSession.invalidate() and redirecting to a page that uses a SessionScoped Bean a ContextNotActiveException exception gets thrown. This is a different behavior than when using the optional JSF annotations (ManagedBean, SessionScoped) and is also different from the standard HttpRequest behaviour where a call HttpRequest.getSession() by default creates a new Session, even after a call to invalidate in the same request/response cycle. -- 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

14 years, 3 months

4
8
0 / 0

[JBoss JIRA] Created: (WELD-385) Some resources should be looked up from "special" locations according to the EJB spec

by Pete Muir (JIRA)

Some resources should be looked up from "special" locations according to the EJB spec ------------------------------------------------------------------------------------- Key: WELD-385 URL: https://jira.jboss.org/jira/browse/WELD-385 Project: Weld Issue Type: Feature Request Components: Weld SPI Reporter: Pete Muir Fix For: 1.0.1.CR1 For example @Resource TimerService timerService from java:comp/TimerService Need to check the EJB spec for these, and then modify AbstractResourceServices -- 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

14 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-312) AroundInvoke annotation is not honoured by SPI

by Stuart Douglas (JIRA)

AroundInvoke annotation is not honoured by SPI ---------------------------------------------- Key: WELD-312 URL: https://jira.jboss.org/jira/browse/WELD-312 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Reporter: Stuart Douglas When registering interceptors using the SPI weld ignores the information passed in via the AnnotatedMethod object and instead looks for the AroundInvoke annotation using reflection. -- 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

14 years, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (CDITCK-101) /WebProfileMethodSelector Does not work

by Gurkan Erdogdu (JIRA)

/WebProfileMethodSelector Does not work --------------------------------------- Key: CDITCK-101 URL: https://jira.jboss.org/jira/browse/CDITCK-101 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.1.CR1 Reporter: Gurkan Erdogdu /WebProfileMethodSelector includeMethod must contain setStopped(true). -- 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

14 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-99) Decorator Error

by Gurkan Erdogdu (JIRA)

Decorator Error --------------- Key: CDITCK-99 URL: https://jira.jboss.org/jira/browse/CDITCK-99 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu AFAIK, Decorators must implement interface for its decorated types. But org.jboss.jsr299.tck.tests.interceptors.definition.interceptorCalledBeforeDecorator.FooDecorator.FooDecorator does not implement any interface. I think it is error. -- 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

14 years, 3 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues January 2010