Hi Friends,

What is the recommended way to create classes for business logic, that
gets shared between multiple Actions?

Typically, in J2EE parlance, we create session beans (EJB's) for
this...or may be a simple layer of business logic, like
UserAppService, ListingsAppService etc...with static methods...

We can create a method in the model layer as well...but model layer
code is very tightly coupled with database...in the sense, there is a
class for every table...but the business logic code could fetch and
update data from several different tables...so wouldn't be prudent to
use any single Peer class, right?

May be we can create some class in lib/ folder...?

What do you guys do in such a case? I didn't find this in the
documentation...

I am using Symfony 1.0 by the way...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to