May 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3698) Error during rendering of an EMail in an event listener causes failure in rendering of next page

by Wayne Bagguley (JIRA)

Error during rendering of an EMail in an event listener causes failure in rendering of next page ------------------------------------------------------------------------------------------------ Key: JBSEAM-3698 URL: https://jira.jboss.org/jira/browse/JBSEAM-3698 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.0.SP1 Environment: Windows XP, Java 6, 2GB RAM, JBoss 4.2.2.GA Reporter: Wayne Bagguley Assignee: Pete Muir I have a method that is defined as a listener like this : @Observer(JpaIdentityStore.EVENT_USER_CREATED) This attempts to send an email to the user when he registers but if the email rendering fails for some reason the exception is caught and the method returns normally. However, instead of the next page being rendered, the original page gets rendered incorrectly, with parts of the form in the wrong place. The failure of rendering the EMail should not affect the progress of the rendering of the next page if the exception is caught. -- 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

8
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3056) JPDL navigation and seam

by Florian Keusch (JIRA)

JPDL navigation and seam ------------------------ Key: JBSEAM-3056 URL: http://jira.jboss.com/jira/browse/JBSEAM-3056 Project: Seam Issue Type: Task Components: BPM Reporter: Florian Keusch hi In our applications we have a navigation menu. When we use seam and some jpdl pageflows we have the following problem: if we leave the pageflow with a <s:link propagation="end"> (e.g. clicking on the menu), then the pageflow conversation is ended but also an illegal navigation exception is thrown. This issue was described on the seam framework: http://www.seamframework.org/Community/ProblemWithJPDLIllegalNavigation but I could not find it in this Jira. It's not solved. In the code (PageFlow.java) there's a TODO where the illegal navigation ecxeption is thrown: //now check that the restored view id matches what we expect //from the pageflow node //TODO: we need some way to disable this check, since users // might want some adhoc nav in and out of a pageflow? String viewId = Pages.getViewId(facesContext); if ( !viewId.equals( getPage().getViewId() ) ) { illegalNavigationError(); } If we use <s:link propagation="none"> in our menu navigation then this will not cause a illegal navigation exception, but in the background the conversations are still there not ended. fke -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4144) Example booking: javax.ejb.NoSuchEJBException: Could not find stateful bean in undeployment

by Marek Novotny (JIRA)

Example booking: javax.ejb.NoSuchEJBException: Could not find stateful bean in undeployment ------------------------------------------------------------------------------------------- Key: JBSEAM-4144 URL: https://jira.jboss.org/jira/browse/JBSEAM-4144 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.2.CR1 Environment: jboss 4.2.3 java 6 Reporter: Marek Novotny Priority: Minor I am getting NoSuchEJBException when undeploying booking example. Steps to reproduce: 1. deploy booking example 2. login into seam-booking webapp 3. Do some hotel booking 4. on command line undeploy the booking example - ant undeploy Exception is always happened, also for icefaces example. -- 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

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4091) model validation on page param should be optional

by Dan Allen (JIRA)

model validation on page param should be optional ------------------------------------------------- Key: JBSEAM-4091 URL: https://jira.jboss.org/jira/browse/JBSEAM-4091 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.1.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.1.2.GA When page parameters are being used to capture input for queries, it may not be appropriate to run the model validator on them. It should be possible to disable the model validator. However, the default would be that the model validator is enabled. -- 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

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3699) Slow hot deployment - Seam scans and builds component tree each time to check for hot deploy changes

by Pete Muir (JIRA)

Slow hot deployment - Seam scans and builds component tree each time to check for hot deploy changes ---------------------------------------------------------------------------------------------------- Key: JBSEAM-3699 URL: https://jira.jboss.org/jira/browse/JBSEAM-3699 Project: Seam Issue Type: Bug Components: Core Reporter: Pete Muir Priority: Blocker Fix For: 2.1.1.CR1 -- 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, 1 month

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4200) hot deploy re-reads the class files on every request, not just timestamps

by Vadim Berezniker (JIRA)

hot deploy re-reads the class files on every request, not just timestamps ------------------------------------------------------------------------- Key: JBSEAM-4200 URL: https://jira.jboss.org/jira/browse/JBSEAM-4200 Project: Seam Issue Type: Bug Components: Hot Deploy Affects Versions: 2.1.2.CR2 Reporter: Vadim Berezniker Priority: Minor When enabling hot deploy, every request becomes slower. I started looking into the Seam code yesterday and this is what I found: redeploy creates a TimestampCheckForwardingDeploymentStrategy which has a method to initiate a Scanner that doesn't check the file contents however it doesn't appear to be ever used. Instead all the calls are forwarded to the hot deployment strategy delegate which uses the normal scanner which re-reads the contents of the class files even if none of the files have changed. -- 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, 1 month

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4199) Blog directory plugin shows duplicate attachments

by Christian Bauer (JIRA)

Blog directory plugin shows duplicate attachments ------------------------------------------------- Key: JBSEAM-4199 URL: https://jira.jboss.org/jira/browse/JBSEAM-4199 Project: Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assignee: Christian Bauer Priority: Minor Probably because the list of attachments is in page scope when a document is rendered, so if we render multiple documents on a single page (like several blog entries...) we get duplicate attachments. Need to figure out how we can scope that better. -- 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, 1 month

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4180) Error in <s:convertEntity/> when orm.xml is the only mechanism for persistence

by Cristian Fabiano (JIRA)

Error in <s:convertEntity/> when orm.xml is the only mechanism for persistence ------------------------------------------------------------------------------ Key: JBSEAM-4180 URL: https://jira.jboss.org/jira/browse/JBSEAM-4180 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: Windows XP SP2 Reporter: Cristian Fabiano When my entities are mapped only in orm.xml, they do not have the @Entity annotation, and I use a one <s:convertEntity/> with one, I got the exception: org.jboss.seam.Entity $ NotEntityException: Unable to establish name of entity class com.emmsistemas.emmvendas.entidade.Grupo my orml.xml for this Entity: <entity class="com.emmsistemas.emmvendas.entidade.Grupo"> <table name="GRUPO"></table> <attributes> <id name="id"> <column name="gru_id"/> <generated-value strategy="IDENTITY"/> </id> <basic name="nome"> <column name="gru_nome"/> </basic> <basic name="descricao"> <column name="gru_descricao"/> </basic> <basic name="condicional"> <column name="gru_condicional"/> </basic> </attributes> </entity> Seam does not recognize the Entity when it not have a @Entity? -- 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, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4135) Upload selenium libs to jboss maven repository

by Jozef Hartinger (JIRA)

Upload selenium libs to jboss maven repository ---------------------------------------------- Key: JBSEAM-4135 URL: https://jira.jboss.org/jira/browse/JBSEAM-4135 Project: Seam Issue Type: Task Components: Test Harness Affects Versions: 2.1.2.CR1 Reporter: Jozef Hartinger Assignee: Marek Novotny Fix For: 2.1.2.CR2 selenium-java-client-driver and selenium-server need to be obtainable with maven in order to get rid of binaries in svn -- 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, 1 month

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4197) Scoped cache-provider

by Alexey Kakunin (JIRA)

Scoped cache-provider --------------------- Key: JBSEAM-4197 URL: https://jira.jboss.org/jira/browse/JBSEAM-4197 Project: Seam Issue Type: Feature Request Components: Performance and Scalability Reporter: Alexey Kakunin Seam has cacheProvider component and it is great. But, in some cases, we need to prevent data, stored in cache for one user, to be visible for another user. Bets implementation for this I see - to be able to define cacheProvider with scope SESSION - and, in general, with any scope - additionally to default, APPLICATION-scoped cacheProvider -- 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, 1 month

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2009