October 2007 - seam-issues - Jboss List Archives

[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

16 years, 11 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1906) Client side validation

by Dupont Dupont (JIRA)

Client side validation ---------------------- Key: JBSEAM-1906 URL: http://jira.jboss.com/jira/browse/JBSEAM-1906 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Dupont Dupont Supporting client side validation with javascript would be cool with Hibernate annotations. Feature asked in thread http://jboss.com/index.html?module=bb&op=viewtopic&t=109404. Some Jsf libraries have already some cool javascript validation features for instance Quipukit with http://www.teamdev.com/quipukit/demo/validators/Validators_standard.jsf. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1936) Provide other Caching framework integration to be used with Seam

by Joshua Jackson (JIRA)

Provide other Caching framework integration to be used with Seam ---------------------------------------------------------------- Key: JBSEAM-1936 URL: http://jira.jboss.com/jira/browse/JBSEAM-1936 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.0.0.CR1 Environment: All Reporter: Joshua Jackson Priority: Minor Fix For: 2.0.1.GA Recently I tried using JBoss cache for caching page and components and deployed it on Glassfish but it turns out it has dependency to some other jboss library like the JBoss MBeans. Perhaps it would be nice if Seam provides and abstraction for caching to some other caching framework like ehcache or OSCache just like Hibernate did. -- 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

4
6
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

16 years, 11 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

16 years, 11 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

16 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1661) Use more templating in seam-gen

by Matt Drees (JIRA)

Use more templating in seam-gen ------------------------------- Key: JBSEAM-1661 URL: http://jira.jboss.com/jira/browse/JBSEAM-1661 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.BETA1 Reporter: Matt Drees Priority: Minor Seam-gen'ed apps tend to look very copy-pasted, which makes it difficult to tweak things once created. It'd be nice if it used more templating and/or source tags (maybe going as far as using Rick Hightower's <a:field fieldName="title" entity="#{CDManagerBean.cd}" /> tag (see http://www.ibm.com/developerworks/java/library/j-facelets/index.html and http://www.ibm.com/developerworks/java/library/j-facelets2.html)). Also, I think it would be good for people new to JSF to see good patterns in an example app. The downside is it's more complex, but I think it's worth it. -- 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

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1856) Transaction Commit and Rollback events

by Moshe Immerman (JIRA)

Transaction Commit and Rollback events -------------------------------------- Key: JBSEAM-1856 URL: http://jira.jboss.com/jira/browse/JBSEAM-1856 Project: JBoss Seam Issue Type: Feature Request Reporter: Moshe Immerman It would be nice to have org.jboss.seam.transactionCommit and org.jboss.seam.transactionRollback events -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1908) Booking example clones need updating to newer s:decorate

by Pete Muir (JIRA)

Booking example clones need updating to newer s:decorate -------------------------------------------------------- Key: JBSEAM-1908 URL: http://jira.jboss.com/jira/browse/JBSEAM-1908 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.0.GA -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1680) Have a way to "bootsrap" the seam engine for batch processes

by Denis Forveille (JIRA)

Have a way to "bootsrap" the seam engine for batch processes ------------------------------------------------------------ Key: JBSEAM-1680 URL: http://jira.jboss.com/jira/browse/JBSEAM-1680 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.BETA1, 1.2.1.GA Reporter: Denis Forveille It should be possible to write a "pure" batch processes that uses seam components. Seam should provide a way to "bootstrap" the "seam engine" outside any web/jee container to allow programmers to reuse seam components outside a war, typically from a standard "main" method, run with a standard j2se class. Typical scenario/usage for this: - an online application build around seam, POJOs and hibernate. - the business seam components ("managers" + "model" classes) are isolated into a separate jar file (common.jar) - the "view controllers", which are seam components (aka "backing beans") are directly held into the war module - the war module uses the business components held into the common.jar module. - a batch process, which is standard j2se class with a main method, performs some business process by calling the "business" seam components defined in the common.jar file. The high-level algorithm of this "batch" process is the following - bootstrap the seam engine - for each business item to process (maybe tens of thousand or more...): - begin transaction - do some business stuff by calling the seam components in common.jar that read/update the database - commit - shutdown the seam engine For this, we need a class or harness to "boostrap" the seam engine. This harness should not depends on any of the services provided by a typical web/ jee container, this includes: - naming/jndi - security - jsf/jsp/facelets - ...etc The harness should be able to manage injection/bijection of user defined components and also to provide the injection of some non-web dependent object like the hibernate session and the logger. Of course none of the "web" functions are required (Conversation managment, @DataModel etc...) At a minimun, this harness should be able to handle the @Name, @In, @Out, @Create, @Destroy, @Factory, @Transactional, @Logger annotations Big Thanks... -- 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

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 October 2007