RE: [wsrp-wsia] [change request #176] ID,Key and Handle not used inWSDL

["Tamari, Yossi" <yossi.tamari@sap.com>]

Hi Alejandro,

 

You misunderstood what I meant by "ANY". I meant the English word, not the XSD element... It just happened that the XSD element is a good example of my point...

 

My viewpoint is, implementation is always behind definition, and if nobody uses defined features, they don't get implemented, which creates a circle. If we use a WSDL feature we need and our stacks do not support, we can go back to the stack developers and tell them they need to develop this feature, and use a workaround until they do. If we only stick to features that exist in everybody's implementations, we will be extremely handicapped.

 

Anyway, I don't see this as a major issue, and (considering emails from Rich and Andre) give up on the subject.

 

    Yossi.

-----Original Message-----
From: Alejandro Abdelnur [mailto:Alejandro.Abdelnur@Sun.COM]
Sent: Wednesday, February 26, 2003 9:01 PM
To: Tamari, Yossi; wsrp-wsia@lists.oasis-open.org
Subject: Re: [wsrp-wsia] [change request #176] ID,Key and Handle not used in WSDL

JAX-RCP 1.0 specification provisions for [optionally] supporting ANY. It does not provision for [optionally|mandatory] supporting strings with restrictions. Certainly this can be done with custom serializers/deserializers, but the serializer story is not specified yet, it is left to vendors. We've already made quite a few accomodations in WSRP because other stardards are not there yet. I don't see this as something essential, we are not changing/lossing functionality because of this one.

The RI is not meant to be industrial strength (it could be), but is meant to be spec functional complete.

My understanding on tabling attachments (SOAP attachments and/or DIME) was because we did not have something common supported in both platforms and as you say it was not essential. But I think that if we had both platforms supporting either one of the attachment mechanisms it would be there in WSRP.

Alejandro


Tamari, Yossi wrote:

Hi Alejandro,

This was not meant as a knock against JAX-RPC, Sun, or the RI, but it does seem that the RI is very basic. It is true that JAX-RPC does not require implementation of strings, but based on that, we would need to disqualify ANY feature of SOAP that JAX-RPC does not require, even if everybody implements it... I do not think the RI was meant as an industrial strength implementation, am I wrong?
I do not think we decided not to support SOAP Attachment. I think we decided to delay that and DIME to 1.1, since they were not essential to the operation of WSRP, and we felt we did not have the time to fully explore them.

	Yossi.

-----Original Message-----
From: Alejandro Abdelnur [mailto:Alejandro.Abdelnur@Sun.COM]
Sent: Wednesday, February 26, 2003 8:21 PM
To: Gil Tayar
Cc: Tamari, Yossi; wsrp-wsia@lists.oasis-open.org
Subject: Re: [wsrp-wsia] [change request #176] ID,Key and Handle not
used in WSDL



JAX-RPC RI is not a proof of concept, is the *reference* implementation, 
it fully implements the JAX-RPC specification. If a JAX-RPC 
implementation supports restrictions on String is an feature of the 
implementation, but it is not required for an implementation to do 
so.The "Futures" chapter in the spec states "Extended support for XML 
schema types and Java types", it seems they will support it in a future 
version.

Alejandro
PS: We decided not to use SOAP with Attachments (a SOAP 1.1 extension 
submitted to the W3C)  because the .NET stack does not support it, 
didn't we?

Gil Tayar wrote:

  

Down with jax-rpc! :-) 

Seriously, I agree.

-----Original Message-----
From: "Tamari, Yossi" <yossi.tamari@sap.com>
Date: Tue, 25 Feb 2003 17:52:26 
To:wsrp-wsia@lists.oasis-open.org
Subject: RE: [wsrp-wsia] [change request #176] ID,
Key and Handle not used	in WSDL

Can someone please refresh my memory on if we decided not to do "the right thing" in the WSDL, simply because the JAX-RPC RI does not support them?
I can understand this if these are advanced WSDL features that all WS stacks have problems with, but the JAX-RPC RI is just a proof of concept, it should not be taken as a model implementation in my opinion.

	Yossi.

-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Tuesday, February 25, 2003 5:58 PM
To: wsrp-wsia@lists.oasis-open.org
Subject: [wsrp-wsia] [change request #176] ID, Key and Handle not used
in WSDL


Document: wsrp_v1_types.xsd
Section:  General types
Page/Line: 
Requested by: Richard Jacob
Old text: none
New text: add comments about non-use of Id, Key and Handle types
Reasoning:
Our Spec defines types for IDs, Keys and Handles. However we don't use 
them in the WSDL as JAX-RPC RI can't handle restrictions on strings, 
instead we use plain string types. We should comment in our XSD, that 
these aren't used because of the mentioned problems.


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
 

    

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>