April 2011 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2697) Add attribute to s:link tag to make creation of magic dataModelSelection URL parameter optional

by Wolfgang Schwendt (JIRA)

Add attribute to s:link tag to make creation of magic dataModelSelection URL parameter optional ----------------------------------------------------------------------------------------------- Key: JBSEAM-2697 URL: http://jira.jboss.com/jira/browse/JBSEAM-2697 Project: JBoss Seam Issue Type: Feature Request Components: JSF Controls Affects Versions: 2.0.1.GA Reporter: Wolfgang Schwendt Priority: Minor When an s:link component (org.jboss.seam.ui.component.UILink) is placed into a h:dataTable backed by a javax.faces.model.DataModel, the s:link automatically generates the magic token for the magic "dataModelSelection" parameter regardless of whether the latter is really needed or not. This can generate ugly URLs. The following example is particulary ugly: http://127.0.0.1:8080/seminaris/seminarDetails.seam?seminarId=2&dataModel... Without the "dataModelSelection" parameter, the URL would look much cleaner: http://127.0.0.1:8080/seminaris/seminarDetails.seam?semId=2 So my question: Couldn't we make the "dataModelSelection" parameter optional? (For example, by adding an attribute to the s:link tag). Btw: I'm aware that org.jboss.seam.ui.component.UISeamCommandBase.getUrl() is the culprit that triggers inclusion of the the dataModelSelection parameter, so I know how to remove the dataModelSelection parameter generation, but it would be nice if also the officially released Seam version allowed the deactivation of the magic token generation. Further, no magic token is generated if a UIDataTable is supplied by a normal List rather than a DataModel (cf. UISeamCommandBase.getSelection() ), but unfortunately there can be cases where it makes sense to supply the table data as DataModel rather than normal List. -- 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, 10 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4428) <s:decorate> tag gives a "[renderkit] 'for' attribute cannot be null" message when no EditableValueHolder is found

by Julien Kronegg (JIRA)

<s:decorate> tag gives a "[renderkit] 'for' attribute cannot be null" message when no EditableValueHolder is found ------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-4428 URL: https://jira.jboss.org/jira/browse/JBSEAM-4428 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.GA Environment: Seam 2.1.2.GA, http://fisheye.jboss.org/browse/Seam/branches/community/Seam_2_1/ui/src/m..., http://fisheye.jboss.org/browse/Seam/branches/community/Seam_2_1/ui/src/m... Reporter: Julien Kronegg Priority: Minor When a field is decorated using <s:decorate> with the default Seam template "edit.xhtml" on content without EditableValueHolder (i.e. editable elements such as <h:inputText>), the following warning is issued: WARN [renderkit] 'for' attribute cannot be null This occurs for example on the following code snippet: <s:decorate id="char" template="edit.xhtml"> <ui:define name="label">Characters Left:</ui:define> <h:outputText id="charLeft" value="#{smsClass.charLeft}"/> </s:decorate> The Seam edit.xhtml template is the following: <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:s="http://jboss.com/products/seam/taglib"> <div class="prop"> <s:label styleClass="name #{invalid?'errors':''}"> <ui:insert name="label"/> <s:span styleClass="required" rendered="#{required}">*</s:span> </s:label> <span class="value #{invalid?'errors':''}"> <s:validateAll> <ui:insert/> </s:validateAll> </span> <span class="error"> <h:graphicImage value="/img/error.gif" rendered="#{invalid}" styleClass="errors"/> <s:message styleClass="errors"/> </span> </div> </ui:composition> This is caused by org.jboss.seam.ui.component.UIDecorate which gets the 'for' id by looking at the first available EditableValueHolder. When there is no such element, the 'for' id is null, hence the warning message (probably issued by the org.jboss.seam.ui.component.UIMessage parent class javax.faces.component.html.HtmlMessage). The warning message is very anonying and give no useful information on what is going wrong: this kind of messages takes a lot of time to track and makes a big impact on the developper productivity. The UIDecorate class should either: 1) display no error message (by either attaching the s:message tag to the s:decorate itself, or by avoid rendering the s:message) 2) display a more meaningfull message such as "No editable component found to attach the message in the decorate with id=xxx" (maybe to be combined with solution 1). -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4072) JUnit 4 version of SeamTest

by Dan Allen (JIRA)

JUnit 4 version of SeamTest --------------------------- Key: JBSEAM-4072 URL: https://jira.jboss.org/jira/browse/JBSEAM-4072 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.1.GA Reporter: Dan Allen Fix For: The future NetBeans still lacks a good plugin for TestNG and arguably JUnit 4 is still better supported in IDEs overall. Therefore, it would be nice if Seam would provide a base test class for JUnit 4. Since JUnit 4 has parallel support for tests being declared through the use of annotations, it should be fairly straightforward to support both test frameworks. Better yet, someone has already done the work. Please see http://bernard.labno.pl/?action=seamtest4junit -- 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, 11 months

3
5
0 / 0

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

4
10
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, 11 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, 11 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, 12 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, 12 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

13 years

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

13 years

3
12
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2011