W. Ambler and Tyler
> Jewell.
> I have been reading this book, it is a good book for beginners.
>
> Sridhar
>
> -Original Message-
> From: PC Leung [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 21, 2004 7:04 AM
> To: Struts Users Mailing List
> Subject: Re
Subject: Re: Where to put the business logics?
Lots of people support the use of EJB.
I have not touched EJB before.
I have a book about EJB which is quite difficult.
I am afraid of being too old to learn.
Any other simpler methods for oldies (nearly 41
[EMAIL PROTECTED] wrote the following on 9/21/2004 11:51 AM:
Take a look at the Spring framework - it helps use POJO's rather than EJB's
I think everyone is making this more difficult than it needs to be. I
think as start just have your actions call some delegate or service
class or whatever the
rs Mailing List" <[EMAIL PROTECTED]>
|
| cc:
|
| S
gt;
09/21/2004 10:38 AM
Please respond to
"Struts Users Mailing List" <[EMAIL PROTECTED]>
To
Struts Users Mailing List
<[EMAIL PROTECTED]>
cc
Subject
Re: Where to put the business
logics?
Any suggested POJO web sites so that I can have a
glance?
I don't agree :
- My app will NEVER be anything else than a webapp
- We are 3 developpers working both on business and web
BUT we defined a business API using interfaces for business logic
Using this, we can change business tier for a mock one for application demo or testing
cases that may be d
Any suggested POJO web sites so that I can have a glance?
- Original Message -
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tue, 21 Sep 2004 10:12:16 -0400
Subject: Re: Where to put the business logics?
To: Struts Users Mailing List <[EMAIL PROTECTED]>
Depending on y
ggetto: Re: Where to put the business logics?
What is POJO anyway? Why differs from other J2EE technologies? Is it
requires AS?
--
Regards,
M. Onur Tokan
On Tue, 21 Sep 2004 10:18:38 -0400 (EDT), Frank W. Zammetti (MLists)
<[EMAIL PROTECTED]> wrote:
> Thanks for defining POJO Dennis! I&#x
I strongly agree with you of decoupling business logic and action class.
If ejb is the right way, any easy tutorial online?
On Tue, 21 Sep 2004 07:23:32 -0700, Michael McGrady
<[EMAIL PROTECTED]> wrote:
>
>
> PC Leung wrote:
>
> >In the mailing list, I have read some people suggesting not to p
That's a good point...
If you KNOW your application is NEVER going to be anything other than a
web-based application, and if you KNOW you won't need to re-use your
business logic (or expose it in any way outside the application), and if
your development team is not really separated (especially if
d in Rod Johnsons
> > "Expert J2EE w/o EJB" book:
> > http://www.bookpool.com/.x/7dybtc9v34/sm/0764558315
> >
> > Dennis
> >
> >
> >
> >
> > PC Leung <[EMAIL PROTECTED]>
> > 09/21/2004 10:03 AM
> > Please respond to
PC Leung wrote:
In the mailing list, I have read some people suggesting not to put
business logics in Action class. Certainly, business logics should not
be in JSP or Form class. Then where should the business logics be put?
Thanks
A good answer to this question is impossible to give, PC, without
ECTED]>
>
>
> To
> Struts Users Mailing List <[EMAIL PROTECTED]>
> cc
>
> Subject
> Re: Where to put the business logics?
>
>
>
>
>
>
> Lots of people support the use of EJB.
> I have not touched E
21/2004 10:03 AM
Please respond to
"Struts Users Mailing List" <[EMAIL PROTECTED]>
To
Struts Users Mailing List
<[EMAIL PROTECTED]>
cc
Subject
Re: Where to put the business
logics?
Lots of people support the use of EJB.
I have not touched EJB before.
I have a b
Lots of people support the use of EJB.
I have not touched EJB before.
I have a book about EJB which is quite difficult.
I am afraid of being too old to learn.
Any other simpler methods for oldies (nearly 41)?
-
To unsubscribe, e-
One thing to be careful of, a mistake I've seen made often, is a clean
separation of the business delegates and the Actions... When calling on
your delegates, be sure NOT to pass anything that is web-specific like
session or request objects. This will make changing business classes a
lot easier an
A common practice is to use the J2EE design pattern "Business Delegate",
that provides a clean separation between the technology used to store data
and all the rest of the application.
The Business Delegate will expose some "APIs", but it does not show how it
is really implemented (JDBC, EJB,etc.)
I think accessing(reading data) one or more table using join is very
difficult using EJB's. I prefer JDBC (sometimes using PL/SQL for
oracle databases) for reading from datasources and CMP Entity Object's
for writing to the database.
Sincerly Onur
On Tue, 21 Sep 2004 17:49:09 +0800, PC Leung <[EM
In model !
Struts is a MVC framework without any 'M' support : you can use anything you want to
build your model.
> In the mailing list, I have read some people suggesting not to put
> business logics in Action class. Certainly, business logics should not
> be in JSP or Form class. Then where
hi,
Action classes must be delegates to the actual business logic. Make
business logic available in a different layer (say helper classes) and let
the action class to invoke the actual business logic.
Jitender Kumar C.V.
In the mailing list, I have read some people suggesting not to put
business logics in Action class. Certainly, business logics should not
be in JSP or Form class. Then where should the business logics be put?
Thanks
-
To unsubscr
21 matches
Mail list logo
