Hello, I"m trying to get lances Tapestry Cometd working with 5.4, however
I'm running into a couple problems.
I'm get the following exception.
Now I'd like to point out I'm not using Tapestry-Jquery like the
documentation says your suppose to do to the fact jquery is now a part of
5.4.
Lance, an
I'm building a service MasterFooProvider that takes contributions of type
FooProvider. I'd really love for one my FooProvider implementations,
ConfigurableFooProvider, to be able to take contributions of its own (of
type String), so its behavior can be customized.
My first stab at implementing thi
Hi,
Thanks for pointing this out Dmitry.
Yes I have bound my child components parameters to a PersistConstants.FLASH
property in the containing parent component! This of course explains why it is
lost after subsequent use. I'm not sure what to do about that if persisting
into session is bad pr
On Fri, 06 Dec 2013 16:28:51 -0200, Nicolas Barrera
wrote:
I 'm using 5.3
Check the documentation at https://github.com/trsvax/tapestry-bootstrap.
As far as I could see, fwtype is a parameter of the FW mixin, which is
applied to all components automatically by Tapestry-Bootstrap.
Ni
I 'm using 5.3
Nicolás.-
On Fri, Dec 6, 2013 at 6:15 AM, Eugen wrote:
> Hi,
> which vewrsion of Tapestry are You using?
> for 5.4 You don't need to user fwtype, just 'class' attribute
>
> Eugen
>
> 2013/12/5 Nicolas Barrera :
> > Hi,
> >
> > Just wandering why should I use the fwtype parameter
On Fri, 06 Dec 2013 11:33:05 -0200, Dusko Jovanovski
wrote:
It works both in pages and components.
Just remember that @Cached only caches method return values during a
request, but not between requests. I'm planning to do provide some caching
(not just in a single thread) in for Tapestr
By the way, an interesting side effect of this is if you pass literal
constant to parameter value and try to modify the param value from
somewhere you'll see runtime error saying that parameter binding is read
only. Which is true, because you can't change the value of constant literal:
Page.tml
I don't think you understand that tapestry parameters are actually
bindings, which means they don't store any values at all -- the value if
stored on the referencing side. See this example:
Page.tml
Page.java
public class Page {
@Property
private String value;
}
Component.java
public cl
"what would the value IF the @Parameter be" should be "what would the value
OF the @Parameter be" (smartphone typo)
On 6 Dec 2013 13:54, "Lance Java" wrote:
> Let's consider that your component was being used in a t:loop and that the
> current loop value was passed to your component as a @Paramet
Let's consider that your component was being used in a t:loop and that the
current loop value was passed to your component as a @Parameter.
We know that tapestry's static structure / dynamic behaviour means that
there is only 1 instance of your component (rendered multiple times). So,
what would t
It works both in pages and components.
On Fri, Dec 6, 2013 at 2:20 PM, John wrote:
> does @Cached work in only pages, or should it work in components too?
On Fri, 06 Dec 2013 10:56:32 -0200, John wrote:
Hi Lance,
Hi!
I am resistant to passing these parameters in the t:context to my event
handlers because:
1) it is boilerplate stuff and Tapestry is supposed to handle that
without me writing code
That's very, very, very wrong. See my mes
does @Cached work in only pages, or should it work in components too?
On Fri, 06 Dec 2013 11:02:27 -0200, John wrote:
Hi,
Hi!
I am not very CSS savy Thiago, but I think center is code efficient vs
the css way?
I disagree. HTML is structure, CSS is layout. is something that
shouldn't be used anymore.
Please see my previous response to Lance as to why I
Hi,
I am not very CSS savy Thiago, but I think center is code efficient vs the css
way?
Please see my previous response to Lance as to why I am resisting your
suggestions. In short it is not OO, DRY or to the Tapestry ethos.
IMO Tapestry framework should take care of persisting component param
Hi Lance,
I am resistant to passing these parameters in the t:context to my event
handlers because:
1) it is boilerplate stuff and Tapestry is supposed to handle that without me
writing code
2) it clutters my event handlers contract with fields and functions the method
is not directly concerne
I've raised an issue, can you try the fix attached to the issue?
https://github.com/uklance/tapestry-offline/issues/4
Thanx for the guidance. I tried out tapestry-offline and it works very
nicely for me, I think I will stick with this one.
I had one configuration problem with tapestry-offline (maybe a bug?):
I was getting exception when GZIP compression was turned on (full stack
trace below).
When I turned off g
On Thu, 05 Dec 2013 21:53:44 -0200, John wrote:
here is the template with the problematic actionlink highlighted
Thanks!
${message:text.diarydenied}
I haven't seen the very deprecated HTML tag for many years . . .
I felt like in 1998 when I read it. :P
t:zone="dateZon
Hi,
which vewrsion of Tapestry are You using?
for 5.4 You don't need to user fwtype, just 'class' attribute
Eugen
2013/12/5 Nicolas Barrera :
> Hi,
>
> Just wandering why should I use the fwtype parameter as in the jumpstart
> bootstrap example (
> http://jumpstart.doublenegative.com.au/jumpstart
I've said this many times now. You must pass the parameters in the event
context.
onActionFromFoo(String param1, Foo param2, Bar param3)
BTW: IMHO actionlink is deprecated and shouldn't be used. Use eventlink
instead.
21 matches
Mail list logo
