You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Angelo Chen <an...@yahoo.com.hk> on 2008/03/13 15:07:10 UTC
t5: new features in 5.0.11
Hi,
As usual I always like to look at new features of every release, here are
the one officially listed as new to the 5.0.11:
1. The @Cached annotation has been added to allowing the caching of method
results.
Can't understand this, any use case to explain this?
2. Tapestry can now generate accessor methods for fields automatically via
the @Property annotation.
This is a cool feature, saving a lot of code.
3. It is now possible to override the built-in display and edit blocks for
data types.
What's this?
4. Tapestry now supports "Index" pages at the root or in sub-folders.
nice feature.
5. Tapestry pages may now be secured for access only via HTTPS.
good feature.
6. Added the FormFragment component to allow for forms that are mutable on
the client-side. In addition, the Form component may now update a Zone.
good feature.
a.c.
--
View this message in context: http://www.nabble.com/t5%3A-new-features-in-5.0.11-tp16025541p16025541.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: t5: new features in 5.0.11
Posted by Christian Edward Gruber <ch...@gmail.com>.
Can you still do so, supporting the old packaged but deprecating
those annotations with the old packaging?
I think that now would be the time, since you're ramping up to release.
Christian.
On 13-Mar-08, at 19:11 , Howard Lewis Ship wrote:
> I think it is safe to say that all annotations in
> org.apache.tapestry.annotations apply ONLY to Tapestry component
> classes (components, mixins, pages, base).
>
> Oops, that's not quite true; theres just a couple mixed in there that
> are modifiers for @Inject and can work with IoC dependency injection.
>
> With hindsight, I would have separated the component annotations from
> the more widely used annotations.
>
> On Thu, Mar 13, 2008 at 10:13 AM, Ted Steen <te...@gmail.com>
> wrote:
>> Only classes controlled by tapestry.
>> That is, components, mixins, pages and base-classes
>> I hope I didn't miss any.
>>
>> 2008/3/13, Marcus <mv...@gmail.com>:
>>
>>
>>> Hi,
>>>
>>> @Property works for any class? or only for components and pages?
>>>
>>> thanks,
>>>
>>>
>>> Marcus
>>>
>>>
>>> On 3/13/08, Robert Zeigler <ro...@scazdl.org> wrote:
>>>>
>>>> On Mar 13, 2008, at 3/139:07 AM , Angelo Chen wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> As usual I always like to look at new features of every release,
>>>>> here are
>>>>> the one officially listed as new to the 5.0.11:
>>>>>
>>>>> 1. The @Cached annotation has been added to allowing the caching
>>>>> of
>>>>> method
>>>>> results.
>>>>>
>>>>> Can't understand this, any use case to explain this?
>>>>
>>>>
>>>> .java:
>>>>
>>>> public List<DataType> getListOfDataType() {
>>>> return someExpensiveMethodCall();
>>>> }
>>>>
>>>> .tml:
>>>>
>>>> <t:if test="listOfDataType.size()">
>>>> <t:loop source="listOfDataType">
>>>> ...
>>>> </t:loop>
>>>> <t:parameter name="else">
>>>> No data to display
>>>> </t:parameter>
>>>> </t:if>
>>>>
>>>> W/out @Cached, the above template results in
>>>> someExpensiveMethodCall
>>>> being called 2x per render. Would be nice to call it only once/
>>>> render.
>>>> So if you change .java to look like:
>>>>
>>>> @Cached
>>>> public List<DataType> getListOfDataType() {
>>>> return someExpensiveMethodCall();
>>>> }
>>>>
>>>> Now someExpensiveMethodCall() will only occur once/render.
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>> 2. Tapestry can now generate accessor methods for fields
>>>>> automatically via
>>>>> the @Property annotation.
>>>>>
>>>>> This is a cool feature, saving a lot of code.
>>>>>
>>>>> 3. It is now possible to override the built-in display and edit
>>>>> blocks for
>>>>> data types.
>>>>>
>>>>> What's this?
>>>>
>>>> Tapestry supplies a set of "defaults" for editing & viewing data
>>>> types
>>>> via BeanEditor, BeanEditForm, Grid, BeanDisplay, and so forth.
>>>> Now you can override the defaults. As an example, due to licensing
>>>> issues, T5 dropped the use of the dynarch calendar in favor of
>>>> a simpler javascript calendar with compatible licensing. Suppose
>>>> you
>>>> really want to use dynarch's js calendar.
>>>> Before this change, there was no way to supply your own calendar
>>>> component in place of Tapestry's default, so even if you had this
>>>> pretty jscalendar-based component,
>>>> it wouldn't be used, unless you did something like add:
>>>> @DataType("customdate") to every one of your date fields, or had a
>>>> service that changed the DataType for any bean models you create.
>>>> Yuck.
>>>> Now, you can override the built-in, and tapestry picks it up. Nice.
>>>>
>>>> Cheers,
>>>>
>>>> Robert
>>>>
>>>>>
>>>>>
>>>>> 4. Tapestry now supports "Index" pages at the root or in sub-
>>>>> folders.
>>>>>
>>>>> nice feature.
>>>>>
>>>>> 5. Tapestry pages may now be secured for access only via HTTPS.
>>>>>
>>>>> good feature.
>>>>>
>>>>> 6. Added the FormFragment component to allow for forms that are
>>>>> mutable on
>>>>> the client-side. In addition, the Form component may now update a
>>>>> Zone.
>>>>>
>>>>> good feature.
>>>>>
>>>>> a.c.
>>>>> --
>>>>> View this message in context:
>>>> http://www.nabble.com/t5%3A-new-features-in-5.0.11-tp16025541p16025541.html
>>>>> Sent from the Tapestry - User mailing list archive at Nabble.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
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>
>>
>> --
>> /ted
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> 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: t5: new features in 5.0.11
Posted by Howard Lewis Ship <hl...@gmail.com>.
I think it is safe to say that all annotations in
org.apache.tapestry.annotations apply ONLY to Tapestry component
classes (components, mixins, pages, base).
Oops, that's not quite true; theres just a couple mixed in there that
are modifiers for @Inject and can work with IoC dependency injection.
With hindsight, I would have separated the component annotations from
the more widely used annotations.
On Thu, Mar 13, 2008 at 10:13 AM, Ted Steen <te...@gmail.com> wrote:
> Only classes controlled by tapestry.
> That is, components, mixins, pages and base-classes
> I hope I didn't miss any.
>
> 2008/3/13, Marcus <mv...@gmail.com>:
>
>
> > Hi,
> >
> > @Property works for any class? or only for components and pages?
> >
> > thanks,
> >
> >
> > Marcus
> >
> >
> > On 3/13/08, Robert Zeigler <ro...@scazdl.org> wrote:
> > >
> > > On Mar 13, 2008, at 3/139:07 AM , Angelo Chen wrote:
> > >
> > > >
> > > > Hi,
> > > >
> > > > As usual I always like to look at new features of every release,
> > > > here are
> > > > the one officially listed as new to the 5.0.11:
> > > >
> > > > 1. The @Cached annotation has been added to allowing the caching of
> > > > method
> > > > results.
> > > >
> > > > Can't understand this, any use case to explain this?
> > >
> > >
> > > .java:
> > >
> > > public List<DataType> getListOfDataType() {
> > > return someExpensiveMethodCall();
> > > }
> > >
> > > .tml:
> > >
> > > <t:if test="listOfDataType.size()">
> > > <t:loop source="listOfDataType">
> > > ...
> > > </t:loop>
> > > <t:parameter name="else">
> > > No data to display
> > > </t:parameter>
> > > </t:if>
> > >
> > > W/out @Cached, the above template results in someExpensiveMethodCall
> > > being called 2x per render. Would be nice to call it only once/render.
> > > So if you change .java to look like:
> > >
> > > @Cached
> > > public List<DataType> getListOfDataType() {
> > > return someExpensiveMethodCall();
> > > }
> > >
> > > Now someExpensiveMethodCall() will only occur once/render.
> > >
> > >
> > >
> > > >
> > > >
> > > > 2. Tapestry can now generate accessor methods for fields
> > > > automatically via
> > > > the @Property annotation.
> > > >
> > > > This is a cool feature, saving a lot of code.
> > > >
> > > > 3. It is now possible to override the built-in display and edit
> > > > blocks for
> > > > data types.
> > > >
> > > > What's this?
> > >
> > > Tapestry supplies a set of "defaults" for editing & viewing data types
> > > via BeanEditor, BeanEditForm, Grid, BeanDisplay, and so forth.
> > > Now you can override the defaults. As an example, due to licensing
> > > issues, T5 dropped the use of the dynarch calendar in favor of
> > > a simpler javascript calendar with compatible licensing. Suppose you
> > > really want to use dynarch's js calendar.
> > > Before this change, there was no way to supply your own calendar
> > > component in place of Tapestry's default, so even if you had this
> > > pretty jscalendar-based component,
> > > it wouldn't be used, unless you did something like add:
> > > @DataType("customdate") to every one of your date fields, or had a
> > > service that changed the DataType for any bean models you create.
> > > Yuck.
> > > Now, you can override the built-in, and tapestry picks it up. Nice.
> > >
> > > Cheers,
> > >
> > > Robert
> > >
> > > >
> > > >
> > > > 4. Tapestry now supports "Index" pages at the root or in sub-folders.
> > > >
> > > > nice feature.
> > > >
> > > > 5. Tapestry pages may now be secured for access only via HTTPS.
> > > >
> > > > good feature.
> > > >
> > > > 6. Added the FormFragment component to allow for forms that are
> > > > mutable on
> > > > the client-side. In addition, the Form component may now update a
> > > > Zone.
> > > >
> > > > good feature.
> > > >
> > > > a.c.
> > > > --
> > > > View this message in context:
> > > http://www.nabble.com/t5%3A-new-features-in-5.0.11-tp16025541p16025541.html
> > > > Sent from the Tapestry - User mailing list archive at Nabble.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
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> /ted
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: t5: new features in 5.0.11
Posted by Ted Steen <te...@gmail.com>.
Only classes controlled by tapestry.
That is, components, mixins, pages and base-classes
I hope I didn't miss any.
2008/3/13, Marcus <mv...@gmail.com>:
> Hi,
>
> @Property works for any class? or only for components and pages?
>
> thanks,
>
>
> Marcus
>
>
> On 3/13/08, Robert Zeigler <ro...@scazdl.org> wrote:
> >
> > On Mar 13, 2008, at 3/139:07 AM , Angelo Chen wrote:
> >
> > >
> > > Hi,
> > >
> > > As usual I always like to look at new features of every release,
> > > here are
> > > the one officially listed as new to the 5.0.11:
> > >
> > > 1. The @Cached annotation has been added to allowing the caching of
> > > method
> > > results.
> > >
> > > Can't understand this, any use case to explain this?
> >
> >
> > .java:
> >
> > public List<DataType> getListOfDataType() {
> > return someExpensiveMethodCall();
> > }
> >
> > .tml:
> >
> > <t:if test="listOfDataType.size()">
> > <t:loop source="listOfDataType">
> > ...
> > </t:loop>
> > <t:parameter name="else">
> > No data to display
> > </t:parameter>
> > </t:if>
> >
> > W/out @Cached, the above template results in someExpensiveMethodCall
> > being called 2x per render. Would be nice to call it only once/render.
> > So if you change .java to look like:
> >
> > @Cached
> > public List<DataType> getListOfDataType() {
> > return someExpensiveMethodCall();
> > }
> >
> > Now someExpensiveMethodCall() will only occur once/render.
> >
> >
> >
> > >
> > >
> > > 2. Tapestry can now generate accessor methods for fields
> > > automatically via
> > > the @Property annotation.
> > >
> > > This is a cool feature, saving a lot of code.
> > >
> > > 3. It is now possible to override the built-in display and edit
> > > blocks for
> > > data types.
> > >
> > > What's this?
> >
> > Tapestry supplies a set of "defaults" for editing & viewing data types
> > via BeanEditor, BeanEditForm, Grid, BeanDisplay, and so forth.
> > Now you can override the defaults. As an example, due to licensing
> > issues, T5 dropped the use of the dynarch calendar in favor of
> > a simpler javascript calendar with compatible licensing. Suppose you
> > really want to use dynarch's js calendar.
> > Before this change, there was no way to supply your own calendar
> > component in place of Tapestry's default, so even if you had this
> > pretty jscalendar-based component,
> > it wouldn't be used, unless you did something like add:
> > @DataType("customdate") to every one of your date fields, or had a
> > service that changed the DataType for any bean models you create.
> > Yuck.
> > Now, you can override the built-in, and tapestry picks it up. Nice.
> >
> > Cheers,
> >
> > Robert
> >
> > >
> > >
> > > 4. Tapestry now supports "Index" pages at the root or in sub-folders.
> > >
> > > nice feature.
> > >
> > > 5. Tapestry pages may now be secured for access only via HTTPS.
> > >
> > > good feature.
> > >
> > > 6. Added the FormFragment component to allow for forms that are
> > > mutable on
> > > the client-side. In addition, the Form component may now update a
> > > Zone.
> > >
> > > good feature.
> > >
> > > a.c.
> > > --
> > > View this message in context:
> > http://www.nabble.com/t5%3A-new-features-in-5.0.11-tp16025541p16025541.html
> > > Sent from the Tapestry - User mailing list archive at Nabble.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
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
/ted
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: t5: new features in 5.0.11
Posted by Marcus <mv...@gmail.com>.
Hi,
@Property works for any class? or only for components and pages?
thanks,
Marcus
On 3/13/08, Robert Zeigler <ro...@scazdl.org> wrote:
>
> On Mar 13, 2008, at 3/139:07 AM , Angelo Chen wrote:
>
> >
> > Hi,
> >
> > As usual I always like to look at new features of every release,
> > here are
> > the one officially listed as new to the 5.0.11:
> >
> > 1. The @Cached annotation has been added to allowing the caching of
> > method
> > results.
> >
> > Can't understand this, any use case to explain this?
>
>
> .java:
>
> public List<DataType> getListOfDataType() {
> return someExpensiveMethodCall();
> }
>
> .tml:
>
> <t:if test="listOfDataType.size()">
> <t:loop source="listOfDataType">
> ...
> </t:loop>
> <t:parameter name="else">
> No data to display
> </t:parameter>
> </t:if>
>
> W/out @Cached, the above template results in someExpensiveMethodCall
> being called 2x per render. Would be nice to call it only once/render.
> So if you change .java to look like:
>
> @Cached
> public List<DataType> getListOfDataType() {
> return someExpensiveMethodCall();
> }
>
> Now someExpensiveMethodCall() will only occur once/render.
>
>
>
> >
> >
> > 2. Tapestry can now generate accessor methods for fields
> > automatically via
> > the @Property annotation.
> >
> > This is a cool feature, saving a lot of code.
> >
> > 3. It is now possible to override the built-in display and edit
> > blocks for
> > data types.
> >
> > What's this?
>
> Tapestry supplies a set of "defaults" for editing & viewing data types
> via BeanEditor, BeanEditForm, Grid, BeanDisplay, and so forth.
> Now you can override the defaults. As an example, due to licensing
> issues, T5 dropped the use of the dynarch calendar in favor of
> a simpler javascript calendar with compatible licensing. Suppose you
> really want to use dynarch's js calendar.
> Before this change, there was no way to supply your own calendar
> component in place of Tapestry's default, so even if you had this
> pretty jscalendar-based component,
> it wouldn't be used, unless you did something like add:
> @DataType("customdate") to every one of your date fields, or had a
> service that changed the DataType for any bean models you create.
> Yuck.
> Now, you can override the built-in, and tapestry picks it up. Nice.
>
> Cheers,
>
> Robert
>
> >
> >
> > 4. Tapestry now supports "Index" pages at the root or in sub-folders.
> >
> > nice feature.
> >
> > 5. Tapestry pages may now be secured for access only via HTTPS.
> >
> > good feature.
> >
> > 6. Added the FormFragment component to allow for forms that are
> > mutable on
> > the client-side. In addition, the Form component may now update a
> > Zone.
> >
> > good feature.
> >
> > a.c.
> > --
> > View this message in context:
> http://www.nabble.com/t5%3A-new-features-in-5.0.11-tp16025541p16025541.html
> > Sent from the Tapestry - User mailing list archive at Nabble.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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: t5: new features in 5.0.11
Posted by Robert Zeigler <ro...@scazdl.org>.
On Mar 13, 2008, at 3/139:07 AM , Angelo Chen wrote:
>
> Hi,
>
> As usual I always like to look at new features of every release,
> here are
> the one officially listed as new to the 5.0.11:
>
> 1. The @Cached annotation has been added to allowing the caching of
> method
> results.
>
> Can't understand this, any use case to explain this?
.java:
public List<DataType> getListOfDataType() {
return someExpensiveMethodCall();
}
.tml:
<t:if test="listOfDataType.size()">
<t:loop source="listOfDataType">
...
</t:loop>
<t:parameter name="else">
No data to display
</t:parameter>
</t:if>
W/out @Cached, the above template results in someExpensiveMethodCall
being called 2x per render. Would be nice to call it only once/render.
So if you change .java to look like:
@Cached
public List<DataType> getListOfDataType() {
return someExpensiveMethodCall();
}
Now someExpensiveMethodCall() will only occur once/render.
>
>
> 2. Tapestry can now generate accessor methods for fields
> automatically via
> the @Property annotation.
>
> This is a cool feature, saving a lot of code.
>
> 3. It is now possible to override the built-in display and edit
> blocks for
> data types.
>
> What's this?
Tapestry supplies a set of "defaults" for editing & viewing data types
via BeanEditor, BeanEditForm, Grid, BeanDisplay, and so forth.
Now you can override the defaults. As an example, due to licensing
issues, T5 dropped the use of the dynarch calendar in favor of
a simpler javascript calendar with compatible licensing. Suppose you
really want to use dynarch's js calendar.
Before this change, there was no way to supply your own calendar
component in place of Tapestry's default, so even if you had this
pretty jscalendar-based component,
it wouldn't be used, unless you did something like add:
@DataType("customdate") to every one of your date fields, or had a
service that changed the DataType for any bean models you create.
Yuck.
Now, you can override the built-in, and tapestry picks it up. Nice.
Cheers,
Robert
>
>
> 4. Tapestry now supports "Index" pages at the root or in sub-folders.
>
> nice feature.
>
> 5. Tapestry pages may now be secured for access only via HTTPS.
>
> good feature.
>
> 6. Added the FormFragment component to allow for forms that are
> mutable on
> the client-side. In addition, the Form component may now update a
> Zone.
>
> good feature.
>
> a.c.
> --
> View this message in context: http://www.nabble.com/t5%3A-new-features-in-5.0.11-tp16025541p16025541.html
> Sent from the Tapestry - User mailing list archive at Nabble.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: new features in 5.0.11
Posted by Jonathan Barker <jo...@gmail.com>.
The documentation also gives a way to define this by contributions (see the
Securing Multiple Pages section)
http://tapestry.formos.com/nightly/tapestry5/tapestry-core/guide/secure.html
> -----Original Message-----
> From: kranga [mailto:kranga@k2d2.org]
> Sent: Thursday, March 13, 2008 9:02 PM
> To: Tapestry users
> Subject: Re: new features in 5.0.11
>
> Defining secure access via HTTPS is a high level architectural decision.
> Seldom is one going to want to do that by annotation.
>
> ----- Original Message -----
> From: "Angelo Chen" <an...@yahoo.com.hk>
> To: <us...@tapestry.apache.org>
> Sent: Thursday, March 13, 2008 10:07 AM
> Subject: t5: new features in 5.0.11
>
>
> >
> > Hi,
> >
> > As usual I always like to look at new features of every release, here
> are
> > the one officially listed as new to the 5.0.11:
> >
> > 1. The @Cached annotation has been added to allowing the caching of
> method
> > results.
> >
> > Can't understand this, any use case to explain this?
> >
> > 2. Tapestry can now generate accessor methods for fields automatically
> via
> > the @Property annotation.
> >
> > This is a cool feature, saving a lot of code.
> >
> > 3. It is now possible to override the built-in display and edit blocks
> for
> > data types.
> >
> > What's this?
> >
> > 4. Tapestry now supports "Index" pages at the root or in sub-folders.
> >
> > nice feature.
> >
> > 5. Tapestry pages may now be secured for access only via HTTPS.
> >
> > good feature.
> >
> > 6. Added the FormFragment component to allow for forms that are mutable
> on
> > the client-side. In addition, the Form component may now update a Zone.
> >
> > good feature.
> >
> > a.c.
> > --
> > View this message in context:
> > http://www.nabble.com/t5%3A-new-features-in-5.0.11-
> tp16025541p16025541.html
> > Sent from the Tapestry - User mailing list archive at Nabble.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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: new features in 5.0.11
Posted by Kevin Menard <km...@servprise.com>.
It's been an oft requested feature over the years. In fact, I'd still love
to have T4 version.
While doable at a high-level, it's error prone. Rewrite rules or
declaritive security statements have to be written and every resource
accessed to test. Now, if Tapestry is already writing the URLs out for me
and I already know which resources I want protected, it makes a lot of sense
to define that in the class itself. Moreover, the guy deploying and the guy
developing are often different people and lack of communication using a
"high-level" approach can lead to big problems.
Also, please start new threads if you want to wrangle other issues. Jumping
to framework design issues and URL schemes really doesn't help the matter of
the Secure annotation at all.
--
Kevin
On 3/15/08 7:58 AM, "kranga" <kr...@k2d2.org> wrote:
> Funny - my experience has been the exact opposite.
>
> Building a general purpose framework on one's personal experience can have
> shortfalls. For example you state in your blog "I also think Tapestry's
> built-in rules for URLs are really strong and appealing; I simply don't see
> customizing the built-in rules to be a priority, or frankly, of any great
> value."
>
> I can tell you the URL scheme of Tapestry would not work at all for some of
> the apps I've built.
>
> ----- Original Message -----
> From: "Howard Lewis Ship" <hl...@gmail.com>
> To: "Tapestry users" <us...@tapestry.apache.org>
> Sent: Friday, March 14, 2008 2:38 AM
> Subject: Re: new features in 5.0.11
>
>
>> It's nice that you think that.
>>
>> The reality is that almost every application I've worked on or
>> consulted for had a subset of pages that needed to be protected via
>> HTTPS and the remainder could operate via HTTP.
>>
>> On Thu, Mar 13, 2008 at 6:01 PM, kranga <kr...@k2d2.org> wrote:
>>> Defining secure access via HTTPS is a high level architectural decision.
>>> Seldom is one going to want to do that by annotation.
>>>
>>> ----- Original Message -----
>>> From: "Angelo Chen" <an...@yahoo.com.hk>
>>> To: <us...@tapestry.apache.org>
>>> Sent: Thursday, March 13, 2008 10:07 AM
>>> Subject: t5: new features in 5.0.11
>>>
>>>
>>>>
>>>> Hi,
>>>>
>>>> As usual I always like to look at new features of every release, here
>>> are
>>>> the one officially listed as new to the 5.0.11:
>>>>
>>>> 1. The @Cached annotation has been added to allowing the caching of
>>> method
>>>> results.
>>>>
>>>> Can't understand this, any use case to explain this?
>>>>
>>>> 2. Tapestry can now generate accessor methods for fields automatically
>>> via
>>>> the @Property annotation.
>>>>
>>>> This is a cool feature, saving a lot of code.
>>>>
>>>> 3. It is now possible to override the built-in display and edit blocks
>>> for
>>>> data types.
>>>>
>>>> What's this?
>>>>
>>>> 4. Tapestry now supports "Index" pages at the root or in sub-folders.
>>>>
>>>> nice feature.
>>>>
>>>> 5. Tapestry pages may now be secured for access only via HTTPS.
>>>>
>>>> good feature.
>>>>
>>>> 6. Added the FormFragment component to allow for forms that are
>>> mutable on
>>>> the client-side. In addition, the Form component may now update a
>>> Zone.
>>>>
>>>> good feature.
>>>>
>>>> a.c.
>>>> --
>>>> View this message in context:
>>>>
>>> http://www.nabble.com/t5%3A-new-features-in-5.0.11-tp16025541p16025541.html
>>>> Sent from the Tapestry - User mailing list archive at Nabble.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
>>>
>>>
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator Apache Tapestry and Apache HiveMind
>>
>> ---------------------------------------------------------------------
>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: new features in 5.0.11
Posted by kranga <kr...@k2d2.org>.
Funny - my experience has been the exact opposite.
Building a general purpose framework on one's personal experience can have
shortfalls. For example you state in your blog "I also think Tapestry's
built-in rules for URLs are really strong and appealing; I simply don't see
customizing the built-in rules to be a priority, or frankly, of any great
value."
I can tell you the URL scheme of Tapestry would not work at all for some of
the apps I've built.
----- Original Message -----
From: "Howard Lewis Ship" <hl...@gmail.com>
To: "Tapestry users" <us...@tapestry.apache.org>
Sent: Friday, March 14, 2008 2:38 AM
Subject: Re: new features in 5.0.11
> It's nice that you think that.
>
> The reality is that almost every application I've worked on or
> consulted for had a subset of pages that needed to be protected via
> HTTPS and the remainder could operate via HTTP.
>
> On Thu, Mar 13, 2008 at 6:01 PM, kranga <kr...@k2d2.org> wrote:
>> Defining secure access via HTTPS is a high level architectural decision.
>> Seldom is one going to want to do that by annotation.
>>
>> ----- Original Message -----
>> From: "Angelo Chen" <an...@yahoo.com.hk>
>> To: <us...@tapestry.apache.org>
>> Sent: Thursday, March 13, 2008 10:07 AM
>> Subject: t5: new features in 5.0.11
>>
>>
>> >
>> > Hi,
>> >
>> > As usual I always like to look at new features of every release, here
>> are
>> > the one officially listed as new to the 5.0.11:
>> >
>> > 1. The @Cached annotation has been added to allowing the caching of
>> method
>> > results.
>> >
>> > Can't understand this, any use case to explain this?
>> >
>> > 2. Tapestry can now generate accessor methods for fields automatically
>> via
>> > the @Property annotation.
>> >
>> > This is a cool feature, saving a lot of code.
>> >
>> > 3. It is now possible to override the built-in display and edit blocks
>> for
>> > data types.
>> >
>> > What's this?
>> >
>> > 4. Tapestry now supports "Index" pages at the root or in sub-folders.
>> >
>> > nice feature.
>> >
>> > 5. Tapestry pages may now be secured for access only via HTTPS.
>> >
>> > good feature.
>> >
>> > 6. Added the FormFragment component to allow for forms that are
>> mutable on
>> > the client-side. In addition, the Form component may now update a
>> Zone.
>> >
>> > good feature.
>> >
>> > a.c.
>> > --
>> > View this message in context:
>> >
>> http://www.nabble.com/t5%3A-new-features-in-5.0.11-tp16025541p16025541.html
>> > Sent from the Tapestry - User mailing list archive at Nabble.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
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> 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: new features in 5.0.11
Posted by Howard Lewis Ship <hl...@gmail.com>.
It's nice that you think that.
The reality is that almost every application I've worked on or
consulted for had a subset of pages that needed to be protected via
HTTPS and the remainder could operate via HTTP.
On Thu, Mar 13, 2008 at 6:01 PM, kranga <kr...@k2d2.org> wrote:
> Defining secure access via HTTPS is a high level architectural decision.
> Seldom is one going to want to do that by annotation.
>
> ----- Original Message -----
> From: "Angelo Chen" <an...@yahoo.com.hk>
> To: <us...@tapestry.apache.org>
> Sent: Thursday, March 13, 2008 10:07 AM
> Subject: t5: new features in 5.0.11
>
>
> >
> > Hi,
> >
> > As usual I always like to look at new features of every release, here are
> > the one officially listed as new to the 5.0.11:
> >
> > 1. The @Cached annotation has been added to allowing the caching of method
> > results.
> >
> > Can't understand this, any use case to explain this?
> >
> > 2. Tapestry can now generate accessor methods for fields automatically via
> > the @Property annotation.
> >
> > This is a cool feature, saving a lot of code.
> >
> > 3. It is now possible to override the built-in display and edit blocks for
> > data types.
> >
> > What's this?
> >
> > 4. Tapestry now supports "Index" pages at the root or in sub-folders.
> >
> > nice feature.
> >
> > 5. Tapestry pages may now be secured for access only via HTTPS.
> >
> > good feature.
> >
> > 6. Added the FormFragment component to allow for forms that are mutable on
> > the client-side. In addition, the Form component may now update a Zone.
> >
> > good feature.
> >
> > a.c.
> > --
> > View this message in context:
> > http://www.nabble.com/t5%3A-new-features-in-5.0.11-tp16025541p16025541.html
> > Sent from the Tapestry - User mailing list archive at Nabble.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
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: new features in 5.0.11
Posted by kranga <kr...@k2d2.org>.
Defining secure access via HTTPS is a high level architectural decision.
Seldom is one going to want to do that by annotation.
----- Original Message -----
From: "Angelo Chen" <an...@yahoo.com.hk>
To: <us...@tapestry.apache.org>
Sent: Thursday, March 13, 2008 10:07 AM
Subject: t5: new features in 5.0.11
>
> Hi,
>
> As usual I always like to look at new features of every release, here are
> the one officially listed as new to the 5.0.11:
>
> 1. The @Cached annotation has been added to allowing the caching of method
> results.
>
> Can't understand this, any use case to explain this?
>
> 2. Tapestry can now generate accessor methods for fields automatically via
> the @Property annotation.
>
> This is a cool feature, saving a lot of code.
>
> 3. It is now possible to override the built-in display and edit blocks for
> data types.
>
> What's this?
>
> 4. Tapestry now supports "Index" pages at the root or in sub-folders.
>
> nice feature.
>
> 5. Tapestry pages may now be secured for access only via HTTPS.
>
> good feature.
>
> 6. Added the FormFragment component to allow for forms that are mutable on
> the client-side. In addition, the Form component may now update a Zone.
>
> good feature.
>
> a.c.
> --
> View this message in context:
> http://www.nabble.com/t5%3A-new-features-in-5.0.11-tp16025541p16025541.html
> Sent from the Tapestry - User mailing list archive at Nabble.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