Though the jbi.xml descriptor in the standard doesn't seem to inhibit
several endpoints in one service unit, your setup with establishing 2
endpoints in one xbean seems a bit inusual.
Have you tried to establish the same thing with 2 different service
units?
> > > > > > > <loc-message>More than one endpoint found in the SU for
key:
> > > > > > > {http://xfire.codeh
> > > > > > > aus.org}BookService:bookServiceEndpoint</loc-message>
Have you tried to name the endpoints differently, but let the target
endpoint of the consumer unit point to the endpoint of the provider?
> > > <http:endpoint ...
> > > endpoint="BookServiceHttpPort"
> > > <http:endpoint ...
> > > endpoint="bookServiceConsumerEndpoint"
> > ...
> > > targetEndpoint="BookServiceHttpPort"
Ciao,
Philipp
> -----Mensaje original-----
> De: Michael Mattox [mailto:[EMAIL PROTECTED]
> Enviado el: jueves, 31 de mayo de 2007 13:06
> Para: [email protected]
> Asunto: Re: 404 Unable to find requested resource when requesting WSDL
> Importancia: Baja
>
> > Well, you're still using different endpoint names.
> >
> > > <http:endpoint ...
> > > endpoint="BookServiceHttpPort"
> > > <http:endpoint ...
> > > endpoint="bookServiceConsumerEndpoint"
> > ...
> > > targetEndpoint="bookServiceProviderEndpoint"
>
> If I use the same name I get the parsing error and my SA won't start.
>
> > I don't have code for your particular example, but take a look at
this:
> > Provider:
> > <jsr181:endpoint
> > endpoint="SensorDataServiceSOAPPort"
> > .../>
>
> I think the difference is your example uses jsr181 and I'm using http.
>
> Thanks
> Michael
This e-mail may contain confidential or privileged information. Any unauthorised
copying, use or distribution of this information is strictly prohibited.
