Re: upgrade from 20060427 snapshot to shale 1.0.3

Sorry, one more thing to add, prerender doesn't seem to be called for session beans. Costa Basil [EMAIL PROTECTED] wrote: Hi: Today I made the attempt to upgrade from the 27-apr-2006 snapshot to 1.0.3. Unfortunately I am having some problems that maybe someone can shed some light on. I use

Remoting and other app security concerns - shale 1.0.3

Today, I added some code for calling bean methods from ajax via shale remoting and to my wonder I discovered the mechanisms for executing bean calls are enabled by default. I don't think this is right. I think they should be disabled by default, and they should be enabled once the

s:token usability question

Hi, I am trying to use s:token and I have the following scenario where I think token doesn't behave as I expect (I accept I might be wrong). In a few words the token value is not refreshed as I expected. I use shale 1.0.3, myfaces 1.1.5. The org.apache.shale.component.Token class is the same

Re: s:token usability question

Hi, Lionel: Thank you for your reply. I think I am going to create my own token tag and I will extend the shale Token class to remove the attribute if the token validation passes in order to force the token to generate a new value when it gets rendered. This way I don't have to remember to

JSF 1.2 (MyFaces Core 1.2.x - implementation) Struts Shale

I've been successfully using Struts Shale 1.0.3 with MyFaces 1.1.x Tomhawk 1.1.x. Now I want to upgrade to MyFaces Core 1.2.x which is a JSF 1.2 implementation. Can someone please tell me if JSF 1.2 makes some of features in Struts Shale Core obsolete - for instance the ViewController

Re: JSF 1.2 (MyFaces Core 1.2.x - implementation) Struts Shale

I'm using JSF 1.2 Mojarra implementation w/ Shale just fine, but I unfortunately can't speak to MyFaces compatibility. That is good to know. Thanks __ Looking for the perfect gift? Give the gift of Flickr!