[jira] Created: (SHALE-409) Shale 1.0.4+ breaks AJAX4JSF

[Todd Bush (JIRA)]

Shale 1.0.4+ breaks AJAX4JSF


 Key: SHALE-409
 URL: https://issues.apache.org/struts/browse/SHALE-409
 Project: Shale
  Issue Type: Bug
  Components: View
Affects Versions: 1.0.4, 1.0.5-SNAPSHOT
 Environment: WinXP, AJAX4JSF-1.0.6, Shale-1.0.4 (Application, Core, 
Dialog, Spring, Tiger, View)
Reporter: Todd Bush


I've successfully implemented AJAX4JSF-1.0.6 with Shale-1.0.3, but when I 
attempt to upgrade Shale to 1.0.4 (also 1.0.5-SNAPSHOT) the a4j functionality 
stops working.  I receive no stack trace or other server side error.  I do 
receive a javascript error A4J is undefined.  

Viewing the output when running Shale-1.0.3, this javascript URL reference 
exists or A4J ...

!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN 
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; 
html xmlns=http://www.w3.org/1999/xhtml; 
xmlns:acegijsf=http://sourceforge.net/projects/jsf-comp/acegijsf;headtitle/title!--
 HTTP 1.1 --
script type=text/javascript 
src=/crown/a4j.res/org.ajax4jsf.framework.ajax.AjaxScript.xhtml
/scriptmeta http-equiv=Cache-Control content=no-store /!-- HTTP 1.0 --

With Shale-1.0.4, the same page is missing the javascript URL reference for A4J 
...

!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN 
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; 
html xmlns=http://www.w3.org/1999/xhtml; 
xmlns:acegijsf=http://sourceforge.net/projects/jsf-comp/acegijsf;headtitle/title!--
 HTTP 1.1 --
meta http-equiv=Cache-Control content=no-store /!-- HTTP 1.0 --

Also, a Nabble references detailing the same problem

http://www.nabble.com/Solved!-A4J-is-Undefined-t3152071.html
http://www.nabble.com/AJAX4JSF---Shale-1.0.4-t3148641.html

Thanks.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SHALE-410) Add warning when duplicate renderids are found in a component definition

[Hermod Opstvedt (JIRA)]

Add warning when duplicate renderids are found in a component definition


 Key: SHALE-410
 URL: https://issues.apache.org/struts/browse/SHALE-410
 Project: Shale
  Issue Type: Improvement
  Components: Clay
Affects Versions: 1.0.4
Reporter: Hermod Opstvedt
Priority: Minor


When defining a new Clay component I did the error of duplicating the 
renderId's for two sibling elements within the component defintion. There was 
no error/warning issued.. The effect was that the last defined element was 
simply not rendered. I think it would be nice if a warning was issued (logged) 
when Clay encounters this situation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.