Hi,
i stumbled over
Wicket some time ago and now have time to have a more close look on it.
Therefore i have some questions.
1. I wantet to get a
"Hello World app" working, however, i failed in finding out what is "really"
necessary, to do it. I tried the Quickstart (Eclipse) example, but
Korbinian,
So we deliver a package that contains everything you need, including
documentation, and then you complain that it is not minimal? :-)
A servlet container suffices, so you can do in the quickstart project:
mvn package or ant war and the resulting war file (found in the target
Hi Gwyn,
thank you for your reply,
Just down to the defintion of appserver - all that's
needed is servlet container functionality - We tend to use
Jetty as it's easy to embed in IDEs run standalone, but
there's no requirement for it over any other servlet engine.
ok, then it seems as
well, i follow the definition by sun - not marketing buzz
:P
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von James
CookGesendet: Donnerstag, 3. August 2006 15:07An:
wicket-user@lists.sourceforge.netBetreff: Re: [Wicket-user] Basic
Skeleton, Beginner
Hi Martijn,
So we deliver a package that contains everything you need,
including documentation, and then you complain that it is not
minimal? :-)
well, these additional things were the problem for me ;) - no, seriously,
because of the included jetty, docs and other jars i was a bit
On 8/3/06, Korbinian Bachl [EMAIL PROTECTED] wrote:
ok, then it seems as the wicket-homepage is bit away of the officialspecification what anappserver is (these are only the big-thing with whole EE stack with them)Not to pick nits, but I think maybe your understanding of 'appserver' is a bit
the reason why jetty is included is that there is a little file called Start.java. setup the project in the ide, right click Start to debug as a java application and bam you get a working servlet container setup with your app in exploded form. no need to package/deploy/blah blah
-IgorOn 8/3/06,
