February 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-901) Enhance Conversation.endAndRedirect with a boolean parameter to specify destruction of the conversation before the redirect

by Mike Quilleash (JIRA)

Enhance Conversation.endAndRedirect with a boolean parameter to specify destruction of the conversation before the redirect --------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-901 URL: http://jira.jboss.com/jira/browse/JBSEAM-901 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash At the moment this can be achieved by Extracting the parent conversation id from Manager Calling endBeforeRedirect() Doing a Redirect.execute() manually. Would be handy just to be able to do "Conversation.endAndRedirect( true )" Either that or have a method to set the destroyBeforeRedirect flag. Conversation.setDestroyBeforeRedirect( true ); Conversation.endAndRedirect(); -- 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

19 years, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-741) auto-redirect to HTTPS

by Gavin King (JIRA)

auto-redirect to HTTPS ---------------------- Key: JBSEAM-741 URL: http://jira.jboss.com/jira/browse/JBSEAM-741 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.2.0.BETA1 We should make it easy to direct the request to https. We should also validate that requests that *should* be https actually *are* https. -- 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

19 years, 1 month

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-900) Seam taglibrary descriptor not recogniced

by Carsten H?hne (JIRA)

Seam taglibrary descriptor not recogniced ----------------------------------------- Key: JBSEAM-900 URL: http://jira.jboss.com/jira/browse/JBSEAM-900 Project: JBoss Seam Issue Type: Patch Components: JSF Affects Versions: 1.1.6.GA Reporter: Carsten H?hne The taglib.tld file in src/ui/META-INF has an omission It looks like <?xml version="1.0"?> <taglib xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd" version="2.0"> The schemalocation is missing one element. I think it should be read like this: <?xml version="1.0"?> <taglib xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd" version="2.0"> Without this change i cannot bring the tld in the exadel palette for using drag and drop of components -- 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

19 years, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-902) Make persistenceContextName configurable

by Carsten H?hne (JIRA)

Make persistenceContextName configurable ---------------------------------------- Key: JBSEAM-902 URL: http://jira.jboss.com/jira/browse/JBSEAM-902 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 1.1.6.GA Reporter: Carsten H?hne The persistenceContextName is hardcoded to EntityHome: entityManager HibernateEntityHome: session For the sake of readability i suggest to make it configurable. I can name my core:managed-hibernate-session or core:managed-persistence-context whatever i like in components.xml. It is an nice idea to set the name of these things used by the framework also in components.xml perhaps like framework:hibernate-session-name framework:persistence-context-name or whatever you like best. -- 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

19 years, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-899) Throw exception for dupe <navigation> elements on a page

by Gavin King (JIRA)

Throw exception for dupe <navigation> elements on a page -------------------------------------------------------- Key: JBSEAM-899 URL: http://jira.jboss.com/jira/browse/JBSEAM-899 Project: JBoss Seam Issue Type: Bug Components: JSF Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.7.GA They all must have distinct view-ids. -- 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

19 years, 1 month

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-849) Extending loading way for configuration files

by Fernando Monta￱ño (JIRA)

Extending loading way for configuration files --------------------------------------------- Key: JBSEAM-849 URL: http://jira.jboss.com/jira/browse/JBSEAM-849 Project: JBoss Seam Issue Type: Feature Request Reporter: Fernando Monta￱ño There sould be an altervative way to load the Seam XML configuration files. I think you should include some way (alternative to fine grained configuration) which we can use to configure the configuration files we want to load (pages.xml, components.xml...etc). Maybe adding something like (web.xml): <context-param>  <param-name>seam.pages.CONFIG_FILES</param-name> <param-value>/WEB-INF/pages-module1.xml</param-value> </context-param> -- 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

19 years, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-890) UISelectItems leaks memory/state

by Guy Veraghtert (JIRA)

UISelectItems leaks memory/state -------------------------------- Key: JBSEAM-890 URL: http://jira.jboss.com/jira/browse/JBSEAM-890 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.1.7.GA Reporter: Guy Veraghtert When you use UISelectItems with a no selection label, a ConverterChain is set as the converter of the component. As the converter is part of the component state, upon a postback that converchain will be restored. However, when addNoSelectionLabel() is called in UISelectItems (this method is called indirectly when getValue() is called), a new ConverterChain instance is created and set as the converter of the component, the original converter of that component (which was already a converterchain) will be added to the new ConverterChain. As a result, NoSelectionConverter will be added to the chain more than once, and worse: memory leaks/state grows and grows when multiple postbacks are made to the same page (as the chain grows and grows). -- 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

19 years, 1 month

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-763) Dropdown for Year and for Month in <s:selectDate>

by Ciro Cavani (JIRA)

Dropdown for Year and for Month in <s:selectDate> ------------------------------------------------- Key: JBSEAM-763 URL: http://jira.jboss.com/jira/browse/JBSEAM-763 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.1.5.GA Reporter: Ciro Cavani Priority: Optional Like in Tomahawk for cases like Birthdays that are some years in past and (my case) date parameters for historic data (from 1999) -- 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

19 years, 1 month

7
26
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-838) Should not require empty drl file to use security

by Gavin King (JIRA)

Should not require empty drl file to use security ------------------------------------------------- Key: JBSEAM-838 URL: http://jira.jboss.com/jira/browse/JBSEAM-838 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Priority: Minor Fix For: 1.1.7.GA I'm not sure if this is actually right, but the booking example as an empty drl file. This should not be required. It should work even if you specify no rule base, or at leat no rule file for th rule base. -- 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

19 years, 1 month

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-896) seamspace ContentServlet broken

by Gavin King (JIRA)

seamspace ContentServlet broken ------------------------------- Key: JBSEAM-896 URL: http://jira.jboss.com/jira/browse/JBSEAM-896 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 1.1.7.GA Reporter: Gavin King Assigned To: Shane Bryzak Priority: Blocker Fix For: 1.1.7.GA 14:21:01,472 ERROR [[Content Servlet]] Servlet.service() for servlet Content Servlet threw exception java.lang.IllegalStateException: No application context active at org.jboss.seam.Component.forName(Component.java:1531) at org.jboss.seam.Component.getInstance(Component.java:1581) at org.jboss.seam.Component.getInstance(Component.java:1564) at org.jboss.seam.Component.getInstance(Component.java:1543) at org.jboss.seam.Component.getInstance(Component.java:1538) at org.jboss.seam.example.seamspace.ContentServlet.doGet(ContentServlet.java:66) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:42) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:53) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:613) -- 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

19 years, 1 month

2
1
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 February 2007