Re: Setup Wicket in Eclipse without need to re-initialize the whole servlet container

2012-09-10 Thread Dmitry Zamula
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.wag...@gmail.com seba.wag...@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.wag...@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.brant...@gmail.com


Re: Setup Wicket in Eclipse without need to re-initialize the whole servlet container

2012-09-09 Thread Michael Mosmann
I have used run-jetty-run as eclipse plugin... If this is not enough, you 
should use jrebel.

Michael mosmann



seba.wag...@gmail.com seba.wag...@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.wag...@gmail.com

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

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Re: Setup Wicket in Eclipse without need to re-initialize the whole servlet container

2012-09-09 Thread Alec Swan
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 mich...@mosmann.de wrote:
 I have used run-jetty-run as eclipse plugin... If this is not enough, you 
 should use jrebel.

 Michael mosmann



 seba.wag...@gmail.com seba.wag...@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.wag...@gmail.com

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

 --
 Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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



Re: Setup Wicket in Eclipse without need to re-initialize the whole servlet container

2012-09-09 Thread zenith77
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+s1842946n4651880...@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=nodenode=4651880i=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=nodenode=4651880i=1
 [hidden email] http://user/SendEmail.jtp?type=nodenode=4651880i=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=nodenode=4651880i=3
 
 -
 To unsubscribe, e-mail: [hidden 
 email]http://user/SendEmail.jtp?type=nodenode=4651880i=4
 For additional commands, e-mail: [hidden 
 email]http://user/SendEmail.jtp?type=nodenode=4651880i=5
 
  --
  Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
 gesendet.

 -
 To unsubscribe, e-mail: [hidden 
 email]http://user/SendEmail.jtp?type=nodenode=4651880i=6
 For additional commands, e-mail: [hidden 
 email]http://user/SendEmail.jtp?type=nodenode=4651880i=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 
 herehttp://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=1842946code=Y29saW5yb2dlcnM3N0BnbWFpbC5jb218MTg0Mjk0Nnw4ODcwMzk5Nzg=
 .
 NAMLhttp://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=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-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org