On Fri, 2005-05-27 at 16:00 -0400, David Whipple wrote:
> This is an off topic post, but there seem to be a lot of people with good
> opinions here.
> 
> I am trying to provide a framework (based on Stuts and Spring) for our
> company
> to use.  I'd like to make a reinforcement of the business layer in
> applications.
> 
> We do not use EJBs, so a lot of the patterns that are out there do not seem
> to
> apply.  I have not been able to find any references I like.
> 
> The goal is to encourage better program design and development by
> having a clear definition of what are the business objects in the program.
> 
> We want to come up with a way through patterns to help programmers avoid
> poor
> programming practices.  Clear separation into layers is one basic idea
> behind
> this.  We want to come up with some interface to the business layer which
> will
> force programmers to know what are to be the business objects in their
> architecture.
> 
> Does anyone have any ideas and/or know of any references for this?
> 
> Thanks,
> Dave
> 
Greetings:

We use Chain of Responsibility (CoR) implemented by commons-chain and
its Agility to construct a Request/Response framework to connect a
request to its designated service, whether the designated service is in
a web-application service container, a portlet container, auth for
authentication/authorization, or a Jcr container. At the business layer,
the designated service may use other services in other containers. e.g.
the personalization of auth container uses UserDaoImpl of DAO container.

We use Spring IoC to assemble chain Catalogs and their commands. Hence
the request/response framework is based on CoR/IoC integrated with your
presentation engine at the front. We use Jsf+Tiles as our presentation
engine.

The good thing is that available infrastructure takes care of detailed
connections while isolating the dependencies of itemized services within
1 container and among containers. Developers just need to plug in the
required specified functionality based on design contract.

We integrate the Request/Response with workflow using Shale Dialog and
Spring WebFlow to produce Request/Response/Workflow Business Application
Framework.

More detailed discussion is in the following link, which will be updated
by 2nd week of June after the release of RedHat Fedora 4.

http://www.dbgroups.com/docs/architecture.html#BusinessApplicationsFramework


Hope this may help.

BaTien
DBGROUPS

> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to