On Thu, Feb 16, 2012 at 4:00 AM, Greg Dritschler
greg.dritsch...@gmail.com wrote:
For something that seems so simple, this is turning into a quagmire.
The web service binding processor is not the best place to test intents
because the builder obviously has not yet run and propagated intents
I was thinking about having the WebServiceBindingBuilder perform the port
selection. It calls the WebServiceBinding methods getBinding(),
setBinding(), and setGeneratedWSDLDocument() which
drive determineWSDLCharacteristics() under the covers. It seems like this
should be done consistently with
When a web service binding uses wsdl.service, WebServiceBindingProcessor
picks the first port.
if (model.getPortName() != null) {
port =
service.getElement().getPort(model.getPortName());
} else {
// BWS20006
On Wed, Feb 15, 2012 at 4:58 PM, Greg Dritschler
greg.dritsch...@gmail.com wrote:
When a web service binding uses wsdl.service, WebServiceBindingProcessor
picks the first port.
if (model.getPortName() != null) {
port =
For something that seems so simple, this is turning into a quagmire.
The web service binding processor is not the best place to test intents
because the builder obviously has not yet run and propagated intents down
to the binding. It would only be able to test the intent on the binding
itself.
