Roger,
AFAIK, issue 130 is invalid. Facelets just uses the RenderKit-provided
ResponseWriter for its output. So if the RenderKit supports
XHTML, Facelets does as well. (This is true of 1.1; things
were different in 1.0).
-- Adam
Roger Kitain wrote:
> If you are going to do another facelets release, can you take a look at
> fixing:
>
> https://facelets.dev.java.net/issues/show_bug.cgi?id=130
>
> -roger
>
> Ed Burns wrote:
>
>> Hello Jacob,
>>
>> As mentioned previously, I'm fleshing out jsf-extensions avatar by
>> ensuring that the following use cases work
>>
>> 1. the jMaki and scroller use cases, as shown in the jsf-extensions
>> sample app.
>>
>> 2. all the use cases in your JavaOne sample app
>>
>> 3. The zone concept (or lack thereof) as shown in the cardemo app
>>
>> For 2, I have run into two problems regarding facelets. We've already
>> talked about one.
>>
>> a) incorrect DTD in Facelets 1.1.10. You said you were going to fix
>> this in Facelets 1.1.12, but that doesn't appear to be out yet.
>>
>> b) the absence of UIRepeat.invokeOnComponent(). This prevents the
>> contextual autosuggest from working.
>> Can you please release another version of Facelets that addresses these
>> issues? For b) I realize this will force you to confront the "does
>> facelets run in JSF 1.1 issue.
>>
>> Ed
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jsf-extensions.dev.java.net
> For additional commands, e-mail: dev-help_at_jsf-extensions.dev.java.net
>