umesh awasthi wrote:
Thanks Jeromy for the rply
we will try to impliment DOJO 1.x along with struts2

some point i want to confirm if u have any exp using dojo with struts2

I don't use Dojo in any production applications any more. After getting advice from others I have moved entirely to YUI. I prefer YUI's approach overall, but still appreciate Dojo's design.

1) IF we will replace the Struts2 ajax tag with dojo will there be any
functional changes to struts2
lilke action automatically populate form beans in the action.


Struts2 will be the same functionally in that it will accept request, set properties of your actions and setup the ValueStack and forward to/render your view. What you lose is the functionality that is contained within the ajax tags. The tags get values from the attributes and ValueStack and insert them into a template. Instead you'll need to get values from the ValueStack and insert them into your page (or own template). eg. you'll use s:property a lot more to populate attributes required by the dojo markup Have a look at the existing templates to get an appreciation of what they do. Also have a look at the thread "Dojo plugin update using 1.1.0 framework" in struts-dev.

You do need to think about the separation between the client-side and server-side a little more. It is definitely more effort than having the tags to work with, but easier to extend, customise, debug and most importantly you'll be able to use Dojo's tutorials and usergroups directly.

if we will use dojo tags will it again populate the beans like struts2 do on
each request??

Yes, definitely.  Struts doesn't know or care where the request comes from.

or any other specific configuration which we have to take in to account??


I don't think so. I suggest you create a test application with one widget populated from a struts action before committing to this path though.

Hope that helps,
Jeromy Evans


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

Reply via email to