July 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAM-71) Seam-booking example: Unable to find matching navigation case with from-view-id '/home.xhtml' for action '#{identity.login}' with outcome 'failed'

by Marek Schmidt (JIRA)

Seam-booking example: Unable to find matching navigation case with from-view-id '/home.xhtml' for action '#{identity.login}' with outcome 'failed' -------------------------------------------------------------------------------------------------------------------------------------------------- Key: SEAM-71 URL: https://issues.jboss.org/browse/SEAM-71 Project: Seam 3 Distribution Issue Type: Bug Components: Shared Examples Affects Versions: 3.0.0.Final Environment: JBossAS6 Reporter: Marek Schmidt Priority: Minor Fix For: Future In seam-booking example, there is a navigation case missing for the "failed" outcome in the login action, which causes an ugly message to be displayed when entering wrong credentials: Unable to find matching navigation case with from-view-id '/home.xhtml' for action '#{identity.login}' with outcome 'failed' -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-26) Make caught exception available as named bean

by Dan Allen (JIRA)

Make caught exception available as named bean --------------------------------------------- Key: SEAMCATCH-26 URL: https://issues.jboss.org/browse/SEAMCATCH-26 Project: Seam Catch Issue Type: Feature Request Components: Core Implementation Reporter: Dan Allen Assignee: Jason Porter Priority: Minor As we get into error pages, it's going to be useful to have the caught exception available via a named bean. I think this is just a matter of adding a dependent-scoped producer that reads the value of the current CaughtException from a field in the exception dispatcher. In Seam 2, the following two variables were available: org.jboss.seam.caughtException - the original exception that was caught org.jboss.seam.handledException - the exception cause currently being handled I think we could just map org.jboss.seam.caughtException to CaughtException...that way all the info is available, including the exception being handled, the original exception and the unwrapped stack. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
12
0 / 0

[JBoss JIRA] Created: (SEAMFACES-168) Error page navigation after Seam Catch

by Andrew Wheeler (JIRA)

Error page navigation after Seam Catch -------------------------------------- Key: SEAMFACES-168 URL: https://issues.jboss.org/browse/SEAMFACES-168 Project: Seam Faces Issue Type: Feature Request Components: Conversations Affects Versions: 3.0.1 Environment: JBoss AS6, Mojarra 2.1 Reporter: Andrew Wheeler It would be nice to annotate a Seam Catch handler with an error page view that is restored after the exception has been handled. This should tidy (destroy) any active conversation as the view probably can't be restored. It could also mark the event as handled (some default behaviour) if it hasn't been handled by the exception handler method. E.g: @ErrorPage("error") public void noConversationHandler(@Handles CaughtException<NonexistentConversationException> event) { messages.info("The view you were editing has expired."); } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3848) Seam fails to create and inject components when multiple ajax-requests are fired from a commandLink or commandButton, using ajax4jsf.

by etirk etirk (JIRA)

Seam fails to create and inject components when multiple ajax-requests are fired from a commandLink or commandButton, using ajax4jsf. ------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3848 URL: https://jira.jboss.org/jira/browse/JBSEAM-3848 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Environment: windows vista / rhel4 sun jdk5, jdk6 latest versions jboss as 4.2.2 and 4.2.3 firefox2 and 3, ie 6 and 7. Reporter: etirk etirk Fix For: 2.1.2.GA Seam fails to create and inject components when multiple ajax-requests are fired from a commandLink or commandButton, using ajax4jsf. Replication found using seam-booking in examples, trunk as of 081216. Rewrite the find-method in the HotelSearchAction-class, in the seam booking example application. It should look like this. public void find() { page = 0; queryHotels(); try { Thread.sleep(1000 * 5); } catch (InterruptedException ignore) { } } Now, start the application, register a user and enter main.html. Click multiple times on the search hotel button. Depending upon how fast your computer is, you might need to do more than a double-click. Sometimes you may need to klick fast up to 5-8 times. But it will occur. You will end up with an exception that says: Caused by javax.servlet.ServletException with message: javax.el.ELException: /main.xhtml @74,130 rendered=#{hotelSearch.nextPageAvailable}: Error reading nextPageAvailable on type org.javassist.tmp.java.lang.Object_$$_javassist_4 Which in turn comes from a synchronization problem. Caused by org.jboss.seam.core.LockTimeoutException with message: could not acquire lock on @Synchronized component: hotelSearch This is in a way funny, since the hotelSearch-component is not annotated with synchronized. Anyway, our application does not throw an exception like this, but we to have tried synchronizing our involved components, with no luck. Our exception is mostly this Caused by javax.servlet.ServletException with message: javax.el.ELException: /layout/template.xhtml @18,59 rendered=#{authenticator.inSpecialMode}: Error reading inSpecialMode on type se.session.Authenticator_$$_javassist_4 Which in turn comes from the failed injections Caused by org.jboss.seam.RequiredException with message: @In attribute requires non-null value: authenticator.entityManager This problem occurs all over the application, always when an ajax request is double-clicked and seam tries to recreate seam components and runs out of time. In 99% of the case it is the first read property of our authenticator-component that fails, and most often it is that seam cannot create a entityManager to inject, and the system fails due to that the annotation is set to only inject, without create. Removing the entityManager from the component will only result in that seam cannot inject another component instead, until you have no injections left in authenticator, and it still fails! Similar behaviour has been noticed using non-ajax calls, using standard h:commandButton/Link. This is however much more rare. -- 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, 10 months

6
15
0 / 0

[JBoss JIRA] Created: (SEAMFACES-179) s:viewaction not invoked with Mojarra 2.1.2

by Sebastian Sachtleben (JIRA)

s:viewaction not invoked with Mojarra 2.1.2 ------------------------------------------- Key: SEAMFACES-179 URL: https://issues.jboss.org/browse/SEAMFACES-179 Project: Seam Faces Issue Type: Bug Affects Versions: 3.0.2 Environment: JBoss 6.1.0-SNAPSHOT (Hudson build) with updated Weld 1.1.1-Final and updated Mojarra 2.1.2 Reporter: Sebastian Sachtleben s:viewAction will not invoke after updating to Mojarra 2.1.2. Tested with: <f:metadata> <s:viewAction action="#{myBean.validate}"/> </f:metadata> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBSEAM-4500) Seam 2.2.0 based application fails to run if hibernate 4.0.2 GA used

by Ilya Shaikovsky (JIRA)

Seam 2.2.0 based application fails to run if hibernate 4.0.2 GA used -------------------------------------------------------------------- Key: JBSEAM-4500 URL: https://jira.jboss.org/jira/browse/JBSEAM-4500 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.GA Environment: tomcat 6 Reporter: Ilya Shaikovsky https://forum.hibernate.org/viewtopic.php?f=9&t=1001094 I tried to update RF demo dependencies to use JSR-303. Exception on server start just as posted at forum. It seems component just should not be instantiated if misses required dependency. -- 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, 10 months

6
9
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-46) Error while catching NonexistentConversationException

by Brian Leathem (JIRA)

Error while catching NonexistentConversationException ----------------------------------------------------- Key: SEAMCATCH-46 URL: https://issues.jboss.org/browse/SEAMCATCH-46 Project: Seam Catch Issue Type: Bug Components: Framework Integration Affects Versions: 3.0.0.Beta2 Environment: Glassfish 3.1 M2 (b41), weld 1.1 patched with Stuart's WELD-846 patch. Reporter: Brian Leathem Assignee: Jason Porter 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. 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

12 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (SEAMSOCIAL-3) Creating Documentation

by Antoine Sabot-Durand (JIRA)

Creating Documentation ---------------------- Key: SEAMSOCIAL-3 URL: https://issues.jboss.org/browse/SEAMSOCIAL-3 Project: Seam Social Issue Type: Task Affects Versions: 3.0.0.Alpha1 Reporter: Antoine Sabot-Durand Assignee: Antoine Sabot-Durand Fix For: 3.0.0.Alpha1 Have to work on Dockbook to create first documentation for Seam Social -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

5
7
0 / 0

[JBoss JIRA] Created: (JBSEAM-4648) s:defaultAction blocks new lines in <textArea>

by Adrian Mitev (JIRA)

s:defaultAction blocks new lines in <textArea> ---------------------------------------------- Key: JBSEAM-4648 URL: https://jira.jboss.org/jira/browse/JBSEAM-4648 Project: Seam Issue Type: Bug Components: JSF Controls Reporter: Adrian Mitev s:defaultAction shouldn't work if the enter button is presses inside textarea element. To fix the issue wrap the javascript that s:convertEntity generates inside this code: var evt = event.IE ? event.srcElement : event.target; if (evt.tagName.toLowerCase() != 'textarea') { <original javascript here> } -- 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, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBSEAM-4637) Seam does not work with JSF 2.0 faces-config.xml

by Ryan Nideffer (JIRA)

Seam does not work with JSF 2.0 faces-config.xml ------------------------------------------------ Key: JBSEAM-4637 URL: https://jira.jboss.org/jira/browse/JBSEAM-4637 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.2.1.CR1 Reporter: Ryan Nideffer I am attempting to use JSF 2.0 in my Seam application for, among other benefits, composite components. I am able to upgrade the jsf-api.jar and jsf-impl.jar, remove jsf-facelets.jar and my application functions fine, however I am still running in JSF 1.2 mode due to this faces-config.xml: <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"> <view-handler>com.sun.facelets.FaceletViewHandler</view-handler> According to thread comments from a Mojarra developer and the Release Notes for Mojarra 2, all thats needed is to remove the view-handler and reference v2.0 in faces-config. http://forums.java.net/jive/message.jspa?messageID=373539 https://javaserverfaces.dev.java.net/nonav/rlnotes/2.0.1/releasenotes.html As soon as I do this though, I get the following exception when my application is deployed: 2010-04-16 11:24:18,249 INFO [javax.enterprise.resource.webcontainer.jsf.config] (Thread-2) Unsanitized stacktrace from failed start... javax.faces.view.facelets.FaceletException: Must have a Constructor that takes in a ComponentConfig at com.sun.faces.facelets.tag.AbstractTagLibrary$UserComponentHandlerFactory.<init>(AbstractTagLibrary.java:289) ... Caused by: java.lang.NoSuchMethodException: org.jboss.seam.ui.handler.CommandButtonParameterComponentHandler.<init>(javax.faces.view.facelets.ComponentConfig) at java.lang.Class.getConstructor0(Class.java:2706) According to Dan Allen, Seam 2 and JSF 2 work together beautifully: http://seamframework.org/Documentation/DoesSeamWorkWithJSF2 -- 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, 10 months

7
17
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2011