You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Scott Kurz <sc...@gmail.com> on 2006/04/26 19:45:42 UTC
EntryPoint name must match wired-to Service name?
I'm observing an issue (running April 17th SVN contents) and I'm not sure if
this is a bug or a limitation with the current Tuscany implementation or if
this is working according to the 0.9 spec (in which case I'm not
understanding it).
The issue is that with a WS binding you currently need (unnecessarily in my
opinion) to match the EntryPoint name with the name of the Service it is
wired to via the <references> tag.
So, for example, in the HelloWorld WS sample's sca.module file, you have:
<entryPoint name="HelloWorldService">
<interface.wsdl interface="
http://helloworldaxis.samples.tuscany.apache.org#HelloWorldServiceImpl"/>
<binding.ws port="
http://helloworldaxis.samples.tuscany.apache.org#helloworld"/>
<reference>HelloWorldServiceComponent/HelloWorldService</reference>
</entryPoint>
It seems to me you should be able to rename the entryPoint as:
<entryPoint name="HelloWorldServiceEP">
but be able to keep the reference as:
<reference>HelloWorldServiceComponent/HelloWorldService</reference>
I don't see that the spec requires that the two names be the same, but when
I tried this recently in Tomcat I had this problem.
Does anyone not think I should open a JIRA? I didn't see one for this
issue.
Thanks,
Scott
Re: EntryPoint name must match wired-to Service name?
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Scott Kurz wrote:
> I'm observing an issue (running April 17th SVN contents) and I'm not sure if
> this is a bug or a limitation with the current Tuscany implementation or if
> this is working according to the 0.9 spec (in which case I'm not
> understanding it).
>
> The issue is that with a WS binding you currently need (unnecessarily in my
> opinion) to match the EntryPoint name with the name of the Service it is
> wired to via the <references> tag.
>
> So, for example, in the HelloWorld WS sample's sca.module file, you have:
>
> <entryPoint name="HelloWorldService">
> <interface.wsdl interface="
> http://helloworldaxis.samples.tuscany.apache.org#HelloWorldServiceImpl"/>
> <binding.ws port="
> http://helloworldaxis.samples.tuscany.apache.org#helloworld"/>
> <reference>HelloWorldServiceComponent/HelloWorldService</reference>
> </entryPoint>
>
> It seems to me you should be able to rename the entryPoint as:
>
> <entryPoint name="HelloWorldServiceEP">
>
> but be able to keep the reference as:
>
> <reference>HelloWorldServiceComponent/HelloWorldService</reference>
>
> I don't see that the spec requires that the two names be the same, but when
> I tried this recently in Tomcat I had this problem.
>
> Does anyone not think I should open a JIRA? I didn't see one for this
> issue.
>
> Thanks,
> Scott
>
>
Scott, I think it's a bug and yes you can open a JIRA for it. Thanks!
--
Jean-Sebastien
Re: EntryPoint name must match wired-to Service name?
Posted by Jim Marino <jm...@myromatours.com>.
Nevermind,
'
I just saw the JIRA. Thanks.
Jim
On Apr 26, 2006, at 12:31 PM, Jim Marino wrote:
> Could you post a stack trace?
>
> Thanks,
> Jim
>
>
> On Apr 26, 2006, at 10:45 AM, Scott Kurz wrote:
>
>
>> I'm observing an issue (running April 17th SVN contents) and I'm
>> not sure if
>> this is a bug or a limitation with the current Tuscany
>> implementation or if
>> this is working according to the 0.9 spec (in which case I'm not
>> understanding it).
>>
>> The issue is that with a WS binding you currently need
>> (unnecessarily in my
>> opinion) to match the EntryPoint name with the name of the Service
>> it is
>> wired to via the <references> tag.
>>
>> So, for example, in the HelloWorld WS sample's sca.module file,
>> you have:
>>
>> <entryPoint name="HelloWorldService">
>> <interface.wsdl interface="
>> http://
>> helloworldaxis.samples.tuscany.apache.org#HelloWorldServiceImpl"/>
>> <binding.ws port="
>> http://helloworldaxis.samples.tuscany.apache.org#helloworld"/>
>> <reference>HelloWorldServiceComponent/HelloWorldService</
>> reference>
>> </entryPoint>
>>
>> It seems to me you should be able to rename the entryPoint as:
>>
>> <entryPoint name="HelloWorldServiceEP">
>>
>> but be able to keep the reference as:
>>
>> <reference>HelloWorldServiceComponent/HelloWorldService</
>> reference>
>>
>> I don't see that the spec requires that the two names be the same,
>> but when
>> I tried this recently in Tomcat I had this problem.
>>
>> Does anyone not think I should open a JIRA? I didn't see one for
>> this
>> issue.
>>
>> Thanks,
>> Scott
>>
>>
>
>
Re: EntryPoint name must match wired-to Service name?
Posted by Jim Marino <jm...@myromatours.com>.
Could you post a stack trace?
Thanks,
Jim
On Apr 26, 2006, at 10:45 AM, Scott Kurz wrote:
> I'm observing an issue (running April 17th SVN contents) and I'm
> not sure if
> this is a bug or a limitation with the current Tuscany
> implementation or if
> this is working according to the 0.9 spec (in which case I'm not
> understanding it).
>
> The issue is that with a WS binding you currently need
> (unnecessarily in my
> opinion) to match the EntryPoint name with the name of the Service
> it is
> wired to via the <references> tag.
>
> So, for example, in the HelloWorld WS sample's sca.module file, you
> have:
>
> <entryPoint name="HelloWorldService">
> <interface.wsdl interface="
> http://
> helloworldaxis.samples.tuscany.apache.org#HelloWorldServiceImpl"/>
> <binding.ws port="
> http://helloworldaxis.samples.tuscany.apache.org#helloworld"/>
> <reference>HelloWorldServiceComponent/HelloWorldService</
> reference>
> </entryPoint>
>
> It seems to me you should be able to rename the entryPoint as:
>
> <entryPoint name="HelloWorldServiceEP">
>
> but be able to keep the reference as:
>
> <reference>HelloWorldServiceComponent/HelloWorldService</
> reference>
>
> I don't see that the spec requires that the two names be the same,
> but when
> I tried this recently in Tomcat I had this problem.
>
> Does anyone not think I should open a JIRA? I didn't see one for this
> issue.
>
> Thanks,
> Scott
>