Win a copy of Modern JavaScript for the Impatient this week in the Server-Side JavaScript and NodeJS forum!
  • 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

serialization is affecting performance !!

Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We have MVC archittecute based application. typically we are using JSP for front end and Servlets and EJB for controller and modelling etc. I have a regrtation module that spans acroos three jsp pages ( we have next button for navigation). Application is registered in 3 steps,
1st page takes individual info, press next
2nd page takes address info , press next
and in 3rd page entitre application is submitted.
Now the problem is that in each apge all the information
is being serilaized and and thats taking long time when next button is pressed to go to next page, someone suggested that a singleton class can be used as a pseudo stateful session bean.
But I am not sure how we can do that ?
Please give me your opinions.
Ranch Hand
Posts: 111
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sorry for posting a reply so late !
I would suggest you to use some J2EE patterns (marketing word to say : "Patterns applied to J2EE" ).
Basically this problem is a recurring one & the best practice say that you usually should create a Session Facade (either as a Session Bean or an Entity Bean, but quiet often as a SessionBean).
Any way quickly said this would reduce the Chattiness of the Application & bring on the Server a "Controler" (MVC). I would suggest you to give a deep look at Bill Venners' site or read the following book : Core J2EE Patterns - Best practice & Design Strategies, by Deepak ALUR, John CRUPI, Dan MALKS, publ. @ PRENTICE HALL (ISBN : 0-13-064884-1).
Anyway as EJB is build upon RMI I would also suggest you to look at "Tips & tricks" to improve RMI performance. Without going into details you may create a few ValueObject & ValueObject Assembler and provide an implementation of the readObject (), writeObject ().
[ April 20, 2002: Message edited by: Thomas SMETS ]
Sometimes you feel like a nut. Sometimes you feel like a tiny ad.
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic