Replying to myself so quickly - not a good sign. ;-)
Anyway, I found another solution which is to let the event bubble up to the
parent component which needs to do the initialisation of the derived variable
(which is then provided as a source for the sub-component) and do the init in
the event
It makes some sense, but more details would help.
You said that the parameter is "redundant": in what way is it redundant?
If the parameter is already passed to the component, then what's the
issue?
If the value is calculated, why can't the component calculate it?
Incidentally, if the componen
Thanks for the replay Robert, I'll try to explain better.
Here's the component hierarchy, '->' means contains.
Page -> Component -> Sub-component
Page passes parameter (results) to Component which extracts a derived object
(grouper) using the statement "grouper = results.getGrouper();" in
setu
Hi Andrew,
if I got you right, Component hands over a parameter grouper to Sub-Component
although grouper actually is null. This seems a bit smelly. Perhaps you should
rethink your concept (no offense meant :-) ).
But anyway, maybe Tapestry's Environment service could solve your problem. That
I am sorry if i was not clear but this drop down is dhtml dorp-down. so even
if i submit i will not able to send two parameters.
--
View this message in context:
http://www.nabble.com/actionlink-context-value-tp17482696p17498038.html
Sent from the Tapestry - User mailing list archive at Nabble.
I just updated to the latest shapshot jars (and updated my import statements
to the new org.apache.tapestry5 package names), and now I can't find the
TapestryConstants class. My pom.xml looks like this
5.0.12-SNAPSHOT
...
The TapestryConstants class have been replaced
by BindingConstants, CSSClassConstants,...
Please see
http://tapestry.formos.com/nightly/tapestry5/apidocs/index.html
Shing
--- Franz Amador-2 <[EMAIL PROTECTED]> wrote:
>
> I just updated to the latest shapshot jars (and
> updated my import sta
As mentioned earlier, TapestryConstants has been refactored.
From trunk/tapestry-project:
find ./ -name '*Constants.java'
.//tapestry-core/src/main/java/org/apache/tapestry5/
BindingConstants.java
.//tapestry-core/src/main/java/org/apache/tapestry5/
CSSClassConstants.java
.//tapestry-core/src
Hi José,
Maybe this help.
http://tapestry.apache.org/tapestry5/tapestry-core/guide/beaneditform.html
http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-core/src/test/app3/
http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integratio
Hi José,
Maybe you could use onValidateForm(), it's called before onSuccess().
Marcus
Gotcha.
Why not do something simple like make the bound property a pseudo-
property?
Something like:
"Component".java:
@Component(parameters={"source=subSource",...})
SubComponent sub;
public Object getSubSource() {
return results.getGrouper();
}
...
Now subSource will be evaluate
Thanks, that's what I needed. How did you know this?
Robert Zeigler wrote:
>
> As mentioned earlier, TapestryConstants has been refactored.
>
> From trunk/tapestry-project:
>
> find ./ -name '*Constants.java'
> .//tapestry-core/src/main/java/org/apache/tapestry5/
> BindingConstants.java
>
Unsurprisingly, due to the package-name changes, t5-acegi and t5-components
no longer work with the snapshot version of t5. Are there snapshot versions
of them that use the new package names? I didn't see one for t5-acegi in
the localhost.nu repository. Otherwise, will the new, matching version
Such is the nature of open source. :)
You could download the source code and make the necessary changes
yourself, though.
-Filip
On 2008-05-28 00:51, Franz Amador-2 wrote:
Unsurprisingly, due to the package-name changes, t5-acegi and t5-components
no longer work with the snapshot version of
Hi Andy,
There's nothing wrong with letting events bubble - this is a core part
of the Tapestry design and you pretty much have to do this when using,
for example, BeanEditForm.
-Filip
On 2008-05-27 18:48, Blower, Andy wrote:
Replying to myself so quickly - not a good sign. ;-)
Anyway, I f
You could do something like this (in your page class):
@Inject
private BeanModelSource _beanModelSource;
@Inject
private ComponentResources _componentResources;
private BeanModel _model;
@OnEvent("activate")
void setupGrid() {
_model = _beanModelSource.create(YourGridRowClassType.class
Gang
I'm new to tapestry and I'm currently trying to catch a duplicate
database entry(i.e. user registered twice) and I'd like to catch the
hibernate exception and forward to the Exception Report page but
instead of displaying the error message, instead I'd like to say "User
already regis
17 matches
Mail list logo