-
Persistent object store in Mule uses the key as the filename of the object store. This activity may result in a generated filename that is invalid in Windows operating system. Workaround: use a key name (such as a hash of the key) that will result in the generation of a key with a valid filename.
-
The Anypoint Service Registry agent that syncs with Mule ESB standalone perpetuates the object store filename issue in Windows. If you run standalone in Windows, download a patch for ESB 3.4.0 from the Customer Portal.
Mule ESB 3.4.0 Release Notes
April 16, 2013
MuleSoft is pleased to announce the release of Mule ESB 3.4.0 which introduces new functionality and improvements to our industry-leading ESB software.
These release notes apply to both the Community and the Enterprise runtimes of Mule ESB 3.4.0. Where appropriate, we have applied an Enterprise marker to identify features or functionality that are available only in the Enterprise runtime.
For this release, we have focused our efforts on features and tools that improve developer productivity and make SaaS integration even easier. Our new version of Studio now functions as a single download, enabling developers to easily switch between Community and Enterprise runtimes. We also continue to harden our product, making it more stable and easier to use as we apply bug fixes and improvements.
Download Mule ESB 3.4.0 to take advantage of the latest and greatest!
Current Release Version
Mule ESB 3.4.0 Beta Enterprise Edition |
Mule ESB 3.4.0 Beta Community Edition |
|
---|---|---|
ESB Runtime |
Build 746c76f4 |
Build c8afb471 |
Studio |
Build 201304121501 |
|
Management Console |
Build number: 00863f754a |
n/a |
Mule DevKit |
Build number: 3.4.0.1555.8df15c1 |
|
Amazon SQS Connector |
Studio Plugin Version: 2.2.1.201304081205 Connector Version: 2.2.1 |
|
CMIS Connector |
Studio Plugin Version: 1.12.0.201304081630 Connector Version: 1.12 |
|
Studio Plugin Version: 2.2.0.201304081316 Connector Version: 2.2.0 |
||
Google Calendars |
Studio Plugin Version: 1.1.0.201304081239 Connector Version: 1.1.0 |
|
Google Spreadsheets |
Studio Plugin Version: 1.1.0.201304081245 Connector Version: 1.1.0 |
|
Google Tasks |
Studio Plugin Version: 1.1.0.201304081247 Connector Version: 1.1.0 |
|
Magento Connector |
Studio Plugin Version: 2.0.0.201304081301 Connector Version: 2.0.0 |
|
MongoDB Connector |
Studio Plugin Version: 3.3.0.201304081324 Connector Version: 3.3.0 |
|
Salesforce Connector |
Studio Plugin Version: 5.3.1.201304081315 Connector Version: 5.3.1 |
|
SAP Enterprise Connector |
Studio Plugin Version: 3.4.0.201304081435 Connector Version: 2.1.0 |
n/a |
Twilio Connector |
Studio Plugin Version: 1.4.0.201212071208 Connector Version: 1.4.0 |
|
Twitter Connector |
Studio Plugin Version: 2.9.1.201304081343 Twitter version: 2.9.1 |
New Features and Functionality
-
Visual Flow Debugger: Enables users to insert breakpoints in flows, step through breakpoints in the visual debugger, and examine message content as it moves through the flow. Remote debugging is also supported.
-
Anypoint DataMapper Enhancements: Enterprise Includes the ability to use information from other flows directly in mapping, the ability to modify your input/output without losing mappings, and the support for the Mule Expression Language directly within the DataMapper transformation logic. Refer to the Anypoint DataMapper documentation for more detail.
-
Studio as an Eclipse Distribution: Studio is available as a Eclipse plugin package. User can now leverage Studio with Eclipse 3.8-based IDEs, including Spring Tool Suite (STS). We support the Java, Java EE, and STS 3.1.0 distributions that use Eclipse 3.8.
-
Studio Documentation Generation: Studio provides the ability to generate HTML-based documentation for a project. These materials contain the diagram and XML for flows and the description of flows and their components as entered by developers within the application.
-
Metadata-Based Development: Enterprise This feature, called DataSense, automatically discovers the operation data types for several Anypoint Connectors so as to prescribe mapping within a DataMapper. You no longer have to explore the documentation of your connectors and the description of their underlying APIs in order to be able understand their data types – DataSense automatically discovers and displays them in Studio.
-
Maven support: Enhancements to make it easier for users to create and run Maven projects directly in Studio. Further, Studio automatically maintains all dependencies. Users can import Maven projects into Studio, or export them as needed.
-
Anypoint Service Registry support: Enterprise Via an Anypoint Service Registry endpoint, Mule supports dynamic routing of messages according the rules defined within the Service Registry.
-
Transactional improvement: Enterprise Studio supports finer-grained control over the demarcation of transactions within flows.
-
SAP Connector improvements: Enterprise Studio supports multiple logins for an endpoint, new XML representation for Functions (BAPI), and the ability to create JCoFUnction XML schema. See SAP Connector documentation for details.
-
Dynamic Changes to HA Clusters: Enterprise Management Console supports the ability to dynamically add or remove nodes in a high availability cluster without disbanding it.
-
Password Encryption in Management Console: Enterprise Management Console supports the ability to encrypt the following types of passwords: user passwords stored in the Console’s default database, the LDAP password used by the Console in an LDAP authentication configuration, and the user credentials for the Business Events database.
Hardware and Software System Requirements
For most use cases, Mule ESB 3.4.0 does not change the hardware and software system requirements established by Mule ESB 3.3.X. 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 ESB 3.4.0. Please read this list before reporting any issues you may have spotted.
Mule ESB
Object Store |
|
MULE-6779 |
Unable to load wrapper’s native library Workaround: Server should work regardless of issue. |
MULE-6769 |
MuleContext.dispose should call stop on started connectors and then dispose |
MULE-6765 |
Chaining more than one HTTP outbound endpoint will use the HTTP method of the first one Workaround: Use a subflow for the followings endpoints. |
MULE-6721 |
Restarting Mule app makes loss JMS messages due to redelivery failure Workaround: Increase max redelivery. |
EE-3200 |
Exception on logs when transferring big file in clustering |
EE-3184 |
Patches are not being loaded if copied in lib/patches dir. Only if they are copied in lib/user Workaround: Put patches on lib/user dir. |
EE-3183 |
Starting Mule EE shows quartz start info in console |
EE-3182 |
Starting Mule shows resource and provider class search details in console |
EE-3181 |
Starting Mule EE shows Clustering disabled warning on console |
EE-3180 |
Starting mule shows ASR missing token error on logs |
EE-3141 |
When using a Throttling policy with throttling statics enabled, limit headers are swapped. |
EE-3108 |
Upper case "?WSDL" not supported Workaround: Change to lowercase. |
EE-3097 |
Quartz endpoint starts executing before the application has finished deploying |
EE-3076 |
Setting a throttling policy with zero or negative values should throw an exception |
EE-3048 |
Setting 0message/seg on a throttling policy process messages anyway |
Mule Studio
Maven Support |
|
DataSense |
|
Studio Visual Debugger |
|
Two-Way Editing |
If XML config contains an element with an unknown attribute, Studio’s Message Flow canvas (i.e. the graphical interface) deletes the attribute. In other words, shifting from Studio’s Visual Editor to Studio XML Editor removes the unknown attribute. Workaround: do not shift between the XML and Visual editor. |
DataMapper |
In a DataMapper which uses a JSON file in its mappings, if one of the mappings fails, all subsequent mappings fail until you terminate, then restart your application. |
eGit Plug in for Studio |
Mule Studio 3.4.0 does not support the latest version of the eGit plugin (2.3.1.201302201838-r). A known issue, we will add support for the eGit plugin in a subsequent maintenance release of Studio 3.4.0. Previous versions of the eGit plug in are supported. |
Chaining HTTP Outbound Endpoints |
If you configure more than one HTTP outbound endpoint in your flow, Mule applies the HTTP method of the first endpoint to all subsequent endpoints. For example, if the first endpoint specifies |
Studio on Ubuntu 12.04 LTS |
Due to an issue with the graphical interface user toolkit (GTK), Studio freezes during launch on Ubuntu OS 12.04 LTS. Other Linux distributions pose no challenges to using Studio. |
Object Builder in Studio |
Studio with 3.4.0 runtime does not support arbitrary POJO construction. |
Online Help Links to Web Doc |
Eclipse dynamic help for Studio includes links to primary documentation on the Web that should open in an external browser. On platforms other than Windows, Eclipse does not reliably support opening external browsers from links in help files. On Windows, these links will open in Internet Explorer. |
Mule Management Console
Adding a cluster to a group |
If you place a cluster in a server group, you may experience issues with deployments which target the group instead of the cluster directly. |
Adding a server to a group |
If you add a server to a group via the server details panel (using the settings tab and editing the server info), deployments targeting the group are not transferred to the newly added server. |
Error Messages |
Some error messages in the MMC main window may contain a "See More" link which, when clicked, displays a new window containing only the text |
Mule SAP Connectors
SAPCONN-168 |
Application restart during hot-deployment causes memory access fault on native SAP jco libs |
SAPCONN-167 |
DestinationDataProvider reference gets lost after hot-redeploy of an application |
SAPCONN-166 |
Start up error when multiple sap application which includes mule-transport-sap.jar are deployed |
SAPCONN-157 |
<sap:object-to-xml> doesn’t work with <catch-exception-strategy> |
SAPCONN-137 |
SAP per-app logging problem |
Fixed in this Release
Mule ESB
EE-2931 |
Staring OOB Mule Standalone distro includes it in a cluster configured in an other box |
EE-3041 |
Mule clustering: only one node processing messages in two node cluster |
EE-3051 |
Useless threads are being created (and remain idle) when doing multiple requests to an http inbound endpoint |
EE-3086 |
Setting FixedTimeFrame throttling policies with discardResponse and delayResponse, process more request than expected. |
MULE-6584 |
HTTP/TCP bound to 127.0.0.1 listens on all interfaces |
MULE-6629 |
Concurrent modification exception when evaluation MEL expressions |
MULE-6706 |
PartitionedPersistentObjectStore throws error when deserializes objects created in a plugin |
MULE-6699 |
Intercepting Are not generating message processor path |
EE-2982 |
The Redelivery Policy of the RollbackExceptionStrategy doesn’t work on Cluster |
EE-2989 |
Add missing tanuki wrapper libs to support S/390 |
MULE-4209 |
Embedded distribution has no version info in MANIFEST and so startup splash screen does not show version info |
MULE-5301 |
The MailMessageFactory adds inbound email headers to the outbound scope of the message |
MULE-5776 |
Jetty and Ajax transport do not extend correct schema type and are therefore missing various configuration options |
MULE-6183 |
DynamicOutboundEndpoint.createStaticEndpoint is marked as synchronized and causes congestion under high load |
MULE-6197 |
overwrite SFTP strategy doesn’t work |
MULE-6272 |
UdpMuleMessageFactory adds message properties in the outbound scope |
MULE-6400 |
IdempotentRedeliveryPolicy does not rely on Mule object store manager to create an object store |
MULE-6448 |
The foreach stops the flow when in a xpath collection one tag is empty |
MULE-6453 |
Wrong junit version in cep example |
MULE-6472 |
Missing event initialization on AbstractAsyncRequestReplyRequester |
MULE-6484 |
MulePropertyEditorRegistrar causing performance issues when generating dynamic endpoints concurrently |
MULE-6486 |
MVELExpressionLanguageContext retains payload instance |
MULE-6488 |
JmxAgent - Infinite loop when undeploying an app if it has a flow with a name that includes the character ':' |
MULE-6491 |
HTTP/S transport does not reuse connections |
MULE-6492 |
NullPointer Exception in org.mule.routing.EventGroup.addEvent when running in a cluster |
MULE-6516 |
MEL xpath function does not reset the message payload when the original payload is a stream |
MULE-6524 |
MEL ClassCastException with function |
MULE-6527 |
Exception when calling DeploymentService#undeploy on a stoppedapp |
MULE-6531 |
Put AspectJ Weaver dependency back in the distribution |
MULE-6534 |
Catch-exception-strategy’s expressions fail to filter exceptions |
MULE-6535 |
Flow loses invocation variables added after returning from sub-flow when calling exception strategy |
MULE-6537 |
Improve Multicast handling with several mule servers |
MULE-6548 |
PGP is not closing the stream when ends the encryption |
MULE-6553 |
MESSAGE-PROCESSOR notification events are not detected by the notification publisher |
MULE-6556 |
IdempotentMessageFilter does not allow setting onUnaccepted |
MULE-6581 |
MessageProcessor Notifications not fired after foreach |
MULE-6630 |
Expression component serializes requests |
EE-2922 |
Installing security example fails |
EE-2829 |
AbstractCSVTransformer - use IOUtils.getResourceAsString to pick up the mappingFile |
EE-2873 |
Missing MANIFEST.MF information do not allow to start mule while using mule-ee-distribution-embedded-3.3.x.jar |
EE-2924 |
mule-ee-parent-poms should include the datamapper parent too |
EE-2964 |
Mule cannot find AspectJ’s classes even though they are in the app’s lib/ folder |
EE-3025 |
Agent port range capability does not work on Windows. |
EE-3034 |
MessageProcessor Notifications not fired after cache element |
EE-3078 |
Running a SELECT query with the JTDS driver fails |
EE-3098 |
Reduce DataMapper logging verbosity |
MULE-5232 |
xslt-transformer uriResolver setting does not work |
MULE-5363 |
Improper response from ws:proxy (pattern based configuration) when request header contains Accept-Encoding: gzip,deflate |
MULE-5954 |
Mule cannot configure JBOSS TM properties - defaultTimeout and txReaperTimeout |
MULE-6426 |
payload-type-filter not allowed within collection-aggregator-router since mule 3.x |
MULE-6427 |
#[payload == null] is not true when the payload is NullPayload |
MULE-6550 |
Different build numbers are displayed from the same distribution |
MULE-6552 |
XMPP doesn’t support dynamic endpoints |
MULE-6555 |
File transport moveToPattern fails to create directories if streaming is true |
MULE-6571 |
The staxon dependency can no longer be resolved |
MULE-6591 |
Exception on shutdown provokes app redeployment |
MULE-6593 |
Fligh Reservation system does not recognize JSON command on IE 9. |
MULE-6606 |
Phase execution engine is not dispatching to next phase if previous phase is not supported |
MULE-6607 |
NullPointerException on commons-pool when using jdbc queries nested on inbound/outbound endpoints |
MULE-6617 |
First successful not working when used with inputstream based transports |
MULE-6499 |
Java version checking should not log a warning with a supported version |
MULE-6522 |
JDK version checking does not always work inside an IDE |
MULE-6573 |
HTTPS error mappings have less entries than HTTP |
MULE-6590 |
Removing anchor file does not undeploy application |
MULE-6640 |
AbstractTransportMessageProcessTemplate attempts to acquire message twice and doesn’t set OutputStream |
MULE-6668 |
HTTP MessageContext is returning the MessageReceiver, not the InboundEndpoint |
MULE-6690 |
StringToEmailMessage doesn’t encode subject correctly |
MULE-6583 |
Fix thread context classloader in HttpRequestDispatcher |
MULE-6654 |
Message format is wrong in AbstractAddVariablePropertyTransformer.transformMessage() |
MULE-6778 |
Application redeployment is broken |
MULE-6773 |
TCP/HTTP/HTTPS Connectors: invalid maxThreadsIdle |
MULE-6768 |
After applying HTTP Basic Auth Policy, start to get a NotSerializableException |
MULE-6760 |
ProcessorChain and SubFlows are intercepting when they shouldn’t |
MULE-6759 |
Http dispatcher thread leak |
MULE-6753 |
Application logging configuration is not used |
MULE-6750 |
Classloading problem when there are mule plugins installed |
MULE-6749 |
ReplyToHandlers do not work with Dynamic Outbound Endpoints |
MULE-6732 |
HTTP(S) transport generates everlasting temporary files |
MULE-6718 |
When setting a basic authorization filter if no authorizations headers are set in the request, an exception is thrown and there is no request from the browser to add the keys. |
MULE-6699 |
Intercepting Are not generating message processor path |
MULE-6584 |
HTTP/TCP bound to 127.0.0.1 listens on all interfaces |
EE-3203 |
InvalidClassException changing application log level in CloudHub |
EE-3201 |
CH log appender not loading |
MULE-6776 |
TransactedPollingMessageReceiver doesn’t call Exception Listener |
MULE-6743 |
File, Ftp and Mail message factories, sets outbound properties. |
MULE-6737 |
Application with IMAP connector doesn’t undeploy |
MULE-6735 |
MessageProcessorChain is not propagating muleContext to children correctly |
MULE-6731 |
File inbound endpoint triggers multiple flow instances if file read time is longer than pollingFrequency |
MULE-6612 |
Core exports unnecessary transient dependency to junit |
MULE-6587 |
Concurrent XA transactions on same resource manager will lose messages during rollback |
MULE-6485 |
useContinuations parameter failure |
MULE-5301 |
The MailMessageFactory adds inbound email headers to the outbound scope of the message |
EE-3093 |
resultset-to-maps-transformer fails with stored procedures returning a cursor |
MULE-6775 |
Application should close composite classloader on dispose |
MULE-6766 |
foreach not accepting property placeholder for batchSize |
MULE-6756 |
Configuration with CXF Not Generating Notifications |
MULE-6741 |
HttpRequestDispatcherWorkTestCase fails because mockito is unable to mock InetSocketAddress |
MULE-6427 |
#[payload == null] is not true when the payload is NullPayload |
MULE-5276 |
processing.time.monitor thread leak |
EE-3075 |
CSVToMapsTransformer fails with \t as delimiter |
MULE-6770 |
All is not generating Notifications when no processor chain is present |
Mule Studio
STUDIO-3103 |
Modifying the project name in the mule-project.xml file generates problems in many places in Studio |
STUDIO-3099 |
Object builder not been open for S3 connector operations |
STUDIO-3098 |
Metadata is not being retrieved and propagated |
STUDIO-3087 |
Import (backward compatibility) : scan application xml’s for usage of CC in order to add the libraries to the classpath when importing |
STUDIO-3085 |
Problem with Legacy Modernization Example |
STUDIO-3081 |
Importing existing project with Security Module is not adding the library with the dependencies |
STUDIO-3078 |
Studio is not being able to understand another Mule project in the workspace that provides a custom MessageProcesso |
STUDIO-3077 |
Studio Feedback: modify error message dialog to point the users to the forums or jira instead of pointing to the studio-feedback email |
STUDIO-3076 |
Unable to download connectors from the Update Site which comes with Mule Studio |
STUDIO-3068 |
Cannot map input value from CSV to FlowRef |
STUDIO-3066 |
Cannot store value-ref in the XML using property collections for connectors |
STUDIO-3064 |
XML could not be parsed after deleting a logger component from an All flow control |
STUDIO-3063 |
Using security module in studio results in corrupted namespace declarations |
STUDIO-3062 |
Cannot augment working DataMapper with FlowRef LookUp |
STUDIO-3058 |
Datamapper map to SFDC Contact works with 4 but fails with 5 rows |
STUDIO-3050 |
DateMapper Issue support for function str2date |
STUDIO-3039 |
Strange GUI behavior when trying to map JSON to JSON |
STUDIO-3026 |
Cannot use Editor to create User Defined Lookup Table |
STUDIO-3019 |
Metadata does not get the appropriate metadata for arguments different than the one marked as default payload |
STUDIO-3007 |
When using a custom event template, switching to graphical view in Studio fails |
STUDIO-3006 |
When using a custom event template, switching to graphical view in Studio fails |
STUDIO-2998 |
Subflow scope is not working correctly |
STUDIO-2995 |
Visual editor overrides XML when trying to disable default events tracking at element level |
STUDIO-2978 |
Save failed every time with assertion error |
STUDIO-2946 |
Editing configuration deletes all processor configured fields |
STUDIO-2945 |
NPE when creating the first CE project on a new workspace |
STUDIO-2938 |
Studio stops working when trying to add a target value on the enricher editor |
STUDIO-2911 |
XML schema locations are incorrectly generated after manually adding a namespace |
STUDIO-2858 |
Cannot create XML mappings from examples |
STUDIO-2844 |
Datamapper - Returning previous results |
STUDIO-2806 |
Missing Schema Location for namespace Service Registry |
STUDIO-2756 |
Export can’t handle JAR files when not in workspace |
STUDIO-2753 |
ALL processor ignores news processors in certain situations |
STUDIO-2742 |
Endpoint exchange-pattern is automatically set to one-way after explicity stating it should be request-response |
STUDIO-2738 |
Order Processing example template fails at startup |
STUDIO-2737 |
Setting the serviceClass attribute in a SOAP message processor (JAX-WS Service) produces garbage text |
STUDIO-2733 |
Connectors are missing from plugin |
STUDIO-2709 |
JDBC connector is generating invalid XML structure |
STUDIO-2668 |
Studio Blocks when 'generate default' is used and the input is a connector POJO |
STUDIO-2663 |
Code in expression component gets duplicated |
STUDIO-2649 |
pop3 adds namespace to mule config which breaks application |
STUDIO-2633 |
Run as Mule Application is not working |
STUDIO-2630 |
Create a new element (similar to childElement) which supports "addCommand" |
STUDIO-2616 |
DataMapper: problem with class loading |
STUDIO-2613 |
Datamapper wizard showing 'null' error when mapping XML to xml |
STUDIO-2612 |
None of the EE features can be used because of license issue |
STUDIO-2610 |
Runtime: applications can not be run within Studio |
STUDIO-2609 |
DataMapper: problem when mapping with MEL, InvocationTargetException |
STUDIO-2601 |
DataMapper: can not map more than one line of a csv file when using MEL |
STUDIO-2596 |
Exception Strategy section disappears from the flows |
STUDIO-2592 |
Problem with transactional |
STUDIO-2578 |
Missing Run As Mule Application |
STUDIO-2572 |
Saving on the visual editor breaks schema location |
STUDIO-2565 |
All examples are broken due to validations problems |
STUDIO-2564 |
Two way editing ir removing some XML elements |
STUDIO-2554 |
POJO’s attributes are not shown in output view |
STUDIO-2551 |
Two Way Editing: Studio is removing some child configuration |
STUDIO-2545 |
Problem with Expression attribute validations |
STUDIO-2533 |
Runtime: NoClassDefFoundError caused by log4j.properties |
STUDIO-2526 |
One Studio: When creating some EE examples the Default runtime libraries are the CE ones |
STUDIO-2511 |
NPE Caused by the UI used in the Salesforce connector for the Create operation |
STUDIO-2508 |
DataMapper: InvalidGraphObjectNameException when having characters different than [A-Za-z0-9_] |
STUDIO-2495 |
Two Way Editing is not working |
STUDIO-2489 |
We need to change the UI for Maps (used in connectors) |
STUDIO-2465 |
Debugger is not working, EOF Exception is thrown |
STUDIO-2457 |
Evaluator attribute is being required again |
STUDIO-2448 |
Problem with classpath in runtime when using connector’s libraries |
STUDIO-2447 |
DataMapper Hangs Studio |
STUDIO-2440 |
Character ' (single quote) is not being generated well |
STUDIO-2432 |
JDBC Endpoint configuration window won’t open - StackOverflowError |
STUDIO-2416 |
Problem with Choice message router |
STUDIO-2381 |
Problem with the new Transactional Scope |
STUDIO-2364 |
Assertion error when saving a project |
STUDIO-2346 |
Escape invalid XML characters when going from and to the editor to the XML file |
STUDIO-2325 |
Studio corrupts the XML randomly |
STUDIO-2322 |
Unable to add Mule’s .jars as a library into the build path of a Java project |
STUDIO-2321 |
Data Mapper DB Lookup Table, java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic is still active |
STUDIO-2319 |
The 2 way editing breaks because of the new commands to wrap selected components into scopes and to refactor them to flows or sublows |
STUDIO-2286 |
Import Project deletes source project |
STUDIO-1733 |
List<Pojo> to List<Map> always gives an empty array |
STUDIO-1541 |
Datamapper does not work when running in a case sensitive file system |
STUDIO-1429 |
Xpath retrieving null when in second level calling first level fields |
STUDIO-1212 |
Response section is not displayed |
STUDIO-921 |
User should not be able to create a global element with the name of an element that already exits. |
STUDIO-3118 |
Change the way Studio handles ESB runtime changes |
STUDIO-3115 |
ClassCastException when saving multiple files |
STUDIO-3110 |
SchemaLocations get duplicated |
STUDIO-3107 |
NPE is raised after HANDSHOOK |
STUDIO-3059 |
Http outbound sets method to GET from POST when editing graphical view |
STUDIO-3057 |
Upgrade SAP connector to 2.1.0 |
STUDIO-3056 |
Magento metadata not being fetched |
STUDIO-3047 |
Add value-ref support to the Object builder for objects that cannot be persisted in the XML |
STUDIO-3045 |
NPE’s when exporting/importing project |
STUDIO-3034 |
Dynamic Endpoint Naming and Shape |
STUDIO-3031 |
Get Studio interop use cases tested and to a green status |
STUDIO-3027 |
Replace new Studio Help Files |
STUDIO-3023 |
Object Builder: when you cancel the modification of the object it is removing all the object from the XML |
STUDIO-3010 |
Rollback Exception Strategy is not well drawn in the canvas |
STUDIO-3009 |
Custom Event templates lead to XML-Graphical View exceptions |
STUDIO-2994 |
Include new examples in Studio |
STUDIO-2993 |
Update Studio’s Application Deployer in order to be up to date with the changes in MULE-6726 |
STUDIO-2989 |
Studio-created Mule archives and Maven-created are significantly different |
STUDIO-2988 |
POM-added JAR dependencies are not added to exported archive |
STUDIO-2986 |
JDBC: Problem with validation |
STUDIO-2977 |
Renaming a file by using refactor option deletes all the scripts in the file |
STUDIO-2975 |
Improve DB lookup tables usability |
STUDIO-2972 |
Maven: studio:studio duplicated referenced libraries with the ones in the Runtime (when they are transitive dependencies) |
STUDIO-2970 |
Integrate the connectors snapshot repository into the build |
STUDIO-2969 |
Set up the continuous automated testing |
STUDIO-2967 |
Maven: should detect if Maven is installed and prevent the user from enabling maven support/fail at doing maven things |
STUDIO-2966 |
Problem with validation in Script component |
STUDIO-2964 |
Metadata Cache Consistency |
STUDIO-2961 |
Inter-project dependencies are not preserved when running project |
STUDIO-2959 |
Connectivity Testing/Get Metadata Types is not using the values in the configuration dialog for Global Connectors |
STUDIO-2953 |
Avoid trying to get metadata when the connector reference is not configured |
STUDIO-2943 |
Maven: NPE when pom is not parseable |
STUDIO-2941 |
Integrate Custom Compiled Connectors into Studio |
STUDIO-2935 |
XML elements are incorrectly labeled as attributes |
STUDIO-2927 |
Not able to toggle breakpoint inside global exception strategy |
STUDIO-2926 |
Update Mule-common library to include enhanced error management and new maps features |
STUDIO-2923 |
NullPointerException when adding a query in a JDBC endpoint or connector |
STUDIO-2922 |
Arrows are rendered incorrectly when a composite source contains an endpoint whose exchange-pattern is request-response |
STUDIO-2903 |
Modify 3.4 Targeted Examples to Reflect Latest Features |
STUDIO-2885 |
Incorrect XML is generated when changing the transaction demarcation of nested transactions |
STUDIO-2868 |
Getting exception when attempting to add a SalesForce Connector |
STUDIO-2865 |
Retrieved metadata from operations must be available through different Studio session. |
STUDIO-2864 |
Data Mapper Script Editor Tree Shows fields from other element mappings |
STUDIO-2855 |
Getting RuntimeException in mapping wizard when creating an XML to Map mapping |
STUDIO-2851 |
There is a validation problem in the OrderFulfilment template project |
STUDIO-2848 |
Remote debugger doesn’t run from Mule Studio |
STUDIO-2845 |
Getting exception when attempting to do a CSV lookup |
STUDIO-2842 |
Connectors that do Not have Meta-data Should Work with new metadata enabled version of Studio without issues |
STUDIO-2841 |
Place all examples in GIT |
STUDIO-2834 |
Getting "Unknown lookup table" at runtime when using FlowRef lookup table |
STUDIO-2833 |
Remove archived examples from Studio |
STUDIO-2832 |
Studio Welcome Page Update |
STUDIO-2827 |
Mule 3.4 Pairing with Registry |
STUDIO-2820 |
New JDBC endpoint turns all previous JDBC endpoints to one-way in visual editor |
STUDIO-2802 |
Dynamic Router missing required field validations |
STUDIO-2800 |
New line character after an expression in the expression transformer breaks the flow. |
STUDIO-2788 |
Dynamic First Successful routing strategy does not allow to configure failureExpression |
STUDIO-2784 |
Addition of DB2 and MS SQL Server to the list of databases on Studio JDBC connector configuration window - Studio Work |
STUDIO-2779 |
Studio Online Help Enhancements |
STUDIO-2774 |
Should not display confirmation dialogue upon successful retrieval of metadata. |
STUDIO-2773 |
ObjectBuilder usability improvements |
STUDIO-2772 |
DataMapper should not show metadata objects as KV pairs, but as an Object |
STUDIO-2771 |
Clear metadata through right-click on connector in connections browser |
STUDIO-2769 |
Using expression transformer without specifying an expression causes the studio validation to fail but the flow itself runs fine. |
STUDIO-2760 |
Updating the set of connectors available in the connections explorer |
STUDIO-2730 |
DM concurrency issue. |
STUDIO-2719 |
Clear metadata through right-click on connector in connections browser |
STUDIO-2717 |
focus is lost when debuggin a sub flow |
STUDIO-2705 |
Should not display confirmation dialogue upon successful retrieval of metadata. |
STUDIO-2701 |
renaming a flow crashes all breakpoints |
STUDIO-2694 |
Classes from included java build path projects not available at runtime |
STUDIO-2693 |
Error database connector name needs to be unique |
STUDIO-2691 |
JDBC exchange patterns get changed |
STUDIO-2689 |
Maven: Duplicate Classpath entries when using studio:studio on a project in Studio |
STUDIO-2674 |
New DataMapper window is missing function list |
STUDIO-2660 |
Jboss Transaction Manager does not have a required attribute name |
STUDIO-2651 |
Control+D is forcefully bound to "Export Mule Studio Documentation" |
STUDIO-2650 |
Exporting and importing a project in Studio is showing an error message if the name of the project is not changed |
STUDIO-2646 |
EE features cause error when running FunctionalTestCase |
STUDIO-2640 |
Problem with validation in JDBC endpoint |
STUDIO-2634 |
Assertion error when saving a project |
STUDIO-2632 |
DataMapper leaking .fbufdrb*.tmp files |
STUDIO-2629 |
Add support to create transactional manager |
STUDIO-2628 |
Transactional endpoints are missing the NOT_SUPPORTED action |
STUDIO-2625 |
Transactional: is not being displayed when using the CE runtime |
STUDIO-2623 |
Remove validation from Java Compoenent |
STUDIO-2621 |
Transactional: Remove ee prefix from the simple transactional element |
STUDIO-2620 |
DataMapper: Streaming is not working well when using MEL |
STUDIO-2617 |
Choice: JMS is not allowed to be child element of when |
STUDIO-2615 |
DataMapper showing exception when mapping XML to xml |
STUDIO-2614 |
Connectivity Testing showing INVALID_CHARACTER_ERR in JDBC example |
STUDIO-2602 |
DataMapper: recursive code generation of 'function integer transform() \{//#CTL2' |
STUDIO-2600 |
DataMapper: auto generated mapping is generating an invalid script when using MEL |
STUDIO-2599 |
Choice: Remove wrong validation |
STUDIO-2595 |
Drag and Drop: Dragging a choice Message router inside another Choice generates a ClassCastException |
STUDIO-2593 |
As of 3.3.2 and using the default configuration, large mappings hang up without further information due to thread pool settings |
STUDIO-2591 |
The storePrefix attribute/element is silently removed from collection aggregators |
STUDIO-2584 |
Studio Debug layout changes and debugger specific perspective |
STUDIO-2583 |
Debugger breakpoints are not deleted |
STUDIO-2582 |
Debugger unexpectedly steps into Java code |
STUDIO-2581 |
Visual Flow Debugger Usability Improvements |
STUDIO-2575 |
Can’t swap between http and https once the component was saved |
STUDIO-2569 |
Deploying to CloudHub from Studio stores your username/password in plain text in a file that could be committed to source code repos |
STUDIO-2568 |
Using DataMapper prevents you from performing functional tests |
STUDIO-2566 |
Getting duplicate exception strategies when adding an exception strategy to a Transactional scope |
STUDIO-2563 |
Problem dragging and dropping exception strategies when you have unknown elements |
STUDIO-2562 |
NPE when saving a project |
STUDIO-2561 |
The "operation" drop down list is now shown when a connector has only one operation |
STUDIO-2560 |
Problem in mflow file with auxiliary-index property |
STUDIO-2553 |
Problem with validation in outbound-endpoint (Generic) |
STUDIO-2548 |
Import: problem with "import project from external location" |
STUDIO-2536 |
DataMapper: Changing the type field in a fixed width generates an NPE |
STUDIO-2525 |
One Studio: If you are using a JDBC and you change to a CE runtime you get a NPE |
STUDIO-2524 |
JDBC EE highlights the query-ref when the query is defined in another file. |
STUDIO-2520 |
Add preference for the CloudHub server in Studio |
STUDIO-2512 |
The line delimiter in the schemaLocation section is being escaped |
STUDIO-2502 |
Exception Strategies are not being shown in the canvas in CE (only in the palette) |
STUDIO-2500 |
Creating MySQL data source with empty password is not adding the empty password field in the XML |
STUDIO-2496 |
When editing Global Elements, the name gets a duplicated error by default |
STUDIO-2491 |
Splitter is still requiring the evaluator attribute |
STUDIO-2483 |
Apps using Data Mapper takes exceedingly long time to start on CloudHub |
STUDIO-2475 |
Two way editing: problem with soap version attribute |
STUDIO-2466 |
Wrong XML generation for transaction demarcation |
STUDIO-2463 |
Studio (DM) hangs when importing an empty csv file. |
STUDIO-2446 |
Connectors are not generating the XML code for the Reconnection Strategy |
STUDIO-2443 |
Debugger: Problem with debugger highlight |
STUDIO-2436 |
Problem with Hello example in Studio CE |
STUDIO-2430 |
Assertion error having loose Spring Beans in configuration file |
STUDIO-2429 |
Add HL7 messages support to data mapper |
STUDIO-2420 |
Problem with Script Component |
STUDIO-2419 |
Problem with Script Component |
STUDIO-2413 |
Breakpoints are duplicated accros projects |
STUDIO-2404 |
License Manager error when deploying certain connectors to the embedded server |
STUDIO-2401 |
Debugger: problem when adding breakpoints in a complex flow |
STUDIO-2397 |
Problem with "to Documentation" feature |
STUDIO-2392 |
Failed to read Data Mapper Schema When Running MVN Test |
STUDIO-2385 |
HTTP schemaLocation replaced by just an "s" when saving in "visual editor" |
STUDIO-2383 |
JDBC EE namespace appended to almost everything |
STUDIO-2378 |
Problem when trying to export a project to documentation |
STUDIO-2377 |
Transaction manager with activemq-xa-connector does not work |
STUDIO-2376 |
Static Component in a poll is removed when generic endpoint connector is changed or removed in Message Flow |
STUDIO-2375 |
Running within Studio, customer java classes cannot access connector classes |
STUDIO-2371 |
Import project moves source code from original location |
STUDIO-2339 |
Schema location for HTTP automatically changes and is invalid |
STUDIO-2338 |
Datamapper Complex JSON sample |
STUDIO-2337 |
Arrows disappears when adding a "Processing strategy ref"to a flow |
STUDIO-2335 |
Support for data mapper streaming |
STUDIO-2334 |
Support For Fixed width files |
STUDIO-2333 |
Flow Ref Lookups |
STUDIO-2326 |
Queued Asynchronous Processing Strategy select queue store shows error "Attribute class Required" |
STUDIO-2324 |
ERROR with drag and drop |
STUDIO-2323 |
Configuring poll frequency is generating a NPE |
STUDIO-2306 |
JDBC Queries in the connector are not being shown in the endpoint when the connector is in another file |
STUDIO-2302 |
I’m not able to edit Global Elements when the reference is in another file |
STUDIO-2282 |
Attribute name in Global Catch-Exception-Strategy not working |
STUDIO-2277 |
Incorrect validation of spring:map element when used in a Component |
STUDIO-2262 |
Erroneous Studio schema validation |
STUDIO-2258 |
Two way editing is changing the order of the transaction element |
STUDIO-2232 |
Possible Memory leak in PatternDefinition |
STUDIO-2188 |
SAP Connector duplicates sap:definition element when switching between XML and graphical. |
STUDIO-2186 |
Maven Generated studio project does not deploy correctly to cloudhub |
STUDIO-2171 |
Assertion error upon project saving |
STUDIO-2158 |
Studio - Classpath problem when having two references to mule-core within the project |
STUDIO-2058 |
Change name to CloudHub |
STUDIO-2011 |
Data Mapper Usability enhancements |
STUDIO-1999 |
Error while updating an Studio Installation after having moved it |
STUDIO-1994 |
DataMapper doesn’t show mapping information because of invalid state |
STUDIO-1992 |
Imposible to add a transaction manager from the GUI |
STUDIO-1972 |
While defining the managed-store the tooltip is used instead of the XML attribute |
STUDIO-1947 |
Mule studio is not able to draw a valid mule config |
STUDIO-1943 |
Remove map evaluator from scripting and stockquote example since it hasn’t been fixed yet |
STUDIO-1909 |
SOAP Security tab: various problems showing errors in the UI and XML tab |
STUDIO-1832 |
Studio deletes script from scripting component |
STUDIO-1825 |
If Mapping Component is already selected DM is not showing it |
STUDIO-1815 |
Rules are beeing shown in all associations |
STUDIO-1804 |
Cannot modify mapping metadata |
STUDIO-1790 |
STDIO End-Point Issue: |
STUDIO-1774 |
edit Map fields doesn’t work correctly |
STUDIO-1740 |
[Mapping Generation] Creating two structure mapping to the root generates invalid mapping |
STUDIO-1608 |
Doesn’t support passing an object inside a list by reference in Connectors |
STUDIO-1499 |
Incorrect validation in the jersey:resources component when using a spring-object reference |
STUDIO-1497 |
OutOfMemory error when modifying a flow |
STUDIO-1494 |
Data Mapper should thrown a common exception |
STUDIO-1415 |
Executing simple lookup table configuration is showing error message |
STUDIO-1404 |
Studio EE does not allow mysql-data-source at runtime |
STUDIO-1366 |
Studio regenerated mule-deploy.properties and discards changes |
STUDIO-1348 |
Delete "ee:" prefix for multi-resource transaction |
STUDIO-1334 |
Mule Studio rewrites jersey:resources loses reference to spring-object |
STUDIO-986 |
Within the jersey:resources XML element, the editor overwrites changes I make to the component element when I edit the canvas and save |
STUDIO-949 |
Global Reference across flow files |
STUDIO-539 |
Add support for multiple versions of the ESB in the framework |
STUDIO-534 |
Support multiple ESB versions in Studio (and provide new ones via the updater) |
STUDIO-66 |
Support for adding notes to a flow diagram |
STUDIO-3108 |
get-object operations XML gets broken |
STUDIO-3102 |
Stock Quote Example not functional |
STUDIO-3100 |
Metadata is not available for Twitter get-similar-places operation |
STUDIO-3093 |
Salesforce empty-recycle-bin metadata not available |
STUDIO-3035 |
Improving the way lists are managed and displayed in the Object builder. |
STUDIO-3030 |
Object Builder: additional metadata field can’t be edited |
STUDIO-3029 |
Object Builder: metadata field can’t be added to the list |
STUDIO-3024 |
Object Builder: I shouldn’t be able to set the string attribute name |
STUDIO-3022 |
Object Builder: When clicking in the + button in the object editor window, when the attribute is added the value from the last element in the list is set to the new attribute |
STUDIO-3017 |
When trying to create a new global filter from the 'filter reference' element the global elements list is empty |
STUDIO-3015 |
Debugger not stoping at the correct break point when using poll endpoint |
STUDIO-3013 |
'From message' radio button selection does not stay on |
STUDIO-3012 |
DataMapper: the InputArguments in the preview doesn’t have access to the ClassLoader |
STUDIO-3003 |
Generate Documentation is not working with Order Processing template project |
STUDIO-3002 |
DataSense: NPE when clicking OK in the object builder without configuring the object |
STUDIO-3001 |
DataMapper: Creating a CSV lookup table with an invalid file hangs Studio |
STUDIO-2997 |
DataMapper: when changing the type to Element nothing happens |
STUDIO-2958 |
DataMapper: When using the connector category the global configuration of the mapping is displayed in the combo and is causing an assertion error |
STUDIO-2956 |
Maven: add an option to manually refresh the projects dependencies |
STUDIO-2955 |
When modifying the pom.xml the .mflow file somehow gets updated and you need to save it again before running the project |
STUDIO-2951 |
debugger doesn’t stop if breakpoint is set on sub-flow |
STUDIO-2950 |
DataSense should use the proper type field depending on the connector. |
STUDIO-2949 |
Groovy Editor entirely missing script text |
STUDIO-2939 |
Can not import my own classes in datamapper script |
STUDIO-2937 |
Using CSV lookup tables which map integer input to string output causes exception |
STUDIO-2930 |
Elements are ignored when creating a data mapping flow with XML as input or output |
STUDIO-2910 |
Dragging elements inside the ALL processor generates incorrect XML |
STUDIO-2902 |
Breakpoint not working after Datamapper component |
STUDIO-2901 |
Generate Default feature of the Fixed Width mapping type is not warning user to set the width of the fields |
STUDIO-2874 |
Dragging the Reference Exception Strategy outside of the flow causes the strategy to disappear |
STUDIO-2856 |
Part of the mapping wizard blanks out |
STUDIO-2853 |
Unexpected error while creating data mapping from connector |
STUDIO-2817 |
Excel To JSON template looks for the wrong type of excel spreadsheet |
STUDIO-2799 |
Dynamic First Successful is not default in the UI |
STUDIO-2795 |
A Rollback Exception Strategy on a flow prevents the generation of documentation for that flow |
STUDIO-2793 |
When debugging a project for the first time, debugger view says that debugger is not running |
STUDIO-2758 |
Mulexml namespace silently deleted by graphical editor |
STUDIO-2754 |
Maven: Upon project creation, the use of Maven for building the project should be an 'opt-in' |
STUDIO-2752 |
MySQL Data Source host and database properties should not be mutually exclusive |
STUDIO-2713 |
Groovy editor needs horizontal scroll |
STUDIO-2710 |
Maven: As a user, I’d like to turn the Studio Support for Maven on/off on a per project basis |
STUDIO-2704 |
Message variables should be alpha sorted |
STUDIO-2702 |
can name an input contact-dynamics in dm editor but fails during runtime |
STUDIO-2698 |
Debugger view should show the message |
STUDIO-2683 |
DataMapper can’t save config |
STUDIO-2679 |
DataMapper doesn’t recognize java.sql.Date and exposes its internal attributes instead |
STUDIO-2677 |
debugger logs should not be shown |
STUDIO-2676 |
Console should be bring to front when building an application with mvn |
STUDIO-2669 |
Debugger view doesn’t follow you when flow ref points to a differnet file |
STUDIO-2665 |
Studio reports numerous bogus validation errors for valid Spring beans |
STUDIO-2664 |
Impossible to change an input POJO with "re-create metadata" |
STUDIO-2662 |
Resize DM new input argument dialog so the expression field is visible |
STUDIO-2661 |
Inconsistent Port # between Mule ESB and Studio Remote Debug Config |
STUDIO-2658 |
Empty error box appears when trying to edit a Generic endpoint |
STUDIO-2657 |
Creating a DataMapper component referencing existing .grf using the drag and drop feature is not working correctly |
STUDIO-2654 |
Widget is dispose error when re-creating metadata |
STUDIO-2648 |
Error marker appears in the previous component |
STUDIO-2639 |
Export to DOCs brings an NPE if you clic when no project is opened |
STUDIO-2636 |
Documentation generation doesn’t work when Flow name contains strange characters |
STUDIO-2626 |
DataMapper: EmptyStackException when trying to configure an input List (POJO) |
STUDIO-2611 |
Class attribute on custom-processor not recognized. |
STUDIO-2608 |
DataMapper: quote string attribute is not being updated in the mapping |
STUDIO-2606 |
DataMapper: When deleting the Element Mapping the script is not updated |
STUDIO-2604 |
Reference Exception strategy should be able to be dropped inside a choice exception strategy |
STUDIO-2598 |
Connectivity testing is disabled |
STUDIO-2594 |
One Studio: problem when updating JDBC namespace |
STUDIO-2590 |
NPE when running hello example using 3.4 M2 CE runtime |
STUDIO-2586 |
DataMapper: Exception generated when using an invalid JSON file |
STUDIO-2585 |
Problem when debugging a project with errors |
STUDIO-2580 |
Breakpoints should be deleted when I delete a message processor that has a breakpoint |
STUDIO-2574 |
refs do not support spring beans |
STUDIO-2571 |
Quartz jobs cannot be stateful |
STUDIO-2570 |
jdbc outbound endpoint doesn’t like expressions as query key |
STUDIO-2559 |
Datamapper parses JSON incorrectly, fiels inside the collection are marked as unrelated |
STUDIO-2556 |
Queries showing Required Attribute not defined error when having Enters in the XML |
STUDIO-2541 |
adds class attribute to component inside rest message processor when using Spring inside |
STUDIO-2532 |
Connection View is generating an NPE when changing the ESB runtime version |
STUDIO-2531 |
Debugger: problem with highlight |
STUDIO-2523 |
Debugger: Add the Debugger 'Disable Timeout' option to the Studio Preferences |
STUDIO-2521 |
Debugger: the 'Mule Debugger View' is not bring to front after pressing F6 a couple of times |
STUDIO-2516 |
Connector libraries should be added to the Classpath when creating global connectors for connectors |
STUDIO-2510 |
Escaping the 'Returns' in the JDBC querys when we should not |
STUDIO-2509 |
DataMapper: when the output is a CSV file, I’m not able to clic on finish until I clic first in 'Edit Fields' |
STUDIO-2507 |
DataMapper: when setting the data type to Element or List<Element> the change is not updated |
STUDIO-2505 |
Removal of multiple output fields only removes one field |
STUDIO-2501 |
Creating a new JDBC connector is not refreshing the mule resource explorer |
STUDIO-2498 |
Default UTF-8 encoding not persisted when the GRF is generated |
STUDIO-2494 |
DataMapper: EmptyStackException |
STUDIO-2488 |
Data Mapper arbitrarily assigns order of elements |
STUDIO-2486 |
Two way editing: Groovy script transformer is not working correctly |
STUDIO-2485 |
Upgrading to Latest Mule Studio causes single quotes to be escaped in XML |
STUDIO-2482 |
Choice Router cannot edit routes in Win32XP |
STUDIO-2479 |
Resource Explorer: it’s not working when there are unknown global elements |
STUDIO-2477 |
Debugger: Clear all breakpoints it’s not refreshing the UI |
STUDIO-2476 |
Studio Dock icon is a red quadrate |
STUDIO-2469 |
DataMapper: Flow ref lookup table cannot be resolved |
STUDIO-2468 |
Add MEL support to DataMapper |
STUDIO-2467 |
Add Remote debugging support to Studio |
STUDIO-2459 |
In the DataMapper, objects cannot be enriched from complex objects |
STUDIO-2453 |
cannot map to Map<Native, Pojo> |
STUDIO-2451 |
Expression Transformer/Filter: "evaluator" attribute is considered as required, but it should not be |
STUDIO-2445 |
DB lookup fields displayed in the Mappings view does not have the correct field names |
STUDIO-2444 |
Extract to flow is not working |
STUDIO-2433 |
Maven: studio should add dependencies to the pom.xml automatically for maven projects |
STUDIO-2426 |
Element: Property Placeholder is not allowed to be child of element Beans |
STUDIO-2424 |
Don’t delete XML elements when removing connectors from Studio |
STUDIO-2422 |
cannot update mule studio from 1.3.0 to 1.3.1 |
STUDIO-2417 |
Running maven projects in studio could cause: "There are two transformers that are an exact match for input" error |
STUDIO-2415 |
Debugger: the breakpoints in the SOAP component are not reflected in the UI until you go back and forth to the XML view |
STUDIO-2412 |
If when start debugging you are in the XML view and after send a message you change to the canvas view, the current MP is not selected. |
STUDIO-2410 |
Script wrapped with a CDATA in the flows are breaking the To Documentation feature documents |
STUDIO-2408 |
Missing first flow in the To Documentation generated documentation for some projects |
STUDIO-2406 |
Invalid XML format when generating Documentation using To Documentation Feature |
STUDIO-2396 |
Move <tracking:transaction> to be the first element of the flow instead of the last one |
STUDIO-2387 |
Pasting jdbc prefix into studio causes studio to attempt to fix the namespaces |
STUDIO-2379 |
Add verification to "Extract to Flow/Subflow" functionality |
STUDIO-2373 |
Editing field does not show the type for certain xmls |
STUDIO-2369 |
"Widget is disposed" error is thrown each time a processor is modified |
STUDIO-2366 |
Maven Libraries not exported to MMC but are to MuleStudio Zip |
STUDIO-2363 |
Not Filter doesn’t validate nested elements |
STUDIO-2362 |
Add refactor method for a selection of message processors |
STUDIO-2357 |
Problem in default value in catch exception strategy |
STUDIO-2354 |
Breakpoints should be persisted |
STUDIO-2331 |
Move Poll, All and Compoiste Source to the framework |
STUDIO-2330 |
Improve the saving speed, when using big files the speed of saving can be very slow |
STUDIO-2329 |
Use the current server XSD to perform XML validations |
STUDIO-2318 |
Allow the user to export the project documentation he creates. |
STUDIO-2314 |
Unable to delete Scripting Text |
STUDIO-2305 |
Problem when undoing drag operation in an unsaved project |
STUDIO-2303 |
Add Connectivity Testing support in Studio |
STUDIO-2301 |
JDBC Connector: Transaction per Message in Advanced tab should be ticked by default (true) |
STUDIO-2297 |
Problem with nested element validations |
STUDIO-2291 |
Once you drag and drop an Exception Strategy out of a flow you are not able to put it back where it was |
STUDIO-2290 |
I’m not able to drop an endpoint before a foreach inside a choice |
STUDIO-2289 |
Each time you modify something in the flow the script text within a Script component gets moved to the right in the xml |
STUDIO-2283 |
Attribute name from flow-ref should accept mule expression |
STUDIO-2279 |
Some improvements are needed in the echo example embedded in Studio |
STUDIO-2276 |
DM data source editor |
STUDIO-2275 |
Cannot edit property name |
STUDIO-2273 |
Red underline int the XML view is not always updated properly |
STUDIO-2267 |
Can no longer deploy iApp with Data Mapper components onto Cloudhub |
STUDIO-2256 |
Property placeholder creates XML validation error when using property placeholder |
STUDIO-2253 |
Enable the override of the category in which a extension is displayed in the palette |
STUDIO-2248 |
Global Elements duplicate name problems do not disappear when they are resolved in another file |
STUDIO-2242 |
Data Mapper DB Lookup Table - Green + icon does not do anything |
STUDIO-2233 |
Copy to Workspace checkbox |
STUDIO-2231 |
Hyphen / Dash in logger message content will cost UI to indicate error |
STUDIO-2224 |
Username is not saved between deploys when deploying to cloudhub |
STUDIO-2223 |
Property place holder reports error for path with a system variable |
STUDIO-2212 |
Enricher & For-Each will mess up the lines in the flow editor |
STUDIO-2208 |
Studio crashed when saving Data Mapper changes |
STUDIO-2207 |
When using Global Endpoints, an endpoint with both ref and connector-ref gives a false error at design time |
STUDIO-2194 |
Spring Property Placeholder - Studio tries to validate if a filename containing a variable exists |
STUDIO-2187 |
can’t install a devkit 3.3.1 connector |
STUDIO-2185 |
Selecting Excel example file causes error in Data Mapper |
STUDIO-2184 |
HTTP inbound endpoint’s editor fills host and port properties when address is set |
STUDIO-2183 |
Using csv-to-maps-transformer throws unable to locate NamespaceHandler error. |
STUDIO-2177 |
XML autocomplete uses a wrong schema alias |
STUDIO-2140 |
Editing of DataMapper expressions - formatting can be lost or corrupt map |
STUDIO-2138 |
Add support for quoted strings in data mapper |
STUDIO-2114 |
Mule Studio does not allow to choose server runtime |
STUDIO-2111 |
<message-properties-transformer> scope="invocation" property missing after ui interaction |
STUDIO-2105 |
Unable to drag from the canvas a Twitter neither a Salesforce Streaming into a composite source already placed on the canvas |
STUDIO-2097 |
IMAP connector, the INBOX and Move To folders are IMAP folders not local file system |
STUDIO-2060 |
Zuora connector putting zquery values with linebreaks, leading to error messages. |
STUDIO-2052 |
mule-project.xml Checked On By Default |
STUDIO-2037 |
Echo Example - Change the name of the flow and XML to Echo |
STUDIO-2033 |
jdbc-ee:mysql-data-source empty user password gets removed |
STUDIO-2023 |
Data Mapper UI is slow with big structures |
STUDIO-2019 |
Connectors don’t get exported |
STUDIO-1986 |
Exception on saving project |
STUDIO-1954 |
DataMapper - Support for Custom Java Functions |
STUDIO-1953 |
DataMapper - Complex XMLs - Ability to handle recursive elements in the XML |
STUDIO-1910 |
Twitter connector - show status operation - incorrect parameter type |
STUDIO-1881 |
Global connector are not shared among different flow as they should |
STUDIO-1876 |
Error markers disappear when opening flow properties |
STUDIO-1845 |
Updating namespaces upon initial opening of earlier version flow puts object-to-string transformer in EE namespace |
STUDIO-1829 |
FTP Global Element Properties: always goes back to "Delete files after processing" |
STUDIO-1809 |
XML validation should be done using mule schemas |
STUDIO-1807 |
Cache dialog loses strategy |
STUDIO-1780 |
OAuth configuration not available |
STUDIO-1778 |
Structure Mapping Condition is not generating correctly |
STUDIO-1772 |
Processing Strategy Ref doesn’t get set on a flow in XML |
STUDIO-1753 |
Groovy component - Script Text Field |
STUDIO-1736 |
Getting Java Null Pointer Exception in the error logs when closing a project that contains Datamapper |
STUDIO-1725 |
Custom Business Event: namespace version issue |
STUDIO-1724 |
User wants to install and use multiple Mule ESB runtimes |
STUDIO-1723 |
Apply a Mule ESB patch in Studio |
STUDIO-1712 |
Datamapper: When maaping to an XML I’m not able to scpate some attribute to be a CDATA so that it can contain any character |
STUDIO-1702 |
Date on the CC features are incorrectly generated and lead to improper updates |
STUDIO-1701 |
Referenced Libraries not updated properly after updating CC feature |
STUDIO-1697 |
Yammer-Connector "authorize" operation (required for OAuth) cannot be edited in Studio with GUI editor |
STUDIO-1696 |
config-ref attribute viewed as Error for Yammer (OAuth based) connector |
STUDIO-1690 |
The file selection of a Groovy script file in the Groovy component properties shows a popup menu at the wrong time |
STUDIO-1689 |
When installing a new connector license is not shown for the connector |
STUDIO-1680 |
The New Project wizard allows the creation of flows with an empty name |
STUDIO-1678 |
Scripting transformer/component should use the namespace <script:> instead of <scripting:> |
STUDIO-1616 |
Data Mapper can’t auto-detect types of a connect when it’s in a <poll> tag |
STUDIO-1602 |
An <all> element without <processor-chain>s does not draw properly |
STUDIO-1600 |
Add support for Spring Property Placeholders |
STUDIO-1587 |
Connectors: the Configuration reference is lost the first time you do it |
STUDIO-1575 |
Remove Connectors from Studio |
STUDIO-1565 |
Input arguments are not being converted automatically |
STUDIO-1564 |
Perview panel does not execute latest changes when modified |
STUDIO-1508 |
Studio renames XML namespace without renaming schema location for email schema |
STUDIO-1506 |
Spring object bean being deleted |
STUDIO-1473 |
Method attribute disappears from the endpoint |
STUDIO-1466 |
Working with wrong JSON files, does not report the error properly |
STUDIO-1457 |
Response Portion for REST/SOAP flows |
STUDIO-1434 |
XSLT Transformer places xslt text in wrong namespace |
STUDIO-1427 |
xml mapping showing pieces of empty Xml structure |
STUDIO-1424 |
Deleting a mapping flow is not automatically closing the mapping flow |
STUDIO-1403 |
NPE when opening a flow in a new project |
STUDIO-1400 |
I can’t add timeout to endpoint-polling-job |
STUDIO-1398 |
Two-way editing: Opening flow configuration and clicking on OK removes default exception strategy from the XML |
STUDIO-1364 |
Dialogs are too wide when the description is too long |
STUDIO-1313 |
Generate a documentation from FLOW |
STUDIO-1083 |
Inconsistencies regarding some validations for Splitter, Expression Transformer and Expression Filter |
STUDIO-1066 |
Order Operations List in SOAP component |
STUDIO-971 |
No way to add a transaction manager from the "Global Elements" so one can use XA transactions |
STUDIO-961 |
In the "Configuration XML" tab, within some XML elements, auto-completion is showing all possible XML elements regardless of schema constraints |
STUDIO-948 |
Underline only the attribute or if it is missing the line where it should be located when getting errors in the XML |
STUDIO-937 |
Resource attribute is not implemented in the UI and throws an error that it is not a valid property while it is valid and it is suggested in the auto-completion |
STUDIO-936 |
Warning is shown when an expression is used as a path in a file endpoint |
STUDIO-908 |
Improve Beans user interface |
STUDIO-722 |
GUI framework modeSwitch should support ordering |
STUDIO-660 |
zip files in external libraries not added into lib folder when exporting the project |
STUDIO-637 |
Elements repeated for the autocompletion feature |
STUDIO-306 |
When using HTTP with address and delete the port that is displayed by default, the port is not removed and causes errors when running the app |
STUDIO-77 |
Support for transaction demarcation |
STUDIO-3126 |
Add a 'Don’t warn me again' checkbox to the warning popup that communicates that the maven installation could not be found |
STUDIO-3117 |
Project name field allows non-ascii characters (it shouldn’t) and then the project creation does not work |
STUDIO-3052 |
Transaction Action NOT_SUPPORTED is missing in autocompletion |
STUDIO-3040 |
Maven: when no maven installation is found the error message shows a null location |
STUDIO-2991 |
Change export documentation icon |
STUDIO-2948 |
CSV Lookup table showing wrong field labels |
STUDIO-2921 |
Global element remains in Global Reference list after it is deleted |
STUDIO-2920 |
Filter cannot reference spring beans |
STUDIO-2914 |
Moving through different datamapper components in script view does not refresh the view correctly |
STUDIO-2857 |
Output "Generate default" doesn’t work if an example is used as input |
STUDIO-2847 |
DM messes up mappings when having multiple XML elements that permit text content |
STUDIO-2839 |
Studio removes newlines in script component |
STUDIO-2801 |
Dynamic route Contract ID should not be displayed at all when in 'Service' lookup type |
STUDIO-2768 |
In the Mule Debugger View, editing the Message Processor’s Value column causes an exception |
STUDIO-2755 |
Maven: should have feedback while studio:studio is being run upon project creation |
STUDIO-2749 |
Error signs are attributed to a wrong element in the Message Flow canvas when dragging a Reference Exception Strategy |
STUDIO-2746 |
Autocompletion does not display a list outside flow elements |
STUDIO-2744 |
Scrolling in autocompletion is behaving erratically |
STUDIO-2715 |
if app gets redeployed stopped debugger does not follow |
STUDIO-2659 |
Error marker is not showed at the correct component |
STUDIO-2652 |
A new console is created and kept open for each start of a Mule Maven project |
STUDIO-2579 |
Cache element inline doc is wrong |
STUDIO-2515 |
HTTP inbound endpoint: if no exchange pattern was set in the XML the endpoint should be shown as request-response |
STUDIO-2513 |
Salesforce: problem with the List of Maps UI |
STUDIO-2421 |
To Documentation feature should warn user that the project is not saved |
STUDIO-2399 |
No field to specify WSDL in SOAP dialog box |
STUDIO-2394 |
FTP endpoints are always in passive mode |
STUDIO-2391 |
Missing dot in file name when saving a flow snapshot (screenshot) |
STUDIO-2390 |
Selecting Input Argument from drop-down in lookup table not working if user doesn’t do focus out |
STUDIO-2370 |
Export flow image to file generates wrong filename |
STUDIO-2342 |
Max Idle field in Advanced tab of XSLT should accept "0" value as valid input. |
STUDIO-2311 |
Convert Java Project to Mule Project Improvement |
STUDIO-2284 |
Flow ref component adds an invalid option in the combobox |
STUDIO-2281 |
testing jira for new workflow |
STUDIO-2280 |
Key word search does not show Exception Strategies when writing 'exc' |
STUDIO-2129 |
XSLT Transformer - Xslt text entered in "XSLT Content" text area should not be escaped. |
STUDIO-2067 |
Datamapper Tabs on Bottom are unintuitive |
STUDIO-1998 |
Output bean type should support Interface |
STUDIO-1946 |
Add an option to the pop up to convert an existing Eclipse project into an Studio one |
STUDIO-1928 |
Wrong icon on project setup |
STUDIO-1875 |
File config - enable stream tooltip - uncomplete description |
STUDIO-1866 |
</mule> closing tag is not well indented |
STUDIO-1734 |
Business is misspelled in the flow configuration dialog |
STUDIO-1716 |
User wants to export an image of the current flow in order to display how it works to others |
STUDIO-1687 |
Wrong configured Salesforce connector doesn’t show error mark |
STUDIO-1686 |
When installing new software a 'connector' name element is shown for the added connector |
STUDIO-1685 |
Scrolling problem within classpath configuration |
STUDIO-1663 |
SAP endpoint - Need to resize the configuration dialog by default so that text is not displayed cut |
STUDIO-1614 |
Data mapper logs too much |
STUDIO-1611 |
JDBC endpoint: the Key: combobox is not aligned with other combo boxes in the General tab |
STUDIO-1495 |
No warning is displayed when erasing a lookup table |
STUDIO-1455 |
attribute 'name' in element 'cxf:jaxws-client' is only allowed to be mule expression or integer due to validation.. should be able to use wsdl port (String) |
STUDIO-1223 |
Connector operation names are generally ill-named and badly capitalized |
STUDIO-1051 |
Flow reference description does not fit the window. |
STUDIO-2886 |
Transaction actions appear at the bottom of the list of possible values |
STUDIO-2846 |
Misspelled word in lookup assignment dialog |
STUDIO-1745 |
Create a way to export image/print flow and data mappings |
STUDIO-1410 |
Advanced Editor wrongly showing unsaved transformations message |
STUDIO-1341 |
dragging flow from project explorer onto canvas causes studio to hang |
STUDIO-3072 |
Throwable Error in DataMapper |
STUDIO-3061 |
Connector not added to the classpath |
STUDIO-2971 |
Ouput field names containing certain numeric values will corrupt on Data Mapper |
STUDIO-2852 |
Data Mapper is unable to load large (>1 MB) HL7 messages in a timely manner (currently takes ~10mins) |
STUDIO-2576 |
static-resource-handler doesn’t work when http inbound doesn’t have path attribute |
STUDIO-2356 |
When breakpoints are removed from the breakpoints view the canvas figures should be updated |
STUDIO-2136 |
MySQL Data Source does not come with mysql driver |
STUDIO-2044 |
Http Endpoint Resets Default Value |
STUDIO-1698 |
Expression Filter being marked as invalid when its not |
Mule Management Console
MP-274 |
On Applications, filter by application name doesn’t work |
MP-236 |
On Rest API, creating a deployment with empty name, generates error 500 instead of 400 |
MP-299 |
On Rest API, when listing flows, password information is shown for secure protocols (eg sftp) |
MP-275 |
SFTP endpoint shows details about user and password |
MP-295/SE-39 |
SFTP username and password visible in plain text in MMC |
- |
Improved visualization of JMX trees with clusters |
MP-15 (pt.) |
Allow to apply alerts to clusters in the alert definition panel (alerts apply to each node in the cluster individually) |
SAP Connector
SAPCONN-86 |
JCoServer conflict when starting two applications in the same Mule ESB instance |
SAPCONN-87 |
Trace To Mule Log files not working as documented |
SAPCONN-88 |
jcoLang in Connector gets overriden by default value in endpoint |
SAPCONN-91 |
Two inbound endpoints cannot use the same connector |
SAPCONN-95 |
Using payload with encoding different form UTF-8 |
SAPCONN-96 |
Error when SAP transport is deployed |
SAPCONN-141 |
Add support for <transactional> in outbound-endpoint |
SAPCONN-142 |
BAPI_TRANSACTION_COMMIT not being called in SRFC BAPI Transactions |
SAPCONN-147 |
XML text input from tab "XML Definition" of endpoint dialogue makes repeated copy to its configuration |
SAPCONN-148 |
The SAP transport throws an exception if Evaluate Function Response is true and a RFC function is defined to return exceptions |
SAPCONN-149 |
The SAP transport throws an exception even if Evaluate Function Response is false. |
SAPCONN-150 |
SAP transport throws an exception If Evaluate Function Response is true and a RFC function is defined to return both the export parameter and the table, but the export parameter doesn’t have "RETURN" |
SAPCONN-152 |
Mule Studio doesn’t support the attribute jcoTrace. |
SAPCONN-153 |
The SAP transport updates table parameter incorrectly. |
SAPCONN-156 |
SapJcoServerListener.handleRequest() has an exception initialization bug. |
SAPCONN-159 |
evaluateFunctionResponse not working when BAPI has an exception list |
SAPCONN-160 |
SAP Connector editor doesn’t support JCoTrace and JCoTraceToLog |
SAPCONN-162 |
NullPointer exception when flow starting with sap inbound endpoint returns null |
SAPCONN-165 |
SAP Connector can’t handle dynamic credential correctly for second request. |
SAPCONN-170 |
Exception thrown when RETURN record has CODE instead of NUMBER |
Mule DevKit
DEVKIT-348 |
Generated Pool Factory is not returning connected objects causing pool exhaustion |
DEVKIT-337 |
Create library for DevKit runtime dependencies |
DEVKIT-336 |
generated OAuth manager doesn’t compile due to bad getter name |
DEVKIT-312 |
Parameters for processors can’t be of types with cycles in their Class hierarchies |
DEVKIT-349 |
Version checker in LifecycleAdapter is not working |
DEVKIT-287 |
Problems with generated yyyyyConnectorOAuthClientFactory validateObject method |
DEVKIT-240 |
Add support for Set |
DEVKIT-314 |
Parameter names are not honored if the type is a Map or a List |
DEVKIT-62 |
Shade of DevKit annotations and interfaces |
DEVKIT-316 |
RetryIntereceptor will retry with all exceptions (only managed ones should be taken into account) |
DEVKIT-347 |
maxWait parameter for pool configuration not supported in Studio |
DEVKIT-147 |
Mime integration Test does not test anything |
Third Party Connectors and other modules
At this time, not all of the third party modules you may have been using with previous versions of Mule ESB have been upgraded to work with Mule ESB 3.4.0. Contact MuleSoft if you have a question about a specific module.
Migrating from Mule ESB 3.3.X to 3.4.0
The following sub-sections offer details on the changed and improved behaviors that Mule ESB 3.4.0 introduces.
Custom HTTP Transport Message Receivers
To support the new throttling functionality in Mule, the behavior of HTTP transport message receivers changed. While an improved to out-of-the-box HTTP receivers, the change may introduce issues with any custom HTTP transport message receivers you may have configured.
To adjust existing custom receivers and migrate to Mule 3.4.0:
Custom HTTP Receiver inherits from: |
Adjust to extend from: |
|
HTTP |
org.mule.transport.http.HttpMessageReceiver |
org.mule.transport.http.OldHttpMessageReceiver |
HTTPS |
org.mule.transport.http.HttpsMessageReceiver |
org.mule.transport.http.OldHttpsMessageReceiver |
However, if you prefer to use the previous implementation of HTTP transport message receivers in your custom receivers, you can revert to the previous behavior.
Per server |
Add attached preferred-http.properties and preferred-https.properties file in $MULE_HOME/conf/META-INF/services/org/mule/transport dir of the mule server |
Per connector |
Configure the connector to use the old implementation as per the following code: HTTP
HTTPS
|
File, FTP, and SMTP Outbound Properties
For the above-listed endpoints, some outbound properties are no longer available. (The inbound properties remain the same.) If you have configured your endpoints with any of the endpoints in the table below, change the property to a inbound.
Endpoint | Outbound Properties Not Available |
---|---|
File |
|
FTP |
|
SMTP |
|
Jackson Upgrade
Mule includes native support for JSON via the Jackson library. To take advantage of several bug fixes, Mule 3.4.0 uses the latest updated version: Jackson 1.9.11.
JCA Removal
In Mule 3.4.0, we have removed the support modules used for the following distributions:
-
mule-module-jca-core
-
mule-module-jca-generic
-
mule-module-jca-jboss
localhost Behavior
Mule ESB 3.4.0 adjusts the behavior of the TCP server socket binding to provide better security by default. This change affects the following transports: TCP, SSL, HTTP, HTTPS and Jetty.
Previously, localhost binding opened your local system to all public interfaces. This presented a potential security risk as it opened an unsecure channel to your private local system. By default, TCP server socket bindings in Mule applications now bind to the defined localhost on your computer, usually the loopback, 127.0.0.1. This change means that when you bind to localhost, you alone will be able to access the Mule application. To make the application available to all public interfaces beyond your own local system, bind to 0.0.0.0.
This added security feature will change the behavior of any localhost bindings currently in place in your existing Mule applications– anything bound to localhost restricts access to you alone on your local system.
However, if you prefer to keep localhost open to all public interfaces (i.e. revert to previous behavior for localhost), you can adjust an environment variable to ensure open access of localhost bindings. Set the following variable on your local environment: mule.tcp.bindlocalhosttoalllocalinterfaces = true
We strongly recommend, however, that rather than use the environment variable to enable open access by all public interfaces, you adjust the binding on any existing Mule application to 0.0.0.0 as described above. Taking this step ensures that the binding behavior is consistent across applications.
-
localhost = 127.0.0.1 = local access only
-
0.0.0.0 = access by all public interfaces
This change may cause confusion if the name of your computer is localhost. In practice, this issue usually only surfaces with Mac computers. Check the name of your computer (System Preferences > Sharing) and change it to something other than localhost to prevent issues with interfaces. |
Maven and Anypoint Connectors
When working with a Maven project in Studio, Mule seamlessly and automatically updates all Anypoint connector dependencies. This dependency support ensures that any connectors you use in your flows always have the correct dependencies updated for Maven. We recommend updating any connectors you may use in your Mule applications to the latest versions to ensure that your connectors, and their dependencies, are all up-to-date.
However, if you prefer to continue using older versions of connectors in your Maven project in Studio, you can disable Maven support in Studio, which also disables the automatic updates of connector dependencies. * Contact MuleSoft for more details about how to disable Maven to maintain the use of older connectors.
Model Deprecation
The use of Models is formally deprecated along with services in Mule 3.4.0 and will be removed in Mule 4.0. This includes the SedaModel configured with the <model>
XML element and any custom implementations. Further, support for flows configured inside a model is now deprecated. You can configure a flows outside a <model>
elements without incurring any differences in behavior.
Mule Expression Language and NullPayload
To improve usability, Mule Expression Language (MEL) no longer exposes org.mule.transport.NullPayload
.
In Mule 3.4.0, if the message payload is an instance of NullPayload
, the expression #[message.payload]
returns null (not NullPayload)
. This slight adjustment allows easier value testing via expressions. If you are currently testing payload value in your MEL expressions using NullPayload
, be sure to update your expressions to use null
.
Previously | Currently |
---|---|
#[message.payload is org.mule.transport.NullPayload] |
#[message.payload == null] |
#[message.payload is org.mule.transport.NullPayload] |
|
#[message.payload instanceof org.mule.transport.NullPayload] |
Groovy expressions remain unaffected by this change to Mule Expression Language. |
Mule Expression Language MVEL Upgrade
To leverage the many bug fixes available in the latest version of MVEL, we have upgraded the expression engine that Mule Expression Language leverages to MVEL 2.1.3.
SAP Connector Changes
Because transaction support in the SAP Connector version 1.x is very limited (only transactions with one function call are allowed), we have made improvements to SAP Connector 2.1.0 to support more complex transactions. Thus, the attribute bapiTransaction
is no longer present at the transaction level; it has moved to the outbound endpoint.
For detail about the use and configuration parameters of the bapiTransaction attribute, refer to Outbound Endpoint Transactions.
Services Deprecation
Services, both SedaSrvices configured via the <service>
XML element and custom services configured via the <custom-service>
XML are formally deprecated in Mule 3.4.0 and will be removed in Mule 4.0. All functionality provided by services can be accomplished, with significant advantages, using flows. For further information about migrating from Services to Flows see the explanatory blog post.
Spring Upgrade
To leverage the newest features in Spring features, Mule has adopted Spring 3.2.1. Review new features of Spring 3.2.1 and examine the related Spring Migration Guide.
UDP Connector
To ensure consistency amongst transports, the UDP connector’s packet.address
and packet.port
properties now have an inbound scope.
Undeployment of Applications
As an improvement, Mule now invokes the undeployment of an application when you remove its anchor file. Previously, removing an anchor file resulted in a failure to invoke undeployment– an app without an anchor file could run indefinitely. This change ensures consistent behavior upon removal of an anchor file.
User Object Store
Utilized primarily by Mule Extensions and Anypoint Connectors, User Object Store has been changed to become persistent by default. (By default, User Object Store used to be transient.)
However, if you prefer that User Object Store be transient, you can disable persistence by adjusting the following system property: mule.objectstore.user.transient="true"