Not me... It's from Patrick, Mike, and some other people.. I've been reviewing some of the chapters though.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2003 2:04 PM > To: [EMAIL PROTECTED] > Subject: RE: [OS-webwork] WebWork Getting Started Guide > > > <sarcasm>I can't imagine where that book would be coming > from.</sarcasm> :-D > > -----Original Message----- > From: Jason Carreira [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2003 11:57 AM > To: [EMAIL PROTECTED] > Subject: RE: [OS-webwork] WebWork Getting Started Guide > > Les, > > You should try not to access Hibernate stuff directly in your > action... Pull it out into separate services (Stores, DAO's, > whatever you want to call them) and make them implement > interfaces... Then you can mock the interfaces and use the > mocks instead... You can then know what to expect for calls > to the interface and return something your code can use. > > There is a need for this kind of info, but I happen to know > for a fact that a very good book that covers a lot of this > material and how it fits together is being written :-) > > Jason > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, June 24, 2003 11:10 AM > > To: [EMAIL PROTECTED] > > Subject: RE: [OS-webwork] WebWork Getting Started Guide > > > > > > I think that what you are suggesting is a better approach. > > Though, having not used mock before, I need to spend some > > time figuring it out > > -- especially figuring out how to make it transparent. In my > > case, I think this may be a challenge because I have > > Hibernate references in my actions. So, I have to fool > > hibernate into searching mock stuff and not a db. Hopefully, > > those guys have some examples of how to do that. > > > > Anyway, I still think this is a little difficult for a newbie > > to figure out. So, it may be worth either a small framework > > or at least a wiki entry to explain how to do it and give > > examples. Of course, that falls in line with the general need > > for docs...but you guys haven't heard that enough have you?? :) > > > > I'll let you know what I end up with. Maybe I'll write that > > wiki entry in all of my spare time. :) I appreciate the help. > > > > LES > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU > Hosting Partner. Refer Dedicated Servers. We Manage Them. You > Get 10% Monthly Commission! INetU Dedicated Managed Hosting > http://www.inetu.net/partner/index.php > > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU > Hosting Partner. Refer Dedicated Servers. We Manage Them. You > Get 10% Monthly Commission! INetU Dedicated Managed Hosting > http://www.inetu.net/partner/index.php > > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
