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.
Why is that so? I thought it would be unusual to create a new SU for each endpoint. What is really strange is my coworker put together a demo that does something similar but with some BPEL inside and it worked for him several months ago (3.1-SNAPSHOT). And he can't figure out why mine isn't working, especially since I used his project as an example.
Have you tried to establish the same thing with 2 different service units?
I create a new SU and then put the consumer in one and the provider in the other. I think this is when I got a 302 when I called my web service with SOAP-UI but I don't remember for sure. I can live without the WSDL but I need the SOAP call to work. I then deleted my entire project and started again from scratch. I got the same result.
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"
I don't understand this, that's what I had.
