July 2007 - seam-issues - Jboss List Archives

[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, 11 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, 11 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, 11 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, 11 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, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1496) Posibility to use Seam's exception handling in portlet environments

by ivica c (JIRA)

Posibility to use Seam's exception handling in portlet environments ------------------------------------------------------------------- Key: JBSEAM-1496 URL: http://jira.jboss.com/jira/browse/JBSEAM-1496 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.3.0.ALPHA, 1.2.1.GA Reporter: ivica c Fix For: 1.3.0.BETA1, 1.3.0.BETA2, 1.3.0.GA Currently, to use Seam's exception handling you need to define Seam's Filter in web.xml. But in portlet environments it is not possible. It would be nice try find a way how to define and use Seam's exception handling when Seam is used in portlet environment. -- 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, 11 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1448) Get rid of switch statements in Component

by Gavin King (JIRA)

Get rid of switch statements in Component ----------------------------------------- Key: JBSEAM-1448 URL: http://jira.jboss.com/jira/browse/JBSEAM-1448 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Minor Fix For: 1.3.0.BETA2 It would be better to have EntityBeanComponentType, SessionBeanComponentType, JavaBeanComponentType -- 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, 11 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1446) Provide example of using Seam with Flex

by Mikhail Grushinskiy (JIRA)

Provide example of using Seam with Flex --------------------------------------- Key: JBSEAM-1446 URL: http://jira.jboss.com/jira/browse/JBSEAM-1446 Project: JBoss Seam Issue Type: Feature Request Components: Examples Environment: all Reporter: Mikhail Grushinskiy Fix For: 1.3.0.BETA1, 1.3.0.BETA2, 1.3.0.GA, 1.3.1.GA Provide example of using Seam with Flex. -- 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, 11 months

5
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1396) AssertionError running seam-discs example application

by Stuart Robertson (JIRA)

AssertionError running seam-discs example application ----------------------------------------------------- Key: JBSEAM-1396 URL: http://jira.jboss.com/jira/browse/JBSEAM-1396 Project: JBoss Seam Issue Type: Bug Components: Examples Environment: Seam from CVS, Jboss 4.2.0GA, OS X Reporter: Stuart Robertson Priority: Minor When hitting the landing page for seam-discs I get the following: 13:42:06,631 INFO [STDOUT] Hibernate: select artist0_.id as id74_, artist0_.name as name74_, artist0_.description as descript4_74_, artist0_.DTYPE as DTYPE74_ from Artist artist0_ order by artist0_.name 13:42:07,483 ERROR [ExceptionFilter] uncaught exception javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:313) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:210) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:167) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:140) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:93) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:64) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:60) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:81) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:47) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:126) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:248) at org.jboss.seam.web.AbstractAjax4jsfFilter.doFilter(AbstractAjax4jsfFilter.java:35) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:55) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:126) 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:433) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:613) Caused by: java.lang.AssertionError at org.apache.myfaces.trinidadinternal.application.StateManagerImpl._removeTransientComponents(StateManagerImpl.java:728) at org.apache.myfaces.trinidadinternal.application.StateManagerImpl.saveSerializedView(StateManagerImpl.java:252) at org.ajax4jsf.framework.ajax.AjaxStateManager.saveSerializedView(AjaxStateManager.java:90) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:594) at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:182) at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:232) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) ... 40 more -- 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, 11 months

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1352) Allow @Startup to be used on conversation scoped components

by Mike Quilleash (JIRA)

Allow @Startup to be used on conversation scoped components ----------------------------------------------------------- Key: JBSEAM-1352 URL: http://jira.jboss.com/jira/browse/JBSEAM-1352 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Environment: Any Reporter: Mike Quilleash @Startup on a conversation component would instantiate and call @Create the component whenever a conversation context is created (not when nested conversations start tho as the root conversation will already have created it). Not sure if this should be done when a conversation context is created or when a long running conversation is begun. Use case is wanting to pass information from a nested conversation to it's parent, at the moment the parent has to explicitly instantiate any components it wishes to share with the child. If the child creates it they get attached to the child conversation id and destroyed when the child ends. e.g. I want to pass FacesMessages (or some equivalent) from a edit screen to it's parent search screen when the edit is completed. "Entity created/updated". A current workaround I think is to use the event stuff to have an @Observer in the relevant components to create themselves. -- 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, 11 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2007