; I would like to share with you a new small tapestry5 library that may be
> > helpful for tapestry JPA applications:
> >
> > https://github.com/satago/tapestry-jpa-transactions
> >
> > 1) It overrides @CommitAfter annotation with support for nested calls
> (on
are with you a new small tapestry5 library that may be
> helpful for tapestry JPA applications:
>
> https://github.com/satago/tapestry-jpa-transactions
>
> 1) It overrides @CommitAfter annotation with support for nested calls (only
> top-most method will actually commit transaction)
rapped in a
> TransactionalUnit?
>
> I look forward to testing out your library when time permits.
>
> Thanks
> Tony
>
> > On Jul 23, 2015, at 5:03 PM, Dmitry Gusev
> wrote:
> >
> > Hello Tapestry users!
> >
> > I would like to share
@CommitAfter get wrapped in a TransactionalUnit?
I look forward to testing out your library when time permits.
Thanks
Tony
> On Jul 23, 2015, at 5:03 PM, Dmitry Gusev wrote:
>
> Hello Tapestry users!
>
> I would like to share with you a new small tapestry5 library that may be
> helpfu
Hey !
All those features seems nice... I'll take a look at it !
Thanks a lot.
Cheers
Le jeu. 23 juil. 2015 à 23:05, Dmitry Gusev a
écrit :
> Hello Tapestry users!
>
> I would like to share with you a new small tapestry5 library that may be
> helpful for tapestry JPA applic
Hello Tapestry users!
I would like to share with you a new small tapestry5 library that may be
helpful for tapestry JPA applications:
https://github.com/satago/tapestry-jpa-transactions
1) It overrides @CommitAfter annotation with support for nested calls (only
top-most method will actually
Charlouze,
I worked on a world class backbone (meaning multi flavored request broker
rmi/ejb/corba hostname:port ) for integrating supply chains bidders amidst a
slew of Javascript apps...
In our applications... we performed transactions... responsibly.
To say I am uncomfortable with tynamo's
Original Message-
> > From: Charlouze [mailto:m...@charlouze.com]
> > Sent: Thursday, September 25, 2014 9:56 AM
> > To: Tapestry users
> > Subject: Re: Tapestry-jpa commitAfter advisor problem
> >
> > @Chris: I'm using 5.4 and I don't really want to use
I was just trying to give you an easy option. It has worked well for me.
YMMV.
Tony
> -Original Message-
> From: Charlouze [mailto:m...@charlouze.com]
> Sent: Thursday, September 25, 2014 9:56 AM
> To: Tapestry users
> Subject: Re: Tapestry-jpa commitAfter advisor pro
>
> Tony
>
> > -Original Message-
> > From: Chris Mylonas [mailto:ch...@opencsta.org]
> > Sent: Thursday, September 25, 2014 9:43 AM
> > To: Tapestry users
> > Subject: Re: Tapestry-jpa commitAfter advisor problem
> >
> > I only know EJB/JPA bu
.
Tony
> -Original Message-
> From: Chris Mylonas [mailto:ch...@opencsta.org]
> Sent: Thursday, September 25, 2014 9:43 AM
> To: Tapestry users
> Subject: Re: Tapestry-jpa commitAfter advisor problem
>
> I only know EJB/JPA but I'm sure some people will say Sp
I only know EJB/JPA but I'm sure some people will say Spring. I prototype
in tapestry-hibernate because the docs were easier at the time to use than
tapestry-jpa, and when I hit nesting problems that's when I switch to using
the @EJB annotation.
I need to switch to tapestry-jpa
Thx for your quick answer.
My method2 can be used in a "stand-alone way" so removing @CommitAfter is
not an option. I could get around the problem with another method called by
both method 1 and 2 but it'll bring mess to my code having one method that
commits the transaction and another one that d
The @CommitAfter annotation should be used as a convenience for simple
scenarios, it doesn't support nesting. This has been discussed many times
in the past on this mailing list.
For the scenario that you described, I would remove the @CommitAfter
annotation from method2, this way all of the code w
Hey everyone
Here is my problem :
I have a service (service1) that has a method (method1) which has the
@CommitAfter annotation in order for tapestry to take care of the
transaction.
I have a second service (service2) that has a method (method2) which also
has the @CommitAfter annotation.
service
gs to keep in mind
>
> 1. To be consistent with tapestry-hibernate, a new gradle submodule for
> tapestry-jpa-core is required. This will only have tapestry-ioc as a
> dependency. This will contain JpaCoreModule and the core jpa services.
>
> 2. tapestry-jpa-core needs a jar manif
> What is the procedure for me to provide a patch ? Developing it and
creating an issue with the patch attached ?
That's a great start.
Some things to keep in mind
1. To be consistent with tapestry-hibernate, a new gradle submodule for
tapestry-jpa-core is required. This will only have
re quite similar. What
is the procedure for me to provide a patch ? Developing it and creating an
issue with the patch attached ?
2014-07-17 23:05 GMT+02:00 Lance Java :
> I think it's a good idea to split tapestry-jpa in the same way as
> tapestry-hibernate.
>
> See HibernateCore
I think it's a good idea to split tapestry-jpa in the same way as
tapestry-hibernate.
See HibernateCoreModule and HibernateModule to see how it's split.
On 17 Jul 2014 21:47, "Charlouze" wrote:
> I will do what you said but maybe i could open a ticket for this issue an
What are you instantiating in tapestry-jpa that needs context? To test your
persistence layer, you should only need an entityManager. You could have
something like this as a base class for unit testing:
public abstract class BasePersistenceTest {
private static Class[] entities = new Class
You might find this stack overflow question useful, it's about
tapestry-hibernate but has some parallels.
http://stackoverflow.com/questions/15664815/how-to-test-dao-layer-in-tapestry-dependent-projects
On 17 Jul 2014 21:32, "Lance Java" wrote:
> Ah, I haven't u
I will do what you said but maybe i could open a ticket for this issue and
propose a patch for tapestry-jpa, what do you think ?
2014-07-17 22:32 GMT+02:00 Lance Java :
> Ah, I haven't used tapestry-jpa myself. tapestry-hibernate is split into
> two modules to allow for this type
Ah, I haven't used tapestry-jpa myself. tapestry-hibernate is split into
two modules to allow for this type of testing.
If this is the case, you may need to override ApplicationGlobals and
provide a mock ServletContext as I said initially.
On 17 Jul 2014 17:37, "Charlouze" w
I have separated modules for the service tier and the web tier but
tapestry-jpa requires tapestry web modules... IMO, it should not but that's
the way it is (maybe JpaModule should be divided into two modules). Anyway,
I would have the same problem with beanvalidation module.
I'll take
t;> I'm currently setting up an application using T5.4-b13. For unit testing,
>> I
>> use junit, unitils-dbunit, spock (with spock-tapestry and spock-unitils
>> extension).
>>
>> In my specification I added @submodule annotation with every needed module
>>
ion I added @submodule annotation with every needed module
> (Tapestry, Jpa, beanValidator and my custom module).
>
> My problem is that there are no context and therefore, my tests do not pass
> the assert context != null in ContextResource class constructor. Does
> anyone know what can I do ?
>
> Thanks in advance
>
> Charles.
>
Hello everyone.
I'm currently setting up an application using T5.4-b13. For unit testing, I
use junit, unitils-dbunit, spock (with spock-tapestry and spock-unitils
extension).
In my specification I added @submodule annotation with every needed module
(Tapestry, Jpa, beanValidator and my c
I am trying to convert to Glassfish 4 (JEE7) and having problems with Tapestry
JPA.
JEE 7 has a new default data source:
https://blogs.oracle.com/arungupta/entry/default_datasource_in_java_ee
Apparently, Tapestry-JPA is now using that datasource for all database queries,
even if I specify a
Thanks, that's good news - do you know any example I can base my work on?
John
- Original Message -
From: Dimitris Zenios
To: Tapestry users
Sent: Sunday, June 09, 2013 8:10 AM
Subject: Re: Tapestry JPA
You car write your own advisor on top of commit after and if c
You car write your own advisor on top of commit after and if commit after
didnt throw an exception you can call your success listeners.
On Sun, Jun 9, 2013 at 12:02 AM, John wrote:
> Hi,
>
> I want to audit the database updates in some DAO classes I am using from
> my pages.
>
> Obviously I'd o
Hi,
I want to audit the database updates in some DAO classes I am using from my
pages.
Obviously I'd only want to fire the auditing if the updates are commited
successfully.
I already have some of the nastiness below in my DAO interfaces
@CommitAfter
@PersistenceContext(unitName = "AuditD
If you use Tynamo Security + Apache Shiro then you can get current
authenticated subject via static context:
org.apache.shiro.SecurityUtils.getSubject()
http://tynamo.org/tapestry-security+guide
On Fri, May 31, 2013 at 5:00 PM, John wrote:
> Hi,
>
> Is there a way of obtaining the logged in
Hi,
Is there a way of obtaining the logged in username from the http session and
somehow getting that into JPA so I can log who is making changes inmy DAO layer?
I'm trying to integrate using the EclipseLink history classes but these are all
in the JPA layer.
regards,
John
please see/feedback https://issues.apache.org/jira/browse/TAP5-2029
- Original Message -
From: Thiago H de Paula Figueiredo
To: Tapestry users
Sent: Monday, November 19, 2012 5:48 PM
Subject: Re: Tapestry jpa transactions
On Mon, 19 Nov 2012 14:45:48 -0200, John wrote
Sounds like you should be using the full JEE stack. We use it along with Shiro
security
And we have custom menu components ( was very easy to create ) that do what you
are trying to do.
On Nov 19, 2012, at 11:45 AM, "John" wrote:
> In the tapestry jpa docs we are instruct
On Mon, 19 Nov 2012 14:45:48 -0200, John wrote:
In the tapestry jpa docs we are instructed to provide annotations to
manage transaction commitment into the DAO interface classes, e.g.
@CommitAfter
@PersistenceContext(unitName = "DemoUnit")
void add(User user);
I'm
In the tapestry jpa docs we are instructed to provide annotations to manage
transaction commitment into the DAO interface classes, e.g.
@CommitAfter
@PersistenceContext(unitName = "DemoUnit")
void add(User user);
I'm not liking this much as I don't want to ex
cure/attachment/12553649/TapestryJPATest.zip
>
> It reproduces the problem and you can see how I code my DAOs.
>
> John
> - Original Message -
> From: Lenny Primak
> To: Tapestry users
> Sent: Wednesday, November 14, 2012 3:44 PM
> Subject: Re: tapestry
ginal Message -
From: Lenny Primak
To: Tapestry users
Sent: Wednesday, November 14, 2012 3:44 PM
Subject: Re: tapestry-jpa EntityManagerObjectProvider fixes entities not
associated with correct entity manager issue
Perhaps. I just tested two pages with one PU each (different PUs
t; - Original Message -
> From: Lenny Primak
> To: Tapestry development
> Sent: Wednesday, November 14, 2012 3:19 AM
> Subject: Re: PATCH: tapestry-jpa EntityManagerObjectProvider fixes entities
> not associated with correct entity manager issue
>
>
> I ju
This looks like a bug where a class member variable is used to cache the
EntityManager that is subsequently handed to all the PersistenceContext
annotations regardless of the unitName, like I said.
The following replacement class is tested working and handles multiple
persistence units correctl
53)> at
org.mortbay.jetty.servlet.Context.startContext(Context.java:140)> >
----- Original Message - > From: Lenny Primak > To: Tapestry
users > Sent: Monday, November 12, 2012 3:39 PM> Subject: Re:
tapestry-jpa entities not associated with correct enti
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
> 50)
>at
> org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.ja
> va:653)
>at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
>
> - Original Message
: Tapestry users
Sent: Monday, November 12, 2012 3:39 PM
Subject: Re: tapestry-jpa entities not associated with correct entity manager
Yes, I have multiple PUs working correctly, using Glassfish and the FlowLogix
library:
Here are some references:
http://code.google.com/p/flowlogix/wiki
I put some system out in JpaInternalUtils and it associates the wrong PU with
the annotation I have in the service class when it instantiates.
John
- Original Message -
From: Lenny Primak
To: Tapestry users
Sent: Monday, November 12, 2012 3:40 PM
Subject: Re: tapestry-jpa
;
> When I output the
> jabberEntityManager.getEntityManagerFactory().getProperties() I find they are
> the configs for another PU. That is my problem!
>
> It looks like tapestry-jpa is not processing the context tags correctly? The
> PU that gets used first is just handed to lat
vate static final long serialVersionUID = 803545730972339902L;
>
> @Id
> @Column(name = "username")
> private String username;
> - Original Message -
> From: Lenny Primak
> To: Tapestry users
> Cc: Tapestry users
> Sent: Sunday, November 11, 20
@Inject
@PersistenceContext(unitName = "JabberDBUnit")
private EntityManager jabberEntityManager;
When I output the jabberEntityManager.getEntityManagerFactory().getProperties()
I find they are the configs for another PU. That is my problem!
It looks like tapestry-jpa is not proc
om: Lenny Primak
To: Tapestry users
Cc: Tapestry users
Sent: Sunday, November 11, 2012 4:30 PM
Subject: Re: tapestry-jpa entities not associated with correct entity manager
I would suggest either using or looking at FlowLogix tapestry library
It has a jpa package that takes care of usin
estry users
Sent: Sunday, November 11, 2012 4:30 PM
Subject: Re: tapestry-jpa entities not associated with correct entity manager
I would suggest either using or looking at FlowLogix tapestry library
It has a jpa package that takes care of using multiple persistence units in
one applic
I would suggest either using or looking at FlowLogix tapestry library
It has a jpa package that takes care of using multiple persistence units in one
application.
The key is to have entities with different PUs in different packages.
On Nov 11, 2012, at 3:49 AM, "John" wrote:
> I'm finding tha
I'm finding that entities are not being attached to the correct entity manager
even though they are indicated in the persistence.xml.
This manifests that if the user logs in first which uses AuditDBUnit then the
entities in JabberDBUnit are not available. If the JabberDBUnit is used first,
enti
kovic
To: Tapestry users
Sent: Wednesday, November 07, 2012 8:23 PM
Subject: Re: Tapestry JPA + Stored Procedures
Hi,
you can inject the session directly. please take a look at the
documentation.
G,
Kris
Am 07.11.2012 09:31 schrieb "John" :
> I got the JPA(with ec
Hi,
you can inject the session directly. please take a look at the
documentation.
G,
Kris
Am 07.11.2012 09:31 schrieb "John" :
> I got the JPA(with eclipselink) to work and have been using
> @NamedStoredProcedureQuery annotations in entities to obtain entity classes
> successully from SQLServer.
I got the JPA(with eclipselink) to work and have been using
@NamedStoredProcedureQuery annotations in entities to obtain entity classes
successully from SQLServer. This technique doesn't seem to work well or fit the
situation where the stored proc just returns output parameters (no entity class
missing something, either some dependency or some
setup code for making it run in a NON-webapp environment.
Could you give me some advise?
Best regards,
Matias.
On Tue, Oct 2, 2012 at 6:30 PM, Matías Blasi wrote:
> Hi everybody,
>
> I am trying to set a POC application with Tapestry-JP
Hi everybody,
I am trying to set a POC application with Tapestry-JPA.
I just have a couple of entities, services, and tests.
This is not a webapp (yet), I'm just starting the registry manually from my
test, I did it before, but now something is not working, I dont know if
something has ch
Anyone?
On Tue, May 22, 2012 at 6:43 PM, Dimitris Zenios
wrote:
> Hi guys i think there is a bug in tapestry-jpa and value encoder
>
> In a discussion i was reading, Howard changed valueEncoder of
> tapestry-hibernate to return null in toClient if the id of the object
> was nu
Hi guys i think there is a bug in tapestry-jpa and value encoder
In a discussion i was reading, Howard changed valueEncoder of
tapestry-hibernate to return null in toClient if the id of the object
was null.That was use full in cases where we wanted to have the same
page for save/edit.
Quote from
If your code or the code you are testing is using context assets
(which tapestry-jpa does), you need to set the context:
ApplicationGlobals globals =
registry.getObject(ApplicationGlobals.class, null);
globals.storeContext(new PageTesterContext(contextPath
Not sure how tapestry-jpa handles un-persisted instances. That is certainly
another area where tapestry-hibernate does not give you a useable ValueEncoder.
To clarify my last post: tapestry-hibernate will give you a functional default
value encoder if:
1) The entity has a single column pk
2
mponent to
use. I was hoping to get away from writing custom value encoders for simple
component implementations like the one stated above.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-jpa-5-3-vs-Tapestry-Hibernate-tp5566580p5566606.html
Sent from the Tapes
Disclaimer: I haven't used tapestry-jpa. :)
But, Tapestry uses value encoders. tapestry-hibernate uses them, tapestry-jpa
uses them.
Tapestry uses them. The only question is whether you need to write custom value
encoders.
tapestry-hibernate will provide default encoders for entities w
Hello everyone, I figured it's been a while since this topic has been brought
up, so I'd like to come back to it again. I've finally managed to find some
free time to play with my personal project "yay", which means I'll be doing
a full rewrite. I'd like to hear
Hi,
I am using the spock snapshot (0.6) and when tapestry-jpa (5.3.2) is added,
I am getting this error:
--- excerpt
java.lang.RuntimeException: Exception constructing service
'RegistryStartup': Error invoking service contribution method
org.apache.tapestry5.jpa.JpaModule.st
Hello again,
I sorted the problem thanks to Igor's help as follows:
Thanks,
Julien.
2011/10/21 Julien Martin
> Igor,
> Here is the page:
>
> *public class InscriptionProfessionnelGardeEnfant {*
> *
> *
> *@Property*
> *@Persist*
> *@Valid*
> *private ChildminderAccount childmi
Igor,
Here is the page:
*public class InscriptionProfessionnelGardeEnfant {*
*
*
*@Property*
*@Persist*
*@Valid*
*private ChildminderAccount childminderAccount;*
*
*
*@Property*
*private SelectModel childminderStatusSelectModel;*
*
*
*@Inject*
*private SelectModelFa
Either the object graph is not traversed or your ChildminderAccount object
is null. The @Valid annotation is ignored for null objects. Please post the
entire page class and template. You can also pass childminderAccount to the
Form's validate parameter.
On Thu, Oct 20, 2011 at 9:53 PM, Julien Mart
up
2011/10/20 Julien Martin
> Hi Igor,
>
> Yes I do use the form component as follows:
>
> From the class:
> *@InjectComponent*
> *private Form childminderRegistrationForm;*
> *
> *
> From template:
> *clientValidation="none">*
>
> Julien.
>
> 2011/10/20 Igor Drobiazko
>
>> Please m
Hi Igor,
Yes I do use the form component as follows:
>From the class:
*@InjectComponent*
*private Form childminderRegistrationForm;*
*
*
>From template:
* *
Julien.
2011/10/20 Igor Drobiazko
> Please more details. "one of my Tapestry classes" is not precise enough to
> identify the
Please more details. "one of my Tapestry classes" is not precise enough to
identify the problem. You are using the Form component, right? Did you use
the Form's validate parameter?
On Thu, Oct 20, 2011 at 9:30 PM, Julien Martin wrote:
> Hello,
>
> I have the following property in one of my Tapes
Hello,
I have the following property in one of my Tapestry classes:
*@Property*
*@Persist*
*@Valid*
*private ChildminderAccount childminderAccount;*
The ChildminderAccount entity extends an abstract Account entity class as
follows:
* public class ChildminderAccount extends Ac
OK i think i found it.
The constructor gets called but propertyAdapter is null.In order to
fix it had to change idAttribute.getJavaMember().getName(); to
idAttribute.getName(). I dont know if it matters but the annotations
in my entity are placed on the methods and not on the properties.
On Mon
It seems there is a problem with Tapestry JPA.From what i can tell,
value encoder does not work.I am using tapestry 5.3 beta 22.toClient
of value encoder is not called and if i go to the page by hand in
order to force toValue method then i get this exception
org.apache.tapestry5.runtime.Componen
have added tapestry-jpa, ejb3 and eclipselink dependencies. I have a
persistence.xml, I have edited the web.xml, and everything as in the example. I
run my app with runjettyrun in Eclipse. I have tried with postgres and H2, but
that doesn't seem to make a difference. I don't see an eclip
th ago about getting the example app running as
> explained here: http://tapestry.apache.org/integrating-with-jpa.html
>
> I have put version 5.3.0 in my pom, so it downloads Tapestry 5.3.0 including
> jpa. I have added tapestry-jpa, ejb3 and eclipselink dependencies. I have a
> pe
Hi,
I read the messages from a month ago about getting the example app
running as explained here:
http://tapestry.apache.org/integrating-with-jpa.html
I have put version 5.3.0 in my pom, so it downloads Tapestry 5.3.0
including jpa. I have added tapestry-jpa, ejb3 and eclipselink
I ran into a case where the whole tapestry web app fails to start if it is
unable to log into any database.I believe it should be resilient enough to be
able to at least catch the failure in a nice error page.Right now, if
EclipseLink fails to initialize, the whole web app, whether it relies on
Well, I have never used Hibernate, so the 'conformance' is foreign to me.
When developing 'pure' EJB apps in the past, the default I don't need to worry
about putting my entities in a certain place, I guess it is confusing when
coming
from a pure EJB development to tapestry, because this behavior
Currently, Tapestry excludes the unlisted managed classes. The
tag in the persistence descriptor is ignored, so that the following method
always returns true.
http://download.oracle.com/javaee/5/api/javax/persistence/spi/PersistenceUnitInfo.html#excludeUnlistedClasses%28%29
The reason is: I'm n
Just curious... how do they get instrumented?
Are there any side-effects of not putting them into a package that Tapestry
knows about?
Thanks!
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional command
We solved a similar problem by creating a view that calculated the field
instead of using a transient field.
Then we just mapped the view as a read only object and all the sorting worked.
-Tony
On Jul 11, 2011, at 7:28 PM, Richard Yunhua Sang wrote:
> Thanks for your reply, but I do want to so
Imagine the implementation
if(there_is_a_transient_field)
{
populate_all_data();
sort_yourself_based_on_sort_constraint();
paginate();
}
else
{
pass_the_paging_and_sort_constraints_to_jpa();
}
Instead you already have a JPAGridDataSource and you can have your own
JPAInMemoryGridDataSo
Hi Taha,
I have no problem to write a new GridDataSource to do such thing; but as I
said, it would be good to have this function in JPAGridDataSource.
e.g.
@Entity
public class Student {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
private String fir
Hi Richard,
Internally JPAGridDataSource does not handle sorting itself, instead it
delegates it to JPA and transient values are unknown to JPA. If you want to
handle transient values, you will have to write you own implementation of
GridDataSource where in you can retrieve all the rows from the d
HI Igor,
I have a small Maven project to demonstrate this problem, can I send it as a
zip file to your personal gmail address?
Thanks,
Yunhua
On Mon, Jul 11, 2011 at 5:19 PM, Igor Drobiazko wrote:
> Can you please provide more details? Perfectly some source code to
> reproduce
> the issue.
>
>
Thanks for your reply, but I do want to sort the result by transient field
in Grid. It would be appreciated that the JPAGridDataSource is able to sort
the result within JVM.
On Mon, Jul 11, 2011 at 5:29 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Mon, 11 Jul 2011 18:06:17
On Mon, 11 Jul 2011 18:06:17 -0300, Richard Yunhua Sang
wrote:
Hi there,
Hi!
I am using a Grid with JpaGridDataSource; when I click sort icon on a
transient field of an entity, I get following exception:
I don't think any GridDataSource implementation backed by a database would
be abl
Can you please provide more details? Perfectly some source code to reproduce
the issue.
On Mon, Jul 11, 2011 at 11:06 PM, Richard Yunhua Sang wrote:
> Hi there,
>
> I am using a Grid with JpaGridDataSource; when I click sort icon on a
> transient field of an entity, I get following exception:
>
Hi there,
I am using a Grid with JpaGridDataSource; when I click sort icon on a
transient field of an entity, I get following exception:
Caused by: java.lang.IllegalArgumentException: Unable to resolve attribute
[name] against path
at
org.hibernate.ejb.criteria.path.AbstractPathImpl.unknownAttri
Excellent job Piero!
Kalle
On Tue, Jan 26, 2010 at 2:39 AM, Piero Sartini wrote:
> I am proud to announce the first release of tapestry-jpa which is now
> part of the tynamo[1] project. It features full JPA2 integration and
> provides you with all the functionalities known from t
On Tue, 26 Jan 2010 08:39:16 -0200, Piero Sartini
wrote:
I am proud to announce the first release of tapestry-jpa which is now
part of the tynamo[1] project. It features full JPA2 integration and
provides you with all the functionalities known from tapestry's
hibernate support.
Nice!
I am proud to announce the first release of tapestry-jpa which is now
part of the tynamo[1] project. It features full JPA2 integration and
provides you with all the functionalities known from tapestry's
hibernate support. To get started, you may want to take a look at our
Tapestry JPA Gu
people are trying out tapesry-jpa.
You may want to have a look at the new documentation wiki as well:
http://docs.codehaus.org/display/TYNAMO/Tapestry+JPA
After i followed the quickstart infos on
http://kenai.com/projects/tapestry-jpa/pages/Quickstart (which says, in
short, that all i have to
Hi Peter,
nice to hear people are trying out tapesry-jpa.
You may want to have a look at the new documentation wiki as well:
http://docs.codehaus.org/display/TYNAMO/Tapestry+JPA
> After i followed the quickstart infos on
> http://kenai.com/projects/tapestry-jpa/pages/Quickstart (which sa
Hi,
Beeing new to tapestry (and all the J2EE/web application stuff) i try to
find my way to use it together with JPA.
Following this (very helpfull) mailinglist i found tapestry-jpa
/tapestry-jpa2, actually hosted at tynamo.
Unfortunately i`m not able to bring it together.
I downloaded the
You can wire the injection so that it needs additional marker
annotations; when you declare you service you annotate the service to
identify which marker annotation(s) are used to select it.
On Fri, Dec 4, 2009 at 3:30 PM, Pierce T. Wetter III wrote:
>
> On Dec 3, 2009, at 11:20 AM, Piero Sartini
On Dec 3, 2009, at 11:20 AM, Piero Sartini wrote:
>> @CommitAfter("unit1")
>>
>> JPA already defines something like this does anyone have an opinion on
>> using @Inject vs. @PersistenceContext("unit1")?
>
> Hard to say, but I would prefer @Inject. I like to know that I am
> working with the
> �...@commitafter("unit1")
>
> JPA already defines something like this does anyone have an opinion on using
> @Inject vs. @PersistenceContext("unit1")?
Hard to say, but I would prefer @Inject. I like to know that I am
working with the tapestry stuff, not in the JavaEE context. Could be
confusin
> This has come up recently; the simple idea is that the when injecting
> a Hibernate Session and additional annotation may be present to
> identify *which* session to inject.
i.e.
@CommitAfter("unit1")
JPA already defines something like this does anyone have an opinion on using
@Injec
1 - 100 of 105 matches
Mail list logo
