t;
> h) Is this correct? And have I done everything that I need to?
>
> Regards,
> Daniel P.
>
>
> -Ursprüngliche Nachricht-
> Von: Charlouze [mailto:m...@charlouze.com]
> Gesendet: Donnerstag, 23. April 2015 15:48
> An: Tapestry users
> Betreff: Re: AW: AW: Splitt
che Nachricht-
Von: Charlouze [mailto:m...@charlouze.com]
Gesendet: Donnerstag, 23. April 2015 15:48
An: Tapestry users
Betreff: Re: AW: AW: Splitting a tapestry web app into modules
I"m using JPA 2.1 and:
http://java.sun.com/xml/ns/persistence"; version="1.0">
Le jeu.
uot;;>
>
> Okay, do I have to regress back to JPA 2.0? Or can I still use 2.1 via
> changes to the persistence.xml?
>
> Regards,
> Daniel P.
>
> -----Ursprüngliche Nachricht-----
> Von: Poggenpohl, Daniel [mailto:daniel.poggenp...@isst.fraunhofer.de]
> Gesendet: Don
to regress back to JPA 2.0? Or can I still use 2.1 via changes
to the persistence.xml?
Regards,
Daniel P.
-Ursprüngliche Nachricht-
Von: Poggenpohl, Daniel [mailto:daniel.poggenp...@isst.fraunhofer.de]
Gesendet: Donnerstag, 23. April 2015 13:47
An: Tapestry users
Betreff: AW: AW: AW:
The @PersistenceContext annotation is like the @Inject for EM. If you have
only one persistence unit, you don't need to use it, the EM will be passed
to the constructor by the registry. If you have multiple persistence unit
as it seems that you do, you have to annotate the constructor parameter
wit
On Thu, 23 Apr 2015 08:46:53 -0300, Poggenpohl, Daniel
wrote:
Hi,
thank you for your time, but I still have more questions...
e) Are the [...]Module classes to be placed in the services package in
the Tapestry app module?
The package doesn't matter, unless in the case described below.
f
ailto:m...@charlouze.com]
Gesendet: Donnerstag, 23. April 2015 13:22
An: Tapestry users
Betreff: Re: AW: AW: Splitting a tapestry web app into modules
Yep it's correct and no, there isn't any order.
Each of your modules should have its own ModuleNameModule class. This class
should contain a
AppModule that I
> read about?
> >
> > Regards,
> > Daniel P.
> >
> > -----Ursprüngliche Nachricht-
> > Von: Charlouze [mailto:m...@charlouze.com]
> > Gesendet: Donnerstag, 23. April 2015 11:37
> > An: Tapestry users
> > Betreff: Re: AW: AW: Splittin
il 2015 11:54
An: Tapestry users
Betreff: Re: AW: AW: Splitting a tapestry web app into modules
If your service is bound to the registry via a ServiceBinder then it should.
Le jeu. 23 avr. 2015 à 11:50, Poggenpohl, Daniel <
daniel.poggenp...@isst.fraunhofer.de> a écrit :
> Hi,
>
>
:37
> An: Tapestry users
> Betreff: Re: AW: AW: Splitting a tapestry web app into modules
>
> Hey !
>
> You can define your DAO as service and get any other services you need in
> your DAO by adding parameters to your DAO constructor.
>
> Le jeu. 23 avr. 2015 à 11:23,
[mailto:m...@charlouze.com]
Gesendet: Donnerstag, 23. April 2015 11:37
An: Tapestry users
Betreff: Re: AW: AW: Splitting a tapestry web app into modules
Hey !
You can define your DAO as service and get any other services you need in your
DAO by adding parameters to your DAO constructor.
Le jeu. 23
ther simple way or do I have to manually create the EntityManager?
>
> (I know that I can add a dependency to tapestry5-annotations)
>
> Regards,
> Daniel P.
>
> -Ursprüngliche Nachricht-
> Von: Charlouze [mailto:m...@charlouze.com]
> Gesendet: Mittwoch, 22. April 2015
: Splitting a tapestry web app into modules
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
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
--Original Message-
From: Poggenpohl, Daniel [mailto:daniel.poggenp...@isst.fraunhofer.de]
Sent: Mittwoch, 22. April 2015 15:53
To: Tapestry users
Subject: AW: AW: Splitting a tapestry web app into modules
Hello,
I'm gonna pick up this strand because more problems seem to arise when
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
nd of the controller method, as this is a more logical
> point in time.
> So do I add the tapestry-jpa dependency to my controller methods? And what
> then? Do I have to register my controller as a service with Tapestry?
>
> Hope you can help me, as I'm a little bit confused.
&g
Nachricht-
Von: Thiago H de Paula Figueiredo [mailto:thiag...@gmail.com]
Gesendet: Donnerstag, 16. April 2015 18:08
An: Tapestry users
Betreff: Re: AW: Splitting a tapestry web app into modules
On Thu, 16 Apr 2015 11:09:53 -0300, Poggenpohl, Daniel
wrote:
> Hello again,
>
> I think I
On Thu, 16 Apr 2015 11:09:53 -0300, Poggenpohl, Daniel
wrote:
Hello again,
I think I understand now.
The only problem I see at the moment is that once I split the app into
model and tapestry app, I can't use e.g. @NonVisual or @Validate
anymore because those are Tapestry-specific. Or c
Hello again,
I think I understand now.
The only problem I see at the moment is that once I split the app into model
and tapestry app, I can't use e.g. @NonVisual or @Validate anymore because
those are Tapestry-specific. Or could I add a dependency to the annotation
packages? If the model woul
Hi,
I'm not sure I get how you do it.
Reading up on
http://tapestry.apache.org/ioc.html
http://tapestry.apache.org/starting-the-ioc-registry.html
http://tapestry.apache.org/registry-startup.html
I'm not connecting what is described with my problem yet.
Perhaps using an example would help me.
Let'
Hi,
I'm using tapestry-jpa.
I've found a reference to JpaEntityPackageManager. I can contribute package
names, but can I contribute packages in other projects?
Regards,
Daniel P.
-Ursprüngliche Nachricht-
Von: Charlouze [mailto:m...@charlouze.com]
Gesendet: Donnerstag, 16. April 2015 1
22 matches
Mail list logo
