so if i am reading this right, You also do the:
code, compile, deploy, debug/test, stop and then -> co...?
Why is everybody doing that? It is so immensely waste of time !!
Deploy only once or whenever the jvm really can't handly the hotswap of
a class
(when you add or remove a instance variable for example)
code/compile/debug/text is one step that you do at the same time
This is how i work since the beginning of my java years (around jdk
version 1.1.5)
johan
Joni Suominen wrote:
On Tue, 2005-08-23 at 16:44 -0500, Jonathan Carlson wrote:
I'm sorry for the stupid question. Feel free to ignore it. I'm trying
to monitor the list and do real work at the same time. (Wicket is my
off-hours passion)
No, problem at all, Wicket is currently my off-hours passion too.
Hopefully I can use it in a commercial project when we get the currently
developed one to production.
I'm curious. What does it do?
Simply put, it just allows you to deploy Wicket components quickly from
Eclipse. It requires a JUnit test case, though. The test case is serving
as a launcher which means that the test fixture and all other test
artifacts (mocks etc.) are readily available in launched application.
Motivation for this kind of (experimental) plugin came while doing
current project (sadly done with Tapestry, we did not have courage to
start with Wicket 0.9 ;). The project is quite large, having more than
200 custom web components and more that 100 web pages. It has more than
50 Hibernate mapping files so even while we use pretty lightweight
containers (Tomcat and Spring), the system takes about 20 seconds to
boot up. A typical development cycle (while coding ui) consists of
following steps:
1. Hot deploy the web app (~15 - 30 s)
2. Run acceptance test fixture in (~5 - 10 s)
3. Navigate to the page where your component is (~5 - 10 s)
And web UI coding tends to require repeated cycles like that. It would
be much more productive and fun if this 25 - 50 second cycle could be
shortened close to 2 seconds.
One of the things which attracts me in Wicket is that its mostly pure
Java, making it very easy to practice Test Driven Development (this
attribute is not common when comparing web ui frameworks). I do not
consider a component to be ready unless it has at least moderately good
tests. So, this plugin allows me to reuse the investments made into test
cases.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
