November 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-985) Make Tomcat 6 and Jetty 6 and 7 specific configuration obsolete

by Geoffrey De Smet (JIRA)

Make Tomcat 6 and Jetty 6 and 7 specific configuration obsolete --------------------------------------------------------------- Key: WELD-985 URL: https://issues.jboss.org/browse/WELD-985 Project: Weld Issue Type: Feature Request Components: Bootstrap and Metamodel API Reporter: Geoffrey De Smet Priority: Critical According to the documentation: http://docs.jboss.org/weld/reference/1.1.0.Final/en-US/html_single/#d0e5286 We have to add extra configuration files to deploy to certain appservers and certain versions. But the existence of those files can sometimes create issues on other appservers. For example, jetty 6 needs an WEB-INF/jetty-env.xml file (and Jetty 7 needs another version of that file). "Maven profiles" are not a solution, see WELD-984. Since weld-servlet's bootstrap actually detects what appserver and what version is in play, it should be thoroughly investigated if weld can't do that for us and only configure the content of those extra files if the correct appserver/version is being used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
4
0 / 0

[JBoss JIRA] (WELD-1015) Upgrade to SLF4J 1.6.1

by Lukáš Fryč (Created) (JIRA)

Upgrade to SLF4J 1.6.1 ---------------------- Key: WELD-1015 URL: https://issues.jboss.org/browse/WELD-1015 Project: Weld Issue Type: Component Upgrade Affects Versions: 1.1.3.SP1 Reporter: Lukáš Fryč slf4j 1.6.1 is currently widely used version: JBoss AS 7: https://github.com/jbossas/jboss-as/blob/7.1.0.Alpha1/pom.xml#L212 Hibernate: https://github.com/hibernate/hibernate-core/blob/4.0.0.CR6/build.gradle#L44 RichFaces: https://github.com/richfaces/build/blob/4.1.0.20111111-CR1/parent/pom.xml... Seam: https://github.com/seam/parent/blob/master/pom.xml#L76 There seems to be API change between 1.5.10 and 1.6.1. {code} SEVERE: Error configuring application listener of class org.jboss.weld.environment.servlet.Listener java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;Ljava/lang/Throwable;)V {code} -- 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

13 years

3
2
0 / 0

[JBoss JIRA] Created: (WELD-855) Error while catching NonexistentConversationException with Seam Faces/Catch

by Brian Leathem (JIRA)

Error while catching NonexistentConversationException with Seam Faces/Catch --------------------------------------------------------------------------- Key: WELD-855 URL: https://issues.jboss.org/browse/WELD-855 Project: Weld Issue Type: Bug Environment: Glassfish 3.1 M2 (b41), weld 1.1 patched with Stuart's WELD-846 patch. Reporter: Brian Leathem I have a Faces app, with the exception handler: void conversationExpired(@Handles CaughtException<NonexistentConversationException> t) {...} When I pull up a URL with an invalid cid, I get the stacktrace below. (copied from SEAMCATCH-46) Stacktrace: --------------- java.lang.RuntimeException: Exception invoking method [conversationExpired] on object [ca.triumf.mis.qms.workrequest.jsf.exception.ExceptionCatchHandler@264d6a2c], using arguments [org.jboss.seam.exception.control.CaughtException@24758259] at org.jboss.seam.solder.reflection.Reflections.invokeMethod(Reflections.java:547) at org.jboss.seam.solder.reflection.Reflections.invokeMethod(Reflections.java:458) at org.jboss.seam.solder.reflection.annotated.InjectableMethod.invoke(InjectableMethod.java:189) at org.jboss.seam.exception.control.HandlerMethodImpl.notify(HandlerMethodImpl.java:189) at org.jboss.seam.exception.control.ExceptionHandlerDispatch.executeHandlers(ExceptionHandlerDispatch.java:129) 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.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:270) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:222) at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:632) at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:619) at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:613) at org.jboss.seam.faces.exception.CatchExceptionHandler.handle(CatchExceptionHandler.java:81) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:113) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:409) at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1534) at org.apache.catalina.core.ApplicationDispatcher.doInvoke(ApplicationDispatcher.java:787) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:649) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:483) at org.apache.catalina.core.ApplicationDispatcher.doDispatch(ApplicationDispatcher.java:454) at org.apache.catalina.core.ApplicationDispatcher.dispatch(ApplicationDispatcher.java:350) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:300) at org.apache.catalina.authenticator.FormAuthenticator.forwardToLoginPage(FormAuthenticator.java:465) at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:253) at com.sun.web.security.RealmAdapter.invokeAuthenticateDelegate(RealmAdapter.java:1192) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:551) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:623) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98) at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:91) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:162) at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:326) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:170) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.IllegalStateException: Unable to load current conversations from the associated request, something went badly wrong when associate() was called at org.jboss.weld.context.AbstractConversationContext.getCurrentConversation(AbstractConversationContext.java:413) at org.jboss.weld.jsf.ConversationAwareViewHandler.getActionURL(ConversationAwareViewHandler.java:91) at com.sun.faces.application.view.MultiViewHandler.getRedirectURL(MultiViewHandler.java:381) at javax.faces.application.ViewHandlerWrapper.getRedirectURL(ViewHandlerWrapper.java:204) at javax.faces.application.ViewHandlerWrapper.getRedirectURL(ViewHandlerWrapper.java:204) at org.jboss.weld.jsf.ConversationAwareViewHandler.getRedirectURL(ConversationAwareViewHandler.java:134) at com.sun.faces.application.NavigationHandlerImpl.handleNavigation(NavigationHandlerImpl.java:166) at org.jboss.seam.faces.event.SeamPreNavigationHandler.handleNavigation(SeamPreNavigationHandler.java:77) at ca.triumf.mis.qms.workrequest.jsf.exception.ExceptionCatchHandler.conversationExpired(ExceptionCatchHandler.java:27) 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.jboss.seam.solder.reflection.Reflections.invokeMethod(Reflections.java:535) ... 59 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

13
28
0 / 0

[JBoss JIRA] (WELD-1014) Weld does not work with Oracle WebLogic Server 11g (10.3.5)

by George Gastaldi (Created) (JIRA)

Weld does not work with Oracle WebLogic Server 11g (10.3.5) ----------------------------------------------------------- Key: WELD-1014 URL: https://issues.jboss.org/browse/WELD-1014 Project: Weld Issue Type: Bug Reporter: George Gastaldi Weblogic doesn´t seem to run Weld. When configuring the WeldListener, I get the following exception: {code:java} java.lang.IllegalStateException: Singleton is not set at org.jboss.weld.bootstrap.api.helpers.IsolatedStaticSingletonProvider$IsolatedStaticSingleton.get(IsolatedStaticSingletonProvider.java:52) at org.jboss.weld.Container.instance(Container.java:54) at org.jboss.weld.jsf.WeldPhaseListener.instance(WeldPhaseListener.java:161) at org.jboss.weld.jsf.WeldPhaseListener.activateConversations(WeldPhaseListener.java:98) at org.jboss.weld.jsf.WeldPhaseListener.beforePhase(WeldPhaseListener.java:85) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:111) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:508) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) {code} -- 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

13 years

6
14
0 / 0

[JBoss JIRA] Created: (WELD-834) URLScanner can not handle paths containing spaces

by Štěpán Mík (JIRA)

URLScanner can not handle paths containing spaces ------------------------------------------------- Key: WELD-834 URL: https://issues.jboss.org/browse/WELD-834 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.1.0.Final Environment: Windows, Jetty 7.2.2 Reporter: Štěpán Mík When actual classpath includes folder that contains spaces, URLScanner throws an exception (java.io.FileNotFoundException). Problem is at line 93 where string holding URL is "converted" to path just by stripping URL scheme prefix. Unfortunately, spaces in URL are expressed either by plus sing or %20 escape sequence, which remains in file path instead of proper URL decoding. For example "file:/C:/with%20space" is converted to "/C:/with%20space" instead of "C:/with space". -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

6
13
0 / 0

[JBoss JIRA] (CDITCK-237) Implement tests for CDI-2

by Jozef Hartinger (Created) (JIRA)

Implement tests for CDI-2 ------------------------- Key: CDITCK-237 URL: https://issues.jboss.org/browse/CDITCK-237 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 1.1.0.CR1 Implement tests for CDI-2 -- 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

13 years, 1 month

4
3
0 / 0

[JBoss JIRA] (CDITCK-242) Replace EnterpriseArchive with WebArchive where possible

by Martin Kouba (Created) (JIRA)

Replace EnterpriseArchive with WebArchive where possible -------------------------------------------------------- Key: CDITCK-242 URL: https://issues.jboss.org/browse/CDITCK-242 Project: CDI TCK Issue Type: Task Security Level: Public (Everyone can see) Reporter: Martin Kouba Assignee: Martin Kouba -- 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

13 years, 1 month

2
1
0 / 0

[JBoss JIRA] (CDITCK-241) Revise use of TestNG groups

by Martin Kouba (Created) (JIRA)

Revise use of TestNG groups --------------------------- Key: CDITCK-241 URL: https://issues.jboss.org/browse/CDITCK-241 Project: CDI TCK Issue Type: Task Security Level: Public (Everyone can see) Reporter: Martin Kouba Assignee: Martin Kouba -- 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

13 years, 1 month

2
1
0 / 0

[JBoss JIRA] (CDITCK-240) Align the TCK with CDI-136

by Jozef Hartinger (Created) (JIRA)

Align the TCK with CDI-136 -------------------------- Key: CDITCK-240 URL: https://issues.jboss.org/browse/CDITCK-240 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Reporter: Jozef Hartinger Assignee: Martin Kouba Fix For: 1.1.0.CR1 * update TCK assertions * align existing tests with the assertions (see the exclude list in the weld TCK runner) * move tests from the weld testsuite to the TCK (see https://github.com/weld/core/commit/492a517f6fee29886414630224a8b775a28dc662 and https://github.com/weld/core/commit/1e8f00015dc58f7b30129f36c9772f4805d5f993) See CDI-136 for details. -- 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

13 years, 1 month

2
1
0 / 0

[JBoss JIRA] (CDITCK-239) Align the TCK with CDI-141

by Jozef Hartinger (Created) (JIRA)

Align the TCK with CDI-141 -------------------------- Key: CDITCK-239 URL: https://issues.jboss.org/browse/CDITCK-239 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Reporter: Jozef Hartinger Assignee: Martin Kouba Fix For: 1.1.0.CR1 * update TCK assertions * align existing tests with the assertions * move tests from the weld testsuite to the TCK (see https://github.com/weld/core/commit/129e8208d3fe9c1a1238572288eb68ea488fa920) See CDI-141 for details. -- 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

13 years, 1 month

3
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2011