RE: Can I develop without recompiling/restarting after every change?
Our particular web application simply could not exist if wicket did not allow us to load markup from outside the jar. I think it's fine that the default is loading markup from the jar. I our case we have a number of mechanisms by which more skilled end users can adjust markup so to force an app reload each time an end user does this would certainly place the policy of 'markup should be stored in the jar' outside the realms of best practice. >-Original Message- >From: b...@actrix.gen.nz [mailto:b...@actrix.gen.nz] >Sent: Monday, 7 June 2010 9:05 AM >To: users@wicket.apache.org; John Krasnay >Subject: Re: Can I develop without recompiling/restarting after every >change? > >Hi > >>Yes, I understand that. But you have to put the markup for each >>component somewhere. If it's not on the classpath, then you will not be >>able to package that component into a JAR for re-use. > >As I wrote, both methods co-exist, and you can put markup on the >classpath and package it as jar while other markup is separate from >the classpath. How otherwise would I be able to use Wicket components >with my scheme? Please accept the good news that your "but" is not >justified. > >>No, we disagree because I think that "doing nothing", i.e. keeping your >>component markup on the classpath, *is* the best practice, that is, the >>majority opinion on what makes the most sense for most people. > >Quoting "majority opinion" and "community consensus" is a very weak >contribution to innovation, a sign that the speaker is running out of >genuine ideas. In such context I would typically say that my views >represent the other 100% of such perceived majority/consensus, just to >make it absolutely clear what kind of Orwellian bsht this is. > >Page developers, especially those who work with markup, and that is >the majority that Wicket is targeting (not component developers) need >the markup in the context of their resolvable image, script and other >resource files which is in the web directory. Otherwise they cannot >view the markup in the browser. They don't care where these files are >at runtime as long as they are not broken at design time which they >currently are. You never seem to comment on this critical point. > >> >>If you feel that the default approach isn't the best practice, then you >>are saying that the Wicket designers made a mistake by making this the >>default. I disagree strongly with that sentiment. > >You accept broken markup at design time and I don't accept it because >I have solved the problem. > >I would not go as far as to say they made THAT mistake. As you know, >they gave us the option. But the non-default option is broken because >of the missing three lines of Java code, and whenever people try it, >they become part of your perceived community consensus due to >frustration. Like prisoners. > >>I think perhaps we mean different things by "deploy on save". When I say >>"deploy" I mean it in the J2EE sense, where the container re-loads my >>WAR package. In my case, this re-loads my Spring context and a few dozen >>JPA entity beans, which takes up to 15 seconds on my relatively modern >>laptop. There is no way rearranging my markup (or running it on a "fully >>certified J2EE server") would turn this into milliseconds. > >True. "deploy on save" is not invented here. It is a term used in >IDEs. The IDE decides what deployment method to use depending on file >location etc.. That is one of two reasons why I would recommend to not >store page markup in Java package directories. > > >>Look, the only reason I took up this (now too long) thread is your use >>of the words "best practice", which implies a broadly held consensus. >>Now that you've included "as I see it" I'm happy to let it drop. > >Wrong. > >Best practice does not imply "broadly held consensus" at all. I am not >using this as a buzzword as you are. If I invent a better mouse trap >today that is more effective at delivering the outcome than any other >technique, while the better mouse trap is not even available or known >to everyone, then using it becomes best practice overnight. > >Regards > >Bernard > > >- >To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Can I develop without recompiling/restarting after every change?
hotmail just destroyed my last post. I apologize. I will try one more time to
share my source
import org.mortbay.jetty.Connector;import org.mortbay.jetty.Server;import
org.mortbay.jetty.bio.SocketConnector;import
org.mortbay.jetty.webapp.WebAppContext;import
org.mortbay.jetty.webapp.WebInfConfiguration;import
org.mortbay.jetty.webapp.WebXmlConfiguration;
public class Start {
public static void main(String[] args) throws Exception { Server server =
new Server(); SocketConnector connector = new SocketConnector(); //
Set some timeout options to make debugging easier.
connector.setMaxIdleTime(1000 * 60 * 60); connector.setSoLingerTime(-1);
connector.setPort(8080); server.setConnectors(new Connector[] { connector
}); WebAppContext bb = new WebAppContext(); bb.setServer(server);
bb.setContextPath("/"); bb.setWar("target/MY_APPLICATION");
bb.setConfigurationClasses(new String[] { WebInfConfiguration.class.getName(),
WebXmlConfiguration.class.getName() }); bb.setParentLoaderPriority(true);
// START JMX SERVER // MBeanServer mBeanServer =
ManagementFactory.getPlatformMBeanServer(); // MBeanContainer mBeanContainer
= new MBeanContainer(mBeanServer); //
server.getContainer().addEventListener(mBeanContainer); //
mBeanContainer.start(); server.addHandler(bb);
try { System.out.println(">>> STARTING EMBEDDED JETTY SERVER, PRESS
[ENTER] TO STOP"); server.start(); System.in.read();
System.out.println(">>> STOPPING EMBEDDED JETTY SERVER");
server.stop(); server.join(); } catch (Exception e) {
e.printStackTrace(); System.exit(100); } }}
_
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
RE: Can I develop without recompiling/restarting after every change?
I have to thank Martijn for pointing out the Start.java file. I am trying hard
not to beat myself up for not using this sooner. I have not gone through the
works just yet to move my HTML files to another location. I've left them in
with the class files. So, for eclipse love in this situation, I added the HTML
files to the eclipse build so that anytime I save a file eclipse moves them to
the target folder. I changed the build output location to be
target/MY_APPLICATION/WEB-INF/classes and I added the same path to the runtime
configuration classpath. So far, I love it! Just as Martijn pointed out
earlier, run in debug mode and every time you edit/save a java file or html
file the changes are immediately picked up. SO much better than hot deploy for
laptop development. This will save me hours, and it has no impact on my current
maven project. Its just what I needed. THANK YOU.
If you don't want to use the quickstart, here is the Start.java source I use.
import org.mortbay.jetty.Connector;import org.mortbay.jetty.Server;import
org.mortbay.jetty.bio.SocketConnector;import
org.mortbay.jetty.webapp.WebAppContext;import
org.mortbay.jetty.webapp.WebInfConfiguration;import
org.mortbay.jetty.webapp.WebXmlConfiguration;
public class Start {
public static void main(String[] args) throws Exception {
Server server = new Server(); SocketConnector connector = new
SocketConnector(); // Set some timeout options to
make debugging easier. connector.setMaxIdleTime(1000 * 60 * 60);
connector.setSoLingerTime(-1); connector.setPort(8080);
server.setConnectors(new Connector[] { connector });
WebAppContext bb = new WebAppContext();
bb.setServer(server); bb.setContextPath("/");//
CHANGE ME - point to your project path
bb.setWar("target/YOUR_APP"); bb.setConfigurationClasses(new String[]
{ WebInfConfiguration.class.getName(), WebXmlConfiguration.class.getName() });
bb.setParentLoaderPriority(true); // START JMX SERVER
// MBeanServer mBeanServer =
ManagementFactory.getPlatformMBeanServer();// MBeanContainer
mBeanContainer = new MBeanContainer(mBeanServer); //
server.getContainer().addEventListener(mBeanContainer); //
mBeanContainer.start(); server.addHandler(bb);
try { System.out.println(">>> STARTING
EMBEDDED JETTY SERVER, PRESS [ENTER] TO STOP");
server.start(); System.in.read();
System.out.println(">>> STOPPING EMBEDDED JETTY SERVER");
server.stop(); server.join(); } catch (Exception e) {
e.printStackTrace();System.exit(100);
} }}
_
The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
Re: Can I develop without recompiling/restarting after every change?
Hi >Yes, I understand that. But you have to put the markup for each >component somewhere. If it's not on the classpath, then you will not be >able to package that component into a JAR for re-use. As I wrote, both methods co-exist, and you can put markup on the classpath and package it as jar while other markup is separate from the classpath. How otherwise would I be able to use Wicket components with my scheme? Please accept the good news that your "but" is not justified. >No, we disagree because I think that "doing nothing", i.e. keeping your >component markup on the classpath, *is* the best practice, that is, the >majority opinion on what makes the most sense for most people. Quoting "majority opinion" and "community consensus" is a very weak contribution to innovation, a sign that the speaker is running out of genuine ideas. In such context I would typically say that my views represent the other 100% of such perceived majority/consensus, just to make it absolutely clear what kind of Orwellian bsht this is. Page developers, especially those who work with markup, and that is the majority that Wicket is targeting (not component developers) need the markup in the context of their resolvable image, script and other resource files which is in the web directory. Otherwise they cannot view the markup in the browser. They don't care where these files are at runtime as long as they are not broken at design time which they currently are. You never seem to comment on this critical point. > >If you feel that the default approach isn't the best practice, then you >are saying that the Wicket designers made a mistake by making this the >default. I disagree strongly with that sentiment. You accept broken markup at design time and I don't accept it because I have solved the problem. I would not go as far as to say they made THAT mistake. As you know, they gave us the option. But the non-default option is broken because of the missing three lines of Java code, and whenever people try it, they become part of your perceived community consensus due to frustration. Like prisoners. >I think perhaps we mean different things by "deploy on save". When I say >"deploy" I mean it in the J2EE sense, where the container re-loads my >WAR package. In my case, this re-loads my Spring context and a few dozen >JPA entity beans, which takes up to 15 seconds on my relatively modern >laptop. There is no way rearranging my markup (or running it on a "fully >certified J2EE server") would turn this into milliseconds. True. "deploy on save" is not invented here. It is a term used in IDEs. The IDE decides what deployment method to use depending on file location etc.. That is one of two reasons why I would recommend to not store page markup in Java package directories. >Look, the only reason I took up this (now too long) thread is your use >of the words "best practice", which implies a broadly held consensus. >Now that you've included "as I see it" I'm happy to let it drop. Wrong. Best practice does not imply "broadly held consensus" at all. I am not using this as a buzzword as you are. If I invent a better mouse trap today that is more effective at delivering the outcome than any other technique, while the better mouse trap is not even available or known to everyone, then using it becomes best practice overnight. Regards Bernard - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
On Sun, Jun 06, 2010 at 08:54:18AM +1200, b...@actrix.gen.nz wrote: > If you study the effects of adding resource paths in Wicket then you > will find that both methods will co-exist, not negate each other as > you write. Yes, I understand that. But you have to put the markup for each component somewhere. If it's not on the classpath, then you will not be able to package that component into a JAR for re-use. > There are environments such as yours and other trivial environments > where nothing needs to be done at all. I'm curious as to why you think my environment is trivial. > That does not mean that doing > nothing is best practice. Best practice is something else. A best > approach in an individual case may be different from best practice, > and that is why you disagree. No, we disagree because I think that "doing nothing", i.e. keeping your component markup on the classpath, *is* the best practice, that is, the majority opinion on what makes the most sense for most people. If you feel that the default approach isn't the best practice, then you are saying that the Wicket designers made a mistake by making this the default. I disagree strongly with that sentiment. > Deploy on save would take only milliseconds (with my proposed path > structure applied) and the session would be preserved if you were > using GlassFish 3.0 and NetBeans, leading to a performance gain. You > may not need this functionality, but your setup seems to be slower > than what is achievable. I think perhaps we mean different things by "deploy on save". When I say "deploy" I mean it in the J2EE sense, where the container re-loads my WAR package. In my case, this re-loads my Spring context and a few dozen JPA entity beans, which takes up to 15 seconds on my relatively modern laptop. There is no way rearranging my markup (or running it on a "fully certified J2EE server") would turn this into milliseconds. > Yes I am moving markup around. And that (with an additional 3 lines of > framwork code) leads to a re-definition of best practice for Wicket > page development as I see it because of two gains: Look, the only reason I took up this (now too long) thread is your use of the words "best practice", which implies a broadly held consensus. Now that you've included "as I see it" I'm happy to let it drop. jk - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
Hi, >I don't >agree that it's the best approach in all environments, and I think your >advice negates one of the best features of Wicket, namely the ability to >package complete Wicket components (including their markup and other >resources) into JAR files for convenient re-use across applications. > Wrong. Let me repeat what I wrote in my previos article: "This would not break the ability of packaging markup of some components in the classpath because Wicket can handle that at the same time." If you study the effects of adding resource paths in Wicket then you will find that both methods will co-exist, not negate each other as you write. There are environments such as yours and other trivial environments where nothing needs to be done at all. That does not mean that doing nothing is best practice. Best practice is something else. A best approach in an individual case may be different from best practice, and that is why you disagree. >I think perhaps you're missing the point here. In my development >environment (Eclipse+Tomcat) I *don't* re-deploy on save. That would be >far too slow. But any markup changes I make (and a good portion of the >Java changes, too) are usually picked up by the time I Alt-Tab to my >browser and refresh the page. With my proposed method, your cycle would not be affected at all. You would still have all your benefits. My method is inclusive and general wheteher you chose to deploy on save or not. Deploy on save would take only milliseconds (with my proposed path structure applied) and the session would be preserved if you were using GlassFish 3.0 and NetBeans, leading to a performance gain. You may not need this functionality, but your setup seems to be slower than what is achievable. >I think that was Martijn's point: if you're doing re-deploy on save in >your development environment (as the OP implied he was) then you're >doing it wrong. No amount of moving markup around is goint to change >this. I am sorry your statement is wrong. You are assuming that I am using Tomcat. For fully certified J2EE servers, and I wrote that my general approach includes these, IDE instrumentation is not necessarily the same as for Tomcat. Yes I am moving markup around. And that (with an additional 3 lines of framwork code) leads to a re-definition of best practice for Wicket page development as I see it because of two gains: - Markup re-factoring within the scope of the web directory becomes possible because links are no longer broken - Application server IDE instrumentation can make better deployment choices for deploy on save optimisation I am not claiming that you will personally benefit from this. You seem to be happy enough with your setup. Regards, Bernard - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
On Sat, Jun 05, 2010 at 10:13:42AM +1200, b...@actrix.gen.nz wrote: > Hi, > > My suggestions were meant to be general, and with "best" I actually > meant in all environments including certified J2EE servers. I'm aware that's what you meant. That's why I challenged it. I don't agree that it's the best approach in all environments, and I think your advice negates one of the best features of Wicket, namely the ability to package complete Wicket components (including their markup and other resources) into JAR files for convenient re-use across applications. Since the OP is a self-confessed "n00b" I wanted to make sure he didn't miss out on this important point. > That is because deployment environments may or may not make decisions > on which way to deploy different file types, or depending on > directories they are loaded from. Files in the web directory are quite > obviously candidates for the fastest deployment method. > > If the environment thinks that HTML files need to be deployed in the > same way as Java files, which is quite likely if they are stored in > Java packages, then deploy-on-save setups may slow down the > development process of complex applications due to heavy CPU use. I think perhaps you're missing the point here. In my development environment (Eclipse+Tomcat) I *don't* re-deploy on save. That would be far too slow. But any markup changes I make (and a good portion of the Java changes, too) are usually picked up by the time I Alt-Tab to my browser and refresh the page. I think that was Martijn's point: if you're doing re-deploy on save in your development environment (as the OP implied he was) then you're doing it wrong. No amount of moving markup around is goint to change this. jk - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
;> background on how to take this one step further. >> >> >> >> Additionally, with GlassFish V3, you get session preservation on hot >> >> deployment of Java classes. >> >> >> >> You can enable "deploy on save" for convenience. >> >> >> >> If that is not fast enough, you can run your app in debug mode and hot >> >> swap classes after save while you are debugging it. >> >> >> >> All this comes with the NetBeans IDE. You really don't have to worry >> >> about this stuff anymore. >> >> >> >> Regards >> >> >> >> Bernard >> >> >> >> >> >> >> >> On Sat, 29 May 2010 16:12:46 +0100, you wrote: >> >> >> >>>have you tried JRebel? ?I've not used it myself, but there was an >> >>>interview on JavaPosse recently, sounds like it'd be an ideal fit for >> >>>any Wicket developer. >> >>> >> >>>Dan >> >>> >> >>>On 22/07/28164 20:59, David Chang wrote: >> >>>> I am using Tomcat, any tips about how to develop out >> >>>> recompiling/restarting after every change? >> >>>> >> >>>> Best. >> >>>> >> >>>> --- On Fri, 5/21/10, Jeremy Thomerson ?wrote: >> >>>> >> >>>> >> >>>>> From: Jeremy Thomerson >> >>>>> Subject: Re: Can I develop without recompiling/restarting after every >> >>>>> change? >> >>>>> To: users@wicket.apache.org >> >>>>> Date: Friday, May 21, 2010, 12:17 PM >> >>>>> the easiest way to do this is to use >> >>>>> the Start class (Start.java) from the >> >>>>> quickstart to run an embedded jetty instance in your >> >>>>> IDE. ?then, if you run >> >>>>> it in debug mode, it will hotswap any possible changes (and >> >>>>> tell you if you >> >>>>> must restart if it's an incompatible change) >> >>>>> >> >>>>> -- >> >>>>> Jeremy Thomerson >> >>>>> http://www.wickettraining.com >> >>>>> >> >>>>> >> >>>>> >> >>>>> On Fri, May 21, 2010 at 10:53 AM, ekallevig >> >>>>> wrote: >> >>>>> >> >>>>> >> >>>>>> I'm a front-end developer trying to learn Java (total >> >>>>>> >> >>>>> n00b) and working on >> >>>>> >> >>>>>> a >> >>>>>> wicket application at work. ?The whole process >> >>>>>> >> >>>>> feels very slow primarily >> >>>>> >> >>>>>> because I have to recompile and restart JBoss every >> >>>>>> >> >>>>> time I make a change. >> >>>>> >> >>>>>> So I'm wondering what the best way is to avoid having >> >>>>>> >> >>>>> to do this when >> >>>>> >> >>>>>> editing .java/.js/.css/.html files during development? >> >>>>>> >> >>>>> I'd like to just >> >>>>> >> >>>>>> make >> >>>>>> changes and then refresh the browser to test -- is >> >>>>>> >> >>>>> this possible? >> >>>>> >> >>>>>> I've seen in the FAQ that you can change the >> >>>>>> >> >>>>> application settings to >> >>>>> >> >>>>>> auto-reload markup .html files -- where would I insert >> >>>>>> >> >>>>> this setting >> >>>>> >> >>>>>> (remember I'm a total n00b). >> >>>>>> >> >>>>>> As to .css/.js/.java files -- do I need jRebel or >> >>>>>> >> >>>>> something like that to >> >>>>> >> >>>>>> get >> >>>>>> these files to reload automatically? >> >>>>>> >> >>>>>> Thanks for helping out a super-beginner :) >> >>>>>> -- >> >>>>>> View this message in context: >> >>>>>> http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2226360.html >> >>>>>> Sent from the Wicket - User 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 >> >>>>>> >> >>>>>> >> >>>>>> >> >>>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >> >> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> > >- >To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
On Thu, Jun 3, 2010 at 1:57 AM, wrote:
> Martijn,
>
> You are making a *lot* of assumptions.
>
> Not everybody uses Eclipse.
>
> Nobody in this thread would consider restarts acceptable, still we are
> using this subject.
>
> HTML files location has to do with performance in the developing
> process depending on how the IDE handles the files.
>
> Please advise how to configure the NetBeans IDE to redeploy a HTML
> file in a Java package in a J2EE app server with the same speed as
> HTML files in the web directory (milliseconds not seconds).
launch the Start class supplied by quickstart and archetype to launch
the application from netbeans in debug mode. this will get you jvm
hotswapping for changes you make to java code.
for resources add lines like these to your application.init()
getResourceSettings().addResourceFolder("src/main/java");
getResourceSettings().addResourceFolder("src/main/resources");
the lines above are for a project using maven layout, if you use a
different layout adjust the paths.
this will get you reloading of markup and property files.
to adjust the frequency of reloading set it in resource settings,
although i doubt it takes you less then a second to switch from your
ide to the browser and hit refresh after you make a change.
-igor
>
>
> Thanks
>
> Bernard
>
>
>
>
> On Sun, 30 May 2010 15:23:09 +0200, you wrote:
>
>>Huh?
>>
>>Storing the HTML in the packages has *nothing* to do with requiring
>>restarts. Only wrongly configured IDEs may cause that.
>>
>>If your HTML doesn't get reloaded when you change it, then you should
>>run Wicket in DEVELOPMENT mode. Also make sure you've configured
>>Eclipse to copy all resources (not just .properties files)
>>
>>The Wicket Quickstart project and using Maven to generate your eclipse
>>project files (mvn eclipse:eclipse) will configure everything
>>correctly.
>>
>>Martijn
>>
>>On Sat, May 29, 2010 at 11:18 PM, wrote:
>>> Hi,
>>>
>>> For best performance of redeploys in Wicket, consider storing HTML not
>>> in the Java package structure but in the web directory. So if your IDE
>>> and app server allow for hot deployment, then HTML changes deploy much
>>> faster, ie instantly. In your application init(), you add one
>>> statement
>>>
>>> getResourceSettings().addResourceFolder("wicket");
>>>
>>> where "wicket" matches the url-pattern in your filter-mapping in
>>> web.xml.
>>>
>>> PLease see https://issues.apache.org/jira/browse/WICKET-2881 for some
>>> background on how to take this one step further.
>>>
>>> Additionally, with GlassFish V3, you get session preservation on hot
>>> deployment of Java classes.
>>>
>>> You can enable "deploy on save" for convenience.
>>>
>>> If that is not fast enough, you can run your app in debug mode and hot
>>> swap classes after save while you are debugging it.
>>>
>>> All this comes with the NetBeans IDE. You really don't have to worry
>>> about this stuff anymore.
>>>
>>> Regards
>>>
>>> Bernard
>>>
>>>
>>>
>>> On Sat, 29 May 2010 16:12:46 +0100, you wrote:
>>>
>>>>have you tried JRebel? I've not used it myself, but there was an
>>>>interview on JavaPosse recently, sounds like it'd be an ideal fit for
>>>>any Wicket developer.
>>>>
>>>>Dan
>>>>
>>>>On 22/07/28164 20:59, David Chang wrote:
>>>>> I am using Tomcat, any tips about how to develop out
>>>>> recompiling/restarting after every change?
>>>>>
>>>>> Best.
>>>>>
>>>>> --- On Fri, 5/21/10, Jeremy Thomerson wrote:
>>>>>
>>>>>
>>>>>> From: Jeremy Thomerson
>>>>>> Subject: Re: Can I develop without recompiling/restarting after every
>>>>>> change?
>>>>>> To: users@wicket.apache.org
>>>>>> Date: Friday, May 21, 2010, 12:17 PM
>>>>>> the easiest way to do this is to use
>>>>>> the Start class (Start.java) from the
>>>>>> quickstart to run an embedded jetty instance in your
>>>>>> IDE. then, if you run
>>>>>> it in debug mode, it will hotswap any possible changes (and
>>>>>> tell you if you
>>>>>> must restart if it's an incompatible change)
>>>
Re: Can I develop without recompiling/restarting after every change?
Hrm, perhaps you should have qualified your advice: "If you're using
NetBeans, then for best performance..."
Also, the packaging of markup on the classpath allows you to create
re-usable JARs of components and IMHO is one of the best features of
Wicket. So perhaps the qualification should really be, "If you're using
NetBeans, and you're not planning on packaging your Wicket components in
a re-usable JAR, then for best performance..."
The way your original post is phrased makes it sound like a best
practice, and it implies the Wicket default to fetch markup from the
classpath is inferior. I don't think this is a consensus among the
community.
jk
On Thu, Jun 03, 2010 at 08:57:43PM +1200, b...@actrix.gen.nz wrote:
> Martijn,
>
> You are making a *lot* of assumptions.
>
> Not everybody uses Eclipse.
>
> Nobody in this thread would consider restarts acceptable, still we are
> using this subject.
>
> HTML files location has to do with performance in the developing
> process depending on how the IDE handles the files.
>
> Please advise how to configure the NetBeans IDE to redeploy a HTML
> file in a Java package in a J2EE app server with the same speed as
> HTML files in the web directory (milliseconds not seconds).
>
>
> Thanks
>
> Bernard
>
>
>
>
> On Sun, 30 May 2010 15:23:09 +0200, you wrote:
>
> >Huh?
> >
> >Storing the HTML in the packages has *nothing* to do with requiring
> >restarts. Only wrongly configured IDEs may cause that.
> >
> >If your HTML doesn't get reloaded when you change it, then you should
> >run Wicket in DEVELOPMENT mode. Also make sure you've configured
> >Eclipse to copy all resources (not just .properties files)
> >
> >The Wicket Quickstart project and using Maven to generate your eclipse
> >project files (mvn eclipse:eclipse) will configure everything
> >correctly.
> >
> >Martijn
> >
> >On Sat, May 29, 2010 at 11:18 PM, wrote:
> >> Hi,
> >>
> >> For best performance of redeploys in Wicket, consider storing HTML not
> >> in the Java package structure but in the web directory. So if your IDE
> >> and app server allow for hot deployment, then HTML changes deploy much
> >> faster, ie instantly. In your application init(), you add one
> >> statement
> >>
> >> getResourceSettings().addResourceFolder("wicket");
> >>
> >> where "wicket" matches the url-pattern in your filter-mapping in
> >> web.xml.
> >>
> >> PLease see https://issues.apache.org/jira/browse/WICKET-2881 for some
> >> background on how to take this one step further.
> >>
> >> Additionally, with GlassFish V3, you get session preservation on hot
> >> deployment of Java classes.
> >>
> >> You can enable "deploy on save" for convenience.
> >>
> >> If that is not fast enough, you can run your app in debug mode and hot
> >> swap classes after save while you are debugging it.
> >>
> >> All this comes with the NetBeans IDE. You really don't have to worry
> >> about this stuff anymore.
> >>
> >> Regards
> >>
> >> Bernard
> >>
> >>
> >>
> >> On Sat, 29 May 2010 16:12:46 +0100, you wrote:
> >>
> >>>have you tried JRebel? ?I've not used it myself, but there was an
> >>>interview on JavaPosse recently, sounds like it'd be an ideal fit for
> >>>any Wicket developer.
> >>>
> >>>Dan
> >>>
> >>>On 22/07/28164 20:59, David Chang wrote:
> >>>> I am using Tomcat, any tips about how to develop out
> >>>> recompiling/restarting after every change?
> >>>>
> >>>> Best.
> >>>>
> >>>> --- On Fri, 5/21/10, Jeremy Thomerson ?wrote:
> >>>>
> >>>>
> >>>>> From: Jeremy Thomerson
> >>>>> Subject: Re: Can I develop without recompiling/restarting after every
> >>>>> change?
> >>>>> To: users@wicket.apache.org
> >>>>> Date: Friday, May 21, 2010, 12:17 PM
> >>>>> the easiest way to do this is to use
> >>>>> the Start class (Start.java) from the
> >>>>> quickstart to run an embedded jetty instance in your
> >>>>> IDE. ?then, if you run
> >>>>> it in debug mode, it will hotswap any possible changes (and
> >>>>> tell you if you
> >>>>> must restart if it&
Re: Can I develop without recompiling/restarting after every change?
Martijn,
You are making a *lot* of assumptions.
Not everybody uses Eclipse.
Nobody in this thread would consider restarts acceptable, still we are
using this subject.
HTML files location has to do with performance in the developing
process depending on how the IDE handles the files.
Please advise how to configure the NetBeans IDE to redeploy a HTML
file in a Java package in a J2EE app server with the same speed as
HTML files in the web directory (milliseconds not seconds).
Thanks
Bernard
On Sun, 30 May 2010 15:23:09 +0200, you wrote:
>Huh?
>
>Storing the HTML in the packages has *nothing* to do with requiring
>restarts. Only wrongly configured IDEs may cause that.
>
>If your HTML doesn't get reloaded when you change it, then you should
>run Wicket in DEVELOPMENT mode. Also make sure you've configured
>Eclipse to copy all resources (not just .properties files)
>
>The Wicket Quickstart project and using Maven to generate your eclipse
>project files (mvn eclipse:eclipse) will configure everything
>correctly.
>
>Martijn
>
>On Sat, May 29, 2010 at 11:18 PM, wrote:
>> Hi,
>>
>> For best performance of redeploys in Wicket, consider storing HTML not
>> in the Java package structure but in the web directory. So if your IDE
>> and app server allow for hot deployment, then HTML changes deploy much
>> faster, ie instantly. In your application init(), you add one
>> statement
>>
>> getResourceSettings().addResourceFolder("wicket");
>>
>> where "wicket" matches the url-pattern in your filter-mapping in
>> web.xml.
>>
>> PLease see https://issues.apache.org/jira/browse/WICKET-2881 for some
>> background on how to take this one step further.
>>
>> Additionally, with GlassFish V3, you get session preservation on hot
>> deployment of Java classes.
>>
>> You can enable "deploy on save" for convenience.
>>
>> If that is not fast enough, you can run your app in debug mode and hot
>> swap classes after save while you are debugging it.
>>
>> All this comes with the NetBeans IDE. You really don't have to worry
>> about this stuff anymore.
>>
>> Regards
>>
>> Bernard
>>
>>
>>
>> On Sat, 29 May 2010 16:12:46 +0100, you wrote:
>>
>>>have you tried JRebel? I've not used it myself, but there was an
>>>interview on JavaPosse recently, sounds like it'd be an ideal fit for
>>>any Wicket developer.
>>>
>>>Dan
>>>
>>>On 22/07/28164 20:59, David Chang wrote:
>>>> I am using Tomcat, any tips about how to develop out
>>>> recompiling/restarting after every change?
>>>>
>>>> Best.
>>>>
>>>> --- On Fri, 5/21/10, Jeremy Thomerson wrote:
>>>>
>>>>
>>>>> From: Jeremy Thomerson
>>>>> Subject: Re: Can I develop without recompiling/restarting after every
>>>>> change?
>>>>> To: users@wicket.apache.org
>>>>> Date: Friday, May 21, 2010, 12:17 PM
>>>>> the easiest way to do this is to use
>>>>> the Start class (Start.java) from the
>>>>> quickstart to run an embedded jetty instance in your
>>>>> IDE. then, if you run
>>>>> it in debug mode, it will hotswap any possible changes (and
>>>>> tell you if you
>>>>> must restart if it's an incompatible change)
>>>>>
>>>>> --
>>>>> Jeremy Thomerson
>>>>> http://www.wickettraining.com
>>>>>
>>>>>
>>>>>
>>>>> On Fri, May 21, 2010 at 10:53 AM, ekallevig
>>>>> wrote:
>>>>>
>>>>>
>>>>>> I'm a front-end developer trying to learn Java (total
>>>>>>
>>>>> n00b) and working on
>>>>>
>>>>>> a
>>>>>> wicket application at work. The whole process
>>>>>>
>>>>> feels very slow primarily
>>>>>
>>>>>> because I have to recompile and restart JBoss every
>>>>>>
>>>>> time I make a change.
>>>>>
>>>>>> So I'm wondering what the best way is to avoid having
>>>>>>
>>>>> to do this when
>>>>>
>>>>>> editing .java/.js/.css/.html files during development?
>>>>>>
>>>>> I'd like to just
>>>>>
>>>>>> make
>>>>>> c
Re: Can I develop without recompiling/restarting after every change?
On Sun, May 30, 2010 at 5:22 PM, Jeremy Thomerson wrote: > I've not used jRebel, but I commonly run my applications in debug mode in > Eclipse and do not have to restart the server - even with code changes. The > exception is changing a method signature of classes that are already loaded > - but adding methods, classes, or changing 90% of code does not require a > restart. So, what does jRebel add? Does it eliminate restarts even in > these cases where the normal debug mode requires one? > JRebel allows more types of class changes before you need a restart. You can add/remove methods with JRebel, no problem. There are still some situations where you can't reload, but it definitely cuts down on restarts. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
Indeed JRebel reloads class structure changes as well. A very time-saving in combination with jetty. The sysdeo plugin that was recommended earlier is very outdated, hasn't been updated in 3 years. On 05/31/2010 06:01 PM, John Krasnay wrote: This is how I work too. It uses the "hot swap" feature of the JVM. It works if you only change method bodies, but if you make changes to the class structure (fields, method signatures, etc.) you have to restart the VM. Apparently jRebel can reload even these kinds of changes. I'm happy with hot swap, but then again my app only takes ~14 seconds to restart. jk On Sun, May 30, 2010 at 04:22:29PM -0500, Jeremy Thomerson wrote: On Sun, May 30, 2010 at 12:05 PM, Alex Objeleanwrote: jRebel allows you to change the java code without restarting the server. I've not used jRebel, but I commonly run my applications in debug mode in Eclipse and do not have to restart the server - even with code changes. The exception is changing a method signature of classes that are already loaded - but adding methods, classes, or changing 90% of code does not require a restart. So, what does jRebel add? Does it eliminate restarts even in these cases where the normal debug mode requires one? -- Jeremy Thomerson http://www.wickettraining.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
This is how I work too. It uses the "hot swap" feature of the JVM. It works if you only change method bodies, but if you make changes to the class structure (fields, method signatures, etc.) you have to restart the VM. Apparently jRebel can reload even these kinds of changes. I'm happy with hot swap, but then again my app only takes ~14 seconds to restart. jk On Sun, May 30, 2010 at 04:22:29PM -0500, Jeremy Thomerson wrote: > On Sun, May 30, 2010 at 12:05 PM, Alex Objelean > wrote: > > > > > jRebel allows you to change the java code without restarting the server. > > > > I've not used jRebel, but I commonly run my applications in debug mode in > Eclipse and do not have to restart the server - even with code changes. The > exception is changing a method signature of classes that are already loaded > - but adding methods, classes, or changing 90% of code does not require a > restart. So, what does jRebel add? Does it eliminate restarts even in > these cases where the normal debug mode requires one? > > -- > Jeremy Thomerson > http://www.wickettraining.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
This is really a great discussion thread and turned up lot of good stuff. Love this forum! Cheers! --- On Sun, 5/30/10, Jason Lea wrote: > From: Jason Lea > Subject: Re: Can I develop without recompiling/restarting after every change? > To: users@wicket.apache.org > Date: Sunday, May 30, 2010, 3:57 PM > I use DWP in Eclipse... > > In the server view, you have your Tomcat server > listed that you can start/stop etc. When you double > click it opens up the settings for runtime environment and > other options. One option is something like 'serve > module without publishing' - that one means it basically > serves it from the target directory - and any changes to > .html/.js/.css/.xml/.properties etc are available > immediately without republishing. > > Doesn't deal with java changes though... that still > requires republish - but I haven't experimented with other > hot code replacement options and DWP. > > > On 31/05/10 6:36 AM, Ray Weidner wrote: > > Nobody seems to have mentioned it, but I have been > developing with Eclipse's > > Dynamic Web Projects, and it has greatly shortened my > development cycle from > > when I was loading the project into Tomcat through the > manager web > > interface. Basically, a DWP is able to run the > server itself, and it > > automatically republishes a new build and restarts the > server in the > > background. Even when I have to start it myself, > it is fast, and I don't > > have to leave the Eclipse interface. More > importantly, I am able to run my > > code in debug, allowing me to set breakpoints > etc. I don't have enough > > experience with the other solutions to compare it, but > it sure beats manual > > deployment and restarting the server every time you > want to try a new build. > > > > > > DWP is built into Eclipse, not requiring any > additional plug-ins. You just > > create the project as a DWP and take it from > there. I ported a different > > project's web code into the DWP simply by copying over > the relevant code, > > and making changes needed to build. The > directory layout corresponds > > roughly to the internal structure of the resulting WAR > file, so it's pretty > > easy to figure out where different files should > go. When you want to create > > a WAR file for use outside the project, you just > export the project to a > > WAR. Debugging and building can all be performed > using Eclipses standard > > menu options. The only trick is that you have to > create a server for your > > DWP, and you want to point that instance to an actual > installed instance of > > Tomcat or JBoss. This presents you with new > artifact on the Package View, > > and you might want to open up the Server View window > for control over it > > (start, stop and publish are the main things to do > here). That's all there > > is to it. > > > > > > On Fri, May 21, 2010 at 11:53 AM, ekallevig > wrote: > > > > > >> I'm a front-end developer trying to learn Java > (total n00b) and working on > >> a > >> wicket application at work. The whole > process feels very slow primarily > >> because I have to recompile and restart JBoss > every time I make a change. > >> So I'm wondering what the best way is to avoid > having to do this when > >> editing .java/.js/.css/.html files during > development? I'd like to just > >> make > >> changes and then refresh the browser to test -- is > this possible? > >> > >> > > > > -- Jason Lea > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
On Sun, May 30, 2010 at 12:05 PM, Alex Objelean wrote: > > jRebel allows you to change the java code without restarting the server. > I've not used jRebel, but I commonly run my applications in debug mode in Eclipse and do not have to restart the server - even with code changes. The exception is changing a method signature of classes that are already loaded - but adding methods, classes, or changing 90% of code does not require a restart. So, what does jRebel add? Does it eliminate restarts even in these cases where the normal debug mode requires one? -- Jeremy Thomerson http://www.wickettraining.com
Re: Can I develop without recompiling/restarting after every change?
I use DWP in Eclipse... In the server view, you have your Tomcat server listed that you can start/stop etc. When you double click it opens up the settings for runtime environment and other options. One option is something like 'serve module without publishing' - that one means it basically serves it from the target directory - and any changes to .html/.js/.css/.xml/.properties etc are available immediately without republishing. Doesn't deal with java changes though... that still requires republish - but I haven't experimented with other hot code replacement options and DWP. On 31/05/10 6:36 AM, Ray Weidner wrote: Nobody seems to have mentioned it, but I have been developing with Eclipse's Dynamic Web Projects, and it has greatly shortened my development cycle from when I was loading the project into Tomcat through the manager web interface. Basically, a DWP is able to run the server itself, and it automatically republishes a new build and restarts the server in the background. Even when I have to start it myself, it is fast, and I don't have to leave the Eclipse interface. More importantly, I am able to run my code in debug, allowing me to set breakpoints etc. I don't have enough experience with the other solutions to compare it, but it sure beats manual deployment and restarting the server every time you want to try a new build. DWP is built into Eclipse, not requiring any additional plug-ins. You just create the project as a DWP and take it from there. I ported a different project's web code into the DWP simply by copying over the relevant code, and making changes needed to build. The directory layout corresponds roughly to the internal structure of the resulting WAR file, so it's pretty easy to figure out where different files should go. When you want to create a WAR file for use outside the project, you just export the project to a WAR. Debugging and building can all be performed using Eclipses standard menu options. The only trick is that you have to create a server for your DWP, and you want to point that instance to an actual installed instance of Tomcat or JBoss. This presents you with new artifact on the Package View, and you might want to open up the Server View window for control over it (start, stop and publish are the main things to do here). That's all there is to it. On Fri, May 21, 2010 at 11:53 AM, ekallevig wrote: I'm a front-end developer trying to learn Java (total n00b) and working on a wicket application at work. The whole process feels very slow primarily because I have to recompile and restart JBoss every time I make a change. So I'm wondering what the best way is to avoid having to do this when editing .java/.js/.css/.html files during development? I'd like to just make changes and then refresh the browser to test -- is this possible? -- Jason Lea - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
Nobody seems to have mentioned it, but I have been developing with Eclipse's Dynamic Web Projects, and it has greatly shortened my development cycle from when I was loading the project into Tomcat through the manager web interface. Basically, a DWP is able to run the server itself, and it automatically republishes a new build and restarts the server in the background. Even when I have to start it myself, it is fast, and I don't have to leave the Eclipse interface. More importantly, I am able to run my code in debug, allowing me to set breakpoints etc. I don't have enough experience with the other solutions to compare it, but it sure beats manual deployment and restarting the server every time you want to try a new build. DWP is built into Eclipse, not requiring any additional plug-ins. You just create the project as a DWP and take it from there. I ported a different project's web code into the DWP simply by copying over the relevant code, and making changes needed to build. The directory layout corresponds roughly to the internal structure of the resulting WAR file, so it's pretty easy to figure out where different files should go. When you want to create a WAR file for use outside the project, you just export the project to a WAR. Debugging and building can all be performed using Eclipses standard menu options. The only trick is that you have to create a server for your DWP, and you want to point that instance to an actual installed instance of Tomcat or JBoss. This presents you with new artifact on the Package View, and you might want to open up the Server View window for control over it (start, stop and publish are the main things to do here). That's all there is to it. On Fri, May 21, 2010 at 11:53 AM, ekallevig wrote: > > I'm a front-end developer trying to learn Java (total n00b) and working on > a > wicket application at work. The whole process feels very slow primarily > because I have to recompile and restart JBoss every time I make a change. > So I'm wondering what the best way is to avoid having to do this when > editing .java/.js/.css/.html files during development? I'd like to just > make > changes and then refresh the browser to test -- is this possible? >
Re: Can I develop without recompiling/restarting after every change?
jRebel allows you to change the java code without restarting the server. Alex -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2236403.html Sent from the Wicket - User 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
Re: Can I develop without recompiling/restarting after every change?
Why do you need jRebel. I run jetty from inside eclipse and I have no need for jRebel. Also, it makes debugging much simpler if jettty is running inside the eclipse jvm. D/ On May 30, 2010, at 5:27 AM, Alex Objelean wrote: > > If you are using eclipse IDE for your development, I find the best tools the > following: > 1) Run-jetty-run plugin: http://code.google.com/p/run-jetty-run/ > 2) jRebel > > With these two, you require absolutely no restart, no matter what you have > changed in your wicket application (and not only wicket). > > Alex > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2236201.html > Sent from the Wicket - User 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 > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
I have similar frustrations with WAS 7 in RAD 7.5. WAS 6 supported hot code replacement while debugging and life was good, but WAS 7 doesn't seem to. The hot code checkbox is checked, but seems ignored. Any RAD users out there have this problem and/or know how to fix it? Brian Mulholland On Sun, May 30, 2010 at 9:30 AM, David Chang wrote: > Alex, > >> 1) Run-jetty-run plugin: http://code.google.com/p/run-jetty-run/ > > You are right. I googled it out yesterday and tested it. It works perfect. > > Thanks for chiming! > > Best, > David > > > --- On Sun, 5/30/10, Alex Objelean wrote: > >> From: Alex Objelean >> Subject: Re: Can I develop without recompiling/restarting after every change? >> To: users@wicket.apache.org >> Date: Sunday, May 30, 2010, 6:27 AM >> >> If you are using eclipse IDE for your development, I find >> the best tools the >> following: >> 1) Run-jetty-run plugin: http://code.google.com/p/run-jetty-run/ >> 2) jRebel >> >> With these two, you require absolutely no restart, no >> matter what you have >> changed in your wicket application (and not only wicket). >> >> Alex >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2236201.html >> Sent from the Wicket - User 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 >> >> > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
Alex, > 1) Run-jetty-run plugin: http://code.google.com/p/run-jetty-run/ You are right. I googled it out yesterday and tested it. It works perfect. Thanks for chiming! Best, David --- On Sun, 5/30/10, Alex Objelean wrote: > From: Alex Objelean > Subject: Re: Can I develop without recompiling/restarting after every change? > To: users@wicket.apache.org > Date: Sunday, May 30, 2010, 6:27 AM > > If you are using eclipse IDE for your development, I find > the best tools the > following: > 1) Run-jetty-run plugin: http://code.google.com/p/run-jetty-run/ > 2) jRebel > > With these two, you require absolutely no restart, no > matter what you have > changed in your wicket application (and not only wicket). > > Alex > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2236201.html > Sent from the Wicket - User 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 > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
Huh?
Storing the HTML in the packages has *nothing* to do with requiring
restarts. Only wrongly configured IDEs may cause that.
If your HTML doesn't get reloaded when you change it, then you should
run Wicket in DEVELOPMENT mode. Also make sure you've configured
Eclipse to copy all resources (not just .properties files)
The Wicket Quickstart project and using Maven to generate your eclipse
project files (mvn eclipse:eclipse) will configure everything
correctly.
Martijn
On Sat, May 29, 2010 at 11:18 PM, wrote:
> Hi,
>
> For best performance of redeploys in Wicket, consider storing HTML not
> in the Java package structure but in the web directory. So if your IDE
> and app server allow for hot deployment, then HTML changes deploy much
> faster, ie instantly. In your application init(), you add one
> statement
>
> getResourceSettings().addResourceFolder("wicket");
>
> where "wicket" matches the url-pattern in your filter-mapping in
> web.xml.
>
> PLease see https://issues.apache.org/jira/browse/WICKET-2881 for some
> background on how to take this one step further.
>
> Additionally, with GlassFish V3, you get session preservation on hot
> deployment of Java classes.
>
> You can enable "deploy on save" for convenience.
>
> If that is not fast enough, you can run your app in debug mode and hot
> swap classes after save while you are debugging it.
>
> All this comes with the NetBeans IDE. You really don't have to worry
> about this stuff anymore.
>
> Regards
>
> Bernard
>
>
>
> On Sat, 29 May 2010 16:12:46 +0100, you wrote:
>
>>have you tried JRebel? I've not used it myself, but there was an
>>interview on JavaPosse recently, sounds like it'd be an ideal fit for
>>any Wicket developer.
>>
>>Dan
>>
>>On 22/07/28164 20:59, David Chang wrote:
>>> I am using Tomcat, any tips about how to develop out recompiling/restarting
>>> after every change?
>>>
>>> Best.
>>>
>>> --- On Fri, 5/21/10, Jeremy Thomerson wrote:
>>>
>>>
>>>> From: Jeremy Thomerson
>>>> Subject: Re: Can I develop without recompiling/restarting after every
>>>> change?
>>>> To: users@wicket.apache.org
>>>> Date: Friday, May 21, 2010, 12:17 PM
>>>> the easiest way to do this is to use
>>>> the Start class (Start.java) from the
>>>> quickstart to run an embedded jetty instance in your
>>>> IDE. then, if you run
>>>> it in debug mode, it will hotswap any possible changes (and
>>>> tell you if you
>>>> must restart if it's an incompatible change)
>>>>
>>>> --
>>>> Jeremy Thomerson
>>>> http://www.wickettraining.com
>>>>
>>>>
>>>>
>>>> On Fri, May 21, 2010 at 10:53 AM, ekallevig
>>>> wrote:
>>>>
>>>>
>>>>> I'm a front-end developer trying to learn Java (total
>>>>>
>>>> n00b) and working on
>>>>
>>>>> a
>>>>> wicket application at work. The whole process
>>>>>
>>>> feels very slow primarily
>>>>
>>>>> because I have to recompile and restart JBoss every
>>>>>
>>>> time I make a change.
>>>>
>>>>> So I'm wondering what the best way is to avoid having
>>>>>
>>>> to do this when
>>>>
>>>>> editing .java/.js/.css/.html files during development?
>>>>>
>>>> I'd like to just
>>>>
>>>>> make
>>>>> changes and then refresh the browser to test -- is
>>>>>
>>>> this possible?
>>>>
>>>>> I've seen in the FAQ that you can change the
>>>>>
>>>> application settings to
>>>>
>>>>> auto-reload markup .html files -- where would I insert
>>>>>
>>>> this setting
>>>>
>>>>> (remember I'm a total n00b).
>>>>>
>>>>> As to .css/.js/.java files -- do I need jRebel or
>>>>>
>>>> something like that to
>>>>
>>>>> get
>>>>> these files to reload automatically?
>>>>>
>>>>> Thanks for helping out a super-beginner :)
>>>>> --
>>>>> View this message in context:
>>>>> http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2226360.html
>>>>> Sent from the Wicket - User 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
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
If you are using eclipse IDE for your development, I find the best tools the following: 1) Run-jetty-run plugin: http://code.google.com/p/run-jetty-run/ 2) jRebel With these two, you require absolutely no restart, no matter what you have changed in your wicket application (and not only wicket). Alex -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2236201.html Sent from the Wicket - User 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
Re: Can I develop without recompiling/restarting after every change?
Hi,
For best performance of redeploys in Wicket, consider storing HTML not
in the Java package structure but in the web directory. So if your IDE
and app server allow for hot deployment, then HTML changes deploy much
faster, ie instantly. In your application init(), you add one
statement
getResourceSettings().addResourceFolder("wicket");
where "wicket" matches the url-pattern in your filter-mapping in
web.xml.
PLease see https://issues.apache.org/jira/browse/WICKET-2881 for some
background on how to take this one step further.
Additionally, with GlassFish V3, you get session preservation on hot
deployment of Java classes.
You can enable "deploy on save" for convenience.
If that is not fast enough, you can run your app in debug mode and hot
swap classes after save while you are debugging it.
All this comes with the NetBeans IDE. You really don't have to worry
about this stuff anymore.
Regards
Bernard
On Sat, 29 May 2010 16:12:46 +0100, you wrote:
>have you tried JRebel? I've not used it myself, but there was an
>interview on JavaPosse recently, sounds like it'd be an ideal fit for
>any Wicket developer.
>
>Dan
>
>On 22/07/28164 20:59, David Chang wrote:
>> I am using Tomcat, any tips about how to develop out recompiling/restarting
>> after every change?
>>
>> Best.
>>
>> --- On Fri, 5/21/10, Jeremy Thomerson wrote:
>>
>>
>>> From: Jeremy Thomerson
>>> Subject: Re: Can I develop without recompiling/restarting after every
>>> change?
>>> To: users@wicket.apache.org
>>> Date: Friday, May 21, 2010, 12:17 PM
>>> the easiest way to do this is to use
>>> the Start class (Start.java) from the
>>> quickstart to run an embedded jetty instance in your
>>> IDE. then, if you run
>>> it in debug mode, it will hotswap any possible changes (and
>>> tell you if you
>>> must restart if it's an incompatible change)
>>>
>>> --
>>> Jeremy Thomerson
>>> http://www.wickettraining.com
>>>
>>>
>>>
>>> On Fri, May 21, 2010 at 10:53 AM, ekallevig
>>> wrote:
>>>
>>>
>>>> I'm a front-end developer trying to learn Java (total
>>>>
>>> n00b) and working on
>>>
>>>> a
>>>> wicket application at work. The whole process
>>>>
>>> feels very slow primarily
>>>
>>>> because I have to recompile and restart JBoss every
>>>>
>>> time I make a change.
>>>
>>>> So I'm wondering what the best way is to avoid having
>>>>
>>> to do this when
>>>
>>>> editing .java/.js/.css/.html files during development?
>>>>
>>> I'd like to just
>>>
>>>> make
>>>> changes and then refresh the browser to test -- is
>>>>
>>> this possible?
>>>
>>>> I've seen in the FAQ that you can change the
>>>>
>>> application settings to
>>>
>>>> auto-reload markup .html files -- where would I insert
>>>>
>>> this setting
>>>
>>>> (remember I'm a total n00b).
>>>>
>>>> As to .css/.js/.java files -- do I need jRebel or
>>>>
>>> something like that to
>>>
>>>> get
>>>> these files to reload automatically?
>>>>
>>>> Thanks for helping out a super-beginner :)
>>>> --
>>>> View this message in context:
>>>> http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2226360.html
>>>> Sent from the Wicket - User 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
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>>
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
Yes. I am using tomcatPlugin 3.2.1. Here is what I followed as instructed by the download: Version 3.2 New features : - Tomcat 6.x supported. If you want to use DevLoader with Tomcat 6.x. Rename DevLoader.zip file to DevLoader.jar and put it in <%Tomcat6_Home%>/lib I modified parenet html or child html a few times, each trigger tomcat's restart. Did I miss something? Thanks! --- On Sat, 5/29/10, Wouter de Vaal wrote: > From: Wouter de Vaal > Subject: Re: Can I develop without recompiling/restarting after every change? > To: users@wicket.apache.org > Date: Saturday, May 29, 2010, 11:52 AM > Did you use the DevLoader? If so, the > eclipse classpath gets loaded > directly into tomcat, making hotreplace and debugging > possible. See > http://www.eclipsetotale.com/tomcatPlugin/readmeDevLoader.html > For heavy changes you might need restarts, but eclipse will > prompt > when necessary. When you use a tool like JRebel these > restarts are let > frequently needed. > > Wouter > > 2010/5/29 David Chang : > > Wouter, thanks for your input! > > > > I got tomcatPlugiin installed as you sugggested and I > can start it from within eclipse to run a wicket app. But > how can I do development without recompiling or restarting > after every change? > > > > The quickstart's Start.java in Jeremy's suggestion > uses Jetty as web server. How can I do a similar thing with > Tomcat? Any pointers? I am using Tomcat 6.x. > > > > Best, > > David > > > > --- On Sat, 5/29/10, Wouter de Vaal > wrote: > > > >> From: Wouter de Vaal > >> Subject: Re: Can I develop without > recompiling/restarting after every change? > >> To: users@wicket.apache.org > >> Date: Saturday, May 29, 2010, 9:52 AM > >> If you're using eclipse, use sysdeo: > >> > >> http://www.eclipsetotale.com/tomcatPlugin.html > >> > >> Wouter > >> > >> 2010/5/29 David Chang : > >> > I am using Tomcat, any tips about how to > develop out > >> recompiling/restarting after every change? > >> > > >> > Best. > >> > > >> > --- On Fri, 5/21/10, Jeremy Thomerson > >> wrote: > >> > > >> >> From: Jeremy Thomerson > >> >> Subject: Re: Can I develop without > >> recompiling/restarting after every change? > >> >> To: users@wicket.apache.org > >> >> Date: Friday, May 21, 2010, 12:17 PM > >> >> the easiest way to do this is to use > >> >> the Start class (Start.java) from the > >> >> quickstart to run an embedded jetty > instance in > >> your > >> >> IDE. then, if you run > >> >> it in debug mode, it will hotswap any > possible > >> changes (and > >> >> tell you if you > >> >> must restart if it's an incompatible > change) > >> >> > >> >> -- > >> >> Jeremy Thomerson > >> >> http://www.wickettraining.com > >> >> > >> >> > >> >> > >> >> On Fri, May 21, 2010 at 10:53 AM, > ekallevig > >> >> wrote: > >> >> > >> >> > > >> >> > I'm a front-end developer trying to > learn > >> Java (total > >> >> n00b) and working on > >> >> > a > >> >> > wicket application at work. The > whole > >> process > >> >> feels very slow primarily > >> >> > because I have to recompile and > restart JBoss > >> every > >> >> time I make a change. > >> >> > So I'm wondering what the best way > is to > >> avoid having > >> >> to do this when > >> >> > editing .java/.js/.css/.html files > during > >> development? > >> >> I'd like to just > >> >> > make > >> >> > changes and then refresh the browser > to test > >> -- is > >> >> this possible? > >> >> > > >> >> > I've seen in the FAQ that you can > change the > >> >> application settings to > >> >> > auto-reload markup .html files -- > where would > >> I insert > >> >> this setting > >> >> > (remember I'm a total n00b). > >> >> > > >> >> > As to .css/.js/.java files -- do I > need > >> jRebel or > >> >>
Re: Can I develop without recompiling/restarting after every change?
Did you use the DevLoader? If so, the eclipse classpath gets loaded directly into tomcat, making hotreplace and debugging possible. See http://www.eclipsetotale.com/tomcatPlugin/readmeDevLoader.html For heavy changes you might need restarts, but eclipse will prompt when necessary. When you use a tool like JRebel these restarts are let frequently needed. Wouter 2010/5/29 David Chang : > Wouter, thanks for your input! > > I got tomcatPlugiin installed as you sugggested and I can start it from > within eclipse to run a wicket app. But how can I do development without > recompiling or restarting after every change? > > The quickstart's Start.java in Jeremy's suggestion uses Jetty as web server. > How can I do a similar thing with Tomcat? Any pointers? I am using Tomcat 6.x. > > Best, > David > > --- On Sat, 5/29/10, Wouter de Vaal wrote: > >> From: Wouter de Vaal >> Subject: Re: Can I develop without recompiling/restarting after every change? >> To: users@wicket.apache.org >> Date: Saturday, May 29, 2010, 9:52 AM >> If you're using eclipse, use sysdeo: >> >> http://www.eclipsetotale.com/tomcatPlugin.html >> >> Wouter >> >> 2010/5/29 David Chang : >> > I am using Tomcat, any tips about how to develop out >> recompiling/restarting after every change? >> > >> > Best. >> > >> > --- On Fri, 5/21/10, Jeremy Thomerson >> wrote: >> > >> >> From: Jeremy Thomerson >> >> Subject: Re: Can I develop without >> recompiling/restarting after every change? >> >> To: users@wicket.apache.org >> >> Date: Friday, May 21, 2010, 12:17 PM >> >> the easiest way to do this is to use >> >> the Start class (Start.java) from the >> >> quickstart to run an embedded jetty instance in >> your >> >> IDE. then, if you run >> >> it in debug mode, it will hotswap any possible >> changes (and >> >> tell you if you >> >> must restart if it's an incompatible change) >> >> >> >> -- >> >> Jeremy Thomerson >> >> http://www.wickettraining.com >> >> >> >> >> >> >> >> On Fri, May 21, 2010 at 10:53 AM, ekallevig >> >> wrote: >> >> >> >> > >> >> > I'm a front-end developer trying to learn >> Java (total >> >> n00b) and working on >> >> > a >> >> > wicket application at work. The whole >> process >> >> feels very slow primarily >> >> > because I have to recompile and restart JBoss >> every >> >> time I make a change. >> >> > So I'm wondering what the best way is to >> avoid having >> >> to do this when >> >> > editing .java/.js/.css/.html files during >> development? >> >> I'd like to just >> >> > make >> >> > changes and then refresh the browser to test >> -- is >> >> this possible? >> >> > >> >> > I've seen in the FAQ that you can change the >> >> application settings to >> >> > auto-reload markup .html files -- where would >> I insert >> >> this setting >> >> > (remember I'm a total n00b). >> >> > >> >> > As to .css/.js/.java files -- do I need >> jRebel or >> >> something like that to >> >> > get >> >> > these files to reload automatically? >> >> > >> >> > Thanks for helping out a super-beginner :) >> >> > -- >> >> > View this message in context: >> >> > http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2226360.html >> >> > Sent from the Wicket - User 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 >> >> > >> >> > >> >> >> > >> > >> > >> > >> > >> - >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> > For additional commands, e-mail: users-h...@wicket.apache.org >> > >> > >> >> >> >> -- >> check out https://www.memolio.com >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- check out https://www.memolio.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
Wouter, thanks for your input! I got tomcatPlugiin installed as you sugggested and I can start it from within eclipse to run a wicket app. But how can I do development without recompiling or restarting after every change? The quickstart's Start.java in Jeremy's suggestion uses Jetty as web server. How can I do a similar thing with Tomcat? Any pointers? I am using Tomcat 6.x. Best, David --- On Sat, 5/29/10, Wouter de Vaal wrote: > From: Wouter de Vaal > Subject: Re: Can I develop without recompiling/restarting after every change? > To: users@wicket.apache.org > Date: Saturday, May 29, 2010, 9:52 AM > If you're using eclipse, use sysdeo: > > http://www.eclipsetotale.com/tomcatPlugin.html > > Wouter > > 2010/5/29 David Chang : > > I am using Tomcat, any tips about how to develop out > recompiling/restarting after every change? > > > > Best. > > > > --- On Fri, 5/21/10, Jeremy Thomerson > wrote: > > > >> From: Jeremy Thomerson > >> Subject: Re: Can I develop without > recompiling/restarting after every change? > >> To: users@wicket.apache.org > >> Date: Friday, May 21, 2010, 12:17 PM > >> the easiest way to do this is to use > >> the Start class (Start.java) from the > >> quickstart to run an embedded jetty instance in > your > >> IDE. then, if you run > >> it in debug mode, it will hotswap any possible > changes (and > >> tell you if you > >> must restart if it's an incompatible change) > >> > >> -- > >> Jeremy Thomerson > >> http://www.wickettraining.com > >> > >> > >> > >> On Fri, May 21, 2010 at 10:53 AM, ekallevig > >> wrote: > >> > >> > > >> > I'm a front-end developer trying to learn > Java (total > >> n00b) and working on > >> > a > >> > wicket application at work. The whole > process > >> feels very slow primarily > >> > because I have to recompile and restart JBoss > every > >> time I make a change. > >> > So I'm wondering what the best way is to > avoid having > >> to do this when > >> > editing .java/.js/.css/.html files during > development? > >> I'd like to just > >> > make > >> > changes and then refresh the browser to test > -- is > >> this possible? > >> > > >> > I've seen in the FAQ that you can change the > >> application settings to > >> > auto-reload markup .html files -- where would > I insert > >> this setting > >> > (remember I'm a total n00b). > >> > > >> > As to .css/.js/.java files -- do I need > jRebel or > >> something like that to > >> > get > >> > these files to reload automatically? > >> > > >> > Thanks for helping out a super-beginner :) > >> > -- > >> > View this message in context: > >> > http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2226360.html > >> > Sent from the Wicket - User 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 > >> > > >> > > >> > > > > > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > -- > check out https://www.memolio.com > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Re: Can I develop without recompiling/restarting after every change?
have you tried JRebel? I've not used it myself, but there was an interview on JavaPosse recently, sounds like it'd be an ideal fit for any Wicket developer. Dan On 22/07/28164 20:59, David Chang wrote: I am using Tomcat, any tips about how to develop out recompiling/restarting after every change? Best. --- On Fri, 5/21/10, Jeremy Thomerson wrote: From: Jeremy Thomerson Subject: Re: Can I develop without recompiling/restarting after every change? To: users@wicket.apache.org Date: Friday, May 21, 2010, 12:17 PM the easiest way to do this is to use the Start class (Start.java) from the quickstart to run an embedded jetty instance in your IDE. then, if you run it in debug mode, it will hotswap any possible changes (and tell you if you must restart if it's an incompatible change) -- Jeremy Thomerson http://www.wickettraining.com On Fri, May 21, 2010 at 10:53 AM, ekallevig wrote: I'm a front-end developer trying to learn Java (total n00b) and working on a wicket application at work. The whole process feels very slow primarily because I have to recompile and restart JBoss every time I make a change. So I'm wondering what the best way is to avoid having to do this when editing .java/.js/.css/.html files during development? I'd like to just make changes and then refresh the browser to test -- is this possible? I've seen in the FAQ that you can change the application settings to auto-reload markup .html files -- where would I insert this setting (remember I'm a total n00b). As to .css/.js/.java files -- do I need jRebel or something like that to get these files to reload automatically? Thanks for helping out a super-beginner :) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2226360.html Sent from the Wicket - User 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
If you're using eclipse, use sysdeo: http://www.eclipsetotale.com/tomcatPlugin.html Wouter 2010/5/29 David Chang : > I am using Tomcat, any tips about how to develop out recompiling/restarting > after every change? > > Best. > > --- On Fri, 5/21/10, Jeremy Thomerson wrote: > >> From: Jeremy Thomerson >> Subject: Re: Can I develop without recompiling/restarting after every change? >> To: users@wicket.apache.org >> Date: Friday, May 21, 2010, 12:17 PM >> the easiest way to do this is to use >> the Start class (Start.java) from the >> quickstart to run an embedded jetty instance in your >> IDE. then, if you run >> it in debug mode, it will hotswap any possible changes (and >> tell you if you >> must restart if it's an incompatible change) >> >> -- >> Jeremy Thomerson >> http://www.wickettraining.com >> >> >> >> On Fri, May 21, 2010 at 10:53 AM, ekallevig >> wrote: >> >> > >> > I'm a front-end developer trying to learn Java (total >> n00b) and working on >> > a >> > wicket application at work. The whole process >> feels very slow primarily >> > because I have to recompile and restart JBoss every >> time I make a change. >> > So I'm wondering what the best way is to avoid having >> to do this when >> > editing .java/.js/.css/.html files during development? >> I'd like to just >> > make >> > changes and then refresh the browser to test -- is >> this possible? >> > >> > I've seen in the FAQ that you can change the >> application settings to >> > auto-reload markup .html files -- where would I insert >> this setting >> > (remember I'm a total n00b). >> > >> > As to .css/.js/.java files -- do I need jRebel or >> something like that to >> > get >> > these files to reload automatically? >> > >> > Thanks for helping out a super-beginner :) >> > -- >> > View this message in context: >> > http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2226360.html >> > Sent from the Wicket - User 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 >> > >> > >> > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- check out https://www.memolio.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
I am using Tomcat, any tips about how to develop out recompiling/restarting after every change? Best. --- On Fri, 5/21/10, Jeremy Thomerson wrote: > From: Jeremy Thomerson > Subject: Re: Can I develop without recompiling/restarting after every change? > To: users@wicket.apache.org > Date: Friday, May 21, 2010, 12:17 PM > the easiest way to do this is to use > the Start class (Start.java) from the > quickstart to run an embedded jetty instance in your > IDE. then, if you run > it in debug mode, it will hotswap any possible changes (and > tell you if you > must restart if it's an incompatible change) > > -- > Jeremy Thomerson > http://www.wickettraining.com > > > > On Fri, May 21, 2010 at 10:53 AM, ekallevig > wrote: > > > > > I'm a front-end developer trying to learn Java (total > n00b) and working on > > a > > wicket application at work. The whole process > feels very slow primarily > > because I have to recompile and restart JBoss every > time I make a change. > > So I'm wondering what the best way is to avoid having > to do this when > > editing .java/.js/.css/.html files during development? > I'd like to just > > make > > changes and then refresh the browser to test -- is > this possible? > > > > I've seen in the FAQ that you can change the > application settings to > > auto-reload markup .html files -- where would I insert > this setting > > (remember I'm a total n00b). > > > > As to .css/.js/.java files -- do I need jRebel or > something like that to > > get > > these files to reload automatically? > > > > Thanks for helping out a super-beginner :) > > -- > > View this message in context: > > http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2226360.html > > Sent from the Wicket - User 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 > > > > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can I develop without recompiling/restarting after every change?
Or use jrebel On May 23, 2010 1:41 PM, "ekallevig" wrote: Thanks for the reply -- I'll look into that option! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2227956.html Sent from the Wicket - User mailing list archive at Nabble.com. ---...
Re: Can I develop without recompiling/restarting after every change?
Thanks for the reply -- I'll look into that option! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2227956.html Sent from the Wicket - User 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
Re: Can I develop without recompiling/restarting after every change?
the easiest way to do this is to use the Start class (Start.java) from the quickstart to run an embedded jetty instance in your IDE. then, if you run it in debug mode, it will hotswap any possible changes (and tell you if you must restart if it's an incompatible change) -- Jeremy Thomerson http://www.wickettraining.com On Fri, May 21, 2010 at 10:53 AM, ekallevig wrote: > > I'm a front-end developer trying to learn Java (total n00b) and working on > a > wicket application at work. The whole process feels very slow primarily > because I have to recompile and restart JBoss every time I make a change. > So I'm wondering what the best way is to avoid having to do this when > editing .java/.js/.css/.html files during development? I'd like to just > make > changes and then refresh the browser to test -- is this possible? > > I've seen in the FAQ that you can change the application settings to > auto-reload markup .html files -- where would I insert this setting > (remember I'm a total n00b). > > As to .css/.js/.java files -- do I need jRebel or something like that to > get > these files to reload automatically? > > Thanks for helping out a super-beginner :) > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Can-I-develop-without-recompiling-restarting-after-every-change-tp2226360p2226360.html > Sent from the Wicket - User 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 > >
