Re: Business Logic Javabeans

Subject: Re: Business Logic Javabeans From: David Bolsover [EMAIL PROTECTED] === Ric Your proposals for saeparate classes to represent User and Database are very close to the generally accepted way of doing things in struts. To expand - In this situation, I would use classes like

RE: Business Logic Javabeans

The bean on the GUI has to follow naming conventions, but thats not the bean used to perform the business logic. For that bean means only an own java class to seperate the business logic from the gui(action,jsp). Partially you can prepare your data in the action classes, but the normal business

RE: Business Logic Javabeans

Sorry what i forgot to say, the business logic i meant is mainly checking database, adding database entries and so on, not changing the values or building a value object. This should be done in the action -Original Message- From: Ric Searle [mailto:[EMAIL PROTECTED]] Sent: Thursday,

Re: Business Logic Javabeans

for a good tutorial on javabeans visit the site www.pdf.coreservlets.com this is a book available on-line in pdf format and the chapter on javabeans (chapter no -13) is really good ( does not talk in gui context ), i hope this helps you and think that for a start on javabeans is really good.

RE: Business Logic Javabeans

While I agree that all this work should be done during the action, the code that implements your business logic shouldn't be directly in the perform method of the action object. It should be in other objects that you call. This provides for re-use of the business logic and seperation

RE: Business Logic Javabeans

I think this depends on the set-up that you have. the pattern you are referring to is business-delegate and that is exactly what it does -- delegates. the book ejb design patterns talks about the pros and cons. for us -- it doesn't make a lot of sense. Sandeep --- Jay sissom [EMAIL PROTECTED]