Hi chris, thanks for the reply.
On Sun, Nov 4, 2018 at 8:19 PM Chris Poulsen wrote:
>
> With a few exceptions, I would generally say that using @Persist in
> components is a smell, instead pass the information as a parameter - Pages
> are ultimately the things driving the components, they shoul
Hi
It sounds like you are attempting to do something in a way that may not be
ideal (judging from all the hoops you are trying to jump through).
In Tapestry you can usually get really far using the simple building blocks
that are provided. With a few exceptions you are usually taking a bad
course
Hi Thiago,
This component is some ui that we extract from few common pages. It shows a
series of tabs. Each tabs has its own related Hibernate Entity. We don't
pass all the tabs entity as parameter to the component. Instead we just
pass the root component and let the rest of the tab get their enti
Hello!
What exactly is this component trying to do? I couldn't get it by looking
at your code snippet.
Anyway, the probably best way of doing it if you want to create a component
which edits something is to subclass AbstractField.
The error message says you're trying to pass a null object to Bea
Hai guys, still working on my custom component.
How do we let our custom component participate in form submission.
Apparently there is no onPrepare hook for tapestry custom component.
http://tapestry.apache.org/component-rendering.html.
I'm reading
http://jumpstart.doublenegative.com.au/jumpstart
