The problem is described in this one of Bogdan's mails:
http://argouml.tigris.org/servlets/ReadMsg?list=dev&msgNo=20834
It is about why quirks ArgoEclipse has done to work. By solving it as I
suggest, this will no longer be a quirk but a requirement from the Model
subsystem to be initialized with an implementation.
/Linus
> -----Original Message-----
> From: Bob Tarling [mailto:[EMAIL PROTECTED]
> Sent: den 30 april 2007 17:45
> To: [email protected]
> Subject: Re: [argouml-dev] Detangling MDR from the model subsystem
>
> Could you explain the problem your trying to solve here.
>
> It seems like you're suggesting the MDR knowledge move out of the
> model subsystem. That seems wrong to me.
>
> Bob.
>
> On 29/04/07, Linus Tolke <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > Hello all!
> >
> >
> >
> > I have a memory of someone thinking it would be a good idea not to
have
> the
> > MDR instantiated by default from the Model subsystem. I think I have
now
> > understood how to solve this and the solution is not as complicated
as I
> > thought. I have identified the following changes:
> >
> > * MDR to be instantiated in the application subsystem (probably
> > org.argouml.application.Main) and fed to the Model subsystem.
> >
> > * As a consequence of this, the ArgoEclipse application will also
have
> to
> > instantiate it.
> >
> > * All test cases that actually use the model will have to
instantiate it
> > (except those using the mock model).
> >
> > * For extra credit, we could throw a special NotInitializedError
when
> any of
> > the access methods are called without the Model subsystem being
> initialized
> > properly. For the time being they will most likely throw an
> > NullPointerException.
> >
> >
> >
> > Have I missed something important that will complicate this later?
Is
> this
> > worth doing now?
> >
> >
> >
> > /Linus
> >
> >
> >
> > ************************************************
> >
> > Linus Tolke
> >
> > [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
> >
> > ArgoUML
> >
> > ************************************************
> >
> >
>
> ---------------------------------------------------------------------
> 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]
