hey !
here is my thoughts about your concerns :
a) controllers should be services that are bound to the registry in a
ControllerModule class.
b) persistence.xml file should probably be in your dao-hibernate module.
You can configure where to find this file in a Module class.
c) thiago already a
Hi Daniel,
not quite sure what exactly you mean by Controller but it sounds like what you
would do in a Tapestry Page or Component class. If so, I'd pack that with the
webui stuff. @CommitAfter will work on Tapestry Page and Component Methods.
The last project I set up had the following division
On Wed, 22 Apr 2015 10:53:01 -0300, Poggenpohl, Daniel
wrote:
Hello,
Hi!
First, to be generic with my DAO interfaces, I can't use @CommitAfter on
them, because then I'd need a dependency to tapestry-jpa.
If you use 5.4-beta-22 or up, you don't need to put the annotation in the
interf
I make extensive use of multi maven modules (even a war overlay!) in my
project. Maybe browsing through the code can help you.
Since we are making a reusable core set of modules (under graphene-parent),
each customer implementation gets it's own separate maven project that uses
our stuff as depend
We're using inheritance to avoid duplication and inheritance is a supported
pattern in tapestry - So I would not expect this to break by updating to
the latest 5.4 beta.
@Michael - I've though about the signatures, but it have been working up
until now. It just seems odd that the "onActivate" nami
Hello,
I'm gonna pick up this strand because more problems seem to arise when
splitting the application...
Okay, right now I have 5 modules/projects:
1) model (the data model for the application; annotated using the Bean
Validation API)
2) dao-interfaces (the DAO interface layer for the data mo
I wonder if it might have something to do with the superclass signature
being:
void activate(EventContext)
and the subclass signature being:
Object activate(EventContext)
I know I've used similar patterns in 5.3, but haven't tried in 5.4 yet.
mrg
On Wed, Apr 22, 2015 at 6:56 AM, Chris Poulse
Possibly a sign you should be using composition instead of inheritance ;)
Hi,
We have an abstract parent class with an activation handler declared like
this:
@OnEvent( EventConstants.ACTIVATE )
void activate( EventContext ec ) (Called)
And an extending class with an activation handler declared like this:
@OnEvent( EventConstants.ACTIVATE )
Object activate( EventConte
