You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Paul Fremantle <pz...@gmail.com> on 2006/12/04 17:33:53 UTC
Using wsrm namespace for sandesha config
Folks
I notice we use the wsrm namespace for our own internal config policy
statements as well as the real wsrm policy statements. That seems to
me to be a bug. I notice rampart is very clear about using a separate
namespace.
Does that mean that neethi will publish our internal configs as well
as the public policies?
If you agree its a bug I will raise a JIRA. I suggest that we
deprecate the wsrm: versions and encourage people to move over to a
new namespace.
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
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Using wsrm namespace for sandesha config
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Paul,
Sorry, think I was too hasty. If u meant the policies that were defined by
the WSRM 1.0 spec. Yes I agree.
It will be lot easier to hv those with one namespace and others
configuration data with another. Please raise a JIRA.
Chamikara
On 12/5/06, Chamikara Jayalath <ch...@gmail.com> wrote:
>
> Hi Paul,
>
> How can we exactly define real wsrm policy statements ?
>
> Chamikara
>
>
> On 12/4/06, Paul Fremantle < pzfreo@gmail.com> wrote:
> >
> > Folks
> >
> > I notice we use the wsrm namespace for our own internal config policy
> > statements as well as the real wsrm policy statements. That seems to
> > me to be a bug. I notice rampart is very clear about using a separate
> > namespace.
> >
> > Does that mean that neethi will publish our internal configs as well
> > as the public policies?
> >
> > If you agree its a bug I will raise a JIRA. I suggest that we
> > deprecate the wsrm: versions and encourage people to move over to a
> > new namespace.
> >
> > 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
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: sandesha-dev-help@ws.apache.org
> >
> >
>
Re: Using wsrm namespace for sandesha config
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Paul,
Sorry, think I was too hasty. If u meant the policies that were defined by
the WSRM 1.0 spec. Yes I agree.
It will be lot easier to hv those with one namespace and others
configuration data with another. Please raise a JIRA.
Chamikara
On 12/5/06, Chamikara Jayalath <ch...@gmail.com> wrote:
>
> Hi Paul,
>
> How can we exactly define real wsrm policy statements ?
>
> Chamikara
>
>
> On 12/4/06, Paul Fremantle < pzfreo@gmail.com> wrote:
> >
> > Folks
> >
> > I notice we use the wsrm namespace for our own internal config policy
> > statements as well as the real wsrm policy statements. That seems to
> > me to be a bug. I notice rampart is very clear about using a separate
> > namespace.
> >
> > Does that mean that neethi will publish our internal configs as well
> > as the public policies?
> >
> > If you agree its a bug I will raise a JIRA. I suggest that we
> > deprecate the wsrm: versions and encourage people to move over to a
> > new namespace.
> >
> > 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
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: sandesha-dev-help@ws.apache.org
> >
> >
>
Re: Using wsrm namespace for sandesha config
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Paul,
How can we exactly define real wsrm policy statements ?
Chamikara
On 12/4/06, Paul Fremantle <pz...@gmail.com> wrote:
>
> Folks
>
> I notice we use the wsrm namespace for our own internal config policy
> statements as well as the real wsrm policy statements. That seems to
> me to be a bug. I notice rampart is very clear about using a separate
> namespace.
>
> Does that mean that neethi will publish our internal configs as well
> as the public policies?
>
> If you agree its a bug I will raise a JIRA. I suggest that we
> deprecate the wsrm: versions and encourage people to move over to a
> new namespace.
>
> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>
Re: Using wsrm namespace for sandesha config
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Paul,
How can we exactly define real wsrm policy statements ?
Chamikara
On 12/4/06, Paul Fremantle <pz...@gmail.com> wrote:
>
> Folks
>
> I notice we use the wsrm namespace for our own internal config policy
> statements as well as the real wsrm policy statements. That seems to
> me to be a bug. I notice rampart is very clear about using a separate
> namespace.
>
> Does that mean that neethi will publish our internal configs as well
> as the public policies?
>
> If you agree its a bug I will raise a JIRA. I suggest that we
> deprecate the wsrm: versions and encourage people to move over to a
> new namespace.
>
> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>