I currently use Eclipse 3.4 J2EE, Run-Jetty-Run and Jetty 6 with no problems
at all, I can debug quite happily through the debugger with class reloading
(components/pages) and template (.tml) changes all happening live. The only
thing I need to restart for is non-managed clesses such as Entities a
Hi All,
I seem to be having trouble getting my component to render informal
parameters, see enclosed classes, I can only get the informals to render on
the container element, not on the component itself.
So I have my Inf component which uses a tml - the compnent div already
having an 'existing'
Hi Ben,
I'm no classloader expert but I had a similar problem running with
RunJettyRun, that might be related to your problem, but I think its a clash
between the SLF4J in Jetty and the one in your app see
http://wiki.apache.org/tapestry/Tapestry5HowToSetupEclipseRunJettyRun
Regards,
Adam.
--
V
Hi All,
I'm seeing the same behaviour, I have a page that displays a list of items
which link off to a viewitem page with a pagelink with an item id for the
context (a string). When I hit the viewitem page I'm seeing the onActivate
event handler being called twice, the first time I can see that t
Hi All,
I love T5.
However I'm not over the moon with being force-fed protoype/scriptaculous
when I'm developing say a dojo app, I don't want proto/scrpt downloaded as
well to do stuff that dojo can do, so here is my suggestion with dealing
with this.
Normally all the standard functionality is
Hi Arve,
Yep, I got it to work as well - I should have been a bit more persistent
with my searching, still its little 'should be simple' things like this that
can trip you up if you are new to the T5 way. Its just a question of the
docs getting updated, I thought I saw talk of a grid section/tuto
I'm seeing the same behaviour, if my source is empty and I use the 'remove'
parameter I get the same exception:
'grid: xxx -- no source to determine list type from'
Results.tml
Removing the 'remove' param the page renders with the 'nothing to display'
message.
--
View this message in context