is cocoon the right solution for my need (suggested answer: "YES", but why)

[Wojciech Biela <il...@gmail.com>]

Hi!

if this text is too long tell me, I'll try to repost it in a shorter
version. didn't want to be misunderstood so I elaborated a bit.

I've seen something that touches the subject but here
http://www.planetcocoon.com/node/1710, but I believe my question is a
bit different. Nevertheless that post was unanswered to. I haven't
found any other posts that would help me.

1. the background: 
I personally like the Cocoon way :), but I don't like treating
technology like religion, so I have to honestly evaluate every
possibility. I'm not the only decisionmaker my boss will have to hear
me out and will approve or not. He knows Cocoon and favoures it a bit
but as a manager at his position he is very careful. So my job is to
find the right answer and convince him.

2. the problem: 
One of your customers needs an e-shop. We would like to provide him
with one. We don't want to do it all over again if another of our
customers decides he want's one too. So we need to have something
that's customizable and changable in a reasonal amount of time.

3. the possible solutions I think of: 
We just did a refactory project, rewriting a part of our old Struts
application to a proper MVC design using Struts+Spring. So the Spring
approach proved very nice.

(a) so this is one option do it using the Spring MVC (together with
the Spring Web Flow continuations).

(b) another tempting, suggested by my boss, alternative would be
Tapestry (or maybe just use Tapestry as the view layer and wire
everything with Spring) - the ease of modifications of tapestry
HTML-only templates is very attractive (and may be useful ) but I have
no experiences with Tapestry, so if anyone has some downsides please
provide (cause I found words of adoration on numerous sites (TSS
discussions, etc)).

(c) and finally Cocoon. I know, as cocooners point out everywhere,
Cocoon is something bigger than just a webapp framework like those two
above, but it has such a framwork inside and one has to choose one
technology over the other. If so then why. Something tells me it could
be my best bet if I was supposed to deliver it to many customers, but
for now it's just a gut feeling I can't communicate to my boss.

------------------------------------------------
So finally the questions: 
1. What do you think would be the best bet here? 
2. Why, how should one convince sbd to use this and not one of the other two?
------------------------------------------------

Please give me any hints, because I found myself in a corner and don't
quite know what direction to move right now.

Thanks in advance, best regards,
Wojtek Biela

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org