August 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4378) Conversation picker does not now what current conversation is

by Tony Herstell (JIRA)

Conversation picker does not now what current conversation is ------------------------------------------------------------- Key: JBSEAM-4378 URL: https://jira.jboss.org/jira/browse/JBSEAM-4378 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Environment: WIndoze PC XP64 JBoss 5.1GA Richfaces (nightly build) Reporter: Tony Herstell Priority: Minor using Seam JPAIdentityStore for a login page with configured entities for User and Role. URL: https://localhost/site/pages/user/login.seam?cid=372 Markup: <h:column> <f:facet name="header"> <h:outputText value="#{messages.template_workspace}" /> </f:facet> <h:commandLink action="#{entry.select}" value="#{entry.description}" rendered="#{!entry.current}"/> <h:outputText value="[current]" rendered="#{entry.current}" /> <h:outputText value="#{entry.id}" /> <h:outputText value="#{entry.current}" /> </h:column> What is shown on page: Workspace Activity Action Logging in of new User372false 10:37 AM - 10:37 AM Problem is why conversation 372 is not shown as true when this shows I am in a "conversation". components.xml <?xml version="1.0" encoding="UTF-8"?> <components xmlns="http://jboss.com/products/seam/components" xmlns:core="http://jboss.com/products/seam/core" xmlns:security="http://jboss.com/products/seam/security" xmlns:transaction="http://jboss.com/products/seam/transaction" xmlns:persistence="http://jboss.com/products/seam/persistence" xmlns:mail="http://jboss.com/products/seam/mail" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:drools="http://jboss.com/products/seam/drools" xmlns:international="http://jboss.com/products/seam/international" xsi:schemaLocation="http://jboss.com/products/seam/core http://jboss.com/products/seam/core-2.1.xsd http://jboss.com/products/seam/transaction http://jboss.com/products/seam/transaction-2.1.xsd http://jboss.com/products/seam/security http://jboss.com/products/seam/security-2.1.xsd http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.1.xsd http://jboss.com/products/seam/persistence http://jboss.com/products/seam/persistence-2.1.xsd http://jboss.com/products/seam/mail http://jboss.com/products/seam/mail-2.1.xsd"> <core:init jndi-pattern="Risingstars/#{ejbName}/local" debug="false" /> <core:manager conversation-timeout="360000" concurrent-request-timeout="500" conversation-id-parameter="cid" /> <persistence:managed-persistence-context name="entityManager" auto-create="true" persistence-unit-jndi-name="java:/risingstarsEntityManagerFactories"/> <component class="org.jboss.seam.web.MultipartFilter"> <property name="createTempFiles">false</property> <property name="maxRequestSize">500000</property> </component>  <factory name="basePath" value="#{facesContext.externalContext.request.scheme}://#{facesContext.externalContext.request.serverName}:#{facesContext.externalContext.request.serverPort}#{facesContext.externalContext.request.contextPath}/" /> <international:locale-config default-locale="en" supported-locales="en_GB de"/>  <international:locale-selector cookie-enabled="true"/> <security:rule-based-permission-resolver security-rules="#{securityRules}"/>  <security:jpa-identity-store user-class="nz.co.softwarefactory.risingstars.model.User" role-class="nz.co.softwarefactory.risingstars.model.Role"/>  <event type="org.jboss.seam.security.notLoggedIn"> <action execute="#{redirect.captureCurrentView}"/> </event> <event type="org.jboss.seam.security.loginSuccessful"> <action execute="#{redirect.returnToCapturedView}"/> </event> </components> pages.xml <?xml version="1.0" encoding="UTF-8"?> <pages 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.1.xsd" no-conversation-view-id="/home.xhtml" login-view-id="/pages/user/login.xhtml"> <page view-id="*" scheme="http"> <navigation from-action="#{identity.logout}"> <redirect view-id="/home.xhtml" /> </navigation> </page> <page view-id="/home.xhtml" login-required="false"> <description>Home Page</description> </page> <page view-id="/pages/user/login.xhtml" login-required="false" scheme="https"> <description>Logging in of new User</description> </page> <exception class="org.jboss.seam.security.NotLoggedInException"> <redirect view-id="/home.xhtml"> <message severity="ERROR"> #{messages.security_permission} </message> </redirect> </exception> <exception class="org.jboss.seam.security.AuthorizationException"> <end-conversation/> <redirect view-id="/home.xhtml"> <message severity="ERROR"> #{messages.security_not_logged_in} </message> </redirect> </exception> <exception class="javax.faces.application.ViewExpiredException"> <end-conversation/> <redirect view-id="/home.xhtml"> <message severity="INFO"> #{messages.session_timeout} </message> </redirect> </exception> <exception> <end-conversation/> <redirect view-id="/home.xhtml"> <message severity="WARN">Unexpected Error #{org.jboss.seam.handledException.message}</message> </redirect> </exception> </pages> -- 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

15 years, 4 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4210) EmptyStackException thrown by Seam transactions

by Stephane Epardaud (JIRA)

EmptyStackException thrown by Seam transactions ----------------------------------------------- Key: JBSEAM-4210 URL: https://jira.jboss.org/jira/browse/JBSEAM-4210 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: Stephane Epardaud When Trinidad is acting up while sending an email using seam: 17:17:32,076 ERROR [STDERR] Jun 2, 2009 5:17:32 PM org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit createResponseWriter SEVERE: No RenderingContext has been created. I get the following exception: 17:17:32,272 ERROR [ExceptionFilter] could not roll back transaction java.util.EmptyStackException at java.util.Stack.peek(Stack.java:85) at java.util.Stack.pop(Stack.java:67) at org.jboss.seam.transaction.SeSynchronizations.afterTransactionRollback(SeSynchronizations.java:45) at org.jboss.seam.transaction.UTTransaction.rollback(UTTransaction.java:70) at org.jboss.seam.web.ExceptionFilter.rollbackTransactionIfNecessary(ExceptionFilter.java:159) at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:113) 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.jboss.seam.web.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:42) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) 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.IdentityFilter.doFilter(IdentityFilter.java:40) 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:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) 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.valves.AccessLogValve.invoke(AccessLogValve.java:562) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:619) I can reproduce this but I cannot find a minimal test case yet. We've been having tons of problems with Trinidad and the latest Seam 2.1. This works with Seam 2.0. -- 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

15 years, 4 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1592) <s:graphicImage> should accept raw byte[] without conversion

by Gena Batalski (JIRA)

<s:graphicImage> should accept raw byte[] without conversion ------------------------------------------------------------ Key: JBSEAM-1592 URL: http://jira.jboss.com/jira/browse/JBSEAM-1592 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.BETA1, 1.3.0.ALPHA, 1.2.1.GA Environment: latest from repo Reporter: Gena Batalski Priority: Minor It would be helpful to feed the <s:graphicImage> with raw byte[] (possible also ByteArray - stream) without converting it to BufferedImage or something else. Also the content type could be manually entered. Of course, its in the responsibility of the developer, to take care about the correctness of input. Optional attributes (forceContentType, forceImage or something else) could do this job on the UI side. Background of the request: if i comment out the byte[] handling in Image.class (line 404 method readImage()) as in a following snipplet, i get an expected quality. Otherwise, the image quality decreases significantly, especially for small images (icons, thumbnails). /* byte[] b = (byte[]) input; readImage(new ByteArrayInputStream(b)); */ output = (byte[]) input; I also would have some possibility, to prepare the image on demand. Currently i'm using two servlets: one SeamResource and one for my images. My servlet receives an URI and selects an image LOB from DB, because it isn't necessary to store the images in memory (they could be large) and the images could stay unrequested. What i need is some kind callback (converter?) which asks me for byte[] or stream representation of an image uri. Thanks Gena -- 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

15 years, 4 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2429) converterId in Seam page param not recognised in EAR project structure

by Terry (JIRA)

converterId in Seam page param not recognised in EAR project structure ---------------------------------------------------------------------- Key: JBSEAM-2429 URL: http://jira.jboss.com/jira/browse/JBSEAM-2429 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Windows, Project Structure EAR, JBoss 4.2 EAP. Seam2+Sun JSF RI+Facelets+Richfaces. Reporter: Terry In a EAR project structure; assigning converterId in page parameter in .page.xml file is not recognised. Throws errors: javax.faces.FacesException: Expression Error: Named Object: org.jboss.seam.ui.converter.DateTimeConverter not found. <param name="settlementDateFrom" converterId="org.jboss.seam.ui.converter.DateTimeConverter" value="#{paymentReconciliation.settlementDateFrom}"/> See forum issue for more details. -- 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

15 years, 5 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3305) Seam testsuite skipping and failing many tests on windows XP machine

by Jay Balunas (JIRA)

Seam testsuite skipping and failing many tests on windows XP machine -------------------------------------------------------------------- Key: JBSEAM-3305 URL: https://jira.jboss.org/jira/browse/JBSEAM-3305 Project: Seam Issue Type: Bug Components: Test Harness Affects Versions: 2.1.0.BETA1 Environment: windows XP JDK5 Reporter: Jay Balunas Fix For: 2.1.0.BETA2 When running "ant testall testreport" on windows XP there are many failures and skipped tests. It appears to be a timing or io conflict with an hsql localDB.lck file in the embedded server. When you "ant test" the same examples individually they work fine. -- 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

15 years, 5 months

5
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2759) Seam dist directory structure verification and comparison between releases.

by Jay Balunas (JIRA)

Seam dist directory structure verification and comparison between releases. ----------------------------------------------------------------------------- Key: JBSEAM-2759 URL: http://jira.jboss.com/jira/browse/JBSEAM-2759 Project: JBoss Seam Issue Type: Task Components: Build Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Jay Balunas Assigned To: Jay Balunas Seam release directory structure verification and comparison between releases. This can be done through existing tools, and ant scripts. It will provide a information on where risk has been added and also fine issues related structure between releases. May be integrated with CI if able. -- 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

15 years, 5 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4293) Make JBoss restart after a specified number of ftests run to prevent OutOfMemoryError

by Ondrej Skutka (JIRA)

Make JBoss restart after a specified number of ftests run to prevent OutOfMemoryError ------------------------------------------------------------------------------------- Key: JBSEAM-4293 URL: https://jira.jboss.org/jira/browse/JBSEAM-4293 Project: Seam Issue Type: Task Components: Test Harness Reporter: Ondrej Skutka Assignee: Ondrej Skutka Priority: Minor When running ftests JBoss ends up with OutOfMemoryError. Make JBoss restart after a specified number of tests run. -- 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

15 years, 5 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3879) e:cell formatting of date or number colum fails, if first value is a null value

by Alexander Schwartz (JIRA)

e:cell formatting of date or number colum fails, if first value is a null value ------------------------------------------------------------------------------- Key: JBSEAM-3879 URL: https://jira.jboss.org/jira/browse/JBSEAM-3879 Project: Seam Issue Type: Sub-task Components: Excel Affects Versions: 2.1.1.GA Environment: Seam 2.1.1.GA, Windows, Jetty Reporter: Alexander Schwartz The cell style of a e:cell is cached (for the specific id) when it is accessed for the first time. When the first value is a null value, uiCell.getDataType() is unable to automatically detect the data type of the column and returns 'general'. This is then cached. All other columns are then treated as 'general' in createCell(), and all data is converted using data.toString() leading to ugly results. Our solution is to add "xls-force-type: date" to all e:cell of type number or date. We added this to the evaluation (see below). Another idea would have been to defer caching until the first non-null value has been met. But this might cause troubles in createCell() when there is a handing depending on the type. from JXLHelper.java: /** * Gets the cell type for a cell. Tries to look it up in a cache based on the * component id of the cell. If it's not found, it's created and cached. * * @param uiCell The cell to look up * @return The data type of a cell */ private CellType getCellDataType(UICell uiCell) { if (log.isTraceEnabled()) { log.trace("Getting cell data type from cache for #0", uiCell.getId()); } CellType cellDataType = cellInfoCache.getCachedCellType(uiCell.getId()); if (cellDataType == null) { /* old code: cellDataType = uiCell.getDataType(); */ /* new code start */ CellStyle cellStyle = new CellStyle(parser.getCascadedStyleMap(uiCell)); cellDataType = cellStyle.forceType != null ? CellType .valueOf(cellStyle.forceType) : uiCell.getDataType(); /* new code end */ cellInfoCache.setCachedCellType(uiCell.getId(), cellDataType); } return cellDataType; } -- 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

15 years, 5 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1855) FacesMessages.instance().addToControl and Datatable do not work properly

by Andy Bosch (JIRA)

FacesMessages.instance().addToControl and Datatable do not work properly ------------------------------------------------------------------------ Key: JBSEAM-1855 URL: http://jira.jboss.com/jira/browse/JBSEAM-1855 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.0.GA Reporter: Andy Bosch It is possible do add FacesMessages via the Seam functionality with FacesMessages.instance().addToControl. In the parameters you have to pass the component id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In the JSF-way you have to pass the client-id. With normal input components you can use both ways. But when you work with datatables, you MUST work with the client-id, the Seam-way with using only the component-id does NOT work. Explanation: When using a datatable-tag, you only have one component. The renderer generates the various rows. In the component-tree there is yet only one component! If you want to add a FacesMessage to one row, you can only work with client-ids (because you have to include the row-index). My wish: Please change FacesMessages.instance().addToControl. for using with client-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

15 years, 5 months

10
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4397) Using JPAIdentityStore means Hibernate Annotations are not used in UI

by Tony Herstell (JIRA)

Using JPAIdentityStore means Hibernate Annotations are not used in UI --------------------------------------------------------------------- Key: JBSEAM-4397 URL: https://jira.jboss.org/jira/browse/JBSEAM-4397 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.GA Environment: WinXP64 Dev / Ubuntu Server Reporter: Tony Herstell Follow Doco and use @UserPrincipal But if you use other hibernate validation annotations on the field then it is not propagated to view. -- 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

15 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2009