Re: [wsrp] Any thoughts on the markup locale issue?

[Subbu Allamaraju <subbu@bea.com>]

Ricky,

Right. The MarkupParams.locales array is meant for markup generation 
only. Although it is not illegal to send the same locales used for 
metadata operations (like getServiceDescription), the producer may not 
be able to generate usable markup.

Subbu

ricky_frost@peoplesoft.com wrote:
> 
> Subbu,
> 
> Thanks for responding so quickly. You highlight my point exactly from the
> jira. Isn't the consumer supported locale meant for meta-data exchange
> (i.e. titles, keywords etc). How is it relevant to the markup request?
> 
> My example: If the client is asking for "it", and the producer can create
> "it" markup, but the consumer only supports "fr". In that case the
> "intersection" is "en" correct?
> 
> Who does that serve?
> 
> 
> subbu@bea.com wrote:
> 
> I think the userAgent and locales are two different issues.
> 
> a. Since there are no conformance statements for the userAgent string,
> consumer is free to send any arbitrary string. But I don't see why the
> consumer should not send whatever the user agent supplies.
> 
> b. Consumer can use some implementation-specific filtering to supply
> locales. It could, e.g. take an intersection of whatever the producer
> said it supports (in the service description) and those supplied by the
> user agent.
> 
> Subbu
> 
> ricky_frost@peoplesoft.com wrote:
>  > http://nagoya.apache.org/jira/browse/WSRP4J-40
> 
>