Create a factory mechanism for HTTP transports

Details

  • User impact:
    Medium
  • Effort points:
    2
  • Affects Docs:
    Yes
  • Similar Issues:
    None

Description

Now that we have multiple HTTP implementations, I'm coming around to Andrew P's point of view that we need a factory mechanism.

When I create an http endpoint I shouldn't have to worry about it being in the jetty namespace or prefixing it with jetty:. I should just configure the HTTP connector with the server I want. If I have jetty specific information I want to configure, I should embed it in the connector/endpoint definition:

<http:connector .... default attributes ...>
<jetty:config ... jetty specific info ../>
</http:connector>

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MULE-3603 <jetty:endpoint/> cannot be configured in the same way as <http:endpoint/>

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

There are no comments yet on this issue.

People

  • Assignee:
    Unassigned
    Reporter:
    Dan Diephouse
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: