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 2013/04/07 01:45:56 UTC
Tapestry 5.4-alpha-3
Hot off the presses! The latest preview release of Tapestry, 5.4-alpha-3,
is now available.
Point your build tool of choice at the Maven repository:
https://repository.apache.org/content/repositories/orgapachetapestry-072/
Binary and source archives:
http://people.apache.org/~hlship/tapestry-releases/
What's new?
So much, I've kind of lost track; the main changes are:
Most assets are now accessed using a URL that incorporates a Adler32
checksum of the asset content. Prior versions of Tapestry incorporated the
application version number into the URL.
What does this mean? When you redeploy your web application, most assets
will have not changed: same content, same path, same checksum, therefore,
same URL. This means that client browsers will not have to re-download all
those assets again just because the application version number has changed.
Assets that have changed will have a different content hash, and therefore,
a different asset URL. Browsers will be sure to pull down those new
versions.
Modules are slightly different; because all JavaScript modules are expected
to start in a common root URL, there is no reasonable way to generate a
unique content hash for each; module URLs still use the application version
number. However, modules and all assets now also send an ETag header; this
means that module requests will still be sent, but will often get a 304
(resource not modified) response.
Obviously, this is a big change, and we're welcoming feedback.
Next up; we have first class support for jQuery.A little bit of symbol
tweaking, and Prototype and Scriptaculous are simply gone for good.
There's also been improvements to operation tracking, with more operations
performed during a request being tracked. This is useful for the part of
the exception report page that discusses what Tapestry did during a
request, leading up to the actual exception.
There's been big improvements, c/o Kalle, in terms of how exceptions are
reported, with finer control over what gets the full exception page, and
what doesn't.
For the rare places where public interfaces changed in incompatible ways,
there's now an @IncompatibleChange annotation for methods that have changed.
A few informational pages such as PageCatalog, ServiceStatus, and Hibernate
Statistics have been merged into a new single (extensible) page,
T5Dashboard.
... and lots more little changes, fixes, and improvements.
There's still a lot more to come, however. Two principle improvements I'm
targeting for 5.4:
Proper server-side push/websocket support.
Built-in performance monitoring and reporting.
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: Tapestry 5.4-alpha-3
Posted by Howard Lewis Ship <hl...@gmail.com>.
I'd like to see a sample of code and template before deciding if this is a
bug, or user error. It is likely a bug, but I haven't had a chance to test
it.
On Fri, Apr 19, 2013 at 5:02 PM, Charlouze <me...@charlouze.com> wrote:
> New information about my problem: it's working with classpath assets but it
> is not working with context assets.
>
> Am I doing something wrong or is this a bug ?
>
>
> 2013/4/17 Charlouze <me...@charlouze.com>
>
> > I'm 100% sure that my app is not in production mode and my file is not
> > packaged in a JAR file.
> >
> > As I said, it works well when I use the css file without the stack using
> > @import.
> >
> >
> > 2013/4/17 Howard Lewis Ship <hl...@gmail.com>
> >
> >> It is supposed to clear its cache if there's a change to the file. I've
> >> tested that manually but don't know if there's an automated test for
> that.
> >>
> >> There's no chance you are running in production mode, or have the file
> in
> >> question packaged in a JAR file? Live reload is only for files on the
> >> file
> >> system itself.
> >>
> >>
> >> On Wed, Apr 17, 2013 at 3:25 PM, Charlouze <me...@charlouze.com> wrote:
> >>
> >> > I explore the code of the ExtensibleJavaScriptStack class and it
> >> calculates
> >> > the asset link on first use. Maybe I can disable the checksum in URL ?
> >> >
> >> >
> >> > 2013/4/17 Charlouze <me...@charlouze.com>
> >> >
> >> > > I build my app with eclipse 3.7.2. I use the m2e plugin (1.1.0) and
> >> the
> >> > > m2e-wtp (0.15.3) to configure my eclipse project. I'm running the
> app
> >> > using
> >> > > the run jetty run plugin (1.3.3). The selected jetty version is
> 8.1.2.
> >> > >
> >> > > I just made a small test project (only an index page with nothing
> but
> >> a
> >> > > title and the styles.css file). I figured out where the problem is:
> >> if I
> >> > > load my styles.css through an ExtensibleJavaScriptStack it does'nt
> >> work,
> >> > > the address is not changing when I add some css rules to the file.
> If
> >> I
> >> > use
> >> > > @Import(stylesheet = { "context:/css/styles.css" }) on my index
> page,
> >> it
> >> > > works well.
> >> > >
> >> > > Should I file a bug on jira ?
> >> > >
> >> > >
> >> > > 2013/4/17 Howard Lewis Ship <hl...@gmail.com>
> >> > >
> >> > >> When you refresh your page, it *should* be building a new URL to
> the
> >> > >> updated asset. The particulars matter here ... how exactly are you
> >> > >> building & running the app?
> >> > >>
> >> > >>
> >> > >> On Wed, Apr 17, 2013 at 9:31 AM, Charlouze <me...@charlouze.com>
> wrote:
> >> > >>
> >> > >> > Hey everyone,
> >> > >> >
> >> > >> > I have some trouble with the 5.4-alpha-3. When I add some stuff
> to
> >> my
> >> > >> > styles.css file, it get another address to access it (that is
> >> > perfectly
> >> > >> > normal according to the new asset feature). The problem is that
> if
> >> I
> >> > >> don't
> >> > >> > restart my application my pages tries to load my styles.css file
> >> from
> >> > >> the
> >> > >> > old address. I probably miss somthing.
> >> > >> >
> >> > >> > For your information, I'm am in development mode. I use eclipse
> and
> >> > the
> >> > >> run
> >> > >> > jetty run plugin.
> >> > >> >
> >> > >> > Charles.
> >> > >> >
> >> > >> >
> >> > >> > 2013/4/12 François Facon <fr...@atos.net>
> >> > >> >
> >> > >> > > By the way, tapestry5-portlet is also ready to be used with
> 5.4.
> >> But
> >> > >> I am
> >> > >> > > still looking for a way to run integration tests inside Pluto
> >> with
> >> > >> > Gradle.
> >> > >> > > Perhaps the use of Arquillian with Pluto under gradle is the
> >> > solution.
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> >> > >> > >
> >> > >> > > > That's great news!
> >> > >> > > >
> >> > >> > > >
> >> > >> > > > On Fri, Apr 12, 2013 at 12:35 PM, François Facon <
> >> > >> > > francois.facon@atos.net
> >> > >> > > > >wrote:
> >> > >> > > >
> >> > >> > > > > Thanks to Emmanuel, tapestry-jquery is already working fine
> >> with
> >> > >> 5.4.
> >> > >> > > > >
> >> > >> > > > >
> >> > >> > > > >
> >> > >> > > > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> >> > >> > > > >
> >> > >> > > > > > We don't control the tapestry-jquery library; I actually
> >> > haven't
> >> > >> > > looked
> >> > >> > > > > at
> >> > >> > > > > > it. I suspect it will need to be reworked significantly
> for
> >> > 5.4.
> >> > >> > > > > >
> >> > >> > > > > >
> >> > >> > > > > > On Fri, Apr 12, 2013 at 9:40 AM, George Christman
> >> > >> > > > > > <gc...@cardaddy.com>wrote:
> >> > >> > > > > >
> >> > >> > > > > > > I'm just curious if Tapestry5.4 will just be
> integrating
> >> the
> >> > >> > > > > > > Tapestry-Jquery library?
> >> > >> > > > > > >
> >> > >> > > > > > > On Sun, Apr 7, 2013 at 10:29 AM, hantsy <
> >> > hantsy@yahoo.com.cn>
> >> > >> > > wrote:
> >> > >> > > > > > > >
> >> > >> > > > > > > > Created a new thread for it. Thanks
> >> > >> > > > > > > >
> >> > >> > > > > > > > On 4/7/2013 22:16, Bob Harner wrote:
> >> > >> > > > > > > >> Hantsy, you might want to start a separate thread.
> >> Your
> >> > >> > question
> >> > >> > > > > isn't
> >> > >> > > > > > > >> about 5.4-alpha-3 at all.
> >> > >> > > > > > > >>
> >> > >> > > > > > > >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <
> >> > >> hantsy@yahoo.com.cn>
> >> > >> > > > wrote:
> >> > >> > > > > > > >>
> >> > >> > > > > > > >>> I want to know if Tapestry has plan to integrate
> with
> >> > Java
> >> > >> > EE,
> >> > >> > > > such
> >> > >> > > > > > as
> >> > >> > > > > > > >>> how to use CDI with Tapestry, I know Tapestry has
> >> its DI
> >> > >> > > > container,
> >> > >> > > > > > it
> >> > >> > > > > > > >>> can be replaced with CDI?
> >> > >> > > > > > > >>>
> >> > >> > > > > > > >>> I have used Tapestry4 before, and know little about
> >> the
> >> > >> > newest
> >> > >> > > > > > > Tapestry 5.
> >> > >> > > > > > > >>>
> >> > >> > > > > > > >>>
> >> > >> > > > > > > >>> Hantsy
> >> > >> > > > > > > >>> On 4/7/2013 09:11, Saeed wrote:
> >> > >> > > > > > > >>>> Great news! jQuery finally. Well done sire!
> >> > >> > > > > > > >>>>
> >> > >> > > > > > > >>>>
> >> > >> > > > > > > >>>>
> >> > >> > > > > > > >>>>
> >> > >> > > > > > > >>>>
> >> > >> > > > > > > >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis
> Ship <
> >> > >> > > > > > hlship@gmail.com>
> >> > >> > > > > > > >>> wrote:
> >> > >> > > > > > > >>>>> Hot off the presses! The latest preview release
> of
> >> > >> > Tapestry,
> >> > >> > > > > > > >>> 5.4-alpha-3,
> >> > >> > > > > > > >>>>> is now available.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> Point your build tool of choice at the Maven
> >> > repository:
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>
> >> > >> > > > > > >
> >> > >> > > > > >
> >> > >> > > > >
> >> > >> > > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
> >> > >> > > > > > > >>>>> Binary and source archives:
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>>
> >> http://people.apache.org/~hlship/tapestry-releases/
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> What's new?
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> So much, I've kind of lost track; the main
> changes
> >> > are:
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> Most assets are now accessed using a URL that
> >> > >> incorporates
> >> > >> > a
> >> > >> > > > > > Adler32
> >> > >> > > > > > > >>>>> checksum of the asset content. Prior versions of
> >> > >> Tapestry
> >> > >> > > > > > > incorporated
> >> > >> > > > > > > >>> the
> >> > >> > > > > > > >>>>> application version number into the URL.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> What does this mean? When you redeploy your web
> >> > >> > application,
> >> > >> > > > > most
> >> > >> > > > > > > >>> assets
> >> > >> > > > > > > >>>>> will have not changed: same content, same path,
> >> same
> >> > >> > > checksum,
> >> > >> > > > > > > >>> therefore,
> >> > >> > > > > > > >>>>> same URL. This means that client browsers will
> not
> >> > have
> >> > >> to
> >> > >> > > > > > > re-download
> >> > >> > > > > > > >>> all
> >> > >> > > > > > > >>>>> those assets again just because the application
> >> > version
> >> > >> > > number
> >> > >> > > > > has
> >> > >> > > > > > > >>> changed.
> >> > >> > > > > > > >>>>> Assets that have changed will have a different
> >> content
> >> > >> > hash,
> >> > >> > > > and
> >> > >> > > > > > > >>> therefore,
> >> > >> > > > > > > >>>>> a different asset URL. Browsers will be sure to
> >> pull
> >> > >> down
> >> > >> > > those
> >> > >> > > > > new
> >> > >> > > > > > > >>>>> versions.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> Modules are slightly different; because all
> >> JavaScript
> >> > >> > > modules
> >> > >> > > > > are
> >> > >> > > > > > > >>> expected
> >> > >> > > > > > > >>>>> to start in a common root URL, there is no
> >> reasonable
> >> > >> way
> >> > >> > to
> >> > >> > > > > > > generate a
> >> > >> > > > > > > >>>>> unique content hash for each; module URLs still
> use
> >> > the
> >> > >> > > > > application
> >> > >> > > > > > > >>> version
> >> > >> > > > > > > >>>>> number. However, modules and all assets now also
> >> send
> >> > an
> >> > >> > ETag
> >> > >> > > > > > header;
> >> > >> > > > > > > >>> this
> >> > >> > > > > > > >>>>> means that module requests will still be sent,
> but
> >> > will
> >> > >> > often
> >> > >> > > > > get a
> >> > >> > > > > > > 304
> >> > >> > > > > > > >>>>> (resource not modified) response.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> Obviously, this is a big change, and we're
> >> welcoming
> >> > >> > > feedback.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> Next up; we have first class support for jQuery.A
> >> > little
> >> > >> > bit
> >> > >> > > of
> >> > >> > > > > > > symbol
> >> > >> > > > > > > >>>>> tweaking, and Prototype and Scriptaculous are
> >> simply
> >> > >> gone
> >> > >> > for
> >> > >> > > > > good.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> There's also been improvements to operation
> >> tracking,
> >> > >> with
> >> > >> > > more
> >> > >> > > > > > > >>> operations
> >> > >> > > > > > > >>>>> performed during a request being tracked. This is
> >> > useful
> >> > >> > for
> >> > >> > > > the
> >> > >> > > > > > > part of
> >> > >> > > > > > > >>>>> the exception report page that discusses what
> >> Tapestry
> >> > >> did
> >> > >> > > > > during a
> >> > >> > > > > > > >>>>> request, leading up to the actual exception.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> There's been big improvements, c/o Kalle, in
> terms
> >> of
> >> > >> how
> >> > >> > > > > > exceptions
> >> > >> > > > > > > are
> >> > >> > > > > > > >>>>> reported, with finer control over what gets the
> >> full
> >> > >> > > exception
> >> > >> > > > > > page,
> >> > >> > > > > > > and
> >> > >> > > > > > > >>>>> what doesn't.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> For the rare places where public interfaces
> >> changed in
> >> > >> > > > > incompatible
> >> > >> > > > > > > >>> ways,
> >> > >> > > > > > > >>>>> there's now an @IncompatibleChange annotation for
> >> > >> methods
> >> > >> > > that
> >> > >> > > > > have
> >> > >> > > > > > > >>>>> changed.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> A few informational pages such as PageCatalog,
> >> > >> > ServiceStatus,
> >> > >> > > > and
> >> > >> > > > > > > >>> Hibernate
> >> > >> > > > > > > >>>>> Statistics have been merged into a new single
> >> > >> (extensible)
> >> > >> > > > page,
> >> > >> > > > > > > >>>>> T5Dashboard.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> ... and lots more little changes, fixes, and
> >> > >> improvements.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> There's still a lot more to come, however. Two
> >> > >> principle
> >> > >> > > > > > > improvements
> >> > >> > > > > > > >>> I'm
> >> > >> > > > > > > >>>>> targeting for 5.4:
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> Proper server-side push/websocket support.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> Built-in performance monitoring and reporting.
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> --
> >> > >> > > > > > > >>>>> Howard M. Lewis Ship
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> Creator of Apache Tapestry
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> The source for Tapestry training, mentoring and
> >> > support.
> >> > >> > > > Contact
> >> > >> > > > > me
> >> > >> > > > > > > to
> >> > >> > > > > > > >>>>> learn how I can get you up and productive in
> >> Tapestry
> >> > >> fast!
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>>> (971) 678-5210
> >> > >> > > > > > > >>>>> http://howardlewisship.com
> >> > >> > > > > > > >>>>>
> >> > >> > > > > > > >>>
> >> > >> > > > > > > >>>
> >> > >> > > > >
> >> > >>
> ---------------------------------------------------------------------
> >> > >> > > > > > > >>> To unsubscribe, e-mail:
> >> > >> > users-unsubscribe@tapestry.apache.org
> >> > >> > > > > > > >>> For additional commands, e-mail:
> >> > >> > > users-help@tapestry.apache.org
> >> > >> > > > > > > >>>
> >> > >> > > > > > > >>>
> >> > >> > > > > > > >
> >> > >> > > > > > > >
> >> > >> > > > > > > >
> >> > >> > > >
> >> > >>
> ---------------------------------------------------------------------
> >> > >> > > > > > > > To unsubscribe, e-mail:
> >> > >> users-unsubscribe@tapestry.apache.org
> >> > >> > > > > > > > For additional commands, e-mail:
> >> > >> > users-help@tapestry.apache.org
> >> > >> > > > > > > >
> >> > >> > > > > > >
> >> > >> > > > > > >
> >> > >> > > > > > >
> >> > >> > > > > > > --
> >> > >> > > > > > > George Christman
> >> > >> > > > > > > www.CarDaddy.com
> >> > >> > > > > > > P.O. Box 735
> >> > >> > > > > > > Johnstown, New York
> >> > >> > > > > > >
> >> > >> > > > > > >
> >> > >> > >
> >> > ---------------------------------------------------------------------
> >> > >> > > > > > > To unsubscribe, e-mail:
> >> > users-unsubscribe@tapestry.apache.org
> >> > >> > > > > > > For additional commands, e-mail:
> >> > >> users-help@tapestry.apache.org
> >> > >> > > > > > >
> >> > >> > > > > > >
> >> > >> > > > > >
> >> > >> > > > > >
> >> > >> > > > > > --
> >> > >> > > > > > Howard M. Lewis Ship
> >> > >> > > > > >
> >> > >> > > > > > Creator of Apache Tapestry
> >> > >> > > > > >
> >> > >> > > > > > The source for Tapestry training, mentoring and support.
> >> > >> Contact me
> >> > >> > > to
> >> > >> > > > > > learn how I can get you up and productive in Tapestry
> fast!
> >> > >> > > > > >
> >> > >> > > > > > (971) 678-5210
> >> > >> > > > > > http://howardlewisship.com
> >> > >> > > > > >
> >> > >> > > > >
> >> > >> > > >
> >> > >> > > >
> >> > >> > > >
> >> > >> > > > --
> >> > >> > > > Howard M. Lewis Ship
> >> > >> > > >
> >> > >> > > > Creator of Apache Tapestry
> >> > >> > > >
> >> > >> > > > The source for Tapestry training, mentoring and support.
> >> Contact
> >> > me
> >> > >> to
> >> > >> > > > learn how I can get you up and productive in Tapestry fast!
> >> > >> > > >
> >> > >> > > > (971) 678-5210
> >> > >> > > > http://howardlewisship.com
> >> > >> > > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> > >>
> >> > >>
> >> > >> --
> >> > >> Howard M. Lewis Ship
> >> > >>
> >> > >> Creator of Apache Tapestry
> >> > >>
> >> > >> The source for Tapestry training, mentoring and support. Contact me
> >> to
> >> > >> learn how I can get you up and productive in Tapestry fast!
> >> > >>
> >> > >> (971) 678-5210
> >> > >> http://howardlewisship.com
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Howard M. Lewis Ship
> >>
> >> Creator of Apache Tapestry
> >>
> >> The source for Tapestry training, mentoring and support. Contact me to
> >> learn how I can get you up and productive in Tapestry fast!
> >>
> >> (971) 678-5210
> >> http://howardlewisship.com
> >>
> >
> >
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: Tapestry 5.4-alpha-3
Posted by Charlouze <me...@charlouze.com>.
New information about my problem: it's working with classpath assets but it
is not working with context assets.
Am I doing something wrong or is this a bug ?
2013/4/17 Charlouze <me...@charlouze.com>
> I'm 100% sure that my app is not in production mode and my file is not
> packaged in a JAR file.
>
> As I said, it works well when I use the css file without the stack using
> @import.
>
>
> 2013/4/17 Howard Lewis Ship <hl...@gmail.com>
>
>> It is supposed to clear its cache if there's a change to the file. I've
>> tested that manually but don't know if there's an automated test for that.
>>
>> There's no chance you are running in production mode, or have the file in
>> question packaged in a JAR file? Live reload is only for files on the
>> file
>> system itself.
>>
>>
>> On Wed, Apr 17, 2013 at 3:25 PM, Charlouze <me...@charlouze.com> wrote:
>>
>> > I explore the code of the ExtensibleJavaScriptStack class and it
>> calculates
>> > the asset link on first use. Maybe I can disable the checksum in URL ?
>> >
>> >
>> > 2013/4/17 Charlouze <me...@charlouze.com>
>> >
>> > > I build my app with eclipse 3.7.2. I use the m2e plugin (1.1.0) and
>> the
>> > > m2e-wtp (0.15.3) to configure my eclipse project. I'm running the app
>> > using
>> > > the run jetty run plugin (1.3.3). The selected jetty version is 8.1.2.
>> > >
>> > > I just made a small test project (only an index page with nothing but
>> a
>> > > title and the styles.css file). I figured out where the problem is:
>> if I
>> > > load my styles.css through an ExtensibleJavaScriptStack it does'nt
>> work,
>> > > the address is not changing when I add some css rules to the file. If
>> I
>> > use
>> > > @Import(stylesheet = { "context:/css/styles.css" }) on my index page,
>> it
>> > > works well.
>> > >
>> > > Should I file a bug on jira ?
>> > >
>> > >
>> > > 2013/4/17 Howard Lewis Ship <hl...@gmail.com>
>> > >
>> > >> When you refresh your page, it *should* be building a new URL to the
>> > >> updated asset. The particulars matter here ... how exactly are you
>> > >> building & running the app?
>> > >>
>> > >>
>> > >> On Wed, Apr 17, 2013 at 9:31 AM, Charlouze <me...@charlouze.com> wrote:
>> > >>
>> > >> > Hey everyone,
>> > >> >
>> > >> > I have some trouble with the 5.4-alpha-3. When I add some stuff to
>> my
>> > >> > styles.css file, it get another address to access it (that is
>> > perfectly
>> > >> > normal according to the new asset feature). The problem is that if
>> I
>> > >> don't
>> > >> > restart my application my pages tries to load my styles.css file
>> from
>> > >> the
>> > >> > old address. I probably miss somthing.
>> > >> >
>> > >> > For your information, I'm am in development mode. I use eclipse and
>> > the
>> > >> run
>> > >> > jetty run plugin.
>> > >> >
>> > >> > Charles.
>> > >> >
>> > >> >
>> > >> > 2013/4/12 François Facon <fr...@atos.net>
>> > >> >
>> > >> > > By the way, tapestry5-portlet is also ready to be used with 5.4.
>> But
>> > >> I am
>> > >> > > still looking for a way to run integration tests inside Pluto
>> with
>> > >> > Gradle.
>> > >> > > Perhaps the use of Arquillian with Pluto under gradle is the
>> > solution.
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
>> > >> > >
>> > >> > > > That's great news!
>> > >> > > >
>> > >> > > >
>> > >> > > > On Fri, Apr 12, 2013 at 12:35 PM, François Facon <
>> > >> > > francois.facon@atos.net
>> > >> > > > >wrote:
>> > >> > > >
>> > >> > > > > Thanks to Emmanuel, tapestry-jquery is already working fine
>> with
>> > >> 5.4.
>> > >> > > > >
>> > >> > > > >
>> > >> > > > >
>> > >> > > > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
>> > >> > > > >
>> > >> > > > > > We don't control the tapestry-jquery library; I actually
>> > haven't
>> > >> > > looked
>> > >> > > > > at
>> > >> > > > > > it. I suspect it will need to be reworked significantly for
>> > 5.4.
>> > >> > > > > >
>> > >> > > > > >
>> > >> > > > > > On Fri, Apr 12, 2013 at 9:40 AM, George Christman
>> > >> > > > > > <gc...@cardaddy.com>wrote:
>> > >> > > > > >
>> > >> > > > > > > I'm just curious if Tapestry5.4 will just be integrating
>> the
>> > >> > > > > > > Tapestry-Jquery library?
>> > >> > > > > > >
>> > >> > > > > > > On Sun, Apr 7, 2013 at 10:29 AM, hantsy <
>> > hantsy@yahoo.com.cn>
>> > >> > > wrote:
>> > >> > > > > > > >
>> > >> > > > > > > > Created a new thread for it. Thanks
>> > >> > > > > > > >
>> > >> > > > > > > > On 4/7/2013 22:16, Bob Harner wrote:
>> > >> > > > > > > >> Hantsy, you might want to start a separate thread.
>> Your
>> > >> > question
>> > >> > > > > isn't
>> > >> > > > > > > >> about 5.4-alpha-3 at all.
>> > >> > > > > > > >>
>> > >> > > > > > > >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <
>> > >> hantsy@yahoo.com.cn>
>> > >> > > > wrote:
>> > >> > > > > > > >>
>> > >> > > > > > > >>> I want to know if Tapestry has plan to integrate with
>> > Java
>> > >> > EE,
>> > >> > > > such
>> > >> > > > > > as
>> > >> > > > > > > >>> how to use CDI with Tapestry, I know Tapestry has
>> its DI
>> > >> > > > container,
>> > >> > > > > > it
>> > >> > > > > > > >>> can be replaced with CDI?
>> > >> > > > > > > >>>
>> > >> > > > > > > >>> I have used Tapestry4 before, and know little about
>> the
>> > >> > newest
>> > >> > > > > > > Tapestry 5.
>> > >> > > > > > > >>>
>> > >> > > > > > > >>>
>> > >> > > > > > > >>> Hantsy
>> > >> > > > > > > >>> On 4/7/2013 09:11, Saeed wrote:
>> > >> > > > > > > >>>> Great news! jQuery finally. Well done sire!
>> > >> > > > > > > >>>>
>> > >> > > > > > > >>>>
>> > >> > > > > > > >>>>
>> > >> > > > > > > >>>>
>> > >> > > > > > > >>>>
>> > >> > > > > > > >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <
>> > >> > > > > > hlship@gmail.com>
>> > >> > > > > > > >>> wrote:
>> > >> > > > > > > >>>>> Hot off the presses! The latest preview release of
>> > >> > Tapestry,
>> > >> > > > > > > >>> 5.4-alpha-3,
>> > >> > > > > > > >>>>> is now available.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> Point your build tool of choice at the Maven
>> > repository:
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>
>> > >> > > > > > >
>> > >> > > > > >
>> > >> > > > >
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> >
>> https://repository.apache.org/content/repositories/orgapachetapestry-072/
>> > >> > > > > > > >>>>> Binary and source archives:
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>>
>> http://people.apache.org/~hlship/tapestry-releases/
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> What's new?
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> So much, I've kind of lost track; the main changes
>> > are:
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> Most assets are now accessed using a URL that
>> > >> incorporates
>> > >> > a
>> > >> > > > > > Adler32
>> > >> > > > > > > >>>>> checksum of the asset content. Prior versions of
>> > >> Tapestry
>> > >> > > > > > > incorporated
>> > >> > > > > > > >>> the
>> > >> > > > > > > >>>>> application version number into the URL.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> What does this mean? When you redeploy your web
>> > >> > application,
>> > >> > > > > most
>> > >> > > > > > > >>> assets
>> > >> > > > > > > >>>>> will have not changed: same content, same path,
>> same
>> > >> > > checksum,
>> > >> > > > > > > >>> therefore,
>> > >> > > > > > > >>>>> same URL. This means that client browsers will not
>> > have
>> > >> to
>> > >> > > > > > > re-download
>> > >> > > > > > > >>> all
>> > >> > > > > > > >>>>> those assets again just because the application
>> > version
>> > >> > > number
>> > >> > > > > has
>> > >> > > > > > > >>> changed.
>> > >> > > > > > > >>>>> Assets that have changed will have a different
>> content
>> > >> > hash,
>> > >> > > > and
>> > >> > > > > > > >>> therefore,
>> > >> > > > > > > >>>>> a different asset URL. Browsers will be sure to
>> pull
>> > >> down
>> > >> > > those
>> > >> > > > > new
>> > >> > > > > > > >>>>> versions.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> Modules are slightly different; because all
>> JavaScript
>> > >> > > modules
>> > >> > > > > are
>> > >> > > > > > > >>> expected
>> > >> > > > > > > >>>>> to start in a common root URL, there is no
>> reasonable
>> > >> way
>> > >> > to
>> > >> > > > > > > generate a
>> > >> > > > > > > >>>>> unique content hash for each; module URLs still use
>> > the
>> > >> > > > > application
>> > >> > > > > > > >>> version
>> > >> > > > > > > >>>>> number. However, modules and all assets now also
>> send
>> > an
>> > >> > ETag
>> > >> > > > > > header;
>> > >> > > > > > > >>> this
>> > >> > > > > > > >>>>> means that module requests will still be sent, but
>> > will
>> > >> > often
>> > >> > > > > get a
>> > >> > > > > > > 304
>> > >> > > > > > > >>>>> (resource not modified) response.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> Obviously, this is a big change, and we're
>> welcoming
>> > >> > > feedback.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> Next up; we have first class support for jQuery.A
>> > little
>> > >> > bit
>> > >> > > of
>> > >> > > > > > > symbol
>> > >> > > > > > > >>>>> tweaking, and Prototype and Scriptaculous are
>> simply
>> > >> gone
>> > >> > for
>> > >> > > > > good.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> There's also been improvements to operation
>> tracking,
>> > >> with
>> > >> > > more
>> > >> > > > > > > >>> operations
>> > >> > > > > > > >>>>> performed during a request being tracked. This is
>> > useful
>> > >> > for
>> > >> > > > the
>> > >> > > > > > > part of
>> > >> > > > > > > >>>>> the exception report page that discusses what
>> Tapestry
>> > >> did
>> > >> > > > > during a
>> > >> > > > > > > >>>>> request, leading up to the actual exception.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> There's been big improvements, c/o Kalle, in terms
>> of
>> > >> how
>> > >> > > > > > exceptions
>> > >> > > > > > > are
>> > >> > > > > > > >>>>> reported, with finer control over what gets the
>> full
>> > >> > > exception
>> > >> > > > > > page,
>> > >> > > > > > > and
>> > >> > > > > > > >>>>> what doesn't.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> For the rare places where public interfaces
>> changed in
>> > >> > > > > incompatible
>> > >> > > > > > > >>> ways,
>> > >> > > > > > > >>>>> there's now an @IncompatibleChange annotation for
>> > >> methods
>> > >> > > that
>> > >> > > > > have
>> > >> > > > > > > >>>>> changed.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> A few informational pages such as PageCatalog,
>> > >> > ServiceStatus,
>> > >> > > > and
>> > >> > > > > > > >>> Hibernate
>> > >> > > > > > > >>>>> Statistics have been merged into a new single
>> > >> (extensible)
>> > >> > > > page,
>> > >> > > > > > > >>>>> T5Dashboard.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> ... and lots more little changes, fixes, and
>> > >> improvements.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> There's still a lot more to come, however. Two
>> > >> principle
>> > >> > > > > > > improvements
>> > >> > > > > > > >>> I'm
>> > >> > > > > > > >>>>> targeting for 5.4:
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> Proper server-side push/websocket support.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> Built-in performance monitoring and reporting.
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> --
>> > >> > > > > > > >>>>> Howard M. Lewis Ship
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> Creator of Apache Tapestry
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> The source for Tapestry training, mentoring and
>> > support.
>> > >> > > > Contact
>> > >> > > > > me
>> > >> > > > > > > to
>> > >> > > > > > > >>>>> learn how I can get you up and productive in
>> Tapestry
>> > >> fast!
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>>> (971) 678-5210
>> > >> > > > > > > >>>>> http://howardlewisship.com
>> > >> > > > > > > >>>>>
>> > >> > > > > > > >>>
>> > >> > > > > > > >>>
>> > >> > > > >
>> > >> ---------------------------------------------------------------------
>> > >> > > > > > > >>> To unsubscribe, e-mail:
>> > >> > users-unsubscribe@tapestry.apache.org
>> > >> > > > > > > >>> For additional commands, e-mail:
>> > >> > > users-help@tapestry.apache.org
>> > >> > > > > > > >>>
>> > >> > > > > > > >>>
>> > >> > > > > > > >
>> > >> > > > > > > >
>> > >> > > > > > > >
>> > >> > > >
>> > >> ---------------------------------------------------------------------
>> > >> > > > > > > > To unsubscribe, e-mail:
>> > >> users-unsubscribe@tapestry.apache.org
>> > >> > > > > > > > For additional commands, e-mail:
>> > >> > users-help@tapestry.apache.org
>> > >> > > > > > > >
>> > >> > > > > > >
>> > >> > > > > > >
>> > >> > > > > > >
>> > >> > > > > > > --
>> > >> > > > > > > George Christman
>> > >> > > > > > > www.CarDaddy.com
>> > >> > > > > > > P.O. Box 735
>> > >> > > > > > > Johnstown, New York
>> > >> > > > > > >
>> > >> > > > > > >
>> > >> > >
>> > ---------------------------------------------------------------------
>> > >> > > > > > > To unsubscribe, e-mail:
>> > users-unsubscribe@tapestry.apache.org
>> > >> > > > > > > For additional commands, e-mail:
>> > >> users-help@tapestry.apache.org
>> > >> > > > > > >
>> > >> > > > > > >
>> > >> > > > > >
>> > >> > > > > >
>> > >> > > > > > --
>> > >> > > > > > Howard M. Lewis Ship
>> > >> > > > > >
>> > >> > > > > > Creator of Apache Tapestry
>> > >> > > > > >
>> > >> > > > > > The source for Tapestry training, mentoring and support.
>> > >> Contact me
>> > >> > > to
>> > >> > > > > > learn how I can get you up and productive in Tapestry fast!
>> > >> > > > > >
>> > >> > > > > > (971) 678-5210
>> > >> > > > > > http://howardlewisship.com
>> > >> > > > > >
>> > >> > > > >
>> > >> > > >
>> > >> > > >
>> > >> > > >
>> > >> > > > --
>> > >> > > > Howard M. Lewis Ship
>> > >> > > >
>> > >> > > > Creator of Apache Tapestry
>> > >> > > >
>> > >> > > > The source for Tapestry training, mentoring and support.
>> Contact
>> > me
>> > >> to
>> > >> > > > learn how I can get you up and productive in Tapestry fast!
>> > >> > > >
>> > >> > > > (971) 678-5210
>> > >> > > > http://howardlewisship.com
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> Howard M. Lewis Ship
>> > >>
>> > >> Creator of Apache Tapestry
>> > >>
>> > >> The source for Tapestry training, mentoring and support. Contact me
>> to
>> > >> learn how I can get you up and productive in Tapestry fast!
>> > >>
>> > >> (971) 678-5210
>> > >> http://howardlewisship.com
>> > >>
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator of Apache Tapestry
>>
>> The source for Tapestry training, mentoring and support. Contact me to
>> learn how I can get you up and productive in Tapestry fast!
>>
>> (971) 678-5210
>> http://howardlewisship.com
>>
>
>
Re: Tapestry 5.4-alpha-3
Posted by Charlouze <me...@charlouze.com>.
I'm 100% sure that my app is not in production mode and my file is not
packaged in a JAR file.
As I said, it works well when I use the css file without the stack using
@import.
2013/4/17 Howard Lewis Ship <hl...@gmail.com>
> It is supposed to clear its cache if there's a change to the file. I've
> tested that manually but don't know if there's an automated test for that.
>
> There's no chance you are running in production mode, or have the file in
> question packaged in a JAR file? Live reload is only for files on the file
> system itself.
>
>
> On Wed, Apr 17, 2013 at 3:25 PM, Charlouze <me...@charlouze.com> wrote:
>
> > I explore the code of the ExtensibleJavaScriptStack class and it
> calculates
> > the asset link on first use. Maybe I can disable the checksum in URL ?
> >
> >
> > 2013/4/17 Charlouze <me...@charlouze.com>
> >
> > > I build my app with eclipse 3.7.2. I use the m2e plugin (1.1.0) and the
> > > m2e-wtp (0.15.3) to configure my eclipse project. I'm running the app
> > using
> > > the run jetty run plugin (1.3.3). The selected jetty version is 8.1.2.
> > >
> > > I just made a small test project (only an index page with nothing but a
> > > title and the styles.css file). I figured out where the problem is: if
> I
> > > load my styles.css through an ExtensibleJavaScriptStack it does'nt
> work,
> > > the address is not changing when I add some css rules to the file. If I
> > use
> > > @Import(stylesheet = { "context:/css/styles.css" }) on my index page,
> it
> > > works well.
> > >
> > > Should I file a bug on jira ?
> > >
> > >
> > > 2013/4/17 Howard Lewis Ship <hl...@gmail.com>
> > >
> > >> When you refresh your page, it *should* be building a new URL to the
> > >> updated asset. The particulars matter here ... how exactly are you
> > >> building & running the app?
> > >>
> > >>
> > >> On Wed, Apr 17, 2013 at 9:31 AM, Charlouze <me...@charlouze.com> wrote:
> > >>
> > >> > Hey everyone,
> > >> >
> > >> > I have some trouble with the 5.4-alpha-3. When I add some stuff to
> my
> > >> > styles.css file, it get another address to access it (that is
> > perfectly
> > >> > normal according to the new asset feature). The problem is that if I
> > >> don't
> > >> > restart my application my pages tries to load my styles.css file
> from
> > >> the
> > >> > old address. I probably miss somthing.
> > >> >
> > >> > For your information, I'm am in development mode. I use eclipse and
> > the
> > >> run
> > >> > jetty run plugin.
> > >> >
> > >> > Charles.
> > >> >
> > >> >
> > >> > 2013/4/12 François Facon <fr...@atos.net>
> > >> >
> > >> > > By the way, tapestry5-portlet is also ready to be used with 5.4.
> But
> > >> I am
> > >> > > still looking for a way to run integration tests inside Pluto with
> > >> > Gradle.
> > >> > > Perhaps the use of Arquillian with Pluto under gradle is the
> > solution.
> > >> > >
> > >> > >
> > >> > >
> > >> > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> > >> > >
> > >> > > > That's great news!
> > >> > > >
> > >> > > >
> > >> > > > On Fri, Apr 12, 2013 at 12:35 PM, François Facon <
> > >> > > francois.facon@atos.net
> > >> > > > >wrote:
> > >> > > >
> > >> > > > > Thanks to Emmanuel, tapestry-jquery is already working fine
> with
> > >> 5.4.
> > >> > > > >
> > >> > > > >
> > >> > > > >
> > >> > > > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> > >> > > > >
> > >> > > > > > We don't control the tapestry-jquery library; I actually
> > haven't
> > >> > > looked
> > >> > > > > at
> > >> > > > > > it. I suspect it will need to be reworked significantly for
> > 5.4.
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > On Fri, Apr 12, 2013 at 9:40 AM, George Christman
> > >> > > > > > <gc...@cardaddy.com>wrote:
> > >> > > > > >
> > >> > > > > > > I'm just curious if Tapestry5.4 will just be integrating
> the
> > >> > > > > > > Tapestry-Jquery library?
> > >> > > > > > >
> > >> > > > > > > On Sun, Apr 7, 2013 at 10:29 AM, hantsy <
> > hantsy@yahoo.com.cn>
> > >> > > wrote:
> > >> > > > > > > >
> > >> > > > > > > > Created a new thread for it. Thanks
> > >> > > > > > > >
> > >> > > > > > > > On 4/7/2013 22:16, Bob Harner wrote:
> > >> > > > > > > >> Hantsy, you might want to start a separate thread. Your
> > >> > question
> > >> > > > > isn't
> > >> > > > > > > >> about 5.4-alpha-3 at all.
> > >> > > > > > > >>
> > >> > > > > > > >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <
> > >> hantsy@yahoo.com.cn>
> > >> > > > wrote:
> > >> > > > > > > >>
> > >> > > > > > > >>> I want to know if Tapestry has plan to integrate with
> > Java
> > >> > EE,
> > >> > > > such
> > >> > > > > > as
> > >> > > > > > > >>> how to use CDI with Tapestry, I know Tapestry has its
> DI
> > >> > > > container,
> > >> > > > > > it
> > >> > > > > > > >>> can be replaced with CDI?
> > >> > > > > > > >>>
> > >> > > > > > > >>> I have used Tapestry4 before, and know little about
> the
> > >> > newest
> > >> > > > > > > Tapestry 5.
> > >> > > > > > > >>>
> > >> > > > > > > >>>
> > >> > > > > > > >>> Hantsy
> > >> > > > > > > >>> On 4/7/2013 09:11, Saeed wrote:
> > >> > > > > > > >>>> Great news! jQuery finally. Well done sire!
> > >> > > > > > > >>>>
> > >> > > > > > > >>>>
> > >> > > > > > > >>>>
> > >> > > > > > > >>>>
> > >> > > > > > > >>>>
> > >> > > > > > > >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <
> > >> > > > > > hlship@gmail.com>
> > >> > > > > > > >>> wrote:
> > >> > > > > > > >>>>> Hot off the presses! The latest preview release of
> > >> > Tapestry,
> > >> > > > > > > >>> 5.4-alpha-3,
> > >> > > > > > > >>>>> is now available.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> Point your build tool of choice at the Maven
> > repository:
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
> > >> > > > > > > >>>>> Binary and source archives:
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> http://people.apache.org/~hlship/tapestry-releases/
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> What's new?
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> So much, I've kind of lost track; the main changes
> > are:
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> Most assets are now accessed using a URL that
> > >> incorporates
> > >> > a
> > >> > > > > > Adler32
> > >> > > > > > > >>>>> checksum of the asset content. Prior versions of
> > >> Tapestry
> > >> > > > > > > incorporated
> > >> > > > > > > >>> the
> > >> > > > > > > >>>>> application version number into the URL.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> What does this mean? When you redeploy your web
> > >> > application,
> > >> > > > > most
> > >> > > > > > > >>> assets
> > >> > > > > > > >>>>> will have not changed: same content, same path, same
> > >> > > checksum,
> > >> > > > > > > >>> therefore,
> > >> > > > > > > >>>>> same URL. This means that client browsers will not
> > have
> > >> to
> > >> > > > > > > re-download
> > >> > > > > > > >>> all
> > >> > > > > > > >>>>> those assets again just because the application
> > version
> > >> > > number
> > >> > > > > has
> > >> > > > > > > >>> changed.
> > >> > > > > > > >>>>> Assets that have changed will have a different
> content
> > >> > hash,
> > >> > > > and
> > >> > > > > > > >>> therefore,
> > >> > > > > > > >>>>> a different asset URL. Browsers will be sure to pull
> > >> down
> > >> > > those
> > >> > > > > new
> > >> > > > > > > >>>>> versions.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> Modules are slightly different; because all
> JavaScript
> > >> > > modules
> > >> > > > > are
> > >> > > > > > > >>> expected
> > >> > > > > > > >>>>> to start in a common root URL, there is no
> reasonable
> > >> way
> > >> > to
> > >> > > > > > > generate a
> > >> > > > > > > >>>>> unique content hash for each; module URLs still use
> > the
> > >> > > > > application
> > >> > > > > > > >>> version
> > >> > > > > > > >>>>> number. However, modules and all assets now also
> send
> > an
> > >> > ETag
> > >> > > > > > header;
> > >> > > > > > > >>> this
> > >> > > > > > > >>>>> means that module requests will still be sent, but
> > will
> > >> > often
> > >> > > > > get a
> > >> > > > > > > 304
> > >> > > > > > > >>>>> (resource not modified) response.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> Obviously, this is a big change, and we're welcoming
> > >> > > feedback.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> Next up; we have first class support for jQuery.A
> > little
> > >> > bit
> > >> > > of
> > >> > > > > > > symbol
> > >> > > > > > > >>>>> tweaking, and Prototype and Scriptaculous are simply
> > >> gone
> > >> > for
> > >> > > > > good.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> There's also been improvements to operation
> tracking,
> > >> with
> > >> > > more
> > >> > > > > > > >>> operations
> > >> > > > > > > >>>>> performed during a request being tracked. This is
> > useful
> > >> > for
> > >> > > > the
> > >> > > > > > > part of
> > >> > > > > > > >>>>> the exception report page that discusses what
> Tapestry
> > >> did
> > >> > > > > during a
> > >> > > > > > > >>>>> request, leading up to the actual exception.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> There's been big improvements, c/o Kalle, in terms
> of
> > >> how
> > >> > > > > > exceptions
> > >> > > > > > > are
> > >> > > > > > > >>>>> reported, with finer control over what gets the full
> > >> > > exception
> > >> > > > > > page,
> > >> > > > > > > and
> > >> > > > > > > >>>>> what doesn't.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> For the rare places where public interfaces changed
> in
> > >> > > > > incompatible
> > >> > > > > > > >>> ways,
> > >> > > > > > > >>>>> there's now an @IncompatibleChange annotation for
> > >> methods
> > >> > > that
> > >> > > > > have
> > >> > > > > > > >>>>> changed.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> A few informational pages such as PageCatalog,
> > >> > ServiceStatus,
> > >> > > > and
> > >> > > > > > > >>> Hibernate
> > >> > > > > > > >>>>> Statistics have been merged into a new single
> > >> (extensible)
> > >> > > > page,
> > >> > > > > > > >>>>> T5Dashboard.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> ... and lots more little changes, fixes, and
> > >> improvements.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> There's still a lot more to come, however. Two
> > >> principle
> > >> > > > > > > improvements
> > >> > > > > > > >>> I'm
> > >> > > > > > > >>>>> targeting for 5.4:
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> Proper server-side push/websocket support.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> Built-in performance monitoring and reporting.
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> --
> > >> > > > > > > >>>>> Howard M. Lewis Ship
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> Creator of Apache Tapestry
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> The source for Tapestry training, mentoring and
> > support.
> > >> > > > Contact
> > >> > > > > me
> > >> > > > > > > to
> > >> > > > > > > >>>>> learn how I can get you up and productive in
> Tapestry
> > >> fast!
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>>> (971) 678-5210
> > >> > > > > > > >>>>> http://howardlewisship.com
> > >> > > > > > > >>>>>
> > >> > > > > > > >>>
> > >> > > > > > > >>>
> > >> > > > >
> > >> ---------------------------------------------------------------------
> > >> > > > > > > >>> To unsubscribe, e-mail:
> > >> > users-unsubscribe@tapestry.apache.org
> > >> > > > > > > >>> For additional commands, e-mail:
> > >> > > users-help@tapestry.apache.org
> > >> > > > > > > >>>
> > >> > > > > > > >>>
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > >
> > >> ---------------------------------------------------------------------
> > >> > > > > > > > To unsubscribe, e-mail:
> > >> users-unsubscribe@tapestry.apache.org
> > >> > > > > > > > For additional commands, e-mail:
> > >> > users-help@tapestry.apache.org
> > >> > > > > > > >
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > > --
> > >> > > > > > > George Christman
> > >> > > > > > > www.CarDaddy.com
> > >> > > > > > > P.O. Box 735
> > >> > > > > > > Johnstown, New York
> > >> > > > > > >
> > >> > > > > > >
> > >> > >
> > ---------------------------------------------------------------------
> > >> > > > > > > To unsubscribe, e-mail:
> > users-unsubscribe@tapestry.apache.org
> > >> > > > > > > For additional commands, e-mail:
> > >> users-help@tapestry.apache.org
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > --
> > >> > > > > > Howard M. Lewis Ship
> > >> > > > > >
> > >> > > > > > Creator of Apache Tapestry
> > >> > > > > >
> > >> > > > > > The source for Tapestry training, mentoring and support.
> > >> Contact me
> > >> > > to
> > >> > > > > > learn how I can get you up and productive in Tapestry fast!
> > >> > > > > >
> > >> > > > > > (971) 678-5210
> > >> > > > > > http://howardlewisship.com
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > --
> > >> > > > Howard M. Lewis Ship
> > >> > > >
> > >> > > > Creator of Apache Tapestry
> > >> > > >
> > >> > > > The source for Tapestry training, mentoring and support. Contact
> > me
> > >> to
> > >> > > > learn how I can get you up and productive in Tapestry fast!
> > >> > > >
> > >> > > > (971) 678-5210
> > >> > > > http://howardlewisship.com
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Howard M. Lewis Ship
> > >>
> > >> Creator of Apache Tapestry
> > >>
> > >> The source for Tapestry training, mentoring and support. Contact me to
> > >> learn how I can get you up and productive in Tapestry fast!
> > >>
> > >> (971) 678-5210
> > >> http://howardlewisship.com
> > >>
> > >
> > >
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
Re: Tapestry 5.4-alpha-3
Posted by Howard Lewis Ship <hl...@gmail.com>.
It is supposed to clear its cache if there's a change to the file. I've
tested that manually but don't know if there's an automated test for that.
There's no chance you are running in production mode, or have the file in
question packaged in a JAR file? Live reload is only for files on the file
system itself.
On Wed, Apr 17, 2013 at 3:25 PM, Charlouze <me...@charlouze.com> wrote:
> I explore the code of the ExtensibleJavaScriptStack class and it calculates
> the asset link on first use. Maybe I can disable the checksum in URL ?
>
>
> 2013/4/17 Charlouze <me...@charlouze.com>
>
> > I build my app with eclipse 3.7.2. I use the m2e plugin (1.1.0) and the
> > m2e-wtp (0.15.3) to configure my eclipse project. I'm running the app
> using
> > the run jetty run plugin (1.3.3). The selected jetty version is 8.1.2.
> >
> > I just made a small test project (only an index page with nothing but a
> > title and the styles.css file). I figured out where the problem is: if I
> > load my styles.css through an ExtensibleJavaScriptStack it does'nt work,
> > the address is not changing when I add some css rules to the file. If I
> use
> > @Import(stylesheet = { "context:/css/styles.css" }) on my index page, it
> > works well.
> >
> > Should I file a bug on jira ?
> >
> >
> > 2013/4/17 Howard Lewis Ship <hl...@gmail.com>
> >
> >> When you refresh your page, it *should* be building a new URL to the
> >> updated asset. The particulars matter here ... how exactly are you
> >> building & running the app?
> >>
> >>
> >> On Wed, Apr 17, 2013 at 9:31 AM, Charlouze <me...@charlouze.com> wrote:
> >>
> >> > Hey everyone,
> >> >
> >> > I have some trouble with the 5.4-alpha-3. When I add some stuff to my
> >> > styles.css file, it get another address to access it (that is
> perfectly
> >> > normal according to the new asset feature). The problem is that if I
> >> don't
> >> > restart my application my pages tries to load my styles.css file from
> >> the
> >> > old address. I probably miss somthing.
> >> >
> >> > For your information, I'm am in development mode. I use eclipse and
> the
> >> run
> >> > jetty run plugin.
> >> >
> >> > Charles.
> >> >
> >> >
> >> > 2013/4/12 François Facon <fr...@atos.net>
> >> >
> >> > > By the way, tapestry5-portlet is also ready to be used with 5.4. But
> >> I am
> >> > > still looking for a way to run integration tests inside Pluto with
> >> > Gradle.
> >> > > Perhaps the use of Arquillian with Pluto under gradle is the
> solution.
> >> > >
> >> > >
> >> > >
> >> > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> >> > >
> >> > > > That's great news!
> >> > > >
> >> > > >
> >> > > > On Fri, Apr 12, 2013 at 12:35 PM, François Facon <
> >> > > francois.facon@atos.net
> >> > > > >wrote:
> >> > > >
> >> > > > > Thanks to Emmanuel, tapestry-jquery is already working fine with
> >> 5.4.
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> >> > > > >
> >> > > > > > We don't control the tapestry-jquery library; I actually
> haven't
> >> > > looked
> >> > > > > at
> >> > > > > > it. I suspect it will need to be reworked significantly for
> 5.4.
> >> > > > > >
> >> > > > > >
> >> > > > > > On Fri, Apr 12, 2013 at 9:40 AM, George Christman
> >> > > > > > <gc...@cardaddy.com>wrote:
> >> > > > > >
> >> > > > > > > I'm just curious if Tapestry5.4 will just be integrating the
> >> > > > > > > Tapestry-Jquery library?
> >> > > > > > >
> >> > > > > > > On Sun, Apr 7, 2013 at 10:29 AM, hantsy <
> hantsy@yahoo.com.cn>
> >> > > wrote:
> >> > > > > > > >
> >> > > > > > > > Created a new thread for it. Thanks
> >> > > > > > > >
> >> > > > > > > > On 4/7/2013 22:16, Bob Harner wrote:
> >> > > > > > > >> Hantsy, you might want to start a separate thread. Your
> >> > question
> >> > > > > isn't
> >> > > > > > > >> about 5.4-alpha-3 at all.
> >> > > > > > > >>
> >> > > > > > > >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <
> >> hantsy@yahoo.com.cn>
> >> > > > wrote:
> >> > > > > > > >>
> >> > > > > > > >>> I want to know if Tapestry has plan to integrate with
> Java
> >> > EE,
> >> > > > such
> >> > > > > > as
> >> > > > > > > >>> how to use CDI with Tapestry, I know Tapestry has its DI
> >> > > > container,
> >> > > > > > it
> >> > > > > > > >>> can be replaced with CDI?
> >> > > > > > > >>>
> >> > > > > > > >>> I have used Tapestry4 before, and know little about the
> >> > newest
> >> > > > > > > Tapestry 5.
> >> > > > > > > >>>
> >> > > > > > > >>>
> >> > > > > > > >>> Hantsy
> >> > > > > > > >>> On 4/7/2013 09:11, Saeed wrote:
> >> > > > > > > >>>> Great news! jQuery finally. Well done sire!
> >> > > > > > > >>>>
> >> > > > > > > >>>>
> >> > > > > > > >>>>
> >> > > > > > > >>>>
> >> > > > > > > >>>>
> >> > > > > > > >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <
> >> > > > > > hlship@gmail.com>
> >> > > > > > > >>> wrote:
> >> > > > > > > >>>>> Hot off the presses! The latest preview release of
> >> > Tapestry,
> >> > > > > > > >>> 5.4-alpha-3,
> >> > > > > > > >>>>> is now available.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> Point your build tool of choice at the Maven
> repository:
> >> > > > > > > >>>>>
> >> > > > > > > >>>>>
> >> > > > > > > >>>
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
> >> > > > > > > >>>>> Binary and source archives:
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> http://people.apache.org/~hlship/tapestry-releases/
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> What's new?
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> So much, I've kind of lost track; the main changes
> are:
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> Most assets are now accessed using a URL that
> >> incorporates
> >> > a
> >> > > > > > Adler32
> >> > > > > > > >>>>> checksum of the asset content. Prior versions of
> >> Tapestry
> >> > > > > > > incorporated
> >> > > > > > > >>> the
> >> > > > > > > >>>>> application version number into the URL.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> What does this mean? When you redeploy your web
> >> > application,
> >> > > > > most
> >> > > > > > > >>> assets
> >> > > > > > > >>>>> will have not changed: same content, same path, same
> >> > > checksum,
> >> > > > > > > >>> therefore,
> >> > > > > > > >>>>> same URL. This means that client browsers will not
> have
> >> to
> >> > > > > > > re-download
> >> > > > > > > >>> all
> >> > > > > > > >>>>> those assets again just because the application
> version
> >> > > number
> >> > > > > has
> >> > > > > > > >>> changed.
> >> > > > > > > >>>>> Assets that have changed will have a different content
> >> > hash,
> >> > > > and
> >> > > > > > > >>> therefore,
> >> > > > > > > >>>>> a different asset URL. Browsers will be sure to pull
> >> down
> >> > > those
> >> > > > > new
> >> > > > > > > >>>>> versions.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> Modules are slightly different; because all JavaScript
> >> > > modules
> >> > > > > are
> >> > > > > > > >>> expected
> >> > > > > > > >>>>> to start in a common root URL, there is no reasonable
> >> way
> >> > to
> >> > > > > > > generate a
> >> > > > > > > >>>>> unique content hash for each; module URLs still use
> the
> >> > > > > application
> >> > > > > > > >>> version
> >> > > > > > > >>>>> number. However, modules and all assets now also send
> an
> >> > ETag
> >> > > > > > header;
> >> > > > > > > >>> this
> >> > > > > > > >>>>> means that module requests will still be sent, but
> will
> >> > often
> >> > > > > get a
> >> > > > > > > 304
> >> > > > > > > >>>>> (resource not modified) response.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> Obviously, this is a big change, and we're welcoming
> >> > > feedback.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> Next up; we have first class support for jQuery.A
> little
> >> > bit
> >> > > of
> >> > > > > > > symbol
> >> > > > > > > >>>>> tweaking, and Prototype and Scriptaculous are simply
> >> gone
> >> > for
> >> > > > > good.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> There's also been improvements to operation tracking,
> >> with
> >> > > more
> >> > > > > > > >>> operations
> >> > > > > > > >>>>> performed during a request being tracked. This is
> useful
> >> > for
> >> > > > the
> >> > > > > > > part of
> >> > > > > > > >>>>> the exception report page that discusses what Tapestry
> >> did
> >> > > > > during a
> >> > > > > > > >>>>> request, leading up to the actual exception.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> There's been big improvements, c/o Kalle, in terms of
> >> how
> >> > > > > > exceptions
> >> > > > > > > are
> >> > > > > > > >>>>> reported, with finer control over what gets the full
> >> > > exception
> >> > > > > > page,
> >> > > > > > > and
> >> > > > > > > >>>>> what doesn't.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> For the rare places where public interfaces changed in
> >> > > > > incompatible
> >> > > > > > > >>> ways,
> >> > > > > > > >>>>> there's now an @IncompatibleChange annotation for
> >> methods
> >> > > that
> >> > > > > have
> >> > > > > > > >>>>> changed.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> A few informational pages such as PageCatalog,
> >> > ServiceStatus,
> >> > > > and
> >> > > > > > > >>> Hibernate
> >> > > > > > > >>>>> Statistics have been merged into a new single
> >> (extensible)
> >> > > > page,
> >> > > > > > > >>>>> T5Dashboard.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> ... and lots more little changes, fixes, and
> >> improvements.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> There's still a lot more to come, however. Two
> >> principle
> >> > > > > > > improvements
> >> > > > > > > >>> I'm
> >> > > > > > > >>>>> targeting for 5.4:
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> Proper server-side push/websocket support.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> Built-in performance monitoring and reporting.
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> --
> >> > > > > > > >>>>> Howard M. Lewis Ship
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> Creator of Apache Tapestry
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> The source for Tapestry training, mentoring and
> support.
> >> > > > Contact
> >> > > > > me
> >> > > > > > > to
> >> > > > > > > >>>>> learn how I can get you up and productive in Tapestry
> >> fast!
> >> > > > > > > >>>>>
> >> > > > > > > >>>>> (971) 678-5210
> >> > > > > > > >>>>> http://howardlewisship.com
> >> > > > > > > >>>>>
> >> > > > > > > >>>
> >> > > > > > > >>>
> >> > > > >
> >> ---------------------------------------------------------------------
> >> > > > > > > >>> To unsubscribe, e-mail:
> >> > users-unsubscribe@tapestry.apache.org
> >> > > > > > > >>> For additional commands, e-mail:
> >> > > users-help@tapestry.apache.org
> >> > > > > > > >>>
> >> > > > > > > >>>
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > >
> >> ---------------------------------------------------------------------
> >> > > > > > > > To unsubscribe, e-mail:
> >> users-unsubscribe@tapestry.apache.org
> >> > > > > > > > For additional commands, e-mail:
> >> > users-help@tapestry.apache.org
> >> > > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > --
> >> > > > > > > George Christman
> >> > > > > > > www.CarDaddy.com
> >> > > > > > > P.O. Box 735
> >> > > > > > > Johnstown, New York
> >> > > > > > >
> >> > > > > > >
> >> > >
> ---------------------------------------------------------------------
> >> > > > > > > To unsubscribe, e-mail:
> users-unsubscribe@tapestry.apache.org
> >> > > > > > > For additional commands, e-mail:
> >> users-help@tapestry.apache.org
> >> > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > > --
> >> > > > > > Howard M. Lewis Ship
> >> > > > > >
> >> > > > > > Creator of Apache Tapestry
> >> > > > > >
> >> > > > > > The source for Tapestry training, mentoring and support.
> >> Contact me
> >> > > to
> >> > > > > > learn how I can get you up and productive in Tapestry fast!
> >> > > > > >
> >> > > > > > (971) 678-5210
> >> > > > > > http://howardlewisship.com
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > --
> >> > > > Howard M. Lewis Ship
> >> > > >
> >> > > > Creator of Apache Tapestry
> >> > > >
> >> > > > The source for Tapestry training, mentoring and support. Contact
> me
> >> to
> >> > > > learn how I can get you up and productive in Tapestry fast!
> >> > > >
> >> > > > (971) 678-5210
> >> > > > http://howardlewisship.com
> >> > > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Howard M. Lewis Ship
> >>
> >> Creator of Apache Tapestry
> >>
> >> The source for Tapestry training, mentoring and support. Contact me to
> >> learn how I can get you up and productive in Tapestry fast!
> >>
> >> (971) 678-5210
> >> http://howardlewisship.com
> >>
> >
> >
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: Tapestry 5.4-alpha-3
Posted by Charlouze <me...@charlouze.com>.
I explore the code of the ExtensibleJavaScriptStack class and it calculates
the asset link on first use. Maybe I can disable the checksum in URL ?
2013/4/17 Charlouze <me...@charlouze.com>
> I build my app with eclipse 3.7.2. I use the m2e plugin (1.1.0) and the
> m2e-wtp (0.15.3) to configure my eclipse project. I'm running the app using
> the run jetty run plugin (1.3.3). The selected jetty version is 8.1.2.
>
> I just made a small test project (only an index page with nothing but a
> title and the styles.css file). I figured out where the problem is: if I
> load my styles.css through an ExtensibleJavaScriptStack it does'nt work,
> the address is not changing when I add some css rules to the file. If I use
> @Import(stylesheet = { "context:/css/styles.css" }) on my index page, it
> works well.
>
> Should I file a bug on jira ?
>
>
> 2013/4/17 Howard Lewis Ship <hl...@gmail.com>
>
>> When you refresh your page, it *should* be building a new URL to the
>> updated asset. The particulars matter here ... how exactly are you
>> building & running the app?
>>
>>
>> On Wed, Apr 17, 2013 at 9:31 AM, Charlouze <me...@charlouze.com> wrote:
>>
>> > Hey everyone,
>> >
>> > I have some trouble with the 5.4-alpha-3. When I add some stuff to my
>> > styles.css file, it get another address to access it (that is perfectly
>> > normal according to the new asset feature). The problem is that if I
>> don't
>> > restart my application my pages tries to load my styles.css file from
>> the
>> > old address. I probably miss somthing.
>> >
>> > For your information, I'm am in development mode. I use eclipse and the
>> run
>> > jetty run plugin.
>> >
>> > Charles.
>> >
>> >
>> > 2013/4/12 François Facon <fr...@atos.net>
>> >
>> > > By the way, tapestry5-portlet is also ready to be used with 5.4. But
>> I am
>> > > still looking for a way to run integration tests inside Pluto with
>> > Gradle.
>> > > Perhaps the use of Arquillian with Pluto under gradle is the solution.
>> > >
>> > >
>> > >
>> > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
>> > >
>> > > > That's great news!
>> > > >
>> > > >
>> > > > On Fri, Apr 12, 2013 at 12:35 PM, François Facon <
>> > > francois.facon@atos.net
>> > > > >wrote:
>> > > >
>> > > > > Thanks to Emmanuel, tapestry-jquery is already working fine with
>> 5.4.
>> > > > >
>> > > > >
>> > > > >
>> > > > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
>> > > > >
>> > > > > > We don't control the tapestry-jquery library; I actually haven't
>> > > looked
>> > > > > at
>> > > > > > it. I suspect it will need to be reworked significantly for 5.4.
>> > > > > >
>> > > > > >
>> > > > > > On Fri, Apr 12, 2013 at 9:40 AM, George Christman
>> > > > > > <gc...@cardaddy.com>wrote:
>> > > > > >
>> > > > > > > I'm just curious if Tapestry5.4 will just be integrating the
>> > > > > > > Tapestry-Jquery library?
>> > > > > > >
>> > > > > > > On Sun, Apr 7, 2013 at 10:29 AM, hantsy <ha...@yahoo.com.cn>
>> > > wrote:
>> > > > > > > >
>> > > > > > > > Created a new thread for it. Thanks
>> > > > > > > >
>> > > > > > > > On 4/7/2013 22:16, Bob Harner wrote:
>> > > > > > > >> Hantsy, you might want to start a separate thread. Your
>> > question
>> > > > > isn't
>> > > > > > > >> about 5.4-alpha-3 at all.
>> > > > > > > >>
>> > > > > > > >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <
>> hantsy@yahoo.com.cn>
>> > > > wrote:
>> > > > > > > >>
>> > > > > > > >>> I want to know if Tapestry has plan to integrate with Java
>> > EE,
>> > > > such
>> > > > > > as
>> > > > > > > >>> how to use CDI with Tapestry, I know Tapestry has its DI
>> > > > container,
>> > > > > > it
>> > > > > > > >>> can be replaced with CDI?
>> > > > > > > >>>
>> > > > > > > >>> I have used Tapestry4 before, and know little about the
>> > newest
>> > > > > > > Tapestry 5.
>> > > > > > > >>>
>> > > > > > > >>>
>> > > > > > > >>> Hantsy
>> > > > > > > >>> On 4/7/2013 09:11, Saeed wrote:
>> > > > > > > >>>> Great news! jQuery finally. Well done sire!
>> > > > > > > >>>>
>> > > > > > > >>>>
>> > > > > > > >>>>
>> > > > > > > >>>>
>> > > > > > > >>>>
>> > > > > > > >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <
>> > > > > > hlship@gmail.com>
>> > > > > > > >>> wrote:
>> > > > > > > >>>>> Hot off the presses! The latest preview release of
>> > Tapestry,
>> > > > > > > >>> 5.4-alpha-3,
>> > > > > > > >>>>> is now available.
>> > > > > > > >>>>>
>> > > > > > > >>>>> Point your build tool of choice at the Maven repository:
>> > > > > > > >>>>>
>> > > > > > > >>>>>
>> > > > > > > >>>
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://repository.apache.org/content/repositories/orgapachetapestry-072/
>> > > > > > > >>>>> Binary and source archives:
>> > > > > > > >>>>>
>> > > > > > > >>>>> http://people.apache.org/~hlship/tapestry-releases/
>> > > > > > > >>>>>
>> > > > > > > >>>>> What's new?
>> > > > > > > >>>>>
>> > > > > > > >>>>> So much, I've kind of lost track; the main changes are:
>> > > > > > > >>>>>
>> > > > > > > >>>>> Most assets are now accessed using a URL that
>> incorporates
>> > a
>> > > > > > Adler32
>> > > > > > > >>>>> checksum of the asset content. Prior versions of
>> Tapestry
>> > > > > > > incorporated
>> > > > > > > >>> the
>> > > > > > > >>>>> application version number into the URL.
>> > > > > > > >>>>>
>> > > > > > > >>>>> What does this mean? When you redeploy your web
>> > application,
>> > > > > most
>> > > > > > > >>> assets
>> > > > > > > >>>>> will have not changed: same content, same path, same
>> > > checksum,
>> > > > > > > >>> therefore,
>> > > > > > > >>>>> same URL. This means that client browsers will not have
>> to
>> > > > > > > re-download
>> > > > > > > >>> all
>> > > > > > > >>>>> those assets again just because the application version
>> > > number
>> > > > > has
>> > > > > > > >>> changed.
>> > > > > > > >>>>> Assets that have changed will have a different content
>> > hash,
>> > > > and
>> > > > > > > >>> therefore,
>> > > > > > > >>>>> a different asset URL. Browsers will be sure to pull
>> down
>> > > those
>> > > > > new
>> > > > > > > >>>>> versions.
>> > > > > > > >>>>>
>> > > > > > > >>>>> Modules are slightly different; because all JavaScript
>> > > modules
>> > > > > are
>> > > > > > > >>> expected
>> > > > > > > >>>>> to start in a common root URL, there is no reasonable
>> way
>> > to
>> > > > > > > generate a
>> > > > > > > >>>>> unique content hash for each; module URLs still use the
>> > > > > application
>> > > > > > > >>> version
>> > > > > > > >>>>> number. However, modules and all assets now also send an
>> > ETag
>> > > > > > header;
>> > > > > > > >>> this
>> > > > > > > >>>>> means that module requests will still be sent, but will
>> > often
>> > > > > get a
>> > > > > > > 304
>> > > > > > > >>>>> (resource not modified) response.
>> > > > > > > >>>>>
>> > > > > > > >>>>> Obviously, this is a big change, and we're welcoming
>> > > feedback.
>> > > > > > > >>>>>
>> > > > > > > >>>>> Next up; we have first class support for jQuery.A little
>> > bit
>> > > of
>> > > > > > > symbol
>> > > > > > > >>>>> tweaking, and Prototype and Scriptaculous are simply
>> gone
>> > for
>> > > > > good.
>> > > > > > > >>>>>
>> > > > > > > >>>>> There's also been improvements to operation tracking,
>> with
>> > > more
>> > > > > > > >>> operations
>> > > > > > > >>>>> performed during a request being tracked. This is useful
>> > for
>> > > > the
>> > > > > > > part of
>> > > > > > > >>>>> the exception report page that discusses what Tapestry
>> did
>> > > > > during a
>> > > > > > > >>>>> request, leading up to the actual exception.
>> > > > > > > >>>>>
>> > > > > > > >>>>> There's been big improvements, c/o Kalle, in terms of
>> how
>> > > > > > exceptions
>> > > > > > > are
>> > > > > > > >>>>> reported, with finer control over what gets the full
>> > > exception
>> > > > > > page,
>> > > > > > > and
>> > > > > > > >>>>> what doesn't.
>> > > > > > > >>>>>
>> > > > > > > >>>>> For the rare places where public interfaces changed in
>> > > > > incompatible
>> > > > > > > >>> ways,
>> > > > > > > >>>>> there's now an @IncompatibleChange annotation for
>> methods
>> > > that
>> > > > > have
>> > > > > > > >>>>> changed.
>> > > > > > > >>>>>
>> > > > > > > >>>>>
>> > > > > > > >>>>> A few informational pages such as PageCatalog,
>> > ServiceStatus,
>> > > > and
>> > > > > > > >>> Hibernate
>> > > > > > > >>>>> Statistics have been merged into a new single
>> (extensible)
>> > > > page,
>> > > > > > > >>>>> T5Dashboard.
>> > > > > > > >>>>>
>> > > > > > > >>>>> ... and lots more little changes, fixes, and
>> improvements.
>> > > > > > > >>>>>
>> > > > > > > >>>>> There's still a lot more to come, however. Two
>> principle
>> > > > > > > improvements
>> > > > > > > >>> I'm
>> > > > > > > >>>>> targeting for 5.4:
>> > > > > > > >>>>>
>> > > > > > > >>>>> Proper server-side push/websocket support.
>> > > > > > > >>>>>
>> > > > > > > >>>>> Built-in performance monitoring and reporting.
>> > > > > > > >>>>>
>> > > > > > > >>>>> --
>> > > > > > > >>>>> Howard M. Lewis Ship
>> > > > > > > >>>>>
>> > > > > > > >>>>> Creator of Apache Tapestry
>> > > > > > > >>>>>
>> > > > > > > >>>>> The source for Tapestry training, mentoring and support.
>> > > > Contact
>> > > > > me
>> > > > > > > to
>> > > > > > > >>>>> learn how I can get you up and productive in Tapestry
>> fast!
>> > > > > > > >>>>>
>> > > > > > > >>>>> (971) 678-5210
>> > > > > > > >>>>> http://howardlewisship.com
>> > > > > > > >>>>>
>> > > > > > > >>>
>> > > > > > > >>>
>> > > > >
>> ---------------------------------------------------------------------
>> > > > > > > >>> To unsubscribe, e-mail:
>> > users-unsubscribe@tapestry.apache.org
>> > > > > > > >>> For additional commands, e-mail:
>> > > users-help@tapestry.apache.org
>> > > > > > > >>>
>> > > > > > > >>>
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > >
>> ---------------------------------------------------------------------
>> > > > > > > > To unsubscribe, e-mail:
>> users-unsubscribe@tapestry.apache.org
>> > > > > > > > For additional commands, e-mail:
>> > users-help@tapestry.apache.org
>> > > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > --
>> > > > > > > George Christman
>> > > > > > > www.CarDaddy.com
>> > > > > > > P.O. Box 735
>> > > > > > > Johnstown, New York
>> > > > > > >
>> > > > > > >
>> > > ---------------------------------------------------------------------
>> > > > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> > > > > > > For additional commands, e-mail:
>> users-help@tapestry.apache.org
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > > Howard M. Lewis Ship
>> > > > > >
>> > > > > > Creator of Apache Tapestry
>> > > > > >
>> > > > > > The source for Tapestry training, mentoring and support.
>> Contact me
>> > > to
>> > > > > > learn how I can get you up and productive in Tapestry fast!
>> > > > > >
>> > > > > > (971) 678-5210
>> > > > > > http://howardlewisship.com
>> > > > > >
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Howard M. Lewis Ship
>> > > >
>> > > > Creator of Apache Tapestry
>> > > >
>> > > > The source for Tapestry training, mentoring and support. Contact me
>> to
>> > > > learn how I can get you up and productive in Tapestry fast!
>> > > >
>> > > > (971) 678-5210
>> > > > http://howardlewisship.com
>> > > >
>> > >
>> >
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator of Apache Tapestry
>>
>> The source for Tapestry training, mentoring and support. Contact me to
>> learn how I can get you up and productive in Tapestry fast!
>>
>> (971) 678-5210
>> http://howardlewisship.com
>>
>
>
Re: Tapestry 5.4-alpha-3
Posted by Charlouze <me...@charlouze.com>.
I build my app with eclipse 3.7.2. I use the m2e plugin (1.1.0) and the
m2e-wtp (0.15.3) to configure my eclipse project. I'm running the app using
the run jetty run plugin (1.3.3). The selected jetty version is 8.1.2.
I just made a small test project (only an index page with nothing but a
title and the styles.css file). I figured out where the problem is: if I
load my styles.css through an ExtensibleJavaScriptStack it does'nt work,
the address is not changing when I add some css rules to the file. If I use
@Import(stylesheet = { "context:/css/styles.css" }) on my index page, it
works well.
Should I file a bug on jira ?
2013/4/17 Howard Lewis Ship <hl...@gmail.com>
> When you refresh your page, it *should* be building a new URL to the
> updated asset. The particulars matter here ... how exactly are you
> building & running the app?
>
>
> On Wed, Apr 17, 2013 at 9:31 AM, Charlouze <me...@charlouze.com> wrote:
>
> > Hey everyone,
> >
> > I have some trouble with the 5.4-alpha-3. When I add some stuff to my
> > styles.css file, it get another address to access it (that is perfectly
> > normal according to the new asset feature). The problem is that if I
> don't
> > restart my application my pages tries to load my styles.css file from the
> > old address. I probably miss somthing.
> >
> > For your information, I'm am in development mode. I use eclipse and the
> run
> > jetty run plugin.
> >
> > Charles.
> >
> >
> > 2013/4/12 François Facon <fr...@atos.net>
> >
> > > By the way, tapestry5-portlet is also ready to be used with 5.4. But I
> am
> > > still looking for a way to run integration tests inside Pluto with
> > Gradle.
> > > Perhaps the use of Arquillian with Pluto under gradle is the solution.
> > >
> > >
> > >
> > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> > >
> > > > That's great news!
> > > >
> > > >
> > > > On Fri, Apr 12, 2013 at 12:35 PM, François Facon <
> > > francois.facon@atos.net
> > > > >wrote:
> > > >
> > > > > Thanks to Emmanuel, tapestry-jquery is already working fine with
> 5.4.
> > > > >
> > > > >
> > > > >
> > > > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> > > > >
> > > > > > We don't control the tapestry-jquery library; I actually haven't
> > > looked
> > > > > at
> > > > > > it. I suspect it will need to be reworked significantly for 5.4.
> > > > > >
> > > > > >
> > > > > > On Fri, Apr 12, 2013 at 9:40 AM, George Christman
> > > > > > <gc...@cardaddy.com>wrote:
> > > > > >
> > > > > > > I'm just curious if Tapestry5.4 will just be integrating the
> > > > > > > Tapestry-Jquery library?
> > > > > > >
> > > > > > > On Sun, Apr 7, 2013 at 10:29 AM, hantsy <ha...@yahoo.com.cn>
> > > wrote:
> > > > > > > >
> > > > > > > > Created a new thread for it. Thanks
> > > > > > > >
> > > > > > > > On 4/7/2013 22:16, Bob Harner wrote:
> > > > > > > >> Hantsy, you might want to start a separate thread. Your
> > question
> > > > > isn't
> > > > > > > >> about 5.4-alpha-3 at all.
> > > > > > > >>
> > > > > > > >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <hantsy@yahoo.com.cn
> >
> > > > wrote:
> > > > > > > >>
> > > > > > > >>> I want to know if Tapestry has plan to integrate with Java
> > EE,
> > > > such
> > > > > > as
> > > > > > > >>> how to use CDI with Tapestry, I know Tapestry has its DI
> > > > container,
> > > > > > it
> > > > > > > >>> can be replaced with CDI?
> > > > > > > >>>
> > > > > > > >>> I have used Tapestry4 before, and know little about the
> > newest
> > > > > > > Tapestry 5.
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>> Hantsy
> > > > > > > >>> On 4/7/2013 09:11, Saeed wrote:
> > > > > > > >>>> Great news! jQuery finally. Well done sire!
> > > > > > > >>>>
> > > > > > > >>>>
> > > > > > > >>>>
> > > > > > > >>>>
> > > > > > > >>>>
> > > > > > > >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <
> > > > > > hlship@gmail.com>
> > > > > > > >>> wrote:
> > > > > > > >>>>> Hot off the presses! The latest preview release of
> > Tapestry,
> > > > > > > >>> 5.4-alpha-3,
> > > > > > > >>>>> is now available.
> > > > > > > >>>>>
> > > > > > > >>>>> Point your build tool of choice at the Maven repository:
> > > > > > > >>>>>
> > > > > > > >>>>>
> > > > > > > >>>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
> > > > > > > >>>>> Binary and source archives:
> > > > > > > >>>>>
> > > > > > > >>>>> http://people.apache.org/~hlship/tapestry-releases/
> > > > > > > >>>>>
> > > > > > > >>>>> What's new?
> > > > > > > >>>>>
> > > > > > > >>>>> So much, I've kind of lost track; the main changes are:
> > > > > > > >>>>>
> > > > > > > >>>>> Most assets are now accessed using a URL that
> incorporates
> > a
> > > > > > Adler32
> > > > > > > >>>>> checksum of the asset content. Prior versions of
> Tapestry
> > > > > > > incorporated
> > > > > > > >>> the
> > > > > > > >>>>> application version number into the URL.
> > > > > > > >>>>>
> > > > > > > >>>>> What does this mean? When you redeploy your web
> > application,
> > > > > most
> > > > > > > >>> assets
> > > > > > > >>>>> will have not changed: same content, same path, same
> > > checksum,
> > > > > > > >>> therefore,
> > > > > > > >>>>> same URL. This means that client browsers will not have
> to
> > > > > > > re-download
> > > > > > > >>> all
> > > > > > > >>>>> those assets again just because the application version
> > > number
> > > > > has
> > > > > > > >>> changed.
> > > > > > > >>>>> Assets that have changed will have a different content
> > hash,
> > > > and
> > > > > > > >>> therefore,
> > > > > > > >>>>> a different asset URL. Browsers will be sure to pull down
> > > those
> > > > > new
> > > > > > > >>>>> versions.
> > > > > > > >>>>>
> > > > > > > >>>>> Modules are slightly different; because all JavaScript
> > > modules
> > > > > are
> > > > > > > >>> expected
> > > > > > > >>>>> to start in a common root URL, there is no reasonable way
> > to
> > > > > > > generate a
> > > > > > > >>>>> unique content hash for each; module URLs still use the
> > > > > application
> > > > > > > >>> version
> > > > > > > >>>>> number. However, modules and all assets now also send an
> > ETag
> > > > > > header;
> > > > > > > >>> this
> > > > > > > >>>>> means that module requests will still be sent, but will
> > often
> > > > > get a
> > > > > > > 304
> > > > > > > >>>>> (resource not modified) response.
> > > > > > > >>>>>
> > > > > > > >>>>> Obviously, this is a big change, and we're welcoming
> > > feedback.
> > > > > > > >>>>>
> > > > > > > >>>>> Next up; we have first class support for jQuery.A little
> > bit
> > > of
> > > > > > > symbol
> > > > > > > >>>>> tweaking, and Prototype and Scriptaculous are simply gone
> > for
> > > > > good.
> > > > > > > >>>>>
> > > > > > > >>>>> There's also been improvements to operation tracking,
> with
> > > more
> > > > > > > >>> operations
> > > > > > > >>>>> performed during a request being tracked. This is useful
> > for
> > > > the
> > > > > > > part of
> > > > > > > >>>>> the exception report page that discusses what Tapestry
> did
> > > > > during a
> > > > > > > >>>>> request, leading up to the actual exception.
> > > > > > > >>>>>
> > > > > > > >>>>> There's been big improvements, c/o Kalle, in terms of how
> > > > > > exceptions
> > > > > > > are
> > > > > > > >>>>> reported, with finer control over what gets the full
> > > exception
> > > > > > page,
> > > > > > > and
> > > > > > > >>>>> what doesn't.
> > > > > > > >>>>>
> > > > > > > >>>>> For the rare places where public interfaces changed in
> > > > > incompatible
> > > > > > > >>> ways,
> > > > > > > >>>>> there's now an @IncompatibleChange annotation for methods
> > > that
> > > > > have
> > > > > > > >>>>> changed.
> > > > > > > >>>>>
> > > > > > > >>>>>
> > > > > > > >>>>> A few informational pages such as PageCatalog,
> > ServiceStatus,
> > > > and
> > > > > > > >>> Hibernate
> > > > > > > >>>>> Statistics have been merged into a new single
> (extensible)
> > > > page,
> > > > > > > >>>>> T5Dashboard.
> > > > > > > >>>>>
> > > > > > > >>>>> ... and lots more little changes, fixes, and
> improvements.
> > > > > > > >>>>>
> > > > > > > >>>>> There's still a lot more to come, however. Two principle
> > > > > > > improvements
> > > > > > > >>> I'm
> > > > > > > >>>>> targeting for 5.4:
> > > > > > > >>>>>
> > > > > > > >>>>> Proper server-side push/websocket support.
> > > > > > > >>>>>
> > > > > > > >>>>> Built-in performance monitoring and reporting.
> > > > > > > >>>>>
> > > > > > > >>>>> --
> > > > > > > >>>>> Howard M. Lewis Ship
> > > > > > > >>>>>
> > > > > > > >>>>> Creator of Apache Tapestry
> > > > > > > >>>>>
> > > > > > > >>>>> The source for Tapestry training, mentoring and support.
> > > > Contact
> > > > > me
> > > > > > > to
> > > > > > > >>>>> learn how I can get you up and productive in Tapestry
> fast!
> > > > > > > >>>>>
> > > > > > > >>>>> (971) 678-5210
> > > > > > > >>>>> http://howardlewisship.com
> > > > > > > >>>>>
> > > > > > > >>>
> > > > > > > >>>
> > > > >
> ---------------------------------------------------------------------
> > > > > > > >>> To unsubscribe, e-mail:
> > users-unsubscribe@tapestry.apache.org
> > > > > > > >>> For additional commands, e-mail:
> > > users-help@tapestry.apache.org
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail:
> users-unsubscribe@tapestry.apache.org
> > > > > > > > For additional commands, e-mail:
> > users-help@tapestry.apache.org
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > George Christman
> > > > > > > www.CarDaddy.com
> > > > > > > P.O. Box 735
> > > > > > > Johnstown, New York
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > > > For additional commands, e-mail:
> users-help@tapestry.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Howard M. Lewis Ship
> > > > > >
> > > > > > Creator of Apache Tapestry
> > > > > >
> > > > > > The source for Tapestry training, mentoring and support. Contact
> me
> > > to
> > > > > > learn how I can get you up and productive in Tapestry fast!
> > > > > >
> > > > > > (971) 678-5210
> > > > > > http://howardlewisship.com
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Howard M. Lewis Ship
> > > >
> > > > Creator of Apache Tapestry
> > > >
> > > > The source for Tapestry training, mentoring and support. Contact me
> to
> > > > learn how I can get you up and productive in Tapestry fast!
> > > >
> > > > (971) 678-5210
> > > > http://howardlewisship.com
> > > >
> > >
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
Re: Tapestry 5.4-alpha-3
Posted by Howard Lewis Ship <hl...@gmail.com>.
When you refresh your page, it *should* be building a new URL to the
updated asset. The particulars matter here ... how exactly are you
building & running the app?
On Wed, Apr 17, 2013 at 9:31 AM, Charlouze <me...@charlouze.com> wrote:
> Hey everyone,
>
> I have some trouble with the 5.4-alpha-3. When I add some stuff to my
> styles.css file, it get another address to access it (that is perfectly
> normal according to the new asset feature). The problem is that if I don't
> restart my application my pages tries to load my styles.css file from the
> old address. I probably miss somthing.
>
> For your information, I'm am in development mode. I use eclipse and the run
> jetty run plugin.
>
> Charles.
>
>
> 2013/4/12 François Facon <fr...@atos.net>
>
> > By the way, tapestry5-portlet is also ready to be used with 5.4. But I am
> > still looking for a way to run integration tests inside Pluto with
> Gradle.
> > Perhaps the use of Arquillian with Pluto under gradle is the solution.
> >
> >
> >
> > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> >
> > > That's great news!
> > >
> > >
> > > On Fri, Apr 12, 2013 at 12:35 PM, François Facon <
> > francois.facon@atos.net
> > > >wrote:
> > >
> > > > Thanks to Emmanuel, tapestry-jquery is already working fine with 5.4.
> > > >
> > > >
> > > >
> > > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> > > >
> > > > > We don't control the tapestry-jquery library; I actually haven't
> > looked
> > > > at
> > > > > it. I suspect it will need to be reworked significantly for 5.4.
> > > > >
> > > > >
> > > > > On Fri, Apr 12, 2013 at 9:40 AM, George Christman
> > > > > <gc...@cardaddy.com>wrote:
> > > > >
> > > > > > I'm just curious if Tapestry5.4 will just be integrating the
> > > > > > Tapestry-Jquery library?
> > > > > >
> > > > > > On Sun, Apr 7, 2013 at 10:29 AM, hantsy <ha...@yahoo.com.cn>
> > wrote:
> > > > > > >
> > > > > > > Created a new thread for it. Thanks
> > > > > > >
> > > > > > > On 4/7/2013 22:16, Bob Harner wrote:
> > > > > > >> Hantsy, you might want to start a separate thread. Your
> question
> > > > isn't
> > > > > > >> about 5.4-alpha-3 at all.
> > > > > > >>
> > > > > > >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <ha...@yahoo.com.cn>
> > > wrote:
> > > > > > >>
> > > > > > >>> I want to know if Tapestry has plan to integrate with Java
> EE,
> > > such
> > > > > as
> > > > > > >>> how to use CDI with Tapestry, I know Tapestry has its DI
> > > container,
> > > > > it
> > > > > > >>> can be replaced with CDI?
> > > > > > >>>
> > > > > > >>> I have used Tapestry4 before, and know little about the
> newest
> > > > > > Tapestry 5.
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> Hantsy
> > > > > > >>> On 4/7/2013 09:11, Saeed wrote:
> > > > > > >>>> Great news! jQuery finally. Well done sire!
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <
> > > > > hlship@gmail.com>
> > > > > > >>> wrote:
> > > > > > >>>>> Hot off the presses! The latest preview release of
> Tapestry,
> > > > > > >>> 5.4-alpha-3,
> > > > > > >>>>> is now available.
> > > > > > >>>>>
> > > > > > >>>>> Point your build tool of choice at the Maven repository:
> > > > > > >>>>>
> > > > > > >>>>>
> > > > > > >>>
> > > > > >
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
> > > > > > >>>>> Binary and source archives:
> > > > > > >>>>>
> > > > > > >>>>> http://people.apache.org/~hlship/tapestry-releases/
> > > > > > >>>>>
> > > > > > >>>>> What's new?
> > > > > > >>>>>
> > > > > > >>>>> So much, I've kind of lost track; the main changes are:
> > > > > > >>>>>
> > > > > > >>>>> Most assets are now accessed using a URL that incorporates
> a
> > > > > Adler32
> > > > > > >>>>> checksum of the asset content. Prior versions of Tapestry
> > > > > > incorporated
> > > > > > >>> the
> > > > > > >>>>> application version number into the URL.
> > > > > > >>>>>
> > > > > > >>>>> What does this mean? When you redeploy your web
> application,
> > > > most
> > > > > > >>> assets
> > > > > > >>>>> will have not changed: same content, same path, same
> > checksum,
> > > > > > >>> therefore,
> > > > > > >>>>> same URL. This means that client browsers will not have to
> > > > > > re-download
> > > > > > >>> all
> > > > > > >>>>> those assets again just because the application version
> > number
> > > > has
> > > > > > >>> changed.
> > > > > > >>>>> Assets that have changed will have a different content
> hash,
> > > and
> > > > > > >>> therefore,
> > > > > > >>>>> a different asset URL. Browsers will be sure to pull down
> > those
> > > > new
> > > > > > >>>>> versions.
> > > > > > >>>>>
> > > > > > >>>>> Modules are slightly different; because all JavaScript
> > modules
> > > > are
> > > > > > >>> expected
> > > > > > >>>>> to start in a common root URL, there is no reasonable way
> to
> > > > > > generate a
> > > > > > >>>>> unique content hash for each; module URLs still use the
> > > > application
> > > > > > >>> version
> > > > > > >>>>> number. However, modules and all assets now also send an
> ETag
> > > > > header;
> > > > > > >>> this
> > > > > > >>>>> means that module requests will still be sent, but will
> often
> > > > get a
> > > > > > 304
> > > > > > >>>>> (resource not modified) response.
> > > > > > >>>>>
> > > > > > >>>>> Obviously, this is a big change, and we're welcoming
> > feedback.
> > > > > > >>>>>
> > > > > > >>>>> Next up; we have first class support for jQuery.A little
> bit
> > of
> > > > > > symbol
> > > > > > >>>>> tweaking, and Prototype and Scriptaculous are simply gone
> for
> > > > good.
> > > > > > >>>>>
> > > > > > >>>>> There's also been improvements to operation tracking, with
> > more
> > > > > > >>> operations
> > > > > > >>>>> performed during a request being tracked. This is useful
> for
> > > the
> > > > > > part of
> > > > > > >>>>> the exception report page that discusses what Tapestry did
> > > > during a
> > > > > > >>>>> request, leading up to the actual exception.
> > > > > > >>>>>
> > > > > > >>>>> There's been big improvements, c/o Kalle, in terms of how
> > > > > exceptions
> > > > > > are
> > > > > > >>>>> reported, with finer control over what gets the full
> > exception
> > > > > page,
> > > > > > and
> > > > > > >>>>> what doesn't.
> > > > > > >>>>>
> > > > > > >>>>> For the rare places where public interfaces changed in
> > > > incompatible
> > > > > > >>> ways,
> > > > > > >>>>> there's now an @IncompatibleChange annotation for methods
> > that
> > > > have
> > > > > > >>>>> changed.
> > > > > > >>>>>
> > > > > > >>>>>
> > > > > > >>>>> A few informational pages such as PageCatalog,
> ServiceStatus,
> > > and
> > > > > > >>> Hibernate
> > > > > > >>>>> Statistics have been merged into a new single (extensible)
> > > page,
> > > > > > >>>>> T5Dashboard.
> > > > > > >>>>>
> > > > > > >>>>> ... and lots more little changes, fixes, and improvements.
> > > > > > >>>>>
> > > > > > >>>>> There's still a lot more to come, however. Two principle
> > > > > > improvements
> > > > > > >>> I'm
> > > > > > >>>>> targeting for 5.4:
> > > > > > >>>>>
> > > > > > >>>>> Proper server-side push/websocket support.
> > > > > > >>>>>
> > > > > > >>>>> Built-in performance monitoring and reporting.
> > > > > > >>>>>
> > > > > > >>>>> --
> > > > > > >>>>> Howard M. Lewis Ship
> > > > > > >>>>>
> > > > > > >>>>> Creator of Apache Tapestry
> > > > > > >>>>>
> > > > > > >>>>> The source for Tapestry training, mentoring and support.
> > > Contact
> > > > me
> > > > > > to
> > > > > > >>>>> learn how I can get you up and productive in Tapestry fast!
> > > > > > >>>>>
> > > > > > >>>>> (971) 678-5210
> > > > > > >>>>> http://howardlewisship.com
> > > > > > >>>>>
> > > > > > >>>
> > > > > > >>>
> > > > ---------------------------------------------------------------------
> > > > > > >>> To unsubscribe, e-mail:
> users-unsubscribe@tapestry.apache.org
> > > > > > >>> For additional commands, e-mail:
> > users-help@tapestry.apache.org
> > > > > > >>>
> > > > > > >>>
> > > > > > >
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > > > For additional commands, e-mail:
> users-help@tapestry.apache.org
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > George Christman
> > > > > > www.CarDaddy.com
> > > > > > P.O. Box 735
> > > > > > Johnstown, New York
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Howard M. Lewis Ship
> > > > >
> > > > > Creator of Apache Tapestry
> > > > >
> > > > > The source for Tapestry training, mentoring and support. Contact me
> > to
> > > > > learn how I can get you up and productive in Tapestry fast!
> > > > >
> > > > > (971) 678-5210
> > > > > http://howardlewisship.com
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Howard M. Lewis Ship
> > >
> > > Creator of Apache Tapestry
> > >
> > > The source for Tapestry training, mentoring and support. Contact me to
> > > learn how I can get you up and productive in Tapestry fast!
> > >
> > > (971) 678-5210
> > > http://howardlewisship.com
> > >
> >
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: Tapestry 5.4-alpha-3
Posted by Charlouze <me...@charlouze.com>.
Hey everyone,
I have some trouble with the 5.4-alpha-3. When I add some stuff to my
styles.css file, it get another address to access it (that is perfectly
normal according to the new asset feature). The problem is that if I don't
restart my application my pages tries to load my styles.css file from the
old address. I probably miss somthing.
For your information, I'm am in development mode. I use eclipse and the run
jetty run plugin.
Charles.
2013/4/12 François Facon <fr...@atos.net>
> By the way, tapestry5-portlet is also ready to be used with 5.4. But I am
> still looking for a way to run integration tests inside Pluto with Gradle.
> Perhaps the use of Arquillian with Pluto under gradle is the solution.
>
>
>
> 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
>
> > That's great news!
> >
> >
> > On Fri, Apr 12, 2013 at 12:35 PM, François Facon <
> francois.facon@atos.net
> > >wrote:
> >
> > > Thanks to Emmanuel, tapestry-jquery is already working fine with 5.4.
> > >
> > >
> > >
> > > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> > >
> > > > We don't control the tapestry-jquery library; I actually haven't
> looked
> > > at
> > > > it. I suspect it will need to be reworked significantly for 5.4.
> > > >
> > > >
> > > > On Fri, Apr 12, 2013 at 9:40 AM, George Christman
> > > > <gc...@cardaddy.com>wrote:
> > > >
> > > > > I'm just curious if Tapestry5.4 will just be integrating the
> > > > > Tapestry-Jquery library?
> > > > >
> > > > > On Sun, Apr 7, 2013 at 10:29 AM, hantsy <ha...@yahoo.com.cn>
> wrote:
> > > > > >
> > > > > > Created a new thread for it. Thanks
> > > > > >
> > > > > > On 4/7/2013 22:16, Bob Harner wrote:
> > > > > >> Hantsy, you might want to start a separate thread. Your question
> > > isn't
> > > > > >> about 5.4-alpha-3 at all.
> > > > > >>
> > > > > >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <ha...@yahoo.com.cn>
> > wrote:
> > > > > >>
> > > > > >>> I want to know if Tapestry has plan to integrate with Java EE,
> > such
> > > > as
> > > > > >>> how to use CDI with Tapestry, I know Tapestry has its DI
> > container,
> > > > it
> > > > > >>> can be replaced with CDI?
> > > > > >>>
> > > > > >>> I have used Tapestry4 before, and know little about the newest
> > > > > Tapestry 5.
> > > > > >>>
> > > > > >>>
> > > > > >>> Hantsy
> > > > > >>> On 4/7/2013 09:11, Saeed wrote:
> > > > > >>>> Great news! jQuery finally. Well done sire!
> > > > > >>>>
> > > > > >>>>
> > > > > >>>>
> > > > > >>>>
> > > > > >>>>
> > > > > >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <
> > > > hlship@gmail.com>
> > > > > >>> wrote:
> > > > > >>>>> Hot off the presses! The latest preview release of Tapestry,
> > > > > >>> 5.4-alpha-3,
> > > > > >>>>> is now available.
> > > > > >>>>>
> > > > > >>>>> Point your build tool of choice at the Maven repository:
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
> > > > > >>>>> Binary and source archives:
> > > > > >>>>>
> > > > > >>>>> http://people.apache.org/~hlship/tapestry-releases/
> > > > > >>>>>
> > > > > >>>>> What's new?
> > > > > >>>>>
> > > > > >>>>> So much, I've kind of lost track; the main changes are:
> > > > > >>>>>
> > > > > >>>>> Most assets are now accessed using a URL that incorporates a
> > > > Adler32
> > > > > >>>>> checksum of the asset content. Prior versions of Tapestry
> > > > > incorporated
> > > > > >>> the
> > > > > >>>>> application version number into the URL.
> > > > > >>>>>
> > > > > >>>>> What does this mean? When you redeploy your web application,
> > > most
> > > > > >>> assets
> > > > > >>>>> will have not changed: same content, same path, same
> checksum,
> > > > > >>> therefore,
> > > > > >>>>> same URL. This means that client browsers will not have to
> > > > > re-download
> > > > > >>> all
> > > > > >>>>> those assets again just because the application version
> number
> > > has
> > > > > >>> changed.
> > > > > >>>>> Assets that have changed will have a different content hash,
> > and
> > > > > >>> therefore,
> > > > > >>>>> a different asset URL. Browsers will be sure to pull down
> those
> > > new
> > > > > >>>>> versions.
> > > > > >>>>>
> > > > > >>>>> Modules are slightly different; because all JavaScript
> modules
> > > are
> > > > > >>> expected
> > > > > >>>>> to start in a common root URL, there is no reasonable way to
> > > > > generate a
> > > > > >>>>> unique content hash for each; module URLs still use the
> > > application
> > > > > >>> version
> > > > > >>>>> number. However, modules and all assets now also send an ETag
> > > > header;
> > > > > >>> this
> > > > > >>>>> means that module requests will still be sent, but will often
> > > get a
> > > > > 304
> > > > > >>>>> (resource not modified) response.
> > > > > >>>>>
> > > > > >>>>> Obviously, this is a big change, and we're welcoming
> feedback.
> > > > > >>>>>
> > > > > >>>>> Next up; we have first class support for jQuery.A little bit
> of
> > > > > symbol
> > > > > >>>>> tweaking, and Prototype and Scriptaculous are simply gone for
> > > good.
> > > > > >>>>>
> > > > > >>>>> There's also been improvements to operation tracking, with
> more
> > > > > >>> operations
> > > > > >>>>> performed during a request being tracked. This is useful for
> > the
> > > > > part of
> > > > > >>>>> the exception report page that discusses what Tapestry did
> > > during a
> > > > > >>>>> request, leading up to the actual exception.
> > > > > >>>>>
> > > > > >>>>> There's been big improvements, c/o Kalle, in terms of how
> > > > exceptions
> > > > > are
> > > > > >>>>> reported, with finer control over what gets the full
> exception
> > > > page,
> > > > > and
> > > > > >>>>> what doesn't.
> > > > > >>>>>
> > > > > >>>>> For the rare places where public interfaces changed in
> > > incompatible
> > > > > >>> ways,
> > > > > >>>>> there's now an @IncompatibleChange annotation for methods
> that
> > > have
> > > > > >>>>> changed.
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>>> A few informational pages such as PageCatalog, ServiceStatus,
> > and
> > > > > >>> Hibernate
> > > > > >>>>> Statistics have been merged into a new single (extensible)
> > page,
> > > > > >>>>> T5Dashboard.
> > > > > >>>>>
> > > > > >>>>> ... and lots more little changes, fixes, and improvements.
> > > > > >>>>>
> > > > > >>>>> There's still a lot more to come, however. Two principle
> > > > > improvements
> > > > > >>> I'm
> > > > > >>>>> targeting for 5.4:
> > > > > >>>>>
> > > > > >>>>> Proper server-side push/websocket support.
> > > > > >>>>>
> > > > > >>>>> Built-in performance monitoring and reporting.
> > > > > >>>>>
> > > > > >>>>> --
> > > > > >>>>> Howard M. Lewis Ship
> > > > > >>>>>
> > > > > >>>>> Creator of Apache Tapestry
> > > > > >>>>>
> > > > > >>>>> The source for Tapestry training, mentoring and support.
> > Contact
> > > me
> > > > > to
> > > > > >>>>> learn how I can get you up and productive in Tapestry fast!
> > > > > >>>>>
> > > > > >>>>> (971) 678-5210
> > > > > >>>>> http://howardlewisship.com
> > > > > >>>>>
> > > > > >>>
> > > > > >>>
> > > ---------------------------------------------------------------------
> > > > > >>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > >>> For additional commands, e-mail:
> users-help@tapestry.apache.org
> > > > > >>>
> > > > > >>>
> > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > George Christman
> > > > > www.CarDaddy.com
> > > > > P.O. Box 735
> > > > > Johnstown, New York
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Howard M. Lewis Ship
> > > >
> > > > Creator of Apache Tapestry
> > > >
> > > > The source for Tapestry training, mentoring and support. Contact me
> to
> > > > learn how I can get you up and productive in Tapestry fast!
> > > >
> > > > (971) 678-5210
> > > > http://howardlewisship.com
> > > >
> > >
> >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator of Apache Tapestry
> >
> > The source for Tapestry training, mentoring and support. Contact me to
> > learn how I can get you up and productive in Tapestry fast!
> >
> > (971) 678-5210
> > http://howardlewisship.com
> >
>
Re: Tapestry 5.4-alpha-3
Posted by François Facon <fr...@atos.net>.
By the way, tapestry5-portlet is also ready to be used with 5.4. But I am
still looking for a way to run integration tests inside Pluto with Gradle.
Perhaps the use of Arquillian with Pluto under gradle is the solution.
2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> That's great news!
>
>
> On Fri, Apr 12, 2013 at 12:35 PM, François Facon <francois.facon@atos.net
> >wrote:
>
> > Thanks to Emmanuel, tapestry-jquery is already working fine with 5.4.
> >
> >
> >
> > 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> >
> > > We don't control the tapestry-jquery library; I actually haven't looked
> > at
> > > it. I suspect it will need to be reworked significantly for 5.4.
> > >
> > >
> > > On Fri, Apr 12, 2013 at 9:40 AM, George Christman
> > > <gc...@cardaddy.com>wrote:
> > >
> > > > I'm just curious if Tapestry5.4 will just be integrating the
> > > > Tapestry-Jquery library?
> > > >
> > > > On Sun, Apr 7, 2013 at 10:29 AM, hantsy <ha...@yahoo.com.cn> wrote:
> > > > >
> > > > > Created a new thread for it. Thanks
> > > > >
> > > > > On 4/7/2013 22:16, Bob Harner wrote:
> > > > >> Hantsy, you might want to start a separate thread. Your question
> > isn't
> > > > >> about 5.4-alpha-3 at all.
> > > > >>
> > > > >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <ha...@yahoo.com.cn>
> wrote:
> > > > >>
> > > > >>> I want to know if Tapestry has plan to integrate with Java EE,
> such
> > > as
> > > > >>> how to use CDI with Tapestry, I know Tapestry has its DI
> container,
> > > it
> > > > >>> can be replaced with CDI?
> > > > >>>
> > > > >>> I have used Tapestry4 before, and know little about the newest
> > > > Tapestry 5.
> > > > >>>
> > > > >>>
> > > > >>> Hantsy
> > > > >>> On 4/7/2013 09:11, Saeed wrote:
> > > > >>>> Great news! jQuery finally. Well done sire!
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <
> > > hlship@gmail.com>
> > > > >>> wrote:
> > > > >>>>> Hot off the presses! The latest preview release of Tapestry,
> > > > >>> 5.4-alpha-3,
> > > > >>>>> is now available.
> > > > >>>>>
> > > > >>>>> Point your build tool of choice at the Maven repository:
> > > > >>>>>
> > > > >>>>>
> > > > >>>
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
> > > > >>>>> Binary and source archives:
> > > > >>>>>
> > > > >>>>> http://people.apache.org/~hlship/tapestry-releases/
> > > > >>>>>
> > > > >>>>> What's new?
> > > > >>>>>
> > > > >>>>> So much, I've kind of lost track; the main changes are:
> > > > >>>>>
> > > > >>>>> Most assets are now accessed using a URL that incorporates a
> > > Adler32
> > > > >>>>> checksum of the asset content. Prior versions of Tapestry
> > > > incorporated
> > > > >>> the
> > > > >>>>> application version number into the URL.
> > > > >>>>>
> > > > >>>>> What does this mean? When you redeploy your web application,
> > most
> > > > >>> assets
> > > > >>>>> will have not changed: same content, same path, same checksum,
> > > > >>> therefore,
> > > > >>>>> same URL. This means that client browsers will not have to
> > > > re-download
> > > > >>> all
> > > > >>>>> those assets again just because the application version number
> > has
> > > > >>> changed.
> > > > >>>>> Assets that have changed will have a different content hash,
> and
> > > > >>> therefore,
> > > > >>>>> a different asset URL. Browsers will be sure to pull down those
> > new
> > > > >>>>> versions.
> > > > >>>>>
> > > > >>>>> Modules are slightly different; because all JavaScript modules
> > are
> > > > >>> expected
> > > > >>>>> to start in a common root URL, there is no reasonable way to
> > > > generate a
> > > > >>>>> unique content hash for each; module URLs still use the
> > application
> > > > >>> version
> > > > >>>>> number. However, modules and all assets now also send an ETag
> > > header;
> > > > >>> this
> > > > >>>>> means that module requests will still be sent, but will often
> > get a
> > > > 304
> > > > >>>>> (resource not modified) response.
> > > > >>>>>
> > > > >>>>> Obviously, this is a big change, and we're welcoming feedback.
> > > > >>>>>
> > > > >>>>> Next up; we have first class support for jQuery.A little bit of
> > > > symbol
> > > > >>>>> tweaking, and Prototype and Scriptaculous are simply gone for
> > good.
> > > > >>>>>
> > > > >>>>> There's also been improvements to operation tracking, with more
> > > > >>> operations
> > > > >>>>> performed during a request being tracked. This is useful for
> the
> > > > part of
> > > > >>>>> the exception report page that discusses what Tapestry did
> > during a
> > > > >>>>> request, leading up to the actual exception.
> > > > >>>>>
> > > > >>>>> There's been big improvements, c/o Kalle, in terms of how
> > > exceptions
> > > > are
> > > > >>>>> reported, with finer control over what gets the full exception
> > > page,
> > > > and
> > > > >>>>> what doesn't.
> > > > >>>>>
> > > > >>>>> For the rare places where public interfaces changed in
> > incompatible
> > > > >>> ways,
> > > > >>>>> there's now an @IncompatibleChange annotation for methods that
> > have
> > > > >>>>> changed.
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> A few informational pages such as PageCatalog, ServiceStatus,
> and
> > > > >>> Hibernate
> > > > >>>>> Statistics have been merged into a new single (extensible)
> page,
> > > > >>>>> T5Dashboard.
> > > > >>>>>
> > > > >>>>> ... and lots more little changes, fixes, and improvements.
> > > > >>>>>
> > > > >>>>> There's still a lot more to come, however. Two principle
> > > > improvements
> > > > >>> I'm
> > > > >>>>> targeting for 5.4:
> > > > >>>>>
> > > > >>>>> Proper server-side push/websocket support.
> > > > >>>>>
> > > > >>>>> Built-in performance monitoring and reporting.
> > > > >>>>>
> > > > >>>>> --
> > > > >>>>> Howard M. Lewis Ship
> > > > >>>>>
> > > > >>>>> Creator of Apache Tapestry
> > > > >>>>>
> > > > >>>>> The source for Tapestry training, mentoring and support.
> Contact
> > me
> > > > to
> > > > >>>>> learn how I can get you up and productive in Tapestry fast!
> > > > >>>>>
> > > > >>>>> (971) 678-5210
> > > > >>>>> http://howardlewisship.com
> > > > >>>>>
> > > > >>>
> > > > >>>
> > ---------------------------------------------------------------------
> > > > >>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > >>> For additional commands, e-mail: users-help@tapestry.apache.org
> > > > >>>
> > > > >>>
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > George Christman
> > > > www.CarDaddy.com
> > > > P.O. Box 735
> > > > Johnstown, New York
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Howard M. Lewis Ship
> > >
> > > Creator of Apache Tapestry
> > >
> > > The source for Tapestry training, mentoring and support. Contact me to
> > > learn how I can get you up and productive in Tapestry fast!
> > >
> > > (971) 678-5210
> > > http://howardlewisship.com
> > >
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
Re: Tapestry 5.4-alpha-3
Posted by Howard Lewis Ship <hl...@gmail.com>.
That's great news!
On Fri, Apr 12, 2013 at 12:35 PM, François Facon <fr...@atos.net>wrote:
> Thanks to Emmanuel, tapestry-jquery is already working fine with 5.4.
>
>
>
> 2013/4/12 Howard Lewis Ship <hl...@gmail.com>
>
> > We don't control the tapestry-jquery library; I actually haven't looked
> at
> > it. I suspect it will need to be reworked significantly for 5.4.
> >
> >
> > On Fri, Apr 12, 2013 at 9:40 AM, George Christman
> > <gc...@cardaddy.com>wrote:
> >
> > > I'm just curious if Tapestry5.4 will just be integrating the
> > > Tapestry-Jquery library?
> > >
> > > On Sun, Apr 7, 2013 at 10:29 AM, hantsy <ha...@yahoo.com.cn> wrote:
> > > >
> > > > Created a new thread for it. Thanks
> > > >
> > > > On 4/7/2013 22:16, Bob Harner wrote:
> > > >> Hantsy, you might want to start a separate thread. Your question
> isn't
> > > >> about 5.4-alpha-3 at all.
> > > >>
> > > >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <ha...@yahoo.com.cn> wrote:
> > > >>
> > > >>> I want to know if Tapestry has plan to integrate with Java EE, such
> > as
> > > >>> how to use CDI with Tapestry, I know Tapestry has its DI container,
> > it
> > > >>> can be replaced with CDI?
> > > >>>
> > > >>> I have used Tapestry4 before, and know little about the newest
> > > Tapestry 5.
> > > >>>
> > > >>>
> > > >>> Hantsy
> > > >>> On 4/7/2013 09:11, Saeed wrote:
> > > >>>> Great news! jQuery finally. Well done sire!
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <
> > hlship@gmail.com>
> > > >>> wrote:
> > > >>>>> Hot off the presses! The latest preview release of Tapestry,
> > > >>> 5.4-alpha-3,
> > > >>>>> is now available.
> > > >>>>>
> > > >>>>> Point your build tool of choice at the Maven repository:
> > > >>>>>
> > > >>>>>
> > > >>>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
> > > >>>>> Binary and source archives:
> > > >>>>>
> > > >>>>> http://people.apache.org/~hlship/tapestry-releases/
> > > >>>>>
> > > >>>>> What's new?
> > > >>>>>
> > > >>>>> So much, I've kind of lost track; the main changes are:
> > > >>>>>
> > > >>>>> Most assets are now accessed using a URL that incorporates a
> > Adler32
> > > >>>>> checksum of the asset content. Prior versions of Tapestry
> > > incorporated
> > > >>> the
> > > >>>>> application version number into the URL.
> > > >>>>>
> > > >>>>> What does this mean? When you redeploy your web application,
> most
> > > >>> assets
> > > >>>>> will have not changed: same content, same path, same checksum,
> > > >>> therefore,
> > > >>>>> same URL. This means that client browsers will not have to
> > > re-download
> > > >>> all
> > > >>>>> those assets again just because the application version number
> has
> > > >>> changed.
> > > >>>>> Assets that have changed will have a different content hash, and
> > > >>> therefore,
> > > >>>>> a different asset URL. Browsers will be sure to pull down those
> new
> > > >>>>> versions.
> > > >>>>>
> > > >>>>> Modules are slightly different; because all JavaScript modules
> are
> > > >>> expected
> > > >>>>> to start in a common root URL, there is no reasonable way to
> > > generate a
> > > >>>>> unique content hash for each; module URLs still use the
> application
> > > >>> version
> > > >>>>> number. However, modules and all assets now also send an ETag
> > header;
> > > >>> this
> > > >>>>> means that module requests will still be sent, but will often
> get a
> > > 304
> > > >>>>> (resource not modified) response.
> > > >>>>>
> > > >>>>> Obviously, this is a big change, and we're welcoming feedback.
> > > >>>>>
> > > >>>>> Next up; we have first class support for jQuery.A little bit of
> > > symbol
> > > >>>>> tweaking, and Prototype and Scriptaculous are simply gone for
> good.
> > > >>>>>
> > > >>>>> There's also been improvements to operation tracking, with more
> > > >>> operations
> > > >>>>> performed during a request being tracked. This is useful for the
> > > part of
> > > >>>>> the exception report page that discusses what Tapestry did
> during a
> > > >>>>> request, leading up to the actual exception.
> > > >>>>>
> > > >>>>> There's been big improvements, c/o Kalle, in terms of how
> > exceptions
> > > are
> > > >>>>> reported, with finer control over what gets the full exception
> > page,
> > > and
> > > >>>>> what doesn't.
> > > >>>>>
> > > >>>>> For the rare places where public interfaces changed in
> incompatible
> > > >>> ways,
> > > >>>>> there's now an @IncompatibleChange annotation for methods that
> have
> > > >>>>> changed.
> > > >>>>>
> > > >>>>>
> > > >>>>> A few informational pages such as PageCatalog, ServiceStatus, and
> > > >>> Hibernate
> > > >>>>> Statistics have been merged into a new single (extensible) page,
> > > >>>>> T5Dashboard.
> > > >>>>>
> > > >>>>> ... and lots more little changes, fixes, and improvements.
> > > >>>>>
> > > >>>>> There's still a lot more to come, however. Two principle
> > > improvements
> > > >>> I'm
> > > >>>>> targeting for 5.4:
> > > >>>>>
> > > >>>>> Proper server-side push/websocket support.
> > > >>>>>
> > > >>>>> Built-in performance monitoring and reporting.
> > > >>>>>
> > > >>>>> --
> > > >>>>> Howard M. Lewis Ship
> > > >>>>>
> > > >>>>> Creator of Apache Tapestry
> > > >>>>>
> > > >>>>> The source for Tapestry training, mentoring and support. Contact
> me
> > > to
> > > >>>>> learn how I can get you up and productive in Tapestry fast!
> > > >>>>>
> > > >>>>> (971) 678-5210
> > > >>>>> http://howardlewisship.com
> > > >>>>>
> > > >>>
> > > >>>
> ---------------------------------------------------------------------
> > > >>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > >>> For additional commands, e-mail: users-help@tapestry.apache.org
> > > >>>
> > > >>>
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > >
> > >
> > >
> > > --
> > > George Christman
> > > www.CarDaddy.com
> > > P.O. Box 735
> > > Johnstown, New York
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator of Apache Tapestry
> >
> > The source for Tapestry training, mentoring and support. Contact me to
> > learn how I can get you up and productive in Tapestry fast!
> >
> > (971) 678-5210
> > http://howardlewisship.com
> >
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: Tapestry 5.4-alpha-3
Posted by François Facon <fr...@atos.net>.
Thanks to Emmanuel, tapestry-jquery is already working fine with 5.4.
2013/4/12 Howard Lewis Ship <hl...@gmail.com>
> We don't control the tapestry-jquery library; I actually haven't looked at
> it. I suspect it will need to be reworked significantly for 5.4.
>
>
> On Fri, Apr 12, 2013 at 9:40 AM, George Christman
> <gc...@cardaddy.com>wrote:
>
> > I'm just curious if Tapestry5.4 will just be integrating the
> > Tapestry-Jquery library?
> >
> > On Sun, Apr 7, 2013 at 10:29 AM, hantsy <ha...@yahoo.com.cn> wrote:
> > >
> > > Created a new thread for it. Thanks
> > >
> > > On 4/7/2013 22:16, Bob Harner wrote:
> > >> Hantsy, you might want to start a separate thread. Your question isn't
> > >> about 5.4-alpha-3 at all.
> > >>
> > >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <ha...@yahoo.com.cn> wrote:
> > >>
> > >>> I want to know if Tapestry has plan to integrate with Java EE, such
> as
> > >>> how to use CDI with Tapestry, I know Tapestry has its DI container,
> it
> > >>> can be replaced with CDI?
> > >>>
> > >>> I have used Tapestry4 before, and know little about the newest
> > Tapestry 5.
> > >>>
> > >>>
> > >>> Hantsy
> > >>> On 4/7/2013 09:11, Saeed wrote:
> > >>>> Great news! jQuery finally. Well done sire!
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <
> hlship@gmail.com>
> > >>> wrote:
> > >>>>> Hot off the presses! The latest preview release of Tapestry,
> > >>> 5.4-alpha-3,
> > >>>>> is now available.
> > >>>>>
> > >>>>> Point your build tool of choice at the Maven repository:
> > >>>>>
> > >>>>>
> > >>>
> >
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
> > >>>>> Binary and source archives:
> > >>>>>
> > >>>>> http://people.apache.org/~hlship/tapestry-releases/
> > >>>>>
> > >>>>> What's new?
> > >>>>>
> > >>>>> So much, I've kind of lost track; the main changes are:
> > >>>>>
> > >>>>> Most assets are now accessed using a URL that incorporates a
> Adler32
> > >>>>> checksum of the asset content. Prior versions of Tapestry
> > incorporated
> > >>> the
> > >>>>> application version number into the URL.
> > >>>>>
> > >>>>> What does this mean? When you redeploy your web application, most
> > >>> assets
> > >>>>> will have not changed: same content, same path, same checksum,
> > >>> therefore,
> > >>>>> same URL. This means that client browsers will not have to
> > re-download
> > >>> all
> > >>>>> those assets again just because the application version number has
> > >>> changed.
> > >>>>> Assets that have changed will have a different content hash, and
> > >>> therefore,
> > >>>>> a different asset URL. Browsers will be sure to pull down those new
> > >>>>> versions.
> > >>>>>
> > >>>>> Modules are slightly different; because all JavaScript modules are
> > >>> expected
> > >>>>> to start in a common root URL, there is no reasonable way to
> > generate a
> > >>>>> unique content hash for each; module URLs still use the application
> > >>> version
> > >>>>> number. However, modules and all assets now also send an ETag
> header;
> > >>> this
> > >>>>> means that module requests will still be sent, but will often get a
> > 304
> > >>>>> (resource not modified) response.
> > >>>>>
> > >>>>> Obviously, this is a big change, and we're welcoming feedback.
> > >>>>>
> > >>>>> Next up; we have first class support for jQuery.A little bit of
> > symbol
> > >>>>> tweaking, and Prototype and Scriptaculous are simply gone for good.
> > >>>>>
> > >>>>> There's also been improvements to operation tracking, with more
> > >>> operations
> > >>>>> performed during a request being tracked. This is useful for the
> > part of
> > >>>>> the exception report page that discusses what Tapestry did during a
> > >>>>> request, leading up to the actual exception.
> > >>>>>
> > >>>>> There's been big improvements, c/o Kalle, in terms of how
> exceptions
> > are
> > >>>>> reported, with finer control over what gets the full exception
> page,
> > and
> > >>>>> what doesn't.
> > >>>>>
> > >>>>> For the rare places where public interfaces changed in incompatible
> > >>> ways,
> > >>>>> there's now an @IncompatibleChange annotation for methods that have
> > >>>>> changed.
> > >>>>>
> > >>>>>
> > >>>>> A few informational pages such as PageCatalog, ServiceStatus, and
> > >>> Hibernate
> > >>>>> Statistics have been merged into a new single (extensible) page,
> > >>>>> T5Dashboard.
> > >>>>>
> > >>>>> ... and lots more little changes, fixes, and improvements.
> > >>>>>
> > >>>>> There's still a lot more to come, however. Two principle
> > improvements
> > >>> I'm
> > >>>>> targeting for 5.4:
> > >>>>>
> > >>>>> Proper server-side push/websocket support.
> > >>>>>
> > >>>>> Built-in performance monitoring and reporting.
> > >>>>>
> > >>>>> --
> > >>>>> Howard M. Lewis Ship
> > >>>>>
> > >>>>> Creator of Apache Tapestry
> > >>>>>
> > >>>>> The source for Tapestry training, mentoring and support. Contact me
> > to
> > >>>>> learn how I can get you up and productive in Tapestry fast!
> > >>>>>
> > >>>>> (971) 678-5210
> > >>>>> http://howardlewisship.com
> > >>>>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > >>> For additional commands, e-mail: users-help@tapestry.apache.org
> > >>>
> > >>>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> >
> >
> >
> > --
> > George Christman
> > www.CarDaddy.com
> > P.O. Box 735
> > Johnstown, New York
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
Re: Tapestry 5.4-alpha-3
Posted by Howard Lewis Ship <hl...@gmail.com>.
We don't control the tapestry-jquery library; I actually haven't looked at
it. I suspect it will need to be reworked significantly for 5.4.
On Fri, Apr 12, 2013 at 9:40 AM, George Christman
<gc...@cardaddy.com>wrote:
> I'm just curious if Tapestry5.4 will just be integrating the
> Tapestry-Jquery library?
>
> On Sun, Apr 7, 2013 at 10:29 AM, hantsy <ha...@yahoo.com.cn> wrote:
> >
> > Created a new thread for it. Thanks
> >
> > On 4/7/2013 22:16, Bob Harner wrote:
> >> Hantsy, you might want to start a separate thread. Your question isn't
> >> about 5.4-alpha-3 at all.
> >>
> >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <ha...@yahoo.com.cn> wrote:
> >>
> >>> I want to know if Tapestry has plan to integrate with Java EE, such as
> >>> how to use CDI with Tapestry, I know Tapestry has its DI container, it
> >>> can be replaced with CDI?
> >>>
> >>> I have used Tapestry4 before, and know little about the newest
> Tapestry 5.
> >>>
> >>>
> >>> Hantsy
> >>> On 4/7/2013 09:11, Saeed wrote:
> >>>> Great news! jQuery finally. Well done sire!
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <hl...@gmail.com>
> >>> wrote:
> >>>>> Hot off the presses! The latest preview release of Tapestry,
> >>> 5.4-alpha-3,
> >>>>> is now available.
> >>>>>
> >>>>> Point your build tool of choice at the Maven repository:
> >>>>>
> >>>>>
> >>>
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
> >>>>> Binary and source archives:
> >>>>>
> >>>>> http://people.apache.org/~hlship/tapestry-releases/
> >>>>>
> >>>>> What's new?
> >>>>>
> >>>>> So much, I've kind of lost track; the main changes are:
> >>>>>
> >>>>> Most assets are now accessed using a URL that incorporates a Adler32
> >>>>> checksum of the asset content. Prior versions of Tapestry
> incorporated
> >>> the
> >>>>> application version number into the URL.
> >>>>>
> >>>>> What does this mean? When you redeploy your web application, most
> >>> assets
> >>>>> will have not changed: same content, same path, same checksum,
> >>> therefore,
> >>>>> same URL. This means that client browsers will not have to
> re-download
> >>> all
> >>>>> those assets again just because the application version number has
> >>> changed.
> >>>>> Assets that have changed will have a different content hash, and
> >>> therefore,
> >>>>> a different asset URL. Browsers will be sure to pull down those new
> >>>>> versions.
> >>>>>
> >>>>> Modules are slightly different; because all JavaScript modules are
> >>> expected
> >>>>> to start in a common root URL, there is no reasonable way to
> generate a
> >>>>> unique content hash for each; module URLs still use the application
> >>> version
> >>>>> number. However, modules and all assets now also send an ETag header;
> >>> this
> >>>>> means that module requests will still be sent, but will often get a
> 304
> >>>>> (resource not modified) response.
> >>>>>
> >>>>> Obviously, this is a big change, and we're welcoming feedback.
> >>>>>
> >>>>> Next up; we have first class support for jQuery.A little bit of
> symbol
> >>>>> tweaking, and Prototype and Scriptaculous are simply gone for good.
> >>>>>
> >>>>> There's also been improvements to operation tracking, with more
> >>> operations
> >>>>> performed during a request being tracked. This is useful for the
> part of
> >>>>> the exception report page that discusses what Tapestry did during a
> >>>>> request, leading up to the actual exception.
> >>>>>
> >>>>> There's been big improvements, c/o Kalle, in terms of how exceptions
> are
> >>>>> reported, with finer control over what gets the full exception page,
> and
> >>>>> what doesn't.
> >>>>>
> >>>>> For the rare places where public interfaces changed in incompatible
> >>> ways,
> >>>>> there's now an @IncompatibleChange annotation for methods that have
> >>>>> changed.
> >>>>>
> >>>>>
> >>>>> A few informational pages such as PageCatalog, ServiceStatus, and
> >>> Hibernate
> >>>>> Statistics have been merged into a new single (extensible) page,
> >>>>> T5Dashboard.
> >>>>>
> >>>>> ... and lots more little changes, fixes, and improvements.
> >>>>>
> >>>>> There's still a lot more to come, however. Two principle
> improvements
> >>> I'm
> >>>>> targeting for 5.4:
> >>>>>
> >>>>> Proper server-side push/websocket support.
> >>>>>
> >>>>> Built-in performance monitoring and reporting.
> >>>>>
> >>>>> --
> >>>>> Howard M. Lewis Ship
> >>>>>
> >>>>> Creator of Apache Tapestry
> >>>>>
> >>>>> The source for Tapestry training, mentoring and support. Contact me
> to
> >>>>> learn how I can get you up and productive in Tapestry fast!
> >>>>>
> >>>>> (971) 678-5210
> >>>>> http://howardlewisship.com
> >>>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>
> >>>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
>
>
>
> --
> George Christman
> www.CarDaddy.com
> P.O. Box 735
> Johnstown, New York
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
Re: Tapestry 5.4-alpha-3
Posted by François Facon <fr...@atos.net>.
Howard go a step forward in jQuery integration by using coffeescript. So
Tapestry-jQuery.js that was provided by Tapestry-jQuery is no more needed.
Tapestry-jQuery have to be consider as a lib that ease the use of some
jQuery Plugin used by Kawwa.
2013/4/12 George Christman <gc...@cardaddy.com>
> I'm just curious if Tapestry5.4 will just be integrating the
> Tapestry-Jquery library?
>
> On Sun, Apr 7, 2013 at 10:29 AM, hantsy <ha...@yahoo.com.cn> wrote:
> >
> > Created a new thread for it. Thanks
> >
> > On 4/7/2013 22:16, Bob Harner wrote:
> >> Hantsy, you might want to start a separate thread. Your question isn't
> >> about 5.4-alpha-3 at all.
> >>
> >> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <ha...@yahoo.com.cn> wrote:
> >>
> >>> I want to know if Tapestry has plan to integrate with Java EE, such as
> >>> how to use CDI with Tapestry, I know Tapestry has its DI container, it
> >>> can be replaced with CDI?
> >>>
> >>> I have used Tapestry4 before, and know little about the newest
> Tapestry 5.
> >>>
> >>>
> >>> Hantsy
> >>> On 4/7/2013 09:11, Saeed wrote:
> >>>> Great news! jQuery finally. Well done sire!
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <hl...@gmail.com>
> >>> wrote:
> >>>>> Hot off the presses! The latest preview release of Tapestry,
> >>> 5.4-alpha-3,
> >>>>> is now available.
> >>>>>
> >>>>> Point your build tool of choice at the Maven repository:
> >>>>>
> >>>>>
> >>>
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
> >>>>> Binary and source archives:
> >>>>>
> >>>>> http://people.apache.org/~hlship/tapestry-releases/
> >>>>>
> >>>>> What's new?
> >>>>>
> >>>>> So much, I've kind of lost track; the main changes are:
> >>>>>
> >>>>> Most assets are now accessed using a URL that incorporates a Adler32
> >>>>> checksum of the asset content. Prior versions of Tapestry
> incorporated
> >>> the
> >>>>> application version number into the URL.
> >>>>>
> >>>>> What does this mean? When you redeploy your web application, most
> >>> assets
> >>>>> will have not changed: same content, same path, same checksum,
> >>> therefore,
> >>>>> same URL. This means that client browsers will not have to
> re-download
> >>> all
> >>>>> those assets again just because the application version number has
> >>> changed.
> >>>>> Assets that have changed will have a different content hash, and
> >>> therefore,
> >>>>> a different asset URL. Browsers will be sure to pull down those new
> >>>>> versions.
> >>>>>
> >>>>> Modules are slightly different; because all JavaScript modules are
> >>> expected
> >>>>> to start in a common root URL, there is no reasonable way to
> generate a
> >>>>> unique content hash for each; module URLs still use the application
> >>> version
> >>>>> number. However, modules and all assets now also send an ETag header;
> >>> this
> >>>>> means that module requests will still be sent, but will often get a
> 304
> >>>>> (resource not modified) response.
> >>>>>
> >>>>> Obviously, this is a big change, and we're welcoming feedback.
> >>>>>
> >>>>> Next up; we have first class support for jQuery.A little bit of
> symbol
> >>>>> tweaking, and Prototype and Scriptaculous are simply gone for good.
> >>>>>
> >>>>> There's also been improvements to operation tracking, with more
> >>> operations
> >>>>> performed during a request being tracked. This is useful for the
> part of
> >>>>> the exception report page that discusses what Tapestry did during a
> >>>>> request, leading up to the actual exception.
> >>>>>
> >>>>> There's been big improvements, c/o Kalle, in terms of how exceptions
> are
> >>>>> reported, with finer control over what gets the full exception page,
> and
> >>>>> what doesn't.
> >>>>>
> >>>>> For the rare places where public interfaces changed in incompatible
> >>> ways,
> >>>>> there's now an @IncompatibleChange annotation for methods that have
> >>>>> changed.
> >>>>>
> >>>>>
> >>>>> A few informational pages such as PageCatalog, ServiceStatus, and
> >>> Hibernate
> >>>>> Statistics have been merged into a new single (extensible) page,
> >>>>> T5Dashboard.
> >>>>>
> >>>>> ... and lots more little changes, fixes, and improvements.
> >>>>>
> >>>>> There's still a lot more to come, however. Two principle
> improvements
> >>> I'm
> >>>>> targeting for 5.4:
> >>>>>
> >>>>> Proper server-side push/websocket support.
> >>>>>
> >>>>> Built-in performance monitoring and reporting.
> >>>>>
> >>>>> --
> >>>>> Howard M. Lewis Ship
> >>>>>
> >>>>> Creator of Apache Tapestry
> >>>>>
> >>>>> The source for Tapestry training, mentoring and support. Contact me
> to
> >>>>> learn how I can get you up and productive in Tapestry fast!
> >>>>>
> >>>>> (971) 678-5210
> >>>>> http://howardlewisship.com
> >>>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>
> >>>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
>
>
>
> --
> George Christman
> www.CarDaddy.com
> P.O. Box 735
> Johnstown, New York
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Tapestry 5.4-alpha-3
Posted by George Christman <gc...@cardaddy.com>.
I'm just curious if Tapestry5.4 will just be integrating the
Tapestry-Jquery library?
On Sun, Apr 7, 2013 at 10:29 AM, hantsy <ha...@yahoo.com.cn> wrote:
>
> Created a new thread for it. Thanks
>
> On 4/7/2013 22:16, Bob Harner wrote:
>> Hantsy, you might want to start a separate thread. Your question isn't
>> about 5.4-alpha-3 at all.
>>
>> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <ha...@yahoo.com.cn> wrote:
>>
>>> I want to know if Tapestry has plan to integrate with Java EE, such as
>>> how to use CDI with Tapestry, I know Tapestry has its DI container, it
>>> can be replaced with CDI?
>>>
>>> I have used Tapestry4 before, and know little about the newest Tapestry 5.
>>>
>>>
>>> Hantsy
>>> On 4/7/2013 09:11, Saeed wrote:
>>>> Great news! jQuery finally. Well done sire!
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <hl...@gmail.com>
>>> wrote:
>>>>> Hot off the presses! The latest preview release of Tapestry,
>>> 5.4-alpha-3,
>>>>> is now available.
>>>>>
>>>>> Point your build tool of choice at the Maven repository:
>>>>>
>>>>>
>>> https://repository.apache.org/content/repositories/orgapachetapestry-072/
>>>>> Binary and source archives:
>>>>>
>>>>> http://people.apache.org/~hlship/tapestry-releases/
>>>>>
>>>>> What's new?
>>>>>
>>>>> So much, I've kind of lost track; the main changes are:
>>>>>
>>>>> Most assets are now accessed using a URL that incorporates a Adler32
>>>>> checksum of the asset content. Prior versions of Tapestry incorporated
>>> the
>>>>> application version number into the URL.
>>>>>
>>>>> What does this mean? When you redeploy your web application, most
>>> assets
>>>>> will have not changed: same content, same path, same checksum,
>>> therefore,
>>>>> same URL. This means that client browsers will not have to re-download
>>> all
>>>>> those assets again just because the application version number has
>>> changed.
>>>>> Assets that have changed will have a different content hash, and
>>> therefore,
>>>>> a different asset URL. Browsers will be sure to pull down those new
>>>>> versions.
>>>>>
>>>>> Modules are slightly different; because all JavaScript modules are
>>> expected
>>>>> to start in a common root URL, there is no reasonable way to generate a
>>>>> unique content hash for each; module URLs still use the application
>>> version
>>>>> number. However, modules and all assets now also send an ETag header;
>>> this
>>>>> means that module requests will still be sent, but will often get a 304
>>>>> (resource not modified) response.
>>>>>
>>>>> Obviously, this is a big change, and we're welcoming feedback.
>>>>>
>>>>> Next up; we have first class support for jQuery.A little bit of symbol
>>>>> tweaking, and Prototype and Scriptaculous are simply gone for good.
>>>>>
>>>>> There's also been improvements to operation tracking, with more
>>> operations
>>>>> performed during a request being tracked. This is useful for the part of
>>>>> the exception report page that discusses what Tapestry did during a
>>>>> request, leading up to the actual exception.
>>>>>
>>>>> There's been big improvements, c/o Kalle, in terms of how exceptions are
>>>>> reported, with finer control over what gets the full exception page, and
>>>>> what doesn't.
>>>>>
>>>>> For the rare places where public interfaces changed in incompatible
>>> ways,
>>>>> there's now an @IncompatibleChange annotation for methods that have
>>>>> changed.
>>>>>
>>>>>
>>>>> A few informational pages such as PageCatalog, ServiceStatus, and
>>> Hibernate
>>>>> Statistics have been merged into a new single (extensible) page,
>>>>> T5Dashboard.
>>>>>
>>>>> ... and lots more little changes, fixes, and improvements.
>>>>>
>>>>> There's still a lot more to come, however. Two principle improvements
>>> I'm
>>>>> targeting for 5.4:
>>>>>
>>>>> Proper server-side push/websocket support.
>>>>>
>>>>> Built-in performance monitoring and reporting.
>>>>>
>>>>> --
>>>>> Howard M. Lewis Ship
>>>>>
>>>>> Creator of Apache Tapestry
>>>>>
>>>>> The source for Tapestry training, mentoring and support. Contact me to
>>>>> learn how I can get you up and productive in Tapestry fast!
>>>>>
>>>>> (971) 678-5210
>>>>> http://howardlewisship.com
>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
--
George Christman
www.CarDaddy.com
P.O. Box 735
Johnstown, New York
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry 5.4-alpha-3
Posted by hantsy <ha...@yahoo.com.cn>.
Created a new thread for it. Thanks
On 4/7/2013 22:16, Bob Harner wrote:
> Hantsy, you might want to start a separate thread. Your question isn't
> about 5.4-alpha-3 at all.
>
> On Sun, Apr 7, 2013 at 9:23 AM, hantsy <ha...@yahoo.com.cn> wrote:
>
>> I want to know if Tapestry has plan to integrate with Java EE, such as
>> how to use CDI with Tapestry, I know Tapestry has its DI container, it
>> can be replaced with CDI?
>>
>> I have used Tapestry4 before, and know little about the newest Tapestry 5.
>>
>>
>> Hantsy
>> On 4/7/2013 09:11, Saeed wrote:
>>> Great news! jQuery finally. Well done sire!
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <hl...@gmail.com>
>> wrote:
>>>> Hot off the presses! The latest preview release of Tapestry,
>> 5.4-alpha-3,
>>>> is now available.
>>>>
>>>> Point your build tool of choice at the Maven repository:
>>>>
>>>>
>> https://repository.apache.org/content/repositories/orgapachetapestry-072/
>>>> Binary and source archives:
>>>>
>>>> http://people.apache.org/~hlship/tapestry-releases/
>>>>
>>>> What's new?
>>>>
>>>> So much, I've kind of lost track; the main changes are:
>>>>
>>>> Most assets are now accessed using a URL that incorporates a Adler32
>>>> checksum of the asset content. Prior versions of Tapestry incorporated
>> the
>>>> application version number into the URL.
>>>>
>>>> What does this mean? When you redeploy your web application, most
>> assets
>>>> will have not changed: same content, same path, same checksum,
>> therefore,
>>>> same URL. This means that client browsers will not have to re-download
>> all
>>>> those assets again just because the application version number has
>> changed.
>>>> Assets that have changed will have a different content hash, and
>> therefore,
>>>> a different asset URL. Browsers will be sure to pull down those new
>>>> versions.
>>>>
>>>> Modules are slightly different; because all JavaScript modules are
>> expected
>>>> to start in a common root URL, there is no reasonable way to generate a
>>>> unique content hash for each; module URLs still use the application
>> version
>>>> number. However, modules and all assets now also send an ETag header;
>> this
>>>> means that module requests will still be sent, but will often get a 304
>>>> (resource not modified) response.
>>>>
>>>> Obviously, this is a big change, and we're welcoming feedback.
>>>>
>>>> Next up; we have first class support for jQuery.A little bit of symbol
>>>> tweaking, and Prototype and Scriptaculous are simply gone for good.
>>>>
>>>> There's also been improvements to operation tracking, with more
>> operations
>>>> performed during a request being tracked. This is useful for the part of
>>>> the exception report page that discusses what Tapestry did during a
>>>> request, leading up to the actual exception.
>>>>
>>>> There's been big improvements, c/o Kalle, in terms of how exceptions are
>>>> reported, with finer control over what gets the full exception page, and
>>>> what doesn't.
>>>>
>>>> For the rare places where public interfaces changed in incompatible
>> ways,
>>>> there's now an @IncompatibleChange annotation for methods that have
>>>> changed.
>>>>
>>>>
>>>> A few informational pages such as PageCatalog, ServiceStatus, and
>> Hibernate
>>>> Statistics have been merged into a new single (extensible) page,
>>>> T5Dashboard.
>>>>
>>>> ... and lots more little changes, fixes, and improvements.
>>>>
>>>> There's still a lot more to come, however. Two principle improvements
>> I'm
>>>> targeting for 5.4:
>>>>
>>>> Proper server-side push/websocket support.
>>>>
>>>> Built-in performance monitoring and reporting.
>>>>
>>>> --
>>>> Howard M. Lewis Ship
>>>>
>>>> Creator of Apache Tapestry
>>>>
>>>> The source for Tapestry training, mentoring and support. Contact me to
>>>> learn how I can get you up and productive in Tapestry fast!
>>>>
>>>> (971) 678-5210
>>>> http://howardlewisship.com
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry 5.4-alpha-3
Posted by Bob Harner <bo...@gmail.com>.
Hantsy, you might want to start a separate thread. Your question isn't
about 5.4-alpha-3 at all.
On Sun, Apr 7, 2013 at 9:23 AM, hantsy <ha...@yahoo.com.cn> wrote:
> I want to know if Tapestry has plan to integrate with Java EE, such as
> how to use CDI with Tapestry, I know Tapestry has its DI container, it
> can be replaced with CDI?
>
> I have used Tapestry4 before, and know little about the newest Tapestry 5.
>
>
> Hantsy
> On 4/7/2013 09:11, Saeed wrote:
> > Great news! jQuery finally. Well done sire!
> >
> >
> >
> >
> >
> > On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <hl...@gmail.com>
> wrote:
> >
> >> Hot off the presses! The latest preview release of Tapestry,
> 5.4-alpha-3,
> >> is now available.
> >>
> >> Point your build tool of choice at the Maven repository:
> >>
> >>
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
> >>
> >> Binary and source archives:
> >>
> >> http://people.apache.org/~hlship/tapestry-releases/
> >>
> >> What's new?
> >>
> >> So much, I've kind of lost track; the main changes are:
> >>
> >> Most assets are now accessed using a URL that incorporates a Adler32
> >> checksum of the asset content. Prior versions of Tapestry incorporated
> the
> >> application version number into the URL.
> >>
> >> What does this mean? When you redeploy your web application, most
> assets
> >> will have not changed: same content, same path, same checksum,
> therefore,
> >> same URL. This means that client browsers will not have to re-download
> all
> >> those assets again just because the application version number has
> changed.
> >>
> >> Assets that have changed will have a different content hash, and
> therefore,
> >> a different asset URL. Browsers will be sure to pull down those new
> >> versions.
> >>
> >> Modules are slightly different; because all JavaScript modules are
> expected
> >> to start in a common root URL, there is no reasonable way to generate a
> >> unique content hash for each; module URLs still use the application
> version
> >> number. However, modules and all assets now also send an ETag header;
> this
> >> means that module requests will still be sent, but will often get a 304
> >> (resource not modified) response.
> >>
> >> Obviously, this is a big change, and we're welcoming feedback.
> >>
> >> Next up; we have first class support for jQuery.A little bit of symbol
> >> tweaking, and Prototype and Scriptaculous are simply gone for good.
> >>
> >> There's also been improvements to operation tracking, with more
> operations
> >> performed during a request being tracked. This is useful for the part of
> >> the exception report page that discusses what Tapestry did during a
> >> request, leading up to the actual exception.
> >>
> >> There's been big improvements, c/o Kalle, in terms of how exceptions are
> >> reported, with finer control over what gets the full exception page, and
> >> what doesn't.
> >>
> >> For the rare places where public interfaces changed in incompatible
> ways,
> >> there's now an @IncompatibleChange annotation for methods that have
> >> changed.
> >>
> >>
> >> A few informational pages such as PageCatalog, ServiceStatus, and
> Hibernate
> >> Statistics have been merged into a new single (extensible) page,
> >> T5Dashboard.
> >>
> >> ... and lots more little changes, fixes, and improvements.
> >>
> >> There's still a lot more to come, however. Two principle improvements
> I'm
> >> targeting for 5.4:
> >>
> >> Proper server-side push/websocket support.
> >>
> >> Built-in performance monitoring and reporting.
> >>
> >> --
> >> Howard M. Lewis Ship
> >>
> >> Creator of Apache Tapestry
> >>
> >> The source for Tapestry training, mentoring and support. Contact me to
> >> learn how I can get you up and productive in Tapestry fast!
> >>
> >> (971) 678-5210
> >> http://howardlewisship.com
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Tapestry 5.4-alpha-3
Posted by hantsy <ha...@yahoo.com.cn>.
I want to know if Tapestry has plan to integrate with Java EE, such as
how to use CDI with Tapestry, I know Tapestry has its DI container, it
can be replaced with CDI?
I have used Tapestry4 before, and know little about the newest Tapestry 5.
Hantsy
On 4/7/2013 09:11, Saeed wrote:
> Great news! jQuery finally. Well done sire!
>
>
>
>
>
> On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
>
>> Hot off the presses! The latest preview release of Tapestry, 5.4-alpha-3,
>> is now available.
>>
>> Point your build tool of choice at the Maven repository:
>>
>> https://repository.apache.org/content/repositories/orgapachetapestry-072/
>>
>> Binary and source archives:
>>
>> http://people.apache.org/~hlship/tapestry-releases/
>>
>> What's new?
>>
>> So much, I've kind of lost track; the main changes are:
>>
>> Most assets are now accessed using a URL that incorporates a Adler32
>> checksum of the asset content. Prior versions of Tapestry incorporated the
>> application version number into the URL.
>>
>> What does this mean? When you redeploy your web application, most assets
>> will have not changed: same content, same path, same checksum, therefore,
>> same URL. This means that client browsers will not have to re-download all
>> those assets again just because the application version number has changed.
>>
>> Assets that have changed will have a different content hash, and therefore,
>> a different asset URL. Browsers will be sure to pull down those new
>> versions.
>>
>> Modules are slightly different; because all JavaScript modules are expected
>> to start in a common root URL, there is no reasonable way to generate a
>> unique content hash for each; module URLs still use the application version
>> number. However, modules and all assets now also send an ETag header; this
>> means that module requests will still be sent, but will often get a 304
>> (resource not modified) response.
>>
>> Obviously, this is a big change, and we're welcoming feedback.
>>
>> Next up; we have first class support for jQuery.A little bit of symbol
>> tweaking, and Prototype and Scriptaculous are simply gone for good.
>>
>> There's also been improvements to operation tracking, with more operations
>> performed during a request being tracked. This is useful for the part of
>> the exception report page that discusses what Tapestry did during a
>> request, leading up to the actual exception.
>>
>> There's been big improvements, c/o Kalle, in terms of how exceptions are
>> reported, with finer control over what gets the full exception page, and
>> what doesn't.
>>
>> For the rare places where public interfaces changed in incompatible ways,
>> there's now an @IncompatibleChange annotation for methods that have
>> changed.
>>
>>
>> A few informational pages such as PageCatalog, ServiceStatus, and Hibernate
>> Statistics have been merged into a new single (extensible) page,
>> T5Dashboard.
>>
>> ... and lots more little changes, fixes, and improvements.
>>
>> There's still a lot more to come, however. Two principle improvements I'm
>> targeting for 5.4:
>>
>> Proper server-side push/websocket support.
>>
>> Built-in performance monitoring and reporting.
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator of Apache Tapestry
>>
>> The source for Tapestry training, mentoring and support. Contact me to
>> learn how I can get you up and productive in Tapestry fast!
>>
>> (971) 678-5210
>> http://howardlewisship.com
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Tapestry 5.4-alpha-3
Posted by Saeed <si...@gmail.com>.
Great news! jQuery finally. Well done sire!
On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> Hot off the presses! The latest preview release of Tapestry, 5.4-alpha-3,
> is now available.
>
> Point your build tool of choice at the Maven repository:
>
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
>
> Binary and source archives:
>
> http://people.apache.org/~hlship/tapestry-releases/
>
> What's new?
>
> So much, I've kind of lost track; the main changes are:
>
> Most assets are now accessed using a URL that incorporates a Adler32
> checksum of the asset content. Prior versions of Tapestry incorporated the
> application version number into the URL.
>
> What does this mean? When you redeploy your web application, most assets
> will have not changed: same content, same path, same checksum, therefore,
> same URL. This means that client browsers will not have to re-download all
> those assets again just because the application version number has changed.
>
> Assets that have changed will have a different content hash, and therefore,
> a different asset URL. Browsers will be sure to pull down those new
> versions.
>
> Modules are slightly different; because all JavaScript modules are expected
> to start in a common root URL, there is no reasonable way to generate a
> unique content hash for each; module URLs still use the application version
> number. However, modules and all assets now also send an ETag header; this
> means that module requests will still be sent, but will often get a 304
> (resource not modified) response.
>
> Obviously, this is a big change, and we're welcoming feedback.
>
> Next up; we have first class support for jQuery.A little bit of symbol
> tweaking, and Prototype and Scriptaculous are simply gone for good.
>
> There's also been improvements to operation tracking, with more operations
> performed during a request being tracked. This is useful for the part of
> the exception report page that discusses what Tapestry did during a
> request, leading up to the actual exception.
>
> There's been big improvements, c/o Kalle, in terms of how exceptions are
> reported, with finer control over what gets the full exception page, and
> what doesn't.
>
> For the rare places where public interfaces changed in incompatible ways,
> there's now an @IncompatibleChange annotation for methods that have
> changed.
>
>
> A few informational pages such as PageCatalog, ServiceStatus, and Hibernate
> Statistics have been merged into a new single (extensible) page,
> T5Dashboard.
>
> ... and lots more little changes, fixes, and improvements.
>
> There's still a lot more to come, however. Two principle improvements I'm
> targeting for 5.4:
>
> Proper server-side push/websocket support.
>
> Built-in performance monitoring and reporting.
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
Re: Tapestry 5.4-alpha-3
Posted by Saeed <si...@gmail.com>.
Great news! jQuery finally. Well done sire!
On Sat, Apr 6, 2013 at 11:45 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> Hot off the presses! The latest preview release of Tapestry, 5.4-alpha-3,
> is now available.
>
> Point your build tool of choice at the Maven repository:
>
> https://repository.apache.org/content/repositories/orgapachetapestry-072/
>
> Binary and source archives:
>
> http://people.apache.org/~hlship/tapestry-releases/
>
> What's new?
>
> So much, I've kind of lost track; the main changes are:
>
> Most assets are now accessed using a URL that incorporates a Adler32
> checksum of the asset content. Prior versions of Tapestry incorporated the
> application version number into the URL.
>
> What does this mean? When you redeploy your web application, most assets
> will have not changed: same content, same path, same checksum, therefore,
> same URL. This means that client browsers will not have to re-download all
> those assets again just because the application version number has changed.
>
> Assets that have changed will have a different content hash, and therefore,
> a different asset URL. Browsers will be sure to pull down those new
> versions.
>
> Modules are slightly different; because all JavaScript modules are expected
> to start in a common root URL, there is no reasonable way to generate a
> unique content hash for each; module URLs still use the application version
> number. However, modules and all assets now also send an ETag header; this
> means that module requests will still be sent, but will often get a 304
> (resource not modified) response.
>
> Obviously, this is a big change, and we're welcoming feedback.
>
> Next up; we have first class support for jQuery.A little bit of symbol
> tweaking, and Prototype and Scriptaculous are simply gone for good.
>
> There's also been improvements to operation tracking, with more operations
> performed during a request being tracked. This is useful for the part of
> the exception report page that discusses what Tapestry did during a
> request, leading up to the actual exception.
>
> There's been big improvements, c/o Kalle, in terms of how exceptions are
> reported, with finer control over what gets the full exception page, and
> what doesn't.
>
> For the rare places where public interfaces changed in incompatible ways,
> there's now an @IncompatibleChange annotation for methods that have
> changed.
>
>
> A few informational pages such as PageCatalog, ServiceStatus, and Hibernate
> Statistics have been merged into a new single (extensible) page,
> T5Dashboard.
>
> ... and lots more little changes, fixes, and improvements.
>
> There's still a lot more to come, however. Two principle improvements I'm
> targeting for 5.4:
>
> Proper server-side push/websocket support.
>
> Built-in performance monitoring and reporting.
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>