Hi Kathy, I'm back from vacation now... I just wanted to check if you'd
found any problems related to the endpointAddress value in the test
harness. -- thanks, Ken
kathy walsh wrote:
> Ken,
> I'll take a look at the RM example.
> The endpointAddress supplied by the client program
> should be the endpoint that a dispatch invocation
> hits-
> Kathy
>
> Ken Hofsass wrote:
>
>> Hi Kohsuke, Kathy,
>>
>> Kohsuke Kawaguchi wrote:
>>
>>> The dispatch is bit tricky with this respect, because the test code
>>> needs to set the endpoint address, which is otherwise hidden by the
>>> harness. And my current thinking is that we just export variable
>>> 'endpointAddress' into the test code (for the test code to create a
>>> dispatch), and I think this still allow the harness to control the
>>> communication channel.
>>
>>
>>
>> Please forgive my inexperience here but I'm not sure why
>> 'endpointAddress' is required to be exposed directly? My chnages do
>> make 'endpointAddress' available in the beanshell environment. (well
>> the first one, if multiple, but that's a different issue). However,
>> the RM example worked even before that value was made visible to the
>> scripts (which don't use it anyhow).
>>
>> Maybe it was just the particular example (the RM dispatch test) that
>> I started with but I didn't see where that would be used. Looking at
>> the JAX-WS dispatch sample, again, I didn't see where the
>> endpointAddress was being used directly in the user's code.
>>
>> Can one of you point me to an example?
>>
>> thanks,
>> Ken
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_ws-test-harness.dev.java.net
>> For additional commands, e-mail: dev-help_at_ws-test-harness.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_ws-test-harness.dev.java.net
> For additional commands, e-mail: dev-help_at_ws-test-harness.dev.java.net
>