Re: RM CloseSequence message with the wrong Sequence header

2014-05-14 Thread Dennis Sosnoski
Hi Aki, We definitely don't want that Sequence header on the CloseSequence message. That code has been in place since I split the interceptors, so it's probably just a mistake from when I was doing the split. I'll take out the added clause on the if. Thanks for catching this, Aki! - Denni

Re: CXF 3.0 builds tomorrow....

2014-05-14 Thread Aki Yoshida
For the problem that we thought there is, an empty partial response being returned as an soap envelope with http 202 was a ghost. On the network, the soap content is definitely not sent. I see each request is returned with the expected 202 response, as HTTP/1.1 202 Accepted Content-Type: text/xml;

Re: RM CloseSequence message with the wrong Sequence header

2014-05-14 Thread Aki Yoshida
committed the correction. 2014-05-14 12:01 GMT+02:00 Aki Yoshida : > Hi Dennis, > after playing around the modified code that omits this handling, I > discovered that that special handling is needed for RM 1.0. because RM > 1.0. has a pseudo CloseSequence behavior using its lastMessage action. >

Re: RM CloseSequence message with the wrong Sequence header

2014-05-14 Thread Aki Yoshida
Hi Dennis, after playing around the modified code that omits this handling, I discovered that that special handling is needed for RM 1.0. because RM 1.0. has a pseudo CloseSequence behavior using its lastMessage action. I'll run some more tests with the corrected modification and submit this change

Re: RM CloseSequence message with the wrong Sequence header

2014-05-14 Thread Dennis Sosnoski
Yes, I'd already found this out and made the change so the added header is only with RM 1.0. I'm just making sure the merge is good before pushing. Thanks, - Dennis On 05/14/2014 10:01 PM, Aki Yoshida wrote: Hi Dennis, after playing around the modified code that omits this handling, I disco

Re: CXF 3.0 builds tomorrow....

2014-05-14 Thread Daniel Kulp
Thanks Aki and Dennis, Things are looking good. I’ve just reviewed the NOTICE/LICENSE stuff and that looks OK. Did a little more testing and things look fine for 3.0. I think anything left can push to 3.0.1. Thus, I plan on starting the builds shortly. Shout ASAP if there’s an issue.

Re: git commit: Reorder some of hte calls to get the createSequence stuff occuring immediately to fix the tests

2014-05-14 Thread Dennis Sosnoski
I reverted the change yesterday, so let me know if you're still seeing any problems. I don't know why I didn't see the issues with the integration tests, which led to Dan changing the order, before I checked in the original change. Normally I run the RM integration tests before every commit. So