read the pdf intro and i'm still in the dark about what ozstruts actually does. I appreciate all of the problem spots you highlight in struts, but it's really not clear how your page-driven classes overcome them all.
For instance, you want to look up the action class. You have to go through the struts-config.xml anyway to get the class for the URL. What difference does ozstruts make there? That's just the first point. I see how there might be some interesting pattern implementations in the way the page classes communicate to mask 'transitions', but it's not clear at all how.
I don't mean to be negative - I am interested since I find the implementation of struts to be quite difficult to get right each time.
Rgds Adam
On 11/08/2004 12:05 AM Tak Yoshida wrote:
Hi,
I would like to introduce Page Driven development, OzStruts, to all Struts developers, which makes Struts application more clean and maintainable.
I guess most of Struts developers are having same issues I had, so please take a look at my two cent idea. Any productive suggestion and critices would be really appreciated.
Documentations are available at http://sourceforge.net/project/showfiles.php?group_id=111296&package_id=120334&release_id=280886
OzStruts 1.0 is available at http://sourceforge.net/project/showfiles.php?group_id=111296&package_id=128965&release_id=280994
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
