Hi Dan, thanks for helping out. I've attached a tarball containing
HTML pages for both the Woodstock 4.1 (which renders OK) and Woodstock
4.1.1 (which does not). I will send you a pointer to the live app shortly.
-Kenneth
Dan Labrecque wrote:
> Kenneth Suter wrote:
>> I added debug='true' to the head tag. No errors in Firefox's Error
>> Console.
>>
>> In Firebug, the Console and Net tabs shows 2 requests
>> (/theme/com/sun/webui/jsf/suntheme/javascript_uncompressed/theme/nls/en/suntheme.jsnls/en/suntheme.js,
>> and
>> /theme/com/sun/webui/jsf/suntheme/javascript_uncompressed/theme/nls/en-us/suntheme.js)
>> that return 404 errors. Additionally Firebug's Net tab shows an
>> additional request to /theme/META-INF/com_sun_faces_ajax-max.js that
>> also returns a 404 error. However all 3 of these errors show up on
>> both the working (4.1) and non-working (4.1.1) implementations so I'm
>> not sure if they would be relevant to this problem in particular.
>
> You can ignore the 404 warnings. The requests are an attempt to obtain
> locale variants and warnings are expected. This is Dojo's convention
> for loading i18n resources.
>
>>
>> The HTML tab for the working (4.1) version shows that the span tags
>> were correctly added for label components whereas they do not exist
>> in the non-working (4.1.1) version.
>>
>> I noticed that the inline Javascript is different for the working and
>> non-working versions although I suppose this is a result of the dojo
>> library change. At any rate the DOM is never updated with the UI
>> components.
>
> Right. The underlying JavaScript changed due to Dojo 1.0. Although, I
> don't have enough information to tell you what is wrong. Is it
> possible to forward a pointer to your app? If not, can you send me the
> rendered HTML page?
>
> Dan
>
>>
>> -Kenneth
>>
>> Dan Labrecque wrote:
>>> Do you see any JavaScript errors in the page? If you set the debug
>>> attribute of the head tag to true, that may show messages in the
>>> Firebug console. You can also add "?debug" to the end of your URL.
>>>
>>> Dan
>>>
>>> Kenneth Suter wrote:
>>>> Hello,
>>>>
>>>> I have a very simple application running with Woodstock 4.1, Tomcat
>>>> 6.0.14, and Facelets 1.1.13. However when I upgrade the app to
>>>> Woodstock 4.1.1 (replacing the 18 jars in the WEB-INF/lib
>>>> directory) some of the components stop rendering. The masthead and
>>>> common task components seem to work OK but simple elements like
>>>> buttons and textfields do not appear in the browser (Firefox and
>>>> Safari). If I revert the jars back to 4.1 the components work as
>>>> expected.
>>>>
>>>> It looks all the client in-line Javascript for generating the
>>>> components is present and I used Firebug to make sure that the
>>>> createWidgetOnLoad is being called correctly but I'm not sure where
>>>> to go from there.
>>>>
>>>> Any ideas?
>>>>
>>>> Thanks,
>>>>
>>>> -Kenneth
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>>>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
>> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>