You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Rania Khalaf <rk...@watson.ibm.com> on 2006/08/18 20:01:31 UTC
HelloworldE4xws sample, M1
Hi,
I have two quick questions about how the M1 helloworld e4x sample is
working. Basically, the naming conventions seem off which is quite
confusing.
I was looking at the M1 samples in order to understand how the URLs are
created for deployed WS.
It was under the impression that it is: http:/[host]:[portnum]/[name
of webapps subdirectory]/services/[entry point name]
1) the e4x hellworld sample uses the same url in its port as that for
the pojo helloworld sample:
location="http://localhost:8080/sample-helloworldws/services/HelloWorldWebService"
It also says to use the same client as the POJO sample. Why is that
not 'helloworlde4xws' after the port number since that is the name of
the webapps dir where this sample is?
2)The reference element in an entry point is usually
componentName/serviceName. The helloworld pojo sample does that exactly,
using:
<reference>HelloWorldServiceComponent/HelloWorldService</reference>
But the E4X one drops the service name (even though it does define it in
its componentType side file) in its reference element:
<reference>HelloWorldComponent</reference>
Can anyone please clarify whether the sample is correct, and if so how
come it works ?
Maybe: things defaulting to certain values somewhere ? is there a
precedence order for clashing URLs? is the port element ignored
altogether ? are we supposed to only deploy one or the other of the ws
samples and use the same directory name in the tomcats webapps dir ?
thanks,
Rania
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: HelloworldE4xws sample, M1
Posted by Rania Khalaf <rk...@watson.ibm.com>.
Hi Ant,
Did eventually trace the js client through JSON and on to the Axis
binding into the e4xws sample :)
Missed the js the first time.
thanks for the tip on the optional service name.
thanks,
Rania
ant elder wrote:
> Hi Rania,
>
> In the M1 code the WS entryPoint ignores the endpoint value of the
> port in
> the WSDL, it is as you say: http:/[host]:[portnum]/[name of webapps
> subdirectory]/services/[entry point name]
>
> The readme for helloworlde4xws actually says use the
> helloworldjsclient not
> the helloworldwsclient (thats _js_ not _ws_). That JavaScript client has
> separate buttons to invoke the e4x or ws samples. If you look at the
> sca.module file for the helloworldjsclient you'll see it has separate
> externalService definitions for each web service it uses and thats
> where the
> different endpoints are defined.
>
> The service name is optional in a reference if the component only
> exposes a
> singe service so it was left off in the sample to keep things simple.
>
> ...ant
>
> On 8/18/06, Rania Khalaf <rk...@watson.ibm.com> wrote:
>
>>
>> Hi,
>>
>> I have two quick questions about how the M1 helloworld e4x sample is
>> working. Basically, the naming conventions seem off which is quite
>> confusing.
>>
>> I was looking at the M1 samples in order to understand how the URLs are
>> created for deployed WS.
>> It was under the impression that it is: http:/[host]:[portnum]/[name
>> of webapps subdirectory]/services/[entry point name]
>>
>> 1) the e4x hellworld sample uses the same url in its port as that for
>> the pojo helloworld sample:
>> location="
>> http://localhost:8080/sample-helloworldws/services/HelloWorldWebService"
>>
>> It also says to use the same client as the POJO sample. Why is that
>> not 'helloworlde4xws' after the port number since that is the name of
>> the webapps dir where this sample is?
>>
>> 2)The reference element in an entry point is usually
>> componentName/serviceName. The helloworld pojo sample does that exactly,
>> using:
>> <reference>HelloWorldServiceComponent/HelloWorldService</reference>
>> But the E4X one drops the service name (even though it does define it in
>> its componentType side file) in its reference element:
>> <reference>HelloWorldComponent</reference>
>>
>> Can anyone please clarify whether the sample is correct, and if so how
>> come it works ?
>>
>> Maybe: things defaulting to certain values somewhere ? is there a
>> precedence order for clashing URLs? is the port element ignored
>> altogether ? are we supposed to only deploy one or the other of the ws
>> samples and use the same directory name in the tomcats webapps dir ?
>>
>> thanks,
>> Rania
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: HelloworldE4xws sample, M1
Posted by ant elder <an...@gmail.com>.
Hi Rania,
In the M1 code the WS entryPoint ignores the endpoint value of the port in
the WSDL, it is as you say: http:/[host]:[portnum]/[name of webapps
subdirectory]/services/[entry point name]
The readme for helloworlde4xws actually says use the helloworldjsclient not
the helloworldwsclient (thats _js_ not _ws_). That JavaScript client has
separate buttons to invoke the e4x or ws samples. If you look at the
sca.module file for the helloworldjsclient you'll see it has separate
externalService definitions for each web service it uses and thats where the
different endpoints are defined.
The service name is optional in a reference if the component only exposes a
singe service so it was left off in the sample to keep things simple.
...ant
On 8/18/06, Rania Khalaf <rk...@watson.ibm.com> wrote:
>
> Hi,
>
> I have two quick questions about how the M1 helloworld e4x sample is
> working. Basically, the naming conventions seem off which is quite
> confusing.
>
> I was looking at the M1 samples in order to understand how the URLs are
> created for deployed WS.
> It was under the impression that it is: http:/[host]:[portnum]/[name
> of webapps subdirectory]/services/[entry point name]
>
> 1) the e4x hellworld sample uses the same url in its port as that for
> the pojo helloworld sample:
> location="
> http://localhost:8080/sample-helloworldws/services/HelloWorldWebService"
>
> It also says to use the same client as the POJO sample. Why is that
> not 'helloworlde4xws' after the port number since that is the name of
> the webapps dir where this sample is?
>
> 2)The reference element in an entry point is usually
> componentName/serviceName. The helloworld pojo sample does that exactly,
> using:
> <reference>HelloWorldServiceComponent/HelloWorldService</reference>
> But the E4X one drops the service name (even though it does define it in
> its componentType side file) in its reference element:
> <reference>HelloWorldComponent</reference>
>
> Can anyone please clarify whether the sample is correct, and if so how
> come it works ?
>
> Maybe: things defaulting to certain values somewhere ? is there a
> precedence order for clashing URLs? is the port element ignored
> altogether ? are we supposed to only deploy one or the other of the ws
> samples and use the same directory name in the tomcats webapps dir ?
>
> thanks,
> Rania
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>