Hi!
Manie Coetzee wrote:
> A made the abstraction of having a data layer, business layer
> and a environment layer in object level. Basically the business
> object is a pure java class with no dependencies other than a VM.
> This functionality can be tested on each own with a unit test.
> This object can then be wrapped up by a servlet, EJB or
> Jini wrapper. The wrapper will just extend the business
> object, inheriting all the business methods. The wrapper
> itself then add all the functionality in order for this
> object to exists in whatever environment. The data that
> the object accesses, is also abstracted into a data access
> object (DAO). At the end of the day you end up with a mini
> three tier architecture where you have your DAO, Business object
> and environment wrapper. Each of these will have a unit test.
>
> In this way your business logic is nicely abstracted and environment
> independent.
>
> Your thoughts on this?
Well, it sounds tricky to get this right without doing some serious
mindbending, but if you got it going, then that's good! :-)
What I'm mostly worried about is the semantics of using, for example, a
transactional bean in a non-transactional setting such as a servlet. It
sounds like you can easily get false security. But as above, if you are
aware of this and have it functioning properly in all contexts, then I
guess it's ok.
regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
