On 12/18/05, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
This is bad, for a lot of reasons, the largest of which is that this breaks having components within components, which specifically breaks my use of tacos ;) This is an exposure of what I believe is a much larger flaw in tapestry in general, but not one easily solved.
I'm going to probably want this call to use the page if at all possible.On 12/17/05, Leonardo Quijano Vincenzi < [EMAIL PROTECTED]> wrote:I'm worried people are assuming that a component container is the page.
This is not always the case.
So, in StringUtils:
//Resolve observer
IComponent container = comp.getContainer();
if (container == null) {
container = comp.getPage();
}
observer = (AjaxEventSubmit) eval.read(container, value);
And not:
//Resolve observer
IComponent container = comp.getPage();
observer = (AjaxEventSubmit) eval.read(container, value);
Just in case ;).
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel
