OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [ws-rx] In support of simplifying WSRM Policy


Would we also remove the extensibility in the assertion -- which allows 
parameters to be defined outside of the WSRM policy doc?

If not, then even if the current parameters (AI and MaxMessageNumber) go 
away, we sill have to deal with extensible parameters.

-Anish
--

Jacques Durand wrote:
> If  Proposed-03 is accepted as new issue, could we discuss it right 
> away, and before i075 and i021?
> Not only its proposed resolution overlaps significantly with current 
> resolution on the table for i075, but gutting the RM policy of its 
> protocol parameters, meaning not associating these to a WSDL, may 
> certainly impact the above issues.
> 
> Jacques
> 
> -----Original Message-----
> From: Paul Fremantle [mailto:paul@wso2.com]
> Sent: Thursday, January 12, 2006 2:33 AM
> To: wsrx
> Subject: [ws-rx] In support of simplifying WSRM Policy
> 
> Yesterday I visited a large financial institution (a customer of a
> number of our member's companies) who is looking seriously at WSRM as a
> major part of their infrastructure.
> 
> They made some pertinent comments, based on trying three different RM
> implementations from various of the organisations represented in our TC.
> 
> Interoperability is their biggest issue. The biggest problems they have
> had today come from WS-Policy attachment. Different vendors have chosen
> to put the WSRMP in different places, and this caused them a number of
> headaches. When I pointed out this was an easy thing for us to fix, I
> got the reply that they have no need for policy. They are using WSRM in
> fixed patterns inside there organisation, and they suggested (unprompted
> I might add) that they would like an effective model of using WSRM
> without policy. I believe this backs up the proposals I have made for
> simplifying WSRM Policy.
> 
> They also made a request that when doing interoperability testing we not
> only publish the results, but also some details of the codebases that
> were used. They have concerns that some interoperability tests have been
> effected using different codebases than are then offered to the 
> marketplace.
> 
> Regards, Paul
> 
> -- 
> 
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> 
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
> 
> "Oxygenating the Web Service Platform", www.wso2.com
> 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]