You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2006/01/07 19:44:40 UTC
[ANNOUNCE] Tapestry 4.0 (final)
After nearly two years of work, the Tapestry development team is proud
to announce the next major release of the Tapestry web application
framework (http://jakarta.apache.org/tapestry/).
Tapestry is an open-source framework for creating dynamic, robust,
highly scalable web applications in Java. Tapestry complements and
builds upon the standard Java Servlet API, and so it works in any
servlet container or application server.
Tapestry divides a web application into a set of pages, each
constructed from components. This provides a consistent structure,
allowing the Tapestry framework to assume responsibility for key
concerns such as URL construction and dispatch, persistent state
storage on the client or on the server, user input validation,
localization/internationalization, and exception reporting. Developing
Tapestry applications involves creating HTML templates using plain
HTML, and combining the templates with small amounts of Java code
using (optional) XML descriptor files. In Tapestry, you create your
application in terms of objects, and the methods and properties of
those objects -- and specifically not in terms of URLs and query
parameters. Tapestry brings true object oriented development to Java
web applications.
Tapestry is specifically designed to make creating new components very
easy, as this is a routine approach when building applications. The
distribution includes over fifty components, ranging from simple
output components all the way up to complex data grids and tree
navigators.
Tapestry is architected to scale from tiny applications all the way up
to massive applications consisting of hundreds of individual pages,
developed by large, diverse teams. Tapestry easily integrates with any
kind of backend, including J2EE, HiveMind and Spring.
Tapestry 4.0 represents a significant advance over Tapestry 3.0. The
following are the most significant changes between the two releases:
* The new 4.0 specification DTDs have been simplified.
* The syntax used for binding parameters inside an HTML template
and inside an XML specification is now consistent. Both make use of
binding prefixes.
* "Friendly" URLs (that is, URLs that pack more information into
the path and less into query parameters) are built in. This makes it
easy to divide your application across many folders (reducing
clutter), and leverage J2EE declarative security along the way.
* Listener methods are much easier and more flexible; listener
parameters in the URL are automatically mapped to listener method
parameters, and listener methods can return the page name or page
instance to activate.
* Component parameters now just work, without having to worry
about "direction".
* Applications can now have a global message catalog, in addition
to per-page and per-component message catalogs. Messages not found in
the component message catalog are searched for in the application
catalog.
* Full, native support for developing JSR-168 Portlets has been added.
* Tapestry 4.0 makes much less use of reflection and OGNL than
Tapestry 3.0; partly because there are many new binding prefixes and
largely because of how parameters are now implemented.
* HiveMind services and Spring beans can be directly injected into
page and component classes.
* Tapestry 4.0 includes optional JDK 1.5 annotation support (but
Tapestry still works with JDK 1.3).
* Tapestry 4.0 debuts a new and much more sophisticated user input
validation subsystem.
* Line precise error reporting can now display the contents of
files containing errors.
* Forms can now be canceled, bypassing client-side validation
logic, and invoking an alternate listener on the server-side.
* You are no longer limited to just Global and Visit; you can have
as many application state objects as you like.
* The use of HiveMind under the covers means that Tapestry can be
easily customized to fit your needs.
* Page properties can now be persisted on the client, as well as
in the session.
* Components and component parameters can now be marked as
deprecated. Component parameters may have aliases (used when renaming
a parameter).
* The examples have been rewritten to take full advantage of
Tapestry 4.0 features, including annotations.
Tapestry is released under the Apache Software Licence 2.0.
Tapestry is distributed as a combined binary/source distribution, and
an additional documentation distribution. Tapestry may be downloaded
from the http://jakarta.apache.org/site/downloads/downloads_tapestry.cgi.
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANNOUNCE] Tapestry 4.0 (final)
Posted by "Filip S. Adamsen" <fi...@stubkjaer-adamsen.dk>.
This is wonderful news! Thanks a lot to everyone involved, especially
Howard. =)
Howard Lewis Ship wrote:
> After nearly two years of work, the Tapestry development team is proud
> to announce the next major release of the Tapestry web application
> framework (http://jakarta.apache.org/tapestry/).
[...]
> Tapestry is released under the Apache Software Licence 2.0.
>
> Tapestry is distributed as a combined binary/source distribution, and
> an additional documentation distribution. Tapestry may be downloaded
> from the http://jakarta.apache.org/site/downloads/downloads_tapestry.cgi.
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work. http://howardlewisship.com
Re: [ANNOUNCE] Tapestry 4.0 (final)
Posted by "Filip S. Adamsen" <fi...@stubkjaer-adamsen.dk>.
Greg Ward wrote:
> On 07 January 2006, Howard Lewis Ship said:
>
>>After nearly two years of work, the Tapestry development team is proud
>>to announce the next major release of the Tapestry web application
>>framework (http://jakarta.apache.org/tapestry/).
>
>
> Congratulations. Have the docs on upgrading from T3 improved much in
> the last couple of months?
Tapestry 4.0 includes some very nice documentation improvements in my
opinion - pretty much everything you need to know is documented, at
least what I need to know is. ; )
> I tried converting our Tapestry 3
> application to T4 back in August, around b6 or b7 or so, and got
> utterly, hopelessly, completely, totally lost.
This is a long time ago, actually. Much of the documentation was
improved upon recently, so you might try to convert your application
again. Also, you're always welcome to send any questions you might have
to this very list - we're here to help. : )
> (I'm looking at
> http://jakarta.apache.org/tapestry/UsersGuide/upgrade.html right now and
> don't see huge changes.)
I do... From what I remember of the Tapestry 3.0 docs, anyways.
> In particular, is there a decent explanation of HiveMind anywhere? I
> was utterly unable to wrap my head around it back in August, which is
> probably the biggest reason my upgrade attempt was a failure.
HiveMind is - and has in my opinion always been - distributed with some
excellent documentation. There's probably a lot for you to learn, but
there's only one thing to do about it - and that's to get started. ; D
> Greg
Regards,
Filip
Re: [ANNOUNCE] Tapestry 4.0 (final)
Posted by Greg Ward <gw...@python.net>.
On 07 January 2006, Howard Lewis Ship said:
> After nearly two years of work, the Tapestry development team is proud
> to announce the next major release of the Tapestry web application
> framework (http://jakarta.apache.org/tapestry/).
Congratulations. Have the docs on upgrading from T3 improved much in
the last couple of months? I tried converting our Tapestry 3
application to T4 back in August, around b6 or b7 or so, and got
utterly, hopelessly, completely, totally lost.
(I'm looking at
http://jakarta.apache.org/tapestry/UsersGuide/upgrade.html right now and
don't see huge changes.)
In particular, is there a decent explanation of HiveMind anywhere? I
was utterly unable to wrap my head around it back in August, which is
probably the biggest reason my upgrade attempt was a failure.
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANNOUNCE] Tapestry 4.0 (final)
Posted by Lindsay Steele <ls...@iinet.net.au>.
This is good news.
The previous article about the developer works article also seems to
have been published at slashdot.
http://developers.slashdot.org/article.pl?sid=06/01/07/2231246
The comments seem relatively reasonable but it might be good if some
real tapestry developers get in and give some real live experiences
rather than the usual "ruby on rails" etc etc stuff.
The announcement has also been put up on Digg
http://digg.com/programming/digg
Might be good to get a few people digging it so it gets up on the front
page.
Howard Lewis Ship wrote:
>After nearly two years of work, the Tapestry development team is proud
>to announce the next major release of the Tapestry web application
>framework (http://jakarta.apache.org/tapestry/).
>
>Tapestry is an open-source framework for creating dynamic, robust,
>highly scalable web applications in Java. Tapestry complements and
>builds upon the standard Java Servlet API, and so it works in any
>servlet container or application server.
>
>Tapestry divides a web application into a set of pages, each
>constructed from components. This provides a consistent structure,
>allowing the Tapestry framework to assume responsibility for key
>concerns such as URL construction and dispatch, persistent state
>storage on the client or on the server, user input validation,
>localization/internationalization, and exception reporting. Developing
>Tapestry applications involves creating HTML templates using plain
>HTML, and combining the templates with small amounts of Java code
>using (optional) XML descriptor files. In Tapestry, you create your
>application in terms of objects, and the methods and properties of
>those objects -- and specifically not in terms of URLs and query
>parameters. Tapestry brings true object oriented development to Java
>web applications.
>
>Tapestry is specifically designed to make creating new components very
>easy, as this is a routine approach when building applications. The
>distribution includes over fifty components, ranging from simple
>output components all the way up to complex data grids and tree
>navigators.
>
>Tapestry is architected to scale from tiny applications all the way up
>to massive applications consisting of hundreds of individual pages,
>developed by large, diverse teams. Tapestry easily integrates with any
>kind of backend, including J2EE, HiveMind and Spring.
>
>Tapestry 4.0 represents a significant advance over Tapestry 3.0. The
>following are the most significant changes between the two releases:
>
> * The new 4.0 specification DTDs have been simplified.
> * The syntax used for binding parameters inside an HTML template
>and inside an XML specification is now consistent. Both make use of
>binding prefixes.
> * "Friendly" URLs (that is, URLs that pack more information into
>the path and less into query parameters) are built in. This makes it
>easy to divide your application across many folders (reducing
>clutter), and leverage J2EE declarative security along the way.
> * Listener methods are much easier and more flexible; listener
>parameters in the URL are automatically mapped to listener method
>parameters, and listener methods can return the page name or page
>instance to activate.
> * Component parameters now just work, without having to worry
>about "direction".
> * Applications can now have a global message catalog, in addition
>to per-page and per-component message catalogs. Messages not found in
>the component message catalog are searched for in the application
>catalog.
> * Full, native support for developing JSR-168 Portlets has been added.
> * Tapestry 4.0 makes much less use of reflection and OGNL than
>Tapestry 3.0; partly because there are many new binding prefixes and
>largely because of how parameters are now implemented.
> * HiveMind services and Spring beans can be directly injected into
>page and component classes.
> * Tapestry 4.0 includes optional JDK 1.5 annotation support (but
>Tapestry still works with JDK 1.3).
> * Tapestry 4.0 debuts a new and much more sophisticated user input
>validation subsystem.
> * Line precise error reporting can now display the contents of
>files containing errors.
> * Forms can now be canceled, bypassing client-side validation
>logic, and invoking an alternate listener on the server-side.
> * You are no longer limited to just Global and Visit; you can have
>as many application state objects as you like.
> * The use of HiveMind under the covers means that Tapestry can be
>easily customized to fit your needs.
> * Page properties can now be persisted on the client, as well as
>in the session.
> * Components and component parameters can now be marked as
>deprecated. Component parameters may have aliases (used when renaming
>a parameter).
> * The examples have been rewritten to take full advantage of
>Tapestry 4.0 features, including annotations.
>
>Tapestry is released under the Apache Software Licence 2.0.
>
>Tapestry is distributed as a combined binary/source distribution, and
>an additional documentation distribution. Tapestry may be downloaded
>from the http://jakarta.apache.org/site/downloads/downloads_tapestry.cgi.
>--
>Howard M. Lewis Ship
>Independent J2EE / Open-Source Java Consultant
>Creator, Jakarta Tapestry
>Creator, Jakarta HiveMind
>
>Professional Tapestry training, mentoring, support
>and project work. http://howardlewisship.com
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANNOUNCE] Tapestry 4.0 (final)
Posted by Paul Cantrell <ca...@pobox.com>.
The release looks good here in Minneapolis.
Congratulations to the Tapestry team! Well done!
Cheers,
Paul
On Jan 7, 2006, at 12:44 PM, Howard Lewis Ship wrote:
> After nearly two years of work, the Tapestry development team is proud
> to announce the next major release of the Tapestry web application
> framework (http://jakarta.apache.org/tapestry/).
>
> Tapestry is an open-source framework for creating dynamic, robust,
> highly scalable web applications in Java. Tapestry complements and
> builds upon the standard Java Servlet API, and so it works in any
> servlet container or application server.
>
> Tapestry divides a web application into a set of pages, each
> constructed from components. This provides a consistent structure,
> allowing the Tapestry framework to assume responsibility for key
> concerns such as URL construction and dispatch, persistent state
> storage on the client or on the server, user input validation,
> localization/internationalization, and exception reporting. Developing
> Tapestry applications involves creating HTML templates using plain
> HTML, and combining the templates with small amounts of Java code
> using (optional) XML descriptor files. In Tapestry, you create your
> application in terms of objects, and the methods and properties of
> those objects -- and specifically not in terms of URLs and query
> parameters. Tapestry brings true object oriented development to Java
> web applications.
>
> Tapestry is specifically designed to make creating new components very
> easy, as this is a routine approach when building applications. The
> distribution includes over fifty components, ranging from simple
> output components all the way up to complex data grids and tree
> navigators.
>
> Tapestry is architected to scale from tiny applications all the way up
> to massive applications consisting of hundreds of individual pages,
> developed by large, diverse teams. Tapestry easily integrates with any
> kind of backend, including J2EE, HiveMind and Spring.
>
> Tapestry 4.0 represents a significant advance over Tapestry 3.0. The
> following are the most significant changes between the two releases:
>
> * The new 4.0 specification DTDs have been simplified.
> * The syntax used for binding parameters inside an HTML template
> and inside an XML specification is now consistent. Both make use of
> binding prefixes.
> * "Friendly" URLs (that is, URLs that pack more information into
> the path and less into query parameters) are built in. This makes it
> easy to divide your application across many folders (reducing
> clutter), and leverage J2EE declarative security along the way.
> * Listener methods are much easier and more flexible; listener
> parameters in the URL are automatically mapped to listener method
> parameters, and listener methods can return the page name or page
> instance to activate.
> * Component parameters now just work, without having to worry
> about "direction".
> * Applications can now have a global message catalog, in addition
> to per-page and per-component message catalogs. Messages not found in
> the component message catalog are searched for in the application
> catalog.
> * Full, native support for developing JSR-168 Portlets has been
> added.
> * Tapestry 4.0 makes much less use of reflection and OGNL than
> Tapestry 3.0; partly because there are many new binding prefixes and
> largely because of how parameters are now implemented.
> * HiveMind services and Spring beans can be directly injected into
> page and component classes.
> * Tapestry 4.0 includes optional JDK 1.5 annotation support (but
> Tapestry still works with JDK 1.3).
> * Tapestry 4.0 debuts a new and much more sophisticated user input
> validation subsystem.
> * Line precise error reporting can now display the contents of
> files containing errors.
> * Forms can now be canceled, bypassing client-side validation
> logic, and invoking an alternate listener on the server-side.
> * You are no longer limited to just Global and Visit; you can have
> as many application state objects as you like.
> * The use of HiveMind under the covers means that Tapestry can be
> easily customized to fit your needs.
> * Page properties can now be persisted on the client, as well as
> in the session.
> * Components and component parameters can now be marked as
> deprecated. Component parameters may have aliases (used when renaming
> a parameter).
> * The examples have been rewritten to take full advantage of
> Tapestry 4.0 features, including annotations.
>
> Tapestry is released under the Apache Software Licence 2.0.
>
> Tapestry is distributed as a combined binary/source distribution, and
> an additional documentation distribution. Tapestry may be downloaded
> from the http://jakarta.apache.org/site/downloads/
> downloads_tapestry.cgi.
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work. http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
_________________________________________________________________
Piano music podcast: http://inthehands.com
Other interesting stuff: http://innig.net
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANNOUNCE] Tapestry 4.0 (final)
Posted by mike jones <mi...@gmail.com>.
Congratulations!
I have been using tapestry 4 since the beta versions and find is a pleasure
to develop with. So much so that I chose it for the project at work. This is
(as always) a project with very tight deadlines, lots of integration with
various technologies and other projects. The new features of tapestry 4 has
really helped speed up development and produce succinct less error prone
code. The integration with hivemind and annotations, and the ability to
inject services into pages components is such a great feature, and the fact
that the parameters just work makes things a lot easier. The new validation
system is a lot more powerful and easy to use, I was able to produces a
required dhtml dojo text area in no time at all.
Thanks again to everyone involved :)
On 08/01/06, Jun Tsai <ju...@gmail.com> wrote:
>
> Congratulations !!!!
>
> 2006/1/8, Jean-Philippe Bouchard <je...@mail.mcgill.ca>:
> > Congratulations to Howard and everybody involved!
> >
> > I've migrated my site recently to 4.0-rc2 (in order to get non-ugly
> > urls) and the migration was virtually painless.
> >
> > Well done!
> >
> > Ciao
> > JPB
> >
> > Howard Lewis Ship wrote:
> > > After nearly two years of work, the Tapestry development team is proud
> > > to announce the next major release of the Tapestry web application
> > > framework (http://jakarta.apache.org/tapestry/).
> > >
> > > Tapestry is an open-source framework for creating dynamic, robust,
> > > highly scalable web applications in Java. Tapestry complements and
> > > builds upon the standard Java Servlet API, and so it works in any
> > > servlet container or application server.
> > >
> > > Tapestry divides a web application into a set of pages, each
> > > constructed from components. This provides a consistent structure,
> > > allowing the Tapestry framework to assume responsibility for key
> > > concerns such as URL construction and dispatch, persistent state
> > > storage on the client or on the server, user input validation,
> > > localization/internationalization, and exception reporting. Developing
> > > Tapestry applications involves creating HTML templates using plain
> > > HTML, and combining the templates with small amounts of Java code
> > > using (optional) XML descriptor files. In Tapestry, you create your
> > > application in terms of objects, and the methods and properties of
> > > those objects -- and specifically not in terms of URLs and query
> > > parameters. Tapestry brings true object oriented development to Java
> > > web applications.
> > >
> > > Tapestry is specifically designed to make creating new components very
> > > easy, as this is a routine approach when building applications. The
> > > distribution includes over fifty components, ranging from simple
> > > output components all the way up to complex data grids and tree
> > > navigators.
> > >
> > > Tapestry is architected to scale from tiny applications all the way up
> > > to massive applications consisting of hundreds of individual pages,
> > > developed by large, diverse teams. Tapestry easily integrates with any
> > > kind of backend, including J2EE, HiveMind and Spring.
> > >
> > > Tapestry 4.0 represents a significant advance over Tapestry 3.0. The
> > > following are the most significant changes between the two releases:
> > >
> > > * The new 4.0 specification DTDs have been simplified.
> > > * The syntax used for binding parameters inside an HTML template
> > > and inside an XML specification is now consistent. Both make use of
> > > binding prefixes.
> > > * "Friendly" URLs (that is, URLs that pack more information into
> > > the path and less into query parameters) are built in. This makes it
> > > easy to divide your application across many folders (reducing
> > > clutter), and leverage J2EE declarative security along the way.
> > > * Listener methods are much easier and more flexible; listener
> > > parameters in the URL are automatically mapped to listener method
> > > parameters, and listener methods can return the page name or page
> > > instance to activate.
> > > * Component parameters now just work, without having to worry
> > > about "direction".
> > > * Applications can now have a global message catalog, in addition
> > > to per-page and per-component message catalogs. Messages not found in
> > > the component message catalog are searched for in the application
> > > catalog.
> > > * Full, native support for developing JSR-168 Portlets has been
> added.
> > > * Tapestry 4.0 makes much less use of reflection and OGNL than
> > > Tapestry 3.0; partly because there are many new binding prefixes and
> > > largely because of how parameters are now implemented.
> > > * HiveMind services and Spring beans can be directly injected into
> > > page and component classes.
> > > * Tapestry 4.0 includes optional JDK 1.5 annotation support (but
> > > Tapestry still works with JDK 1.3).
> > > * Tapestry 4.0 debuts a new and much more sophisticated user input
> > > validation subsystem.
> > > * Line precise error reporting can now display the contents of
> > > files containing errors.
> > > * Forms can now be canceled, bypassing client-side validation
> > > logic, and invoking an alternate listener on the server-side.
> > > * You are no longer limited to just Global and Visit; you can have
> > > as many application state objects as you like.
> > > * The use of HiveMind under the covers means that Tapestry can be
> > > easily customized to fit your needs.
> > > * Page properties can now be persisted on the client, as well as
> > > in the session.
> > > * Components and component parameters can now be marked as
> > > deprecated. Component parameters may have aliases (used when renaming
> > > a parameter).
> > > * The examples have been rewritten to take full advantage of
> > > Tapestry 4.0 features, including annotations.
> > >
> > > Tapestry is released under the Apache Software Licence 2.0.
> > >
> > > Tapestry is distributed as a combined binary/source distribution, and
> > > an additional documentation distribution. Tapestry may be downloaded
> > > from the
> http://jakarta.apache.org/site/downloads/downloads_tapestry.cgi.
> > > --
> > > Howard M. Lewis Ship
> > > Independent J2EE / Open-Source Java Consultant
> > > Creator, Jakarta Tapestry
> > > Creator, Jakarta HiveMind
> > >
> > > Professional Tapestry training, mentoring, support
> > > and project work. http://howardlewisship.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
>
>
> --
> Welcome to China Java Users Group(CNJUG).
> http://cnjug.dev.java.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
d-_-b \m/(>_<)\m/ (9ò_ó)-o(@_o)
Re: [ANNOUNCE] Tapestry 4.0 (final)
Posted by Jun Tsai <ju...@gmail.com>.
Congratulations !!!!
2006/1/8, Jean-Philippe Bouchard <je...@mail.mcgill.ca>:
> Congratulations to Howard and everybody involved!
>
> I've migrated my site recently to 4.0-rc2 (in order to get non-ugly
> urls) and the migration was virtually painless.
>
> Well done!
>
> Ciao
> JPB
>
> Howard Lewis Ship wrote:
> > After nearly two years of work, the Tapestry development team is proud
> > to announce the next major release of the Tapestry web application
> > framework (http://jakarta.apache.org/tapestry/).
> >
> > Tapestry is an open-source framework for creating dynamic, robust,
> > highly scalable web applications in Java. Tapestry complements and
> > builds upon the standard Java Servlet API, and so it works in any
> > servlet container or application server.
> >
> > Tapestry divides a web application into a set of pages, each
> > constructed from components. This provides a consistent structure,
> > allowing the Tapestry framework to assume responsibility for key
> > concerns such as URL construction and dispatch, persistent state
> > storage on the client or on the server, user input validation,
> > localization/internationalization, and exception reporting. Developing
> > Tapestry applications involves creating HTML templates using plain
> > HTML, and combining the templates with small amounts of Java code
> > using (optional) XML descriptor files. In Tapestry, you create your
> > application in terms of objects, and the methods and properties of
> > those objects -- and specifically not in terms of URLs and query
> > parameters. Tapestry brings true object oriented development to Java
> > web applications.
> >
> > Tapestry is specifically designed to make creating new components very
> > easy, as this is a routine approach when building applications. The
> > distribution includes over fifty components, ranging from simple
> > output components all the way up to complex data grids and tree
> > navigators.
> >
> > Tapestry is architected to scale from tiny applications all the way up
> > to massive applications consisting of hundreds of individual pages,
> > developed by large, diverse teams. Tapestry easily integrates with any
> > kind of backend, including J2EE, HiveMind and Spring.
> >
> > Tapestry 4.0 represents a significant advance over Tapestry 3.0. The
> > following are the most significant changes between the two releases:
> >
> > * The new 4.0 specification DTDs have been simplified.
> > * The syntax used for binding parameters inside an HTML template
> > and inside an XML specification is now consistent. Both make use of
> > binding prefixes.
> > * "Friendly" URLs (that is, URLs that pack more information into
> > the path and less into query parameters) are built in. This makes it
> > easy to divide your application across many folders (reducing
> > clutter), and leverage J2EE declarative security along the way.
> > * Listener methods are much easier and more flexible; listener
> > parameters in the URL are automatically mapped to listener method
> > parameters, and listener methods can return the page name or page
> > instance to activate.
> > * Component parameters now just work, without having to worry
> > about "direction".
> > * Applications can now have a global message catalog, in addition
> > to per-page and per-component message catalogs. Messages not found in
> > the component message catalog are searched for in the application
> > catalog.
> > * Full, native support for developing JSR-168 Portlets has been added.
> > * Tapestry 4.0 makes much less use of reflection and OGNL than
> > Tapestry 3.0; partly because there are many new binding prefixes and
> > largely because of how parameters are now implemented.
> > * HiveMind services and Spring beans can be directly injected into
> > page and component classes.
> > * Tapestry 4.0 includes optional JDK 1.5 annotation support (but
> > Tapestry still works with JDK 1.3).
> > * Tapestry 4.0 debuts a new and much more sophisticated user input
> > validation subsystem.
> > * Line precise error reporting can now display the contents of
> > files containing errors.
> > * Forms can now be canceled, bypassing client-side validation
> > logic, and invoking an alternate listener on the server-side.
> > * You are no longer limited to just Global and Visit; you can have
> > as many application state objects as you like.
> > * The use of HiveMind under the covers means that Tapestry can be
> > easily customized to fit your needs.
> > * Page properties can now be persisted on the client, as well as
> > in the session.
> > * Components and component parameters can now be marked as
> > deprecated. Component parameters may have aliases (used when renaming
> > a parameter).
> > * The examples have been rewritten to take full advantage of
> > Tapestry 4.0 features, including annotations.
> >
> > Tapestry is released under the Apache Software Licence 2.0.
> >
> > Tapestry is distributed as a combined binary/source distribution, and
> > an additional documentation distribution. Tapestry may be downloaded
> > from the http://jakarta.apache.org/site/downloads/downloads_tapestry.cgi.
> > --
> > Howard M. Lewis Ship
> > Independent J2EE / Open-Source Java Consultant
> > Creator, Jakarta Tapestry
> > Creator, Jakarta HiveMind
> >
> > Professional Tapestry training, mentoring, support
> > and project work. http://howardlewisship.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
Welcome to China Java Users Group(CNJUG).
http://cnjug.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANNOUNCE] Tapestry 4.0 (final)
Posted by Jean-Philippe Bouchard <je...@mail.mcgill.ca>.
Congratulations to Howard and everybody involved!
I've migrated my site recently to 4.0-rc2 (in order to get non-ugly
urls) and the migration was virtually painless.
Well done!
Ciao
JPB
Howard Lewis Ship wrote:
> After nearly two years of work, the Tapestry development team is proud
> to announce the next major release of the Tapestry web application
> framework (http://jakarta.apache.org/tapestry/).
>
> Tapestry is an open-source framework for creating dynamic, robust,
> highly scalable web applications in Java. Tapestry complements and
> builds upon the standard Java Servlet API, and so it works in any
> servlet container or application server.
>
> Tapestry divides a web application into a set of pages, each
> constructed from components. This provides a consistent structure,
> allowing the Tapestry framework to assume responsibility for key
> concerns such as URL construction and dispatch, persistent state
> storage on the client or on the server, user input validation,
> localization/internationalization, and exception reporting. Developing
> Tapestry applications involves creating HTML templates using plain
> HTML, and combining the templates with small amounts of Java code
> using (optional) XML descriptor files. In Tapestry, you create your
> application in terms of objects, and the methods and properties of
> those objects -- and specifically not in terms of URLs and query
> parameters. Tapestry brings true object oriented development to Java
> web applications.
>
> Tapestry is specifically designed to make creating new components very
> easy, as this is a routine approach when building applications. The
> distribution includes over fifty components, ranging from simple
> output components all the way up to complex data grids and tree
> navigators.
>
> Tapestry is architected to scale from tiny applications all the way up
> to massive applications consisting of hundreds of individual pages,
> developed by large, diverse teams. Tapestry easily integrates with any
> kind of backend, including J2EE, HiveMind and Spring.
>
> Tapestry 4.0 represents a significant advance over Tapestry 3.0. The
> following are the most significant changes between the two releases:
>
> * The new 4.0 specification DTDs have been simplified.
> * The syntax used for binding parameters inside an HTML template
> and inside an XML specification is now consistent. Both make use of
> binding prefixes.
> * "Friendly" URLs (that is, URLs that pack more information into
> the path and less into query parameters) are built in. This makes it
> easy to divide your application across many folders (reducing
> clutter), and leverage J2EE declarative security along the way.
> * Listener methods are much easier and more flexible; listener
> parameters in the URL are automatically mapped to listener method
> parameters, and listener methods can return the page name or page
> instance to activate.
> * Component parameters now just work, without having to worry
> about "direction".
> * Applications can now have a global message catalog, in addition
> to per-page and per-component message catalogs. Messages not found in
> the component message catalog are searched for in the application
> catalog.
> * Full, native support for developing JSR-168 Portlets has been added.
> * Tapestry 4.0 makes much less use of reflection and OGNL than
> Tapestry 3.0; partly because there are many new binding prefixes and
> largely because of how parameters are now implemented.
> * HiveMind services and Spring beans can be directly injected into
> page and component classes.
> * Tapestry 4.0 includes optional JDK 1.5 annotation support (but
> Tapestry still works with JDK 1.3).
> * Tapestry 4.0 debuts a new and much more sophisticated user input
> validation subsystem.
> * Line precise error reporting can now display the contents of
> files containing errors.
> * Forms can now be canceled, bypassing client-side validation
> logic, and invoking an alternate listener on the server-side.
> * You are no longer limited to just Global and Visit; you can have
> as many application state objects as you like.
> * The use of HiveMind under the covers means that Tapestry can be
> easily customized to fit your needs.
> * Page properties can now be persisted on the client, as well as
> in the session.
> * Components and component parameters can now be marked as
> deprecated. Component parameters may have aliases (used when renaming
> a parameter).
> * The examples have been rewritten to take full advantage of
> Tapestry 4.0 features, including annotations.
>
> Tapestry is released under the Apache Software Licence 2.0.
>
> Tapestry is distributed as a combined binary/source distribution, and
> an additional documentation distribution. Tapestry may be downloaded
> from the http://jakarta.apache.org/site/downloads/downloads_tapestry.cgi.
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work. http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [ANNOUNCE] Tapestry 4.0 (final)
Posted by NYG <ny...@yahoo.com>.
This is great news!!!
Howard Lewis Ship <hl...@gmail.com> wrote: After nearly two years of work, the Tapestry development team is proud
to announce the next major release of the Tapestry web application
framework (http://jakarta.apache.org/tapestry/).
Tapestry is an open-source framework for creating dynamic, robust,
highly scalable web applications in Java. Tapestry complements and
builds upon the standard Java Servlet API, and so it works in any
servlet container or application server.
Tapestry divides a web application into a set of pages, each
constructed from components. This provides a consistent structure,
allowing the Tapestry framework to assume responsibility for key
concerns such as URL construction and dispatch, persistent state
storage on the client or on the server, user input validation,
localization/internationalization, and exception reporting. Developing
Tapestry applications involves creating HTML templates using plain
HTML, and combining the templates with small amounts of Java code
using (optional) XML descriptor files. In Tapestry, you create your
application in terms of objects, and the methods and properties of
those objects -- and specifically not in terms of URLs and query
parameters. Tapestry brings true object oriented development to Java
web applications.
Tapestry is specifically designed to make creating new components very
easy, as this is a routine approach when building applications. The
distribution includes over fifty components, ranging from simple
output components all the way up to complex data grids and tree
navigators.
Tapestry is architected to scale from tiny applications all the way up
to massive applications consisting of hundreds of individual pages,
developed by large, diverse teams. Tapestry easily integrates with any
kind of backend, including J2EE, HiveMind and Spring.
Tapestry 4.0 represents a significant advance over Tapestry 3.0. The
following are the most significant changes between the two releases:
* The new 4.0 specification DTDs have been simplified.
* The syntax used for binding parameters inside an HTML template
and inside an XML specification is now consistent. Both make use of
binding prefixes.
* "Friendly" URLs (that is, URLs that pack more information into
the path and less into query parameters) are built in. This makes it
easy to divide your application across many folders (reducing
clutter), and leverage J2EE declarative security along the way.
* Listener methods are much easier and more flexible; listener
parameters in the URL are automatically mapped to listener method
parameters, and listener methods can return the page name or page
instance to activate.
* Component parameters now just work, without having to worry
about "direction".
* Applications can now have a global message catalog, in addition
to per-page and per-component message catalogs. Messages not found in
the component message catalog are searched for in the application
catalog.
* Full, native support for developing JSR-168 Portlets has been added.
* Tapestry 4.0 makes much less use of reflection and OGNL than
Tapestry 3.0; partly because there are many new binding prefixes and
largely because of how parameters are now implemented.
* HiveMind services and Spring beans can be directly injected into
page and component classes.
* Tapestry 4.0 includes optional JDK 1.5 annotation support (but
Tapestry still works with JDK 1.3).
* Tapestry 4.0 debuts a new and much more sophisticated user input
validation subsystem.
* Line precise error reporting can now display the contents of
files containing errors.
* Forms can now be canceled, bypassing client-side validation
logic, and invoking an alternate listener on the server-side.
* You are no longer limited to just Global and Visit; you can have
as many application state objects as you like.
* The use of HiveMind under the covers means that Tapestry can be
easily customized to fit your needs.
* Page properties can now be persisted on the client, as well as
in the session.
* Components and component parameters can now be marked as
deprecated. Component parameters may have aliases (used when renaming
a parameter).
* The examples have been rewritten to take full advantage of
Tapestry 4.0 features, including annotations.
Tapestry is released under the Apache Software Licence 2.0.
Tapestry is distributed as a combined binary/source distribution, and
an additional documentation distribution. Tapestry may be downloaded
from the http://jakarta.apache.org/site/downloads/downloads_tapestry.cgi.
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------
Yahoo! DSL Something to write home about. Just $16.99/mo. or less