Hi Davor,
Have you tried running Jetty standalone, out of eclipse?
This is what we do. I'm not sure it has anything to do with your problem
but it might be worth a try.
It's only a few lines of code to write a simple Jetty server launcher as
you can see http://pastebin.com/WsEFi2yh
Just write a
You don't have to copy the templates anywhere. It still may not
explain why class reloading is slow for you, but file IO is fairly
expensive and thus should be avoided.
Kalle
On Wed, May 25, 2011 at 1:17 AM, Davor Hrg wrote:
> Hi,
>
> your suggestion did improve reload when only template is cha
Hi,
your suggestion did improve reload when only template is changed.
Still 6 seconds reload happens when I change page class.
Hope this is also abnormal and someone has some suggestions
how to fix it as well.
to clarify :
adding exclude ** for resources will stop eclipse from doing anything th
I put it back into the src/main/resources line of .classpath, like:
My templates are being copied to the expected place, like ...
target\classes\com\companyname\appname\pages\PageName.tml.
Maybe there's something else amiss with your maven/build configuration.
Does your pom.xml have the se
I also removed excluding ** for src/main/resurces
but without it templates do not get copied to calsses dir
where did you put back the excluding ** ?
Davor Hrg
Honestly, we have a pretty complex app: multiple zones, lots of and
nested components, loads of injected assets, services etc and it reloads
faster than I can hit F5.
On Tue, 2011-05-24 at 19:06 +0200, Davor Hrg wrote:
> I've updated run-jetty,
> and tried with and without page-pool
> still 5-
Maybe you did the same thing I did?
http://tapestry.1045711.n5.nabble.com/slow-page-reload-td4287502.html
On Tue, May 24, 2011 at 1:06 PM, Davor Hrg wrote:
> I've updated run-jetty,
> and tried with and without page-pool
> still 5-6 seconds load time.
>
>
> I decided to try to go as simple as p
I've updated run-jetty,
and tried with and without page-pool
still 5-6 seconds load time.
I decided to try to go as simple as possible ...
empty page with layout component takes 500 ms
- add a form .. it jumps to 700 ms
- add few submit buttons ... jumps to 800 ms
- add a component with a zon
Hi Davor,
I use a similar spec. Should take a second or two.
- Joel
On Tue, 2011-05-24 at 18:10 +0200, Davor Hrg wrote:
> ok,
>
> we are on 5.2.4 now,
> I am running it from eclipse using run-jetty-run 1.1.1
> I'll try newer jetty plugin 1.2.2.1
>
> how long should I expect a page reload to la
ok,
we are on 5.2.4 now,
I am running it from eclipse using run-jetty-run 1.1.1
I'll try newer jetty plugin 1.2.2.1
how long should I expect a page reload to last for:
- page
- editing component inside
- two forms in the component
- maybe 20 form fields total
Quad core intel Core i7
4GB
For me as well, instantaneous under Jetty.
5.2.5 adds "field write-behind" when in development mode, to assist
with debugging. This is also present in 5.3.
There is a switch to use the page pool, please chck the documentation
(configuration page).
On Tue, May 24, 2011 at 8:37 AM, Davor Hrg wro
Tomcat or Jetty? I forget why (perhaps I can dig out the details) but I
found class reloading on Tomcat was very slow - so I switched to Jetty
which is essentially instantaneous - very quick.
On Tue, 2011-05-24 at 17:37 +0200, Davor Hrg wrote:
> Hi,
>
> I may be wrong but since T5 5.2+
> live
Hi,
I may be wrong but since T5 5.2+
live class reloading is much slower.
I remember it being faster before
for a page with maybe 10-20 components
reload lasts for 5-10 seconds.
it becomes worse with each component added.
This is far from productive and far from advertised by the framewor
13 matches
Mail list logo
