You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by William Hoover <wh...@nemours.org> on 2007/06/15 14:37:45 UTC
[Trinidad] Custom Component UINodePropertyKey Missing
I recently created a custom component that uses extended PropertyKey using the new FacesBean.Type(SOME_EXT_COMPONENT.TYPE) and TYPE.registerKey(...) registering the all the needed type keys. All the properties have accociated getters/setters. Also, all of the extended properties are defined in faces-config.xml, but none of the extended type keys (UINodePropertyKey) are showing up in the FacesBean > Type when state is being restored. Does anyone know what may be causing this?
RE: [Trinidad] Custom Component UINodePropertyKey Missing
Posted by William Hoover <wh...@nemours.org>.
I can't believe that I overlooked that! That was exactly what it was! Thanks Adam (Your the MAN!)
-----Original Message-----
From: Adam Winer [mailto:awiner@gmail.com]
Sent: Friday, June 15, 2007 12:12 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Custom Component UINodePropertyKey Missing
Have you overridden:
protected FacesBean.Type getBeanType()
to return your type?
-- Adam
On 6/15/07, William Hoover <wh...@nemours.org> wrote:
> Using Trinidad 1.0.0
>
> The non-customized component contains the UINodePropertyKey. When stepping through StateUtils > restoreKey(FacesBean.Type type, Object value) the _KeyList contains a list of UINodePropertyKey. It's using type.findKey(((Number) value).intValue()) to find the key from the _KeyList in FacesBean > Type. All of the property keys are within this list except for the PropertyKeys that are registered in the custom component extension.
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com]On Behalf Of
> Matthias Wessendorf
> Sent: Friday, June 15, 2007 8:55 AM
> To: MyFaces Discussion
> Subject: Re: [Trinidad] Custom Component UINodePropertyKey Missing
>
>
> are you creating the custom component w/ the maven-faces-plugin, like
> Trinidad does itself ?
>
> I think the UINodePropertyKey is deprecated, since it is from pre-jsf-days.
>
> -M
>
> On 6/15/07, William Hoover <wh...@nemours.org> wrote:
> > I recently created a custom component that uses extended PropertyKey using the new FacesBean.Type(SOME_EXT_COMPONENT.TYPE) and TYPE.registerKey(...) registering the all the needed type keys. All the properties have accociated getters/setters. Also, all of the extended properties are defined in faces-config.xml, but none of the extended type keys (UINodePropertyKey) are showing up in the FacesBean > Type when state is being restored. Does anyone know what may be causing this?
> >
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>
>
Re: [Trinidad] Custom Component UINodePropertyKey Missing
Posted by Adam Winer <aw...@gmail.com>.
Have you overridden:
protected FacesBean.Type getBeanType()
to return your type?
-- Adam
On 6/15/07, William Hoover <wh...@nemours.org> wrote:
> Using Trinidad 1.0.0
>
> The non-customized component contains the UINodePropertyKey. When stepping through StateUtils > restoreKey(FacesBean.Type type, Object value) the _KeyList contains a list of UINodePropertyKey. It's using type.findKey(((Number) value).intValue()) to find the key from the _KeyList in FacesBean > Type. All of the property keys are within this list except for the PropertyKeys that are registered in the custom component extension.
>
> -----Original Message-----
> From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com]On Behalf Of
> Matthias Wessendorf
> Sent: Friday, June 15, 2007 8:55 AM
> To: MyFaces Discussion
> Subject: Re: [Trinidad] Custom Component UINodePropertyKey Missing
>
>
> are you creating the custom component w/ the maven-faces-plugin, like
> Trinidad does itself ?
>
> I think the UINodePropertyKey is deprecated, since it is from pre-jsf-days.
>
> -M
>
> On 6/15/07, William Hoover <wh...@nemours.org> wrote:
> > I recently created a custom component that uses extended PropertyKey using the new FacesBean.Type(SOME_EXT_COMPONENT.TYPE) and TYPE.registerKey(...) registering the all the needed type keys. All the properties have accociated getters/setters. Also, all of the extended properties are defined in faces-config.xml, but none of the extended type keys (UINodePropertyKey) are showing up in the FacesBean > Type when state is being restored. Does anyone know what may be causing this?
> >
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>
>
RE: [Trinidad] Custom Component UINodePropertyKey Missing
Posted by William Hoover <wh...@nemours.org>.
Using Trinidad 1.0.0
The non-customized component contains the UINodePropertyKey. When stepping through StateUtils > restoreKey(FacesBean.Type type, Object value) the _KeyList contains a list of UINodePropertyKey. It's using type.findKey(((Number) value).intValue()) to find the key from the _KeyList in FacesBean > Type. All of the property keys are within this list except for the PropertyKeys that are registered in the custom component extension.
-----Original Message-----
From: mwessendorf@gmail.com [mailto:mwessendorf@gmail.com]On Behalf Of
Matthias Wessendorf
Sent: Friday, June 15, 2007 8:55 AM
To: MyFaces Discussion
Subject: Re: [Trinidad] Custom Component UINodePropertyKey Missing
are you creating the custom component w/ the maven-faces-plugin, like
Trinidad does itself ?
I think the UINodePropertyKey is deprecated, since it is from pre-jsf-days.
-M
On 6/15/07, William Hoover <wh...@nemours.org> wrote:
> I recently created a custom component that uses extended PropertyKey using the new FacesBean.Type(SOME_EXT_COMPONENT.TYPE) and TYPE.registerKey(...) registering the all the needed type keys. All the properties have accociated getters/setters. Also, all of the extended properties are defined in faces-config.xml, but none of the extended type keys (UINodePropertyKey) are showing up in the FacesBean > Type when state is being restored. Does anyone know what may be causing this?
>
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Re: [Trinidad] Custom Component UINodePropertyKey Missing
Posted by Matthias Wessendorf <ma...@apache.org>.
are you creating the custom component w/ the maven-faces-plugin, like
Trinidad does itself ?
I think the UINodePropertyKey is deprecated, since it is from pre-jsf-days.
-M
On 6/15/07, William Hoover <wh...@nemours.org> wrote:
> I recently created a custom component that uses extended PropertyKey using the new FacesBean.Type(SOME_EXT_COMPONENT.TYPE) and TYPE.registerKey(...) registering the all the needed type keys. All the properties have accociated getters/setters. Also, all of the extended properties are defined in faces-config.xml, but none of the extended type keys (UINodePropertyKey) are showing up in the FacesBean > Type when state is being restored. Does anyone know what may be causing this?
>
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org