August 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1758) DocumentStorePhaseListener fails if installed before SeamPhaseListener when used in a portlet

by Chris Rudd (JIRA)

DocumentStorePhaseListener fails if installed before SeamPhaseListener when used in a portlet --------------------------------------------------------------------------------------------- Key: JBSEAM-1758 URL: http://jira.jboss.com/jira/browse/JBSEAM-1758 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Reporter: Chris Rudd When the DocumentStorePhaseListener is installed before the SeamPhaseListener (this can happend when the jboss-seam.jar sits in the ear, and the jboss-seam-pdf.jar sits in the war) in a portlet environment, a "No active application context" exception is thrown during Portlet.render. This is becaus the SeamPhaseListener hasn't had a chance to setup the Seam contexts yet. I would suggest changing the code so that it responds to the Phase events that the SeamPhaseListener publishes ( org.jboss.seam.beforePhase ) so that its guaranteed to be executed after the SeamPhaseListener has property set things up. -- 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

14 years, 3 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1625) <param> node in <exception> in pages.xml is not used

by Zalder R (JIRA)

<param> node in <exception> in pages.xml is not used ---------------------------------------------------- Key: JBSEAM-1625 URL: http://jira.jboss.com/jira/browse/JBSEAM-1625 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: jboss 4.2, seam 2.0.0.B1 Reporter: Zalder R The param option in an exception node in pages.xml is not used : <exception class="org.my.Exception"> <redirect view-id="/mypage.xhtml"> <param name="u" value="#{user.username}"/> <message severity="warn">#{messages['MSG.ERROR.MAX_TEXT_REACHED']}</message> </redirect> </exception> When the exception is triggered : redirect is done to mypage.xhtml ... not mypage.xhtml?u=whatever -- 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

14 years, 3 months

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1841) Need examples/documentation for how to use seamgen generated EntityHome interefaces and related functionality

by steve tynor (JIRA)

Need examples/documentation for how to use seamgen generated EntityHome interefaces and related functionality ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1841 URL: http://jira.jboss.com/jira/browse/JBSEAM-1841 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 2.0.0.BETA1 Reporter: steve tynor Please add some documentation, perhaps an example project, that uses seamgen-generated EntityHome classes in order to demonstrate the intended use of the wire(), isWired(), createInstance(), getDefinedInstance(), setId(), etc. functions. Some discussion on how these related to <param> and <f:param> in XHTML is also needed. As it stands, these are completely undocumented without any explanation of their intended use, so those of us that have boostrapped a project with seamgen, have no guidance on how to maintian these classes as our application changes (new properties added to entities, etc.) -- 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

14 years, 3 months

5
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1505) Application-level log

by Christian Bauer (JIRA)

Application-level log --------------------- Key: JBSEAM-1505 URL: http://jira.jboss.com/jira/browse/JBSEAM-1505 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor Create a persistent LogEvent and raise a Seam event whenever anything interesting happens in the app (user registered, document deleted, notification stopped because of bounces, and so on). Show log in the admin interface and allow admin to set log level and clear the log. -- 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

14 years, 3 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1852) Implement dynamic privilege system with assignment to roles and users

by Christian Bauer (JIRA)

Implement dynamic privilege system with assignment to roles and users --------------------------------------------------------------------- Key: JBSEAM-1852 URL: http://jira.jboss.com/jira/browse/JBSEAM-1852 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer -- 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

14 years, 3 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1246) pages.xml fails to load during application startup

by Mike Quilleash (JIRA)

pages.xml fails to load during application startup -------------------------------------------------- Key: JBSEAM-1246 URL: http://jira.jboss.com/jira/browse/JBSEAM-1246 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: Any Reporter: Mike Quilleash pages.xml will not be found by the resource loader when the Pages component is @Created during startup ie outside a JSF request. One of my components that queries the Pages component is causing the component to be created and look for its pages outside a JSF request. The only resource lookup that can succeed for something in WEB-INF is the ExternalContext.getResource() but this is not available outside a JSF request. Using ServletContext.getResource() will work instead however this is not portable to Portlets etc. -- 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

14 years, 3 months

6
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1563) create "bin" distribution

by Dan Allen (JIRA)

create "bin" distribution ------------------------- Key: JBSEAM-1563 URL: http://jira.jboss.com/jira/browse/JBSEAM-1563 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1, 1.3.0.ALPHA, 1.2.1.GA Reporter: Dan Allen The current releases of Seam are ridiculously large, weighing in at around 80MB. That is almost as big as the JBoss AS download! While it is critical to offer the entire bundle for Seam developers, contributors, and source builders, I think it would be appropriate to offer a "bin" distribution that is intended just to run Seam. Perhaps just spin off seam-gen as its own download. That should give people exactly what they need to run Seam, and nothing more. Below is a comparison table of some competing projects: Spring Framework: 10MB (2.6MB if you pull it from the maven repository) Ruby on Rails: 2.2 MB (standalone version) I remember when I first discovered Seam, I put off trying it out because it was too hefty of a download. Let's make it more attractive. -- 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

14 years, 4 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1557) Seam is peforming a redirect in when running as a portlet, rather than using the portlet lifecycle

by Neil Griffin (JIRA)

Seam is peforming a redirect in when running as a portlet, rather than using the portlet lifecycle -------------------------------------------------------------------------------------------------- Key: JBSEAM-1557 URL: http://jira.jboss.com/jira/browse/JBSEAM-1557 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: WinXP / Liferay 4.3.0 / Tomcat 6.0.13 Reporter: Neil Griffin Background: I found this problem when attempting to package the Seam "Registration" example as a portlet under Liferay Portal. Section 7.4.2 of the JSF 1.1 specifcation says that since redirects are not possible in the case of portlets. Nevertheless, the Seam Conversation Manager (Manager.java) is forcing the portal to redirect outside its portal pages, rather than use the portlet lifecycle. The way this would be manifested to the user would be like this: If a Seam application was contained within a portlet, and the portlet were placed on a portal page, then when the user clicks on a button that invokes navigation to a different JSF view, then the Seam application would "jump out" (so to speak) of the rectangular portlet container, and become a full-browser-page thing. This is incorrect. If a Seam application starts out as a portlet, then it must remain a portlet for its entire lifespan. In addition, the current behavior of Seam is not conforming to section 7.4.2 of the JSF 1.1. specification. Now, it might be the case that this redirect works under JBoss Portal, but it causes exceptions to be thrown under Liferay Portal. This is because Liferay Portal expects JSF-based portlets to not perform redirects, as they must not do that anyway. -- 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

14 years, 4 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1554) Validation message obtainable by EL within <s:decorate /> tag

by Slawomir Trybus (JIRA)

Validation message obtainable by EL within <s:decorate /> tag ------------------------------------------------------------- Key: JBSEAM-1554 URL: http://jira.jboss.com/jira/browse/JBSEAM-1554 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.3.0.BETA1 Reporter: Slawomir Trybus It would be very useful to have #{invalidMessage} available inside <s:decorate /> tag. -- 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

14 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1525) Add the EJB @Remove like functionality for POJO components.

by Chris Rudd (JIRA)

Add the EJB @Remove like functionality for POJO components. ----------------------------------------------------------- Key: JBSEAM-1525 URL: http://jira.jboss.com/jira/browse/JBSEAM-1525 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.3.0.ALPHA Reporter: Chris Rudd Currnrntly Statefull EJBs can be removed from the Seam context when an @Remove method is called. This functionality would be helpful for Pojo components as well. -- 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

14 years, 4 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2007