May 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-116) Pluggable conversationId handler

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-116?page=all ] Gavin King updated JBSEAM-116: ------------------------------ Fix Version/s: 1.3.1.BETA1 (was: 1.3.0.ALPHA) > Pluggable conversationId handler > -------------------------------- > > Key: JBSEAM-116 > URL: http://jira.jboss.com/jira/browse/JBSEAM-116 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Priority: Critical > Fix For: 1.3.1.BETA1 > > > Currently, there is no way to plug in a user-defined strategy for decoding and encoding the conversationId in the request/response. > We need this to really properly support AJAX/Soap invocations. -- 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

17 years, 7 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-157) Pageflow composition

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-157?page=all ] Gavin King updated JBSEAM-157: ------------------------------ Fix Version/s: 1.3.1.BETA1 (was: 1.3.0.ALPHA) > Pageflow composition > -------------------- > > Key: JBSEAM-157 > URL: http://jira.jboss.com/jira/browse/JBSEAM-157 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.3.1.BETA1 > > > The jBPM mechanism for process composition does not work for pageflow. Need to figure out a different mechanism. AFAICT, this needs to be solved more in jBPM than in Seam. -- 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

17 years, 7 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-274) More flexible mapping of URLs to view ids

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-274?page=all ] Gavin King updated JBSEAM-274: ------------------------------ Fix Version/s: 1.3.1.BETA1 (was: 1.3.0.ALPHA) > More flexible mapping of URLs to view ids > ----------------------------------------- > > Key: JBSEAM-274 > URL: http://jira.jboss.com/jira/browse/JBSEAM-274 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.3.1.BETA1 > > > For example, I want to be able to use a URL like this: > http://mydomain.com/myblog/archive/200306 > To get me to archive.xhtml with a request parameter 200306 (not really a request parameter, but we could try to abstract that so that it can be used with @RequestParameter). > Not sure if this is possible without changing the JSF implementation. -- 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

17 years, 7 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-802) Support for code coverage (emma) in Seam-gen projects

by Mariusz Smykula (JIRA)

Support for code coverage (emma) in Seam-gen projects ----------------------------------------------------- Key: JBSEAM-802 URL: http://jira.jboss.com/jira/browse/JBSEAM-802 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.1.6.GA Reporter: Mariusz Smykula This can be very helpful for developers using seam-gen :) -- 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

17 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-718) Make exception object available in redirected/rendered view

by Peter Muir (JIRA)

Make exception object available in redirected/rendered view ----------------------------------------------------------- Key: JBSEAM-718 URL: http://jira.jboss.com/jira/browse/JBSEAM-718 Project: JBoss Seam Issue Type: Feature Request Reporter: Peter Muir -- 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

17 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1050) Enhanced EL working for all <s:> tags

by Greg Zoller (JIRA)

Enhanced EL working for all <s:> tags ------------------------------------- Key: JBSEAM-1050 URL: http://jira.jboss.com/jira/browse/JBSEAM-1050 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.0.GA Environment: n/a Reporter: Greg Zoller Priority: Minor Seam improves EL, notably the ability to call methods w/parameters, for its own attributes. For example <s:link action="#{foo.bar(a,b,c)}"> is valid and the correct method/parameters will be used. But... It seems that non-Seam attributes of these same tags are merely passed through to JSF. For example if I add a rendered attributed to <s:link> and try to use a method call w/parameters it chokes w/an exception complaining about the '('. I'm not advocating that Seam correct JSF's lost opportunity by redoing all JSF tags (unless you are really motivated), but certainly all the attributes of the <s:> tags Seam does support should handle the improved EL uniformly. Apologies if this is a dup. Nothing like this jumped out at me when I searched Jira. -- 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

17 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1015) Cannot disable built-in components

by Leszek Kowalski (JIRA)

Cannot disable built-in components ---------------------------------- Key: JBSEAM-1015 URL: http://jira.jboss.com/jira/browse/JBSEAM-1015 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.0.GA Environment: Seam 1.2.0Patch1, Jetty 5.1.12 Reporter: Leszek Kowalski Since rev 1.152 of Initialization.java (JIRA-897) it is not possible to disable built-in Seam component in components.xml (using <ns:componentName installed="false"). Here is problematic code: //if this class already has the @Name annotation, the XML element //is just adding configuration to the existing component, don't //add another ComponentDescriptor (this is super-important to //allow overriding!) if ( nameAnnotation!=null && nameAnnotation.value().equals(name) ) { Install install = clazz.getAnnotation(Install.class); if ( install.value() ) { className = null; } } For all components with @Install annotation className is set to null and installComponentFromXmlElement() cannot create "not-installed ComponentDescriptor". -- 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

17 years, 7 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-898) s:hasRole, etc in EL in pages.xml and other places

by Gavin King (JIRA)

s:hasRole, etc in EL in pages.xml and other places -------------------------------------------------- Key: JBSEAM-898 URL: http://jira.jboss.com/jira/browse/JBSEAM-898 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.7.GA Because of MyFaces inability to implement the JSF spec correctly, EL functions are not supported in lots of places they are useful. We need to find a better way. -- 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

17 years, 7 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1135) double byte encoding issue of the Seam Debug Page

by Hiroyuki Wada (JIRA)

double byte encoding issue of the Seam Debug Page ------------------------------------------------- Key: JBSEAM-1135 URL: http://jira.jboss.com/jira/browse/JBSEAM-1135 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.1.GA Reporter: Hiroyuki Wada The encoding of the Seam Debug Page isn't UTF-8 now, so the Seam Debug Page show garbage characters when Context have double byte characters. I think it should be set UTF-8 to content type in SeamDebugPhaseListener.java as follows. response.setContentType("text/html; UTF-8"); -- 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

17 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1089) Allow extended EL method expression construction programmatically

by Mike Quilleash (JIRA)

Allow extended EL method expression construction programmatically ----------------------------------------------------------------- Key: JBSEAM-1089 URL: http://jira.jboss.com/jira/browse/JBSEAM-1089 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash The enhanced EL parser for method parameters is not available programmatically. e.g. facesContext.getApplication().getExpressionFactory().createMethodExpression( "#{bean.func( param )}" ); This is because the expression factory is only loaded into the facelets compiler not the JSF application. As Seam already has an overriden Application implementation (SeamApplication12) it should be trivial to change this so getExpressionFactory() returns the SeamExpressionFactory which would delegate down to the default getExpressionFactory(). Then the enhanced EL would be available in the API as well as facelets files. (Facelets just calls Application.getExpressionFactory() so this should work as it did before). This would be extremely useful for me as I do a fair bit of dynamic component/EL generation. -- 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

17 years, 7 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2007