Make Java Class optional for Rendering Pages
--------------------------------------------
Key: TAPESTRY-1747
URL: https://issues.apache.org/jira/browse/TAPESTRY-1747
Project: Tapestry
Issue Type: Improvement
Components: Framework
Affects Versions: 5.0.5
Environment: Microsoft Windows Vista Business Edition, Eclipse 3.3,
Maven 2, Jetty 5.5, Tomcat 6
Reporter: Evan M Rawson
Priority: Minor
Fix For: 5.0.6
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
