Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0.1
-
Fix Version/s: Product Backlog
-
Component/s: Transport: HTTP(S) / Jetty
-
Labels:
-
User impact:Medium
-
Effort points:2
-
Affects Docs:Yes
-
Similar Issues:
MULE-681Implements a TransactionManager factory for JOTMMULE-3More flexible configuration mechanismMULE-3675Beans created by object factories not autowiredMULE-3369Update the Creating Transports page on the 2.0 wikiMULE-529Need to create Stream Transport docMULE-4743MuleClient.send() timeout is not respected with http transportMULE-5960Create Factory methods for each type of TransactionTemplate and use those instead of TransactionTemplate constructorMULE-5327Improve ThreadPoolFactory discovery mechanismMULE-2502Important attribute "factory-ref" has been lostMULE-1037Improve HTTP transport with better configuration for maxConnectionsPerHost
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
| Related | |||
|---|---|---|---|
|
|
|
||