June 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMMAIL-4) Render/Send mail from non-web requests (e.g. MDB, EJB async, JMS queue, EJB remote invocation)

by Pete Muir (JIRA)

Render/Send mail from non-web requests (e.g. MDB, EJB async, JMS queue, EJB remote invocation) ---------------------------------------------------------------------------------------------- Key: SEAMMAIL-4 URL: https://jira.jboss.org/browse/SEAMMAIL-4 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir -- 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

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBSEAM-4643) Add built-in primefaces option to seam-gen

by sertac anadollu (JIRA)

Add built-in primefaces option to seam-gen ------------------------------------------ Key: JBSEAM-4643 URL: https://jira.jboss.org/jira/browse/JBSEAM-4643 Project: Seam Issue Type: Feature Request Components: JSF Integration Affects Versions: 2.2.1.CR2 Reporter: sertac anadollu Fix For: 2.2.1.CR2 Primefaces is the one of most popular open source jsf component libraries and day by day it is widely used in seam based projects. Some advantages of this library are its simplicity, natural compatibility with other libraries, high performance, having interesting components, simple setup, good documentation, development team behind it and licensed under Apache License V2. I used it many seam based projects and I am very happy for being with it. It is very nice to see primefaces option in the seam-gen setup. -- 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

13 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-1) Handle errors from sending mail

by Pete Muir (JIRA)

Handle errors from sending mail ------------------------------- Key: SEAMMAIL-1 URL: https://jira.jboss.org/browse/SEAMMAIL-1 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir > Another thing the current implementation does is render and send at the same > time. This is a bad idea as well. You'd generally want to save the rendered? > email, and retry on send errors. Email has two types of errors, those that the MTA will automatically retry for, and those that cause bounces. If you are referring to bounces, how do you process the bounces? -- 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

13 years, 5 months

3
10
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-5) Save rendered Mail message to JPA

by Pete Muir (JIRA)

Save rendered Mail message to JPA --------------------------------- Key: SEAMMAIL-5 URL: https://jira.jboss.org/browse/SEAMMAIL-5 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir -- 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

13 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-7) Consider how users can edit mail templates

by Pete Muir (JIRA)

Consider how users can edit mail templates ------------------------------------------ Key: SEAMMAIL-7 URL: https://jira.jboss.org/browse/SEAMMAIL-7 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir Apparently XML templates are too complex. -- 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

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-3) Support multiple to addresses

by Pete Muir (JIRA)

Support multiple to addresses ----------------------------- Key: SEAMMAIL-3 URL: https://jira.jboss.org/browse/SEAMMAIL-3 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir -- 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

13 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-2) Testing infrastructure

by Pete Muir (JIRA)

Testing infrastructure ---------------------- Key: SEAMMAIL-2 URL: https://jira.jboss.org/browse/SEAMMAIL-2 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir -- 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

13 years, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3347) change column width in tables of pdf doc in security chapter

by Carsten Hoehne (JIRA)

change column width in tables of pdf doc in security chapter ------------------------------------------------------------ Key: JBSEAM-3347 URL: https://jira.jboss.org/jira/browse/JBSEAM-3347 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.BETA1 Reporter: Carsten Hoehne Please try to adapt the column width of tables in the security chapter. As an example see table 15.4 Identity Management API in chapter 15.4.6 Please make the columnb Description a little bit wider and try to not overwrite strings in column Returns with strings in column Method Thanks in advance -- 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

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4589) ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans

by Sebastien Boutte (JIRA)

ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans -------------------------------------------------------------------------------- Key: JBSEAM-4589 URL: https://jira.jboss.org/jira/browse/JBSEAM-4589 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.2.GA Reporter: Sebastien Boutte As it is said in documentation (Part : EJB Passivation and the ManagedEntityInterceptor) ; seam is capable of passivate SMPC (EntityManager with @In) and reattach all instances loaded at activation. For simple fields (Entities, Lists, Maps ...) , it works perfectly. For user defined fields (Wrapper with entity object, or more complex structure), this is not the case and cause a lazy exception later after activation. In class ManagedEntityWrapper, methods wrap and deserialize are not able to do in depth operations. -- 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

13 years, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4375) ManagedEntityInterceptor destroys components in parent nested conversation, when ending a nested conversation

by Darryl Smith (JIRA)

ManagedEntityInterceptor destroys components in parent nested conversation, when ending a nested conversation ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4375 URL: https://jira.jboss.org/jira/browse/JBSEAM-4375 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Reporter: Darryl Smith setup: Parent (cid1) -> First Nested (cid2) ----> Second Nested (cid3) cid3: conversation.endAndRedirect(true); which calls setLongRunningConversation(false); FacesManager's redirect method tries to encode the page parameters of the parent view, which accesses a component created in cid2 the conversation we are returning to. This triggers ManagedEntityWrapper's switchToConversationContextOfComponent which switches the current conversation to cid2 after ManagedEntityWrapper wraps the component ManagedEntityWrapper's restorePreviousConversationContextIfNecessary method is called with oldCid = cid3 which triggers Contexts.getConversationContext().flush(); When flush is invoke the conversation (cid2) isn't long running, so flush removes all components created in cid2 -- 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

13 years, 5 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2010