Or instead of putting the code in the constructor you can create an
eagerly loaded build-method which instantiates the service, calls the
method and then returns the service instance.
Something like this:
@EagerLoad
public static PricelistHandler buildPricelistHandler(@Inject
Hello,
the beaneditform provides a method recordError which expects a field of
the form. I couldn't find out, how I can get a reference to a field
of the form.
I would like to call
myForm.recordError(myInputField, bad problem);
--
Best Regards / Viele Grüße
Sebastian Hennebrueder
-
That's not 100% correct. @Component defines a component in your
component class that you can then use in your template while
@InjectComponent injects a component defined in your template.
Cheers,
Uli
Kalle Korhonen schrieb:
How do you reference your myForm? All components are handled the
Yeah, doing work inside a constructor isn't really a good way to go,
in general. It makes things very hard to test.
I can't remember, however - is there any lifecycle management in T5-
ioc? Can you mark something as an initialization method, so that
before it's presented to a calling
Hi everyone:
I have a problem with beandisplay. I tried at first the most easy version, and
appeared the information of only some fields. My problem is that the Long
Objects from the methods I use don't appear on the screen neither their labels.
I have some date on Calendar Object and it
Hi, i know that there are developers much more actively using Tapestry
than me but...i'm just a poor guy asking for a christmas gift :-).
gift 1 - t:else
gift 2 - t:elseif
gift 3 - t:contains value_to_check_if_it_exists, array_to_check
gift 4 - t:greaterThan
gift 5 - t:greterThanOrEqual
gift 6
Hello Martin,
I think you need to provide the bean as well.
--
Best Regards / Viele Grüße
Sebastian Hennebrueder
-
Software Developer and Trainer for Hibernate / Java Persistence
http://www.laliluna.de
Martin Torre Castro schrieb:
Hi everyone:
I have a problem with beandisplay. I tried
Christmas comes early this year: use the ognl binding from chenillekit
(http://www.chenillekit.org/chenillekit-tapestry/ognlbinding.html). Be
a good boy now.
Kalle
On Sat, Aug 22, 2009 at 9:23 AM, akirawilsonaik...@gmail.com wrote:
Hi, i know that there are developers much more actively using
Oks, Sebastian, this is the class of 'incid'. Here you are. I'm sorry about
the format, but hotmail's editor sucks :-(
@Entity
public class Incidencia {
private Long numIncidencia;
private String nombre;
private Calendar date;
private String desc;
private Empleado empAlta,
Oh that - you need tell the bean editor that you want the field to be
used in your form. See Property Editor Overrides at
http://tapestry.apache.org/tapestry5.1/guide/beaneditform.html, e.g:
t:beaneditform object=formModel
t:parameter name=country
t:label for=country/
I found this solution 5 minutes ago but thought it was a workaround. To
allow cross field validation, it would be nice
if the beaneditform provides access to the fields uses internally.
What do you think?
--
Best Regards / Viele Grüße
Sebastian Hennebrueder
-
Software Developer and Trainer
An eagerly loaded build-method works beautifully! Thank you so much!
On Sat, Aug 22, 2009 at 10:56 AM, Christian Edward
Gruberchristianedwardgru...@gmail.com wrote:
Yeah, doing work inside a constructor isn't really a good way to go, in
general. It makes things very hard to test.
I can't
I don't see it as a workaround considering that you'd do exactly the
same if it was a regular form. However, I suppose it'd be entirely
possible and likely even easy to implement a getField(String
propertyName) for BeanEditForm. Maybe open an issue for it?
Kalle
On Sat, Aug 22, 2009 at 10:54
You can also mark the class as @EagerLoad, and mark method(s) to
execute as @PostInjection.
On Fri, Aug 21, 2009 at 11:53 PM, Joakim Olssonargo...@lingonpaj.com wrote:
Or instead of putting the code in the constructor you can create an
eagerly loaded build-method which instantiates the service,
For cross field validation it would be nice if the Form object allowed
you to mark multiple fields with a single validation failure.
Currently, the only way I can see to do this is to either create two
validation errors, one for each field (so that they are decorated
properly). However, if you
In BeanEditForm, if your setters are private then the field won't be
shown. I realize that you are using BeanDispaly (which I am not very
familiar with), but maybe it is using similar logic. Are the missing
fields properties which have a non public or non existent setter? If
so, try making a
Kalle, i know that (i googled, looked to the top 20 results and
found on the mailing list), but to a newbie (me) the ognl it's the
same thing as Oh no, more one thing to learn, it's not that
difficult but a newbie will google and not find the answer on the T5
site but on the mailing list
17 matches
Mail list logo
