You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openmeetings.apache.org by "seba.wagner@gmail.com" <se...@gmail.com> on 2012/09/09 19:27:02 UTC
Setup Wicket in Eclipse without need to re-initialize the whole
servlet container
Hi,
we have set up Wicket in OpenMeetings and it is working fine!
However the development cycle is pretty long:
Every change requires us to recompile and restart the servlet container.
As we use Wicket + Spring + openJPA a restart takes around 20 seconds
+ compilations time, it takes around 30 seconds in total.
When working with UI components you regularly sit on your desk and
wait for this cycle to complete ;)
Is there a way to develop and test Wicket more agile?
Is there some "Hot-plug" mechanism that does not require to reload the
whole servlet container with every change?
Thanks!
Sebastian
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: Setup Wicket in Eclipse without need to re-initialize the whole
servlet container
Posted by Maxim Solodovnik <so...@gmail.com>.
You need to modify red5-debug and set your own path to jrebel.jar
On Wed, Sep 12, 2012 at 2:08 PM, Maxim Solodovnik <so...@gmail.com>wrote:
> I believe commiting it into SVN will not be a good idea (since JRebel is
> not free)
> attached are my changes to the current trunk + modified red5-debug.bat
>
> The only thing need to be done after Red5 is started: modify file and save
> it :)
>
> Please let me know if you need more details on this
>
>
> On Wed, Sep 12, 2012 at 2:02 PM, seba.wagner@gmail.com <
> seba.wagner@gmail.com> wrote:
>
>> We might ask at the general list. Maybe there is a cooperation with
>> the ASF or for Apache projects.
>> Please share your project setup :)
>>
>> Sebastian
>>
>> 2012/9/12 Maxim Solodovnik <so...@gmail.com>:
>> > I finally was able to find time and set up JRebel for Openmeetings.
>> > What I should note: it is working :))
>> >
>> > @Sebastian
>> > Should I tried to apply for 1-year free OSS license? (I'm not sure what
>> > will happens after 1 year will pass, but we can try it)
>> >
>> > What do you think?
>> > I can share configuration/setup details.
>> >
>> >
>> > On Mon, Sep 10, 2012 at 8:29 AM, Maxim Solodovnik <solomax666@gmail.com
>> >wrote:
>> >
>> >> Thanks,
>> >>
>> >> I'll try it.
>> >>
>> >>
>> >> On Mon, Sep 10, 2012 at 1:45 AM, Dmitry Zamula <
>> club.brantner@gmail.com>wrote:
>> >>
>> >>> Hello, Sebastian.
>> >>>
>> >>> You can try to use JRebel (http://zeroturnaround.com/software/jrebel/
>> ).
>> >>> This is a JVM agent, that eliminates the need for redeployment. You
>> can
>> >>> read about JRebel and Wicket here:
>> >>>
>> http://zeroturnaround.com/software/jrebel/how-to-use-jrebel-with-wicket/
>> >>>
>> >>> P.S. JRebel is free for opensource projects.
>> >>>
>> >>> 2012/9/9 seba.wagner@gmail.com <se...@gmail.com>
>> >>>
>> >>> > Hi,
>> >>> >
>> >>> > we have set up Wicket in OpenMeetings and it is working fine!
>> >>> >
>> >>> > However the development cycle is pretty long:
>> >>> > Every change requires us to recompile and restart the servlet
>> container.
>> >>> > As we use Wicket + Spring + openJPA a restart takes around 20
>> seconds
>> >>> > + compilations time, it takes around 30 seconds in total.
>> >>> > When working with UI components you regularly sit on your desk and
>> >>> > wait for this cycle to complete ;)
>> >>> >
>> >>> > Is there a way to develop and test Wicket more agile?
>> >>> > Is there some "Hot-plug" mechanism that does not require to reload
>> the
>> >>> > whole servlet container with every change?
>> >>> >
>> >>> > Thanks!
>> >>> > Sebastian
>> >>> >
>> >>> > --
>> >>> > Sebastian Wagner
>> >>> > https://twitter.com/#!/dead_lock
>> >>> > http://www.webbase-design.de
>> >>> > http://www.wagner-sebastian.com
>> >>> > seba.wagner@gmail.com
>> >>> >
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Best Regards,
>> >>> *Dmitry Zamula*
>> >>>
>> >>> Saint-Petersburg, Russia
>> >>> UTC/GMT +4 hours
>> >>>
>> >>> Mobile phone: +7 (904) 646-9254
>> >>> Skype Id: brantner_ru
>> >>> E-mail: club.brantner@gmail.com
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> WBR
>> >> Maxim aka solomax
>> >>
>> >
>> >
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>>
>>
>>
>> --
>> Sebastian Wagner
>> https://twitter.com/#!/dead_lock
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wagner@gmail.com
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: Setup Wicket in Eclipse without need to re-initialize the whole
servlet container
Posted by Maxim Solodovnik <so...@gmail.com>.
I believe commiting it into SVN will not be a good idea (since JRebel is
not free)
attached are my changes to the current trunk + modified red5-debug.bat
The only thing need to be done after Red5 is started: modify file and save
it :)
Please let me know if you need more details on this
On Wed, Sep 12, 2012 at 2:02 PM, seba.wagner@gmail.com <
seba.wagner@gmail.com> wrote:
> We might ask at the general list. Maybe there is a cooperation with
> the ASF or for Apache projects.
> Please share your project setup :)
>
> Sebastian
>
> 2012/9/12 Maxim Solodovnik <so...@gmail.com>:
> > I finally was able to find time and set up JRebel for Openmeetings.
> > What I should note: it is working :))
> >
> > @Sebastian
> > Should I tried to apply for 1-year free OSS license? (I'm not sure what
> > will happens after 1 year will pass, but we can try it)
> >
> > What do you think?
> > I can share configuration/setup details.
> >
> >
> > On Mon, Sep 10, 2012 at 8:29 AM, Maxim Solodovnik <solomax666@gmail.com
> >wrote:
> >
> >> Thanks,
> >>
> >> I'll try it.
> >>
> >>
> >> On Mon, Sep 10, 2012 at 1:45 AM, Dmitry Zamula <club.brantner@gmail.com
> >wrote:
> >>
> >>> Hello, Sebastian.
> >>>
> >>> You can try to use JRebel (http://zeroturnaround.com/software/jrebel/
> ).
> >>> This is a JVM agent, that eliminates the need for redeployment. You can
> >>> read about JRebel and Wicket here:
> >>>
> http://zeroturnaround.com/software/jrebel/how-to-use-jrebel-with-wicket/
> >>>
> >>> P.S. JRebel is free for opensource projects.
> >>>
> >>> 2012/9/9 seba.wagner@gmail.com <se...@gmail.com>
> >>>
> >>> > Hi,
> >>> >
> >>> > we have set up Wicket in OpenMeetings and it is working fine!
> >>> >
> >>> > However the development cycle is pretty long:
> >>> > Every change requires us to recompile and restart the servlet
> container.
> >>> > As we use Wicket + Spring + openJPA a restart takes around 20 seconds
> >>> > + compilations time, it takes around 30 seconds in total.
> >>> > When working with UI components you regularly sit on your desk and
> >>> > wait for this cycle to complete ;)
> >>> >
> >>> > Is there a way to develop and test Wicket more agile?
> >>> > Is there some "Hot-plug" mechanism that does not require to reload
> the
> >>> > whole servlet container with every change?
> >>> >
> >>> > Thanks!
> >>> > Sebastian
> >>> >
> >>> > --
> >>> > Sebastian Wagner
> >>> > https://twitter.com/#!/dead_lock
> >>> > http://www.webbase-design.de
> >>> > http://www.wagner-sebastian.com
> >>> > seba.wagner@gmail.com
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> Best Regards,
> >>> *Dmitry Zamula*
> >>>
> >>> Saint-Petersburg, Russia
> >>> UTC/GMT +4 hours
> >>>
> >>> Mobile phone: +7 (904) 646-9254
> >>> Skype Id: brantner_ru
> >>> E-mail: club.brantner@gmail.com
> >>>
> >>
> >>
> >>
> >> --
> >> WBR
> >> Maxim aka solomax
> >>
> >
> >
> >
> > --
> > WBR
> > Maxim aka solomax
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
--
WBR
Maxim aka solomax
Re: Setup Wicket in Eclipse without need to re-initialize the whole
servlet container
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
We might ask at the general list. Maybe there is a cooperation with
the ASF or for Apache projects.
Please share your project setup :)
Sebastian
2012/9/12 Maxim Solodovnik <so...@gmail.com>:
> I finally was able to find time and set up JRebel for Openmeetings.
> What I should note: it is working :))
>
> @Sebastian
> Should I tried to apply for 1-year free OSS license? (I'm not sure what
> will happens after 1 year will pass, but we can try it)
>
> What do you think?
> I can share configuration/setup details.
>
>
> On Mon, Sep 10, 2012 at 8:29 AM, Maxim Solodovnik <so...@gmail.com>wrote:
>
>> Thanks,
>>
>> I'll try it.
>>
>>
>> On Mon, Sep 10, 2012 at 1:45 AM, Dmitry Zamula <cl...@gmail.com>wrote:
>>
>>> Hello, Sebastian.
>>>
>>> You can try to use JRebel (http://zeroturnaround.com/software/jrebel/).
>>> This is a JVM agent, that eliminates the need for redeployment. You can
>>> read about JRebel and Wicket here:
>>> http://zeroturnaround.com/software/jrebel/how-to-use-jrebel-with-wicket/
>>>
>>> P.S. JRebel is free for opensource projects.
>>>
>>> 2012/9/9 seba.wagner@gmail.com <se...@gmail.com>
>>>
>>> > Hi,
>>> >
>>> > we have set up Wicket in OpenMeetings and it is working fine!
>>> >
>>> > However the development cycle is pretty long:
>>> > Every change requires us to recompile and restart the servlet container.
>>> > As we use Wicket + Spring + openJPA a restart takes around 20 seconds
>>> > + compilations time, it takes around 30 seconds in total.
>>> > When working with UI components you regularly sit on your desk and
>>> > wait for this cycle to complete ;)
>>> >
>>> > Is there a way to develop and test Wicket more agile?
>>> > Is there some "Hot-plug" mechanism that does not require to reload the
>>> > whole servlet container with every change?
>>> >
>>> > Thanks!
>>> > Sebastian
>>> >
>>> > --
>>> > Sebastian Wagner
>>> > https://twitter.com/#!/dead_lock
>>> > http://www.webbase-design.de
>>> > http://www.wagner-sebastian.com
>>> > seba.wagner@gmail.com
>>> >
>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> *Dmitry Zamula*
>>>
>>> Saint-Petersburg, Russia
>>> UTC/GMT +4 hours
>>>
>>> Mobile phone: +7 (904) 646-9254
>>> Skype Id: brantner_ru
>>> E-mail: club.brantner@gmail.com
>>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
>
> --
> WBR
> Maxim aka solomax
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: Setup Wicket in Eclipse without need to re-initialize the whole
servlet container
Posted by Maxim Solodovnik <so...@gmail.com>.
I finally was able to find time and set up JRebel for Openmeetings.
What I should note: it is working :))
@Sebastian
Should I tried to apply for 1-year free OSS license? (I'm not sure what
will happens after 1 year will pass, but we can try it)
What do you think?
I can share configuration/setup details.
On Mon, Sep 10, 2012 at 8:29 AM, Maxim Solodovnik <so...@gmail.com>wrote:
> Thanks,
>
> I'll try it.
>
>
> On Mon, Sep 10, 2012 at 1:45 AM, Dmitry Zamula <cl...@gmail.com>wrote:
>
>> Hello, Sebastian.
>>
>> You can try to use JRebel (http://zeroturnaround.com/software/jrebel/).
>> This is a JVM agent, that eliminates the need for redeployment. You can
>> read about JRebel and Wicket here:
>> http://zeroturnaround.com/software/jrebel/how-to-use-jrebel-with-wicket/
>>
>> P.S. JRebel is free for opensource projects.
>>
>> 2012/9/9 seba.wagner@gmail.com <se...@gmail.com>
>>
>> > Hi,
>> >
>> > we have set up Wicket in OpenMeetings and it is working fine!
>> >
>> > However the development cycle is pretty long:
>> > Every change requires us to recompile and restart the servlet container.
>> > As we use Wicket + Spring + openJPA a restart takes around 20 seconds
>> > + compilations time, it takes around 30 seconds in total.
>> > When working with UI components you regularly sit on your desk and
>> > wait for this cycle to complete ;)
>> >
>> > Is there a way to develop and test Wicket more agile?
>> > Is there some "Hot-plug" mechanism that does not require to reload the
>> > whole servlet container with every change?
>> >
>> > Thanks!
>> > Sebastian
>> >
>> > --
>> > Sebastian Wagner
>> > https://twitter.com/#!/dead_lock
>> > http://www.webbase-design.de
>> > http://www.wagner-sebastian.com
>> > seba.wagner@gmail.com
>> >
>>
>>
>>
>> --
>> Best Regards,
>> *Dmitry Zamula*
>>
>> Saint-Petersburg, Russia
>> UTC/GMT +4 hours
>>
>> Mobile phone: +7 (904) 646-9254
>> Skype Id: brantner_ru
>> E-mail: club.brantner@gmail.com
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: Setup Wicket in Eclipse without need to re-initialize the whole
servlet container
Posted by Maxim Solodovnik <so...@gmail.com>.
Thanks,
I'll try it.
On Mon, Sep 10, 2012 at 1:45 AM, Dmitry Zamula <cl...@gmail.com>wrote:
> Hello, Sebastian.
>
> You can try to use JRebel (http://zeroturnaround.com/software/jrebel/).
> This is a JVM agent, that eliminates the need for redeployment. You can
> read about JRebel and Wicket here:
> http://zeroturnaround.com/software/jrebel/how-to-use-jrebel-with-wicket/
>
> P.S. JRebel is free for opensource projects.
>
> 2012/9/9 seba.wagner@gmail.com <se...@gmail.com>
>
> > Hi,
> >
> > we have set up Wicket in OpenMeetings and it is working fine!
> >
> > However the development cycle is pretty long:
> > Every change requires us to recompile and restart the servlet container.
> > As we use Wicket + Spring + openJPA a restart takes around 20 seconds
> > + compilations time, it takes around 30 seconds in total.
> > When working with UI components you regularly sit on your desk and
> > wait for this cycle to complete ;)
> >
> > Is there a way to develop and test Wicket more agile?
> > Is there some "Hot-plug" mechanism that does not require to reload the
> > whole servlet container with every change?
> >
> > Thanks!
> > Sebastian
> >
> > --
> > Sebastian Wagner
> > https://twitter.com/#!/dead_lock
> > http://www.webbase-design.de
> > http://www.wagner-sebastian.com
> > seba.wagner@gmail.com
> >
>
>
>
> --
> Best Regards,
> *Dmitry Zamula*
>
> Saint-Petersburg, Russia
> UTC/GMT +4 hours
>
> Mobile phone: +7 (904) 646-9254
> Skype Id: brantner_ru
> E-mail: club.brantner@gmail.com
>
--
WBR
Maxim aka solomax
Re: Setup Wicket in Eclipse without need to re-initialize the whole
servlet container
Posted by Dmitry Zamula <cl...@gmail.com>.
Hello, Sebastian.
You can try to use JRebel (http://zeroturnaround.com/software/jrebel/).
This is a JVM agent, that eliminates the need for redeployment. You can
read about JRebel and Wicket here:
http://zeroturnaround.com/software/jrebel/how-to-use-jrebel-with-wicket/
P.S. JRebel is free for opensource projects.
2012/9/9 seba.wagner@gmail.com <se...@gmail.com>
> Hi,
>
> we have set up Wicket in OpenMeetings and it is working fine!
>
> However the development cycle is pretty long:
> Every change requires us to recompile and restart the servlet container.
> As we use Wicket + Spring + openJPA a restart takes around 20 seconds
> + compilations time, it takes around 30 seconds in total.
> When working with UI components you regularly sit on your desk and
> wait for this cycle to complete ;)
>
> Is there a way to develop and test Wicket more agile?
> Is there some "Hot-plug" mechanism that does not require to reload the
> whole servlet container with every change?
>
> Thanks!
> Sebastian
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
--
Best Regards,
*Dmitry Zamula*
Saint-Petersburg, Russia
UTC/GMT +4 hours
Mobile phone: +7 (904) 646-9254
Skype Id: brantner_ru
E-mail: club.brantner@gmail.com
Re: Setup Wicket in Eclipse without need to re-initialize the whole
servlet container
Posted by Dmitry Zamula <cl...@gmail.com>.
Hello, Sebastian.
You can try to use JRebel (http://zeroturnaround.com/software/jrebel/).
This is a JVM agent, that eliminates the need for redeployment. You can
read about JRebel and Wicket here:
http://zeroturnaround.com/software/jrebel/how-to-use-jrebel-with-wicket/
P.S. JRebel is free for opensource projects.
2012/9/9 seba.wagner@gmail.com <se...@gmail.com>
> Hi,
>
> we have set up Wicket in OpenMeetings and it is working fine!
>
> However the development cycle is pretty long:
> Every change requires us to recompile and restart the servlet container.
> As we use Wicket + Spring + openJPA a restart takes around 20 seconds
> + compilations time, it takes around 30 seconds in total.
> When working with UI components you regularly sit on your desk and
> wait for this cycle to complete ;)
>
> Is there a way to develop and test Wicket more agile?
> Is there some "Hot-plug" mechanism that does not require to reload the
> whole servlet container with every change?
>
> Thanks!
> Sebastian
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
--
Best Regards,
*Dmitry Zamula*
Saint-Petersburg, Russia
UTC/GMT +4 hours
Mobile phone: +7 (904) 646-9254
Skype Id: brantner_ru
E-mail: club.brantner@gmail.com
Re: Setup Wicket in Eclipse without need to re-initialize the whole
servlet container
Posted by zenith77 <co...@gmail.com>.
I use the simplest of setups - embedded Jetty in a Java main method, and run
from within Eclipse in debug mode. I just point the root directory to my
local project files, and off I go. No buggy plug-ins, or configuration -
just plain old Java.
Means you can edit java files and they automatically hotswap and
resources automatically
update. Can post the code up later, if you want? (although there are plenty
of examples on the web).
I usually have two versions - one that runs in the maven 'test' directories and
uses the 'test' configuration and another that runs in the 'main' directories
and uses the deployment configuration.
On 10 September 2012 03:47, Alec Swan [via Apache Wicket] <
ml-node+s1842946n4651880h68@n4.nabble.com> wrote:
> I had pretty good luck with JRebel. In addition I use
> RemoteSyncronizer IntelliJ plugin to automatically copy HTML/JS/CSS
> files from my source tree to webapp deployment dir.
>
> Alec
>
> On Sun, Sep 9, 2012 at 11:36 AM, Michael Mosmann <[hidden email]<http://user/SendEmail.jtp?type=node&node=4651880&i=0>>
> wrote:
>
> > I have used run-jetty-run as eclipse plugin... If this is not enough,
> you should use jrebel.
> >
> > Michael mosmann
> >
> >
> >
> > "[hidden email] <http://user/SendEmail.jtp?type=node&node=4651880&i=1>"
> <[hidden email] <http://user/SendEmail.jtp?type=node&node=4651880&i=2>>
> schrieb:
> >
> >>Hi,
> >>
> >>we have set up Wicket in OpenMeetings and it is working fine!
> >>
> >>However the development cycle is pretty long:
> >>Every change requires us to recompile and restart the servlet
> >>container.
> >>As we use Wicket + Spring + openJPA a restart takes around 20 seconds
> >>+ compilations time, it takes around 30 seconds in total.
> >>When working with UI components you regularly sit on your desk and
> >>wait for this cycle to complete ;)
> >>
> >>Is there a way to develop and test Wicket more agile?
> >>Is there some "Hot-plug" mechanism that does not require to reload the
> >>whole servlet container with every change?
> >>
> >>Thanks!
> >>Sebastian
> >>
> >>--
> >>Sebastian Wagner
> >>https://twitter.com/#!/dead_lock
> >>http://www.webbase-design.de
> >>http://www.wagner-sebastian.com
> >>[hidden email] <http://user/SendEmail.jtp?type=node&node=4651880&i=3>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: [hidden email]<http://user/SendEmail.jtp?type=node&node=4651880&i=4>
> >>For additional commands, e-mail: [hidden email]<http://user/SendEmail.jtp?type=node&node=4651880&i=5>
> >
> > --
> > Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
> gesendet.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]<http://user/SendEmail.jtp?type=node&node=4651880&i=6>
> For additional commands, e-mail: [hidden email]<http://user/SendEmail.jtp?type=node&node=4651880&i=7>
>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-wicket.1842946.n4.nabble.com/Setup-Wicket-in-Eclipse-without-need-to-re-initialize-the-whole-servlet-container-tp4651878p4651880.html
> To unsubscribe from Apache Wicket, click here<http://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1842946&code=Y29saW5yb2dlcnM3N0BnbWFpbC5jb218MTg0Mjk0Nnw4ODcwMzk5Nzg=>
> .
> NAML<http://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Setup-Wicket-in-Eclipse-without-need-to-re-initialize-the-whole-servlet-container-tp4651878p4651883.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Setup Wicket in Eclipse without need to re-initialize the whole
servlet container
Posted by Alec Swan <al...@gmail.com>.
I had pretty good luck with JRebel. In addition I use
RemoteSyncronizer IntelliJ plugin to automatically copy HTML/JS/CSS
files from my source tree to webapp deployment dir.
Alec
On Sun, Sep 9, 2012 at 11:36 AM, Michael Mosmann <mi...@mosmann.de> wrote:
> I have used run-jetty-run as eclipse plugin... If this is not enough, you should use jrebel.
>
> Michael mosmann
>
>
>
> "seba.wagner@gmail.com" <se...@gmail.com> schrieb:
>
>>Hi,
>>
>>we have set up Wicket in OpenMeetings and it is working fine!
>>
>>However the development cycle is pretty long:
>>Every change requires us to recompile and restart the servlet
>>container.
>>As we use Wicket + Spring + openJPA a restart takes around 20 seconds
>>+ compilations time, it takes around 30 seconds in total.
>>When working with UI components you regularly sit on your desk and
>>wait for this cycle to complete ;)
>>
>>Is there a way to develop and test Wicket more agile?
>>Is there some "Hot-plug" mechanism that does not require to reload the
>>whole servlet container with every change?
>>
>>Thanks!
>>Sebastian
>>
>>--
>>Sebastian Wagner
>>https://twitter.com/#!/dead_lock
>>http://www.webbase-design.de
>>http://www.wagner-sebastian.com
>>seba.wagner@gmail.com
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>For additional commands, e-mail: users-help@wicket.apache.org
>
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Setup Wicket in Eclipse without need to re-initialize the whole servlet container
Posted by Michael Mosmann <mi...@mosmann.de>.
I have used run-jetty-run as eclipse plugin... If this is not enough, you should use jrebel.
Michael mosmann
"seba.wagner@gmail.com" <se...@gmail.com> schrieb:
>Hi,
>
>we have set up Wicket in OpenMeetings and it is working fine!
>
>However the development cycle is pretty long:
>Every change requires us to recompile and restart the servlet
>container.
>As we use Wicket + Spring + openJPA a restart takes around 20 seconds
>+ compilations time, it takes around 30 seconds in total.
>When working with UI components you regularly sit on your desk and
>wait for this cycle to complete ;)
>
>Is there a way to develop and test Wicket more agile?
>Is there some "Hot-plug" mechanism that does not require to reload the
>whole servlet container with every change?
>
>Thanks!
>Sebastian
>
>--
>Sebastian Wagner
>https://twitter.com/#!/dead_lock
>http://www.webbase-design.de
>http://www.wagner-sebastian.com
>seba.wagner@gmail.com
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>For additional commands, e-mail: users-help@wicket.apache.org
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.