I have tried to follow this whole thread (but probably I have missed
some aspects, so sorry if I re-sayin something already said or
bringing an arguement already demolished).

My understand was the same as Ian's (after a long thread I had with Pattrick).

1. The idea would that WebWork/SAF2 core should provide the means to
build almost all we can think of AJAX based on DWR integration.

2. The current Dojo based widgets are simple enough to be used in some
sample/tutorial like pages but for real life apps they don't work (or
put it in another more realistic way: I haven't been able to have them
working within a normal timeframe).
I have to mention, that  I haven't used the Dojo-based tree, but I
tried all the others.

3. These widgets can live in a separate project. The lifecycle and
stability of SAF2, DWR and Dojo are completely different and by moving
them to a separate project we can ensure a more uptodate integration.

./alex
--
.w( the_mindstorm )p.
---
(http://themindstorms.blogspot.com)


On 6/19/06, Joe Germuska <[EMAIL PROTECTED]> wrote:
At 10:34 AM -0700 6/19/06, Don Brown wrote:
>This is exactly how Struts Action 2 works today - we package Dojo into our
>jar, then let SAF2 serve up its static content through a known prefix,
>"struts/" I believe.  We also provide hooks to let you serve up other
>static content from jars.

yep. I'm sure that's part of where I started to get the idea (along
with the way DWR provides JS from behind a servlet) -- but what
Martin is suggesting is presumably more specific to Dojo and not just
a way of plugging it into Struts?

Joe

--
Joe Germuska
[EMAIL PROTECTED] * http://blog.germuska.com

"You really can't burn anything out by trying something new, and
even if you can burn it out, it can be fixed.  Try something new."
        -- Robert Moog

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to