Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Received-SPF: pass (athena.apache.org: domain of glahiru@gmail.com designates
 74.125.82.174 as permitted sender)
MIME-Version: 1.0
Date: Wed, 14 May 2014 12:17:57 -0400
Message-ID: 
 <CAKq9_6JQbr0BiOUMtYRa=T_qZSJDTZAPkjho49RDpiu+Va_R8g@mail.gmail.com>
Subject: Validation failures and storing the failures
From: Lahiru Gunathilake <glahiru@gmail.com>
To: dev <dev@airavata.apache.org>
Content-Type: multipart/alternative; boundary=047d7b5d327cff554004f95e850f

--047d7b5d327cff554004f95e850f
Content-Type: text/plain; charset=UTF-8

Hi All,

We recently added validation logics to orchestrator, so gateway developers
can add/configure their validators to be invoked. If they failed they can
wrap an error message in their validation logic and return that.
Orchestrator needs to take these error messages and store them to a
persistent storage so that if the validation failed these errors can be
showed to the gateway user to make it correct. Unless we give a proper
error message to the end user there is no way to make it correct.

Currently in the orchestrator implementation it does not store the error
but we have a proper result object which keeps the validation state and a
message.

Where should I save this information in our data model ? This is an
information specific to each invocation and there could be multiple error
messages came from multiple validators because we do not return immediately
after the first validation failure but rather we invoke all the validators
and collect all the errors (currently we just have access to them and
simply logging those errors in server side). If there is no placeholder for
these validation errors can we add something to the data model to store
them and retrieve them from the client code ?

I have added FAQ type of a document for Orchestrator[1], please provide
your feedback on this.

[1]
https://docs.google.com/document/d/1FOc0X6HCMZ9E-fTnZQ8aGo7tK20C8lvKlycNouswICI/edit

Regards
Lahiru

-- 
System Analyst Programmer
PTI Lab
Indiana University

--047d7b5d327cff554004f95e850f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi All,<div><br></div><div>We recently added validation lo=
gics to orchestrator, so gateway developers can add/configure their validat=
ors to be invoked. If they failed they can wrap an error message in their v=
alidation logic and return that. Orchestrator needs to take these error mes=
sages and store them to a persistent storage so that if the validation fail=
ed these errors can be showed to the gateway user to make it correct. Unles=
s we give a proper error message to the end user there is no way to make it=
 correct.</div>

<div><br></div><div>Currently in the orchestrator implementation it does no=
t store the error but we have a proper result object which keeps the valida=
tion state and a message.</div><div><br></div><div>Where should I save this=
 information in our data model ? This is an information specific to each in=
vocation and there could be multiple error messages came from multiple vali=
dators because we do not return immediately after the first validation fail=
ure but rather we invoke all the validators and collect all the errors (cur=
rently we just have access to them and simply logging those errors in serve=
r side). If there is no placeholder for these validation errors can we add =
something to the data model to store them and retrieve them from the client=
 code ?</div>
<div><br></div><div>I have added FAQ type of a document for Orchestrator[1]=
, please provide your feedback on this.</div><div><br></div><div>[1]<a href=
=3D"https://docs.google.com/document/d/1FOc0X6HCMZ9E-fTnZQ8aGo7tK20C8lvKlyc=
NouswICI/edit">https://docs.google.com/document/d/1FOc0X6HCMZ9E-fTnZQ8aGo7t=
K20C8lvKlycNouswICI/edit</a></div>

<div><br></div><div>Regards</div><div>Lahiru</div><div><div><br></div>-- <b=
r>System Analyst Programmer<div>PTI Lab</div><div>Indiana University</div>
</div></div>

--047d7b5d327cff554004f95e850f--