RE: TWS - Clarification

["Reynolds, Peter" <Peter.Reynolds@bowneglobal.ie>]

Hi Kevin,

If I remember correctly, I think the quote was to be returned as a SOAP
attachment rather than a parameter.

Andrzej, Can you remember whether this is right. 

Thanks,

Peter.

-----Original Message-----
From: Kevin.Bargary [mailto:Kevin.Bargary@ul.ie] 
Sent: 23 September 2005 15:14
To: Reynolds, Peter; Kevin.Bargary; azydron@xml-intl.com
Cc: Michael.J.Bourke; Reinhard.Schaler; trans-ws@lists.oasis-open.org
Subject: RE: TWS - Clarification

Hi Peter and Andrzej,

When going through the specification I came across a call, namely
"retrieveQuote". This "allows for the retrieval of the quote".

Input = ticket ( jobID, projectID and userID ) Return Value = ticket (
jobID, projectID and userID )

Same input and output!

There is no information about the quote in this call. Just the ticket
info.
Would it be feasible to also send back some information regarding the
quote (such as available date?, or other data submitted throught the
requestQuote call). At the moment, all it seems to be returning is
exactly what is sent to it rendering it redundant.

I see this call as being used when the client needs to check his quote
(not his ticket) using his ticket (jobID,projectID,userID) or in case he
forgot the details from requestQuote response? Am I missing the point?

Is there some other purpose that I am failing to see for this call?

Thanks in Advance,

Kevin


-----Original Message-----
From: Reynolds, Peter [mailto:Peter.Reynolds@bowneglobal.ie]
Sent: 23 September 2005 11:40
To: Kevin.Bargary; azydron@xml-intl.com
Cc: Michael.J.Bourke; Reinhard.Schaler; trans-ws@lists.oasis-open.org
Subject: RE: TWS - Clarification

Hi Kevin,

Thanks for this.

I think returning the hard coded values is fine for the moment. The
purpose of the exercise is to show the web services work and not some
back end system which doesn't exist anyway. That said, if it were
possible to return more meaningful values at some stage that would be
excellent.

I still want to visit you at the LRC and see what you are doing. However
work is busy at present. I will contact you next week about this and we
can try and arrange something.

Thanks,

Peter.

-----Original Message-----
From: Kevin.Bargary [mailto:Kevin.Bargary@ul.ie]
Sent: 23 September 2005 11:06
To: Reynolds, Peter; 'azydron@xml-intl.com'
Cc: Michael.J.Bourke; Reinhard.Schaler
Subject: TWS - Clarification

Hi Peter and Andrzej,

Sorry about not sending this to the TWS mailing list but I still cannot
send emails to this list. My sent emails keep bouncing, which is strange
because I receive all emails sent to the list. I just need some
clarification regarding development of the implementation of the TWS
specification.

As I am developing the server side code for the services, all I am doing
is returning hard coded values from the server. Is this ok? Or had you
guys something else in mind for the server side? If so, it would be good
to incorporate them now so as the code will not have to be changed over
and over again. The reason I am asking this is because it is not too
difficult to return hard coded strings, but in a real environment this
would never be the case - there would always be a back-end no matter how
basic.

Having said all that, if time is an issue then I can work away and just
return meaningless values purely for demonstrative purposes just to get
it done! 

Could you clarify the requirements, as I am unsure to what level you
want this implementation developed? 

Thanks in Advance,

Kevin Bargary

++++++++++++++++++
Kevin Bargary BSc.
Research Assistant,
Localisation Research Centre,
University of Limerick,
Ireland.
Email: Kevin.Bargary@ul.ie
Telephone: 061-213557
++++++++++++++++++