RE: [wsrp-webservice] [wsrp-webservices] what to consider for binar yat tachment

[Andre Kramer <andre.kramer@eu.citrix.com>]

Title: RE: [wsrp-webservice] [wsrp-webservices] what to consider for binar yat tachment

thanks for that, Subbu. I was delayed by another commitment today and failed to open the wsrp SC call on time.

apologies,
Andre

-----Original Message-----
From: Subbu Allamaraju [mailto:subbu@bea.com]
Sent: 10 December 2003 14:26
To: wsrp-webservice@lists.oasis-open.org
Subject: Re: [wsrp-webservice] [wsrp-webservices] what to consider for
binar yat tachment

When I add the extra element, our schema compiler fails with the
following error

wsrp_v1_types.xsd:502: error: Content model violates the unique particle
attribution rule

Regards,

Subbu

Andre Kramer said the following on 11/26/2003 08:20 AM:
> Only Subbu called in this week and he volunteered to test the extra
> schema file with BEA and Apache stacks - thanks.
> 
> regards (and a good Holiday to US folks),
> Andre
>
>     -----Original Message-----
>     *From:* Andre Kramer [mailto:andre.kramer@eu.citrix.com]
>     *Sent:* 24 November 2003 14:54
>     *To:* wsrp-webservice@lists.oasis-open.org
>     *Subject:* [wsrp-webservice] [wsrp-webservices] what to consider for
>     binary at tachment
>
>     One of the things that came up in the last call was the list for
>     candidates for special handling as binary or specially encoded data.
>     Here is a first attempt of such a list for this Wednesday' conf
>     call. Because of this week's US Holiday, I expect we will just have
>     a quick call to touch on this and the extra schema types, elements &
>     namespace issue.
>
>     regards,
>     Andre
>
>     -------------------
>
>     Elements that are potentially large or binary (or character or
>     otherwise encoded), or would allow for a compact domain specific
>     serialization, that could benefit from attachment (H - high benefit,
>     M - medium, L - low):
>
>     MarkupContext.markupString (H)
>     MarkupContext.markupBinary (H)
>     UploadContext.uploadData (H)
>     Property.value - could be large or binary (portlet and registration
>     property data) (H)
>
>     ResourceList - could be large or in diverse character sets. May
>     allow for JAR (Java ARchive) or other representation to be used for
>     serialization. (M)
>
>     RegistrationState.registrationState - could be cached on consumer
>     and uploaded at intervals (pushed back later) if large. (M)
>
>     RuntimeContext.templates - though cached in session (could vary per
>     call or be large) (M)
>     PortletContext.portletState - could be cached on consumer and
>     uploaded at intervals (pushed back later) if large. (M)
>     UserContext.userProfile - though cached it can be large or domain
>     specific (e.g. biometric data) (M)
>
>     ModelType - could be domain specific. (L)
>     ClientData.extensions? - could be large capability model (L)
>     UserContext.extensions? (L)
>     fault.details? (L)
>
>

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrp-webservice/members/leave_workgroup.php.