Hi Manveen, Jiandong,
The security & SC tests that you are running, are they standalone tests
or using the e2e harness [1]? Hudson shows 4 failures for security &
two for SC even with the latest changes (which fixed the other XWSS & SC
test failures).
If you're using the harness, how did you run your tests? (that is, 'ant'
or directly with 'java') What transport did you use? (local or http)
I'm asking because I want to make sure the e2e harness is working
properly, esp. on hudson. And since e2e test runs on hudson are not
showing the same results, I'm trying to figure out what's causing the
discrepancy.
thanks,
Ken
[1]
http://kohsuke.sfbay/hudson/job/wsit-e2e-test-local
Manveen Kaur wrote:
> Arun Gupta wrote:
>
>> [s/pteam/tech]
>>
>> The WSDL does not have any UsingAddressing assertion. I added that
>> assertion (in W3C namespace) for xwss/s1 and the saw the correct set
>> of WS-A headers on request and response message. However if I change
>> the UsingAddressing namespace to MemberSubmission then I can
>> reproduce this NPE.
>>
>> I fixed the problem in JAX-WS and AddressingModelConfiguratorProvider
>> and now can see the correct set of WS-A headers in xwss/s1 and s2
>> scenarios. I tried s1 in both W3C and Member submission and saw the
>> correct headers.
>>
>> Manveen/Jiandong,
>>
>> Can you try rest of the scenarios and let me know if you see any
>> other issues ?
>>
>> -Arun
>
> Just to confirm that I also ran all the security e2e tests and they
> passed with the latest fix.
>
> Thanks,
> Manveen