Thanks for the info.
I'd like to hear what we should do in the long run whit @Retain? Is it
recommended to initialize everything again and again and never use @Retain
anymore? When the page pool is dropped is the @Retain dropped also?
- Ville
Robert Zeigler wrote:
>
>
> On Aug 17, 2010, at 8/1711:22 PM , 9902468 wrote:
>
>>
>> Hi,
>>
>> First of all our software seems, if possible, even more snappier when run
>> with 5.2, so thank you everyone how have contributed.
>>
>> Now let's get to issues I encountered:
>>
>> 1. Asset protection: The documentation is not yet there, as it still
>> speaks
>> about AssetPathAuthorizer. How should I fix the app now? I have my assets
>> all around the final jar, and the only solution I found was to add
>>
>> public static void
>> contributeClasspathAssetAliasManager(MappedConfiguration<String,String>
>> configuration) {
>> configuration.add("orientT5", "com/orient/framework");
>> }
>>
>> which means everything. (Classes and tml are all in
>> com.orient.framework.something, javascript is at com.orient.framework.js
>> etc.) Are my assets now secured?
>>
>
> I haven't looked closely at the new security system, so I can't speak to
> the security of your assets, but if you liked the AssetProtection
> framework, it's still available as a 3rd-party library (which is what it
> was originally):
> http://maven.saiwai-solutions.com/com/saiwai-solutions/AssetProtectionDispatcher/1.0.0/AssetProtectionDispatcher-1.0.0.jar
> Yes, maven.saiwai-solutions.com is a proper maven repo, so you can add it
> to your repo and fetch via maven, as well.
> I still use it for my projects (call me paranoid, but I like explicit
> control over what is accessible ;).
>
>> 2. contributeTranslatorSource methods broke as the configuration has
>> changed
>> from list to mapped. Not mentioned in the nightly docs upgrade notes.
>>
>
> Good catch.
>
>> 3. The @Retain annotation is deprecated, with a text saying that it is
>> likely to cause threading issues with 5.2!! Not mentioned in the nightly
>> docs upgrade notes. I have over 200 hits of these deprecation messages in
>> the first client I tried. Mostly properties that hold beanmodels, but not
>> all. Do I have to evaluate these one by one, or do I have to remove all
>> of
>> them and change the way the properties are constructed? (Now using 5.1
>> recommended way to use static construction, copied away from the tapestry
>> home page...) What is the recommended upgrade practise on this one?
>>
>
> This changed as a result of tossing out the page pool.
> If you're in a hurry... ;) You can tell tapestry to continue using the
> page pool (for now).
> That would at least let you continue working on your project and gradually
> evaluate the individual uses of @Retain.
>
>> Number 3 will mean a LOT of work and testing for us os any info on that
>> one
>> would be nice. It makes things even worse that this will only be an issue
>> in
>> the production, as the developer machines are not likely to see this
>> (load
>> testing, I know...).
>>
>> - Ville
>> --
>> View this message in context:
>> http://tapestry.1045711.n5.nabble.com/T5-2-Upgrade-issues-tp2638940p2638940.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
>
On Aug 17, 2010, at 8/1711:22 PM , 9902468 wrote:
>
> Hi,
>
> First of all our software seems, if possible, even more snappier when run
> with 5.2, so thank you everyone how have contributed.
>
> Now let's get to issues I encountered:
>
> 1. Asset protection: The documentation is not yet there, as it still
> speaks
> about AssetPathAuthorizer. How should I fix the app now? I have my assets
> all around the final jar, and the only solution I found was to add
>
> public static void
> contributeClasspathAssetAliasManager(MappedConfiguration<String,String>
> configuration) {
> configuration.add("orientT5", "com/orient/framework");
> }
>
> which means everything. (Classes and tml are all in
> com.orient.framework.something, javascript is at com.orient.framework.js
> etc.) Are my assets now secured?
>
I haven't looked closely at the new security system, so I can't speak to the
security of your assets, but if you liked the AssetProtection framework,
it's still available as a 3rd-party library (which is what it was
originally):
http://maven.saiwai-solutions.com/com/saiwai-solutions/AssetProtectionDispatcher/1.0.0/AssetProtectionDispatcher-1.0.0.jar
Yes, maven.saiwai-solutions.com is a proper maven repo, so you can add it to
your repo and fetch via maven, as well.
I still use it for my projects (call me paranoid, but I like explicit
control over what is accessible ;).
> 2. contributeTranslatorSource methods broke as the configuration has
> changed
> from list to mapped. Not mentioned in the nightly docs upgrade notes.
>
Good catch.
> 3. The @Retain annotation is deprecated, with a text saying that it is
> likely to cause threading issues with 5.2!! Not mentioned in the nightly
> docs upgrade notes. I have over 200 hits of these deprecation messages in
> the first client I tried. Mostly properties that hold beanmodels, but not
> all. Do I have to evaluate these one by one, or do I have to remove all of
> them and change the way the properties are constructed? (Now using 5.1
> recommended way to use static construction, copied away from the tapestry
> home page...) What is the recommended upgrade practise on this one?
>
This changed as a result of tossing out the page pool.
If you're in a hurry... ;) You can tell tapestry to continue using the page
pool (for now).
That would at least let you continue working on your project and gradually
evaluate the individual uses of @Retain.
> Number 3 will mean a LOT of work and testing for us os any info on that
> one
> would be nice. It makes things even worse that this will only be an issue
> in
> the production, as the developer machines are not likely to see this (load
> testing, I know...).
>
> - Ville
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/T5-2-Upgrade-issues-tp2638940p2638940.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
On Aug 17, 2010, at 8/1711:22 PM , 9902468 wrote:
>
> Hi,
>
> First of all our software seems, if possible, even more snappier when run
> with 5.2, so thank you everyone how have contributed.
>
> Now let's get to issues I encountered:
>
> 1. Asset protection: The documentation is not yet there, as it still
> speaks
> about AssetPathAuthorizer. How should I fix the app now? I have my assets
> all around the final jar, and the only solution I found was to add
>
> public static void
> contributeClasspathAssetAliasManager(MappedConfiguration<String,String>
> configuration) {
> configuration.add("orientT5", "com/orient/framework");
> }
>
> which means everything. (Classes and tml are all in
> com.orient.framework.something, javascript is at com.orient.framework.js
> etc.) Are my assets now secured?
>
I haven't looked closely at the new security system, so I can't speak to the
security of your assets, but if you liked the AssetProtection framework,
it's still available as a 3rd-party library (which is what it was
originally):
http://maven.saiwai-solutions.com/com/saiwai-solutions/AssetProtectionDispatcher/1.0.0/AssetProtectionDispatcher-1.0.0.jar
Yes, maven.saiwai-solutions.com is a proper maven repo, so you can add it to
your repo and fetch via maven, as well.
I still use it for my projects (call me paranoid, but I like explicit
control over what is accessible ;).
> 2. contributeTranslatorSource methods broke as the configuration has
> changed
> from list to mapped. Not mentioned in the nightly docs upgrade notes.
>
Good catch.
> 3. The @Retain annotation is deprecated, with a text saying that it is
> likely to cause threading issues with 5.2!! Not mentioned in the nightly
> docs upgrade notes. I have over 200 hits of these deprecation messages in
> the first client I tried. Mostly properties that hold beanmodels, but not
> all. Do I have to evaluate these one by one, or do I have to remove all of
> them and change the way the properties are constructed? (Now using 5.1
> recommended way to use static construction, copied away from the tapestry
> home page...) What is the recommended upgrade practise on this one?
>
This changed as a result of tossing out the page pool.
If you're in a hurry... ;) You can tell tapestry to continue using the page
pool (for now).
That would at least let you continue working on your project and gradually
evaluate the individual uses of @Retain.
> Number 3 will mean a LOT of work and testing for us os any info on that
> one
> would be nice. It makes things even worse that this will only be an issue
> in
> the production, as the developer machines are not likely to see this (load
> testing, I know...).
>
> - Ville
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/T5-2-Upgrade-issues-tp2638940p2638940.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-2-Upgrade-issues-tp2638940p2638953.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
