Thanks Igor.
-Original Message-
From: Igor Drobiazko [mailto:igor.drobia...@gmail.com]
Sent: 04 March 2010 09:05 AM
To: Tapestry users
Subject: Re: Display a hashmap using a grid component
Just create your own implementation of GridDataSource [1] and pass it to
the
Grid component.
[1]
Just create your own implementation of GridDataSource [1] and pass it to the
Grid component.
[1]
http://tapestry.apache.org/tapestry5.1/apidocs/org/apache/tapestry5/grid/GridDataSource.html
On Thu, Mar 4, 2010 at 7:58 AM, Eldred Mullany wrote:
> Hello everyone
>
>
>
> I would like to know if an
Hello everyone
I would like to know if anyone has successfully implemented a hash map
through a grid component. How do I display the desired value
(map.get("key")) on my template using a grid component ? Is this
possible in T5.1.0.5?
Thanking you in advance
Eldred Mullany
Hello,
Has anyone developed some nice page-level client persistence strategy and is
willing to share it?
Default @Persist("client") keeps URL parameter present all the time until
discarded explicitly via code, even when user leaves the page in question,
but I need something that will act simil
That's what Java code is for ... you can inject the AssetSource
service to obtain assets from dynamically-assembled strings.
On Wed, Mar 3, 2010 at 5:17 PM, Hilco Wijbenga wrote:
> Hi all,
>
> I used to have (in my .tml):
>
>
>
> which of course worked fine.
>
> To support multiple colours I nee
Hi all,
I used to have (in my .tml):
which of course worked fine.
To support multiple colours I need a little bit more flexibility so I
tried to do
which failed miserably because T5 doesn't do variable expansion inside
variable expansions. Not entirely unreasonable, I suppose. :-)
I had a
Thanks for the help. I refactored the code to remove the need of the
InjectionProvider to assure it will work in both 5.1 and 5.2.
Thanks for pointing me to the problem.
Kind regards,
Joachim
Thiago H. de Paula Figueiredo wrote:
On Wed, 03 Mar 2010 04:23:58 -0300, Joachim Van der Auwera
wrot
Tapestry 5.1 error page fails when something in the session has a
toString() or a getter method that throws some exception when invoked.
Caused by: java.lang.NullPointerException
at
org.apache.jasper.compiler.TagLibraryInfoImpl.toString(TagLibraryInfoImpl.java:127)
Why would a JSP compiler
I've been struggling quite a while with this problem. On Jetty, the
non-production mode exception page mostly works the first few requests,
after that it starts to crash with the exception listed below. I'm not 100%
sure, but I think it worked on tomcat 6. Our test server is running T5 in
productio
On Wed, Mar 3, 2010 at 8:24 AM, Massimo Lusetti wrote:
> On Tue, Mar 2, 2010 at 11:39 PM, Howard Lewis Ship wrote:
>
>> You may have to recode some of your custom
>> ComponentClassTransformWorker. If you don't have one, show us the
>> full stack trace so I can see what went wrong.
>>
>> You're s
On Wed, 03 Mar 2010 12:54:10 -0300, Howard Lewis Ship
wrote:
The new approach makes it so much easier to add meta-programming to
component classes and it repesents a path away from Javassist. I've
been making the judgement call that these benefits outweigh the costs
... but what we're seeing
On Tue, Mar 2, 2010 at 11:39 PM, Howard Lewis Ship wrote:
> You may have to recode some of your custom
> ComponentClassTransformWorker. If you don't have one, show us the
> full stack trace so I can see what went wrong.
>
> You're seeing some imperfect backwards compatibility in the process of
>
The problem is that
org.equanda.t5gui.services.EquandaMessagesInjectionProvider is coded
against Tapestry 5.1.
This brings up a painful issue: fixing fundamental problems vs.
perfect backwards compatibility,.
The changes I've made to the ClassTransformation interface are really
keen ... but they
On Wed, 03 Mar 2010 11:35:00 -0300, DavidWei wrote:
Thanks for your suggestion. I will try to do what you suggested and to
see if it is working.
I can assure you it works, even being easier than using a script block.
Generating JavaScript in templates, regardless of which engine, is worse
Thanks for your suggestion. I will try to do what you suggested and to see if
it is working.
By the way, I like to point out that exact same codes work fine with old
version Tapestry 5.0.0.18, but do not work with T5.1.0.5 when I am upgrading
Tapestry. So there must be some changes on renderings
On Wed, 03 Mar 2010 09:39:49 -0300, Joachim Van der Auwera (PROGS bvba)
wrote:
Thanks Thiago,
You're welcome!
Should it not still work for backward compatibility?
This change was made very recently and I haven't looked at that yet, so I
don't know the answer. Anyway, from reading Howa
Thanks Thiago,
Should it not still work for backward compatibility?
Anyway, I will check whether I can remove this from equanda (and make it
work in both 5.1 and 5.2.
Kind regards,
Joachim
Thiago H. de Paula Figueiredo wrote:
On Wed, 03 Mar 2010 04:23:58 -0300, Joachim Van der Auwera
wrote
On Wed, 03 Mar 2010 08:04:02 -0300, Stephan Windmüller
wrote:
http://wiki.apache.org/tapestry/FormClientPersistence
It's for Tapestry 4, not 5.
Oups. It seems that I misunderstood the description. What I wanted was
persisting values into hidden form field instead of the session.
It wou
On Wed, 03 Mar 2010 04:23:58 -0300, Joachim Van der Auwera
wrote:
Caused by: java.lang.RuntimeException: Method
ClassTransformation.extendMethod(TransformMethodSignature, String) has
been deprecated and is no longer functional. Please consult the JavaDoc
for a suitable replacement.
at
On 03.03.2010 12:01, Stephan Windmüller wrote:
http://wiki.apache.org/tapestry/FormClientPersistence
Oups. It seems that I misunderstood the description. What I wanted was
persisting values into hidden form field instead of the session.
- Stephan
---
Hello!
I found this interesting Wiki article:
http://wiki.apache.org/tapestry/FormClientPersistence
Does anyone if this is possible with Tapestry5, too?
Regards
Stephan
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.ap
21 matches
Mail list logo
