Hi Jiandong,
With the newer wsit & jaxws 2.1 code that particular problem doesn't
happen. The test still fails but the current problem is a bug in the
test harness itself... there is a bug in 'patching' the location of the
STS endpoint for use with local transport. I'm working on correcting
that and should have it fixed today. I'll let you know whether the test
is successful or not as soon as I can. I'm excited to see it work finally.
Thanks a lot for following up!
Ken
Jiandong Guo wrote:
> Hi Ken,
>
> How is going with this?
>
> Jiandong
>
> Ken Hofsass wrote:
>
>> Jiandong,
>>
>> I know you're probably swamped with the jaxws 2.1 migration right
>> now, but when you have a chance I would appreciate your help on the
>> following issue...
>>
>> The wstrust test (scenario5) we've automated with the harness fails.
>> The failure is caused by SecurityServerPipe.process() calling into
>> Packet.getApplicationScopedProperties() with
>> Constants.SUN_TRUST_SERVER_SECURITY_POLICY_NS.
>> In the last pre-jaxws2.1 version of SecurityServerPipe.java (1.13)
>> it's at line 215 or line 187 in the latest version (1.14). I'm using
>> the WSIT tree from Monday afternoon, a few hours before Arun checked
>> in the JAXWS 2.1 jars.
>>
>> Kohsuke changed getApplicationScopedProperties to 'assert false'
>> immediately a while back. This seems to indicate that the test
>> harness run is getting in a block of code in
>> SecurityServerPipe.process() that is not normally executed...
>>
>> This failure code path might occur because the harness is using local
>> transport. (I'll try it with http and see if happens too). Or it
>> could be a bug or config error with the e2e harness. If you could
>> take a look and let me know if you see anything obvious, that would
>> be great.
>>
>> thanks,
>> Ken
>>