Dan Diephouse wrote:
On 4/2/07, Polar Humenn <[EMAIL PROTECTED]> wrote:
Dan Diephouse wrote:
> The problem is this line:
>
> EndpointImpl ep =
> new EndpointImpl(
> getBus(),
> implementor1,
> "http://apache.org/hello_world";,
>
> this.getClass().getResource("resources/greeting.wsdl"));
>
> Before we were ignoring the 3rd paramter - which is supposed to be the
> Binding URI. It has nothing to do with the target namespace. You don't
> want
> to be passing anything in there I'm guessing :-) So just make it null.
>
I guess, I was only guessing?
You think, maybe problems like this might be alleviated by
documentation?
Oh, I forgot about "Comment rot"!
How about naming the parameter "bindingURI"?
:-) I will fix this in my copy and commit it with my next commit.
I'd still like to know how I figure out the "configuration" name of the
Http-destination from this call.
<http:destination id="{
http://apache.org/hello_world}Mortimer.http-destination";>
</http:destination>
id = {targetNamespace}PortName.http-destination
I should have explained myself better.
If you noticed the WSDL file contains about multiple ports with
localhost addresses from 9000-9009.
It is ep.publish(address) that actually selects the port name, not the
constructor, right? which is of course, is just luck that it's defined
in the WSDL, correct?
If you look at the WSDL and I then give this call
ep.publish("http://localhost:12000/";);
It seems to work -- the endpoint goes up at port 12000. Yet, I have no
idea what the port name or the target namespace is, and subsequently the
http-destination is also unknown (to me) at this point.
How do I figure this out? What target namespace and what port name got
assigned?
Cheers,
-Polar
Cheers,
- Dan
