January 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-321) Define interceptors in components.xml

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-321?page=all ] Pete Muir closed JBSEAM-321. ---------------------------- Resolution: Duplicate Issue This is really a dupe of JBSEAM-1485 > Define interceptors in components.xml > ------------------------------------- > > Key: JBSEAM-321 > URL: http://jira.jboss.com/jira/browse/JBSEAM-321 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.0.1 > Reporter: Gavin King > Assigned To: Gavin King > > It makes sense to allow definition of an interceptor stack in components.xml: -- 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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-334) Examples need changes to run on JBoss 5.x

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-334?page=all ] Pete Muir closed JBSEAM-334. ---------------------------- Resolution: Out of Date Seam has moved to RI a while back > Examples need changes to run on JBoss 5.x > ----------------------------------------- > > Key: JBSEAM-334 > URL: http://jira.jboss.com/jira/browse/JBSEAM-334 > Project: JBoss Seam > Issue Type: Bug > Components: Examples > Affects Versions: 1.0.1 > Reporter: Stan Silvert > > The examples need to be updated so that they can deploy and run on JBoss 5.x. > JBoss 5.x ships with the RI JSF 1.2 implementation. To get the examples to run on JBoss 5.x, you need to remove this from web.xml: > <listener> > <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class> > </listener> > For JBoss 5.x, the listener for JSF 1.2 is added automatically, so you don't need to put it in web.xml. > Also, there are some third party libraries such as cglib that do not ship with JBoss 5.x. I was able to get the examples to run on JBoss 5.x by adding Seam's thridparty-all.jar to the server/default/lib directory. However, that's probably not the best way to handle the problem. -- 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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-318) ViewHandler.createView using SeamViewHandler.calculateLocale tries to use already released FacesContext when used outside lifecycle

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-318?page=all ] Pete Muir closed JBSEAM-318. ---------------------------- Resolution: Out of Date SeamViewHandler is dead. > ViewHandler.createView using SeamViewHandler.calculateLocale tries to use already released FacesContext when used outside lifecycle > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-318 > URL: http://jira.jboss.com/jira/browse/JBSEAM-318 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Affects Versions: 1.0.1 > Environment: JBoss 4.0.4.GA > MyFaces 1.1.3 > Reporter: Tuomas Kiviaho > > ViewHandler.createView can't be used outside lifecycle phases. The locale calculation done by seam view handler using locale selector ends up in a NullPointerException (should propably be t be IllegalStateException) > in MyFaces external context implementation if FacesContext had already been consumed by Seam threadlocals (Contexts) > One could ask why I am using createView outside lifecycle, but this is what happens when done so. > StackTrace (NullPointerException): > ApplicationMap.getAttribute(String) line: 42 > ApplicationMap(AbstractAttributeMap).get(Object) line: 87 > FacesApplicationContext.get(String) line: 46 > FacesApplicationContext.get(Class) line: 79 > Init.instance() line: 95 > Component.getInstanceFromFactory(String) line: 1199 > Component.getInstance(String, boolean, Object) line: 1176 > Component.getInstance(String, ScopeType, boolean) line: 1169 > LocaleSelector.instance() line: 123 > SeamViewHandler.calculateLocale(FacesContext) line: 32 > JspViewHandlerImpl.createView(FacesContext, String) line: 130 > To tacle the symptom: > 1. FacesContext.getExternalContext could be used inside Seam's FacesApplicationContext instead of direct reference to see if the context has been released by catching the IllegalStateException that MyFaces throws. > 2. Using external context with RuntimeException precaution > (3. Blame the messenger) > But what then can be done inside Seam goes beyond my knowledge, since Seam's component instantiation is a core part of the system. Of course this step can be left alone just by a try/catch around locale selector instantiation and continuing with a warning. -- 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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-300) Propagate variable to parent conversation

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-300?page=all ] Pete Muir closed JBSEAM-300. ---------------------------- Resolution: Duplicate Issue > Propagate variable to parent conversation > ----------------------------------------- > > Key: JBSEAM-300 > URL: http://jira.jboss.com/jira/browse/JBSEAM-300 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Raul Piaggio > > It is often desirable to output a value from a nested conversation to its parent. > One possible way is to add a property to the @Out annotation (i.e.: @Out(scope=CONVERSATION, level=PARENT)). If there's no outer conversation it can propagate to SESSION. > Alternatively, it can be explicited by the inner conversation via the @Begin or @End annotations. (i.e.: @Begin(nested=true, outputs="parameter1,parameter2"). The variables "parameter1" and "parameter2" would be promoted to the outer conversation when the inner one ends. I think @Begin is better since a conversation may end via a pageflow <end-conversation/>. Also, this is similar of how we usually declare methods in any language (output explicit in signature). -- 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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-273) Specify HTTP headers in pages.xml

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-273?page=all ] Pete Muir reassigned JBSEAM-273: -------------------------------- Assignee: Norman Richards (was: Gavin King) > Specify HTTP headers in pages.xml > --------------------------------- > > Key: JBSEAM-273 > URL: http://jira.jboss.com/jira/browse/JBSEAM-273 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Norman Richards > > Eg. it would be very useful to be able to do: > <page view-id="document.xhtml" expires="20000"/> > Where expires gives a number in seconds, which is converted by Seam to an absolute time. > But more generally, we want to be able to do stuff like: > <page view-id="document.xml"> > <header name="Content-Type">test/xml</header> > </page> -- 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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-271) null Seam components OR default scope for non-Seam components

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-271?page=all ] Pete Muir closed JBSEAM-271. ---------------------------- Resolution: Won't Fix I don't see how this is useful. There is a default, the scope of the outjecting component. Alternatively, you can use the manager pattern to specify a default scope. I've also never seen a single request for this functionality on the forum. > null Seam components OR default scope for non-Seam components > ------------------------------------------------------------- > > Key: JBSEAM-271 > URL: http://jira.jboss.com/jira/browse/JBSEAM-271 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Raul Piaggio > Priority: Minor > > Seam-managed components have a default Seam scope and are always created upon reference by a view. > User-managed variables can be created and destroyed ad-hoc, but they don't have a default scope (it has to be specified in every outjection, leading to more costly code maintenance). > The request is for a feature to allow creating and destroying variables in the Seam-controlled space but specify their scope in a unique location. (See forum reference for an example). > Suggestions: > 1) Allow null Seam components. This could be achieved with a "create" or "required" property in the @Role annotation (and in @Scope). Defaults to "true", but we could specify "create=false" or "required=false". > 2) Create another annotation, similar to @Role and with the same properties. This would allow to specify a role and default scope for a class, which would not be Seam-managed in that role. > Note that ideally, we would have role granularity, not class. That is to say, the same class would be Seam-managed in some roles but not in others. (Again, see forum reference). > Thank you. -- 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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-260) FacesMessages component: add convenience methods for severity levels.

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-260?page=all ] Pete Muir closed JBSEAM-260. ---------------------------- Resolution: Won't Fix We already have around 20 addXXX methods in facesMessages, doing this would mean we have around 80... > FacesMessages component: add convenience methods for severity levels. > ---------------------------------------------------------------------- > > Key: JBSEAM-260 > URL: http://jira.jboss.com/jira/browse/JBSEAM-260 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Ryan Dewell > Priority: Trivial > > Since there are a small and finite number of severity levels in JSF, add convenience methods for each in facesMessages. Example: > addFatal(String) > addWarn(String) > addInfo(String) > addError(String > One less import for developer, and less typing. -- 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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-220) Plain EJBs (non-Seam-components) not detected when running on E-EJB

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-220?page=all ] Pete Muir closed JBSEAM-220. ---------------------------- Resolution: Out of Date Now using Embedded JBoss > Plain EJBs (non-Seam-components) not detected when running on E-EJB > ------------------------------------------------------------------- > > Key: JBSEAM-220 > URL: http://jira.jboss.com/jira/browse/JBSEAM-220 > Project: JBoss Seam > Issue Type: Bug > Components: EJB3 > Reporter: Gavin King > Assigned To: Gavin King > > When deploying on embeddable ejb3, we need to scan archives with no seam.properties file for EJB3 components. We can do this by using the servlet context to get a list of all resources. -- 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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-193) <s:link propagation="kill"/>

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-193?page=all ] Pete Muir closed JBSEAM-193. ---------------------------- Resolution: Out of Date We now have end-before-redirect. > <s:link propagation="kill"/> > ---------------------------- > > Key: JBSEAM-193 > URL: http://jira.jboss.com/jira/browse/JBSEAM-193 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > > Kill the conversation at the beginning of the request, instead of ending it at the end of the request.... -- 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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-143) Support configurable faces error messages severity with hibernate validator

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-143?page=all ] Pete Muir closed JBSEAM-143. ---------------------------- Resolution: Out of Date No longer using @IfInvalid. And I don't entirely see that you'd ever want this anything but ERROR. > Support configurable faces error messages severity with hibernate validator > --------------------------------------------------------------------------- > > Key: JBSEAM-143 > URL: http://jira.jboss.com/jira/browse/JBSEAM-143 > Project: JBoss Seam > Issue Type: Patch > Components: JSF > Affects Versions: 1.0 beta 2 > Environment: All > Reporter: Andrew > Attachments: JBSEAM-143.diff > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I would be great if the "ifInvalid" interceptor annotation could take a severity so that it would not default to FacesMessage.INFO. I would rather have hibernate validation issues as error. -- 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

16 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2008