Well, you're still using different endpoint names.

> <http:endpoint ...
>                endpoint="BookServiceHttpPort"
> <http:endpoint ...
>                endpoint="bookServiceConsumerEndpoint"
...
>                targetEndpoint="bookServiceProviderEndpoint"

I don't have code for your particular example, but take a look at this:

Consumer:
>>
<http:endpoint service="tsys:SensorDataService"
                 endpoint="SensorDataServiceSOAPPort"
                 role="consumer"
.../>
<<
Provider:
>>
<jsr181:endpoint
                endpoint="SensorDataServiceSOAPPort"
.../>
<<

In MC4J, this gives me *one* endpoint with a name 
{http___...}SensorDataServiceSensorDataServiceSOAPPort with 2 sub types, 
internal and external.

Hope this helps,
Ciao,
Philipp

> -----Mensaje original-----
> De: Michael Mattox [mailto:[EMAIL PROTECTED]
> Enviado el: miércoles, 30 de mayo de 2007 19:20
> Para: [email protected]
> Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> Importancia: Baja
>
> Changed it to:
>
> <http:endpoint service="test:BookService"
>                endpoint="BookServiceHttpPort"
>                role="provider"
>                soapVersion="1.1"
>                soap="true"
>                locationURI="http://127.0.0.1:8080/test-business-
> service/services/BookService"
>                />
>
> <http:endpoint service="test:BookService"
>                endpoint="bookServiceConsumerEndpoint"
>                targetService="test:BookService"
>                targetEndpoint="bookServiceProviderEndpoint"
>                role="consumer"
>                locationURI="http://0.0.0.0:8192/BookService/";
>                defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
>                soapVersion="1.1"
>                soap="true"
>                />
>
>
> I get the same error as before.
>
> What is weird is a friend has used servicemix to do this and he spent
> yesterday afternoon with me and he couldn't figure it out either.
>
>
> On 5/30/07, Rossmanith, Philipp <[EMAIL PROTECTED]> wrote:
> >
> > No worries. The name of the endpoint attribute in your xbean.xml; try
> setting it to the name of the port.
> >
> > Please note that endpoint is a WSDL 2.0 term, whereas your WSDL is 1.1.
> >
> > Ciao,
> > Philipp
> >
> > > -----Mensaje original-----
> > > De: Michael Mattox [mailto:[EMAIL PROTECTED]
> > > Enviado el: miércoles, 30 de mayo de 2007 17:56
> > > Para: [email protected]
> > > Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> > > Importancia: Baja
> > >
> > > Philipp,
> > >
> > > Try setting what to the name of the port?  (sorry I'm new at this)
> > >
> > > Thanks,
> > > Michael
> > >
> > > On 5/30/07, Rossmanith, Philipp <[EMAIL PROTECTED]>
> wrote:
> > > >
> > > > Hi Michael,
> > > >
> > > > Try setting it to the name of the port: BookServiceHttpPort.
> > > >
> > > > Have you tried making the Web service accessible via ServiceMix
> without
> > > establishing a consumer endpoint for it?
> > > >
> > > > If so, was it visible via JMX?
> > > >
> > > > Ciao,
> > > > Philipp
> > > >
> > > > > -----Mensaje original-----
> > > > > De: Michael Mattox [mailto:[EMAIL PROTECTED]
> > > > > Enviado el: miércoles, 30 de mayo de 2007 17:41
> > > > > Para: [email protected]
> > > > > Asunto: Re: 404 Unable to find requested resource when requesting
> WSDL
> > > > > Importancia: Baja
> > > > >
> > > > > I just searched the WSDL and do not find the word "endpoint" at
> all.
> > > > > I am attaching the WSDL.
> > > > >
> > > > > I get the same result:
> > > > >
> > > > > 17:38:15,998 | DEBUG | btpool0-1  | HttpComponent            |
> > > > > e.servicemix.soap.SoapEndpoint  276 | Retrieving proxied endpoint
> > > > > definition
> > > > > 17:38:15,998 | DEBUG | btpool0-1  | HttpComponent            |
> > > > > icemix.common.DefaultComponent   79 | Querying service description
> for
> > > > >
> > >
> ServiceEndpoint[service={http://xfire.codehaus.org}BookService,endpoint=bo
> > > > > okServiceProviderEndpoint]
> > > > > 17:38:15,998 | DEBUG | btpool0-1  | HttpComponent            |
> > > > > icemix.common.DefaultComponent   87 | No description found for
> > > > > {http://xfire.codehaus.org}BookService:bookServiceProviderEndpoint
> > > > >
> > > > > This tells me that servicemix is making the connection from the
> > > > > consumer to the provider, and that it cannot locate the provider.
> > > > > Which I don't understand because it's in the xbean.xml, pasted
> again
> > > > > here for reference:
> > > > >
> > > > > <beans xmlns:http="http://servicemix.apache.org/http/1.0";
> > > > >          xmlns:test="http://xfire.codehaus.org";>
> > > > >
> > > > > <http:endpoint service="test:BookService"
> > > > >                endpoint="bookServiceProviderEndpoint"
> > > > >                role="provider"
> > > > >                soapVersion="1.1"
> > > > >                soap="true"
> > > > >                locationURI="http://127.0.0.1:8080/test-business-
> > > > > service/services/BookService"
> > > > >                />
> > > > >
> > > > > <!--
> > > > >                targetService="test:BookService"
> > > > > -->
> > > > >
> > > > > <http:endpoint service="test:BookService"
> > > > >                endpoint="bookServiceConsumerEndpoint"
> > > > >                targetService="test:BookService"
> > > > >                targetEndpoint="bookServiceProviderEndpoint"
> > > > >                role="consumer"
> > > > >                locationURI="http://0.0.0.0:8192/BookService/";
> > > > >                defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
> > > > >                soapVersion="1.1"
> > > > >                soap="true"
> > > > >                />
> > > > >
> > > > >
> > > > > </beans>
> > > > >
> > > > >
> > > > > On 5/30/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote:
> > > > > > Michael,
> > > > > >
> > > > > > Isn't it possible that the webservice you're targeting is also
> > > called
> > > > > > bookServiceEndpoint?  If not, can you try to revert to different
> > > > > > endpoint names and add a targetService and targetEndpoint
> attribute
> > > to
> > > > > > your consumer end?
> > > > > >
> > > > > > Gert
> > > > > >
> > > > > > Michael Mattox wrote:
> > > > > > >> I haven't tried your particular setup yet, but from my
> experience
> > > > > both
> > > > > > >> the service and the endpoint names need to match between a
> > > consumer
> > > > > > >> and a provider.
> > > > > > >> >                endpoint="providerBookService"
> > > > > > >> >                endpoint="consumerBookService"
> > > > > > >>
> > > > > > >> Hope that helps.
> > > > > > >
> > > > > > > Philipp, thanks for the suggestion.  I just set the two
> endpoints
> > > to
> > > > > > > "bookServiceEndpoint" and I get this error:
> > > > > > >
> > > > > > > <loc-message>More than one endpoint found in the SU for key:
> > > > > > > {http://xfire.codeh
> > > > > > > aus.org}BookService:bookServiceEndpoint</loc-message>
> > > > > > >
> > > > > > > -Michael
> > > > > > >
> > > > > >
> > > >
> > > > This e-mail may contain confidential or privileged information. Any
> > > unauthorised
> > > > copying, use or distribution of this information is strictly
> prohibited.
> > > >
> >
> > This e-mail may contain confidential or privileged information. Any
> unauthorised
> > copying, use or distribution of this information is strictly prohibited.
> >

This e-mail may contain confidential or privileged information. Any unauthorised
copying, use or distribution of this information is strictly prohibited.

Reply via email to