Hi Ted,
While ideally an announcement like this should bring across "joy",
ironically enough it brings some "concerns" to developers like me!

I am uninitiated in WebWork yet. I have just learnt a bit of struts
some 4 months ago. Just when I thought I learnt a little the "floor
(read framework)" moves!

I can start off yet another holy war on merits of "special frameworks"
for special purposes vs. a utopian one framework for all purposes! But
instead let me just ask a few simple question:
What does this integration mean to a developer like me?

I am using struts 1.2.8 and use the struts-layout tags for my UI
components. I have done some 50% of my project work using this
combination. And I must say I am quite happy with what these
layout-tags offer so far.

Now, how do I get webwork into my ecosystem?
Is it correct that webwork's main strength is its rich UI components?
Can I make struts-layout (or for that matter any other struts based
taglibs) to co-exist with webwork ? Will integrating with webwork mean
that if I replace my current struts version with the integrated new
version, my earlier taglibs will stop working?

Best Regards,
Raghu

ps: While its good to encourage mutations and variants to get the
"fittest" one as victorious.. it has its own demerits. In the
Microsoft world, good(?),bad,ugly - there is just one choice. On day
1, you know "this" is what I need to use in the MS world! But here ..
you decide only on day 10 of the combination of frameworks you want to
use. And on day 12, you realize there is an option you havent
considered!  Just a thought ... observing the direction struts has
been taking over the last 4 months.. :-)



On 2/7/06, Ted Husted <[EMAIL PROTECTED]> wrote:
> See
> * http://blogs.opensymphony.com/webwork/2006/02/webwork_221_released.html
>
> A companion release of XWork 1.1 is also available
> * http://forums.opensymphony.com/thread.jspa?threadID=16919&tstart=0
>
> -Ted.
>
> ---------------------------------------------------------------------
> 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