July 23, 2013
MuleSoft is pleased to announce the release of Mule 3.5.0 Andes. Focusing on the tools that improve developer productivity, Mule 3.5.0 Andes makes on-premise and SaaS integration even easier.
Our new version of Studio now functions as a single download with two runtimes:
-
Mule 3.4.0 Enterprise runtime - available for deployment on-premise and CloudHub
-
Mule 3.5.0 Andes runtime - available for deployment on CloudHub
These release notes apply to Studio and the Enterprise runtimes of Mule 3.5.0 Andes. Note that the new features and functionality in Andes that are not design time features are only available for deployment in CloudHub using the Mule 3.5.0-andes runtime. If you intend to deploy your application to an on-premise production server, use a Mule 3.4 runtime when you begin a new project in Mule Studio. Access Mule 3.4 documentation for details and read our blog post to learn more about our new release strategy for CloudHub and Mule ESB.
Download Mule 3.5.0 Andes to take advantage of the latest and greatest!
Access the Release Notes for the Andes release of CloudHub.
Access the Release Notes for the Andes release of Anypoint Service Registry.
| Enterprise Runtime | Community Runtime | |
|---|---|---|
ESB Runtime |
n/a |
n/a |
Studio |
Version: 3.5.0 |
|
Managemente Console |
n/a |
n/a |
Mule DevKit |
n/a |
|
-
DataSense Query Language: Mule’s new SQL-like query language allows you to easily query and retrieve complex metadata from remote applications, saving you the effort of manually discovering which data types and fields are available to query. Use Studio’s graphical query editor to quickly assemble a query on an Anypoint Connector which supports query functionality.
-
Work with Multiple Versions of Connectors: Rather than bluntly forcing all your applications to use a single version of a connector, you can arrange to download and use multiple versions of the same Anypoint Connector on your instance of Studio.
-
Improved Source Control Integration: If using git to keep track of changes in an application, you can use Studio to prepare a standard gitignore file for a new Mule Project.
-
Properties Editor: We’ve been working on usability! By default, Mule Studio’s Visual Editor enables you to double-click a building block on the canvas to open its Properties Editor pop-up; optionally, you can now adjust the Preferences in Mule Studio to display the Properties Editor as a tab in the console
-
Project Environment Settings: Throughout the different phases in the development lifecycle you may wish to deploy an application to multiple different environments, such as Production, QA and Test. You can configure your Mule application to facilitate deployment to one of many different environments, both on-premise and in the cloud.
-
CloudHub Sandboxes: CloudHub includes the ability to create sandboxes, restrictive environments for developers and testers to safely test applications without the risk of affecting the production environment.
-
Watermarks: Easily keep track of the last record or time that you’ve sync’d without writing custom logic when extracting data from a system like Salesforce.
-
Anypoint Connectors Compatibility: All connectors available on MuleSoft’s Anypoint Connectors website are compatible with Mule 3.5.0 Andes runtime, although not all connectors support DataSense. Refer to the complete list of DataSense-enabled connectors.
-
CXF Upgrade to 2.5.9
For most use cases, Mule 3.5.0 Andes does not change the hardware and software system requirements established by Mule 3.4.0. Please contact MuleSoft with any questions you may have about system requirements.
This list covers some of the known issues with Mule 3.5.0 Andes. Please read this list before reporting any issues you may have spotted.
MULE-6837 |
Mule application fails when doing stop/start |
MULE-6816 |
Shutdown timeout is not respected |
MULE-6560 |
Incorrect value in recommended JDK version checking |
MULE-6559 |
Wrong messages on JDK version validation |
STUDIO-3490 |
Multiple versions of connectors, problem when trying to load libraries. |
STUDIO-3495 |
If deleting an element inside a poll, the cannot receive new elements. |
STUDIO-3479 |
When updating the Default expression in the Properties Editor of the Choice Flow Control, the branches in the Choice representation on the canvas don’t update until you access the Configuration XML view, then return to the canvas. |
SE-266 |
DataMapper does not maintain the sequence of elements when imported from XSD. |
STUDIO-3494 |
Debugger does not stop on breakpoints in flows built for APIkit. |
STUDIO-3512 |
Issues when using Transactional building block. |
STUDIO-3516 |
Issues with the response arrow when using Composite Source. |
| New Features |
|---|
MULE-6861 Watermark / Binding object store items to flow variables |
MULE-6794 CXF WS-Security - SecurityContext is not set after successful authentication |
MULE-6788 Upgrade CXF to 2.5.9 |
MULE-6809 When using a persisten object store keys that are not valid file names fail |
EE-3301 Update Saxon version to 9.1.0.8 |
MULE-6913 Add a way to invalidate the content of a caching strategy |
MULE-6848 Improve JdbcTransactionFactory to support multi transactions |
MULE-6796 Allow MEL expressions in cxf:property of cxf:ws-config |
MULE-6843 Move OAuth from DevKit to ESB |
MULE-6825 Make loggin less verbose in CompositeApplicationClassLoader |
EE-3274 Add JDBC support on multi-transaction |
Fixed |
MULE-6874 Memory leak with dynamic endpoints |
MULE-6864 SFTP: Jsch issue in java 1.7 and Kerberos |
MULE-6849 ReplyToDestination is not properly configured in some scenarios |
MULE-5301 The MailMessageFactory adds inbound email headers to the outbound scope of the message |
MULE-6887 Duplicating instanceName in quartz connectors cause weird application failures |
MULE-6884 HTTP/HTTPS Connectors: tcpNoDelay |
MULE-6882 TCP Outbound Endpoint ignores responseTimeout |
MULE-6880 FTP responseTimeout has no effect |
MULE-6863 File, FTP and SFTP message factories sets outbound properties. |
MULE-6858 Filename-wildcard filter to fails with SFTP |
MULE-6853 Sftp does not support files with no extension when using tempDir and useTempFileTimestampSuffix |
MULE-6833 GZip transformer failing |
MULE-6829 cxf_operation is wrong when using proxy-client of a soap 1.1 request |
MULE-6791 Jetty inbound endpoint configured with useContinuations="true" sets http.method as outbound rather than inbound |
MULE-6790 File transport sets the Directory attribute incorrectly |
MULE-6783 HTTP inbound keep-alive attribute not overriding the keepAlive attribute of HTTP connector |
MULE-6564 Using cxf:configuration element prevents generation of WSDL on JAXWS SOAP component |
MULE-3704 AttachmentsPropagationTestCase needs XML config file |
MULE-6870 HTTP Patch body is ignored |
MULE-6871 DefaultMuleSession got broken between mule 3.2 and 3.3 |
MULE-5685 Unformatted log line when a property is optional |
EE-3258 JDBC transport complains about invalid expression template #[payload] |
EE-3265 DeploymentService lock not released under error conditions |
EE-3273 Remove ReplyToParameterProcessor from internalMessageProcessorNames list |
Fixed |
STUDIO-173 sometimes, when removing several items one by one, undo works only once. (usualy in Edit→Undo case) |
STUDIO-337 Fatal error when trying to delete a Mule project |
STUDIO-382 Changes to Java code do not get hot deployed |
STUDIO-436 Endpoints not changing their icons when setting RQ-RS for Composite source and Sub-Flow |
STUDIO-459 Unable to add a response when creating a second flow in the same mflow |
STUDIO-502 Confusing window when renaming a project |
STUDIO-596 Script Transformer and Script Component change the generic script framework to specific transformer and component script depending on the engine when clicking on ok and clicking on config xml and coming back to the canvas |
STUDIO-620 Message Properties component loses the values related with the properties if you don’t press the 'enter' key when you do the input |
STUDIO-981 REST widget dialog box shouldn’t offer support for interceptors since they don’t work |
STUDIO-1084 The line location is not displayed anymore for the errors in the problems pane |
STUDIO-1103 Allow dispatcher-threading-profile & receiver-threading-profile to be configured from any connector widget dialog box |
STUDIO-1125 Remove one of the error messages in the error view |
STUDIO-1166 Expression Transformer Custom evaluator not sorted alphabetically for return arguments |
STUDIO-1169 Add a validation that prevents the user from creating the same JDBC query in the connector and endpoint with the same name |
STUDIO-1419 Creating new mapping with the same name as an existing one is overwriting the old mapping without warning the user |
STUDIO-1420 Improvement Deleting an xpath rule should be warning regarding possible fields having this rule assigned. |
STUDIO-1428 Unable to create new mappings using new excel format xlsx |
STUDIO-1496 When renaming lookup table referenced fields loses reference |
STUDIO-1538 Undo option (command + z / Ctrl + z ) does not work if you remove a global element |
STUDIO-1619 Error due to no-expression in choice router isn’t visble |
STUDIO-1650 Renaming flow XML doesn’t update mule-deploy.properties |
STUDIO-1675 When renaming an mflow file, the associated xml file is deleted and not regenerated until the mflow is opened again |
STUDIO-1766 mflow file is not generated after exporting and importing a project that contains errors in the XML (E.g.: Not having correct namespaces) |
STUDIO-1794 Edit input argument name not editable |
STUDIO-1811 Studio is not validating that certain scopes should start only with inbound or outbound endpoints |
STUDIO-1874 All Message Router: 'All properties' tab should be removed in Studio CE |
STUDIO-1922 Add default value # for expressions in return arguments in the expression transformer |
STUDIO-1936 Creating new Project does not respect Working Set selection |
STUDIO-1944 Choice doesn’t have display name |
STUDIO-1948 JDBC inbound endpoint should have an empty queryTimeout if not specified. |
STUDIO-1961 Examples: add/correct the 'version' attribute |
STUDIO-1966 If you delete multiple elements from the UI the undo botton is not enabled |
STUDIO-1977 Need a way to solve dependendency conflicts |
STUDIO-1987 Salesforce: problem with the UI |
STUDIO-1990 Project Structure: when opening a configuration file from src/main/resources you miss the outline view. |
STUDIO-2055 Restore the tutorial example files |
STUDIO-2059 Exceptions in CloudHub API should be handled better |
STUDIO-2080 DataMapper should throw an Exception when fed with wrong types |
STUDIO-2089 Drag and drop of response elements inside the canvas does not work and feedback icon is wrong |
STUDIO-2122 New Mule Project wizard inconsistent when changing Server Runtime and creating templates |
STUDIO-2141 DataMapper edit and save a rule, refreshes left tree and scrolls to the top |
STUDIO-2147 Only queryKey is marked as mandatory for JDBC endpoint while Address is a valid attribute if queryKey is not specified |
STUDIO-2149 createMultipleTransactedReceivers attribute is not supported by Studio in any connector by the UI nor the XML (Getting errors) |
STUDIO-2154 error adding context:property-place-holder |
STUDIO-2160 Icon not showing when adding dependency |
STUDIO-2166 Problem drap-&-drop Flow-Ref into Enricher |
STUDIO-2195 Drag and Drop: when dragging multiple elements to an empty flow, the response lane isn’t shown |
STUDIO-2196 Build Path has system JRE before Mule when projects created in Studio |
STUDIO-2234 Block the editing of the DisplayName in the canvas for Exception Strategies |
STUDIO-2235 Direct-edit display name has a strange behavior under Windows |
STUDIO-2247 Validation: Flow name property should be unique across the whole project |
STUDIO-2249 Remove MIME type attribute from the HTTP endpoint advanced tab |
STUDIO-2250 Studio very slow to edit |
STUDIO-2252 Define a new way to show Beans and validate that the Name / ID is unique |
STUDIO-2254 DB Lookup Table sql script & field belowmust- match, otherwise, SQLException with Column index out of range |
STUDIO-2266 Problem with turn off error reporting |
STUDIO-2285 MuleStudio adds test config files to src/main/app which cause Mule Application to fail during startup when mule-deploy.properties updated with test config in 'config.resources' property |
STUDIO-2288 Mule Studio 3.3 CE Export Error when project resource is out of sync |
STUDIO-2293 When opening an project made with a previous version of Studio, Studio should migrate Cloud Connectors namespace version to the 'current' namespace |
STUDIO-2298 When using the filter palette behaviour is not the same for all the categories |
STUDIO-2299 When deleting a field, everything seem to be deleted due to collapse |
STUDIO-2308 mule-deploy.properties getting imported wrong |
STUDIO-2309 When looking for JDBC in the Global Elements filter, nothing is shown |
STUDIO-2312 Warning icon shown in GUI but not in XML |
STUDIO-2327 Studio randomly crashes when multiple flows are re ordered and referencing one another. |
STUDIO-2347 Export to Mule Deployable Archive should not include files under src/test/* |
STUDIO-2348 the Mule Server launched from MuleStudio should not include files under src/test/resources/* to its classpath. |
STUDIO-2367 There are problems when you zoom out in a flow |
STUDIO-2368 When doing drag and drop you are not able to scroll across the long canvas |
STUDIO-2384 Avalara connector config endpoint properties disappear when saving in "visual editor" |
STUDIO-2393 Salesforce Connector OAuth Configuration |
STUDIO-2407 The main toolbar disappears when minimizing the Welcome Screen |
STUDIO-2409 Long flows are not correctly visible for the users in the Documentation generated using the To Documentation feature |
STUDIO-2414 Debugger: when converting an inbound endpoint to outbound the breakpoints are moved |
STUDIO-2418 Losing the Undo option when moving from flow to the xml view and back to the xml view |
STUDIO-2438 XSDs with namespaces and XML without namespaces issue |
STUDIO-2439 Input Argument: String Type cannot handle variables that happen to hold integer values |
STUDIO-2441 Problem opening mule-config.xml file in src/test/resources from a project created with the Cloud Connector’s archetype |
STUDIO-2450 DataMapper Encrypting database lookup password over and over again |
STUDIO-2452 DataMapper Database lookup table is not validating connection when password is encrypted |
STUDIO-2470 Marquee: I’m not allowed to use the wrap in option when selecting multiple items with the marquee tool |
STUDIO-2471 Marquee: it randomly select the Message Processors when you have a big flow or scopes |
STUDIO-2473 Extract to flow: it is not working well when I extract the flow to a file that is opened |
STUDIO-2474 Update validation for XML Module |
STUDIO-2478 Debugger: breakpoints position is not well refreshed when there is a router |
STUDIO-2481 Salesforce connector losing Global Element Properties information |
STUDIO-2487 Studio doesn’t support complex type nor lists |
STUDIO-2514 Convert to Outbound: when converting an HTTP endpoint to outbound the canvas UI is nor refreshed. |
STUDIO-2517 Connectivity Testing: add proper error messages |
STUDIO-2529 Invalid names are allowed in the Data Mapper creation wizard |
STUDIO-2534 Connections in Connections Explorer don’t refresh when moving through projects in the Package Explorer |
STUDIO-2540 Mapping failing for Excel numbers to POJO BigDecimal |
STUDIO-2546 Fix transactional element |
STUDIO-2547 Problem saving project |
STUDIO-2558 Error when exporting a Mule project in Studio |
STUDIO-2597 Remove unneeded processor chain from templates |
STUDIO-2622 Transactional: the dropping area for the exception strategies does not allow you to drop an exception strategy |
STUDIO-2635 Can’t import project if not copied into the workspace |
STUDIO-2637 Expressions in choice router are lost if you dont tab after input |
STUDIO-2644 locahost is removed when deleting references in HTTP Endpoint |
STUDIO-2645 Some dependencies are on the classpath twice when using m2eclipse |
STUDIO-2656 Security exception when starting a project that has Derby as a dependency |
STUDIO-2671 Studio 3.4 refers to Mule 3.2 schemas in the XML catalog |
STUDIO-2673 Contribution sources points to non existent jar |
STUDIO-2675 Multiple problems occur when closing an editor window |
STUDIO-2681 cloudhub connector studio showing config reference required when it is not |
STUDIO-2682 XML matching tag highlighting does not work |
STUDIO-2699 Debugger exception is show in console |
STUDIO-2703 Not displaying errors on correct message processors |
STUDIO-2718 flow ref editor should be alpha sorted and allow filtering |
STUDIO-2722 Delete all breakpoints only works if one selected |
STUDIO-2725 Getting "Resource project name/src/main/app/project name.xml not exist" when creating a Mule project for the very first time |
STUDIO-2728 The SQL Explorer preferences pane is no longer accessible after a Mule project has been created |
STUDIO-2731 Order Discounter template doesn’t run due to mule-module-twitter dependency |
STUDIO-2732 Deleting scopes using the marquee tool causes NullPointerException |
STUDIO-2736 Hello example template’s logging is not the same as the other templates |
STUDIO-2739 Sometimes app fails to launch because studio is unable to delete a folder |
STUDIO-2741 Deleting multiple widgets and then undoing the delete causes an exception |
STUDIO-2743 Undo doesn’t occur in the Message Flow tab when deleting an inbound-endpoint and the processor next to it |
STUDIO-2747 Cannot click elements inside the Message Flow screen when re-entering window after using Marquee tool |
STUDIO-2748 In New Project wizard, New Mule Flow dialog doesn’t replace whitespaces in the project name with underscores for the flow filename |
STUDIO-2750 Deleting an .mflow file causes an error to be shown in the Error Log view |
STUDIO-2751 Cannot use transaction ee:xa-transactional or ee:multi-transactional from a test case |
STUDIO-2757 Run history |
STUDIO-2759 Breakpoint marker does not move with attached processor |
STUDIO-2761 http connector adds optional attributes by default |
STUDIO-2762 Hot deployment fails for a particular workspace |
STUDIO-2763 Dragging and dropping a Rollback Exception Strategy into a flow messes up the Message Flow canvas |
STUDIO-2764 Breakpoint is permitted on a POLL processor but it doesn’t have any effect |
STUDIO-2765 Breakpoints of deleted/closed projects remain visible in the Mule Breakpoints view |
STUDIO-2766 In the Mule Debugger View, "Connected with mule ESB…" should be changed |
STUDIO-2770 Mule Enterprise security components show up under the Cloud Connectors section when viewed from the global elements tab |
STUDIO-2790 No documentation is generated for global elements |
STUDIO-2792 Generated documentation uses Transformer icon to represent SOAP processor |
STUDIO-2794 Clearly separate message processor and flow documentation sections |
STUDIO-2796 Exception Strategies in generated documentation have broken image link |
STUDIO-2797 Documentation is not generated for processors that are not supported by studio |
STUDIO-2803 WebSocket Writer Group field not showing required field error message |
STUDIO-2804 Web Socket in HTTP component not showing error message for 'Group' mandatory field |
STUDIO-2805 Web Socket enablement in the HTTP Outbound is not adding V13 to the XML |
STUDIO-2812 Global endpoint and connector descriptions of certain transports are identical. |
STUDIO-2813 As one scrolls down in the generated documentation, long flow names overlap flows |
STUDIO-2819 Can not populate serviceClass in CXF component by browsing interface |
STUDIO-2835 ".groovy" files cannot be used as input data in the preview feature |
STUDIO-2838 Changes made to the mapping file are not applied by hot deployment |
STUDIO-2843 Cannot add an attribute for a user-defined XSD |
STUDIO-2854 Mapping is not done if a root name other than "object" is used for user-defined JSON |
STUDIO-2861 XML Lenient Error Policy doesn’t work as expected |
STUDIO-2867 No docs are generated for description in mule-project.xml |
STUDIO-2871 Importing the attached app using a CE run-time, I get a ""xsl:stylesheet" is not bound." error but using a EE run-time-works |
STUDIO-2876 Data mapper type selector should use operation name not xml tag |
STUDIO-2877 Connector without friendlyName cannot have libraries added to project |
STUDIO-2879 Processor chain is lost when I drag a message processor chain inside a scoped processor |
STUDIO-2883 Should not be allowed to add a Poll to a transactional processor |
STUDIO-2884 Poll processor should not be allowed inside the Rollback & Catch Exception Strategy since it is not legal |
STUDIO-2887 Data sources can be viewed from Connection Explorer |
STUDIO-2906 When using hierarchical POJO model data mapper always shows base class |
STUDIO-2912 Documentation is incorrectly generated when flow files are copied and pasted in the same project |
STUDIO-2913 Project title is hidden under the list of flow files when generating documentation from a project containing a large number of flow files |
STUDIO-2924 Property names in the Mule Debugger view are incorrectly set when their values are modified |
STUDIO-2929 Typo when clicking "Generate default" in Data Mapping flow |
STUDIO-2932 Selecting the text() attribute of XML elements in data mapping files causes a NullPointerException |
STUDIO-2933 Nested attributes are created when adding an XML element with a name identical to an existing attribute |
STUDIO-2934 Misspelled word when errors are encountered when executing a mapping |
STUDIO-2940 Cannot open non-Studio Mule projects in Eclipse when Studio plugins installed |
STUDIO-2973 Remove Clover ETL import functionality |
STUDIO-2974 Basic Tutorial (Spellchecker) does not delete file from InXML folder |
STUDIO-2992 Datamapper isn’t validating last row when it has less columns than header in csv file |
STUDIO-3008 CustomEvent templates defined in XML lead to issues when switching to graphical view |
STUDIO-3018 class loading is not consistent across packagings |
STUDIO-3020 Debugger: the option to add a breakpoint in an endpoint which is inside of a poll is being displayed and it shouldn’t |
STUDIO-3028 Object Builder: We are showing a third column that is not needed |
STUDIO-3041 Maven: deleting maven from /usr/share while studio is opened is letting users to create mvn projects. |
STUDIO-3042 Export to deployable archive should include transitive project dependencies |
STUDIO-3044 Magento create-product xml gets broken |
STUDIO-3051 When using the CE runtime the JDBC icon shown in the connection explorer is the EE icon |
STUDIO-3054 Validation warning in XPath expression |
STUDIO-3055 Import a zip that has _MACOSX folder inside (right click compress in finder) does not work |
STUDIO-3065 Studio fails to show the right spot of an error in the ui editor |
STUDIO-3070 JUNIT 4.0 TestCase does not work with flow on DataMapper |
STUDIO-3073 Saving a Mapping in DataMapper |
STUDIO-3075 Comments in unknown nested elements are moved to different location (2-way editing) |
STUDIO-3079 Renaming an mflow creates an error in the error log view |
STUDIO-3080 Project Refactoring Exception |
STUDIO-3088 Remove @SupressWarning from the com.mulesoft.se.orders.OrderSummary.java class as it is causing warnings in the Order Processing template project |
STUDIO-3094 Salesforce List<Map<String, Object>> child elements validations |
STUDIO-3106 Security Module Message Processors are being shown in the palette when the project is using the CE runtime |
STUDIO-3113 XML not generated on CMIS operations with Pojo child elements |
STUDIO-3116 Sometimes when you create the first project you get a resource already exists error |
STUDIO-3121 Problem with ALL Message Processor |
STUDIO-3141 Changing a flow var using the debugger alters the variable list order |
STUDIO-3153 Adding maven support doesn’t modify the build path |
STUDIO-3177 Nested objects on complete-data-load signature |
STUDIO-3208 Unable to map excel in .xlsx format |
STUDIO-3215 Mule project are not associated with the selected working set |
STUDIO-3223 Error importing maven project when the project folder is already on the workspace folder on the File System |
STUDIO-3240 Problems with import 'Mule Studio Project from External Location' |
STUDIO-3251 Cloudhub deploy from Studio allows description for the application, but CH doesn’t support it |
STUDIO-3252 Deploy to Cloudhub should warn about numeric HTTP endpoint ports |
STUDIO-3257 Foreach loses customized field values when switching back and forth between canvas and XML editor |
STUDIO-3258 Studio returns 400 error when deploying to cloudhub |
STUDIO-3265 APIkit 0.2 causes DataMapper issues |
STUDIO-3271 DataMapper wizard throws NPE when DataSense required params are not configured |
STUDIO-3273 Maven (forum) failing to use a class (transformer) that resides in a dependency that is a jar packaged, mavenized mule project |
STUDIO-3284 Maven "Run as Mule Application" fails on a project with maven support and two cloud connectors built with different devkit versions |
STUDIO-3300 Enum combos are not properly reset when changin operation |
STUDIO-3305 DataMapper Not able to handle spaces in element name |
STUDIO-3307 No maven installation was found at the specified location |
STUDIO-3310 Missing environment variables when building with maven |
STUDIO-3321 Maven Import fails silently when importing something that is inside the workspace |
STUDIO-3336 Can not drag unknown message processors around on canvas |
STUDIO-3339 Error message when creating a pojo with a list inside of it |
STUDIO-3341 Sequence of child elements of HTTPS connector is not respected |
STUDIO-3343 Quartz Jobs are marked as invalid when the stateful attribute is added to the job |
STUDIO-3349 Test connection successful even when it shouldn’t be |
STUDIO-3353 DataMapper "Move Up" of attribute not working |
STUDIO-3361 Support POJO based query builders |
STUDIO-3372 Wrong XML generation for Taleo beans |
STUDIO-3376 When creating a global transformer from and endpoint reference tab, the combo list is not updated |
STUDIO-3386 Breakpoints disappearing when deleting components |
STUDIO-3387 wsdl2java error thrown by JAXB |
STUDIO-3390 FTP Namespaces is not correctly updated when changing the runtime (EE to CE) |
STUDIO-3394 API Definition wizard feature is overwriting exiting definitions with same name without warnings |
STUDIO-3408 Old Properties Editor not working correctly in twitter |
STUDIO-3412 Tooltip of API Definition auto-complete showing wrong information |
STUDIO-3418 Response section is not displayed until moving out and coming back to message flow view |
STUDIO-3419 New Properties Editor: when maximising the properties editor window all the attributes disappears |
STUDIO-3436 Query Builder: Adding to many filters prevents user of seeing the order by feature at the bottom |
STUDIO-3440 Query builder: Once the user selects something in the order by dropdown it can’t be changed to nothing |
STUDIO-3459 Apikit: showing duplicated key errors when creating a yaml file |
STUDIO-3460 Query Builder: it’s modifying the order of the Filters |
STUDIO-3461 Wrongly showing HTTP endpoint as outbound when drag and dropping it to an empty flow |
STUDIO-3467 APIKIT: Unable to read schema document because there is a space in it |
STUDIO-3479 Choice: when updating the Default expression in the New Properties Editor the branches in the Choice doesn’t get redrawn until you go to the XML view and back to the Message Flow View |
STUDIO-3485 APIKIT: Drag and Dropping apikit router to the flow is breaking the project |
STUDIO-3490 Multiple Cloud Connectors: problem when trying to load libraries (backward compatibility) |
STUDIO-3491 Connection View: NPE when the CC is not installed |
STUDIO-3494 Debugger does not stop on breakpoints in flows used by APIKit |
STUDIO-3496 Query Builder: Searching and selecting fields in query editor is broken |
STUDIO-3506 EE dependencies added to POM even when targetting a CE runtime |
STUDIO-3508 Usability problem to create template project when having multiple runtimes |
STUDIO-3512 Problem when drawing flows that uses transactional |
STUDIO-3513 Apikit: src/main/api folder is not being imported from previously exported mule projects |
STUDIO-3514 Apikit: When importing a Mule project with apikit router component the apikit library is not added to the project |
STUDIO-3515 Apikit: apikit router component is adding non required empty fields in the xml |
STUDIO-3516 Problem drawing the response section when using Composite Source |
Improvement |
STUDIO-381 When the project gets saved the flog config file should get 'touched' automatically |
STUDIO-574 Difficult to run configuration if you haven’t already ran the app as a Mule app |
STUDIO-708 Support "Run As" on the Canvas |
STUDIO-1217 JDBC: When Configuring a datasource Studio should let the user know that he\she must import the driver |
STUDIO-1220 Improve usability of SOAP client by automatically detecting operations when service class is selected |
STUDIO-1301 Add a button for the custom elements that creates a class for you |
STUDIO-1346 DevKit library should be added to classpath. |
STUDIO-1652 mule-app.properties says its generated content |
STUDIO-1688 The validation message for the Java component UI is not user friendly |
STUDIO-1759 More easily navigate between XML and GUI |
STUDIO-1787 Duplicate Project Issue in Maven Import |
STUDIO-2025 Changing name of flow will lead to error in flow reference |
STUDIO-2101 NullPointer Exception Unable to set values to attributes that doesn’t have getters |
STUDIO-2113 Scripting file references need to be relative paths |
STUDIO-2143 DataMapper: improve error message when mapping an interface class with errors |
STUDIO-2210 Provide a way to inspect the devkit classloader for debugging |
STUDIO-2216 Ask the user to save changes in a file when changing from one file to another |
STUDIO-2226 Change the "New Mule Flow" option to "New Mule Configuration File" |
STUDIO-2227 Hide the .mflow extension in the package explorer |
STUDIO-2268 Pressing ENTER over a message processor in the canvas should open the MP configuration window |
STUDIO-2269 As a Studio user I would like to be able to move from one MP to another using the arrows keys from the keyboard so that I can avoid using the mouse too much |
STUDIO-2307 Issues while importing existing projects |
STUDIO-2332 Move the Choice message router to the framework |
STUDIO-2344 Custom java transformer component should link to the class |
STUDIO-2361 Improve scopes handeling in Studio |
STUDIO-2435 Maven: Studio should build the application with the maven-mule-plugin when running it (if it is a maven project) |
STUDIO-2437 Change the Import menu |
STUDIO-2455 HTTP/HTTPS Connector dialog should not set proxy settings to localhost:80 by default |
STUDIO-2472 Change Select and Marquee icons in the palette so that they are only in one line |
STUDIO-2503 Import: when importing a project Studio should suggest or use the runtime that the project was using when it was exported |
STUDIO-2535 Whenever the project has a change, Connections Explorer should warn the user to save the project changes before executing test connection |
STUDIO-2537 DataMapper: validate that the Json file structure is valid |
STUDIO-2538 Mule Studio overwrites config.resources in mule-deploy.properties |
STUDIO-2587 Introduce support for default namespace prefix optimization (aka implicit namespaces) |
STUDIO-2641 Flow breakpoint not hit when running a FunctionalTestCase from Studio |
STUDIO-2687 Global elements configuration doesn’t pick values from mule-app.properties file |
STUDIO-2711 Maven support enablement isn’t saved when exporting/importing |
STUDIO-2714 element mapping conditions need to be more powerful |
STUDIO-2723 mule breakpoints list should allow multiple select |
STUDIO-2726 When deploying to cloudhub I can’t choose to enable insights |
STUDIO-2836 Visually map input arguments complex object fields |
STUDIO-2859 Add option to download dependencies in the background |
STUDIO-2860 CSV lookup table uses an absolute path instead of a relative path for a CSV file located within the project |
STUDIO-2872 Welcome page is missing in Studio plugin |
STUDIO-2928 Generate default option should be disabled when there are no fields to generate from |
STUDIO-2957 Propogation of custom Map types |
STUDIO-2990 When exporting a maven-enabled Studio project it would be good to default the file name to the Maven filename |
STUDIO-3091 Easy way to access a flow through a flow reference |
STUDIO-3123 Test Connection doesn’t work with property placeholders |
STUDIO-3168 Encapsulate and ease the MetadataModel API |
STUDIO-3205 Connections View usability improvements |
STUDIO-3256 Security: Add the possibility to add security to an HTTP endpoint |
STUDIO-3287 Unify the Maven archetype |
STUDIO-3289 Add the ability to set maven arguments when running an application with maven |
STUDIO-3297 Cannot manage mule-deploy.properties manually |
STUDIO-3330 Improve user interface for new properties editors and DataMapper in Windows XP |
STUDIO-3382 Connectivity Testing Improve error message |
STUDIO-3424 Review PreviewResultAnalyzer functionality to improve performance |
STUDIO-3434 Query Builder: lets the user create an invalid queries and then when you open the builder again you get a Malformed query error |
STUDIO-3471 Multiple Runtimes and Maven support: when changing the runtime version the pom.xml is not updated |
STUDIO-3481 APIKIT: Router Processor not able to find yaml file if user does not specify the file extension '.yaml' |
STUDIO-3484 New Properties Editors: when pressing CMD + S or CTRL + S the changes in the editor should be reflected in the file, and the file should be saved |
STUDIO-3489 Query Builder: improve the time that it takes to translate a dsql query to a native query |
STUDIO-3505 Poll: improve watermark validation |
STUDIO-3511 Maven: remove dependencies from pom.xml file when removing the libraries from the project |
New Feature |
STUDIO-783 Wiretap is not available as a widget |
STUDIO-1648 Allow polling window to be specified in seconds, minutes, or hours |
STUDIO-1695 OAuth-based connectors cannot be used in Studio |
STUDIO-1906 Drill Down into element |
STUDIO-2018 Data Mapper Runtime Features |
STUDIO-2024 Support for DM Streaming |
STUDIO-2255 Missing <tracking:transaction/> support |
STUDIO-2292 Add missing TCP Connector |
STUDIO-2304 Convert Java Project to Mule Studio Project |
STUDIO-2315 Bad maven project import in studio using studio:studio |
STUDIO-2317 Allow the user to wrap components into new scopes and to extract selected components to a new Flow or Subflow |
STUDIO-2328 Implement "Rename" refactor |
STUDIO-2343 Allow cross project flow copy paste |
STUDIO-2351 Add debugger views into the mule perspective |
STUDIO-2352 Add toggle breakpoint action to right click context menu in canvas |
STUDIO-2353 Support breakpoints in multiple configurations |
STUDIO-2355 Add watches support in the debugger |
STUDIO-2360 Add marquee support in Studio |
STUDIO-2427 Add enable/disable option to breakpoints |
STUDIO-2431 Addd the ability to remove an scope without removing the elements inside of it |
STUDIO-2493 Input/Output Structure Change: |
STUDIO-2643 Studio deployer needs to support classloader override |
STUDIO-2965 Add support for POJOs in the Object builder and persist them in the XML |
STUDIO-3037 Add metadata support for constant fields. |
STUDIO-3167 Support hybrid metadata models |
STUDIO-3270 Studio support for filter, split, aggregate and routing record level data |
STUDIO-3291 Add support for MEL autocompletion in all attributes text boxes |
STUDIO-3398 Database lookup table JDBC configure should support spring property placeholders |
STUDIO-2336 Multiple sources for data mapper |
STUDIO-2403 Implement Metadata and Preview for Flow Ref Lookup tables |
STUDIO-2908 Specify metadata key at design time |
STUDIO-3298 Studio support for watermark |
STUDIO-3504 Integrate Cloud Connectors to Studio |
-
With Mule 3.5.0 Andes, Apache CXF was upgraded from 2.5.1 to 2.5.9. This upgrade is transparent to Mule applications. However, if you are accessing internal CXF APIs, consult the CXF migration guide for details.
-
With Mule 3.5.0 Andes, Saxon was upgraded from 8.9.0.4 to 9.1.0.8. This upgrade is transparent to Mule applications. However, if you are accessing the Saxon API, consult the Saxon migration guide for details.
For a full and detailed list of considerations when migrating from the previous version to this one, see the MIGRATION.txt file, located in the root folder of Mule ESB.
At this time, not all of the third party extensions you may have been using with previous versions of Mule ESB have been upgraded to work with Mule ESB 3.5.0 Andes. Contact MuleSoft if you have a question about a specific module.
-
Refer to MuleSoft’s online Documentation at mulesoft.org for instructions on how to use the new features and improved functionality in Mule ESB 3.5.0 Andes.
-
Access MuleSoft’s Forum to pose questions and get help from Mule’s broad community of users.
-
To access MuleSoft’s expert support team, subscribe to Mule ESB Enterprise and log in to MuleSoft’s Customer Portal.