You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "Dittmann, Werner" <we...@siemens.com> on 2005/12/08 15:40:51 UTC

[Policy] Question / problem in PolicyReader (Stream OM based)

Sanka,

during the tests to check the updates and synchronization
of the DOM based reader I also modified the policy2.xml
to see if the xml:base option works. 

While I got it working with the DOM based reader I noticed
that the stream OM based reader does not find this option
- pls have a look in this module, I left the debug
printouts in the code.

I'm not familiar with the Stream/OM model, but to me it seems 
that this parser omits the setting for the namespace that is
bound to the xml prefix. This namespace is fixed and should be
wired in any parser that is namespace aware (see the constants
file for the namespace definition).

Werner

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


Re: [Policy] Question / problem in PolicyReader (Stream OM based)

Posted by Sanka Samaranayake <ss...@gmail.com>.
Hi Werner,

On 12/8/05, Dittmann, Werner <we...@siemens.com> wrote:
> Sanka,
>
> during the tests to check the updates and synchronization
> of the DOM based reader I also modified the policy2.xml
> to see if the xml:base option works.
>
> While I got it working with the DOM based reader I noticed
> that the stream OM based reader does not find this option
> - pls have a look in this module, I left the debug
> printouts in the code.
>
> I'm not familiar with the Stream/OM model, but to me it seems
> that this parser omits the setting for the namespace that is
> bound to the xml prefix. This namespace is fixed and should be
> wired in any parser that is namespace aware (see the constants
> file for the namespace definition).

I think its a bug in the XML Stream parser which they use as the
default. Let me ask for expert's advice about this in axis-dev mailing
list.

Sanka
>
> Werner
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


Re: [Policy] Question / problem in PolicyReader (Stream OM based)

Posted by Ruchith Fernando <ru...@gmail.com>.
fixed :-)

Pls try the latest svn (after revision-355405)

- Ruchith

On 12/9/05, Sanka Samaranayake <ss...@gmail.com> wrote:
> On 12/8/05, Davanum Srinivas <da...@gmail.com> wrote:
> > Sanka,
> >
> > Please log a JIRA bug, so that we can track it.
>
> done !!
> Sanka
>
> >
> > thanks,
> > dims
> >
> > On 12/9/05, Sanka Samaranayake <ss...@gmail.com> wrote:
> > > On 12/8/05, Dittmann, Werner <we...@siemens.com> wrote:
> > > > Sanka,
> > > >
> > > > during the tests to check the updates and synchronization
> > > > of the DOM based reader I also modified the policy2.xml
> > > > to see if the xml:base option works.
> > > >
> > > > While I got it working with the DOM based reader I noticed
> > > > that the stream OM based reader does not find this option
> > > > - pls have a look in this module, I left the debug
> > > > printouts in the code.
> > > >
> > > > I'm not familiar with the Stream/OM model, but to me it seems
> > > > that this parser omits the setting for the namespace that is
> > > > bound to the xml prefix. This namespace is fixed and should be
> > > > wired in any parser that is namespace aware (see the constants
> > > > file for the namespace definition).
> > >
> > >
> > > I think its a bug in the XML Stream parser which they use as the
> > > default. Let me ask for expert's advice about this in axis-dev mailing
> > > list.
> > >
> > > Sanka
> > > >
> > > > Werner
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: wss4j-dev-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: wss4j-dev-help@ws.apache.org
>
>


--
Ruchith

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


Re: [Policy] Question / problem in PolicyReader (Stream OM based)

Posted by Ruchith Fernando <ru...@gmail.com>.
fixed :-)

Pls try the latest svn (after revision-355405)

- Ruchith

On 12/9/05, Sanka Samaranayake <ss...@gmail.com> wrote:
> On 12/8/05, Davanum Srinivas <da...@gmail.com> wrote:
> > Sanka,
> >
> > Please log a JIRA bug, so that we can track it.
>
> done !!
> Sanka
>
> >
> > thanks,
> > dims
> >
> > On 12/9/05, Sanka Samaranayake <ss...@gmail.com> wrote:
> > > On 12/8/05, Dittmann, Werner <we...@siemens.com> wrote:
> > > > Sanka,
> > > >
> > > > during the tests to check the updates and synchronization
> > > > of the DOM based reader I also modified the policy2.xml
> > > > to see if the xml:base option works.
> > > >
> > > > While I got it working with the DOM based reader I noticed
> > > > that the stream OM based reader does not find this option
> > > > - pls have a look in this module, I left the debug
> > > > printouts in the code.
> > > >
> > > > I'm not familiar with the Stream/OM model, but to me it seems
> > > > that this parser omits the setting for the namespace that is
> > > > bound to the xml prefix. This namespace is fixed and should be
> > > > wired in any parser that is namespace aware (see the constants
> > > > file for the namespace definition).
> > >
> > >
> > > I think its a bug in the XML Stream parser which they use as the
> > > default. Let me ask for expert's advice about this in axis-dev mailing
> > > list.
> > >
> > > Sanka
> > > >
> > > > Werner
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: wss4j-dev-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: wss4j-dev-help@ws.apache.org
>
>


--
Ruchith

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


Re: [Policy] Question / problem in PolicyReader (Stream OM based)

Posted by Sanka Samaranayake <ss...@gmail.com>.
On 12/8/05, Davanum Srinivas <da...@gmail.com> wrote:
> Sanka,
>
> Please log a JIRA bug, so that we can track it.

done !!
Sanka

>
> thanks,
> dims
>
> On 12/9/05, Sanka Samaranayake <ss...@gmail.com> wrote:
> > On 12/8/05, Dittmann, Werner <we...@siemens.com> wrote:
> > > Sanka,
> > >
> > > during the tests to check the updates and synchronization
> > > of the DOM based reader I also modified the policy2.xml
> > > to see if the xml:base option works.
> > >
> > > While I got it working with the DOM based reader I noticed
> > > that the stream OM based reader does not find this option
> > > - pls have a look in this module, I left the debug
> > > printouts in the code.
> > >
> > > I'm not familiar with the Stream/OM model, but to me it seems
> > > that this parser omits the setting for the namespace that is
> > > bound to the xml prefix. This namespace is fixed and should be
> > > wired in any parser that is namespace aware (see the constants
> > > file for the namespace definition).
> >
> >
> > I think its a bug in the XML Stream parser which they use as the
> > default. Let me ask for expert's advice about this in axis-dev mailing
> > list.
> >
> > Sanka
> > >
> > > Werner
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: wss4j-dev-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


Re: [Policy] Question / problem in PolicyReader (Stream OM based)

Posted by Sanka Samaranayake <ss...@gmail.com>.
On 12/8/05, Davanum Srinivas <da...@gmail.com> wrote:
> Sanka,
>
> Please log a JIRA bug, so that we can track it.

done !!
Sanka

>
> thanks,
> dims
>
> On 12/9/05, Sanka Samaranayake <ss...@gmail.com> wrote:
> > On 12/8/05, Dittmann, Werner <we...@siemens.com> wrote:
> > > Sanka,
> > >
> > > during the tests to check the updates and synchronization
> > > of the DOM based reader I also modified the policy2.xml
> > > to see if the xml:base option works.
> > >
> > > While I got it working with the DOM based reader I noticed
> > > that the stream OM based reader does not find this option
> > > - pls have a look in this module, I left the debug
> > > printouts in the code.
> > >
> > > I'm not familiar with the Stream/OM model, but to me it seems
> > > that this parser omits the setting for the namespace that is
> > > bound to the xml prefix. This namespace is fixed and should be
> > > wired in any parser that is namespace aware (see the constants
> > > file for the namespace definition).
> >
> >
> > I think its a bug in the XML Stream parser which they use as the
> > default. Let me ask for expert's advice about this in axis-dev mailing
> > list.
> >
> > Sanka
> > >
> > > Werner
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: wss4j-dev-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


Re: [Policy] Question / problem in PolicyReader (Stream OM based)

Posted by Davanum Srinivas <da...@gmail.com>.
Sanka,

Please log a JIRA bug, so that we can track it.

thanks,
dims

On 12/9/05, Sanka Samaranayake <ss...@gmail.com> wrote:
> On 12/8/05, Dittmann, Werner <we...@siemens.com> wrote:
> > Sanka,
> >
> > during the tests to check the updates and synchronization
> > of the DOM based reader I also modified the policy2.xml
> > to see if the xml:base option works.
> >
> > While I got it working with the DOM based reader I noticed
> > that the stream OM based reader does not find this option
> > - pls have a look in this module, I left the debug
> > printouts in the code.
> >
> > I'm not familiar with the Stream/OM model, but to me it seems
> > that this parser omits the setting for the namespace that is
> > bound to the xml prefix. This namespace is fixed and should be
> > wired in any parser that is namespace aware (see the constants
> > file for the namespace definition).
>
>
> I think its a bug in the XML Stream parser which they use as the
> default. Let me ask for expert's advice about this in axis-dev mailing
> list.
>
> Sanka
> >
> > Werner
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: wss4j-dev-help@ws.apache.org
>
>


--
Davanum Srinivas : http://wso2.com/blogs/

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


Re: [Policy] Question / problem in PolicyReader (Stream OM based)

Posted by Davanum Srinivas <da...@gmail.com>.
Sanka,

Please log a JIRA bug, so that we can track it.

thanks,
dims

On 12/9/05, Sanka Samaranayake <ss...@gmail.com> wrote:
> On 12/8/05, Dittmann, Werner <we...@siemens.com> wrote:
> > Sanka,
> >
> > during the tests to check the updates and synchronization
> > of the DOM based reader I also modified the policy2.xml
> > to see if the xml:base option works.
> >
> > While I got it working with the DOM based reader I noticed
> > that the stream OM based reader does not find this option
> > - pls have a look in this module, I left the debug
> > printouts in the code.
> >
> > I'm not familiar with the Stream/OM model, but to me it seems
> > that this parser omits the setting for the namespace that is
> > bound to the xml prefix. This namespace is fixed and should be
> > wired in any parser that is namespace aware (see the constants
> > file for the namespace definition).
>
>
> I think its a bug in the XML Stream parser which they use as the
> default. Let me ask for expert's advice about this in axis-dev mailing
> list.
>
> Sanka
> >
> > Werner
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: wss4j-dev-help@ws.apache.org
>
>


--
Davanum Srinivas : http://wso2.com/blogs/

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


Re: [Policy] Question / problem in PolicyReader (Stream OM based)

Posted by Sanka Samaranayake <ss...@gmail.com>.
On 12/8/05, Dittmann, Werner <we...@siemens.com> wrote:
> Sanka,
>
> during the tests to check the updates and synchronization
> of the DOM based reader I also modified the policy2.xml
> to see if the xml:base option works.
>
> While I got it working with the DOM based reader I noticed
> that the stream OM based reader does not find this option
> - pls have a look in this module, I left the debug
> printouts in the code.
>
> I'm not familiar with the Stream/OM model, but to me it seems
> that this parser omits the setting for the namespace that is
> bound to the xml prefix. This namespace is fixed and should be
> wired in any parser that is namespace aware (see the constants
> file for the namespace definition).


I think its a bug in the XML Stream parser which they use as the
default. Let me ask for expert's advice about this in axis-dev mailing
list.

Sanka
>
> Werner
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


Re: [Policy] Question / problem in PolicyReader (Stream OM based)

Posted by Sanka Samaranayake <ss...@gmail.com>.
On 12/8/05, Dittmann, Werner <we...@siemens.com> wrote:
> Sanka,
>
> during the tests to check the updates and synchronization
> of the DOM based reader I also modified the policy2.xml
> to see if the xml:base option works.
>
> While I got it working with the DOM based reader I noticed
> that the stream OM based reader does not find this option
> - pls have a look in this module, I left the debug
> printouts in the code.
>
> I'm not familiar with the Stream/OM model, but to me it seems
> that this parser omits the setting for the namespace that is
> bound to the xml prefix. This namespace is fixed and should be
> wired in any parser that is namespace aware (see the constants
> file for the namespace definition).


I think its a bug in the XML Stream parser which they use as the
default. Let me ask for expert's advice about this in axis-dev mailing
list.

Sanka
>
> Werner
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


Re: [Policy] Question / problem in PolicyReader (Stream OM based)

Posted by Sanka Samaranayake <ss...@gmail.com>.
Hi Werner,

On 12/8/05, Dittmann, Werner <we...@siemens.com> wrote:
> Sanka,
>
> during the tests to check the updates and synchronization
> of the DOM based reader I also modified the policy2.xml
> to see if the xml:base option works.
>
> While I got it working with the DOM based reader I noticed
> that the stream OM based reader does not find this option
> - pls have a look in this module, I left the debug
> printouts in the code.
>
> I'm not familiar with the Stream/OM model, but to me it seems
> that this parser omits the setting for the namespace that is
> bound to the xml prefix. This namespace is fixed and should be
> wired in any parser that is namespace aware (see the constants
> file for the namespace definition).

I think its a bug in the XML Stream parser which they use as the
default. Let me ask for expert's advice about this in axis-dev mailing
list.

Sanka
>
> Werner
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


Adding security for attachments

Posted by Elilvannan Nagarajah <el...@affno.lk>.
Hi all,
       I am using wss4j for adding security for webservices. 
For one case I have to send an invoice (as a file) in a webservice. 
I used the datahandler for this (as attachment).
Then only I realized that wss4j did not support for attachment encryption.
(It put the signature but didn't encrypt the attachment).
I am using axis 1.3 and wss4j 1.o.
(I don't want to use axis2)
Is there other ways to send this file (as java.io.File or ..) within the
soap body part?
Any performance issues....

Could anyone help in this issue?

Thanks and best regards,
N.Elilvannan





---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org


Adding security for attachments

Posted by Elilvannan Nagarajah <el...@affno.lk>.
Hi all,
       I am using wss4j for adding security for webservices. 
For one case I have to send an invoice (as a file) in a webservice. 
I used the datahandler for this (as attachment).
Then only I realized that wss4j did not support for attachment encryption.
(It put the signature but didn't encrypt the attachment).
I am using axis 1.3 and wss4j 1.o.
(I don't want to use axis2)
Is there other ways to send this file (as java.io.File or ..) within the
soap body part?
Any performance issues....

Could anyone help in this issue?

Thanks and best regards,
N.Elilvannan





---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org