Hey! Always more questions!
I'm following this example: Ajax EventLinks in a Loop
http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/eventlinksinaloop
. I've modified some code to fit my use case. I have a table that uses a
t:loop to iterate through services and show if they are
I've been reading other posts but nothing seems to work for me.
Here's my page:
public class ServiceActivation {
private ListUser users;
@Property
private UserService userservice;
@Property
private User u;
Yes, that did it. God damn it's been bugging me for two hours trying to find
solutions. I think I had switched it because something had previously caused
an exception and I thought I needed the expansion. Can you explain the use
of formState and encoder in the form component? I don't quite get the
Hey
So it worked as you said, but now I have another problem.
Can you tell me why this isn't working?
t:loop source = services values = service formState = none
${service.name}
/t:loop
It gives me the following error:
Render queue error in
I need sleep. Thanks!
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/5-3-6-Loop-component-giving-coercion-error-tp5718395p5718403.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
While we are on the subject. @CommitAfter commits the transaction after the
called method. What if I call multiple methods annotated with @CommitAfter?
The commits happen after each of them. If I reach a method where an
Exception is raised and I need to rollback, will it rollback every
transaction
More questions:
I have an onSuccess() method in my Page class that calls a DAO delete method
annotated with @CommitAfter. When the onSuccess() gets called (I'm using a
form with a submit) the delete doesn't get commit at the end of the request
(although I see hibernate log it). If I annotate the
Answer my question too. I read that little bit you linked and I understand
the HibernateTransactionAdvisor does it for you.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/CommitAfter-not-committing-my-transaction-tp5718364p5718408.html
Sent from the Tapestry - User
User();
u.setUsername(Pillar);
u.setEmail(yahoo...@yahoo.ca);
u.setPassword(poof);
s.save(u);
}
Once execution exits this method and my page is rendered, I check my
database and there is no entry for the above user.
I'm
It is in a Controller. If it was in DAO Layer, do I still use the @Inject for
a session or get it from HibernateUtils style class?
Now regardless of if I get the Transaction from the Session I'm given from
the SessionFactory, shouldn't Tapestry be finding the same Transaction and
committing it?
As far as I know a Hibernate Session has only one Transaction at a time,
hence the session.beginTransaction, session.getTransaction(). Also, the
SessionFactory has the getCurrentSession() which returns a per thread
session. So unless, I'm completely wrong in how I think tapestry-hibernate
is
I'm not in a position to test it right now, so I won't say if it worked.
Where does Tapestry get that session for you? But you are right, that is
smarter/better than popping out your own every time.
--
View this message in context:
Ok, so I didn't know that, I thought SessionFactory was a singleton. I will
use Tapestry-Hibernate the way it's meant to just like in the link you
posted. Thanks!
--
View this message in context:
Hi,
In the Tapestry User Guide for session storage
http://tapestry.apache.org/session-storage.html , it states Any other
component or page that declares a field of the same type, regardless of
name, and marks it with the SessionState annotation will share the same
value. I have the following
: Re: SessionState
On Mon, 26 Nov 2012 18:45:14 -0200, Pillar [hidden email] wrote:
Hi,
Hi!
In the Tapestry User Guide for session storage
http://tapestry.apache.org/session-storage.html , it states Any other
component or page that declares a field of the same type
15 matches
Mail list logo
