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 mechanism? Will Struts Shale work with MyFaces 1.2 seamlessly? My code is relying heavily on the shale framework (core) - all my managed beans extend the AbstractViewController class and rely on the ViewController calls made by the framework to prerender, init co. I am also using some of the validation tags. I didn't dig up the JSF 1.2 documentation but I think I read somewhere that JSF 1.2 offers something similar to the ViewController mechanism. Thanks __ Connect with friends from any web browser - no download required. Try the new Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php
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! http://www.flickr.com/gift/
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 reset the token. Costa - All new Yahoo! Mail - Get news delivered. Enjoy RSS feeds right on your Mail page.
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 in shale 1.0.3 and 1.0.4 (except comments). The page that I have contains a table and a link for deleting the rows from the table. I select a row by clicking on it then I click on the delete link to delete the row. All these actions are posts to the same page. Selecting a row is an immediate event and it bypasses any validation (in the action listener method I call getFacesContext().renderResponse() to bypass any validation). The delete link has immediate set to false. The problem is that after I delete one row, the value of the token is not refreshed, and I cannot delete any other row! I would have thought that after the validation is passed the token value should be refreshed but that is not the case. The token value is saved in the component attributes map and the attributes map is saved and restored to/from the state, and then used in Token.getToken(). One could trigger the refresh by removing the TOKEN_ATTRIBUTE_KEY attribute but I think it is a hack. Any thoughts? Thanks - All new Yahoo! Mail - Get news delivered. Enjoy RSS feeds right on your Mail page.
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 configuration settings are added to the web.xml. When I added shale core and shale remoting to my project I didn't have time to read the remoting documentation (I didn't have to use it at that time) and I didn't think shale would provide ways to poke server code by default. Is there anything else that I should be aware of? Anyway, I want to enable access only to one bean. I used the DYNAMIC_RESOURCES_INCLUDES directive, but this doesn't make any difference. I didn't understand from the documentation how shale processes the DYNAMIC_RESOURCES_INCLUDES and DYNAMIC_RESOURCES_EXCLUDES parameters and I didn't have time to read the code. Can someone explain this? The other way would be to use the default web app security settings. Thanks - Make free worldwide PC-to-PC calls. Try the new Yahoo! Canada Messenger with Voice
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 backing beans for each page and my backing beans extend AbstractViewController. The backing beans are declared in the config files using the convention: $ , for instance: test$testPage -TestPageBackingBean where I access the testPage through http://localhost:7001/myapp/faces/test/testPage.jsp Now, the problem that I have is that the prerender method of the backing bean is not called, and it was called before when I used the snapshot. Can someone tell me what I am doing wrong? Thx - The best gets better. See why everyone is raving about the All-new Yahoo! Mail. - Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail
