[jira] Commented: (TAP5-85) Make Java Class optional for Rendering Pages

["Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org>]

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

Thiago H. de Paula Figueiredo commented on TAP5-85:
---------------------------------------------------

I prefer the idea of a Maven plugin that creates the empty classes automatically way more than changing the framework itself, as this would complicate a lot the way pages and components are located.

> Make Java Class optional for Rendering Pages
> --------------------------------------------
>
>                 Key: TAP5-85
>                 URL: https://issues.apache.org/jira/browse/TAP5-85
>             Project: Tapestry 5
>          Issue Type: New Feature
>    Affects Versions: 5.0.15
>         Environment: Microsoft Windows Vista Business Edition, Eclipse 3.3, Maven 2, Jetty 5.5, Tomcat 6
>            Reporter: Evan M Rawson
>            Priority: Minor
>
> You should not need a java class create to view a page. The framework should be able to generate a basic class on the fly. This would aid significantly to the production flow of tapestry applications. Meaning that designers and system architects do not need to setup the basic java class in order to build and test the front end user interface.
> When a java class representing the page is present then it would override this default generate class that tapestry makes on the fly.
> EX: right now im creating a pretty decent sized tapestry application (75 to 125 pages). The pages have been mocked up and the interface is being assembled (html/css). I am finding that i am needing to create a bunch of empty java classes in order to view the page to test it; this seems pointless and redundant to me. For example a script in maven could be written to auto generate all of the classes based on the html template dir is stored, saving a few hours of naming and creating.
>  the java developer should not have to create the html pages, technically they should be able to use junit to handle testing their base components which they have created. The backend and frontend should seamlessly integrated with each other.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.