The MonkeyStruts example initiates everything in the constructor of the beans, and because they're in session memory, there's no issue with having to manage anything with regards to request scope and bean population. Result: nasty code in the constructors that shouldn't be duplicated in a real system. The code is found in the beans themselves.
The beans of a nested structure should be built and managed from actions like all other good Struts objects. All the beans in the nested structure shouldn't know how they're built, and are basic beans like all good form beans. Any business logic in the beans will make things messy very quick. The MonkeyStruts example is mainly geared to be an example of how easy and powerful the tags are, rather than a good example of bean management. In this respect the example needs a rework. This the info you're after?... Arron. > attention mr. aaron bates and for those who saw the StrutsMonkey example in > the keymonkey site, could you please help me out here....im tracing through > the source code of it but i cant see where the BananaBunch and BananaBean > were instantiated for them to be used in the jsp. as i understood, when the > form was populated, the monkeyteambean is been populated with the > monkeyworkers right? and then the connection of the beans stops there, but > where is the realizations of the bananabean and bananabunch? and in the jsp > there is a "pickedBunches" property, where did you get that? i find your > example very neat and very helpful in what im doing right now, so that's why > i have to understand it very well, thanks. > -- > Frances Aleah Z. De Guzman > SA/Programmer > Ingenium Technology, Inc. > http://www.ingenium.com.ph > > Disclaimer : > This message is intended only for the named recipient. If you are not the > intended recipient you are notified that disclosing, copying, distributing > or taking any action in reliance on the contents of this information is > strictly prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
