A few thoughts: (1) The push/pull dichotomy really does not apply to what you are talking about. That relationship is between the client and the server and has more to do with the nature of the protocol, viz. HTTP, being employed in a browser context.
(2) Likewise, some of the other things you say seem to not track the semantics of the actual problem space. For example, JSPs never "capture data" but are used to create dynamic HTML in the response. The data always comes from the request object which only indirectly is related to the prior JSP page and the form elements available on that page. We could always put together a request object without any JSP at all and scoot it off to the server. Hackers, of course, do just that. (3) A JSP page "fronted" by a simple ActionForward cannot be populated unless you have something put the populating bean in some scope. Presumably that activity has to somehow be explained. Why you do not what to use an ActionForm or this is not clear. I do many things, of course, without the ActionForm participating, but the Action or the ActionForm must be doing something. A simple ActionForward cannot give you a bean with the data you need. Something is wrong with this description. I would guess that you have some Action put the bean into scope. This has nothing to do with "pull" as that term is normally used in the "push/pull" discussions outside Dr. Dolittle's push-pull llama. (4) When you say there is no "custom" action to populate the bean but that it is "pulled" from the page, I can only think that you mean you have the code that should be in the model on the JSP page. If so, this is not "pull" and is not a good idea. Is that right? If not, then I don't know where the so-called "pull data" is coming from. -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
