Jochen Kemnade created TAP5-2143:
------------------------------------
Summary: Extract a tapestry-web-core module
Key: TAP5-2143
URL: https://issues.apache.org/jira/browse/TAP5-2143
Project: Tapestry 5
Issue Type: Wish
Affects Versions: 5.3, 5.4
Reporter: Jochen Kemnade
Quite regularly, I create a servlet that can handle a small number of different
service URLs that are called from external applications and as well as serve
static resources like html pages and JS/CS/CSS files.
Usually, I use tapestry-ioc, a ContextListener (to build the registry and and
store it in the servlet context) and a HttpServlet (for the request handling).
Compared to using tapestry-core, that's quite a step back and also, you lose
useful and important parts, e.g. the request handler pipelines, assets
(including minification), dispatchers, and response compression.
I do *not* use tapestry-core, because it provides lots of functionality that I
don't need. Basically, that's everything related to components and client-side
logic: component rendering, transformation, component events, value encoders,
included components like the Grid, validation, and page initialization to name
a few.
I think, tapestry-core should be split into the "component-related parts" and
the rest, although that's a bit oversimplified.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
