On Jan 21, 2008 1:54 AM, Joshua Jackson <[EMAIL PROTECTED]> wrote:
> SEAM is not that bad actually. Though it still has some quirks.
Though most people will use it together with JSF, SEAM does have a
different scope. You can use it by itself as a business component
framework. There are two (kind o
SEAM is not that bad actually. Though it still has some quirks.
On 1/21/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I fully agree. I used JSF/SEAM before switching to Wicket.
> My experience is that Wicket is "JSF-Done-Right"
--
It's not going to be like this forever
Blog: http://joshuaj
I fully agree. I used JSF/SEAM before switching to Wicket.
My experience is that Wicket is "JSF-Done-Right"
>
>As I've stated before in a previous post, I work a for a company that
>develops software for the health care industry. It was a battle between
>JSF/Seam and Wicket as the framework of c
igor.vaynberg wrote:
>
> it would be great if we could see the whitepaper :)
>
> -igor
>
I'll see what I can do.
- rm3
--
View this message in context:
http://www.nabble.com/We-are-adopting-Wicket-in-our-Organization-tp14988751p14989916.html
Sent from the Wicket - User mailing list archive
it would be great if we could see the whitepaper :)
-igor
On Jan 20, 2008 3:58 PM, robert.mcguinness
<[EMAIL PROTECTED]> wrote:
>
> As I've stated before in a previous post, I work a for a company that
> develops software for the health care industry. It was a battle between
> JSF/Seam and Wick
> I'd like to thank the authors of the framework for building such a fine
> tool. After years of struts development, developing web applications with
> Wicket is a breath of fresh air. Keep up the fine work.
Good to hear it works well for you Robert.
> I'll update this forum with our experience
