[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [wsrp-webservice] Re: [wsrp-wsia] web services call
Is the first problem just at the time when the tools are generating stubs
and proxies? If so, I would see relaxing it at that time as ok, but the
customization subgroup really did want this to be schema elements only.
I seem to remember that the second was a bigger problem with the stack
during deserialization. I would hate to introduce a wrapper for the
"normal" payload of the Property element, though I understand this makes
the developers job of extracting the fields more difficult.
Rich Thompson
David Ward <david.ward@oracle.com>
03/12/2003 11:34 AM
To: Andre Kramer <andre.kramer@eu.citrix.com>
cc: Rich Thompson/Watson/IBM@IBMUS,
"'wsrp-webservice@lists.oasis-open.org'"
<wsrp-webservice@lists.oasis-open.org>
Subject: Re: [wsrp-wsia] web services call
Hi
Initial testing with the latest 0.92 WSDL seems to suggest it will work OK
with our (fixed) JAX-RPC RI [the fixes I am referring to are the ones
concerning the serialization of null values]. I haven't had a chance to
try the latest drop from Sun.
However:
I have already told you that in ModelTypes, <any namespace="
http://www.w3.org/2001/XMLSchema"/> messes us up, and the best we can hope
for is <any namespace="##other"/>
I would have preferred the <any> inside the Property type to be wrapped
inside an element of its own, so that we still get typed members for
stringValue, name and lang
Regards
David
Andre Kramer wrote:
Since only Rich and I called in we mainly used the time to go over some
minor editorials I found in 0.92.
I will recommend that the best practice for sending XML fragments for now
is
as a markupString or as markupBinary if charset matters.
Rich (or Richard with Web Master userCategory) will put the 0.92 wsdl on
the
Oasis Web site.
Chris, David, did you find any issues for your Web stacks?
regards,
Andre
-----Original Message-----
From: Andre Kramer
Sent: 11 March 2003 12:35
To: 'Rich Thompson'
Cc: 'wsrp-webservice@lists.oasis-open.org'
Subject: RE: [wsrp-wsia] Spec v0.92
Looks fine on first test (except version numbers in wsdl are wrong).
Should
we have a wsdl sub group call tomorrow?
Wednesdays, 7 am PST / 10 am EST / 4 pm CET, 1 hour
US dial in #: 1.888.481.3032
International Dial in #: 1.617.801.9600
Participant Passcode: 28614774 (you will be asked for your name)
UK 0800 904 7961
D 0800 1813856
Some wsdl related comments below.
regards,
Andre
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: 10 March 2003 18:31
To: wsrp-wsia@lists.oasis-open.org; wsia@lists.oasis-open.org;
wsrp@lists.oasis-open.org
Subject: [wsrp-wsia] Spec v0.92
I have reflected the change request resolutions to-date into the spec to
produce this version. I think the following are all the open items still
needing resolution:
Left open at the Jan F2F:
- Sasha to propose language for 1.2.4 about what the protocol enables
End-Users to do.
- WSDL subgroup to explore a more "natural" way to carry xml markup.
(current best is in the markupBinary field)
<ak> I sent the attached to the email list after the last f2f partly to
address this issue, but we did not discusss it yet.</ak>
- Desire to rename the MarkupType Type. Suggestions have included
MarkupSupport and MarkupFormat. Any others?
<ak> UploadContext uses mimeType. http uses ContentType. </ak>
Open Change Requests:
- 138 – How does info get to proxied resources
- 141 – Add previous windowState and mode?
- 207 – PortletDescription dependent on UserContext?
- 213 – Require modes, windowstates & userAuthentication are URIs (This
was in the set that was blanket adopted and is reflected in v0.92, but is
enough different from the discussion of the blanket adopted set that I am
calling it out here.)
- 215 – Delete statement about “private conversational state”
- 230 – Setting navState
- 234 – Delete section B.1
The "marked" version has had all of the formatting changes accepted so
that it is easier to see the insertions and deletions. The second copy has
had all changes accepted for those who find the change marks distracting.
An item that has been discussed in the WSDL subgroup that also merits
calling out is that we define two types in our WSDL (StringArray and
NamedStringArray) that we do not use. They have been left in the
definition for possible use by extensions.
<ak> We are going to call out NamedStringArray for UserProfile extension
using name / value pairs? Then it should be in the spec doc as well as in
wsdl. </ak>
Rich Thompson
--
David Ward
Principal Software Engineer
Oracle Portal
Oracle European Development Centre
520 Oracle Parkway
Thames Valley Park
Reading
Berkshire RG6 1RA
UK
Email:
david.ward@oracle.com
Tel:
+44 118 924 5079
Fax:
+44 118 924 5005
^qyڦj)vn{[O<m j}=nuM4E ~&jwkzJڙȭ,\fz't+afw^lƬ)pyM; ǝ};ǜm j}=nuM4]*Z+Z
Nz|z+u䞌' B^z- &u}^f)zz+#?m j}=nuM4E ~&- &- &Mn8o( zrnȭ,\o<R]{+a#>'I
;o_, nǫ' +-)zz+8nCm4OyF14^qykfMnY[ j}5rnȭ,\mtM~\r+k(;^R13t u+zqb(jȬ1M7cE ~&Mn5VMfj)lqԉzjq j)UYe54m j}=MM4E o(p{!W- &+a"{^w1Iǹn_bt4=0Y8nCm4Oy4M z ^^< =1|[\M\r+k(Z ݭjgjwkzJڙȭ,\dzqb(jȬ0py zX+(n7d֭!6y8nCm4Oy~4M z"}t\ƢȞLj)RzqyۮwШק<zױej)܅zج9Xm 0y z+uiڮڮ{ͿYzq(,
W+('H ,kzǧbhjȜ> WhZ ^~nh^ȨhZd rj
yhikz-謲}mifz{l~8ӅZ')ܢh^8z0@֜g0K)yȟƭڝkyj{ ^n) jZr"d-gƗZb
+jezםvzVh^* bh\^rqp0Y[y&Wy▇+2yڝax{]\jvނ)0֩/jW2rWYbjrz M7b*'jYrz)kǬ镩x y˫wG֤x(^笶*'hqܕrߢǨ~Z+lzDMg."ry)+aj~)^lu)z)jw\ezx" jށݰ ݭ
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]