where does you page markup come from? because if you also can generate
that then you can dynamically generate the page markup an component
structure. That is what we (servoy) do

On 6/12/07, Patrick Angeles <[EMAIL PROTECTED]> wrote:
>
> We're up to the prototyping phase of a new JEE application. We are looking
> at
> EJB3 + some UI framework. There's actually two types of UI: a complex admin
> UI with around 100 concurrent users, and several public-facing, CMS-driven,
> branded web-sites with 1000s of concurrent users. Obviously, we'd prefer to
> use the same UI framework for both, but would need to take performance into
> account.
>
> I would love to use a component based framework for the admin UI. This
> leaves us with: JSF, Tapestry, Wicket, GWT... perhaps even SWT deployed via
> Java WebStart. The SWT solution is a bit risky, as we'd have to contend with
> corporate firewalls and basically come up with some HTTP tunneling solution
> (JAX-WS?). GWT is intriguing, but not an option for the CMS-driven
> front-end. Tapestry hasn't even entered into my mindshare, but I'm leery
> based on their track record of breaking backward-compatibility. This leaves
> us with Wicket and JSF. I've played with both technologies (v1.2.4 of
> Wicket), and JSF just scares me. I've used Facelets and Seam with JSF. We
> cannot take advantage of Seam because of the tiered architecture of our
> application (separate presentation and service clusters).
>
> So there's Wicket. Right now, I have the following reservations with Wicket:
> - Dates. When will 1.3 be released? How about 1.4?
> - Documentation. There's not one coherent document for 1.3... the Wiki is
> littered with bits of wisdom, but it's hard to tell what techniques work
> with or are obsoleted by version 1.3...
> - Books. When are the books coming out?
> - CMS... as I've said, the front-end is CMS driven, and because of load, I'd
> like to keep things stateless as much as possible (altho, all bets are off
> when the user logs in). I haven't yet found a good description of how 1.3
> handles session state. I'd also like to know if I can mount bookmarkable
> pages dynamically... say if someone were to create and publish a new CMS
> page from the admin app.
>
> I like what I've seen of Wicket so far, and I would love to deploy the first
> enterprise-class application running Wicket, but I need some advice to get
> rid of the butterflies in my stomach.
>
> Regards,
>
> - P
> --
> View this message in context:
> http://www.nabble.com/Evaluating-Wicket-tf3909204.html#a11084242
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to