Mule 4
作者：Daniel Feist
1. Non-Functional Improvements
1.1. MuleMessage
1.2. MuleEvent / MuleSession
2. Integration Language Simplications
2.1. MEL vs DW
2.2. Filters
2.3. Transformers
2.4. Message Properties
2.4.1. Affects MEL auto-complete
2.4.2. Affects Debugger
2.5. Components
2.6. Java Support Pack
2.6.1. CXF
2.6.2. JAXB
2.7. Hide CXF from user.
2.7.1. Gateway currently uses this.
3. DataTypes and Transformation
3.1. Unified/Improved Data Types
3.1.1. Huge impact on studio.
3.2. MP Data Type Introspection
3.3. Improved Auto-Transformation
4. Mule 3 - Mule 4 Migration
5. Gateway
5.1. Mule Dynamic Policy API
5.2. Port Policies and other functionality to Mule 4 API's
6. Unified Connectivity
6.1. SDK
6.1.1. Connection Testing
6.1.2. Connection Management
6.1.3. Message Sources
6.1.4. etc.
6.2. Re-write Mule Transports/Modules as Connectors
6.2.1. HTTP
6.2.1.1. API Gateway needs this.
6.3. Migrate Connectors from Devkit to SDK
6.4. Project X Connectivity API's
6.4.1. Agent Services for TAP API's
6.5. Studio to use TAP API's for connection testing + Meta-Data
6.5.1. How does Studio instantiate Mule and use TAP API's? Agent is EE only.
6.6. Use one connector programatically in another one. e.g. HTTP in WS-Consumer or WS-Consumer in SFDC.
7. Upgrades
7.1. Isolation
7.1.1. OSGi has more impact on studio
7.2. API/Modularization
7.2.1. Munit API Requirements
7.2.2. Agent API Requirements
7.2.3. User API Requirements
7.2.4. Gateway API Requirements
7.2.5. ARM / CloudHub