If this document object is large, saving it in the session, or back to temporary database tables might be your best option.
We're doing a lot of similar things to this right now with our apps. We create an object on the first page, and then make modifications (usually adding relationships and other objects) to it as we move along. This, in turn, can make the amount we store in session really large, but currently, we only have a very small concurrent user base, so its ok. On Thu, 17 Feb 2005 20:43:48 -0600, Mark <[EMAIL PROTECTED]> wrote: > Sean Schofield wrote: > > >It sounds like you need to share information between two beans. Is > >that correct? If so, there are better ways to this than using the > >request. What is the nature of the information you are trying to > >share and is this the case? > > > >sean > > > > > > > > > Yes, actually more than two beans. The application is a way for users > to import a document into our document management system. (Documentum) > without having an account on the system. They basically provide > metadata for the document (title, subject, etc) and then supply the > file, review their submission and then import into Documentum or save > it (database) to import at a later time. When the user logs in they > will have the option to start a new document or edit one of the ones > they haven't finished yet. Either way the process is similar, the only > difference is that if they choose edit we start the process with an > already existing Document object (from database) otherwise we create > one. The general idea is to pass this document object along from bean > to bean updating it and putting it back in to the request until they are > ready to import or save it for later. This has proved harder than I > originally though it would be. > > Thanks, > -Mark > > -- -Heath Borders-Wing [EMAIL PROTECTED]
