Still waiting for a response ...
Arun Gupta wrote:
> The default properties added to Packet were in handler scope to begin
> with, then changed to application scope and it seems like now they are
> back to handler scope.
>
> I'm still looking for how to set application-scoped property names in
> WS-A pipe. Packet.getApplicationPropertyScopeNames(boolean) is
> deprecated. I think either deprecation should be removed or there be
> another way to set application-scoped property.
>
> Packet.getHandlerScopePropertyNames(true).remove(...) does not look very
> intuitive.
>
> -Arun
>
>
> Rama Pulavarthi wrote:
>> I agree.
>> What the spec says is only properties with Application Scope are
>> copied to response context.
>> So, when you set any property and want it to be available in response
>> context, make sure it has application scope.
>> Supposedly , additional properties should come only from a handler,
>> where one can set scope for a property.
>>
>> In this case, this additional property is set on a Packet in a WSA
>> Pipe and needs to be available in response context, make it available
>> on the Packet such that packet.supports(prop) through
>> DistributedPropertySet . If it returns true, we don't check scope of
>> the property.
>>
>> thanks,
>> Rama Pulavarthi
>>
>>
>> kathy walsh wrote:
>>> ResponseContext as represented in the jaxws 2.0 spec and docs
>>> does not have a way to set the scope-
>>> Kathy
>>>
>>> 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
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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