tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Toby (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAP5-1526) Tapestry5 plugin for roo
Date Tue, 17 May 2011 15:40:48 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Toby updated TAP5-1526:
-----------------------

    Description: 
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.

  was:
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....



> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message