October 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4228) expose rewrite rules

by Duncan Stockdill (JIRA)

expose rewrite rules -------------------- Key: JBSEAM-4228 URL: https://jira.jboss.org/jira/browse/JBSEAM-4228 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.2.CR2 Reporter: Duncan Stockdill The RewriteFilter translates the requests to the internal view URLs and dispatches the request with the rewritten URL. e.g. RequestDispatcher dispatcher = request.getRequestDispatcher(newPath); dispatcher.forward(request, response); As a result, the original URL is lost to processing further down the chain. In some cases it's useful to have access the original URL. Potentially the URL could be stored and made available as an injectable component, but a more generic answer would be to expose the rewrite rules so an internal view can be converted to an external URL programatically. e.g. add matchPatterns or rewritePath to Pages class. -- 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

16 years, 2 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3833) Be able to find out the Event type in observers

by Sanne Grinovero (JIRA)

Be able to find out the Event type in observers ----------------------------------------------- Key: JBSEAM-3833 URL: https://jira.jboss.org/jira/browse/JBSEAM-3833 Project: Seam Issue Type: Feature Request Components: Core Reporter: Sanne Grinovero To "find out" I mean programmatically. As the same method could be listening for more Events, it's possible we need actually to detect all types, not just one, or be sure to be fired once for each event. This is a requirement for PBR-58 -- 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

16 years, 2 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4170) Concurrent call to conversation Exception for first login

by Hunter Lee (JIRA)

Concurrent call to conversation Exception for first login --------------------------------------------------------- Key: JBSEAM-4170 URL: https://jira.jboss.org/jira/browse/JBSEAM-4170 Project: Seam Issue Type: Bug Components: Framework Affects Versions: 2.1.2.CR1 Environment: jboss-4.2.3.GA / jdk1.5.0_16 / Win XP sp3 Reporter: Hunter Lee Priority: Blocker 1. Clean Browser cookies 2. Type an URL that need to login without cid 3. Enter login account and password. 4. expect go to the typed URL directly, but throw an Exception: 11:33:33,921 WARN [SeamPhaseListener] uncaught exception, passing to exception handler org.jboss.seam.ConcurrentRequestTimeoutException: Concurrent call to conversation at org.jboss.seam.core.Manager.restoreAndLockConversation(Manager.java:641) at org.jboss.seam.core.Manager.restoreConversation(Manager.java:603) at org.jboss.seam.jsf.SeamPhaseListener.afterRestoreView(SeamPhaseListener.java:392) at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:230) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:196) at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:175) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:114) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:104) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:445) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292) at org.jboss.seam.web.RewriteFilter.process(RewriteFilter.java:98) at org.jboss.seam.web.RewriteFilter.doFilter(RewriteFilter.java:57) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:532) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) 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.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517) 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:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) 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:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:366) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) 11:33:33,937 ERROR [CachedConnectionValve] Application error: default did not complete its transaction -- 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

16 years, 2 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1687) Include GanttChart into Charting

by Samuel Mendenhall (JIRA)

Include GanttChart into Charting -------------------------------- Key: JBSEAM-1687 URL: http://jira.jboss.com/jira/browse/JBSEAM-1687 Project: JBoss Seam Issue Type: Feature Request Reporter: Samuel Mendenhall Priority: Minor Including GanttChart into Seams charting package. -- 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

16 years, 2 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-560) seam new-query

by Gavin King (JIRA)

seam new-query -------------- Key: JBSEAM-560 URL: http://jira.jboss.com/jira/browse/JBSEAM-560 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Gavin King Assigned To: Norman Richards To generate a stub query page -- 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

16 years, 2 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4190) RewriteFilter is Non-deterministic

by John Gilbert (JIRA)

RewriteFilter is Non-deterministic ---------------------------------- Key: JBSEAM-4190 URL: https://jira.jboss.org/jira/browse/JBSEAM-4190 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: John Gilbert The RewriteFilter is non-deterministic in some cases. An example serves best. Here are the rewrite rules I would like: /Customer/edit/{id} -> /jsf/Customer/Edit.xhtml /Customer/create -> /jsf/Customer/Edit.xhtml /Customer/{id} -> /jsf/Customer/View.xhtml When debugging the value of RewriteFilter.getAllPatterns(), the order of the two rules for /jsf/Customer/Edit.xhtml are always preserved. However, because Pages.getKnownViewIds() returns a HashSet there is no guarantee that the rules for /jsf/Customer/View.xhtml will come after the rules for /jsf/Customer/Edit.xhtml. As a result, /Customer/create sometimes translates to /jsf/Customer/View.xhtml when /jsf/Customer/View.xhtml is returned first in the set. There are several possible solutions: 1) Change /Customer/{id} to /Customer/view/{id}. However, this is not the best url for a View. 2) Change Pages.pagesByViewId to a TreeMap. This is the patch I am currently using, but it is only guaranteed for my patterns. 3) Change RewriteFilter.getAllPatterns() to returns a TreeSet sorted from longest to shortest. This is similar to the way Pages.wildcardViewIds works. -- 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

16 years, 2 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1758) DocumentStorePhaseListener fails if installed before SeamPhaseListener when used in a portlet

by Chris Rudd (JIRA)

DocumentStorePhaseListener fails if installed before SeamPhaseListener when used in a portlet --------------------------------------------------------------------------------------------- Key: JBSEAM-1758 URL: http://jira.jboss.com/jira/browse/JBSEAM-1758 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Reporter: Chris Rudd When the DocumentStorePhaseListener is installed before the SeamPhaseListener (this can happend when the jboss-seam.jar sits in the ear, and the jboss-seam-pdf.jar sits in the war) in a portlet environment, a "No active application context" exception is thrown during Portlet.render. This is becaus the SeamPhaseListener hasn't had a chance to setup the Seam contexts yet. I would suggest changing the code so that it responds to the Phase events that the SeamPhaseListener publishes ( org.jboss.seam.beforePhase ) so that its guaranteed to be executed after the SeamPhaseListener has property set things up. -- 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

16 years, 2 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2069) itext example tests

by Norman Richards (JIRA)

itext example tests ------------------- Key: JBSEAM-2069 URL: http://jira.jboss.com/jira/browse/JBSEAM-2069 Project: JBoss Seam Issue Type: Task Reporter: Norman Richards Assigned To: Norman Richards Priority: Minor Fix For: 2.0.0.GA -- 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

16 years, 2 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4012) NotBoundException when undeploying Seam examples on AS5

by Pete Muir (JIRA)

NotBoundException when undeploying Seam examples on AS5 ------------------------------------------------------- Key: JBSEAM-4012 URL: https://jira.jboss.org/jira/browse/JBSEAM-4012 Project: Seam Issue Type: Bug Components: EJB3, Examples Affects Versions: 2.1.0.SP1 Environment: JDK 6 AS 5 trunk Seam trunk r9564 Reporter: Jozef Hartinger Assignee: Norman Richards Fix For: 2.1.2.CR1 I am getting NotBoundException when undeploying Seam example when @Remove method is being called on statefull session bean. Affected examples are booking, dvdstore, nestedbooking, icefaces. Basic interaction with the example is needed before undeployment to reproduce the problem. -- 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

16 years, 2 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4209) StringIndexOutOfBoundsException in RedirectHandler

by Nicko Cadell (JIRA)

StringIndexOutOfBoundsException in RedirectHandler -------------------------------------------------- Key: JBSEAM-4209 URL: https://jira.jboss.org/jira/browse/JBSEAM-4209 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.CR2 Reporter: Nicko Cadell StringIndexOutOfBoundsException in RedirectHandler This exception is thrown if ViewExpiredException is thown and I'm hndling this with a redirect back to the same page: i.e. my exception config looks like: {code} <exception class="javax.faces.application.ViewExpiredException"> <redirect /> </exception> {code} AND I am using the <web:rewrite-filter /> to rewrite the URLs. The code in RedirectHandler assumes that the request servlet path will contain a URL that matches up to one of the view by changing the file extension. This is not always the case. In this case the RewriteFilter is intercepting the path, which does not contain a .seam extension. The following exception is thrown: {code} java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1938) at org.jboss.seam.exception.RedirectHandler.handle(RedirectHandler.java:39) 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.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:368) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:495) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) {code} It looks like the RewriteFilter process() method does have some commented out code to wrap the request so that the call to getServletPath() would return the rewritten URL (i.e. something that could be converted to a view id by the RedirectHandler). I assume that the wrapped request was commented out to resolve some other issue. -- 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

16 years, 2 months

4
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2009