Quoting my magic 8 ball-- "Signs point to yes."
If your Model "knows" your View, model-view separation is violated.
If I've followed you correctly, your Server (aka. Model) has a method that
knows
about your LoggingForm (aka. View).
Maybe something like this:
public class Server {
public LoggingForm getServerStatus() {
/* create, populate and return a LoggingForm */
}
}
Looking closely at this dependancy, you'll see that changes
to your View components could imply changes to your model component.
For instance, if you want to add another field LoggingForm,
you would need to modify your Model (Server) implementation
to make sure it correctly populates your form.
-- Levi
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 19, 2001 1:15 PM
> To: [EMAIL PROTECTED]
> Subject: Breaking MVC separation?
>
>
>
>
> I have a small architectural question...
>
> I have a LoggingForm bean for displaying the logging
> parameters on our own
> server. This contains several variables - boolean whether
> logging enabled,
> String current severity, Vector of possible severities, along
> with Vector of
> categories, each of which is a Parameter object holding key,
> value, description.
>
> I have a server bean which encapsulates all calls to the
> Server, and all of the
> above variables are obtained from one call to the server
> which returns a list
> containing the above in a specified order. My question is
> whether it is okay to
> pass the LoggingForm to the server bean and have it fill all
> the variables at
> once, or is this breaking the MVC separation? Should I,
> instead, call the
> server bean each time, to get/set each of the variables?
>
> I know all this gets a little fuzzy at times, but would
> appreciate any input.
>
> Thanks,
>
> Dave
>
>
>
