You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by Nencho Lupanov <ne...@googlemail.com> on 2007/06/27 16:10:19 UTC
[rampart]rampart xsd schema change?
Hi all,
recently i fixed a bug in rampart that prevented the usage of ssl encyption
in a transport binding policy.That fix use a custom rampart assertion that
is new to the rampart config....this fix is already adopted - you can check
the jira request at:
https://issues.apache.org/jira/browse/RAMPART-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496738
My question is - do we need to change also the rampart policy schema?
Regards,
Nencho
Re: [rampart]rampart xsd schema change?
Posted by Ruchith Fernando <ru...@gmail.com>.
The SSLConfig assertion is an optional assertion in the RampartConfig
assertion. It parsed using the
org.apache.rampart.policy.builders.SSLConfigBuilder class and we
create the SSLConfig object. If there are errors in the syntax of the
assertion then the SSLConfigBuilder should complain. Is this
validation sufficient?
We do not have an xml schema definition for RampartConfig assertion
and its child assertions at the moment and I don't see the requirement
of one for validation of the assertions since the model we have seems
to takes care of validation.
Am I missing something here?
Thanks,
Ruchith
On 7/11/07, Nencho Lupanov <ne...@googlemail.com> wrote:
> Hi Ruchith,
>
> the sslConfig assertion is cutom - e.g. not presented in the xsd chema but
> it still
> processed without errors....so it is not validated?
>
> Regards,
> Nencho
>
>
> 2007/7/11, Ruchith Fernando <ru...@gmail.com>:
> >
> > Well ... I believe when we are parsing the assertion we automatically
> > validate the assertions in the respective builders.
> >
> > Thanks,
> > Ruchith
> >
> > On 7/11/07, Angel Todorov <at...@gmail.com> wrote:
> > > Hi Ruchith,
> > >
> > > The question is not only about documenting it, but also about validating
> it.
> > > Does rampart currently validate against the XSD ? Thanks.
> > >
> > > Regards,
> > > Angel
> > >
> > >
> > > On 7/10/07, Ruchith Fernando <ruchith.fernando@gmail.com > wrote:
> > > >
> > > > Hmm ... This raises the issue of us not having documented the schema
> > > > of RampartConfig :-) ... I'll create a JIRA on this !
> > > >
> > > > Thanks,
> > > > Ruchith
> > > >
> > > > On 6/27/07, Nencho Lupanov < nencholupanov@googlemail.com> wrote:
> > > > > Hi all,
> > > > >
> > > > > recently i fixed a bug in rampart that prevented the usage of ssl
> > > encyption
> > > > > in a transport binding policy.That fix use a custom rampart
> assertion
> > > that
> > > > > is new to the rampart config....this fix is already adopted - you
> can
> > > check
> > > > > the jira request at:
> > > > >
> > >
> https://issues.apache.org/jira/browse/RAMPART-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496738
> > > > >
> > > > > My question is - do we need to change also the rampart policy
> schema?
> > > > >
> > > > > Regards,
> > > > > Nencho
> > > >
> > > >
> > > > --
> > > > www.ruchith.org
> > > > www.wso2.org
> > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> > > axis-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > www.ruchith.org
> > www.wso2.org
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [rampart]rampart xsd schema change?
Posted by Nencho Lupanov <ne...@googlemail.com>.
Hi Ruchith,
the sslConfig assertion is cutom - e.g. not presented in the xsd chema but
it still
processed without errors....so it is not validated?
Regards,
Nencho
2007/7/11, Ruchith Fernando <ru...@gmail.com>:
>
> Well ... I believe when we are parsing the assertion we automatically
> validate the assertions in the respective builders.
>
> Thanks,
> Ruchith
>
> On 7/11/07, Angel Todorov <at...@gmail.com> wrote:
> > Hi Ruchith,
> >
> > The question is not only about documenting it, but also about validating
> it.
> > Does rampart currently validate against the XSD ? Thanks.
> >
> > Regards,
> > Angel
> >
> >
> > On 7/10/07, Ruchith Fernando <ru...@gmail.com> wrote:
> > >
> > > Hmm ... This raises the issue of us not having documented the schema
> > > of RampartConfig :-) ... I'll create a JIRA on this !
> > >
> > > Thanks,
> > > Ruchith
> > >
> > > On 6/27/07, Nencho Lupanov < nencholupanov@googlemail.com> wrote:
> > > > Hi all,
> > > >
> > > > recently i fixed a bug in rampart that prevented the usage of ssl
> > encyption
> > > > in a transport binding policy.That fix use a custom rampart
> assertion
> > that
> > > > is new to the rampart config....this fix is already adopted - you
> can
> > check
> > > > the jira request at:
> > > >
> >
> https://issues.apache.org/jira/browse/RAMPART-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496738
> > > >
> > > > My question is - do we need to change also the rampart policy
> schema?
> > > >
> > > > Regards,
> > > > Nencho
> > >
> > >
> > > --
> > > www.ruchith.org
> > > www.wso2.org
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> >
>
>
> --
> www.ruchith.org
> www.wso2.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
Re: [rampart]rampart xsd schema change?
Posted by Ruchith Fernando <ru...@gmail.com>.
Well ... I believe when we are parsing the assertion we automatically
validate the assertions in the respective builders.
Thanks,
Ruchith
On 7/11/07, Angel Todorov <at...@gmail.com> wrote:
> Hi Ruchith,
>
> The question is not only about documenting it, but also about validating it.
> Does rampart currently validate against the XSD ? Thanks.
>
> Regards,
> Angel
>
>
> On 7/10/07, Ruchith Fernando <ru...@gmail.com> wrote:
> >
> > Hmm ... This raises the issue of us not having documented the schema
> > of RampartConfig :-) ... I'll create a JIRA on this !
> >
> > Thanks,
> > Ruchith
> >
> > On 6/27/07, Nencho Lupanov < nencholupanov@googlemail.com> wrote:
> > > Hi all,
> > >
> > > recently i fixed a bug in rampart that prevented the usage of ssl
> encyption
> > > in a transport binding policy.That fix use a custom rampart assertion
> that
> > > is new to the rampart config....this fix is already adopted - you can
> check
> > > the jira request at:
> > >
> https://issues.apache.org/jira/browse/RAMPART-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496738
> > >
> > > My question is - do we need to change also the rampart policy schema?
> > >
> > > Regards,
> > > Nencho
> >
> >
> > --
> > www.ruchith.org
> > www.wso2.org
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [rampart]rampart xsd schema change?
Posted by Angel Todorov <at...@gmail.com>.
Hi Ruchith,
The question is not only about documenting it, but also about validating it.
Does rampart currently validate against the XSD ? Thanks.
Regards,
Angel
On 7/10/07, Ruchith Fernando <ru...@gmail.com> wrote:
>
> Hmm ... This raises the issue of us not having documented the schema
> of RampartConfig :-) ... I'll create a JIRA on this !
>
> Thanks,
> Ruchith
>
> On 6/27/07, Nencho Lupanov <ne...@googlemail.com> wrote:
> > Hi all,
> >
> > recently i fixed a bug in rampart that prevented the usage of ssl
> encyption
> > in a transport binding policy.That fix use a custom rampart assertion
> that
> > is new to the rampart config....this fix is already adopted - you can
> check
> > the jira request at:
> >
> https://issues.apache.org/jira/browse/RAMPART-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496738
> >
> > My question is - do we need to change also the rampart policy schema?
> >
> > Regards,
> > Nencho
>
>
> --
> www.ruchith.org
> www.wso2.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
Re: [rampart]rampart xsd schema change?
Posted by Ruchith Fernando <ru...@gmail.com>.
Hmm ... This raises the issue of us not having documented the schema
of RampartConfig :-) ... I'll create a JIRA on this !
Thanks,
Ruchith
On 6/27/07, Nencho Lupanov <ne...@googlemail.com> wrote:
> Hi all,
>
> recently i fixed a bug in rampart that prevented the usage of ssl encyption
> in a transport binding policy.That fix use a custom rampart assertion that
> is new to the rampart config....this fix is already adopted - you can check
> the jira request at:
> https://issues.apache.org/jira/browse/RAMPART-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496738
>
> My question is - do we need to change also the rampart policy schema?
>
> Regards,
> Nencho
--
www.ruchith.org
www.wso2.org
Re: [rampart]rampart xsd schema change?
Posted by Ruchith Fernando <ru...@gmail.com>.
Hmm ... This raises the issue of us not having documented the schema
of RampartConfig :-) ... I'll create a JIRA on this !
Thanks,
Ruchith
On 6/27/07, Nencho Lupanov <ne...@googlemail.com> wrote:
> Hi all,
>
> recently i fixed a bug in rampart that prevented the usage of ssl encyption
> in a transport binding policy.That fix use a custom rampart assertion that
> is new to the rampart config....this fix is already adopted - you can check
> the jira request at:
> https://issues.apache.org/jira/browse/RAMPART-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496738
>
> My question is - do we need to change also the rampart policy schema?
>
> Regards,
> Nencho
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org