At this stage, T5 will not play very nice with others; the fact that
it is a filter means that it will intercept and attempt to operate
upon URLs intended for your Struts/JSP application (this can be
avoided with a couple of service contributions, but still).

It is possible for Tapestry (4) and JSP-based apps to interoperate,
with reasonable limitations. I don't know about jsp:include, more like
"after this form submits, jump to a JSP page" or "in this JSP page,
this link is to a Tapestry page".

I may be biased, but to me the Struts/JSP side is "a bunch of actions
and views" and the Tapestry side is an actual application, with a real
structure to it.

Remember, T5 is still alpha.

On 3/30/07, Chris Chiappone <[EMAIL PROTECTED]> wrote:
Hi,

My company has a rather large application written in a custom
framework similar to struts.  I have been messing around with Tapestry
5 and enjoying the ease of use it has to offer us.  I was thinking
about building new pages of the application using tapestry 5.

First of all is this a good idea with the current Tapestry 5.0.3 framework?

How difficult would it be for these two frameworks to coexist?

Would it be possible to include tapestry 5 pages within a jsp using
<jsp:include ../?>, and what would this entail?  The reason for this
is because I wouldn't really want to duplicate all the navigation code
within a Border page using tapestry at the moment.

Any thoughts comments concerns would be appreciated.

--
~chris

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to