August 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-652) Allow use of EHCache with <s:cache/>

by Gavin King (JIRA)

Allow use of EHCache with <s:cache/> ------------------------------------ Key: JBSEAM-652 URL: http://jira.jboss.com/jira/browse/JBSEAM-652 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Priority: Minor -- 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

18 years, 2 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1692) Rome tag library

by Gavin King (JIRA)

Rome tag library ---------------- Key: JBSEAM-1692 URL: http://jira.jboss.com/jira/browse/JBSEAM-1692 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King The wiki example renders Atom via the Rome library. We should wrap it in JSF tags. -- 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

18 years, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-650) <s:formattedText value="#{post.body}" highlight="#{word}"/>

by Gavin King (JIRA)

<s:formattedText value="#{post.body}" highlight="#{word}"/> ----------------------------------------------------------- Key: JBSEAM-650 URL: http://jira.jboss.com/jira/browse/JBSEAM-650 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.5.GA Seam needs to support wikitext ootb. -- 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

18 years, 2 months

5
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1862) jsf control (convertor) that will convert bytes to kilobytes/megabytes/...

by Adrian Mitev (JIRA)

jsf control (convertor) that will convert bytes to kilobytes/megabytes/... -------------------------------------------------------------------------- Key: JBSEAM-1862 URL: http://jira.jboss.com/jira/browse/JBSEAM-1862 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Adrian Mitev This is useful when fileupload is performed to show the file size in user-readable form. -- 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

18 years, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1793) s:transformImageSize - could be optimized if image already has requested size

by henrik lindberg (JIRA)

s:transformImageSize - could be optimized if image already has requested size ----------------------------------------------------------------------------- Key: JBSEAM-1793 URL: http://jira.jboss.com/jira/browse/JBSEAM-1793 Project: JBoss Seam Issue Type: Feature Request Reporter: henrik lindberg Priority: Optional If an image already has the requested size, s:transformImageSize does not have to go through the drawing logic. Would save some cycles. -- 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

18 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1502) Declarative renderers in seam-ui

by Pete Muir (JIRA)

Declarative renderers in seam-ui -------------------------------- Key: JBSEAM-1502 URL: http://jira.jboss.com/jira/browse/JBSEAM-1502 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Pete Muir Fix For: 1.3.0.BETA1 Evaluate and implement -- 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

18 years, 2 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1499) Remove org.jboss.seam.ui.util.cdk.*

by Pete Muir (JIRA)

Remove org.jboss.seam.ui.util.cdk.* ----------------------------------- Key: JBSEAM-1499 URL: http://jira.jboss.com/jira/browse/JBSEAM-1499 Project: JBoss Seam Issue Type: Task Components: JSF Reporter: Pete Muir Fix For: 1.3.0.BETA1 These classes have been copied from ajax4jsf -- 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

18 years, 2 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1522) @Intercept is gone but still documented

by Christian Bauer (JIRA)

@Intercept is gone but still documented --------------------------------------- Key: JBSEAM-1522 URL: http://jira.jboss.com/jira/browse/JBSEAM-1522 Project: JBoss Seam Issue Type: Bug Reporter: Christian Bauer Assigned To: Gavin King How do I disable interception now? -- 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

18 years, 2 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-671) Add an inheritance mechanism for themes

by Bill Wallace (JIRA)

Add an inheritance mechanism for themes --------------------------------------- Key: JBSEAM-671 URL: http://jira.jboss.com/jira/browse/JBSEAM-671 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 1.1.0.GA Reporter: Bill Wallace It would be very nice to have an item in a theme that allowed one to indicate which theme to inherit from, eg: default theme - no inheritance: printable.properties: org.jboss.seam.theme.inherit default accessible.properties: org.jboss.seam.theme.inherit default accessible-printable.properties org.jboss.seam.theme.inherit printable accessible ... Thus, the accessible-printable version would inherit first from printable, then from accessible. Assuming they could in fact co-exist, that might work out nicely to produce an accessible-printable version. It would also be nice to allow inheritance from generic property files that are NOT explicit themes - that way, you can put portions of a theme in another file, and just inherit from all the required themes. Note that the Java API makes this relatively easy, just be creating a chain of inheritance. (Note that only accessible would chain to default, a new printable would be needed that only inherited from accessible, not from anything else.) -- 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

18 years, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1516) Issuing another request while waiting for AJAX request to return causes concurrent conversation exception

by Robb Greathouse (JIRA)

Issuing another request while waiting for AJAX request to return causes concurrent conversation exception --------------------------------------------------------------------------------------------------------- Key: JBSEAM-1516 URL: http://jira.jboss.com/jira/browse/JBSEAM-1516 Project: JBoss Seam Issue Type: Bug Components: Async Affects Versions: 1.2.1.GA Environment: RichFaces, AJAX and Seam 1.2.1 Reporter: Robb Greathouse Priority: Minor When the user kicks off an AJAX request and then clicks on a link before it responds we get a concurrent conversation exception. Shouldn't a request that would cause this error be held until the request either times out or is completed and then passed through? Thinking that the filter in tomcat that gets the conversation could also prevent consurrency crashes. -- 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

18 years, 2 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2007