[ogsa-hpcp-wg] Globus Status

[Liang Zhong]

In order to have good effect on the SC06 Demo, we have done some
modification on our WS-Addressing module to add the EPR ReferenceParamters
to the SOAP header.
The most important is some one using just simple address fields to identify
their services, but others using the EPR.
Another problem is some one is still using SOAP 1.1 in their implementation.
When I choice to using SOAP 1.2 in our client, then we will got a fault from
the server side, when using SOAP 1.1, everything is ok.

Best Regards,
Liang ZHONG
Grid Computing Research Group
Institute of Advanced Computing Technology, Beihang University
Tel: +86 10 8231 6262
Fax: +86 10 8231 6796
Addr: Room 507, Building G,The New Main Building, 37# Xueyuan Rd., Haidian
District, Beijing 100083, PRC

-----Original Message-----
From: ogsa-hpcp-wg-bounces at ogf.org [mailto:ogsa-hpcp-wg-bounces at ogf.org] On
Behalf Of Peter G. Lane
Sent: Tuesday, November 07, 2006 12:09 AM
To: Mark Morgan
Cc: ogsa-hpcp-wg at ggf.org
Subject: Re: [ogsa-hpcp-wg] Globus Status

This is what Chris said:

I'm guessing that yours will require me to
set some SOAP header blocks based on the WS-Addressing SOAP binding. I had
hoped to avoid this detail for now....

By this I was under the impression that nobody was going to build clients
that added WS-Addressing 
SOAP headers. If that was the case, then services shouldn't publish EPRs
that have anything more 
than an address field.

Chris, did you change your mind? Was this only your point of view, or did
you think that everyone 
was going to skip the SOAP headers as well?

At any rate, I should still be able to interop with those services that
aren't expecting the SOAP 
headers. It just means I have to exclude at least the Genesis II
implementation since I won't have 
enough time to implement the agreed upon version of WS-Addressing.

Peter

Mark Morgan wrote:
> I think you misunderstood the result of that discussion.  The end result
was
> that services that didn't NEED EPRs, could use URLs.  However, we didn't
> dissalow EPRs, only allowed the more degenerate case of them (the pure
URL).
> 
> -Mark
> 
> --
> Mark Morgan
> Research Scientist
> Department of Computer Science
> University of Virginia
> http://www.cs.virginia.edu
> mmm2a at virginia.edu
> (434) 982-2047 
> 
>> -----Original Message-----
>> From: ogsa-hpcp-wg-bounces at ogf.org 
>> [mailto:ogsa-hpcp-wg-bounces at ogf.org] On Behalf Of Peter G. Lane
>> Sent: Monday, November 06, 2006 10:28 AM
>> To: ogsa-hpcp-wg at ggf.org
>> Subject: [ogsa-hpcp-wg] Globus Status
>>
>> I have the create and terminate operations implemented and 
>> working locally. I will put up an endpoint sometime today, 
>> and by them will hopefully have the other operations 
>> implemented. Is there a WSDL snipit or something of this 
>> "Show job output" operation, or does this just mean that I 
>> have an FTP server running?
>>
>> Problems
>> --------
>> I am unable to get responses from either of the .Net 
>> implementations using my client. My SOAP message logging show 
>> that the client message is going out, but nothing is ever 
>> received back. Are these services still up?
>>
>> I tried using my client on the Platform service (service URL 
>> https://plato.dreadnought.org), but I got an error saying 
>> that the client couldn't find the correct CA. I did download 
>> and install the CA cert and have debug output showing it was 
>> loaded, so I'm wondering if anyone has had success with this 
>> service recently. If so, Chris, could I get the public 
>> certificate of the server to help in my debugging?
>>
>> After agreeing that we wouldn't use EPRs, I'm confused about 
>> the use of them on the wiki. I did what others did and didn't 
>> bother implementing support for the WS-Addressing SOAP 
>> headers. The Platform EPR is trivial so that's not a problem. 
>> The GenesisII EPR, though, is very non-trivial. That said, I 
>> see that some clients have indeed talked to the GenesisII 
>> endpoint, so I'm rather confused. Did I miss a discussion 
>> where it was decided that full WS-Addressing support was now 
>> mandatory?
>>
>> Finally, I tried to use the CROWN endpoint too, but I get the 
>> following error:
>>
>> Authentication failed [Caused by: Defective credential 
>> detected [Caused by: [JGLOBUS-96] Certificate 
>> "C=CN,ST=Beijing,L=Beijing,O=company,OU=department,CN=localhos
>> t" expired]]
>>
>> Peter
>>
>