On Thu, Jul 14, 2011 at 1:22 PM, Matt Brictson wrote:
> Hmm. I would expect that your LoginPage would see changes reflected when you
> hit the browser refresh button. Sounds like a bug to me.
>
> Is it related to this one?
>
> https://issues.apache.org/jira/browse/WICKET-3891
This bug says that
Hmm. I would expect that your LoginPage would see changes reflected when you
hit the browser refresh button. Sounds like a bug to me.
Is it related to this one?
https://issues.apache.org/jira/browse/WICKET-3891
On Jul 13, 2011, at 12:10 PM, Andrew Todd wrote:
> On Wed, Jul 13, 2011 at 2:40 PM,
On Wed, Jul 13, 2011 at 2:40 PM, Matt Brictson wrote:
> FWIW I tried 1.5-SNAPSHOT and the HTML resource reloading seems to work fine.
I'm seeing reloading working as expected on the basic HomePage.
However, on a LoginPage that I'm working on, a I do not see changes
reflected until I go to the URL
lication#init[2].
3. Ran mvn jetty:run.
4. While jetty was running, I edited Home.html: I changed "Congratulations" to
"Testing".
5. Hit refresh in my browser and the change showed up.
[1]: http://wicket.apache.org/start/quickstart.html
[2]:
http://apache-wicket.1842946.n4.nabbl
With the latest snapshot, I still wasn't seeing changes propagate. Until --
On Wed, Jul 13, 2011 at 2:03 PM, Martin Grigorov wrote:
> It is possible but you have to extend maven-jetty-plugin's configuration.
> There was something about Scanner. Ask Google for more info
Adding the scanIntervalSec
Yes, it is possible configure the jetty plugin to completely redeploy the
webapp when it detects a class file has changed, but this isn't quite the same
as what the Eclipse IDE and JRebel do. JRebel's site says: "instantly see any
code change made to an app *without* redeploying."
In my experie
On Wed, Jul 13, 2011 at 9:00 PM, Matt Brictson wrote:
> Just to clarify, the resource polling should allow you to see HTML changes
> (but note Martin's comment about this potentially being broken in 1.5RC1). It
> does not affect Java reloading.
>
> For Java changes I believe this is not possible
Just to clarify, the resource polling should allow you to see HTML changes (but
note Martin's comment about this potentially being broken in 1.5RC1). It does
not affect Java reloading.
For Java changes I believe this is not possible without an IDE or perhaps a
commercial product like JRebel[1].
> 'Resources in the
> htmlDir that was already set, like CSS, are also not updating.
I apologize for sending that last message prematurely; things in the
webapp/ directory are updating. HTML in the java/ subfolder is not,
however.
--
See https://issues.apache.org/jira/browse/WICKET-3878 and
https://issues.apache.org/jira/browse/WICKET-3891.
RC5.1 has some issues in that area. Try with 1.5-SNAPSHOT.
On Wed, Jul 13, 2011 at 8:04 PM, Matt Brictson wrote:
> The way I've always done it (and this works just fine outside of Eclipse
On Wed, Jul 13, 2011 at 1:04 PM, Matt Brictson wrote:
> The way I've always done it (and this works just fine outside of Eclipse as
> well), is to enable resource polling in Wicket for the directory that
> contains the HTML files.
>
> In the init() method of your WebApplication subclass (in the
The way I've always done it (and this works just fine outside of Eclipse as
well), is to enable resource polling in Wicket for the directory that contains
the HTML files.
In the init() method of your WebApplication subclass (in the quickstart this is
called WicketApplication.java) do something
Hello,
I'm investigating writing a new project in Wicket and am playing
around with a project created from the 1.5-RC5.1 quickstart maven
archetype.
Using 'mvn jetty:run' from the command-line, none of the changes I
make to source files, either Java or HTML, are picked up unless I
restart the ser
13 matches
Mail list logo
