You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Emmanuel DEMEY (Commented) (JIRA)" <ji...@apache.org> on 2012/01/23 10:26:38 UTC

[jira] [Commented] (TAP5-1526) Tapestry5 plugin for roo

    [ https://issues.apache.org/jira/browse/TAP5-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190947#comment-13190947 ] 

Emmanuel DEMEY commented on TAP5-1526:
--------------------------------------

Hi

I have just started a Spring Roo plugin for Tapestry, available on Github : https://github.com/Gillespie59/Tapestry-Roo.

Right now, this plugin just create the basic Tapestry Structure. 

If you have some features you want to see in this kind of plugin, do not hesitate to contact me!

Manu
                
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira