March 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-716) <core:transactionListener/> documentation

by Stephan Bublava (JIRA)

<core:transactionListener/> documentation ----------------------------------------- Key: JBSEAM-716 URL: http://jira.jboss.com/jira/browse/JBSEAM-716 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.1.1.GA Reporter: Stephan Bublava Could you please add <core:transactionListener/> (as used in the booking example components.xml) to the reference documentation? (What does it do? In which cases is it needed?) -- 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

18 years, 4 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-843) Seam-gen Enchancement

by Kent Lam (JIRA)

Seam-gen Enchancement --------------------- Key: JBSEAM-843 URL: http://jira.jboss.com/jira/browse/JBSEAM-843 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.1.6.GA Reporter: Kent Lam Priority: Minor Would it be great that seam-gen will generate crud pages and classes for an existing Entity class,just like seam-gen generate the crud pages,classes and entity classes from database. Thanks -- 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

18 years, 4 months

9
26
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-474) Extending the framework using EJB3 components

by Gavin King (JIRA)

Extending the framework using EJB3 components --------------------------------------------- Key: JBSEAM-474 URL: http://jira.jboss.com/jira/browse/JBSEAM-474 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 1.1.0.BETA1, 1.1.0.BETA2 Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.0.CR1 The documentation claims that it is possible to inherit EJB3 components from the framework, but in practice it turns out to not be so easy :-( -- 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

18 years, 5 months

6
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1131) Example web.xml is incomplete

by Christian Bauer (JIRA)

Example web.xml is incomplete ----------------------------- Key: JBSEAM-1131 URL: http://jira.jboss.com/jira/browse/JBSEAM-1131 Project: JBoss Seam Issue Type: Bug Components: Tools Reporter: Christian Bauer I was running into this when using an ajax4jsf tag: SEVERE: Error Rendering View[/docDisplay.xhtml] javax.faces.FacesException: Resources framework is not initialised, check web.xml for Filter configuration at org.ajax4jsf.framework.resource.ResourceBuilderImpl.getWebXml(ResourceBuilderImpl.java:107) at org.ajax4jsf.framework.resource.ResourceBuilderImpl.getUri(ResourceBuilderImpl.java:309) at org.ajax4jsf.framework.resource.InternetResourceBase.getUri(InternetResourceBase.java:211) at org.ajax4jsf.framework.resource.BaseResourceRenderer.encodeBegin(BaseResourceRenderer.java:62) at org.ajax4jsf.framework.resource.OneTimeRenderer.encodeBegin(OneTimeRenderer.java:48) at org.ajax4jsf.framework.resource.BaseResourceRenderer.encode(BaseResourceRenderer.java:45) at org.ajax4jsf.framework.resource.InternetResourceBase.encode(InternetResourceBase.java:306) at org.ajax4jsf.framework.resource.ClientScript.encode(ClientScript.java:143) at org.ajax4jsf.framework.renderer.HeaderResourcesRendererBase.encodeResourcesArray(HeaderResourcesRendererBase.java:131) at org.ajax4jsf.framework.renderer.HeaderResourcesRendererBase.preEncodeBegin(HeaderResourcesRendererBase.java:117) at org.ajax4jsf.framework.renderer.RendererBase.encodeBegin(RendererBase.java:98) at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:512) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:242) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:573) at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:229) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) It only happened right after redeployment, and if the first page I called (with an ajax4jsf tag on it) was behind my rewrite filter, last in web.xml: <filter> <filter-name>UrlRewriteFilter</filter-name> <filter-class>org.tuckey.web.filters.urlrewrite.UrlRewriteFilter</filter-class> <init-param> <param-name>logLevel</param-name> <param-value>WARN</param-value> </init-param> <init-param> <param-name>statusEnabled</param-name> <param-value>false</param-value> </init-param> </filter> <filter-mapping> <filter-name>UrlRewriteFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> Note that this rewrites internally somehow, not with a redirect. If I called, right after deployment, a page with a not rewritten URL and an ajax4jsf tag on it, it would work fine. Interesting enough but after it would work once, even pages that had rewritten URLs worked fine. So there is some initialization issue hidden in this somewhere. After reading this http://jboss.com/index.html?module=bb&op=viewtopic&t=103561 I started playing with random web.xml settings. Take a seam-gen WAR deployment web.xml and make the following modifications: <filter-mapping> <filter-name>ajax4jsf</filter-name> <url-pattern>*.seam</url-pattern> <dispatcher>REQUEST</dispatcher> <dispatcher>FORWARD</dispatcher> <dispatcher>INCLUDE</dispatcher> </filter-mapping> <filter-mapping> <filter-name>Seam Filter</filter-name> <url-pattern>*.seam</url-pattern> </filter-mapping> This seems to work now. I have no idea what happens. Put this on the Java EE 6.0 list: web.xml must be replaced with something that makes sense. Or we need to find a proprietary way to configure a stack of a dozen filters with explicit URL pattern/precedence matching. Maybe we should move this into a Seam config file and initialize the web container programmatically (if that is possible). -- 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

18 years, 6 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1010) RESTful partial page submit with Ajax4JSF

by Gavin King (JIRA)

RESTful partial page submit with Ajax4JSF ----------------------------------------- Key: JBSEAM-1010 URL: http://jira.jboss.com/jira/browse/JBSEAM-1010 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Igor Shabalov Priority: Critical If Ajax4JSF could put page parameters after the # in the URL after a partial submit, then we could make the page bookmarkable. Requires changes to Ajax4JSF, possibly also to Seam. -- 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

18 years, 6 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-990) Check Hotels in Yucatan

by Emmanuel Bernard (JIRA)

Check Hotels in Yucatan ----------------------- Key: JBSEAM-990 URL: http://jira.jboss.com/jira/browse/JBSEAM-990 Project: JBoss Seam Issue Type: Task Affects Versions: 1.2.0.GA, 1.1.7.CR1, 1.1.6.GA, 1.1.5.GA, 1.1.1.GA, 1.1.0.GA, 1.1.0.CR2, 1.1.0.CR1, 1.1.0.BETA2, 1.1.0.BETA1, 1.0.1, 1.0, 1.0 beta 2, 1.0 beta 1 Reporter: Emmanuel Bernard Assigned To: Gavin King Priority: Blocker I can't believe you dared to release the project with such a flaw. It's simply unusable. -- 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

18 years, 6 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-660) Externally switching parameters on a form page backed by "page parameters" constructs yields erratic behaviour

by Giampaolo Tomassoni (JIRA)

Externally switching parameters on a form page backed by "page parameters" constructs yields erratic behaviour -------------------------------------------------------------------------------------------------------------- Key: JBSEAM-660 URL: http://jira.jboss.com/jira/browse/JBSEAM-660 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.0.GA, 1.1.1.GA, 1.1.5.GA, 1.2.0.BETA1 Environment: JBoss-4.0.5.GA Reporter: Giampaolo Tomassoni When a form with "page parameters" is shown and then the same page but with new parameters is attempted by some external action (in example, by manually changing the parameter values in the browser's navigation bar, the page still holds the previous parameter values. This is particularly annoing in frame-based sites, in which a frame is used to "navigate" on the parameter's space of a form in the right frame. -- 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

18 years, 6 months

6
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-568) provide a mechanism to split a datetime into date and time components

by Norman Richards (JIRA)

provide a mechanism to split a datetime into date and time components --------------------------------------------------------------------- Key: JBSEAM-568 URL: http://jira.jboss.com/jira/browse/JBSEAM-568 Project: JBoss Seam Issue Type: Feature Request Reporter: Norman Richards We need a way to support splitting a date+time field into separate date and time fields for an input. The datepicker component could be used to select the date while another component (or even a raw input field) could select the time. Ideally this would be generic enough to be used for other types of a conversations: splitting a pure date object into month + day or a time into hours and minutes. -- 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

18 years, 7 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-907) pages.xml ought to accept plain strings as well as valuebindings

by Peter Muir (JIRA)

pages.xml ought to accept plain strings as well as valuebindings ---------------------------------------------------------------- Key: JBSEAM-907 URL: http://jira.jboss.com/jira/browse/JBSEAM-907 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.6.GA Reporter: Peter Muir Priority: Minor In JSF in most places you can put a vb you can put a string, but in pages.xml you can't (it blows up if you try). This would be useful e.g. <end-task transition="end" /> or <end-task transition="#{foo.transition}" />. Obviously you can just work around this in the Pages parser (if it starts with #{...) but a general solution would be better IMO -- 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

18 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-974) Document Seam dependencies

by Carsten H?hne (JIRA)

Document Seam dependencies -------------------------- Key: JBSEAM-974 URL: http://jira.jboss.com/jira/browse/JBSEAM-974 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Reporter: Carsten H?hne There is a wiki page here: http://wiki.jboss.org/wiki/Wiki.jsp?page=SeamDependencies But this page is not uptodate. I would like to see an apendix to the documentation where all Seam dependencys are described. This appendix can than be updated every new release. -- 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

18 years, 7 months

2
2
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 March 2007