You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Ryan Wynn <bi...@gmail.com> on 2005/11/09 23:11:39 UTC
Possible bug in extended HtmlDataTable
I am using shale clay with myfaces. So like facelets, I am not using jsp but
rather html/xml templates.
I noticed that the myfaces extended HtmlDataTable component was defaulting
to the renderer type javax.faces.Table (inherited) instead of the correct
type org.apache.myfaces.Table.
I looked at the jsp tag and found out that org.apache.myfaces.Table is
being set on the component there. So to patch it I just set the rendererType
explicitly in the clay config. But it seems to me that the component should
default to an appropriate renderer, instead of relying on the tag to do it.
Any thoughts? I will submit a bug to JIRA if the group agrees. From what I
have seen most components declare a constant String DEFAULT_RENDERER_TYPE.
Re: Possible bug in extended HtmlDataTable
Posted by Ryan Wynn <bi...@gmail.com>.
Thomas,
I think my problem is that I am still using 1.1.1 RC3. In this version the
constructor is empty. Thanks for your help.
Ryan
On 11/9/05, Thomas Spiegl <th...@gmail.com> wrote:
>
> This does not seem to be the problem. The renderer type for
> org.apache.myfaces.component.html.ext.HtmlDataTable
> is set to "org.apache.myfaces.Table" in HtmlDataTable's constructor
> (DEFAULT_RENDERER_TYPE = "org.apache.myfaces.Table").
>
> Can you explore the problem again?
>
> .
>
> On 11/9/05, Ryan Wynn <bi...@gmail.com> wrote:
> > I am using shale clay with myfaces. So like facelets, I am not using jsp
> > but rather html/xml templates.
> >
> > I noticed that the myfaces extended HtmlDataTable component was
> defaulting
> > to the renderer type javax.faces.Table (inherited) instead of the
> correct
> > type org.apache.myfaces.Table.
> >
> > I looked at the jsp tag and found out that org.apache.myfaces.Table is
> being
> > set on the component there. So to patch it I just set the rendererType
> > explicitly in the clay config. But it seems to me that the component
> should
> > default to an appropriate renderer, instead of relying on the tag to do
> it.
> >
> > Any thoughts? I will submit a bug to JIRA if the group agrees. From what
> I
> > have seen most components declare a constant String
> DEFAULT_RENDERER_TYPE.
> >
> >
> >
> >
>
>
> --
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
Re: Possible bug in extended HtmlDataTable
Posted by Thomas Spiegl <th...@gmail.com>.
This does not seem to be the problem. The renderer type for
org.apache.myfaces.component.html.ext.HtmlDataTable
is set to "org.apache.myfaces.Table" in HtmlDataTable's constructor
(DEFAULT_RENDERER_TYPE = "org.apache.myfaces.Table").
Can you explore the problem again?
.
On 11/9/05, Ryan Wynn <bi...@gmail.com> wrote:
> I am using shale clay with myfaces. So like facelets, I am not using jsp
> but rather html/xml templates.
>
> I noticed that the myfaces extended HtmlDataTable component was defaulting
> to the renderer type javax.faces.Table (inherited) instead of the correct
> type org.apache.myfaces.Table.
>
> I looked at the jsp tag and found out that org.apache.myfaces.Table is being
> set on the component there. So to patch it I just set the rendererType
> explicitly in the clay config. But it seems to me that the component should
> default to an appropriate renderer, instead of relying on the tag to do it.
>
> Any thoughts? I will submit a bug to JIRA if the group agrees. From what I
> have seen most components declare a constant String DEFAULT_RENDERER_TYPE.
>
>
>
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces