Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » OHF » prefix not associated to uri in Bridge wsdl
prefix not associated to uri in Bridge wsdl [message #37168] Thu, 15 November 2007 06:22 Go to next message
Takeo Satomi is currently offline Takeo Satomi
Messages: 32
Registered: July 2009
Member
I've been looking for a library that would make my soap programming easier
and I though I found it, but it didn't work. As long as I see, the
library uses namespace uri and associated prefix written in WSDL to see
the type of the given soap parameter is primitive (int, string, boolean,
etc.) or complex. And I noticed the WSDL the Bridge provides uses
prefixes like xsd, tns1 or impl without any associated uri. I can't be
sure if it's valid or not though. Can anyone else?

Takeo Satomi
Re: prefix not associated to uri in Bridge wsdl [message #37237 is a reply to message #37168] Thu, 15 November 2007 14:33 Go to previous messageGo to next message
No real name is currently offline No real name
Messages: 292
Registered: July 2009
Senior Member
Hi Takeo,

I'm not sure I understand your question below. Is this a problem you see
with the OHF Bridge, in that the prefixing in the WSDL is not associated
with declared uri? My gut reaction to this is issue (if I understand you
correctly) is that this is not what is intended, but I'll have to defer
to Matt to be sure.

Please clarify if I'm not correctly understanding your question.
- Sarah



Takeo Satomi wrote:
> I've been looking for a library that would make my soap programming
> easier and I though I found it, but it didn't work. As long as I see,
> the library uses namespace uri and associated prefix written in WSDL to
> see the type of the given soap parameter is primitive (int, string,
> boolean, etc.) or complex. And I noticed the WSDL the Bridge provides
> uses prefixes like xsd, tns1 or impl without any associated uri. I
> can't be sure if it's valid or not though. Can anyone else?
>
> Takeo Satomi
>
Re: prefix not associated to uri in Bridge wsdl [message #37339 is a reply to message #37237] Fri, 16 November 2007 00:02 Go to previous messageGo to next message
Takeo Satomi is currently offline Takeo Satomi
Messages: 32
Registered: July 2009
Member
Thank you for your reply Sarah,

And sorry for my confusing post. I think you understand it correctly.
If the current wsdl, having prefixes without association to declared URIs,
is neither as intended nor valid, I'd love to have fixed one.

Thanks,
Takeo Satomi

Sarah Knoop wrote:

> Hi Takeo,

> I'm not sure I understand your question below. Is this a problem you see
> with the OHF Bridge, in that the prefixing in the WSDL is not associated
> with declared uri? My gut reaction to this is issue (if I understand you
> correctly) is that this is not what is intended, but I'll have to defer
> to Matt to be sure.

> Please clarify if I'm not correctly understanding your question.
> - Sarah



> Takeo Satomi wrote:
>> I've been looking for a library that would make my soap programming
>> easier and I though I found it, but it didn't work. As long as I see,
>> the library uses namespace uri and associated prefix written in WSDL to
>> see the type of the given soap parameter is primitive (int, string,
>> boolean, etc.) or complex. And I noticed the WSDL the Bridge provides
>> uses prefixes like xsd, tns1 or impl without any associated uri. I
>> can't be sure if it's valid or not though. Can anyone else?
>>
>> Takeo Satomi
>>
Re: prefix not associated to uri in Bridge wsdl [message #37373 is a reply to message #37339] Fri, 16 November 2007 02:10 Go to previous messageGo to next message
Takeo Satomi is currently offline Takeo Satomi
Messages: 32
Registered: July 2009
Member
I'm sorry to have bother you all, since I've found prefixes are declared
correctly with associated URIs. It's just my browser was hiding those
attributes for unknow reason. I'll check the soap helper library and
will let you know if there's any problem with the wsdl.

Takeo
Re: prefix not associated to uri in Bridge wsdl [message #37406 is a reply to message #37373] Fri, 16 November 2007 12:29 Go to previous message
No real name is currently offline No real name
Messages: 292
Registered: July 2009
Senior Member
Thanks for the update Takeo. Keep us posted on your progress.

- Sarah



Takeo Satomi wrote:
> I'm sorry to have bother you all, since I've found prefixes are declared
> correctly with associated URIs. It's just my browser was hiding those
> attributes for unknow reason. I'll check the soap helper library and
> will let you know if there's any problem with the wsdl.
>
> Takeo
>
>
Re: prefix not associated to uri in Bridge wsdl [message #583160 is a reply to message #37168] Thu, 15 November 2007 14:33 Go to previous message
No real name is currently offline No real name
Messages: 292
Registered: July 2009
Senior Member
Hi Takeo,

I'm not sure I understand your question below. Is this a problem you see
with the OHF Bridge, in that the prefixing in the WSDL is not associated
with declared uri? My gut reaction to this is issue (if I understand you
correctly) is that this is not what is intended, but I'll have to defer
to Matt to be sure.

Please clarify if I'm not correctly understanding your question.
- Sarah



Takeo Satomi wrote:
> I've been looking for a library that would make my soap programming
> easier and I though I found it, but it didn't work. As long as I see,
> the library uses namespace uri and associated prefix written in WSDL to
> see the type of the given soap parameter is primitive (int, string,
> boolean, etc.) or complex. And I noticed the WSDL the Bridge provides
> uses prefixes like xsd, tns1 or impl without any associated uri. I
> can't be sure if it's valid or not though. Can anyone else?
>
> Takeo Satomi
>
Re: prefix not associated to uri in Bridge wsdl [message #583222 is a reply to message #37237] Fri, 16 November 2007 00:02 Go to previous message
Takeo Satomi is currently offline Takeo Satomi
Messages: 32
Registered: July 2009
Member
Thank you for your reply Sarah,

And sorry for my confusing post. I think you understand it correctly.
If the current wsdl, having prefixes without association to declared URIs,
is neither as intended nor valid, I'd love to have fixed one.

Thanks,
Takeo Satomi

Sarah Knoop wrote:

> Hi Takeo,

> I'm not sure I understand your question below. Is this a problem you see
> with the OHF Bridge, in that the prefixing in the WSDL is not associated
> with declared uri? My gut reaction to this is issue (if I understand you
> correctly) is that this is not what is intended, but I'll have to defer
> to Matt to be sure.

> Please clarify if I'm not correctly understanding your question.
> - Sarah



> Takeo Satomi wrote:
>> I've been looking for a library that would make my soap programming
>> easier and I though I found it, but it didn't work. As long as I see,
>> the library uses namespace uri and associated prefix written in WSDL to
>> see the type of the given soap parameter is primitive (int, string,
>> boolean, etc.) or complex. And I noticed the WSDL the Bridge provides
>> uses prefixes like xsd, tns1 or impl without any associated uri. I
>> can't be sure if it's valid or not though. Can anyone else?
>>
>> Takeo Satomi
>>
Re: prefix not associated to uri in Bridge wsdl [message #583232 is a reply to message #37339] Fri, 16 November 2007 02:10 Go to previous message
Takeo Satomi is currently offline Takeo Satomi
Messages: 32
Registered: July 2009
Member
I'm sorry to have bother you all, since I've found prefixes are declared
correctly with associated URIs. It's just my browser was hiding those
attributes for unknow reason. I'll check the soap helper library and
will let you know if there's any problem with the wsdl.

Takeo
Re: prefix not associated to uri in Bridge wsdl [message #583243 is a reply to message #37373] Fri, 16 November 2007 12:29 Go to previous message
No real name is currently offline No real name
Messages: 292
Registered: July 2009
Senior Member
Thanks for the update Takeo. Keep us posted on your progress.

- Sarah



Takeo Satomi wrote:
> I'm sorry to have bother you all, since I've found prefixes are declared
> correctly with associated URIs. It's just my browser was hiding those
> attributes for unknow reason. I'll check the soap helper library and
> will let you know if there's any problem with the wsdl.
>
> Takeo
>
>
Previous Topic:OHF Connectathon Mesa Test Status and Schedule
Next Topic:Bridge: Node-Authentication failure message (#1222)
Goto Forum:
  


Current Time: Mon Jul 28 08:33:24 EDT 2014

Powered by FUDForum. Page generated in 0.01814 seconds