• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Server-side state saving ,JSF 1.1.1

Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
in my web.xml the.STATE_SAVING_METHOD setting is server





for measurement of application security isn't not allow to change this parameter to client , so the problem when I access for application and I open a new page via linker for print for example and I would access for my initial page to make change or modify my initial page it s no possible to make any modification because I have a empty bean , but if the state saving is a client I haven't a problem because a tree map is stored in client browser, so my version of JSF is 1.1.1 ,

So can you explain the cause for this problem and what's the solution?
Saloon Keeper
Posts: 22483
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to the JavaRanch, Bej!

You really should consider upgrading to JSF version 2. It has been a long time since JSF1 was in production. It usually doesn't take that much effort and it will cost less than making a more radical conversion when there's no longer anyone who can help with JSF1 and JSF2 itself becomes obsolete.

I am afraid that I don't understand your question. It sounds like the app is attempting to meddle with the internal JSF data structures and that's almost always a bad idea. JSF was designed to hide the platform-specifics stuff (which tends to break between releases) and let the developer work with POJOs.

Whether your state is kept in the client or in the server should have zero effect on the application logic behavior. Yes, server-side information is more secure and you don't have as much overhead passing state back and forth between client and server, but functionally that's invisible to the application code. Or should be.
Get off me! Here, read this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic