Passing Validation result between tiers??

[Albert Tollkuçi]

I have created a class ValidationResult which
looks like:
class ValidationResult
{
ValidationStatus Status;
ValidationItemCollection Items;
}
The ValidationItem is defined as below:
class ValidationItem
{
ValidationStatus Staus;
string Code; // Error code usually, but can be a warning, info or sth
else
string Message;
}
ValidationStatus is an enumeration which for the moment is defined as:
enum ValidationStatus
{
Success,
Failed
// Later can be added Warning, Info etc.
}
Now the problem is how to pass the ValidationResult object to the UI. I see
3 options:
1. throw an exeception which has a property of type ValidationResult. The UI
then can catch the exception and proceed. Looks a bit messy to me...
Pros: Force the UI to handel the validation.
Cons: Looks like a bad design. UI code would be messy...
2. Fire an event on a "global" object accessible from both UI and
components. "Recomment" the UI to attach an event handler...
Pros: UI code should be better organized...
Cons: UI is not forced to handle the event...
3. Use some kind of queue to add the ValidationResult objects from the
components and poll them from the UI.
Pros: ?
Cons: ?

Any thoughts are welcome.

Thanx,
Albert

[Santhi Maadhaven]

Instead of this why cant you make the class as static and access the
validationstattus anywhere.It will be an good solution.

"Albert Tollkuçi" wrote:

I have created a class ValidationResult which
looks like:
class ValidationResult
{
ValidationStatus Status;
ValidationItemCollection Items;
}
The ValidationItem is defined as below:
class ValidationItem
{
ValidationStatus Staus;
string Code; // Error code usually, but can be a warning, info or sth
else
string Message;
}
ValidationStatus is an enumeration which for the moment is defined as:
enum ValidationStatus
{
Success,
Failed
// Later can be added Warning, Info etc.
}
Now the problem is how to pass the ValidationResult object to the UI. I see
3 options:
1. throw an exeception which has a property of type ValidationResult. The UI
then can catch the exception and proceed. Looks a bit messy to me...
Pros: Force the UI to handel the validation.
Cons: Looks like a bad design. UI code would be messy...
2. Fire an event on a "global" object accessible from both UI and
components. "Recomment" the UI to attach an event handler...
Pros: UI code should be better organized...
Cons: UI is not forced to handle the event...
3. Use some kind of queue to add the ValidationResult objects from the
components and poll them from the UI.
Pros: ?
Cons: ?

Any thoughts are welcome.

Thanx,
Albert

[Albert Tollkuçi]

A static class is variation of the third option.
It can work, but it's not a good OO design...I'm not sure if it's the right
way to go...

"Santhi Maadhaven" <Sa*************@discussions.microsoft.com> wrote in
message news:F9**********************************@microsof t.com...

Instead of this why cant you make the class as static and access the
validationstattus anywhere.It will be an good solution.

"Albert Tollkuçi" wrote:

I have created a class ValidationResult which
looks like:
class ValidationResult
{
ValidationStatus Status;
ValidationItemCollection Items;
}
The ValidationItem is defined as below:
class ValidationItem
{
ValidationStatus Staus;
string Code; // Error code usually, but can be a warning, info or sth
else
string Message;
}
ValidationStatus is an enumeration which for the moment is defined as:
enum ValidationStatus
{
Success,
Failed
// Later can be added Warning, Info etc.
}
Now the problem is how to pass the ValidationResult object to the UI. I
see
3 options:
1. throw an exeception which has a property of type ValidationResult. The
UI
then can catch the exception and proceed. Looks a bit messy to me...
Pros: Force the UI to handel the validation.
Cons: Looks like a bad design. UI code would be messy...
2. Fire an event on a "global" object accessible from both UI and
components. "Recomment" the UI to attach an event handler...
Pros: UI code should be better organized...
Cons: UI is not forced to handle the event...
3. Use some kind of queue to add the ValidationResult objects from the
components and poll them from the UI.
Pros: ?
Cons: ?

Any thoughts are welcome.

Thanx,
Albert

[Greg Ro]

On Tue, 2 Aug 2005 13:45:31 +0200, "Albert Tollkuçi"
<al****@shqiperia.com> wrote:

A static class is variation of the third option.
It can work, but it's not a good OO design...I'm not sure if it's the right
way to go...

"Santhi Maadhaven" <Sa*************@discussions.microsoft.com> wrote in
message news:F9**********************************@microsof t.com...

Instead of this why cant you make the class as static and access the
validationstattus anywhere.It will be an good solution.

"Albert Tollkuçi" wrote:

I have created a class ValidationResult which
looks like:
class ValidationResult
{
ValidationStatus Status;
ValidationItemCollection Items;
}
The ValidationItem is defined as below:
class ValidationItem
{
ValidationStatus Staus;
string Code; // Error code usually, but can be a warning, info or sth
else
string Message;
}
ValidationStatus is an enumeration which for the moment is defined as:
enum ValidationStatus
{
Success,
Failed
// Later can be added Warning, Info etc.
}
Now the problem is how to pass the ValidationResult object to the UI. I
see
3 options:
1. throw an exeception which has a property of type ValidationResult. The
UI
then can catch the exception and proceed. Looks a bit messy to me...
Pros: Force the UI to handel the validation.
Cons: Looks like a bad design. UI code would be messy...
2. Fire an event on a "global" object accessible from both UI and
components. "Recomment" the UI to attach an event handler...
Pros: UI code should be better organized...
Cons: UI is not forced to handle the event...
3. Use some kind of queue to add the ValidationResult objects from the
components and poll them from the UI.
Pros: ?
Cons: ?

Any thoughts are welcome.

Thanx,
Albert

Forgive my ignorance. Are you talking about windows genuine
validation?
Greg Ro

[Albert Tollkuçi]

No, I'm taking about business rules validation.

"Greg Ro" wrote:

On Tue, 2 Aug 2005 13:45:31 +0200, "Albert Tollkuçi"
<al****@shqiperia.com> wrote:

A static class is variation of the third option.
It can work, but it's not a good OO design...I'm not sure if it's the right
way to go...

"Santhi Maadhaven" <Sa*************@discussions.microsoft.com> wrote in
message news:F9**********************************@microsof t.com...

Instead of this why cant you make the class as static and access the
validationstattus anywhere.It will be an good solution.

"Albert Tollkuçi" wrote:

I have created a class ValidationResult which
looks like:
class ValidationResult
{
ValidationStatus Status;
ValidationItemCollection Items;
}
The ValidationItem is defined as below:
class ValidationItem
{
ValidationStatus Staus;
string Code; // Error code usually, but can be a warning, info or sth
else
string Message;
}
ValidationStatus is an enumeration which for the moment is defined as:
enum ValidationStatus
{
Success,
Failed
// Later can be added Warning, Info etc.
}
Now the problem is how to pass the ValidationResult object to the UI. I
see
3 options:
1. throw an exeception which has a property of type ValidationResult. The
UI
then can catch the exception and proceed. Looks a bit messy to me...
Pros: Force the UI to handel the validation.
Cons: Looks like a bad design. UI code would be messy...
2. Fire an event on a "global" object accessible from both UI and
components. "Recomment" the UI to attach an event handler...
Pros: UI code should be better organized...
Cons: UI is not forced to handle the event...
3. Use some kind of queue to add the ValidationResult objects from the
components and poll them from the UI.
Pros: ?
Cons: ?

Any thoughts are welcome.

Thanx,
Albert

Forgive my ignorance. Are you talking about windows genuine
validation?
Greg Ro