Re: Regarding a design issue - in Java



Ravi,

Its very hard to get from your post (i.e. very less information and may
be big project), but

User is part of the common framework, but customer belongs to the customer
module. Hence currently the framework is having dependency on the customer
module, which we do not want. And also, the customer may vary from country

What I GUESS is, User-part is tightly coupled with Common framework and
hence to perform any operation on Custormer you need to take help of
USER.

customer---->user & relatedfunction/API/Interfaces ----> Framework
(log+user+WF)


Even, you may find your user-module(which is tightly-coupled with other
element,workflow,logging etc..) is working fine, can your design able
to scale-it up, ?

if yes then there are great many chances that you can use simillar
design for the customer also,

if no then your design may tightly coupled with user module, one of the
way is too decouple user from other stuff i.e. logging etc, which
belongs to common framework,


Hence currently the framework is having dependency on the customer module, which we do not want.

Think reverse, or define specification of what should be common
interface/syntax/xml- part etc for the stuff that WANT TO USE
FRAMEWORK, apply that to customer (as well user, as well any future new
stuff that want to use framework)


For dependency
segregation, we can use interfaces, but then the interfaces need to be in
the common classpath, which again we dont want.

Interfaces are rarely changes, and this may not be the problem.


Not sure, whether I am doing the right option, but because I went through
JMX Microkernal architecture of JBoss, I would like to suggest the following
idea. Let customer be a managed service, which will be started when a
customer is created. Let common framework be a kernal, and let common
framework add/wrap the customer service when needed through JMX. In this
way, the customer service can vary anytime anywhere.

During you perform any operation on customer (with or without JMX )
would it internally call/invoke/use USER related stuff ?


Please note this is just a GUESS based on your description, but may
help to you.


--
Raxit Sheth

.



Relevant Pages

  • With Respect To an Investment Application
    ... All these modules are resting on a common ... framework, which does routing, workflow, logging etc. ... country to country. ... There are two main domain objects, User and Customer. ...
    (comp.lang.java.programmer)
  • Re: There is no .NET in Vista Code?
    ... a prospective customer off giving your application a fair look. ... ..NET application to a /specific/ framework version ... application can break yours when your app ... the safety net of guaranteed backwards compatibility. ...
    (borland.public.delphi.non-technical)
  • Re: Is Open Source viable for very small teams or individual developers?
    ... customer specific customization. ... selling books (documentatation) ... and keeping layers on top of it closed.. ... Related to this is open-sourcing a framework and selling applications ...
    (comp.lang.misc)
  • Re: Is Open Source viable for very small teams or individual developers?
    ... customer specific customization. ... selling books (documentatation) ... support and integration services. ... Related to this is open-sourcing a framework and selling applications ...
    (comp.lang.misc)
  • Regarding a design issue - in Java
    ... I have posted the same query to comp.lang.java, but kindly dont consider ... country to country. ... There are two main domain objects, User and Customer. ... User is part of the common framework, but customer belongs to the customer ...
    (comp.object)