Re: what is Wicket 2.x?

[Kees van Dieren]

We are using Wicket 6 .0 on OC4j 10.1.3.5. This is a Servlet 2.4 container
with support of some Servlet api 2.5 features.

Work well here.

The quickstart application works on OC4J (
http://wicket.apache.org/start/quickstart.html). (some slight modification
is needed when using Wicket via a web.xml Filter).

If you are familiar with Maven, using the quickstart archetype it is quite
easy to give it a try :).





2012/12/11 Joachim Schrod 

> Martijn Dashorst wrote:
> > On Mon, Dec 10, 2012 at 4:39 PM, Joachim Schrod  wrote:
> >> I'd like to add my voice to Martijn's comment that there are still
> >> people out there who have no choice but to use 1.4. Typically guys
> >> who have to support Wicket apps on app servers with no servlet-2.5-api.
> >
> > I'm not 100% sure, but did you try running a newer wicket (1.5) on ye
> > old container?
>
> Actually, no. The relase notes said "you need to have servlet api
> 2.5" and I believed them.
>
> Joachim
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Joachim Schrod, Roedermark, Germany
> Email: jsch...@acm.org
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Best regards / Met vriendelijke groet,

Kees van Dieren
Squins | IT, Honestly
Oranjestraat 23
2983 HL Ridderkerk
The Netherlands
Mobile: +31 (0)6 30413841
www.squins.com
http://twitter.com/keesvandieren
Chamber of commerce Rotterdam: 24435130
Boeken voor school en werk bestel je op studieboekencenter.nl

Re: what is Wicket 2.x?

[Joachim Schrod]

Martijn Dashorst wrote:
> On Mon, Dec 10, 2012 at 4:39 PM, Joachim Schrod  wrote:
>> I'd like to add my voice to Martijn's comment that there are still
>> people out there who have no choice but to use 1.4. Typically guys
>> who have to support Wicket apps on app servers with no servlet-2.5-api.
> 
> I'm not 100% sure, but did you try running a newer wicket (1.5) on ye
> old container?

Actually, no. The relase notes said "you need to have servlet api
2.5" and I believed them.

Joachim

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod, Roedermark, Germany
Email: jsch...@acm.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: what is Wicket 2.x?

[Martijn Dashorst]

On Mon, Dec 10, 2012 at 4:39 PM, Joachim Schrod  wrote:
> I'd like to add my voice to Martijn's comment that there are still
> people out there who have no choice but to use 1.4. Typically guys
> who have to support Wicket apps on app servers with no servlet-2.5-api.

I'm not 100% sure, but did you try running a newer wicket (1.5) on ye
old container?

I guess it should not be too difficult of fixing 1.5 to actually run
on a 2.4 servlet api.

At least Wicket 1.5.10-SNAPSHOT builds when I modify the servlet API
dependency to 2.4 (no compilation nor unit test failures)

Wicket 6 also requires Java 6, which might pose bigger problems.

> I'm one of them. :-( Next year, upgrade to JBoss 7 and thus Wicket
> 6 is hopefully possible.

I hope so too.

Martijn

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: what is Wicket 2.x?

[Joachim Schrod]

Martin Grigorov wrote:
> 
> Additionally I think that everything that is related to Wicket 1.4 and less
> should be removed from the Wiki.

I'd like to add my voice to Martijn's comment that there are still
people out there who have no choice but to use 1.4. Typically guys
who have to support Wicket apps on app servers with no servlet-2.5-api.

I'm one of them. :-( Next year, upgrade to JBoss 7 and thus Wicket
6 is hopefully possible.

Joachim

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod, Roedermark, Germany
Email: jsch...@acm.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: what is Wicket 2.x?

[Martijn Dashorst]

On Mon, Dec 10, 2012 at 10:24 AM, Martin Grigorov  wrote:
> everyone can edit the wiki pages. All you need is to create an account.
>
> Additionally I think that everything that is related to Wicket 1.4 and less
> should be removed from the Wiki.

Funny, I just gave a presentation to a institution that still runs
Wicket 1.4 applications and can only upgrade next year to a more
recent version (6)

I think we probably should compartmentalize the various pages better
(tagging?) so information about 1.4 is easier to detect.

Martijn

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: what is Wicket 2.x?

[Martin Grigorov]

Hi,

everyone can edit the wiki pages. All you need is to create an account.

Additionally I think that everything that is related to Wicket 1.4 and less
should be removed from the Wiki.


On Sat, Dec 8, 2012 at 3:21 PM, Lucio Crusca  wrote:

> In data venerdì 7 dicembre 2012 20:06:45, Jeremy Thomerson ha scritto:
> > Yep.  There was a big change to constructors IIRC, although I can't
> > remember exactly what the change was.  Next came 1.3.0 with generics.
> >
>
> Can I (we, you, ...) edit that sentence from the wiki pages then? It's
> confusing for newcomers like me. Does the IModel interface work as
> described
> in that page also in 6.x, except for generics?
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com 

Re: what is Wicket 2.x?

[Lucio Crusca]

In data venerdì 7 dicembre 2012 20:06:45, Jeremy Thomerson ha scritto:
> Yep.  There was a big change to constructors IIRC, although I can't
> remember exactly what the change was.  Next came 1.3.0 with generics.
> 

Can I (we, you, ...) edit that sentence from the wiki pages then? It's 
confusing for newcomers like me. Does the IModel interface work as described 
in that page also in 6.x, except for generics?

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: what is Wicket 2.x?

[Martijn Dashorst]

Instead of adding components to their parents, you provide a child
with their parent at construction time. The idea was that it would
help in parsing, component construction and better feedback when
creating pages. The burden it imposed outweighed the benefits be a
great margin.

Martijn

On Fri, Dec 7, 2012 at 8:06 PM, Jeremy Thomerson
 wrote:
> Yep.  There was a big change to constructors IIRC, although I can't
> remember exactly what the change was.  Next came 1.3.0 with generics.
>
>
>
> --
> Jeremy Thomerson
> http://wickettraining.com
> *Need a CMS for Wicket?  Use Brix! http://brixcms.org*
>
>
> On Fri, Dec 7, 2012 at 12:55 PM, Pierre Goupil wrote:
>
>> Good evening,
>>
>> It's an old experiment which was due to go to "ready for prime-time" but
>> never succeeded. If I remember correctly, it was before what became Wicket
>> 1.3.
>>
>> Regards,
>>
>> Pierre
>>
>>
>> On Fri, Dec 7, 2012 at 7:47 PM, Lucio Crusca  wrote:
>>
>> > Hello *,
>> >
>> > while reading this page
>> >
>> > https://cwiki.apache.org/WICKET/working-with-wicket-models.html
>> >
>> > I stumbled upon the following sentence:
>> >
>> > «NOTE: this page is about models like they exist for Wicket 1.x. The
>> IModel
>> > interface is slightly changed in Wicket 2.x»
>> >
>> > What version of Wicket is 2.x? I'm aware of 1.x and 6.x, but never heard
>> > about
>> > 2.x...
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> > For additional commands, e-mail: users-h...@wicket.apache.org
>> >
>> >
>>
>>
>> --
>> Le bonheur n'est pas une destination, mais une façon de voyager.
>>
>> Papa d'une petite Lou-Ann depuis le 30 juin.
>>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: what is Wicket 2.x?

[Jeremy Thomerson]

Yep.  There was a big change to constructors IIRC, although I can't
remember exactly what the change was.  Next came 1.3.0 with generics.



-- 
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket?  Use Brix! http://brixcms.org*


On Fri, Dec 7, 2012 at 12:55 PM, Pierre Goupil wrote:

> Good evening,
>
> It's an old experiment which was due to go to "ready for prime-time" but
> never succeeded. If I remember correctly, it was before what became Wicket
> 1.3.
>
> Regards,
>
> Pierre
>
>
> On Fri, Dec 7, 2012 at 7:47 PM, Lucio Crusca  wrote:
>
> > Hello *,
> >
> > while reading this page
> >
> > https://cwiki.apache.org/WICKET/working-with-wicket-models.html
> >
> > I stumbled upon the following sentence:
> >
> > «NOTE: this page is about models like they exist for Wicket 1.x. The
> IModel
> > interface is slightly changed in Wicket 2.x»
> >
> > What version of Wicket is 2.x? I'm aware of 1.x and 6.x, but never heard
> > about
> > 2.x...
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
>
> --
> Le bonheur n'est pas une destination, mais une façon de voyager.
>
> Papa d'une petite Lou-Ann depuis le 30 juin.
>

Re: what is Wicket 2.x?

[Pierre Goupil]

Good evening,

It's an old experiment which was due to go to "ready for prime-time" but
never succeeded. If I remember correctly, it was before what became Wicket
1.3.

Regards,

Pierre


On Fri, Dec 7, 2012 at 7:47 PM, Lucio Crusca  wrote:

> Hello *,
>
> while reading this page
>
> https://cwiki.apache.org/WICKET/working-with-wicket-models.html
>
> I stumbled upon the following sentence:
>
> «NOTE: this page is about models like they exist for Wicket 1.x. The IModel
> interface is slightly changed in Wicket 2.x»
>
> What version of Wicket is 2.x? I'm aware of 1.x and 6.x, but never heard
> about
> 2.x...
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Le bonheur n'est pas une destination, mais une façon de voyager.

Papa d'une petite Lou-Ann depuis le 30 juin.

what is Wicket 2.x?

[Lucio Crusca]

Hello *,

while reading this page

https://cwiki.apache.org/WICKET/working-with-wicket-models.html

I stumbled upon the following sentence:

«NOTE: this page is about models like they exist for Wicket 1.x. The IModel 
interface is slightly changed in Wicket 2.x»

What version of Wicket is 2.x? I'm aware of 1.x and 6.x, but never heard about 
2.x...

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: what is wicket

[Christopher L Merrill]

Gerald Fernando wrote:

Hello Friends,
Am Gerald, new to wicket.
can anyone say about wicket and advantages over other technologies
it is very useful to my next step.
please help me


http://lmgtfy.com/?q=wicket+advantages

--
 -
Chris Merrill   |  Web Performance, Inc.
ch...@webperformance.com|  http://webperformance.com
919-433-1762|  919-845-7601

Website Load Testing and Stress Testing Software & Services
 -

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: what is wicket

[Craig McIlwee]

This is probably a good starting point:
http://wicket.apache.org/introduction.html

Craig

-Original Message-
From: Gerald Fernando [mailto:gerald.anto.ferna...@gmail.com]
Sent: Tuesday, July 14, 2009 8:51 AM
To: users@wicket.apache.org
Subject: what is wicket

Hello Friends,
Am Gerald, new to wicket.
can anyone say about wicket and advantages over other technologies
it is very useful to my next step.
please help me

Thanks&Regards,
Gerald A



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: what is wicket

[Linda van der Pal]

Have a look at the documentation: http://wicket.apache.org/introduction.html

Linda

Gerald Fernando wrote:

Hello Friends,
Am Gerald, new to wicket.
can anyone say about wicket and advantages over other technologies
it is very useful to my next step.
please help me

Thanks&Regards,
Gerald A

  




No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.5.375 / Virus Database: 270.13.13/2237 - Release Date: 07/14/09 05:56:00


  



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: what is wicket

[francisco treacy]

Well... comparing to what other technologies? There are plenty of
resources on the net. Just use your favourite search engine.

You may want to start with this:
http://ptrthomas.wordpress.com/2007/05/14/a-wicket-user-tries-jsf/

Francisco

2009/7/14 Gerald Fernando :
> Hello Friends,
> Am Gerald, new to wicket.
> can anyone say about wicket and advantages over other technologies
> it is very useful to my next step.
> please help me
>
> Thanks&Regards,
> Gerald A
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: what is wicket

[Erik van Oosten]

Hello Gerald,

You can find much of this kind of information on http://wicket.apache.org.

Regards,
Erik.


On Tue, 14 Jul 2009 18:21:16 +0530, Gerald Fernando
 wrote:
> Hello Friends,
> Am Gerald, new to wicket.
> can anyone say about wicket and advantages over other technologies
> it is very useful to my next step.
> please help me
> 
> Thanks&Regards,
> Gerald A

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

what is wicket

[Gerald Fernando]

Hello Friends,
Am Gerald, new to wicket.
can anyone say about wicket and advantages over other technologies
it is very useful to my next step.
please help me

Thanks&Regards,
Gerald A

Re: What is Wicket? from WIA

[Eyal Golan]

wow.
thanks.
That was very helpful :)

Eyal

On Mon, Jun 2, 2008 at 12:08 AM, Eelco Hillenius <[EMAIL PROTECTED]>
wrote:

> Wicket supports private state for individual components, whereas the
> traditional (REST) pattern assumes to take the state out (to string
> based request parameters) and up to the request level. The big
> difference is that without using a framework like Wicket, you can't
> really create self contained components. You have to ensure that state
> gets passed in any URL that is generated on a page, ensure the
> parameters are properly scoped, have to worry about how to serialize
> and de-serialize (from regular objects to strings and vice versa),
> etc.
>
> You can test this by creating a Struts app where you create a pageable
> list. You'd append parameters for e.g. the page number and query to
> every URL that passes back to the page, even if the link you are
> constructing has nothing to do with the pageable list. Just the fact
> that it is on the page means you have to pass the parameter. That by
> itself is doable - though destroys encapsulation -; the problems
> really start when you decide to move/ reuse the 'component' to/ in
> another page, and when e.g. you add more things to the pass that need
> to pass state like for instance tabs.
>
> Eelco
>
> On Sun, Jun 1, 2008 at 1:53 PM, Eyal Golan <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I read chapter 1 in Wicket in Action and I have a question.
> > in section 1.2.1 it says:
> > "You can get rid of all of these problems  by using Wicket.  It  is  a
> > stateful framework,  so you
> > don't have  to follow  the REST  (though you can,  but we will  talk
> about
> > that  later  in this  book)
> > approach. The main idea behind REST is scalability. Fine. But let me make
> a
> > bold statement here:
> > Very often, REST is premature optimization."
> >
> > Wicket is my first Web Framework and I was wondering if someone can
> explain
> > why Wicket solves the REST problem (which I understood the problem
> itself).
> > Is it because in Wicket we don;t need to pass parameters in the request?
> And
> > instead we create pages with the necessary information? (or something
> like
> > that)
> >
> > Thank
> >
> > --
> > Eyal Golan
> > [EMAIL PROTECTED]
> >
> > Visit: http://jvdrums.sourceforge.net/
> > LinkedIn: http://www.linkedin.com/in/egolan74
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Eyal Golan
[EMAIL PROTECTED]

Visit: http://jvdrums.sourceforge.net/
LinkedIn: http://www.linkedin.com/in/egolan74

Re: What is Wicket? from WIA

[Eelco Hillenius]

Wicket supports private state for individual components, whereas the
traditional (REST) pattern assumes to take the state out (to string
based request parameters) and up to the request level. The big
difference is that without using a framework like Wicket, you can't
really create self contained components. You have to ensure that state
gets passed in any URL that is generated on a page, ensure the
parameters are properly scoped, have to worry about how to serialize
and de-serialize (from regular objects to strings and vice versa),
etc.

You can test this by creating a Struts app where you create a pageable
list. You'd append parameters for e.g. the page number and query to
every URL that passes back to the page, even if the link you are
constructing has nothing to do with the pageable list. Just the fact
that it is on the page means you have to pass the parameter. That by
itself is doable - though destroys encapsulation -; the problems
really start when you decide to move/ reuse the 'component' to/ in
another page, and when e.g. you add more things to the pass that need
to pass state like for instance tabs.

Eelco

On Sun, Jun 1, 2008 at 1:53 PM, Eyal Golan <[EMAIL PROTECTED]> wrote:
> Hi,
> I read chapter 1 in Wicket in Action and I have a question.
> in section 1.2.1 it says:
> "You can get rid of all of these problems  by using Wicket.  It  is  a
> stateful framework,  so you
> don't have  to follow  the REST  (though you can,  but we will  talk about
> that  later  in this  book)
> approach. The main idea behind REST is scalability. Fine. But let me make a
> bold statement here:
> Very often, REST is premature optimization."
>
> Wicket is my first Web Framework and I was wondering if someone can explain
> why Wicket solves the REST problem (which I understood the problem itself).
> Is it because in Wicket we don;t need to pass parameters in the request? And
> instead we create pages with the necessary information? (or something like
> that)
>
> Thank
>
> --
> Eyal Golan
> [EMAIL PROTECTED]
>
> Visit: http://jvdrums.sourceforge.net/
> LinkedIn: http://www.linkedin.com/in/egolan74
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

What is Wicket? from WIA

[Eyal Golan]

Hi,
I read chapter 1 in Wicket in Action and I have a question.
in section 1.2.1 it says:
"You can get rid of all of these problems  by using Wicket.  It  is  a
stateful framework,  so you
don't have  to follow  the REST  (though you can,  but we will  talk about
that  later  in this  book)
approach. The main idea behind REST is scalability. Fine. But let me make a
bold statement here:
Very often, REST is premature optimization."

Wicket is my first Web Framework and I was wondering if someone can explain
why Wicket solves the REST problem (which I understood the problem itself).
Is it because in Wicket we don;t need to pass parameters in the request? And
instead we create pages with the necessary information? (or something like
that)

Thank

-- 
Eyal Golan
[EMAIL PROTECTED]

Visit: http://jvdrums.sourceforge.net/
LinkedIn: http://www.linkedin.com/in/egolan74