Ah, that explains!
Why is that the correct behavior ?
Packet.getApplicationPropertyScopeNames(boolean) is deprecated. So what
would be the correct way to set it ?
-Arun
Rama Pulavarthi wrote:
> I fixed the RI to consider any non-standard property to default to
> handler scope.
> Unless you specify this is in Application scope, it won't appear in
> response context.
>
>
> thanks,
> Rama Pulavarthi
>
> Arun Gupta wrote:
>> Another data point ...
>>
>> With #1212, this property is not in handler scope.
>>
>> -Arun
>>
>> Arun Gupta wrote:
>>>>> Somewhere after JAX-WS #1212, response context on BindingProvider
>>>>> is returning AddressingContext (a javax.xml.* property as of now)
>>>>> as null even though it's present in
>>>>> responseContext.packet.invocationProperties.
>>>>
>>>> What about scope? Is it in Handler scope by chance ?
>>> It turned out it is in handler scope. This code has not changed in
>>> JAX-WSA for few months.
>>>
>>> Has the behavior changed in JAX-WS after #1212 though ?
>>>
>>> This is how I'm adding the properties:
>>>
>>> packet.invocationProperties.put(JAXWSAConstants.CLIENT_ADDRESSING_PROPERTIES,
>>> ap);
>>>
>>> -Arun
>>>
>>>>
>>>> Jitu
>>>>
>>>>>
>>>>> I'll debug this tomorrow but in the meanwhile does anybody know
>>>>> what might have caused this ?
>>>>>
>>>>> -Arun
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
>>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
>
--
got Web Services ?
Download and Contribute Web Services Interoperability Technology (WSIT)
http://java.sun.com/webservices/interop