You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/01/12 09:10:53 UTC
[jira] [Closed] (TAP5-1526) Tapestry5 plugin for roo
[ https://issues.apache.org/jira/browse/TAP5-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade closed TAP5-1526.
--------------------------------
Resolution: Invalid
We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.
> 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.3.4#6332)