June 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4621) Page Navigation exception after upgrading to JSF 2.0

by Sheng Gu (JIRA)

Page Navigation exception after upgrading to JSF 2.0 ---------------------------------------------------- Key: JBSEAM-4621 URL: https://jira.jboss.org/jira/browse/JBSEAM-4621 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.1.CR1 Environment: Seam 2.2.1.CR1 + JSF 2.0 Sun Reporter: Sheng Gu Priority: Blocker Fix For: 2.2.1.CR2 Hi there, After upgrading to JSF2.0, I got the following exceptions. The login.xhtml and login.page.xml codes are listed as follows: login.xhtml: <h:commandButton value="LOGIN" action="#{identity.login}"/> <h:commandButton value="SIGN UP!" action="register" immediate="true"/> login.page.xml: <?xml version="1.0" encoding="UTF-8"?> <page xmlns="http://jboss.com/products/seam/pages" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.com/products/seam/pages http://jboss.com/products/seam/pages-2.2.xsd"> <end-conversation before-redirect="true" root="true"/> <navigation from-action="#{identity.login}"> <rule if="#{identity.loggedIn}"> <end-conversation before-redirect="true" root="true"/> <redirect view-id="/home.xhtml" /> </rule> </navigation> <navigation from-action="register"> <begin-conversation join="false"/> <redirect view-id="/register.xhtml" /> </navigation> </page> java.lang.IllegalStateException at org.apache.catalina.connector.ResponseFacade.sendRedirect(ResponseFacade.java:435) at org.jboss.seam.mock.MockExternalContext.redirect(MockExternalContext.java:528) at org.jboss.seam.faces.FacesManager.redirect(FacesManager.java:220) at org.jboss.seam.faces.FacesManager.redirect(FacesManager.java:185) at org.jboss.seam.faces.Navigator.redirect(Navigator.java:55) at org.jboss.seam.faces.Navigator.redirect(Navigator.java:42) at org.jboss.seam.exception.RedirectHandler.handle(RedirectHandler.java:51) at org.jboss.seam.exception.Exceptions.handle(Exceptions.java:76) at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) -- 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 months

4
10
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-71) Improve LDAP integration in general

by Thorsten Kunz (JIRA)

Improve LDAP integration in general ----------------------------------- Key: SEAMSECURITY-71 URL: https://issues.jboss.org/browse/SEAMSECURITY-71 Project: Seam Security Issue Type: Feature Request Affects Versions: 3.0.0.Final Reporter: Thorsten Kunz As described in the forum thread right now getting LDAP integration to work is quite the project since there a features missing (in Seam Security as well as PicketLink IDM) and there is little to no documentation on how to enable Seam Security to use PicketLink IDM LDAP integration. It would be very nice if Seam Security would have the same level of LDAP usability that Seam 2 has. At least it should be possible to enable simple LDAP integration by XML configuration only without the need to implement any classes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

6
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2896) component set for generating excel documents

by Dan Allen (JIRA)

component set for generating excel documents -------------------------------------------- Key: JBSEAM-2896 URL: http://jira.jboss.com/jira/browse/JBSEAM-2896 Project: Seam Issue Type: Feature Request Components: JSF Controls Affects Versions: 2.1.0.A1, 2.0.2.CR1, 2.0.1.GA Reporter: Dan Allen Fix For: 2.1.x We should mirror the functionality of creating PDF documents from Facelets templates and create a component set that generates excel documents. There are two approaches we can take. One approach is to use POI to build the document structure and then export it. The second approach is to build an XML document that Excel can understand. Technically there is no reason to actually produce a binary Excel document as long as we can feed something that Excel knows how to convert. Regular CSV support would be nice too, but I always find that to be such a cop out. Creating this module shouldn't be too technically challenging since most of the infrastructure has been set up already when creating the PDF components. In fact, i would start by working in that module and then split it out into another JAR. Some resource links: http://www.codeproject.com/KB/office/excelxmllibrary.aspx http://xelem.sourceforge.net/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
27
0 / 0

[JBoss JIRA] Created: (JBSEAM-4756) Update Seam drools libraries to Drools 5.1

by Alessandro Lazarotti (JIRA)

Update Seam drools libraries to Drools 5.1 ------------------------------------------ Key: JBSEAM-4756 URL: https://issues.jboss.org/browse/JBSEAM-4756 Project: Seam Issue Type: Feature Request Environment: fedora 12, jdk 1.6, Seam 2.2, Guvnor 5.1 and drools-expert 5.1 Reporter: Alessandro Lazarotti Is necessary update drools libs to be compatible with Guvnor 5.1 serialization process -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (SEAMFACES-5) ContextualHttpServletRequest

by Nicklas Karlsson (JIRA)

ContextualHttpServletRequest ---------------------------- Key: SEAMFACES-5 URL: https://jira.jboss.org/jira/browse/SEAMFACES-5 Project: Seam Faces Issue Type: Feature Request Reporter: Nicklas Karlsson Assignee: Lincoln Baxter III (actually a Seam Servlet thing) A similar construct to the Seam 2 ContextualHttpServletRequest that can be used for running contextual stuff where the contexts are not automatically available (work already started) -- 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 months

3
5
0 / 0

[JBoss JIRA] Created: (JBSEAM-4722) Build seam2.5

by he youlin (JIRA)

Build seam2.5 ------------- Key: JBSEAM-4722 URL: https://jira.jboss.org/browse/JBSEAM-4722 Project: Seam Issue Type: Feature Request Affects Versions: 2.2.1.CR2 Reporter: he youlin Priority: Optional I think seam team should consider building seam 2.5 version so we can upgrade our old project to jsf2.0,ejb3.1,hibernate 3.6,beanvalidation,glassfish3 or jboss6 and get rid of hibernate3.2 validation and richfaces3 dependcy. I have upgraded my old project a few months ago from seam2.2 to use jsf2.1,hibernate 3.6,beanvalidation,granite-seam21,spring3.05 under tomcat 7.0.5-dev and used in the production environment.I test it on glassfish v3.1 and jboss6 but not test ejb. If considered i can provide my patch to seam team as a reference or push full source code to github with your team permission. Please consider. heyoulin -- 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, 2 months

6
16
0 / 0

[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, 3 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, 3 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, 3 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, 3 months

6
15
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2011