IMHO, a better technique is to bubble up an event. It's better because it
doesn't require the component to know anything about its container.
In the example below, PersonUpdate bubbles up UPDATED like this...
componentResources.triggerEvent(UPDATED, new Object[] { person }, null);
...wh
Hi,
Have a look for a thread I started called "component events bubbling down?".
There's a link and some discussion that should help you.
On the whole it is generally advisable to avoid tight coupling between
component type classes because it reduced reusability. It is specifically
desirable f
Hi,
For our current project we have the need to be able to connect to
multiple databases using Hibernate.
I have seen the blog post of Taha
(http://tawus.wordpress.com/2012/03/03/tapestry-hibernate-multiple-databases/)
and was wondering if there exists a library based on this or similar
that I can
Hi Thiago,
Thanks for all your responses.I am still stuck with the problem related to
the loading of images , when less to css compilation is forced by us.
As I told you:
In the less file the images are referenced with paths, like
@product: url(../images/product.svg)--( though I agree that we c
You could take the quick and dirty way and have a tapestry filter redirect
to the correct asset paths.
We use this at work for things like rich text editors that attempts to load
stuff relative to the first js file loaded.
--
Chris
On Mon, Oct 13, 2014 at 3:37 PM, akshay wrote:
> Hi Thiago,
>
Thanks everyone. Geoff, I ended up finding your jumpstart example soon
after my reply. I've been studying your way of doing it. I'm still
learning it, but thus far I like it much better than my original
approach.
-
To unsubscribe,
On Mon, 13 Oct 2014 10:37:25 -0300, akshay
wrote:
Hi Thiago,
Thanks for all your responses.I am still stuck with the problem related
to
the loading of images , when less to css compilation is forced by us.
As I told you:
In the less file the images are referenced with paths, like
@prod
Anyone please ? Is my question unclear ?
*-*
*Muhammad Gelbana*
http://www.linkedin.com/in/mgelbana
On Mon, Oct 13, 2014 at 8:34 AM, Muhammad Gelbana
wrote:
> I have a *Select* component. I need to display a *Zone* when the *Select*
> component is rendered so I specified the
I'm using 5.4 and for some reason I can not get my ajax form to hold
onto the field values after a validation error has occurred. When a
validation error occures all my fields are blanked out. Does anybody
have any idea what might be causing this?
I have the following code snippet.
//additiona
Odd behavior, I found if I removed the form from the zone it fixed the
issue; however this does not make any sense to me though.
//additional fields
On Mon, Oct 13, 2014 at 1:43 PM, George Christman
wrote:
> I'm using 5.4 and for some reason I can not get my ajax form to hold
> onto the fi
So I think I'm close to figuring out the cause of this issue, it looks
as if the form/field id's are changing with the zone up date which I
believe is the cause of this issue. Any experts have any thoughts?
On Mon, Oct 13, 2014 at 3:01 PM, George Christman
wrote:
> Odd behavior, I found if I remo
figured it out, was an error on my behalf. I needed to wrap new
UserProfile with a null check.
public void onPrepareFromRegisterForm() {
if (userProfile == null) {
userProfile = new UserProfile();
userProfile.setCreateDate(new Date());
}
}
On Mon, Oct 1
John I'm a little confused with step 2.
>
> 1) componentA - trigger event
> onSuccessFromLogin() {
> componentResources.triggerEvent("LoginComplete"...
>
> 2) container of both A and B components - handover event
> onLoginComplete(Object[] ctxValues) {
> componentB.onLoginComplete(ctxValues
So I was able to get it working by using the following code inside of
SiteIndex, but this does not seem very reusable.
@InjectComponent
private Layout layout;
void onShowLoginRegister() {
layout.onShowLoginRegister();
}
So is this the correct way to do this for this scenario?
My
On 14 Oct 2014, at 1:14 pm, George Christman wrote:
> So I was able to get it working by using the following code inside of
> SiteIndex, but this does not seem very reusable.
>
> @InjectComponent
>private Layout layout;
>
> void onShowLoginRegister() {
>layout.onShowLoginRegister()
Good question. I think it may be an historical accident, made largely redundant
by AjaxResponseRenderer, and MultiZoneUpdate before it. They take no notice of
what was specified in the component's zone parameter. With AjaxResponseRenderer
you don't even have to return a zone - instead you could
On Mon, Oct 13, 2014 at 9:52 PM, Geoff Callender <
geoff.callender.jumpst...@gmail.com> wrote:
> On 14 Oct 2014, at 1:14 pm, George Christman
> wrote:
> > So I was able to get it working by using the following code inside of
> > SiteIndex, but this does not seem very reusable.
> > @InjectComponen
Hi,
On Tue, Oct 14, 2014 at 7:27 AM, Geoff Callender <
geoff.callender.jumpst...@gmail.com> wrote:
>
> Perhaps it's time for Tapestry to replace the zone parameter with
> ajax="true" or xhr="true"?
>
> Geoff
>
A good deal of the components already supports async parameter for exactly
this.
--
Since 5.4! I'd completely missed that. Thanks.
On 14 Oct 2014, at 5:39 pm, Chris Poulsen wrote:
> Hi,
>
> On Tue, Oct 14, 2014 at 7:27 AM, Geoff Callender <
> geoff.callender.jumpst...@gmail.com> wrote:
>
>>
>> Perhaps it's time for Tapestry to replace the zone parameter with
>> ajax="true" o
19 matches
Mail list logo
