seam-issues May 2012

seam-issues@lists.jboss.org

1 participants
175 discussions

[JBoss JIRA] (SOLDER-327) BeanBuilder readFromType method should use annotatedType.getTypeClosure() instead of building set of types

by Marek Smigielski (JIRA)

Marek Smigielski created SOLDER-327: --------------------------------------- Summary: BeanBuilder readFromType method should use annotatedType.getTypeClosure() instead of building set of types Key: SOLDER-327 URL: https://issues.jboss.org/browse/SOLDER-327 Project: Solder Issue Type: Feature Request Reporter: Marek Smigielski When you create class which is supertype of another one: ElementDao extends AbstractDao<Element> and use ServiceHandlerExtension to convert this class to bean, than you can't inject bean based on its typed superclass: @Inject AbstractDao<Element> dao; only direct injection works: @Inject ElementDao dao; It would be better to read types from annotatedType.getTypeClosure() instead of building set of types in beanBuilder.readFromType method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SEAMSOCIAL-33) Upgrafe facebook button name in ftest

by Tomas Remes (JIRA)

Tomas Remes created SEAMSOCIAL-33: ------------------------------------- Summary: Upgrafe facebook button name in ftest Key: SEAMSOCIAL-33 URL: https://issues.jboss.org/browse/SEAMSOCIAL-33 Project: Seam Social Issue Type: Enhancement Components: Facebook Reporter: Tomas Remes Assignee: Tomas Remes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
2
0 / 0

[JBoss JIRA] (SEAMFACES-222) Support Portlet deployments

by Ken Finnigan (Created) (JIRA)

Support Portlet deployments --------------------------- Key: SEAMFACES-222 URL: https://issues.jboss.org/browse/SEAMFACES-222 Project: Seam Faces Issue Type: Feature Request Components: CDI Integration Affects Versions: 3.1.0.Beta4 Reporter: Ken Finnigan Assignee: Ken Finnigan Currently Faces assumes that a ServletContext will always be available to retrieve a BeanManager, amongst other things. Support needs to be added for retrieving the BeanManager from a PortalContext when running inside a Portal environment. https://github.com/seam/faces/blob/develop/impl/src/main/java/org/jboss/s... and https://github.com/seam/faces/blob/develop/impl/src/main/java/org/jboss/s... definitely need Portal equivalents, and additional code could require updates but need to search for ServletContext to confirm. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4428) <s:decorate> tag gives a "[renderkit] 'for' attribute cannot be null" message when no EditableValueHolder is found

by Julien Kronegg (JIRA)

<s:decorate> tag gives a "[renderkit] 'for' attribute cannot be null" message when no EditableValueHolder is found ------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-4428 URL: https://jira.jboss.org/jira/browse/JBSEAM-4428 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.GA Environment: Seam 2.1.2.GA, http://fisheye.jboss.org/browse/Seam/branches/community/Seam_2_1/ui/src/m..., http://fisheye.jboss.org/browse/Seam/branches/community/Seam_2_1/ui/src/m... Reporter: Julien Kronegg Priority: Minor When a field is decorated using <s:decorate> with the default Seam template "edit.xhtml" on content without EditableValueHolder (i.e. editable elements such as <h:inputText>), the following warning is issued: WARN [renderkit] 'for' attribute cannot be null This occurs for example on the following code snippet: <s:decorate id="char" template="edit.xhtml"> <ui:define name="label">Characters Left:</ui:define> <h:outputText id="charLeft" value="#{smsClass.charLeft}"/> </s:decorate> The Seam edit.xhtml template is the following: <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:s="http://jboss.com/products/seam/taglib"> <div class="prop"> <s:label styleClass="name #{invalid?'errors':''}"> <ui:insert name="label"/> <s:span styleClass="required" rendered="#{required}">*</s:span> </s:label> <span class="value #{invalid?'errors':''}"> <s:validateAll> <ui:insert/> </s:validateAll> </span> <span class="error"> <h:graphicImage value="/img/error.gif" rendered="#{invalid}" styleClass="errors"/> <s:message styleClass="errors"/> </span> </div> </ui:composition> This is caused by org.jboss.seam.ui.component.UIDecorate which gets the 'for' id by looking at the first available EditableValueHolder. When there is no such element, the 'for' id is null, hence the warning message (probably issued by the org.jboss.seam.ui.component.UIMessage parent class javax.faces.component.html.HtmlMessage). The warning message is very anonying and give no useful information on what is going wrong: this kind of messages takes a lot of time to track and makes a big impact on the developper productivity. The UIDecorate class should either: 1) display no error message (by either attaching the s:message tag to the s:decorate itself, or by avoid rendering the s:message) 2) display a more meaningfull message such as "No editable component found to attach the message in the decorate with id=xxx" (maybe to be combined with solution 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

12 years, 1 month

2
1
0 / 0

[JBoss JIRA] (SEAMSOCIAL-34) OAuthGenericManager

by Franck Garcia (JIRA)

Franck Garcia created SEAMSOCIAL-34: --------------------------------------- Summary: OAuthGenericManager Key: SEAMSOCIAL-34 URL: https://issues.jboss.org/browse/SEAMSOCIAL-34 Project: Seam Social Issue Type: Bug Reporter: Franck Garcia Assignee: Antoine Sabot-Durand -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
1
0 / 0

← Newer
1
...
15
16
17
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2012