On Fri, 08 Oct 2010 23:56:18 -0300, Fanzhen
wrote:
well ,you know, there maybe two ways to import a component in page tml.
You don't import a component in a page template, you define one component
instance in a page or component template.
first way,
, I can put two same components
headache, it did not work well, could anyone give some suggestion?
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
sorry everyone I got the method.
set clientId for my component and handle it by
ComponentSource.getComponent(completeId);
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h
well ,you know, there maybe two ways to import a component in page tml.
first way,
, I can put two same components
which are using in two places in one page.
and second way,
, well this way I
could handle the it in page class.
the problem is if I do the first way, how to handle the comp
On Fri, Oct 8, 2010 at 11:32 AM, Rich M wrote:
> Ah, darn it. This is for a vital product and my company wouldn't let me use
> 5.2 until its a final release. However, a little bit of digging I was able
> to improve on my previous code for 5.1.0.5. Albeit no @CommitAfter, but it
> does seem a bette
Ah, darn it. This is for a vital product and my company wouldn't let me
use 5.2 until its a final release. However, a little bit of digging I
was able to improve on my previous code for 5.1.0.5. Albeit no
@CommitAfter, but it does seem a better solution that using Transaction
explicitly (which
On Fri, 08 Oct 2010 14:40:29 -0300, Rich M wrote:
Hi,
Hi!
I'm using 5.1.0.5, good to know about the annotations for services.
Please try 5.2 and tells us what happens.
Your code seems OK to me. My architecture looks exactly like yours for
DAOs. :) But I don't use tapestry-hibernate mys
Hi,
I'm using 5.1.0.5, good to know about the annotations for services. I
modified my code so the Interfaces are using the @CommitAfter annotation
for the desired methods. Also made those methods public (I wanted
protected because the DAO class isn't supposed to be directly accessed
except by
On Fri, 08 Oct 2010 12:41:41 -0300, Rich M wrote:
Hi,
Hi!
@CommitAfter
protected void executeUpdate(Entity entity){
Have you tried making your method public? Another question: what
Tapestry-IoC version are you using? Tapestry 5.1.0.5 didn't add
annotations put in method implem
Hi,
so this thread has inspired me (along with some freetime) to clean up my
Tapestry-Hibernate DAO code, but I'm having a hard time getting the
@CommitAfter annotation to seemingly work correctly. I'm assuming I'm
missing a small step. I advise the TransactionCommitAdvice in my AppModule:
@
have a look here,
perhaps it helps you
http://www.chenillekit.org/chenillekit-hibernate/dao_sample.html
with regards
Sven Homburg
Founder of the Chenille Kit Project
http://chenillekit.codehaus.org
2010/10/8 Alex W. Croton :
> Many thanks to all who offered solutions on this one - I think I'
Many thanks to all who offered solutions on this one - I think I've got it
cracked now.
My problem was not so much in getting the code for the DAO working, it was the
realisation that I could/needed to inject the Session into the DAO to be able
to 'talk' to Hibernate, and to then inject the DAO
On Fri, 08 Oct 2010 05:18:30 -0300, aertsko wrote:
This is exactly what I am looking for.
Could you explain in more detail how the capturing and triggering of the
edit event works? I can capture the action event from my actionlink, but
I can't find how to trigger the edit event.
@Inject Co
Howard Lewis Ship wrote:
>
> Often, a component will capture "action" events from one or more
> components and trigger new events with names customized to what the
> component does; here is might trigger an "edit" event, and you would
> name your method onEditFromLayout().
>
Hi Howard,
This i
On Fri, 08 Oct 2010 04:07:16 -0300, ael wrote:
So what would be the difference?
The important is you achieve
what you want to do.
The difference is that the Tapestry-Hibernate integration (session and
transaction handling) will not work if your DAO is not a Tapestry-IoC
service. That simp
Hi,
I just built a new project from the maven archetype, it seems like
'https' are still present in the catalog file...
Any idea ?
Cheers
Christophe
2010/7/22 Andreas Andreou :
> ok, my bad - i've left some https references in
> http://tapestry.apache.org/archetype-catalog.xml
> and that's proba
Which is true, but if you aren't going to use the facilites of
Tapestry, such as its built-in Hibernate integration, then please seek
answers to your problems elsewhere.
Using the Tapestry mechanisms means that the you can be sure of using
the same session instance across all pages, components and
So what would be the difference?
The important is you achieve
what you want to do.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Early-steps-getting-Tapestry-and-Hibernate-working-via-DAO-tp3072498p3204134.html
Sent from the Tapestry - User mailing list archive at Nabbl
18 matches
Mail list logo
