February 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3091) Extend s:decorate by adding #{disabled} attribute

by Scott Bader (JIRA)

Extend s:decorate by adding #{disabled} attribute ------------------------------------------------- Key: JBSEAM-3091 URL: http://jira.jboss.com/jira/browse/JBSEAM-3091 Project: Seam Issue Type: Feature Request Affects Versions: 2.0.2.GA Reporter: Scott Bader Desire is to conditionally format based on the disabled/enabled state of the component. Refer also to forum question: Is it possible to pass the 'disabled' attribute into s:decorate like #{required} and #{invalid} are? Has anyone figured out a nice workaround for this? http://www.jboss.com/index.html?module=bb&op=viewtopic&t=115864 -- 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

15 years, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3426) Make Exception Handling, Redirection URI a page request rather than Ajax request for ICEfaces integration

by judy guglielmin (JIRA)

Make Exception Handling, Redirection URI a page request rather than Ajax request for ICEfaces integration --------------------------------------------------------------------------------------------------------- Key: JBSEAM-3426 URL: https://jira.jboss.org/jira/browse/JBSEAM-3426 Project: Seam Issue Type: Bug Components: Exception Handling Environment: ICEfaces Reporter: judy guglielmin Assignee: Pete Muir Fix For: 2.1.0.CR1 please see ICEfaces jira #2990 http://jira.icefaces.org/browse/ICE-2990 Pete...if you require more info, test app, just let us know. Since there are other integrations, it was difficult for us to know all ramifications in order to produce a patch. This is pretty important as all redirections for exception-handling done in UPDATE_MODEL and INVOKE_APPLICATION are included here. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2051) please put WEB-INF under view instead of resources (seam-gen)

by Dan Allen (JIRA)

please put WEB-INF under view instead of resources (seam-gen) ------------------------------------------------------------- Key: JBSEAM-2051 URL: http://jira.jboss.com/jira/browse/JBSEAM-2051 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.CR1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.x I am aware that there is no hotter issue than this one. But PAUSE before rejecting it and hear me out. The current seam-gen project structure is src action model resources WEB-INF META-INF view IDEs choke on this structure, but it really comes down to just one folder. The src/ and resources/ directory really aren't a problem. The real problem is that WEB-INF/ just needs to be under view/. Seriously, if that can happen, the IDEs really will be happier. People are not arguing for the sake of arguing. This convention is the way that Sun laid out more than a decade ago and vendors have catered to it ever since (even JBoss). It's not like we woke up one day and said, gee, let's put WEB-INF/ in the folder with web artifacts. Rather than try to change the whole world, can we just move this one folder? I promise I am not arguing to read my own writing. Proposed structure src action model resources META-INF view WEB-INF -- 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

15 years, 9 months

6
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3913) Lower web site performance once logged in at seamframework.org

by Julien Kronegg (JIRA)

Lower web site performance once logged in at seamframework.org -------------------------------------------------------------- Key: JBSEAM-3913 URL: https://jira.jboss.org/jira/browse/JBSEAM-3913 Project: Seam Issue Type: Bug Components: WS Environment: MSIE 6.0 and Firefox 3.0.5 Reporter: Julien Kronegg Priority: Minor The Seam web site performance is much lower once logged in (i.e. the pages take much longer to load). For example, on 2009.01.26, the page http://seamframework.org/Community/Forums loads in: - when not logged in: 2 seconds - when logged in: 9 seconds The timings are reproductible when reloading the pages. Since the forum is implemented using Seam technology, this is not a good advertizing. ;-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3578) Bad link named "JBoss Product Versioning Guidelines" in seamframework.org download section

by Julien Kronegg (JIRA)

Bad link named "JBoss Product Versioning Guidelines" in seamframework.org download section ------------------------------------------------------------------------------------------ Key: JBSEAM-3578 URL: https://jira.jboss.org/jira/browse/JBSEAM-3578 Project: Seam Issue Type: Bug Components: Wiki Environment: web site Reporter: Julien Kronegg Assignee: Christian Bauer Priority: Optional The seamframework web site's download section ( http://www.seamframework.org/Download ) has a link named "JBoss Product Versioning Guidelines" which points to http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProductVersioning This page redirects to http://www.jboss.org/community/docs/DOC-10725 so the link on the download page should be changed -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3916) SeamELResolver.resolveInMap() will resolve a property "size" to ((Map)base).size() even if the Map contains a key named "base" - instead, it should return null and allow javax.el.MapELResolver to resolve the property to ((Map)base).get("size")

by Ian Springer (JIRA)

SeamELResolver.resolveInMap() will resolve a property "size" to ((Map)base).size() even if the Map contains a key named "base" - instead, it should return null and allow javax.el.MapELResolver to resolve the property to ((Map)base).get("size") --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3916 URL: https://jira.jboss.org/jira/browse/JBSEAM-3916 Project: Seam Issue Type: Bug Components: EL Affects Versions: 2.1.0.SP1 Reporter: Ian Springer Priority: Critical I have an expression: #{MyBean.someMap['size']} In my non-Seam JSF app, this expression was resolving to MyBean.getSomeMap().get("size"). However, when I integrated Seam into my app, the expression started instead resolving to MyBean.getSomeMap().size(), which broke my app. This is occurring because SeamELResolver is ahead of javax.el.MapELResolver in the CompositeELResolver resolver list, and its resolveInMap() function ensures a property named "size" resolves to ((Map)base).size() This makes it impossible for me to obtain the value of the element with key "size" from my Map via EL. To solve this, I suggest changing SeamELResolver.resolveInMap() to the following: private Object resolveInMap(ELContext context, Object base, Object property) { if ( !( (Map) base ).containsKey("size") && "size".equals(property) ) { context.setPropertyResolved(true); return ( (Map) base ).size(); } else if ( !( (Map) base ).containsKey("values") && "values".equals(property) ) { context.setPropertyResolved(true); return ( (Map) base ).values(); } else if ( !( (Map) base ).containsKey("keySet") && "keySet".equals(property) ) { context.setPropertyResolved(true); return ( (Map) base ).keySet(); } else if ( !( (Map) base ).containsKey("entrySet") && "entrySet".equals(property) ) { context.setPropertyResolved(true); return ( (Map) base ).entrySet(); } else { return null; } } The only disadvantage of this is that if you actually are trying to get at map.size(), there will be no way to do so if the Map happens to contain a key named "size". However, in such a case, #{MyBean.someMap.keySet.size} or #{MyBean.someMap.values.size} could instead be used to obtain the Map's size. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3383) REST @Context injection for Seam component resources

by Christian Bauer (JIRA)

REST @Context injection for Seam component resources ---------------------------------------------------- Key: JBSEAM-3383 URL: https://jira.jboss.org/jira/browse/JBSEAM-3383 Project: Seam Issue Type: Bug Components: WS Reporter: Christian Bauer Assignee: Christian Bauer Priority: Critical The JAX-RS @Context annotation on fields does not work for JAX-RS resources when the resource class is a Seam component (instantiated and intercepted by Seam). AFAIK the fields annotated with @Context are injected with a proxy when instantiated by Resteasy. When Seam instantiates and manages the object, the proxy isn't injected. Need to find out how Resteasy does that and port it/call it from a Seam interceptor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3673) horizontalAlignment="right" broken in PDF cells (regression)

by Dan Allen (JIRA)

horizontalAlignment="right" broken in PDF cells (regression) ------------------------------------------------------------ Key: JBSEAM-3673 URL: https://jira.jboss.org/jira/browse/JBSEAM-3673 Project: Seam Issue Type: Bug Components: PDF Affects Versions: 2.1.0.SP1 Reporter: Dan Allen Fix For: 2.1.1.CR1 All of a sudden the horizontal alignment on PDF cells stopped working in Seam 2.1. You can see the discrepancy by deploying the iText example in Seam 2.0 and Seam 2.1 and observing the servlet path /seam-itext/format.seam. You'll notice that the Order Summary table is formatted differently in the two cases, with the right-hand alignment not taking affect under Seam 2.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

7
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2589) gen-ui: order of fields in generated forms

by Stephan Grter (JIRA)

gen-ui: order of fields in generated forms ------------------------------------------ Key: JBSEAM-2589 URL: http://jira.jboss.com/jira/browse/JBSEAM-2589 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.1.GA Environment: Mac OS X 10.4.10 PPC, Java 1.5.0_13-121, JBoss-AS 4.2.2.GA, Seam 2.0.1.GA, PostgreSQL 8.2.4 Reporter: Stephan Grter When I generate the xhtml files from existing entities, then the entry fields will be displayed in alphabetical order of the entity properties and not in the order of declaration. For rapid prototyping it would be desirable, if the fields would appear in the order of declaration. Since the fields in the auto generated database table are in the the order of declaration, this should be possible for gen-ui 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

15 years, 9 months

8
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2347) ComponentScanner fails with classes in WEB-INF/classes on websphere

by Norman Richards (JIRA)

ComponentScanner fails with classes in WEB-INF/classes on websphere ------------------------------------------------------------------- Key: JBSEAM-2347 URL: http://jira.jboss.com/jira/browse/JBSEAM-2347 Project: JBoss Seam Issue Type: Bug Reporter: Norman Richards Assigned To: Norman Richards Priority: Minor Fix For: 2.0.1.GA If looks like websphere adds the WAR contents directly to the classpath, which causes scanner errors when loading: java.lang.NoClassDefFoundError: WEB-INF.classes.com.somecompany.SomeComponent I'll fix the scanner as soon as I've verified the issue on websphere. -- 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

15 years, 9 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 February 2009