November 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-2298) Allow validateAll to overwrite or supplement hibernate validator

by dapeng wang (JIRA)

Allow validateAll to overwrite or supplement hibernate validator ---------------------------------------------------------------- Key: JBSEAM-2298 URL: http://jira.jboss.com/jira/browse/JBSEAM-2298 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.GA Reporter: dapeng wang Fix For: 2.0.1.GA Currently, if a custom validator method is specified on a component, the underlying default hibernate validator will be overwritten und therefore not checked by validateAll. Pls extend validateAll with an attribute supplment="true" to allow either overwriteing default validation or allow supplment of default validation with custom validation. -- 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
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-2221) Introduce way to retrieve proxy object of a Seam JavaBean Component

by Wolfgang Schwendt (JIRA)

Introduce way to retrieve proxy object of a Seam JavaBean Component ------------------------------------------------------------------- Key: JBSEAM-2221 URL: http://jira.jboss.com/jira/browse/JBSEAM-2221 Project: JBoss Seam Issue Type: Feature Request Reporter: Wolfgang Schwendt The EJB programming model requires that a Session Bean never passes a "this"-pointer to other client objects. Instead, javax.ejb.SessionContext provides a method getBusinessObject(). If a SessionBean wants to pass a reference pointing to itself to other clients, it first has to retrieve its own EJB object reference by calling SessionContext.getBusinessObject() which it then can pass to other beans. This reference returned by javax.ejb.SessionContext.getBusinessObject() is the equivalent to Java's this pointer. With respect to Seam's interceptor framework, such a feature is missing as far as normal JavaBean components are concerned. It leads to subtle programming errors: Consider the implementation of org.jboss.seam.framework.Query. getDataModel(): /** * Wrap the result set in a JSF {@link DataModel} * * Delegates to {@link DataModels#getDataModel(Query)} * */ @Transactional public DataModel getDataModel() { if (dataModel==null) { dataModel = DataModels.instance().getDataModel(this); } return dataModel; } This method method passes a "this"-reference to the org.jboss.seam.faces.dataModels Seam-component. But this can lead to a behavior not expected by the programmer. If the (Entity)Query-component gets instantiated as a conversation-scoped component, Seam wraps the ManagedEntityIdentityInterceptor around this Query component. After each method invocation intercepted by the ManagedEntityIdentityInterceptor, the ManagedEntityIdentityInterceptor saves wrappers for all contained Entity references in the conversation context and sets the corresponding reference fields in the Query component to null. Now, consider again above implementation of Query.getDataModel(). Because a "this" pointer is passed to the dataModels-component, any calls conducted by the datamodel-component via this reference won't (!) be routed through the ManagedEntityIdentity interceptor. Hence, when the datamodel-component calls the Query-component via the Java-this pointer it received previously, the ManagedEntityIdentity won't be invoked and in turn the Entity reference fields in the Query-component won't be restored. This leads to a bug as described in JBSEAM-1814. In order to fix that bug, we would have to change the implementation of Query. getDataModel(). Rather than passing the Java-this pointer to the dataModels component, the correct implementation would be as follows. The Query component would first have to retrieve a reference to its own proxy object, which it then could pass to the dataModels component. Summary: For JavaBean Seam components we need a feature similar to SessionContext.getBusinessObject(), to enable a JavaBean Seam component to pass a proxy reference to itself to other Seam components instead of passing directly the Java-this pointer. -- 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

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2261) Default s:link propagation attribute value.

by Richard Teviotdale (JIRA)

Default s:link propagation attribute value. ------------------------------------------- Key: JBSEAM-2261 URL: http://jira.jboss.com/jira/browse/JBSEAM-2261 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.GA Reporter: Richard Teviotdale The propagation attribute of s:link has possible values of begin, join, nest, none or end. When the attribute is not specified the tag propagates the active conversations by default. Please add a value that specifies the default behavior - perhaps propagation="propagate". Please see forum posting for more information. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007