You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Payne, Matthew" <Pa...@pennmutual.com> on 2006/06/06 19:57:46 UTC
RE: Tapernate and Spring
re: "since Spring does not have explicit Tapestry-support"
Is it up to spring add tapestry support?
No. Its is up to Tapestry to fix it brokenness?
Webwork is not mentioned in spring's lib/src, yet its spring support is superior.
Right now tapestry's spring support is kind of half baked. Pages cannot be autowired from spring.
In addition, I don't think its possible today to do "prototype" proxy-ing of Tapestry pages/actions via auto-proxy or explicitly, since spring cannot create the abstract tapestry pages. We will have to wait for the framework to become more pojo based.
For now, I believe recommendation "explicitly" inject your singleton services. All the advice would be specified on the service.
If you don't want your services to be singletons, I am not sure if all that lifecycle handling is complete yet.
Matt
-----Original Message-----
From: Mark [mailto:lists@mark-arnold.net]
Sent: Sunday, May 28, 2006 3:28 AM
To: Tapestry users
Subject: Tapernate and Spring
Hi all,
In a recent different thread, the question about "Why use Tapernate if
you use Spring" had come up as a side-question.
It seems that some (Hibernate-related) features of Tapernate are
alternatives to equivalent Spring features, while others are more
Tapestry-related features (e.g. the DataSqueezer) that are not available
in Spring, since Spring does not have explicit Tapestry-support.
For some of the features listed on the feature-list at
http://www.carmanconsulting.com/tapernate/ I am not sure which category
they belong to:
- Is there anything in Spring that deals with the
reattachment-strategies ("Persistence Strategies" on the list)?
- Is the "POJO-Rollback" functionality covered by Spring's Transaction
facility?
Does anybody know if there is a document with a comparison of the
various frameworks/add-on libs that offer persistence-support
(Tapernate, Hivetranse, Honeycomb, [Spring]; are there more?) for
Tapestry? Like a quick features and pros/cons comparison?
Thanks,
MARK
P.S. James, did you forget to list the transaction-strategies on the
feature list, or did you leave it out intentionally?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
This message, including any attachments, is intended only for the recipient(s)
named above. It may contain confidential and privileged information. If you have
received this communication in error, please notify the sender immediately and
destroy or delete the original message. Also, please be aware that if you are not
the intended recipient, any review, disclosure, copying, distribution or any
action or reliance based on this message is prohibited by law.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: Tapernate and Spring
Posted by James Carman <ja...@carmanconsulting.com>.
Or maybe we should use HiveMind and not Spring! :-)
-----Original Message-----
From: Payne, Matthew [mailto:Payne.Matthew@pennmutual.com]
Sent: Tuesday, June 06, 2006 1:58 PM
To: Tapestry users
Subject: RE: Tapernate and Spring
re: "since Spring does not have explicit Tapestry-support"
Is it up to spring add tapestry support?
No. Its is up to Tapestry to fix it brokenness?
Webwork is not mentioned in spring's lib/src, yet its spring support is
superior.
Right now tapestry's spring support is kind of half baked. Pages cannot be
autowired from spring.
In addition, I don't think its possible today to do "prototype" proxy-ing of
Tapestry pages/actions via auto-proxy or explicitly, since spring cannot
create the abstract tapestry pages. We will have to wait for the framework
to become more pojo based.
For now, I believe recommendation "explicitly" inject your singleton
services. All the advice would be specified on the service.
If you don't want your services to be singletons, I am not sure if all that
lifecycle handling is complete yet.
Matt
-----Original Message-----
From: Mark [mailto:lists@mark-arnold.net]
Sent: Sunday, May 28, 2006 3:28 AM
To: Tapestry users
Subject: Tapernate and Spring
Hi all,
In a recent different thread, the question about "Why use Tapernate if
you use Spring" had come up as a side-question.
It seems that some (Hibernate-related) features of Tapernate are
alternatives to equivalent Spring features, while others are more
Tapestry-related features (e.g. the DataSqueezer) that are not available
in Spring, since Spring does not have explicit Tapestry-support.
For some of the features listed on the feature-list at
http://www.carmanconsulting.com/tapernate/ I am not sure which category
they belong to:
- Is there anything in Spring that deals with the
reattachment-strategies ("Persistence Strategies" on the list)?
- Is the "POJO-Rollback" functionality covered by Spring's Transaction
facility?
Does anybody know if there is a document with a comparison of the
various frameworks/add-on libs that offer persistence-support
(Tapernate, Hivetranse, Honeycomb, [Spring]; are there more?) for
Tapestry? Like a quick features and pros/cons comparison?
Thanks,
MARK
P.S. James, did you forget to list the transaction-strategies on the
feature list, or did you leave it out intentionally?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
This message, including any attachments, is intended only for the
recipient(s)
named above. It may contain confidential and privileged information. If you
have
received this communication in error, please notify the sender immediately
and
destroy or delete the original message. Also, please be aware that if you
are not
the intended recipient, any review, disclosure, copying, distribution or any
action or reliance based on this message is prohibited by law.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org