February 2010 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4185) ViewExpiredException is printed in the log even if i set log="false"

by Adrian Mitev (JIRA)

ViewExpiredException is printed in the log even if i set log="false" -------------------------------------------------------------------- Key: JBSEAM-4185 URL: https://jira.jboss.org/jira/browse/JBSEAM-4185 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.1.2.CR1 Reporter: Adrian Mitev Attachments: exception.txt See exception.txt for the stacktrace. This is what i have in pages.xml <exception class="javax.faces.application.ViewExpiredException" log="false"> <redirect view-id="/common/error.xhtml"> <message>#{messages.sessionTimeout}</message> </redirect> </exception> and the redirect is performed but i still see the exception in the log -- 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

11 years, 11 months

5
13
0 / 0

[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

11 years, 12 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

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, 1 month

3
5
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, 1 month

5
27
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, 2 months

6
15
0 / 0

[JBoss JIRA] Created: (JBSEAM-4500) Seam 2.2.0 based application fails to run if hibernate 4.0.2 GA used

by Ilya Shaikovsky (JIRA)

Seam 2.2.0 based application fails to run if hibernate 4.0.2 GA used -------------------------------------------------------------------- Key: JBSEAM-4500 URL: https://jira.jboss.org/jira/browse/JBSEAM-4500 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.GA Environment: tomcat 6 Reporter: Ilya Shaikovsky https://forum.hibernate.org/viewtopic.php?f=9&t=1001094 I tried to update RF demo dependencies to use JSR-303. Exception on server start just as posted at forum. It seems component just should not be instantiated if misses required dependency. -- 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

6
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3020) Links to seam and gsg of jbosstools

by Svetlana mukhina (JIRA)

Links to seam and gsg of jbosstools ----------------------------------- Key: JBSEAM-3020 URL: http://jira.jboss.com/jira/browse/JBSEAM-3020 Project: Seam Issue Type: Task Components: Documentation Issues Reporter: Svetlana mukhina Assigned To: Michael Yuan Priority: Optional Looking through the guide http://docs.jboss.com/seam/2.0.2.GA/reference/en-US/html/index.html I've found a chapter http://docs.jboss.com/seam/2.0.2.GA/reference/en-US/html/gettingstartedwi... that overlapping with some of our guides - http://docs.jboss.org/tools/2.1.0.CR1/en/seam/publish/en-US/html/index.html and http://docs.jboss.org/tools/2.1.0.CR1/en/GettingStartedGuide/publish/en-U..., maybe it will be good to add links in the chapter referring to these 2 guides where a user could find more information on the topic? -- 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, 3 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3971) Documentation to run under Websphere should contain information about Websphere 6.1 and Websphere 7.0

by Julien Kronegg (JIRA)

Documentation to run under Websphere should contain information about Websphere 6.1 and Websphere 7.0 ----------------------------------------------------------------------------------------------------- Key: JBSEAM-3971 URL: https://jira.jboss.org/jira/browse/JBSEAM-3971 Project: Seam Issue Type: Feature Request Components: Documentation Issues Environment: Trunk documentation http://fisheye.jboss.org/browse/Seam/trunk/doc/Seam_Reference_Guide/en-US... Reporter: Julien Kronegg Priority: Minor Until Seam 2.1.1.GA, the documentation gives information about running examples under Websphere 6.1: http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/websphere.html In the latest version (future 2.1.2.GA?), the documentation gives information about running examples under Websphere 7.0. The (valuable) documentation about running under WAS 6.1 is gone. It would be cool to add a sentence such as: "Information about other Websphere version can be found in previous Seam release documentation: - [Websphere 6.1=>http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/websphere.html]" This has the advantage to give useful information to Websphere users without having to much documentation content to add/rewrite. -- 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

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4454) HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing

by Arsen Torbarina (JIRA)

HibernatePersistenceProvider.init() and PersistenceProvider.init() not executing -------------------------------------------------------------------------------- Key: JBSEAM-4454 URL: https://jira.jboss.org/jira/browse/JBSEAM-4454 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA, 2.2.0.CR1, 2.1.2.GA, 2.1.2.CR2, 2.1.2.CR1 Reporter: Arsen Torbarina Fix For: 2.2.1.CR1 Method org.jboss.seam.persistence.PersistenceProvider.init() (including its subclass' method HibernatePersistenceProvider.init()) never gets executed, because it is annotated with @org.jboss.seam.annotations.intercept.PostConstruct instead of @javax.ejb.PostConstruct. -- 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

5
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2010