July 2009 - seam-issues - Jboss List Archives

[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-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-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-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

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1336) Let Seam annotations be used as meta-annotations

by Gavin King (JIRA)

Let Seam annotations be used as meta-annotations ------------------------------------------------ Key: JBSEAM-1336 URL: http://jira.jboss.com/jira/browse/JBSEAM-1336 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King As a a general principle, Seam annotations that currently appear on component classes, should be usable as meta-annotations. For example, discussion in JBSEAM-1117 suggests that @RaiseEvent could be a meta-annotation. @Restrict is another great example, as is @Scope, @Interceptors, @Install. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1275) Configuring nested objects in components.xml

by Pete Muir (JIRA)

Configuring nested objects in components.xml -------------------------------------------- Key: JBSEAM-1275 URL: http://jira.jboss.com/jira/browse/JBSEAM-1275 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Pete Muir Priority: Optional I would ilike to be able to do <mail:meldware> <mail:users> <value> <mail:user username="pmuir" password="secret"> <mail:aliases> <value>pmuir(a)example.com</value> </mail:aliases> </mail:user> </value> </mail:users> </mail:meldware> Of course, I can do this by making each user a Seam component and then injecting them using EL, but this just isn't as neat. -- 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

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1270) use JSF RI expression factory context-param

by Norman Richards (JIRA)

use JSF RI expression factory context-param ------------------------------------------- Key: JBSEAM-1270 URL: http://jira.jboss.com/jira/browse/JBSEAM-1270 Project: JBoss Seam Issue Type: Task Reporter: Norman Richards This will soon work in JSP 2.1 environments, so we'll be able to use that: https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=563 -- 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-1260) Feature request for a Seam/Richfaces/EJB3 example which includes a tree component.

by asddsa dsasd (JIRA)

Feature request for a Seam/Richfaces/EJB3 example which includes a tree component. ---------------------------------------------------------------------------------- Key: JBSEAM-1260 URL: http://jira.jboss.com/jira/browse/JBSEAM-1260 Project: JBoss Seam Issue Type: Feature Request Components: Examples Affects Versions: 1.2.1.GA Reporter: asddsa dsasd Priority: Optional I'm fairly new to seam and richfaces. There are no tutorials, that I'm aware of, that explain how to do simple ajax tree component using richfaces, seam and ejb3. If possible I would like to request such example (complete eclipse project if possible) to aid me in learning. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1269) Support for remotely deployed EJBs

by Roland Räz (JIRA)

Support for remotely deployed EJBs ---------------------------------- Key: JBSEAM-1269 URL: http://jira.jboss.com/jira/browse/JBSEAM-1269 Project: JBoss Seam Issue Type: Feature Request Components: EJB3 Affects Versions: 1.2.1.GA Reporter: Roland Räz We found that Seam currently has only weak support for remotely located EJBs. The only way to get to a remotely located EJB reference is to use a façade or a factory, which forces us to write unnecessary glue code. A typical use case would be a stateless SOA service, which is usually deployed remotely. This remote service might not even use Seam. We would like to see Seam support component declarations for interfaces + jndi-name in components.xml (as opposed to class + jndi-name). This would allow Seam to find remote components, which could be referenced through the EL. Obviously no in-/outjection would work, which is usually not required for stateless remote services. This feature request has been already discussed in the Seam Forum. -- 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
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2009