Binding UI for HTTP Gateway

[bfitzpat]

While working on SWITCHYARD-1027, which is the tooling side of SWITCHYARD-985, I ran into a couple of questions I'm hoping to get some feedback on...

First, here's a screen shot of the UI for an HTTP binding associated with a Service:

And here's a shot of the HTTP binding associated with a Reference:

Not much of a difference other than a few fields (Context Path on the Service side and Operation Selector & Address on the Reference side).

Question #1 - Should I make Method field a drop-down list with the common HTTP methods? (GET, POST, PUT, DELETE, HEAD, OPTIONS, TRACE, CONNECT) If I go that route does it need to be editable?

Question #2 - Should I make the Content Type field an editable drop-down list with some common content types? This seems largely impossible unless we limit it to a few common text types (http://en.wikipedia.org/wiki/MIME_type).

Or should I leave them both just as plain text fields folks can enter anything into?

Thanks in advance.

[mageshbk]

Hi Brian,

I started this thread for capturing the config items there. I needed to add some more properties that were applicable for Reference binding as similar to JBoss ESB. I will elaborate them soon. Can this task wait for a day or two?

Method and contentType are not needed for Service binding.

1. A drop-down seems likely

2. This just needs to be a textbox.

[bfitzpat]

Hey Magesh, if your changes are still in-flight it'll have to wait a couple of days.

As for Method & contentType, I will make them Reference only. And for now I'll change the Method to a drop-down with the HTTP operations while I wait to see what new magical properties you add.

Thanks!

[mageshbk]

Brian, I updated the thread above. I wanted to add HTTPClient properties like proxy server, authentication information etc., But that can wait for next release.