Jesse Kuhnert wrote:
You are mostly understanding correctly, besides the listener reloading
the entire page in the response, sort of... :)
Yes but no... The listener isn't reloading the entire page, but it is
indeed *rendering* the whole page. Am I right?
Two points:
1) Direct component refresh is not reliable. That's until the "use with
care" warning is removed, hehe... Now if we have a Direct refresh that
'just works' (I can put it in a @For or anywhere and it would work)
that'd be great. But the "component service" solution is also useful.
2) I'm thinking of in-container component testing. I'd call the
"component direct" service, or whatever is called, and use some HTML
testing tool to check my components. Now, components really *shouldn't*
have any external dependencies besides the ones define in its interface
(the JWC file, annotations, etc), right? Or I could try to manually test
a component by calling it directly and setting the parameters on some
kind of component-test web interface.
If the component update is rendering the whole page, isn't this process
expensive? Even if it's cached...
(and if it's not cached, the devoleper time is also valuable.. you know)
--
Ing. Leonardo Quijano Vincenzi
Director Técnico
DTQ Software
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
