>
>
>
> This may cause a lot of pain !
>>
>
> I'm not following you . . .
>
>
I just meant this won't be easy to manipulate generated DOM with java, but
if it's the only way, I can deal with that.
>
> So, can I conclude that the use of @Property wouldn't be recommended
>> within components ? Be
On Fri, May 13, 2011 at 1:43 PM, Rich M wrote:
> I've run into this issue now myself, was there ever a resolution to this or
> a workaround? As David said, supply an explicit value encoder isn't able to
> solve the issue for me either.
My brute force workaround was to disable
tapestry.hibernate.p
I've run into this issue now myself, was there ever a resolution to this
or a workaround? As David said, supply an explicit value encoder isn't
able to solve the issue for me either.
Thanks,
Rich
On 03/24/2011 10:52 PM, David Rees wrote:
TAP5-920 has long been an issue for one of our applicat
On Fri, 13 May 2011 14:49:47 -0300, Rich M wrote:
I'm sorry, I'm not sure I fully understand how that would work. Wouldn't
that re-render all the other zones as well? I'm trying to isolate just
one of the components and not update the other ones.
No. You just add to the MultiZoneUpdate obj
On Fri, 13 May 2011 14:06:46 -0300, Rich M wrote:
Hi,
Hi!
Use multiple zones instead of a single one and return a MultiZoneUpdate in
your event handler method.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owne
On Fri, 13 May 2011 12:52:36 -0300, Clément Uster
wrote:
Ok, I understand.
Interesting approach, thanks.
It's one of what I consider one of the hidden gems of Tapestry: its
server-side DOM.
This may cause a lot of pain !
I'm not following you . . .
So, can I conclude that the use of
Hi,
I'm trying to put together an interactive page with multiple components,
where each component can go through event/actions.
For example, two components might be account details and reports. In
account details the initial view is a display of your basic fields and
their values, but if you
>
>
> This is an old "corporate" lib, that isn't supposed to evolve anymore.
>>
>
> This scenario isn't very good . . .
Indeed...
The component was frozen with tapestry 5.1.0.5 and the need was too urgent
to wait for a release.
But, ok ! No worries. :)
>
> It has a simple loop, and I want to
Hi ,
Now you have a running demo application for eofficeo : *
https://demo.officeo.fr/demo*
The English version will be finished in a few weeks, but the current version
is almost finished.
All comments and suggests are welcome.
Thank you
Mourad
2011/2/3 bagou [via Tapestry Users] <
ml-node+598818
Hi,
I've put the above into a Mixin, which works fine, but the
implementation is a little "leaky" i.e. the containing component needs
to define it as an Implementation Mixin and set the tracker name /
context in the onPrepareForSubmit event.
I've been trying to change it so that the mixin can be
On Fri, 13 May 2011 11:53:19 -0300, Clément Uster
wrote:
Thanks Taha and Thiago.
Hi!
This is an old "corporate" lib, that isn't supposed to evolve anymore.
This scenario isn't very good . . .
It has a simple loop, and I want to change what is displayed for a
particular index (by addin
Thanks Taha and Thiago.
This is an old "corporate" lib, that isn't supposed to evolve anymore.
It has a simple loop, and I want to change what is displayed for a
particular index
(by adding an "if" component, testing the value of "index").
2011/5/13 Thiago H. de Paula Figueiredo
> On Fri, 13
On Fri, 13 May 2011 10:37:18 -0300, Clément Uster
wrote:
Thanks for your very quick answer. :)
:)
What do you suggest if extending component isn't recommended ?
Rewritting it ?
In many scenarios you can solve problems by creating a mixin. Could you
describe in more detail what you're
You can use composition
Embed that component inside your component, and publish its properties.
See the last topics of this page
http://tapestry.apache.org/component-parameters.html
regards
Taha
2011/5/13 Clément Uster
> Thanks for your very quick answer. :)
>
> What do you suggest if exte
Thanks for your very quick answer. :)
What do you suggest if extending component isn't recommended ?
Rewritting it ?
I can't create getters and setters since the component belongs to another
library.
I guess this shouldn't happen if the component had more entry points.
2011/5/13 Thiago H. de P
On Fri, 13 May 2011 10:11:19 -0300, Clément Uster
wrote:
Hi everyone,
Hi!
Let's imagine I have a component (coming from a component library) that
has an "index" property. So index has the @Property annotation.
I want to create a component that extends the previous component.
Extendin
On Fri, 13 May 2011 09:03:52 -0300, nazarhussain_s
wrote:
hi,
Hi!
I am a novice in Tapestry and using Tapestry 4.0 currently.
Just curious: why 4.0 and not 5.2 or at least 4.1? Existing project?
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate c
Hi everyone,
I have a tricky question for you. :)
Let's imagine I have a component (coming from a component library) that has
an "index" property.
So index has the @Property annotation.
I want to create a component that extends the previous component.
And I want to test "index"'s value to chang
hi,
I am a novice in Tapestry and using Tapestry 4.0 currently. I have to
develop AJAX Functionality in Tapestry 4.0 . For that one suitable option
that i found was Tacos. Can anybody provide info on how to integrate Tacos
in Tapestry 4.0 .(or is there any other more optimistic solution othe
19 matches
Mail list logo
