Nav

Mule Studio December 2013 Release Notes 

December 9, 2013

MuleSoft is pleased to announce the release of Mule Studio (December 2013) with CloudHub Mule Runtime (December 2013).

Our new version of Studio functions as a single download with two runtimes:

  • Mule 3.4.1 Enterprise Runtime - available for deployment on premises and to CloudHub

  • CloudHub Mule Runtime (December 2013) - available for deployment to CloudHub

These release notes apply to Mule Studio (December 2013) and the CloudHub Mule Runtime (December 2013). Note that the new features and functionality described here are only available for deployment in CloudHub using the CloudHub Mule Runtime (December 2013). If you intend to deploy your application to an on-premises production server, use a Mule 3.4.1 runtime when you begin a new project in Mule Studio. 

Further, these release notes offer some detail on the tangentially released APIkit version 1.1. See New Features and Functionality section below.

Refer to our Release Strategy for full details about our most recently released runtimes and their deployment options.

Download Mule Studio (December 2013) to take advantage of the latest and greatest! 
Access the Release Notes for the December 2013 release of CloudHub
Access the API Gateway Runtime.  

  

Document Revision History

December 9, 2013, v1.0 Initial Publication. 
January 9, 2014, v1.1 Added details for APIkit version 1.1 launched in conjunction with the December release.
January 10, 2014, v.1.2 Added note about known issue with December 2013 runtime and API Manager.
April 4, 2014, v.1.3 Added notes about five bug fixes included in Studio update released today. Refer to Mule Studio section under Fixed in this Release.

Current Release Version

Enterprise Edition Community Edition

ESB

n/a

 n/a

Studio

Version: 3.5.0 Build Number: 201312091746

 

Management Console

n/a

 n/a

New Features and Functionality

  • Better DataMapper: Improved DataMapper performance.

  • Batch processing: New in Mule, use batch processing functionality to process data sets – particularly large or streaming – in batches to maximize data integration efficiency.

  • Auto-completion for MEL: All configuration parameters in Studio now support auto-completion of MEL expressions. 

  • Poll scheduler: Supports adjusting the default polling interval and other more complex polling logic, including Cron expressions.

  • DataSense Usability Improvements: Added time out functionality so as to facilitate quicker response to 'cancel' operation.

  • Improved GUI Design: Mule Studio has an improved New Project wizard designed to simplify the creation of a new project or example project.  

  • Having joined the API Platform family of products, the Anypoint Service Registry has a new name: API Manager. Further, it has has some new functionality: LDAP Security Provider PolicyConsumer Key enforcement, and Endpoint aliasing.

  • New and Improved CloudHub features: New Enterprise Virtual Private Cloud and support for poll scheduling and batch processing.

  • APIkit version 1.1: released in conjunction with the December 2013 release, the newest version of APIkit includes improved functionality:

    • APIkit automatically detects hyperlinks to RAML editor 

    • APIkit validates files even before they have been saved 

    • APIkit now displays any errors which occur within any !included files 

    • APIkit now offers the ability to configure the console in an independent endpoint

Hardware and Software System Requirements

For most use cases, Mule Studio (December 2013) with CloudHub Mule Runtime (December 2013) does not change the hardware and software system requirements established by Mule 3.4.1. Please https://www.mulesoft.com/support-and-services/mule-esb-support-license-subscription[contact MuleSoft Support] with any questions you may have about system requirements.

Important Notes and Known Issues in this Release

This list covers some of the known issues with Mule Studio (December 2013) with CloudHub Mule Runtime (December 2013). Please read this list before reporting any issues you may have spotted.

API Manager

HABITAT-1194

Services, proxies, or APIs deployed to the December 2013 release on CloudHub and manually registered in API Manager using the CloudHub endpoint URL do not support runtime policies. For more details, see the API Manager release notes.

Workaround:

This issue is fixed in the updated API Manager agent version 5.0.1, which is embedded in the Mule 3.4.2 runtime. As a workaround, deploy services, APIs, and proxies to the Mule 3.4.2 runtime on CloudHub.

Mule Studio

n/a

XSD validations work only with a functional Internet connection.

STUDIO-3797
STUDIO-3693

Issues with classpath. This may cause existing applications to have problems opening in Mule Studio (December 2013), primarily if users added jar files to internal folders of the Runtime Plugin Folder.

STUDIO-4176

Validation only accepts MEL expressions> If using an evaluator, you may get an error message in the expression.  

STUDIO-4172

Inconsistent behavior of Undo function in Studio.

STUDIO-4146
STUDIO-4148
STUDIO-4110

MEL auto-completion limitations:

  • issue when a string starts to be a complex expression.

  • auto-completion not functional inside templates examples in Studio.

  • auto-completion not yet implemented for drop-down fields, just text-entry fields.

  • auto-completion not yet implemented for some text fields, such as the Queries dialog. 

STUDIO-4135

Some root methods do not resolve properly.

Anypoint Connector DevKit

DEVKIT-448

Cannot add a List and specify the DataType when using the DynamicObjectFieldBuilder.
Workaround: DevKit allows to create lists of specific types while creating metadata

DEVKIT-468

Add Enum implementations class when creating enum fields using the object builder.
Workaround: DevKit allows implementation classes while creating enums inside of dynamic objects

DEVKIT-196

INCLUDE_ERROR code snippets in generated docs.  javadoc:javadoc is passed as an argument 

DEVKIT-432

Wrong transformer package generated for BigDecimal, makes compilation fail.
Workaround: DevKit accepts Java enums as argument/fields in a connector, and does not introspect objects that belong to java

DEVKIT-472

Incorrect generated code when combining filter and Injection of the MuleMessage
Workaround: DevKit now allows the use of MuleMessage as an injected parameter when using @Filter

Fixed in this Release

Mule ESB

MULE-7042

Event correlation timeout incorrectly detected on cluster

MULE-6992

Race condition when refreshing access tokens

MULE-6991

postAuth() method does not catch token expiration exception

MULE-7116

Message receiver fail when trying to schedule work after reconnection

MULE-7137

DefaultMessageProcessor chain needs to decouple from Pipeline

MULE-6943

Not serializable error when wrong updates expression is used for watermark

MULE-7091

IllegalStateException when doing OAuth dance with InMemoryObjectStore

MULE-7043

Cannot put a Foreach after an OAuth authorize

MULE-7118

Incompatible usage of MVEL on Drools

EE-3535

Change MVEL dependency to use mule’s MVEL

MULE-7015

ObjectToHttpClientMethodRequest fails to process DefaultMessageCollection when http.version is set to 1.0

MULE-7008

Private flow sends duplicate message when replyTo property is set

MULE-7027

ExpiringGroupMonitoringThread must process event groups only when the node is primary

EE-3496

Expensive lookup in Spring Registry is performed every time a MEL expression is evaluated

EE-3470

Queues with limited size behave differently in standalone and cluster mode

MULE-7024

DataSense core doesn’t support inbound endpoints

MULE-7021

AbstractListeningMessageProcessor needs to implement MessageProcessorContainer To be debugable

MULE-7004

Fixed Frequency Scheduler allows negative value on startDelay

MULE-7019

AccessTokenPool is not closed after disposal

MULE-6808

When running salesforce operations in parallel (with Oauth integration), in some scenarios we are getting an exception related to the access token for Oauth

EE-2916

java.io.NotSerializableException at org.mule.config.spring.parsers.assembly.MapEntryCombiner when having a JDBC Inbound in a clustered environment

MULE-7005

ServerNotification completing work after listener failure

MULE-6800

Thread leak on Mule redeployments for embedded

EE-3449

Incorrect validation for node ID in cluster causes error on removal if node IDs are not reassigned

MULE-7062

It is not possible to send outbound attachments over http

MULE-7080

Race condition checking file attributes on SFTP transport

MULE-7050

MuleApplicationClassLoader loadClass() method not synchronized

MULE-7041

EventProcessingThread must manage exceptions thrown by implementation classes

MULE-7036

QueuedAsynchronousProcessingStrategy ignores queue store configuration

MULE-7114

Outbound HTTP Patch call is not sending the payload as message body

MULE-7121

OAuth support throws raw exception when authorization code not found

MULE-7119

MEL DateTime is not serializable

MULE-7123

MuleExceptions are not all Serializable

EE-3473

The generated Studio runtime bundle needs to have a different internal structure

EE-3466

When something failes in the on-complete-step of batch scope, there is no failure message.

MULE-7012

HTTP/HTTPS outbound endpoints ignore the keep-alive attribute

MULE-7025

Serialization exception using persistent queues

MULE-6917

set-attachment adds attachments that Mule can’t really use

MULE-7028

MuleMessageToHttpResponse not evaluating outbound scope to set the content type header

MULE-7034

MuleEvent is not serializable when using a JDBC inbound endpoint with a nested query

MULE-6973

jersey:resources component doesn’t register multiple jersey:context-resolver

MULE-6972

jersey:resources component doesn’t register multiple exception mappers

MULE-7040

Request-reply throwing ResponseTimeoutException on Mule shutdown

MULE-7087

NullSessionHandler - Empty Mule Session header

Mule Studio

Mule Studio December 2013, April 4 Update

STUDIO-4551

Datamapper is not creating the mapping from List<Map> to CSV on Windows

STUDIO-4381

DB: Polish database editors

SE-736

Cannot set namespace when creating an element

SE-698

Invalid XML element in DataMapper mapping for Salesforce

SE-647

Datamapper appending 'x005f' in nested XML element names when underscore is in the element name

Mule Studio December 2013

STUDIO-3895

parameters in methods should display the name not the type

STUDIO-3897

add support for mel global fields (message, payload, mule, server)

STUDIO-3898

add support for 3.5 examples

STUDIO-3900

add test for import examples

STUDIO-1262

$\{app.home} is not taken into account when validating file paths

STUDIO-3208

Unable to map excel in .xlsx format

STUDIO-3239

Object type in salesforce connector is lost in Linux

STUDIO-3385

handleOutputResultSets should be available on the JDBC EE connector

STUDIO-3386

Breakpoints disappearing when deleting components

STUDIO-3432

Mule Studio 3.4.0 does not read project defined log4j.xml; it works fine with log4j.properties

STUDIO-3566

After resolving duplicate flow names, studio continues to show errors

STUDIO-3595

Typo in an error message

STUDIO-3600

CXF Property in WS- Config Wrongly Asserts Required Value Attribute in Conjunction with Value-Ref

STUDIO-3614

APIkit flows can not be visually debugged with Visual Flow Debugger

STUDIO-3619

VM Connector Persistent Queue xml not recognized in Mule Studio XML verification

STUDIO-3625

Studio removes Spring Beans attributes in the p namespace when switching between XML and flow view

STUDIO-3633

Double metadata fetching in Query Builder editors

STUDIO-3638

Studio erroneously flags as error an filter in a response element

STUDIO-3667

create a new project from a template lets you create an empty project without ends the wizard

STUDIO-3693

ClassNotFoundException when running a Mule Project from Studio that uses the WMQ connector

STUDIO-3722

Installing egit plugin in Studio 3.5 Big Horn gives errors on Windows 7 64 bit

STUDIO-3731

TweetBook example application throws SAXParseException when run from Mule Studio

STUDIO-3780

Add Memory Cache for Maps and Pojo in DM

STUDIO-3781

Classloader leaks with DataSense JDBC test connectivity

STUDIO-3784

Studio crashes when attempting to "recreate metadata from input" in Datamapper

STUDIO-3803

SAP: remove metadata types from Client Settings in the inbound endpoint

STUDIO-3817

CE JDBC transport in MuleStudio allows for batch inserts

STUDIO-3825

handleOutputResultSets in jdbc-ee:connector not recognized by Studio

STUDIO-3832

The 8K bug: datamapper only process csv headers lower than 8k characters.

STUDIO-3845

Two- way editing tests for all Transports

STUDIO-3853

APIkit editor gives ConcurrentModificationException upon saves

STUDIO-3859

"Enable DataSense" connector option not taken into account if the file containing the connector is not saved

STUDIO-3860

DataSense Query Builder Unavailable immediately after configuring Salesforce Credentials

STUDIO-3863

DM Calendar Functions are not working properly

STUDIO-3865

DataMapper fails to validate with error on Excel to List<Map>

STUDIO-3866

Breakpoints don’t stick to the message processor that were toggled for

STUDIO-3868

DataMapper: NPE when executing Preview in Graphical tab when the input String is null

STUDIO-3874

Visual Debugger fails to connect to runtime

STUDIO-3901

Generate Default CSV in DataMapper defaults to pipe separated files, not comma.

STUDIO-3903

Refresh project on import

STUDIO-3907

Application filename set to tmp file name when deploying to cloudhub

STUDIO-3908

Datamapper fails to recognize SFDC operation and create grf file

STUDIO-3910

DataMapper does not automatically display Salesforce object structure on right pane

STUDIO-3926

After adding a Datamapper mp to a flow, the palette Filter no longer works.

STUDIO-3934

When classpath is invalid a nullpointerexception is thrown while doing export

STUDIO-3936

Memory leak in DataMapper

STUDIO-3940

NPE from preview panel when a mapping to XML fails

STUDIO-3968

Add support for new DataSense failure types

STUDIO-3974

Batch :: XML Schema location missing

STUDIO-3975

Batch :: Step scope:: stepID is not marked as required as specified in mule-batch.xsd

STUDIO-3976

When having two flows with the same name in different mflows, there is no way to remove the error report.

STUDIO-3978

Batch does not validate XML structure againts XSD

STUDIO-3980

Batch: problem with steps doc:name and name

STUDIO-3981

When Drag and Drop a Catch ES inside a Choice ES is not added int the canvas until you go to the XML view and back

STUDIO-3982

Exception Strategies: Problem with Drag and Drop

STUDIO-3983

Batch: batch:input is not present in autocompletion

STUDIO-3985

Batch: is not using the doc:name as the display name

STUDIO-3989

Batch aggregator :: empty Response scope is added when batch aggregator is drop into a Flow (not a Batch)

STUDIO-3990

Batch: problem with drag and drop

STUDIO-3991

Batch :: When Display Name of a batch scope is changed, only applied when go and back from XML editor

STUDIO-3992

Batch :: Add Batch to Suggestions…​

STUDIO-3993

Batch :: duplicated Batch when having a batch inside a flow

STUDIO-3998

Batch element (except batch execute) inside a flow should not be allowed from XML editor

STUDIO-4001

batch :: 'Extract to' should not be allowed for complete Step

STUDIO-4002

Batch :: It is allowed to move a batch inside another batch, in canvas

STUDIO-4004

Add Icons to batch

STUDIO-4008

DataMapper should generate an intelligent doc:name

STUDIO-4011

Hash map with list of hash map to a csv generates an empty line.

STUDIO-4012

DataSense not working for transports

STUDIO-4015

XML has duplicated lines when moving an element from one scope to another scope and doing two way editing

STUDIO-4019

Can’t drop a component into a step after placing an aggregator (with something inside it) into step

STUDIO-4020

Poll Element Cleanup

STUDIO-4022

Batch Job and Step tags don’t have autocompletion for the attributes

STUDIO-4023

Poll fixed-frequency- scheduler duplicates the frequency attribute at a poll level and a child element level

STUDIO-4028

option to take Snapshot of the diagram is disabled

STUDIO-4030

Studio hangs after applying changes in the properties editor

STUDIO-4033

Cannot enable maven support

STUDIO-4039

NPE when running a project that has native libraries outside the Mule project

STUDIO-4040

Mule project wizard :: Improvements

STUDIO-4042

Accept policy is ONLY_FAILURES not FAILURES_ONLY

STUDIO-4043

Maven settings are lost upon restarting Studio

STUDIO-4049

NPE with SFDC datasense

STUDIO-4052

Batch :: Batch reference is defined as batch execute in the UC

STUDIO-4055

New Mule Project Wizard :: Only first letter entered in the project name is saved as project name

STUDIO-4061

Soap proxy-client soapVersion reset to 1.1 each time editing done in graphical view

STUDIO-4067

New Project Wizard: both option shows only On Premises and CloudHub shows both runtimes

STUDIO-4069

Batch job does not show the name attribute in the editor

STUDIO-4071

Logger is not being highlighted when debugging inside a batch

STUDIO-4073

DataMapper: problem when generating a mapping with an attribute that ends with 'try'

STUDIO-4074

Batch: I’m able to drop Message Processors in Process Records section out of a batch Step

STUDIO-4075

Drag and Drop: some times when having to scopes it’s imposible to drop something in between

STUDIO-4077

Classpath: files .DS_store should be ignore from the classpath

STUDIO-4080

Batch :: 'Name must be unique' validation message when executing another batch with batch:execute

STUDIO-4081

DataMapper :: In Output > Connector there is a mapping name displayed

STUDIO-4082

Debugger: when inside a batch step and stopping in a JDBC endpoint, the endpoint is not highlighted

STUDIO-4084

No error reported in the editor if the name of the batch job or the batch step is missing

STUDIO-4085

Open MEL expression should report an error

STUDIO-4089

Canvas Drawing: DefinitionNotFoundException when using batch it’s causing the batch not to be drawn

STUDIO-4090

Batch :: Batch Step : Name must be an identifier

STUDIO-4091

Maven Import :: NPE when Importing Mule project from pom.xml

STUDIO-4092

Bundle latest snapshot version of SFDC connector

STUDIO-4093

Add "Mule Example Project" to the file and "new" menu

STUDIO-4094

Message properties transformer :: Typo : Reaname message instead of Rename message

STUDIO-4095

Batch: Adjust Job Expression Id title in XML

STUDIO-4100

Problem with XSD validations: failed to read schema

STUDIO-4104

New Project Wizard runtimes are not displayed well in windows

STUDIO-4106

API manager Token is reported as empty or missing even when correctly declared on preferences.

STUDIO-4109

Batch: Datamapper record delimeter issue

STUDIO-4112

Foreach batchSize attribute is wrongly rendered as batch size-size

STUDIO-4113

MEL autocompletion: completion after assignment to mule variables does not work

STUDIO-4120

Runtimes released on bighorn (any) cannot be used in Cascade

STUDIO-4124

Validation :: The string in 'location' is validated and a "Path does not exist" error is displayed

STUDIO-4127

Prblem with autocompletion in Windows XP

STUDIO-4129

Stack overflow when having unknown attributes

STUDIO-4130

DataMapper :: Intelligent Doc: name set null when using a connector

STUDIO-4138

improve MEL validation

STUDIO-4139

Templates and Keywords shouldn’t be suggested when an identifier is resolved

STUDIO-4143

MEL Autocompletion: problem with templates

STUDIO-4144

MEL Autocompletion: when navigating through packages the selection in the list is not updated according to what you type

STUDIO-4145

NPE when using global elements

STUDIO-4147

NPE when opening and old workspace with current nightly build

STUDIO-4156

DataMapper :: MAP <K,V> as "map<k,v>.grf" in XML with intelligent name

STUDIO-4159

'Errors in Workspace' popup window not working as expected

STUDIO-4163

Could not run Mule application after creating project with APIkit components in CE

STUDIO-4167

Batch :: Error when editing configuration of a Step from an imported project

STUDIO-4169

Autocompletion: inherited methods are not shown during autocompletion

STUDIO-3896

make autocompletion compatible with eclipse regions

STUDIO-1652

mule- app.properties says its generated content

STUDIO-1738

Add JAXB support

STUDIO-2199

Missing dom-to-xml transformer as a studio widget

STUDIO-2423

The xml-to-dom transformer isn’t available as a widget

STUDIO-2957

Propogation of custom Map types

STUDIO-3797

Runtime classloader should have the same order as the on-premises ESB

STUDIO-3814

DataSense not propagated for SFDC create contact

STUDIO-3857

Improve locking in DataSense Caches

STUDIO-3913

add Template support in autocompletion

STUDIO-3924

Schema validation filter is missing two attributes

STUDIO-3929

Improve "New Project" creation process

STUDIO-3942

Change the name for Batch containers (input and on- complete)

STUDIO-3948

Dragging batch job into canvas should pre- populate with 1 step

STUDIO-3949

Create the step container when a component is drag & droped inside the batch process scope

STUDIO-3973

UI improvements to the Connections Explorer view

STUDIO-4016

Add "Batch" suggestion tag to Record Variable

STUDIO-4017

Change name of "Step" to "Batch Step"

STUDIO-4018

Change color of Batch Step and Batch Aggregator scope header to green.

STUDIO-4026

Change it’s to it in Mule Properties View default screen

STUDIO-4027

Rename <aggregate> element to <commit> inside batch steps

STUDIO-4051

Core Studio Remove duplicate elements in core.xml

STUDIO-4072

Improve New project Dialog

STUDIO-4115

Use double- click to create the selected element in the global type chooser dialog.

STUDIO-4116

mule- common Add support for adding XML examples in XML metadata.

STUDIO-4140

Javadoc should be displayed on the suggestion additional information

STUDIO-4141

add support for MEL date time function

STUDIO-4150

Streamline error reporting in DataSense

New Feature

 

STUDIO-3291

Add support for MEL autocompletion in all attributes text boxes

STUDIO-3576

Refactor Studio framework to support top level elements via Framework XML files.

STUDIO-3613

Editor for batch:execute

STUDIO-3621

Cron syntax support for <poll> in Studio

STUDIO-3858

Add a timeout to DataSense related connection threads

STUDIO-3886

Batch Generate new elements, and model definitions (Containers in xml and ContainerDefinitions)

STUDIO-3887

Batch Create Studio model for batch elements. (ContainerNode, etc)

STUDIO-3917

improve MEL parser

STUDIO-3930

Add "New Mule Project from Example" wizard

STUDIO-4045

MEL auto- complete support for recordVars

STUDIO-4086

False validation error for salesforce connector

STUDIO-4119

Add and option to clear/refresh metadata on a cloud connector message processor in the canvas.

STUDIO-2824

Select the sort direction connector queries

STUDIO-2908

Specify metadata key at design time

STUDIO-3524

Getting features (capabilities) a DevKit module supports

STUDIO-3879

Analyze autocompletion for all elements text boxes

STUDIO-3880

Allow disabling stats collections from Studio preferences

STUDIO-3889

Batch UI

STUDIO-3943

Integrate Batch with Debugger

STUDIO-3944

Add basic DataSense propagation to batch

STUDIO-3945

Add support for batch aggregator

STUDIO-3946

Add support for batch message sources

STUDIO-3950

Threading profile for batch

STUDIO-3952

DataSense integration with Autocompletion

STUDIO-3967

Add set record variable component

STUDIO-4035

Studio changes required for ASR rebranding

STUDIO-3835

Analyze top level element changes/refactor to support Batch

STUDIO-3839

Create Jubula plugin to support new Property Editors

STUDIO-3843

Integrate Mock connector to Studio build

STUDIO-3847

Batch Module Mockups

STUDIO-3882

Create Jubula automated tests for the Services Essential training: LABS 1, 2 and 3

STUDIO-3923

Upgrade Jubula runtime/projects/plugins to version 7.2

STUDIO-3970

Create an automatic backup of the Jubula Database in the Amazon S3

STUDIO-3972

Change CloudHub Runtime name to CloudHub Mule Runtime (Dec 2013)

STUDIO-4000

Upgrade SAP Connector to 2.1.1

STUDIO-4059

Replace Batch icons with the final ones.

STUDIO-4062

Studio changes required for ASR rebranding

STUDIO-4125

Hide password in editors

 

Anypoint Enterprise Security

SEC-162

Support multiple files in "location" of secure-property-placeholder:config.

SEC-114

Fixed example that had a missing decryption key.

SAP Connector

SAPCONN-171

Inbound endpoint editor shows metadata types 

SAPCONN-177

SAP connector should generate less information in the metadata XSD

SAPCONN-178

Generate better datasense messages when there is a failure

SAPCONN-71

Command line utility to retrieve BAPI/Function XML Template 

Migrating from Mule Studio October 2013 to Mule Studio December 2013

It is recommended that you create a new workspace in Mule Studio (December 2013), then import any existing projects into your new workspace.

MULE-7013

The keepSendSocketOpen attribute in the HTTP/S connector is deprecated. It is inherited from TCP Connector but has no effect on outbound HTTP connections and will be removed in the future.

MULE-7023

The keep-alive attribute in inbound and outbound HTTP/S endpoints has been renamed to keepAlive.

MULE-7011

The org.mule.util.queue.Queue class now has a clear() method to discard all elements in the queue while leaving the queue usable. If you have your own implementation of a Mule Queue, be sure to to implement the new method.

MULE-7010

The ObjectStore class now has a clear() method which discards all elements while leaving the store usable. If you have your own implementation of ObjectStore, be sure to implement the new method.

MULE-7090

Mule uses the default security provider and TLSv1 as the default algorithm for secure socket connections. The
tlsProtocolHandler attribute from the TLS configuration in SSL, TLS, SMTPS, and Jetty HTTPS transports is deprecated. Mule uses the default settings defined in the JVM platform. This parameter is no longer needed in
supported JDKs.

MULE-6968

Previously, requests to “/” were only received by an HTTP endpoint when no path was defined, and rejected if path was empty or set to “/”. Now requests are received by the endpoint in any of the three cases.

MULE-7061

The Jetty transport now uses Jetty 8. Applications using a custom jetty.xml configuration file must update the Jetty classes referenced in this file. Review details for more information.  

For more details on how to migrate from previous versions of Mule Studio, access the migration guide embedded within the release notes for previous versions of Mule, or the library of legacy Migration Guides.

Third-Party Extensions

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 Studio (December 2013). Contact MuleSoft Support if you have a question about a specific module.

Support Resources

  • Refer to MuleSoft’s online documentation at MuleSoft Docs for instructions on how to use the new features and improved functionality in Mule Studio (December 2013) with CloudHub Mule Runtime (December 2013).

  • 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