Hi all,
I've justed started with Tapestry and I have a question.
I'm trying to store a Visit object and access it from a page.
I have put the following in the .application file:
com.hp.eclaims.web.utils.Visit
This Visit object contains a property called collectionInfo which is a
bean.
Th
"org.apache.tapestry.visit-class" for the
property in your .application file
-Original Message-----
From: Bode, Bianca [mailto:[EMAIL PROTECTED]
Sent: 04 April 2006 16:56
To: tapestry-user@jakarta.apache.org
Subject: Tapestry 3: trouble accessing Visit object
Hi all,
I've just
ailto:[EMAIL PROTECTED]
Sent: dinsdag 4 april 2006 17:35
To: Tapestry users
Subject: Re: Tapestry 3: trouble accessing Visit object
Just out of curiosity, if you're only starting off with tapestry now why
did you choose version 3 over 4?
On 4/4/06, Bode, Bianca <[EMAIL PROTECTED]> wrot
sing Visit object
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bode, Bianca wrote:
> We're on a project where a few developers already had some experience
> with 3.
> Unfortunately none of them could help me with this...
>
> Management decided to stick to 3.
> They also be
ter any major issues. Above
all, note that it's passed beta status already.
Francis
On 4/4/06, Bode, Bianca <[EMAIL PROTECTED]> wrote:
>
> We're on a project where a few developers already had some experience
> with 3.
> Unfortunately none of them could help me with this
Hi all,
I have created a component, that renders some plain html, with
parameters:
And component:
Now, depending on the 'editable' parameter I want the type of my 'city'
component to be either
'Insert' when 'editable' is false or 'TextField' when 'editable'is true.
Can this be d
.jwc?
I think you want to provide both in your template, and wrap them with
appropriate Conditional components:
Then in your template:
-Mike
On 4/5/06, Bode, Bianca <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have created a component, that ren
for just
these types of scenerios. (there should be a 3.X series component
reference in the 3.X pages as well)
http://jakarta.apache.org/tapestry/tapestry/ComponentReference/RenderBlo
ck.html
On 4/5/06, Bode, Bianca <[EMAIL PROTECTED]> wrote:
>
> I started out like this, but that requi
additional typing is limited to specifying the editable prameter. If
your new component was called MaybeEdit, your view components would be
declared as follows:
Thus the only difference is passing in the editable param.
On 4/5/06, Bode, Bianca <[EMAIL PROTECTED]>
Hi all,
I have a lot of images on another server that need to be incorporated in
my application.
Instead of defining the external assets on every page I need them, can I
have them all in one 'properties' file and reference them from there?
Kind regards, Bianca
---
Hello all,
I'm currently working on a page on which I have a nested Contrib:Table
component and it works not as expected.
Now I'm not sure if I am doing something wrong, or that this is
happening because of the nesting..can anyone help me?
The .html file has two tables that use the Contrib:Table
I will not be able to read and reply to your answers untill Friday as I
have to leave now.
Just to let you know that I'm not being inpolite here ;)
-Original Message-
From: Bode, Bianca
Sent: woensdag 19 april 2006 17:28
To: Tapestry users
Subject: Nested Contrib:Table - st
Hi all,
I was wondering if anyone has ever done the following, and if so, how :)
The situation is pretty complex, but basically it comes down to this:
I want to validate an Insert component, but only if another component, a
CheckBox, is checked...
Anyone?
Kind regards, Bianca.
If you have set the ASO in the hivemodule.xml like this:
You can inject it in a page like this:
Add this to your class:
public abstract Visit getVisitObject();
Now you can access the object in a method like this:
Visit v = getVisitObject();
Don't know if this is what you meant
The validator doesnt reject it because 'choice' is a value as well, and
thus valid. A validator cannot on it is own determine that 'choice' is
an invalid value for a 'gender' field
Besides that you also need to set an actual validator on your
PropertySelection component, otherwise it will never wor
e this... on the front
end... I think it was something like ...
Tony.
> -Original Message-
> From: Bode, Bianca [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 29 April 2006 1:34 a.m.
> To: Tapestry users
> Subject: Conditional validation
>
> Hi all,
>
> I
16 matches
Mail list logo
