[
https://issues.apache.org/jira/browse/TAP5-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1526:
---------------------------------
This issue has been last updated about 1.5 years ago and has no information
about the versions that are affected. That makes it hard to determine whether
it is still relevant.
If the issue still persists with the current stable version (5.3.7) or the most
recent development preview of Tapestry (5.4-beta-6), both of which are
available from Maven Central, please update it as soon as possible, adding the
respective version(s) to the issue's "Affects Version/s".
> Tapestry5 plugin for roo
> ------------------------
>
> Key: TAP5-1526
> URL: https://issues.apache.org/jira/browse/TAP5-1526
> Project: Tapestry 5
> Issue Type: Wish
> Reporter: Toby
>
> There should be a Tapestry5 plugin for Roo (http://www.springsource.org/roo).
> As probably every Tapestry5 developer is also using Spring, it would be good
> if Tapestry5 and Roo joined forces....
> Things like:
> - command line tools
> - plugins (spring-security, selenium....)
> - eclipse tools
> could be shared.
> Both the pure Java approach and the Tapestry approach have their
> advantages/disadvantages, depending on the scenerio.
> So control interfaces or ajax/comet/atmosphere kind of application are often
> better off to be developed using Roo+Vaadin - and as an alternative for web
> applications where seo/urls and templates matter,
> Roo+Tapestry5 is the best choice (e.g. when ready-made HTML templates are
> delivered and need to be implemented).
> Roo seems to focus more on the first approach, but a kind of plugin (e.g. for
> Tapestry5), to offer the second approach to Roo developers would be extremely
> helpful.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
