May 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMFACES-166) UIValidateForm doesn't set the rendererType property correctly

by Christian Kaltepoth (JIRA)

UIValidateForm doesn't set the rendererType property correctly -------------------------------------------------------------- Key: SEAMFACES-166 URL: https://issues.jboss.org/browse/SEAMFACES-166 Project: Seam Faces Issue Type: Bug Components: Validation & Conversion Affects Versions: 3.0.1 Environment: Tomcat 7.0.5, MyFaces 2.0.5, Weld 1.1.0 Reporter: Christian Kaltepoth Priority: Minor MyFaces emits some warning when <s:validateForm> is used on a page: {code} 30.05.2011 17:30:03 org.apache.myfaces.renderkit.html.HtmlRenderKitImpl getRenderer WARNUNG: Unsupported component-family/renderer-type: org.jboss.seam.faces.ValidateForm/javax.faces.Text 30.05.2011 17:30:03 org.apache.catalina.core.ApplicationContext log INFO: No Renderer found for component {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /validation.xhtml][Class: javax.faces.component.html.HtmlForm,Id: j_id98696035_5e1fb46][Class: org.jboss.seam.faces.component.UIValidateForm,Id: j_id98696035_5e1fb24]} (component-family=org.jboss.seam.faces.ValidateForm, renderer-type=javax.faces.Text) 30.05.2011 17:30:03 javax.faces.component.UIComponentBase getRenderer WARNUNG: No Renderer found for component {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /validation.xhtml][Class: javax.faces.component.html.HtmlForm,Id: j_id98696035_5e1fb46][Class: org.jboss.seam.faces.component.UIValidateForm,Id: j_id98696035_5e1fb24]} (component-family=org.jboss.seam.faces.ValidateForm, renderer-type=javax.faces.Text) {code} {{UIValidateForm}} doesn't render any output and therefore implements the {{encode*()}} methods with empty method bodies. The {{rendererType}} property has to be {{null}} for this methods to be used (direct implementation model for rendering components). The problem with {{UIValidateForm}} is that it is a subclass of {{UIInput}}. According to 4.1.6.2 the default value of the {{rendererType}} property for {{UIInput}} is {{javax.faces.Text}}. As {{UIValidateForm}} doesn't overwrite {{getRendererType()}} MyFaces uses the default value and therefore searches for a renderer for the component. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMREPORTS-13) Create a seam forge plugin for Seam Reports

by George Gastaldi (JIRA)

Create a seam forge plugin for Seam Reports -------------------------------------------- Key: SEAMREPORTS-13 URL: https://issues.jboss.org/browse/SEAMREPORTS-13 Project: Seam Reports Issue Type: Feature Request Reporter: George Gastaldi It would be nice to have a Seam Forge plugin. Forge developers could type then: "reports setup --provider PENTAHO" for example, to use the Seam Reports Pentaho module impl, for example. Info on how to create a plugin: http://docs.jboss.org/forge/1.0.0.Alpha3/reference/en-US/html_single/#for... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (SEAMFACES-135) The #{cc.attrs.id} of nested composite component of UIInputContainer does not include the id of the container component

by Alt Avatar (JIRA)

The #{cc.attrs.id} of nested composite component of UIInputContainer does not include the id of the container component ----------------------------------------------------------------------------------------------------------------------- Key: SEAMFACES-135 URL: https://issues.jboss.org/browse/SEAMFACES-135 Project: Seam Faces Issue Type: Bug Components: UI Components Affects Versions: 3.0.0.Final Environment: Ubuntu 10.10 64bit, JBoss AS 6 Reporter: Alt Avatar Nested #{cc.attrs.id} of composite components nested inside a UIInputContainer are incorrect. <x:inputcontainer id="foo"> <x:customInput/ id="bar"> // #{cc.attrs.id} of customInput will be "bar" instead of "foo:bar" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (SEAMFACES-133) UIInputContainer should accept ValueExpression for the label attribute.

by Alt Avatar (JIRA)

UIInputContainer should accept ValueExpression for the label attribute. ----------------------------------------------------------------------- Key: SEAMFACES-133 URL: https://issues.jboss.org/browse/SEAMFACES-133 Project: Seam Faces Issue Type: Bug Components: UI Components Affects Versions: 3.0.0.Final Environment: Ubuntu 10.10 64bit, JBoss 6 Reporter: Alt Avatar UIInputContainer should evaluate ValueExpressions for the "label" attribute. This is especially useful for internationalization, where the component could be included as: <x:inputcontainer label="#{msg.foo}/><h:inputText... Currently, ValueExpressions are ignored and only String literals work. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBSEAM-4809) seam-resteasy integration conflicts with resteasy deployer on JBoss AS 6

by Jozef Hartinger (JIRA)

seam-resteasy integration conflicts with resteasy deployer on JBoss AS 6 ------------------------------------------------------------------------ Key: JBSEAM-4809 URL: https://issues.jboss.org/browse/JBSEAM-4809 Project: Seam 2 Issue Type: Bug Components: WS Affects Versions: 2.2.2.Final Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: The future As a result of auto-scanning performed by the resteasy-deployer, resources not intended to be registered are registered within RESTEasy which causes redirect loops breaking the entire application. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMCRON-22) NPE stopping scheduler under Weld

by Peter Royle (JIRA)

NPE stopping scheduler under Weld --------------------------------- Key: SEAMCRON-22 URL: https://issues.jboss.org/browse/SEAMCRON-22 Project: Seam Cron Issue Type: Bug Reporter: Peter Royle Assignee: Peter Royle Notice in the tests since switching to Weld Arquillian and when redeploying on JBoss AS there is a NPE during undeployment. I have been incorrectly relying on providers being @ApplicationScoped which seems to work in OWB but not in Weld. I'm not sure what position the spec takes on that. Will simply remote the scoping and rework so dependencies are injected into each observer of the Extension. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (SEAMCRON-23) Extension does not follow spec

by Peter Royle (JIRA)

Extension does not follow spec ------------------------------ Key: SEAMCRON-23 URL: https://issues.jboss.org/browse/SEAMCRON-23 Project: Seam Cron Issue Type: Bug Reporter: Peter Royle Assignee: Peter Royle Fix For: 3.0.0.Alpha1 I was using @ApplicationScoped provider implementations, expecting the same instance of the bean to be available for injection during AfterBeanValidation and BeforeShutdown. I found that the injected instances were different, and therefore any initialisation I performaed at startup could not properly be unding on shutdown. This was the main cause of SEAMCRON-15. After further investigation and reading this thread (http://weld-development-discussions.46994.n3.nabble.com/clarification-of-...) I realise that I cannot depend on any scopes being active during AfterBeanValidation (this seemed to work in OWB though). Not yet sure what the appropriate way is to do this. I'm getting the feeling that if I'm going to be grabbing providers from the manager, they'll need to be no/default-scoped and cached by the extension. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAM-90) Newest snapshot seam-bom versions seam faces as 3.0.0 not 3.0.1

by Patrick McFarland (JIRA)

Newest snapshot seam-bom versions seam faces as 3.0.0 not 3.0.1 --------------------------------------------------------------- Key: SEAM-90 URL: https://issues.jboss.org/browse/SEAM-90 Project: Seam 3 Distribution Issue Type: Bug Reporter: Patrick McFarland See summary -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMWICKET-38) CDIPropertyModel

by Ondrej Zizka (JIRA)

CDIPropertyModel ---------------- Key: SEAMWICKET-38 URL: https://issues.jboss.org/browse/SEAMWICKET-38 Project: Seam for Apache Wicket Issue Type: Feature Request Reporter: Ondrej Zizka An idea for possible addition: CDIPropertyModel, which would get a value from @Named CDI bean. new CDIPropertyModel("myManagedBean.someValue") -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMVALIDATE-17) ValidationInterceptor needs to be Serializable

by Jan Groth (JIRA)

ValidationInterceptor needs to be Serializable ---------------------------------------------- Key: SEAMVALIDATE-17 URL: https://issues.jboss.org/browse/SEAMVALIDATE-17 Project: Seam Validation Issue Type: Bug Reporter: Jan Groth Assignee: Gunnar Morling ... otherwise it cannot be used in Beans which are passivation-enabled Didn't submit a patch because too trivial ;-) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
4
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 May 2011