This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi When it is possible to access pakage level variables in the same package by other classes, then why do servlets communicate via query strings, session variables, hidden fields etc. Why don't we make a class containing required variables, give it package level accessibility and set & use their values in servlets where-ever required? Regards Anu
Keep in mind that the main problem with servlets is managing user data so it doesn't get mixed up with other "simultaneous" users. The very elegant servlet API uses sessions for this. It is indeed a good idea to create a class to hold user specific variables. This can be shared between servlets by the session mechanism or whatever you like. Bill
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com