Jenkins build is back to normal : woden-trunk » Woden #256

See https://builds.apache.org/job/woden-trunk/org.apache.woden$woden/256/ - To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org

Re: Streaming-WebServices-Security-Framework inclusion into WSS4J

Hi Marc, One thing I would like to discuss is that we move the streaming c14n, signature and encryption code to the Santuario project. It seems like the logical place for it, rather than keep it as part of WSS4J. There is a large number of test vectors in Santuario that we could test the

Re: Streaming-WebServices-Security-Framework inclusion into WSS4J

Hi Amila, 1. After this change will we be able to use WSS4J as we do it now, (As in current release, i.e 1.6.2) without doing major changes to Rampart ? Yes absolutely. The new streaming implementation will not be available until next year I guess, and will appear as a new major version

[jira] [Commented] (AXIOM-383) MTOM has problems when I create an attachtment from a byte array of zero elements

[ https://issues.apache.org/jira/browse/AXIOM-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088564#comment-13088564 ] Hudson commented on AXIOM-383: -- Integrated in ws-axiom-trunk #505 (See

[jira] [Commented] (WSS-305) Migrate to OpenSaml2 2.5.1 from 2.4.1

[ https://issues.apache.org/jira/browse/WSS-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088589#comment-13088589 ] Colm O hEigeartaigh commented on WSS-305: - Hi Gary, Unfortunately there is a bug in

[jira] [Commented] (AXIOM-377) When a multipart message is built, there should be a way to retrieve a DataHandler to the MTOM part without reading the entire incoming stream

[ https://issues.apache.org/jira/browse/AXIOM-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088565#comment-13088565 ] Hudson commented on AXIOM-377: -- Integrated in ws-axiom-trunk #505 (See

[jira] [Updated] (WSS-305) Migrate to OpenSaml2 2.5.1 from 2.4.1

[ https://issues.apache.org/jira/browse/WSS-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-305: Fix Version/s: 1.6.3 Migrate to OpenSaml2 2.5.1 from 2.4.1

[jira] [Commented] (WODEN-231) Woden parsing error found when deploying service AAR in simple Axis2 server

[ https://issues.apache.org/jira/browse/WODEN-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088650#comment-13088650 ] Sagara Gunathunga commented on WODEN-231: -- Hi Ping, Did you able to make any

[jira] [Updated] (WSS-312) Improve logging levels

[ https://issues.apache.org/jira/browse/WSS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Sharma updated WSS-312: --- Attachment: 0001-Improved-logging-levels.patch Improved logging levels. Instead of exceptions being

[jira] [Commented] (WSS-305) Migrate to OpenSaml2 2.5.1 from 2.4.1

[ https://issues.apache.org/jira/browse/WSS-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088658#comment-13088658 ] Gary D. Gregory commented on WSS-305: - Hi Colm, Are you sure you are talking about

[jira] [Commented] (WSS-305) Migrate to OpenSaml2 2.5.1 from 2.4.1

[ https://issues.apache.org/jira/browse/WSS-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088660#comment-13088660 ] Colm O hEigeartaigh commented on WSS-305: - Hi Gary, The problem is in the Opensaml

[jira] [Commented] (WSS-305) Migrate to OpenSaml2 2.5.1 from 2.4.1

[ https://issues.apache.org/jira/browse/WSS-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088670#comment-13088670 ] Gary D. Gregory commented on WSS-305: - Hi Colm, Arg! I created

[jira] [Commented] (WSS-305) Migrate to OpenSaml2 2.5.1 from 2.4.1

[ https://issues.apache.org/jira/browse/WSS-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088681#comment-13088681 ] Colm O hEigeartaigh commented on WSS-305: - The same problem exists for xmltooling

[jira] [Commented] (WSS-312) Improve logging levels

[ https://issues.apache.org/jira/browse/WSS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088718#comment-13088718 ] Daniel Kulp commented on WSS-312: - I have to say that I disagree with this patch.This is

[jira] [Commented] (WSS-312) Improve logging levels

[ https://issues.apache.org/jira/browse/WSS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088731#comment-13088731 ] Andreas Veithen commented on WSS-312: - I fully agree with Dan's comment. This is indeed

Re: [jira] [Commented] (WODEN-231) Woden parsing error found when deploying service AAR in simple Axis2 server

Hi Sagara, I've been working on this issue. I traced down to where the code is broken. So should be able to identify it soon? But the project in my job is now entering critical stage so I have to spend all time on it. But thanks for asking. I'll try to have it done by this weekend. Thanks

[jira] [Commented] (AXIOM-377) When a multipart message is built, there should be a way to retrieve a DataHandler to the MTOM part without reading the entire incoming stream

[ https://issues.apache.org/jira/browse/AXIOM-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088925#comment-13088925 ] Hudson commented on AXIOM-377: -- Integrated in ws-axiom-trunk #506 (See