diff --git "a/database/tawos/tfidf/MULE_tfidf-se.csv" "b/database/tawos/tfidf/MULE_tfidf-se.csv" new file mode 100644--- /dev/null +++ "b/database/tawos/tfidf/MULE_tfidf-se.csv" @@ -0,0 +1,2936 @@ +"issuekey","created","storypoint","context","codesnippet","t_Bug","t_Enhancement.Request","t_Story","t_Task","t_Epic","c_Build..Distributions","c_Modules..XML..XSLT..XPath..SXC","c_Core...other.","c_Core..Routing...Filters","c_Build..Libraries...Dependencies","c_Modules..CXF","c_Transport..FTP...SFTP","c_Transport..Quartz","c_Core..Components","c_Transport..HTTP.S....Jetty","c_Core..Exception.Handling","c_Core..Transports","c_Transport..JMS","c_Core..Containers","c_Core..Logging","c_Build...other.","c_Mule.Core","c_Core..API","c_Module..APIKit","c_Modules...other.","c_Build..Integration.Tests","c_Transport..JDBC","c_Core..Concurrency...Threading","c_Build..Maven","c_Core..Event.Message","c_Modules..Devkit.Support","c_Core..Transactions","c_Transport..AJAX","c_Core..Streaming","c_Transport..Email","c_Modules..XA.Transactions","c_Core..Queues..SEDA....Persistence","c_Core..Flow","c_Core..Domains.shared.resources","c_Transport..TCP...UDP...SSL...Multicast","c_Core..Bootstrap...Standalone","c_Modules..WS.Consumer","c_Core..Deployment","c_Tools","c_Core..Configuration","c_Core..Registry","c_Build..JDK.Compatibility","c_Core..Services","c_Core..Transformers","c_Core..Properties","c_Core..Watermark","c_Core..Expressions","c_Examples...Tutorials","c_Transport..VM","c_Modules..Management...JMX","c_Modules..HTTP","c_Core..Endpoints","c_Core..Lifecycle","c_Extensions.API","c_Transport..File","c_Schema","c_Documentation...Website","c_Tools..Archetypes","c_Modules..Security..Spring.Security..Acegi..PGP..WS.Security.","c_Modules..Jersey","c_Batch","c_Core..Sessions","c_Core..Non.Blocking","c_Transport..Axis","c_Transport..XMPP..Jabber.","c_Extensions","c_sdk","c_e..DataSense","c_Modules..File","c_Core..DSL.processing","c_Core..Classloading","c_Test..Testing.Framework","c_Modules..FTP","c_Modules..Email","c_Extensions..Maven.Plugin","c_Core..Agents","c_Modules..MuleClient","c_Modules..Sockets","c_Core..Policies","c_jms.module","c_Tooling.Client","c_Core..Request.Reply","c_soap","c_mule4","c_Service..HTTP","c_Modules..RSS...ATOM","c_Core..ObjectStore","c_Debugger","c_Interception.API","c_Service..SOAP","c_Connector..DB","c_Tooling.API","c_Module..Aggregators","c_Connector..ObjectStore","c_core..Notifications","c_Modules..OAuth","c_Connector..VM","c_Service..Scheduling","c_SDK.AST","c_Mule.Runtime" +"MULE-4223","02/28/2009 00:59:32",0,"Use of tr [:upper:] [:lower:] | tr -d [:blank:] in bin/mule fails on Solaris 10 ""When trying to run bin/mule on a Solaris 10 system following error occurs Bad string Bad string Bad string Bad string Your machine's hardware type (uname -m) was not recognized by the Service Wrapper as a supported platform. Please report this message along with your machine's processor/architecture. Error occurs on line 389 DIST_OS=`uname -s | tr [:upper:] [:lower:] | tr -d [:blank:]` and again on 419 PROC_ARCH=`uname $UNAME_PROC_OPTION | tr [:upper:] [:lower:] | tr -d [:blank:]` of bin/mule in the 2.1.2 release This syntax is not supported on Solaris 10 to fix use on line 389 DIST_OS=`uname -s | tr [A-Z] [a-z] | tr -d ' '` and line 419 PROC_ARCH=`uname $UNAME_PROC_OPTION | tr [A-Z] [a-z] | tr -d ' '` ""","",1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-5382","01/31/2011 22:18:29",0,"XSL Transformation fails with xsl:result-document on repeated transformations ""xsl:result-document outputs a file to the configured href. The first time the transformation of a particular file is carried out it succeeds, after that it fails with the following error. """"Cannot write more than one result document to the same URI, or write to a URI that has been read:"""" In my particular set-up, Mule is listening on a particular directory. When a file is dropped in that directory the transformation is applied. When I drop the same file a second (or third etc.) time I see this error. It seems probably that the issue is because the transformer is not getting reset after each transformation. In the XsltTransformer file (v2.2.1), I added the line transformer.reset(); (after transformer.clearParameters();) and that seemed to resolve the issue.""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6087","02/23/2012 18:20:31",8,"Include validation module in Mule core distribution ""Emiliano created a validation module, something that's missing inside mule. Validation module support built-in validators. Also it supports different types of exceptions for each validation allowing to generate a different response for each kind of exception. Module: http://mulesoft.github.com/mule-module-validation/ ""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6129","03/15/2012 19:20:29",2,"Change default behavior for Choice when no otherwise Processor is set ""In a mule flow, when using a message router without setting a Processor in the section, and the MuleMessage does not match any of the clauses, an exception is thrown. To achieve a conditional behavior currently mule requires to set a dummy processor on the otherwise clause. One usability improvement would be letting the message be processed by the remaining part of the flow if no clause was matched and no processor provided.""","",0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6145","03/27/2012 18:38:23",8,"until-successful should support synchronous use cases ""Imagine a simple synchronous HTTP proxy use case, e.g.: If outbound endpoint is wrapped in until-successful, the flow won't work anymore. until-successful must support synchronous scenarios as well.""","",0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6172","04/18/2012 20:23:20",3,"Upgrade apache-commons-pool ""Since error handling in current version of Apache commons-pool is buggy (borrowConnection method throws a NoSuchElementException losing the original cause) we may need to update the library. Version 1.6 DOES NOT fix the issue. However, current code in trunk tackles the issue (we'll have to wait for a new release). ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6251","05/28/2012 20:35:56",3,"Add a default object store for non internal usages ""Current version provides object stores default (persistent/in memory) to use while processing events internally but there is no object store which could be used by users as default.""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6355","07/24/2012 23:50:10",8,"soapVersion ignored on CXF proxy ""Invoking this proxy with a Soap 1.2 message fails with a WARNing in the logs and a SOAP fault for the caller: NB. Removing the soapVersion attribute and invoking the same proxy with a SOAP 1.1 message works with intense happiness."""," ns1:VersionMismatch A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint. ",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6367","07/27/2012 21:54:48",5,"FTP Inbound endpoint fails when reading empty file ""Put an empty file into FTP inbound path""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6386","08/08/2012 20:08:12",5,"Outbound endpoint with scheduled dispatch job delivers messages again and again ""If you send test messages to vm://test.in (say every second with a different payload for ex 1 2 3 ...) you'll notice that what's delivered to vm://accumulatedMessageHandler is: {{1 2 3 4 5}} then {{1 2 3 4 5 6 7 8 9 10}} then {{1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16}} (in a random order but the idea is here)""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6417","08/24/2012 23:56:25",0,"/ by zero in ComponentStatistics ""Recently I have been querying JMX statistics periodically via the MXBean interface (domain=Mule.*, type=org.mule.Statistics). After collecting statistics for each MBean, I reset the bean by invoking """"clearStatistics"""" with no arguments, so that I can come back and collect fresh statistics later. Howeven, when I do this while mule is under load, I see that the ComponentStatistics class starts to throw an exception on a divide-by-zero error. It tends to happen on multiple processor threads, and it seems to be a persistent issue - i.e. it throws the error every few seconds until I restart mule. I am uncertain if a message is trapped in limbo due to the repeated exception, but I think it may be as the message seems to repeat over and over again. ERROR org.mule.exception.DefaultMessagingExceptionStrategy - Caught exception in Exception Strategy: / by zero java.lang.ArithmeticException: / by zero at org.mule.management.stats.ComponentStatistics.addExecutionBranchTime(ComponentStatistics.java:163) at org.mule.management.stats.FlowConstructStatistics.addFlowExecutionBranchTime(FlowConstructStatistics.java:110) at org.mule.management.stats.ProcessingTime.addFlowExecutionBranchTime(ProcessingTime.java:95) at org.mule.interceptor.ProcessingTimeInterceptor.last(ProcessingTimeInterceptor.java:53) at org.mule.interceptor.AbstractEnvelopeInterceptor.process(AbstractEnvelopeInterceptor.java:61) at org.mule.processor.AsyncInterceptingMessageProcessor.processNextTimed(AsyncInterceptingMessageProcessor.java:111) at org.mule.processor.AsyncInterceptingMessageProcessor$AsyncMessageProcessorWorker.doRun(AsyncInterceptingMessageProcessor.java:158) at org.mule.work.AbstractMuleEventWork.run(AbstractMuleEventWork.java:43) at org.mule.work.WorkerContext.run(WorkerContext.java:310) at java.util.concurrent.ThreadPoolExecutor$CallerRunsPolicy.rejectedExecution(ThreadPoolExecutor.java:1746) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658) at org.mule.work.ScheduleWorkExecutor.doExecute(ScheduleWorkExecutor.java:41) at org.mule.work.MuleWorkManager.executeWork(MuleWorkManager.java:250) at org.mule.work.MuleWorkManager.scheduleWork(MuleWorkManager.java:218) at org.mule.processor.SedaStageInterceptingMessageProcessor.run(SedaStageInterceptingMessageProcessor.java:233) at org.mule.work.WorkerContext.run(WorkerContext.java:310) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6441","09/17/2012 07:09:34",5,"Inconsistent behaviour of foreach with inside flowvar ""The index of the foreach inside the flow of the flowref is not consistent. It seems that there is a lack of atomicity with the invocation variables causing as a result jump of indexes of the iteration and overwrite of invocation variables. In the example below my payload is the result of a sql query so an ArrayList. I save the value of each row in a flow variable to make it always available in next operations (the original project has more flowRef). The problem comes out because in the contained flow accessed by the flowRef, the invocation variable carrying the index of the iteration and also the name of the element that I saved is not consistent during each iteration. Sometimes some idexes are jumped and also the element of my array tooks more time the same value.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6468","10/03/2012 22:12:19",8,"Messages generated from http-messages.properties should be escaped when returned to the client as http response ""Currently if you send the the following http request: you will receive the following response: containing potential malicious javascript code that the browser will run. Anytime a message is returned to the client the inputs should be parsed to prevent this kind of problems"""," GET /unionstation/ens/form HTTP/1.1 Accept: */* Accept-Language: en-us UA-CPU: x86 User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Host: staging-unionstation.optuminsight.com Authorization: Pragma: no-cache Referer: https://staging-unionstation.optuminsight.com:443/unionstation/ens/form X-Scan-Memo: Category=""""Audit""""; Function=""""createStateRequestFromAttackDefinition""""; SID=""""CF1B85D9856FC7300BE04E08AE969344""""; PSID=""""1D12AD7B110413DEBB8E6634539F76CF""""; SessionType=""""AuditAttack""""; CrawlType=""""None""""; AttackType=""""HeaderParamManipulation""""; OriginatingEngineID=""""1354e211- 9d7d-4cc1-80e6-4de3fd128002""""; AttackSequence=""""3""""; AttackParamDesc=""""Authorization""""; AttackParamIndex=""""6""""; AttackParamSubIndex=""""0""""; CheckId=""""(null)""""; Engine=""""Cross+Site+Scripting""""; Retry=""""False""""; SmartMode=""""NonServerSpecificOnly""""; AttackString=""""%3csCrIpT%3ealert(88585)%3c%2fsCrIpT%3e""""; AttackStringProps=""""Attack""""; Connection: Keep-Alive Cookie: CustomCookie=WebInspect76158ZX7B636566555940D48015FD4B8FB9C0F6Y76AF UnitedHealth Group 5Report Date: 9/28/2012 Vulnerability (Legacy) HTTP/1.1 403 Forbidden Date: Thu, 27 Sep 2012 07:55:26 GMT Server: Mule Core/3.3.0 http.status: 403 X-MULE_ENCODING: UTF-8 WWW-Authenticate: Basic realm=""""X12Files"""" Content-Type: text/plain; charset=UTF-8 Content-Length: 116 Connection: close Http Basic filter doesnt know how to handle header . Message payload is of type: String ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6471","10/04/2012 14:39:45",1,"Default exception strategy is not being called ""I have the following flow: When I post with an invalid JSON, the return is """"Could not store the User"""" However when I do: The exception is not handled"""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6501","10/26/2012 22:45:41",8,"XsltTransformer forcefully evaluate expressions in context-property into Strings ""This arbitrary limitation prevents passing DOM nodes as XSL parameters :( It comes from the fact the XSL transformer uses the deprecated {{parse}} method in: """," protected Object evaluateTransformParameter(String key, Object value, MuleMessage message) throws TransformerException { if (value instanceof String) { return muleContext.getExpressionManager().parse(value.toString(), message); } return value; } ",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6512","11/02/2012 18:49:18",2,"MuleMessageToHttpResponse.createResponse shouldn't use SimpleDateFormat ""We should use JodaTime's DateTimeFormatter since it is thread-safe (we can use one static instance) and faster than creating a new one each time.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6557","12/05/2012 21:05:22",0,"Performance regression when caching JMS Sessions ""When enabling cacheJmsSessions attribute on the JMS Connector performance drops to a factor of 10. Attached test case contains an example of this, if runned on mule 3.2.2, it lasts 3 to 5 seconds to process 10k messages, if runned on mule 3.3.0 or 3.3.1, it lasts 30 to 32 seconds to process 10k messages. This has been tested on ActiveMQ and Websphere Message Broker.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6604","01/21/2013 19:48:09",1,"Upgrade Jackson to 1.9.11 ""This version works with 1.8.0 and there are some deprecated methods in 1.9.11, so there is a need for an upgrade.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6628","02/02/2013 00:31:23",5,"Should be able to replace Log4j for another logging implementation ""http://www.mulesoft.org/documentation/display/MULE3USER/Configuring+Logging says in the section titled """"I don't want to use Log4j"""" that the log4j jar can be removed so long as SLF4J is wired to another logging implementation. Removing the Log4j jar results in WrapperManager Error: Error in WrapperListener.start callback. java.lang.NoClassDefFoundError: org/apache/log4j/spi/RepositorySelector WrapperManager Error: java.lang.NoClassDefFoundError: org/apache/log4j/spi/RepositorySelector WrapperManager Error: at java.lang.Class.getDeclaredConstructors0(Native Method) WrapperManager Error: at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) WrapperManager Error: at java.lang.Class.getConstructor0(Class.java:2699) WrapperManager Error: at java.lang.Class.getConstructor(Class.java:1657) WrapperManager Error: at org.mule.module.reboot.MuleContainerWrapper.start(MuleContainerWrapper.java:53) WrapperManager Error: at org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:3925) WrapperManager Error: Caused by: java.lang.ClassNotFoundException: org.apache.log4j.spi.RepositorySelector WrapperManager Error: at java.net.URLClassLoader$1.run(URLClassLoader.java:202) WrapperManager Error: at java.security.AccessController.doPrivileged(Native Method) WrapperManager Error: at java.net.URLClassLoader.findClass(URLClassLoader.java:190) WrapperManager Error: at java.lang.ClassLoader.loadClass(ClassLoader.java:306) WrapperManager Error: at java.lang.ClassLoader.loadClass(ClassLoader.java:247) WrapperManager Error: ... 6 more This is due to the patch done to fix MULE-5264 which causes MuleContainer to have a direct reference to Log4j's RepositorySelector. Simply moving the reference and the call to setRepositorySelector to some other class which is not accessed via a static reference should solve the problem.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6641","02/13/2013 23:57:42",0,"REST Service/Interface Definition ""http://corp.wiki.mulesource.com/display/WP/Simplified+REST+Service+Creation""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6642","02/13/2013 23:57:47",8,"REST Document Resource Definition ""http://corp.wiki.mulesource.com/display/WP/Simplified+REST+Service+Creation""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6645","02/13/2013 23:58:01",8,"REST Swagger Definition Generation ""http://corp.wiki.mulesource.com/display/WP/Simplified+REST+Service+Creation""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6646","02/13/2013 23:58:06",5,"REST Browsable Web UI Generation ""http://corp.wiki.mulesource.com/display/WP/Simplified+REST+Service+Creation""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6647","02/14/2013 00:10:14",5,"Remove all examples, except the new hello world and existing loan broker, from ESB stand-alone distribution ""* Packaged examples should be modified as per the following plan: https://docs.google.com/a/mulesoft.com/spreadsheet/ccc?key=0ArwrJmCfHowWdDNCdnJYeldHcDI5M0dYaTRsWUwxd2c#gid=2 * This requires the following additional work: - Creation of the two new identified examples. - Modification of target examples to use latest 3.4 features. Beyond specifics identified on spreadsheet this includes adding in-studio documentation for all examples. - Modification of documentation for target examples. - Removal of examples tagged as Archive from Studio. - Modification of docs to reflect an Archived examples section. - Placement of all examples in GIT and tagging as active versus archived. - From the ESB stand-alone distribution point of view: Remove all examples except the new hello world and existing loan broker.""","",0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6649","02/14/2013 20:11:49",3,"Addition of DB2 and MS SQL Server to the list of databases on Studio JDBC connector configuration window - ESB Work ""Today we show MySQL, Derby, and Oracle. However, MS SQL and DB2 are RDBMS's with very large footprints. As such, we should add these two databases to the set that shows up on the JDBC connector's configuration screen. ""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6657","02/19/2013 05:54:18",8,"NIO and WebSocket Completion ""As a Mule ESB user, I would like to be able to turn on the use of the NIO stack through a deploy.properties toggle. As a Mule ESB user, I would like to be able to use the new WebSocket components within my flows. ""","",0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6659","02/19/2013 06:06:49",3,"Testing Mule 3.4 Pairing with GA Registry ""As a Mule user, I would like to configure my Mule instance to be paired with my Registry account through my registry key so that I may be able to manage my ESB instance's endpoints with the registry. User should be configure the registry key for their registry account for an ESB instance. From there on: The HTTP endpoints of all apps deployed to the ESB instance should be manageable with the paired registry instance. Detailed specs described here: http://corp.wiki.mulesource.com/display/PRODMGMT/Registry+Interaction+and+License+Management+Support ""","",0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6661","02/19/2013 06:08:05",1,"Testing - Mule 3.4 Dynamic Lookup with GA Registry ""As a Mule user, I would like to use the dynamic lookup component within my flows. Detailed specs defined here: http://corp.wiki.mulesource.com/display/WP/Dynamic+Router+%28supports+Registry+Dynamic+Endpoint+Resolution%29""","",0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6663","02/19/2013 06:55:38",0,"Testing - Mule 3.4 Thorttling with GA Registry ""As a Registry user, I would like to be able to apply throttling policies to my Mule ESB flow end-points. ""","",0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6673","02/20/2013 15:20:02",5,"Update Spring version used in Mule to 3.2 ""Update the version of Spring we are using to 3.2""","",0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6699","02/27/2013 14:34:55",5,"Intercepting Are not generating message processor path ""This is currently breaking debugger, since all MP that executes after an intercepting MP are not being executed. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6700","02/27/2013 18:23:49",1,"mule-common dependency should be on a fixed version ""We should be on a fixed version rather than a SNAPSHOT. mule-common is at 0.11.0-SNAPSHOT so we'll go with 0.11.0.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6710","03/05/2013 13:22:43",8,"REST Representations definition ""Multiple representation support for apikit""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6711","03/05/2013 13:25:14",8,"APIkit example application ""Create an example application to showcase apikit functionality""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6713","03/05/2013 15:38:03",8,"GitHub migration ""- svn repo migration to github - bamboo plans update""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6814","03/05/2013 18:54:02",8,"APIkit REST Controller Resource ""REST Controller Resource""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6815","03/05/2013 19:04:03",3,"APIkit Tech Debt ""APIkit Tech Debt""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6714","03/05/2013 19:07:40",5,"Deprecate Services (and anything else we can) ""Deprecate Services (and anything else we can)""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6732","03/13/2013 14:32:52",5,"HTTP(S) transport generates everlasting temporary files ""When doing a multipart upload it may create a temporary file. It will remain on the disk drive because the file is not being deleted once the outputstream is closed. A deleteOnExit flag would not be effective for never-closing applications. This eventually leads to """"java.io.IOException: No space left on device"""". The location where this file is being created may be seen at https://github.com/mulesoft/mule/blob/mule-3.x/transports/http/src/main/java/org/mule/transport/http/multipart/MultiPartInputStream.java#L135""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6746","03/19/2013 20:06:06",5,"Fix the 3.x site build ""javadoc generation is failing. check log here: http://bamboo.mulesoft.org/browse/MULE3X-MULE3XSITE-SITE""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6749","03/20/2013 00:07:20",8,"ReplyToHandlers do not work with Dynamic Outbound Endpoints ""ReplyToHandler in the case of Ajax (AjaxReplyToHandler) depends on the MessageSourceURI to actually send the message back to the caller. If a dynamic outbound endpoint is introduced in the middle which replaces the event's MessageSourceURI it breaks the replyTo. See the following flow (modified version of the Order Processing example shipped with Studio): produces the following error: """," {""""timestamp"""":""""Wed, 20 Mar 2013 00:03:58 GMT"""",""""id"""":""""370"""",""""data"""":{},""""channel"""":""""/orders/soap"""",""""clientId"""":""""k9lc8wpz6dr1fsvppi""""} java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.mortbay.cometd.BayeuxService.doInvoke(BayeuxService.java:357) at org.mortbay.cometd.BayeuxService.invoke(BayeuxService.java:309) at org.mortbay.cometd.BayeuxService.access$400(BayeuxService.java:59) at org.mortbay.cometd.BayeuxService$AsyncListen.deliver(BayeuxService.java:393) at org.mortbay.cometd.ClientImpl.notifyMessageListener(ClientImpl.java:214) at org.mortbay.cometd.ClientImpl.doDelivery(ClientImpl.java:194) at org.mortbay.cometd.ChannelImpl.deliverToSubscriber(ChannelImpl.java:502) at org.mortbay.cometd.ChannelImpl.doDelivery(ChannelImpl.java:464) at org.mortbay.cometd.ChannelImpl.doDelivery(ChannelImpl.java:494) at org.mortbay.cometd.ChannelImpl.doDelivery(ChannelImpl.java:494) at org.mortbay.cometd.AbstractBayeux$PublishHandler.handle(AbstractBayeux.java:1293) at org.mortbay.cometd.AbstractBayeux.handle(AbstractBayeux.java:287) at org.mortbay.cometd.continuation.ContinuationCometdServlet.service(ContinuationCometdServlet.java:171) at org.mule.transport.ajax.container.MuleAjaxServlet.service(MuleAjaxServlet.java:107) at org.mortbay.cometd.AbstractCometdServlet.service(AbstractCometdServlet.java:265) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) Caused by: org.mule.api.MessagingException: Endpoint scheme must be compatible with the connector scheme. Connector is: """"ajax"""", endpoint is """"http://0.0.0.0:1080/orders"""" (java.lang.IllegalArgumentException). Message payload is of type: String at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:35) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:46) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:93) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:66) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.processor.AbstractInterceptingMessageProcessorBase.processNext(AbstractInterceptingMessageProcessorBase.java:105) at org.mule.processor.AsyncInterceptingMessageProcessor.process(AsyncInterceptingMessageProcessor.java:98) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:46) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:93) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:66) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.processor.AbstractInterceptingMessageProcessorBase.processNext(AbstractInterceptingMessageProcessorBase.java:105) at org.mule.interceptor.AbstractEnvelopeInterceptor.process(AbstractEnvelopeInterceptor.java:55) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:46) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.processor.AbstractInterceptingMessageProcessorBase.processNext(AbstractInterceptingMessageProcessorBase.java:105) at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:44) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:46) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.processor.AbstractInterceptingMessageProcessorBase.processNext(AbstractInterceptingMessageProcessorBase.java:105) at org.mule.construct.AbstractPipeline$1.process(AbstractPipeline.java:102) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:46) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:93) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:66) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.doProcess(InterceptingChainLifecycleWrapper.java:57) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:66) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.access$001(InterceptingChainLifecycleWrapper.java:29) at org.mule.processor.chain.InterceptingChainLifecycleWrapper$1.process(InterceptingChainLifecycleWrapper.java:90) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:46) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.process(InterceptingChainLifecycleWrapper.java:85) at org.mule.construct.AbstractPipeline$3.process(AbstractPipeline.java:194) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:46) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:93) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:66) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.doProcess(InterceptingChainLifecycleWrapper.java:57) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:66) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.access$001(InterceptingChainLifecycleWrapper.java:29) at org.mule.processor.chain.InterceptingChainLifecycleWrapper$1.process(InterceptingChainLifecycleWrapper.java:90) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:46) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.process(InterceptingChainLifecycleWrapper.java:85) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:46) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.processor.chain.SimpleMessageProcessorChain.doProcess(SimpleMessageProcessorChain.java:47) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:66) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.doProcess(InterceptingChainLifecycleWrapper.java:57) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:66) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.access$001(InterceptingChainLifecycleWrapper.java:29) at org.mule.processor.chain.InterceptingChainLifecycleWrapper$1.process(InterceptingChainLifecycleWrapper.java:90) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:46) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.process(InterceptingChainLifecycleWrapper.java:85) at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:220) at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:202) at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:194) at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:181) at org.mule.transport.ajax.AjaxMessageReceiver$ReceiverService.route(AjaxMessageReceiver.java:76) ... 32 more Caused by: java.lang.IllegalArgumentException: Endpoint scheme must be compatible with the connector scheme. Connector is: """"ajax"""", endpoint is """"http://0.0.0.0:1080/orders"""" at org.mule.endpoint.AbstractEndpointBuilder.doBuildOutboundEndpoint(AbstractEndpointBuilder.java:254) at org.mule.endpoint.AbstractEndpointBuilder.buildOutboundEndpoint(AbstractEndpointBuilder.java:122) at com.mulesoft.habitat.agent.endpoint.AnypointEnabledEndpointFactory.getOutboundEndpoint(AnypointEnabledEndpointFactory.java:44) at org.mule.transport.ajax.AjaxReplyToHandler.processReplyTo(AjaxReplyToHandler.java:66) at org.mule.routing.requestreply.AbstractReplyToPropertyRequestReplyReplier.processReplyTo(AbstractReplyToPropertyRequestReplyReplier.java:69) at org.mule.routing.requestreply.AbstractReplyToPropertyRequestReplyReplier.process(AbstractReplyToPropertyRequestReplyReplier.java:45) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) ... 104 more ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6760","03/27/2013 12:26:13",5,"ProcessorChain and SubFlows are intercepting when they shouldn't ""Currently ProcessorChain and SublFlows are Intercepting this affects debugger because notifications are generated wrong. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6765","03/27/2013 19:58:17",13,"Chaining more than one HTTP outbound endpoint will use the HTTP method of the first one ""If I have a config file as follows: The second outbound-endpoint will always do a GET because if the input payload is of type HTTPMethod, then it takes the value from there."""," ... ... ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6788","04/10/2013 21:27:57",5,"Upgrade CXF to 2.5.9 ""We should upgrade cxf to get the latest security patches.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6789","04/10/2013 22:13:25",8,"NullPointerException during JMS Reconnect Attempt ""If you configure an xa enabled connector to a JMS broker and the jms broker goes down, the following exception get thrown: Step to reproduce: * run the attached config * tear down the activemq broker and start it again"""," DEBUG 2013-02-19 10:34:55,584 [MuleServer.2] org.mule.retry.notifiers.ConnectNotifier: java.lang.NullPointerException at org.mule.transport.AbstractPollingMessageReceiver.schedule(AbstractPollingMessageReceiver.java:97) at org.mule.transport.AbstractPollingMessageReceiver.doStart(AbstractPollingMessageReceiver.java:62) at org.mule.transport.TransactedPollingMessageReceiver.doStart(TransactedPollingMessageReceiver.java:102) at org.mule.transport.AbstractTransportMessageHandler$3.onTransition(AbstractTransportMessageHandler.java:316) at org.mule.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:141) at org.mule.transport.ConnectableLifecycleManager.fireStartPhase(ConnectableLifecycleManager.java:51) at org.mule.transport.AbstractTransportMessageHandler.start(AbstractTransportMessageHandler.java:312) at org.mule.transport.AbstractConnector$5.doWork(AbstractConnector.java:1579) at org.mule.retry.policies.AbstractPolicyTemplate.execute(AbstractPolicyTemplate.java:67) at com.mulesoft.mule.retry.async.RetryWorker.run(RetryWorker.java:74) at org.mule.work.WorkerContext.run(WorkerContext.java:310) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Thread.java:662) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6795","04/15/2013 07:48:45",0,"Throw ""Invalidated calling setPayload"" exception when data flow past from router to java component ""Flow config is following: There are two components in the one router: public class B implements Callable { @Override public Object onCall(MuleEventContext eventContext) throws Exception { System.out.println(""""B""""); return """"B""""; } public class C implements Callable { @Override public Object onCall(MuleEventContext eventContext) throws Exception { System.out.println(""""C""""); return """"C""""; } } There is a component after the router: public class CollctToString implements Callable { @Override public Object onCall(MuleEventContext eventContext) throws Exception { return """"CollctToString""""; } } Run the app, it will throw following exception after executing components B and C: java.lang.IllegalStateException: Payload was invalidated calling setPayload and the message is not collection anymore. at org.mule.DefaultMessageCollection.checkValidPayload(DefaultMessageCollection.java:107) at org.mule.DefaultMessageCollection.newThreadCopy(DefaultMessageCollection.java:312) at org.mule.DefaultMuleEvent.newThreadCopy(DefaultMuleEvent.java:779) at org.mule.RequestContext.newEvent(RequestContext.java:140) I debugged it and found the cause: DefaultMessageCollection.setPayload() has been called by DefaultMessageCollection.transformMessage(MuleEvent, Transformer). And DefaultMessageCollection.invalidatedPayload field value is true. The 2sec passing parameter of DefaultMessageCollection.transformMessage(MuleEvent, Transformer) method is a transformer which I do not custom, and it will transform message to a String result. I cannot understand what does the code """" if (this.getPayload() == payload) """" of DefaultMessageCollection.setPayload() mean, this.getPayload() is a collection and payload is a string by previous transformMessage() method. I think it should call addMessage(MuleMessage message) to add all objects returned from components in the router. It's success when I insert a custom transformer for converting Collection between router output data flow and component class CollctToString.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6796","04/17/2013 20:24:02",3,"Allow MEL expressions in cxf:property of cxf:ws-config ""It would be nice to be able to use MEL expressions for the values of properties in the ws-config so we can set properties based upon the message being processed.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7001","04/18/2013 06:10:38",8,"Write initial draft of shared ports spec ""We are having a number of critical users requests for being able to deploy multiple apps on the same Mule instance using the same IP/Port endpoint. This story is to do some analysis to identify the possible solutions for addressing this problem space. ""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6800","04/22/2013 20:23:24",5,"Thread leak on Mule redeployments for embedded ""When Mule is running embedded in a container, after redeploying an application, there is a thread which still lives from the previous deployment and gets created again with the new one: Mule.log.slf4j.ref.handler. Steps to reproduce: 1. Deploy a Mule embedded app in Tomcat (bookstore-admin.war from the examples, for instance). 2. Check the thread count and look for the mentioned thread 3. Re-deploy the app 4. Check the thread count, it should have gone up by 1 and there should be 2 threads called Mule.log.slf4j.ref.handler""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6826","05/08/2013 15:05:55",1,"Fix flaky unit test: DateTimeTestCase ""DateTimeTestCase has many test that are flaky because they depend on the current system time. For example: Problem is that there are two different calls to obtain the current second, so they could obtain different values from time to time. Same problem exist in many tests, but as they are checking for minutes, hours, days, weeks, etc they less probable to fail, but they are still flaky in theory. """," @Test public void seconds() { assertEquals(Calendar.getInstance(TimeZone.getTimeZone(""""UTC"""")).get(Calendar.SECOND), now.getSeconds()); } ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6829","05/08/2013 20:39:44",5,"cxf_operation is wrong when using proxy-client of a soap 1.1 request ""When processing a soap 1.1 request, the org.apache.cxf.binding.soap.interceptor.SoapActionInInterceptor looks for the soap action in soapMessage.get(Message.PROTOCOL_HEADERS).get(SoapBindingConstants.SOAP_ACTION). If Mule doesn't set this beforehand, cxf doesn't find it. This is a problem because the SoapActionInInterceptor will then fail to set the BindingOperationInfo for the request and thus the StaxDataBindingInterceptor will not know which BindingOperationInfo to use so it just picks the first one of its list (which is probably wrong!) and bam! we're executing the wrong operation. Processing soap 1.2 requests (which is much more prevalent) doesn't have this problem.""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6843","05/22/2013 07:06:56",13,"Move OAuth from DevKit to ESB ""* Move generated DevKit code to ESB and expose an interface that DevKit can use * Improve user experience when trying to configure an OAuth connector http://corp.wiki.mulesource.com/display/WP/Making+OAuth+user+experience+smoother""","",0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6844","05/22/2013 07:14:43",5,"Connector Auto-Paging ""See here: http://corp.wiki.mulesource.com/pages/viewpage.action?pageId=27132117 This will require some in-iteration investigation.""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6845","05/22/2013 07:45:12",3,"Define Polling Watermarks ""Right now, when a poll needs to deal with updated objects, we use watermarks as an approach to filter out elements that were already processed. The only way to do that right now is to implement the logic manually which forces the user to deal with object stores, default values, repeated logic, dev time dependencies, etc. This story is a container of all the features required for watermark ""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6846","05/22/2013 07:46:51",5,"Define filter, split, aggregate and route record level data strategy ""Basic requirements: http://corp.wiki.mulesource.com/pages/viewpage.action?pageId=27132117 ""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6848","05/23/2013 14:21:49",0,"Improve JdbcTransactionFactory to support multi transactions ""JdbcTransactionFactory needs to implement UniversalTransactionFactory in order to work with mule-module-multi-tx-ee""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6849","05/23/2013 14:55:50",8,"ReplyToDestination is not properly configured in some scenarios ""ReplyToParameterProcessor which is used to move the replyToDestination info from the message to the event is not always invoked before other processing occurs. This causes that the message processed inside the flow is not sent back to the client.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6852","05/24/2013 17:24:03",3,"Default object store for until-successful ""until-successful needs to be configured with an objectstore by default so it works out of the box very easily.""","",0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6858","05/29/2013 16:48:35",2,"Filename-wildcard filter to fails with SFTP ""MULE-6743 modified the scope of originalFilename property: originally it was stored in the outbound scope, but it was changed to inbound. Filename wildcard filter was also changed to read that property from the inbound scope. However the SFTP transport is still storing the property in the outbound scope, making the filter to work incorrectly (not processing file that should be processed). After the mentioned changes, file transport is storing the property in INBOUND and OUTBOUND, FTP is storing it in INBOUND, and SFTP is doing it only in OUTBOUND. ""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6861","05/30/2013 16:28:55",5,"Watermark / Binding object store items to flow variables ""h1. Watermarking Right now, when a poll needs to deal with updated objects, we use watermarks as an approach to filter out elements that were already processed. Watermarks require a value to be persisted across flow invocations. Typically, this value will have a default the first time used, and will be used as part of a query or outbound request. Based on how the flow processes the results, the value may be updated. This can be done using several steps: - Fetch a value form a persistent object store and save it as a flow variable - Refer to the flow variable when doing a query / outbound request - Update the variable based (either once - i.e. the watermark is the date of the query, or per record - i.e. the watermark is the highest id from an object) - At the end of the processing, persist the value to the persistent object store This pattern is very common in synchronisation flows. Enough common to deserve better support. To make this easier out of the box we will add a new optional parameter to that will provide the watermarking variable persistence out of the box. Watermark Example: h2. Watermark properties * variable (required): This attribute signals both the object store key that will be used to store this watermark as also the name of the flowVar in which its value will be exposed to the user. * default-expression (required): In case that the key above can't be found on the object store, the default expression is used to generate a value. This is useful for the first run of the flow * update-expression (optional): The result of this expression will be used to update the watermark once the execution is finished. It defaults to the value of the variable parameter. * objectStore-ref (optional): A reference to the object store you wish to use to store the watermarks. If not provided, the default user object store will be used h2. Watermark behaviour * It is bound to the poll * It is bound to synchronous flows only. If not then it execution must fail * When executed, it goes to the configured object store looking for a value of the given key. If found, that value is exposed through a flowVar using the same key. * If no value is found for that key in the object store, then the default-expression is executed and that value is exposed through the flowVar. * Watermark will also fire a notification interceptable by the event tracking module. The underlaying tracking event will be enriched with the watermark value. * The message processors will be executed. * If the flow was correctly executed, then the watermark will be updated. * After updating the object store, another notification is fired to the event tracking system so that the new value can also be recorded there * If the intercepted processors throw any exceptions, then the watermark will not be updated. Since the watermark is stored in the object store, the user can always use a exception strategy to put a custom value in case of failure. * In case the watermark value is not serializable then fail the store of the watermark in the object store """," = #[flowVars['lastModifiedDate']]""""/> ..... ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6864","05/31/2013 17:19:39",3,"SFTP: Jsch issue in java 1.7 and Kerberos ""There is a known issue with JSch running in java 1.7 and connecting to a server with Kerberos enabled. When trying to connect to that server, it will request the password to be manually entered. The issue is described in the following page: https://issues.apache.org/bugzilla/show_bug.cgi?id=53437 Setting """"PreferredAuthentications"""" property to """"publickey,password,keyboard-interactive"""" in the SftpClient solves the problem.""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6866","06/03/2013 22:38:55",8,"Upgrade to Groovy 2.3.6 ""Upgrade Mule's Groovy dependency to Groovy 2.3.6.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6896","06/06/2013 14:58:01",8,"Ability to handle record level errors in for-each ""As an user, I want to catch exceptions at a record level in a for-each/batch element so I can continue processing and put my individual records on a DLQ.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6872","06/06/2013 15:03:32",8,"Poll 2.0 ""For studio, we want to be able to start, stop and execute polls via an API.""","",0,0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6894","06/24/2013 04:24:46",8,"Split collection processor ""Spec TBD ""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6898","06/25/2013 16:57:09",5,"Create Mule API to inject Poll a different scheduler ""Poll elements have a single scheduler strategy (it uses sheduledWithFixDelay) we want users to be able to determine a different scheduler strategy as part of the story MULE-6872""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6899","06/25/2013 16:58:12",2,"Provide an API to stop/start and execute schedulers ""We need external systems to be able to stop/start and execute schedulers at any given time.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6900","06/25/2013 16:59:35",5,"Change Poll schema to accept a scheduler strategy ""New poll schema will accept scheduler strategies: ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6903","06/27/2013 18:05:37",1,"UntilSuccessful doesn't correctly validate payload is Serializable ""When ensuring that the message payload is Serializable, the validation is not property done when the message is a DefaultMuleMessage and the payload isn't consumable""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6906","06/27/2013 19:04:04",1,"Add utility methods to execute flows in FunctionalTestCase ""Right now FunctionalTestCase only provides one testFlow() method which does't really fit all use cases. FunctionalTestCase could be improve adding the runFlow() family of methods that Devkit generates when archetyping a CloudConnector. This would be better for a user testing their applications and would also help the effort of moving code from Devkit to mule""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6918","07/02/2013 15:21:52",5,"Add dynamic round robin routing support ""Related to MULE-6653 where support for dynamic router was implemented for 'first successful' and 'all' strategies. A new strategy should be added for round robin. The new dynamic-round-robin will round robin through the routes to dispatch the message, maintaining a state to keep track of the next message processor that needs to be processed. The state should be maintained based on a route resolver identifier, the goal behind it is to keep track of the iteration for each configuration of the router. By default it should assume the route resolver has no state if it does not implement an IdentifiableDynamicRouteResolver (which is an interface that extends DynamicRouteResolver)""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6956","07/16/2013 20:29:03",1,"Watermark - unable to access default user Object Store instance ""*Steps* with this flow watermark does not access the default user Object Store """," ",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6959","07/18/2013 22:27:51",5,"Race condition creating MVELExpressionLanguage instances ""Constructor of MVELExpressionLanguage is updating the expression language configured in the DefaultExpressionManager. This creates a reace condition when there are more than one instance created and multiple threads using the expression manager. In those cases, some threads can get a NPE. This is a problem using Data Mapper as they extend the MVELExpressionLanguage. There is a second problem having MVELExpressionLanguage constructor setting the expression language: after a DM component, the expression language use in the app will continue to be the expression language from DM, not the original mvel""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6965","07/23/2013 15:47:18",8,"Erro during mule message serialization when using byte array as payload ""Attached configuration works well on standalone mode, but when switch to cluster mode I got this exception: INFO 2013-06-18 16:04:26,722 [[pepe].connector.file.mule.default.receiver.01] org.mule.transport.file.FileMessageReceiver: Lock obtained on file: /private/tmp/test/file.txt ERROR 2013-06-18 16:04:26,904 [[pepe].inputFlow.stage1.01] org.mule.exception.DefaultSystemExceptionStrategy: Caught exception in Exception Strategy: java.lang.String cannot be cast to org.mule.api.MuleEvent java.lang.ClassCastException: java.lang.String cannot be cast to org.mule.api.MuleEvent at org.mule.processor.SedaStageInterceptingMessageProcessor.dequeue(SedaStageInterceptingMessageProcessor.java:134) at org.mule.processor.SedaStageInterceptingMessageProcessor.run(SedaStageInterceptingMessageProcessor.java:209) at org.mule.work.WorkerContext.run(WorkerContext.java:311) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6968","07/24/2013 21:28:22",8,"Http endpoint with path="""" or path=""/"" do not attend requests at root level ""enpoints #2 and #3 behave differently than #1 that shows the correct behavior. 1) 2) 3) only #1 answers requests to http://localhost:8000/ #2 and #3 throw the following error: Cannot bind to address """"http://localhost:8000/"""" No component registered on that endpoint ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6986","08/23/2013 06:12:25",5,"http:static-resource-handler fails when request path is '/' ""Given a http:inbound-endpoint with no context path, and a http:static-resource-handler with a resourceBase set, expect that visiting http://server:port should redirect or service http://server:port/index.html. Noted the following issues: 1) Server actually sends a 302 redirect to '//', which is not handled well by modern browsers (Chrome) 2) Visiting http://server:port// actually returns the contents of index.html 3) As a side-issue, visiting http://server:port/index.html if resourceBase does not have a trailing slash results in a file not found error (does not add the necessary slash) Looking at the source here: https://github.com/mulesoft/mule/blob/8de5e6b1de40e8d5f792e8e0f0b9d1de7506c2d8/transports/http/src/main/java/org/mule/transport/http/components/StaticResourceMessageProcessor.java The issue is that the request path is stripped back from '/' to '' here: And so the following code fails to match on 'path.endsWith': And the subsequent code block to redirect is used. The functional test cases don't catch this because the context path is not the same as the request path."""," String path = event.getMessage().getInboundProperty(HttpConnector.HTTP_REQUEST_PATH_PROPERTY); String contextPath = event.getMessage().getInboundProperty(HttpConnector.HTTP_CONTEXT_PATH_PROPERTY); // Remove the contextPath from the endpoint from the request as this isn't part of the path. path = path.substring(contextPath.length()); if (file.isDirectory() && path.endsWith(""""/"""")) { file = new File(resourceBase + path + defaultFile); } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-6998","09/01/2013 21:23:32",3,"Incorrect maven dependency for drools ""Drools (mule-module-drools) needs the jasper-jdt jar, but does not declare a dependency for it. For a drools project to work, you also need to declare a dependency for mule-transport-ajax. mule-transport-ajax declares a dependency for org.apache.tomcat:jasper:jar which will also bring in jorg.apache.tomcat:jasper-jdt:jar But mule-transport-ajax shouldn't be required for using drools with Mule.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7012","09/10/2013 14:58:37",13,"HTTP/HTTPS outbound endpoints ignore the keep-alive attribute ""The HTTP outbound endpoint has an attribute keep-alive that controls the use of persistent HTTP outbound connections. This attribute is currently ignored. An endpoint configured with exchange-pattern=""""one-way"""" always keeps outbound connections alive. If the request-response exchange pattern is used, a new connection is created in each request. This behavior should depend on the keep-alive attribute of the endpoint. In the following example the keep-alive attribute is set to false but the endpoint keeps alive the connection: """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7013","09/10/2013 15:01:56",8,"Deprecate keepSendSocketOpen attribute in HTTP connector ""The HTTP Connector has an attribute 'keepSendSocketOpen' that is inherited from the TCP connector. This attribute is a TCP setting that should not exist in the HTTP connector (to keep outbound connections open the keep-alive attribute in the outbound endpoint should be used). Add documentation for this change.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7022","09/13/2013 22:03:43",1,"Add nexus profile to distributions pom. ""Add nexus profile to distributions pom.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7027","09/19/2013 15:00:55",5,"ExpiringGroupMonitoringThread must process event groups only when the node is primary ""ExpiringGroupMonitoringThread is used on the EventCorrelator to detect EventGroup that expired and must be deleted. This thread is always started as part of the EventCorrelator and that means that in a cluster environment, every node will have a thread running. This causes problems when different nodes try to process the same event group simultaneously. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7030","09/23/2013 20:47:51",13,"Need to support XPATH 3.0 in the xpath filter ""Xpath 2.0 is supported in the XSLT transformers but not in filters right now. This will only apply for xpath expressions not jxpath According to [~philip.parker] AFAIK we only support xpath version 1.0 in flows using MEL, it seems we may support version 2.0 in xslt transformation, in DM I think we support version 3.0. All of these really should be aligned to the same version. Since xpath 2.0 came out in 2007 I think we should be using that as a minimum, if not we should be using 3.0 to take advantage of the newer functions. As we move onto the bigger customers and SOAP WS, they may well want to use XML.""","",0,1,0,0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7031","09/23/2013 22:05:42",1,"Add getObjectStoreManager() in MuleContext ""Add a method in the MuleContext for easy access to the ObjectStoreManager""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7043","10/02/2013 15:00:49",3,"Cannot put a Foreach after an OAuth authorize ""Creating a simple flow that do the authorization and calls get-contacts and iterate through the payload. INFO 2013-09-23 18:12:12,291 [[google-contacts-paged-test].connector.http.mule.default.receiver.02] org.mule.api.processor.LoggerMessageProcessor: Authorized... ERROR 2013-09-23 18:16:09,797 [[google-contacts-paged-test].connector.http.mule.default.receiver.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : Object """"org.mule.modules.google.contact.wrappers.GoogleContactEntry"""" not of correct type. It must be of type """"{interface java.lang.Iterable,interface java.util.Iterator,interface org.mule.routing.MessageSequence,interface java.util.Collection}"""" (java.lang.IllegalArgumentException). Message payload is of type: GoogleContactEntry Code : MULE_ERROR--2 -------------------------------------------------------------------------------- Exception stack is: 1. Object """"org.mule.modules.google.contact.wrappers.GoogleContactEntry"""" not of correct type. It must be of type """"{interface java.lang.Iterable,interface java.util.Iterator,interface org.mule.routing.MessageSequence,interface java.util.Collection}"""" (java.lang.IllegalArgumentException) org.mule.util.collection.EventToMessageSequenceSplittingStrategy:61 (null) 2. Object """"org.mule.modules.google.contact.wrappers.GoogleContactEntry"""" not of correct type. It must be of type """"{interface java.lang.Iterable,interface java.util.Iterator,interface org.mule.routing.MessageSequence,interface java.util.Collection}"""" (java.lang.IllegalArgumentException). Message payload is of type: GoogleContactEntry (org.mule.api.MessagingException) org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor:35 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MessagingException.html) -------------------------------------------------------------------------------- Root Exception stack trace: java.lang.IllegalArgumentException: Object """"org.mule.modules.google.contact.wrappers.GoogleContactEntry"""" not of correct type. It must be of type """"{interface java.lang.Iterable,interface java.util.Iterator,interface org.mule.routing.MessageSequence,interface java.util.Collection}"""" at org.mule.util.collection.EventToMessageSequenceSplittingStrategy.split(EventToMessageSequenceSplittingStrategy.java:61) at org.mule.util.collection.EventToMessageSequenceSplittingStrategy.split(EventToMessageSequenceSplittingStrategy.java:26) at org.mule.routing.CollectionSplitter.splitMessageIntoSequence(CollectionSplitter.java:33) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ********************************************************************************""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7044","10/02/2013 17:00:09",3,"Make poll schedulers part of the same namespace ""When poll was enhanced to support different schedulers in Andes, the simple scheduler ended up being defined in the mule schema, and the cron scheduler ended up being part of the schedulers schema. In order to improve consistency, we want to have all the schedulers distributed by the ESB in the same schema. Move the default scheduler bean definition to the scheduler namespace. ""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7052","10/05/2013 22:50:09",13,"Create bitronix transaction manager module and integrate with existent transports ""Create a module to use bitronix transaction manager in mule. Integrate the module with existent mule transports""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7057","10/14/2013 17:55:05",13,"Finalize shared resources spec + create tasks to implement feature ""The initial draft of the shared resources spec is here: https://docs.google.com/a/mulesoft.com/document/d/15Pt1N4ylouxk-nFiAFAtfnOiqYyn5fnJn4X3iJtF9tI/edit?usp=drive_web Now that sufficient time has passed, we should finalize the specification, and scope out the amount of work it takes to implement the feature in Mule. Acceptance criteria for this Jira is that more Jiras are created with story points allocated to implement the feature.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7063","10/17/2013 20:49:24",2,"Add Spring Security LDAP to Mule Distribution ""Add Spring Security LDAP dependency to the standalone distribution.""","",0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7067","10/21/2013 13:59:16",8,"Improve the way webapps are deployed in the Jetty transport ""Remove the WebAppDeployer class, use WebAppProvider from newer Jetty versions instead.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7069","10/21/2013 15:39:12",3,"Update Cometd version in Ajax transport ""The current Cometd version used in the Ajax transport uses Jetty 6. Update Cometd in order to remove all references to Jetty 6 and use Jetty 8. Update ajax tests that use old jetty version.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7071","10/21/2013 15:43:14",2,"Update mule-jetty.xsd that contains references to old Jetty classes in its comments ""The mule-jetty.xsd file still contains references to old Jetty clases (org.mortbay) in the comments. Update this file.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7074","10/23/2013 17:30:29",8,"Need a way to add message properties other thread ""DM needs to be able to add flowVars in a asynch way to the message. See https://www.mulesoft.org/jira/browse/EE-3479""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7078","10/24/2013 18:32:15",1,"Create API for record level partial error handling ""Both Batch module, connectors, devkit and advanced applications will need some common ground to make partial error handling work: Devkit and connectors will need classes that return bulk operation status on a record per record basis Batch module will need to read partial error classes and treat them accordingly for marking record level errors. Advanced applications may define their own components that may return partial error information. Munit, debugger, batch module and advanced applications will also need to work on a uniform definition of record: Munit to provide means to set record level variables or assert record state Debugger to provide information about record state Batch module to register MEL extensions accessing the record, and in general to provide record level scopes. Advanced applications may eventually define custom steps (this extension is not planned on the initial release), needing to tap into the record scope objects. A small API maven module has to be introduced, so that it may be used as a dependency on the other projects as needed. This module should have the -api suffix, and have a version scheme independent from mule.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7082","10/28/2013 17:55:32",5,"Implement new summary module for calculating aggregation functions over streams ""Implement new module according to spec at https://github.com/mulesoft/mule/wiki/%5B3.5.-M3%5D-Summarizers""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7084","10/29/2013 13:46:03",5,"Deprecate dev.ee repository in favour of repository.mulesoft.org ""Change distribution management repositories to: https://repository-aster.mulesoft.org/nexus/content/repositories/ And build repositories to: https://repository.mulesoft.org/nexus/content/repositories/ ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7088","10/30/2013 13:26:47",8,"Improve the way Mime types are registered for outbound http attachments ""The HTTP transport uses javax.activation to handle outbound attachments. Mime types are registered by the email transport (through a static initialization block in the class DefaultDataContentHandlerFactory). Therefore, if this class is not loaded, there are no mime types available and there is an error when sending outbound attachments through HTTP (for example: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type text/plain). In the normal use of Mule this problem doesn't happen because all transports are in the classpath, but there should not be a dependency between the HTTP transport and the email transport. See HttpOutboundAttachmentFunctionalTestCase. If the mule-transport-email dependency is removed from the http transport pom, this test fails. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7089","10/30/2013 18:37:14",3,"Write spec for new summarizer feature ""Write a spec for a new feature that is compliant with the following story: Add a new message processor that would allow to totalise element attributes over a collection or stream. The element should be able to extract a value based on an expression, and then calculate on these summarizer functions: add, average, count, max, min over the value. The result should be saved into a flow variable also defined in the element. This processor should work with streams like auto paging collections. For these cases, the options are to lazily calculate the elements as the stream is consumed or to consume the whole stream. The former should be he default, and there should be an attribute allowing to change the behaviour.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7090","10/30/2013 18:54:13",5,"Make Mule rely on platform configured JCE provider instead of fixing on a predefined version ""TlsConfiguration gets defaults for several properties using an AutoDiscoverySecurityProviderFactory, which in turn provides defaults based on the JVM flavour in use. In particular, it sets the default JCE Provider to use, the JCE Provider implementation class, the default Keystore type, and the default SSL protocol type being use. This has several problems: * It doesn't allow to properly setup JCE providers as part of the platform configuration, something required to use a FIPS 140-2 compliant JCE provider * It fixes on old versions of the providers and doesn't leverage improvements made in the platforms, like IBM's improved JCE driver (currently we use a JCE provider that is 6+ years old on IBM JVMs) * It fixes the SSL/TLS versions supported, which causes SSL endpoints to support SSL3 (considered deprecated) but no TLS The java platform provides sensible defaults for all these, which get updated as the security landscape evolves, and which can be defined as part of the JVM configuration. Remove the """"discovery"""" of defaults, and use platform defaults for operations in and depending on TlsConfiguration. Acceptance criteria: It should be possible to use any JCE provider defined in the JVM environment in order to support FIPS compliant providers. Endpoints should rely on the registered JCE provider for SSL and use the default ssl type instead of hardcoding one (As FIPS providers will disable several modes and only allow TLS 1.0+). ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7091","10/30/2013 21:18:28",1,"IllegalStateException when doing OAuth dance with InMemoryObjectStore ""OAuth dance works fine with PersistentObjectStores but when using in-memory ones this error is obtained: ******************************************************************************** Message : Failed to invoke fetch-access-token. Message payload is of type: String Code : MULE_ERROR--2 -------------------------------------------------------------------------------- Exception stack is: 1. Only owner thread can write to message: Thread[[splunkfulfillmentqa].connector.http.mule.default.receiver.02,5,main]/Thread[[splunkfulfillmentqa].httpscon.receiver.02,5,main] (java.lang.IllegalStateException) org.mule.DefaultMuleMessage:1626 (null) 2. Failed to invoke fetch-access-token. Message payload is of type: String (org.mule.api.MessagingException) org.mule.devkit.processor.DevkitBasedMessageProcessor:134 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MessagingException.html) -------------------------------------------------------------------------------- Root Exception stack trace: java.lang.IllegalStateException: Only owner thread can write to message: Thread[[splunkfulfillmentqa].connector.http.mule.default.receiver.02,5,main]/Thread[[splunkfulfillmentqa].httpscon.receiver.02,5,main] at org.mule.DefaultMuleMessage.newException(DefaultMuleMessage.java:1626) at org.mule.DefaultMuleMessage.checkMutable(DefaultMuleMessage.java:1612) at org.mule.DefaultMuleMessage.assertAccess(DefaultMuleMessage.java:1541) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ********************************************************************************""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7097","11/04/2013 18:22:29",8,"Provide a way to specify valid cipher specs for SSL on transports that support the protocol ""SSL/TLS negotiate the actual cryptographic functions used on a session by session basis. In strict environments, it's necessary to remove older and weaker variants of many algorithms. It should be possible to setup the list of cipher specs allowed on secure connections. This setup should happen at server or at least application level, and the default should be to use whatever the cipher specs defined by default by the current provider. Note that this should affect not only https, but any other transport using tis, like pops, imaps, etc. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7098","11/04/2013 18:26:14",13,"Create automated test cases for xa transaction recovery ""Create automated test cases for xa transaction recovery.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7101","11/04/2013 19:54:41",8,"Add pool configuration elements for JMS and JDBC in bitronix ""It must be possible to configure a JMS ConnectionFactory pool and JDBC DataSource pool explicitly through XML configuration.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7103","11/04/2013 20:34:41",5,"Add support for specifying as a system property, FIPS compliant security model ""Add a system property mule.security.model that when used may alter the security setup of mule and it's modules. The default value should be 'default', and should result in the actual behaviour. Using a value that is not recognised should result in a fatal error preventing mule to be successfully initialised. The second supported value should be 'fips140-2', and should result in: * The pgp module being disabled - that is, using php module constructs should raise an error * Any TLS cipher suite NOT defined in the following list should be disabled: (note that the provider may not support all the suites described below - if it doesn't support any of these, an error should be raised). List of approved suites for FIPS: SSL_RSA_WITH_3DES_EDE_CBC_SHA SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA TLS_ECDH_RSA_WITH_AES_128_CBC_SHA TLS_ECDH_RSA_WITH_AES_256_CBC_SHA TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7108","11/05/2013 20:03:50",2,"Need to decouple Pipeline interface from MessageProcessorPath generation ""In order to be able to implement EE-3510 need to fix this issue.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7113","11/08/2013 12:16:30",3,"Add selectors functionality on Watermark ""Implement selectors functionality on watermark as described in https://github.com/mulesoft/mule/wiki/%5B3.5-M1%5D-Watermark""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7119","11/12/2013 21:29:54",1,"MEL DateTime is not serializable ""DateTimes should be serializable so that they can work with watermark.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7121","11/13/2013 15:21:01",1,"OAuth support throws raw exception when authorization code not found ""When receiving the Oauth callback an exception of type java.lang.Exception is thrown if no authorization code is found on the response (which is often the case when the user denys authorization). Because the exception is a raw type, there's no way to catch it and take a specific action. A new exception type should be created to that purpose and that exception should be thrown""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7123","11/15/2013 13:15:03",1,"MuleExceptions are not all Serializable ""The Exception interface is Serializable, however some implementations of MuleException contain non-serializabe fields which violates the Exception contract and causes errors when trying to persist the Exception in an ObjectStore. All non-serializable fields in any implementation of MuleException should be marked as transient""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7128","11/19/2013 17:04:24",2,"Need to support short lived queues ""So far, all queues in Mule start and stop with the mule context, meaning that once a queue is created it remains active until the owning application stops. This model does not fit the Batch module, which creates queues when a job instance is started and then needs to discard it when the job instance finishes. The clear() method that was added in 3.5.0-ME allows reclaiming the storage but the QueueManager still keeps in-memory resources that are never freed. Therefore the QueueManager interface needs to add the following method: void disposeQueue(Queue); This method frees all resources currently held by the queue including the storage (meaning that queue.clear() will be invoked automatically) Additionally, another common need when dealing with short lived queues is the ability to easily create/retrieve queues with custom configurations. To do that, the QueueSession interface will gain the following method: Queue getQueue(String name, QueueConfiguration queueConfiguration);""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7137","11/20/2013 18:43:39",3,"DefaultMessageProcessor chain needs to decouple from Pipeline ""DefaultMessageProcessorChain decides how to handle VoidMuleEvent on whether the flowConstruct is a Service or a Flow. This is done by testing the flowConstruct to be an instance of Pipeline. Now that the batch module has been introduced, we have a new type of FlowConstruct which is not a Service but not a Pipeline either, which causes errors when one-way outbound endpoints are used in batch. DefaultMessageProcessorChain should be changed so that it takes decisions based on the flowConstruct being an instance of Service only""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7140","11/21/2013 18:29:38",13,"Create domain concept in mule, basic resource sharing, and domain deployment feature ""This task includes: - Add domain concept within mule code base. - Behaviour of domain deployment / undeployment / redeployment including notifications - Class loading changes for domain class loader - Create resource based on a domain configuration file - Add logging functionality so domain resources log in their own file""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7142","11/21/2013 18:38:19",8,"Create mule domain + domain applications project creation using maven artifact. ""This should be kind of an extension of MULE-7138 but should also allow to have a multi module project where one of the project is defined as the domain and the other projects are mule applications that belong to that domain. This artifact should create a package containing the domain + the apps that during deployment it will first create the domain and then deploy the applications.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7145","11/22/2013 19:33:24",5,"Redeploy domain when domain config resource is updated ""When the domain configuration file gets updated, then the domain must be redeploy. Domain redeploy must also include redeployment of the applications of the domain. The sequence should be: - Acknowledge domain resources has changed. - Undeploy domain applications - Undeploy domain - Redeploy using the updated configuration - Redeploy domain applications""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7156","11/29/2013 20:01:40",1,"QueueProducer should have a variable generic type ""QueueProducer class is tied to Serializable as a generic type. it should allow any T""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7157","11/29/2013 20:11:56",1,"Allow creating ConsumerIterator instances without selecting a Consumer ""In 3.5.0-M3, ConsumerIterator has only one constructor which receives a Consumer. It can be confusing for a dev to choose the right Consumer implementations besides of generating unnecessary coupling between the streaming framework and whichever component using it. It'd be great for a developer to be able to only provide the Producer and let the system choose which Consumer implementation is a best fit""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7162","12/02/2013 21:12:31",5,"Add support for HTTP connector sharing ""Allow an http connector to be shared using it as a shared resources in a domain configuration.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7165","12/04/2013 19:03:06",3,"Request Body is not closed in the HttpMessageReceiver ""With the changes made in HTTP in 3.4 there's an issue were from time to time a request is accepted but the sockets gets unexpectedly closed. This doesn't happen with the OldHttpMessageReceiver class. We found that the difference on how the response is handled between both implementation is that in the OldHttpMessageReceiver the request's body if closed after successfully sending the response (something that the new receiver is not doing). After we added this code to the new receiver the issue was solved. Unfortunately we weren't able to reproduce this issue in our side, so we cannot create a test case to confirm the fix. The code we need to add is found in the line 210 of the org.mule.transport.http.OldHttpMessageReceiver class: if (request.getBody() != null) { request.getBody().close(); }""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7185","12/16/2013 19:12:14",8,"Analyze proper solution to MULE-6432 (true asynchronous ""We should decide the proper approach for implementing a truly asynchronous message processor.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7191","12/18/2013 22:51:36",1,"DefaultMuleMessage should instantiate transient fields when deserealized ""We're working in a new serialization mechanism for Mule that will not require objects to implement Serializable or to provide a default constructor. This relies on ASM, Objenesis and other non standard instantiaton methods that have as a side effects that transient fields initialized in line not being initialized. For example: private transient Map inboundAttachments = new ConcurrentHashMap(); When the MuleMessage is initialized through Objenesis, inboundAttachments will be null since a new constructor is added via ASM which ignores the transient fields. Since this constructor will only be used when serializing and DefaultMuleMessage implements the DeserializationPostInitialisable interface, the initAfterDeserialisation method should instantiate these fields if they are null""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7192","12/18/2013 23:57:58",1,"CollectionSplitter uses wrong type of List ""CollectionSplitter uses a LinkedList to split payloads of type Collection. An ArrayList would be way more efficient since the size of the collection is known.""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7194","12/19/2013 17:48:27",1,"Improper handling of UnknownHostException in Outbound TCP ""The problem is that when a hostname cannot be resolved (bad hostname is provided, or DNS is down, etc), Mule's connection pooling system will interpret it as localhost. In the case where the local host happens to be listening on the same port, it can result in messages being routed to the wrong place, whereas they should have failed to connect due to the bad hostname. This is caused by: 1. In the constructor of org.mule.transport.tcp.TcpSocketKey, an InetSocketAddress is constructed. If host resolution fails, the object is created anyway. 2. In org.mule.transport.tcp.TcpSocketFactory, 'getAddress()' is called on the socket key and passed directly into socket.connect(...). 3. In the case that step (1) failed, 'getAddress()' will return null. socket.connect(...) interprets null to be localhost.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7197","12/20/2013 20:41:36",2,"Producer interface should not be tied to List ""the Producer interface has a return type of List for the produce() method. This was fine for its original intent but as its uses keep growing we need something more generic. The method signature should change to simple T produce() and replace T with a List when necessary""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7202","12/30/2013 18:19:09",1,"Remove installer specific behaviour from SwitchVersion script ""Remove installer code from this file: https://github.com/mulesoft/mule/blob/mule-3.x/buildtools/scripts/SwitchVersion.groovy""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7206","01/02/2014 17:15:30",8,"Analyse the changes to have MULE_HOME and MULE_BASE ""We need to review the cost and the impact of making the change for MULE-7182 to have Studio starting their apps in the same way Mule Starts them""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7207","01/02/2014 21:23:04",8,"Create Scatter-Gather component for parallel multicasting ""The router currently in Mule makes a good job at doing message multicasting. However, since its processing is sequential, it's not a good fit for some use cases. Implement a scatter-gather component as described in https://github.com/mulesoft/mule/wiki/%5BMULE-3.5-February-2014%5D-Scatter-Gather for parallel multicasting""","",0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7217","01/07/2014 21:39:13",2,"Migrated Tests to new Web Services Consumer module ""Migrated Tests to new Web Services Consumer module""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7218","01/07/2014 21:43:28",5,"Get SOAP action working correctly ""Today the SOAP Action works for .NET WS. This has to work across all technologies.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7219","01/07/2014 21:52:03",13,"Configure Exchange Pattern based on WSDL Operation MEP ""Configure Exchange Pattern based on WSDL Operation MEP""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7220","01/07/2014 21:54:39",2,"Use an expression for the service address ""Use an expression for the service address so that dynamically invoke different services - e.g. in different locations. (different env's).""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7221","01/07/2014 22:03:28",3,"Should be able to add custom soap headers ""Should be able to add custom soap headers""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7222","01/07/2014 22:10:09",3,"An exception to be thrown when a SOAPFault is returned ""An exception to be thrown when a SOAPFault is returned so that I can handle it using exception strategies""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7228","01/09/2014 17:57:48",1,"Confusing log message in EventProcessingThread ""EventProcessingThread has confusing log messages like: logger.debug(""""Stopping expiring group monitoring""""); logger.debug(""""Expiring group monitoring fully stopped""""); Since this is an abstract class with different types of uses, those messages are confusing and should be changed to something that gives information about the actual thread that's executing""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7230","01/13/2014 15:15:40",3,"Changes in HttpMuleMessageFactory and AbstractMuleMessageFactory breaks 3.4.x devkit's generated code ""Changes introduced in HttpMuleMessageFactory and AbstractMuleMessageFactory are affecting 3.4.x devkit's generated code, where the constructor of HttpMuleMessageFactory was using the MuleContext as a parameter. The old behaviour should remain as a connector built in 3.4.x wouldn't work in a new (3.5) Mule version. As a side note: from now on (3.5.0-dolomite) devkit will use the new way of creating the factory.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7239","01/15/2014 15:33:56",8,"loader.override being ignored in 3.5.0-cascade - Cloudhub(Dec 2013) runtime ""The Connector is using CXF 2.6.0 dependencies, and it has defined a plugin.properties with the follow line loader.override=org.apache.cxf,org.apache.ws,org.apache.xml In 3.5 with Cloudhub (Dec 2013) runtime environment the same application fails because is invoking one operation that is not defined in cxf 2.5.9. The same application is working correctly on Mule Studio 3.4. The Demo Application can be found in here (https://docs.google.com/a/mulesoft.com/file/d/0B9Ow2Z2e_0YmOTlLSURNdmwxZXFDcFM4MU4wODB0VllYcjFz/edit). The connector version that is working can be located in here (https://github.com/mulesoft/ms-dynamics-crm-connector/tree/mule-module-ms-dynamics-crm-1.7.1) ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7252","01/20/2014 18:15:58",8,"Restart applications automatically even after failure ""When using Studio, it saves my changes to disk and Mule restarts my application automatically - which is wonderful, because I can rapidly prototype my application. However, if I make a syntax error, Mule will cease to redeploy my application after that, forcing me to restart Mule completely. Mule should auto-redeploy applications, even if the last deployment failed. (If we can't make that the default for 3.5, we should add a flag to support this in Studio)""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7253","01/23/2014 18:11:00",5,"Allow BTM to configure username and password for JMS ""The Bitronix Connection Factory should be able to receive a username and password to be used for JMS connections.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7256","01/28/2014 14:29:48",1,"WS consumer throws NullPointerException when defining an empty security element ""When defining a global configuration element for WS consumer that has an empty security element (defined but empty), a null pointer is thrown upon initialisation. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7258","01/28/2014 17:27:50",8,"Request reply does not work when using specific connector ""When the inbound endpoint of a request-reply router uses an specific connector, different to the default one for that transport, then it does not work since it cannot find the endpoint. Adding the connector as attribute of the path makes it work: To solve this problem the replyTo property must be generated with the specific connector if available.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7259","01/28/2014 20:07:31",1,"move scatter-gather config elements to the top ""scatter-gather component has two config elements: threading-profile and custom-aggregation-strategy. Right now, those share a sequence with the inner message processors in which its defined that these elements go on the bottom. For consistency with other components, they should be moved to the top, so that what used to be: Should now be: ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7261","01/29/2014 17:20:43",8,"Add support for domain bundle zip file deployment ""Add support for deploying a mule domain bundle file. Domain bundle includes not only the domain but the apps to deploy in that domain. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7263","01/29/2014 19:42:32",5,"MULE_REMOTE_CLIENT_ADDRESS variable gets the wrong value when http requests are proxied ""If an http request is proxied, the MULE_REMOTE_CLIENT_ADDRESS will have the address of the proxy instead of the client address. The X-Forwarded-For header contains a comma separated list of addresses, the first of which is the original client. Mule should look if the http headers contain an X-Forwarded-For header, and in such case populate the MULE_REMOTE_CLIENT_ADDRESS from it's first element if such element is a valid IP address. Additionally, when this situation is detected, add a new INBOUND property called MULE_PROXY_ADDRESS that contains the proxy address ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7264","01/29/2014 20:22:50",1,"DevkitSupport module should use apache commons StringUtils instead of Spring ""Replace usage of org.springframework.util.StringUtils for org.apache.commons.lang.StringUtils to prevent class loading issues when older projects are using prior versions of Spring""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7269","01/31/2014 18:10:59",8,"Review flaky tests in 3.x builds. ""Most of the slow test builds are failing because of flaky tests. We need to review them, test them locally and ignore them if necessary, saving the logs from the failures to later fix them.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7270","01/31/2014 18:33:45",8,"WS consumer returns an invalid xml document when the payload contains multiple namespaces ""If a soap envelope contains a body which uses at least two different namespaces, and one of those is not used in the top element, the resulting xml document doesn't declare all the namespaces, and thus is not valid. Example response that is not processed correctly: ... false false ... ... fails because it's returned as: ... false false ... ... Note that the xsi namespace is not imported. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7280","02/05/2014 13:10:12",5,"Anchor file is created before application gets deployed ""Anchor file is created after application unzip but application is still not initialized. Problem is in ArtifactArchiveInstaller#installArtifact To reproduce: # Create a zipped app with the below configuration. # Copy zipped file to ${MULE_HOME}/apps # Start mule using this command {{bin/mule start; if [ -f ${MULE_HOME}/apps/application-name-anchor.txt ] ; then curl http://127.0.0.1:8811/in ; fi }} You should receive and {{in}} message in the console but you get {{curl: (7) couldn't connect to host}} ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7282","02/05/2014 19:11:15",2,"Upgrade schema versions to 3.5 ""Upgrade the schema version to 3.5""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7284","02/05/2014 20:49:29",0,"Allow to use a different timeout on TestProcess.waitUntilStarted(). ""When Starting a TestProcess instance, if the application is larger than normal or depends on many services, it may take longer to start than the hardcoded 30 seconds, we should provide a way to set this property.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7285","02/05/2014 21:19:32",2,"If an error occurs while configuring a just created mule context, inside DefaultMuleContextFactory, this context is not disposed ""Several methods inside DefaultMuleContextFactory class create MuleContext objects and then configure them. If the configuration phase raises an exception, the created mule context is not returned and the could not be disposed.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7286","02/05/2014 21:33:48",2,"The class EventCorrelator.ExpiringGroupMonitoringThread has an expiryMonitor member that is not disposed at dispose phase. ""The dispose method of the EventCorrelator class is not taking into account the expiry monitor inside its inner class ExpiringGroupMonitoringThread.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7288","02/06/2014 02:07:18",3,"Allow new DB module config to be share between applications ""Allow the new DB config elements to be shared between applications using them as a domain resource. This will allow to share DataSource connections between applications. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7290","02/06/2014 13:50:17",5,"It shouldn't be allowed to deploy an application to more than one domain ""Try to deploy an application to more than one domain by putting this lines into mule-deploy.properties: """," domain=default domain=default2 ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7291","02/06/2014 14:07:07",5,"Disposing a domain do not undeploy application ""# Deploy an application to a domain # Delete domain anchor file Expected: application gets undeployed Actual: application remains deployed""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7293","02/06/2014 14:41:11",2,"TransientRegistry does not dispose all registered objects on dispose. ""When the dispose method is called on a TransientRegistry instance, the current registered objects are not disposed. Also, if different objects are registered using the same key, just the last object is kept and previous ones are lost. They should also be disposed at dispose phase.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7296","02/06/2014 16:25:54",5,"Domain initialization result (failure or success) should be shown in a box at the end of the log when starting ""Currently, domain initialization status is shown in the logs when performed. But, in the same way that applications, it should be shown in a summary box at the end of server start.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7299","02/07/2014 15:16:54",8,"Initial preparations for the Mule 4 development branch ""This task will track changes made in the mule-4.x branch in order to accomodate code cleanup tasks. The scope includes: - Upgrading minimum JDK to 7 - Removing any JDK 6 specific code or modules - Get a full maven build to run Out of scope (to be tracked in other tasks) - Removing classes and methods deprecated in mule-3.x ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7302","02/07/2014 17:59:58",5,"HTTP inbound endpoints listen for requests in a different path ""When http inbound endpoint listens to *in* path, if you send a request to path *inxxx* it receives it. To reproduce deploy this configuration using bin/mule -M-Dhttp.port=YYYY and run curl http://127.0.0.1:YYYY/inxxx """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7303","02/07/2014 18:10:12",1,"WS-Consumer wsdl doesn't allow resource paths ""The web service consumer requires the location of a wsdl file as part of it's configuration. The location is parsed as a URL and if not valid, it is parsed as a file path. The convention in mule is to treat these fields as resource paths, which would allow URLs, absolute files, but will also look for resource files (relative to the current classpath, and possibly inside a jar). Change the behavior so that the wsdl location is treated as a reouce location. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7307","02/07/2014 21:32:35",3,"Disallow multiple transaction manager to be used within an application ""Currently if multiple transaction manager are configured in mule, as mule only supports one, it will just peek the first one. To avoid confusion to users we must not allow users to configure multiple transaction managers.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7311","02/10/2014 13:43:49",8,"Lack of synchronization causes multiple expiration requests on Aggregator groups ""The test EventCorrelatorTestCase.processesExpiredGroupInPrimaryNode fails intermitently due to a lack of synchronization in the access to an object store between different threads, that sporadically leads to a group expiry being triggered several times. This may be a problem if the correlation is setup to process the group at expiration instead of giving an error. The problem is mitigated when using persistent object stores as I/O synchronisation is creating an adhoc happens-after causality.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7842","02/10/2014 13:45:23",13,"Jersey version upgrade ""Mule is using old jersey libraries (1.6) that would need to be upgraded to latest to develop new agent. Dependent on this library are: - current agent - some example and test classes - mule-module-jersey in CE ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7313","02/10/2014 21:14:17",5,"OAuth2 authorize MessageProcessor enters a loop if it's the last processor in the flow ""Consider the following flow: That results in google's OAuth login screen showing up. After authorization, the browser is continuously redirected to the same page over and over again. However, if the flow is changed to this: It starts to work perfectly after any message processor is placed after the authorization one. This is probably and issue due to the fact that authorize MP's are intercepting but in the first example there's nothing to intercept.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7314","02/11/2014 20:01:47",1,"Poll: watermark gives a wrong warning message when no results are returned from the query inside the poll ""When polling Salesforce to retrieve data using the watermark feature, a warning message saying that the watermark is null appears if the query does not bring back any data. For example, the following Salesforce query: SELECT Email,FirstName,LastName,LastModifiedDate FROM Contact WHERE LastModifiedDate > #[flowVars['timestamp']] Then the following warning appears even though the watermark value is not null: WARN Watermark [pool-13-thread-1]: Watermark value is null and will be ignored""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7316","02/12/2014 18:46:37",5,"Fix flaky FlowSyncAsyncProcessingStrategyTestCase. ""This is a flaky that was ignored.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7320","02/13/2014 15:31:46",8,"New database module Streaming feature is not working with large queries ""When the Streaming option of the new database module is activated, there is an error with large queries. Additionally, no error message is shown and no results are returned. Config: """"#[flowVars['timestampdb']]""""]]> Same configuration without watermark was also tested and same behavior resulted.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7321","02/13/2014 20:09:05",5,"Deprecate in favor of ""Now that we have an implementation of the scatter gather pattern, deprecate the element in favor of it. There is a slight variation in functionality, but for most cases scatter-gather will be prefered, and the advanced cases were you need to evaluate the same payload sequentially, yet fail at the first failure, can be accomplished using wire-taps. This task requires: - Issuing a warning when parsing in an xml definition. - Changing mule schema's documentation to flag the deprecation in doc - Deprecate class implementing the all router.""","",0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7322","02/13/2014 20:34:17",3,"MuleApplicationContext renamed to MuleArtifactContext breaks backwards compatibility ""On Mule 3.5-M4, MuleApplicationContext was renamed to MuleArtifactContext. This class is used in other projects, and will break them. Provide a deprecated MuleApplicationContext to avoid breaking these apps. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7323","02/13/2014 22:35:44",1,"ExpressionSplitterXPathTestCase has wrong assertions ""ExpressionSplitterXPathTestCase has tests which are broken but, as the assertions are not ok, they seem to pass. Lines: XMLUnit.compareXML(EXPECTED_MESSAGE_1, results.get(0).toString()); XMLUnit.compareXML(EXPECTED_MESSAGE_2, results.get(1).toString()); Should be: assertTrue(XMLUnit.compareXML(EXPECTED_MESSAGE_1, results.get(0).toString()).identical()); assertTrue(XMLUnit.compareXML(EXPECTED_MESSAGE_2, results.get(1).toString()).identical()); ""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7324","02/13/2014 22:42:13",1,"CxfBasicTestCase has wrong assertions ""CxfBasicTestCase has tests which are broken but, as the assertions are not ok, they seem to pass. Line: XMLUnit.compareXML(echoWsdl, result.getPayloadAsString()); Should be: assertTrue(XMLUnit.compareXML(echoWsdl, result.getPayloadAsString()).identical());""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7326","02/14/2014 22:30:08",5,"Can't use WebService consumer with operation without parameters ""Consider the documentation attached: The endpoint localhost:8081/ consumes a web services that takes a ZIP as an input parameter. That operation works perfectly. However, in localhost:8081/test I'm trying to consume an operation which doesn't take any parameters. There's no way to make this work because: 1) WS consumer is expecting me to generate the soap envelope using datamapper, however, I don't have a payload to transform so I'm forced to create a dummy map 2) Because the operation is expecting no parameters, the XML that DataMapper generates looks like this: 3) The above results in WS consumer returning this error, basically because there's no envelope to consume: org.mule.api.transport.DispatchException: COULD_NOT_READ_XML_STREAM. Failed to route event via endpoint: org.mule.module.cxf.CxfOutboundMessageProcessor. Message payload is of type: PostMethod Error put aside, it doesn't make sense to me that: * It seems like the only easy way to generate the SOAP envelopes is through DataMapper, which is not a CE feature like WS Consumer is * How do I create a valid envelope when the operation takes no parameters? * Because envelope generation depends on datamapper, I have to drop the WS Consumer box in the canvas before the DataMapper one. It's not natural for the developer to think the flow from right to left. * Shouldn't WS consumer be capable of auto generating the envelope, at least when it requires no parameters? ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7328","02/17/2014 14:05:29",8,"Can't use WS consumer with message properties ""Consider the attached configuration in which I'm trying to receive a ZIP as an http query param and then use that zip to invoke a weather web service. It is impossible to do so unless I use that message property to create a map in the payload and then use datamapper to create the invocation body. I should have to be forced to create completely artificial set-payload and datamapper message processors for doing something as simple as asking for the weather of a ZIP number. I should't have to write the SOAP body myself either. Any of these two options defeat the purpose of the component. I should be able to just pass the ws:consumer whatever attributes the invocation takes and it should be able to construct the body. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7329","02/17/2014 14:45:21",5,"Number of JMS consumers decreases to 1 after reconnection ""After reconnection the number of JMS consumers goes from 4 to 1 (In fact to 0, but goes to 1 after queueing a message). Steps: # Install the attached mule-config.xml # Start an ActiveMQ broker # Copy activemq-all-5.9.0.jar to lib/user # bin/mule -M-Dhttp.port=8811 # Wait for deployment # Go to activemq console and verify that there are 4 consumers on queue *in* # Verify that application works running: curl http://127.0.0.1:8811/jms1 and seeing that one message is queued in queue *out* # Restart activemq broker # Wait for console to be up ## Expected: 4 consumers on queue in ## Actual: 0 consumers # bin/mule -M-Dhttp.port=8811 ## Expected: 4 consumers on queue in ## Actual: 1 consumers I've tried setting {{numberOfConsumers=""""4""""}} in the connector but works in the same way It's a regression since in 3.4.1 and before works as expected Tried to load the application with 1000 requests and the consumer's number remains the same mule-config: ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7331","02/17/2014 18:58:15",1,"JMS inbound do not reconnect to queue after broker restart ""When restarting ActiveMQ a JMS inbound endpoint do not reconnect. To reproduce: # Install the attached mule-config.xml # Start an ActiveMQ broker # Copy activemq-all-5.9.0.jar to lib/user # bin/mule -M-Dhttp.port=8811 # Wait for deployment # Verify that application works running: curl http://127.0.0.1:8811/jms1 and seeing that one message is queued in queue out # Restart activemq broker # curl http://127.0.0.1:8811/jms1 ## Expected: one message is queued on queue out ## Actual: out queue has no message besides the one before restarting ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7335","02/17/2014 23:58:26",5,"Transformer resolution in TypeBasedTransformerResolver fails depending on which order transformers are found ""TypeBasedTransformerResolver uses registry to lookup all the transformers that are compatible with a given transformation. Then it searches on the obtained list of transformers looking for the best match to execute the transformation. Problem its that the transformers are not ordered, so the best match calculation fails to obtain a transformer when the two first transformers have the same weight but different implementation classes. In this case, if the best transformer is a third one, then it won't be found because the resolution will fail on the previous ones.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7336","02/18/2014 01:15:08",8,"Avoid transformer lookup inside registry to improve performance ""Transformer resolution inside MuleRegistryHelper implies two different lookup operations: one for TransformerResolver and another for Transformers. Both lookup operations have a high cost as they imply that prototype beans will be created during the search process. Performance can be improved, in particular avoiding high contention on the application classLoader, if the mentioned lookup are not executed. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7338","02/18/2014 14:11:13",1,"New Database Message Processor: Template tag is not accepting dynamic-query as a child element ""Steps to reproduce: 1.- Execute the followed Mule config: Issue: You get the followed SAXParserException """," Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'db:dynamic-query'. One of '{""""http://www.mulesoft.org/schema/mule/core"""":annotations, """"http://www.mulesoft.org/schema/mule/db"""":parameterized-query, """"http://www.mulesoft.org/schema/mule/db"""":template-query-ref, """"http://www.mulesoft.org/schema/mule/db"""":in-param}' is expected. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:388) ... 24 more ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7342","02/18/2014 14:40:29",1,"New Database Messsage Processor: rename to ""To be consistent with the db:in-param, the output parameter should be named db:out-param. Studio is already generating the XML as ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7343","02/18/2014 15:13:36",5,"Fail to expand properties when using property placeholder shared in a domain ""Steps: # Deploy the below application and domain # Put domain.properties in domain root dir # bin/mule * Expected: Mule starts and flow listens on 127.0.0.1:8811/in1 and 127.0.0.1:8811/in2 * Actual: Mule fails to start because $[http.port] is an invalid value for port * Note: I put domain.properties file in domain root directory because in domain/classes it is not found ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7346","02/18/2014 15:57:27",1,"New Database Message Processor: NPE when parsing queries in Templates ""Steps to reproduce: 1.- Create and run the followed Mule config: Issue: when running the application you get the followed NPE """," ', @OptionName = ] 'startup', @OptionValue = 'on';]]> INFO 2014-02-18 12:37:34,663 [main] org.mule.module.db.sqlexecutor.parser.SimpleSqlCommandParser: Parsing SQL: DELETE FROM Customers WHERE CustomerName='Alfreds Futterkiste' AND ContactName='Maria Anders'; INFO 2014-02-18 12:37:34,669 [main] org.mule.module.db.sqlexecutor.parser.SimpleSqlCommandParser: Parsing SQL: SELECT * FROM Users INFO 2014-02-18 12:37:34,671 [main] org.mule.module.db.sqlexecutor.parser.SimpleSqlCommandParser: Parsing SQL: USE AdventureWorks2012; GO EXEC sp_procoption @ProcName = '', @OptionName = ] 'startup', @OptionValue = 'on'; ERROR 2014-02-18 12:37:34,691 [main] org.mule.module.launcher.application.DefaultMuleApplication: null java.lang.NullPointerException at org.mule.module.db.config.CommandDefinitionBeanDefinitionParser.parseSqlReference(CommandDefinitionBeanDefinitionParser.java:69) at org.mule.module.db.config.CommandDefinitionBeanDefinitionParser.doParse(CommandDefinitionBeanDefinitionParser.java:62) at org.mule.config.spring.parsers.AbstractMuleBeanDefinitionParser.parseInternal(AbstractMuleBeanDefinitionParser.java:297) at org.springframework.beans.factory.xml.AbstractBeanDefinitionParser.parse(AbstractBeanDefinitionParser.java:59) at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:73) at org.mule.config.spring.MuleHierarchicalBeanDefinitionParserDelegate.parseCustomElement(MuleHierarchicalBeanDefinitionParserDelegate.java:85) at org.mule.config.spring.MuleHierarchicalBeanDefinitionParserDelegate.parseCustomElement(MuleHierarchicalBeanDefinitionParserDelegate.java:127) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1428) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:190) at org.mule.config.spring.MuleBeanDefinitionDocumentReader.parseBeanDefinitions(MuleBeanDefinitionDocumentReader.java:51) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:140) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:111) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:493) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174) at org.mule.config.spring.MuleArtifactContext.loadBeanDefinitions(MuleArtifactContext.java:106) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130) at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:537) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:451) at org.mule.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:86) at org.mule.registry.AbstractRegistry.initialise(AbstractRegistry.java:105) at org.mule.config.spring.SpringXmlConfigurationBuilder.createSpringRegistry(SpringXmlConfigurationBuilder.java:133) at org.mule.config.spring.SpringXmlConfigurationBuilder.doConfigure(SpringXmlConfigurationBuilder.java:88) at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:43) at org.mule.config.builders.AbstractResourceConfigurationBuilder.configure(AbstractResourceConfigurationBuilder.java:69) at org.mule.config.builders.AutoConfigurationBuilder.autoConfigure(AutoConfigurationBuilder.java:101) at org.mule.config.builders.AutoConfigurationBuilder.doConfigure(AutoConfigurationBuilder.java:52) at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:43) at org.mule.config.builders.AbstractResourceConfigurationBuilder.configure(AbstractResourceConfigurationBuilder.java:69) at org.mule.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:80) at org.mule.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:170) at org.mule.module.launcher.artifact.ArtifactWrapper$2.execute(ArtifactWrapper.java:62) at org.mule.module.launcher.artifact.ArtifactWrapper.executeWithinArtifactClassLoader(ArtifactWrapper.java:129) at org.mule.module.launcher.artifact.ArtifactWrapper.init(ArtifactWrapper.java:57) at org.mule.module.launcher.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:25) at org.mule.tooling.server.application.ApplicationDeployer.main(ApplicationDeployer.java:121) ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7352","02/19/2014 13:11:55",1,"Watermark should fail to start if update expression is not an expression ""It doesn't make sense for the watermakr use case to have constants as update expressions, thus, the user should be warn and the application should not start if such an error occurs. Right now, Watermark just evaluates that expression as a constant resulting in useless watermark values.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7353","02/19/2014 17:48:57",5,"Cannot share caching-connection-factory ""So far you cannot share caching-connection-factory.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7354","02/19/2014 19:49:31",2,"Selector watermark is not thread safe ""When using watermark with a selector, the same selector instance is reused across invocations which means that if two polls are executed concurrently values would be overwritten. Right now this is a non issue because watermark only runs on synchronous flows. However, it makes affects code reusability and this will potentially break if we decide to support async watermark or if CloudHub centralised scheduler decides to fire concurrently for different tenants""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7361","02/20/2014 21:08:10",1,"RequestContext.getEvent() returns null inside poll ""When a flow has a poll as a message source, the RequestContext is only set with the event after the poll listener has been executed. So, if inside the poll there's a MP depending on the RequestContext, it fails with NPE""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7362","02/20/2014 21:48:53",2,"Allow MEL expressions to safely access nested null properties ""Consider an object a with property b The expresion """"a.b.c"""" will fail if a.b is null. MVEL was enhanced to include a null safe get flag that would make that expression return null. Change Mule to set that mode of operation. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7365","02/21/2014 17:05:15",3,"Fix MtomClientTestCase. ""This is a flaky test.""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7366","02/21/2014 19:39:05",8,"Mule logs switch to DEBUG level when application uses the Salesforce Connector ""When deploying an application using the salesforce connector, logging level is downgraded to DEBUG. Also, all logging goes to the console and no file is generated for the app on the logs folder. The same app running from Studio doesn't show this behavior. This issue greatly affects performance and readability of the logs""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7367","02/21/2014 19:40:07",8,"Clean pom files to support faster build cycles ""We follow a build cycle of running tests of increasingly time in steps. In order to improve build times, refactor poms so that features can be disabled when needed. We will settle to standarize on the following switches: -DskipVerifications --> will disable running style checkers, licence checkers, and enforcer plugin -DskipIntegrationTests --> Will disable integration tests -DskipArchetypeTests --> Will skip archetype tests (which require archetypes to be already installed) Running unit vs functional tests will not be modified yet and will use our custom surefire plugin""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7368","02/21/2014 20:11:55",3,"SoapAction header is not being set in WS Consumer for Soap 1.2 web services ""The Web Service Consumer component is not adding the Soap Action header when consuming a Soap 1.2 web service. Example: http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDL If you consume the GetWeatherInformation operation through the WeatherSoap port, the Soap Action header is sent and everything works OK. If you consume the same operation through the WeatherSoap12 port, the server returns an error indicating that the SOAP Action header is invalid. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7373","02/24/2014 20:07:12",1,"Devkit intercepting message processors fail if they are the last element of a chain ""Then an intercepting message processor is the last in a chain, it's listener is null. AbstractListeningMessageProcessor, which is the base class for all intercepting message processors created by the devkit, assumes that it will always receive a non-null listener, and fails with a NPE on the process(...) methods that will attempt to call method process of the listener. This is reproduced by putting any devkit intercepting component as the last element of a flow or scope, or at unit testing level, if you don't set the listener but try to use any of the SourceCallback methods. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7374","02/25/2014 13:20:32",1,"The serviceAddress attribute should be required in WS consumer ""The serviceAddress attribute should be required. Currently if it is not set, an exception with an error message that is not clear is thrown.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7376","02/25/2014 20:42:37",5,"NullPointerException while initialising body ""When trying to consume the login operation from https://www.mulesoft.org/jira/rpc/soap/jirasoapservice-v2 , the attached NPE is found when WS Consumer MP is initialised""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7377","02/25/2014 20:45:29",5,"WS Consumer ignores imports in WSDL ""I'm trying to consume the login operation from https://www.mulesoft.org/jira/rpc/soap/jirasoapservice-v2. That operation relies on an Array type defined in an import. WS Consumer fails to detect if that operation has parameters or not because it ignores the import and thus it cannot resolve the type""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7379","02/25/2014 21:44:07",0,"Domain initialization should fail when domain dir structure is invalid ""Domain shouldn't get deployed when filesystem structure is not valid. It should check that mule-domain-config.xml is present and allowed directories should be lib, resources and classes or something similar. To reproduce create a directory MULE_HOME/domains/domain/ with a single empty file called test.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7380","02/25/2014 21:51:37",1,"Expiration doesn't work on object store ""This simple test reproduce that expiration policies don't work on the object store. Expected behavior is that last line return false but returns true."""," final String TOKEN_LAUTARO = """"lautaro""""; ObjectStoreManager osManager = muleContext.getObjectStoreManager(); ObjectStore store = osManager.getObjectStore(""""RefreshTokenStore"""", false, 0, 5*1000, 5*1000); store.store(TOKEN_LAUTARO, true); Thread.sleep(6*1000); store.contains(TOKEN_LAUTARO); //returns true, when it should be false ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7382","02/26/2014 14:43:06",3,"RefreshTokenManager's ObjectStore is not expiring entries ""RefreshTokenManager has an expirable object store to make sure that an access token is not refreshed more than one time in the lapse of one minute. That store should expire its entries after one minute but it's not doing so.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7383","02/26/2014 15:44:15",3,"Logging of message reception is written to domain log instead of app log when sharing http connector ""When an http endpoint receives a request it should be logged in application log, but it is logged in domain log.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7384","02/26/2014 16:00:20",3,"Stopping an application that shares an http connector makes the other application endpoint to stop ""# Deploy the two applications and domain # Start mule # curl http://127.0.0.1:8080/in1 and curl http://127.0.0.1:8080/in2 returns the expected # rm $MULE_HOME/apps/app2-anchor.txt # wait for app to get undeployed * Error: curl http://127.0.0.1:8080/in1 fails to connect""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7386","02/26/2014 16:37:27",5,"Shared connector MBean appears under application MBean and should be under the domain one ""There is currently no MBean for Domains, we should have one and shared resources should not be in each individual domain application.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7387","02/26/2014 18:49:07",1,"Add methods to handle schedulers and sub-flows in FunctionalTestCase ""Need to add methods to manually: * Stop all schedules * Run a scheduler on demand * get a sub flow * get all schedulers ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7390","02/27/2014 14:25:57",5,"XSLT transformer is vulnerable to XXE ""The current implementation of the XSLT transformer is vulnerable to the following threat: https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Processing Currently, there is no way to prevent this since it would require to: * Set the property 'javax.xml.stream.isSupportingExternalEntities' to false for the xmlInputFactory. Currently no property can be set XML factory at all. * Set the attribute of the transformer 'useStaxSource'. When this parameter is false (default) the XML factory is ignored. This attribute can't be set right now. We need to disable XXE by default and add an attribute which allows it when needed to keep backwards compatibility. Steps to reproduce: 1. Run the attached configuration. 2. Post the following XML to the endpoint http://localhost:9000/test: ]> &spi_entity_ref; 3. Inspect the content of the output and log. It will show the content of the /etc/passwd file. If you don't have it, you can change it to a file that you have in your filesystem.""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7394","02/27/2014 21:03:34",1,"Mule common's sources and javadoc aren't deployed to maven repo ""Mule common's sources and javadoc aren't deployed to maven repo. Maven command should add sources:jar and javadoc:jar. This is important since connector developer may use classes inside those jars and javadoc + sources are a must for usability.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7395","02/27/2014 21:57:29",1,"Add migration guide on CE distribution ""Add migration guide to the CE distribution""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7396","02/27/2014 22:19:16",1,"Cache and provide the StreamCloser through the MuleContext ""MuleContext should have a method getStreamCloser():StreamCloser so that it's easy to get it and we have an easy way to cache it""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7398","02/28/2014 01:35:17",5,"WebService Consumer does not distinguish between 1.1 and 1.2 services ""According to wsdl spec version 1.1 mandates the use of the SOAPAction header. Version 1.2 removes its use. Our consumer effectively assumes that the service is of type 1.1 and so attempts to set the SOAPAction header. This can upset a service of type 1.2 which may return an error like """"Server did not recognize the value of HTTP Header SOAPAction: ."""" Try to consume the service at http://webservicex.net/ws/WSDetails.aspx?CATID=2&WSID=74 for example using both the 1.1 and 1.2 request versions. 1.2 will fail. The way to address this in the cxf Proxy client was to make sure no SOAPAction was present in the outgoing request.""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7401","02/28/2014 19:10:51",2,"Include the security model used at mule container startup console ""Part of the changes made for 3.5 included creating a way of definning the security model to be used. The problem is that there's no feedback to the use on the security model except than the side effects derived from it. Make Mule container display the security model used when starting up.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7402","02/28/2014 19:21:14",8,"Fixed unused and undeclared dependencies in maven ""Running mvn dependency:analyze shows a lot of warnings due to unused dependencies and transitive dependencies used directly but undeclared Fix the project descriptors of the modules to include needed dependencies and remove unused ones. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7404","02/28/2014 19:43:54",5,"Reduce the number of distributions ""Mule builds the following distributions: deb-package embedded profiler scripting standalone standalone-light studio - Remove the distributions deb-package, profiler and scripting - Verify if embedded can be removed and replaced by requiring people to use maven - Verify is standalone-light can be removed (it's standalone without source code), or we can change standalone distribution to skip source code - we do publish source code for each artifact so the information is there for IDEs. - Verify if the Studio distribution can be removed. ""","",0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7406","03/01/2014 00:42:50",2,"New database: streaming is useless if statement fetch size is not configured ""Streaming mode is intended to avoid OutOfMemory exceptions when processing big resultSets and the idea is to return an iterator as the result of a query so the user can request records on demand. Statements have a fetchSize attribute that indicates the size of the chunk of records that will be returned on each database round trip. For example, fetchSize=5 and a resultset of 20 records will imply 4 chunks of 5 records each. The problem is that when fetchSize is not configured properly, the resultset won't be paged and it will be completely loaded into memory, ie: making streaming useless.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7408","03/03/2014 20:30:11",3,"StageName generation should be decoupled from Flow ""Right now, the Flow is responsible for generating stage names for resources that leave on its pipeline. That makes it imposible for components relying on such names (such as async) to exists in a FlowConstruct that is not an instance of Flow. This should be refactored so that other types of FlowConstruct can contain an async block""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7411","03/05/2014 16:39:23",1,"SXC filter router fails due to uninitialised transformer ""Due to the fix of MULE-7390, XmlToXMLStreamReader is now initialisable. SxcFilteringOutboundRouter is using an instance of that Transformer without invoking its initialise() method which causes it to fail. SxcFilteringOutboundRouter should properly initialise the transformer""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7412","03/05/2014 18:55:03",3,"Echo example fails to start because does not find mule-app.properties ""To reproduce # copy echo example zip app from distribution to app directory # Run bin/mule # See error in log""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7413","03/05/2014 21:47:04",2,"Bulk mode in insert/update/delete message processors should accept collection payloads only ""When bulkMode=true and payload is not a collection, insert/update/delete message processors are resolving queries using the default values in the query definition. That causes the execution of the query just once, but with null parameter values. Those message processors should accept only collections as payload/source. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7416","03/06/2014 22:15:47",2,"DB: Insert with bulk mode set to true does not return the correct metadata ""The new db component is not returning the correct datasense metadata when using the insert operation with the bulk mode set to true. Example: INSERT INTO TABLE TB1 VALUES(PAYLOAD.ID, PAYLOAD.NAME) with BULK = TRUE the expected metadata should be List<{id, name}>. Today it is returning {id, name}""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7418","03/07/2014 18:32:07",8,"DB Connector throws NPE when advanced-udate fails because connection error ""# Copy derbyclient-10.9.1.0.jar to lib/user # Deploy the attached config # curl http://localhost:8080/in * Expected: curl returns 0 * Actual: curl returns {{null (java.lang.NullPointerException). Message payload is of type: String}}""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7425","03/11/2014 14:49:36",3,"xpath function should not have any side effects on the message ""when the xpath() function is not given a source parameter, the result of the evaluation is put on the message payload, which is fine. However, when the source parameter is provided, the payload should not be modified because that causes undesired side effects when using the function in filters or choice routers. When a source is provided, the evaluation result should be set on the source itself""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7426","03/11/2014 19:12:50",3,"WS consumer not generating payload for a SOAP 1.2 web service with no parameters ""Currently the WS consumer detects if a web service doesn't require any input parameters, and in that case ignores the payload and generates automatically the SOAP body with the request. This is working correctly for SOAP 1.1 web services but not with 1.2 web services (in that case the payload is still used as SOAP body).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7428","03/12/2014 16:34:24",13,"Fix VM underlaying implementation ""Current queues implementation stores the queue content in the transient object store or in the persistent object store if the queue is persistent. We end up with a queue implementation based on a Map which doesn't make any sense. This also causes performance issues. Transactions are not reliable. We don't have a transaction log for local tx or for XA txs.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7429","03/12/2014 17:46:47",2,"Fix UntilSuccessfulWithQueuePersistenceObjectStoreTestCase recoversFromPersistedQueue test ""This test is testing on some build runs, and it relies on writing a file directly into an object store folder as part of it's execution. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7431","03/12/2014 19:53:19",3,"AbstractMessagingExceptionStrategy accessing an incorrect Even when using RequestContext ""When a collection message is sent to a subflow and an exception is raised inside it, the exception is not properly raised because is replaced by a """"java.lang.IllegalStateException: Payload was invalidated calling setPayload and the message is not collection anymore."""" instead of keep the original one.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7435","03/14/2014 17:31:12",3,"Fix ListSchema.groovy script ""This script prints lots of errors. ""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7439","03/17/2014 18:49:27",1,"Replace StringBuffer with StringBuilder whenever possible ""Because Mule started on the JDK 1.4 era, there're a lot of uses of StringBuffer. In most cases, there's no need for the contention that it generates and it should be replaced with StringBuilder""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7443","03/17/2014 21:20:35",1,"Move SimpleLoggingTable to core ""Move SimpleLoggingTable to core so that it can be reused by other modules without the need to depend on the launcher""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7459","03/25/2014 13:56:23",3,"Echo example mvn build fails because of test error. ""# Download mule-ee-distribution-standalone-3.5.0-M5-20140325.085332-72.tar.gz # Extract # cd examples/echo # mvn test""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7463","03/26/2014 13:56:42",3,"Monitored ObjectStores should behave consistently ""Monitored object stores do not behave consistently: * PartitionableExpirableObjectStore instances trim to max size by applying a Least recently used algorithm. However, MonitoredObjectStoreWrapper does it by applying a Last recently used algorithm. * Additionally, it is allowed to create objects stores that are: completely unbounded, TTL bounded only, TTL and size bounded, but you can't create one that's size bounded only. Expected behavior should be: * Managed object stores always trim to size in a consistent way using LRU. * I can have an ObjectStore that's bounded size wise but unbounded TTL wise ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7473","03/27/2014 15:17:26",8,"Remove deprecated methods on Transformer interface ""Remove deprecated methods and replace uses""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7478","03/27/2014 19:51:44",1,"All test log4j.properties should have the rootLogger at WARN level ""Many modules define their own log4j.properties, but some set the rootLogger to INFO which becomes too verbose. They should always be set to WARN""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7480","03/27/2014 21:12:33",1,"Add profile for system tests ""We need a profile for system tests (aka Standalone tests), execute only when profile system is active.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7481","03/28/2014 13:52:39",1,"Add extension point in MuleLockFactory ""MuleLockFactory delegates into a LockProvider to actually build the lock. Upon initialisation, it grabs such provider from the registry. An extension point is needed so that a provider can be passed into it before initialisation. If such provider is not given, then it fallbacks to the current behavior of taking it from the registry""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7482","03/31/2014 21:17:33",1,"Create Connector aware PagingDelegate concept ""Create the concept of connection aware and process aware PagingDelegate for cases in which a connection manager PagingDelegate is needed""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7485","04/01/2014 21:38:40",13,"Registered transformers in bootstrap.properties won't be found when the key is different than transformer.{x} ""Registered transformers in bootstrap.properties won't be found when the key is different than transformer.{x} If you define your transformer in the bootstrap.properties file as FooTransformer=org.mule.bar.FooTransformer This transformer won't be found by using the lookupTransformer/s methods. And therefore a failure will happen if the transformation is needed.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7488","04/04/2014 12:27:57",3,"Handles .NET ?singleWsdl wrong ""If http://demo.bromose.eu/DemoService.svc?singleWsdl is used, the flow gets a 400 response code. http://demo.bromose.eu/DemoService.svc?Wsdl is used, the flow works""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7490","04/04/2014 18:41:34",5,"Improve mule test cases to use a temporary folder for each test case ""Improve mule test cases so each of them use a temporary folder for the application working directory. This will probably reduce flakiness of test cases storing information in disk and also will allow to run test in parallel in the future.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7492","04/04/2014 21:05:56",1,"Add a tool for matching exceptions by its stack trace ""Sometimes it's needed to know if two exceptions have the same stack trace. To do this, we need to be able to compare the full stack traces but discarding the exception (and its causes) messages since they may contain invocation specific data. We need a tool that can generate an exception's full stack trace without any messages""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7494","04/07/2014 19:11:17",5,"Test cases override DefaultObjectStoreFactoryBean static delegate causing other tests to fail when split and aggregate operations are used. ""Test cases override DefaultObjectStoreFactoryBean static delegate causing other tests to fail when split and aggregate operations are used.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7500","04/09/2014 15:45:35",3,"WS Consumer fails when there is an invocation property ""operation"" defined ""When a message contains an invocation property called """"operation"""" and a WS consumer is present, the execution of the WS consumer fails because CXF uses the value of the """"operation"""" variable.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7501","04/09/2014 15:49:55",5,"Provide a way to log the SOAP envelope that is being sent in WS Consumer ""Currently it is hard to debug WS consumer because there is no way to log the SOAP envelope that is being sent. Provide a way to do this and consider how to integrate it with Studio debugger.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7502","04/09/2014 19:24:01",8,"Exception thrown by one-way outbound endpont in a Catch ES causes infinite loop ""If a System Exception is thrown inside a Catch Exception Strategy, and the flow that references it is asynchronous, and infinite loop is created, the application will retry to execute the exception strategy infinite times. I've attached to the jira a test case that reproduces the issue""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7504","04/09/2014 22:31:45",0,"Applications sharing connectors mix endpoint MBeans ""When connectors are shared inside a domain all the MBeans for the endpoints for those connectors are shown in all the applications contained in the domain.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7509","04/13/2014 15:06:35",5,"Transactional Queue Recovery fails when recovery queue has transient queue config. ""When executing local tx recovery and there's a transient config for a recovery queue mule fails with a NotImplementedException""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7510","04/14/2014 14:04:25",3,"MEL behavior is not consistent betsween maps and pojos for proeprty access ""With changes made for 3.5, MEL was changed so that property access for maps didn't fail (to be consistent with value access though map[key] syntax). This caused an inconsistency, as the same expression a.b will fail or return null depending on the actual type of a. In order to be consistent, we have decided to make property access return null in all cases. We will also revert back the changes that implied null safe property access by default, and keep asking users to use the .? explicitely). ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7512","04/14/2014 16:21:36",1,"Synchronous until-successfull waits in milliseconds instead of seconds ""When in synchronous mode, the until successful is waiting for the exact value of the seconds-between-retries attribute. Expected: a value of 10 on a synchronous until-successful waits ten seconds between each retry Obtained: it only waits 10 milliseconds ""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7513","04/14/2014 19:27:53",2,"deprecate until-successful's secondsBetweenRetries in favor of millisBetweenRetries ""Seconds between retries is fine for the asynchronous case, but when doing a synchronous wait, there're cases in which just a millisecond wait is required. This enhancement consists on: * deprecate secondsBetweenRetries attribute. Using it results in a warning message in the logs. It is to be mark as deprecated in the java code and the xsd * add a millisBetweenRetries property which is the new correct way of using the component * For backwards compatibility, setting secondsBetweenRetries will implicitly set millisBetweenRetries with an equivalent value * Setting both attributes at the same time will result in exception""","",0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7520","04/16/2014 18:55:57",3,"Avoid writing app log entries in container log file when not using an specific log4j config file for the app. ""When a log4j config file is not attached to an app, a default file appender is created but the app is still sending its output to the container log file. App default logging should only send app logs to default app log file.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7524","04/21/2014 14:32:33",3,"Encoded characters not working when using expressions for dynamic endpoints ""When using encoded characters (e.g. %40 for @) in conjunction with expressions it fails. For example this works: But this doesn't: Attached there's a project with a test case to reproduce this problem.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7536","04/22/2014 16:36:50",3,"Mule is still creating old default domain classloader instead of using new one ""Mule still has the lib/shared/default folder. This causes to use the old domain class loader infrastructure instead of the new one. This folder must be removed and a default folder must be created in domains.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7538","04/22/2014 18:59:48",1,"Application fails to start when having 16 or more connectors with asynch reconnection that fail to connect ""The problem is that the work manager used for reconnection is the one defined inside the DefaultMuleContext. This work manager is not configurable so it can handle 16 threads at most. The problem is that when a reconnection fails all the time uses 1 of the threads. So if you have more than 16 reconnections going on the number 17 will never get the chance to execute.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7543","04/23/2014 15:00:14",1,"Deprecate jdbc transport ""Due the creation of the new DB module, we should deprecate the old jdbc transport as studio has already done.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7548","04/24/2014 19:03:33",3,"Lifecycle does not start a QueueManager in the right order ""QueueManager must be started before any Flow. That's not happening for all QueueMAnager, it's only happening for TransactionalQueueManager""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7559","04/26/2014 16:56:16",3,"Mule build reactor is building embedded distribution before other modules ""Mule Embedded distribution is being build before modules and transports that are in it, so, build is failing.""","",1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7563","04/28/2014 11:01:16",8,"org.mule.util.Base64 upgrade ""org.mule.util.Base64 is a import of the version 2.1 of http://iharder.net/base64 This library is now available as maven dep, and therefor there is no need to copy&paste it. This library has several new versions 2.3.7, some of them with relevant bugfixes. However, 2.3.7 has some API changes. This might need to wait till Mule 4.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7571","04/29/2014 20:36:00",3,"Persistent queue logs and data remove after shutdown ""After mule shutdown mule queues logs and data are being removed. The problem is that dispose of the queue manager is removing everything. There's a another issue to solve which is that during undeploy of an app, the app data store in .mule/app-name folder is not being cleared. There seems to be two kind of dispose needed. One for undeploy of an app. And another just for shutting down the server.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7574","04/30/2014 20:10:31",1,"Possible contention on DefaultStreamCloserService. ""When running a batch job(ee feature), it was seen that periodically the threads gets locked as shown into the given stack-trace. We should add a way to improve this with a cache or another work-arround.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7575","04/30/2014 20:53:22",3,"Aggregator result has invalid session variables values ""When using a persistent store in an aggregator the session variables values do not have the latests value after the message aggregation. We should prioritise latest stored event session variables values over the ones provided by previous events. If not when execution inside a collection splitter and aggregator is synchronous the merge of the mule events results in a session with not the latests values.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7577","05/01/2014 00:27:37",1,"OAuth regression - RC1 OAuth connectors not working at all ""I found the issue in the org.mule.security.oauth.util.HttpUtilImpl#post(String, String) method. The refactor made to improve the exception error (MULE-7521) modified the way of working with the OutputStreamWriter (look for """"out"""" variable). After doing the #write(String) there is no flush(), hence the stream is not filled with the API response, and the response is always an error. The code is: when it should be This should solve all the issues with OAuth support for DevKit connectors."""," //.. try { out = new OutputStreamWriter(conn.getOutputStream()); out.write(body); int responseCode = conn.getResponseCode(); //.. } //.. //.. try { out = new OutputStreamWriter(conn.getOutputStream()); out.write(body); out.flush();//magic happens here int responseCode = conn.getResponseCode(); //.. } //.. ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7578","05/01/2014 00:46:11",2,"Improve HttpUtilTestCase ""HttpUtilTestCase passes regardless HttpUtilImpl flushes the output stream or not, which caused a bug. That test/functionality should be improved ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7588","05/07/2014 18:21:32",13,"LifeCycle is inconsistent across registries ""Because the LifeCycle manager handles individual objects instead of the mule context as a whole, there're differences in how the life cycle is applied to objects in the TransientRegistry in opposition to the ones in the SpringRegistry: * Objects in the TransientRegistry have a correct life cycle * Objects in the Spring registry that were registered by Mule's bootstrap, receive the Start and Stop phases correctly. They don't receive the dispose phase and the init one is invoked by Spring directly as an init-method, not through the life cycle execution. * Because default Spring registry objects don't receive the init through standard life cycle phase, they cannot be started before the TransientRegistry * Objects manually added to the spring registry by an app, don't receive the initialise nor dispose phases * LifeCycle is applied on Spring registry objects once they're all available in the application context. However, objects in the TransientRegistry get their lifecycle as they're registered, making it impossible for component A to reference component B if A is not registered first. This issue greatly depends on MULE-7587 ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7589","05/07/2014 18:44:41",8,"VM transactions should support multithreading ""VM transactions have as a known limitation around concurrency. Only the thread that started the transaction should be able to use it and/or close it. For highly concurrent use cases, it'd be great if scenarios like the following would be supported: Thread 1: Opens transaction A and polls one element from it Thread 2: Opens transaction B over the same queue and polls one element from it Thread 2: writes to the queue in the context of transaction A Thread 1: writes to the queue in the context of transaction B Thread 2: commits/rollbacks the transaction A Thread 1: commits/rollbacks the transaction B ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7594","05/09/2014 17:51:43",1,"Scatter-gather throws exception when using a one-way outbound endpoint. ""Using a one-way outbound endpoint in a scatter-gather with no message processors after it causes an exception. Tried VM and HTTP. I'm attaching the configuration to reproduce the issue. Using a request reply one or adding a message processor after the endpoint fixes it.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7597","05/12/2014 17:17:57",1,"scatter gather should require at least two routes ""Scatter gather should fail at start time it it doens't have at least two routes configured. Having only one route doesn't make sense for a parallel multicast.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7599","05/12/2014 21:46:59",1,"Add GPG signature to artifacts ""Need to add GPG signature to deploy to Maven Central ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7603","05/13/2014 14:15:49",0,"When using a Throttling policy with throttling statics enabled, limit headers are swapped. ""When the policy is applied, returned headers look like: Connection →close Content-Length →18 Content-Type →text/plain X-RateLimit-Limit →0 X-RateLimit-Remaining →10 X-RateLimit-Reset →60000 Wich shows that Limit and Remaining statics are swapped. (Remaining should normally be less or equal than Limit).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7611","05/16/2014 15:29:52",8,"MEL expression using dot notation .'variable-name' always returns null if first value at first access is null, even after value changes ""The following three logs: consistently work for 1st and 3rd. The second one using the dot notation consistently fails forever if first invocation fails after server restart and consistently succeeds forever if first invocation succeeds after server restart. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7615","05/16/2014 19:26:31",3,"RandomAccessFileQueueStore.getLength() is slow. ""The problem is the use of RandomAccessFile.getLength() inside RandomAcccesFileQueueStore. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7620","05/21/2014 17:15:14",13,"Define unified way to define the exception handler in execution scopes in mule ""Currently exception handler is defined by: - Flow - Transactional scope - Exception strategies - Outbound endpoint (when using LaxAsync) due bug fix. In some places the exception handler is retrieve by doing: event.getFlowConstruct().getExceptionListener() (AsyncInterceptingMessageProcessor). This is bad design because the MuleEvent should not have a reference to the FlowConstruct and the exception handler should not be retrieved from the MuleEvent. The MuleEvent contains dynamic information related to the current message while the exception handler must be defined statically by the flow configuration. The recommendation is that each scope or execution block (new Threads running part of the flow) should have statically defined the exception handler to use.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7621","05/21/2014 18:14:21",13,"Review mule logging consistency and analyse the effort to make it consistent and improve underlying technology ""We need to review our logs implementation ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7624","05/22/2014 02:01:29",3,"Fix JMX agent tests in management module ""As we changed the management module to run all the tests in the same JVM, a couple of tests failed becuase they create an RMI registry on a fixed port and interfere with each other. Change those tests so that they use a dynamically allocated port and run fine on the same jvm instance""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7627","05/22/2014 20:56:23",1,"CloserService generates debug log message without checking logger state ""If no closer is found for a stream, the StreamCloserService logs a message with debug level, even if the logger is not in debug mode. Additionally, that message contains the stream which in some cases can result in the stream being consumed and/or the thread blocking, as shown in the attached log""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7629","05/23/2014 20:51:20",0,"Provide a way to preserve the original directory when using moveToDirectory ""Wen using the moveToDirectory the original directory is not available in any property or scope.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7631","05/26/2014 16:52:44",2,"CopyOnWriteCaseInsensitiveMap KeyIterator class implementation issue ""Due to the way the KeyIterator class is implemented, calling next() followed by remove() removes not the element the iterator """"is on"""", but the following one. In line #181 of the class CopyOnWriteCaseInsensitiveMap, the array is evaluated to the original index, but any subsequent call to remove is performed on the incremented index.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7635","05/28/2014 18:19:20",1,"Add capabilities concept into extension API ""Add the concept of capabilities and Capable objects into the extensions api. An object is capable if it provides optional support for additional capabilities. A capability is identified by a class type. Implementations are not required to implement any capability at all, even if they support this interface. Capabilities are used to provide a future-proof path to incorporate changes that may otherwise break backwards compatibility. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7636","05/29/2014 15:26:21",1,"MuleProcessController default timeout is wrongfully configured ""by default it's 0, and it should be something like 60000.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7637","06/02/2014 18:00:40",8,"Implement HTTP Outbound performance improvements ""We need to implement the changes needed to improve http outbound performance based on the performance outcome for the proxy scenarios. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7638","06/02/2014 19:27:57",8,"OOM when recovering VM transactions ""When a transactional persistent queue is recovered and the size of the queue doesn't fit into memory then there's an OOM exception trying to recovery the pending transactions.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7639","06/03/2014 15:02:15",0,"Run OWASP dependency check in our dependencies ""Run this tool (https://www.owasp.org/index.php/OWASP_Dependency_Check) to assess possible vulnerabilities in our dependencies. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7640","06/03/2014 20:14:33",8,"Add introspection capabilities in the extensions API ""Introspection is the capability of an extension to be automatically discovered and described by mule""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7642","06/03/2014 22:26:06",0,"Close method for ReceiverFileInputStream should not raise errors if called twice. ""Close method for ReceiverFileInputStream should not raise errors if called twice.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7644","06/04/2014 14:42:28",8,"Upgrade build plans to Java 7 for compilation and test Mule ""We are dropping java 6 support in Mule 3.6, so we need to migrate our build plans to compile and test Mule to run on Java 7. We also need to remove the Java 6 builds. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7645","06/04/2014 14:47:58",13,"Create Java 8 test build ""We need to create builds to run the test suite of Mule on Java 8. This should be Oracle and Open JDK. Review if we should use IBM JDK 8 Beta or wait till it's final. - Create build for Mule Common with Oracle JDK 8 (We need to run Mule Common tests with JDK 8) - Create builds for CE and EE with Oracle JDK 8 - Create builds for CE and EE with Open JDK 8 - Optionally create builds for CE and EE with IBM JDK 8 (currently in beta AFAIK) Consider the possibility of having Mule builds parametrized and configure Java 7 as the default JDK and override with Java 8.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7646","06/04/2014 14:56:41",8,"Spike on new HTTP transport underlying technology ""We need to do a spike, and validate which underlying technology should be used for the new HTTP transport. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7650","06/04/2014 16:51:14",8,"DynamicClassLoader leaking classloaders ""Apparently DynamicClassLoader is holding a strong reference to MuleApplicationClassLoader when it should not. This is the GC root path for the leaked MuleApplicationClassLoader instance. To reproduce deploy any mule app, then undeploy it and check that there is a leaked MuleApplicationClassLoader instance."""," org.mule.module.launcher.MuleApplicationClassLoader parent of org.mule.mvel2.optimizers.dynamic.DynamicClassLoader classLoader of org.mule.mvel2.optimizers.dynamic.DynamicOptimizer [603] of java.lang.Object[5120] elementData of java.util.Vector classes of org.mule.module.reboot.MuleContainerSystemClassLoader contextClassLoader of java.lang.Thread [Stack Local, Thread] """"Mule.app.deployer.monitor.1.thread.1"""" native ID: 0x6403 ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7651","06/05/2014 01:36:23",13,"Implement plan to improve surfacing of schema reference in documentation ""Implementation of Schema Documentation Modernisation Plan articulated here: https://docs.google.com/a/mulesoft.com/document/d/1pLy1BBRQRrzltz-o8PKU9WN1IFEMdGvwkOdabSkRf6s/edit""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7661","06/10/2014 15:12:18",1,"org.mule.api.security.tls.TlsConfiguration#getSslContext() no longer visible ""org.mule.api.security.tls.TlsConfiguration#getSslContext used to have public visibility in mule 3.4.x and was being used from mule extensions. In 3.5.0, it's visibility was reduced to private breaking backwards compatibility with those extensions. The method must be restored as public""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7663","06/10/2014 22:16:50",5,"tls-default.conf entries are ignored sometimes ""When creating a SocketFactory for a https transport, the protocols declared in tls-default.conf are intersected with the default ones from the JDK. Because of this, protocols like SSLv2Hello cannot be enabled when running Mule 3.5.0 in JDK7. What should actually happen is that those protocols should be intercepted against the supported ones. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7673","06/16/2014 14:48:08",5,"DatabaseMuleArtifactTestCase broken after maven changes ""DatabaseMuleArtifactTestCase was broken by the manven changes related to not forking the JVM anymore when running test.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7674","06/16/2014 15:53:38",8,"mule frezes with 100% CPU utilization if accessing property of non-existing property ""If flowVars contains no element `user` then expression `#[flowVars['user']['name']]` will freeze mule (thread) eating your CPU @ 100%. ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7687","06/19/2014 15:04:36",5,"mule does not propagate system properties when started with ""restart"" command ""bin/mule restart -M-Ddefault.port=1337 expected: app deployed what happens: deployment error because system properties are not propagated. ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7692","06/20/2014 01:23:35",8,"Create way to process JMS messages in a guaranteed order without needing to override a Java class ""Several customers want to know how they can enable message sequencing in MuleESB (making sure that inbound messages are delivered in the same order to the various endpoints in a flow). Using the resequencer is not a pattern as the number of messages could be infinite. There is currently no way to do this in a cluster. You can however extend the message receiver in the JMS transport. Albin did this for Boeing and they seemed satisfied with the solution. https://github.com/albinkjellin/jms-single-consumer We should implement this, or a more elegant version of it, in the product itself.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7696","06/24/2014 21:29:05",0,"App specific log file not created on windows ""App specific log file not created on windows.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7701","06/26/2014 20:38:22",5,"Fix flacky test UntilSuccessfulTestCase.testPermanentDeliveryFailureDLQ ""Fails on CI with message: Error Message Wanted but not invoked: outboundEndpoint.process(); -> at org.mule.routing.UntilSuccessfulTestCase.testPermanentDeliveryFailureDLQ(UntilSuccessfulTestCase.java:193) Actually, there were zero interactions with this mock. Stacktrace Wanted but not invoked: outboundEndpoint.process(); -> at org.mule.routing.UntilSuccessfulTestCase.testPermanentDeliveryFailureDLQ(UntilSuccessfulTestCase.java:193) Actually, there were zero interactions with this mock. at org.mule.routing.UntilSuccessfulTestCase.testPermanentDeliveryFailureDLQ(UntilSuccessfulTestCase.java:193) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:46) at org.junit.internal.runners.statements.FailOnTimeout$1.run(FailOnTimeout.java:28) Standard Output ================================================================================ = Testing: testPermanentDeliveryFailureDLQ = ================================================================================""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7713","07/02/2014 19:49:03",0,"Instead of logging throughout the wrapper, mule should only send to stdout important information. ""Currently, all mule logs are sent to the console (stdout) where the tanuki wrapper encapsule them and duplicate it on console (adding its own information) and also to the mule.log file. This may be causing performance problems. We know that loggin directly to a file or limiting logging to level error can increase performance. So a possible solution to this could be: - Add a fileAppender to the log4j configuration with the actual INFO level - Increase the consoleAppender level to WARNING or ERROR - We still want to log wrapper information, we should find a way to do not duplicate this information.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7715","07/03/2014 15:31:33",8,"Support XML definition of Beans in extensions configurations ""Some extensions make use of beans on their configuration. It should be possible to create those beans directly on the config definition without the need of defining a spring bean. At the same time, the same extension mike take lists or sets of beans. Those should be supported also. For example, assuming that the heisenberg extension has a configuration Bean of type Door, and a list/set of type Ricin. As a user, I should be able to define this: ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7716","07/03/2014 15:41:35",8,"Generated XSD for Mule extensions should include map class javadocs to schema documentation ""When Extension XSD is generated in the compile phase, it should be possible to use an annotation scanner to extract the extension's javadocs to use them as schema documentation. It is acceptable for this to not happen when building the schema for test case purposes""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7718","07/03/2014 16:41:07",5,"Add test support for extensions ""Need test infrastructure for extensions, so that we can guarantee that * the extensions manager will be available every time it's needed an * The xsd is regenerated on each run so that a developer doesn't need to do so automatically every time""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7719","07/03/2014 16:47:24",5,"Create parent module for extensions ""Create a parent artifact for extensions to agglutinate all the created extensions. The purpose of this parent artifact is not only about organising modules, it's also to define a parent pom which will hook up from the compiling phase to automatically generate the schema definition and spring handlers""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7720","07/03/2014 16:50:52",13,"Define Extensions execution API ""Just like we defined an introspection API for mule extensions, we now need an API to execute operations on those extensions. This task is about defining, designing and documenting that API. Not implementing it.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7721","07/04/2014 15:22:08",2,"Create a maven property for groovy-all version ""This dependency in pom.xml has a harcoded version, we should use a property. org.codehaus.groovy groovy-all 1.8.6 And also verify that there is no other places where we use the hardcoded version ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7723","07/04/2014 20:54:30",5,"Remove unsued configuration builders ""We have code to support creating a mule flow / service using a jruby script, groovy or Guice. The actual creating of the script requires advance knowledge of mule internals and it's not useful. Nobody is using it and also we don't support it in our IDE. We should only keep the spring configuration builders""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7724","07/04/2014 20:54:32",5,"release profile doesn't build javadoc jar ""Running {{mvn -P release install}} doesn't build javadoc jars at least for mule-core. It only builds: * mule-core-3.5.1-sources.jar * mule-core-3.5.1-tests.jar * mule-core-3.5.1.jar ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7725","07/07/2014 15:08:55",0,"Update Maven pom information ""For uploading to Maven Central repo we need to have our pom developer section completed.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7728","07/07/2014 21:13:04",0,"Collection aggregator fails with high amount of messages. Default in memory object store is inefficient. ""When a high amount of messages are aggregated the collection aggregator performs several inefficient operations that make the operation fail. Also, the default implementation for the in memory object store is very inefficient when there are a big object store partition.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7730","07/08/2014 19:38:36",3,"Create javadoc jars on the release profile ""Currently, we don't create javadoc jars as part of the release profile, requiring us to manually create and deploy them. Modify the build descriptors to create the javadoc files for each module. Note that besides this, there must still be a way to create the aggregated javadocs to be published online. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7731","07/08/2014 22:11:35",3,"JMS transport should reuse javax.jms.Session, javax.jms.MessageProducer instances by default ""All Mule JMS transport must reuse javax.jms.Session, javax.jms.MessageProducer by default without relying on a specific connection factory implementation. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7736","07/08/2014 22:39:16",3,"Ensure internal SEDA queues are bound by default to avoid OutOfMemoryException's ""A default size for maxQueueSize must be defined, at least for the case where the queue is in-memory. We need to determine if: i) this default is best defined on the processing strategy or object store. ii) if it’s best to use a static default, or if it is best to determine the default based on heap size or some other parameter. In ii), a related concern to keep in mind here is whether or not we can have a mechanism for Mule self-tuning that we can include as EE-only.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7740","07/09/2014 23:09:36",5,"Bundle scripting pack with Mule CE by default ""Mule CE currently doesn't bundle the scripting libraries (i.e. Jython) by default. Instead, users have to download a separate scripting pack: https://repository.mulesoft.org/nexus/content/repositories/releases/org/mule/distributions/mule-scripting-pack/3.5.0/mule-scripting-pack-3.5.0.zip We should evaluate whether or not it is feasible/practical to bundle this scripting pack together with the base Mule CE build, and do so if seen fit. The Mule EE distribution currently comes with these scripting libraries bundled with the deistribution afiak.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7743","07/11/2014 17:46:05",0,"Delete test replaced by system one and added again by mistake. ""Test UntilSuccessfulWithQueuePersistenceObjectStoreTestCase was marked as flaky, replaced by a system test and removed. However, it somehow made it back to the 3.4.x branch and it's causing the build to fail since the config file is missing.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7748","07/14/2014 22:22:16",5,"Seda queues with persistent profile fail in Windows ""When using a queue asynchronous with a persistent queue store, and when using windows it fails because the name of the file to store the queue data is invalid. See: http://forum.mulesoft.org/mulesoft/topics/anypoint_studio_default_persistent_queue_store_java_io_ioexception_the_filename_is_incorrect""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7751","07/16/2014 16:46:56",3,"Update maven-deploy plugin to 2.8 ""Artifact deployment repo is defined in the distributionManagement section of the mule main pom.xml file. Sometimes we need to stage changes in other repositories in order to make tests that do not affect the rest of the community. The maven deploy plugin provides a way to override the deployment repo, but only in version 2.8 it allows specifying separate snapashot and release repos. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7753","07/17/2014 16:27:45",3,"Remove maven archtetypes and ant tools ""Remove Maven archetypes, archetype tests and bobberplus (archetype builder). Transport, Module, Catalog, Patterna rchetypes are outdated and unmaintained. Application archetype has evolved into it's own project in AppKit. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7759","07/17/2014 17:32:46",8,"AMQP transport. Define specs document. ""AS A product owner or community member I WANT to be able to review the specs SO THAT I can and contribute with my feedback ""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7760","07/17/2014 17:34:34",8,"AMQP transport. Define connector schema ""AS A user I WANT I want to be able to rely on a defined schema to write my AMQP integrations SO THAT I have exact knowledge of how I’m syntactically supposed to use the transport and to have help from my IDE to autocomplete and detect errors. ""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7762","07/17/2014 17:39:15",8,"AMQP transport. Create configuration element (connector). ""AS A user I WANT I want to be able to configure the transport in a single point SO THAT I can configure the common transport attributes in a single reusable place ""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7763","07/17/2014 17:41:26",8,"AMQP transport. Create inbound receiver (consume) ""AS A user I WANT I want to be able consume continuously amqp messages SO THAT a MuleEvent is created and delivered to a flow when a messages arrives to a queue and is comsumed ""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7764","07/17/2014 17:43:26",5,"AMQP transport. Create inbound requestor (request) ""AS A user I WANT I want to be able consume instantly amqp messages SO THAT I can consume messages at any point of the flow ""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7766","07/17/2014 17:47:16",8,"AMQP Transport. Integration testing. ""AS A user I WANT I want the transport to be tested against a real broker and a real application. SO THAT I can be sure the transport works on real world usage. ""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7767","07/17/2014 17:48:58",0,"AMQP Transport. Write documentation ""AS A user I WANT I want to have documentation around the features of this transport SO THAT I can learn how to use it and to have a reference ""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7771","07/18/2014 20:39:10",5,"Fix DateTimeTimeTestCase.seconds flakyness. ""This test is flaky. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7772","07/18/2014 21:38:40",1,"Create script for uploading to Maven Central ""Upload the script to upload to maven central.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7773","07/21/2014 14:14:58",0,"Dynamic reference to sub flow produces lifecycle errors ""When a sub flow is referenced using a dynamic expression the sub flow initialization raises an exception and the flow is aborted.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7774","07/21/2014 16:08:44",0,"Wrong format for date in HTTP header ""HttpResponseBuilder is using a wrong format for the 'Date' header: EEE, dd MMM yyyy hh:mm:ss zzz This comes from org.mule.transport.http.HttpConstants.DATE_FORMAT The problem is that with this format it's impossible to know whether the date is AM or PM. For example, it shows the following when executing it at 3:24 PM Fri, 04 Jul 2014 03:24:27 ART Here you can't tell whether it's 3 PM or 3 AM. The output should include the AM/PM indicator or use a 24 h format (by changing the 'hh' to 'HH'). There's also another constant in the mentioned class that seems to have a better format: org.mule.transport.http.HttpConstants.DATE_FORMAT_RFC822 In order to reproduce this issue, please find attached a test case that doesn't contain any meaningful assertion but it logs the 'Date' header. Also this needs to be executed after 12 PM to see the problem better.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7775","07/21/2014 16:38:19",0,"Replace all uses of wrong date format for RFC one in HTTP transport. ""Some of the references to date format are using one with no AM/PM and no 24 hour format. These need to change for the format specified in the RFC.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7777","07/23/2014 20:23:35",3,"Add GPG Maven Plugin to Mule Common ""Add the plugin, default skipping signature and configure release build plan to enable GPG signature.""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7780","07/25/2014 16:55:03",0,"JUnit rules and matchers for Mule Standalone server ""# Create a JUnit rule that starts Mule Standalone in the before stage and stops it in the after stage. # Create a JUnit rule that starts installs Mule Standalone in the before stage and clean it in the after stage. # Create a JUnit matcher to know if mule is running # Create a JUnit matcher to know if application is deployed in Mule Standalone ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7784","07/30/2014 18:00:24",0,"Configure build for skipping functional tests ""Need to configure when to run functional tests or not. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7787","07/30/2014 22:06:43",5,"Do performance testing of log4j2 implementation ""MULE-7769 implemented asynchronous logging through log4j2. Please do performance testing over it""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7788","07/30/2014 22:09:08",8,"Create automated tests for log separation ""MULE-7769 revamped mule's logging infrastructure. This code already contains some unit tests about its behavior, but actually verifying that 2 apps deployed in mule have their logs separated, that they are properly rolled over, etc requires an external system test""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7789","07/31/2014 01:12:10",8,"Update mule-transports-http to tomcat 6+ ""PR-514 mule-transports-http depends on tomcat 5.5.23 for cookie processing. Upgraded to tomcat 6 version used by mule elsewhere using ${tomcatVersion}. Tomcat moved this into coyote. Verified working in tomcat 6+. Defaulted httpOnly to false in this instance since it was not part of tomcat 5 and not part of cookie from commons-httpclient and thus was naturally already false. In tomcat 6, httpOnly is configurable and default in tomcat 7+. This seemed most appropriate way to get onto tomcat 6+ as tomcat 5 is end of life and solved use case we had running mule within tomcat 7 & 8. See pull request on github PR #514, jira request Mule-6705, and jira request Mule-5100. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7805","08/13/2014 16:06:54",0,"Upgrade Spring version to 3.2.10 in Mule 3.5.x ""Upgrade Spring version to 3.2.10 in Mule 3.5.x""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7807","08/13/2014 18:34:55",3,"Running unit tests on clean working directory with an empty repository fails because missing jar "" This fails because unpacking embedded distribution dependencies is binded to generate-sources phase, but jars are still not available (because we are running test phase). Apparently Maven dependency plugin when jar is not available and has to resolve the dependency, resolves the artifact file as the classes directory for the dependency, so every file in that module is available to the current module. As we are trying to unpack it fails because the classes directory is not a jar file. """," git co git@github.com:mulesoft/mule.git cd mule mvn -Punit -Dmule.test.timeoutSecs=30 ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7809","08/14/2014 00:13:48",3,"Remove incorrect assertion from Test createHttpServerConnectionWithHttpConnectorProperties ""Test org.mule.transport.http.HttpServerConnectionTestCase.createHttpServerConnectionWithHttpConnectorProperties asserts that socket packet size is set on a newly created socket to the value specified by configuration. But the value as specified by the JDK documentation is just a suggestion, and the test is currently failing on CI: org.mule.transport.http.HttpServerConnectionTestCase.createHttpServerConnectionWithHttpConnectorProperties Error Details expected:<1024> but was:<1148> Stack Trace java.lang.AssertionError: expected:<1024> but was:<1148> at org.junit.Assert.fail(Assert.java:93) at org.junit.Assert.failNotEquals(Assert.java:647) at org.junit.Assert.assertEquals(Assert.java:128) at org.junit.Assert.assertEquals(Assert.java:472) at org.junit.Assert.assertEquals(Assert.java:456) at org.mule.transport.http.HttpServerConnectionTestCase.createHttpServerConnectionWithHttpConnectorProperties(HttpServerConnectionTestCase.java:263) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:46) at org.junit.internal.runners.statements.FailOnTimeout$1.run(FailOnTimeout.java:28) Standard Output ================================================================================ = Testing: createHttpServerConnectionWithHttpConnectorProperties = ================================================================================ ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7810","08/14/2014 15:56:49",3,"Functional test not ran when outside test/functional directory ""When I try to run FileReceiverMoveDeleteTestCase test from root directory it fails because the test is not found, but when I run it from transports/file it runs fine. Using this command: {{mvn test -Pfunctional -Dtest=FileReceiverMoveDeleteTestCase}}""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7811","08/14/2014 17:11:17",13,"Clean up opensource AMQP connector ""Old AMQP transport should be clean up, current issues fixed, current pull requests merged/refused.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7820","08/19/2014 20:16:53",0,"ClassLoader leak when undeploying application ""ApplicationClassLoader is not collected after application is undeployed. This is due to several issues which are linked to this container one. This issue should only be closed after all related issues are fixed and we can see that undeploying an application collects the classloader""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7829","08/22/2014 18:51:56",3,"upgrade log4j2 version to 2.0.2 ""log4j 2.0.2 was release and it contains some fixes, some of which we requested. We should upgrade""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7837","08/25/2014 20:24:29",0,"Imap 'RetrieveMessageReceiver' does not read the whole folder when deleteReadMessages=""false"" ""When reading emails with IMAP and not deleting them, the poller receiver continues to infinitely loop over the same set of messages, as it can be evidenced on org.mule.transport.email.RetrieveMessageReceiver class in the poll() the following line can be found: Message[] messages = folder.getMessages(1, batchSize); The first argument should increase proportional to the batch size to avoid retrieving the same messages over and over and thus not meeting the loop condition. done = batchSize >= count;""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7843","08/29/2014 03:35:33",8,"Allow extensions code to be splitted in several units ""As described in the execution section of the spec, a extension's developer needs to have the option to spread the configurations and operations across several classes which instances have their own lifecycle.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7847","08/29/2014 21:16:51",8,"Upgrade JSCH to version 0.151 """"""Verify:false"""" exception is still encountered in Mule 3.5.1 with Jsch 0.150, according to their release note it may require version 0.151 http://www.jcraft.com/jsch/ChangeLog Australian Post is still in 3.4.0 and has reported this issue(https://na6.salesforce.com/5008000000ZO4Qe), I have tried to use loader.override to include jsch 0.151 in the application but """"verify:false"""" exception is still sporadically encountered during the load test. If I replace the jsch.jar to 0.151 in /lib/opt, then the issue seems to be resolved. I have run the load test for an hour and I did not encounter the exception. Please advise 1. Is there any impact to upgrade jsch jar to 0.151 in Mule's default distribution? 2. Is there any way to patch the issue without replacing the jsch.jar from /lib/opt? We would need to patch both the standalone and cloudhub deployment runtime. Some other customers in Cloudhub are also heavily using SFTP, they can't replace the jsch jar in the Cloudhub runtime themselves. Many thanks!""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7851","09/03/2014 16:14:57",0,"SecretKeyEncryptionStrategy does not use the supplied key ""SecretKeyEncryptionStrategy takes a key as an argument but then it never uses it. Instead, a dynamic key is generated during initialisation time. This does not only breaches the contract exposed to the user, it also makes it impossible to decrypt messages after an application restart since the generated key will be different.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7852","09/03/2014 18:15:24",0,"Add a way to do assertions on mule logs with or without the mule process controller. ""As part of the logging tests we need a way to do assertions on the mule logs.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7979","09/03/2014 18:46:25",1,"Deployment Service tracks applications before they are successfully deployed ""Deployment service tracks applications as deployed before they have actually been deployed. This leads to retrieving an application from the list that has a context which has not been initialized yet or even that failed to deploy. In gateway we are retrieving all applications with getApplications, and verifying that the muleContext is not null.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8003","09/03/2014 18:52:53",5,"Register core extensions as domain deployment listeners if it applies ""When a core extension is initialized, if it implements the DeploymentListener interface, it's added to the collection of deployment listeners but not to the collection of domain deployment listeners. In the Gateway we are registering the core extensions as deployment listeners and setting the endpoint message notification on the context when the mule context creation notification is fired, but when the domain's mule context is deployed, the core extensions are not registered as listeners and the notification is never fired. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7859","09/09/2014 16:58:05",5,"getApplications() method in MuleDeploymentService should include more apps ""The getApplications() method in MuleDeploymentService only returns applications that were successfully deployed or that failed to start. Applications that failed to be installed or initialised are not returned but kept in a zoombies map. This is inconsistent. The method should return all applications for which deployment has been attempted, and per MULE-7800, it should have a status marking which ones failed. This makes for more useful and predictable behaviour while eliminating the need for the zoombies map. Finally, notice that the javadoc for that method says that it only returns deployed applications. That comment does not reflect the actual behaviour of the method not its real intent. That javadoc should be fixed also.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7863","09/10/2014 18:54:29",13,"Spike on Extensions API execution model - Part 1 ""Do a spike on being able to execute operations through the extensions API""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7865","09/11/2014 15:49:40",13,"Add support for OAuth in the HTTP connector (Authorization code) ""Implement OAuth support for the outbound part of the HTTP connector. Support only the authentication-code grant type for now.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7873","09/11/2014 17:14:29",8,"Add support for HTTP Response builder and HTTP Response Error Builder ""Add support for HTTP listener child element http response builder and http error response builder. All features from the HTTP connector spec for this elements should be supported.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7878","09/15/2014 14:20:51",3,"Enable TLS protocol versions 1.1 and 1.2 by default ""As Mule 3.6 requires Java 7, enable by default protocolo TLS versions 1.1 and 1.2 so that secure socket connections can leverage them. They were not enabled by default due to Java 6 compatibility, which doesn't implement them, but while they are not the default in Java 7, they are always supported. This change will mostly be around setting up the correct definition in tls-default configuration file. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7887","09/19/2014 20:36:01",2,"DEPLOYMENT_FAILED status should be applied to applications that fail to start ""The status DEPLOYMENT_FAILED was added per issue MULE-7800. That status is applied to applications that failed to be installed or initialised. The same status should be applied to applications that fail to start.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7890","09/23/2014 15:41:23",0,"Include hamcrest-library dependency. ""We are now using hamcrest-core (as part of junit 4.11), we need to instead include hamcrest-library and exclude junit's dependency. This will let us use many fundamental matchers, like the ones regarding number comparisons (greaterThan, lessThan, etc) and make our tests clearer.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7897","09/25/2014 16:21:19",8,"Test pax-exam using bundle repository ""Create a Pax-exam version of FunctionalTestCase in order to run mule tests inside an OSGi container. Detect and report issues and things to improve""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7899","09/25/2014 16:22:14",13,"Move tests from core/spring-config/vm to the new testing framework as needed ""Add description""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7903","09/25/2014 18:10:13",8,"Fix UntilSuccessfulTestCase flaky test. ""We need to fix testSuccessfulDeliveryAckExpression and check for other flaky tests.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7907","09/29/2014 21:49:19",0,"JDBCTransaction is not closing the connection correctly ""The class org.mule.transport.jdbc.JdbcTransaction is not closing the connections in a finally block, this happens in both doCommit and doRollback methods. So, in case of an exception in the commit or rollback call the connection will remain open, and a leak could be caused. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7910","09/30/2014 15:56:52",0,"Two providers for mapping from JAX-RS to JSON ""When exposing a REST service through Jersey, if you produce JSON, the mule runtime contains two libraries that jersey may pick for mapping from POJO to JSON. jersey-json jackson-jaxrs The choice on which the framework will use is random and may vary between one environment and the other. The issue is that these libs expose different behavior and may cause unexpected side effects. I'd suggest removing either one or the other from the mule distribution, alternatively provide means of configuration for using one or the other.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7913","10/01/2014 15:56:48",0,"Scatter-gather: NPE when applying expression filter ""You get a Null Pointer Exception when applying a expression filter to a path of Scatter-Gather. The following example flow reproduces the issue, the alternative solution in the meantime is to use a choice. ""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7920","10/03/2014 18:19:50",3,"SimpleLog mode should have custom logic for locating configuration file ""OOTB, log4j2 looks for its configuration file using this algorithm: * Scan all classpath looking for file log4j2-test.xml * If not found, repeat looking for log4j2.xml When Mule is running with its default logging infrastructure, this logic is overridden so that the search is not performed on all classpath but: * First on the application classpath * If not found on the domain classpath * If not found, on the configuration folder When running in simple log mode, all of Mule's custom logic is not applied and we fallback to log4j2 default implementation, which causes issues because we cannot guarantee that any other jar in the classpath includes such a file, causing the wrong file to be picked up. When runnning in simple mode, log separation should be disabled but our custom search algorithm should still be applied. Additionally, in both cases we should generate a log line informing the path in which we found the file.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7923","10/06/2014 16:52:01",1,"Better support for sequential processing in scatter-gather ""Scatter Gather replaces the router which was deprecated in 3.5.0. However, it doesn't behave that well on sequential use cases as its predecesor. That's because if you configure a threading pool of just one, the processing is not sequential just across the routers but across all executions of the flow. Another misbehaving use case is the one in which the routes are extremely fast, like just a couple of ms each. In that case, the overall response gain is lower than the time penalty of managing the threads. To accommodate for these use cases we need to better support the sequential case of scatter gather, its threading profile type should change from asynchronousThreadingProfileType to threadingProfileType. This will enable a doThreading option which when set to false will execute always on the same thread, behaving similar to the old router. ""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7927","10/06/2014 20:03:43",8,"Add helper properties for http listener element ""Add http listener helper properties. This properties are created to simplify usability and provide extra information about the processed request.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7928","10/06/2014 20:06:11",5,"Add TLS support for HTTP listener ""Add support for SSL in new HTTP Connector.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7929","10/06/2014 20:07:28",13,"WS Consumer support for using new HTTP Connector ""Add support for the new HTTP connector in WS Consumer""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7931","10/06/2014 20:10:16",5,"HTTP Listener response streaming support ""Add support for sending streaming a response in new HTTP Connector. This implies sending Transfer-Encoding: chunck.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7932","10/06/2014 20:11:12",3,"Allow to customise protocol in new HTTP Connector ""Allow to the user to change the HTTP protocol to use in the new HTTP Connector""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7930","10/06/2014 20:54:24",5,"Validate HTTP Proxy scenario using new HTTP Connector ""Build and validate a template created with http:request and http:listener for a proxy scenario.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7938","10/06/2014 22:06:37",8,"Upgrade to latest asm version ""Upgrade to the latest version of the asm library which has no compatibility issues with the dependencies of Mule 4 and which is also compatible with whatever JDK version we choose as minimum requirement for such version of the platform""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7936","10/06/2014 22:17:07",0,"Upgrade Joda time to latest version ""Upgrade Joda time to latest available version""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7946","10/07/2014 15:30:54",5,"Remove dependencies no longer needed with JDK 1.7 ""Now that JDK 1.7 is the minimum required JDK version for running Mule, the following dependencies should not be needed anymore: * saaj-api * jaxb-api * jaxb-impl * javax.mail: (including geronimo companion) * jaxb-xjc * retrotranslator * servlet-api * geronimo-jaxrpc_1.1_spec * geronimo-ejb_2.1_spec * geronimo-j2ee-connector_1.5_spec Verify that we can indeed remove these libraries and if so go ahead and take them away from the distribution""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7947","10/07/2014 15:45:37",8,"Perform spike on upgrading XSLT support ""Perform a spike on upgrading our XSLT support by using newer libraries which provide more up to date features and performance. For this spike to be considered successful, we should not only gain in functionality and performance, but we also need to remain backwards compatible with the behaviour of Mule 3.5.x""","",0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7948","10/07/2014 15:58:34",8,"Perform spike on upgrading XPath function ""Perform a spike on upgrading our XPath support following these requirements: * Support Xpath2 * Provide a new xpath2() MEL function which behaves more consistently than its current brother and deprecates it * Can be leveraged to other transformers or elements currently present in Mule (research which ones) * Be backwards compatible with Mule 3.5.x ""","",0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7949","10/07/2014 16:04:52",3,"Upgrade Guava to the v18 ""Upgrade Guava to the latest version which at the moment of filing this issue is v18""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7950","10/07/2014 16:08:44",5,"Upgrade apache commons libraries to latest versions ""The following apache commons libraries can be upgraded. * commons-codec * commons-beanutils * commons-exec * commons-dbcp * commons-net ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7951","10/07/2014 16:11:54",8,"Upgrade test dependencies ""The following libraries are used in our test infrastructure and can be upgraded. * activemq * derby * mockito-core * xmlunit * ftpserver-core * ftplet-api * mysql-connector * postgres * jmockit (check if we really need this one) ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7954","10/07/2014 16:18:47",0,"Upgrade woodstox to the latest version ""Upgrade woodstox to the latest version which doesn't break backwards compatibility""","",0,1,0,0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7969","10/08/2014 20:42:45",8,"Add source and target attributes to the http:request element ""The http:request element should have the attributes source and target. Currently the default behavior is to read the body from the payload, and then set the payload with the body of the response. This should be configurable by setting these new attributes.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7970","10/08/2014 20:43:54",5,"Add followRedirects attribute to the http:request element ""The user should be able to configure in the request element if redirects should be followed or not, as defined in the spec for the new HTTP connector.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7971","10/09/2014 14:07:30",8,"Fix flaky test UntilSuccessfulTestCase ""org.mule.routing.UntilSuccessfulTestCase.testPermanentDeliveryFailureDLQ was ignored because it was flaky and was making build fail all the time. We need to fix flakiness and remove Ignore annotation. Also check that the rest of the test of this class are not flaky and these tests successfully pass in CI.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7972","10/09/2014 15:32:15",13,"Redesign muleContext bootstrapping in OSGi ""Current bootstrapping mechanism inspects all available jars searching for bootstrap properties files. That must be modified to work on an OSGi container. In OSGi, bootstrapping should follow white-board model so a bootstrapping service can be used (with no OSGi knowledge) which would enable test running with not container to be able to bootstrap the mule context. ""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7974","10/13/2014 21:16:45",0,"Web Service Consumer serviceAddress with MEL causes NullPointerException ""When using a ws:consumer-config with a serviceAddress containing MEL, Mule fails to start due to a NullPointerException in MuleEndpointURL.getScheme(). Example configuration: """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7976","10/15/2014 17:19:28",5,"Migrate HTTP Connector to use grizzly ""This is just to replace Netty server with Grizzly server. There is going to be a different task for properly configure grizzly server and the execution model.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7977","10/15/2014 18:42:57",1,"Add a system property to force a console appender ""Add a system property named mule.forceConsoleLog which forces a console appender if one is not already defined on the current log4j configuration. The purpose of this is to enable other products such as Studio to always have a predictable way to capture all the logs of the application regardless (and without tampering with) its configuration. This is something additive to the configuration already present for the application (if any). It doesn't altere the standard configuration selection nor log separation performed in standard mode. the mule.SimpleLog property has precedence over this property. If it is specified, then all the logic described here will not be executed.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7983","10/17/2014 15:48:32",8,"Change DevKit support module to use new http connector ""When doing OAuth with Connectors created by DevKit it's possible to define a connector-ref attribute and reference the http:connector that will listen for the OAuth callbacks. This is the way in which current Devkit connectors allow support for https on the callback. This should integrate with the new connector in the following way: * If no connector is specified, we should use the new one with a default config * If no connector is specified, but the useOldHttpTransport configuration flag is turned on, then we default to the old transport * If a connector-ref is specified, then it should show the same behaviour with either the new connector or the old transport""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7986","10/20/2014 18:56:42",8,"Make sure the new HTTP connector handles 0.0.0.0 and IP endpoints on the same port. ""MULE-7985 refers to the old transport, we need to make sure the new connector handles it too.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7987","10/22/2014 15:38:37",8,"Upgrade Saxon to 9.6.0.1-HE ""Upgrade Saxon in order to get fully compliant 2.0 and basic 3.0 support for XPath, XSLT and XQuery""","",0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7990","10/23/2014 15:15:10",5,"Create Serialization API ""Create a serialization API which replaces direct uses of SerializationUtils. This API will allow applications to specify custom serialization mechanisms.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7991","10/23/2014 15:23:06",8,"Migrate HTTP request element to use grizzly ""Currently http request element is using jetty. We need to change it to use grizzly.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7992","10/23/2014 15:27:15",3,"Change http listener response writing to do streaming ""The listener response streaming behaviour is implemented but we still need to write the grizzly response using streaming. This requires some research in grizzly to figure out how to do it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7994","10/23/2014 16:46:58",3,"Add flag to avoid parsing incoming multipart in http listener ""For proxy scenarios we need to avoid parsing multipart incoming request. This will also allow to the user to do streaming with multipart.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7996","10/23/2014 19:24:51",0,"Mule applications should clear their deployment class loader when they are disposed. ""After a mule application is disposed it's deployment class loader should be cleared so the application is ready to be redeployed if necessary. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7997","10/24/2014 15:07:17",8,"HTTP response builder is not parsed correctly within flow ""response-builder as MP is not working because of the definition parsers. The old new http transport is replacing the old transport definition parser so it's failing.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-7998","10/24/2014 15:31:05",0,"Ensure to set target namespaces on xml schemas when creating CXF endpoint server. ""XML validation schemas should have set the target namespace in order to avoid null pointer exceptions in the validation process.""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8001","10/28/2014 15:36:33",0,"XQuery transformer does not return all matches ""By default, the XQuery transformer only returns the first result, unless an array is specified in the returnClass attribute, in which case it returns all the matches in an Object[] (even if the return type was set to X[]). This means that by default, the transformer does not return all results. If the user does specify a return value, but no results were found then it returns NullPayload. If it came back with only one, then it returns that one element, even if you asked for an Array. Although this is clearly a bug and a usability pain, fixing this could break some applications which are taking this bug as a feature. Thus, the result will be: * By default, the xquery transformer will return a List * That list will contain all the results, even if only one was found * If no results found, then the list will be empty * If the user did specified a return class, then we will fallback to the current behaviour (array, one element, or null). ""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8004","10/28/2014 18:08:24",5,"Remove examples from the distribution ""Because we now have examples in Studio and the Mulesoft library, it doesn't make sense to also keep maintaining the examples on the distribution. They should be removed from the distribution and our code base. Notice that before removing them we need to make sure that: * They don't ship with any tests worth keeping (the scripting example has a couple that I'd like to move to the scripting module) * Some system tests use them. We need to make sure they remain available for those testes Keep examples folder with a README file saying that we are not shipping examples anymore (check content with Steven) Fix examples version in QA builds.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8006","10/29/2014 18:14:37",5,"Add test cases to validate Content-Type encoding and mule transformations ""We need to add test cases that validate mule transformations when receiving a request in http listener and when sending a response. Same with http requester. When Mule receives a request in http:listener, then if the user wants to transform the message to an string we need to do the transformation taking into account the Content-Type header charset (if there's one). Same when sending a response through http:listener and when using the http:request element.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8007","10/29/2014 18:25:07",3,"Fix spring-security tests. ""There are many tests using static ports in this module. We need to change them for dynamic ones to avoid flakiness.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8009","10/30/2014 21:19:04",13,"Add support for consuming wsdl files with more than 1 part ""I'm using the Web Service Consumer, and selecting a wsdl url. Anypoint Studio displays the message """"Warning: Operation Messages With More Than 1 Part Are Not Supported."""" after reloading the wsdl and selecting an operation. An extract of the wsdl is below: ... Mule only accepts this if both the """"header"""" part and the soap header is removed. The wsdl is consumed successfully by other applications, including SoapUI.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8011","11/03/2014 18:06:57",5,"Module HTTP Listener Connector Request based on path not working fine ""When you use a Wildcard to support a pattern in the PATH it's not working fine in these scenarios: For path=""""/in_wildcard/*"""" /> 1) It doesn't work consuming it with path=""""/in_wildcard/"""" 2) It doesn't work consuming it with path=""""/in_wildcard/foo1/foo2"""" (with /in_wildcard/foo1 works fine) If I have another flow in the same app with a path=""""/in_wildcard/*/subpath1"""" /> 1) It doesn't work consuming it with path=""""/in_wildcard/foo1/subpath1"""" Examples: 1) GET Method: http://localhost:8083/in_wildcard/ should return """"TestOk"""" but it doesn't work in that path (STATUS 404 No listener for endpoint: /in_wildcard/) 2) GET Method: http://localhost:8083/in_wildcard/foo1/foo2 should return """"TestOk"""" but it doesn't work in that path (STATUS 404 No listener for endpoint: /in_wildcard/foo1/foo2/) 3) GET Method: http://localhost:9001/in/in_wildcard/foo1/subpath1 should return """"TestOk123"""" but it doesn't work in that path (STATUS 404 No listener for endpoint: /in_wildcard/foo1/subpath1)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8013","11/04/2014 18:37:02",8,"Support keepAlive for persistent connections in HTTP Connector ""We need to support persistent connections, both for listener and request in the new connector.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8018","11/06/2014 11:46:51",13,"Merge http connector code cleanup and merge ""Cleanup code from the http connector module and merge it into 3.6 branch.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8019","11/06/2014 12:07:04",13,"Replace builders with a fluent API ""Replace the Builders with a fluent API at an ExtensionManager or Describer level. A mockup to take as reference (not commitment) of what we're shooting for is this: This should improve usability and reduce the complexity of our own code since now the builder implementation is part of the API"""," public Construct test() { return new DeclarationConstruct(""""ws-consumer"""", """"1.0"""").describedAs(""""Web Service Consumer"""") .withConfig(""""config"""").declaredIn(String.class) .with().requiredParameter(""""wsdl-location"""").describedAs(""""uri to find the wsdl"""").ofType(String.class).whichIsNotDynamic() .with().requiredParameter(""""service"""").describedAs(""""serviceName"""").ofType(String.class) .withConfig(""""newConnector"""") .with().requiredParameter(""""wsdl-location"""").describedAs(""""uri to find the wsdl"""").ofType(String.class).whichIsDynamic() .with().requiredParameter(""""service"""").describedAs(""""serviceName"""").ofType(String.class) .with().optionalParameter(""""connector"""").describedAs(""""The connector to use"""").ofType(Object.class).defaultingTo(null) .withOperation(""""consume"""").describedAs(""""Go get them tiger!"""") .with().requiredParameter(""""operation"""").describedAs(""""the operation to execute"""").ofType(String.class) .with().optionalParameter(""""mtomEnabled"""").describedAs(""""Whether to use mtom or not"""").ofType(boolean.class); } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8020","11/06/2014 12:09:17",1,"Remove prefixes from ext-api core classes ""Remove the """"Extension"""" prefix from classes such as ExtensionConfiguration, ExtensionParameter, ExtensionOperation, etc""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8021","11/06/2014 12:26:14",1,"Remove minMuleVersion restricition from extensions API ""In the future, we'll shoot for letting the runtime should decide this based on the extensions metadata""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8022","11/06/2014 12:27:38",1,"Remove the api subpackage in the extensions API ""Extensions API will be beta during the whole 3.x series, so it shouldn't have the api keyword on its packages. When we move to Mule 4, extensions API will be an OSGi bundle so the whole api classification makes no sense anymore""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8023","11/06/2014 12:31:19",2,"Reduce the amount of DataTypeQualifiers ""We need less DataTypeQualifiers than we're actually supporting. The following should be removed: * Stream * Void The following should be collapsed: * short / int * DATE / DATE_TIME""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8024","11/06/2014 12:34:00",2,"Enable registration of top level pojos ""Enable registering pojos as top level elements. The logic to do this is already done, all that's missing is the namespacehandler for it and testing""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8025","11/06/2014 12:35:38",1,"Forbid one same class to define both configurations and operations ""Configurations and operations have to be defined in separate classes.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8026","11/06/2014 12:50:18",5,"Replace current extensions discoverer with OSGish activator class ""In order to be aligned with Mule's OSGified future, replace the current discovery model with something of this sort: public class MyActivator implements ExtensionActivator { public void init(Manager mgr) { fluentApi.stuff(); } } } The activator is to be discovered through standard java SPI""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8030","11/06/2014 15:01:56",3,"TransactionNotification should return the name of the application that triggered it ""When the Agent receives a transaction Notification there is no way to know the name of the application ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8034","11/10/2014 20:58:29",5,"Uri Parameters should appear decoded in the inboundProperties ""When a Uri paramter is sent with an encoded character it doesn't appear decoded in the inboundProperties (http.uri.params) . Example: http://localhost:9000/resource/value 01/ (value"""" """"01 = space between value and 01) it will be send encoded to http://localhost:9000/resource/value%2001/ or http://localhost:9000/resource/value+01/ But it has to appear in the http.uri.params as """"value 01"""" not as """"value+01"""" when i obtain the """"resource_param"""".""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8038","11/12/2014 02:39:07",8,"HTTP Module configured as proxy duplicate messages ""Seems that new http connector configured for proxy scenario is sending more request to the client server than expected. See test case HttpProxyTemplateTestCase,proxyStreaming,""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8039","11/12/2014 02:50:37",8,"Add behaviour to send a flow message source response asynchronously ""Currently we can process a message through MessageProcessingManager but the processing is done all synchronous. We need, for the new http module, to add support to send the http response asynchronously. The only change required so far is a new FlowProcessingPhase with support for asynchronous dispatching of the response message.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8040","11/12/2014 15:52:01",1,"Remove the concept of input and output types from an extension operation ""Remove the concept of input and output types from an extension operation""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8044","11/14/2014 17:23:01",8,"Http Listener fail to send response after receiving a big payload with transfer-encoding chunk ""When sending a big payload with transfer-encoding chunk to an http listener, then the listener fails to send the response. See org.mule.module.http.functional.listener.HttpListenerRequestStreamingTestCase .""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8047","11/17/2014 00:44:47",5,"Support shared http listener and request config in domains ""We need to be able to shared http:listener-config and http:request-config betweens applications using domains.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8051","11/17/2014 08:52:39",8,"Scatter-Gather: Custom Aggregation Strategy - AggregationContext gives wrong events when exceptions occur ""When implementing a custom aggregation strategy (as a Java class) as in the documentation: http://www.mulesoft.org/documentation/display/current/Scatter-Gather , section Complete Code Example there seems to be an issue with messages that throw exceptions. It seems that the method collectEventsWithExceptions() from AggregationContext gives the event(s) as they were before entering the Scatter-Gather. So it is basically impossible to get the message(s) that actually caused the exception. collectEventsWithoutExceptions() - works as expected""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8052","11/17/2014 17:54:30",5,"New HTTP Module Request not encode values in the path attribute ""In the new HTTP Request Module when you use a path that have chars that need to be encoded it doesn't produce an URI with the values encoded. For example: The PATH in this case has to be encoded and arrive to the listener server as """"/out%201"""" ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8054","11/17/2014 19:00:59",0,"Exception trying to close a not opened IMAP folder ""Since we are closing the folder without checking if it is open first, a lot of exceptions are cluttering the logs.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8061","11/19/2014 13:20:24",8,"Remove duplicate message creation from test cases. ""After MULE-8028 there are several test cases duplicating code to for mule message creation. we should add a method in our test infrastructure and reuse that.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8063","11/19/2014 17:26:40",0,"Replace configuration attribute useHttpTransportByDefault with a configuration extension ""As part of the review of MULE-8028 we found that using a configuration element's attribute to disable/enable the usage of the HTTP transport is not correct. To be able to configure this attribute a new configuration extension for HTTP should be added.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8065","11/19/2014 17:53:17",5,"Change DefaultHttpRequester to receive a Configuration object instead of separated attributes for each configuration value ""In HTTP connector, there is a HttpRequesterBuilder#setOperationConfig(HttpRequestOptions) method which is used to configure a DefaultHttpRequester instance. That configuration is done invoking every property setter in DefaultHttpRequester. DefaultHttpRequester must accept a HttpRequestOptions instead of having properties for each configurable value to reduce code duplication and make the code more simple ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8067","11/19/2014 18:08:12",13,"Decouple the extension-api from the concept of declaring or acting classes ""Currently, the Extension, Configuration and Operation interfaces have the concept of declaring or acting classes. This ties the API to the traditional implementation model of annotated classes, which might not always be the case. Decouple that by introducing two new interfaces: ConfigurationIntantiator and OperationImplementation""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8068","11/19/2014 18:19:18",2,"Add tests to verify that extension api parsers support place holders ""In the tests that validate the parsing of configurations and operations through XML, validate that property placeholders are correclty resolved""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8069","11/19/2014 18:25:34",8,"Define a richer set of expression aware XSD types ""Now that the extensions api is going to make the parsing of expressions easier and enabled by default on every component, we should define new XSD types which bette reflect the expected return types. For example: * expressionSubstitutableString * expressionSubstitutableInt * etc Things to discuss and define: * Do we always allow embedded expressions? * is """"#[foo] """" a valid expression? ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8070","11/19/2014 18:35:01",3,"Jersey fails to retrieve cookie when running with new http module. ""Jersey fails to retrieve cookie when running with new http module. See org.mule.module.jersey.JerseyCookiePropagationTestCase""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8072","11/19/2014 19:45:31",3,"Http Requester returns 200 instead of the actual request status code. ""On the proxy scenario, when the proxied service is unavailable a 500 response should be received, instead it is responding with """"200 Internal Server Error"""" which doesn't respect the http protocol. Steps to reproduce: - Deploy application. - Make sure there is no service being proxy. - Hit the endpoint. - A response containing the status """"200 Internal Server Error"""" will be shown. Expected behaviour: The requester and proxy escenario should reply with the same status code and message.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8074","11/20/2014 12:05:51",8,"Fix flaky test AuthorizationCodeMinimalConfigTestCase ""Fix flaky test AuthorizationCodeMinimalConfigTestCase. Failure is: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:152) at java.net.SocketInputStream.read(SocketInputStream.java:122) at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:136) at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:152) at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:270) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:140) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:260) at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:161) at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:153) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:271) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:254) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) at org.apache.http.client.fluent.Request.execute(Request.java:143) at org.mule.module.oauth2.internal.authorizationcode.functional.AuthorizationCodeMinimalConfigTestCase.hitRedirectUrlAndGetToken(AuthorizationCodeMinimalConfigTestCase.java:29) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at com.github.tomakehurst.wiremock.junit.WireMockRule$1.evaluate(WireMockRule.java:74) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8079","11/20/2014 18:16:56",3,"Cast exception on the proxy http scenario. ""When running the Proxy scenario of the http module, a very small percentage of the requests fails with the shown exception.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8081","11/21/2014 17:25:54",0,"CheckRequiredAttributes#preProcess performance improvement ""CheckRequiredAttributes#preProcess evaluates every defined attribute group to see if the element matches each of them. This is not required we need to know if at least one of them matches. Avoiding this redundant check will slightly reduce the time needed to parse a mule configuration file.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8082","11/21/2014 18:08:35",0,"Upgrade XStream to version 1.4.7 ""Upgrade XStream to version 1.4.7""","",0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8083","11/21/2014 21:45:25",0,"JXPath Evaluator is vulnerable to XXE ""JXPathExpressionEvaluator includes: XMLUtils.toW3cDocument does not disable external entities, so the message payload could include an XXE attack. We need to apply there the same fix as in MULE-7390"""," document = XMLUtils.toW3cDocument(message.getPayload()); ",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8086","11/25/2014 17:18:04",5,"File handlers are not closed after a Queue is disposed ""Per the Queue contract, when a queue is disposed all its storage is to be freed and the resources released. However, it is only clearing the storage but the file handlers remain open. I have verified that the number of files in the queuestore directory in .mule/ grows constantly. Checked with lsof -p Code is in github at https://github.com/mulesoft-consulting/ucso-api-manager.git ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8089","11/26/2014 14:19:26",8,"Wrong attributes for TLS in OAuth config ""Attributes requestConfig and listenerConfig were not removed from the OAuth authorization grant types. We need to use tlsContext-ref instead.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8092","11/26/2014 16:01:24",1,"Email address dev@mule.codehaus.org bounces back in ""WARN org.mule.DefaultMuleMessage: setProperty(key, value) called with null value"" ""Using a message enricher to extract a non-existent property from the current payload and assign it to a flow variable causes the following warning. It has been reported that an email to the given address dev@mule.codehaus.org just bounced back. Please correct the email address, or remove the stack trace (which makes it look much worse than a warning), or remove the message from being logged in this situation altogether. WARN 2014-11-14 16:07:37,292 [[].httpc.receiver.04] org.mule.DefaultMuleMessage: setProperty(key, value) called with null value; removing key: ; please report the following stack trace to dev@mule.codehaus.org java.lang.Throwable at org.mule.DefaultMuleMessage.setProperty(DefaultMuleMessage.java:470) at org.mule.el.context.MessagePropertyMapContext.put(MessagePropertyMapContext.java:49) at org.mule.el.context.MessagePropertyMapContext.put(MessagePropertyMapContext.java:17) at org.mule.mvel2.optimizers.impl.refl.nodes.MapAccessor.setValue(MapAccessor.java:52) at org.mule.mvel2.optimizers.impl.refl.nodes.VariableAccessor.setValue(VariableAccessor.java:46) at org.mule.mvel2.compiler.CompiledAccExpression.setValue(CompiledAccExpression.java:59) at org.mule.mvel2.ast.DeepAssignmentNode.getReducedValueAccelerated(DeepAssignmentNode.java:92) at org.mule.mvel2.MVELRuntime.execute(MVELRuntime.java:86) at org.mule.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) at org.mule.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) at org.mule.mvel2.MVEL.executeExpression(MVEL.java:943) at org.mule.el.mvel.MVELExpressionExecutor.execute(MVELExpressionExecutor.java:72) at org.mule.el.mvel.MVELExpressionLanguage.evaluateInternal(MVELExpressionLanguage.java:198) at org.mule.el.mvel.MVELExpressionLanguage.evaluate(MVELExpressionLanguage.java:183) at org.mule.expression.DefaultExpressionManager.enrich(DefaultExpressionManager.java:244) at org.mule.enricher.MessageEnricher.enrich(MessageEnricher.java:112) at org.mule.enricher.MessageEnricher.process(MessageEnricher.java:78) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:94) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:67) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.doProcess(InterceptingChainLifecycleWrapper.java:50) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:67) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.access$001(InterceptingChainLifecycleWrapper.java:22) at org.mule.processor.chain.InterceptingChainLifecycleWrapper$1.process(InterceptingChainLifecycleWrapper.java:66) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.process(InterceptingChainLifecycleWrapper.java:61) at org.mule.routing.AbstractSelectiveRouter.processEventWithProcessor(AbstractSelectiveRouter.java:308) at org.mule.routing.AbstractSelectiveRouter.routeWithProcessors(AbstractSelectiveRouter.java:298) at org.mule.routing.AbstractSelectiveRouter.routeWithProcessor(AbstractSelectiveRouter.java:288) at org.mule.routing.AbstractSelectiveRouter.process(AbstractSelectiveRouter.java:203) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:94) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:67) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.AbstractInterceptingMessageProcessorBase.processNext(AbstractInterceptingMessageProcessorBase.java:102) at org.mule.construct.DynamicPipelineMessageProcessor.process(DynamicPipelineMessageProcessor.java:54) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:94) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:67) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.AbstractInterceptingMessageProcessorBase.processNext(AbstractInterceptingMessageProcessorBase.java:102) at org.mule.interceptor.AbstractEnvelopeInterceptor.process(AbstractEnvelopeInterceptor.java:51) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.AbstractInterceptingMessageProcessorBase.processNext(AbstractInterceptingMessageProcessorBase.java:102) at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:40) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.AbstractInterceptingMessageProcessorBase.processNext(AbstractInterceptingMessageProcessorBase.java:102) at org.mule.construct.AbstractPipeline$1.process(AbstractPipeline.java:109) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:94) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:67) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.doProcess(InterceptingChainLifecycleWrapper.java:50) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:67) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.access$001(InterceptingChainLifecycleWrapper.java:22) at org.mule.processor.chain.InterceptingChainLifecycleWrapper$1.process(InterceptingChainLifecycleWrapper.java:66) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.process(InterceptingChainLifecycleWrapper.java:61) at org.mule.construct.AbstractPipeline$3.process(AbstractPipeline.java:207) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.chain.SimpleMessageProcessorChain.doProcess(SimpleMessageProcessorChain.java:43) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:67) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.doProcess(InterceptingChainLifecycleWrapper.java:50) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:67) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.access$001(InterceptingChainLifecycleWrapper.java:22) at org.mule.processor.chain.InterceptingChainLifecycleWrapper$1.process(InterceptingChainLifecycleWrapper.java:66) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.process(InterceptingChainLifecycleWrapper.java:61) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.chain.SimpleMessageProcessorChain.doProcess(SimpleMessageProcessorChain.java:43) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:67) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.doProcess(InterceptingChainLifecycleWrapper.java:50) at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:67) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.access$001(InterceptingChainLifecycleWrapper.java:22) at org.mule.processor.chain.InterceptingChainLifecycleWrapper$1.process(InterceptingChainLifecycleWrapper.java:66) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:24) at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:58) at org.mule.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:44) at org.mule.processor.chain.InterceptingChainLifecycleWrapper.process(InterceptingChainLifecycleWrapper.java:61) at org.mule.transport.AbstractMessageReceiver.routeEvent(AbstractMessageReceiver.java:511) at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:226) at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:208) at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:200) at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:187) at org.mule.transport.http.HttpMessageReceiver$7$1.process(HttpMessageReceiver.java:483) at org.mule.transport.http.HttpMessageReceiver$7$1.process(HttpMessageReceiver.java:480) at org.mule.execution.ExecuteCallbackInterceptor.execute(ExecuteCallbackInterceptor.java:16) at org.mule.execution.HandleExceptionInterceptor.execute(HandleExceptionInterceptor.java:30) at org.mule.execution.HandleExceptionInterceptor.execute(HandleExceptionInterceptor.java:14) at org.mule.execution.BeginAndResolveTransactionInterceptor.execute(BeginAndResolveTransactionInterceptor.java:54) at org.mule.execution.ResolvePreviousTransactionInterceptor.execute(ResolvePreviousTransactionInterceptor.java:44) at org.mule.execution.SuspendXaTransactionInterceptor.execute(SuspendXaTransactionInterceptor.java:50) at org.mule.execution.ValidateTransactionalStateInterceptor.execute(ValidateTransactionalStateInterceptor.java:40) at org.mule.execution.IsolateCurrentTransactionInterceptor.execute(IsolateCurrentTransactionInterceptor.java:41) at org.mule.execution.ExternalTransactionInterceptor.execute(ExternalTransactionInterceptor.java:48) at org.mule.execution.RethrowExceptionInterceptor.execute(RethrowExceptionInterceptor.java:28) at org.mule.execution.RethrowExceptionInterceptor.execute(RethrowExceptionInterceptor.java:13) at org.mule.execution.TransactionalErrorHandlingExecutionTemplate.execute(TransactionalErrorHandlingExecutionTemplate.java:109) at org.mule.execution.TransactionalErrorHandlingExecutionTemplate.execute(TransactionalErrorHandlingExecutionTemplate.java:30) at org.mule.transport.http.HttpMessageReceiver$7.process(HttpMessageReceiver.java:479) at org.mule.transport.http.HttpMessageReceiver$7.process(HttpMessageReceiver.java:475) at org.mule.transport.http.ThrottlingExecutionTemplate.execute(ThrottlingExecutionTemplate.java:91) at org.mule.transport.http.HttpMessageReceiver.routeHttpRequest(HttpMessageReceiver.java:474) at org.mule.transport.http.HttpMessageReceiver.routeRequest(HttpMessageReceiver.java:415) at org.mule.transport.http.HttpMessageReceiverRouterWorker.run(HttpMessageReceiverRouterWorker.java:31) at org.mule.transport.TrackingWorkManager$TrackeableWork.run(TrackingWorkManager.java:267) at org.mule.work.WorkerContext.run(WorkerContext.java:286) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8094","11/26/2014 18:01:39",5,"HTTP Listener with Basic Auth should return status code 401 when authentication fails ""When using the Basic-Auth with the new Module Http Listener it returns a 500 status code but it would be better to return a 401 like the old http does. Example: In the first flow (listenerBasicAuth) using the tag: - or - after the listener it returns a 500 in an invalid authentication. But with the old HTTP, in the second flow (""""httpInboundBasicAuth"""") it returns a 401. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8095","11/26/2014 19:13:47",0,"Managed object store expiration incorrectly detected on cluster ""Managed object store defines an entre Time to Live (TTL) in order to determine if a given entry must be removed form the stored during the expiring process. In oder to to that, each entry contains a timestamp which is compared against the current time and the configured TTL. That the timestamp is calculated using System.nanoTime. The problem is that System.nanoTime can only be used to measure elapsed time and is not related to any other notion of system or wall-clock time. This implies that the returned values are only meaningful inside a given JVM, but we can't compare timestamps generated on different machines.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8097","11/27/2014 13:42:23",3,"Hot spot in ServerAddress of HTTP Connector ""When ServerAddress executes: this.ip = InetAddress.getByName(host).getHostAddress(); It's take a while to return. We need to improve it since it's used with every request.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8099","11/27/2014 21:15:15",0,"Domains should not allow Mule elements nested in a element ""For security and consistency reasons, domains should not allow Mule elements nested in a element""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8101","11/28/2014 14:56:08",8,"HTTP requester not sending query parameters when processing a redirect under HTTPS ""Check the behavior of redirects in the http:request element of the new HTTP module when using HTTPS. If the Location header contains a URL with query parameters, the request to that URL doesn't contain the parameters. To reproduce, check AuthorizationCodeFullConfigTestCase#localAuthorizationUrlRedirectsToOAuthAuthorizationUrl. MuleClient is being used twice, to manually process redirects, replace that with only one call with enabled redirects.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8102","11/28/2014 15:32:42",1,"Upgrade schema versions to 3.6 ""Upgrade schema versions to 3.6""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8104","12/01/2014 15:17:18",3,"HTTP Requester not removing previous inbound properties ""The http:request sets inbound properties to the resulting Mule message but keeps any previous inbound property that were set before the request. To reproduce, test the proxy scenario using a flow with an http:listener and an http:request. When returning from the request, the Mule message still has inbound properties from the listener.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8106","12/02/2014 13:58:12",3,"TCP Transport creating MULE_REMOTE_CLIENT_ADDRESS as outbound ""While working on STUDIO-5148, the team found that TCP is creating the MULE_REMOTE_CLIENT_ADDRESS as outbound property rather than inbound as per our way to adapt messages and the way we set that property everywhere else. https://github.com/mulesoft/mule/blob/bfb3a17263d1e4b32ee10272cbf710a2bf41b16b/transports/tcp/src/main/java/org/mule/transport/tcp/TcpMessageReceiver.java#L421 ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8107","12/02/2014 15:30:14",3,"Default maxThreads is 128 when worker-threading-profile isn't present but 16 when it is. ""As title..""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8110","12/02/2014 16:00:02",3,"Http Listener Module Path Issue with path with wildcard and another hardcoded in the same port and with spaces in the path ""When there are two listeners in the same port but one has a wildcard the other has a hardcoded path and there is a collision between them it has to enter in the listener that has the hardcoded path. For example: 1) Flow with path = """"/in"""" and another flow with path = """"/in/* """" It enters in the /in/* listener but it should enter in the """"/in"""" without wildcard 2) path=""""/in/*/subpath1"""" path=/in/* When you consume it with """"/in/foo1/subpath1"""" it goes to the path /in/* 3) Similar to the previous case. path=""""/in/*/subpath1/*"""" and Path=/in/* When you consume it with """"/in/foo1/subpath1/subpath2"""" it goes with the /in/* 4) path=""""/encodedValues/foo 1"""" and you consume it with /encodedValues/foo%201 it returns a 404. For all of these cases there are Functional Test Cases inside the System folder of the HTTP module tests: *HttpListenerPathTestCase ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8112","12/02/2014 18:26:01",1,"ArrayIndexOutOfBoundsException when logging exceptions ""Sometimes, when logging an exception with a RollingFileAppender an ArrayIndexOutOfBoundsException is thrown. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8113","12/02/2014 19:43:13",1,"Tests Infrastructure modules build warning ""When running mvn validate on mule-tests-infrastructure module I get a warning because there is a duplicated declaration of maven-jar-plugin in mule pom.xml. """," [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.mule.tests:mule-tests-infrastructure:jar:3.7.0-M1-SNAPSHOT [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.apache.maven.plugins:maven-jar-plugin @ org.mule:mule:3.7.0-M1-SNAPSHOT, /Users/alejandrosequeira/dev/mule/ce/pom.xml, line 1803, column 21 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] [INFO] [INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Mule Tests Infrastructure 3.7.0-M1-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-maven-version) @ mule-tests-infrastructure --- [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1.269 s [INFO] Finished at: 2014-12-02T16:40:14-03:00 [INFO] Final Memory: 9M/246M [INFO] ------------------------------------------------------------------------ ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8116","12/03/2014 14:15:55",3,"Error in the XML Parser of the HTTP Module when the Header tag is used with the Error Response Builder ""This exception is throw when there is an Error Response Builder: """"nested exception is java.lang.IllegalStateException: No parser defined for header in the context error-response-builder""""""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8117","12/03/2014 16:58:44",3,"StringIndexOutOfBoundsException when requester receives GET with wrong body ""When sending a GET with content-type application/x-www-form-urlencoded and an incorrect form body it returns an empty response due to a java.lang.StringIndexOutOfBoundsException. To reproduce run the following command using the configuration: """," $curl -G --data 'hello' http://localhost:8080/1 curl: (52) Empty reply from server ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8122","12/03/2014 20:41:21",0,"Negative seek offset after queue file goes trough transaction recovery process ""After an ungraceful shutdown of an application doing intensive use of durable transactional queues, the recovery process appends recovered records at the beginning of the queue and not at the end as it is expected to. As a result, the entries index created by RandomAccessFileQueueStore is corrupted and the file can't be read.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8123","12/03/2014 21:24:46",5,"Jetty http.context.path inbound property has a different value in 3.6 compared to 3.5 ""The jetty transport in 3.6.0-M3 is setting the http.context.path inbound property to a different value than 3.5 given the following endpoint address and request: endpoint address: http://localhost:8080/api request: http://localhost:8080/api/console/index.html in 3.6 we get: http.context.path: /api/console/index.html and in 3.5 the value was: http.context.path: /api the 3.5 behavior is the expected one. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8124","12/03/2014 21:30:18",3,"Resource Not Found in HTTP should return a body with a clear message ""HTTP Module returns 404 when a valid port is hit but there's no listener in it.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8127","12/04/2014 14:25:49",5,"HTTP Listener Module is not adding the WWW-Authenticate header field in the response ""When you send bad basic credentials for authentication the response of the listener is not adding the WWW-Authenticate header field. But in the case you don't send the authentication header credential it includes the WWW-Authenticate header field. As I understand in the RFC (http://tools.ietf.org/html/rfc2616#section-10.4.2) the server has to add the WWW-Authenticate header field in both scenarios. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8129","12/04/2014 15:07:55",3,"HTTP Listener config throws NPE when a request is received but no listener is referencing the config ""When no listener is referencing a listener-config, and a request is received in the configured port, a NPE is thrown in the server. To reproduce, add this listener-config: Run the app, and then hit with a browser http://localhost:1234""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8132","12/05/2014 15:25:40",2,"HTTP listener not setting exception payload. ""There's a scenario in CXF where an exception is thrown after calling an HTTP listener. An exception payload is expected but you get null. Test is testServerClientProxyDefaultException and can be found in ExceptionStrategyTestCase.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8133","12/05/2014 19:02:45",3,"Log separation doesn't work after upgrading to log4j 2.1 ""Because of a change in Log4j's lifecycle, after upgrading to 2.1 the application logs never load their configuration which in practice means that log separation is disabled even though applications do have a separate logging context.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8134","12/05/2014 21:00:24",3,"JUL loggers are not bridged to log4j2 ""Components like jersey and Grizzly are logging using JUL but that API is not bridged to log4j2. JUL loggers should have the same treatment as the others do""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8136","12/08/2014 14:30:15",0,"SERVER_ACCEPT IOEvents should not be processed using ThreadPoolExecutor ""The custom IOStrategy being used in the http module (ExecutorPerServerAddressIOStrategy) is causing server_accept IO events to be processed in a worker thread. This is not ideal, and not what the Grizzly implementatio do either.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8142","12/10/2014 18:44:26",8,"HTTP Listener is storing only the first part of a MultiPart request as attachment ""given the following request using RestAssured: only the first part (""""description"""") is being stored as an inboundAttachment. Using http:inbound instead of listener generates both attachments as expected. failing test using listener: https://github.com/mulesoft/apikit/blob/http-3.6/mule-module-apikit/src/test/java/org/mule/module/apikit/leagues/LeaguesHttpListenerTestCase.java passing test using endpoint: https://github.com/mulesoft/apikit/blob/http-3.6/mule-module-apikit/src/test/java/org/mule/module/apikit/leagues/LeaguesTestCase.java in both classes the test in question is putMultiPartFormData()"""," given() .multiPart(""""description"""", """"Barcelona Badge"""") .multiPart(""""image"""", """"bbva.jpg"""", this.getClass().getClassLoader().getResourceAsStream(""""org/mule/module/apikit/leagues/bbva.jpg"""")) .expect() .statusCode(200) .body(""""upload"""", is(""""OK"""")) .when() .put(""""/api/leagues/liga-bbva/badge""""); ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8146","12/11/2014 13:57:08",8,"Grizzly thread leaks ""When running the CE test suite, you can see grizzly threads piling up to the point in which by the time the suite is almost over there's a gigantic amount of idle threads. This leads to flakiness and in some environments it even fails the build because the host can't allocate more threads. Additionally, it raises the concern about those threads being actually stopped when an application is undeployed on a live container. Please trace and fix the leak and verify that those threads do not survive an application undeployment.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8147","12/11/2014 17:04:51",13,"Support doc/literal with multiple message parts in ws consumer ""WS Consumer should support doc/literal web services that have multiple message parts inside them. Note: since WS consumer sets the payload to the body of the SOAP message, this means that it will have to have a wrapper element around the message parts.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8148","12/11/2014 17:07:28",8,"WS Encryption support for WS Consumer ""We should support WS Security encryption/decryption capabilities in WS consumer.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8149","12/11/2014 17:08:01",8,"WS Security Signature support for WS consumer ""We should support WS Security signature and verification capabilities in WS consumer.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8150","12/11/2014 20:19:23",8,"HTTP Connector OAuth Implicit Credentials ""Need to support OAuth implicit credentials for new HTTP connector.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8151","12/11/2014 20:25:09",5,"Malformed responses when Jersey sends a chuncked response ""When a Jersey endpoint responds with a chuncked response, then the chunks are not correctly formed and the last one is not correctly finialized. As a result, the response is garbled. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8156","12/15/2014 19:08:08",13,"Create examples for HTTP module documentation ""Create exmaples to include in documentation for new HTTP Module.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8159","12/16/2014 18:29:24",5,"java.lang.IllegalStateException: Only owner thread can write to message still occures with http module "".""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8160","12/16/2014 18:32:07",8,"100% errors with http listener under high concurrency ""100% Failures at 8000 concurrency. Http transport only has 0.32% failures, and jetty none.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8162","12/17/2014 15:22:17",5,"HTTP listener fails with NPE when the message is filtered out ""The following config is failing with NPE. It doesn't fail when the message is not filtered out. Error: java.lang.NullPointerException at org.mule.module.http.internal.listener.HttpResponseBuilder.build(HttpResponseBuilder.java:77) ~[mule-module-http-3.6.0-M3-SNAPSHOT.jar:3.6.0-M3-SNAPSHOT] at org.mule.module.http.internal.listener.HttpMessageProcessorTemplate.sendResponseToClient(HttpMessageProcessorTemplate.java:87) ~[mule-module-http-3.6.0-M3-SNAPSHOT.jar:3.6.0-M3-SNAPSHOT] at org.mule.execution.AsyncResponseFlowProcessingPhase.runPhase(AsyncResponseFlowProcessingPhase.java:56) ~[mule-core-3.6.0-M3-SNAPSHOT.jar:3.6.0-M3-SNAPSHOT] at org.mule.execution.AsyncResponseFlowProcessingPhase.runPhase(AsyncResponseFlowProcessingPhase.java:23) ~[mule-core-3.6.0-M3-SNAPSHOT.jar:3.6.0-M3-SNAPSHOT]""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8163","12/17/2014 19:05:25",8,"Requests randomly fail (1 in 1M) with NPE, even at low conconcurrencies e.g. 50 ""Around 10 times in a million requests, the request fails due a null pointer exception caused by the future returning null instead of a valid response. Class and line: org.mule.module.http.internal.request.grizzly.GrizzlyHttpClient#send response = future.get(responseTimeout, TimeUnit.MILLISECONDS); ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8165","12/18/2014 16:06:47",13,"Spike on execution model of extensions api ""Make it execute operations""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8166","12/18/2014 16:13:46",13,"Make a Spike on consolidating all mule registries into a Spring one ""Make a Spike on consolidating all mule registries into a Spring one""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8167","12/18/2014 17:15:56",1,"Remove byte as a DataQualifier ""Remove it""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8170","12/18/2014 17:34:55",8,"Redesign context builder discovery for OSGi ""Current context builder discovery mechanism inspects all available jars searching for service properties files. That must be modified to work on an OSGi container. In OSGi, transport discovery should follow white-board model so a context builder service can be used (with no OSGi knowledge) which would enable test running with not container to be able to properly create the mule context.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8172","12/18/2014 18:52:20",8,"Cannot log to application log for a failed deployment ""Install latest snapshot (build c22fb549), create an application with the attached config and start using bin/mule -M-Dmule.agent.enabled=false. Deployment fails as expected but there is a problem when trying to log to application log. See attached log.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8173","12/19/2014 13:34:09",5,"Add protocol attribute to listener-config and request-config to improve usability ""Currently is difficult for an user to realice how to configure HTTPS for listening HTTP requests or sending HTTP requests. The way to do that currently is by defining a TLS Context element (which can be empty for sending request, in such case it will use jvm default certificatess) inside the listener-config or de request-config element. That it's not straightforward if the user is working with XML and for users that do not know that SSL / TLS is the protocol behing HTTPS isn't either despite they use Studio. The idea is to add a protocol attribute (with default value HTTP) in the listener-config and the request-config. - Listener config: - if user sets protocol=""""http"""" or provides no values then we validate that the user didn't put a TlsContext. - If user sets protocol=""""https"""" we validate that the user provided a TlsContext with at least a keystore configured on it. - Request config: - if user sets protocol=""""http"""" or provides no value then we validate that the user didn't put a TlsContext - if user sets protocol=""""https"""" and provides no TlsContext config then we create a TlsContext by default (implicitly) using the default jvm certificates - if http is selected, port 80 is used by default - if https is selected, port 443 is used by default The usability improvements is: From Studio the user has a much more easy way to find where to define the use of HTTPS since it's going to be in the main configuration section of both listener-config and request-config From XML the user will see a hint from the XML content assistant to pick the protocol right in the listener-config element or request-config element. With the new behaviour there's no reason to support an empty tls:context element in the config. When we rebuild the current TCP transport ideally we can reuse the same mechanism as in HTTP (no idea what the """"protocol"""" attribute would be called in that case) or add support for an empty tls:context again. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8176","12/22/2014 14:04:31",5,"Deprecate HTTP transport ""Deprecate XML elements of the HTTP transport.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8177","12/22/2014 17:28:05",3,"HttpListener ParameterMap should behave as a Map ""ParameterMap is a Map and holds the values of query parameters, uri parameters and POST params. The problem that currently have are: - The parameter map is mutable when it should't - It does not have an API in the interface that can be used by the user (there's an special method getAll used when a parameter returns a collection of values) - it does not comply with the Map interface for Map as it declares. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8178","12/22/2014 18:06:59",3,"Default HTTPS configuration in requester not working correctly ""The protocol=""""HTTPS"""" configuration in the request-config is ignored if there is no default TLS context factory in the registry.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8199","12/23/2014 03:41:11",8,"Remove Maven warnings ""We recently had an [issue|MULE-8113] with our Maven build, it wasn't including a dependency. When doing a little research I found that it was because a duplicated declaration of maven-jar-plugin. This root problem didn't appear when building the module, but when building an ancestor (distance 2). To avoid this kind of issues we must ensure that we don't have Maven warning in our builds.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8180","12/29/2014 16:07:13",5,"HTTP Listener fails during initialization inside batch ""When adding an http:listener inside the input of a batch job then the app fails during startup. Seems that DefaultBatchEngine is asking for all the batch jobs during initialization, then the batch job manually executes initialize and injection over the input elements (http:listener) but at this point the HttpListenerConnectionManager has not bean registered (using registry bootstrap) so there's a null pointer during listener initialization. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8181","12/29/2014 17:21:26",8,"Problem sending outbound attachments in HTTP requester ""When sending a multipart request, the requester assumes that each part is a file, and adds the corresponding headers (filename attribute at the beginning of the part, transfer-encoding: binary, etc). This makes the request to be invalid in some cases. Use case to test: upload a file to Box. Example test (replace the dev token and the parent folder id): The requester sends a multipart request with the following format. POST /api/2.0/files/content HTTP/1.1 Host: localhost:8082 Authorization: Bearer xxxxxxxxxx MULE_ENCODING: UTF-8 Connection: keep-alive Accept: */* User-Agent: NING/1.0 Content-Type: multipart/form-data; boundary=Tdv259AB4D2JOrezEkOphg5Ikreks3mIO2jC Content-Length: 463 --Tdv259AB4D2JOrezEkOphg5Ikreks3mIO2jC Content-Disposition: form-data; name=""""attributes""""; filename=""""attributes"""" Content-Type: application/json Content-Transfer-Encoding: binary {""""name"""":""""test.txt"""", """"parent"""":{""""id"""":""""12345678""""}} --Tdv259AB4D2JOrezEkOphg5Ikreks3mIO2jC Content-Disposition: form-data; name=""""test.txt""""; filename=""""test.txt"""" Content-Type: text/plain Content-Transfer-Encoding: binary Test content --Tdv259AB4D2JOrezEkOphg5Ikreks3mIO2jC-- The problem is the """"attributes"""" part, which is sent as a file part. It shouldn't contain the filename attribute, and the transfer encoding shouldn't be binary. Postman just sends the following, and it works correctly: Content-Disposition: form-data; name=""""attributes"""" {""""name"""":""""test.txt"""", """"parent"""":{""""id"""":""""12345678""""}} ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8184","12/29/2014 20:19:12",5,"HTTP Listener Server should return Method not supported ""When there's at least one HTTP listener for a uri but the listeners for that uri do not support a given method an status code 405 Method Not Allowed should be return. Currently it's returning 404.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8185","12/29/2014 22:37:43",3,"Change the AsyncCompletionHandler in the HTTP requester to use a static logger ""The AsyncCompletionHandler used by AHC in the HTTP requester uses a logger that is stored in an instance variable. Change it to use a class variable, to avoid loading the logger from the logger factory each time a request is sent (an AsyncCompletionHandler is created for each request).""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8188","12/30/2014 14:58:26",3,"Mule starts when a request element has host/port undefined, only failing when request is used. ""This should fail at startup, not in runtime.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8189","12/30/2014 15:02:36",3,"Improve HTTP listener logging for usability ""Mule does not log to show what host/port/path Mule listening on. This is important for understanding what might be going on when things aren't working as expected, and existed with the existing http transport. Also, error/logs related to listeners not being available should take into account """"allowedMethods"""" otherwise errors like this which make no sense occur: """," WARN 2014-12-30 10:01:46,424 [[http-module-echo].HTTP_Listener_Configuration.worker.01] org.mule.module.http.internal.listener.HttpListenerRegistry: No listener found for request: / WARN 2014-12-30 10:01:46,424 [[http-module-echo].HTTP_Listener_Configuration.worker.01] org.mule.module.http.internal.listener.HttpListenerRegistry: Available listeners are: [/] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8192","12/30/2014 20:20:15",0,"Outbound endpoints should be correctly disposed when an app with shared resources is undeployed or redeployed. ""If an app references a shared HTTP connector and uses a WS Consumer that creates an outbound endpoint, that endpoint is not correctly disposed and when the app is redeployed the connector continues using the previously created endpoint (the one that was created by the disposed app).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8197","01/02/2015 16:48:22",5,"Listener response streaming only returns part of body. ""If you edit this test case to use larger body sizes, then tests begin to fail: org.mule.module.http.functional.listener.HttpListenerResponseStreamingTestCase""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8201","01/05/2015 17:42:34",3,"Exception in HTTP listener when path=""/"" and basePath=""/"" ""When using an http:listener with path=""""/"""", and referencing a listener-config where basePath=""""/"""", then an ArrayIndexOutOfBounds exception is thrown when receiving a request.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8202","01/05/2015 17:57:31",5,"HTTP requester not adding the reason phrase in the response ""The HTTP requester is adding an inbound property with the status code of the response, but no property with the reason phrase. Currently there is no way of getting the reason phrase of the response, analyze if it makes sense to add another inbound property with the reason phrase. The status code validator should also include the reason phrase when failing due to an invalid status code in the response. This is useful when consuming REST APIs that add information in the reason phrase of an error status code response.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8205","01/06/2015 14:37:55",8,"Listener should respect keep-alive with HTTP 1.0 and disable chunking. ""With HTTP 1.0 KeepAlive header, the http response from Mule returns """"Connection: Close"""" when streamingMode is ALWAYS or the payload is an InputStream. I'm not 100% sure if HTTP 1.0 officially supports chunking, but I am sure that the keepAlive header should be respected an chunking shouldn't affect this.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8206","01/07/2015 02:23:07",5,"Inconsistent implementation of streamingMode=""NEVER"" between listener and requestor. ""There are a number of cases tested in HttpListenerResponseStreamingTestCase where even when responseStreamingMode=""""NEVER"""" chunking is still used. In my mind it should be the """"AUTO"""" mode that decided if it should use chunking based on i) payload type ii) presence of headers. If there is a mode called """"NEVER"""", it should never do chunking otherwise this is confusing/misleading. On the other hand, currently throws an exception in this scenario. Update behaviuor so that in both cases: AUTO: - Chunking if payload is InputStream and no Content-Length header present. - Else delete transfer-encoding header if present and log. ALWAYS: - Delete content-length header and log. NEVER: - Delete transfer-encoding header and log. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8209","01/07/2015 16:27:31",3,"Mule Integration QA build is failing because of wrong sxc dependency version ""tests/integration module is failing because is trying to retrieve sxc version, which is not needed.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8210","01/07/2015 22:10:36",8,"Support parameter grouping in Configurations and Operations ""There are cases in which a group of parameters are frequently used together, for which it makes sense to treat them as a group. The extensions api already supports mapping pojos directly in the XML, but in same cases which group is preferred as parameters rather than a top level object. To enable that, the @Parameters operation will be created The outcome of the code above is a configuration with two parameters called 'color' and 'mode', one required and the other optional. The configuration has no attribute called options. If the Options class were to have another field also annotated with @Parameters, then such fields will be ignored. In the same way, the annotation can be applied to a class holding operations: In this case, both operations will have three parameters: message, color and mode. The last use case for this annotation is to have nested parameter classes: In this last example, the configuration/operation that is augmented with this extra parameters will have the sum of Options and MoreOptions parameters. Those parameters will be flattened, meaning that the model will contain no reference to the fact that the MoreOptions parameters were nested inside Options. The field must be a Java bean property (ie it needs to have setters and getters matching the field name)."""," @Extension public class MyExtension { @Parameters private Options options; } public class Options { @Parameter private String color; @Parameter @Optional private String mode; private String owner; } } public class Operations { @Parameters private Options options; @Operation public void hello(String message) { ... } @Operation public void goodBye(String message) { } } public class Options { @Parameter private String color; @Parameter @Optional private String mode; @Parameters private MoreOptions moreOptions; } } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8212","01/08/2015 18:25:21",1,"Cleanup the @Operation annotation parameters ""The @Operation parameter takes a name argument. That should be remove since directly contradicts the consistency that the API tries to enforce The annotation also contains an """"acceptedPayloadTypes"""" which is no longer used. That should be cleaned up""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8215","01/09/2015 13:50:44",8,"Write spec for validations extension ""Write and validate a Spec for a new extension module for validation purposes.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8216","01/09/2015 13:53:34",0,"Implement a validations extensions ""Implement a validations extensions following the spec defined in MULE-8216""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8220","01/12/2015 15:59:31",3,"Build number Maven plugin should be activated always ""We are currently executing maven-build-number-plugin only in release profile, this should be ran for all profiles.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8229","01/14/2015 20:28:14",5,"Fail to expand properties when using property placeholder shared in a domain ""Steps: # Deploy the below application and domain # Put domain.properties in domain root dir # bin/mule * Expected: Mule starts and flow listens on 127.0.0.1:8811/in1 and 127.0.0.1:8811/in2 * Actual: Mule fails to start because $[http.port] is an invalid value for port * Note: I put domain.properties file in domain root directory because in domain/classes it is not found ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8231","01/15/2015 21:44:08",0,"SftpMessageReceiver doesn't release the lock on files ""SftpMessageReceiver doesn't release the lock on files.""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8232","01/15/2015 22:08:43",1,"Core extension dependencies are not initialized in order ""Core extensions are initialized using the discorevy order instead of the order determined after resolving the dependencies. ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8233","01/16/2015 15:00:59",3,"Move tests/functional tests to tests/integration ""tests/functional should be only for test harness""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8239","01/19/2015 14:24:35",1,"Supported and recommended JRE version should be at least 1.7.0_60 ""In MULE-6866 we upgraded to Groovy 2.3.7-indy but according to [Groovy docs|http://groovy.codehaus.org/InvokeDynamic+support] there are known issues with Java versions lower than 7u60. We should increase supported and recommended versions to 1.7.0_60""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8240","01/19/2015 16:13:48",3,"Allow extension components to extend existing functionality ""There're cases in which an operation implemented through the ext-api should be part of an specific substitution group. Because substitution groups are an XSD specific concept and because the same concept might be necessary in other DSL types, we need a mechanism to denote extensibility that goes beyond Java's """"extends"""" and """"implements"""" keywords but is still type related. For that purpose, two new annotations are created: @Extensible: means that a given type is extensible by another extension. It doesn't mean type subclassing, but extension from a functionality point of view. This annotation has an optional String alias() attribute to allow a better experience when generating XSD @ImplementationOf(type=XX.class): This annotation can be used on a class or method implementing operations. It means that the affected operations are to be part of a substitution group defined by an extensible type. The type argument in this annotation is mandatory and has to be a type that is annotated with @Extensible""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8241","01/19/2015 16:17:12",5,"Allow restriction on which types of operations can be nested ""Currently, the ext-api supports nested operations through the use of arguments of type NestedProcessor. However, the generated schema allows any type of message processor to be nested. There're cases in which it's necessary to limit that to specific groups. For those cases, a new annotation is created: @RestrictedTo(type=XX.class) The type used in that annotation has to be annotated with @Extensible. By doing that, the SchemaGEnerator will generate a specific named group for that extensible type and only items on that group will be allowed as nested for that operation""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8242","01/19/2015 18:20:13",1,"Rename extensions -> extension in java package name ""Also ExtensionManager is better than ExtensionsManager in english IMO.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8247","01/21/2015 14:14:53",0,"SFTP inbound-endpoint autoDelete=""false"" does not work ""The connector's autoDelete value is the only one taken into account, so it can't be overridden and it's default value is """"true"""". This means as a workaround you can set the connector's value to """"false"""" but then that would be the case for all endpoints.""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8257","01/22/2015 18:39:56",13,"The changes in MULE-7742 impacted in performance, a better solution should be used. ""Review that changes in MULE-7742 and the previous changes proposed by Victor Romero.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8261","01/22/2015 20:15:20",0,"Avoid to set the same message listener on the message consumer ""Some JMS MessageConsumer doesn't allow to set the MessageListener once their are started (for example the one from Qpid). That causes the JMS connector to nor reconnect properly.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8263","01/23/2015 14:32:22",0,"Mule global log config is not found when application has plugins ""If an application uses plugins, then the MULE_HOME/conf/log4j2.xml file is not found. This is because when the application has plugins, then the parent classloader is a PluginClassLoader which is unable to locale resources at MULE_HOME/conf. The LoggerContext selector should default to the file is for whatever reason the classloader is unable to find that resource.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8264","01/23/2015 15:27:22",5,"Support TLS SNI Extension in Http OutboundEndpoint ""Java does not send SNI because of the the socket is created. While Java 7 supports the SNI extension with TLS it only uses it if the hostname is specified when the Socket is created rather than a InetAddress (it doesn't get hostName from InetAddress).""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8265","01/23/2015 15:33:08",8,"Test support for TLS SNI Extension in Http Module Requester ""Currently not supported. Also review listener support.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8267","01/23/2015 16:56:39",8,"Mule 3.6 HTTPS Request Connector does not validate certificate presented by remote server ""The server SSL certificate is not validated by requestor at all.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8270","01/26/2015 18:22:01",8,"HttpRequester not configuring TLS cipher suites and protocols ""The HTTP requester from the new module is not configuring restricted protocols and cipher suites for TLS.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8273","01/27/2015 16:25:43",5,"Document new HTTP Connector ""Add documentation for HTTP Connector""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8277","01/29/2015 21:06:52",1,"OAuth2 postAuthorize() with an expired token fails even if token was refreshed ""The Box connector has a postAuthorize method that invokes one of the connector's processors. When one of the connector's processors is invoked and the postAuthorize is called with an expired access token, the BaseOAuth2Manager is able to refresh the access token but re-throws the token expired exception which makes processor invocation fail. I believe the issue can be found in the following method: org.mule.security.oauth.BaseOAuth2Manager.postAuth(OAuth2Adapter, String) ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8278","01/29/2015 21:49:24",8,"HTTP Listener does not handle ""Expect: 100-Continue"" (RFC 2616) header correctly ""This can cause depending the scenario: 1) 1s latency overhead 2) Requests to hang ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8282","02/02/2015 10:55:26",5,"401 response received, but no WWW-authenticate header was present ""I've been searching and and tinkering since last week to figure out what is wrong with this, but no matter how I tried it still gives me this error in the console. I'm testing the http connector (3.6 EE) against twitter ReST API vs testing with Chrome's POSTMAN Rest client. With the POSTMAN client, it is working fine when POSTing status update. However with Mule it fails and gives me the error mentioned. I even added """"WWW-Authenticate"""" (replaced """"Authorization"""") before the call to http connector itself, and tried with adding it to header as well, still everything fails. Note: For the get timeline it is working both on Postman rest client and http connector, but when I tried on POSTing to status/update.json, Postman is successful, while Anypoint http connector fails. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8284","02/02/2015 16:27:04",5,"Http Listener allows inexistent keystore ""When I create an https listener Mule validates that the trustsore file exists but it doesn't validate that the keystore file exists. Try with the attached config. Create the truststore like this: keytool -genkey -alias mule -keyalg RSA -keystore keystore.jks -dname """"CN=Mule, OU=Engineering, O=MuleSoft, L=BA, ST=BA, C=AR""""""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8287","02/03/2015 14:04:30",5,"Allow cipher suite and protocol configuration per connector ""TLS cipher suite configuration is done through conf/tls-default.conf for all the Mule Server. We need a way to allow per connector configuration. Use cases: - Connect to a legacy API uses a vulnerable cipher suite for which the vulnerability has been mitigated, but I don't want to allow that cipher suite for other consumed APIs. - Because of internal security policy I need to use a particular set of cipher suites to publish an API but I need to consume an external API wich uses a different cipher suites not allowed internally.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8486","02/03/2015 19:44:19",3,"Allow to set certificate alias in keystore configuration ""When multiple certificates are installed in the keystore file, we need to provide a mechanism to pick one in the tls context element. How this is done can be review but most likely is using the certificate alias. So an alias optional attribute must be used in the keystore element. When there are multiple certificates and alias is not defined we should define hich on we should pick.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8288","02/03/2015 19:59:18",1,"Disable SSLv3 by default on FIPS 140-2 scenario ""The file tls-fips140-2.conf doesn't restrict enabled protocols by default. When enabling FIPS 140-2 on wrapper.conf, SSLv3 gets enabled by default.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8290","02/03/2015 23:18:54",5,"HTTP static resource component fails with HTTP listener ""The HTTP static resource component fails with the new HTTP listener component because it doesn't extract correctly the listener path to define the resource to return.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8291","02/04/2015 16:16:05",5,"Client credentials does not fail if it could not retrieve access token ""When using client credentials, start up of the application does not fail if mule was not able to retrieve an access token. Additionally some logging information must be added for troubleshooting.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8295","02/05/2015 14:37:56",8,"Upgrade to grizzly 2.3.19 ""See fixes includes multiple bug fixes plus two improvments I requested: 1) SNI Support out of the box with SSLFilter. https://java.net/jira/browse/GRIZZLY-1737 2) Mechanism to limit size of send queue and this direct memory use. https://java.net/jira/browse/GRIZZLY-1730""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8301","02/06/2015 17:55:49",5,"Upload 3.6.0 javadocs ""Upload javadocs to: https://www.mulesoft.org/docs/site/3.6.0/apidocs""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8304","02/09/2015 15:02:00",5,"It is not possible to define more than one keystore/truststore ""The TLS contexts introduced in 3.6 interfere with each other. Reproduce with the following scenario, where there are two flows that consume an HTTPS service, one with the server certificate in the truststore, and the other one without it. The first flow should work but the second one should fail. Currently, they both work correctly. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8306","02/09/2015 20:13:45",0,"DB Drivers should be removed from DriverManager when MuleApplicationClassLoader is disposed. ""Our modules and other libraries could load DB drivers from the Mule App class loader, those drivers should be deregistered when that class loader is disposed because if not they remain unreachable producing memory leaks.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8307","02/11/2015 01:11:56",13,"HTTP requester throws timeout errors with POST request ""Appears to be related to the """"Expect: 100 continue"""" header with Grizzly, that is found in HTTP/1.1 POST request. The bug reproduces in ESB 3.6 and 3.6.1, also GW 1.4. attached is the jmx file, using this proxy app for ESB (no Gateway tags). https://github.com/mulesoft/performanceworks/blob/master/APPS/PROXY-MCD/100B/http_module_proxy/proxy.xml If you change the method to GET instead of POST, you will not get the error. You should be able reproduce it easily. Wai ERROR 2015-02-11 00:29:48,112 [[PabloTestAPI_NewHTTP].proxyConfig.worker.09] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : Error sending HTTP request. Message payload is of type: BufferInputStream Code : MULE_ERROR-29999 -------------------------------------------------------------------------------- Exception stack is: 1. null (java.util.concurrent.TimeoutException) org.glassfish.grizzly.impl.SafeFutureImpl$Sync:357 (null) 2. Error sending HTTP request. Message payload is of type: BufferInputStream (org.mule.api.MessagingException) org.mule.module.http.internal.request.DefaultHttpRequester:190 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MessagingException.html) -------------------------------------------------------------------------------- Root Exception stack trace: java.util.concurrent.TimeoutException at org.glassfish.grizzly.impl.SafeFutureImpl$Sync.innerGet(SafeFutureImpl.java:357) at org.glassfish.grizzly.impl.SafeFutureImpl.get(SafeFutureImpl.java:264) at com.ning.http.client.providers.grizzly.GrizzlyResponseFuture.get(GrizzlyResponseFuture.java:173) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ********************************************************************************""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8311","02/12/2015 18:59:43",0,"Schema locations for includes are not being fixed. ""When a WSDL file includes types from another file, the schema location is not fixed to a proper URI. This prevents the metadata from being generated and the check for input parameters to be done, so the payload is used as SOAP body and operations without parameters fail.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8312","02/13/2015 00:00:49",5,"HTTP requester always add a / at the beginning of the request URI ""An http requester with this config http:request path=""""something"""" should generate a request with uri something but it's generating /something instead.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8318","02/13/2015 18:22:28",5,"WS consumer not evaluating flow vars in the serviceAddress when used with the new HTTP connector ""WS consumer allows MEL expressions in the serviceAddress property. Since 3.6, when the new HTTP connector is used by default, flowVars are not recognized in MEL expressions in the serviceAddress. The only variables that work are properties related to the Mule message. With the HTTP transport it works OK. This is because the outbound call uses muleClient to use the HTTP requestor, and the MuleEvent that carries the flowVars is lost. To reproduce, modify DynamicAddressFunctionalTestCase to use a flow var instead of an inbound property.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8325","02/18/2015 22:29:17",5,"Review and merge MULE-7588 ""Review and merge MULE-7588""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8326","02/18/2015 22:37:54",8,"write a spec on new lifecycle and registry consolidation ""Write and circulate a spec on MULE-7588""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8328","02/19/2015 01:05:27",5,"HTTP delete body is not allowed ""I am not able to call HTTP delete verb from mule HTTP connector with body . ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8331","02/19/2015 16:20:17",8,"Application Plugins (Cloud Connectors) support for external dependencies ""As a user I will like to use a connector such as Siebel, packaged as a plugin deployed in the plugins folder and be able to use external dependencies that cannot be shipped inside the connector.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8338","02/23/2015 17:22:44",1,"HTTP listener fails when receiving empty request with content type x-www-form-urlencoded ""When a POST request with content type application/x-www-form-urlencoded and empty body is sent to an http:listener, a 500 response is received and the flow is not executed. This happens because of a ClassCastException inside the listener. The flow should be executed, with NullPayload in the Mule message.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8341","02/25/2015 18:14:34",5,"Domain redeployment fails with zip file closed ""When doing a redeploy of a domain it fails with zip file closed when trying to reload some classes.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8342","02/26/2015 15:41:14",0,"NPE when Content-Disposition header is absent from multipart-response ""NPEs are being reported ( http://stackoverflow.com/q/28733880/387927 ) when the {{Content-Disposition}} header is not present in HTTP multi-part responses. Using this header is optional, it can't be assumed present. The crux of the problem is here: https://github.com/mulesoft/mule/blob/mule-3.x/modules/http/src/main/java/org/mule/module/http/internal/HttpParser.java#L94 If the header is missing, {{[0]}} is called on {{null}}."""," String contentDisposition = part.getHeader(CONTENT_DISPOSITION_PART_HEADER)[0]; ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8343","02/27/2015 17:47:56",5,"Review and update classloading documentation ""Documentation of mule classloading at http://www.mulesoft.org/documentation/display/current/Classloader+Control+in+Mule is not accurate and is out of date. There are missing things like application plugins, new domain classloading, etc""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8346","03/02/2015 18:43:59",8,"HTTP Request returns 401 when given correct authentication ""A prospect has not been able to connect to a web service hosted in IIS using Digest auth in the HTTP listener. They could connect using a java class with same credentials. none of the following combination worked as username in the HTTP connector: {realm\username, realm\\username, username:realm. Here is the webservice I used to reproduce the error: http://httpbin.org/digest-auth/auth/user/passwd Credentials {username=user, password=passwd} If needed: port=80; realm=me@kennethreitz.com Returned is 401: unauthorized""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8350","03/03/2015 19:48:04",8,"After upgrade CXF to 2.7.15 some jaxws-client configurations fail when using a proxy. ""When the service method receives a Holder OUT parameter and then a String, the string value is not received by the server. If the method returns void, then the value placed in the OUT parameter does not arrive the to client. See org.mule.module.cxf.HolderTestCase, method testClientProxyEcho3Holder.""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8353","03/04/2015 12:53:18",1,"README.txt in /logs is outdated ""The README.txt has not been updated to reflect the changes derived from the implementation of log4j 2.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8356","03/05/2015 17:39:55",5,"Source attribute in http requester not working when payload is null ""When the """"source"""" attribute is specified in an http:request element, it is ignored when the payload of the Mule message is NullPayload. Example: ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8364","03/06/2015 16:46:02",1,"Update commons-io in mule-commons to match the one used in mule ""In mule-common the commons-io version is 1.4: While mule is declaring the version to 2.4: This happens both in 3.6.x and master branches."""," commons-io commons-io 1.4 2.4 ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8367","03/09/2015 14:38:33",0,"Add http.relative.path to the list of inboundProperties in the new http module ""Add http.relative.path property to inboundProperties. This property should be the result of removing the basePath part of the request path.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8377","03/12/2015 18:07:37",0,"Minor fixes for support Java 8. ""Required fixes to run our tests with Java 8.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8382","03/13/2015 01:59:30",2,"Can't uncompress zip files containing no entries for folders ""Mule requires ZIP files that contain entries for folders and files like this: x/lib x/lib/a.jar x/lib/b.jar When the zip file contains only entries for files lie this: x/lib/a.jar x/lib/b.jar The file cannot be processed correctly.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8384","03/13/2015 15:08:38",0,"Session vars ""lost"" in foreach that uses outbound endpoint ""After a foreach that calls an outbound endpoint and modifies a session property, the modification can only be seen in the event's session but not the event's message session properties unless a new event is generated.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8386","03/13/2015 16:59:43",8,"Add support for PGP signature verification ""The PGP module is able to decrypt signed messages, but is not performing any verification on the signature. Add support to verify PGP signatures, and also consider that the key used to sign might not match the key used to encrypt.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8400","03/17/2015 18:31:23",0,"mule-esb-maven-tools pom.xml dependes on mule-artifact-archiver with wrong version ""mule-esb-maven-tools pom.xml dependes on mule-artifact-archiver version 1.0-SNAPSHOT but should be 1.1-SNAPSHOT. Also, remember that this version should be changed to 1.1 on release time.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8405","03/18/2015 12:19:45",0,"Unable to use a keystore with $ in its path ""In IOUtils, method getResourceAsStream tries to parse the resource name and assumes it's a placeholder if $ is found, which causes an exception to be raised since it is not.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8407","03/18/2015 21:07:14",8,"Backport MULE-8315 and MULE-7789 to all maintenenance branches ""As part of the library updates related to security vulnerabilities, there is a couple of changes that must be backported to 3.5.x, 3.4.x, 3.3.x, 3.2.x and 3.1.x: MULE-7789: needed to remove the usage of tomcat-util artifact (this one is already included in 3.5.x branch) MULE-8315: needed to upgrade tomcat libraries to a newer version""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8408","03/18/2015 23:10:13",5,"Collection splitter is not setting the group size when payload is an Iterator ""Salesforce queries return an iterator and when a collection splitter is used, it fails to aggregate the collection after because the group size is set to -1. Attached mule config This seems to be happening because this class https://github.com/mulesoft/mule/blob/bfb3a17263d1e4b32ee10272cbf710a2bf41b16b/core/src/main/java/org/mule/routing/outbound/IteratorMessageSequence.java is used from https://github.com/mulesoft/mule/blob/1dbf6e09a651184e9c54ec8988ecf1907cbdd58f/core/src/main/java/org/mule/util/collection/EventToMessageSequenceSplittingStrategy.java and it is setting UNKNOWN_SIZE as Group size for all Iterator payloads""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8410","03/19/2015 13:51:43",8,"Leverage MULE-7588 in extensions api ""Leverage the work done in MULE-7588 to implement a corrected lifecycle and dependency injection in the extensions api""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8411","03/19/2015 14:01:46",3,"XmlToXMLStreamReader does not support OutputHandler as source type ""XmlToXMLStreamReader declares OutputHandler as source type (in its superclass) but fails to convert that type.""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8412","03/19/2015 14:14:31",8,"Reuse OperationImplementation instances instead of creating and injecting new ones each time ""Currently the ext-api is creating a new instance of the operation implementation for each event. That is very confortable for the user, but it has performance considerations associated to garbage collection and the new to perform dependency injection all the time. We need to move to a schema in which: * One instance is created per configuration and reused as long as that configuration lives * The Class holding the method annotated with @Operation needs to have a constructor which receives a single argument which is the configuration to use. Failure to provide such a constructor which result in the application not starting * Upon creation, Mule will inject dependencies on this class but will not add it to the registry * This also means that it will no longer be valid to obtain things like the MuleEvent through a @Inject annotation, you have to receive it a method argument, which means that the invoker needs a refresh too""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8415","03/19/2015 18:02:24",5,"Add a backwards compatiblity setting to support Devkit artifacts which violate JSR-330 ""Per the work done on MULE-7588, Mule now supports the JSR-330 spec. However, as DEVKIT-1539 explains, Devkit is currently violating that spec. Devkit will fix this for the latest version but we need to add a compatibility setting to allow artifacts generated with older versions of devkit to function. This will work by customizing the injecting post processor to detectinstances which instances are devkit generated and skip dependency injection on them ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8416","03/19/2015 18:11:46",5,"Domains are not well disposed and get reused on redeploy. ""Domains are cached on creation but they are not correctly removed on dispose so on redeployments they get reused.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8421","03/20/2015 18:01:45",8,"Improve MuleMessage's data type consistency ""DefaultMuleMessage's datatype is not being properly updated and maintained. For example: _DefaultMuleMessage#setEncoding does not update dataType's encoding _DefaultMuleMessage#setMimeType does not update dataType's mimeType _DefaultMuleMessage#setPayload does not update dataType's type _DefaultMuleMessage#setProperty is not update dataType when a encoding property is set on the message Improving data type consistency and propagation is required to better support auto transformations and mapping tools""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8422","03/20/2015 18:57:18",8,"Implement Validations XML components ""Implement Validations XML components""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8423","03/20/2015 18:58:15",5,"Create MEL version for each validator in the validations module ""Create MEL version for each validator in the validations module""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8435","03/27/2015 19:55:49",5,"Check if Ext-api jars are Maven Central compliant ""Perform that verifyication on the mule-extensions-api and mule-extensions-api-annotations projects""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8441","03/31/2015 13:02:40",5,"Add a way to inject all available core extensions in a core extension ""Mule core extensions can have dependencies against other core extensions, but these dependencies are fixed on compile time (dependencies are defined using MuleCoreExtensionDependency method annotation). In order to properly support some management scenarios, we need to provide a way to let a core extension to receive all the available core extensions. Given the constraints on lifecycle imposed by the MuleCoreExtensionDependency dependencies, a core extension that receives all the available core extensions cannot contain any methods annotated with it.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8442","03/31/2015 14:24:54",1,"app.home property is no longer available ""When an application is deployed, the Spring configuration builder is running before the SimpleConfigurationBuilder making some properties like app.home not available to the mule config""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8447","04/06/2015 22:46:26",1,"extension API should consistently always inject values through fields instead of setters ""Right now, when the ext-api creates an object uses setters to inject values parsed from XML, while in some other scenarios like when resolving expressions it uses fields. That leads to some inconsistency plus the setter injection limits the ability to encapsulate the internal representation of some object's state. Always use fields to inject values.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8448","04/07/2015 13:28:27",1,"ExtensionResourcesGeneratorAnnotationProcessor is not been fired ""ExtensionResourcesGeneratorAnnotationProcessor is not been fired because the full classname of @Extension has changed and the refactor didn't modified this file. This is because of a java language limitation which doesn't allow a .class.getName() kind of reference there. As a result, xsd is not generated when building a extension""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8450","04/07/2015 16:21:18",1,"add the concept of parameter alias in the ext-api annotations ""When using the ext-api through annotations, there're limitations on the possible names that parameters can take because of the java language reserved words. For example, an attribute cannot be named class. Another problem is when from a coding point of view, an attribute should have one name which isn't so representative when seen from an extension's parameter point of view. Because of that, we need the ability to add an alias attribute to the @Parameter annotation.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8452","04/08/2015 00:22:35",1,"Introduce type level aliases for extensions API ""When the XML support for the ext-api maps a java complex type as a top level element (usually the case when defining global pojos), there's the need to provide an alias so that the global element can have a name which is not directly tied to the Java type name.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8453","04/08/2015 16:41:29",5,"Add data type to message properties ""MuleMessage properties have no information about the type of the value they are holding. Providing a way to maintain this information will help to support more transformation scenarios and will improve usability in Studio""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8457","04/09/2015 00:15:53",5,"Replace SetPayloadTransformer with a plain message processor ""SetPayloadTransfomer is the implementation behind set-payload element. As the name implies, is a Transformer and is executed invoking muleMessage transformation capabilities. Problem with this transformer is that it returns only a value and in order to properly propagated message's dataType, it must set the correct dataType (the one configured by the user). Besides that, transfomer's source/target dataType is not valid on this particular case, because the datatpye is dynamic (assigned value can be resolved from an expression). So dataType can't be statically defined.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8458","04/09/2015 13:15:26",13,"Upgrade async-http-client to 1.9.19. ""We need to upgrade to version 1.9.18 in order to support NTLM. Here's AHC's migration guide: https://github.com/AsyncHttpClient/async-http-client/blob/master/MIGRATION.md There could also be some issues with missing multipart classes.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8459","04/09/2015 13:17:47",5,"Implement NTLM authentication for the HTTP Requester ""Once AHC is upgraded to 1.9.18 we should be able to add support for NTLM.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8465","04/09/2015 16:11:11",8,"Improve set properties transformers to set property datatype ""Mule message properties now contain a datatype. All the transformers that set properties in a message/session should provide a way to configure the datatype and update that datatype in the property accordingly.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8466","04/09/2015 20:54:19",1,"Generated XSD defines restriction groups by extension ""When an operation takes NestedProcessors as an argument, the @RestrictedTo annotation can be used to limit the acceptable message processors to a given substitution group. However, what the XSD generator is doing is to create a group which lists all of the operations in the given restriction type. Because that group is fixed, it doesn't allow to externally contribute more elements with the same substitution group. What the generator should do is to define a group which has a reference to the substitutionGroup and thus allowing variable elements which meet the restriction""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8467","04/09/2015 21:21:53",1,"ArgumentTypeMismatch when many nested operations are supported but only one is provided ""The ext-api supports defining operations which can take one nested Operation or a list of them. When the operation supports many but only one is provided, the ResolverSetResult doesn't contain a list of one NestedOperation but a single one, which results on an ArgumentTypeMismatch.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8468","04/11/2015 14:13:27",2,"Improve data type propagation for properties ""Work done on MULE-8453 did not include updating some property setter methods to include datatype.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8469","04/12/2015 12:59:54",3,"Message transformation must no update payloads data type when payload was not transformed ""DefaulMuleMessage#transformMessage(MuleEvent, Transformer) always updates the message data type to the transformer output data type. That is wrong because some transformers update parts of the message other than the payload. (like message properties) Probably those transformers should be plain message processors, but a way to fix this problem is to check that payload has changed after the transformation.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8471","04/13/2015 14:52:41",0,"Race condition on and deployment lifecycle ""When using a reconnect-forever for a transport connector, the connection logic runs in a different thread. Thus, when the components are being started and receivers are added that need to connect themselves there can be a race condition between the registration of a receiver (where it is connected only if the connector itself is connected) and the connector's connection logic (where the existing receivers are connected). When it occurs the connector's connection logic finds there are no receivers to be connected and the receiver registration finds the connector is not connected, so that receiver is never connected. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8472","04/13/2015 20:24:43",0,"Fix maven-processor-plugin version in extensions pom ""Version of maven-processor-plugin is not specified in extensions pom.xml. Because of that, the latest available version is used (3.1.0-beta1). Using that version causes compilation failures apparently in some machines (apparently when maven version > 3.0.x) Fixing version to 2.2.4 fixes the problem""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8473","04/13/2015 22:17:04",8,"Configs should be optional when using Ext-api operations in a flow ""Right now, every MP which executes an extension operation is required to provide a config. This is not good from a usability standpoint so the desired behaviour is: * If a config is specified through the config-ref attribute, then use it * If no config is specified but there's one configured, then locate it and use it * If no config is specified nor defined, then depending on the extension an implicit one can be created. An implicit configuration is created by simply instantiating the default config. Configs should be marked as not supporting implicit creation through some annotation/annotation attribute""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8474","04/13/2015 22:18:39",1,"remove the ""repackaged"" package from extension-support module ""Because ext-api development started when mule was using Spring 3.x, a Spring 4.x package was embedded into our code. Now that Spring was upgraded to the lastest version, that repackage should be remove in favor of the original classes in the spring jar""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8475","04/13/2015 22:25:59",5,"Implement a solution to automatically infer supported schema versions for XML compatible extensions ""Right now, when an extension is to have XML support, the @Xml annotation includes a """"schemaVersion"""" attribute. That is not a scalable solution because assuming that an extension is released in version 3.7, then its spring bundle should support schemas 3.7, 3.8, 3.9 and so forth, and it's very undesirable for a developer to traverse through all the extensions modifying that. We need a solution in which given an """"inception version"""" version, the current schema version is inferred and the prior ones back to the inception version are also included in the spring bundle. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8476","04/13/2015 22:28:02",8,"Spike on on inferring extension version from project version ""Currently, the @Extension annotation includes a version attribute which is used to specify an extension version. However, it's undesirable to have the need to upgrade the version of every extension each time that a new version is released. A mechanism should be defined for the extension version to be automatically inferred from the underlying ${project.version}. There should still be a way to fix the extension version arbitrarily""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8477","04/13/2015 22:32:40",5,"Validate that Pojo attributes are not composites ""When a pojo is used as a parameter in an Extension, XSD support is generated to allow users define the instance on the XML. However, this won't work if the object is a composite. The composite fields should be skipped when generating the XSD support.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8478","04/13/2015 22:36:01",5,"It should not be mandatory for a class annotated with @Operation to depend on the config object ""Right now, when a class contains methods annotated with @Operation, then it is demanded that a single constructor is available to create the instance and pass the configuration instance over. However, not in all cases the operations in a class require of the configuration. The behaviour should be that if such constructor exists then it's used. If it doesn't, then a default constructor is used to create a config-less operation instance. Only if no constructor is found which matches both criterias should an exception be thrown.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8479","04/13/2015 22:40:02",5,"Operations of an Extensible extensions should not require to be annotated with @ImplementationOf ""Extensions can be annotated with @Extensible to signal that external modules can extend them further. Right now, it's required for the classes in which such extensions are implemented to be annotated with @ImplementationOf. However, that's redundant since a given extension operations are by very definition extending it. Such annotation should only appear on third party extensions which are in fact extending it.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8480","04/13/2015 22:41:01",1,"Consider renaming @ImplementationOf to @ExtensionOf ""Consider renaming @ImplementationOf to @ExtensionOf since it's clearer for some persons""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8481","04/14/2015 14:58:02",3,"WSConsumerConfig should use the HttpRequesterConfig interface rather than the internal implementation ""The *connectirConfig* field of the class org.mule.module.ws.consumer.WSConsumerConfig can be configured by passing an initialized instance of a *DefaultHttpRequesterConfig* when it should be using the interface of the the previous one: *HttpRequesterConfig*. This small chance will unblock the DevKit's story [DEVKIT-1527|https://www.mulesoft.org/jira/browse/DEVKIT-1527] providing an automated way of instantiating WSC manually when initializing a HttpRequesterConfig by hand.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8482","04/14/2015 15:08:54",8,"Provide a builder for HttpRequesterConfig interface ""Despite the normal use case for initializing a HttpRequesterConfig is from the definition parser, for a specific DevKit's story [DEVKIT-1527|https://www.mulesoft.org/jira/browse/DEVKIT-1527] we need to feed the WsConsumerConfig with an already initialized instance of *DefaultHttpRequersterConfig*. Before this jira, ideally, [MULE-8481|https://www.mulesoft.org/jira/browse/MULE-8481] should be tackled down to make WsConsumerConfig consume the HttpRequesterConfig interface, so that from a DevKit's POV initializing objects and passing through the WsConsumerConfig will work properly.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8483","04/15/2015 12:33:46",5,"Update message data type when Content-Type property changes ""When Content-Type property is set on a message, then payload's data type must be updated to reflect the new value.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8484","04/15/2015 14:04:36",1,"Succesful undeployment is not show in console ""# Download 3.7.0-M2-SNAPSHOT # Copy any Mule app to apps directory # Start server # Delete default-anchor.txt Undeployment request is logged and is done but concole never shows that now there is only one app deployed and that default app was undeployed successfully.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8485","04/15/2015 14:49:53",1,"rename the artifact mule-extension-validations to mule-module-validation ""We finally decided to not reflect the difference between a craft module and an ext-api based one on the artifact name since from a user's point of view there shouldn't be a difference""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8498","04/16/2015 09:38:56",3,"Message transformation must maintain original mimeType and encoding when transformer does not provide them ""When a transfomer is applyed on a DefaultMuleMessage and changes its payload, then the transformer's output datatype is assigned to the message datatype. However, transformer's output datatype not always defines mimeType and encoding. If a transformer does not change any of those fields, then the fields from original payload's datatype should be used.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8501","04/16/2015 18:28:40",1,"ExtensionManagerConfigurationBuilder not invoked when Mule starts in standalone mode ""When starting in standalone mode, the ExtensionManagerConfigurationBuilder is not been invoked and thus applications fail to deploy if they contain any extensions""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8503","04/16/2015 23:28:50",1,"Remove the ""extension"" prefix from the generated XSD file name ""Since per MULE-8485 we decided that extensions should not have any naming differentiator, the %s-extension-%s pattern which is now used to name generated XSD needs to change to be source agnostic.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8505","04/17/2015 18:06:14",3,"XSD Generator creates wrong attribute types for numeric parameters ""h2. Size validator has int parameters for min and max values but the generated XSD creates attributes with Long data type. {code} /** * Validates that {@code value} has a size between certain inclusive boundaries. This * validator is capable of handling instances of {@link String}, {@link Collection}, * {@link Map} and arrays * * @param value the value to validate * @param min the minimum expected length (inclusive, defaults to zero) * @param max the maximum expected length (inclusive). Leave unspecified or {@code null} to allow any max length * @param options the {@link ValidationOptions} * @param event the current {@link MuleEvent */ @Operation public void validateSize(Object value, @Optional(defaultValue = """"0"""") int min, @Optional Integer max, @ParameterGroup ValidationOptions options, MuleEvent event) throws Exception { ValidationContext context = createContext(options, event); validateWith(new SizeValidator(value, min, max, context), context, event); } {code} h2. expressionObject is generated for java.lang.Long parameters in isLong validator {code:xml} Specify which configuration to use for this invocation. {code}"""," Specify which configuration to use for this invocation. /** * Validates that {@code value} has a size between certain inclusive boundaries. This * validator is capable of handling instances of {@link String}, {@link Collection}, * {@link Map} and arrays * * @param value the value to validate * @param min the minimum expected length (inclusive, defaults to zero) * @param max the maximum expected length (inclusive). Leave unspecified or {@code null} to allow any max length * @param options the {@link ValidationOptions} * @param event the current {@link MuleEvent */ @Operation public void validateSize(Object value, @Optional(defaultValue = """"0"""") int min, @Optional Integer max, @ParameterGroup ValidationOptions options, MuleEvent event) throws Exception { ValidationContext context = createContext(options, event); validateWith(new SizeValidator(value, min, max, context), context, event); } Specify which configuration to use for this invocation. ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8506","04/17/2015 18:49:46",5,"XSD Generator fails to generate documentation for attributes ""We should check with [this tool|https://github.com/mulesoft/mule-tool-schema-doc] that the documentation generated for Validators extension is correct.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8509","04/17/2015 23:01:18",8,"CXF Proxy-Client is throwing NullPointerException ""Nowadays, if you want to create a proxy, you have to specify the port name and the soapVersion for each binding. This information is provided by the wsdl, so it shouldn't be required, the proxies should detect them automatically. As a consequence, if you have an API with multiple ports, one of them receiving a SOAP 1.1 envelope, and other one receiving a SOAP 1.2 envelope, and if you don't specify the port and the soapVersion in both proxies (service and client) you will not be able to send a SOAP 1.2 message. This means that a simple proxy cannot be used with both types of SOAP versions. ""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8510","04/19/2015 13:40:33",2,"Setting a NullPayload in a property must behave as setting null ""Mule uses NullPayload to represent a null value in a MuleMessage's payload. When a message has NullPayload and a property is set using an expression like #[payload], then the property will contain NullPayload. This situation requires that checking a property requires to consider NullPayload value as a separate case other than null and not null. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8512","04/20/2015 14:26:52",3,"Allow default processing strategy to be configured per app ""Currently if you want to use a sync processing strategy in every flow it is necessary to configure it on every single flow in your app. Add a attribute to the element to define this once. Also, consider allowing a system property too. This would be useful for: - Alternative testing plans - Setting default per instance, e.g. in cloudhub maybe. """," ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8514","04/20/2015 15:08:35",8,"Add support for non-blocking processing strategy to CXF/WS-Consumer ""Add support so that CXF/WS-Consumer can be used in Flow and non-blocking processing supported.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8518","04/20/2015 17:59:21",5,"Provide access to client certificate on 2-way TLS authenticated connections ""When a 2-way TLS authenticated connection is created the client certificate should be exposed in the flow since it may be useful to use it to identify the client. We are going to expose the client certificate ONLY (not the CA certificates) in the flow using a new inbound property http.client.cert. The user can access the client principal by doing message.inboundProperties['http.client.cert'].getSubjectDN() We analyse if there is any risk by exposing the certificate as an inbound property but we got to the conclusion that there's no risk since the client certificate is publicly available in general and it's not used for the communication encrypt / decrypt. It's only used to identify the client.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8527","04/21/2015 18:38:43",3,"Remove AspectJ dependency in CE ""AspectJ needs to be upgraded to version 1.8.5 to be consistent with the version number across all distributions and remove warnings when building.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8529","04/22/2015 20:50:54",0,"Async Loggers stop working after reconfiguration ""If the log4j2.xml file of a deployed application is modified, then log4j2 automatically picks up the change and reconfigures itself, which causes the current Configuration object to be stopped. However, because MuleLoggerContext wraps the loggers into a DispatchingLogger instance, the updateConfiguration(Configuration) method never reach the actual loggers which remain pointing to the stopped configuration instead of the new one. As a result, no AsyncLogger can ever again post any message""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8533","04/23/2015 15:19:59",8,"MBeans/JMX Memory Leak on vanilla Mule ESB Standalone ""Jira created at request of Mariano Gonzalez - see http://forum.mulesoft.org/mulesoft/topics/mbeans-jmx-memory-leak-on-vanilla-mule-esb-standalone-no-custom-code-deployed?utm_source=notification&utm_medium=email&utm_campaign=new_reply&utm_content=reply_button&reply%5Bid%5D=15618818#reply_15618818 1) Deploy an out of the box Mule Standalone ESB, e.g. mule-standalone-3.6.1 2) Start - default app deploys, no custom code deployed 3) Start Oracle VisualVM, connect to Mule ESB 4) Watch the heap being consumed I performed this test with max memory changed to 256Mb in wrapper.conf (so I didn't have to wait so long for memory to be consumed), on openSuse 13.1, with Oracle Java version """"1.8.0_31"""" Java(TM) SE Runtime Environment (build 1.8.0_31-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode) I have observed the same symptoms using Java jdk1.7.0_75 on openSuse, and Java jdk1.7.0_xx on Mac/OS, so it doesn't seem to be o/s or Java related. If I don't attempt to monitor Mule ESB, the memory leaks don't appear to happen, though it's difficult to be sure without being able to monitor, but I presume that this is MBean/JMX instrumentation related. Running Oracle JConsole does not appear to induce the same dramatic memory consumption, but does seem to cause some sort of slow incremental leak. ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8534","04/23/2015 17:53:48",1,"Reverse the semmantics of MULE-8415 ""The flag introduced in MULE-8415 disables dependency injection for devkit components. We need it to be other way around. By default, Mule is not to inject into Devkit and the property is to be renamed to mule.devkit.participates.di and only when set to true devkit will be considered into DI.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8541","04/23/2015 17:55:53",2,"Exposes information needed by DataMapper in order to run as a plugin ""DataMapper is accessing some elements in our code that is defined as protected. Because now DataMapper is going to be a Mule plugin, this won't work anymore as it will ran in a different classloader. Need access to the following fields on MVELExpressionLanguage: globalFunctions, parserConfiguration and aliases Need access to MuleImmutableVariableResolver class""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8535","04/23/2015 18:13:21",8,"Ensure that transformers use a proper return datatype ""Transformers define an output dataType which is set on the message after the transformation. In order to properly propagate message dataType, transformers must return the proper type, mimeType and encoding that corresponds to the executed transformation.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8536","04/24/2015 01:04:10",1,"DI should never include Devkit components ""Although MULE-8534 and MULE-8415 tried to keep some level of compatibility between mule's injector and devkit's components, some other integration issues keep popping up so we decided that for now Devkit will be excluded from it. Devkit will provide its own solution for DI""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8538","04/24/2015 19:39:16",5,"Dispose lifecycle phase is invoked even when initialise phase fails ""dispose() should not be invoked if initialise() fails. At least thats how I believe it always worked. This change causes NPE's in dispose() in a lot of cases. Which results in much more verbose and confusing errores being logged.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8539","04/24/2015 20:01:44",1,"Lifecycle not applied to Objects manually registered during initialisation ""Suppose an Initialisable or Startable object which during any of those phases registers a new Lifecycle object (e.g.: like an endpoint which creates and registers a connector). Only the already completed phases are applied to the newly registered object while the one being currently executed isn't""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8543","04/27/2015 19:03:16",1,"CXF schemas for 3.5 and 3.6 are wrong ""https://github.com/mulesoft/mule/blob/mule-3.x/modules/cxf/src/main/resources/META-INF/spring.schemas#L5-L6 ""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8544","04/27/2015 19:04:25",1,"Core schema for 3.6 is not defined and rubbish at the end of line ""https://github.com/mulesoft/mule/blob/mule-3.x/modules/spring-config/src/main/resources/META-INF/spring.schemas#L11 And remove rubbish bracket at end of line.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8547","04/28/2015 14:04:25",0,"Unused resolvePath method in DefaultHttpListenerConfig ""That method was removed but later reintroduced by the merge of a lifecycle branch that had been branched when the method was still present.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8548","04/28/2015 15:03:40",5,"Upgrade Spring security to 4.0.1.RELEASE ""Spring dependencies were updated to 4.1.6 and keeping Spring security in 3.1.0 is an important risk.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8549","04/28/2015 15:39:24",2,"Update C3P0 to version 0.9.5 ""There is a new version of C3P0. Would be great to update it to replace the old version that is shipped on Mule""","",0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8550","04/28/2015 15:43:43",0,"Transformers are registered twice ""As a side effect of MULE-7588, transformers registered either through registry-bootstrap.properties or as Spring beans are registered twice. As a result, some transformer resolutions fails, specially when the object contains XML or JSon annotations. Although this seems benign at first sight, in some cases it leads to wrong resolution since Mule might thing that it has more than one transformer to resolve the same case""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8553","04/28/2015 18:34:27",3,"Add max-send-buffer-size entry in wrapper.conf ""We need to add that property now that it's available.""","",1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8555","04/28/2015 20:32:22",5,"Promote to public api DefaultHttpListenerConfig.resolvePath or equivalent behavior ""There's no way to resolve the full path of a listener using the public API. Mule 3.6 offered the following method that was changed in 3.7: """," public String resolvePath(String listenerPath) ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8556","04/29/2015 00:51:25",3,"SpringRegistry is not thread-safe ""In versions prior to 3.7.0, the SpringRegistry was read only and all objects registered through the MuleRegistry API went to the transient registry. Per the work in MULE-7588, the TransientRegstry no longer exists and the SpringRegistry is writable. However, it's missing the ReadWriteLock that TransientRegistry had to allow register and lookup objects concurrently. This causes random failures, specially when dealing with dynamic endpoints""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8559","04/29/2015 16:12:20",0,"Deployment failure if two apps are both using BTM in the same Mule server ""Deployment failure if two apps are both using BTM in the same Mule server""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8565","05/05/2015 15:13:40",3,"Add support for preemptive basic authentication in the HTTP module ""Allow to configure if basic authentication is preemptive or not in the new HTTP connector, by adding an attribute to the config: preemtive=""""true|false|expression"""" Also add this to the config builder in the public API of the connector.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8569","05/05/2015 22:29:14",5,"Applications and corresponding domains should share the same OptionalObjectController ""OptionalObjectsController is used to track objects registered through registry-bootstrap.properties which are optional. When an application belongs to a domain, that instance should be shared between the app and the domain. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8572","05/06/2015 16:21:27",3,"Dependency injection fails when injection candidate is registered on domain ""When the @Inject annotation is used to inject an instance which leaves on the parent domain context, injection fails""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8573","05/06/2015 19:02:34",3,"Add support for expressions in the authentication configuration of the HTTP connector ""Add support for MEL expressions in the attributes of the authentication elements of the new HTTP connector.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8577","05/06/2015 23:11:44",0,"It would be useful to have the Datatype mimeType info when you use the logger ""Right now you have the payload type and the encoding but not the mimeType: Ex: org.mule.DefaultMuleMessage { id=badce400-f435-11e4-b227-20c9d0cf41e7 payload=java.lang.String correlationId= correlationGroup=-1 correlationSeq=-1 encoding=UTF-8 exceptionPayload= ... }""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8579","05/06/2015 23:17:09",3,"Datatype cannot be configured when adding properties using message-property-transformer ""You can't set the datatype to the properties in the Message Properties transfomer""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8580","05/07/2015 15:00:32",5,"Fix JDK8 build ""Tests run in a different order in the JDK8 build, so HttpsSharePortTestCase fails in that case because of some other test that runs before it. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8581","05/07/2015 17:37:20",5,"Spike on Collection splitter is not setting the group size when payload is an Iterator ""Salesforce queries return an iterator and when a collection splitter is used, it fails to aggregate the collection after because the group size is set to -1. Attached mule config This seems to be happening because this class https://github.com/mulesoft/mule/blob/bfb3a17263d1e4b32ee10272cbf710a2bf41b16b/core/src/main/java/org/mule/routing/outbound/IteratorMessageSequence.java is used from https://github.com/mulesoft/mule/blob/1dbf6e09a651184e9c54ec8988ecf1907cbdd58f/core/src/main/java/org/mule/util/collection/EventToMessageSequenceSplittingStrategy.java and it is setting UNKNOWN_SIZE as Group size for all Iterator payloads""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8583","05/07/2015 18:11:21",3,"Upgrade async-http-client to 1.9.21 ""This version includes several fixes but depends on also upgrading Grizzly.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8584","05/07/2015 18:12:28",1,"Upgrade grizzly to 2.3.20 ""This is necessary to upgrade AHC.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8587","05/11/2015 21:07:14",0,"Add a Base64 decoded which doesn't automatically unzip ""Currently, the Base64.decode(String) method automatically unzips if it detects a GZIp magic number header. Add a new method which doesn't""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8597","05/13/2015 19:26:50",3,"set-payload with invalid MIME type returns an ugly error ""When using an invalid MIME type in set-payload the error message is not very clear. Deploy this app: Request: ~ curl http://localhost:8081/ javax.activation.MimeTypeParseException: Unable to find a sub type. (org.mule.api.MuleRuntimeException). Message payload is of type: BufferInputStream% App log: org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor:32 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MessagingException.html) -------------------------------------------------------------------------------- Root Exception stack trace: javax.activation.MimeTypeParseException: Unable to find a sub type. at javax.activation.MimeType.parse(MimeType.java:102) at javax.activation.MimeType.(MimeType.java:63) at org.mule.transformer.types.SimpleDataType.(SimpleDataType.java:40) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8598","05/13/2015 19:31:35",3,"Deployment should fail when using Invalid MIME type ""When deploying the below config deployment should fail because MIME type does not exists. Now is failing in runtime when executing the flow """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8600","05/13/2015 20:36:24",8,"Setting wrong encoding causes flow execution to hang ""Deploy the below config and run this: curl -m 10 http://localhost:8081/ curl: (28) Operation timed out after 10004 milliseconds with 0 bytes received It logs an error as soon as I send the request but then I only receive the curl timeout without Mule doing anything. When I remove encoding=""""asdfsadf"""" ti returns 200 immediately.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8601","05/13/2015 20:55:25",3,"Deployment should fail when using invalid encoding ""When deploying the below config deployment should fail because encoding does not exists. Now is failing in runtime when executing the flow """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8603","05/14/2015 14:58:25",8,"keepAlive is not working correctly in the HTTP requester ""keepAlive is not working as expected. The http:request element always sends the header Connection: keep-alive in the request, regardless of the usePersistentConnections attribute in the config. If usePersistentConnections is set to false, keepAlive should be disabled, but the header is still sent. Also, in the proxy scenario (using a listener and a requester) connections are kept alive but not reused. See example config here: https://github.com/mulesoft/performanceworks/blob/master/APPS/PROXY-MCD/100B/http_module_proxy/proxy.xml This causes """"Remotely closed"""" errors, thrown by the service that is being proxied in a highly concurrent scenario. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8604","05/14/2015 15:08:45",2,"Incorrect error processing on Jetty transport ""Jetty transport is not properly managing error conditions that occur when a MuleMessage fails to be created for the current request. For example, if a request contains an invalid mimeType, it won't be possible to create a DefaultMuleMessage from it, an exception will be thrown to signal the error, but the returned response will be a 200 instead of 500. (NOTE: the problem exists only when there is no MuleMessage, once it has been created, then it works as expected)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8609","05/15/2015 14:55:36",1,"Should be able to fetch prototype by name without lifecycle applied ""In most scenarios, when a prototype is lookup up by name, lifecycle should be applied to it before returning. There're some scenarios (e.g.: fetching a MessageProcessor that will go into a DynamicPipeline) which are not so and we need a way to specify that this case is different. The following method was applied to the LifecycleRegistry to support such case: """," /** * Look up a single object by name. *

* Because {@link #lookupObject(String)} will * return objects which had lifecycle phases * applied,this method exists for cases in which * you want to specify that lifecycle is not to be * applied. The actual semantics of that actually depends * on the implementation, since invoking this method * might return a new instance or an already existing one. * If an existing one is returned, then the lifecycle might * have been previously applied regardless. * * @param key the key of the object you're looking for * @param applyLifecycle if lifecycle should be applied to the returned object. * Passing {@code true} doesn't guarantee that the lifecycle is applied * @return object or {@code null} if not found */ T lookupObject(String key, boolean applyLifecycle); ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8610","05/15/2015 17:57:04",1,"Update MVEL version to 2.1.9-MULE-006 ""Need to update MVEL to include the fix for MULE-8336""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8614","05/18/2015 18:57:46",0,"HTTP requester has a worker thread pool that is not used ""The grizzly client used in the HTTP requester is configured with SameThreadIOStrategy, so that the thread that is executing the flow is the same that executes the request. However, a worker thread pool is also defined (unused). This was a workaround for a NPE of the same thread strategy. This pool should not exist.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8616","05/19/2015 19:09:00",0,"NTLM auth doesn't work on redirect ""There's an issue in the underlying library (async-http-client) which causes such a request to fail when the server responds with a 307 redirect instead of a 200 ok. Issue link is: https://github.com/AsyncHttpClient/async-http-client/issues/866 This was fixed in version 1.9.21 of AHC.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8619","05/20/2015 11:49:46",1,"Review event copying and access control in non-blocking support ""Need to ensure there are no issues..""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8626","05/21/2015 16:51:46",5,"Connection and Keep-Alive message properties should not affect Listener/Requestor connection reuse behaviour. ""Listener can be set up to use persistent connections and client attempt to reuse connections, but if for some reason a """"connection"""" header gets returns to the listener this behaviour breaks. Connection reuse behaviour should be encapsulated in listener/requestor.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8628","05/21/2015 18:03:24",5,"HTTP Connector should not send/respond http.* properties ""HTTP Connector knows these properties are internal, so it makes sense that they are filtered and not sent.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8632","05/22/2015 06:48:39",5,"HTTP Listener Connector reject a GET and DELETE that contains a body. ""http://forum.mulesoft.org/mulesoft/topics/http-get-delete-how-to-get-the-body-of-request-using-http-listenner-connector""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8635","05/22/2015 15:56:41",8,"ConcurrentModificationException when hot deploying ""To reproduce: # Deploy first application in Mule Standalone CE # Deploy second application to a different server (app1 depends on it) # Load application with some requests (Don't know if this is needed to reproduce) # Deploy third application by moving the exploded app to apps directory""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8638","05/22/2015 20:46:06",8,"[Regression] NPE when filter fails ""When a filter evaluation fails message is discarded but a NPE is shown in app log.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8639","05/25/2015 15:53:49",0,"Upgrade grizzly to 2.3.21 ""We need this because of issues on version 2.3.20.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8645","05/26/2015 19:11:50",0,"Remove jasper-jdt-6.0.29.jar from Mule distributions ""There are some vulnerabilities related to jasper-jdt-6.0.29.jar that could being affecting mule applications: CVE-2014-0119, CVE-2011-0013, CVE-2012-5886, CVE-2014-0075, CVE-2011-5062, CVE-2011-0534, CVE-2013-2067, CVE-2011-1184, CVE-2011-2526, CVE-2013-4286, CVE-2012-4431, CVE-2010-4172, CVE-2012-5568, CVE-2014-0096, CVE-2012-3544, CVE-2011-4858, CVE-2012-3546, CVE-2010-4312, CVE-2012-2733, CVE-2012-0022, CVE-2014-0227, CVE-2012-5885, CVE-2013-4590, CVE-2011-5064, CVE-2011-5063, CVE-2014-0099, CVE-2012-5887, CVE-2013-4322, CVE-2014-0227 The only way to avoid these vulnerabilities is to remove the mentioned artifact from the distributions and manually add it in case that is required.""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8648","05/27/2015 18:36:38",0,"FTP requester is not validating single files ""When the requester is triggered and a single file is processed (on purpose or because the folder selected only contains one file) validations are not applied and the file is processed regardless. These validations include filename filters and file age in EE.""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8649","05/27/2015 20:09:58",8,"Resolve data type from simple MEL expressions ""Now that dataType is being propagated for payload and properties, it would be good if dataType can be propagated when MEL expressions are used. For example, when using set-payload with """"flowVars['foo']"""" expression, it would be good if the property dataType is assigned to the payload's datatype. Simple expressions include: * payload/message.payload * direct access to invocation/session properties, like #[foo], where foo is an invocation/session variable * access to flowVars, like flowVars['foo'] * access to sessionVars, like sessionVars['foo']""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8650","05/27/2015 21:50:14",3,"SecurityFilterMessageProcessor does not support non-blocking. ""SecurityFilterMessageProcessor should implement NonBlockingSupported""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8655","05/28/2015 20:10:59",3,"Update jython to 2.7.0 ""Update to the lastest jython release""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8661","06/01/2015 18:04:49",0,"Typo in AbstractFlowConstruct ""AbstractFlowConstruct validateConstruct method contains an exception message that says: """"Flow exception listener contains and exception strategy that doesn't handle all request"""". Should be """"an exception"""" instead of """"and exception"""".""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8663","06/02/2015 14:33:35",0,"Update jython to 2.5.3 ""Need update jython to 2.5.3 to avoid CVE-2013-2027 vulnerability.""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8666","06/02/2015 21:13:36",5,"Set mime type correct for common files with FTP/File connectors ""The FTP and File connectors should set mime types for common file types correct, including CSV, XML, and JSON.""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8669","06/03/2015 14:44:57",1,"non-blocking processing strategy should only allow direct-threading-profile ""Currently we cannot force the configuration to use direct-threading-profile for all non-blocking flows, this is because thread pool belong to the listener and not to the flow. We need a bigger change that we cannot make now and we can only address it in Mule 4. Because we don't have a concrete use scenario for using non-blocking with a worker threading profile we want to validate that you can only use direct-threading-profile for HTTP listeners when flow's processing strategy is non-blocking. This validation will be on runtime.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8676","06/04/2015 12:27:58",8,"HTTP listener should ignore 'Transfer-Encoding' property as it is a hop-by-hop header ""Transfer-Encoding is a hop-by-hop header and therefore shouldn't really be used by HTTP listener if there is a """"transfer-encoding"""" property present in the outbound property scope to determine response streaming behaviour. Generally current behaviour is fine, but there is one case that is currently incorrect IMO. * We shouldn't stream a String payload when the """"transfer-encoding"""" outbound message property is present. * We shouldn't stream a String payload when the """"transfer-encoding"""" and """"content-length"""" outbound message properties are both present. * Aso, While I think it is probably correct that a String payload should be streamed when a """"transfer-encoding"""" header is configured and streaming mode is 'AUTO'. This is not the way the user should be enabling streaming and I suggest we log an INFO message whenever a transfer-encoding header is set suggesting the user uses the responseStreamingMode attribute instead. Failing test that show this can be found in this branch: https://github.com/mulesoft/mule/compare/MULE-8676 *AUTO Behaviour appears to be inconsistent with HTTP requestor because the presence of both transfer-encoding/content-length headers results in no streaming with requestor, but streaming with listener*""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8677","06/04/2015 12:51:33",8,"HTTP requestor should ignore 'Transfer-Encoding' property as it is a hop-by-hop header ""Transfer-Encoding is a hop-by-hop header and therefore shouldn't really be used by HTTP requestor if there is a """"transfer-encoding"""" property present in the outbound property scope to determine request streaming behaviour. Generally current behaviour is fine, but there is one case that is currently incorrect IMO. * We shouldn't stream a String payload when the """"transfer-encoding"""" outbound message property is present. Also: * Aso, While I think it is probably correct that a String payload should be streamed when a """"transfer-encoding"""" header is configured and streaming mode is 'AUTO'. This is not the way the user should be enabling streaming and I suggest we log an INFO message whenever a transfer-encoding header is set suggesting the user uses the responseStreamingMode attribute instead. * There are currently no tests covering the case when these headers are configured using a , we should add these. *AUTO Behaviour appears to be inconsistent with HTTP listener because the presence of both transfer-encoding/content-length headers results in no streaming with requestor, but streaming with listener* Failing test that show this can be found in this branch: https://github.com/mulesoft/mule/compare/MULE-8676""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8678","06/04/2015 13:14:09",5,"HTTP Requestor should not use Host property. ""If I have configured requestor to hit google.com, i should then not be able to set a host message property or host header (on request builder) that conflicts with google.com. Currently if i hit google.com and i have in my flow then google with receive """"Host: pirulo"""". If the host configured is an ip address then thats different, need to decide if requestor should take """"Host"""" value from message properties or only from response-builder (or neither) in that case.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8680","06/04/2015 19:22:23",8,"Allow TLS context to be shared in a domain ""It'd be good to be able to share a TLS context so that several shared listener configs can use the same one. Another benefit is that all that data (including passwords) will only need to be visible at the domain level, so app developers could use the certs without having access to the perhaps critical data.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8685","06/05/2015 21:16:23",1,"CopyOnWriteCaseInsensitiveMap should be interoperable with a regular map ""CopyOnWriteCaseInsensitiveMap provides improved performance in cases in which reads vastly outnumbers reads. However, it's not good when: * I want to create a CopyOnWriteCaseInsensitiveMap from an existing map * The initial assumption stops being true and I want to transform the CopyOnWriteCaseInsensitiveMap to a regular one This should be supported""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8690","06/08/2015 20:33:11",1,"Remove registry deprecation warnings from log. ""In API Gateway we need to use a registry feature that generates several log entries like: How to reproduce: - Configure GW to use any valid organization - Deploy an API with autodiscovery - Run GW Expected: - The information is not logged at all in no log file. Actual: - The information is logged in mule_ee with WARN level."""," WARN 2015-06-05 16:41:53,968 [Thread-2] org.mule.registry.DefaultRegistryBroker: 3 registries have been registered, however adding registries has been deprecated as of Mule 3.7.0 ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8693","06/09/2015 16:52:48",3,"XA transaction must set tx timeout in XA resources ""XA transaction must set tx timeout in XA resources""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8698","06/09/2015 22:49:32",5,"NonBlockingNotSupportedFunctionalTestCase.aggregator caused InboundAggregationNoTimeoutTestCase to fail. ""Messages created in NonBlockingNotSupportedFunctionalTestCase.aggregator are not related by their rootId which caused InboundAggregationNoTimeoutTestCase to fail.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8700","06/10/2015 22:25:59",3,"Incorrect XSD generated for extension built using extension API ""Reviewing the code or extensions API implementation, found that the XSD sceham generated for the test Heinsenberg extension's killOne operation is wrong. From that snipet, a XML like the following would be valid if checked against a schame validation tool: """," Specify which configuration to use for this invocation. ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8721","06/22/2015 18:18:14",5,"Write test cases for LIfecycleUtils ""Write unit tests for LifecycleUtils class""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8724","06/23/2015 18:21:39",8,"Operation state handling in extensions api ""We need to clearly define how to manage state within operations define with extensions api. Not only define how to implement each use case but also doing it in a way that fits the user mindset. We need: - Global state between operators - Global state per config - Global state per tenant config - State for a particular operation (one per xml element) disregarding the config I'm just trying to list all the cases, then we would have to try to come up with use cases for each use case. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8725","06/23/2015 18:24:51",8,"Implememnt multitenant configuration eviction policy ""When using configs multitenant with extenision API there should be a way to evict (dispose) config that are not longer used. This is critical to avoid OOM and wasting resources for use cases where there may be hundreds or thousands config created over time.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8728","06/23/2015 19:21:15",0,"Apply minor miscellaneous fixes per the ext-api review ""Per the ext-api review, many action items came out which were translated into jira issues. however, there's another bunch which are really small fixes, javadoc enhancements etc, which don't really justify a one issue per fix approach. For those improvements, this is your jira.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8730","06/23/2015 21:08:23",0,"Update LICENSE.txt to fix year and url for third-party software used by Mule ""The LICENSE.txt files refers to year 2009 in CE and 2010 in EE. For example """"Copyright (c) 2003-2009"""" in LICENSE.txt in the root path of the mule repository. Also the URL referencing the information on the license type for each third-party software product used by Mule is pointing to an old link. The correct one now is """"https://developer.mulesoft.com/docs/display/current/Third-Party+Software+In+Mule""""""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8735","06/25/2015 14:01:22",1,"MuleMessage is going to registry for every transformation when extended transformations are used. ""Now there is no longer a transient registry it is critical that we don't lookup objects in the registry in runtime per-message. Not doing so will cause an performance impact and also thread contention at higher concurrencies. org.mule.DefaultMuleMessage#applyAllTransformers org.mule.DefaultMuleContext#getDataTypeConverterResolver""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8736","06/25/2015 17:12:02",8,"Enricher does not propagates datatype ""Message enricher is not propagating datatype when well-known expressions are used (like expressions returning message's payload/properties)""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8738","06/25/2015 20:29:54",1,"No data type resolution accessing flow/session properties using dot notation ""Data type resolution works for session/flow variables on MEL expressions using map syntax (like flowVars['foo']) but does not work when using dot syntax (like flowVars.foo).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8741","06/25/2015 22:24:16",5,"Extract logic for creating implicit configs to a separate class ""The logic for creating implicit configurations is now part of the DefaultExtensionsManager. Would be good to have that extracted to a separate class""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8742","06/26/2015 18:54:16",8,"Cannot build Mule ESB Maven Tools with Java 8 ""When trying to build mule-esb-maven-tools from source code using JDK 8, it fails with the attached error message.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8743","06/26/2015 20:38:02",8,"Mule registry failing to lookup sub-flows ""When trying to do the following ``` context.getRegistry().lookupObjects(SubflowMessageProcessorChainFactoryBean.class); ``` Over a context that has been created with the following xml: ``` ``` The method returns an empty collection. When you do something like ``` context.getRegistry.get(""""firstFlow"""") ``` The bean is returned. It seems as if the problem is with the type lookup""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8753","07/01/2015 14:23:58",5,"Give the Extension model the concept of vendor ""Currently Extension instances are matched by its getName() method. They should also include the concept of vendor and be used for matching purposes as well. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8754","07/04/2015 00:34:42",0,"Broken link in BUILD.md ""The contributing doc link in the build one is broken. It seems the name changed from CONTRIBUTE.md to CONTRIBUTING.md but it wasn't updated in BUILD.md.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8764","07/06/2015 19:10:33",0,"HTTP requester fails to send HTTPS request through a proxy ""When using the new HTTP connector to send HTTPS requests through a proxy, there are some problems depending on the mule version. In 3.6.2, the request is sent correctly through the proxy, but query parameters are lost. In 3.6.x (3.6.3-SNAPSHOT), the request blocks (this started happening after the Grizzly update). The fix for this is to also upgrade async-http-client (that fixes the original query parameter bug), and add test cases for this scenario.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8769","07/08/2015 13:00:21",8,"Loggers memory leak after fixing MULE-8635 ""Changes from MULE-8635 introduced a memory leak where MuleApplicationClassLoaders are not being disposed. MULE-8635 added logic to clean up loggers, but seems that the logic is executed but the memory is not released. To reproduce the issue: _ Start a vainilla mule instance _ Once default app is deployed force a redeploy touching the app's config file Expected behaviour, according to the code, is that after 15 seconds the memory is released, but that does not happen. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8771","07/08/2015 21:30:05",0,"Synchronous until successful should retry on the original message ""When an until successful component is configured to be synchronous, the retries are performed over the same event, so subsequent modifications are performed on the same event. Every retry should be performed over the original message.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8779","07/14/2015 19:05:10",5,"Hostname verification not working correctly with HTTPS proxy ""When configuring the http requester with HTTPS and a proxy, hostname verification is done against the proxy instead of the real host. This makes the request fail, as the certificate doesn't contain the url of the proxy. The verification should be made against the host of the request. This is a bug in AHC, it is fixed in AHC 1.9.27, so a possible solution to this is updating at least to this version.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8784","07/16/2015 16:10:35",5,"Revisit DefaultExtensionManager implicit config test cases considering MULE-8741 ""Now that implicit configs are instantiated by DefaultImplicitConfigurationFactory related tests should be refactored and that class should have its own tests.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8788","07/21/2015 01:51:25",0,"Polling message receiver should unregister scheduler on dispose. ""When you stop a flow programmatically, if it has a polling message receiver, the scheduler is not stopped but it's recreated when it's programmatically re-started, so both schedulers remain active and events are duplicated. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8790","07/21/2015 15:22:22",0,"If multiples HTTP response headers are associated to the same header name, only the first one is mapped to an inbound property. ""HTTP allows to map several header values to the same header name, when we map the HTTP response to a Mule message, headers are mapped to inbound properties, but only the first value for each header name is mapped, next values are discarded.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8792","07/21/2015 21:35:43",0,"ClassPathRegistryBootstrapDiscoverer is not closing resource streams ""ClassPathRegistryBootstrapDiscoverer searches for all the application resources that are bootstrap.properties and opens a stream against each of them. Each stream should be automatically closed after is consumed, but that is not the case and this causes a problem in Windows where the jars containing the bootstrap properties are locked making the redeployment impossible.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8795","07/23/2015 00:52:21",0,"IOUtils#getResourceAsString is not closing streams ""IOUtils#getResourceAsString opens a streams to load application's resources. Those streams should be automatically closed after is consumed, but that is not the case and this causes a problem in Windows where the mentioned resources files are locked making the undeployment impossible.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8796","07/23/2015 02:36:28",0,"Unnecessary tracking of overridden non disposable objects in TransientRegistry ""When adding an object to the registry, if there is a previous object associated with the same key, it will be stored in a Set called lostObjects, this is so in order to be able to call its dispose logic when the application shuts down: https://www.mulesoft.org/jira/browse/MULE-7293 However if the object is not Disposable storing this object won't be necessary, and it could eventually cause an OOM exception because these objects are never cleared. The Registry should remove the previous entries if the stored object is not Disposable ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8798","07/23/2015 15:27:24",1,"Message mime type/encoding must be reset when payload is set without a datatype ""DefaultMuleMessage#setPayload(Object) is maintaining previous mimeType/encoding instead of cleaning it, this is causing issues as transformers read the payload value taking in account the mimeType, which won't match the payload that was set.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8800","07/23/2015 20:52:52",0,"Multipart content should include Content-Disposition header ""As per the RFC (https://tools.ietf.org/html/rfc7578#section-4.2) all parts should include the header Content-Disposition and the part name in it. Parts that represent a file should also contain the filename. Example: Content-Disposition: form-data; name=""""user""""; filename=""""user.txt"""" ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8812","07/30/2015 20:45:22",0,"Multipart content is always sent chunked by listener ""When responding with multipart content, the listener doesn't set any encoding headers (Content-Length, Transfer-Encoding). Grizzly ends up deciding to use chunked and it seems under those circumstances it never sends the """"0"""" ending part.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8813","08/03/2015 15:43:29",0,"Multipart Content-Type header is sent twice when copying attachments ""Observed in the HttpListenerAttachmentsTestCase: attachments are copied so they already have a Content-Type header but when creating the multipart content this header is added again. Example: POST /formDataPath HTTP/1.1 Content-Length: 213 Content-Type: multipart/form-data; boundary=3B0ItAx4ggGN72zKDerT2p0ninKyMiYijUm Host: localhost:14106 Connection: Keep-Alive User-Agent: Apache-HttpClient/4.3.5 (java 1.5) Accept-Encoding: gzip,deflate --3B0ItAx4ggGN72zKDerT2p0ninKyMiYijUm Content-Disposition: form-data; name=""""field1"""" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit yes --3B0ItAx4ggGN72zKDerT2p0ninKyMiYijUm-- HTTP/1.1 200 Content-Length: 197 Content-Type: multipart/form-data; charset=UTF-8 Date: Mon, 03 Aug 2015 14:22:44 GMT --null Content-Type: text/plain; charset=ISO-8859-1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Disposition: form-data; name=""""field1"""" yes --null--""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8816","08/03/2015 23:35:02",0,"Cron job used by multiple Poll component in different projects misfiring ""I have 2 different mule projects created, each containing different cron frequency and names. When the first application is deployed the polling cron is registered, when we deploy the second application then the poller endpoint is registered The problem is, when I un-deploy the first application with which the cron was registered, the second application poller stops working. It's messing up the logging, both the projects have different log4j's , writing to different files. When the first app is deployed it logs fine, as soon as the second one is deployed you'd notice the logs of 2nd application appearing in the first one. INFO 2015-07-23 15:31:52,009 : ------------------------------In for Polling_2 step1 INFO 2015-07-23 15:31:52,009 : ----------In for Polling_1 step2 INFO 2015-07-23 15:31:54,002 : ----------In for Polling_1 step1 INFO 2015-07-23 15:31:54,003 : ----------In for Polling_1 step2 INFO 2015-07-23 15:31:56,006 : ----------In for Polling_1 step1 INFO 2015-07-23 15:31:56,007 : ------------------------------In for Polling_2 step1 INFO 2015-07-23 15:31:56,008 : ----------In for Polling_1 step2 Steps to reproduce: 1 Import both the projects (pollproject1 & pollproject2) on standalone 2. deploye pollproject1.zip on ti the server 3. observe the logs mule-app-poll-1.log, cron should be working every 2 sec. 4. deploy the pollproject2.zip 5. observe the logs mule-app-poll-2.log, cron should be working every 4 sec. 6. undeploy the pollproject1 by deleting the pollproject2-anchor.txt file. 7. observe the logs mule-app-poll-2.log, the messages stop as well.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8819","08/04/2015 16:04:34",0,"MVEL prints stacktraces to the console ""A class in the mule-mvel library is printing the stack traces to the console when it fails to parse an expression. In this case is a XPath expression that tries to parse an xml form a string that is not an xml. If this error is triggered in a ESB running in CentOS, the tanuki wrapper starts to consume increasingly more memory over time leading to a crash. This simple flow can reproduce this error: In the Studio console you should see the printed stack traces in red. The bug is in this line in this class: https://github.com/mulesoft/mvel/blob/master/src/main/java/org/mule/mvel2/optimizers/impl/refl/ReflectiveAccessorOptimizer.java#L437""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8820","08/04/2015 16:19:18",5,"Performance degradation on registry lookup ""Because the mule registry was unified on Spring, lookup and get operations take longer to execute because spring checks for prototypes, etc. We should add a cache to speed up lookups of things that we know are not prototypes""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8821","08/04/2015 20:47:13",8,"Concurrent calls to the OAuth2 authorize MessageProcessor fail when passing different values for accessTokenUrl ""When the authorize MessageProcessor is invoked by 2 different users at the same time and each of those invocations is done with a different value for the accessTokenUrl, the access token request for one of them is made to the wrong url. I am using the salesforce connector v6.2.1 and this is how my authorize call looks like: The flowVar salesforceUrl can take 2 possible values, which are: https://login.salesforce.com (Salesforce Production) https://test.salesforce.com (Salesforce Sandbox) When a user does the OAuth dance to login.salesforce.com at the same time another user does the OAuth dance to test.salesforce.com, one of the dances fail. ------------------------------------------------------------------------------------------ I believe the problem can be found in the way the accessTokenUrl is retrieved and saved by these 2 processors (in mule-devkit-support): - org.mule.security.oauth.processor.BaseOAuth2AuthorizeMessageProcessor - org.mule.security.oauth.processor.OAuth2FetchAccessTokenMessageProcessor The BaseOAuth2AuthorizeMessageProcessor (line 81) saves the accessTokenUrl value in the defaultUnauthorizedConnector object of the OAuth2Manager. The OAuth2FetchAccessTokenMessageProcessor (line 57) obtains an OAuth2Adapter (used to fetch the access token) from the OAuth2Manager. The OAuth2Manager creates the adapter setting the accessTokenUrl (line 256 BaseOAuth2Manager) with the value taken from the defaultUnauthorizedConnector object. https://github.com/mulesoft/mule/blob/mule-3.5.2/modules/devkit-support/src/main/java/org/mule/security/oauth/processor/BaseOAuth2AuthorizeMessageProcessor.java#L81 https://github.com/mulesoft/mule/blob/mule-3.5.2/modules/devkit-support/src/main/java/org/mule/security/oauth/processor/OAuth2FetchAccessTokenMessageProcessor.java#L57 https://github.com/mulesoft/mule/blob/mule-3.5.2/modules/devkit-support/src/main/java/org/mule/security/oauth/BaseOAuth2Manager.java#L256 The defaultUnauthorizedConnector of the OAuth2Manager is common to all events and threads. I believe that when 2 users are doing the oauth dance at the same time the accessTokenUrl value of the defaultUnauthorizedConnector is being overwritten by the second user before the first is able to fetch the access token.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8822","08/05/2015 00:55:31",5,"OAuth2 Refresh token logic fails after restart for preexistent connection ""This issue is related to the problem encountered in JIRA MULE-8277. After restarting an application that uses the Box Connector, the first time a box request is made with a preexisting Box connection, that has an expired access token in its OAuthState, a refresh token process is triggered that does not attempt to save the refresh and access token obtained from box in the connector's ObjectStore. The Box connector postAuthorize method invokes one of the connector's processors in order to retrieve the id of the user after the OAuth2 dance for identification purposes. That request within the postAuthorize triggers the first refresh token process for the connector on its first use after restart. The way to reproduce the issue would be: - Run a mule application on mule 3.6.2 with the Box Connector and a persistent Objectstore for it - Do the OAuth dance with a Box user using the authorize MessageProcessor. - Wait until the Box access token expires or modify it in the OAuthState saved in the Objectstore to make it invalid - Restart the mule application and attempt to run a Box MessageProcessor like twice. (The first attempt should refresh but not save and the second should fail to refresh)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8823","08/05/2015 18:05:19",8,"Unable to deploy Application in Mule 3.7.0 ""Nowadays, if you want to create a proxy, you have to specify the port name and the soapVersion for each binding. This information is provided by the wsdl, so it shouldn't be required, the proxies should detect them automatically. As a consequence, if you have an API with multiple ports, one of them receiving a SOAP 1.1 envelope, and other one receiving a SOAP 1.2 envelope, and if you don't specify the port and the soapVersion in both proxies (service and client) you will not be able to send a SOAP 1.2 message. This means that a simple proxy cannot be used with both types of SOAP versions. ""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8827","08/06/2015 19:29:03",5,"Tests for HTTP connector in HttpSecurityFilterFunctionalTestCase depend on tests executed one the HTTP transport ""org.mule.module.cxf.HttpSecurityFilterFunctionalTestCase is executed on flows using HTTP transport and HTTP connector. All test pass under the current configuration as the HTTP transport tests are executed before the HTTP connector's. Running the connector test only or switching the order breaks the following tests: * testAuthenticationAuthorisedGetHttps * testAuthenticationAuthorisedPostHttps * testAuthenticationFailureBadCredentialsGetHttps * testAuthenticationFailureBadCredentialsPostHttps""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8829","08/11/2015 15:40:42",0,"NTLM proxy authentication in HTTP Requester sends basic authentication ""When a NTLM proxy is set up, the actual authentication done is Basic. This is a problem in the Grizzly provider of async-http-client.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8833","08/12/2015 16:02:42",1,"Require jdk8 ""Make jdk8 required and set the compilation level to 1.8""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8834","08/12/2015 16:16:23",1,"Fix ext-api version in 3.x ""Further development of the ext-api will continue on the Mule 4 branch and thus the version of it should be fix for 3.x""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8844","08/14/2015 21:14:05",0,"until-successful should propagate the root exception ""Currently until-successful does not propagate the root cause of the exception to the outside of the scope. There's a workaround written by John D""""Emic, it just needs to be merged to the core: https://gist.github.com/johndemic/5670325 ""","",0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8854","08/24/2015 14:56:53",1,"Exceptions are wrapped in extensions API ""There's a problem when throwing certain exceptions. I was invoking a non existent method in the operation of an extension, expecting the NoSuchMethodException to be wrapped by a MessagingException. The result was a MessagingException wrapping a UndeclaredThrowableException that then contained my exception. I tracked it down to the rethrowRuntimeException method in class org.springframework.util.ReflectionUtils: public static void rethrowRuntimeException(Throwable ex) { if (ex instanceof RuntimeException) { throw (RuntimeException) ex; } if (ex instanceof Error) { throw (Error) ex; } throw new UndeclaredThrowableException(ex); } So it seems this involves all exceptions that are not RuntimeException or Error.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8861","08/25/2015 13:37:17",1,"Remove builders module ""Remove builders module from codebase and distributions""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8863","08/25/2015 13:41:55",1,"Remove client module ""Remove client module from codebase and distributions""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8864","08/25/2015 13:46:15",13,"[Spike] Migrate Http Connector to extensions API ""Replace current HTTP connector with a version developed using extensions API""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8865","08/25/2015 13:53:20",8,"Migrate Oauth module to extensions API ""Replace current oauth module with a version developed with extensions API""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8867","08/25/2015 13:55:27",2,"Remove spring-extras module ""Remove spring-extras module from codebase and distributions""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8897","08/26/2015 16:49:31",1,"mule-maven-plugin CloudHub deployment fails when domain is already in use ""When trying to deploy an application to CloudHub, deployment fails if the domain is already in use. Plugin should validate that the domain is free before trying to deploy the application.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8898","08/26/2015 22:15:00",0,"mule-maven-plugin CloudHub deployment rollback not working properly ""Consider the following scenario: 1. You have application A & application B deployed on your CloudHub environment 2. You use the Maven plugin to redeploy app A & B. 3. App A deploys successfully but app B fails because the file doesn't exist or because of a connection issue. Current behavior: - App A will be rolled back and deleted from CloudHub (even though it existed previously) - App B will remain on CloudHub with """"Undeployed"""" status. Expected behavior: A better solution would be to leave App A as it is, since it deployed correctly, and roll back deployment of App B which failed. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8899","08/27/2015 17:42:41",0,"Update Groovy to version 2.4.4 ""There is a new vulnerability detected on Groovy (CVE-2015-3253) which is fixed on 2.4.4 version. Need to update to it""","",0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8901","08/28/2015 15:56:06",0,"Upgrade async-http-client to 1.9.31. ""Once it is available, we should upgrade to that version to fix MULE-8282 and MULE-8829.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8904","08/31/2015 17:05:11",3,"mule-maven-plugin CloudHub redeployment configuration loss ""When you use the Maven plugin to redeploy an application with the redeploy=true flag, the existing application gets deleted before the updated application is deployed. This behavior causes all CloudHub configured properties to be lost, and the plugin currently supports only a few of the configurations to be set on the POM file. CloudHub configurations such as Properties, Insight and Logging need to be reconfigured every time the application is deployed. Ideally, we should be able to specify all configurations so they can be updated through the POM file, or the Maven plugin should redeploy without deleting the existing application so we don't lose the configuration.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8908","08/31/2015 18:35:24",8,"Add the concept of ExceptionEnricher in Ext-Api ""Add the concept of an ExceptionEnricher in the ext-api which gets invoked whenever an operation throws an exception. This is useful to avoid repetitive try..catch blocks. It would be defined by an interface roughly looking like this Then you can declare it at an Extension level: Or at a configuration level: A simple implementation would look similar to this: """," public interface ExceptionEnricher { Exception enrichException(Exception e); } @Extension @Operations(Operations.class); @OnException(handler = PetExceptionEnricher.class) public class PetStoreConnector { … } @Configuration(name=""""pooled-config"""") @PooledConnector(PetClientConnectionHandler.class) @OnException(handler = PooledPetConnectionExceptionEnricher.class) public class PooledConnectionConfig { } public class PetExceptionEnricher implements ExceptionEnricher { public Exception enrichException(Exception e) { if (irrelevantException(e)) { logger.error(e.getMessage()) } else if (e instanceof SocketException) { return new ConnectionException(e); // wants to reconnect } else { return e; } } } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8909","08/31/2015 18:36:41",8,"Implement Reconnection on the Ext-Api ""Implement Reconnection on the Ext-Api""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8910","08/31/2015 18:58:20",8,"Implement connection validation policy on Ext-Api ""Create a mechanism so that connections can be validated to still be functional. Notice that this is not design time connection testing but runtime validation of a connection being usable. If the validation fails, then the reconnection workflow should be triggered""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8915","09/02/2015 16:00:47",0,"Add Visibility on which transformers are selected ""Right now users don't have visibility on which transformers are selected when the user don't specify one. To troubleshoot this the user has no other option than debug Mule code. Solution could be to log with debug level which transformers are selected and why.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8916","09/02/2015 16:04:07",2,"Unclear message when more than one transformer is available ""When Mule finds more than one transformer flow execution fails. In this case we should show more information about the problem to the user, like why those transformers where selected and what to do to solve the problem.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8917","09/02/2015 16:05:29",0,"JMS transformer is selected even when not using JMS ""Even when JMS is not being used JMS transformer is selected.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8919","09/02/2015 18:54:50",1,"mule-maven-plugin CloudHub deployment does not check for file existence ""When you try to deploy a Mule application through a ZIP file, the Maven plugin does not check if the file actually exists. If it is an unexistent file, the deployment process starts anyway and the application is created in CloudHub using the name of the given unexistent file. The build fails because it can't deploy the application but the changes in CloudHub are already done and they're not rolled back. The expected behavior is that the plugin checks if the file exists before making any change in CloudHub. If not, it should throw an exception and fail the build.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8931","09/02/2015 22:18:31",0,"Change ""release"" profile in EE with a new ""distributions"" profile ""Change """"release"""" profile with """"distribution"""" profile in EE to avoid the need to use the property skipDistributions=false when we wanted to build the artifacts of EE (there we use the plugins included in the profile release of CE but we didn't want to build the distributions). *UPDATE*: After the changes: * -Prelease: you can use the -Prelease which will activate the profile release of CE without adding the distribiutions module of EE * -Pdistributions: will only add the distributions module in EE * -DbuildDistributions=true : will activate the release and distributions profile mentioned before. ""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8922","09/03/2015 13:47:23",0,"Enricher broken when target expression references a key inside a map ""Enriching message properties which are maps like does not work on 3.7.x branch. Expected behaviour is that after the enricher, product property contains both 'style' and 'items' keys, but the map is replaced with the 'items' value """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8927","09/03/2015 18:35:43",0,"Have to manually encode @ (or other special characters) when setting the username/password for an smtp sender ""See: MULE-6279 and MULE-6139""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8929","09/07/2015 14:49:13",0,"Proxy validation looses XML tag when payload is body ""When the body tag is immediately followed by another opening tag, said tag is lost and the resulting message is incomplete. This seems to be caused by the StartBodyInterceptor which consumes it and since the ReversibleXMLStreamReader is added after it, that event is not captured.""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8933","09/08/2015 20:30:05",0,"MEL: Concat expression with an empty term throws obscure error ""When evaluating a MEL expression that happens to be invalid, the error message shows what was the expression that caused the error. However, for some invalid expressions (i.e: ) only the message """"not an statement"""" is logged, with no indication of what was the expression. On non-trivial applications, this makes it very difficult to find the source of the error. """," 'some string'+ ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8936","09/11/2015 19:47:59",3,"The 'protocol' attr in an http:request-config element does not support '${propertyname}' as value ""When using the http:request-config element in the flow.xml, the 'protocol' attr only supports HTTPS or HTTP, it does not support a property placeholder like: Not only Studio complains of this issue, but also mule does when you start the application."""," ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8939","09/14/2015 17:49:09",5,"Release MVEL 2.1.9-MULE-008 ""Perform a release of MVEL that contains the fix for MULE-8831 # Update pom.xml to meet Maven Central repository requirements # Update build plan to deploy to Maven Central # Sign the jar using gpg # Add javadoc plugin for releases ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8945","09/16/2015 16:11:07",0,"Exceptions in scatter-gather routes are difficult to find ""When an exception happens in a route of a scatter-gather, a composite exception is created and thrown. Even if this composite has the actual exceptions of the route(s) inside of it, they are not being sent to the log by default (only logged at DEBUG level). For troubleshooting purposes, it would make sense to have at least the original exception message logged at the ERROR level. Also, when the exception in the route is not a MuleException (i.e.: a MEL exception), it is swallowed and not even an empty composite exception is thrown. (MULE-7975)""","",0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8946","09/16/2015 16:43:33",3,"Extensions API should know the Mule API ""Ext-Api should not depend on mule-core. However, now that 4.x will contain a mule-api jar, it makes no sense to shield the ext-api from concepts like the MuleEvent. However, ext-api is advancing faster than the mule-api which is not available yet. For that reason, components such as the ExtensionsManager or the ConfigurationProvider receive the MuleEvent as simply an Object and then cast it on the implementation. When the mule-api becomes available with a well defined MuleEvent, those Objects should be actually typed as MuleEvent. Although this issue uses the MuleEvent as an example, the extent of this goes beyond it and included LIfecycle, MuleMessage, etc. TODO: - Update MetadataResolvingException to extend MuleException ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8951","09/17/2015 15:30:36",0,"SFTP connection leak when the user doesn't have permissions ""When the user has no access to a file inside the folder being polled, an exception is thrown but the client used to retrieve the file is not released. This causes a connection leak (or a deadlock when using a connection pool). Additionally, the exception is not logged in 3.7.1.""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8953","09/17/2015 20:52:01",8,"Use java.util.Base64 for encoding/decoding instead of custom code ""Java 8 provides a Base64 encoder/decoder (java.util.Base64) that outperforms mule's current implementation avg. execution time by 18%. Apart for the performance gain ,we would also be relying on a standard implementation rather than a custom one.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8955","09/18/2015 17:41:33",0,"MEL: Concurrent use of a function variable fails ""There seems to be a concurrency issue with either MVEL or MEL. Error given: Steps to reproduce: 1. Run the application in configuration: 2. Do a request to http://localhost:8888/meltest 3. It should work. 4. Now run it with concurrency (i.e.: with jmeter). 5 simultaneus threads should be enough. """," Root Exception stack trace: java.lang.ClassCastException: org.mule.mvel2.ast.PrototypalFunctionInstance cannot be cast to org.mule.mvel2.ast.Function at org.mule.mvel2.optimizers.impl.refl.nodes.DynamicFunctionAccessor.getValue(DynamicFunctionAccessor.java:37) at org.mule.mvel2.optimizers.impl.refl.nodes.VariableAccessor.getValue(VariableAccessor.java:37) at org.mule.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:108) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8956","09/21/2015 14:31:23",0,"XPath expression right after blocking http request can't access the http response payload ""When running the given mule app, the xpath expression should be able to access the payload returned by the """"remote"""" http call. On non-blocking requests this doesn't happen because the non-blocking handling method calls which correctly sets the environment that the XPath evaluator uses. This can be worked around just by adding a logger right after the http request."""," RequestContext.setEvent(muleEvent); ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8958","09/22/2015 18:56:48",8,"Allow insecure HTTPS connections ""It is now impossible to disable all certificate validations in HTTPS, which would be useful for QA and early development scenarios. Though -Dcom.ning.http.client.AsyncHttpClientConfig.acceptAnyCertificate=true is intended for this, we are always adding our own default TlsContext when the protocol is HTTPS and thus bypassing that AHC logic.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8976","10/02/2015 15:10:21",0,"Logging of message reception is written to domain log instead of app log when sharing jms connector ""When I run the project (in standalone server), the first log messages are routed to the application log file (as expected). The are created by thread [ActiveMQ Session Task-1] After some (short) time, the log message are routed to the log file of the domain (not expected). In the domain log file I have never seen a log message from Task-1, only from Task-2 to Task-5. This bug looks like MULE-7383, but this one affects jms instead of http. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8987","10/06/2015 18:02:59",0,"Improve truncated stack trace in exception log ""The 3-line truncated stacktrace should show only mule code entries, in order to provide useful context about the exception.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-8988","10/06/2015 18:44:16",0,"When logging a payload as part of an exception message, show its content rather than its class ""When logging an exception, unless the payload is consumable, its content should be logged instead of just its class name so the developer can have a better understanding what caused the exception.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9009","10/16/2015 07:35:12",0,"[FIX INCLUDED] MimeType is not set in DataTypeFactory ""[FIX INCLUDED] Steps to reproduce: Have a custom transformer which converts List to List List will have type as java.util.List, itemType as ABC and mime as application/abc List will have type as java.util.List, itemType as XYZ and mime as application/xyz Because of the below bug None of the Collection based transformers are invoked because of the mime set to MimeTypes.ANY I am giving the fix below and i have tested that. MimeType is not set in DataTypeFactory.getObjectMimeType Line number 128. Existing code: if (value instanceof MuleMessage) { MuleMessage mm = (MuleMessage) value; mm.getDataType().getMimeType(); } Fixed code: if (value instanceof MuleMessage) { MuleMessage mm = (MuleMessage) value; mime = mm.getDataType().getMimeType(); }""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9011","10/16/2015 15:42:30",5,"Expand Flowstack functionality ""The list of processors that were executed as part of a message should contain all processors executed, for all flows, so that it can be queried even after the message processing finished.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9012","10/16/2015 16:00:05",3,"Include the name of the xml file where an element is declared when logging the element path ""Currently, only the mule path and the application name are being logged when logging the path of an element as part of an exception message. For large applications composed of many files, the name of the xml file will be helpful to better find the component where the exception happened.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9016","10/21/2015 19:12:27",0,"Processing XLSX files that have comments in mule fails ""The failure is a NPE caused by the fact that XmlBeans.NO_TYPE is null. Issue is a wrong use of BuiltinSchemaTypeSystem in mule-common.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9018","10/22/2015 20:28:32",0,"Upgrade Apache Geronimo libraries to latest versions ""Upgrade Apache Geronimo libraries to latest versions | *Artifact* | *Current* | *New* | | geronimo-j2ee-connector_1.5_spec | 1.1 | 2.0.0 | | geronimo-jms_1.1_spec | 1.1 | 1.1.1 | | geronimo-jaxrpc_1.1_spec | 1.1 | 2.1 |""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9020","10/22/2015 22:00:53",0,"Upgrade BouncyCastle libraries to latest version ""We need to upgrade BouncyCastle libraries to latest artifacts and versions as follows: | *Artifact* | *Version* | *New artifact* | *New version* | | bcmail-jdk16 | 1.46 | bcmail-jdk15on | 1.46 | | bcpg-jdk16 | 1.46 | bcpg-jdk15on | 1.50 | | bcprov-ext-jdk16 | 1.46 | bcprov-ext-jdk15on | 1.50 | | bcprov-jdk16 | 1.46 | bcprov-jdk15on | 1.50 | | bctsp-jdk16 | 1.46 | bctsp-jdk15on | 1.46 |""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9025","10/27/2015 15:04:35",0,"Changes on domain are not being registered by applications ""When updating a domain config that causes a redeploy, the related apps do not see the new changes in the domain.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9032","11/02/2015 15:29:03",5,"Upgrade BouncyCastle libraries to version 1.54 or newer ""We should consider upgrading BouncyCastle to version 1.54 to leverage the latest bugfixes. This is a security related library and we should always use the latest stable version.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9038","11/05/2015 16:15:38",3,"Build Mule 3.7.3 final binaries ""Build Mule 3.7.3 final binaries""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9041","11/06/2015 18:34:10",0,"Keep property with original remote address even if X-Forwarded-For present ""The HTTP module allows clients to spoof the remote address by setting whatever value in the X-Forwarded-For header. For instance, if one makes this request: Then the inbound properties show this: This allows any client to forge a fake remote address. Note: This behaviour is intentional, as per this commit: https://github.com/mulesoft/mule/commit/6421194922b0644687e68a57d753b8eb4bae3db6 However this poses the security issue described above. The solution would be: http.remote.address is always the immediate IP (proxy or not). If the X-Forwarded-For header is present, an inbound property will be included in the message with its value."""," curl http://localhost:8082/test --header """"X-Forwarded-For: hola"""" http.remote.address=hola ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9044","11/09/2015 12:49:47",0,"HTTP Listener returning 500 instead of 400 on invalid Content-Type ""When an error occurs handling a request, the listener returns a 400/500 but since the error is not logged, there's no way of knowing what went wrong. This happens for example when sending a request with an invalid Content-Type header, when additionally a 500 instead a 400 is sent.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9045","11/09/2015 12:53:44",0,"HTTP Listener not sending reason phrase when error occurs ""When an error occurs handling a request, the HTTP listener responds with a 400/500 but since no reason phrase is set it sends the default """"OK"""" which is confusing.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9047","11/10/2015 14:28:50",13,"Review pooling profile and pooling mechanism ""Review if we want to keep using apache as a pooling library and if we can simplify the pooling profile concept""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9050","11/11/2015 20:41:49",0,"Jersey module doesn't support multipart requests ""When trying to use a multipart request against a Jersey component it fails to start Mule with this error: This is happening because multipart is not registered as valid type."""," 1. Validation of the application resource model has failed during application initialization. [[FATAL] No injection source found for a parameter of type public javax.ws.rs.core.Response com.mycompany.MyRestfulBean.createJob(java.util.List,java.lang.String,javax.ws.rs.core.UriInfo) throws java.io.IOException,java.net.URISyntaxException at index 0.; source='ResourceMethod{httpMethod=POST, consumedTypes=[multipart/form-data], producedTypes=[text/plain], suspended=false, suspendTimeout=0, suspendTimeoutUnit=MILLISECONDS, invocable=Invocable{handler=ClassBasedMethodHandler{handlerClass=class com.mycompany.MyRestfulBean, handlerConstructors=[org.glassfish.jersey.server.model.HandlerConstructor@6ce5acd]}, definitionMethod=public javax.ws.rs.core.Response com.mycompany.MyRestfulBean.createJob(java.util.List,java.lang.String,javax.ws.rs.core.UriInfo) throws java.io.IOException,java.net.URISyntaxException, parameters=[Parameter [type=interface java.util.List, source=images, defaultValue=null], Parameter [type=class java.lang.String, source=jobType, defaultValue=null], Parameter [type=interface javax.ws.rs.core.UriInfo, source=null, defaultValue=null]], responseType=class javax.ws.rs.core.Response}, nameBindings=[]}'] (org.glassfish.jersey.server.model.ModelValidationException) org.glassfish.jersey.server.ApplicationHandler:465 (null) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9051","11/12/2015 20:26:49",0,"ForEach fails to provide path elements when not initialised ""When trying to call the method: addMessageProcessorPathElements In a ForEach object that has not been init the method fails with: The reason for it is that, foreach is expecting to be initialised at this time, thus having at least 3 MP. When not init the for each only contains those MP defined in the XML with out the splitter and the filter. So in the event the for each only contains 1 mp it fails. The class ForEach should validate the size of the list, or at least know if it has been init in order not to fail. """," Caused by: java.lang.IllegalArgumentException: fromIndex(1) > toIndex(0) at java.util.ArrayList.subListRangeCheck(ArrayList.java:964) at java.util.ArrayList.subList(ArrayList.java:954) at org.mule.routing.Foreach.addMessageProcessorPathElements(Foreach.java:143) List mps = getOwnedMessageProcessors().subList(1, getOwnedMessageProcessors().size() - 1); ",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9053","11/13/2015 13:13:32",0,"HTTP Listener accepting invalid content-type without body and returning 500 with body ""When an invalid Content-Type is sent on a request to the HTTP listener, it is only rejected if the request has a body and with a 500 instead of a 400. If there is no body, the request goes through and (if the Content-Type is not removed or changed) fails trying to create the HTTP response. We should reject such requests with a 400, just like in MULE-9044.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9060","11/16/2015 13:28:28",3,"Update commons-collections version ""The Apache commons-collections library (4.0, 3.2.1 and older) has a vulnerability in the InvokerTransformer object where serializable collections are allowed to execute arbitrary Java code, whenever the library is in the classpath. If we have an endpoint that receives a serializable object, that object can invoke arbitrary Java code at the moment we try to deserialize it. We should upgrade to the fixed version (3.2.2) as soon as it's available or remove the class from our classpath. ""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9061","11/16/2015 14:40:45",0,"RandomAccessFileQueueStore leak files and space after being disposed ""When a RandomAccessFileQueueStore is disposed, the contents of the queue files are cleared but the files themselves are recreated, causing them to accumulate. Additionally, the CRL file is never clearer not deleted, causing a disk space leak which although small, adds up and can become significant""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9062","11/16/2015 15:24:55",0,"Dropping new domain.zip file does not redeploy apps associated with that domain ""Dropping a new domain.zip for an existing domain does not trigger application redeployment. To reproduce: 1) Start Mule 2) Drop domain zip in /domains 3) Drop app zip (dependant on the domain) in /apps 4) Drop a new version of the domain zip The domain will be redeployed, but the application is not seeing the changes in the domain.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9065","11/16/2015 18:24:32",5,"IndexOutOfBoundsException when header key has empty value ""When an empty header is sent to a Jetty endpoint, it fails with said exception.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9066","11/16/2015 18:24:46",1,"set-property throws runtime exception if the propertyName is empty ""When using set-property, if the propertyName is empty, the schema consider it as a valid value, but every attept to use it throws a java.lang.StringIndexOutOfBoundsException. As a side effect, this also makes the request fail if the set-property is in a flow which contains an http:listener element. The solution IMHO would be changing the mule.xsd schema and adding a minLength value to the set-property element. How to reproduce: - Use the following mule-config. The deployment of the app will be successful. When making a request, the config produces the following exception, and the response *never comes back*. """," ERROR 2015-11-16 14:42:01,527 [[set-property-error].HTTP_Listener_Configuration.worker.01] org.mule.exception.DefaultMessagingExceptionStrategy: Caught exception in Exception Strategy: String index out of range: 0 java.lang.StringIndexOutOfBoundsException: String index out of range: 0 at java.lang.String.charAt(String.java:658) ~[?:1.7.0_71] at org.glassfish.grizzly.http.HttpHeader$Builder.handleSpecialHeaderAdd(HttpHeader.java:1240) ~[grizzly-http-2.3.21.jar:2.3.21] at org.glassfish.grizzly.http.HttpHeader$Builder.header(HttpHeader.java:1134) ~[grizzly-http-2.3.21.jar:2.3.21] at org.mule.module.http.internal.listener.grizzly.BaseResponseCompletionHandler.buildHttpResponsePacket(BaseResponseCompletionHandler.java:34) ~[mule-module-http-3.7.0.jar:3.7.0] at org.mule.module.http.internal.listener.grizzly.ResponseCompletionHandler.(ResponseCompletionHandler.java:52) ~[mule-module-http-3.7.0.jar:3.7.0] at org.mule.module.http.internal.listener.grizzly.GrizzlyRequestDispatcherFilter$1.responseReady(GrizzlyRequestDispatcherFilter.java:96) ~[mule-module-http-3.7.0.jar:3.7.0] at org.mule.module.http.internal.listener.HttpMessageProcessorTemplate.sendResponseToClient(HttpMessageProcessorTemplate.java:99) ~[mule-module-http-3.7.0.jar:3.7.0] at org.mule.execution.AsyncResponseFlowProcessingPhase.runPhase(AsyncResponseFlowProcessingPhase.java:83) ~[mule-core-3.7.0.jar:3.7.0] at org.mule.execution.AsyncResponseFlowProcessingPhase.runPhase(AsyncResponseFlowProcessingPhase.java:38) ~[mule-core-3.7.0.jar:3.7.0] at org.mule.execution.PhaseExecutionEngine$InternalPhaseExecutionEngine.phaseSuccessfully(PhaseExecutionEngine.java:65) ~[mule-core-3.7.0.jar:3.7.0] at org.mule.execution.PhaseExecutionEngine$InternalPhaseExecutionEngine.phaseSuccessfully(PhaseExecutionEngine.java:69) ~[mule-core-3.7.0.jar:3.7.0] at com.mulesoft.mule.throttling.ThrottlingPhase.runPhase(ThrottlingPhase.java:185) ~[mule-module-throttling-ee-3.7.0.jar:3.7.0] at com.mulesoft.mule.throttling.ThrottlingPhase.runPhase(ThrottlingPhase.java:1) ~[mule-module-throttling-ee-3.7.0.jar:3.7.0] at org.mule.execution.PhaseExecutionEngine$InternalPhaseExecutionEngine.process(PhaseExecutionEngine.java:114) ~[mule-core-3.7.0.jar:3.7.0] at org.mule.execution.PhaseExecutionEngine.process(PhaseExecutionEngine.java:41) ~[mule-core-3.7.0.jar:3.7.0] at org.mule.execution.MuleMessageProcessingManager.processMessage(MuleMessageProcessingManager.java:32) ~[mule-core-3.7.0.jar:3.7.0] at org.mule.module.http.internal.listener.DefaultHttpListener$1.handleRequest(DefaultHttpListener.java:126) ~[mule-module-http-3.7.0.jar:3.7.0] at org.mule.module.http.internal.listener.grizzly.GrizzlyRequestDispatcherFilter.handleRead(GrizzlyRequestDispatcherFilter.java:83) ~[mule-module-http-3.7.0.jar:3.7.0] at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119) ~[grizzly-framework-2.3.21.jar:2.3.21] at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:283) ~[grizzly-framework-2.3.21.jar:2.3.21] at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:200) ~[grizzly-framework-2.3.21.jar:2.3.21] at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:132) ~[grizzly-framework-2.3.21.jar:2.3.21] at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:111) ~[grizzly-framework-2.3.21.jar:2.3.21] at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77) ~[grizzly-framework-2.3.21.jar:2.3.21] at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:536) ~[grizzly-framework-2.3.21.jar:2.3.21] at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:112) ~[grizzly-framework-2.3.21.jar:2.3.21] at org.mule.module.http.internal.listener.grizzly.ExecutorPerServerAddressIOStrategy.run0(ExecutorPerServerAddressIOStrategy.java:102) ~[mule-module-http-3.7.0.jar:3.7.0] at org.mule.module.http.internal.listener.grizzly.ExecutorPerServerAddressIOStrategy.access$100(ExecutorPerServerAddressIOStrategy.java:30) ~[mule-module-http-3.7.0.jar:3.7.0] at org.mule.module.http.internal.listener.grizzly.ExecutorPerServerAddressIOStrategy$WorkerThreadRunnable.run(ExecutorPerServerAddressIOStrategy.java:125) ~[mule-module-http-3.7.0.jar:3.7.0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [?:1.7.0_71] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [?:1.7.0_71] at java.lang.Thread.run(Thread.java:745) [?:1.7.0_71] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9067","11/16/2015 19:49:27",0,"Add HTTP (transport/module) tests of empty headers ""We need to add tests on empty headers to ensure all HTTP components behave the same way.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9072","11/17/2015 18:22:43",8,"Cleanup MuleSession ""Cleanup MuleSession, moving anything that can be moved to compatibility module and ensure it's not exposed as part of mule-api.""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9074","11/17/2015 20:58:09",5,"WebService Consumer: xsd:import for external resources through HTTP fails with java.io.FileNotFoundException ""WS consumer can't handle imported or included wsdl/xsd files when they are located externally.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9075","11/17/2015 21:06:29",3,"Remove RC4 cipher suites from tls-default.conf ""As per https://tools.ietf.org/html/rfc7465 we should remove this cipher suites from our suggested ones.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9076","11/18/2015 15:52:03",8,"Spike: Remove MuleEvent dependency on MuleContext if possible. "".""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9078","11/18/2015 16:07:34",5,"Add missing model validators ""The following ModelValidators are missing and should be added: * Validate that all configuration models can be used with all operation models. This comes to the fact that an operation can require a connection type for which the available connection providers might be incompatible with certain configs (Moved to MULE-9214) * Validate that no parameters, configs nor operations are named as any of the following reserved words: name, config, configRef, connection. * Validate clashes on @ParameterGroup fields * Move some validations currently in ImmutableParameterGroup to validators * Validate that all connection providers have different names. Hint the user into using the @Alias annotation to customize the provider's names. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9081","11/18/2015 16:51:42",0,"Errors on Extension code cannot be shown properly ""When building an extension, the errors should show exactly the line of code and java element (method, parameter, field, annotation, annotation field or others) that has the error. Currently we just show a plain text message. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9083","11/18/2015 17:57:59",13,"Add the concept of Message Sources in the Ext-Api ""Allow the Ext-Api and the Ext-Framework to define and implement message sources""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9084","11/18/2015 18:13:12",13,"Allow SDK to generate Studio support ""Allow the new SDK to optionally generate Studio editors and update site. On a first pass we only require functionality similar to that provided by Devkit. We'll iterate more in the future""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9112","11/19/2015 14:54:17",5,"Remove SSL transport ""1.2.14 Remove SSL transport""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9113","11/19/2015 14:55:15",5,"Remove TCP transport ""1.2.13 Remove TCP transport""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9115","11/19/2015 14:56:34",8,"Remove JMS transport ""1.2.17 Remove JMS transport""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9116","11/19/2015 14:56:57",3,"Remove annotations module ""1.2.18 Clean up annotaitons module""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9120","11/19/2015 14:59:45",2,"Remove devkit-support module ""Remove module from the Mule 4 project""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9123","11/19/2015 15:01:21",0,"Discuss managment support for extensions and JMX support ""Discuss managment support for extensins and JMX support""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9127","11/19/2015 15:03:58",0,"Define future of tomcat module "" Define future of tomcat module""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9138","11/20/2015 17:27:42",0,"Fix flaky DeploymentServiceTestCase ""Fix flaky test redeployModifiedDomainAndRedeployFailedApps in DeploymentServiceTestCase.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9140","11/20/2015 21:44:33",0,"""host"" header expected even for HTTP 1.0 clients ""A minimal HTTP 1.0 request that doesn't include the Host header makes the listener to throw a 500 HTTP response status, triggering the issue. The Host header should be mandatory only in HTTP 1.1. Also, 1.1 clients omitting the host header should receive a 400 status instead of the 500 that is being sent.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9142","11/23/2015 12:37:01",8,"Transformed value is lost when transformed value datatype does not match the expected one ""After applying a transformation, the TransformationService checks whether or not the resulting value is of the expected type and if it does not match, then it must throw an exception. The problem is that, as the message is immutable, in cases when the payload is consumable both the original and the transformed values will be lost. As the transformation service throws an exception, that is the only place where a message containing the new payload can be placed.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9144","11/23/2015 20:04:58",0,"SFTP Request doesn’t autoDelete original file ""When using MuleClient to use a SFTP endpoint, autoDelete property of the endpoint or the connector is being ignored, behaving as if it were false.""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9146","11/24/2015 15:37:08",0,"AsyncUntilSuccessful uses a fixed thread pool ""When defining a threading profile for a asynchronous until successful the concurrent threads won't pass the value defined for maxThreadsIdle, when it should grow up to maxThreadsActive. This is because AsynchronousUntilSuccessfulProcessingStrategy creates a scheduled executor that has a fixed thread pool by definition. From https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ScheduledThreadPoolExecutor.html bq. While this class inherits from ThreadPoolExecutor, a few of the inherited tuning methods are not useful for it. In particular, because it acts as a fixed-sized pool using corePoolSize threads and an unbounded queue, adjustments to maximumPoolSize have no useful effect. Additionally, it is almost never a good idea to set corePoolSize to zero or use allowCoreThreadTimeOut because this may leave the pool without threads to handle tasks once they become eligible to run.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9148","11/24/2015 19:07:23",0,"Fix flaky ProcessorsTraceTestCase / MessageProcessorNotificationTestCase ""Fix flaky tests""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9149","11/24/2015 19:17:40",3,"Upgrade antlr to 3.5 ""We need to upgrade this dependency to match the one in mule-common and avoid conflicts. The affected modules would be drools and jBPM.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9153","11/25/2015 17:20:18",2,"Add support for interfaces as parameters of an @Operation ""When using interfaces as parameters of an operation, it fails to generate the Extension module giving a missleading wrong error message. Whe should add the support to have interfaces as parameters. Current error log: """," //Pojo code public class SimplePojo { @Parameter private String someField; public String getSomeField() { return someField; } public void setSomeField(String someField) { this.someField = someField; } } //Interface code public interface MyInterface { String getSomeMessage(String orignal); } //@Operations code public class ExtensionOperations { @Operation public SimplePojo pojoOperation(SimplePojo pojo) { return pojo; } @Operation public void interfaceOperation(MyInterface callback){ } } org.mule.extension.api.exception.IllegalModelDefinitionException: Extension 'first' defines a operation of name 'operation' which contains a parameter of complex type 'class org.mule.module.extension.firstextension.SimplePojo'. However, operation of name 'interfaceOperation' defines a parameter of the same name but type 'org.mule.module.extension.firstextension.MyInterface'. Complex parameter of different types cannot have the same name. at org.mule.module.extension.internal.introspection.validation.NameClashModelValidator$ValidationDelegate.lambda$validateTopLevelParameters$37(NameClashModelValidator.java:137) at org.mule.module.extension.internal.introspection.validation.NameClashModelValidator$ValidationDelegate$$Lambda$26/490407158.accept(Unknown Source) at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:512) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:502) at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) at org.mule.module.extension.internal.introspection.validation.NameClashModelValidator$ValidationDelegate.validateTopLevelParameters(NameClashModelValidator.java:121) at org.mule.module.extension.internal.introspection.validation.NameClashModelValidator$ValidationDelegate.validate(NameClashModelValidator.java:107) at org.mule.module.extension.internal.introspection.validation.NameClashModelValidator$ValidationDelegate.lambda$validate$33(NameClashModelValidator.java:77) at org.mule.module.extension.internal.introspection.validation.NameClashModelValidator$ValidationDelegate$$Lambda$27/1920186116.accept(Unknown Source) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) at org.mule.module.extension.internal.introspection.validation.NameClashModelValidator$ValidationDelegate.validate(NameClashModelValidator.java:77) at org.mule.module.extension.internal.introspection.validation.NameClashModelValidator$ValidationDelegate.access$000(NameClashModelValidator.java:52) at org.mule.module.extension.internal.introspection.validation.NameClashModelValidator.validate(NameClashModelValidator.java:49) at org.mule.module.extension.internal.introspection.DefaultExtensionFactory.lambda$createFrom$39(DefaultExtensionFactory.java:105) at org.mule.module.extension.internal.introspection.DefaultExtensionFactory$$Lambda$18/1393913553.accept(Unknown Source) at java.lang.Iterable.forEach(Iterable.java:75) at org.mule.module.extension.internal.introspection.DefaultExtensionFactory.createFrom(DefaultExtensionFactory.java:105) at org.mule.module.extension.internal.introspection.DefaultExtensionFactory.createFrom(DefaultExtensionFactory.java:94) at org.mule.module.extension.studio.internal.capability.studio.editor.StudioEditorGeneratorTest.testGeneration(StudioEditorGeneratorTest.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9154","11/25/2015 18:25:51",0,"@Optional should not be allowed as a modifier for methods ""@Optional can currently be used to annotate methods. User should not be able mark methods with @Optional""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9155","11/25/2015 18:36:57",5,"@Optional should not be allowed when @Parameter group is used ""When using @ParameterGroup, @Optional should be marked as an error. """," @Operation public SimplePojo parameterGroupPojoOperationWithDefault( @Optional @ParameterGroup SimplePojo pojo) { return pojo; } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9157","11/26/2015 12:37:46",2,"Remove BootstrapServiceDiscoverer reference from MuleContext ""As part of MULE-9089 MuleContext was updated in order to provide a BootstrapServiceDiscoverer. That was done to make easier to start migration to the new container model and must be removed and repalced with dependency injection once the rest of the code is also migrated.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9158","11/26/2015 15:38:40",8,"Change TransformationService to not mutate MuleMessage ""There are two parts to this: * applyTransformers() methods: ** Update applyTransformers() method signatures to return a MuleMessage instance. ** Change implementation of applyTransformers() to return a new message instance with the result of the transformation rather than mutating the original message instance. ** Update all uses to use the return value as the result of the transformation. * getPayload() methods: ** Remove the logic that transparently transforms consumable payloads by mutating the message and setting a byte[] representation. ** Calls to getPayload() that require transformation of a consumable payload will now fail. ** Update uses to perform transformation to non-consumable prior to getPayload() if required. ** Update getPayloadForLogging() implementation to return something like “Stream payload (InputStream)” instead of failing or performing translation. ** Ensure getPayloadForLogging() is only used for system logging and not used be user configured component.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9160","11/26/2015 17:07:37",5,"Upgrade to Log4j latest version ""https://issues.apache.org/jira/browse/LOG4J2-998 figures as already fixed in 2.3 and 2.5 is already out. Mule is currently using 2.1 This may allow to get rid to some custom hacks currently being done in Mule side.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9162","11/30/2015 15:44:52",2,"ForEach component is loaded twice into the Registry ""This is the root cause of MULE-9161 Analyzing the registry when the exception occurs, it is seen that the registry contains an additional uninitialized ForEach component.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9163","11/30/2015 16:49:06",0,"MVEL gets in an infinite loop in CompileException ""An infinite loop happens when building an error message for an invocation on a null object. This is already fixed in MVEL repo: https://github.com/mvel/mvel/commit/188660b2eb6dab8d2262cd385b270017f4a50047""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9164","11/30/2015 16:53:46",5,"Release MVEL 2.1.9-MULE-009 ""Perform a release of MVEL that contains the fix for the linked issues.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9168","12/01/2015 14:08:38",8,"Users should not be forced to use @Parameter to expose pojo fields ""In order to expose pojo fields users are force to annotate the each field with @Parameter. When users consumes external jar, they cannot modify the code. Also if they generate java stubs from a WSDL using CXF, they will need to modify a huge amount of Pojos just to get this to work properly, and what is worst, if a new version of the WSDL goes out and you try to update your connector, you will lose everything after generating the new stubs. The mechanism should be that if the Pojo has any field annotated with @Parameter, then the current logic is valid and should only expose those fields. However, if the Pojo has no @Parameter, every single field that has a gettter and setter should be taken into account (including nested pojo fields)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9171","12/02/2015 16:18:34",3,"When using only one @Configuration users should not be forced to specify a config name ""When writing an Extension with only one class annotated with @Configuration with no name, validations fails forcing you to specify a name for the annotation. If you don't specify a name it fails. The @Configuration should have a name by default and only check collisions of the name attribute"""," @Configuration(name=""""config"""") public class BasicConfig ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9173","12/03/2015 13:16:01",0,"Exclude xalan serializer from CXF ""Nowadays, xalan is excluded from all dependencies and only added when necessary with version 2.7.2. The serialised however is not excluded and even though it is not part of the distribution, the CXF module does include it because of a transitive dependency with version 2.7.1. This causes trouble since the two versions don't match.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9174","12/03/2015 19:53:21",0,"Security credentials not passed to JMS broker when using 1.0.2b spec ""When using JMS 1.0.2b, and *cacheJmsSessions* is not set to *false*, credentials are not passed to the JMS Connection.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9180","12/04/2015 18:09:10",5,"Add support for a Palette Name so that extension can define the display name (like the friendlyName of @Connector) ""Users need to be able to specify a friendly name that will be used to generate the display name of the extension. For example salesforce extension should say """"Salesforce"""" in the palette, and we cannot generate this form the namespace nor the class name.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9181","12/04/2015 18:30:53",13,"Allow users to write Transformers as part of their extension ""Users should be able to write Transformers in their extensions""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9182","12/04/2015 20:23:18",0,"CXF proxy trying to send response for one-way operations ""When invoking SOAP webservice - Proxy Service, calling a one-way operation (no output defined) the response builder of http fails with the stack: When the operation is one-way, an empty payload and status code 202 must be returned."""," java.lang.NullPointerException at org.mule.module.cxf.CxfInboundMessageProcessor$1.write(CxfInboundMessageProcessor.java:423) at org.mule.transformer.simple.ObjectToByteArray.doTransform(ObjectToByteArray.java:63) at org.mule.transformer.AbstractTransformer.transform(AbstractTransformer.java:420) at org.mule.DefaultMuleMessage.getPayload(DefaultMuleMessage.java:377) at org.mule.DefaultMuleMessage.getPayload(DefaultMuleMessage.java:325) at org.mule.DefaultMuleMessage.getPayloadAsBytes(DefaultMuleMessage.java:615) at org.mule.module.http.internal.listener.HttpResponseBuilder.build(HttpResponseBuilder.java:159) at org.mule.module.http.internal.listener.HttpMessageProcessorTemplate.sendResponseToClient(HttpMessageProcessorTemplate.java:97) ",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9183","12/09/2015 13:05:45",0,"CXF: Status code for successful one-way operations should be 202 ""For web service invocations that do not return an envelope (like one-way operations), status code 202 (Accepted) has to be returned instead of 200 (Ok) Reference: http://www.w3.org/TR/soap12-part2/#http-reqbindwaitstate""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9185","12/09/2015 19:57:41",0,"Cleanup of Events put in ThreadLocal with RequestContext ""By using RequestContext and OptimizedRequestContext, the event is put into the ThreadLocal of the processing thread. However, the thread may belong to a pool defined in a domain, and not clenaing the RequestContext properly will result in application stuff being referenced by domain objects, and these will not be garbage collected when undeploying the application while keeping the domain.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9187","12/11/2015 13:32:33",1,"Improved DataType support in MuleMessage to include information of types of list payload ""This is related to consolidation of dataType in mule/ext-api/mule-commons.""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9189","12/11/2015 14:40:06",0,"RegistrationException ""More than one AbstractJmxAgent"" when using domain and enabling jmx ""When starting an application that has a jmx agent, and that application is in a domain other than default, with Mule version 3.7.2, you should get: RegistrationException: More than one object of type class org.mule.module.management.agent.AbstractJmxAgent registered but only one expected. If you change the app's domain back to """"default"""" (the one it's using has no configuration), that exception will not happen on startup. In /META-INF/services/org/mule/config/registry-bootstrap.properties in mule-module-management-3.7.2.jar there are these two agents which are getting picked up automatically by Mule on startup: jmx-agent=org.mule.module.management.agent.JmxApplicationAgent,applyToArtifactType=app domain-jmx-agent=org.mule.module.management.agent.JmxDomainAgent,applyToArtifactType=domain Mule 3.7 uses one registry so maybe that is why this exception is happening.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9191","12/11/2015 18:23:34",13,"Spike on new FTP connector ""Spike on a new FTP connector which is consistent with the new File one""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9193","12/11/2015 19:12:05",0,"Big memory footprint on XMPP Transport: org.jivesoftware.smack.PacketCollector ""XMPP transport uses smack, which stores in memory a large number of objects for the received messages. On versions later that the one currently in use in Mule, the max size of this objects to store is configurable.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9195","12/14/2015 19:37:10",8,"Review new HTTP module if should propagate root message id as old transport ""Old transport propagates the root message id using HTTP headers. We need to define if we want to keep this functionality in Mule 4.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9196","12/14/2015 19:57:10",8,"JAXBMarshallerTransformer fails to transform to byte array ""JAXBMarshallerTransformer fails to transform to a byte array. The easy fix is to add an if in JAXBMarshallerTransformer for byte array. But the real fix seems to be fix the auto transformation logic. Since JAXBMarshallerTransformer knows how to transform to a String and mule knows how to transform from String to byte array then the auto transformation should work.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9199","12/15/2015 13:40:47",0,"HTTP client in devkit support not working against HTTP listener ""The http client in devkit support is failing against and http:listener. The http client implementation is really poor, so was the old http transport and that may be the cause of the failure, bad implementation. Perhaps is better to use a http client library in devkit support instead of a custom implementation.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9200","12/15/2015 13:55:28",2,"Fix context shutdown test cases with http:listener ""Some test cases in ValidShutdownTimeoutRequestResponseTestCase and ExpiredShutdownTimeoutRequestResponseTestCase are failing after migration to new http module.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9201","12/15/2015 14:12:19",0,"HTTP request should throw a ConnectException when it fails to send a request ""Test ExceptionStrategyCommonScenariosTestCase.testStopFlowBasedOnExceptionType is failing because the HTTP request element is not thrown a ConnectException. Is thrown a plain MessagingException.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9202","12/15/2015 14:39:36",2,"Review new http module and password encryption filter ""Old http transport inbound endpoint allow to configure a filter to do some kind of encryption /decription over the password. See EncryptionFunctionalTestCase and PlainTextFunctionalTestCase We need to define if we want to support this functionality in the new HTTP module. The main problem is the usage inside a composite source.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9203","12/15/2015 15:22:57",8,"MTOM attachments not working with WS consumer and HTTP listener ""See MtomFunctionalTestCase. Fails because it seems there's a malformed response.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9204","12/15/2015 18:16:49",5,"HTTP Requester + OAuth: Add the option to send Client id/secret with Basic Auth using Client Credentials ""Right now the HTTP Requester sends the client_id and client_secret in the request-body. This is a valid option but the RFC also allows to send them using Basic Authentication: * https://tools.ietf.org/html/rfc6749#section-2.3.1 For example Paypal and Spotify APIs only support to send them using Basic Auth. * Example: https://developer.paypal.com/docs/api/#oauth-request--response ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9205","12/15/2015 19:06:11",0,"XmppMessageDispatcher doesn't reconnect ""h3. Problem description The customer is working in a scenario where the XMPP Server (Openfire) can disconnect Mule ESB as a client. The class *org.mule.transport.xmpp.XmppConnector* doesn't implement any mechanism to validate the underlying *org.jivesoftware.smack.XMPPConnection* The class XMPPConnection has the method *isConnected()* that could be used to validate the connection before dispatching messages, and eventually fire a reconnection, if needed. Note that during my tests I was able to verify that killing Openfire (with kill -9), no reconnection strategy was fired. Reconnection seems to work only when at initialization time it detects that there is no connection towards the XMPP Server.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9207","12/15/2015 21:54:23",2,"ConnectionProvider getHandlingStrategy must receive a parameterized ConnectionHandlingStrategyFactory ""Current ConnectionProvider getHandlingStrategy interface method receive a ConnectionHandlingStrategyFactory raw type parameter, this results in an unchecked warning on every implementation of this method. The signature of the method must be """," ConnectionHandlingStrategy getHandlingStrategy(ConnectionHandlingStrategyFactory handlingStrategyFactory); ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9211","12/16/2015 18:26:38",8,"Configurations should be able to have dynamic parameters which don't trigger dynamic configurations ""Currently, all configuration parameters with expression values are translated into a DynamicConfigurationResolver. This is fine for most cases There're other cases though in which it's desirable to have dynamic values which shouldn't necessarily trigger a new config instance. For example, an FTP connector which needs to switch between ASCII and BINARY mode. It should be fairly easy to switch modes through the use of an expression, but we don't want to trigger new connection pools for each case. Only connection credentials should trigger that. To enable this case, we can leverage the ValueResolver object which already exists in the extension-support module. The config can have: and then when you want to get the value you go: """," @Parameter private ValueResolver transferMode; ftpConnector.getTransferMode().resolve(event); ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9213","12/16/2015 18:29:46",3,"Transfer mode and passive attributes should not trigger new config instances ""Currently, the passive and transferMode attributes in the new FTP connector are dynamic. However, those should accept expressions but not trigger new config instances since those shouldn't require a new pool to be created. Leverage MULE-9211 to allow this.""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9214","12/16/2015 20:46:46",3,"Add missing syntax validators for annotation driven extensions ""*Add missing syntax validators for annotation driven extensions* * Validate @UseConfig or @UseConfig are used more that once * Validate if configurations or connection providers from the @Extension are compatible with every @UseConfig or @Connection type from the @Operations""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9215","12/16/2015 21:07:04",2,"File system connectors should default to mule message information when possible ""As it is today, the filesystem connectors require the user to provide path and content for each operation. That's great for some cases. In other cases in which the mule message already contains a reference to a file, those attributes should be optional and the connectors should be smart enough to get the necessary parameters from the message itself.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9216","12/17/2015 14:28:49",0,"Introduce the new File and FTP connectors ""Introduce the base for the new file and ftp connectors (even though future commits will keep adding features)""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9217","12/17/2015 17:06:36",1,"Update spring schemas to 3.8 ""Update spring schemas to 3.8""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9224","12/21/2015 15:32:44",0,"Using multiple threads in an until successful causes an exception if the message is rejected ""When a thread stores an event for processing, it owns it's message. If the pool has many threads another might pick it up and though it copies it for processing it does not when abandoning the retries and calling the exception handler (no DLQ is configured) which need to add the exception payload, so an access violated error occurs.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9225","12/21/2015 19:10:32",5,"If the @XML annotation is not present, the extension should not fail. ""Currently when creating an extension, the @XML annotation is mandatory, we should specify at least the namespace of the extension. If the @XML annotation is not present, this error is thrown [ERROR] diagnostic: error: xml model property cannot be null. Instead of creating a validator for avoiding this error, we must implement a default behaviour for the @XML annotation when it is not present. The behavior should be that: 1) The annotation can be either completely absent or present but with all optional parameters 2) The namespace attribute will be derived from the extension name by transforming to lower case, removing all occurrences of the """"connector"""" String and hyphenizing 3) The schemaLocation should default to http://www.mulesoft.org/schema/mule/{1}, where {1} is replaced by the namespace value 4) The schemaVersion should default to the Major and minor components of the Semver extension version, without classifiers. For example: 4.0.0-SNAPSHOT should translate to 4.0 ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9226","12/21/2015 20:55:24",0,"Logging issues when using domain configuration with JMS connector ""JMS receiver is not setting the context classloader of the application its message is for. This causes that when the message is received by a thread managed by the domain or an embedded broker, any log entries for that message processing do not end up in the application log.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9228","12/22/2015 14:12:38",5,"SDK: Split extensions parent POM, for internal and external extensions ""*Split extensions parent POM* * Create a new Parent POM for external (to Mule Distribution) extensions, to be used by MuleSoft internal connectors (Salesforce, Workday, etc) and third party (custom connectors, certification). ** One of the problems the actual POM is that project version (the extension version) is attached to all Mule dependencies version. For external connectors, this should be detached . * Rollback the changes made in the actual extensions POM, to be used exclusively for Mule Distribution extensions. (MULE-9055)""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9229","12/22/2015 19:51:55",0,"UntilSuccessfulTestCase is throwing NPE ""It seems the exception handler was not added to the until-successful functional test case so some of the tests are throwing NPEs.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9232","12/22/2015 21:11:38",8,"Update File and FTP connectors to leverage the changes in the new MuleMessage ""The work on MULE-9216 is based on a FilePayload pojo which is set as payload. Per the changes in the new MuleMessage structure this should be revamped as: * The input stream goes into the payload * The rest of the attributes go into a FileAttribute pojo which is set as metadata * The list operation returns a List""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9233","12/22/2015 21:14:20",5,"File connector requires a custom matcher ""The file connector has the concept of creation, modification and access timestamp for files. The rest of the file connectors most commonly only have the concept of timestamp which is tied to modification time. As defined today, all the connectors based on file-common have the 3 concepts. It should be possible for the FTP family to only handle a timestamp and only file have the specific concept""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9237","12/23/2015 18:16:13",0,"Null pointer while catching the exception thrown from Enricher processor ""When exception is caught that was thrown from Enricher processor, it throws null pointer exception org.mule.exception.CatchMessagingExceptionStrategy: Caught exception in Exception Strategy: null java.lang.NullPointerException at org.mule.processor.AbstractRequestResponseMessageProcessor$1.processReplyTo(AbstractRequestResponseMessageProcessor.java:107) ~[mule-core-3.7.2.jar:3.7.2] at org.mule.routing.requestreply.AbstractReplyToPropertyRequestReplyReplier.processReplyTo(AbstractReplyToPropertyRequestReplyReplier.java:67) ~[mule-core-3.7.2.jar:3.7.2] at org.mule.routing.requestreply.AbstractReplyToPropertyRequestReplyReplier.process(AbstractReplyToPropertyRequestReplyReplier.java:43) ~[mule-core-3.7.2.jar:3.7.2]""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9239","12/23/2015 22:23:28",0,"Extract FlowStack testing code to a common location ""So it can be reused by other modules that include components that support flowStack""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9246","12/29/2015 22:11:21",3,"SDK: Extend IllegalModelDefinitionException to be more specific when validating the Extension model ""*SDK: Extend IllegalModelDefinitionException to be more specific when validating the Extension model* In some test cases like: *ExtensionBuildersTestCase* there are some test cases that are expecting *IllegalModelDefinitionException* or *IllegalArgumentException* that are caused due to some model validations, and a problem that is happening, that maybe a new validation is added and all tests cases still failing with the expected Exception but with an incorrect cause. To solve this: * Review all kinds of exceptions thrown by the validations, and check if make sense to migrate from an super generic *IllegalArgumentException* to an *IllegalModelDefinitionException*. * Extend *IllegalModelDefinitionException* to be more specific in the validation error. An approach could be extending for any kind of model available (Operation, Configuration, Connection Provider and also for Parameters). For example: If it fails because the configuration was not configured with a *ConfigurationFactory*, It should fail with a *IllegalConfigurationModelDefinitionException*. * Review all ModelValidators to throw proper exceptions.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9250","01/04/2016 14:26:58",3,"Remove extensions test jars from mule distribution ""Currently, when creating the studio distributions, extensions used for testing only are being discovered inside the runtime. (Heisenberg Extension). This jar should not be included in the distribution, or at least we should have a flag that needs to be explicitly provided for this jars to be included.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9251","01/04/2016 14:51:16",13,"Add support for Maps in the SDK ""Add support to allow configurations and operations to receive Map parameters""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9252","01/04/2016 14:53:47",2,"Allow users to use password editor for sensitive data fields ""When a field is related to sentisitive data, like passwords or tokens, users should be able to use the password editor field. To do this, users should be able to mark the parameters and configurable field with @Password.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9255","01/04/2016 15:26:27",2,"Allow users to use Text editor for long String input fields ""For long String input fields, users should be able to mark the fields with @Text to generate a text editor instead of a String editor, as the DevKit did.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9258","01/04/2016 15:35:39",8,"Support to receive Mule expressions as parameters without getting resolved ""Add support on the SDK for receiving MEL expressions without getting the string evaluated. This features was supported in DevKit as described here: https://www.mulesoft.org/jira/browse/DEVKIT-245 This will be supported both for @Parameters and Operation arguments, when they are annotated with _@Literal_ When @Literal is used, ExpressionSupport should be _SUPPORTED_.""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9260","01/04/2016 17:50:29",5,"Add support for TlsContext in SDK ""It should be possible in the SDK to have configurations/connection providers which receive a TlsContextFactory: This should automatically generate the proper support to configure a tls-context element reusing the existing infrastructure. If the parameter is also marked as @Optional, then the default TlsCOntext should be injected if the element is not present on the XML"""," @Parameter private TlsContextFactory tlsContextFactory; ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9266","01/05/2016 19:34:07",3,"SDK: Default values are not registered in the Extension XSD ""*SDK: Default values are not registered in the Extension XSD* *Issue:* * The SchemaBuilder class provides the createAttribute() method to create an attribute for the Extension XSD, but the method signature doesn't provide a way to configure the default values of the attributes. *Symptoms:* * Luckily _(And not so luckily)_ when the attribute is based in a *ParameterModel*, the default value is grabbed from the model and not from the XSD so this bug doesn't affect that kind of attributes. * This bug affects to attributes that are doesn't based in any kind of Model, like *disableValidation* , from *ConnectionProvider*, which should have a """"true"""" value by default or POJOs when are configured without *@Parameter* fields. *Work to do:* * *createAttribute()* signature should provide a way to give a default value. * Fix all places where a *createAttribute()* with Default Value it's required.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9268","01/05/2016 20:17:16",0,"Allow studio to discover and instantiate ExtensionModels ""Allow studio to discover and instantiate ExtensionModels. We need to provide an interface that Studio can use to discover extensions given a runtime or extension. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9269","01/05/2016 20:36:25",8,"SDK: Parameter classes names clashes with Operations, Configurations and ConnectionProvider names ""*SDK: Parameter classes names clashes with Operations, Configurations and ConnectionProvider names* * In case that you define a *@Operation* like: Will generate a schema like: When the Mule Application start a *SAXParseException* is thrown due there are two elements defined with the same name: * The same issue can occur when you have a *ConnectionProvider* and a *Operation*: For Example a *ConnectionProvider* without an *Alias* _(so """"connection"""" as name)_ and a POJO Parameter of type """"Connection"""" with generate two elements with """"connection"""" as name. *Work to do*: Add more name clashing validations _(Taking in consideration Parameters types names, ConnectionProviders names, Operations names and Configuration names)_ for this cases to fail nicely at Extension generation time, and not fail at runtime when the Mule App starts. ""","@Operation public Object simplePojo(@Connection SlackClient client, SimplePojo pojo) { return pojo; } is invalid; nested exception is org.xml.sax.SAXParseException; systemId: http://www.mulesoft.org/schema/mule/slack/current/mule-slack.xsd; lineNumber: 212; columnNumber: 132; sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.mulesoft.org/schema/mule/slack,simple-pojo'. (org.mule.api.lifecycle.InitialisationException) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9271","01/06/2016 14:51:59",8,"SDK: POJO fields with and without @Parameter annotation doesn't get validated ""*SDK: POJO fields with and without @Parameter annotation doesn't get validated* * By now all *@Parameter* fields from *Configurations*, *Extensions* and *parameters of operations* are validated by the {{ParameterModelValidator}} with exception of the *@Parameter POJO fields* and the *fields of a POJO without that annotation*. *Why?* Because this fields are not described in a intermediate model, unlike the other examples, they are just taken in taken in account to generate the schema. * *Approaches:* ** Create a model for this kind of fields or use an existing model, and integrate them to the actual validation system. ** Validate at SchemaBuilding time, horrible, duplicated code. ** Other? sure.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9272","01/06/2016 20:24:22",1,"Improve logging when a TLS error occurs ""Right now we might get a """"Remotely closed"""" IOException in the requester, with no relation to TLS or tip to debug it, and no message at all in the listener. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9273","01/06/2016 21:27:10",1,"Troubleshooting: There are some components that only shows the exception message without element xml, element, etc ""There some components that when the throw exception they don't show the element, element xml, etc. I have found that VM, Dataweave, Expression Transformer and Groovy Transformer have this issue. +The groovy transformer exception looks like this:+ ******************************************************************************** Message : groovy.lang.MissingPropertyException: No such property: lala for class: Script5 Possible solutions: class (javax.script.ScriptException) Transformer : ScriptTransformer{this=1a4cfd8, name='ScriptTransformer', ignoreBadInput=false, returnClass=SimpleDataType{type=java.lang.Object, mimeType='*/*', encoding='null'}, sourceTypes=[]} -------------------------------------------------------------------------------- +Expression Transformer exception looks like this:+ ******************************************************************************** Message : Execution of the expression """"fail"""" failed. (org.mule.api.expression.ExpressionRuntimeException) Transformer : ExpressionTransformer{this=58e8d62c, name='ExpressionTransformer', ignoreBadInput=false, returnClass=SimpleDataType{type=java.lang.Object, mimeType='*/*', encoding='null'}, sourceTypes=[SimpleDataType{type=java.lang.Object, mimeType='*/*', encoding='null'}]} --------------------------------------------------------------------------------""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9275","01/07/2016 03:17:43",1,"Troubleshooting: When an exception is thrown in a for_each component the element appear with null ""When an exception is thrown in a for_each component the element appear with null: ******************************************************************************** Message : Execution of the expression """"collection"""" failed. (org.mule.api.expression.ExpressionRuntimeException). Payload : org.glassfish.grizzly.utils.BufferInputStream@72503074 FlowStack : at for_each_flow(/for_each_flow/processors/0 @ troubleshooting_for_each_null:troubleshooting_for_each_null.xml:14 (For Each)) Element : null @ troubleshooting_for_each_null:null:null --------------------------------------------------------------------------------""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9276","01/07/2016 03:28:35",1,"Troubleshooting: It would be nice to add the payload type in the exception logging ""Right now if the payload is not consumable you see the content of the payload but the type is not shown. You can guess but you are not 100% sure if the payload is a string or another type that as the toString is apply to show the content. It could be added at the beginning of the """"payload"""" field (if it is at the end and the payload is long, for example a json it will be difficult to see it) or in another field like """"payload type"""" (in this case it will be added only when the payload is non-consumable) ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9277","01/07/2016 03:35:39",1,"Troubleshooting: Expression component doesn't show the doc:name, element xml and number line in the exception logging ""Troubleshooting: Expression component doesn't show the doc:name, element xml and number line in the exception logging""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9280","01/07/2016 12:17:03",2,"Extract Static/Request context from MuleEvent into ExecutionContext ""ExecutionContext should be immutable and have a factory that can be used from MessageSources, where some values used in the ExecutionContext are provided by the source itself, while others are provided by Mule as required.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9290","01/09/2016 02:37:06",5,"Extensions fail to build if parameter has a wildcard generic ""Consider an extension with a parameter like this: Building such a extension results on the following error: The problem is that because the generic is a wildcard, the ResolveableType obtained by IntrospectionUtils.getFieldDataType() returns a null rawClass. As a result, the generated DataType points to a null class which in turn causes a NPE when an attempt is made to obtain a qualifier. The SDK should: * Ignore a type's generics one they contain at least one wildcard (consider cases like Map * Log a warning when it founds a wildcard generic * Also verify this behaviour for the case of operations in which the parameters are obtained from method arguments instead of fields """," @Parameter private ObjectStore timeObjectStore; [ERROR] diagnostic: error: Can't get qualifier for a null class java.lang.IllegalArgumentException: Can't get qualifier for a null class at org.mule.extension.api.introspection.DataQualifierFactory.getQualifier(DataQualifierFactory.java:176) at org.mule.extension.api.introspection.DataType.of(DataType.java:86) at org.mule.extension.api.introspection.DataType.of(DataType.java:38) at org.mule.extension.api.introspection.DataType.of(DataType.java:62) at org.mule.module.extension.internal.util.IntrospectionUtils.toDataType(IntrospectionUtils.java:172) at org.mule.module.extension.internal.util.IntrospectionUtils.getFieldDataType(IntrospectionUtils.java:118) at org.mule.module.extension.internal.introspection.AnnotationsBasedDescriber.declareSingleParameters(AnnotationsBasedDescriber.java:223) at org.mule.module.extension.internal.introspection.AnnotationsBasedDescriber.declareAnnotatedParameters(AnnotationsBasedDescriber.java:168) at org.mule.module.extension.internal.introspection.AnnotationsBasedDescriber.declareConfiguration(AnnotationsBasedDescriber.java:163) at org.mule.module.extension.internal.introspection.AnnotationsBasedDescriber.declareConfigurations(AnnotationsBasedDescriber.java:140) at org.mule.module.extension.internal.introspection.AnnotationsBasedDescriber.describe(AnnotationsBasedDescriber.java:116) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9313","01/12/2016 22:04:10",0,"MVEL expressions that return NullPayload must return the object ""The following premises should apply: - When comparing a NullPayload with null in a MVEL expression, it must return true. - When getting a NullPayload, it must get a NullPayload instance instead of null.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9314","01/13/2016 04:34:02",5,"Upgrade libraries and remove deprecated components in XML module ""Upgrade saxon and remove all the deprecated components in mule-module-xml""","",0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9317","01/13/2016 18:32:29",0,"HTTP outbound credentials not picked up if credentials exist from inbound ""Customer has a http outbound which needs basic authentication. What he observed is if the inbound is a file connector, it works correctly; however if the inbound is a ftp/sftp connector which has username/password set, it fails with 401. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9318","01/13/2016 21:10:48",0,"Update joda-time to version 2.9 or newer ""We need to update joda-time to the latest version due to compatibility issues with the latest updates of Oracle JDK 8""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9320","01/14/2016 14:26:47",5,"Define threading model for message sources in Mule 4 ""In Mule 3, receivers have a thread pool which they use to run the generated message through the flow. Receivers no longer exist in 4 so we need to define if: * Each MessageSource creates its own thread pool (that's what temporarily happening right now, although it's not possible to configure it) * Each flow has its own thread pool and the message source consumes that * Some other cleaver thought""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9323","01/14/2016 17:12:18",0,"WS consumer fails when reading secured WSDL ""When a wsdl is secured with basic credentials the WS consumer fails to start. The WS consumer does create the following configuration in Studio: As you can see the authentication is sent as part of the URL."""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9324","01/14/2016 21:41:42",0,"No exception is thrown when folder in path is removed ""During run-time if the path to pool files from using the File transport is removed or renamed then the File Transport pooling will not throw any exception.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9326","01/15/2016 13:55:26",5,"Add the 'target' synthetic parameter on all SDK operations ""All operations written through the SDK must automatically include a parameter named target. This parameter is an optional String and doesn't support expression. When provided, it means that the message that first entered the OperationMessageProcessor must leave it untouched. However, whatever output the operation produces must be propagated on a new MuleMessage which is set on a flowVar which name is taken from the target property""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9327","01/15/2016 14:12:42",5,"Add support for new MuleMessage in the SDK ""SDK should no longer be compatible with the Mule 3.x MUle Message. Instead, it should only support the new MuleMessage interface defined in mule-api. Because the new mule message is meant to be immutable but we still haven't reach that point, operations which return a MuleMessage must set the payload, attributes and dataType of the returned message into the one that entered the pipeline. If the attributes or dataType of the returned message are null, then the values currently set on the original message must be preserved. Operations will no longer be allowed to return a MuleEvent.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9328","01/15/2016 14:17:24",13,"Add support for reconnection on SDK message sources ""Extend the work done in MULE-8909 to augment MULE-9083""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9329","01/15/2016 17:36:30",3,"Rethink SDK support for data types ""Currently, the SDK supports obtaining and setting the output message through a combination of the following: * ContentType interface * ContentMetadata interface * ContentMetadataParameters annotation Given that the DataType is now a first class citizen on the new MuleMessage API, we need to rethink if it makes sense to continue to do things like that or if we should just use a simpler, MuleMessage based model""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9330","01/15/2016 17:57:16",3,"Misconfigured file:list throws unfriendly error ""The following log is obtained from a misconfigured file:list operation: {code} ERROR 2016-01-15 14:34:43,672 [[ftp-app].ftp-appFlow.stage1.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : null. Payload : Element : /ftp-appFlow/processors/0 @ ftp-app -------------------------------------------------------------------------------- [2:35] ERROR 2016-01-15 14:34:55,674 [[ftp-app].ftp-appFlow.stage1.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : null. Payload : Element : /ftp-appFlow/processors/0 @ ftp-app -------------------------------------------------------------------------------- Root Exception stack trace: java.lang.NullPointerException at sun.nio.fs.UnixPath.normalizeAndCheck(UnixPath.java:77) at sun.nio.fs.UnixPath.(UnixPath.java:71) at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281) at sun.nio.fs.AbstractPath.resolve(AbstractPath.java:53) {code} Error message should be friendlier and more descriptive about the problem that actually happened. The configuration that generated this is: {code:xml} ​ {code}"""," ERROR 2016-01-15 14:34:43,672 [[ftp-app].ftp-appFlow.stage1.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : null. Payload : Element : /ftp-appFlow/processors/0 @ ftp-app -------------------------------------------------------------------------------- [2:35] ERROR 2016-01-15 14:34:55,674 [[ftp-app].ftp-appFlow.stage1.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : null. Payload : Element : /ftp-appFlow/processors/0 @ ftp-app -------------------------------------------------------------------------------- Root Exception stack trace: java.lang.NullPointerException at sun.nio.fs.UnixPath.normalizeAndCheck(UnixPath.java:77) at sun.nio.fs.UnixPath.(UnixPath.java:71) at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281) at sun.nio.fs.AbstractPath.resolve(AbstractPath.java:53) ​ ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9335","01/20/2016 00:11:49",3,"Remove Expression Evaluators ""Remove expression evaluators""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9336","01/20/2016 17:34:39",3,"Review the implementation of RetryPolicyTemplates in Extensions API to support Async/Non Blocking ""*Review the implementation of RetryPolicyTemplates in Extensions API to support Async/NonBlocking* * Extensions API uses RetryPolicyTemplate to do the retry logic in case of ConnectionExceptions. The problem comes that this RetryPolicyTemplate comes in two flavours Sync and Async, which the last one is not supported nowadays. * This is could be an importante feature in case of transactional scopes. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9338","01/21/2016 12:45:09",0,"Fix flaxy SFTP tests ""Fix flaxy SFTP tests""","",0,0,0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9344","01/22/2016 18:00:34",3,"Move TlsContextFactory to the Mule API ""Move the contents of org.mule.module.tls.api to the mule-api project""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9346","01/22/2016 18:42:07",0,"MESSAGE_SEND_BEGIN event for EndpointMessageNotification is sent after the outbound call is executed ""The event MESSAGE_SEND_BEGIN for the Endpoint Message Notification is triggered only after the message is sent and not before. This causes that the notification is not sent if the outbound call fails (i.e a connection error)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9348","01/25/2016 17:07:16",8,"Merge 3.x to 4.x ""Merge the latest changes on the 3.x branch into 4.x""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9349","01/25/2016 17:20:13",5,"When extensions has a POJO parameter with ExpressionSupport.REQUIRED, no child element should be generated for it ""When a Parameter or Field is configured with org.mule.extension.api.introspection.ExpressionSupport.REQUIRED, no child element should be generated in the XSD. The global element associated to the pojo should be generated. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9350","01/25/2016 19:46:45",5,"Initialisation value should be respected when optional parameter defaults to null ""Consider the following code: If the paremeter had some specific optional value, it would make sense for the QueuDestinationType created there to be overriden. However, if it defaults to null, it's not from a UX perspective to force the user into implementing Initialisable and doing the check/initialisation there. That value should be respected when the optional is null."""," @Parameter @Optional private DestinationType destinationType = new QueueDestinationType(); ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9351","01/25/2016 21:55:57",3,"Required pojos are marked as optional on XSD if not instantiable ""When required pojos are instantiable, the SchemaBuilder generates an optional attribute and an optional nested element to define it. Then, there's a runtime validation to make sure that one of the two have been honoured. However, if the pojo type is not instantiable, the nested element is not generated, yet the parameter is still marked as optional.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9352","01/26/2016 13:29:11",0,"Move ConnectionHandlingTypeModelProperty to Extension API so that it can be consumed from Studio ""In order to generate studio support for pooling profile we need to move the property to extensions API instead of being internal""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9354","01/27/2016 14:13:18",5,"Remove ContentMetadataConcept from SDK ""In MULE-8959 a mechanism was added to allow obtaining and setting the output dataType from a extension operation. With the coming of the new mule message, this mechanism is no longer necessary, since the MuleMessage became a minimalistic thing on which the DataType became a first class citizen. So we need to: 1) Rename the ContentMetadataParameters annotation to DataTypeParameters 2) Delete de ContentMetadata and ContentType concepts from the extensions-api 3) rewrite the org.mule.module.extension.internal.runtime.processor.AbstractReturnDelegate#resolveDataType so that the same behaviour is maintained but using org.mule.api.metadata.DataType instead""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9357","01/27/2016 17:26:50",2,"Add configuration for maven-jar-plugin in the Extensions Parent Pom ""*Add configuration for maven-jar-plugin in the Extensions Parent Pom* Add configuration to add missing entries in the Manifest file like *Implementation-version* and *Specification-version*""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9360","01/27/2016 19:01:54",3,"Two ways of setting aliases for parameters ""The @Alias annotations is the default mechanism to force a name on the SDK. However, the @Parameter annotation also provides an alias attribute which collides with the one above. We need to remove that attribute and standarize on @Alias""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9362","01/28/2016 20:32:53",3,"Update xmlsec version ""xmlsec version is fixed to 1.5.3 which has these medium vulnerabilities: CVE-2013-4517 and CVE-2013-2172. This dependency is only used in CXF, which depends on a newer version where those vulnerabilities are fixed. We should remove the explicit xmlsec dependency from pom.xml so we can use the version that CXF uses. Initially this dependency was added in this commit: 4723ca54625b0318488f2380eb5ca9574d73e779. But right now it doesn't seem that we need a separate version anymore.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9363","01/29/2016 19:38:16",0,"Infinite loop encrypting/decrypting zero length values ""Both EncryptStreamTransformer and DencryptStreamTransformer assume that the value to encrypt/decrypt will have at least one character. This causes an infinite loop when the value has no bytes to process.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9364","01/29/2016 21:09:54",0,"DecryptStreamTransformer does not close original input stream ""DecryptStreamTransformer is not closing the input stream used as source. This causes a problem when a decrypting an encrypting file and the source will never be released (deleted if the file inbound uses autoDelete)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9368","02/10/2016 15:36:53",0,"Add known_hosts validation to SFTP Transport ""We are trying to push a file to an sftp server. We are using the machine name to connect to it. We want to validate that the server we are connecting to is the correct one. We have the third party servers public key. * Does this apply to any connection type or only when using identity file? ** yes i believe this is true for identity file or password based authentication * Any limitations/validations should be applied on that parameter? ** it should be a file that is readable.""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9370","02/10/2016 15:50:14",5,"Proposal to get rid of message enricher ""Since the target attribute is allowed in any message processor from now on, message enricher it may not be required anymore. One of the things message enricher allows to do is to do a target over a set of message processors instead of just one. We need to create a proposal on how to replace all the use cases covered by message enricher with """"target"""" attribute + any other change.""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9371","02/10/2016 16:18:25",8,"Proposal for improving error handling in Mule ""Create a proposal to improve error handling in mule. Ideally we should do error handling in a java agnostic way. We need to consider also the DataWeave limitation of working with Java exceptions. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9372","02/10/2016 16:33:10",8,"Create spec for isolation using custom classloading ""Create a spec describing pros/cons and behaviour of getting component isolation though a custom class loading model. ""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9376","02/10/2016 20:43:59",5,"@Operation annotation should be implicit ""Currently, the new SDK requires specifying the classes in which the extension's operations are defined, plus, those methods need to be annotated with @Operation. This is kind of redundant, since the @Operation does not add any information. We should: * Delete that annotation * All public method in operations classes should be automatically consider as operations * Public methods annotated with @Ignored should be skipped * Add test for @Ignored annotation ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9378","02/12/2016 13:51:27",0,"Expand FlowRunner to support different FlowConstruct types ""Currently, *FlowRunner* only supports running *Flow*s. It must be extensible to allow running other implementations of *FlowConstruct*.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9383","02/17/2016 14:41:55",0,"Allow to receive/send http content with invalid content-type headers ""When a server returns a Content-Type HTTP header without a value (""""Content-Type:\r\n"""") an exception is thrown parsing the value when creating a Mule Message. While this is not probably a valid header when trying the same request with Firefox or Chrome the header is ignored so it would be reasonable to validate the header value before trying to use it and ignore if not valid. This also happens when receiving a content type ended in a semicolon: Content-Type: image/tiff;""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9385","02/17/2016 15:00:24",5,"Add support for Ref Only parameters for Extension's operations ""*Add support for Ref Only parameters for Extension's operations* Nowadays the *SDK* knows when introspect a parameter or not. In the case of POJO parameters, the actual logic is the following: * If a *@Parameter* is used, the SDK will only register the annotated fields. * If it's a pure *POJO*, the SDK will look for all the getters/setters available. But could be cases where we don't want to use annotations or the POJO to be introspected, _examples?_ * The POJO is too complex to be rendered in Studio. * The POJO contains a reserved name that clash with other one in the extension schema. * *I love DataWeave*, the future is DataWeave * Because I want For this cases doesn't exist support yet, to fix that a *DevKit* like *@RefOnly* should be implemented ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9386","02/17/2016 19:27:22",8,"Stream not closed when using async scope ""When deploying the following config and sending this request ({{curl -X POST --data-binary ' ' http://127.0.0.1:8081/input}}) the response is never returned, probably because the stream is not closed. The correct behaviour seems to be not to allow to execute an async router when streaming. """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9387","02/17/2016 20:37:16",8,"Add placement and group metadata to parameters ""We need an equivalent to Devkit's @Placement and @Group annotations. They should translate to model properties at a ParameterModel level and should be available both on configs and operations. This impacts: * Annotations * Describers * Fluent API * The agent needs to be able to expose this when creating the extension's JSON representation * Studio needs to add support for this when generating the Studio editor""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9389","02/18/2016 12:44:20",0,"Mule Context's getTransactionManager randomly returns null if called during context start ""This happens because of a race condition. For instance, when a JMSXAConnector tries to get the transaction manager from the Mule Context and the Mule Context is still starting. The problem seems to be in Spring's DefaultListableBeanFactory.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9391","02/18/2016 16:35:58",5,"Spike: Allow http:request to retry request when there are several IPs for the same hostname ""DNS servers may provide several IPs for the same hostname. This may be used for failover mechanism when a certain IP is not available. We should provide a way to configure http:request to do failover and retry when a certain IP is not reachable and more than one IP has been resolved for a certain hostname. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9392","02/18/2016 17:04:39",8,"Support configurable ObjectStore in every mule component ""We need to allow all components using ObjectStore internally to provide configuration to overriding the default ObjectStore configuration. Components to be updated are: - Idempotent Redelivery Policy - Aggregators - DevKit token manager""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9393","02/18/2016 17:56:28",13,"Spike: Mule Runtime data sense execution API ""We need to do a spike for DataSense execution in the Mule Runtime. DataSense requires the Mule Runtime to resolve how to create components based on the application specific configuration. Ideally we should allow to load single component (connectors, message source, operation) without having to load the whole application.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9395","02/22/2016 16:25:27",1,"Remove warning when building external extension ""When building an external extension a warning is shown because of a missing version in the parent pom for the org.apache.maven.plugins:maven-jar-plugin. We should specify it to avoid this logs: """," [WARNING] [WARNING] Some problems were encountered while building the effective model for org.mule.modules:foo-connector:jar:1.0.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-jar-plugin is missing. @ org.mule.extensions:mule-extensions-parent:4.0-SNAPSHOT, /Users/pablocabrera/.m2/repository/org/mule/extensions/mule-extensions-parent/4.0-SNAPSHOT/mule-extensions-parent-4.0-SNAPSHOT.pom, line 119, column 21 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9399","02/23/2016 17:10:59",0,"Mule throws a LifecycleException when disposing an Extension Source ""*Mule throws a LifecycleException when disposing an Extension Source* * When working with Mule Extension Sources, a way to fail at start time is to to throw an exception inside {{start()}} of a Source, this exception inside the SDK is analysed and if it could not be handled, is propagated to Mule. Mule when detect this exception starts to dispose the Source, when this occur a exceptions is thrown. Stack trace: ""","ERROR 2016-02-23 14:09:35,670 [Thread-4] org.mule.construct.AbstractFlowConstruct: Exception found trying to dispose object. Shutdown will continue java.lang.IllegalStateException: Lifecycle Manager 'source-fail-on-start.stage1' phase 'start' does not support phase 'dispose' at org.mule.lifecycle.AbstractLifecycleManager.checkPhase(AbstractLifecycleManager.java:116) ~[classes/:?] at org.mule.processor.SedaStageLifecycleManager.fireDisposePhase(SedaStageLifecycleManager.java:117) ~[classes/:?] at org.mule.processor.SedaStageInterceptingMessageProcessor.dispose(SedaStageInterceptingMessageProcessor.java:429) ~[classes/:?] at org.mule.processor.chain.AbstractMessageProcessorChain.dispose(AbstractMessageProcessorChain.java:133) ~[classes/:?] at org.mule.api.lifecycle.LifecycleUtils.disposeIfNeeded(LifecycleUtils.java:252) ~[classes/:?] at org.mule.construct.AbstractFlowConstruct.disposeIfDisposable(AbstractFlowConstruct.java:330) ~[classes/:?] at org.mule.construct.AbstractPipeline.doDispose(AbstractPipeline.java:438) ~[classes/:?] at org.mule.construct.AbstractFlowConstruct$4.onTransition(AbstractFlowConstruct.java:166) ~[classes/:?] at org.mule.construct.AbstractFlowConstruct$4.onTransition(AbstractFlowConstruct.java:163) ~[classes/:?] at org.mule.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:136) ~[classes/:?] at org.mule.construct.FlowConstructLifecycleManager.fireDisposePhase(FlowConstructLifecycleManager.java:144) ~[classes/:?] at org.mule.construct.AbstractFlowConstruct.dispose(AbstractFlowConstruct.java:162) ~[classes/:?] at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) ~[?:?] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_66] at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_66] at org.mule.lifecycle.phases.DefaultLifecyclePhase.applyLifecycle(DefaultLifecyclePhase.java:237) ~[classes/:?] at org.mule.lifecycle.phases.MuleContextDisposePhase.applyLifecycle(MuleContextDisposePhase.java:99) ~[classes/:?] at org.mule.config.spring.SpringRegistryLifecycleManager$SpringContextDisposePhase.applyLifecycle(SpringRegistryLifecycleManager.java:132) ~[classes/:?] at org.mule.lifecycle.RegistryLifecycleCallback.doApplyLifecycle(RegistryLifecycleCallback.java:91) ~[classes/:?] at org.mule.lifecycle.RegistryLifecycleCallback.onTransition(RegistryLifecycleCallback.java:67) ~[classes/:?] at org.mule.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:138) ~[classes/:?] at org.mule.lifecycle.RegistryLifecycleManager.fireLifecycle(RegistryLifecycleManager.java:109) ~[classes/:?] at org.mule.registry.AbstractRegistry.dispose(AbstractRegistry.java:71) ~[classes/:?] at org.mule.registry.AbstractRegistryBroker$2.onTransition(AbstractRegistryBroker.java:69) ~[classes/:?] at org.mule.registry.AbstractRegistryBroker$2.onTransition(AbstractRegistryBroker.java:64) ~[classes/:?] at org.mule.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:138) ~[classes/:?] at org.mule.lifecycle.RegistryBrokerLifecycleManager.fireDisposePhase(RegistryBrokerLifecycleManager.java:82) ~[classes/:?] at org.mule.registry.AbstractRegistryBroker.dispose(AbstractRegistryBroker.java:63) ~[classes/:?] at org.mule.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:121) ~[classes/:?] at org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:91) ~[classes/:?] at org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:87) ~[classes/:?] at org.mule.lifecycle.MuleContextLifecycleManager.invokePhase(MuleContextLifecycleManager.java:69) ~[classes/:?] at org.mule.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:61) ~[classes/:?] at org.mule.DefaultMuleContext.dispose(DefaultMuleContext.java:371) ~[classes/:?] at org.mule.tck.junit4.AbstractMuleContextTestCase.disposeContext(AbstractMuleContextTestCase.java:306) ~[classes/:?] at org.mule.tck.junit4.AbstractMuleContextTestCase.disposeContextPerTest(AbstractMuleContextTestCase.java:287) ~[classes/:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_66] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_66] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_66] at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_66] at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) ~[junit-4.11.jar:?] at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) ~[junit-4.11.jar:?] at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) ~[junit-4.11.jar:?] at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) ~[junit-4.11.jar:?] at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168) ~[junit-4.11.jar:?] at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) ~[junit-4.11.jar:?] at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74) ~[junit-4.11.jar:?]",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9400","02/23/2016 19:14:23",5,"Missing child elements in XSD when the extension parameter is a List ""When an extensions has the following field, no child element is generated. A child should be generated for this element"""," @Configuration(name = """"config"""") public class ExtensionConfig { @Parameter private List> myMaps; } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9401","02/23/2016 19:27:04",3,"Inconsistent names in XSD for list parameters ""When an extensions has a configurable list, the name of the root element of the list should always be written in plural. The following parameter generates a root element called parameterList with a child element named parameterList. The root name generated in the XSD should be parametersLists or parameters"""," @Parameter private List parameterslist; ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9405","02/25/2016 17:56:16",2,"NullPointerException when setting a context-property with a null value on org.mule.module.xml.transformer.XsltTransformer ""When a context-property for the xslt-transfomer has a null value, is not handling it therefore setting a null parameter to and it is supported to set null values so an NPE is thrown. *Instead the XsltTransformer should handle this and throw a MuleException with the proper message.* ""","org.mule.module.xml.transformer.XsltTransformerjavax.xml.transform.Transformer#setParameter ERROR 2016-03-01 17:29:18,161 [[xslunittest].connector.http.mule.default.receiver.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : The Context Property for key """"vtn"""" cannot have a null value Type : org.mule.api.DefaultMuleException Code : MULE_ERROR-11 JavaDoc : http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/DefaultMuleException.html ******************************************************************************** Exception stack is: 1. The Context Property for key """"vtn"""" cannot have a null value (org.mule.api.DefaultMuleException) org.mule.module.xml.transformer.XsltTransformer:242 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/DefaultMuleException.html) ******************************************************************************** Root Exception stack trace: org.mule.api.DefaultMuleException: The Context Property for key """"vtn"""" cannot have a null value at org.mule.module.xml.transformer.XsltTransformer.doTransform(XsltTransformer.java:242) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9407","02/26/2016 19:23:18",13,"Replace extensions DataType with MetadataModel ""Leverage the new data sense MetadataModel to replace the org.mule.extension.api.introspection.DataType and provide a richer extension model""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9408","02/26/2016 20:32:34",8,"Move immutable implementations of the extension model to the API ""Move the ImmutableExtensionModel familiy of objects to the extensions-api jar""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9409","02/29/2016 15:07:06",3,"Create MetaData annotations ""Create the following annotations (and any other that is required for DataSense) As described in it's spec: https://docs.google.com/a/mulesoft.com/document/d/1inPuybiA3CTXa4Ihgz4OKl2eoI0Mlj-7vlscarQujnY/edit?usp=sharing"""," @MetaDataScope @MetaDataKeyParam @NoMetaData @ComposedKey @MetaDataCache @Content ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9410","02/29/2016 15:09:36",5,"Create interfaces required for MetaData implementation ""Following are the basic required interfaces: As specified in its spec: https://docs.google.com/a/mulesoft.com/document/d/1inPuybiA3CTXa4Ihgz4OKl2eoI0Mlj-7vlscarQujnY/edit?usp=sharing"""," MetaDataKey MetaDataResolver IncrementalMetaDataResolver ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9411","02/29/2016 15:13:50",8,"Add default implementations for MetaData interfaces ""Some interfaces require a default implementation provided by mule * MetadataResolver * NullMetadataKey * MetadataKeyBuilder ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9414","02/29/2016 15:24:28",8,"SPIKE: DataSense API for mule runtime ""We need to define how metaData will be resolved as a service from Mule and how it will be related to the Extension and its model""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9416","03/01/2016 21:42:41",1,"Troubleshooting: DB insert and delete don't show the element xml and number line in the exception logging ""When an exception occurs in a DB Insert or Delete the logs shows """"null"""" the config file and the number line. Please check the null:null in bold below in the element section: ******************************************************************************** Message : The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL151106174158370' defined on 'PLANET'. (java.sql.SQLIntegrityConstraintViolationException). Element : /jdbcInsertUpdateCountRequestResponse/processors/1 @ 612f4740-dff8-11e5-960f-8a315f85db5e:*null:null* -------------------------------------------------------------------------------- Exception stack is:... +*Steps to reproduce:*+ * In """"mule"""" project checkout to branch MULE-9416-TEST-TO-REPRODUCE * Run test testRequestResponse of class InsertDefaultTestCase inside the DB Module. (.../GitHub/mule/modules/db/src/test/java/org/mule/module/db/integration/insert/InsertDefaultTestCase.java) * In the logs you will see the exception copied above. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9417","03/02/2016 16:55:57",13,"Add support for non-blocking to JMS outbound request response endpoint ""Add support for non-blocking to the request-reply component""","",0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9418","03/02/2016 19:44:31",3,"Add an optional display name metadata to components ""We need an equivalent to Devkit's @FriendlyName annotation. It should translate to model properties at all the models that this feature will have impact in (Sources, Parameters, Operations). Since @FriendlyName its a bit confusing with the SDK @Alias annotation, @DisplayName sounds a little bit clearer. If no value is specified, the name is inferred from the annotated element's name as it does now. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9420","03/02/2016 22:05:00",8,"Move all filters to the compatibility Module ""Remove all filters that can be replaced with expressions or that overlap with the validations module.""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9424","03/02/2016 22:14:26",2,"Properly define behavior for req-resp flows - HTTP ""HTTP Connector must return a 204 - No Content response in case a message is filtered.""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9426","03/03/2016 14:05:35",8,"Refactor plugin classloading features ""Extract and refactor code used to isolate server plugins in order to reuse it on the artifacts from the launcher module.""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9427","03/03/2016 14:07:24",5,"Isolate application plugins ""Application plugins (aka connectors) are not isolate between them as all they are loaded in the same classloader. Those plugins must be isolated in the same way server plugins are isolate on mule 3.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9428","03/03/2016 14:10:37",5,"Isolate applications from application plugins ""Applications are currently exposed to all the code included on application plugins, which is not good from the isolation point of view. Application should only access to the resources explicitly exported by the application plugins.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9429","03/03/2016 14:20:48",5,"Update artifact export policy to support packages and folders only ""Mule 3 plugin export policy is based on classes and packages prefixes (i:e: org.mule.api.* or org.mule.api.Message*). Detecting if a given class is exported or not, in the presence of wildcards, could take some time. In order to improve the classloading lookup time and be more similar to what OSGi does, we should export packages/folders explicitly, with no wildcards.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9430","03/03/2016 14:34:44",5,"Add a way to dynamically configure the exported API on the core artifact ""On the modularization approach we are implementing, all the core modules will be deployed as an artifact, so they will have to define what is exported to the other artifacts. As the number of included core modules could depend on the version or distribution, the exported resources should be dynamically determined, having each module to define them explicitly inside the module binary.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9431","03/03/2016 14:38:41",8,"Invert classloading lookup process for deployed artifacts ""Mule 3 uses a parent-first classloading lookup process. This causes that plugins and application must explicitly define loader overrides when they want to use a different version thatn the one provided by mule. It also means that some apps/plugins can stop working on following versions of mule when mule includes a library that was not used before. To solve this issues and make upgrades easier, classloader lookup must be child-first but everything but mule core system packages.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9432","03/03/2016 14:42:06",5,"Isolate domains from core artifact ""Domains and child elements as applications and application plugins are exposed to all the resources included in the core artifact classloader. Instead of using the core classloader as parent, domains should take a filtering classloader that exposes only the API defined on the core.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9433","03/03/2016 14:49:55",8,"Add isolation improvements to FunctionalTestCase ""Isolation changes introduced on the deployment model should be reflected on the functional test infrastructure in order to have the same restrictions than a standalone execution. Not sure that this will be exactly the same, as for example functional test on mule 3 are not the same than a mule 3 standalone execution, but it should be as similar as possible without causing too much disruption on the development process. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9436","03/03/2016 14:58:23",8,"Define deployment model for extensions ""Extensions created with extensions API must define a package format, deployment lifecycle and isolation capabilities. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9437","03/03/2016 15:00:12",8,"Replace application plugins with extensions ""Replace application plugins artifacts with extensions.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9438","03/03/2016 15:02:05",8,"Document mule 4 classloading/deployment model ""All the changes introduced on the classloader/deployment model as part of the isolation story must be documented on this task.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9439","03/03/2016 15:12:17",13,"Improve serialization of isolated objects ""Serialization/deserialization of java objects that where created inside isolated artifacts introduces the problem that, on deserialization, no every class could be visible in order to create the deserialized objects. The way how this will be solve is still under discussion. This issue is created as a placeholder to make this missing part visible to the team.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9440","03/03/2016 15:32:33",1,"Move extensions annotations to the extensions-api jar ""We no longer require the extension annotations to be on a separate artifact. On the contrary, we want to be able to leverage them in order for the fluent API to generate complete MetadataType models. Merge them into one single artifact and modify the build""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9443","03/04/2016 14:35:57",1,"Update Maven plugin versions ""Update Maven plugins versions and move the version to a property""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9444","03/04/2016 16:35:30",3,"Upgrade Saxon to 9.7.0.3-HE ""Upgrade Saxon due to several issues have been solved since 9.7.0-3-HE version. * [List of issues solved in Saxon 9.7.0-3-HE|https://sourceforge.net/projects/saxon/files/Saxon-HE/9.7/] * in addition to the ones fixed since 9.6.0-1-HE that is the current version used in Mule: [List of issues solved in Saxon 9.6-HE|https://sourceforge.net/projects/saxon/files/Saxon-HE/9.6/]""","",0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9445","03/07/2016 00:11:12",1,"Fix flaky test org.mule.module.launcher.DeploymentServiceTestCase.redeploysDomainZipRefreshesApps ""Test org.mule.module.launcher.DeploymentServiceTestCase.redeploysDomainZipRefreshesApps fails form time to time on mule 4 branch on the continues build""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9446","03/07/2016 12:40:38",1,"TransactionManager created by TestTransactionManagerFactory returns null for hashCode() ""This causes a null pointer exception when the created object is to be put in a HashSet, or a HashSet check for contains of the created object.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9447","03/07/2016 13:50:26",3,"Connection Provider is not registered in XSD inside of a Config if an Extension only have a Source component ""*Connection Provider is not registered in XSD inside of a Config if an Extension only have a Source component* * In the SchemaBuilder, when registering a Config, there is a logic of asking *if any Connected Operation exists* _(An operation that uses a @Connection)_, if not, the Connection Provider is not registered inside the Config. * The border case comes when trying to have a Source (""""Connected Source"""") with out any operation or with Disconnected Operations, where SDK doesn't generate that Connection Provider although is necessary for the Source.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9451","03/08/2016 18:16:10",8,"Separate Extension Model into a description and a runtime model ""Currently the ExtensionModel mixes extension description properties and properties required only at runtime. In order to easily handle Serialization/Deserialization into a JSON for Studio and Mozzart, we need to separate them so that they can be easily consumed using a plain REST api. The refactor involves remove the methods of the current interfaces required only at runtime into other interfaces that extend them with the same name and the prefix """"Runtime"""" on extensions-api, and refactor mule code so that we get the minimal interface required at each method. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9452","03/08/2016 20:23:08",3,"Add support for XPath 3.1 that includes maps and arrays as return types ""[Saxon 9.7 add supports for XPath 3.1|http://www.saxonica.com/html/documentation/expressions/xpath31new.html] which includes a few interested features such: * Maps * Arrays Mule will be upgraded to Saxon 9.7 which supports XPath 3.1 but as these new types are not yet in JAXP API and Mule uses the java API instead of Saxon directly a custom component needs to be implemented in order to use Saxon s9api a get support for map and arrays return types.""","",0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9453","03/08/2016 21:05:58",8,"Pojo's properties not properly introspected depending on code conventions ""The org.mule.module.extension.internal.util.IntrospectionUtils#getExposedFields method checks a given class for fields annotated with @Parameter. If no such field is found, then it uses Introspector.getBeanInfo(Class) to get the pojos properties. However, it then tries to match those properties to fields, assuming that the pojo was written using a code convention in which the getter name is just like the field but with the get prefix. If the pojo was written using a convention such as """"_name"""", then getName() will not be matched to any field and will get dropped. Because the whole purpose of the feature is to support pojos which source is outside of the developer's control, this bug should not behave like this. The fix is harder than it seems. All the ObjectBuilder implementations work on terms of Fields. A deep refactor is needed so that Property accessors are also supported.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9454","03/08/2016 21:09:35",13,"Replace the NestedProcessor interface with a non blocking API ""The NestedProcessor interface was inherited from Devkit and serves the purpose of abstracting the concept of a MuleMessage/MessageProcessor. In mule 4 this will no longer be needed since MessageProcessor and MuleMessage will be API. NestedProcessor should be removed in favor of MessageProcessor""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9455","03/08/2016 21:22:48",1,"Remove endpoint references from generated schemas ""the concept of Endpoint has been removed from Mule 4.x. The following replacements should be done on the schema generator: * mule:messageProcessorOrOutboundEndpoint -> mule:messageProcessorOrMixedContentMessageProcessor * mule:messageSourceOrInboundEndpoint -> mule:abstract-message-source ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9456","03/09/2016 17:25:13",8,"Remove the defaultPoolingProfile parameter from the all the ConnectionHandlingStrategyFactory methods ""Currently when using a concrete ConnectionHandlingStrategyFactory the developer must specify a defaultPoolingProfile for the connector and most of the times the default pooling profile is used like So now we want that SDK manage the defaultPoolingProfile whether is supported or required so the dev doesn't need to think in default pooling profiles. So to accomplish this we must: * Remove the defaultPoolingProfile parameter from the all the ConnectionHandlingStrategyFactory methods and from all its references, * Create a getDefaultPoolingProfile() method in the ConnectionManagerAdapter that returns the SDK defaultPoolingProfile when the final user didnt specified anything in the XML. """," connectionStrategyHandlingFactory.supportsPooling(new PoolingProfile()) ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9459","03/11/2016 15:26:02",5,"Make configurations name available to them ""Configurations have a """"name"""" attribute by default but there's no way to access it. It's marked as reserved when trying to add it as a parameter. It would be helpful to make it available, for example, for logging purposes (""""JMS config 'basicJmsConfig' is set as whatever so this and that will happen."""").""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9460","03/11/2016 17:54:32",1,"Specify version for maven-jar-plugin in mule-extension-parent pom ""Version plugin is missing""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9461","03/11/2016 18:54:41",13,"Implement watcher message source in new File connector ""Implement the watcher message source as described in the spec""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9462","03/11/2016 19:04:01",3,"Create a contract around model properties ""Currently model properties can be of any class and have keys with an implicit contract. We need to be able to: * Clearly identify model properties by a well defined name * Being able to specify if they are public (should be serialized by the agent) or private (information just for the sake of the runtime) * Move all the public ones to the extensions-api artifact * keep the privates on mule internals""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9463","03/11/2016 19:07:06",3,"Add return message attributes type to the OperationModel ""Just like the SourceModel which has a getAttributeType(), the OperationModel should expose a similar thing.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9465","03/13/2016 13:39:02",5,"QName with invalid character is generated when using an Inner Enum class as parameter ""*QName with invalid character is generated when using an Inner Enum class as parameter* When using a Enum Class as parameter of a Operation, the SDK generates a child element with the name of this class. {code:title=SchemaBuilder.java} attribute.setType(new QName(schema.getTargetNamespace(), enumType.getName() + SchemaConstants.ENUM_TYPE_SUFFIX)); {code} But the problem comes when this Enum Class, is a Inner Enum Class, so the full qualifier name of this type would be, for example: {{org.mule.module.http.api.HttpConstants$ProtocolsEnumType}}, which contains the {{$}} symbol, is an Invalid character for a QName. *What to do?* * Fix generation of Inner Enums, replacing or deleting invalid characters. * Check the same problem for Inner Classes *Valid and Invalid characters:* http://stackoverflow.com/questions/1631396/what-is-an-xsncname-type-and-when-should-it-be-used """," attribute.setType(new QName(schema.getTargetNamespace(), enumType.getName() + SchemaConstants.ENUM_TYPE_SUFFIX)); ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9467","03/14/2016 11:51:38",5,"Implement Operation metadata retrieval ""- Implement retrieval of Metadata from the MessageProcessor using the MetadataManager. - Add concept of MetadataDescriptor for Operations and Parameters""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9468","03/14/2016 11:58:29",5,"Add Failure and Result handling to Metadata API ""Allow the developer to communicate errors occurred during Metadata retrieval using exceptions with FailureTypes, and then returning those errors gracefully as Results in the MetadataManager api""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9469","03/14/2016 12:03:56",3,"Prepare first Datasense PR ""Prepare datasense epic branches for the first pull request. This includes squashing, code review and review of javadocs. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9470","03/14/2016 12:06:29",8,"Review first ""SDK Support for Datasense"" PR ""Review first """"SDK Support for Datasense"""" PR""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9472","03/14/2016 12:13:32",13,"SPIKE: Metadata multi-level key structure ""Define the first approach to take on Multi-level metadata keys""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9473","03/14/2016 12:15:49",13,"Add multi-level key support for Datasense ""Implement the mechanism that allow multi level key resolving to the current metadata model. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9475","03/14/2016 12:18:04",13,"Allow config level components in the Extensions API ""When an extension has several configuration models available, there's often the need to have operations, connection providers or even sources which can only function with a subset of those configurations. This is currently not possible. We need to be able to: * Define sources, connection providers an operations an a configuration level. * The sources, providers and operations available to a configuration are those defined at its own level + the ones defined at the extension level * It is possible to have configurations which share any of those components, even though they're not declared at the extension level. For example, an extension has three configs (A, B, C); Configs A and B both point to the AwesomeOperations class. For that to work, there has to be some common type abstraction between A and B so that AwesomeOperations can receive any of those on the operations annotated with @UseConfig * Going back to the example above, if AwesomeOperations is only referenced by configuration A, it should be possible to write such operations depending on A exclusively, making it no longer necessary for A to share any kind of type abstraction with B or C ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9476","03/14/2016 12:19:22",8,"Add MetadataCache to the MetadataContext ""Add the implementation of MetadataCache to the MetadataContext, as defined in the Metadata Spec document.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9477","03/14/2016 14:17:29",5,"Refactor and extend Metadata test suite ""Refactor current Metadata testCases to improve extensibility. Add more test cases, especially those needed for error handling.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9479","03/14/2016 14:37:41",5,"Add support for Datasense in Sources model ""Add support for Datasense in Sources model""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9480","03/14/2016 14:51:35",8,"Injected object in configuration is not initialised ""When attempting to migrate the DefaultHttpListenerConfig to an extension configuration, it was failing because the injected HttpListenerConnectionManager was not initialised. Workaround was to initialise it from the config's initialise method. You can look at those classes and find the workaround in branch MULE-8864, class HttpListenerConfig.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9481","03/14/2016 15:03:07",8,"Move transports and endpoints metadata resolution from Studio to mule core ""We need to move HTTP, FTP, JMS, File endpoints datasense resolution to the mule core""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9484","03/14/2016 21:03:50",5,"Cannot define a threading profile within my config ""I have a config with a ThreadingProfile element annotated with @Parameter. However, the schema produced does not recognised it as such.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9485","03/15/2016 14:07:30",5,"Support object hierarchies ""Suppose I have 3 different kinds of authentication for my configuration, each one requires a different (could be similar) POJO. Right now I have to add each one as an optional parameter and check myself whether several have been added, since having only one is allowed. It would make more sense to have just one parameter that references an interface or abstract class, and say I want all implementations/subclasses to be considered as possibilities. See HTTP authentication or proxy configuration, for example (HttpAuthentication->abstract-http-request-authentication-provider, ProxyConfig->choice).""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9511","03/15/2016 19:19:53",8,"Scheduler error when starting Mule Standalone ""Error message: The error is thrown in the following scenarios: 1. When Mule starts 2. When an application is deployed. 3. When an application is undeployed. ""","2016-03-15 15:58:07,182 WrapperListener_start_runner ERROR Attempted to increment scheduled items after start",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9487","03/16/2016 14:43:05",8,"Extensions should be able to import TopLevel parameters from other extensions ""Extensions that depend on TCP could take advantage of the API defined in the mule sockets module, which is why it would be great to support it just like say, threading profiles are. Basically, one can define socket properties like this: So if I define as a parameter a TcpClientSocketProperties I'd expected the schema to allow that."""," ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9489","03/16/2016 17:15:01",8,"Provide an InterceptiongMessageProcessor equivalent in SDK ""The HttpBasicAuthenticationFilter has exposed the need for InterceptingMessageProcessors to be supported in extensions. There should be a way to have these and not just MPs.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9490","03/16/2016 17:22:31",13,"Migrate Http Connector to extensions API ""The current HTTP connector must be replaced with a version developed using extensions API""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9491","03/16/2016 20:21:37",2,"mule-app-maven-plugin generates an invalid archive if configuration files are within subfolders (v1.1) ""When using a maven project, deployment of the project fails if configuration files are within subfolders. It expects all configuration files to be present in the 'app' folder, and doesn't work in subfolders. The mule-deploy.properties file contents are properly populated by Studio but runtime fails during deployment of the application. The archive file generated by the plugin leaves the subfolder within the configuration file inside the classes folder and the mule-deploy.properties is automatically generated by Studio when running the application and it doesn't include the classes folder on it. Plus, if the application is exported the configuration files are duplicated by Studio in root of app folder and classes folder. The proposed solution is to change the plugin to include in the root of the archive folder the configuration files and folders with configuration files and avoid duplicating them into classes folder too.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9494","03/17/2016 16:15:54",5,"Mule 4 scopes revamp proposal ""We need to review the different Mule 4 scopes and come up with an specifications on how the different scopes will look like in Mule 4 considering the required changes for error handling.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9496","03/17/2016 17:23:19",8,"Use flow paths to obtain Processors and Sources from a Flow in the MuleMetadataManager ""* Actually the *MuleMetadataManager* to retrieve the *MessageProcessor* or *MessageSource* from a flow uses the flow index. * Using a index to retrieve this components ends up being short for the requirement of retrieve metadata from any message processor inside a flow, due that a flow can contain ramifications. * Change the actual logic the *MuleMetadataManagager* to use *flow paths* to obtain MessageProcessors in the same way that the *Mule Debugger* or *Flow Stacks* do""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9498","03/18/2016 13:44:14",0,"Timezone attribute in Quartz connector and scheduler module ""As a user I want to set a specified timezone for the cron expression that I want to use. Right now I have to set the cron in the timezone that I am, if i am using mule local I have to set the cron in my timezone. So I have to change the cron expression every time I change the environment. Quartz Scheduler allow you to do this, but in java code. This is going to be useful if we can set the timezone in the transport like an attribute.""","",0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9500","03/18/2016 22:02:41",0,"Allow specifying custom log4j config locations. ""It would be useful if apps could customise in some ways from where the log4j properties file is loaded, i.e. specify this in mule-deploy.properties""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9505","03/22/2016 22:01:04",8,"Message Processors invocations inside an Until Successful are not notified ""Message Processors invoked inside an Until Successful scope are not notified through the message processor notification server. For example, if you have set-payload inside an Until Successful scope. The invocation of the UntilSuccessful is notified but not the invocation of the set-payload. Another example, if you have an set-payload inside an enricher, and the enricher inside an Until Successful. The invocation of the UntilSuccessful is notified, but not the enricher. On the other hand, the set-payload invocation is notified. This causes notifications in the form of """"/myFlow/processors/0"""" and """"/myFlow/processors/0/0/0"""" but not """"/myFlow/processors/0/0""""""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9507","03/23/2016 14:01:09",5,"SFTP :Support two factor authentication ""An as SFTP connector user, I need to connect to an SFTP server that does Certificate and User/Pass authentication. Currently, mule can do either one or the other. See https://github.com/mulesoft/mule/blob/mule-3.x/transports/sftp/src/main/java/org/mule/transport/sftp/SftpClient.java Lines 124 and 157. Looks like mule could use a single login method and pass all parameters, and if some are not set then use only the others.""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9508","03/23/2016 15:15:38",13,"Apply feedback on DataSense review ""Apply feedback from PR""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9509","03/23/2016 15:25:48",0,"Provide extension points in http module for RequestBuilder ""Allow to override steps of the of the RequestBuilder setup. Allow for http module tests to be run from dependant modules.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9518","03/28/2016 15:53:43",13,"Create serializers for the ExtensionModel ""We need to create reusable serializer/deserializers to marshall extension models to json and back. These need to be reusable so that can be leveraged in Studio and in the agent. Right now we're using XStream but it's doing a very poor job at it and it's hard to customize. Consider using Gson or any other proper tool (careful with the recursive references in the MetadataType).""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9519","03/28/2016 15:57:37",13,"Refactor extensions packaging to be compatible with new plugin architecture ""Make changes into the extensions packaging mechanism to support the work done on MULE-9436""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9520","03/28/2016 16:26:12",8,"second round of review on DataSense ""review PR again an apply new changes""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9521","03/28/2016 16:48:36",5,"Replace MetadataKey properties with typed properties. Add also to MetadataDescriptors ""Replace MetadataKey properties with typed properties and add also to MetadataDescriptors. This typed properties will be similar to the current ModelProperties.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9525","03/29/2016 15:44:49",0,"Deadlock shutting down Mule when using JMS ""In certain circumstance when Mule is shutting down while JMS messages are being received Mule can enter a deadlock and hang.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9527","03/29/2016 21:34:31",1,"Add TLS files in conf directory to Studio distribution ""Add conf directory to Studio distribution with only these two files: tls-default.conf tls-fips140-2.conf""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9530","03/30/2016 15:25:43",5,"Improve Config retrieval when resolving Metadata for MetadataAware components ""When resolving Metadata for MetadataAware components, we need to fetch the Configuration in order to initialize the MetadataContext. Currently, we don't support dynamic configs, which result in two issues: - We need to validate that the config that will be resolved is static, for all the available ways of acquiring a config (access with config-name, with extensionModel or implicit resolution). We need to make this validations without duplicating all the ExtensionManager logic for this. - Even when there is no dynamic config support, it is required to pass a MuleEvent when fetching the config, so we are forced to create an empty event, which may result in an error if the config was indeed of dynamic nature. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9531","03/30/2016 18:13:56",0,"Upgrade AHC to 1.9.37 ""Upgrade to latest ahc version.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9535","03/31/2016 16:00:29",8,"Ability to set a property at a domain level which can be used by every application ""As a user, I would like to be able to set a property in a domain, e.g. connection.url=123, and then reference it via ${connection.url} in every child app ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9540","04/01/2016 18:03:38",2,"HTTP Connector MESSAGE_REQUEST_END notification message has no information about the HTTP response ""h5. Problem HTTP connector is sending the """"request"""" mule message in both notification events so this makes impossible for notification listeners of these events to get data about the response such http.status. In addition to that, events had mule messages with different ids so it will also make impossible to correlate a begin/end message. h5. Proposed Solution Both mule messages sent to begin and end notifications should have the same id and rootId, so the id and rootId will be propagated to the response mule message generated by HTTP module. The mule message generated from the http response is the one that will be sent to the end notification so users could check the result of the request made. h5. Caveats HTTP transport works in a different way so there will be not the same data on this notification events. The transport generated inbound properties for request and response based on its configuration, the connector used them to do the http request instead and they are not set to the mule message. As example, http.request, http.query.params, http.query.string but the URI is passed to the event as it was before.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9541","04/01/2016 21:47:26",3,"Migrate Sockets module to Sockets extension ""Migrate Sockets module to Sockets extension""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9543","04/04/2016 14:20:44",0,"Properly cleanup state in logging integration tests ""*LogConfigurationTestCase* and *ConnectorLevelMessageDispatchingTestCase* do not properly clean up the logger context they initialize.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9544","04/05/2016 15:55:27",0,"Reconnect Strategy not triggered for JMS with XA transactions ""When a JMSException occurs in the XA transaction handler, it is wrapped and that causes the reconnection strategy to not be triggered as expected.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9545","04/05/2016 19:59:00",1,"ExtensionManager should have utility methods to local models by name and/or vendor ""The ExtensionManager currently supports retrieving all the extensions. It would be helpful to be able to locate by name and name+vendor""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9548","04/06/2016 15:26:40",5,"AHC improovment to 1.9.37 ""Updating AHC library caused a 15% regression in the Proxy scenario, it appears to be a memory related issue, possibly a memory leak.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9551","04/06/2016 19:54:04",1,"NPE while building an extension without @Operations ""java.lang.NullPointerException at org.mule.module.extension.internal.capability.xml.schema.AnnotationProcessorUtils.getOperationMethods(AnnotationProcessorUtils.java:113) at org.mule.module.extension.internal.capability.xml.schema.SchemaDocumenter.documentOperations(SchemaDocumenter.java:77) at org.mule.module.extension.internal.capability.xml.schema.SchemaDocumenter.document(SchemaDocumenter.java:71) at org.mule.module.extension.internal.capability.xml.schema.SchemaDocumenterModelEnricher.enrich(SchemaDocumenterModelEnricher.java:58) at org.mule.module.extension.internal.introspection.DefaultExtensionFactory.lambda$enrichModel$2(DefaultExtensionFactory.java:300) at java.lang.Iterable.forEach(Iterable.java:75) at org.mule.module.extension.internal.introspection.DefaultExtensionFactory.enrichModel(DefaultExtensionFactory.java:300) at org.mule.module.extension.internal.introspection.DefaultExtensionFactory.createFrom(DefaultExtensionFactory.java:121) at org.mule.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.parseExtension(ExtensionResourcesGeneratorAnnotationProcessor.java:108) at org.mule.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.lambda$process$0(ExtensionResourcesGeneratorAnnotationProcessor.java:77) at java.lang.Iterable.forEach(Iterable.java:75) at org.mule.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.process(ExtensionResourcesGeneratorAnnotationProcessor.java:72) at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794) at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705) at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91) at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035) at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176) at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856) at com.sun.tools.javac.main.Main.compile(Main.java:523) at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129) at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138) at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.executeWithExceptionsHandled(AbstractAnnotationProcessorMojo.java:545) at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.execute(AbstractAnnotationProcessorMojo.java:285) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) at org.codehaus.classworlds.Launcher.main(Launcher.java:47) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) [ERROR] error on execute: java.lang.NullPointerException""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9552","04/06/2016 20:34:17",5,"Be able to define Metadata Resolvers at Operation class level ""*Be able to define Metadata Resolvers at operation class level* * By now, the extension developer can define Metadata Resolvers (*ContentMetadataResolver*, *OutputMetadataResolver* and *MetadataKeyResolver*) at *Extension class level* or *Operation method level*. * A nice to have feature is to be able to configure Metadata Resolvers at Operation class level, to impact the entire set of operations inside that class. ** *Why?* : If this operations are separated in different classes, you maybe had a grand chance to have different resolvers. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9556","04/07/2016 14:35:50",13,"Support non-blocking processing in one-way flows ""Currently the following scenarios are not supported meaning that http requester and jms outbound request-response endpoints will block, which in turn requires tuning. """," <-- blocks & requires thread tuning ​ ... <-- blocks & requires thread tuning .. ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9557","04/07/2016 22:44:03",1,"The new stack trace report in 3.8 formatting should be the same as java’s standard one ""Every stack trace line in the current version has this format: sun.reflect.DelegatingConstructorAccessorImpl.newInstance:45) and it should be: at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9558","04/07/2016 23:00:33",0,"HTTP failing response streaming calls exception strategy but returns generic error ""The response sent to the client is a simple 500 code, instead of corresponding to what is done in the Exception Strategy. This happens only when there is a streaming response that is lazily evaluated.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9559","04/08/2016 20:31:45",8,"Remove the need for extensions to explicitly declare a Describer ""Have extensions to automatically ship with a descriptor, manifest or similar resource which removes the need for extensions to ship with a describer. Also, define what to do with all the model validators and other componetns which currently depend on SPI. We should not rely on that anymore""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9561","04/08/2016 20:37:01",5,"Crete a Json serializer for the MetadataResult class ""Create a GSON based serializer which leverages the MetadataTypeGsonTypeAdapter class and allows to properly serialize an OperationMetadataDescriptor to Json and back. Try to have such serializer be as consistent with ExtensionModelJsonSerializer as possible""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9565","04/11/2016 16:20:44",5,"Return UnionType when static metadata is fetch on a type that declares SubTypes ""Return UnionType when static metadata is fetch on an abstract POJO type or interface that declares SubTypes.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9566","04/11/2016 18:42:42",0,"Content-Type set in request builder is not considered ""When you set up an HTTP request with a request builder and the header Content-Type, the actual request CT is taken from the payload. The problem is that in MuleEventToHttpRequest, the builder headers are set, then the outbound properties and then if there's no CT outbound property it is set using the data type. Since the check is only against outbound properties the builder header is ignored. As a workaround, one must set the CT as an outbound property instead of using the request builder.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9567","04/11/2016 21:28:40",8,"AHC/Grizzly: Readd locally closed connection validation ""Undo the remming of the else clause in HttpTransactionContext.listener#onClosed()""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9570","04/12/2016 17:05:08",0,"SFTP: Pooled connections not returned to pool on server/network error ""When an sftp connection from a pool is disconnected because of a network error or disconnected by the server, it is not returned to the pool and is leaked.""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9571","04/12/2016 17:22:25",5,"Enforce metadata dynamic output resolver for Map and Object ""The discussion for this feature appeared with the inheritance of metadata resolvers (from the Extension or the Operation class). What happens is that if you have an operation which doesn't need a dynamic resolver but the parent has one defined, it should *only* be applied if the operation return type is a Map or Object. With that solution we avoid the need of an @IgnoreDynamicResolver annotation. The other thing is that in SDK we want to be as restrictive as possible with the developer, and it may be a good idea to forbid operations which return type is Map and doesn't have a resolver assigned. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9574","04/13/2016 07:40:04",1,"slf4j-api schould be 1.7.12 to avoid problems with async-http-client "" with rule RequireUpperBoundDeps reports and So async-http-client library may call methods in slf4j-api which are currently not implemented in the version used for runtime (1.7.7)"""," mvn enforcer:enforce Failed while enforcing RequireUpperBoundDeps. The error(s) are [ Require upper bound dependencies error for org.slf4j:slf4j-api:1.7.7 paths to dependency are: +-com.retail-sc.mule.refdata:mule2plm:2016.6.1-3-SNAPSHOT +-org.mule.modules:mule-module-spring-security:3.7.3 +-org.mule:mule-core:3.7.3 +-org.slf4j:slf4j-api:1.7.7 +-com.retail-sc.mule.refdata:mule2plm:2016.6.1-3-SNAPSHOT +-org.mule.modules:mule-module-spring-security:3.7.3 +-org.mule.transports:mule-transport-http:3.7.3 +-org.mule.modules:mule-module-http:3.7.3 +-com.ning:async-http-client:1.9.31 +-org.slf4j:slf4j-api:1.7.12 ",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9577","04/13/2016 17:19:50",1,"Add lib folder to the extension zip even if there are no dependencies to add ""This is happening with the file extension. The solution is simply adding the lib folder to the extension zip whether exists dependencies in the pom.xml or not.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9578","04/13/2016 17:35:36",1,"Reorganize SDK packages ""Some classes in the Extensions API and framework and in wrong packages. Other packages are excessively big. Rearrange.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9579","04/13/2016 20:11:27",1,"Using transactions when non blocking should log a warning not an info ""When I use a transactional context in a flow with non-blocking processing strategy this message is logged: It logging level is INFO but it should be WARN"""," INFO 2016-04-13 16:08:50,106 [[default].HTTP_Listener_Configuration.worker.01] org.mule.processor.NonBlockingProcessorExecutor: The message processor class org.mule.processor.TransactionalInterceptingMessageProcessor does not currently support non-blocking execution and processing will now fall back to blocking. The 'non-blocking' processing strategy is not recommended if unsupported message processors are being used. ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9581","04/13/2016 20:58:51",2,"Extensions must not be able to override a ModelProperty ""Extensions must not be able to have more than one ModelProperty of the same type when being described. If this occur an IllegalArgumentException should be throwed. * Modify the method withModelProperty of the BaseDescriber.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9586","04/15/2016 15:53:00",0,"Fix flakyness in HttpRequestProxyConfigTestCase ""On some occassions, the test is run before the mock proxy has started, causing failures.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9592","04/18/2016 11:53:59",0,"MuleEndpointURI fails to extract right user and password ""MuleEndpointURI fails when handling special characters in the user and password fields. This happens because the user info is often handled decoded instead of raw, so encoded characters like """":"""" and """"@"""" are decoded and cause trouble when analysing the delimitations of the fields within the URI.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9595","04/18/2016 19:35:25",0,"MEL cached expression with null safe property is invalid after returning null ""When an expression is evaluated and an inner node evaluates to null, the optimized expression will always return null for that inner node, no matter if the context now contains objects fir that expression and it shouldn't return null.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9602","04/20/2016 13:50:30",1,"Release MVEL 2.1.9-MULE-010 ""Perform a release of MVEL that contains the fix for the linked issues.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9603","04/20/2016 15:35:13",1,"Disallow packaging more than one extension in the same plugin ""one plugin should not contain more than one extension""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9604","04/20/2016 15:44:18",8,"Add support for package and resource export on Extensions ""Now that extensions are been built as plugins we need to add support for exporting packages and resources. The following should be exported automatically: * Classes annotated with @Extension * Classes annotated with @Configuration * Classes annotated with @Operation * ObjectType parameters * ConnectionProviders * Generated schema and spring bundles * Generated extension manifest On top of that, there should be an annotation to allow manually exporting custom classes and resources... something like an extension level annotation similar to this: Keep in mind that: * The generated plugin descriptor should not reference the selected classes but their packages * It's possible that several exposed classes belong to the same package. The plugin.descriptor should declare each package only once * The Export annotation is additive. It does not override what's exposed by default."""," @Export(classes = {Foo.class, Bar.class}, resources={""""/some/public/path""""}) ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9605","04/20/2016 20:48:21",13,"SPIKE: migrate OAuth modulo to SDK ""Perform SPike on migrating the OAUth modulo to SDK""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9606","04/20/2016 20:54:13",3,"Decouple the extensions namespace from Spring ""The extensions namespace allows configuring how the runtime handles the extensions. That is currently implemented on the extensions-spring-support module, which means that all extensions have a test dependency to it (because the generated schema imports elements from mule-extensions.xsd) Once the new parsers are implemented, we should move the extensions namespace support to a module which does not require coupling to spring""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9607","04/21/2016 14:08:33",1,"Upgrade MVEL to 2.1.9-MULE-010 ""Upgrade to latest MVEL version.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9613","04/27/2016 14:34:28",8,"Spike on supporting parameters to have a provider for a dynamic list of possible values ""As a connector developer, I'd like to be able to have a dynamic resolver for the possible values that a given parameter can have with my current Connection/Configuration. The idea is similar to what we already use to resolve the MetadataKey values that then are shown as a dropdown to the user so she can select one. This is useful for cases when the possible values of the parameter come from a given set of data (like the channels you have configured in slack), but the set is dynamic since values can be created, updated or deleted, and you have to discover them each time. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9614","04/27/2016 14:46:44",8,"Allow Subtypes placeholder to be populated with any implementation of the base type ""When an extension declares a @SubType replacement group, we should leave open the possibility for any implementation of the _baseType_ to be used to populate the parameter.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9615","04/27/2016 19:05:50",5,"Extension configs can not define the same Source/Operation Class ""*Extension configs can not define the same Source/Operation Class* * Since MULE-9475, SDK supports to define *Source and Operation at config level*. * With this feature if you have something like the following: where you have *two different configs defining the same Source class*, the extension won't work at runtime due that the *generated schema is invalid*, due that the {{SchemaBuilder}} creates two times the same Top Level element _(one per config defining that Source)_. * *Possible Solution:* When generating the schema, check if the Source/Operation class was already defined by other config and skip the generation. """," +------------+ | Extension | +------+-----+ | +---------------------+ | | | +---v----+ +---v----+ +---v----+ |Config A| |Config B| |Config C| +--------+ +--------+ +---+----+ +-----+----+ | | +---v----+ +----v---+ |Source B| |Source A| +--------+ +--------+ ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9616","04/27/2016 19:25:00",0,"Reintroduce transport infrastructure in Mule 4 ""Readd transport infrastructure and a couple of transports to validate.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9618","04/27/2016 20:18:52",1,"ConnectionProvider element missing from config XSD ""When a configuration specifies its own connection provider, the corresponding XSD element is only added if other connection providers are also defined at the extension level""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9619","04/27/2016 23:42:03",1,"NestedProcessors generates leaks of OperationMessageProcessor instances ""When there is a flow using validation:all, there is a constant generation of beans of type OperationMessageProcessor as singleton in the mule registry. This constant generation, over time, causes OutOfMemoryError in the servers. The flow that reproduces this issue is: ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9620","04/28/2016 13:49:05",2,"Updated log4j version to 2.3 for versions previous 3.8. ""A client pointed to us that the logger MP was impacting highly the performance of a simple application, updating the version of the logger from 2.1 to 2.3 decreases the impact of the logging from a 43% to 20%. We also need to create a patch for the client (SE-3664).""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9621","04/28/2016 15:33:24",8,"Update Subtypes schema generation to avoid name collisions with parameters ""Modify schema generation for subtypes to use type references instead of creating named elements. With this, we should be able to have a parameter with the same name as the subtypes alias name""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9622","04/28/2016 15:37:41",8,"Separate transport core support to its own module ""Separate transport core support to its own module""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9623","04/28/2016 15:37:55",8,"Refactor out transport support code in core ""Refactor out transport support code in core""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9624","04/28/2016 15:38:04",8,"Refactor out transport spring support code ""Refactor out transport spring support code""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9629","04/28/2016 15:38:55",3,"Cherry pick changes in transports from 3.x ""Including but not limited to: MULE-9503, MULE-9417, MULE-9556 ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9630","04/28/2016 15:39:02",13,"Reintroduce HTTP transport ""Undo the changes from MULE-9111""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9631","04/28/2016 15:39:13",8,"Reintroduce file transport ""Undo the changes from MULE-8873""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9635","04/28/2016 17:14:13",2,"Include AHC/Grizzly performance fix in mule's custom ahc code ""Include the changes with the performance fix in ahc (https://github.com/AsyncHttpClient/async-http-client/commit/178ec0d668884be648f0a192666e1efcb228f857) into our ahc custom code.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9639","04/29/2016 18:47:53",3,"Application of function requiring Enum output fails ""I have a parameter declared as where HttpStreamingType is an Enum (AUTO, ALWAYS, NEVER). When I try to apply the function, however, I get: """," @Parameter @Optional(defaultValue = """"AUTO"""") private Function requestStreamingMode; Caused by: org.mule.runtime.core.api.transformer.TransformerException: Could not find a transformer to transform """"SimpleDataType{type=java.lang.String, mimeType='*/*', encoding='null'}"""" to """"SimpleDataType{type=org.mule.extension.http.api.HttpStreamingType, mimeType='*/*', encoding='null'}"""". at org.mule.runtime.core.registry.MuleRegistryHelper.lookupTransformer(MuleRegistryHelper.java:166) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9642","05/02/2016 21:14:04",3,"Map in POJO not populated ""I have a POJO which I'm using in an operation and it contains a Map marked as a Parameter: However, using the following the operation receives a requestBuilder that has a null map causing an NPE: """," @Alias(""""request-builder"""") public class HttpRequesterRequestBuilder { @Parameter @Optional private Map queryParams; public Map getQueryParams() { return queryParams; } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9643","05/02/2016 21:22:18",5,"Expression for Map in POJO not generated ""I have a POJO containing a Map, which is used in an operation: But the schema generated only consideres adding each element explicitly, not via an expression that resolves to a Map: """," @Alias(""""request-builder"""") public class HttpRequesterRequestBuilder { @Parameter @Optional private Map queryParams; public Map getQueryParams() { return queryParams; } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9644","05/03/2016 18:58:33",8,"Add Datasense support for partial fetching of multi-level keys . ""A main concern regarding multiple-level keys was that all the possible combinations of the multiple levels had to be resolved at the same time, on a single fetch. This can be a time-consuming task\ To solve this we should add the possibility of partial construction/fetching of the keys that will be provided, allowing the connector developer to improve the responsiveness if its use case requires it. A possible solution is to add a *List appendChilds(MetadataContext context, T key)* method to the MetadataKeyResolver interface that appends the result List to the partial fetched key. Work started in: https://github.com/mulesoft/mule/tree/partial-key-fetching"""," public interface MetadataKeysResolver { List getMetadataKeys(MetadataContext context) throws MetadataResolvingException, ConnectionException; default MetadataKey appendChilds(MetadataContext context, T partialKey) throws MetadataResolvingException, ConnectionException { return partialKey; } } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9645","05/03/2016 19:48:48",1,"MessageHandler should not restrict CompletionHandler's result type ""Right now the MessageHandler's handle method is defined as: which basically means a Source should produce and expect the same """"kind"""" of MuleMessage since the payload and attributes type must be the same for the message and completionHandler. This is wrong since nothing can be assumed about the flow's result. """," /** * Handles the {@code message} and notifies the result using the given {@code completionHandler} * * @param message the {@link MuleMessage} to be handled * @param completionHandler the {@link CompletionHandler} on which the result is to be notified */ //TODO: MULE-8946: this should actually receive a messaging exception void handle(MuleMessage message, CompletionHandler, Exception> completionHandler); ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9650","05/04/2016 13:25:48",8,"Define initial Mule API ""An initial Mule API must de defined, maybe exposing everything that we expose without isolation, so we can start cleaning it up later.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9651","05/04/2016 13:31:31",3,"Remove visibility of server plugins from applications ""Applications have access to functionality provided by server plugins by getting access to those plugin's classloaders. In mule 4, we want to provide extra functionality only with application plugins, that is removing the visibility of server plugins from the app. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9652","05/04/2016 13:35:33",8,"Define standalone distribution content ""Need to define what would be the content of the standalone distribution: which modules and extensions will be available in the basic distro? If no every available module/extension is shipped on the distro, can the user build custom distributions to include them? ""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9653","05/04/2016 13:38:48",8,"Add a way to share application plugins on the domain ""Provide a way to use application plugins on a domain in order to share resources from those plugins. For example, if HTTP is an application plugin, I would like to share a configuration across the apps in the domain.""","",0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9654","05/04/2016 14:22:53",8,"Add a way to deploy applications that use plugins not packaged in the app ""As part of the isolation improvement on Mule 4, connectors and extensions will be packaged as application plugins. Those application plugins will be deployed inside each application that use them. As the number of used plugins increases, so does the size of the application. Some plugins, In particular Data-weave (when converted to an application plugin) are pretty big which, would make the problem more significative. Problem to solve is then how to define an application that can use plugins that are not packaged inside the application artifact. ""","",0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9660","05/04/2016 20:28:46",0,"OAuth2 authorization-code-grant-type is always expecting a refresh_token when it is optional according to the spec ""h5. Problem According to https://tools.ietf.org/html/rfc6749#section-1.5 refresh_token is optional: {quote} Refresh tokens are credentials used to obtain access tokens. Refresh tokens are issued to the client by the authorization server and are used to obtain a new access token when the current access token becomes invalid or expires, or to obtain additional access tokens with identical or narrower scope (access tokens may have a shorter lifetime and fewer permissions than authorized by the resource owner). Issuing a refresh token is optional at the discretion of the authorization server. If the authorization server issues a refresh token, it is included when issuing an access token (i.e., step (D) in Figure 1). {quote} More detail about this in: https://tools.ietf.org/html/rfc6749#section-5.1 {quote} Successful Response The authorization server issues an access token and optional refresh token, and constructs the response by adding the following parameters to the entity-body of the HTTP response with a 200 (OK) status code: access_token REQUIRED. The access token issued by the authorization server. token_type REQUIRED. The type of the token issued as described in Section 7.1. Value is case insensitive. expires_in RECOMMENDED. The lifetime in seconds of the access token. For example, the value """"3600"""" denotes that the access token will expire in one hour from the time the response was generated. If omitted, the authorization server SHOULD provide the expiration time via other means or document the default value. refresh_token OPTIONAL. The refresh token, which can be used to obtain new access tokens using the same authorization grant as described in Section 6. scope OPTIONAL, if identical to the scope requested by the client; otherwise, REQUIRED. The scope of the access token as described by Section 3.3. {quote} Current implementation of OAuth2 authorization-code-grant-type is expecting always to get refresh_token so if the OAuth2 server during a refresh token operation sends only the access_token Mule is failing to get the refresh_token with the following exception: h5. Proposed Solution As described in the spec if there is a refresh_token issued by the OAuth2 server it should be used for getting new access_tokens if not it should fail when the current access_token is no longer valid (after a 401/403 status code and before retrying the request) and a exception of type should be thrown. For instance: """," {""""access_token"""":""""xCaZDjEo2Um9T8g3OESpi-rzRYOn1o7x865f425JQVw"""",""""token_type"""":""""bearer"""",""""expires_in"""":3599} ERROR 2016-04-05 10:48:16,000 [[oauth].HTTP_Listener_Configuration.worker.02] org.mule.module.oauth2.internal.TokenResponseProcessor: Could not extract refresh token from token URL. Expressions used to retrieve refresh token was #[regex('.*""""refresh_token""""[ ]*:[ ]*""""([^\""""]*)"""".*')] ERROR 2016-04-05 10:48:16,038 [[oauth].HTTP_Listener_Configuration.worker.02] org.mule.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : Access token or refresh token were not found from the refresh token oauth call (org.mule.api.MuleRuntimeException). Message payload is of type: BufferInputStream Code : MULE_ERROR--2 -------------------------------------------------------------------------------- Exception stack is: 1. null (org.mule.module.oauth2.internal.TokenNotFoundException) org.mule.module.oauth2.internal.authorizationcode.AutoAuthorizationCodeTokenRequestHandler:230 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/module/oauth2/internal/TokenNotFoundException.html) 2. Access token or refresh token were not found from the refresh token oauth call (org.mule.api.MuleRuntimeException) org.mule.module.oauth2.internal.authorizationcode.AutoAuthorizationCodeTokenRequestHandler:290 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MuleRuntimeException.html) 3. Access token or refresh token were not found from the refresh token oauth call (org.mule.api.MuleRuntimeException). Message payload is of type: BufferInputStream (org.mule.api.MessagingException) org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor:32 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MessagingException.html) -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.module.oauth2.internal.TokenNotFoundException at org.mule.module.oauth2.internal.authorizationcode.AutoAuthorizationCodeTokenRequestHandler.processTokenUrlResponse(AutoAuthorizationCodeTokenRequestHandler.java:230) at org.mule.module.oauth2.internal.authorizationcode.AutoAuthorizationCodeTokenRequestHandler.doRefreshToken(AutoAuthorizationCodeTokenRequestHandler.java:285) at org.mule.module.oauth2.internal.authorizationcode.AbstractAuthorizationCodeTokenRequestHandler.refreshToken(AbstractAuthorizationCodeTokenRequestHandler.java:56) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** """"Cannot do a refresh token to get a new access token for the default user due to OAuth server did not issued a refresh_token. You would have to re-authenticate the user before trying to execute an operation to the API."""" org.mule.module.oauth2.api.RequestAuthenticationException ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9661","05/04/2016 22:10:36",2,"Make CompletionHandler receive a MuleEvent instead of a MuleMessage ""Right now Sources are forced to create a CompletionHandler that takes a MuleMessage. However, the new message is quite limiting: you can basically only ask for the payload and the data type (attributes too but at that point it won't make too much sense). Things like the encoding cannot be determined. I think it would be best to use a MuleEvent.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9662","05/04/2016 22:38:00",3,"Child element not generated for SubType in Source ""If a message source has a Parameter for which a subtype is defined, the XSD attribute is generated but the XSD element is not""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9664","05/05/2016 15:05:42",3,"Configs with sources require some ""connected"" operation ""i have the following configuration: Then I define the following element: {code:xml} {code} However, when it's parsed the connection is ignored causing the following error: {code} org.mule.runtime.api.connection.ConnectionException: No ConnectionProvider has been registered for owner org.mule.extension.http.api.listener.HttpListenerConfig@5f642a7e {code} It seems the error is in org.mule.runtime.module.extension.internal.config.ConfigurationBeanDefinitionParser#parseConfigurationProvider since the provider is ignored if no """"connected"""" operations are found in the config: {code:java} if (MuleExtensionUtils.getConnectedOperations(configurationModel).isEmpty()) { builder.addConstructorArgValue(new StaticValueResolver<>(null)); return; } {code} As a worked around I added a dummy operation to the config that takes a connection."""," @Configuration(name = """"listener-config"""") @Providers(HttpListenerProvider.class) @Sources(HttpListener.class) public class HttpListenerConfig org.mule.runtime.api.connection.ConnectionException: No ConnectionProvider has been registered for owner org.mule.extension.http.api.listener.HttpListenerConfig@5f642a7e if (MuleExtensionUtils.getConnectedOperations(configurationModel).isEmpty()) { builder.addConstructorArgValue(new StaticValueResolver<>(null)); return; } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9665","05/05/2016 16:05:47",1,"Extensions using external parent doesn't compile due to lack of dependencies ""*Extensions using external parent doesn't compile due to lack of dependencies* * When compiling an Extension using the external extension parent {{mule-extensions-parent}}, fails with the following error: * This issue is because the {{mule-module-extensions-spring-support}} is configured with *test scope*""","[INFO] --- maven-processor-plugin:2.2.4:process (process) @ slack-mule-extension --- [ERROR] diagnostic: error: Annotation processor 'org.mule.runtime.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor' not found [WARNING] diagnostic: warning: Annotation processing without compilation requested but no processors were found.",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9667","05/05/2016 18:47:27",3,"Extension sources should have a CompletionHandler which receives an ExceptionCallback ""Extensions sources use a CompletionHandler to get a callback when the owning flow finishes processing the message. However, if the onComplete() method fails, an ExceptionCallback is needed so that the CompletionHandler notifies that it couldn't handle the response. Notice that this requires having the MuleEvent moved over to mule-api""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9672","05/06/2016 17:07:04",1,"Attributes clash between interface baseType and class subType in schema ""I'm defining the following subtype mapping, where ProxyConfig is an interface, DefaultProxyConfig (alias """"proxy"""") a proper implementation and NtlmProxyConfig (alias """"ntlm-proxy"""") another that extends it: DefaultProxyConfig defines the following parameters: The subtype is then used as a parameter for a ConnectionProvider: When the schema is generated the following are types are defined: Thus a conflict arises since both ProxyConfig and DefaultProxyConfig have the attributes from the latter, which is weird since ProxyConfig is an interface. The following error indicating the clash is thrown when trying to parse a test xml: """," @SubTypeMapping(baseType = ProxyConfig.class, subTypes = {DefaultProxyConfig.class, NtlmProxyConfig.class}) @Parameter private String host; @Parameter private int port = Integer.MAX_VALUE; @Parameter private String username; @Parameter private String password; @Parameter @Optional private ProxyConfig proxyConfig; Caused by: org.mule.runtime.core.api.lifecycle.InitialisationException: Line 474 in XML document from URL [file:/Users/anafelisatti/Mule-old/mule-4.x/mule/extensions/http/target/test-classes/basic-http-config.xml] is invalid; nested exception is org.xml.sax.SAXParseException; systemId: http://www.mulesoft.org/schema/mule/httpn/current/mule-httpn.xsd; lineNumber: 474; columnNumber: 137; ct-props-correct.4: Error for type 'org.mule.extension.http.api.request.proxy.DefaultProxyConfig'. Duplicate attribute uses with the same name and target namespace are specified. Name of duplicate attribute use is 'host'. ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9674","05/06/2016 18:42:29",1,"Loading Interface Metadata type with ExtensionsFieldHandler adds inexistent fields to the MetadataType. ""When using ClassTypeLoader to load an Interface Type with getter methods defined the resulting *MetadataType* contains inexistent fields For example having an Interface Animal like this one: The resulting MetadataType will contain a field named """"speciesName"""" """," public interface Animal { String getSpeciesName(); } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9673","05/06/2016 19:01:31",0,"Upgrade Saxon to 9.6.0.7-HE ""Upgrade Saxon due to several issues have been solved since 9.6.0-7-HE version. * 9.6.0-1-HE is the current version used in Mule: [List of issues solved in Saxon 9.6-HE|https://sourceforge.net/projects/saxon/files/Saxon-HE/9.6/]""","",0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9676","05/09/2016 15:20:45",8,"Add SFTP support to new FTP connector ""Add SFTP support for the new ftp connector implemented in MULE-9216""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9677","05/09/2016 15:48:49",13,"Implement new Email connector ""Implement new email connector for Mule 4""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9678","05/09/2016 15:52:19",13,"Implement new TCP, UDP and SSL connectors ""Implement new TCP, UDP and SSL connectors for Mule 4""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9679","05/09/2016 16:20:52",8,"Review tests for new Email connector ""Make sure that the new EMail connector has 100% feature parity with the old transport""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9680","05/09/2016 16:23:24",13,"Review tests for new TCP/UDP/SSL connectors ""Make sure new connectors have 100% feature parity with the old transport""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9684","05/10/2016 16:15:24",8,"Extensions spring support module is required to use an extension ""In order to use an extension in a project, the following dependency must be present: Otherwise things like abstractConnectionProvider won't be found."""," org.mule.modules mule-module-extensions-spring-support ${project.version} ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9685","05/10/2016 18:03:12",5,"Implicit provider generation fails assigning default value to attribute ""I have a ConnectionProvider with the following optional attribute: Since all it's configuration is quite advanced, defining a connection is not required. However, when I try defining my config without it I get the following error: This is the configuration definition: Defining an empty http:request-connection within it solves the problem."""," @Parameter @Optional(defaultValue = """"-1"""") @Expression(NOT_SUPPORTED) private Integer maxConnections; Caused by: java.lang.IllegalArgumentException: Can not set java.lang.Integer field org.mule.extension.http.api.request.HttpRequesterProvider.maxConnections to java.lang.String at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:167) at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:171) at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81) at java.lang.reflect.Field.set(Field.java:764) at org.springframework.util.ReflectionUtils.setField(ReflectionUtils.java:108) at org.mule.runtime.module.extension.internal.util.FieldSetter.set(FieldSetter.java:42) at org.mule.runtime.module.extension.internal.util.SingleValueSetter.set(SingleValueSetter.java:51) at org.mule.runtime.module.extension.internal.runtime.ParameterGroupAwareObjectBuilder.setValues(ParameterGroupAwareObjectBuilder.java:79) at org.mule.runtime.module.extension.internal.runtime.ParameterGroupAwareObjectBuilder.build(ParameterGroupAwareObjectBuilder.java:57) at org.mule.runtime.module.extension.internal.runtime.config.ConnectionProviderObjectBuilder.build(ConnectionProviderObjectBuilder.java:67) at org.mule.runtime.module.extension.internal.runtime.config.ConnectionProviderObjectBuilder.build(ConnectionProviderObjectBuilder.java:28) at org.mule.runtime.module.extension.internal.runtime.ParameterGroupAwareObjectBuilder.build(ParameterGroupAwareObjectBuilder.java:49) at org.mule.runtime.module.extension.internal.runtime.config.DefaultImplicitConnectionProviderFactory.createImplicitConnectionProvider(DefaultImplicitConnectionProviderFactory.java:46) at org.mule.runtime.module.extension.internal.runtime.resolver.ImplicitConnectionProviderValueResolver.lambda$new$95(ImplicitConnectionProviderValueResolver.java:43) at org.mule.runtime.module.extension.internal.runtime.resolver.ImplicitConnectionProviderValueResolver.resolve(ImplicitConnectionProviderValueResolver.java:54) at org.mule.runtime.module.extension.internal.runtime.resolver.ImplicitConnectionProviderValueResolver.resolve(ImplicitConnectionProviderValueResolver.java:30) at org.mule.runtime.module.extension.internal.runtime.config.ConfigurationInstanceFactory.createConfiguration(ConfigurationInstanceFactory.java:112) at org.mule.runtime.module.extension.internal.runtime.config.DefaultConfigurationProviderFactory.createStaticConfigurationProvider(DefaultConfigurationProviderFactory.java:62) at org.mule.runtime.module.extension.internal.config.ConfigurationProviderFactoryBean.getObject(ConfigurationProviderFactoryBean.java:80) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9686","05/10/2016 21:51:17",8,"Wrong schema generation when Parameter List has a name that cannot be singularised. ""Having a List @Parameter attribute with a name that cannot be singularised is generating the childs with the same name as the parent. So for this cases the child name should be composed by the parent name and append to it a *-item*. For example having The generated schema will contain something like this for this element: The parent should be named *bcc* and the child *bcc-item* """," @Parameter private List bcc; ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9689","05/11/2016 18:12:54",3,"Split Jar reactor from Distribution reactor ""APIkit is included in Mule distribution, but it depends on the Mule jars. To build Mule distribution we need first to build the jars, then build APIkit and then the distribution.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9698","05/12/2016 17:14:49",8,"Migrate basic security filter to HTTP extension ""HttpBasicAuthenticationFilter needs to be migrated in a way that allows the same functionality to be used.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9705","05/12/2016 18:02:13",8,"Remove HTTP module - Migrate tests ""Migrate tests that use the old http module to use the new extension""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9706","05/13/2016 00:02:20",5,"Reintroduce TCP/SSL transports ""Bring those transports back.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9709","05/16/2016 18:34:55",3,"Validate SubTypes and BaseType alias names are not the same ""When using SubTypes mapping, if a subtype declares the same alias name that its base type or some of its peers, then model validation should fail.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9711","05/17/2016 13:51:53",3,"Change namespaces of the transports ""This so they do not conflict with the new extensions for Mule 4.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9713","05/17/2016 17:57:19",1,"Top level parameters are not being registered for configuration specific operations ""Actually when registering top level parameters the sdk introspect every configuration parameter and every extension operation parameter. It must also introspect all the operations that are configuration specific. In order to achieve this the _ExtensionNamespaceHandler#registerTopLevelParameters_ method should be updated with that logic.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9715","05/17/2016 19:48:44",3,"Rename operation is missing a overwrite feature in the new file and ftp connectors ""When a file is renamed, a FileWriteMode is missing for the cases in which the target file already exists""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9716","05/17/2016 19:51:30",1,"Subtypes model property should not be externalizable ""Subtypes model property should not be externalizable""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9717","05/17/2016 23:13:51",5,"Extensions should not depend on mule-module-extensions-spring-support ""*Extensions should not depend on mule-module-extensions-spring-support* - In a opposite way that MULE-9665 do, extensions should not depend on {{mule-module-extensions-spring-support}}.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9718","05/18/2016 19:02:55",3,"Collections of enums not supported as child elements ""When an extension has a collection of enums as a parameter, the XSD only supports it as a expressionList attribute. It should be possible to also define it statically as child elements""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9719","05/18/2016 19:07:32",5,"Output MetadataResolvers should consider the message attributes ""Currently the output metadata resolvers only represent the message payload. There're cases in which it's also necessary to represent the message attributes (e.g.: when the attribute type is an interface). It should be possible to provide a resolver to handle such cases""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9721","05/19/2016 13:36:42",5,"Complex type child elements not parsed when default value is set ""In operations with complex parameters that have a default value like the following: Then, support for creating the parameter as child element is provided, but is always overridden by the attribute's default value. In the example, the operation will always take the users List form the """"users"""" attribute, instead of parsing the child elements """," public void create(@Optional(defaultValue=""""#[payload]"""") List users) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9723","05/19/2016 17:43:26",1,"TlsContextFactory not properly parsed when used as extension parameters ""When extensions take TLsContextFactory as parameters, the keyStore and trustStore elements are ignored injecting a blank TlsContextFactory which doesn't honour much of its config.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9725","05/19/2016 19:15:17",0,"Refactor FTP connector code to allow FTPS one to reuse it ""Do some refactoring so that code is more reusable by the FTPS connector""","",0,0,0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9727","05/20/2016 16:23:22",5,"Extension plugin not working if annotated class defines an operation that uses an enum class not included in the same package ""If the extension declares an operation that uses an enum class and it is not in the same package as the extension annotated class when application that uses this plugin is deployed it will fail due to the application classloader is not able to find the operation class when registering the extension. This happens due to the exported packages is only fulfilled with the package of the extension annotated class. As an example the mule-module-validation defines the extension: so the metadata for the plugin would have this package as exported but at the same time the extension defines an operations with classes in the same package but internally end up using classes from For this example the classes are: ValidationExtension->NumberValidationOperation->NumberType. Where NumberType is an enum.""","artifact.export.classPackages=org.mule.extension.validation.internalorg.mule.extension.validation.internal.ValidationExtensionorg.mule.extension.validation.internal.validator",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9729","05/20/2016 20:19:13",1,"Upgrade grizzly to 2.3.25 ""We need to upgrade to the latest version to be released around May 23 (2016).""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9730","05/20/2016 20:24:59",5,"Support grizzly's PRESERVE_HEADER_CASE property ""Right now, all incoming headers are transformed to lower case by Grizzly. Thus all our code is based around that, meaning when we need a header like """"Host"""" we ask for """"host"""", same with """"Content-Type"""" and others. However, the introduction of Grizzly property org.glassfish.grizzly.http.PRESERVE_HEADER_CASE means that when it's set to true all that code will fail. The property is very important for proxy scenarios where the headers received are meant to be sent back to another service exactly as received. We should make sure our code works with that property and add tests to verify the proxy scenario is valid.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9731","05/22/2016 16:26:52",13,"Migrate 3.7 ReplyToHandler centric non-blocking support to use reactive streams API ""The existing approach has significant limitations and is a maintenance issue.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9732","05/23/2016 14:36:33",8,"DefaultExtensionFactory is setting the incorrect ClassLoader ""While doing some changes to classloaders as part of MULE-9652 I found that there is an issue related to how the extension classloader is set. I'm testing my changes by using validations extensions in my application. h5. Problem DefaultExtensionFactory is setting MuleContainerSystemClassLoader instead of the application classloader when creating the RuntimeExtensionModel on method: Actually, the extensionDeclarer has the correct reference to the app classloader: h5. Expected result Application should be successfully deployed and started h5. Actual result I'm getting a classnotfoundexception while the extension namespace handler is being registered. See log attached to the issue."""," public RuntimeExtensionModel createFrom(ExtensionDeclarer declarer) typeLoader->MuleArtifactClassLoader (name: mule-validation-4.0-SNAPSHOT) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9733","05/23/2016 17:08:44",1,"Injected config not present during source initialisation ""I have an Initialisable Source that references it's config: However, when initialise() runs, the config is null."""," @Alias(""""listener"""") public class HttpListener extends Source implements Initialisable { private static final Logger logger = LoggerFactory.getLogger(HttpListener.class); private static final String SERVER_PROBLEM = """"Server encountered a problem""""; @UseConfig private HttpListenerConfig config; ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9735","05/23/2016 21:07:06",5,"Mapped subtype from a different module than its baseType is not parsed correctly ""When extension A Imports a baseType """"Fruit"""" from extension B, and maps it to a new subtype """"Apple"""" (declared in A), when """"Apple"""" is used as a parameter of some B component, then the parsing fails not finding the type """"Apple"""" instantiate. For the declarations: Then, the following xml is valid for the schema, but the parser fails to instantiate the Apple """," @Extension(name = """"SubtypesConnector"""") @Xml(namespace = """"subtypes"""", namespaceLocation = """"http://www.mulesoft.org/schema/mule/subtypes"""") @Import(type = Fruit.class, from = HeisenbergExtension.class) @SubTypeMapping(baseType = Fruit.class, subTypes = {Apple.class}) public class SubTypesMappingConnector { //... public class HeisenbergExtension { @Parameter private Fruit myFruit; ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9780","05/23/2016 23:06:19",1,"Metadata model properties should not reference classes ""Trying to get the extension from a mule app does not work. When asking for a single instance the serializer crashes with the error: {""""errorType"""":""""class java.lang.ClassCastException"""", """"errorMessage"""":""""com.google.common.collect.SingletonImmutableSet cannot be cast to java.util.List""""} When asking for the entire list the error is: {""""errorType"""":""""class java.lang.UnsupportedOperationException"""", """"errorMessage"""":""""Attempted to serialize java.lang.Class: java.lang.String. Forgot to register a type adapter?""""} This happens because the MetadataKeyIdModelProperty class references types by class instead of using a MetadataType. The mule app is a simple app that lists files of a directory: """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9736","05/24/2016 01:53:39",2,"Add the capability to add attributes to the MuleMessage generated by the TestEventRunner ""The framework that we use today to run the tests is outdated with some of the changes that are going on in mule 4, because of that, we can't run a flow with a message that contains attributes. Would be ideal if we can add a method to the FlowConstructRunner _withAttributes(Serializable attributes)_ so we can prepare the flow this way """," ... flowRunner(""""flowName""""). withPayload(someObject). withAttributes(someSerializableAttributes). run(); ... ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9738","05/24/2016 14:27:36",13,"Improve functional test case to work with extensions ""Functional test case uses a filtering classloader similar to the one used on the standalone container in order to reproduce a similar behaviour. That classloader uses a filter that exposes only the mule API. That filter is created using the available mule-module.properties files. In order to use created extensions on functional test cases, each extension must currently provide a mule-module.properties file. This file is only used for testing purposes and must be removed and improve the functional test case to use the API information already defined in the extension descriptor.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9741","05/24/2016 22:03:28",0,"Deadlocks comparing MuleEndpointURI ""A deadlock was found when comparing instances of MuleEndpointURI under load. To reproduce use this code: """," public class ParallelMuleEndpointURIComparison { public static void main(String[] args) throws URISyntaxException, InterruptedException { Properties props1 = System.getProperties(); Properties props2 = new Properties(); for (Map.Entry entry : System.getProperties().entrySet()) { props2.put(entry.getKey() + """"2"""", entry.getValue()); } final MuleEndpointURI uri1 = new MuleEndpointURI("""""""", """""""", """""""", """""""", """""""", props1, new URI(""""http://localhost""""), null); final MuleEndpointURI uri2 = new MuleEndpointURI("""""""", """""""", """""""", """""""", """""""", props2, new URI(""""http://localhost""""), null); ExecutorService pool = Executors.newFixedThreadPool(10); pool.submit(new Runnable(){ @Override public void run() { for (int i = 0; i < 1000; i++) { System.out.println(""""comparing 1 to 2 - """" + i); uri1.equals(uri2); } } }); pool.submit(new Runnable(){ @Override public void run() { for (int i = 0; i < 100000; i++) { System.out.println(""""comparing 2 to 1 - """" + i); uri2.equals(uri1); } } }); pool.shutdown(); pool.awaitTermination(1, TimeUnit.DAYS); System.out.println(""""end""""); } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9748","05/26/2016 12:31:41",0,"Analyse CurrentEventHolder use in HTTP extension ""Moving to 4.0, we need to analyse whether all the RequestContext related code is still necessary in the HTTP extension.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9749","05/26/2016 12:33:40",0,"Analyse ResponseFailureCallback changes impact ""Some small changes were required in the response callback used for failures. We need to make sure they don't impact the behaviour of the extension.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9752","05/26/2016 17:03:08",13,"Define services for the mule container ""Fill details ""","",0,1,0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9753","05/26/2016 17:04:30",8,"Classloading model prone to linkage errors ""Current classloading model suffers from LinkageErrors when applications or plugins redefine classes from the container classloader, and those classes are exposed through the API. Example: Container has and application classloader contains: When the application executes new C(), the linkage error will be thrown as the B parameter passed to A, is the B from the application classloader, instead of being the one from the container."""," package org.foo; public class A { public String doStuff(B b) { return b.doStuff(); } } package org.foo; public class B { public String doStuff() { return """"Done stuff on main classloader""""; } } package org.foo; public class C { public C() { new A().doStuff(new B()); } } package org.foo; public class B { public String doStuff() { return """"Done stuff on app classloader""""; } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9755","05/26/2016 17:30:09",1,"Add the concept of extension walker ""As the ExtensionModel grows in complexity how to navigate and find things on it also becomes harder, which leaves to bugs or omissions. Create the concept of ExtensionWalker so that the complexity can be abstracted.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9759","05/27/2016 15:06:00",5,"Change test extensions packaging from jar to mule-extension ""We need to update the packaging of the test extensions so that we can use them inside mule apps""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9760","05/27/2016 15:07:09",1,"Connection leak if pooling listener fails ""If a Connection provider is pooling connections and the pooling listener fails to execute the onBorrow() method, then the connection is not returned to the pool nor invalidated. ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9761","05/27/2016 17:19:27",5,"Validate the creation of recursive MetadataKeys ""*Validate the creation of recursive MetadataKeys* Nowadays exist two border cases of {{MetadataKey}} creation: * *Recursive Keys:* When creating a multilevel key, you can set a child for a key, this is adding a new level to the MetadataKey, but the problem comes when this child is a parent in the key hierarchy creating a recursive relationship. Besides of been a invalid case this also can be a source of bugs for the parts that uses MetadataKeys: MetadataKey serialiser, this kind of recursive structure produces a {{StackOverflowError}} when trying to serialise the object.{code:title=Recursive keys|bgColor=#FFFFCE} Root Key + | v +->Key1 | + | | | v | Key2 | + +---+ """," Root Key + | v +->Key1 | + | | | v | Key2 | + +---+ Root + +----------------+ v v v Key1 Key2+---->Key3 + +--+----+ v v Key3A Key3B",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9763","05/27/2016 17:51:42",1,"A warning is not shown when using default baseDir ""According to the spec this config should show a WARNING in start time because it is using the default baseDir: """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9765","05/27/2016 19:12:44",2,"move current sockets module to the transport compatibility layer ""move current sockets module to the transport compatibility layer, using a different maven group and artifact ids, so that it doesn't conflicts with the new sockets extension""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9768","05/27/2016 21:05:59",2,"Sources are instantiated twice ""ExtensionMessageSource creates the source during initialisation and during start (because of the reconnection strategy). The issue was fixed in MULE-9490 because it was blocking the task but now we need to add a test.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9769","05/27/2016 21:46:48",8,"ExtensionModel should say where is dynamic metadata supported ""It should be possible by just looking at the ExtensionModel to know which operation parameters support dynamic metadata and which operation have dynamic return types""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9770","05/27/2016 22:00:58",2,"include json representation of ExtensionModel inside extension's jar ""For external reference, the extension's jar should include a extension_model.json file with the JSON representation of the model""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9772","05/27/2016 22:08:48",8,"Extension sources should include the concept of ExchangePattern ""Sources should have the concept of Exchange pattern to indicate if they generate a response or not. * First, a source should declare which patterns it does support (at least one). * The supported types should be accesible from the SourceModel * If the source supports more than one, then the SDK should generate DSL support so that the desired type is configurable * The selected exchange pattern should be available in Runtime through the SourceContext * It is the source's responsibility to honour that MEP, SDK will not enforce it ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9776","05/30/2016 15:36:56",0,"Fix the http-ext to include it as a zip in the distribution ""Fix HTTP Extension to generate a zip and include it in the app-plugins folder to be treated as plugins. We should wait until the validations extension is fixed to move forward though.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9777","05/30/2016 15:38:39",0,"Review per-app logging on mule 4 ""On mule 4, there are different types of mule artifacts. It must be defined what is the expected behaviour of those artifacts regarding logging. As logging is highly related to classloading (because the logging context is tracked by classlaoder), the new estructure of artifacts/classlaoders should be reviewed from the logging perspective and define how each artifact is supposed to log.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9778","05/30/2016 15:53:44",0,"MuleLoggerContextFactory should not create artifact descriptors ""MuleLoggerContextFactory is creating artifact descriptors in order to determine which logging configuration should be used. Creating descriptors requires to access the file system and requires and requires to create the artifact factories. In some cases, creating the artifact factory would require to create many different objects. To avoid these problems the MuleLoggerContextFactory should use a service that searches for descriptors available in the deployment service's dependencies.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9779","05/30/2016 16:50:58",8,"Extensions should generate studio plugin ""Whatever Devkit does""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9782","05/30/2016 23:01:44",0,"Add RAML metadata support to HTTP extension ""The RAML metadata support was outside of the HTTP module but we now need to move it to the extension.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9784","05/31/2016 17:43:42",2,"Missing i18n resource for validation extension ""mule-module-validation when deployed as app-plugin (extension) it is not able to access its i18n resource bundle. h5. Problem Resource is not accessible due to org.mule.runtime.core.config.i18n.MessageFactory.getBundlePath() uses dot characters instead of slash characters. Exception: h5. Proposed solution * To use slash instead of dot character for referencing to i18n resources due to they are exported as folders in MessageFactory * Export the i18n resource file using annotation from Extensions API so it will be accessible from the plugin classloader"""," Root Exception stack trace: java.util.MissingResourceException: Can't find bundle for base name META-INF.services.org.mule.runtime.core.i18n.validation-messages, locale en_US at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1564) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1387) at java.util.ResourceBundle.getBundle(ResourceBundle.java:1082) at org.mule.extension.validation.internal.ValidationMessages.getBundle(ValidationMessages.java:68) at org.mule.runtime.core.config.i18n.MessageFactory.getString(MessageFactory.java:198) at org.mule.runtime.core.config.i18n.MessageFactory.createMessage(MessageFactory.java:113) at org.mule.runtime.core.config.i18n.MessageFactory.createMessage(MessageFactory.java:64) at org.mule.extension.validation.internal.ValidationMessages.invalidEmail(ValidationMessages.java:132) @Export(resources = {""""/META-INF/services/org/mule/runtime/core/i18n""""})",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9788","05/31/2016 21:56:46",0,"Re-enable PGP security tests ""PGP Tests are being skipped when no JCE installed because in previous versions of the JDK, some encryption methods were not available without JCE. Now we need to re-enable them.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9790","06/01/2016 15:13:56",8,"Provider not found error when running Mule Standalone ""When an application/domain is deployed the following """," INFO 2016-06-01 10:37:29,277 [WrapperListener_start_runner] org.mule.runtime.module.launcher.coreextension.DefaultMuleCoreExtensionManagerServer: Initializing core extensions INFO 2016-06-01 10:37:29,349 [WrapperListener_start_runner] com.mulesoft.mule.runtime.cluster.hazelcast.config.ClusterTicketFileLoader: /Users/guillermofernandes/Development/mule-ee/distributions/standalone/target/mule-enterprise-standalone-4.0-SNAPSHOT/.mule/mule-cluster.properties (No such file or directory) WARN 2016-06-01 10:37:29,354 [WrapperListener_start_runner] com.mulesoft.mule.runtime.cluster.boot.ClusterCoreExtension: No cluster ID was specified -- High Availability will be disabled: INFO 2016-06-01 10:37:29,370 [WrapperListener_start_runner] org.mule.runtime.module.launcher.coreextension.DefaultMuleCoreExtensionManagerServer: Starting core extensions INFO 2016-06-01 10:37:29,379 [WrapperListener_start_runner] org.mule.runtime.module.launcher.DefaultArchiveDeployer: ================== New Exploded Artifact: default ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider jdk.nashorn.api.scripting.NashornScriptEngineFactory not found ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider org.jruby.embed.jsr223.JRubyEngineFactory not found ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider jdk.nashorn.api.scripting.NashornScriptEngineFactory not found ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider org.jruby.embed.jsr223.JRubyEngineFactory not found ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9798","06/01/2016 22:25:41",1,"If a domain fails to be deployed a NPE is thrown when deploying and app that is registered for the same domain ""If the domain fails to be deployed then when an application is about to be deployed a NPE is thrown and also the status logged in console throws another NPE. Domain: Then application throws a NPE: Finally the MuleDeploymentService throws another NPE: """," INFO 2016-06-01 14:43:56,798 [WrapperListener_start_runner] org.mule.runtime.module.launcher.DefaultArchiveDeployer: ================== New Exploded Artifact: my-domain ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider jdk.nashorn.api.scripting.NashornScriptEngineFactory not found ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider org.jruby.embed.jsr223.JRubyEngineFactory not found ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider jdk.nashorn.api.scripting.NashornScriptEngineFactory not found ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider apple.applescript.AppleScriptEngineFactory not found ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider org.jruby.embed.jsr223.JRubyEngineFactory not found INFO 2016-06-01 14:44:01,480 [WrapperListener_start_runner] org.mule.runtime.module.launcher.domain.DefaultMuleDomain: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Disposing domain 'my-domain' + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ERROR 2016-06-01 14:44:01,544 [WrapperListener_start_runner] org.mule.runtime.module.launcher.DefaultArchiveDeployer: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Failed to deploy artifact 'my-domain', see below + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ org.mule.runtime.module.launcher.DeploymentInitException: SAXParseException: The prefix """"validation"""" for element """"validation:config"""" is not bound. ... INFO 2016-06-01 14:44:24,291 [WrapperListener_start_runner] org.mule.runtime.module.launcher.DefaultArchiveDeployer: ================== New Exploded Artifact: validations-classloader-isolation ERROR 2016-06-01 14:44:35,182 [WrapperListener_start_runner] org.mule.runtime.module.launcher.DefaultArchiveDeployer: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Failed to deploy exploded artifact: + + 'validations-classloader-isolation', see below + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ java.lang.NullPointerException at org.mule.runtime.module.launcher.application.DefaultApplicationFactory.createAppFrom(DefaultApplicationFactory.java:97) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.application.DefaultApplicationFactory.createArtifact(DefaultApplicationFactory.java:84) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.application.DefaultApplicationFactory.createArtifact(DefaultApplicationFactory.java:42) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArchiveDeployer.deployExplodedApp(DefaultArchiveDeployer.java:283) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:114) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:41) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DeploymentDirectoryWatcher.deployExplodedApps(DeploymentDirectoryWatcher.java:290) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DeploymentDirectoryWatcher.start(DeploymentDirectoryWatcher.java:151) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.MuleDeploymentService.start(MuleDeploymentService.java:120) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.MuleContainer.start(MuleContainer.java:175) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_65] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_65] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_65] at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_65] at org.mule.runtime.module.reboot.MuleContainerWrapper.start(MuleContainerWrapper.java:52) ~[mule-module-boot-ee-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4242) ~[wrapper-3.5.29.jar:3.5.29] INFO 2016-06-01 14:44:35,185 [WrapperListener_start_runner] org.mule.runtime.module.launcher.DeploymentDirectoryWatcher: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Mule is up and kicking (every 5000ms) + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ERROR 2016-06-01 15:32:15,272 [WrapperListener_start_runner] org.mule.runtime.module.launcher.MuleDeploymentService: java.lang.NullPointerException ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9802","06/02/2016 15:23:10",1,"Manifest generator should use ExtensionWalker ""Replace the custom iteration logic in ExportedArtifactsCollector with the ExtensionWalker""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9807","06/02/2016 21:39:44",8,"Byte to ByteArray ends up serialising Byte ""When the payload is a {{java.lang.Byte}} instead of returning that value HTTP listener returns its serialized value or something else. To reproduce deploy the below flow and run {{curl -i http://localhost:8081/http-respose-byte}}. This occurs because the default is to seek a transformation to a ByteArray and the ObjectToByteArray transformer does not handle single Bytes, so SerializableToByteArray is used instead. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9808","06/02/2016 21:41:18",1,"Lifecycle is not being applied on the connection used in a Message Source ""If a source uses a connection that implements Initialisable interface, the initialise method is not being invoked. This doesn't happen to the connections used for operations. The test for this bug should consist in: Implementing Initialisable on HeisenbergConnection and setting some value during the initialise phase, and then check that value was correctly set. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9810","06/03/2016 14:43:16",1,"Avoid exclusions for transitive dependencies in all-extensions pom ""As part of the distributions we have a pom artifact that groups the extensions that would be added to the distro as apps-plugins. These extensions have to be declared as zip type but as currently the maven-assembly-plugin is configure to build the lib/opt folder we have a limitation due to libraries from these extensions are being copied to the lib/opt. This issue is forcing us to duplicate ourselves when declaring dependencies in extensions due to they also have to be excluded. There is a open bug in maven-assembly-plugin related to this issue, it is supposed to work if you do wildcard exclusion: https://issues.apache.org/jira/browse/MASSEMBLY-799""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9811","06/03/2016 17:20:13",5,"Introduce the concept of @NoRef parameters ""Currently, parameters of complex types support either expressions or static string values. When a static string is supplied, it is interpreted as a reference to an object on the Mule Registry. There're cases such as in which the content attribute should be of type Object, but the static """"blah"""" value should not be interpreted as a reference, but as the actual String """"blah"""". To support these cases, the @NoRef attribute needs to be created. It can be applied either to an operation parameter or a configuration field. Should also include updating connectors such as File, FTP and Http ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9813","06/03/2016 19:42:18",3,"Extract plugin-only functionality from extensions-maven-plugin ""For plugins, the assembly functionality of mule-extensions-maven-plugin is needed. It has to be extracted and reutilized by both plugins and extensions builder.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9815","06/03/2016 20:25:42",3,"Thrown exceptions are unwrapped and trace is lost ""Most exceptions that our internal HTTP client throws are wrapped in a IOException, thus the expected cause of a MessagingException from the HTTP requester is an IOException. However, most migrated test are failing because the exceptions received are more """"lower level"""". For example, in HttpRequestTlsInsecureTestCase the exception received is a java.security.cert.CertificateException.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9820","06/05/2016 01:41:59",13,"Add the concept of part name/level to MetadataKeys ""*Add the concept of part name/level to MetadataKeys* * Nowadays {{MetadataKeys}} are able to have {{MetadataKeys}} childs to represent multilevel metadata keys, the problem comes that each level of metadata key doesn't know to which part of the entire multi level MetadataKey represent. * Doesn't having the name of the level inside the MetadataKey complex the Metadata resolution due that there is not way to ensure that each MetadataKey is really the level that the resolution needed.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9821","06/06/2016 13:46:05",8,"Improve MetadataResult error communication ""*Improve MetadataResult error communication* * Nowadays when resolving metadata, this result are wrapped within a {{MetadataResult<>}}, this wrapper helps communicating if the resolutions finished correctly or not, and in this last case, communicates which was the error message. * For cases where the resolution is just for input or output, the error message is very simple, because there is a unique error for the single resolution, the problem comes when resolving the metadata for the entire {{Component}}, so you resolve metadata for the *input* and *output* at the same time, and in the case that something fails you receive a message that you don't know where it came from (input or output), or in a worst scenario you get 2 error messages which you don't know how are their fathers.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9822","06/06/2016 15:50:14",0,"Logged error should suggest how to enable flowstack ""When an error is logged there is a hint about how to enable verbose logging: We should add: """," ERROR 2016-06-06 11:44:45,970 [[default].HTTP_Listener_Configuration.worker.01] org.mule.runtime.core.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : /: Is a directory. Element : /payload-is-path/processors/2 @ default -------------------------------------------------------------------------------- Exception stack is: /: Is a directory. (org.mule.runtime.core.api.MessagingException) sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434) java.nio.file.Files.newOutputStream(Files.java:216) org.mule.extension.file.internal.command.LocalWriteCommand.getOutputStream(LocalWriteCommand.java:81) org.mule.extension.file.internal.command.LocalWriteCommand.write(LocalWriteCommand.java:63) org.mule.runtime.module.extension.file.api.AbstractFileSystem.write(AbstractFileSystem.java:110) (103 more...) (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) (set debug level logging or '-Dmule.verbose.exceptions=true' for everything, or '-Dmule.flowTrace=true' for enabling flow stack information) ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9824","06/06/2016 15:57:12",3,"Rename transports packages so they don't collide with the core packages ""package org.mule.runtime is reserved for the runtime core classes. Classes in the compatibility plugin must have a different package prefix so they can be properly loaded by the new classloaders.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9826","06/06/2016 17:16:01",0,"HTTP timeout when sending x-www-form-urlencoded POST ""To reproduce deploy the attached config and run {{curl -X POST -d 'a=1&b=2' http://127.0.0.1:8081/print-payload}}""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9830","06/06/2016 19:30:12",3,"file:write doesn't preserve encoding when writing an String ""I want to be able to create an String with an encoding different from the default platform encoding during my flow execution and later write that String in a file with that encoding.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9831","06/06/2016 19:34:09",3,"I cannot write an String to a file with an arbitrary encoding ""I have created an String with ASCII encoding and I want to write it in a file with encoding UTF-16.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9834","06/06/2016 22:53:11",1,"Make management work in the compatibility module ""Fix management support for transport/endpoint specific stuff.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9837","06/07/2016 14:50:38",3,"Attributes are not copied when MuleMessage is ""When analysing some test that use a test queue element, the returned message had no attributes. The queue copies the event (and thus the message) but the attributes are not copied so they are lost.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9838","06/07/2016 15:06:11",5,"StringIndexOutOfBoundsException is thrown while documenting the schema with javadoc ""StringIndexOutOfBoundsException is thrown while documenting the schema with javadoc. """," [ERROR] diagnostic: error: Exception found while trying to document XSD schema org.mule.runtime.core.api.MuleRuntimeException: Exception found while trying to document XSD schema at org.mule.runtime.module.extension.internal.capability.xml.schema.SchemaDocumenter.documentOperations(SchemaDocumenter.java:101) at org.mule.runtime.module.extension.internal.capability.xml.schema.SchemaDocumenter.document(SchemaDocumenter.java:71) at org.mule.runtime.module.extension.internal.capability.xml.schema.SchemaDocumenterModelEnricher.enrich(SchemaDocumenterModelEnricher.java:58) at org.mule.runtime.module.extension.internal.introspection.DefaultExtensionFactory.lambda$enrichModel$1(DefaultExtensionFactory.java:339) at java.lang.Iterable.forEach(Iterable.java:75) at org.mule.runtime.module.extension.internal.introspection.DefaultExtensionFactory.enrichModel(DefaultExtensionFactory.java:339) at org.mule.runtime.module.extension.internal.introspection.DefaultExtensionFactory.createFrom(DefaultExtensionFactory.java:123) at org.mule.runtime.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.parseExtension(ExtensionResourcesGeneratorAnnotationProcessor.java:107) at org.mule.runtime.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.lambda$null$17(ExtensionResourcesGeneratorAnnotationProcessor.java:82) at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:1214) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1193) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1213) at org.mule.runtime.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.lambda$process$18(ExtensionResourcesGeneratorAnnotationProcessor.java:81) at java.util.Optional.ifPresent(Optional.java:159) at ... ... Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: 0 at java.lang.String.charAt(String.java:658) at org.mule.runtime.module.extension.internal.capability.xml.schema.AnnotationProcessorUtils.parseJavaDoc(AnnotationProcessorUtils.java:345) at org.mule.runtime.module.extension.internal.capability.xml.schema.AnnotationProcessorUtils.getMethodDocumentation(AnnotationProcessorUtils.java:180) at org.mule.runtime.module.extension.internal.capability.xml.schema.SchemaDocumenter.documentOperations(SchemaDocumenter.java:94) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9840","06/07/2016 16:02:36",1,"Make a reusable ActiveMQ Broker for tests ""Make a reusable junit Rule for starting AMQ since that will be needed also in the system tests and the new JMS extension.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9845","06/08/2016 15:01:53",0,"When assembling extensions/plugins, exclude dependencies with boot/system packages ""This is to avoid including libraries in the assembly that will not be used. This has to go hand in hand with a mechanism to determine which are those dependencies (currently, we only have a packages list in ContainerClassLoaderFactory#SYSTEM_PACKAGES and #BOOT_PACKAGES)""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9846","06/08/2016 17:09:42",3,"New parsers should support list of simple types ""Currently, the new parsers support parsing childs of complex types through the fromChildConfiguration factor method. We need something similar so that things such as List or List can also be parsed. Example, List of String called pets As an additional suggestion, I would rename fromChildConfiguration to fromChildParameter, or something like that """," ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9847","06/08/2016 21:01:26",3,"Add the capability to register multiple XmlInfoProviders ""Currently, the XmlInfoProviders are obtained via SPI. We need an api so that they can be added programatically by a ComponentBuildingDefinitionProvider""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9848","06/08/2016 21:04:38",3,"Need to be able to provide the collection type when parsing a List ""When parsing a child list (either complex or simple types), there should be a way to provide a Supplier which instantiates a custom type of collection. These might also lead to change the API so that the AttributeDefinition refers simply to collections instead of Lists""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9850","06/08/2016 21:29:40",0,"Lifecycle not applied on ObjectFactory output ""When a component definition uses an ObjectFactory, lifecycle is applied on it but not on the object that it produces. It should be applied on both""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9851","06/08/2016 21:41:46",5,"Support for parsing maps ""Need to add support for parsing Maps. Just like with collections, it should be possible to provide a Supplier which creates the map instance Examples of desired syntax: *From String to list of strings* {code:xml} {code} *From String to Long* {code:java} private Map recipe; {code} {code:xml} {code} *From String to Object* {code:java} private Map labeledRicin; {code} {code:xml} {code}"""," private Map> deathsBySeasons; private Map recipe; private Map labeledRicin; ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9852","06/08/2016 21:50:48",1,"Empty domain log files created for each extension ""When you start Mule with the default application these empty log files are created: Even if you use the extension nothing is added to those files."""," mule-domain-mule-module-file-4.0-SNAPSHOT.log mule-domain-mule-module-ftp-4.0-SNAPSHOT.log mule-domain-mule-module-ftps-4.0-SNAPSHOT.log mule-domain-mule-module-validation-4.0-SNAPSHOT.log ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9853","06/08/2016 22:35:47",0,"Support DI on ObjectFactory ""It'd be great to be able to have dependencies injected in an ObjectFactory. Consider that it might not be possible to inject anything since by the time the getObject() method is invoked the spring registry might not yet be available, or maybe there's still not enough information to instantiate objects int the right order. But at the very least, if the beans available on the SimpleRegistry (MuleContext, ConnectionManager, etc) could be injected, that'd be great.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9854","06/08/2016 22:40:31",3,"List of pojos not parsed ""Run ParameterizedConfigParserTestCase and place a breakpoint to obtain the configuration named heisenberg. The ricinPacks collection is null although properly defined on the definition provider.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9855","06/09/2016 11:14:56",8,"Make MuleMessage immutable ""Make MuleMessage immutable""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9856","06/09/2016 11:15:19",8,"Create MuleMessage builder ""Create MuleMessage builder""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9858","06/09/2016 11:16:59",5,"Make Message CorrelationId/SequenceID etc. message attributes rather than properties ""Make Message CorrelationId/SequenceID etc. message attributes rather than properties""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9860","06/09/2016 14:55:48",5,"Define API for connectivity testing - Connection repository ""We need to define the mule API for doing connectivity testing when someone is defining a new connection or trying to test connection over a connection created in the connection repository.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9861","06/09/2016 14:58:40",8,"Dev tooling connectivity testing API implementation - Application ""Implementation of API defined in MULE-9704. It seems we will have to rethink some of the capabilities of ExtAPI and move it to the runtime now that we have better capabilities over the mule configuration.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9862","06/09/2016 15:01:58",13,"Connection repository connectivity testing API implementation ""Implementation of API defined by MULE-9860""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9863","06/09/2016 15:08:51",1,"Define commons-pool version in dependency management ""Extract commons-pool version to a property and use it from dependencyManagemnt""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9864","06/09/2016 15:29:20",3,"Support expression in HTTP response builder headers field ""To make it possible for other teams to use the HTTP extension fully, the headers in the response should allow being set through an expression.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9865","06/09/2016 15:42:51",8,"New parsers still require the spring bundle ""The new parsers still depend on the spring bundle to locate the XSD. This forces new components to have a dummy NamespaceHandler which basically does nothing, just to load the XSD.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9866","06/09/2016 16:01:56",8,"Provide better logging for classloading process ""Classloading model for mule 4 will be more complex than the one used on mule 3.x. In order to make easier to resolve classloading issues, it will be needed to understand what is going on. Better logging must be provided, indicating which classes are loaded from which classloader, which classes are being filtered/accepted, etc. ""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9867","06/09/2016 16:12:01",13,"Add a way to share libraries/module between application plugins ""Different applications plugins can export classes from the same library (ex: connectors sharing a common SDK) or application plugins can extend the functionality provided by another connector (ex: FTP/FTPs). If those plugins need to export the same classes, these classes must be shared in a library/module that is accesible to both plugins. Otherwise the application using those plugins will be exposed to two versions of the same class.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9868","06/09/2016 16:24:23",13,"Create maven plugin to ensure that modules export a complete API ""Modules are defined exporting packages/resources. In order to avoid classlaoding errors on runtime, each module must export every class that is part of the API exposed to other artifacts. For example, if org.foo.A has a method doStuff(org.bar.B) then both org.foo and org.bar must be exported. If there are other dependencies, they must be also exported.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9869","06/09/2016 16:29:06",5,"Ensure that modules are exporting the right packages ""Ensure that each module exports everything that is transitively exposed from the module packages.""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9870","06/09/2016 16:37:50",8,"Change registry bootstrapping to avoid leaking classes on plugins ""Bootstrap process works searching for bootstrap properties files and then instantiating each required object using reflection. To be able to create those objects, the plugin must expose the classes of the objects to bootstrap, which is not good. Bootstrapping process should invert the dependency so each plugin can instantiate objects without requiring to expose them.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9871","06/09/2016 16:41:17",8,"Review if packages imported from other modules must be explicitly declared ""Modules are declaring which classes are exported, both because the module own the class or because the class is a transitive dependency of a owned class. Review if when a module requires to export a class from other module, that class must be declared as """"imported"""", so we can validate whether or not there is more than one module exporting the same package.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9875","06/09/2016 19:10:28",5,"Sometimes file:write acquires lock even when the lock is already taken ""When writing a file with a lock it fails only sometimes. To reproduce deploy the attached flow and run This is the file structure: temp temp/.DS_Store temp/file temp/file.1 temp/file.10 temp/file.100 temp/file.1000 temp/file.101 temp/file.102 temp/file.103 temp/file.104 temp/file.105 temp/file.106 temp/file.107 temp/file.108 temp/file.109 temp/file.11 temp/file.110 temp/file.111 temp/file.112 temp/file.113 temp/file.114 temp/file.115 temp/file.116 temp/file.117 temp/file.118 temp/file.119 temp/file.12 temp/file.120 temp/file.121 temp/file.122 temp/file.123 temp/file.124 temp/file.125 temp/file.126 temp/file.127 temp/file.128 temp/file.129 temp/file.13 temp/file.130 temp/file.131 temp/file.132 temp/file.133 temp/file.134 temp/file.135 temp/file.136 temp/file.137 temp/file.138 temp/file.139 temp/file.14 temp/file.140 temp/file.141 temp/file.142 temp/file.143 temp/file.144 temp/file.145 temp/file.146 temp/file.147 temp/file.148 temp/file.149 temp/file.15 temp/file.150 temp/file.151 temp/file.152 temp/file.153 temp/file.154 temp/file.155 temp/file.156 temp/file.157 temp/file.158 temp/file.159 temp/file.16 temp/file.160 temp/file.161 temp/file.162 temp/file.163 temp/file.164 temp/file.165 temp/file.166 temp/file.167 temp/file.168 temp/file.169 temp/file.17 temp/file.170 temp/file.171 temp/file.172 temp/file.173 temp/file.174 temp/file.175 temp/file.176 temp/file.177 temp/file.178 temp/file.179 temp/file.18 temp/file.180 temp/file.181 temp/file.182 temp/file.183 temp/file.184 temp/file.185 temp/file.186 temp/file.187 temp/file.188 temp/file.189 temp/file.19 temp/file.190 temp/file.191 temp/file.192 temp/file.193 temp/file.194 temp/file.195 temp/file.196 temp/file.197 temp/file.198 temp/file.199 temp/file.2 temp/file.20 temp/file.200 temp/file.201 temp/file.202 temp/file.203 temp/file.204 temp/file.205 temp/file.206 temp/file.207 temp/file.208 temp/file.209 temp/file.21 temp/file.210 temp/file.211 temp/file.212 temp/file.213 temp/file.214 temp/file.215 temp/file.216 temp/file.217 temp/file.218 temp/file.219 temp/file.22 temp/file.220 temp/file.221 temp/file.222 temp/file.223 temp/file.224 temp/file.225 temp/file.226 temp/file.227 temp/file.228 temp/file.229 temp/file.23 temp/file.230 temp/file.231 temp/file.232 temp/file.233 temp/file.234 temp/file.235 temp/file.236 temp/file.237 temp/file.238 temp/file.239 temp/file.24 temp/file.240 temp/file.241 temp/file.242 temp/file.243 temp/file.244 temp/file.245 temp/file.246 temp/file.247 temp/file.248 temp/file.249 temp/file.25 temp/file.250 temp/file.251 temp/file.252 temp/file.253 temp/file.254 temp/file.255 temp/file.256 temp/file.257 temp/file.258 temp/file.259 temp/file.26 temp/file.260 temp/file.261 temp/file.262 temp/file.263 temp/file.264 temp/file.265 temp/file.266 temp/file.267 temp/file.268 temp/file.269 temp/file.27 temp/file.270 temp/file.271 temp/file.272 temp/file.273 temp/file.274 temp/file.275 temp/file.276 temp/file.277 temp/file.278 temp/file.279 temp/file.28 temp/file.280 temp/file.281 temp/file.282 temp/file.283 temp/file.284 temp/file.285 temp/file.286 temp/file.287 temp/file.288 temp/file.289 temp/file.29 temp/file.290 temp/file.291 temp/file.292 temp/file.293 temp/file.294 temp/file.295 temp/file.296 temp/file.297 temp/file.298 temp/file.299 temp/file.3 temp/file.30 temp/file.300 temp/file.301 temp/file.302 temp/file.303 temp/file.304 temp/file.305 temp/file.306 temp/file.307 temp/file.308 temp/file.309 temp/file.31 temp/file.310 temp/file.311 temp/file.312 temp/file.313 temp/file.314 temp/file.315 temp/file.316 temp/file.317 temp/file.318 temp/file.319 temp/file.32 temp/file.320 temp/file.321 temp/file.322 temp/file.323 temp/file.324 temp/file.325 temp/file.326 temp/file.327 temp/file.328 temp/file.329 temp/file.33 temp/file.330 temp/file.331 temp/file.332 temp/file.333 temp/file.334 temp/file.335 temp/file.336 temp/file.337 temp/file.338 temp/file.339 temp/file.34 temp/file.340 temp/file.341 temp/file.342 temp/file.343 temp/file.344 temp/file.345 temp/file.346 temp/file.347 temp/file.348 temp/file.349 temp/file.35 temp/file.350 temp/file.351 temp/file.352 temp/file.353 temp/file.354 temp/file.355 temp/file.356 temp/file.357 temp/file.358 temp/file.359 temp/file.36 temp/file.360 temp/file.361 temp/file.362 temp/file.363 temp/file.364 temp/file.365 temp/file.366 temp/file.367 temp/file.368 temp/file.369 temp/file.37 temp/file.370 temp/file.371 temp/file.372 temp/file.373 temp/file.374 temp/file.375 temp/file.376 temp/file.377 temp/file.378 temp/file.379 temp/file.38 temp/file.380 temp/file.381 temp/file.382 temp/file.383 temp/file.384 temp/file.385 temp/file.386 temp/file.387 temp/file.388 temp/file.389 temp/file.39 temp/file.390 temp/file.391 temp/file.392 temp/file.393 temp/file.394 temp/file.395 temp/file.396 temp/file.397 temp/file.398 temp/file.399 temp/file.4 temp/file.40 temp/file.400 temp/file.401 temp/file.402 temp/file.403 temp/file.404 temp/file.405 temp/file.406 temp/file.407 temp/file.408 temp/file.409 temp/file.41 temp/file.410 temp/file.411 temp/file.412 temp/file.413 temp/file.414 temp/file.415 temp/file.416 temp/file.417 temp/file.418 temp/file.419 temp/file.42 temp/file.420 temp/file.421 temp/file.422 temp/file.423 temp/file.424 temp/file.425 temp/file.426 temp/file.427 temp/file.428 temp/file.429 temp/file.43 temp/file.430 temp/file.431 temp/file.432 temp/file.433 temp/file.434 temp/file.435 temp/file.436 temp/file.437 temp/file.438 temp/file.439 temp/file.44 temp/file.440 temp/file.441 temp/file.442 temp/file.443 temp/file.444 temp/file.445 temp/file.446 temp/file.447 temp/file.448 temp/file.449 temp/file.45 temp/file.450 temp/file.451 temp/file.452 temp/file.453 temp/file.454 temp/file.455 temp/file.456 temp/file.457 temp/file.458 temp/file.459 temp/file.46 temp/file.460 temp/file.461 temp/file.462 temp/file.463 temp/file.464 temp/file.465 temp/file.466 temp/file.467 temp/file.468 temp/file.469 temp/file.47 temp/file.470 temp/file.471 temp/file.472 temp/file.473 temp/file.474 temp/file.475 temp/file.476 temp/file.477 temp/file.478 temp/file.479 temp/file.48 temp/file.480 temp/file.481 temp/file.482 temp/file.483 temp/file.484 temp/file.485 temp/file.486 temp/file.487 temp/file.488 temp/file.489 temp/file.49 temp/file.490 temp/file.491 temp/file.492 temp/file.493 temp/file.494 temp/file.495 temp/file.496 temp/file.497 temp/file.498 temp/file.499 temp/file.5 temp/file.50 temp/file.500 temp/file.501 temp/file.502 temp/file.503 temp/file.504 temp/file.505 temp/file.506 temp/file.507 temp/file.508 temp/file.509 temp/file.51 temp/file.510 temp/file.511 temp/file.512 temp/file.513 temp/file.514 temp/file.515 temp/file.516 temp/file.517 temp/file.518 temp/file.519 temp/file.52 temp/file.520 temp/file.521 temp/file.522 temp/file.523 temp/file.524 temp/file.525 temp/file.526 temp/file.527 temp/file.528 temp/file.529 temp/file.53 temp/file.530 temp/file.531 temp/file.532 temp/file.533 temp/file.534 temp/file.535 temp/file.536 temp/file.537 temp/file.538 temp/file.539 temp/file.54 temp/file.540 temp/file.541 temp/file.542 temp/file.543 temp/file.544 temp/file.545 temp/file.546 temp/file.547 temp/file.548 temp/file.549 temp/file.55 temp/file.550 temp/file.551 temp/file.552 temp/file.553 temp/file.554 temp/file.555 temp/file.556 temp/file.557 temp/file.558 temp/file.559 temp/file.56 temp/file.560 temp/file.561 temp/file.562 temp/file.563 temp/file.564 temp/file.565 temp/file.566 temp/file.567 temp/file.568 temp/file.569 temp/file.57 temp/file.570 temp/file.571 temp/file.572 temp/file.573 temp/file.574 temp/file.575 temp/file.576 temp/file.577 temp/file.578 temp/file.579 temp/file.58 temp/file.580 temp/file.581 temp/file.582 temp/file.583 temp/file.584 temp/file.585 temp/file.586 temp/file.587 temp/file.588 temp/file.589 temp/file.59 temp/file.590 temp/file.591 temp/file.592 temp/file.593 temp/file.594 temp/file.595 temp/file.596 temp/file.597 temp/file.598 temp/file.599 temp/file.6 temp/file.60 temp/file.600 temp/file.601 temp/file.602 temp/file.603 temp/file.604 temp/file.605 temp/file.606 temp/file.607 temp/file.608 temp/file.609 temp/file.61 temp/file.610 temp/file.611 temp/file.612 temp/file.613 temp/file.614 temp/file.615 temp/file.616 temp/file.617 temp/file.618 temp/file.619 temp/file.62 temp/file.620 temp/file.621 temp/file.622 temp/file.623 temp/file.624 temp/file.625 temp/file.626 temp/file.627 temp/file.628 temp/file.629 temp/file.63 temp/file.630 temp/file.631 temp/file.632 temp/file.633 temp/file.634 temp/file.635 temp/file.636 temp/file.637 temp/file.638 temp/file.639 temp/file.64 temp/file.640 temp/file.641 temp/file.642 temp/file.643 temp/file.644 temp/file.645 temp/file.646 temp/file.647 temp/file.648 temp/file.649 temp/file.65 temp/file.650 temp/file.651 temp/file.652 temp/file.653 temp/file.654 temp/file.655 temp/file.656 temp/file.657 temp/file.658 temp/file.659 temp/file.66 temp/file.660 temp/file.661 temp/file.662 temp/file.663 temp/file.664 temp/file.665 temp/file.666 temp/file.667 temp/file.668 temp/file.669 temp/file.67 temp/file.670 temp/file.671 temp/file.672 temp/file.673 temp/file.674 temp/file.675 temp/file.676 temp/file.677 temp/file.678 temp/file.679 temp/file.68 temp/file.680 temp/file.681 temp/file.682 temp/file.683 temp/file.684 temp/file.685 temp/file.686 temp/file.687 temp/file.688 temp/file.689 temp/file.69 temp/file.690 temp/file.691 temp/file.692 temp/file.693 temp/file.694 temp/file.695 temp/file.696 temp/file.697 temp/file.698 temp/file.699 temp/file.7 temp/file.70 temp/file.700 temp/file.701 temp/file.702 temp/file.703 temp/file.704 temp/file.705 temp/file.706 temp/file.707 temp/file.708 temp/file.709 temp/file.71 temp/file.710 temp/file.711 temp/file.712 temp/file.713 temp/file.714 temp/file.715 temp/file.716 temp/file.717 temp/file.718 temp/file.719 temp/file.72 temp/file.720 temp/file.721 temp/file.722 temp/file.723 temp/file.724 temp/file.725 temp/file.726 temp/file.727 temp/file.728 temp/file.729 temp/file.73 temp/file.730 temp/file.731 temp/file.732 temp/file.733 temp/file.734 temp/file.735 temp/file.736 temp/file.737 temp/file.738 temp/file.739 temp/file.74 temp/file.740 temp/file.741 temp/file.742 temp/file.743 temp/file.744 temp/file.745 temp/file.746 temp/file.747 temp/file.748 temp/file.749 temp/file.75 temp/file.750 temp/file.751 temp/file.752 temp/file.753 temp/file.754 temp/file.755 temp/file.756 temp/file.757 temp/file.758 temp/file.759 temp/file.76 temp/file.760 temp/file.761 temp/file.762 temp/file.763 temp/file.764 temp/file.765 temp/file.766 temp/file.767 temp/file.768 temp/file.769 temp/file.77 temp/file.770 temp/file.771 temp/file.772 temp/file.773 temp/file.774 temp/file.775 temp/file.776 temp/file.777 temp/file.778 temp/file.779 temp/file.78 temp/file.780 temp/file.781 temp/file.782 temp/file.783 temp/file.784 temp/file.785 temp/file.786 temp/file.787 temp/file.788 temp/file.789 temp/file.79 temp/file.790 temp/file.791 temp/file.792 temp/file.793 temp/file.794 temp/file.795 temp/file.796 temp/file.797 temp/file.798 temp/file.799 temp/file.8 temp/file.80 temp/file.800 temp/file.801 temp/file.802 temp/file.803 temp/file.804 temp/file.805 temp/file.806 temp/file.807 temp/file.808 temp/file.809 temp/file.81 temp/file.810 temp/file.811 temp/file.812 temp/file.813 temp/file.814 temp/file.815 temp/file.816 temp/file.817 temp/file.818 temp/file.819 temp/file.82 temp/file.820 temp/file.821 temp/file.822 temp/file.823 temp/file.824 temp/file.825 temp/file.826 temp/file.827 temp/file.828 temp/file.829 temp/file.83 temp/file.830 temp/file.831 temp/file.832 temp/file.833 temp/file.834 temp/file.835 temp/file.836 temp/file.837 temp/file.838 temp/file.839 temp/file.84 temp/file.840 temp/file.841 temp/file.842 temp/file.843 temp/file.844 temp/file.845 temp/file.846 temp/file.847 temp/file.848 temp/file.849 temp/file.85 temp/file.850 temp/file.851 temp/file.852 temp/file.853 temp/file.854 temp/file.855 temp/file.856 temp/file.857 temp/file.858 temp/file.859 temp/file.86 temp/file.860 temp/file.861 temp/file.862 temp/file.863 temp/file.864 temp/file.865 temp/file.866 temp/file.867 temp/file.868 temp/file.869 temp/file.87 temp/file.870 temp/file.871 temp/file.872 temp/file.873 temp/file.874 temp/file.875 temp/file.876 temp/file.877 temp/file.878 temp/file.879 temp/file.88 temp/file.880 temp/file.881 temp/file.882 temp/file.883 temp/file.884 temp/file.885 temp/file.886 temp/file.887 temp/file.888 temp/file.889 temp/file.89 temp/file.890 temp/file.891 temp/file.892 temp/file.893 temp/file.894 temp/file.895 temp/file.896 temp/file.897 temp/file.898 temp/file.899 temp/file.9 temp/file.90 temp/file.900 temp/file.901 temp/file.902 temp/file.903 temp/file.904 temp/file.905 temp/file.906 temp/file.907 temp/file.908 temp/file.909 temp/file.91 temp/file.910 temp/file.911 temp/file.912 temp/file.913 temp/file.914 temp/file.915 temp/file.916 temp/file.917 temp/file.918 temp/file.919 temp/file.92 temp/file.920 temp/file.921 temp/file.922 temp/file.923 temp/file.924 temp/file.925 temp/file.926 temp/file.927 temp/file.928 temp/file.929 temp/file.93 temp/file.930 temp/file.931 temp/file.932 temp/file.933 temp/file.934 temp/file.935 temp/file.936 temp/file.937 temp/file.938 temp/file.939 temp/file.94 temp/file.940 temp/file.941 temp/file.942 temp/file.943 temp/file.944 temp/file.945 temp/file.946 temp/file.947 temp/file.948 temp/file.949 temp/file.95 temp/file.950 temp/file.951 temp/file.952 temp/file.953 temp/file.954 temp/file.955 temp/file.956 temp/file.957 temp/file.958 temp/file.959 temp/file.96 temp/file.960 temp/file.961 temp/file.962 temp/file.963 temp/file.964 temp/file.965 temp/file.966 temp/file.967 temp/file.968 temp/file.969 temp/file.97 temp/file.970 temp/file.971 temp/file.972 temp/file.973 temp/file.974 temp/file.975 temp/file.976 temp/file.977 temp/file.978 temp/file.979 temp/file.98 temp/file.980 temp/file.981 temp/file.982 temp/file.983 temp/file.984 temp/file.985 temp/file.986 temp/file.987 temp/file.988 temp/file.989 temp/file.99 temp/file.990 temp/file.991 temp/file.992 temp/file.993 temp/file.994 temp/file.995 temp/file.996 temp/file.997 temp/file.998 temp/file.999 temp/out temp/out/out temp/out/output.1 temp/out/output.10 temp/out/output.100 temp/out/output.1000 temp/out/output.101 temp/out/output.102 temp/out/output.103 temp/out/output.104 temp/out/output.105 temp/out/output.106 temp/out/output.107 temp/out/output.108 temp/out/output.109 temp/out/output.11 temp/out/output.110 temp/out/output.111 temp/out/output.112 temp/out/output.113 temp/out/output.114 temp/out/output.115 temp/out/output.116 temp/out/output.117 temp/out/output.118 temp/out/output.119 temp/out/output.12 temp/out/output.120 temp/out/output.121 temp/out/output.122 temp/out/output.123 temp/out/output.124 temp/out/output.125 temp/out/output.126 temp/out/output.127 temp/out/output.128 temp/out/output.129 temp/out/output.13 temp/out/output.130 temp/out/output.131 temp/out/output.132 temp/out/output.133 temp/out/output.134 temp/out/output.135 temp/out/output.136 temp/out/output.137 temp/out/output.138 temp/out/output.139 temp/out/output.14 temp/out/output.140 temp/out/output.141 temp/out/output.142 temp/out/output.143 temp/out/output.144 temp/out/output.145 temp/out/output.146 temp/out/output.147 temp/out/output.148 temp/out/output.149 temp/out/output.15 temp/out/output.150 temp/out/output.151 temp/out/output.152 temp/out/output.153 temp/out/output.154 temp/out/output.155 temp/out/output.156 temp/out/output.157 temp/out/output.158 temp/out/output.159 temp/out/output.16 temp/out/output.160 temp/out/output.161 temp/out/output.162 temp/out/output.163 temp/out/output.164 temp/out/output.165 temp/out/output.166 temp/out/output.167 temp/out/output.168 temp/out/output.169 temp/out/output.17 temp/out/output.170 temp/out/output.171 temp/out/output.172 temp/out/output.173 temp/out/output.174 temp/out/output.175 temp/out/output.176 temp/out/output.177 temp/out/output.178 temp/out/output.179 temp/out/output.18 temp/out/output.180 temp/out/output.181 temp/out/output.182 temp/out/output.183 temp/out/output.184 temp/out/output.185 temp/out/output.186 temp/out/output.187 temp/out/output.188 temp/out/output.189 temp/out/output.19 temp/out/output.190 temp/out/output.191 temp/out/output.192 temp/out/output.193 temp/out/output.194 temp/out/output.195 temp/out/output.196 temp/out/output.197 temp/out/output.198 temp/out/output.199 temp/out/output.2 temp/out/output.20 temp/out/output.200 temp/out/output.201 temp/out/output.202 temp/out/output.203 temp/out/output.204 temp/out/output.205 temp/out/output.206 temp/out/output.207 temp/out/output.208 temp/out/output.209 temp/out/output.21 temp/out/output.210 temp/out/output.211 temp/out/output.212 temp/out/output.213 temp/out/output.214 temp/out/output.215 temp/out/output.216 temp/out/output.217 temp/out/output.218 temp/out/output.219 temp/out/output.22 temp/out/output.220 temp/out/output.221 temp/out/output.222 temp/out/output.223 temp/out/output.224 temp/out/output.225 temp/out/output.226 temp/out/output.227 temp/out/output.228 temp/out/output.229 temp/out/output.23 temp/out/output.230 temp/out/output.231 temp/out/output.232 temp/out/output.233 temp/out/output.234 temp/out/output.235 temp/out/output.236 temp/out/output.237 temp/out/output.238 temp/out/output.239 temp/out/output.24 temp/out/output.240 temp/out/output.241 temp/out/output.242 temp/out/output.243 temp/out/output.244 temp/out/output.245 temp/out/output.246 temp/out/output.247 temp/out/output.248 temp/out/output.249 temp/out/output.25 temp/out/output.250 temp/out/output.251 temp/out/output.252 temp/out/output.253 temp/out/output.254 temp/out/output.255 temp/out/output.256 temp/out/output.257 temp/out/output.258 temp/out/output.259 temp/out/output.26 temp/out/output.260 temp/out/output.261 temp/out/output.262 temp/out/output.263 temp/out/output.264 temp/out/output.265 temp/out/output.266 temp/out/output.267 temp/out/output.268 temp/out/output.269 temp/out/output.27 temp/out/output.270 temp/out/output.271 temp/out/output.272 temp/out/output.273 temp/out/output.274 temp/out/output.275 temp/out/output.276 temp/out/output.277 temp/out/output.278 temp/out/output.279 temp/out/output.28 temp/out/output.280 temp/out/output.281 temp/out/output.282 temp/out/output.283 temp/out/output.284 temp/out/output.285 temp/out/output.286 temp/out/output.287 temp/out/output.288 temp/out/output.289 temp/out/output.29 temp/out/output.290 temp/out/output.291 temp/out/output.292 temp/out/output.293 temp/out/output.294 temp/out/output.295 temp/out/output.296 temp/out/output.297 temp/out/output.298 temp/out/output.299 temp/out/output.3 temp/out/output.30 temp/out/output.300 temp/out/output.301 temp/out/output.302 temp/out/output.303 temp/out/output.304 temp/out/output.305 temp/out/output.306 temp/out/output.307 temp/out/output.308 temp/out/output.309 temp/out/output.31 temp/out/output.310 temp/out/output.311 temp/out/output.312 temp/out/output.313 temp/out/output.314 temp/out/output.315 temp/out/output.316 temp/out/output.317 temp/out/output.318 temp/out/output.319 temp/out/output.32 temp/out/output.320 temp/out/output.321 temp/out/output.322 temp/out/output.323 temp/out/output.324 temp/out/output.325 temp/out/output.326 temp/out/output.327 temp/out/output.328 temp/out/output.329 temp/out/output.33 temp/out/output.330 temp/out/output.331 temp/out/output.332 temp/out/output.333 temp/out/output.334 temp/out/output.335 temp/out/output.336 temp/out/output.337 temp/out/output.338 temp/out/output.339 temp/out/output.34 temp/out/output.340 temp/out/output.341 temp/out/output.342 temp/out/output.343 temp/out/output.344 temp/out/output.345 temp/out/output.346 temp/out/output.347 temp/out/output.348 temp/out/output.349 temp/out/output.35 temp/out/output.350 temp/out/output.351 temp/out/output.352 temp/out/output.353 temp/out/output.354 temp/out/output.355 temp/out/output.356 temp/out/output.357 temp/out/output.358 temp/out/output.359 temp/out/output.36 temp/out/output.360 temp/out/output.361 temp/out/output.362 temp/out/output.363 temp/out/output.364 temp/out/output.365 temp/out/output.366 temp/out/output.367 temp/out/output.368 temp/out/output.369 temp/out/output.37 temp/out/output.370 temp/out/output.371 temp/out/output.372 temp/out/output.373 temp/out/output.374 temp/out/output.375 temp/out/output.376 temp/out/output.377 temp/out/output.378 temp/out/output.379 temp/out/output.38 temp/out/output.380 temp/out/output.381 temp/out/output.382 temp/out/output.383 temp/out/output.384 temp/out/output.385 temp/out/output.386 temp/out/output.387 temp/out/output.388 temp/out/output.389 temp/out/output.39 temp/out/output.390 temp/out/output.391 temp/out/output.392 temp/out/output.393 temp/out/output.394 temp/out/output.395 temp/out/output.396 temp/out/output.397 temp/out/output.398 temp/out/output.399 temp/out/output.4 temp/out/output.40 temp/out/output.400 temp/out/output.401 temp/out/output.402 temp/out/output.403 temp/out/output.404 temp/out/output.405 temp/out/output.406 temp/out/output.407 temp/out/output.408 temp/out/output.409 temp/out/output.41 temp/out/output.410 temp/out/output.411 temp/out/output.412 temp/out/output.413 temp/out/output.414 temp/out/output.415 temp/out/output.416 temp/out/output.417 temp/out/output.418 temp/out/output.419 temp/out/output.42 temp/out/output.420 temp/out/output.421 temp/out/output.422 temp/out/output.423 temp/out/output.424 temp/out/output.425 temp/out/output.426 temp/out/output.427 temp/out/output.428 temp/out/output.429 temp/out/output.43 temp/out/output.430 temp/out/output.431 temp/out/output.432 temp/out/output.433 temp/out/output.434 temp/out/output.435 temp/out/output.436 temp/out/output.437 temp/out/output.438 temp/out/output.439 temp/out/output.44 temp/out/output.440 temp/out/output.441 temp/out/output.442 temp/out/output.443 temp/out/output.444 temp/out/output.445 temp/out/output.446 temp/out/output.447 temp/out/output.448 temp/out/output.449 temp/out/output.45 temp/out/output.450 temp/out/output.451 temp/out/output.452 temp/out/output.453 temp/out/output.454 temp/out/output.455 temp/out/output.456 temp/out/output.457 temp/out/output.458 temp/out/output.459 temp/out/output.46 temp/out/output.460 temp/out/output.461 temp/out/output.462 temp/out/output.463 temp/out/output.464 temp/out/output.465 temp/out/output.466 temp/out/output.467 temp/out/output.468 temp/out/output.469 temp/out/output.47 temp/out/output.470 temp/out/output.471 temp/out/output.472 temp/out/output.473 temp/out/output.474 temp/out/output.475 temp/out/output.476 temp/out/output.477 temp/out/output.478 temp/out/output.479 temp/out/output.48 temp/out/output.480 temp/out/output.481 temp/out/output.482 temp/out/output.483 temp/out/output.484 temp/out/output.485 temp/out/output.486 temp/out/output.487 temp/out/output.488 temp/out/output.489 temp/out/output.49 temp/out/output.490 temp/out/output.491 temp/out/output.492 temp/out/output.493 temp/out/output.494 temp/out/output.495 temp/out/output.496 temp/out/output.497 temp/out/output.498 temp/out/output.499 temp/out/output.5 temp/out/output.50 temp/out/output.500 temp/out/output.501 temp/out/output.502 temp/out/output.503 temp/out/output.504 temp/out/output.505 temp/out/output.506 temp/out/output.507 temp/out/output.508 temp/out/output.509 temp/out/output.51 temp/out/output.510 temp/out/output.511 temp/out/output.512 temp/out/output.513 temp/out/output.514 temp/out/output.515 temp/out/output.516 temp/out/output.517 temp/out/output.518 temp/out/output.519 temp/out/output.52 temp/out/output.520 temp/out/output.521 temp/out/output.522 temp/out/output.523 temp/out/output.524 temp/out/output.525 temp/out/output.526 temp/out/output.527 temp/out/output.528 temp/out/output.529 temp/out/output.53 temp/out/output.530 temp/out/output.531 temp/out/output.532 temp/out/output.533 temp/out/output.534 temp/out/output.535 temp/out/output.536 temp/out/output.537 temp/out/output.538 temp/out/output.539 temp/out/output.54 temp/out/output.540 temp/out/output.541 temp/out/output.542 temp/out/output.543 temp/out/output.544 temp/out/output.545 temp/out/output.546 temp/out/output.547 temp/out/output.548 temp/out/output.549 temp/out/output.55 temp/out/output.550 temp/out/output.551 temp/out/output.552 temp/out/output.553 temp/out/output.554 temp/out/output.555 temp/out/output.556 temp/out/output.557 temp/out/output.558 temp/out/output.559 temp/out/output.56 temp/out/output.560 temp/out/output.561 temp/out/output.562 temp/out/output.563 temp/out/output.564 temp/out/output.565 temp/out/output.566 temp/out/output.567 temp/out/output.568 temp/out/output.569 temp/out/output.57 temp/out/output.570 temp/out/output.571 temp/out/output.572 temp/out/output.573 temp/out/output.574 temp/out/output.575 temp/out/output.576 temp/out/output.577 temp/out/output.578 temp/out/output.579 temp/out/output.58 temp/out/output.580 temp/out/output.581 temp/out/output.582 temp/out/output.583 temp/out/output.584 temp/out/output.585 temp/out/output.586 temp/out/output.587 temp/out/output.588 temp/out/output.589 temp/out/output.59 temp/out/output.590 temp/out/output.591 temp/out/output.592 temp/out/output.593 temp/out/output.594 temp/out/output.595 temp/out/output.596 temp/out/output.597 temp/out/output.598 temp/out/output.599 temp/out/output.6 temp/out/output.60 temp/out/output.600 temp/out/output.601 temp/out/output.602 temp/out/output.603 temp/out/output.604 temp/out/output.605 temp/out/output.606 temp/out/output.607 temp/out/output.608 temp/out/output.609 temp/out/output.61 temp/out/output.610 temp/out/output.611 temp/out/output.612 temp/out/output.613 temp/out/output.614 temp/out/output.615 temp/out/output.616 temp/out/output.617 temp/out/output.618 temp/out/output.619 temp/out/output.62 temp/out/output.620 temp/out/output.621 temp/out/output.622 temp/out/output.623 temp/out/output.624 temp/out/output.625 temp/out/output.626 temp/out/output.627 temp/out/output.628 temp/out/output.629 temp/out/output.63 temp/out/output.630 temp/out/output.631 temp/out/output.632 temp/out/output.633 temp/out/output.634 temp/out/output.635 temp/out/output.636 temp/out/output.637 temp/out/output.638 temp/out/output.639 temp/out/output.64 temp/out/output.640 temp/out/output.641 temp/out/output.642 temp/out/output.643 temp/out/output.644 temp/out/output.645 temp/out/output.646 temp/out/output.647 temp/out/output.648 temp/out/output.649 temp/out/output.65 temp/out/output.650 temp/out/output.651 temp/out/output.652 temp/out/output.653 temp/out/output.654 temp/out/output.655 temp/out/output.656 temp/out/output.657 temp/out/output.658 temp/out/output.659 temp/out/output.66 temp/out/output.660 temp/out/output.661 temp/out/output.662 temp/out/output.663 temp/out/output.664 temp/out/output.665 temp/out/output.666 temp/out/output.667 temp/out/output.668 temp/out/output.669 temp/out/output.67 temp/out/output.670 temp/out/output.671 temp/out/output.672 temp/out/output.673 temp/out/output.674 temp/out/output.675 temp/out/output.676 temp/out/output.677 temp/out/output.678 temp/out/output.679 temp/out/output.68 temp/out/output.680 temp/out/output.681 temp/out/output.682 temp/out/output.683 temp/out/output.684 temp/out/output.685 temp/out/output.686 temp/out/output.687 temp/out/output.688 temp/out/output.689 temp/out/output.69 temp/out/output.690 temp/out/output.691 temp/out/output.692 temp/out/output.693 temp/out/output.694 temp/out/output.695 temp/out/output.696 temp/out/output.697 temp/out/output.698 temp/out/output.699 temp/out/output.7 temp/out/output.70 temp/out/output.700 temp/out/output.701 temp/out/output.702 temp/out/output.703 temp/out/output.704 temp/out/output.705 temp/out/output.706 temp/out/output.707 temp/out/output.708 temp/out/output.709 temp/out/output.71 temp/out/output.710 temp/out/output.711 temp/out/output.712 temp/out/output.713 temp/out/output.714 temp/out/output.715 temp/out/output.716 temp/out/output.717 temp/out/output.718 temp/out/output.719 temp/out/output.72 temp/out/output.720 temp/out/output.721 temp/out/output.722 temp/out/output.723 temp/out/output.724 temp/out/output.725 temp/out/output.726 temp/out/output.727 temp/out/output.728 temp/out/output.729 temp/out/output.73 temp/out/output.730 temp/out/output.731 temp/out/output.732 temp/out/output.733 temp/out/output.734 temp/out/output.735 temp/out/output.736 temp/out/output.737 temp/out/output.738 temp/out/output.739 temp/out/output.74 temp/out/output.740 temp/out/output.741 temp/out/output.742 temp/out/output.743 temp/out/output.744 temp/out/output.745 temp/out/output.746 temp/out/output.747 temp/out/output.748 temp/out/output.749 temp/out/output.75 temp/out/output.750 temp/out/output.751 temp/out/output.752 temp/out/output.753 temp/out/output.754 temp/out/output.755 temp/out/output.756 temp/out/output.757 temp/out/output.758 temp/out/output.759 temp/out/output.76 temp/out/output.760 temp/out/output.761 temp/out/output.762 temp/out/output.763 temp/out/output.764 temp/out/output.765 temp/out/output.766 temp/out/output.767 temp/out/output.768 temp/out/output.769 temp/out/output.77 temp/out/output.770 temp/out/output.771 temp/out/output.772 temp/out/output.773 temp/out/output.774 temp/out/output.775 temp/out/output.776 temp/out/output.777 temp/out/output.778 temp/out/output.779 temp/out/output.78 temp/out/output.780 temp/out/output.781 temp/out/output.782 temp/out/output.783 temp/out/output.784 temp/out/output.785 temp/out/output.786 temp/out/output.787 temp/out/output.788 temp/out/output.789 temp/out/output.79 temp/out/output.790 temp/out/output.791 temp/out/output.792 temp/out/output.793 temp/out/output.794 temp/out/output.795 temp/out/output.796 temp/out/output.797 temp/out/output.798 temp/out/output.799 temp/out/output.8 temp/out/output.80 temp/out/output.800 temp/out/output.801 temp/out/output.802 temp/out/output.803 temp/out/output.804 temp/out/output.805 temp/out/output.806 temp/out/output.807 temp/out/output.808 temp/out/output.809 temp/out/output.81 temp/out/output.810 temp/out/output.811 temp/out/output.812 temp/out/output.813 temp/out/output.814 temp/out/output.815 temp/out/output.816 temp/out/output.817 temp/out/output.818 temp/out/output.819 temp/out/output.82 temp/out/output.820 temp/out/output.821 temp/out/output.822 temp/out/output.823 temp/out/output.824 temp/out/output.825 temp/out/output.826 temp/out/output.827 temp/out/output.828 temp/out/output.829 temp/out/output.83 temp/out/output.830 temp/out/output.831 temp/out/output.832 temp/out/output.833 temp/out/output.834 temp/out/output.835 temp/out/output.836 temp/out/output.837 temp/out/output.838 temp/out/output.839 temp/out/output.84 temp/out/output.840 temp/out/output.841 temp/out/output.842 temp/out/output.843 temp/out/output.844 temp/out/output.845 temp/out/output.846 temp/out/output.847 temp/out/output.848 temp/out/output.849 temp/out/output.85 temp/out/output.850 temp/out/output.851 temp/out/output.852 temp/out/output.853 temp/out/output.854 temp/out/output.855 temp/out/output.856 temp/out/output.857 temp/out/output.858 temp/out/output.859 temp/out/output.86 temp/out/output.860 temp/out/output.861 temp/out/output.862 temp/out/output.863 temp/out/output.864 temp/out/output.865 temp/out/output.866 temp/out/output.867 temp/out/output.868 temp/out/output.869 temp/out/output.87 temp/out/output.870 temp/out/output.871 temp/out/output.872 temp/out/output.873 temp/out/output.874 temp/out/output.875 temp/out/output.876 temp/out/output.877 temp/out/output.878 temp/out/output.879 temp/out/output.88 temp/out/output.880 temp/out/output.881 temp/out/output.882 temp/out/output.883 temp/out/output.884 temp/out/output.885 temp/out/output.886 temp/out/output.887 temp/out/output.888 temp/out/output.889 temp/out/output.89 temp/out/output.890 temp/out/output.891 temp/out/output.892 temp/out/output.893 temp/out/output.894 temp/out/output.895 temp/out/output.896 temp/out/output.897 temp/out/output.898 temp/out/output.899 temp/out/output.9 temp/out/output.90 temp/out/output.900 temp/out/output.901 temp/out/output.902 temp/out/output.903 temp/out/output.904 temp/out/output.905 temp/out/output.906 temp/out/output.907 temp/out/output.908 temp/out/output.909 temp/out/output.91 temp/out/output.910 temp/out/output.911 temp/out/output.912 temp/out/output.913 temp/out/output.914 temp/out/output.915 temp/out/output.916 temp/out/output.917 temp/out/output.918 temp/out/output.919 temp/out/output.92 temp/out/output.920 temp/out/output.921 temp/out/output.922 temp/out/output.923 temp/out/output.924 temp/out/output.925 temp/out/output.926 temp/out/output.927 temp/out/output.928 temp/out/output.929 temp/out/output.93 temp/out/output.930 temp/out/output.931 temp/out/output.932 temp/out/output.933 temp/out/output.934 temp/out/output.935 temp/out/output.936 temp/out/output.937 temp/out/output.938 temp/out/output.939 temp/out/output.94 temp/out/output.940 temp/out/output.941 temp/out/output.942 temp/out/output.943 temp/out/output.944 temp/out/output.945 temp/out/output.946 temp/out/output.947 temp/out/output.948 temp/out/output.949 temp/out/output.95 temp/out/output.950 temp/out/output.951 temp/out/output.952 temp/out/output.953 temp/out/output.954 temp/out/output.955 temp/out/output.956 temp/out/output.957 temp/out/output.958 temp/out/output.959 temp/out/output.96 temp/out/output.960 temp/out/output.961 temp/out/output.962 temp/out/output.963 temp/out/output.964 temp/out/output.965 temp/out/output.966 temp/out/output.967 temp/out/output.968 temp/out/output.969 temp/out/output.97 temp/out/output.970 temp/out/output.971 temp/out/output.972 temp/out/output.973 temp/out/output.974 temp/out/output.975 temp/out/output.976 temp/out/output.977 temp/out/output.978 temp/out/output.979 temp/out/output.98 temp/out/output.980 temp/out/output.981 temp/out/output.982 temp/out/output.983 temp/out/output.984 temp/out/output.985 temp/out/output.986 temp/out/output.987 temp/out/output.988 temp/out/output.989 temp/out/output.99 temp/out/output.990 temp/out/output.991 temp/out/output.992 temp/out/output.993 temp/out/output.994 temp/out/output.995 temp/out/output.996 temp/out/output.997 temp/out/output.998 temp/out/output.999 temp/prefix ""","for i in {1..1000} ; do ; curl -ik -X POST -d """"$i"""" -H 'Content-Type: text/plain' http://localhost:8081/concat ; [ ! -e """"/temp/out/output.$i"""" ] && touch """"/temp/out/error$i"""" ; done",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9877","06/09/2016 19:31:36",1,"Remove dependency on mule-commons ""Mule 4 is still depending on mule-commons in order to use: * Bulk operation classes used on batch (org.mule.common.bulk.BulkOperationResult, org.mule.common.bulk.BulkItem) * Connectivity testing (org.mule.common.Testable, org.mule.common.Result.Status, etc) * Metadata (org.mule.common.metadata.ConnectorMetaDataEnabled, org.mule.common.metadata.MetaData, etc) ""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9878","06/09/2016 20:20:14",1,"Restarted configuration has no connectivity ""Testing whether connections are broken when configs are stopped I found restarting them has no effect. Take the following code: When trying to send a request again it is refused. It seems like in LifecycleAwareConfigurationInstance, the stop performs and unbind but since the bind is performed in the initialise method, the connection is not reestablished at start time."""," LifecycleAwareConfigurationProvider httpListenerConfig = muleContext.getRegistry().get(""""testLifecycleListenerConfig""""); httpListenerConfig.stop(); httpListenerConfig.start(); ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9879","06/09/2016 21:22:32",2,"HTTP Listener sets arbitrary encoding ""When I send an HTTP POST to an HTTP listener the message DataType has encoding=UTF-8 although I didn't set in the request. I've tried to change the default encoding of the Mule server for UTF-16 configuring it in the wrapper.conf but it doesn't pay attention to it. You can reproduce deploying the attached config and running {{curl -ik -X POST -d """"a.json"""" -H 'Content-Type: juan/perez' http://localhost:8082/read-message}}. h3. HTTP request """," POST http://localhost:8082/read-message HTTP/1.1 Host: localhost:8082 User-Agent: curl/7.43.0 Accept: */* Proxy-Connection: Keep-Alive Content-Type: juan/perez Content-Length: 6 a.json ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9885","06/10/2016 18:36:24",1,"Interface can be used as the type of a @ParameterGroup yet no error or warning is thrown ""SDK is not checking that the field annotated as a @ParameterGroup is instantiable , which allows things like: That doesn't make any sense because we want to use @ParameterGroup to gather together actual fields. This behaviour shouldn't be allowed (it isn't harmful but it will confuse the user for sure). Fix: Check that the @ParameterGroup type is instantiable and if it is not throw an error. """," @ParameterGroup MyInterface myParameter; ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9887","06/10/2016 18:39:27",1,"Child element generated for map parameter is pluralized ""If the parameter is of type Map the child element associated to it pluralized even when it shouldn't. Example: The resulting schema add a child with name *accounts* instead of *account* Expected: The child element should be the same"""," public class ChildPojosOperations { public void mapWithComplexPojo(Map account) { } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9893","06/10/2016 22:27:20",3,"MetadataKeyId params are always considered as ParameterGroup ""*MetadataKeyId params are always considered as ParameterGroup* * Since the introduction of MultiLevel MetadataKeys, to represent this levels SDK started to represent this Keys as ParameterGroup. * The problem comes with simple MetadataKey that are not ParameterGroups, but they are considered in that way, failing at parameter value resolution time. * *Classes to look*: ** {{AnnotationsBasedDescriber}} ** {{MuleExtensionAnnotationParser}} ** {{MethodArgumentResolverDelegate}} ** {{IntrospectionUtils}}""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9895","06/10/2016 22:59:01",5,"Provide a builder api for creating DataType s ""Replace DataTypeFactory with a builder API and move its code to mule-api.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9897","06/13/2016 15:52:50",3,"Support type converter on simple type collections ""Collection with simple types parsed from child configuration elements must also support a custom converter between the configuration type and the value generated by the user.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9899","06/13/2016 15:56:16",13,"Use new parsing mechanism in extensions framework ""Take the work performed on the spike and complete it so that extensions use the new parsing mechanism""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9900","06/13/2016 16:04:55",5,"Support encoding while sending Strings in the Sockets Extension ""Nowadays, when we serialise the String that will be send/received through the socket we get the byte[] from it with losing the encoding information. Add a parameter to the SocketOperation and save the encoding information."""," string.getBytes()",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9901","06/13/2016 16:11:27",13,"Enrich all the extension with display properties ""Make sure that all currently available extensions receive a lot of love regarding display annotations. Give the tooling as much information as possible. Even try to see how the updated extensions models would look like in the toolings we have. Also evaluate if we need better framework support to communicate this, in which case report and fix those issues. Edit: DisplayName annotation doesn't work on methods or types. We need to add these capability in order to enrich those names. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9903","06/13/2016 16:43:19",5,"Verbose logging for Runtime ""Add the functionality included last Hackathon regarding logging verbosity in the runtime such as: product version, patches installed, classloader, etc... *TBD*: Scope and get rid of the """"etc"""".""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12565","06/13/2016 18:14:53",1,"Upgrade Ant to 1.9.6 ""Analyze if we need to keep Ant in the distro and if not, remove the library. Else, update to 1.9.6""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9905","06/13/2016 19:29:18",1,"Implement FileAttributes#toString() so log messages make sense ""If I log a FileAttributes object I see this: It would be useful to see al the FileAttributes information in a nice format""","org.mule.runtime.core.api.processor.LoggerMessageProcessor: org.mule.extension.file.api.LocalFileAttributes@8671516",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9908","06/13/2016 21:30:47",5,"Cannot have a Function parameter with Map result ""I had a parameter defined as: but the method org.mule.runtime.module.extension.internal.config.XmlExtensionParserDelegate#getResolverFromValue failed because org.mule.metadata.java.utils.JavaTypeUtils#getGenericTypeAt returned an empty Optional, rooted at a ClassNotFoundException trying to load Map."""," @Parameter @Optional private Function> headersRef; ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9910","06/14/2016 14:17:26",8,"Cannot name paramater as the name of the class ""It is pretty common that when you have an operation that receives a Pojo, the parameter name will be the name in camelcase. Right now we force the users to change the name of the parameter of the class. Even more inconsistent is the fact that if you have a Pojo with the following structure we generate the XSD perfectly and we don't complain about the child element name: Expected: No renaming should be required for this simple scenario. A DslModelProperty will describe how each element should be generated regarding wrapped and non-wrapped elements, by describing the element name, if its wrapper or not, and the wrapped element name."""," public boolean create(Account account); public boolean get(RecordRef recordRef); public class ComplexPojo { private SimplePojo childPojo; private SimplePojo simplePojo; // If it is allowed here, and xsd is generated correctly, we shouldn't complain when this happens at a parameter public SimplePojo getSimplePojo() { return simplePojo; } public void setSimplePojo(SimplePojo simplePojo) { this.simplePojo = simplePojo; } public SimplePojo getChildPojo() { return childPojo; } public void setChildPojo(SimplePojo childPojo) { this.childPojo = childPojo; } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9918","06/14/2016 20:18:57",2,"Add some default values to the @Optional annotation. ""It would be a good idea to have some default value constants in the Optional annotation for cases where the default value is highly used in multiple connectors. For example: This way we avoid having a PAYLOAD constant in each connector. True and False are other posible default values.""","PAYLOAD = """"#[payload]""""",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9925","06/15/2016 15:34:00",1,"Remove default app from distribution ""Mule Server now starts without failures without that application and it is no needed and the users must manually remove it.""","",0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9929","06/16/2016 16:09:12",5,"Remove MuleContext from MuleMessage ""Remove MuleContext from MuleMessage. The following places where the muleContext is used have to be reviewed: * DefaultMuleMessage#serializeValue() ** transformer to byte[] from the registry * DefaultMuleMessage$SerializedDataHandler ** transformer to byte[] from the registry * MessagingException#generateMessage() ** get a transformation service * WildcardFilter#accept() ** get a transformation service * AbstractSessionHandler#deserialize() ** getExecutionClassLoader() * SerializeOnlySessionHandler#storeSessionInfoToMessage ** getObjectSerializer() * DefaultMuleEvent ** get muleContext from message to keep reference * WsConfig$DynamicAttributeEvalutorMap#getEvaluatedMap() ** getExpressionManager() * OutputPayloadInterceptor#handleMessage ** get a transformation service * IsJsonFilter#accept() ** get a transformation service ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9934","06/16/2016 18:26:17",3,"Extract HTTP response creation logic from response builder component ""Right now, the response builder component that matches the XML code has the transformation logic. This will be a problem when said component is no longer required and is also inconsistent with the request builder code. Having the logic in a separate MuleEventToHttpResponse would be much clearer.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9937","06/16/2016 22:56:34",5,"Lifecycle wrongfully applied on ObjectFactory instances ""Run OperationExecutionTestCase. What happens is that the product of OperationMessageProcessorObjectFactory is receiving its lifecycle before the getObject() method is even invoked on ConfigurationProviderObjectFactory. This happens despite the order declared at org.mule.runtime.config.spring.SpringRegistryLifecycleManager.SpringContextInitialisePhase#SpringContextInitialisePhase What's expected is that: * ConfigurationProvider instances are registered first * ConfigurationProvider instances receive lifecycle first * OperationMessageProcessor comes later Also consider that the same has to work for ConnectionProviderObjectFactory""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9953","06/22/2016 16:17:57",5,"Unclear error message when building an extension with multiple providers ""When building an extension that has 2 or more connection providers with no XML annotation the error shown is useless since it doesn't tell you what were the error is, nor how to solve it. The error should tell you the name of the classes that generated the conflict and suggest to use the @org.mule.runtime.extension.api.annotation.Alias annotation. """," [ERROR] diagnostic: error: Multiple entries with the same key[connection] java.lang.IllegalArgumentException: Multiple entries with the same key[connection] at org.mule.runtime.extension.api.introspection.AbstractComplexModel.toMap(AbstractComplexModel.java:132) at org.mule.runtime.extension.api.introspection.AbstractComplexModel.(AbstractComplexModel.java:48) at org.mule.runtime.extension.api.introspection.ImmutableExtensionModel.(ImmutableExtensionModel.java:58) at org.mule.runtime.extension.api.introspection.ImmutableRuntimeExtensionModel.(ImmutableRuntimeExtensionModel.java:60) at org.mule.runtime.module.extension.internal.introspection.DefaultExtensionFactory$FactoryDelegate.toExtension(DefaultExtensionFactory.java:148) at org.mule.runtime.module.extension.internal.introspection.DefaultExtensionFactory$FactoryDelegate.access$100(DefaultExtensionFactory.java:130) at org.mule.runtime.module.extension.internal.introspection.DefaultExtensionFactory.createFrom(DefaultExtensionFactory.java:124) at org.mule.runtime.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.parseExtension(ExtensionResourcesGeneratorAnnotationProcessor.java:107) at org.mule.runtime.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.lambda$null$0(ExtensionResourcesGeneratorAnnotationProcessor.java:82) at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:1240) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1219) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1239) at org.mule.runtime.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.lambda$process$1(ExtensionResourcesGeneratorAnnotationProcessor.java:81) at java.util.Optional.ifPresent(Optional.java:159) at org.mule.runtime.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.process(ExtensionResourcesGeneratorAnnotationProcessor.java:79) at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794) at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705) at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91) at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035) at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176) at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856) at com.sun.tools.javac.main.Main.compile(Main.java:523) at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129) at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138) at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.executeWithExceptionsHandled(AbstractAnnotationProcessorMojo.java:545) at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.execute(AbstractAnnotationProcessorMojo.java:285) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286) at org.apache.maven.cli.MavenCli.main(MavenCli.java:197) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9955","06/22/2016 18:30:00",8,"Set up parallel builds in Maven ""Set up the project modules to build in parallel at least for the 4.x CE branch. Some tests may need tweaking in order to properly run in multithreaded mode, but our spike shows we can reduce build time by at least 50% in CE.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9958","06/22/2016 19:33:19",8,"Make DataType getters return Objects instead of Strings ""Methods getMimeType and getEncoding currently return strings. They should return MimeType and Charset respectively.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9960","06/22/2016 19:54:33",5,"POJO @Parameters default values are not being set. ""Having a POJO with any @Parameter that is @Optional and has a defaultValue, that defaultValue is never going to be set. The defaultValues aren't written in the schema and are not taking in count when parsing the xml, instead always null is set for those values. For example, for a simple POJO like this one: """," public class Content { @Parameter @Optional(defaultValue = """"text/plain"""") private String contentType; } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9962","06/22/2016 20:39:06",3,"Wrong validation is made when using Map ""When an operation returns a Map and the pojo is a concrete, none abstract class with getters and setters, an error is reported saying you need to add a metadata resolver. *Pojo* *Operation class* *Error* Expected: No error should be shown since there is no dynamic metadata."""," public class Ingredient { private double amount; private String type; public String getType() { return type; } public void setType(String type) { this.type = type; } public double getAmount() { return amount; } public void setAmount(double amount) { this.amount = amount; } } public class BasicOperations { /** * Operation With Map description * * @param mapParameter Map param description */ public Map operationWithMap(Map mapParameter) { return mapParameter; } } [ERROR] Failed to execute goal org.bsc.maven:maven-processor-plugin:2.2.4:process (process) on project extension-with-map-of-string-pojo: Error executing: org.mule.runtime.module.extension.internal.exception.IllegalOperationModelDefinitionException: Component 'operationWithMap' in Extension 'basic' specifies 'java.util.Map' as a return type. Operations with return type such as Object or Map must have defined a not null MetadataOutputResolver -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9963","06/23/2016 15:52:34",5,"Validate that complex types are provided on a exclusive way ""por complex parameters (pojos, lists, maps), we want to allow the user to provide such value either as an expression parameter or as a child element. For example: or We need to have a way so that the parser automatically validates that if the myPojo attribute is present, then the my-pojo element is forbidden. Corner cases: * the myPojo element might have a default value, so Element.getAttribute(String) would return a non-null value anyway. We have to consider Element.getAttributeNode(String).getSpecified() * given the myPojo attribute, the name of the child element to verify is calculated as follows: ** for a Map: hyphenize(pluralize(""""myPojo"""")) ** for a List or Pojo: hyphenize(""""myPojo"""") NOTE: hyphenize and pluralize functions are defined in org.mule.runtime.module.extension.internal.util.NameUtils, feel free to take them somewhere else as long as the SDK runtime is able to use them"""," ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9964","06/23/2016 16:13:38",0,"HTTP listener provider should reuse server ""Right now, the provider is creating a new server on each connect but since the management is cached it works.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9966","06/23/2016 16:19:56",3,"Test Grizzly's PRESERVE_HEADER_CASE property ""Test Grizzly's PRESERVE_HEADER_CASE property""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9975","06/24/2016 01:59:23",13,"Spike: IPv6 support ""Perform a spike on assessing the current support for IPv6 and detect the possible gaps. The outcome of a quick assessment performed by [~nahuel] is that IPv6 is not fully supported. Following are the steps taken for the validation: {quote} Started mule as ./mule -Djava.net.preferIPv6Addresses=true -Djava.net.preferIPv4Stack=false Oracle JDK 8, OS X El Capitan, Amazon AMI with RedHat Note: On wrapper.conf, the default is wrapper.java.additional.3=-Djava.net.preferIPv4Stack=TRUE Deployed an app with a listener with the broadcast host configured in different ways: HOST -- Result 0.0.0.0 -> OK :: -> NPE/Protocol Family unavailable 0:0:0:0:0:0:0:0 -> NPE [::] -> NPE ::1 -> OS X: OK/ Amazon AMI using RedHat: Protocol Family unavailable FF02::1 (ie all nodes) -> Address Family not supported FF02::2 (ie all routers) -> Address Family not supported ::0.0.0.0 -> NPE/Protocol Family unavailable {quote} For this spike to be considered successful, we should have a clear understanding of the current support status and have identified the gaps.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9976","06/24/2016 10:34:53",3,"Add temporary support for spring property placeholders in new DSL ""For now, and until MULE-9825 is complete, we need to add basic support for spring property placeholders in the XML configuration.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9986","06/27/2016 09:50:16",8,"Introduce MultipartPayload ""Introduce MultipartPayload""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9987","06/27/2016 15:56:42",2,"Review DataType implementations equals/hashCode standard compliance ""Currently, DataType implementors have some logic in their equals method that does not comply with the java specification.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9988","06/27/2016 16:02:10",5,"ConnectionProvider.connect() should not depend on the config ""Right now people find it hard to identify which parameters should be placed in the config and which in the connection provider. Also, requiring the CP to have a config in order to connect overcomplicates the connectivity testing feature. To solve the UX and implementation problem, we'll just remove the config parameter from the connect method so that ConnectionProviders can work standalone""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9989","06/27/2016 16:22:08",5,"Support full xml generation based on elements DslModelProperty ""In order to generate the application Xml, Studio and Mozart are required to introspect the MetadataTypes, follow naming conventions and special logic based on the type and its usages. Ideally, we should be able to provide a way to generate the Xml based only in the DslModelProperty, which should contain all the required rules""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9990","06/27/2016 16:42:28",8,"DataSense service returns incomprehensible payload ""when DataSense for a given MP is returned, the JSON response is hard to understand and use. Use a better format.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9995","06/27/2016 23:08:45",1,"Preserve media type parameters in mule ""Currently, when a media type is parsed, only the charset parameter is kept in mule. Maybe we should keep/propagate any other parameters as well.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9996","06/28/2016 16:09:19",3,"First successful is not notifying all paths ""The element first Successful like the one in the example bellow: When asked the Mule context to create all the paths for a flow containing only this code it will return 4 paths: Of those paths, this one flowname/processors/0/0 belongs to the processor chain. Now the problem is, when running this code no notification informing the execution of the path flowname/processors/0/0 is coming. If the processor chain is outside the first successful the notification comes but not inside the first successful. """," flowname/processors/0 flowname/processors/0/0 flowname/processors/0/0/0 flowname/processors/0/0/1 ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-9999","06/28/2016 19:22:57",1,"Incorrect vendor when loading file extension ""When deploying an application that uses file extensions the vendors for the available extensions are listed in the log, but it is empty: """," INFO 2016-06-28 15:20:23,817 [Mule.app.deployer.monitor.1.thread.1] org.mule.runtime.module.extension.internal.manager.DefaultExtensionManager: Registering extension Email Connector (version: 4.0-SNAPSHOT vendor: ) INFO 2016-06-28 15:20:25,652 [Mule.app.deployer.monitor.1.thread.1] org.mule.runtime.module.extension.internal.manager.DefaultExtensionManager: Registering extension File Connector (version: 4.0-SNAPSHOT vendor: ) INFO 2016-06-28 15:20:26,014 [Mule.app.deployer.monitor.1.thread.1] org.mule.runtime.module.extension.internal.manager.DefaultExtensionManager: Registering extension Ftp Connector (version: 4.0-SNAPSHOT vendor: ) INFO 2016-06-28 15:20:27,945 [Mule.app.deployer.monitor.1.thread.1] org.mule.runtime.module.extension.internal.manager.DefaultExtensionManager: Registering extension Ftp Connector (version: 4.0-SNAPSHOT vendor: ) INFO 2016-06-28 15:20:30,314 [Mule.app.deployer.monitor.1.thread.1] org.mule.runtime.module.extension.internal.manager.DefaultExtensionManager: Registering extension Validation Module (version: 4.0-SNAPSHOT vendor: ) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10000","06/28/2016 19:33:32",5,"Add the concept of minimum Mule Version and Extension Category ""*Add the concept of minimum Mule Version and Extension Category* * In the same way as DevKit does: ** add the concept of min Mule Runtime version for extension, to be able to declare which is the minimum version that the extension requires to work correctly ** add the concept of extension category *(Community, Select, Premium and Certified)*, this is required when packaging a connector and also for license checking.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10003","06/29/2016 03:30:53",0,"OAuth2 authorization-code-grant-type should reuse refresh_token ""h5. Problem According to the following section of RFC 6749: https://tools.ietf.org/html/rfc6749#section-6 {quote} The authorization server MAY issue a new refresh token, in which case the client MUST discard the old refresh token and replace it with the new refresh token. The authorization server MAY revoke the old refresh token after issuing a new refresh token to the client. If a new refresh token is issued, the refresh token scope MUST be identical to that of the refresh token included by the client in the request. {quote} It is up to be interpreted by readers but an interpretation would be: if the authorization server didn't return a new refresh_token the old one should be used when refreshing the access_token next time. This scenario is what some servers called it """"offline"""" or """"never expire"""" and it is used mostly with APIs from mobiles. Google's OAuth2 server supports this scenario: https://developers.google.com/identity/protocols/OAuth2WebServer#offline But they would also would need to support RFC 7009 'OAuth 2.0 Token Revocation' in order to allow uses to revoke an """"offline""""/""""never expire"""" refresh token for a given user/app. https://tools.ietf.org/html/rfc7009 On the other hand, other implementations such Box.com do not support this and they always issue to clients both tokens during a refresh access_token. https://www.box.com/blog/oauth2-update-longer-lived-refresh-tokens/ h5. Proposed implementation As the specification has this """"optional"""" scenario where refresh_token 'MAY' not be issued by the server when refreshing the access_token, the OAuth2 component should keep the old 'refresh_token' for next attempt. MULE-9660 changed the behaviour to log a warning message if 'refresh_token' was not issued by the authorization server instead of failing, it was always expecting to get both tokens with every refresh token operation. So, that would be modified to keep the old refresh_token instead and the warning message reverted. If during the next attempt to get a new access_token using the old refresh_token happens after the refresh_token was revoked in authorization server, an unauthorized exception would be thrown.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10008","06/29/2016 21:11:10",1,"StringToBoolean transformer transforms ""hello"" to false ""As shown in MULE-9948 and MULE-9915 this can cause problems when transformer expressions that end up configuring a message processor.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10010","06/30/2016 05:43:48",0,"Improve integration tests performance ""There are several resource leaks in integration tests, which lead to the module taking over 30 minutes to build. The log shows almost 200 hung threads after all tests had run. As a workaround, we increased the PermGen space setting it to 256m, but we should be able to revert this after we fix the tests.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10011","06/30/2016 10:54:43",8,"Transport Message Compatibility/Adaption Documention ""In 3.x DefaultMuleMessage: - Used default encoding, now it has empty (optional) encoding by default. - Set CORRELATION outbound properties, not it doesn't. - Used ENCODING (and CONTENT_TYPE?) in inbound property to set DataType when message created, now it doesn't. - Updated DataType when outbound ENCODING or CONTENT_TYPE properties set, now it doesn't. - Message allows null payload and converts to NullPayload internally, now it does not allow null. - Message allowed inconsistency between `message.payload.class` and `message.dataType.type`, now it doesn't. - Message allowed `message.payload.class` to be sub-class of `message.dataType.type`, now it doesn't. - Message allowed receiving a message as payload and copying its properties, now it doesn't. - MessageInfoMapping is removed. Use set-correlation-id to get the same functionality. - Splitter no longer has an enableCorrelation. use set-correlation-id to get the same functionality if needed.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10012","06/30/2016 17:42:25",1,"file:matcher minSize accepts negative numbers """""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10017","06/30/2016 21:14:28",8,"Remove RequestContext ""Remove usages of RequestContext and RequestContext itself.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10019","06/30/2016 21:49:17",5,"SDK date attributes should support ISO 8601 ""SDK date or datetime attributes should support ISO 8601 format.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10021","07/01/2016 18:50:35",0,"Add capability to lookup for external bundles within mule ""For connectivity testing using just the parameters of a connection provider we need to be able to locate a bundle that may be stored externally from the runtime. This change introduces a repository module for remote retrieval an local caching of external dependencies.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10024","07/01/2016 19:46:58",2,"OperationContext should distinguish between null-value parameters and not passed parameters ""This is needed, for instance, in AbstractReturnDelegate, to know if mediaType and encoding were set. If not, the values that come with the original message must remain. In the case where a value is an expression that evaluates to null, we should fail when setting that as mediaType or charset instead of silently leaving the values form the original message.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10025","07/01/2016 20:27:55",8,"Minimize the amount of classes that extensions need to expose. ""Currently, extensions expose the config classes, the operation classes, the connection providers, etc. Ideally, it should be possible to only expose the complex parameter and return types.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10029","07/04/2016 13:50:38",8,"Update Extension's SchemaBuilder to use the DslSyntaxResolver ""Currently, the schema builder has logic regarding when to generated a child element, a wrapper, how to express a collection based on the types, etc. All this logic should be covered in the DslElementResolver, and the schemaBuilder should consume it in order to generate the according schema, instead of duplicating its logic.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10031","07/04/2016 16:27:49",1,"Add an Extensible as a custom TypeAnnotation contributed by the SDK ""When a Class is annotated with Extensible, the SDK should contribute to the MetadataType of that Class with a custom TypeAnnotation that declares it as an SDK extensible component. This should not be part of `ClassInformationAnnotation` since an extensible class is any non final class, but for the sdk an extensible type is only the classes annotated with Extensible.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10037","07/04/2016 23:16:09",5,"Create annotation to be able to provide descriptions/summaries for Components, Parameters, etc ""*Create annotation to be able to provide descriptions/summaries for Components, Parameters, etc* * In the same way as DevKit does with the {{@Summary}} annotation, create an annotation to provide a way to give a summary or brief description of an Operation, Source, Configuration, Parameter, etc with out using JavaDocs.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10042","07/05/2016 22:41:00",5,"Operations should no longer be allowed to return a MuleMessage instance ""SDK operations should no longer be allowed to return MuleMessage instances since those will no longer have generic types. A new OperationResult object should be created instead so that we can keep using generics as a way of communicating metadata types and decoupling the extensions from the MuleMessage""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10044","07/06/2016 14:22:14",1,"file:create-directory accepts paths in directoryName attribute ""This causes that if I put a full directory in {{directoryName}} to create a directory ignoring the {{basePath}} """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10045","07/06/2016 17:24:56",3,"Redundant basePath attribute in file:create-directory ""When using {{file:create-directory}} the full path is composed by {{file:config/baseDir+file:create-directory/basePath+file:create-directory/directoryName}}, basePath is not needed since {{directoryName}} can use an expression.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10048","07/06/2016 19:43:03",2,"Extension Studio packager generates a wrong feature name ""Extension Studio packager generates a wrong feature name""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10758","07/07/2016 15:28:24",8,"Migrate HTTP Module Listener QA tests to HTTP Extension in Mule 4.x ""Migrate HTTP Module QA tests to HTTP Extension in Mule 4.x""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10057","07/07/2016 23:18:52",3,"Allow new parsers to support different children of same type ""Support for child elements with different names but the same type in the parsers""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10059","07/09/2016 14:17:43",1,"Fix transports-parsers-tests xml schema ""Fix the following tests: org.mule.compatibility.config.spring.parsers.endpoint.AttributeErrorTestCase.testError org.mule.compatibility.config.spring.parsers.endpoint.ComplexEndpointTestCase.testComplex org.mule.compatibility.config.spring.parsers.endpoint.MultipleTransformerRefsTestCase.testSingleRef org.mule.compatibility.config.spring.parsers.endpoint.MultipleTransformerRefsTestCase.testMultipleRefs ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10062","07/11/2016 15:58:32",5,"Add concept of standalone Email to Email Connector ""The new email connector does not have metadata support, we must add the resolvers to support it.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10063","07/11/2016 16:00:42",13,"Support single resource transactions on SDK operations ""Support transactions for local, single resource transactions on operations.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10064","07/11/2016 16:03:03",5,"Provide dynamic metadata resolvers for file and ftp attributes ""File and Ftp connectors share operations but use different implementations of the FileAttributes interface. Add a MetadataResolver which communicates the right type. Consider that this also affect the TreeNode object that the list operation returns""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10065","07/11/2016 16:17:06",1,"Do not propagate attributes when operation does not set it ""sdf""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10066","07/11/2016 16:28:25",13,"Spike on SDK powered WS-Consumer ""Spike on effort and features needed""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10068","07/11/2016 18:27:08",2,"Email Connector: Support connection level headers for SMTP Connections. ""The Email connector must have support for a set of headers that are bounded in each SMTP operation.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10069","07/11/2016 18:42:06",5,"Artifact must export resource files instead of resource's folder paths ""Artifacts are currently exporting resources using the resource path. For example, for a resource with path META-INF/test.properties, a META-INF entry is added to the module properties. This introduces a problem as resource paths can be used in different jars (opposed to java packages which should not be reused)""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10073","07/12/2016 20:11:05",2,"email: Add the capability of add attachments when forwarding and replying an email ""*email: Add the capability of add attachments when forwarding an email* * In the same way when using the {{send}} operation, add the capability on {{forward}} operation to be able to add email attachments""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10074","07/12/2016 22:02:24",5,"Introduce the concept of @XmlElementStyle parameters ""We need a RefOnly annotation that can be applied to complex type parameters (all across the board) so that they cannot be defined inline, they can only be referenced from the registry or provided through an expression. This annotation is: * Exclusive with @NoRef * Only valid when applied to complex types * Redundant when applied to a non instantiable type""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10075","07/12/2016 22:07:16",5,"Support text parameters ""We need to have String parameters which support extensive text. E.g.: For this we can reuse the @Text annotation which right now is just a display hint."""," [[CData bla ]] ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10077","07/12/2016 22:16:18",3,"Metadata Type resolution fails when an operation returns int[][] ""If an operation returns an int[][], then the generated MetadataType doesn't contain a TypeAnnotation""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10078","07/12/2016 22:52:26",0,"Properly handle disposal of XaTransactedJmsMessageReceiver ""The session and consumer for a XaTransactedJmsMessageReceiver are stored in a thread local. This causes these resources to be leaked when the receiver is disposed form a thread different than the one that started it.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10081","07/13/2016 16:38:08",2,"ArtifactClassLoaderRunner - Add support for scanning multiple base packages when discovering extensions ""The current version only supports to configure one basePackage to be used when discovering extensions by scanning the class path for classes annotated with @Extension. It would be nice to support multiple packages in order to allow customers to have extensions with a complete different package from the Mule built in Extensions. Consider performance impact or other tools when implementing this, current version is using Spring to scan the class path.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10083","07/13/2016 16:54:33",8,"ArtifactClassLoaderRunner - Improve classpath classification for selecting which artifacts are already bundled within the container ""ArtifactClassLoaderRunner uses an exclusion filter pattern for artifacts that should not be included in the application classloader neither the plugin classloaders. This is fine for a first version but there could be another way to solve this without having to explicitly set this filters due to they have the issue of keeping duplicated things that are already in pom files into an annotation (see org.mule.functional.junit4.runners.ArtifactClassLoaderRunnerConfig). One approach could be to use maven instead and create a pom that depends in all the mule modules (modules, core, container, etc) that would go to the container, so the users of this runner could define that dependency as provided and that will go to the container class loader. But, still the test dependencies have also transitive dependencies to the same artifacts so they would be need to be optional or either provided so they are not linked from the tests scope artifacts.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10090","07/14/2016 15:01:41",2,"Fix extensions studio plugin packaging ""In order to be able to load custom editor files provided by extensions we need to do the following: - Rename field *editorsPath* => *path* to avoid breaking current mechanism and existing - *editors.xml* doesn't need to be part of the jar used in runtime to run the app. Because of this, the file should not be placed under src/main/resources for it to be part of the generated plugin. The file should be located inside an *editor* folder and copied to the root at the same level as the *plugin.xml* file""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10093","07/14/2016 20:45:25",5,"Subtypes of a type declared only as a generic are not parsed correctly ""Subtypes of a type declared only as a generic are not parsed correctly.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10094","07/14/2016 21:05:10",1,"Incomplete application is continously redeployed ""After configuring the continuous build to work in parallel, a test started to fail from time to time: org.mule.runtime.module.launcher.DeploymentServiceTestCase.redeploysBrokenExplodedAppOnStartup. After playing with the test, if a Thread.sleep(10000) is added right before the last assertion, then the test will fail. Why? Because the application redeployment does not occur just once, but it occur on every cycle of the deployment service.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10097","07/15/2016 15:45:26",3,"file:matcher name should be mandatory outside a flow ""When a {{file:matcher}} is defined as a top level element it should be mandatory the {{name}} attribute. """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10102","07/15/2016 19:50:49",13,"Add Metadata support to WS-CONSUMER ""Add the necessary metadata resolvers needed to support datasense in the new WSC module. This must cover Headers (Represented as a Key Value pair) and the body content for both input and output. WSC usability is highly coupled to this.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10103","07/15/2016 20:06:59",13,"SPIKE: new CXF proxy client for the new WS Consumer ""The current WS consumer works using the inbound and outbound properties for managing headers and attachments, since in mule 4.0 the properties concepts is going to dissapear a new proxy client must be created. The client must be based on a specially configured CXF Client to allow sending raw XML representing a SOAP envelope over CXF for SOAP processing, WS-Security, etc. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10104","07/15/2016 20:19:01",13,"Start development of the new WS consumer extension ""Create the necessary extension classes required to build a the new extension.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10105","07/18/2016 15:21:12",0,"notifyDeletes should default to false in file:listener ""Most use cases for file:listener often include a move or delete operation. Having delete notifications enabled by default can result in confusing loops. Switch the default to false to better suite most common use cases.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10110","07/18/2016 19:23:02",0,"File copy/move fail to overwrite when target file is in a different directory ""When you use the file:copy or file:move operation and you try to overwrite a file which leaves in a different directory than the source one, then it doesn't overwrite but fails saying that the file already exists""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10111","07/18/2016 20:13:45",1,"ExtensionFunctionalTestCase creates wrong manifest directory when using #getConfigFiles() ""When extending from ExtensionFunctionalTestCase and using the method `String[] getConfigFiles()` for returning the list of XML files, the `ExtensionFunctionalTestCase#getEffectiveConfigFile()` fails in the `getConfigurationResources()` implmented by default, as it does return empty string rather than `null`. By returning an empty string, the files generated by the extensions (META-INF/spring.schemas, META-INF/spring.handler, etc..) end up in the current folder of the module being tested rather than in the /target folder (target/META-INF/spring.schemas and so on..) The fix should be checking for `!StringUtils.isBlank(configFile)` in all the ifs, rather than `configFile != null`.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10115","07/19/2016 17:48:04",8,"Review how correlation is implemented/achieved ""Review the implementation/usages of *org.mule.runtime.core.message.Correlation*. Ref: http://www.informit.com/articles/article.aspx?p=1398616&seqNum=6 ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10117","07/19/2016 20:31:31",1,"MVELExpressionExecutor used after a TypeSafeExpressionValueResolver from extensions API cannot load application classes ""Having the configuration attached to this issue where it has an expression-component and uses sockets extension. See for more details, it part of socket's extension tests. The expression-component fails due to it cannot find the class which is the super class of the test being executed. After debugging the code I found that caches the compiled MVEL expressions but always uses the same instance of which resolves only once the ClassLoader for executing the expresion by obtaining it from Thread.currentThread().getContextClassLoader() and assign it to a variable. Therefore, when resolves the expression the parserConfiguration gets the extension classloader and when trying later to evaluate the expresion-component from the flow it cannot find the class.""","org.mule.extension.socket.protocol.LengthProtocolTestCaseorg.mule.extension.socket.SocketExtensionTestCaseorg.mule.runtime.core.el.mvel.MVELExpressionExecutororg.mule.mvel2.ParserConfigurationorg.mule.runtime.module.extension.internal.runtime.resolver.TypeSafeExpressionValueResolver#[payload]",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10120","07/21/2016 00:32:17",0,"Map not sent as form data if mimeType is application/java ""When a Java map is used as payload and the data type's mime type reflects this using """"application/java"""", said map is not sent as form data via HTTP. This is because we assumed under that scenario the calculated content type would be null (but it's """"application/java"""").""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10123","07/21/2016 15:22:47",13,"[SPIKE] Error handling proposal spec ""Per the error handling proposal, we need to implement an error-handler that takes on-error elements capable of assigning the handling to the one that can handle the type of error generated.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10124","07/21/2016 15:42:47",1,"SchemaGenerator doesn't generate elements in the same order ""elements in a generated XSD not necesarilly maintain order. Although this is not a productive problem since the test case is still valid and the runtime doesn't really care, it does makes code review harder, because when a schema does change you see a lot of changes which are unrelated. For example look at https://github.com/mulesoft/mule/pull/2982#discussion_r71688076""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10126","07/21/2016 15:45:52",8,"ArtifactClassLoaderRunner - Add support for artifacts with different versions ""The current version it is not considering different versions for artifacts, for instance if mule-core depends on commons-collections 1.1 and it doesn't export it and an extension/plugin has a dependency to commons-collection 2.3 and it is used internally by the plugin (it is not exported too) the classification and class loaders should be created each with the correct version. We are not supporting this and the classpath is built by maven using nearest version resolution therefore on the described scenario the only commons-collection jar that will be in classpath is version 2.3 due to the testing is happening from the extension artifact.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10134","07/21/2016 16:49:32",5,"Migrate extensions to use isolated test runner ""HTTP, FTP and validations are not yet using the isolated test runner. This task is about migrating those extensions.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10135","07/21/2016 16:53:05",13,"Annotation Based describer should be abstracted from classes ""The AnnotationBased describer currently works by introspecting through the java.reflect API. Create an abstraction around types, methods, fields, etc which allows the describer to work without directly relying on a Class object""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10136","07/21/2016 16:57:27",5,"ArtifactClassLoaderRunner - Add support for services ""Add support for testing MULE-9752 * Classification process should look for services, basically it would scan the classpath to get which jars or target/classes have a service.properties * In order to classify the dependencies it will get all the compile dependencies for those discovered artifacts (as with plugins/extensions, compile is the scope defined for this matter) * Once the classification is done a new artifactClassLoader (with the filter) has to be created as child of container CL but it should not be part of the hierarchy, sharedLibs will continue to be the parent of the composite CL and child of container * In addition to that, a service discoverer would need to be written in order to change the discover default mechanism that Mule Service has for registering the services""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10137","07/21/2016 16:59:43",13,"Allow AnnotationBasedDescriber to work with AST trees ""Following in the work of MULE-10135, implement a Type abstraction which works with an AST tree obtained from an AnnotationProcessor. This also includes changing the current SDK annotation processor to not explicitly enrich the model through the javadocs, but rather rely on this Type abstraction to already provide them. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10138","07/21/2016 17:11:42",8,"Add the concept of exclusive parameters ""Add a way for two optional parameters (at any level) to declare that only one of them can be defined at the same time. This should not be applicable among required parameters.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10140","07/21/2016 18:43:50",8,"Support XA transactions in SDK extensions at the operation level ""Allow SDK powered extensions to have operations which join XA transactions""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10141","07/21/2016 18:49:48",8,"Support multi transactions in SDK powered operations ""SDK should allow extensions to have operations which join multi transactions""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10144","07/22/2016 18:30:05",0,"ArtifactClassLoaderRunner - Add support to explicitly export plugin classes ""While migrating extensions there was this need for exporting classes from the plugin/extension that are not exposed. The tests need to access them for testing the features but they are not supposed to be exported as part of the API. Implement a way to allow exporting particular classes for plugins/extensions.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10145","07/22/2016 19:45:37",2,"Remove mule-tests-functional from distribution ""Remove Mule Testing Framework and its dependencies from Mule distributions. Remove JUnit Remove XMLUnit Users who wish to test their applications should use MUnit Framework.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10146","07/22/2016 19:46:31",8,"SchemaBuilder doesn't support child elements for List of Date types ""Right now, we can provide the value of a Date/LocalDateTime/etc in the XML. That value is parsed and the object is constructed, but if I wanted to specify those objects as child elements of a List that's no possible because those types doesn't fulfil the condition of generating child elements: What we should do is implementing the logic for generating child elements in a metadatatype visitor for the shouldGenerateChildElements method."""," private boolean shouldGenerateChildElementForType(MetadataType metadataType) { boolean isPojo = metadataType instanceof ObjectType; Class clazz = getType(metadataType); boolean isPrimitive = clazz.isPrimitive() || ClassUtils.isPrimitiveWrapper(clazz); return isPrimitive || isExtensible(metadataType) || !subTypesMapping.getSubTypes(metadataType).isEmpty() || (isPojo && isInstantiableWithParameters(clazz)) || (!isPojo && isInstantiable(clazz)); } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10148","07/22/2016 21:44:43",5,"Refactor DeploymentServiceTestCase to avoid using pre-compiled classes and jars ""DeploymentServiceTestCase is currently using different class and jars files to build application, domains, extension and services during the deployment tests. As those files are binary files, is impossible to review the changes on them during the code review process. Also, every change on those file, requires the developer to unzip them into a temp location, change them and then recreate the files replacing the originals. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10149","07/25/2016 16:23:36",5,"Create serialiser for SubtypesModelProperty ""*Create serialiser for SubtypesModelProperty*""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10150","07/25/2016 18:47:37",1,"File extension baseDir is actually a workingDir ""File extension baseDir is actually a workingDir because it works like unix working Dir and not like HTTP basePath which doesn't allow absolute paths and always appends paths to base.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10151","07/25/2016 19:36:43",0,"ArtifactClassLoaderRunner - Missing dependencies at classification when transitive dependency is declared explicitly with another scope ""The following scenario is not well handled by the ArtifactClassLoaderRunner. If an artifact defines a transitive dependency explicitly it is not handled correctly: So, when collecting provided dependencies as scope was part of the identity of a MavenArtifact there was not possible to get the transitive dependency for org.glassfish.grizzly:grizzly-http-server:jar. Fix is to remove scope from the identity and traverse transitive dependencies by artifact identity: groupId/artifacItd/version (optional)."""," // Edge Definitions: """"org.mule.tests:mule-module-http-test:jar::compile"""" -> """"org.mule.modules:mule-module-http:jar::provided"""" ... """"org.mule.modules:mule-module-http:jar::provided"""" -> """"org.glassfish.grizzly:grizzly-http-server:jar::compile""""[style=""""dotted""""] ... """"org.glassfish.grizzly:grizzly-http-server:jar::test"""" -> """"org.glassfish.grizzly:grizzly-http:jar::test"""" ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10152","07/25/2016 19:45:40",0,"ArtifactClassLoaderRunner - When loading modules for container classloader it is using launcher classloader instead of the correct one ""When discovering modules for container classloader it is using TCCL that is launcher CL instead of the one that holds only the urls classified for the container: Instead, it should do: """," @Override protected ArtifactClassLoader createArtifactClassLoader(ClassLoader parentClassLoader, List muleModules, ClassLoaderLookupPolicy containerLookupPolicy) { final ArtifactClassLoader containerClassLoader = new MuleArtifactClassLoader(""""mule"""", urls, parentClassLoader, new MuleClassLoaderLookupPolicy(Collections.emptyMap(), getBootPackages())); return createContainerFilteringClassLoader(discoverModules(), containerClassLoader); } return createContainerFilteringClassLoader(withContextClassLoader(new URLClassLoader(urls, null), () -> discoverModules()), containerClassLoader); ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10155","07/26/2016 16:43:21",3,"Add the concept of keywords to the extension model ""When searching for a component in Studio palette (or even for Mozzart) we support the concept of associated keywords, that makes it easier to find elements in the palette. This keywords have a weight that is used to determine the best match when the user types in the palette filter. For example, the database connector has the following keywords: {code:xml} {code} We could have an annotation that could be used at Extension Level that has a list of Keyword Pojos or a repetable Keyword Annotation. Something like: {code:java} @Keywords({ @Keyword(value=""""db"""",weight=2), @Keyword(value=""""jdbc"""",weight=2) }) public class MyExtension{ ... } {code} Or with the repeatable annotation: {code:java} @Keyword(value=""""db"""" weight=2) @Keyword(value=""""jdbc"""" weight=1) public class MyExtension{ ... } {code}"""," @Keywords({ @Keyword(value=""""db"""",weight=2), @Keyword(value=""""jdbc"""",weight=2) }) public class MyExtension{ ... } @Keyword(value=""""db"""" weight=2) @Keyword(value=""""jdbc"""" weight=1) public class MyExtension{ ... } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10160","07/26/2016 21:55:54",2,"Move lifecycle interfaces to mule-api ""Lifecycle interfaces must be moved to the mule-api project as they are need by other parts of the API""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10172","07/29/2016 14:43:36",8,"Migrate perf-test to mule4 to add them to a build using JMH ""Migrate perf-test to mule4 to add them to a build using contiperf.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10173","07/29/2016 18:21:16",0,"ConnectionProviders should be better typed ""For metadata and transaction support purposes, we need a better way to determine the type of connection management that should be applied to each connection provider. Because the current approach is based on the double dispatch pattern, it requires live instances which is not a good approach for these use cases. ConnectionProviders should be typed in a way that it's simple to provide this information both in the meta model and in live instances.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10174","07/29/2016 20:58:30",3,"Review where do ConnectionProvide specializations belong ""The ConnectionProvider interface has some specializations (PoolingConnectionProvider, CachedConnectionProvider, etc) and they all live in mule-api. There's a concern if the specializations should move to ext-api, in order to keep the main mule-api as tight as possible. Doing so has the following disadvantages: * No real ease in backwards compatibility, since ext-api has to be as backwards compatible as the mule-api * mule-core should have to depend on ext-api which is something we want to avoid""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10175","08/01/2016 04:23:53",3,"Upgrade Repository module dependencies ""Analyze where the dependency comes from and upgrade to the latest version. The current versions include betas and milestone releases.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10178","08/01/2016 20:20:04",0,"InputStream not closed on core, launcher and spring-config ""While researching an issue on Windows when an application is undeployed and some files are not removed from file system I found a few inputStreams not closed. This will generate leaks and in OS' like Windows will lock files.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10180","08/01/2016 20:36:51",0,"Classloader leak when Oracle JDBC Driver is not used but included in application lib folder ""h5. Problem During the disposal process of the application classloader the DriverManager is called to get the registered drivers in order to deregister them if they were loaded with the current classloader. The DriverManager has an static block code that loads by SPI the drivers present in the classloader (from where the DriverManager was called) so whenever is called during the classloader's disposable phase if the OracleDriver was not used by the application it will be loaded when is called just before it will be deregistered by the releaser. This has a side effect and generates classloader leaks due to OracleDriver leaves open inputStreams. h5. Proposal Remove the workaround for http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5041014 in and call method (added in jdk7) that does a better job by closing the classloader and releasing any inputStream opened. This fixes the file locked in Windows OS environments to OracleDriver's jar file. h5. Caveats Oracle has still a memory leak that cannot be resolved with the proposal described here, two objects are left in ThreadLocal and not removed when the driver is deregistered. The objects left in ThreadLocal are: ""","org.mule.module.launcher.artifact.DefaultResourceReleaserDriverManager.getDrivers()org.mule.module.launcher.GoodCitizenClassLoaderURLClassLoader.close() oracle.sql.AnyDataFactory oracle.sql.TypeDescriptorFactory ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10181","08/02/2016 13:00:47",8,"Migrate core transformers to new parsing mechanism. ""Migrate core transformers to new parsing mechanism.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10182","08/02/2016 15:17:32",0,"Duplicate class definition exception when disposing domain 'default' ""When starting a FakeMuleServer with an App that fails to deploy, the system proceeds to stop the domain 'Default' and an exception is raised. Stack trace: """," ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Mule is up and kicking (every 5000ms) + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ INFO 2016-08-02 10:53:07,260 [Thread-1] org.mule.runtime.module.launcher.StartupSummaryDeploymentListener: ********************************************************************** * - - + DOMAIN + - - * - - + STATUS + - - * ********************************************************************** * default * DEPLOYED * ********************************************************************** ******************************************************************************************************* * - - + APPLICATION + - - * - - + DOMAIN + - - * - - + STATUS + - - * ******************************************************************************************************* * app * default * FAILED * ******************************************************************************************************* INFO 2016-08-02 10:53:27,340 [Thread-1] org.mule.runtime.module.launcher.application.DefaultMuleApplication: App 'app' never started, nothing to dispose of INFO 2016-08-02 10:53:27,340 [Thread-1] org.mule.runtime.module.launcher.domain.DefaultMuleDomain: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Stopping domain 'default' + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ INFO 2016-08-02 10:53:27,340 [Thread-1] org.mule.runtime.module.launcher.domain.DefaultMuleDomain: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Disposing domain 'default' + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ INFO 2016-08-02 10:53:27,436 [Thread-1] org.mule.runtime.module.launcher.application.DefaultMuleApplication: App 'app' never started, nothing to dispose of INFO 2016-08-02 10:53:27,436 [Thread-1] org.mule.runtime.module.launcher.domain.DefaultMuleDomain: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Stopping domain 'default' + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ INFO 2016-08-02 10:53:27,436 [Thread-1] org.mule.runtime.module.launcher.domain.DefaultMuleDomain: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Disposing domain 'default' + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ERROR 2016-08-02 10:53:27,439 [Thread-1] org.mule.runtime.module.launcher.DeploymentDirectoryWatcher: Error stopping artifact default java.lang.LinkageError: loader (instance of org/mule/runtime/module/launcher/MuleSharedDomainClassLoader): attempted duplicate class definition for name: """"org/mule/runtime/module/artifact/classloader/DefaultResourceReleaser"""" at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_92] at java.lang.ClassLoader.defineClass(ClassLoader.java:763) ~[?:1.8.0_92] at java.lang.ClassLoader.defineClass(ClassLoader.java:642) ~[?:1.8.0_92] at org.mule.runtime.module.artifact.classloader.MuleArtifactClassLoader.createResourceReleaserInstance(MuleArtifactClassLoader.java:110) ~[mule-module-artifact-4.0.0-M2.jar:4.0.0-M2] at org.mule.runtime.module.artifact.classloader.MuleArtifactClassLoader.dispose(MuleArtifactClassLoader.java:89) ~[mule-module-artifact-4.0.0-M2.jar:4.0.0-M2] at org.mule.runtime.module.launcher.domain.DefaultMuleDomain.dispose(DefaultMuleDomain.java:241) ~[mule-module-launcher-4.0.0-M2.jar:4.0.0-M2] at org.mule.runtime.module.launcher.domain.DomainWrapper.dispose(DomainWrapper.java:48) ~[mule-module-launcher-4.0.0-M2.jar:4.0.0-M2] at org.mule.runtime.module.launcher.DeploymentDirectoryWatcher.stopArtifacts(DeploymentDirectoryWatcher.java:231) ~[mule-module-launcher-4.0.0-M2.jar:4.0.0-M2] at org.mule.runtime.module.launcher.DeploymentDirectoryWatcher.stop(DeploymentDirectoryWatcher.java:214) ~[mule-module-launcher-4.0.0-M2.jar:4.0.0-M2] at org.mule.runtime.module.launcher.MuleDeploymentService.stop(MuleDeploymentService.java:138) ~[mule-module-launcher-4.0.0-M2.jar:4.0.0-M2] at org.mule.test.infrastructure.deployment.FakeMuleServer.stop(FakeMuleServer.java:129) ~[mule-tests-infrastructure-4.0.0-M2.jar:4.0.0-M2] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10183","08/02/2016 16:23:51",5,"Migrate compatibility transport IT tests to use isolated test runner ""Review what would be needed in order to migrate transports compatibility IT tests to use isolated test runner.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10185","08/02/2016 16:40:49",0,"ArtifactClassLoaderRunner CXF issue when running all tests, works when executed isolated ""Running all test ends up failing on these test when isolated runner is used. ""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10186","08/02/2016 17:37:46",0,"Classloader leak due to shutdown listeners are not cleared ""h5. Problem During the disposal process of the application classloader there is a reference to the classloader due to has an anonymous classes with an strong reference to the classloader. The root cause of this issue is classloader doesn't not null the list of listener after it triggers the calls to them. h5. Proposal Clear the list of shutdown listeners""","org.mule.module.launcher.log4j2.MuleLoggerContextFactory",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10188","08/02/2016 21:41:13",3,"Create HTTP hamcrest matchers ""Create Hamcrest matchers that we can reuse in HTTP tests.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10189","08/02/2016 23:11:04",1,"Allow ModelProperties to be searched hierarchically ""Right now, you cannot have a hierarchy of model property since you cannot get them by a base class. Make it happen""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10194","08/03/2016 21:53:27",2,"Review boot packages needed to be exported when migrating IT tests to run with isolation ""While migrating integration tests to run with isolated test runner I needed to expose groovy and aop packages. review why this is necessary. ContainerClassLoaderFactory: This also applies to yourkit."""," //TODO(gfernandes): need to expose every package form groovy """"org.codehaus.groovy"""", //TODO(gfernandes): review why this is required as it is exported on scripting mule-module.properties (fails ClassInterceptorTestCase) """"org.aopalliance.aop"""" ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10197","08/04/2016 17:33:48",3,"Add custom TypeAliasAnnotation for MetadataType ""When a Class is annotated with @Alias, then the metadataType should be able to preserve that information. If no alias is provided, then the class simpleName will be used as alias.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10201","08/05/2016 15:12:48",2,"ArtifactClassLoaderRunner - Add support to infer which kind of artifact is being classified ""There are different cases where classification and classloaders for running tests would happen: * testing extension code from the test folder of the artifact * testing plugin code from the test folder of the artifact * testing an application that uses plugins/extensions Each case defines how target/classes and target/test-classes folder would have to classified and in which classloader should go. It would help to infer if the artifact being tested is a plugin, extension or application: * plugin, the target/classes should go to the plugin classloader and target/test-classes to the application classloader * extension, same as plugin in addition to that it should generate the metadata * application, target/classes and target/test-classes should both go to the application classloader""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10202","08/05/2016 15:22:02",3,"ArtifactClassLoaderRunner - Make it more extensible ""* TestClass should be only used in JUnit context, so the classification and factory can be used outside a JUnit context * Context, remove everything related to testClass and annotation to JUnit runner only * ClassPathURLProvided should allow to extend it with a list of provided URLs * Set the rootArtifactClassesFolder and rootArtifactTestClassesFolder paths to the classification context * Change name to ClassLoaderRunnerFactory to ClassLoaderIsolationFactory * Make protected the three methods on buildAppUrls, buildPluginsUrlClassification, buildContainerUrls (internal extension) * Remove comma separated parsing logic from classloading code and put it in runner JUnit * Define the public API ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10203","08/05/2016 15:26:30",1,"Move to a separate module ArtifactClassLoaderRunner ""Move code to another module""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10205","08/05/2016 15:59:31",8,"Create HTTP service ""We need to move core HTTP functionalities to a service that can be exposed so others can create their own servers and clients. The HTTP extension will use said service as will OAuth, for example.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10209","08/05/2016 19:58:57",3,"Contribute to the MetadataModel with custom TypeAnnotationAdapters ""Contribute to the MetadataModel with custom TypeAnnotationAdapters so serialization of custom annotations provided by the extension are serialized correctly""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10210","08/05/2016 22:02:13",1,"DefaultResourceReleaser should not be exposed, move to an internal package "" and its implementation are exposed by launcher module, in addition to that they are part of runtime packages This could end up in an linkage error due to these classes have to be loaded by each Application and Domain classloader in order to dispose the resources (jdbc drivers). They have to be moved to an internal package.""","org.mule.runtime.module.artifact.classloader.ResourceReleaserorg.mule.runtime",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10212","08/08/2016 13:28:09",0,"Use new MetadataType AnnotationTypes interface ""Mule changes regarding to https://www.mulesoft.org/jira/browse/MDM-12""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10214","08/08/2016 16:15:15",8,"@Import should not require a class element ""The import annotation requires a class element which makes DslSyntaxResolver to have that class in the classpath plus forces extensions to export too many classes.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10215","08/08/2016 16:19:23",13,"Spike on introducing DSQL into the SDK ""Perform a Spike on introducing DSQL into the extensions. Consider: * syntax * execution * data sense * extension model""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10216","08/08/2016 16:21:46",8,"Support auto paging operations in SDK ""Support auto paging""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10217","08/08/2016 16:25:45",1,"ParameterGroups with a ParameterGroup field of the same type of their parent produces a StackOverFlow ""ParameterGroups with a ParameterGroup field of the same type of their parent produces a StackOverFlow""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10218","08/08/2016 16:27:29",8,"Exclusive optionals should support nested groups ""To be completed....""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10220","08/08/2016 16:42:32",8,"Add the concept of operation and sources which don't require a config ""In the current model each operation needs to be executed with a resolved configuration. This is not something that is always needed. Some operations like http:basic-auth-filter doesn't require a config a trying to resolve one is an usability problem, since the extension doesn't contain an implicit config and most common thing is to have two configs defined.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10221","08/08/2016 16:48:38",8,"Create tooling packaging ""In order to separate the artifacts that are deployed when building a mule app and the artifacts that are used for tooling or dependencies management we need to generate another artifact. Currently inside the Studio plugin we have the following information: Also we have a MANIFEST.MF The packaging we need to define should contain: * The zip of the mule plugin that is deployed with the mule app using this extension. * An icons folder with the following structure: ** _theme.id_: *** a small and a large version of the icon. The naming convention is: {prefix}-connector-small.png and {prefix}-connector-large.png The current themes generated by the SDK are: *theme.classic*, *theme.light* * The extension model json. * The custom editor if the extension defines one. * Sources of the extension if available (Community connectors currently package this). * Javadocs of the extension if available (Community connectors currently package this). * Generated documentation (The one DevKit used to generated, this is no the same as Javadocs). * A descriptor/Manifest that has at least the following information: ** Contribution Jar: This can be used to attach the sources for debugging purposes ** Contribution Sources: The sources that the user needs to attach ** Contribution Type: We need know if this is a template, a mule extension, or a mozart project. ** Required Execution Enviroment: In the future maybe some extension will require java 9. ** The dependencies (in the extensions case, the extensions this extension depends of). The extension model already has the following information: * Extension Version * Min mule version * Namespace prefix * Namespace URI * Namespace Schema Location """," Manifest-Version: 1.0 Bundle-SymbolicName: org.mule.tooling.ui.contribution.basic-custom-edi tor.4.0.0;singleton:=true Bundle-Name: BasicCustomEditor Bundle-Version: 4.0.0.201608291051 Archiver-Version: Plexus Archiver Require-Bundle: org.eclipse.ui,org.eclipse.core.runtime,org.mule.tooli ng.core;bundle-version=""""1.0.0"""" Bundle-ManifestVersion: 2 Bundle-RequiredExecutionEnvironment: JavaSE-1.8 Bundle-ActivationPolicy: lazy Bundle-Vendor: Mulesoft Created-By: 25.66-b17 (Oracle Corporation) Eclipse-BundleShape: dir ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10234","08/11/2016 18:56:28",5,"TypeAliasAnnotation value is populated with the wrong value ""When using subtypes, the TypeAlias value generated for pojos that don't use the @Alias doesn't have the expected value. For a pojo with name *Book*, the value should be *book* For a pojo with name *BasePojo*, the value should be *base-pojo* Check the extensions located at https://github.com/mulesoft/mule-tooling-mock-connector/tree/mule-4.x/extension-with-subtypes ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10235","08/11/2016 19:09:34",2,"Move services from launcher to a new services module ""MULE-9752 define the concept of services for the Mule Container. This code was implemented inside mule-module-launcher, this issue is about moving out that code to a new mule-module-services so it can be used from other modules.""","",0,1,0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10236","08/11/2016 20:03:14",1,"CXF components will throw a NPE when added after WMQ or AMQP inbound endpoints ""CXF components will throw a NPE when added after WMQ or AMQP inbound endpoints. The org.apache.cxf.binding.soap.SoapTransportFactory#getDestination() method only recognize the http and jms protocols. Endpoint URL protocol need to be replaced with http:// to works properly. org.mule.module.cxf.builder.AbstractInboundMessageProcessorBuilder#getAddress() method already uses http as default protocol. Pull request to fix the issue submitted. Link below: https://github.com/mulesoft/mule/pull/2631""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10238","08/12/2016 14:59:35",0,"Get rid of SimpleRegistry from Mule ""We need to get rid of the SimpleRegistry that is no longer needed. To do so we also need to consolidate test using AbstractMuleContextTestCase to use the spring mechanism to create the MuleContext. While the SimpleRegistry is later consolidated into the SpringRegistry it's causing issues since, for instance, is making transformers to be registered twice in the transformer graph. This is because the transformer is registered when a transformer is registered as an object intante in the SimpleRegistry but later the SpringRegistry creates a ConstantFactoryBean from it an when it does post processing of beans it registers the transformer twice. This is avoid currently by checking duplicates object in the post processing of registered objects which is not the right way to do it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10240","08/12/2016 15:53:15",3,"Some http config parameters should move to the ConnectionProvider ""Things like user/pass authorization are currently on the request config element, which will make it impossible to manage through the connectivity service.Those should move connection provider. It would also be good to have a general review of all attributes to make sure that we're not missing anything else.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10241","08/12/2016 16:25:12",1,"ExtensionsFieldHandler does not consider ParameterGroups ""ObjectType does not contain the fields which should be derived from a ParameterGroup annotation""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10243","08/12/2016 17:24:16",1,"Subtypes cannot be parsed as top level elements ""Subtypes pojos not always find their way into a top level element parser""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10244","08/12/2016 18:55:05",5,"Move META-INF generated folder and content from folder /classes to /generated-sources ""Right now we are generating all the XSD and resources of the extension under the folder {root}/target/classes. For IDEs to work correctly and out of the box, generated sources should always go to {root}/target/generated-sources. This makes the development of mule app for testing for the extensions much easier since the XSD are recognized automatically allow you ot use the autocompletion. We need to move the location were the files is generated, but without changing the current way we package the extensions.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10248","08/16/2016 14:55:42",8,"Migrate components to use new parsing mechanism ""Migrate components to use new parsing mechanism""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10251","08/16/2016 15:34:41",3,"InterceptingCallback implementation with out generic as return type of an operation produces an ArrayOutOfBoundException when describing an Extension ""*InterceptingCallback implementation with out generic as return type of an operation produces an ArrayOutOfBoundException when describing an Extension* Having a {{InterceptingCallback}} implementation like : Will produce an ArrayOutOfBounds exception when describing the annotated extension. This occurs in the {{IntrospectionUtils#unwrapInterceptingCallback}} when tries to get the generic value of the {{InterceptingCallback}}""","public class SomeInterceptorObject implements InterceptingCallback { @Override public Object getResult() throws Exception { return null; } }",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10254","08/16/2016 18:15:31",5,"@ParameterGroup doesn't work on abstract pojos ""If a pojo is used as a parameter and such pojo has a parameterGroup on a parent abstract class, then such parameterGroup is not injected.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10257","08/17/2016 17:27:03",0,"Cannot access test classes when running isolated tests ""Consider the SelectStoreProcedureTestCase in the DB extension. It doesn't work because the classloader can't find a class in which the store procedure is implemented. There should be a way to make utility classes available.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10259","08/17/2016 17:47:47",13,"Add DSQL into the SDK. ""Add the necessary mechanism to the SDK in order to handle DSQL queries on extensions Full feature specification can be found [here|https://docs.google.com/document/d/11MvxHPCtKHZl5BJw8EM8lAhtAYpO16c8YSKFXJTBGOs/edit#]""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10260","08/17/2016 17:50:35",13,"Add endpoint for retrieving keys by config or resolver ""Provide the capability for retrieving all the MetadataKeys associated to a config or resolver.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10261","08/17/2016 19:07:50",8,"Refactor exception strategies to new error handling semantics ""This task includes: - Refactor choice-exception-strategy to error handler - Refactor catch-exception-strategy to error-handler + on-error-continue - Refactor rollback-exception-strategy to error handler + on-error-propagate: This task does not include get rid of This task does not include also changing any configuration parameter from existing exception strategies.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10262","08/17/2016 19:11:55",3,"Include error type attribute into on-error handlers ""This is just to include the error type parameter with an UNKNOWN error type and be able to filter using it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10264","08/17/2016 19:20:41",5,"Implement message redelivery support ""This is to: - Rename idempotent-redelivery-policy to redelivery-policy - Process placeholder for redelivery-policy inside message source so it's part of the flow chain - Create REDELIVERY_EXHAUSTED error type - Migrate existing test cases.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10265","08/17/2016 19:28:27",5,"Create scope for error handling + transactions ""This is to: - Rename transactional element to the new name for the error-handling + transaction scope - Rename transactional attribute configuration. - Rename all test cases""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10266","08/17/2016 19:41:15",13,"Define common error types and create mapping for internal exceptions within core ""We need to: - Define the set of common errors thrown by the runtime - Define the logic to map the internal processor exceptions to the common errors types - Execute the mapping logic before invoking the error handler (done in MULE-10376) - Move MessagingException away from the API (done in MULE-10376) - Change Error handlers to receive always a MessageException (done in MULE-10262)""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10267","08/17/2016 19:43:36",1,"Allow to define message-redelivery element within any SDK source ""We need the SDK to allow inside ANY message source a message-redelivery element (with the same structure as today's idempotent-message-redelivery). The SDK does not need to do any processing with it. The runtime will enforce the required behaviour""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10268","08/17/2016 20:01:46",0,"Proxy Authentication Header is not included when using proxy for HTTPS target server ""When using HTTP Requestor with Proxy for HTTPs protocol, the Proxy Authentication is not included. https://github.com/AsyncHttpClient/async-http-client/issues/1152 This is an issue reported in AHC and fixed in 1.9.39. MULE-10165 upgraded AHC so this issue will include a test in Mule to verify that the issue is fixed.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10269","08/17/2016 20:09:00",8,"Define and implement mechanism to declare exception mappings per module ""We must define and implement a way for modules to declare exception mappings (e.g. via a provider) that the error type inference interceptor can get when a given message processor fails with an exception to determine the error type.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10272","08/17/2016 20:13:22",8,"Add support to be able to add restriction to parameters values ""*Add support to add restriction to parameters values* * When receiving an *Number* parameter in most cases that value should be restricted to the useful numbers, example: ** *HTTP Connector Port*: 0 and 65535 ** *Anypoint MQ - Fetch size*: 1-10 ** etc... * Also this can be made for *String* parameters, where a regex can be placed to validating that the input is correct, for example, for an email or a URL. * This feature is UI focused and is really important to communicate with out reading a documentation, and more important with out running the mule app, if the configured values is correct or not.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10274","08/17/2016 20:17:09",8,"Move extension model to the runtime so it can be used to describe any extension. ""We want to move part of the extension model to the Mule API since we need a mechanism to describe the different components that can be use in a mule application. This components descriptors will help us have a simpler interaction between mule and tooling and will also allow us to get information from an application just from parsing the configuration and using the descriptors like doing type checks at design time. We want descriptors mainly for: - Global elements - Operations - simple message processors that execute a single action - Routers - Scopes - Transformers Descriptors will contain information about the parameters types of the operations, the return types and also if they reference other global elements in the configuration. Use cases: - Tooling XML writing By providing information with the component describer on what are the possible parameters and how the component can be serialized in XML we have a mechanism for tooling to know how to deal with every component, show an editor for it, and write it to XML. By providing information with the parameters that may reference global elements, and the type of those global elements, the tooling can know which are the possible global elements that may be referenced from a reference parameter. - XML validation Validations - We can validate in design time the values provided for the parameters by the user. For instance, if the user configured an expression over an attribute that do not accepts expressions the we can validate it. Or if the user is referencing a global element that does not match the required type then we can validate it. Type checking - By having all the expected parameter types and the output types provided by then and propagation rules we can do type checking on design time. This also required type inference from the EL used to get the return type of an expression where the input type is known.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10275","08/17/2016 20:18:06",5,"Include exception mapping mechanism in HTTP ""The HTTP service/module/extension needs to declare mappings for each status code error, so as to know which code to send.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10277","08/17/2016 20:26:08",8,"Implement error mappings for message processors ""All message processor must be allowed to define an error mapping, meaning when some error occurs, the actual type is a customised one: To map any errors one could use ANY as sourceType or omit the sourceType attribute altogether. Notice that this should also include allowing the on-error-propagate component to declare an error mapping for the re-thrown error."""," ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10280","08/17/2016 20:35:11",8,"Create MuleEvent error field ""Define the new field within the MuleEvent to hold the error data field This also involves: - Take into account i18n - Define exception type that may hold the error message so it can be used when the error field gets created.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10284","08/18/2016 05:17:12",2,"@Text has no effect when applied to a parameter group in abstract class ""Given the following classes When using the Concrete class as a parameter, the text field translates into the DSL as an attribute instead of an element. If Base were no longer abstract and used instead, then the text field behaves as expected """," public class Group { @Parameter @Text private String text; } public abstract class Base { @ParameterGroup private Group group; } public abstract Concrete extends Base {} ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10285","08/18/2016 05:18:41",8,"@Expression has no effect when used in abstract parameter group ""Given the following classes When using the Concrete class as a parameter, the text field expression is resolved even though marked as literal. """," public class Group { @Parameter @Expression(LITERAL) private String text; } public abstract class Base { @ParameterGroup private Group group; } public abstract Concrete extends Base {} ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10286","08/18/2016 05:21:51",8,"Stack overflow in DslSyntaxResolver when indirect cyclic reference found ""Consider the following classes: DslSyntaxResolver contains logic to control composite relationships in a class. However, when that cycle is implemented through a parameter group, it is not detected and a StackOverflow arises"""," public class Master { @ParamterGroup Group group; } public class Group { @Parameter Master master; } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10287","08/18/2016 06:32:21",1,"Expressions not evaluated on @Text parameters ""When a parameter is annotated with @Text, the value is always assigned as is, without expression evaluation""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10294","08/18/2016 15:45:12",5,"Support TypeConverters on simple type child elements ""We need to define a mechanism that complex elements that resolve to simple types can have a type converter.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10295","08/18/2016 16:10:40",3,"target attribute accepts expressions ""when the SDK automatically adds the target parameter, it accepts values such as #[flowVars.pepe]. It should not. It should verify that it's not an expression. it should also validate that it doesn't start with the flowVars. prefix either""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10296","08/18/2016 16:30:05",5,"Remove event.getMuleContext() dependency from exception creation ""Remove event.getMuleContext() dependency from exception creation""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10297","08/18/2016 16:30:29",5,"Remove event.getMuleContext() dependency from flow statistics ""Remove event.getMuleContext() dependency from flow statistics""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10298","08/18/2016 16:30:30",13,"Deploy applications in parallel ""Mule application deployment is done sequentially, this means that one application is deployed (installed, initialized, started) before any other app is deployed. Some applications can take a lot of time to deploy because the usage of components that require initializing many things, or just because the config XML is huge. When there are many applications deployed in the same container, the time required to start all of them is significative. Making the deployment parallel would help to reduce the required time.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10299","08/18/2016 16:38:57",13,"Remove MuleEvent dependency on FlowConstruct. ""Maybe move it to the execution context?""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10300","08/18/2016 16:47:08",2,"ArtifactClassLoaderRunner - As maven dependency graph could generate loops between dependencies this should be handled while resolving dependencies ""When testing the runner from external extensions there was a loop created by the dependency graph maven plugin when jaxen artifact was having a link to itself. These scenarios should be avoided when reading the graph generated by the plugin. Add a way to handle this cases and log a warn message.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10301","08/18/2016 16:50:14",1,"ArtifactClassLoaderRunner - Support for testing transports from compatibility plugin ""Add support for classifying transports as plugins in order to allow testing them with isolation before they are assembled to the compatibility plugin.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10303","08/18/2016 17:58:29",5,"Extensions Parser fails to load pojos declared as top element if the pojo is only used as value of Map ""The Extension parsers fails to load a global Pojo, when the pojo is only used as the value of a map. The XSD element exists, but you get the following error: The parameter looks like The mule app is: The pojo used for test: """," Caused by: org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: The element 'ingredient' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/map-string-pojo present on the classpath? @Parameter private Map mapParameters; /** * Dummy Pojo for test */ public class Ingredient { private String type; private double amount; public String getType() { return type; } public void setType(String type) { this.type = type; } public double getAmount() { return amount; } public void setAmount(double amount) { this.amount = amount; } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10306","08/18/2016 21:27:11",0,"Add option to disable internal entity expansion in XML (leads to DoS) ""Internal entity expansion in XML allows the following DoS attack in the XSLT component: https://en.wikipedia.org/wiki/Billion_laughs Like in MULE-7390 the solution would involve adding a parameter to disable entity expansion.""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10323","08/19/2016 14:36:49",5,"Define handlers reutilisation (refs) ""We need to define and provide a way for handler to be reused. This includes deciding whether only whole error-handlers or even on-error components can be referenced. This should allow us to get rid of the reference exception strategy.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10325","08/19/2016 17:57:41",5,"Invalid extension can be packaged when an operation has the same name as a POJO ""When an extension has an operation with the same name as a POJO (ignoring case) and that POJO is used as an argument of the operation, the extension can be packaged, but it should fail because a Mule app with this extension fails when deployed. This is the signature of the failing method: And this is the Mule exception: The source code to reproduce this issue is [here|https://github.com/fbarrios/success-factors-connector/tree/40c2810a0406c75fee7e2059c9ab1a1dba55798c]."""," public DataHandler getJobResult(@NotNull final GetJobResult params) throws SuccessFactorsException; ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Failed to deploy artifact 'connectorApp', see below + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ org.mule.runtime.module.launcher.DeploymentException: Failed to deploy artifact [connectorApp] at org.mule.runtime.module.launcher.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:38) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArchiveDeployer.guardedDeploy(DefaultArchiveDeployer.java:324) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArchiveDeployer.deployArtifact(DefaultArchiveDeployer.java:345) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArchiveDeployer.deployExplodedApp(DefaultArchiveDeployer.java:311) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:114) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:41) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DeploymentDirectoryWatcher.deployExplodedApps(DeploymentDirectoryWatcher.java:290) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DeploymentDirectoryWatcher.start(DeploymentDirectoryWatcher.java:151) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.MuleDeploymentService.start(MuleDeploymentService.java:98) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.MuleContainer.start(MuleContainer.java:194) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_73] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_73] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_73] at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_73] at org.mule.runtime.module.reboot.MuleContainerWrapper.start(MuleContainerWrapper.java:52) ~[mule-module-reboot-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:2788) ~[wrapper-3.2.3.jar:3.2.3] Caused by: org.mule.runtime.core.api.MuleRuntimeException: org.mule.runtime.module.launcher.DeploymentInitException: SAXParseException: sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.mulesoft.org/schema/mule/success-factors,get-job-result'. at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1218) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:95) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:53) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:25) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] ... 15 more Caused by: org.mule.runtime.module.launcher.DeploymentInitException: SAXParseException: sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.mulesoft.org/schema/mule/success-factors,get-job-result'. at org.mule.runtime.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:206) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:1212) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:164) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1273) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1235) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1211) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:95) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:53) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:25) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] ... 15 more Caused by: org.mule.runtime.core.api.config.ConfigurationException: Line 166 in XML document from URL [file:/Users/federicobarrios/mulesoft/runtimes/mule-standalone-4.0-20160805.205005-680/apps/connectorApp/org.mule.modules.successfactors.SuccessFactorsConnector.flows.xml] is invalid; nested exception is org.xml.sax.SAXParseException: sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.mulesoft.org/schema/mule/success-factors,get-job-result'. (org.mule.runtime.core.api.lifecycle.InitialisationException) at org.mule.runtime.module.launcher.artifact.ArtifactMuleContextBuilder.lambda$build$0(ArtifactMuleContextBuilder.java:267) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:164) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1273) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1235) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.ArtifactMuleContextBuilder.build(ArtifactMuleContextBuilder.java:236) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:198) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:1212) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:164) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1273) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1235) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1211) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:95) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:53) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:25) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] ... 15 more Caused by: org.mule.runtime.core.api.lifecycle.InitialisationException: Line 166 in XML document from URL [file:/Users/federicobarrios/mulesoft/runtimes/mule-standalone-4.0-20160805.205005-680/apps/connectorApp/org.mule.modules.successfactors.SuccessFactorsConnector.flows.xml] is invalid; nested exception is org.xml.sax.SAXParseException: sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.mulesoft.org/schema/mule/success-factors,get-job-result'. at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:115) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:54) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:49) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:148) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryBrokerLifecycleManager.fireInitialisePhase(RegistryBrokerLifecycleManager.java:61) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker.initialise(AbstractRegistryBroker.java:48) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:122) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:91) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:87) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.invokePhase(MuleContextLifecycleManager.java:69) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:61) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.DefaultMuleContext.initialise(DefaultMuleContext.java:294) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:222) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:83) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.ArtifactMuleContextBuilder.lambda$build$0(ArtifactMuleContextBuilder.java:263) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:164) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1273) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1235) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.ArtifactMuleContextBuilder.build(ArtifactMuleContextBuilder.java:236) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:198) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:1212) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:164) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1273) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1235) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1211) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:95) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:53) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:25) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] ... 15 more Caused by: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 166 in XML document from URL [file:/Users/federicobarrios/mulesoft/runtimes/mule-standalone-4.0-20160805.205005-680/apps/connectorApp/org.mule.modules.successfactors.SuccessFactorsConnector.flows.xml] is invalid; nested exception is org.xml.sax.SAXParseException: sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.mulesoft.org/schema/mule/success-factors,get-job-result'. at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleArtifactContext.loadBeanDefinitions(MuleArtifactContext.java:314) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129) ~[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:541) ~[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:452) ~[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:125) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:107) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:54) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:49) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:148) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryBrokerLifecycleManager.fireInitialisePhase(RegistryBrokerLifecycleManager.java:61) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker.initialise(AbstractRegistryBroker.java:48) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:122) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:91) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:87) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.invokePhase(MuleContextLifecycleManager.java:69) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:61) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.DefaultMuleContext.initialise(DefaultMuleContext.java:294) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:222) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:83) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.ArtifactMuleContextBuilder.lambda$build$0(ArtifactMuleContextBuilder.java:263) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:164) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1273) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1235) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.ArtifactMuleContextBuilder.build(ArtifactMuleContextBuilder.java:236) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:198) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:1212) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:164) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1273) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1235) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1211) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:95) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:53) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:25) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] ... 15 more Caused by: org.xml.sax.SAXParseException: sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.mulesoft.org/schema/mule/success-factors,get-job-result'. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) ~[?:?] at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) ~[?:?] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) ~[?:?] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) ~[?:?] at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown Source) ~[?:?] at org.apache.xerces.impl.xs.traversers.XSDHandler.checkForDuplicateNames(Unknown Source) ~[?:?] at org.apache.xerces.impl.xs.traversers.XSDHandler.buildGlobalNameRegistries(Unknown Source) ~[?:?] at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source) ~[?:?] at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source) ~[?:?] at org.apache.xerces.impl.xs.XMLSchemaValidator.findSchemaGrammar(Unknown Source) ~[?:?] at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) ~[?:?] at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) ~[?:?] at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) ~[?:?] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) ~[?:?] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) ~[?:?] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) ~[?:?] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) ~[?:?] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) ~[?:?] at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) ~[?:?] at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) ~[?:?] at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleDocumentLoader.loadDocument(MuleDocumentLoader.java:91) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadDocument(XmlBeanDefinitionReader.java:429) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:391) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleArtifactContext.loadBeanDefinitions(MuleArtifactContext.java:314) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129) ~[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:541) ~[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:452) ~[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:125) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:107) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:54) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:49) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:148) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryBrokerLifecycleManager.fireInitialisePhase(RegistryBrokerLifecycleManager.java:61) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker.initialise(AbstractRegistryBroker.java:48) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:122) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:91) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:87) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.invokePhase(MuleContextLifecycleManager.java:69) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:61) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.DefaultMuleContext.initialise(DefaultMuleContext.java:294) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:222) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:83) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.ArtifactMuleContextBuilder.lambda$build$0(ArtifactMuleContextBuilder.java:263) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:164) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1273) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1235) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.ArtifactMuleContextBuilder.build(ArtifactMuleContextBuilder.java:236) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:198) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:1212) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:164) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1273) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1235) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:1211) ~[mule-core-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:95) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:53) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.launcher.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:25) ~[mule-module-launcher-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] ... 15 more INFO 2016-08-19 13:30:46,021 [WrapperListener_start_runner] org.mule.runtime.module.launcher.DeploymentDirectoryWatcher: ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10326","08/19/2016 18:38:16",5,"Provide a way to identify a subtitution group for a parameter and subtypes mapping when using the DslElementSyntax ""When generating the editors.xml for an extension that has a subtype mapping, or extensible elements, there is no way to identify the element associated group in order to allow other extensions to contribute to the element. If you use the get the dsl for a base type, it has the element name of something that doesn't exists in the XSD and that it can conflict with a parameter model name. Check extension: https://github.com/mulesoft/mule-tooling-mock-connector/tree/mule-4.x/extension-with-subtypes""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10329","08/19/2016 23:52:19",5,"SchemaBuilder wrongfully adds stuff when operation has a group ""Look at the XSD generated for the stored-procedure operation of the new DB connector. All the ParameterGroup elements are both as flattened attributes and child elements, as if they were pojos""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10336","08/22/2016 16:02:11",3,"Create a build tool to run formatter over all the projects ""Create an script to run the formatter maven goal over all the maven artifacts in the project.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10339","08/22/2016 20:37:41",5,"Replace Function with a better abstraction ""This feature collides a little bit with LITERAL expression support, which ends up requiring the user to know about the ExpressionManager and the MuleEvent. Provide a better API for doing that, one that is: * A top level object, which is capable of evaluating the expression and returning its literal value * Replaces ExpressionSupport.LITERAL * Less verbose ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10345","08/23/2016 22:24:50",8,"Define API for bindings between mule and EL ""Define API for bindings between mule and EL ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10346","08/24/2016 19:26:16",0,"Upgrade woodstox to 5.0.4 ""Upgrade to woodstox 5.0.4, which contains the fix for https://github.com/FasterXML/woodstox/issues/21 and https://github.com/FasterXML/woodstox/issues/22""","",0,0,0,1,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10349","08/25/2016 14:02:16",13,"Support expression for ""response"" parameters in sources ""MULE-9864 had to be done as a workaround since right now it is not possible to have parameters in a source that support expressions. Though it may make sense for parameters that are required when generating a message, when the response makes it back to the source (assuming the source handles responses) there is a MuleEvent to evaluate expressions against. Thus it does make sense that some of the parameters (the ones used to define a response, for example) support expressions. Another option would be to generate child support for Functions, since those are allowed but a combination of a Map and a Function must be used now to supports children and expression. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10351","08/25/2016 19:04:11",13,"WSC Should use http requester to resolve WSDL if specified. ""The WS Consumer doesn't use the TLS configuration of the HTTP requester because it uses the Java Classes directly instead of the Mule Implementation. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10352","08/25/2016 19:51:14",0,"Make HttpClient Startable instead of Initialisable to match Stoppable ""HttpClient is now initialisable and stoppable, which causes a flow stopped and started to fail since the http client is not recreated but it is stopped.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10356","08/25/2016 22:27:07",0,"Http inbound endpoint returns additional headers in 100 Continue response ""The HTTP inbound endpoint incorrectly handles """"Expect: 100-continue"""" because it adds additional headers that make some clients fail (like AsyncHttpClient). Current response (wrong): HTTP/1.1 100 Continue Content-Type: text/plain Content-Length: 0 Connection: close Expected response (right): HTTP/1.1 100 Continue""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10360","08/25/2016 23:27:33",0,"HTTP requester should support reconnection strategy ""When implementing/thinking MULE-10359, it has to be taken into account that it would be ideal to have a way to force a reconnection/session-refresh when the API returns an specific error value. If that applies, then the current session should be destroyed and regenerated""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10363","08/26/2016 00:08:01",0,"HTTP Oauth2 token manager support should be improved ""Consuming the oauth module when the API slightly different to the regular standard might be harsh to understand, ending in debugging the java mule-module-oauth component to truly understand what's happening. Such usability issues are (there might be more): 1) if the *refreshToken* is missing in the *oauth2:token-response* the application fails at start up (some APIs do not invalidate their tokens, thus refreshing is useless) 2) if, for some reason, there's a need to access the already obtained access token, the oauth2 module requires me to pass a *tokenManager-ref* although I do not necessarily have the need to redefine anything on the object store. Just accesing the access token. 3) this is higly related to *2)*, where some times the obtained token must go in a different header than the *Authorization * one, or change the *Bearer * name for something else. Taking Slack API, the obtained token must go as a query parameter named """"token"""", to achieve it I need to implement the following app (ideally, accessing the access token should be simpler, as I already know which *http:requester-config* I'm working with): 4) is quite common to fail hard when understanding APIs, specially when trying to consume those that relies on OAuth to authenticate with. It will be nice to have a safety relay -like, where the first time authenticating and trying to extract the access token, besides showing how your MEL expression failed it also shows the *complete* body's response, so that the developer could quickly understand that maybe the ID is wrong, the MEL is wrong, or anything else. """," ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10365","08/26/2016 16:09:52",5,"Add support for proxys in SFTP connector (for 4.x) ""The current SFTP connector does not offer proxy support out-of-the-box. It would be nice to be able to configure a proxy via attributes in the connector similar to the following: (UnixPath.java:71) at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281) at java.nio.file.Paths.get(Paths.java:84) at org.mule.extension.ftp.internal.ftp.command.FtpCommand.createDirectory(FtpCommand.java:167) at org.mule.extension.ftp.internal.ftp.command.FtpCreateDirectoryCommand.createDirectory(FtpCreateDirectoryCommand.java:34) at org.mule.runtime.module.extension.file.api.AbstractFileSystem.createDirectory(AbstractFileSystem.java:152) at org.mule.runtime.module.extension.file.api.StandardFileSystemOperations.createDirectory(StandardFileSystemOperations.java:325) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) {quote} """," ... ... ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10370","08/29/2016 15:02:52",0,"Remove custom-exception-strategy element ""Remove custom-exception-strategy element and default-exception-strategy. Since this is the last component that requires the old exception handling infrastructure, as part of this task we also need to remove all of that code.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10375","08/29/2016 21:01:39",8,"MuleArtifactClassLoader dispose fail ""When trying to dispose a MuleArtifactClassLoader the method #createResourceReleaserInstance fails due to a classcast exception. This seems only to fail when creating the CL loader through MuleClassLoaderFactory """," ERROR 2016-08-29 16:25:44,121 [main] org.mule.runtime.module.artifact.classloader.MuleArtifactClassLoader: Cannot create resource releaser instance java.lang.RuntimeException: Can not create resource releaser instance from resource: /org/mule/runtime/module/artifact/classloader/DefaultResourceReleaser.class at org.mule.runtime.module.artifact.classloader.MuleArtifactClassLoader.createResourceReleaserInstance(MuleArtifactClassLoader.java:107) ~[mule-module-artifact-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.module.artifact.classloader.MuleArtifactClassLoader.dispose(MuleArtifactClassLoader.java:86) ~[mule-module-artifact-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.munit.classloading.manager.ClassLoaderManager.restoreCurrentThreadClassLoader(ClassLoaderManager.java:47) ~[munit-maven-plugin-2.0.0-SNAPSHOT.jar:?] at org.mule.munit.MUnitMojo.runTests(MUnitMojo.java:243) ~[munit-maven-plugin-2.0.0-SNAPSHOT.jar:?] at org.mule.munit.MUnitMojo.doExecute(MUnitMojo.java:179) ~[munit-maven-plugin-2.0.0-SNAPSHOT.jar:?] at org.mule.munit.MUnitMojo.execute(MUnitMojo.java:129) ~[munit-maven-plugin-2.0.0-SNAPSHOT.jar:?] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) ~[maven-core-3.0.5.jar:3.0.5] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ~[maven-core-3.0.5.jar:3.0.5] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) ~[maven-core-3.0.5.jar:3.0.5] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) ~[maven-core-3.0.5.jar:3.0.5] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) ~[maven-core-3.0.5.jar:3.0.5] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) ~[maven-core-3.0.5.jar:3.0.5] at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) ~[maven-core-3.0.5.jar:3.0.5] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) ~[maven-core-3.0.5.jar:3.0.5] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) ~[maven-core-3.0.5.jar:3.0.5] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) ~[maven-core-3.0.5.jar:3.0.5] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) ~[maven-embedder-3.0.5.jar:3.0.5] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) ~[maven-embedder-3.0.5.jar:3.0.5] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) ~[maven-embedder-3.0.5.jar:3.0.5] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_92] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_92] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_92] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_92] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) ~[plexus-classworlds-2.4.jar:?] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) ~[plexus-classworlds-2.4.jar:?] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) ~[plexus-classworlds-2.4.jar:?] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) ~[plexus-classworlds-2.4.jar:?] Caused by: java.lang.ClassCastException: org.mule.runtime.module.artifact.classloader.DefaultResourceReleaser cannot be cast to org.mule.runtime.module.artifact.classloader.ResourceReleaser at org.mule.runtime.module.artifact.classloader.MuleArtifactClassLoader.createResourceReleaserInstance(MuleArtifactClassLoader.java:105) ~[mule-module-artifact-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] ... 26 more ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10376","08/29/2016 21:05:49",8,"Implement support for error mapping and error type discovery ""Implement support for error mapping and error type discovery""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10377","08/29/2016 22:52:39",5,"Support keyless metadata fetching ""We should add support in the metadata mediator to get dynamic metadata without specifying a metadata key and removing the capability to get the static metadata that is not used by anyone and it's bounded in the extension model. So the new metadata fetch without key should cover this 2 cases: * the key is required (has @MetadataKeyId) so default values should be used to build the key or if tehre are no default values to build the key the fetch *must* fail. * the key is not required (operation without @MetadataKeyId) and the dinamic resolution should be done with the NullMetadataKey ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10378","08/29/2016 23:19:22",5,"Support boolean and Enums in MetadataKeyId parameter ""Support boolean and Enums as MetadataKeyId parameter types.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10379","08/30/2016 14:36:10",1,"SAXParseException adding logger ""When using a {{logger}} I get a SAXParseException, without the loggers the application gets deployed and works fine. To reproduce try to deploy the attached application.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10383","08/30/2016 15:41:21",2,"Classloading issue using extension extending from ExtensionFunctionalTestCase using HTTP connector ""Consuming the HTTP connector from a test ends up in classloading issues throwing the following exception: To try to workaround the issue, I edited the HttpConnector class, adding the HttpClient with the @Export annotation (making it visible in the plugin.properties as an exported package) but still got the same issue. Code of the Java test Code of the http-ext-integration-text.xml Dependencies for the test I needed: ""","================================================================================ = Testing: test = ================================================================================ org.mule.runtime.core.api.config.ConfigurationException: Could not load class org.mule.extension.http.api.request.client.HttpClient (java.lang.IllegalArgumentException) at org.mule.runtime.core.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:43) at org.mule.runtime.core.context.DefaultMuleContextFactory$1.configure(DefaultMuleContextFactory.java:83) at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:191) at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:77) at org.mule.tck.junit4.AbstractMuleContextTestCase.createMuleContext(AbstractMuleContextTestCase.java:214) at org.mule.tck.junit4.AbstractMuleContextTestCase.setUpMuleContext(AbstractMuleContextTestCase.java:137) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74) Caused by: java.lang.IllegalArgumentException: Could not load class org.mule.extension.http.api.request.client.HttpClient at org.mule.metadata.java.api.utils.JavaTypeUtils.getType(JavaTypeUtils.java:41) at org.mule.metadata.java.api.utils.JavaTypeUtils.getType(JavaTypeUtils.java:25) at org.mule.runtime.module.extension.internal.model.property.ConnectivityModelProperty.(ConnectivityModelProperty.java:34) at org.mule.runtime.module.extension.internal.introspection.enricher.ConnectionModelEnricher.addModelProperty(ConnectionModelEnricher.java:117) at org.mule.runtime.module.extension.internal.introspection.enricher.ConnectionModelEnricher.access$000(ConnectionModelEnricher.java:46) at org.mule.runtime.module.extension.internal.introspection.enricher.ConnectionModelEnricher$1.onOperation(ConnectionModelEnricher.java:70) at org.mule.runtime.module.extension.internal.util.IdempotentDeclarationWalker$$Lambda$73/143293910.accept(Unknown Source) at org.mule.runtime.module.extension.internal.util.IdempotentDeclarationWalker.doOnce(IdempotentDeclarationWalker.java:66) at org.mule.runtime.module.extension.internal.util.IdempotentDeclarationWalker.onOperation(IdempotentDeclarationWalker.java:56) at org.mule.runtime.extension.api.introspection.declaration.fluent.util.DeclarationWalker.lambda$walkOperations$14(DeclarationWalker.java:128) at org.mule.runtime.extension.api.introspection.declaration.fluent.util.DeclarationWalker$$Lambda$72/2120054390.accept(Unknown Source) at java.util.LinkedList$LLSpliterator.forEachRemaining(LinkedList.java:1235) at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) at org.mule.runtime.extension.api.introspection.declaration.fluent.util.DeclarationWalker.walkOperations(DeclarationWalker.java:126) at org.mule.runtime.extension.api.introspection.declaration.fluent.util.DeclarationWalker.lambda$walk$10(DeclarationWalker.java:53) at org.mule.runtime.extension.api.introspection.declaration.fluent.util.DeclarationWalker$$Lambda$65/1983324438.accept(Unknown Source) at java.lang.Iterable.forEach(Iterable.java:75) at org.mule.runtime.extension.api.introspection.declaration.fluent.util.DeclarationWalker.walk(DeclarationWalker.java:48) at org.mule.runtime.module.extension.internal.introspection.enricher.ConnectionModelEnricher.enrich(ConnectionModelEnricher.java:82) at org.mule.runtime.module.extension.internal.introspection.DefaultExtensionFactory.lambda$enrichModel$139(DefaultExtensionFactory.java:138) at org.mule.runtime.module.extension.internal.introspection.DefaultExtensionFactory$$Lambda$64/2114005651.accept(Unknown Source) at java.lang.Iterable.forEach(Iterable.java:75) at org.mule.runtime.module.extension.internal.introspection.DefaultExtensionFactory.enrichModel(DefaultExtensionFactory.java:138) at org.mule.runtime.module.extension.internal.introspection.DefaultExtensionFactory.createFrom(DefaultExtensionFactory.java:121) at org.mule.functional.junit4.infrastructure.ExtensionsTestInfrastructureDiscoverer.loadExtensionModel(ExtensionsTestInfrastructureDiscoverer.java:146) at org.mule.functional.junit4.infrastructure.ExtensionsTestInfrastructureDiscoverer.loadExtensionsFromDescribers(ExtensionsTestInfrastructureDiscoverer.java:140) at org.mule.functional.junit4.infrastructure.ExtensionsTestInfrastructureDiscoverer.discoverExtensions(ExtensionsTestInfrastructureDiscoverer.java:88) at org.mule.functional.junit4.ExtensionFunctionalTestCase.createExtensionsManager(ExtensionFunctionalTestCase.java:102) at org.mule.functional.junit4.ExtensionFunctionalTestCase.access$000(ExtensionFunctionalTestCase.java:52) at org.mule.functional.junit4.ExtensionFunctionalTestCase$1.doConfigure(ExtensionFunctionalTestCase.java:88) at org.mule.runtime.core.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:39) ... 16 more Caused by: org.mule.runtime.module.artifact.classloader.exception.NotExportedClassException: Class 'org.mule.extension.http.api.request.client.HttpClient' not found in classloader for artifact 'mule'. at org.mule.runtime.module.artifact.classloader.FilteringArtifactClassLoader.loadClass(FilteringArtifactClassLoader.java:61) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at org.apache.commons.lang3.ClassUtils.getClass(ClassUtils.java:909) at org.mule.metadata.java.api.utils.JavaTypeUtils.getType(JavaTypeUtils.java:39) ... 46 more WARN 2016-08-30 11:08:46,600 [main] org.mule.tck.junit4.AbstractMuleTestCase: -------------------------------------------------------------------------------- Hung threads count: 1. Test case: org.mule.test.operation.HttpExtIntegrationTest. Thread names: -> Log4j2-AsyncLoggerConfig-2 - 15 --------------------------------------------------------------------------------import static org.junit.Assert.assertThat; import org.mule.functional.junit4.ExtensionFunctionalTestCase; import org.mule.runtime.core.api.MuleEvent; import org.hamcrest.core.Is; import org.junit.Test; public class HttpExtIntegrationTest extends ExtensionFunctionalTestCase { @Override protected String getConfigFile() { return """"http-ext-integration-test.xml""""; } @Override protected Class[] getAnnotatedExtensionClasses() { return new Class[] {org.mule.extension.http.internal.HttpConnector.class}; } @Test public void test() throws Exception { MuleEvent muleEvent = flowRunner(""""test"""").run(); assertThat(muleEvent.getMessage().getPayload(), Is.is(""""value1"""")); } } org.mule.modules mule-module-http ${project.version} test org.mule.modules mule-module-http-ext ${project.version} test org.mule.modules mule-module-sockets ${project.version} test ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10397","08/30/2016 18:06:32",1,"Default and ExpressionSupport Annotations are not persisted in the json when a Pojo field is not annotated with @Parameter ""If your pojo has the following definition, the default and expression support information is lost: We should either support this and process the annotation when the field only has setters and getters, or we should fail at compile time."""," package org.mule.modules.basic.model; import org.mule.runtime.extension.api.annotation.Expression; import org.mule.runtime.extension.api.annotation.param.Optional; import org.mule.runtime.extension.api.introspection.parameter.ExpressionSupport; public class Ingredient { private double amount; private String type; @Expression(ExpressionSupport.NOT_SUPPORTED) @Optional( defaultValue = """"6"""") private String noExpressionField; public String getType() { return type; } public void setType(String type) { this.type = type; } public double getAmount() { return amount; } public void setAmount(double amount) { this.amount = amount; } public String getNoExpressionField() { return noExpressionField; } public void setNoExpressionField(String noExpressionField) { this.noExpressionField = noExpressionField; } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10400","08/30/2016 19:21:12",5,"Review multipart implementation in HTTP ""We need to check the implementation regarding the multipart payload to make sure nothing is missing and no irrelevant component remain. After this is finished, we will be able to migrate MULE-10233 to 4.x.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10401","08/30/2016 19:25:03",8,"Remove HTTP parsing mechanism ""Removing the set-attachment component from mule 4, there is no way to create a multipart payload. This means, for example, that a multipart request can't be generated. We need to provide a way to create such a payload, considering all the set-attachment attributes (content type, name) but also filename and custom headers. Now that operation UX is done we need to have a way of creating such payloads with DW.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10402","08/30/2016 19:33:12",0,"User should not need to create a maven-module-mapping.properties to be able to run their extension tests ""Users are forced to create a file named maven-module-mapping.properties to do a mapping or the artifact Id of the project and the name of the folder, even inside a single module project or if the name of the artifact and the folder is the same. This file should not even exists in this scenario."""," # Mapping for multi-module projects and folder names # $mvn -o --also-make exec:exec -Dexec.executable=""""pwd"""" | grep -A 1 'exec-maven-plugin' | sed '/^--$/d' | sed 'N;s/\n/ /' | awk '{print $6,$7,$8}' | sed 's/---/=/g' | tr -d """" """" | sed 's/$/\//' # DO NOT include mule (root folder) my-extension=/my-extension/ ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10403","08/30/2016 21:09:43",2,"FTP Extension: Write operation doesn't work using SFTP when the destination is a new file. It throws ""Found exception trying to obtain path..."" ""Trying to write using SFTP with Mac doesn't work if the file doesn't exist. It throws: {quote} ******************************************************************************** Message : Found exception trying to obtain path /Users/alejandro/sftp-test/output/text.out. Payload : org.mule.extension.ftp.internal.sftp.SftpInputStream@92728f Element : /read-write-as-copy-config-local-to-local-sftp/processors/1 @ fb1a0d50-6eea-11e6-89d4-985aebc8e9b5 -------------------------------------------------------------------------------- Root Exception stack trace: 2: No such file at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2846) at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2198) at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2215) at com.jcraft.jsch.ChannelSftp.stat(ChannelSftp.java:2172) at org.mule.extension.ftp.internal.sftp.connection.SftpClient.getAttributes(SftpClient.java:114) {quote} *Steps to reproduce:* * Start SFTP Server ** Launch System Preferences and go to “Sharing” ** Click on the checkbox next to “Remote Login” to enable SSH and SFTP ** Check it is working with executing in the cosole """"sftp localhost."""" * Use this config copied at the end of the ticket. * Send a request to """"http://localhost:9090/read-write-like-copy-local-to-local-sftp"""" +*App to reproduce:*+ """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10404","08/30/2016 21:10:02",3,"Fix Error API issues ""We need to do a couple of improvements over the Error API in Mule: - Make MuleEvent.getError() return optional instead of an Error. Since this API is not going to be expose through EL we can make it follow the general Optional rule. - Rename ErrorType.getStringRepresentation() to ErrorType.getIdentifier() - Remove every other method from ErrorType that is held by the MuleEvent since the user doesn't need to know about the parent or namespace.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10405","08/31/2016 06:43:01",8,"FTP Extension: SFTP doesn't support the known_hosts validation if the key uses ECDSA or RSA ""Testing with the MAC SFTP server when you connect using """"sftp localhost"""" the key added to your known_hosts file is using """"ecdsa-sha2-nistp256"""". When I want to connect using Mule SFTP Connection I receive this warning {quote} Root Exception stack trace: com.jcraft.jsch.JSchException: UnknownHostKey: localhost. RSA key fingerprint is bb:cb:63:07:52:24:32:13:d8:b8:ac:07:e3:2e:15:23 at com.jcraft.jsch.Session.checkHost(Session.java:797) {quote} If I add the entry after obtaining the ssh-rsa using the command """"ssh-keyscan localhost"""" it throws: {quote} org.mule.runtime.core.api.MuleRuntimeException: Error during login to alejandro@localhost. 2016-08-31 03:53:24,863 [[fb407c40-6f46-11e6-8f29-acbc32a683df].sftp-flow-create-directory.worker.01] ERROR org.mule.runtime.core.exception.DefaultMessagingExceptionStrategy - ******************************************************************************** Message : org.mule.runtime.core.api.MuleRuntimeException: Error during login to alejandro@localhost Payload : null Payload Type : null Element : org.mule.runtime.module.extension.internal.runtime.DefaultExecutionMediator$OperationRetryCallBack@1f147640 @ app -------------------------------------------------------------------------------- Root Exception stack trace: java.lang.ArrayIndexOutOfBoundsException: 222 at com.jcraft.jsch.Util.fromBase64(Util.java:52) at com.jcraft.jsch.KnownHosts.setKnownHosts(KnownHosts.java:218) at com.jcraft.jsch.KnownHosts.setKnownHosts(KnownHosts.java:54) at com.jcraft.jsch.JSch.setKnownHosts(JSch.java:317) at org.mule.extension.ftp.internal.sftp.connection.SftpClient.configureHostChecking(SftpClient.java:187) at org.mule.extension.ftp.internal.sftp.connection.SftpClient.configureSession(SftpClient.java:170) {quote}""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10406","08/31/2016 08:09:34",5,"FTP Extension: In SFTP the create directory doesn't work, it says that the path to create doesn't exist. ""FTP Extension: In SFTP the create directory doesn't work, it says that the path to create doesn't exist. Steps to reproduce: * Start SFTP server in Mac * try to create a directory""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10408","08/31/2016 14:43:34",5,"Define a way to hook to the default EL in Mule ""Define a way to hook to the default EL in Mule""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10409","08/31/2016 14:44:54",8,"Move enricher to compatibility ""Define the UX for enricher that uses MEL. We need to review how now having the enricher affects us considering the 3.x use cases.""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10412","08/31/2016 15:03:20",0,"Define how to do beans lookup ""Define how to do beans lookup. One way this was done was using the app global which exposed the registry.""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10413","08/31/2016 15:05:43",8,"Spike: Define how to define EL functions from modules ""Define how to define EL functions from modules""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10414","08/31/2016 15:06:29",0,"Define API to do type inference for bindings (functions and variables) ""Define API to do type inference for bindings (functions and variables) ""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10421","09/01/2016 14:15:35",8,"Define and implement how to deal with composite exceptions ""We need to provide a mechanism for components that execute many routes to provide a composite exception with the different errors that occur in each route and make that accessible by the user. (i.e.: scatter-gather). This also includes supporting that in mule core components ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10422","09/01/2016 14:19:36",5,"Add mechanism to provide an error message from failing components ""This task is to allow components in mule configuration to provide a MuleMessage with information related to the error like in http when there's an http status code validation but the response of the request must still be available to be used by the user.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10424","09/01/2016 14:23:01",8,"Define bindings to use in Mule 4 from the event ""Define bindings to use in Mule 4""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10425","09/01/2016 14:23:32",5,"Review new operator won't be supported in EL ""Review new won't be supported in EL. Need to evaluate the impact and define how to approach the fact that 'new' won't be accepted in the EL.""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10426","09/01/2016 14:23:59",8,"Redefine DW current components ""- Redefine DW current components - set-payload vs dw:transform - Make DW components as part of core namespace.""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10428","09/01/2016 14:25:21",8,"Allow transform processor to load the script from a file ""Since a dw script can be quite large, it would be ideal to load them from a file.""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10430","09/01/2016 14:31:18",8,"Spike for moving operation execution from ExtAPI to core ""The idea is to see what is the impact of moving the code to execute operation from extensions API to the core so we can reuse it for every operation that executes like a function.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10434","09/01/2016 15:08:38",3,"Compilation fails for an extension with operations shared with different config ""I had an extension that have 2 configs, and they share the same operation, but after the merge of the MULE-10220 it stopped compiling. The extension: Operation: Expected: The compilation should not fail, and when it fails, it should not fail with the execption it is currently failing. The error should specify the components that generated the conflict"""," import org.mule.runtime.extension.api.annotation.Configurations; import org.mule.runtime.extension.api.annotation.Extension; /** * Extension javadoc description */ @Extension(name = """"Basic"""", description = """"Basic Connector Description"""") @Configurations({BasicExtensionConfig.class, SourceAndOperationsBasicExtensionConfig.class}) public class BasicExtension { } public class BasicOperations { /** * Operation With String description * * @param param String param description */ public String operationWithString(String param) { return param; } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10435","09/01/2016 16:20:07",5,"Add a way to shared libs on the isolated tests ""Applications can share libraries with artifact plugins deployed as part of the app. The isoalted test runner must support this feature so we can use libraries that are not part of the extensions (like DB drivers) on our tests""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10436","09/01/2016 16:24:04",1,"Improve logging to help to resolve classloading issues ""FineGrainControlClassLoader should log what classes are being loaded, what lookup policy is being used and what classloader is finally used to load the class.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10440","09/01/2016 16:52:15",8,"Define plugin versions and improve plugin dependencies ""Current version defines plugin dependencies by name. As there will be multiple versions of a given artifact, the name is not enough. Dependencies must be declared in a better way, maybe by defining the maven ID of each artifact. Then the plugin dependencies must be resolved taking in account that there could be multiple versions of a given plugin""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10446","09/01/2016 17:25:46",8,"Spec: Mule 4 Threading model ""Write a spec for the new threading model""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10447","09/01/2016 17:28:44",8,"FTP Extension: Test List operation after the changes and updates needed are done ""The list operation of the FTP Extension needs some changes and updates in it functionality. After they are done we need to test it again. ""","",0,0,0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10449","09/01/2016 18:06:15",5,"Non-Blocking API Spec ""Create/share/review spec for new non-blocking API.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10450","09/01/2016 18:06:55",8,"Introduce new Non-Blocking API ""Introduce new Non-Blocking API""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10451","09/01/2016 18:10:06",8,"Mule 4 Processing Strategy Spec ""Spec""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10452","09/01/2016 22:08:28",3,"Memory leak caused by DefaultDataTypeBuilder's cache ""DefaultDataTypeBuilder contains a cache, used to avoid recreating the same instance DataType instance on each request. This cache is not flushed when the app is undeployed, and because the key references the datatype instance, wich references the classloader, there is a memory leak""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10453","09/01/2016 22:11:50",8,"Memory leak caused by per-app logging ""Per-application logging is causing a memory leak as the logging context maintains a reference to the application classloaders. The issue is easily reproduced on a clean distribution, after default has started redeploy it a couple of times. A profiler will show that there are many MuleappplicationClassLoader instances with strong references when there should be only one. This issue is not reproduced when mule is running using -M-Dmule.simpleLog""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10456","09/02/2016 19:44:37",13,"Exported types are not declared in the extension model ""When an extension declares an Exported type, and that types is not used, or used only as a ParameterGroup are not declared in the extension model of the Extension.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10458","09/03/2016 03:50:35",0,"Define how our socket factories should be enforced ""Right now, the TlsContextFactory claims to be able to generate client and server socket factories when in fact it only exposes a way of obtaining an SSLContext. The problem then is that if we don't exposed TlsConfiguration or our restricted client and server socket factories, users will have no way of obtaining a mule regulated socket factory that guarantees a cipher and protocol configuration that respects the admin setup. We need to define whether we want to add that capabilities to the TlsContextFactory or refactor our TLS approach to allow another way of providing those socket factories.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10459","09/03/2016 06:02:11",1,"FTP Extension: SFTP Rename operation doesn't work ""When trying to do a Rename using SFTP it throws an exception """"Exception occurred while trying to change working directory to null."""" *Steps to reproduce:* * Start the SFTP server in mac and check it is running * Try to rename a file/folder with a flow like this: {quote} DEBUG 2016-09-03 01:57:45,268 [[65af1b30-7191-11e6-93b2-0a0027000000].flow-sftp-rename-folder-and-file.worker.01] org.mule.extension.ftp.internal.sftp.connection.SftpClient: Attempting to cwd to: null {quote} {quote} ******************************************************************************** Message : Exception occurred while trying to change working directory to null. Payload : null Payload Type : null Element : /flow-sftp-rename-folder-and-file/processors/0 @ 65af1b30-7191-11e6-93b2-0a0027000000 -------------------------------------------------------------------------------- Root Exception stack trace: java.lang.NullPointerException at com.jcraft.jsch.ChannelSftp.remoteAbsolutePath(ChannelSftp.java:2916) at com.jcraft.jsch.ChannelSftp.cd(ChannelSftp.java:339) at org.mule.extension.ftp.internal.sftp.connection.SftpClient.changeWorkingDirectory(SftpClient.java:100) at org.mule.extension.ftp.internal.sftp.connection.SftpFileSystem.changeToBaseDir(SftpFileSystem.java:98) at org.mule.runtime.module.extension.file.api.StandardFileSystemOperations.rename(StandardFileSystemOperations.java:310) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) {quote}"""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10460","09/03/2016 06:17:55",1,"FTP Extension: SFTP delete log appears twice when a folder is removed ""When you add the in the log4j2.conf the DEBUG level to the FTP package it shows twice the line of folder deleted in SFTP. In the case of the delete of a file it only shows it once as expected. In the logs you will see both behaviours: {quote} DEBUG 2016-09-03 01:54:50,249 [[65af1b30-7191-11e6-93b2-0a0027000000].flow-sftp-delete-folder-and-file.worker.01] org.mule.extension.ftp.internal.sftp.connection.SftpClient: Attempting to cwd to: /Users/alejandro DEBUG 2016-09-03 01:54:50,250 [[65af1b30-7191-11e6-93b2-0a0027000000].flow-sftp-delete-folder-and-file.worker.01] org.mule.extension.ftp.internal.sftp.command.SftpDeleteCommand: Preparing to delete file '/Users/alejandro/output/hello-world.txt' DEBUG 2016-09-03 01:54:50,251 [[65af1b30-7191-11e6-93b2-0a0027000000].flow-sftp-delete-folder-and-file.worker.01] org.mule.extension.ftp.internal.sftp.command.SftpDeleteCommand: Successfully deleted '/Users/alejandro/output/hello-world.txt' DEBUG 2016-09-03 01:54:50,251 [[65af1b30-7191-11e6-93b2-0a0027000000].flow-sftp-delete-folder-and-file.worker.01] org.mule.extension.ftp.internal.sftp.connection.SftpClient: Attempting to cwd to: /Users/alejandro DEBUG 2016-09-03 01:54:50,252 [[65af1b30-7191-11e6-93b2-0a0027000000].flow-sftp-delete-folder-and-file.worker.01] org.mule.extension.ftp.internal.sftp.command.SftpDeleteCommand: Preparing to delete directory '/Users/alejandro/output' DEBUG 2016-09-03 01:54:50,254 [[65af1b30-7191-11e6-93b2-0a0027000000].flow-sftp-delete-folder-and-file.worker.01] org.mule.extension.ftp.internal.sftp.command.SftpDeleteCommand: Successfully deleted '/Users/alejandro/output' DEBUG 2016-09-03 01:54:50,254 [[65af1b30-7191-11e6-93b2-0a0027000000].flow-sftp-delete-folder-and-file.worker.01] org.mule.extension.ftp.internal.sftp.command.SftpDeleteCommand: Successfully deleted '/Users/alejandro/output' {quote}""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10461","09/03/2016 06:46:35",1,"FTP Extension: In the create dir operation when the Directory already exist it doesn't mention the complete path, just the directory name ""For example for this config: It only displays """"Directory 'input' already exists."""" in place of *""""Directory /Users/alejandro/ftp-test/input/ already exists.""""* or *""""Directory 'input' already exists. in /Users/alejandro/ftp-test/""""*"""," ... ... ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10466","09/05/2016 14:12:39",0,"Update javax transport version to 1.2 ""Upgrade the library""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10468","09/05/2016 20:07:39",5,"Define DslSyntaxResolver behaviour when type is not global ""Define how the resolve(MetadataType type) method should behave when the type doesn't allow global definitions and is not wrapped. Should it fail? Should it return an empty element Name?""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10470","09/05/2016 22:56:15",3,"Upgrade javax.mail to latest version ""E-mail extension is being built using the 1.4.7 version of the javax.mail dependency (March 2013). We should upgrade to the latest version (1.5.6) released in August 2016. Available at: https://mvnrepository.com/artifact/javax.mail/javax.mail-api Also, the dependency is marked as provided, so the version shipped with the distribution is being used. Consider shipping this library with the extension plugin.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10473","09/06/2016 15:56:29",5,"Review Email operations that return mule messages. ""We dont want to expose the Message in the operations of extensions, so we should replace this with the OperationResult concept""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10474","09/06/2016 16:02:55",5,"Review email operations that return or receive a multipart mule message. ""Review the experience of the email operations that return or receive a multipart mule message, describe the final decisions in the Email Connector spec. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10475","09/06/2016 16:23:36",8,"DSLSyntaxResolver crashes when resolving metadata types if the class is not in the classpath ""When loading the extension model and generating the XML definition in studio using as input a metadata type, the DSLSyntaxResolver crashes because it is looking for classes in the classpath. The DSL should not depend on classes being in the classpath. This was working before.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10476","09/06/2016 16:31:12",2,"Provide a way to specify mule plugin dependencies of an extension ""When packaging an extension we should include in the plugin.properties file an entry """"plugin.dependencies' that specifies the list of plugins that the extension is dependant on. We should see if this could be auto-discovered or specified somewhere.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10478","09/06/2016 16:37:40",8,"Pojos should not have top level element support by default ""The current default is to add top level element support for all instantiable types on the XML dsl. This is fine for the code connectors but is problematic for cloud ones. Plus, not all core connectors need that either. Additionally, the tooling becomes cluttered by an excess of top level elements, most of which are hardly needed. Default should change to false, and this should explicitly enabled through a XmlHints annotation""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10479","09/06/2016 18:02:38",5,"Description is not populated in the extension model when the operation is declared at the Configuration instead of the Extension ""If you add operation at an @Configuration class, all the operations and parameters descriptions are empty Operations Generated JSON for the operations: The description should be populated. For configless operations, all the descriptions are populated correctly"""," @Configuration(name = """"config"""", description = """"Config Description"""") @Operations({ BasicOperations.class }) public class BasicExtensionConfig { /** * Config Parameter description */ @Parameter private String configParameter; } public class BasicOperations { /** * Operation With String description * * @param config The extension config * @param param String param description */ public String operationWithString(@UseConfig BasicExtensionConfig config, String param) { return param; } } { """"operationWithString"""": { """"output"""": { """"type"""": { """"format"""": """"java"""", """"type"""": """"String"""", """"annotations"""": { """"typeId"""": """"java.lang.String"""" } }, """"hasDynamicType"""": false, """"description"""": """""""", """"modelProperties"""": {} }, """"outputAttributes"""": { """"type"""": { """"format"""": """"java"""", """"type"""": """"Null"""" }, """"hasDynamicType"""": false, """"description"""": """""""", """"modelProperties"""": {} }, """"parameterModels"""": [ { """"type"""": { """"format"""": """"java"""", """"type"""": """"String"""", """"annotations"""": { """"typeId"""": """"java.lang.String"""" } }, """"hasDynamicType"""": false, """"required"""": true, """"expressionSupport"""": """"SUPPORTED"""", """"name"""": """"param"""", """"description"""": """""""", """"modelProperties"""": { """"layout"""": { """"password"""": false, """"text"""": false, """"order"""": -1, """"groupName"""": """""""", """"tabName"""": """"General"""" } } } ], """"name"""": """"operationWithString"""", """"description"""": """""""", """"modelProperties"""": {} } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10480","09/06/2016 18:40:33",5,"Move deployment code to its own module ""Move deployment code to its own module""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10481","09/06/2016 21:08:21",3,"Email: Add pagination support for the list operation. ""Now the SDK has pagination support, and we should make the list operation paginable. Remember to modify Email's spec to reflect this change.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10482","09/06/2016 21:40:58",5,"Replace Geronimo dependencies with javax ""We should consider upgrading all spec libraries to the latest version of the javax flavor and remove Geronimo packages from the distribution. - J2EE - JMS - EJB - JAX-RPC - Servlet""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10484","09/07/2016 19:01:44",0,"ArtifactClassLoaderRunner - Improve exportPluginClasses to only export classes of the plugin that contains those classes ""While migrating extensions there was this need for exporting classes from the plugin/extension that are not exposed. The tests need to access them for testing the features but they are not supposed to be exported as part of the API. MULE-10144 implements a way to allow exporting particular classes for plugins/extensions but these set of classes is exported by all the plugins/extensions due to there is no way to match which plugin/extensions contains those classes. Find a way to improve this. h5. Proposed solution It should only be allowed to export classes for the rootArtifact if it is a plugin, therefore you would only be able to export classes when doing functional tests from the same plugin that is exporting those classes""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10485","09/07/2016 21:31:17",2,"ArtifactClassLoaderRunner - Add support for reading the maven-shade-plugin configuration using Xpp3 Maven API ""While reading if the pom has maven-shade-plugin during the Workspace findArtifact resolution it would be nice to read the settings of the plugin in order to avoid hardcoding the dependency-reduced-pom.xml file name for reduced pom.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10488","09/08/2016 04:47:06",5,"Allow on-error-* to handle several error types ""Need to support OR operator.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10491","09/08/2016 14:21:03",5,"Add missing UI TypeAnnotations to improve the POJOs support ""*Add missing UI TypeAnnotations to improve the POJOs support* * Nowadays the ExtensionModel have several {{ModelProperty}} that contribute on how to render a UI: ** *LayoutModelProperty* *** Whether is a password *** Whether is a text *** The order of the element *** Group *** Tab ** *DisplayModelProperty* *** DisplayName *** Summary Some of these information there is no way to contribute to a {{MetadataType}} because a {{TypeAnnotation}} is missing and in some other cases the {{MetadataType}} is not contributed correctly.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10495","09/08/2016 16:21:31",5,"Improve test infrastructure for creating Events/Messages ""Review how messages/events are created. Migrate to use the builder.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10497","09/08/2016 16:23:37",8,"Microbenchmark event/message creation/copying/usage ""Update and run benchmarks.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10498","09/08/2016 16:32:30",2,"Review exported extension plugins when packaging. ""We should remove the capability to specify exported plugins in the property and move to what the was defined to solve the classloading and testing issues. Also add tests for this feature. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10500","09/08/2016 18:14:28",0,"SoapFaultException must keep the original SoapFault ""When building a SoapFaultException, certain attributes of the original SoapFault are being kept. Instead, reference to the SoapFault itself should be kept.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10501","09/08/2016 18:42:44",8,"ArtifactClassLoaderRunner - Add unit tests for Aether classification process ""In order to support multiple versions for different artifacts (plugin/container) the classification process for the class loader isolated runner has been changed to use Eclipse Aether (Maven resolution API). This code needs to be tested in order to avoid having to run all the tests that use the runner to check if a change there breaks something else.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10502","09/08/2016 19:08:46",1,"Custom URL path in JMX management module is not working ""Since the host attribute was deprecated, JMX urls with a custom path are not being correctly parsed, and the default */server* is always used as the path.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10503","09/08/2016 21:35:36",1,"DSLSyntaxElement element name is not populated if the paramter has the @Text annotation ""For Database and Email extensions, some parameter are annotated with the @Text annotation. {code} public FooPojo { @Text @Parameter private String superField; } {code} When resolving the DSLElementSyntax using its metadata type, and getting the DSLElementSyntax for the field annotated with @Text, the resulting DSLElementSyntax has an empty element name. Without a name, we cannot persist it in the XML. {code:java} String fieldName = """"superField""""; DslElementSyntax resultFromMetadata = getSyntaxResolver().resolve(parameterModel.getType()); //This is a FooPojo DslElementSyntax metadataFieldDsl = getChildFieldDsl(fieldName ,resultFromMetadata); assertElementName(fieldName ,metadataFieldDsl); //This fails {code}"""," public FooPojo { @Text @Parameter private String superField; } String fieldName = """"superField""""; DslElementSyntax resultFromMetadata = getSyntaxResolver().resolve(parameterModel.getType()); //This is a FooPojo DslElementSyntax metadataFieldDsl = getChildFieldDsl(fieldName ,resultFromMetadata); assertElementName(fieldName ,metadataFieldDsl); //This fails ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10505","09/08/2016 22:11:28",8,"Make mule-module-file-common an artifact plugin ""File common modules is currently distributed in the container an exposed in the API. File, FTP and FTPS extensions depend on that module. As now plugins can depend on other plugins, file common must be removed from the container and converted in to an artifact plugin.""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10506","09/08/2016 22:34:53",3,"File workingDir attribute should be at the file:connection level ""The file connector has the workingDir at the configuration level. This means that the connection provider of file is not considering it when doing connection testing. That should be used since it may be that the configured folder does not exists.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10507","09/08/2016 22:40:29",0,"OAuth Authorization in HTTP Requester redirection URL only works on localhost ""The redirectionUrl needs to be something ESB can listen on as the callback(generated dynamic flow) will be using it. As a result, in CloudHub, this can only be using host: 0.0.0.0 However, when OAuth provider authenticates the login and send an HTTP response with a 'location' header of """"http://0.0.0.0:8081/callback"""", the browser is not able to corelate it to the one exposed by the application, which should be http://appName.cloudhub.io/callback. We need an extra attribute, say 'ExternalRedirectionURL', to send to the remote OAuth provider, so that, when the OAuth provider returns the redirect, it's going to the ExternalRedirectionURL, which eventually will land on the redirectionURL where the ESB runtime is listening on.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10509","09/09/2016 15:52:09",2,"Migrate HTTP extension to depend on Sockets extension as plugin dependency ""As MULE-9867 added support for extension/plugins dependencies HTTP extension has to be migrated to use this new approach.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10513","09/09/2016 16:16:23",1,"ArtifactClassLoaderRunner - Check how DSL metadata is generated for extensions ""org.mule.functional.api.classloading.isolation.ExtensionPluginMetadataGenerator is generating DSL metadata at the end when all the extensions were registered and its manifest created. These means that spring stuff and xsds are created at that point to only one folder, actually it is added this URL to every plugin. Check if this (having the whole metadata on each plugin resources) would have a problem with Extensions Runtime.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10514","09/09/2016 16:25:12",8,"ArtifactClassLoaderRunner - Refactor to encapsulate Aether API inside the runner implementation ""The following packages had to be exported as part of the migration to Aether, refactor the code to avoid exposing this as part of the API: """," org.eclipse.aether.resolution org.eclipse.aether.version org.eclipse.aether.artifact org.eclipse.aether.transfer org.eclipse.aether org.eclipse.aether.installation org.eclipse.aether.graph org.eclipse.aether.collection org.eclipse.aether.deployment org.eclipse.aether.repository org.eclipse.aether.metadata ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10516","09/09/2016 17:35:58",5,"Declare config-ref attribute as a reference in the ComponentBuildingDefinition ""The SDK must declare the attributes pointing to pojos config-ref attribute as a reference when defining the component building definition of the operations. Mule needs to know about the reference parameters in the config in order to clearly know the dependencies between different components in the configurations. This let us create an isolated component together with it dependencies.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10517","09/09/2016 18:01:49",2,"Add information on the EventContext about the origin of its events ""Notifications should contain this information. This will allow the system receiving this notifications to identify the source of those events. Currently, it is containing the name of the xml element for the source or the url of the inbound endpoint for compatibility module. Some more data that would make sense: * name of the receiving flow construct * name of the module and operation of the connector receiving the event""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10519","09/09/2016 18:16:45",8,"Move all exception classes away from MessagingException ""We need to hide MessagingException as much as possible and expose the exceptions that might make it to the user. This will mean no more """"causedBy"""" and restoring the behaviour in MessageVariableResolverFactory when handling """"exception"""" to stop wrapping it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10520","09/09/2016 18:18:50",2,"Add test cases for routers and error handling ""We need to make sure that when a router fails it throws RoutingExceptions (ROUTING error type) but when an inner route fails the original exception is available.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10523","09/11/2016 17:23:55",2,"Exported elements are not in the list of types in the extension-model.json ""None of the exported types is populated in the types field of the extension-model.json Check the sockets extension org.mule.modules:mule-module-sockets for example. TcpClientSocketProperties should be in the list of types, but it is not.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10528","09/12/2016 16:40:17",3,"Do not allow UNKNOWN to be handle as error type in the config ""We should only use the UNKNOWN error type internally and not let the user use it in the config. This is because we will probably have many UNKNOWN error types that we would be moving to specific error types in minor versions. If we let the user catch UNKNOWN, then if we change those we would be breaking backwards compatibility. In such case the users can use the ANY error type.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10529","09/12/2016 21:30:22",5,"Changes in metadata serialization for improved agent error handling ""Change metadata serialization API""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10530","09/12/2016 22:38:34",3,"Rename and make optional the ""key"" attribute of HTTP request operation ""The """"key"""" attribute is necessary for metadata resolution since we are returning an Object, however it should A) be named something like """"outputType"""" and B) be optional using the ANY type as default. Once MULE-10377 is done, this can be addressed.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10531","09/13/2016 04:06:50",1,"Migrate HTTP test that needs to access plugin classes from IT test to Functional Test Case in HTTP Extension ""MULE-9702 added test for HTTP extension, as part of isolation runner modifications classes cannot be exported for plugins except if the rootArtifact is the plugin that those classes belong to. Currently only two tests would need to be moved to HTTP extension test folder: org.mule.test.module.http.functional.requester.HttpRequestFunctionalTestCase org.mule.test.module.http.functional.requester.HttpRequestProxyConfigTestCase ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10532","09/13/2016 05:33:29",2,"ArtifactClassLoaderRunner - Add support for sharing libraries/modules between plugins ""MULE-9867 require to be supported from ArtifactClassLoaderRunner""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10533","09/13/2016 12:56:36",2,"When using a list of maps, the map parameter items xml tag is not recognized by the parser ""If an extension uses List> parameters, the parser fails to load the inline definition of the parameter with the following error: {code} org.mule.runtime.core.api.lifecycle.InitialisationException: Configuration problem: The element 'map-parameter' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/map-list present on the classpath? Offending resource: URL [file:/Users/pablocabrera/dev/mule-tooling-mock-connector/extension-with-map-list/target/test-classes/mule-config.xml] Caused by: org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: The element 'map-parameter' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/map-list present on the classpath? {code} This is the operations definition {code:java} public class BasicOperations { public String operationWithMap(@UseConfig BasicExtensionConfig config, List> mapParameters) { return null; } } {code} The mule app: {code:xml} {code} The XSD has all the definitions maching this signature. Expected: The app should be able to load the XML"""," org.mule.runtime.core.api.lifecycle.InitialisationException: Configuration problem: The element 'map-parameter' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/map-list present on the classpath? Offending resource: URL [file:/Users/pablocabrera/dev/mule-tooling-mock-connector/extension-with-map-list/target/test-classes/mule-config.xml] Caused by: org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: The element 'map-parameter' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/map-list present on the classpath? public class BasicOperations { public String operationWithMap(@UseConfig BasicExtensionConfig config, List> mapParameters) { return null; } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10535","09/13/2016 14:28:48",5,"Connections should be validated at start time ""When the application starts, all connection providers should get a connection, validate it and release it. If any of those fail, the application should not start. User should be able to provide a to prevent the application from failing""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10536","09/13/2016 14:36:11",5,"Content parameter should not support child element declaration ""When consuming an API that has dynamic entities, like salesforce, the most common way to do it is to use a map to represent the entity: In this scenario, the child element name should not be pluralized, and when configuring it as a child, the name of the element should be *dynamic-object*, and not *dynamic-objects*"""," public Map createEntity(@Connection MetadataConnection connection, @MetadataKeyId String type, @Optional @Content Map dynamicObject); ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10537","09/13/2016 17:24:37",0,"Avoid wrapping exceptions to ME in CXF ""Right now, the CxfOutboundMessageProcessor is wrapping the exceptions that occur when calling the client processor in a MessagingException. This allows the interceptor that catches that exception to use the latest event which went through the client processor. We need to figure out a way to not use a MessagingException and still get the same behaviour.""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10538","09/13/2016 19:39:00",3,"Email: Remove the EmailIdConsumerExecutor. ""The EmailIdConsumerExecutor class is the responsible for looking in the incoming message if there are one or more emailIds to accept and perform some operation, as part as mule4 we want to avoid falling back to the incoming messages and be explicit when parameters are needed ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10542","09/14/2016 19:39:49",2,"Fix ToolingService class API ""The ToolingService class expose two methods that are not related at all. While we won't to keep the ToolingService as an agregator of the funcionality that can be used for tooling, we should have a clear API. Probably move the createApplication method to another class.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10543","09/14/2016 20:56:58",8,"Implement the SchedulerService ""Define the threading profiles for the container pools. Hook up the ThreadingService with the service infrastructure.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10545","09/14/2016 20:58:37",8,"Change http selectors/workers to use a connector pool from the service ""This depends on the final definition of http module vs extension vs service.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10547","09/14/2016 21:03:20",2,"Expose the type of processing the current thread is performing ""This is needed by the ProcessingStrategies to make scheduling decisions""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10548","09/14/2016 21:04:02",8,"Cleanup WorkManager and WorkListener ""Remove unneeded and unused code. Cleanup the MuleContext.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10553","09/14/2016 22:07:55",2,"Cleanup asynchronousProcessingStrategy vs threadingProfileType vs asynchronousThreadingProfileType overlap in schema ""Clenup the schema definition""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10554","09/14/2016 23:40:43",8,"Separate artifact construction from artifact deployment ""In order to reuse classloader construction on the isolated test runner, we can't depend on deployment module form the runner module, as that creates a dependency cycle. We must extract artifact classloaders contruction (and related concepts) to a different module. This new module must be related to artifacts and classloaders construction and the deployment module must manage only the deployment part of those artifacts ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10555","09/15/2016 12:18:06",1,"ArtifactClassLoaderRunner - Create on the fly the extension manifest for testing ""JUnits on test-runner have a hard-coded extension-manifest.xml for testing, find out if possible to generate this on the fly.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10557","09/15/2016 14:55:16",8,"Change OAuth callback API to support external url and avoid confusion ""We have the redirectUrl attribute in oauth2:authorization-code-grant-type for the local callback. It's somehow misleading because it's a local callback address to open a listener. It would be better to rename it in addition to adding the external url, and possibly supporting a listener configuration.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10558","09/15/2016 15:17:02",5,"Definition Parsers doesn't load an object if the parameter name is the same of their base type ""*Definition Parsers doesn't load an object if the parameter name is the same of their base type* *Heisenberg case:* We have the following SubtypeMapping: {code}@SubTypeMapping(baseType = Weapon.class, subTypes = {Ricin.class}){code} And then the following operation: {code} public Map processWeapon(Weapon weapon) { ... }{code} And then in a Mule app: {code:xml} {code} When the definition parser try to load the object, treats {{}} as the abstract base type of the subtype mapping instead of the wrapper of the concrete type. This explodes with the following stact trace {code}org.mule.runtime.core.api.lifecycle.InitialisationException: Error creating bean with name 'processWeaponAsChildElement': Cannot create inner bean '(inner bean)#31eef343' of type [org.mule.runtime.module.extension.internal.config.dsl.operation.OperationMessageProcessorObjectFactory$$EnhancerByCGLIB$$99e38baf_42] while setting bean property 'messageProcessors' with key [1]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#31eef343': Cannot create inner bean '(inner bean)#56a73b6b' of type [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22] while setting bean property 'parameters' with key [<>]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#56a73b6b': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22]: Constructor threw exception; nested exception is org.mule.runtime.core.api.MuleRuntimeException: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:93) at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:49) at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:45) at org.mule.runtime.core.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:128) at org.mule.runtime.core.lifecycle.RegistryBrokerLifecycleManager.fireInitialisePhase(RegistryBrokerLifecycleManager.java:54) at org.mule.runtime.core.registry.AbstractRegistryBroker.initialise(AbstractRegistryBroker.java:45) at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:123) at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:77) at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:74) at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.invokePhase(MuleContextLifecycleManager.java:62) at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:56) at org.mule.runtime.core.DefaultMuleContext.initialise(DefaultMuleContext.java:299) at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:194) at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:77) at org.mule.tck.junit4.AbstractMuleContextTestCase.createMuleContext(AbstractMuleContextTestCase.java:203) at org.mule.tck.junit4.AbstractMuleContextTestCase.setUpMuleContext(AbstractMuleContextTestCase.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74) Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'processWeaponAsChildElement': Cannot create inner bean '(inner bean)#31eef343' of type [org.mule.runtime.module.extension.internal.config.dsl.operation.OperationMessageProcessorObjectFactory$$EnhancerByCGLIB$$99e38baf_42] while setting bean property 'messageProcessors' with key [1]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#31eef343': Cannot create inner bean '(inner bean)#56a73b6b' of type [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22] while setting bean property 'parameters' with key [<>]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#56a73b6b': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22]: Constructor threw exception; nested exception is org.mule.runtime.core.api.MuleRuntimeException: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:313) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:129) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:382) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:157) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1475) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1220) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:537) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:303) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:299) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:728) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:762) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:480) at org.mule.runtime.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:112) at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:89) ... 27 more Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#31eef343': Cannot create inner bean '(inner bean)#56a73b6b' of type [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22] while setting bean property 'parameters' with key [<>]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#56a73b6b': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22]: Constructor threw exception; nested exception is org.mule.runtime.core.api.MuleRuntimeException: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:313) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:129) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedMap(BeanDefinitionValueResolver.java:407) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:165) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1475) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1220) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:537) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:299) ... 43 more Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#56a73b6b': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22]: Constructor threw exception; nested exception is org.mule.runtime.core.api.MuleRuntimeException: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:275) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1137) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1040) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:504) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:299) ... 51 more Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22]: Constructor threw exception; nested exception is org.mule.runtime.core.api.MuleRuntimeException: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:163) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:122) at org.mule.runtime.config.spring.util.LaxInstantiationStrategyWrapper.lambda$instantiate$84(LaxInstantiationStrategyWrapper.java:66) at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:143) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:995) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:961) at org.mule.runtime.config.spring.util.LaxInstantiationStrategyWrapper.instantiate(LaxInstantiationStrategyWrapper.java:64) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:267) ... 56 more Caused by: org.mule.runtime.core.api.MuleRuntimeException: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:946) at org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory.(TopLevelParameterObjectFactory.java:46) at org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22.() at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:147) ... 63 more Caused by: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.mule.runtime.module.extension.internal.util.IntrospectionUtils.checkInstantiable(IntrospectionUtils.java:354) at org.mule.runtime.module.extension.internal.util.IntrospectionUtils.checkInstantiable(IntrospectionUtils.java:349) at org.mule.runtime.module.extension.internal.runtime.DefaultObjectBuilder.(DefaultObjectBuilder.java:30) at org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory.lambda$new$51(TopLevelParameterObjectFactory.java:48) at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$18(ClassUtils.java:942) at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:143) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:995) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:961) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:941) ... 70 more {code}""","@SubTypeMapping(baseType = Weapon.class, subTypes = {Ricin.class}) public Map processWeapon(Weapon weapon) { ... } org.mule.runtime.core.api.lifecycle.InitialisationException: Error creating bean with name 'processWeaponAsChildElement': Cannot create inner bean '(inner bean)#31eef343' of type [org.mule.runtime.module.extension.internal.config.dsl.operation.OperationMessageProcessorObjectFactory$$EnhancerByCGLIB$$99e38baf_42] while setting bean property 'messageProcessors' with key [1]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#31eef343': Cannot create inner bean '(inner bean)#56a73b6b' of type [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22] while setting bean property 'parameters' with key [<>]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#56a73b6b': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22]: Constructor threw exception; nested exception is org.mule.runtime.core.api.MuleRuntimeException: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:93) at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:49) at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:45) at org.mule.runtime.core.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:128) at org.mule.runtime.core.lifecycle.RegistryBrokerLifecycleManager.fireInitialisePhase(RegistryBrokerLifecycleManager.java:54) at org.mule.runtime.core.registry.AbstractRegistryBroker.initialise(AbstractRegistryBroker.java:45) at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:123) at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:77) at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:74) at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.invokePhase(MuleContextLifecycleManager.java:62) at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:56) at org.mule.runtime.core.DefaultMuleContext.initialise(DefaultMuleContext.java:299) at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:194) at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:77) at org.mule.tck.junit4.AbstractMuleContextTestCase.createMuleContext(AbstractMuleContextTestCase.java:203) at org.mule.tck.junit4.AbstractMuleContextTestCase.setUpMuleContext(AbstractMuleContextTestCase.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74) Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'processWeaponAsChildElement': Cannot create inner bean '(inner bean)#31eef343' of type [org.mule.runtime.module.extension.internal.config.dsl.operation.OperationMessageProcessorObjectFactory$$EnhancerByCGLIB$$99e38baf_42] while setting bean property 'messageProcessors' with key [1]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#31eef343': Cannot create inner bean '(inner bean)#56a73b6b' of type [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22] while setting bean property 'parameters' with key [<>]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#56a73b6b': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22]: Constructor threw exception; nested exception is org.mule.runtime.core.api.MuleRuntimeException: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:313) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:129) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:382) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:157) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1475) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1220) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:537) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:303) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:299) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:728) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:762) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:480) at org.mule.runtime.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:112) at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:89) ... 27 more Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#31eef343': Cannot create inner bean '(inner bean)#56a73b6b' of type [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22] while setting bean property 'parameters' with key [<>]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#56a73b6b': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22]: Constructor threw exception; nested exception is org.mule.runtime.core.api.MuleRuntimeException: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:313) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:129) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedMap(BeanDefinitionValueResolver.java:407) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:165) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1475) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1220) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:537) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:299) ... 43 more Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#56a73b6b': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22]: Constructor threw exception; nested exception is org.mule.runtime.core.api.MuleRuntimeException: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:275) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1137) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1040) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:504) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:299) ... 51 more Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22]: Constructor threw exception; nested exception is org.mule.runtime.core.api.MuleRuntimeException: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:163) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:122) at org.mule.runtime.config.spring.util.LaxInstantiationStrategyWrapper.lambda$instantiate$84(LaxInstantiationStrategyWrapper.java:66) at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:143) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:995) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:961) at org.mule.runtime.config.spring.util.LaxInstantiationStrategyWrapper.instantiate(LaxInstantiationStrategyWrapper.java:64) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:267) ... 56 more Caused by: org.mule.runtime.core.api.MuleRuntimeException: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:946) at org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory.(TopLevelParameterObjectFactory.java:46) at org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory$$EnhancerByCGLIB$$add4e145_22.() at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:147) ... 63 more Caused by: java.lang.IllegalArgumentException: Class interface org.mule.test.heisenberg.extension.model.Weapon cannot be instantiated. at org.mule.runtime.module.extension.internal.util.IntrospectionUtils.checkInstantiable(IntrospectionUtils.java:354) at org.mule.runtime.module.extension.internal.util.IntrospectionUtils.checkInstantiable(IntrospectionUtils.java:349) at org.mule.runtime.module.extension.internal.runtime.DefaultObjectBuilder.(DefaultObjectBuilder.java:30) at org.mule.runtime.module.extension.internal.config.dsl.parameter.TopLevelParameterObjectFactory.lambda$new$51(TopLevelParameterObjectFactory.java:48) at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$18(ClassUtils.java:942) at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:143) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:995) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:961) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:941) ... 70 more ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10560","09/15/2016 15:21:22",8,"The log4j2.xml confs in the apps are ignored in Mule 4. ""For example in the case of HTTP you can add this line: You spect to see the HTTP Extensions DEBUG logs and also the Grizzly logs of the requests. But right now this is not working. In the case of FTP the same is happening."""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10561","09/15/2016 15:23:02",5,"Expose rest service to do connection testing over an application ""Expose rest service to do connection testing over an application / domain""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10569","09/15/2016 17:36:06",13,"Support non-blocking operations in Ext-API ""Support non-blocking API in Ext-API operations""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10570","09/15/2016 18:21:29",8,"Create tooling client to communicate to the mule runtime services ""Create tooling client to communicate to the mule runtime services""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10571","09/15/2016 18:24:41",2,"ArtifactClassLoaderRunner - TestContainerClassLoaderFactory is not using the ModuleDiscoverer with the list of only URLs for Container ""This ends up in a duplicated module error when container loads Mule Modules.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10572","09/15/2016 18:25:56",1,"ArtifactClassLoaderRunner - Compatibility doesn’t install/deploy mule-plugin classifier jar ""It is missed the maven-jar-plugin declaration to add the jar classified.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10574","09/15/2016 21:54:40",3,"Add model validator for parameters that have the same name as then entries of a map ""*Add model validator for parameters that have the same name as then entries of a map* Exist a border case where a parameter is called exactly as the entry of a map, for example: {code} public void processDoor(Door door, @Optional Map doors) {}{code} The SDK when generates the XSD representation of the {{doors}} parameter will generate an element called {{door}} the same name of the parameter {{Door door}}: {code:xml} {code} This will generate a clashing between the resolvers and finally having troubles in runtime. Other cases to validate: * Same name of top level elements and operations Add a validation to prevent this case."""," public void processDoor(Door door, @Optional Map doors) {} ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10575","09/15/2016 22:54:03",0,"Create serializer for the entity metadata ""Create serializer in extension-api to be used by the agent.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10578","09/16/2016 15:48:10",0,"Exception thrown form a Work#run() is ignored by the WorkManager ""When the #run method of a Work throws an exception, it is ignored by the WorkContext. It must be logged at the very least.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10579","09/16/2016 17:53:38",8,"Centralize and APIfy reconnection ""Right now, each time a component throws a connection exception it attempts to reconnect. However, if multiple of those are thrown concurrently by different components, many reconnections will be attempted concurrently. Connections for a given config should happen in a thread safe manner, and many components shouldn't attempt to reconnect at the same time. Also, if a source looses connectivity, it should be stopped until the connection is regained. When it does, the source should be notified of it so that it can resume. This should actually be the case with any component, but sources are particularly tricky so watch out.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10580","09/16/2016 17:59:41",8,"Operation reconnection should be decoupled from config reconnection ""Right now, when an operation fails due to connectivity, it attempts to reconnect using the same retry policy from the config. This is bad mainly because the retry policy for an operation should not allow blocking=""""false"""". Additionally, it is highly likely that the amount of retries, frequency and exhaustion policy that you want for reconnecting at deploy time are not the same ones as when you're executing an operation, since the operation will block while reconnecting. We should define a way to configure these two reconnection moments separately.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10582","09/16/2016 20:35:40",8,"NPE when an operation throws exception inside a foreach ""When an extension operation is used inside a foreach and this one throws an exception the foreach component throws an NPE. Stack Trace is: """," Caused by: java.lang.NullPointerException at org.mule.runtime.core.routing.Foreach.doProcess(Foreach.java:119) at org.mule.runtime.core.routing.Foreach.process(Foreach.java:96) at org.mule.runtime.core.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:39) at org.mule.runtime.core.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:96) at org.mule.runtime.core.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.runtime.core.processor.BlockingProcessorExecutor.executeNext(BlockingProcessorExecutor.java:77) at org.mule.runtime.core.processor.BlockingProcessorExecutor.execute(BlockingProcessorExecutor.java:51) ",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10583","09/16/2016 21:46:21",5,"Review MetadataService serialization API ""MetadataService interface is exposing more behaviour than it should be. We need to handle the serialization for the different type of MetadataResult internally and not expose it in the API. Having only one method for obtaining the serialized string from the MetadataResult would be away to go. """," String keysResultToJson(MetadataResult metadataResult); String metadataDescriptorResultToJson(MetadataResult metadataResult); String typeMetadataDescriptorResultToJson(MetadataResult metadataResult); ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10585","09/16/2016 23:26:34",8,"Make the container ThreadPools configurable ""Based on current definition of ThreadingProfile. Allow functions of the processors and memory for this (available memory makes sense for the max size of the io pool).""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10591","09/19/2016 15:57:24",1,"Email: delete the ""delete"" IMAP protocol operation. ""In the primary structure of the new email connector the delete operation had a lot of sense, but when the operation moved to be only for the IMAP protocol, since POP3 does not support email fetching by id, this is an overkill because IMAP has the capability to mark the emails as deleted and then physically eliminate them from the folder with the expunge operation.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10592","09/19/2016 16:03:43",1,"ArtifactClassLoaderRunner - Improve error message for dependencies not declared as expeted ""When checking for dependencies declared by the rootArtifact an exception could be thrown if they are not with the correct scope. At the same time IDEA sometimes breaks the classpath and points to another target/classes (even compile the classes there) so it would be great to add to these kind of errors the rootArtifact coordinates.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10593","09/19/2016 16:12:46",0,"App with missing config fails to deploy but has status ""created"" ""Even though deployment fails, the application status is """"created"""" so the Anypoint platform proxy interface reports it as """"starting"""" (which of course never finishes).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10594","09/19/2016 16:27:08",5,"Generic types are not being exported in the extension manifest. ""When having an operation that contains a generic type with generic types as output of an operation, the package of those generics is not being added to the exported types in the extension.manifest for example in the email:list operation. In this case the POP3Attributes package is not being exported."""," public List> listPop3( ... ) { ... } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10596","09/19/2016 17:27:43",0,"Release extensions parent POM 4.0-M3 ""Release Extensions Parent POM 4.0-M3""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10600","09/19/2016 20:30:38",1,"Upgrade CXF to latest 2.7.x patch release ""Upgrade to a version that includes the fix for https://issues.apache.org/jira/browse/CXF-7058""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10602","09/20/2016 15:29:29",8,"Parameter Model should include groups and exclusive optionals information ""*Model property for ExclusiveOptionals parameter groups should be externalizable* * Nowadays the information about {{@ExclusiveOptional}} parameter groups are stored in the *no externalizable* {{ParameterGroupModelProperty}}. This makes imposible for UI generators (Mozart/Studio) know when to generate the proper support. * Make the actual {{ParameterGroupModelProperty}} externalizable is not a good option due that it will expose a lot of java relationship between java objects that doesn't make sense. * *Possible Solutions*: ** Create a new externalizable model property to expose the information about {{@ExclusiveOptional}} parameter groups. ** Create a custom serializer for the {{ParameterGroupModelProperty}} to just expose the needed information.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10606","09/20/2016 22:07:35",3,"Extension's API POJOs should have a getter method for each @Parameter field ""*Extension's API POJOs should have a getter for each @Parameter field* * To be fully with compliant with DataWeave all the POJOs that an Extension expose _(operation parameter, operation return type, etc)_ should have a getter method for each {{@Parameter}} field. * The fundaments for this new requirement are: ** DW detects public attributes thought getter methods. This enables auto transformation. If the POJO attributes are found by looking all the fields there is no way to detect when a field is an {{@Parameter}} (an be exposed) or not. ** Does not exist any case where a *public* POJO have an attribute exposed by a {{@Parameter}} but doesn't have a *getter* to be able to access to the field value. *Action* : Validate that the extension API POJOs have a getter for every {{@Parameter}} field. _(Configurations, ConnProviders, Sources don't enter in this validation)_""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10607","09/21/2016 16:07:45",2,"HttpListener: add method to find the status of the listener ""So far there isn't any way to find out the status of the listener and the its initial status. The Runtime Manager team is working on the management of flows and endpoints. We need to have the status of Http Listener to be able to manage it (start/stop) Note that with the Http endpoint is was possible to know its status. This should be included in mule 3.x and 4.x ""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10608","09/21/2016 17:29:01",0,"Remove support for literal expressions ""Remove such support since it's not needed anymore""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10609","09/21/2016 21:22:47",8,"ParameterResolver should be usable on a config or connection provider ""Right now the ParameterResolver is usable from an operation because we create a new instance per execution and we wrap the event. There's also the need to be able to use it from configurations and connection providers. This means that the event needs to be communicated somehow else. REQUIREMENTS: * Enable the aforementioned * Allow for those config/providers to use this with XML supported complex types (the DSL shouldn't be different if a ParameterResolver or a straight up value is used) * Create a minimal facade to communicate the event. Something like: Where Context is an initially empty interface which we can downcast to an internal implementation which holds the event. This context is to be obtained as an operation parameter: DESIGN TASKS: * Come out with a good name for the Context thing. I lean towards OperationContext or ExecutionContext, but both names are taken. Come out with a third viable option or rename OperationContext to something else. * For the currently supported cases of operations which receive a ParameterResolver we need to either split the ParameterResolver interface in two (one which resolve() method is argless and one which receives the context), or make the context always required and force the operations to also receive the Context. """," T resolve(Context); public String felisatti(@UseConfig config, Context context) { return config.getResolver().resolve(context); } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10612","09/21/2016 23:24:22",0,"Upgrade JAXB to 2.1.17 ""Upgrade JAXB to 2.1.17""","",0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10615","09/22/2016 15:36:06",1,"Define requester behaviour when outputType doesn't match actual type ""Right now, the outputType parameter is ignored by the request operation and t's only there for design time metadata definition. However, since the request operation will generate a certain output type we need to decide how to act when it does not match the user define one. For example, if the user indicated that the request would produce a MultiPartPayload type but then a form url encoded response is received and a Map type returned, should we log a warning or should we fail entirely?""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10619","09/22/2016 18:22:46",2,"FilteringArtifactClassLoader is not being used by RegionClassLoader when loading classes and resources instead it uses the ArtifactClassLoader ""As part of the introduction of the RegionClassLoader when an ArtifactClassLoader is added to the region with the passed filter a new FilteringArtifactClassLoader is created but not later used to resolve classes and resources.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10620","09/22/2016 18:41:19",0,"Envelope namespace used in body produces broken xml when getting the body ""When the body is extracted, it has the soapenv prefix but it lacks the namespace declaration for that prefix.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10622","09/22/2016 20:13:12",1,"Extension model JSON inside a package is not a valid JSON ""When building [this sample extension|https://github.com/fbarrios/hello-world-connector-4.x/commit/6a5d018cf9d861db48d86b635ac047394f0b21d8], the generated JSON is not well formed, as it has duplicated the version key: """," { """"name"""": """"HelloWorldConnector"""", """"description"""": """""""", """"version"""": """"1.0.0-SNAPSHOT"""", """"vendor"""": """"Mulesoft"""", """"category"""": """"COMMUNITY"""", """"version"""": """"1.0.0-SNAPSHOT"""", """"configurations"""": [ { ... ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10625","09/23/2016 18:23:18",1,"Configurations are not registered in the XSD with their hyphenated name ""*Configurations are not registered in the XSD with their hyphenated name* For example we have a configuration like: In the XSD the configuration element will be registered as {{ConfigOne}}, but the ExtensionDefinitionParser will try to load it as {{config-one}}. As consequence everything fails.""","@Configuration(name = """"ConfigOne"""")",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10628","09/26/2016 14:08:19",5,"Review HTTP extension exported packages ""Currently, the http extension is not exporting some classes that are needed by its users, and some are even in an 'internal' package.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10629","09/26/2016 15:02:14",5,"Error handling locator API should work with Throwable ""Right now, all of our error handling locating logic works considering Exception. The problem there is that a) we are leaving out a part of the Java error hierarchy and b) we are casting to Exception in several places which could cause trouble. We should use the more general Throwable, avoid the casts and add a proper type for things in Java under Error (IMO we should have a separate hierarchy from ANY so that those are not handled, though we need to be careful since some modules might need to handle things under Error).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10633","09/26/2016 17:26:28",13,"Support SDK extensions on domains ""Currently, it is not supported to define a config of an SDK based extensions on a domain. It should be""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10634","09/26/2016 18:30:46",13,"Most externalizable model properties should be actual part of the ExtensionModel ""The extension model needs to be more prescriptive and be more front center with the stuff it has. ModelProperties should be all non externalizable and used for runtime implementation things only. All data model properties should be incorporated into the mainstream model. The only currently identified exception are the DataSense ones""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10635","09/26/2016 18:37:54",5,"Improve extension model serialization tests ""Improve extension model serialization tests in order to cover a more comprehensive and complex use cases.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10639","09/26/2016 19:34:02",1,"Remove references to per-app distribution folder ""Per-app folder was used on mule-3.x branches to place modules that had dependencies on third party libraries that were not part of mule distribution (like WMQ client). This folder is not used anymore on Mule 4 as this kind of functionality will be provided by artifact plugins which will have access to app's shared libraries""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10640","09/26/2016 20:12:09",1,"Remove lib/shared folder from distributions ""Old mule 3.x used lib/shared folder to share libraries across different applications. That concept was replaced with the concept of domains and this folder deprecated. Now is time to remote it from the distro.""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10641","09/26/2016 22:13:32",8,"Allow declaration of MetadataResolver at parameter level ""Currently we support only to resolve Dynamic MetadataType for the Content parameter. In order to have dynamic type inference for other parameters, regardless whether or not the parameter is the Content of the operation, we'll have to support the declaration of MetadataResolvers at parameter level. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10642","09/27/2016 04:09:16",1,"Application name should appear in application undeployment message ""When I undeploy an application the message printed in the log doesn't mention the application name but an hexadecimal number, like this: To reproduce undeploy any application by deleting its anchor file."""," ********************************************************************** * Application """"76ad4d00-845e-11e6-b748-28cfe915d821"""" shut down * * normally on: 9/27/16 12:01 AM * * Up for: 0 days, 0 hours, 1 mins, 26.798 sec * ********************************************************************** ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10643","09/27/2016 16:22:11",0,"ResourceBundle class loader leak when undeploying application ""https://docs.oracle.com/javase/6/docs/api/java/util/ResourceBundle.html#clearCache(java.lang.ClassLoader) should be called as part of DefaultResourceReleaser process for releasing resources for an Application/Domain ClassLoader. This will prevent ClassLoader leaks when undeploying applications/domains. Also ResourceBundle leaves a reference to the class loader if a non existent bundle was obtained just right before the dispose is made this reference should be nulled too.""","ResourceBundle.clearCache(ClassLoader classLoader)",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10646","09/27/2016 20:39:09",8,"Refactor GrizzlyHttpClient to use BodyDeferringAsyncHandler ""As it turns out, the standard implementation of AsyncHandler which we are using saves the entire response to memory (see com.ning.http.client.AsyncCompletionHandler#onBodyPartReceived and its uses in GrizzlyHttpClient). This is a problem as there is no actual streaming and can cause an OOM when the response is large. It seems that in order to allow an InputStream to be used as payload and the data provided as the body parts arrive to be streamed down to other components reading it, we need to use a com.ning.http.client.BodyDeferringAsyncHandler providing it with a PipedOutputStream. Then the payload can be a PipedInputStream using that one. Special care should be taken since those two should write/read in different threads and the solution should be applied to both the blocking and non-blocking send. Notice that when dealing with multipart or form url encoded data, reading the whole message is necessary (an InputStream should not be propagated). ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10649","09/28/2016 09:35:17",3,"StackOverflow error while compiling extension with recursive pojos ""Compilation of an extension fails with StackOverflow when using as parameter of an operation a structure like the following: Same happens if we use maps: """," @XmlHints(allowTopLevelDefinition = true) public class RecursivePojo { @Parameter private List childs; } @XmlHints(allowTopLevelDefinition = true) public class RecursivePojo { @Parameter private Map mappedChilds; } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10652","09/28/2016 16:03:33",1,"ArtifactClassLoaderRunner - Add support for running isolated functional test cases on Mule Modules ""Currently we support PLUGIN and APPLICATION while classifying the rootArtifact, it should also be supported MODULE. This means that the target/classes for the rootArtifact should not go to a plugin classification neither to application classification, it should go to container classification urls.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10654","09/29/2016 08:42:01",5,"Model Validator should not complain if the singularized name clashes with another parameter name, when the generic of the list is of the same as the parameter type ""It is a very common case that you can have operations for a single entity or multiple entities in the same connector. Right now we are failing at compile time with the error: Expected: The compilation should pass Also, we should not mention internal implementations like ImmutableRuntimeOperationModel when reporting errors to the users"""," public String operationWithPojo(RecursivePojo pojoParam) { return null; } public String operationWithPojoList(List pojoParams) { return null; } [ERROR] Failed to execute goal org.bsc.maven:maven-processor-plugin:2.2.4:process (process) on project extension-with-resursive-structures: Error executing: org.mule.runtime.core.api.MuleRuntimeException: org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: Extension 'Recursive' contains 1 parameters that clash when singularized. operation 'operationWithPojoList' contains parameter 'pojoParams' that when transformed into DSL language clashes with parameter 'pojoParam' from 'ImmutableRuntimeOperationModel' -> [Help 1] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10655","09/29/2016 11:31:43",8,"Cleanup MessageProcessorChains to ensure consistency of injection and lifecycle ""Cleanup MessageProcessorChains to ensure consistency of injection and lifecycle""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10659","09/29/2016 15:44:24",8,"Transports - Make tests run isolated ""MULE-10301 has added support for testing transports that will go to compatibility plugin. As part of MULE-10628 these transports artifacts were migrated to use isolated test runner but the plugin.properties had to be copied to these artifacts. Clean up these plugin.properties to only export what is needed.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10661","09/29/2016 16:12:39",1,"ArtifactClassLoaderRunner - URLClassLoaders are created for classification process, these CLs have to be closed ""Close URLClassLoaders used for searching resources and other stuff while creating the ArtifactClassLoader for tests.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10662","09/29/2016 16:38:01",3,"Remove host/port from HTTP overrides ""will be replaced with expressions in element""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10663","09/29/2016 16:39:59",3,"Improve field ordering in new Http connector "" Fix ordering: * Connection configuration information needs to be always on top. * User/password always grouped together. * Host/port always grouped together. * Other stuff you can see""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10664","09/29/2016 17:06:55",2,"Fix parameters ordering in new Email connector ""Fix ordering: * Connection configuration information needs to be always on top * User/password always grouped together. * Host/port always grouped together. * Other stuff you can identify and improve""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10677","09/30/2016 20:16:11",3,"schedulers module shouldn't export c3p0 ""The schedulers module is currently exporting c3p0. This is not only conceptually wrong, it also generates leaks when the DB connector (which internally also uses c3p0) tries to dispose pooled datasources.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10678","09/30/2016 20:33:59",2,"Email: Support deleteAfterRetrieve in the imap list operation ""Add a boolean parameter to the list operation of the imap protocol, so when all the emails are retrieved are also deleted.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10679","09/30/2016 21:28:31",13,"Replace Describer with extension loader concept ""Replace the concept of extension describer with that of ExtensionModelLoader.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10681","09/30/2016 21:32:37",8,"Replace NullType with VoidType in places which makes sense ""Right now we use NullType to represent Void, although NullType is intended to be used as an actual null. Find those places and replace them with a VoidType""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10683","09/30/2016 21:44:49",13,"Make DataSense tooling service consistent with the test connectivity one ""The current Metadata Service has consistency and conceptual problems. Problems are that: * It requires a deployed app * It requires providing the coordinates to an actual message processor * It requires providing the metadata key, which is not only already present on the message processor, there's also not guaranteeing that the key supplied in the XML matches that on the API invocation. We should move to a model similar to that of the connectivity testing service which: * Can obtain metadata for a particular MP on a deployed app (using the key already configured in that MP) * Allows pushing an entire config, deduces a minimal app, deploys it as a temporal artifact, extracts the data, disposes the temporal artifact. (This should be done reusing as much logic as possible from the connectivity testing service)""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10685","09/30/2016 22:08:55",1,"TestRunner fetches spring annotated classes when looking for Extensions ""ExtensionPluginMetadataGenerator calls on method scanForExtensionAnnotatedClasses(). The true parameter means that it will look for spring specific annotations that not only are not needed but may cause the calling method to return unwanted classes, causing failures.""","new ClassPathScanningCandidateComponentProvider(true);",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10686","09/30/2016 23:07:56",0,"Disable entity expansion when processing XML to avoid DoS ""In the jersey module it's possible to trigger a DoS by submitting an XML Billion Laughs attack.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10689","10/01/2016 14:16:38",3,"Allow plugins/extensions to include spring components ""Currenty, all spring classes are loaded from the container classloader. Certain extensions or plugins may want to include their own spring components (for instance, spring-jms in the jms extension or the compatibility module plugin). Currently, all org.springframework.* classes are loaded from the container classloader, which prevents the intended usage.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10690","10/03/2016 15:31:58",0,"Some TypeAnnotations doesn't override equals() and hashCode() methods ""*TypeAnnotations doesn't override equals() and hashCode() methods* The {{TypeAnnotations}}: * FlattenedTypeAnnotation * TextTypeAnnotation Doesn't override the *equals()* and *hashCode()* methods, this produce that equals {{MetadataTypes}} are considered different.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10692","10/03/2016 17:34:51",1,"Improve exception messages when classes are not found in RegionClassLoader ""RegionClassLoader doesn't provide enough information for troubleshooting a ClassNotFound exception.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10693","10/03/2016 18:30:02",5,"Extensions modules take a long time to build ""Take for instance the http extension. When building that module on my local machine it takes around 3 minutes. After seeing the output log: 2 things can be observed * The phases between lines 100964 and 179075 run 2 times, doubling the bulk of the work being done * The phase process-classes which runs the ExtensionResourcesGeneratorAnnotationProcessor takes around xxx seconds. After profiling that code, i saw that in this case it is scanning the classpath looking for extensions 3 times (see ClasspathBasedDslContext#findExtensionsInClasspath()). Bases on that observations, the build time for that module could be reduce by 1/6, going from 3 mins to around 30 secs."""," 900 [main] [INFO] Scanning for projects... 4474 [main] [WARNING] 4474 [main] [WARNING] Some problems were encountered while building the effective model for org.mule.tests:mule-tests-integration:jar:4.0-SNAPSHOT 4474 [main] [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.mule.modules:mule-module-extensions-support:jar -> duplicate declaration of version ${project.version} @ org.mule.tests:mule-tests-integration:[unknown-version], /Users/rodrigomerino/git/mule_4/tests/integration/pom.xml, line 265, column 21 4474 [main] [WARNING] 4474 [main] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. 4474 [main] [WARNING] 4474 [main] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. 4474 [main] [WARNING] 4509 [main] [INFO] 4512 [main] [INFO] Using the MultiThreadedBuilder implementation with a thread count of 8 4522 [BuilderThread 0] [INFO] 4522 [BuilderThread 0] [INFO] ------------------------------------------------------------------------ 4522 [BuilderThread 0] [INFO] Building Mule HTTP Extension 4.0-SNAPSHOT 4522 [BuilderThread 0] [INFO] ------------------------------------------------------------------------ 5108 [BuilderThread 0] [INFO] 5108 [BuilderThread 0] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ mule-module-http-ext --- 5160 [BuilderThread 0] [INFO] Deleting /Users/rodrigomerino/git/mule_4/extensions/http/target 5184 [BuilderThread 0] [INFO] 5184 [BuilderThread 0] [INFO] --- buildnumber-maven-plugin:1.4:create (default) @ mule-module-http-ext --- 5477 [BuilderThread 0] [INFO] ShortRevision tag detected. The value is '8'. 5487 [BuilderThread 0] [INFO] Executing: /bin/sh -c cd '/Users/rodrigomerino/git/mule_4/extensions/http' && 'git' 'rev-parse' '--verify' '--short=8' 'HEAD' 5487 [BuilderThread 0] [INFO] Working directory: /Users/rodrigomerino/git/mule_4/extensions/http 5633 [BuilderThread 0] [INFO] Storing buildNumber: 204eead1 at timestamp: 2016-Oct-03 14:20:34 5645 [BuilderThread 0] [INFO] Storing buildScmBranch: MULE-10628 5645 [BuilderThread 0] [INFO] 5646 [BuilderThread 0] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-versions) @ mule-module-http-ext --- 5829 [BuilderThread 0] [INFO] 5829 [BuilderThread 0] [INFO] --- maven-dependency-plugin:2.10:analyze-only (analyze-dependencies-for-extension) @ mule-module-http-ext --- 6095 [BuilderThread 0] [INFO] Skipping plugin execution 6095 [BuilderThread 0] [INFO] 6095 [BuilderThread 0] [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ mule-module-http-ext --- 6176 [BuilderThread 0] [INFO] Using 'ISO-8859-1' encoding to copy filtered resources. 6183 [BuilderThread 0] [INFO] Copying 2 resources 6204 [BuilderThread 0] [INFO] 6204 [BuilderThread 0] [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ mule-module-http-ext --- 6305 [BuilderThread 0] [INFO] Compiling 57 source files to /Users/rodrigomerino/git/mule_4/extensions/http/target/classes 8294 [BuilderThread 0] [INFO] 8294 [BuilderThread 0] [INFO] --- formatter-maven-plugin:1.8.0:validate (default) @ mule-module-http-ext --- 8358 [BuilderThread 0] [INFO] Using 'ISO-8859-1' encoding to format source files. 8374 [BuilderThread 0] [INFO] Number of files to be formatted: 63 9769 [BuilderThread 0] [INFO] Successfully formatted: 0 file(s) 9769 [BuilderThread 0] [INFO] Fail to format : 0 file(s) 9769 [BuilderThread 0] [INFO] Skipped : 126 file(s) 9769 [BuilderThread 0] [INFO] Approximate time taken: 1s 9770 [BuilderThread 0] [INFO] 9770 [BuilderThread 0] [INFO] --- license-maven-plugin:2.11:check (default) @ mule-module-http-ext --- 9922 [BuilderThread 0] [INFO] Checking licenses... 10027 [BuilderThread 0] [INFO] 10028 [BuilderThread 0] [INFO] --- maven-processor-plugin:2.2.4:process (process) @ mule-module-http-ext --- ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. 89693 [BuilderThread 0] [WARNING] diagnostic: warning: The following options were not recognized by any processor: '[extension.version]' 89700 [BuilderThread 0] [INFO] 89700 [BuilderThread 0] [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ mule-module-http-ext --- 89703 [BuilderThread 0] [INFO] Using 'ISO-8859-1' encoding to copy filtered resources. 89704 [BuilderThread 0] [INFO] Copying 6 resources 89709 [BuilderThread 0] [INFO] 89709 [BuilderThread 0] [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ mule-module-http-ext --- 89714 [BuilderThread 0] [INFO] Compiling 6 source files to /Users/rodrigomerino/git/mule_4/extensions/http/target/test-classes 91124 [BuilderThread 0] [INFO] 91124 [BuilderThread 0] [INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ mule-module-http-ext --- 91237 [BuilderThread 0] [INFO] Tests are skipped. 91237 [BuilderThread 0] [INFO] 91237 [BuilderThread 0] [INFO] --- maven-jar-plugin:3.0.1:jar (default-jar) @ mule-module-http-ext --- 91879 [BuilderThread 0] [INFO] Building jar: /Users/rodrigomerino/git/mule_4/extensions/http/target/mule-module-http-ext-4.0-SNAPSHOT.jar 91951 [BuilderThread 0] [INFO] 91951 [BuilderThread 0] [INFO] --- mule-extensions-maven-plugin:1.0.0-SNAPSHOT:package (default-package) @ mule-module-http-ext --- 91954 [BuilderThread 0] [INFO] Adding extension jar 91960 [BuilderThread 0] [INFO] Adding as a lib 91960 [BuilderThread 0] [INFO] Adding as a lib 91960 [BuilderThread 0] [INFO] Adding as a lib 91961 [BuilderThread 0] [INFO] Adding as a lib 91961 [BuilderThread 0] [INFO] Adding as a lib 91961 [BuilderThread 0] [INFO] Adding as a lib 91961 [BuilderThread 0] [INFO] Adding as a lib 91961 [BuilderThread 0] [INFO] Adding as a lib 91962 [BuilderThread 0] [INFO] Adding as a lib 91962 [BuilderThread 0] [INFO] Adding as a lib 91962 [BuilderThread 0] [INFO] Adding as a lib [INFO] Building zip: /Users/rodrigomerino/git/mule_4/extensions/http/target/mule-module-http-ext-4.0-SNAPSHOT.zip 92242 [BuilderThread 0] [INFO] 92242 [BuilderThread 0] [INFO] --- mule-extensions-maven-plugin:1.0.0-SNAPSHOT:studio-package (default-studio-package) @ mule-module-http-ext --- 92519 [BuilderThread 0] [WARNING] The icon [theme.classic/httpn-connector-small.png] was not found in the 'icons' folder. A generic one will be used instead. 92519 [BuilderThread 0] [WARNING] The icon [theme.classic/httpn-connector-large.png] was not found in the 'icons' folder. A generic one will be used instead. 92520 [BuilderThread 0] [WARNING] The icon [theme.light/httpn-connector-small.png] was not found in the 'icons' folder. A generic one will be used instead. 92520 [BuilderThread 0] [WARNING] The icon [theme.light/httpn-connector-large.png] was not found in the 'icons' folder. A generic one will be used instead. 92520 [BuilderThread 0] [WARNING] The icon [theme.classic/httpn-endpoint-large.png] was not found in the 'icons' folder. A generic one will be used instead. 92521 [BuilderThread 0] [WARNING] The icon [theme.classic/httpn-endpoint-small.png] was not found in the 'icons' folder. A generic one will be used instead. 92521 [BuilderThread 0] [WARNING] The icon [theme.light/httpn-endpoint-large.png] was not found in the 'icons' folder. A generic one will be used instead. 92522 [BuilderThread 0] [WARNING] The icon [theme.light/httpn-endpoint-small.png] was not found in the 'icons' folder. A generic one will be used instead. 92596 [BuilderThread 0] [WARNING] No license could be found in the project with the following names: [LICENSE.md,license.txt,License.md] 96977 [BuilderThread 0] [WARNING] No license will be used in the Studio plugin: Error reading from the remote URL: Server returned HTTP response code: 403 for URL: http://www.mulesoft.com/CPAL [INFO] Building jar: /Users/rodrigomerino/git/mule_4/extensions/http/target/update-site/features/org.mule.tooling.ui.extension.http-ext.4.0.0_4.0.0.201610031422.jar [INFO] Building jar: /Users/rodrigomerino/git/mule_4/extensions/http/target/update-site/plugins/org.mule.tooling.ui.contribution.httpn.4.0.0_4.0.0.201610031422.jar 97327 [BuilderThread 0] [INFO] Command line: /bin/sh -c /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre/bin/java -jar /Users/rodrigomerino/.m2/repository/org/eclipse/tycho/tycho-bundles-external/0.14.1/eclipse/plugins/org.eclipse.equinox.launcher_1.3.0.v20111107-1631.jar -nosplash -application org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher -artifactRepository file:/Users/rodrigomerino/git/mule_4/extensions/http/target/update-site/ -metadataRepository file:/Users/rodrigomerino/git/mule_4/extensions/http/target/update-site/ -source /Users/rodrigomerino/git/mule_4/extensions/http/target/update-site -publishArtifacts -append Generating metadata for .. Generation completed with success [0 seconds]. 99087 [BuilderThread 0] [INFO] Command line: /bin/sh -c /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre/bin/java -jar /Users/rodrigomerino/.m2/repository/org/eclipse/tycho/tycho-bundles-external/0.14.1/eclipse/plugins/org.eclipse.equinox.launcher_1.3.0.v20111107-1631.jar -nosplash -application org.eclipse.equinox.p2.publisher.CategoryPublisher -categoryDefinition file:/Users/rodrigomerino/git/mule_4/extensions/http/target/category.xml -categoryQualifier -metadataRepository file:/Users/rodrigomerino/git/mule_4/extensions/http/target/update-site/ Generating metadata for .. Generation completed with success [0 seconds]. [INFO] Building zip: /Users/rodrigomerino/git/mule_4/extensions/http/target/mule-module-http-ext-4.0-SNAPSHOT-studio-plugin.zip 100770 [BuilderThread 0] [INFO] 100770 [BuilderThread 0] [INFO] --- maven-jar-plugin:3.0.1:test-jar (attach-test-jar) @ mule-module-http-ext --- 100772 [BuilderThread 0] [INFO] Skipping packaging of the test-jar 100772 [BuilderThread 0] [INFO] 100773 [BuilderThread 0] [INFO] --- maven-jar-plugin:3.0.1:jar (mule-plugin) @ mule-module-http-ext --- 100799 [BuilderThread 0] [INFO] Building jar: /Users/rodrigomerino/git/mule_4/extensions/http/target/mule-module-http-ext-4.0-SNAPSHOT-mule-plugin.jar 100845 [BuilderThread 0] [INFO] 100845 [BuilderThread 0] [INFO] >>> mule-module-maven-plugin:1.0-SNAPSHOT:analyze (analyze) > test-compile @ mule-module-http-ext >>> 100964 [BuilderThread 0] [INFO] 100964 [BuilderThread 0] [INFO] --- buildnumber-maven-plugin:1.4:create (default) @ mule-module-http-ext --- 100966 [BuilderThread 0] [INFO] ShortRevision tag detected. The value is '8'. 100966 [BuilderThread 0] [INFO] Executing: /bin/sh -c cd '/Users/rodrigomerino/git/mule_4/extensions/http' && 'git' 'rev-parse' '--verify' '--short=8' 'HEAD' 100966 [BuilderThread 0] [INFO] Working directory: /Users/rodrigomerino/git/mule_4/extensions/http 101043 [BuilderThread 0] [INFO] Storing buildNumber: 204eead1 at timestamp: 2016-Oct-03 14:22:09 101052 [BuilderThread 0] [INFO] Storing buildScmBranch: MULE-10628 101052 [BuilderThread 0] [INFO] 101052 [BuilderThread 0] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-versions) @ mule-module-http-ext --- 101053 [BuilderThread 0] [INFO] 101053 [BuilderThread 0] [INFO] --- maven-dependency-plugin:2.10:analyze-only (analyze-dependencies-for-extension) @ mule-module-http-ext --- 101056 [BuilderThread 0] [INFO] Skipping plugin execution 101056 [BuilderThread 0] [INFO] 101056 [BuilderThread 0] [INFO] --- maven-resources-plugin:3.0.1:resources (default-resources) @ mule-module-http-ext --- 101057 [BuilderThread 0] [INFO] Using 'ISO-8859-1' encoding to copy filtered resources. 101058 [BuilderThread 0] [INFO] Copying 2 resources 101058 [BuilderThread 0] [INFO] 101058 [BuilderThread 0] [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ mule-module-http-ext --- 101069 [BuilderThread 0] [INFO] Nothing to compile - all classes are up to date 101069 [BuilderThread 0] [INFO] 101069 [BuilderThread 0] [INFO] --- formatter-maven-plugin:1.8.0:validate (default) @ mule-module-http-ext --- 101070 [BuilderThread 0] [INFO] Using 'ISO-8859-1' encoding to format source files. 101075 [BuilderThread 0] [INFO] Number of files to be formatted: 63 101161 [BuilderThread 0] [INFO] Successfully formatted: 0 file(s) 101161 [BuilderThread 0] [INFO] Fail to format : 0 file(s) 101161 [BuilderThread 0] [INFO] Skipped : 63 file(s) 101161 [BuilderThread 0] [INFO] Approximate time taken: 0s 101161 [BuilderThread 0] [INFO] 101161 [BuilderThread 0] [INFO] --- license-maven-plugin:2.11:check (default) @ mule-module-http-ext --- 101166 [BuilderThread 0] [INFO] Checking licenses... 101214 [BuilderThread 0] [INFO] 101214 [BuilderThread 0] [INFO] --- maven-processor-plugin:2.2.4:process (process) @ mule-module-http-ext --- ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. 179064 [BuilderThread 0] [WARNING] diagnostic: warning: The following options were not recognized by any processor: '[extension.version]' 179068 [BuilderThread 0] [INFO] 179068 [BuilderThread 0] [INFO] --- maven-resources-plugin:3.0.1:testResources (default-testResources) @ mule-module-http-ext --- 179070 [BuilderThread 0] [INFO] Using 'ISO-8859-1' encoding to copy filtered resources. 179071 [BuilderThread 0] [INFO] Copying 6 resources 179071 [BuilderThread 0] [INFO] 179071 [BuilderThread 0] [INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ mule-module-http-ext --- 179075 [BuilderThread 0] [INFO] Nothing to compile - all classes are up to date 179075 [BuilderThread 0] [INFO] 179075 [BuilderThread 0] [INFO] <<< mule-module-maven-plugin:1.0-SNAPSHOT:analyze (analyze) < test-compile @ mule-module-http-ext <<< 179075 [BuilderThread 0] [INFO] 179075 [BuilderThread 0] [INFO] --- mule-module-maven-plugin:1.0-SNAPSHOT:analyze (analyze) @ mule-module-http-ext --- 179078 [BuilderThread 0] [INFO] No module API problems found 179078 [BuilderThread 0] [INFO] 179078 [BuilderThread 0] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ mule-module-http-ext --- 179135 [BuilderThread 0] [INFO] Installing /Users/rodrigomerino/git/mule_4/extensions/http/target/mule-module-http-ext-4.0-SNAPSHOT.jar to /Users/rodrigomerino/.m2/repository/org/mule/modules/mule-module-http-ext/4.0-SNAPSHOT/mule-module-http-ext-4.0-SNAPSHOT.jar 179138 [BuilderThread 0] [INFO] Installing /Users/rodrigomerino/git/mule_4/extensions/http/pom.xml to /Users/rodrigomerino/.m2/repository/org/mule/modules/mule-module-http-ext/4.0-SNAPSHOT/mule-module-http-ext-4.0-SNAPSHOT.pom 179146 [BuilderThread 0] [INFO] Installing /Users/rodrigomerino/git/mule_4/extensions/http/target/mule-module-http-ext-4.0-SNAPSHOT.zip to /Users/rodrigomerino/.m2/repository/org/mule/modules/mule-module-http-ext/4.0-SNAPSHOT/mule-module-http-ext-4.0-SNAPSHOT.zip 179193 [BuilderThread 0] [INFO] Installing /Users/rodrigomerino/git/mule_4/extensions/http/target/mule-module-http-ext-4.0-SNAPSHOT-studio-plugin.zip to /Users/rodrigomerino/.m2/repository/org/mule/modules/mule-module-http-ext/4.0-SNAPSHOT/mule-module-http-ext-4.0-SNAPSHOT-studio-plugin.zip 179260 [BuilderThread 0] [INFO] Installing /Users/rodrigomerino/git/mule_4/extensions/http/target/mule-module-http-ext-4.0-SNAPSHOT-mule-plugin.jar to /Users/rodrigomerino/.m2/repository/org/mule/modules/mule-module-http-ext/4.0-SNAPSHOT/mule-module-http-ext-4.0-SNAPSHOT-mule-plugin.jar 179273 [main] [INFO] ------------------------------------------------------------------------ 179273 [main] [INFO] BUILD SUCCESS 179273 [main] [INFO] ------------------------------------------------------------------------ 179273 [main] [INFO] Total time: 02:58 min (Wall Clock) 179273 [main] [INFO] Finished at: 2016-10-03T14:23:27-03:00 179775 [main] [INFO] Final Memory: 86M/305M 179775 [main] [INFO] ------------------------------------------------------------------------ ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10696","10/03/2016 19:34:56",2,"Improve HttpRequestAttributes builder to accept nothing/old attributes ""The HttpRequestAttributes should have a builder to accept old attributes or nothing. Nowadays the constructor receives all the attributes and it is not very helpful: """," public HttpRequestAttributes(ParameterMap headers, String listenerPath, String relativePath, String version, String scheme, String method, String requestPath, String requestUri, String queryString, ParameterMap queryParams, ParameterMap uriParams, String remoteAddress, Certificate clientCertificate) ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10713","10/04/2016 19:16:22",0,"Add a MuleArtifactFunctionalTestCase exclusions for EE artifacts ""MuleArtifactFunctionalTestCase included in CE provides a list of exclusions that must be applied when defining the container classloader. As EE uses a different set of group Ids on the artifacts those artifacts must be added to the exclusion list ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10707","10/04/2016 20:58:00",8,"Improve MetadataResults propagation in Metadata Service ""Currently, the MetadataManager exposes an structure where each MetadataDescriptor is contained inside a MetadataResult. Navigating through this elements is cumbersome and not clear for the user, since in the serialization we provide a flattened view. We should simplify this error communication mechanism""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10709","10/04/2016 23:22:59",0,"Use custom factory builder for XML parsers to avoid vulnerabilities ""Use custom factory builder for XML parsers to avoid vulnerabilities""","",0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10711","10/05/2016 16:51:07",2,"Include body in request/response builder with payload as default ""We need to include the body in the HTTP builders so that it can be parameterised without first modifying the Message.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10712","10/05/2016 23:19:10",0,"Remove loader.override references ""Loader override is not used anymore. Remove references to it""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10718","10/06/2016 17:20:27",3,"Enrich HttpClient exception to include request URI ""When the requester fails sending a request, the only message is that it failed, there's no reference to the actual request that failed. This is a debugging pain since the requester is very dynamic and the actual request can vary and change completely, making it hard to pinpoint exactly which one failed.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10720","10/06/2016 19:07:44",0,"xml-to-dom-transformer default returnType should be org.w3c.dom.Document instead of byte[] ""The class has no constructor and hence its inherited field returnType is set by its parent class, which is . ""","org.mule.module.xml.transformer.XmlToDomDocumentorg.mule.module.xml.transformer.AbstractXmlTransformerbyte[]",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10722","10/06/2016 20:00:51",0,"Not Handling FTP Connection Errors in FTPMessageReceiver ""While retrieving information from the FTP server, if a null line is read (check SE-4039) it is thrown a FTPConnectionClosedException, which is not handled as a (mule) ConnectException in the AbstractSystemExceptionStrategy. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10723","10/06/2016 20:29:00",1,"com.ning.http.client.ws packaged is not exported in HTTP module ""The HTTP module exports various packages from async-http-client but not com.ning.http.client.ws which causes classloading issues for plugins using it such as the Mule Agent.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10729","10/07/2016 19:37:59",1,"on-error-continue by default should not print the exception ""Usually when you want to go on with the execution you don't care about the error.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10730","10/07/2016 20:28:24",1,"Event.Builder.variables does not clear previous values ""In the interface org.mule.runtime.core.api.Event.Builder we are needing a method to clear properties and variables. The use case is as follows: I have an Event completely defined and I want a copy of it BUT with no flow variables. Currently there is no way to clean only the variables of the event. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10731","10/07/2016 20:29:41",0,"ArtifactClassLoaderRunner - Does not work when using Allure ""Cannot run isolated tests when enabling Allure. Also the following error messages are logged: """," [MuleArtifactClassLoader@30bab9cd] error can't determine superclass of missing type java.lang.Object [Xlint:cantFindType] [MuleArtifactClassLoader@30bab9cd] error can't determine superclass of missing type java.lang.Object [Xlint:cantFindType] [MuleArtifactClassLoader@30bab9cd] error can't determine superclass of missing type java.lang.Object [Xlint:cantFindType] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10733","10/07/2016 22:34:36",5,"Model validator not complaining for missing output resolver when returning a List ""When writing an extension with metadata, if the operation returns a Map and there is not OutputResolver, a model validator fails and shows an error, but if the return type is a List> the validation doesn't fail *Invalid code* The example above fails with the error: {code} org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: createEntity 'Metadata' specifies 'java.util.Map' as a return type. Operations and Sources with return type such as Object or Map must have defined a not null OutputTypeResolver org.mule.runtime.core.api.MuleRuntimeException: org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: createEntity 'Metadata' specifies 'java.util.Map' as a return type. Operations and Sources with return type such as Object or Map must have defined a not null OutputTypeResolver at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:946) {code} After adding the @OutputResolver to the create entity, the compilation doesn't fail, but it should fail for the createBulk *Invalid code that doesn't fail* {code:java} public class BasicOperations { @OutputResolver(TestInputAndOutputResolverWithKeyResolver.class) public Map createEntity(@Connection MetadataConnection connection, @MetadataKeyId String type, @Content @TypeResolver(TestInputAndOutputResolverWithKeyResolver.class) Map dynamicObject); public List> createBulk(@Connection MetadataConnection connection, @MetadataKeyId String type, @Content @TypeResolver(TestInputAndOutputResolverWithKeyResolver.class) List> dynamicObjects); {code}"""," public class BasicOperations { public Map createEntity(@Connection MetadataConnection connection, @MetadataKeyId String type, @Content @TypeResolver(TestInputAndOutputResolverWithKeyResolver.class) Map dynamicObject); public List> createBulk(@Connection MetadataConnection connection, @MetadataKeyId String type, @Content @TypeResolver(TestInputAndOutputResolverWithKeyResolver.class) List> dynamicObjects); org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: createEntity 'Metadata' specifies 'java.util.Map' as a return type. Operations and Sources with return type such as Object or Map must have defined a not null OutputTypeResolver org.mule.runtime.core.api.MuleRuntimeException: org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: createEntity 'Metadata' specifies 'java.util.Map' as a return type. Operations and Sources with return type such as Object or Map must have defined a not null OutputTypeResolver at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:946) public class BasicOperations { @OutputResolver(TestInputAndOutputResolverWithKeyResolver.class) public Map createEntity(@Connection MetadataConnection connection, @MetadataKeyId String type, @Content @TypeResolver(TestInputAndOutputResolverWithKeyResolver.class) Map dynamicObject); public List> createBulk(@Connection MetadataConnection connection, @MetadataKeyId String type, @Content @TypeResolver(TestInputAndOutputResolverWithKeyResolver.class) List> dynamicObjects); ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10735","10/08/2016 14:15:57",8,"ArtifactClassLoaderRunner - Automatically generate plugin.properties for compatibility libs ""Currently, for the proper running of the compatibility tests in an isolated manner, each library that has integration tests has its own plugin.properties to be taken into account when building the classloaders. This causes the same information to be repeated among different libraries. It would be better if those files could be automatically generated, maybe by aggregating the mule-module.properties of the compile dependencies. This would also be useful for automatically generating the mule-module.properties of the compatibility plugin.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12248","10/08/2016 14:25:11",2,"ArtifactClassLoaderRunner - Change plugin export resolver to look for plugin.json descriptor ""Migrate the runner to use new descriptor instead of plugin.properties""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10746","10/12/2016 21:31:00",1,"Remove WS consumer module ""Remove the module.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10748","10/12/2016 21:47:57",5,"Define mechanism to provide configuration for readers in dataweave ""We need to define a mechanism to configure readers in dataweave, for instance, a CSV readers needs to be configured with the field separator, or an XML reader needs to resolve what to return for an empty node, like a null or empty string. There are two possible options so far: - Define this properties in the mapping - Define this properties when defining the data type ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10749","10/12/2016 21:49:20",8,"Define mechanism to allow reuse of streams if they get consumed by dataweave. ""Define mechanism to allow reuse of streams if they get consumed by dataweave.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10750","10/12/2016 22:05:30",3,"Basic support for locating a component in the configuration by path and name ""Basic support for locating a component in the configuration by path and name""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10751","10/12/2016 22:06:28",8,"Complete support for locating a component in the configuration by path and name ""Complete support for locating a component in the configuration by path and name.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10752","10/12/2016 22:53:20",8,"HTTP Extension: when the requester and the listener use different protocols it gives a timeout ""When the requester tls conf uses TLSv1.2 and the listener TLS conf uses TLSv1.1 it throws timeout. If you invert the versions it works fine. You can check it in the test HttpRestrictedCiphersAndProtocolsTestCase#failsWithProtocolMismatch on the Branch MULE-10752 After the fix is done, please remove the ignore from the test HttpTlsContextCustomProtocolsTestCase#testGlobalTlsContextCustomProtocolsRestrictive which is failing from the same issue.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10753","10/12/2016 23:51:49",5,"SDK: Inconsistent behavior when injecting a tlsContext in a pojo ""Take *ClientCredentialsFullConfigTestCase* in branch *oauth-ext*. The *nested* case works correctly, since the inline definition of the tlsContextFactory is properly injected into the pojo *ClientCredentialsGrantType*. However, on the *global* case, the name is never resolved and the tlsContextFactory remains null.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10756","10/13/2016 14:07:10",13,"Spike JMS Extension migration ""Spike JMS Extension migration: - Find gaps in spec vs transport - Iteration one of configs and connections""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10760","10/13/2016 15:28:34",8,"HTTP Service: Create request and response builders ""We need to provide a way for users to create requests (for the client) and responses (for the listener). This will also include a way to generate HttpEntity objects, considering the multipart one as well.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10761","10/13/2016 15:47:24",3,"HTTP Service: Move specific dependencies to the service and remove them from the container ""Libraries such as AHC and grizzly that are specific for http shouldn't be in the container classloader, but rather on the service's.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10765","10/13/2016 16:31:03",8,"Define global bindings ""We need to define bindings like app, server, regex, etc.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10770","10/13/2016 19:03:43",1,"IndexOutOfBoundsException on ApplicationModel when having an empty flow config ""Having a config with a flow without an element: An IndexOutOfBoundsException is thrown when parsing it. """," java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:653) ~[?:1.8.0_65] at java.util.ArrayList.get(ArrayList.java:429) ~[?:1.8.0_65] at org.mule.runtime.config.spring.dsl.model.ApplicationModel.lambda$processSourcesRedeliveryPolicy$5(ApplicationModel.java:290) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.config.spring.dsl.model.ApplicationModel.executeOnEveryFlow(ApplicationModel.java:584) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.config.spring.dsl.model.ApplicationModel.processSourcesRedeliveryPolicy(ApplicationModel.java:289) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.config.spring.dsl.model.ApplicationModel.createEffectiveModel(ApplicationModel.java:282) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.config.spring.dsl.model.ApplicationModel.(ApplicationModel.java:275) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.config.spring.MuleArtifactContext.createApplicationModel(MuleArtifactContext.java:201) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.config.spring.MuleArtifactContext.(MuleArtifactContext.java:167) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] at org.mule.runtime.config.spring.MuleArtifactContext.(MuleArtifactContext.java:137) ~[mule-module-spring-config-4.0-SNAPSHOT.jar:4.0-SNAPSHOT] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10771","10/13/2016 21:00:07",2,"Use a final (non snapshot version) of reactor-core for BETA ""We are depending on an SNAPSHOT version for reactor-core, as soon as the 3.0.3 is released we should upgrade our dependency. """," 3.0.3.BUILD-SNAPSHOT ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10773","10/13/2016 22:06:42",3,"Jaxb unmarshaller doesn't support namespaces anymore ""After the security fix for xml factories the parser used by Jaxb stopped supporting namespaces.""","",1,0,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10778","10/14/2016 19:49:50",8,"Add attachment support to the new Web Service Consumer ""Add attachment support""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10779","10/14/2016 20:03:30",13,"Add Security Strategies to the new WSC ""Add different security strategies to the new Web Service Consumer, UsernameToken, Timestamp and Encryption were supported by the old connector we should at least add those to the new one.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10780","10/14/2016 20:08:03",8,"Prepare the new WSC for merge. ""Prepare the new Web Service Consumer so it can be merged to mule 4. This consists on: * Add javadocs * Prettify code and design. * Basic runtime working * Input Metadata working ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10781","10/14/2016 20:10:54",8,"Ensure test parity between the old and new Web Service Consumer ""Check that all the cases that were tested in the old connector are tested in the new extension.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10782","10/14/2016 20:14:35",5,"Add output metadata to the new WebService Consumer ""We should add output metedata for the response body and headers from attributes of the consume operation.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10783","10/14/2016 20:25:53",13,"Make the Web Service Consumer use the Soap Service ""To ease the first stage of development of the new WSC we used a basic http library as underlying transport to send the SOAP Request, we need to use the Http Extension to ensure consistency and give more options to configure. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10784","10/14/2016 21:11:34",5,"Add soap faults support in the new Web Service Consumer. ""Add Soap Faults support when the soap server produces an error.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10786","10/17/2016 11:50:31",2,"SessionHandler picks wrong serializer when connector is on domain ""Bug reported on MULE-7990 was re-introduced during the work for MULE-9929. When the muleContext was removed from the MuleMessage, we lost the ability to change the object serializer that has to be used to deserialize a serialized session. Problem was not detected as the tests covering this scenario on mule 3.x was deleted from 4.x as part of the original clean up before transports returned back.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10790","10/17/2016 19:15:24",5,"Add Allure configuration for the Extensions Tests. ""Add Allure configuration for the Extensions Tests.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10792","10/18/2016 15:09:04",3,"Model validator does not enforce returning an OperationResult when the OutputResolver specifies an attributes resolver ""The following code should fail at compile time since the OutputResolver specifies an attributes resolver, but the return type is not an OperationResult: """," public class BasicOperations { @OutputResolver(output=TestInputAndOutputResolverWithKeyResolver.class, attributes = TestInputAndOutputResolverWithKeyResolver.class) public List> createBulkWithAttributes(@Connection MetadataConnection connection, @MetadataKeyId String type, @Content @TypeResolver(TestInputAndOutputResolverWithKeyResolver.class) List> dynamicObjects) { if (dynamicObjects == null) { throw new RuntimeException(""""dynamicObjects cannot be null""""); } return dynamicObjects; } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10793","10/18/2016 18:40:12",2,"Add support for building mule-service modules ""Add support in mule-extensions-maven-plugin to build services. Define a mule-service artifact type.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10795","10/18/2016 22:25:34",5,"Remove the old Ws Consumer from mule ""Remove The WS Consumer based on the cxf Module Replace the ws consumer invocations in integration tests with the new SDK based WSC ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10796","10/19/2016 00:10:35",5,"WSC: Add tests for SOAP 12 ""Currently all tests in the wsc are being executed with a SOAP11 service. We should add tests for SOAP 12 and fix the gaps, if there are any.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10801","10/19/2016 19:43:42",1,"Rename MetadataTypeUtils to ExtensionMetadataTypeUtils ""Rename internal MetadataTypeUtils""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10803","10/19/2016 21:47:57",3,"IT tests on Windows environment are failing for Tooling Runtime Client ""The way it is implemented to call Tanuki Service Wrapper is considering the application (default) anchor file to check the status of the Mule Runtime process. This has issues when running the tests on Windows due to raise conditions are happening and the default application gets deleted. Find a way to improve this logic.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10804","10/19/2016 21:50:45",2,"Improve error handling on Tooling Runtime REST API ""Improve error handling on REST API to allow understand what went wrong doing tooling operations. Propagate errors from Mule Tooling Service API throw the REST and also propagate the exception stack trace from These error handling features should be enabled/disabled through configuration.""","org.mule.runtime.api.connection.ConnectionValidationResult",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10806","10/20/2016 14:31:28",8,"Migrate HTTP Module Requester QA tests to HTTP Extension in Mule 4.x ""After the inclusion of the Allure framework listener the numberValidator tests are failing ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10807","10/20/2016 14:43:50",8,"HTTP Extension: Sanity tests Requester ""HTTP Extension: Sanity tests Requester ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10809","10/20/2016 16:15:16",13,"Support native libraries/required dependencies ""For extensions like DB or connectors like SAP, PeopleSoft, JDE users need to specify jars/libraries that are required for the connector to work, but cannot be packaged inside of it because of technical or legal restrictions. We need to define a mechanism to provide this information in the extension model so that tooling can generate a proper UI for it. As an example of the information we currently support we can check the editors in studio: *SAP* *MySQL* *Oracle* """," ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10810","10/20/2016 16:25:03",1,"Deployment should look for application resources relative to the artifactFolder ""When applications are deployed from Tooling Services API the internal implementation of the service delegates the deployment to the deployment module which is not taking into account the artifactFolder to search for the application resources, instead it is using the appName relative to MULE_HOME/apps/$appName This has to be changed in order to allow Tooling Service API to use deployment service and deploy temporary applications that are not going to be added to the MULE_HOME/apps folder.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10812","10/20/2016 19:22:00",0,"ClassNotFound exception is thrown when resolving metadata thought Mule Agent ""When resolving the metadata of a component using the Mule Agent with the Tooling API the endpoint throws the following error: Debugging internally, the ClassLoader that tries to load {{TransactionIsolation}} from DB Connector, is the ClassLoader of the *Agent* which doesn't have access to that class."""," """"message"""": """"Could not load class org.mule.extension.db.api.param.TransactionIsolation"""", """"reason"""": """"java.lang.IllegalArgumentException: Could not load class org.mule.extension.db.api.param.TransactionIsolation\n\tat org.mule.metadata.java.api.utils.JavaTypeUtils.getType(JavaTypeUtils.java:41)\n\tat org.mule.metadata.java.api.utils.JavaTypeUtils.getType(JavaTypeUtils.java:25)\n\tat org.mule.runtime.module.extension.internal.config.dsl.ExtensionDefinitionParser.isExpressionFunction(ExtensionDefinitionParser.java:714)\n\tat org.mule.runtime.module.extension.internal.config.dsl.ExtensionDefinitionParser.resolverOf(ExtensionDefinitionParser.java:478)\n\tat org.mule.runtime.module.extension.internal.config.dsl.ExtensionDefinitionParser.lambda$parseAttributeParameter$23(ExtensionDefinitionParser.java:607)\n\tat org.mule.runtime.config.spring.dsl.spring.ComponentConfigurationBuilder$ValueExtractorAttributeDefinitionVisitor.onConfigurationParameter(ComponentConfigurationBuilder.java:287)\n\tat org.mule.runtime.config.spring.dsl.api.AttributeDefinition.accept(AttributeDefinition.java:52)\n\tat org.mule.runtime.config.spring.dsl.spring.ComponentConfigurationBuilder$ConfigurableAttributeDefinitionVisitor.onMultipleValues(ComponentConfigurationBuilder.java:229)\n\tat org.mule.runtime.config.spring.dsl.api.AttributeDefinition.accept(AttributeDefinition.java:72)\n\tat org.mule.runtime.config.spring.dsl.spring.ComponentConfigurationBuilder.processConfiguration(ComponentConfigurationBuilder.java:71)\n\tat org.mule.runtime.config.spring.dsl.spring.CommonBeanDefinitionCreator.processObjectConstructionParameters(CommonBeanDefinitionCreator.java:266)\n\tat org.mule.runtime.config.spring.dsl.spring.CommonBeanDefinitionCreator.processComponentDefinitionModel(CommonBeanDefinitionCreator.java:220)\n\tat org.mule.runtime.config.spring.dsl.spring.CommonBeanDefinitionCreator.handleRequest(CommonBeanDefinitionCreator.java:107)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:40)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:44)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:44)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:44)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:44)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:44)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:44)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:44)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:44)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:44)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionFactory.resolveComponentBeanDefinition(BeanDefinitionFactory.java:197)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionFactory.resolveComponent(BeanDefinitionFactory.java:153)\n\tat org.mule.runtime.config.spring.dsl.spring.BeanDefinitionFactory.resolveComponentRecursively(BeanDefinitionFactory.java:144)\n\tat org.mule.runtime.config.spring.MuleArtifactContext.lambda$createApplicationComponents$47(MuleArtifactContext.java:311)\n\tat org.mule.runtime.config.spring.dsl.model.ApplicationModel.executeOnComponentTree(ApplicationModel.java:603)\n\tat org.mule.runtime.config.spring.dsl.model.ApplicationModel.lambda$executeOnComponentTree$18(ApplicationModel.java:601)\n\tat java.util.ArrayList.forEach(ArrayList.java:1249)\n\tat org.mule.runtime.config.spring.dsl.model.ApplicationModel.executeOnComponentTree(ApplicationModel.java:600)\n\tat org.mule.runtime.config.spring.dsl.model.ApplicationModel.lambda$executeOnComponentTree$18(ApplicationModel.java:601)\n\tat java.util.ArrayList.forEach(ArrayList.java:1249)\n\tat org.mule.runtime.config.spring.dsl.model.ApplicationModel.executeOnComponentTree(ApplicationModel.java:600)\n\tat org.mule.runtime.config.spring.dsl.model.ApplicationModel.executeOnEveryMuleComponentTree(ApplicationModel.java:579)\n\tat org.mule.runtime.config.spring.MuleArtifactContext.createApplicationComponents(MuleArtifactContext.java:303)\n\tat org.mule.runtime.config.spring.LazyMuleArtifactContext.createComponents(LazyMuleArtifactContext.java:66)\n\tat org.mule.runtime.config.spring.LazyMuleArtifactContext.initializeComponent(LazyMuleArtifactContext.java:117)\n\tat org.mule.runtime.config.spring.LazyMetadataService.initializeComponent(LazyMetadataService.java:100)\n\tat org.mule.runtime.config.spring.LazyMetadataService.getMetadata(LazyMetadataService.java:58)\n\tat com.mulesoft.agent.services.metadata.MuleAgentMetadataService.lambda$getMetadata$1(MuleAgentMetadataService.java:66)\n\tat com.mulesoft.agent.services.metadata.MuleAgentMetadataService.withMetadataManager(MuleAgentMetadataService.java:103)\n\tat com.mulesoft.agent.services.metadata.MuleAgentMetadataService.getMetadata(MuleAgentMetadataService.java:66)\n\tat com.mulesoft.agent.external.handlers.metadata.MetadataRequestHandler.getMetadata(MetadataRequestHandler.java:193)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat java.lang.reflect.Method.invoke(Method.java:497)\n\tat org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)\n\tat org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151)\n\tat org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171)\n\tat org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:152)\n\tat org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104)\n\tat org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:387)\n\tat org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:331)\n\tat org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:103)\n\tat org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:271)\n\tat org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)\n\tat org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)\n\tat org.glassfish.jersey.internal.Errors.process(Errors.java:315)\n\tat org.glassfish.jersey.internal.Errors.process(Errors.java:297)\n\tat org.glassfish.jersey.internal.Errors.process(Errors.java:267)\n\tat org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:297)\n\tat org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:254)\n\tat org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1028)\n\tat org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:372)\n\tat org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:381)\n\tat org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:344)\n\tat org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:221)\n\tat org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696)\n\tat org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1515)\n\tat com.mulesoft.agent.rest.RequestLoggingFilter.doFilter(RequestLoggingFilter.java:95)\n\tat org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486)\n\tat org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:519)\n\tat org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:138)\n\tat org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:564)\n\tat org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:213)\n\tat org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1097)\n\tat org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:448)\n\tat org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:175)\n\tat org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1031)\n\tat org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136)\n\tat org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)\n\tat org.eclipse.jetty.server.Server.handle(Server.java:446)\n\tat org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:271)\n\tat org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:246)\n\tat org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)\n\tat org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)\n\tat org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)\n\tat java.lang.Thread.run(Thread.java:745)\nCaused by: java.lang.ClassNotFoundException: org.mule.extension.db.api.param.TransactionIsolation\n\tat java.net.URLClassLoader.findClass(URLClassLoader.java:381)\n\tat org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:420)\n\tat org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:382)\n\tat java.lang.Class.forName0(Native Method)\n\tat java.lang.Class.forName(Class.java:348)\n\tat org.apache.commons.lang3.ClassUtils.getClass(ClassUtils.java:909)\n\tat org.mule.metadata.java.api.utils.JavaTypeUtils.getType(JavaTypeUtils.java:39)\n\t... 89 more\n"""", ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10814","10/20/2016 20:26:38",1,"Unify coordinate language for ArtifactIsolatedClassLoaderBuilder ""The coordinate language should be such as: If the optionals are not provided they should be assumed."""," :::: ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10818","10/20/2016 22:28:08",2,"ArtifactIsolatedClassLoaderBuilder to add URLs to the application classloader ""The ArtifactIsolatedClassLoaderBuilder needs to provide a way to add jars to the application classloader (jars not maven coordinates) ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10821","10/21/2016 15:48:24",1,"Allow to enable/disable Tooling Runtime REST API verbose by query param ""Allow to pass a query param to enable verbose mode so errors and failures will be added to response on Tooling Runtime REST API.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10822","10/21/2016 15:49:58",0,"Remove auto-generated REST Client for Tooling Runtime Client ""It has limitations, implement it directly instead of auto-generating it from RAML.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10823","10/21/2016 15:52:01",8,"Integrate Metadata Services to Tooling REST API ""Integrate Metadata Services to REST API.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10825","10/21/2016 20:47:13",2,"Move logic for temporary application deployment from Agent to Mule ""Tooling Service in Mule should handle the copy of the appLocation folder to a temporary folder in Mule and the same for an inputStream (with zip content).""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10828","10/24/2016 12:55:48",8,"Add support for resolving Metadata Keys to Tooling client ""Add support for resolving Metadata Keys to Tooling client""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10830","10/25/2016 14:36:50",1,"Add support for checking Mule's service when installed on Windows ""Linux script has support for checking the status of the process, on Windows there is no way to check the status of the service. Tanuki has support for it so it will be nice to include an 'status' command to the bat used on Windows. https://wrapper.tanukisoftware.com/doc/english/launch-win.html#standalone-status""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10836","10/25/2016 21:31:37",8,"Decouple DSL API from spring module ""Decouple DSL API from spring module""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10839","10/26/2016 20:49:40",5,"Operation Exceptions are not being exported. ""All declared exceptions in an operation signature must be exported in the extension manifest. For example having an operation with a signature like this one: The packages of SalamiException and CustomException must be exported."""," public Object consume(String operatioName) throws SalamiException, CustomException ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10844","10/27/2016 15:31:23",2,"Move serialization API from core to mule-api ""Move API defined on core/src/main/java/org/mule/runtime/core/api/serialization to mule-api project.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10850","10/27/2016 17:49:13",8,"Define replacement for MuleClient ""One of the idea is to include a mechanism that underneath uses the EL to execute functions that are the extensions operations. This must also include the review of the usages of MuleClient to see if it's really needed as it is today.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10851","10/27/2016 17:53:33",0,"Mule 4 - Operation UX ""Define how operation content parameter/s needs to be configured for all connectors taking into account: - Type checking - Auto-transformation of parameters - Consistency for different types of connectors - Have in mind the input parameters and the output parameters (http:listener, http:request) - Have in mind how http policies work and policiies in general""","",0,0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10852","10/27/2016 17:55:04",0,"Define configuration for input parameters for the content of operations ""Define how operation content parameter/s needs to be configured for all connectors.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10856","10/28/2016 19:28:34",8,"Improve WSC attachments UX ""We should add metadata support for attachments in the wsc. Input: * If at least one attachment is required the field should be marked as an ArrayType of binary types * if no attachment is required the list should be marked as NullType. Output: * If the output contains at list one attachment the output of the consume operation should be a multipart payload object. * if the output does not contains any attachments then the result should be an string type representing the xml body response. We should also check if its possible to remove the """"Content ID"""" required from the list of parameters and automatically add this field to the requesting body. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10857","10/28/2016 22:20:51",3,"Definition parser doesn't support Connection Providers with alias ""When setting an alias for a Connection Provider, the packaged connector won't deploy due to a definition parser error. This was tested in M3 but is reproducible in SNAPSHOT as well. The bug can be reproduced using [this repo commit|https://github.com/fbarrios/hello-world-connector-4.x/tree/6ac23ed73aa2aa150bd098ef512d8c267967b2e7]. The error logged in the runtime is the following: """," ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Failed to deploy artifact 'connectorApp', see below + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ org.mule.runtime.module.deployment.api.DeploymentException: Failed to deploy artifact [connectorApp] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:33) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployArtifact(DefaultArchiveDeployer.java:266) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployExplodedApp(DefaultArchiveDeployer.java:255) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:88) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:39) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher.deployExplodedApps(DeploymentDirectoryWatcher.java:243) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher.run(DeploymentDirectoryWatcher.java:307) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_73] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) ~[?:1.8.0_73] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) ~[?:1.8.0_73] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) ~[?:1.8.0_73] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_73] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_73] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_73] Caused by: org.mule.runtime.core.api.MuleRuntimeException: org.mule.runtime.module.deployment.api.DeploymentInitException: BeanDefinitionParsingException: Configuration problem: The element 'HelloWorldConnectorConfiguration-connection-connection' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/hello-world present on the classpath? Offending resource: URL [file:/Users/federicobarrios/mulesoft/runtimes/mule-standalone-4.0.0-M3/apps/connectorApp/org.mule.modules.helloworld.HelloWorldConnector.flows.xml] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:946) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:81) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:47) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] ... 13 more Caused by: org.mule.runtime.module.deployment.api.DeploymentInitException: BeanDefinitionParsingException: Configuration problem: The element 'HelloWorldConnectorConfiguration-connection-connection' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/hello-world present on the classpath? Offending resource: URL [file:/Users/federicobarrios/mulesoft/runtimes/mule-standalone-4.0.0-M3/apps/connectorApp/org.mule.modules.helloworld.HelloWorldConnector.flows.xml] at org.mule.runtime.module.deployment.internal.application.DefaultMuleApplication.init(DefaultMuleApplication.java:177) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:942) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:143) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:995) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:961) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:941) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:81) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:47) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] ... 13 more Caused by: org.mule.runtime.core.api.config.ConfigurationException: Configuration problem: The element 'HelloWorldConnectorConfiguration-connection-connection' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/hello-world present on the classpath? Offending resource: URL [file:/Users/federicobarrios/mulesoft/runtimes/mule-standalone-4.0.0-M3/apps/connectorApp/org.mule.modules.helloworld.HelloWorldConnector.flows.xml] (org.mule.runtime.core.api.lifecycle.InitialisationException) at org.mule.runtime.module.deployment.internal.artifact.ArtifactMuleContextBuilder.lambda$build$0(ArtifactMuleContextBuilder.java:244) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:143) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:995) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:961) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.ArtifactMuleContextBuilder.build(ArtifactMuleContextBuilder.java:220) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.application.DefaultMuleApplication.init(DefaultMuleApplication.java:171) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:942) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:143) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:995) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:961) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:941) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:81) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:47) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] ... 13 more Caused by: org.mule.runtime.core.api.lifecycle.InitialisationException: Configuration problem: The element 'HelloWorldConnectorConfiguration-connection-connection' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/hello-world present on the classpath? Offending resource: URL [file:/Users/federicobarrios/mulesoft/runtimes/mule-standalone-4.0.0-M3/apps/connectorApp/org.mule.modules.helloworld.HelloWorldConnector.flows.xml] at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:93) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:49) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:45) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:128) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.lifecycle.RegistryBrokerLifecycleManager.fireInitialisePhase(RegistryBrokerLifecycleManager.java:54) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.registry.AbstractRegistryBroker.initialise(AbstractRegistryBroker.java:45) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:123) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:77) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:74) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.invokePhase(MuleContextLifecycleManager.java:62) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:56) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.DefaultMuleContext.initialise(DefaultMuleContext.java:299) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:194) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:77) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.ArtifactMuleContextBuilder.lambda$build$0(ArtifactMuleContextBuilder.java:242) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:143) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:995) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:961) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.ArtifactMuleContextBuilder.build(ArtifactMuleContextBuilder.java:220) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.application.DefaultMuleApplication.init(DefaultMuleApplication.java:171) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:942) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:143) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:995) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:961) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:941) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:81) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:47) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] ... 13 more Caused by: org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: The element 'HelloWorldConnectorConfiguration-connection-connection' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/hello-world present on the classpath? Offending resource: URL [file:/Users/federicobarrios/mulesoft/runtimes/mule-standalone-4.0.0-M3/apps/connectorApp/org.mule.modules.helloworld.HelloWorldConnector.flows.xml] at org.springframework.beans.factory.parsing.FailFastProblemReporter.fatal(FailFastProblemReporter.java:60) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MissingParserProblemReporter.fatal(MissingParserProblemReporter.java:27) ~[mule-module-spring-config-4.0.0-M3.jar:4.0.0-M3] at org.springframework.beans.factory.parsing.ReaderContext.fatal(ReaderContext.java:68) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.parsing.ReaderContext.fatal(ReaderContext.java:55) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.NamespaceHandlerSupport.findParserForElement(NamespaceHandlerSupport.java:85) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:74) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleHierarchicalBeanDefinitionParserDelegate.parseCustomElement(MuleHierarchicalBeanDefinitionParserDelegate.java:164) ~[mule-module-spring-config-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.config.spring.MuleHierarchicalBeanDefinitionParserDelegate.lambda$parseCustomElement$1(MuleHierarchicalBeanDefinitionParserDelegate.java:156) ~[mule-module-spring-config-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.config.spring.dsl.spring.BeanDefinitionFactory.resolveComponentRecursively(BeanDefinitionFactory.java:138) ~[mule-module-spring-config-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.config.spring.MuleHierarchicalBeanDefinitionParserDelegate.parseCustomElement(MuleHierarchicalBeanDefinitionParserDelegate.java:131) ~[mule-module-spring-config-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.config.spring.MuleHierarchicalBeanDefinitionParserDelegate.parseCustomElement(MuleHierarchicalBeanDefinitionParserDelegate.java:208) ~[mule-module-spring-config-4.0.0-M3.jar:4.0.0-M3] at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1417) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:180) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleBeanDefinitionDocumentReader.parseBeanDefinitions(MuleBeanDefinitionDocumentReader.java:72) ~[mule-module-spring-config-4.0.0-M3.jar:4.0.0-M3] at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:144) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:100) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:510) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:392) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleArtifactContext.loadBeanDefinitions(MuleArtifactContext.java:314) ~[mule-module-spring-config-4.0.0-M3.jar:4.0.0-M3] at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129) ~[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:541) ~[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:452) ~[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:112) ~[mule-module-spring-config-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:89) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:49) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:45) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:128) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.lifecycle.RegistryBrokerLifecycleManager.fireInitialisePhase(RegistryBrokerLifecycleManager.java:54) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.registry.AbstractRegistryBroker.initialise(AbstractRegistryBroker.java:45) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:123) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:77) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:74) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.invokePhase(MuleContextLifecycleManager.java:62) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:56) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.DefaultMuleContext.initialise(DefaultMuleContext.java:299) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:194) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:77) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.ArtifactMuleContextBuilder.lambda$build$0(ArtifactMuleContextBuilder.java:242) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:143) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:995) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:961) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.ArtifactMuleContextBuilder.build(ArtifactMuleContextBuilder.java:220) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.application.DefaultMuleApplication.init(DefaultMuleApplication.java:171) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:942) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:143) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:995) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:961) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:941) ~[mule-core-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:81) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:47) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-M3.jar:4.0.0-M3] ... 13 more ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10859","10/31/2016 13:54:13",1,"Change groupId and artifactId from muleesb to mule ""Change all references to artifacts called muleesb to mule""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10861","10/31/2016 15:30:22",13,"Support new Error Handling in Extensions API ""Implement what was written in the matching spec""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10863","10/31/2016 17:39:20",2,"Remove unused Generic on TypeBuilder ""MetadataTypeBuilder no longer uses generics it should be removed from its uses.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10865","10/31/2016 18:24:45",8,"Write try transaction tests ""We need to write unit/functional tests for {{ ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10868","11/01/2016 12:40:28",8,"Migrate scheduler module ""Quartz should be removed as a dependency of the runtime and be only on the scheduler service.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10870","11/01/2016 13:06:51",0,"Duplicate content-type created in response builder ""Content-type specified in http response builder and also in a property duplicates it: Calling this flow will receive 2 content-type headers returned: {quote} curl -v localhost:8081 * Connected to 127.0.0.1 (127.0.0.1) port 8081 (#0) > GET / HTTP/1.1 > Host: 127.0.0.1:8081 > User-Agent: curl/7.43.0 > Accept: */* > < HTTP/1.1 200 < Content-Length: 4 < Content-Type: application/json;charset=UTF-8 < Content-Type: application/xml;charset=UTF-8 {quote} """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10872","11/01/2016 14:00:58",2,"Add support on Tooling API to access remote Mule Runtime instance ""In addition to current support for accessing local mule instances it would have to allow access remove mule instances.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10873","11/01/2016 15:51:13",0,"Classloading: Drop unzipping mechanism when loading plugins ""Plugins shouldn't be unzipped when generating the filtered classloader, as it not only generates overhead while unzipping or doing the house keeping after the app it's stopped (aka: deleting the files), but it will be also helpful from a tooling point of view. This jira is part of a set of them where the main intent is to allow tooling to extract an ExtensionModel for any plugin, generating a classloader for that plugin in a simplified way (i.e.: no unzipping, nor cleaning after it was consumed)""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10877","11/01/2016 18:16:53",8,"SDK should be able to handle parameters as TypedValues ""The SDK should be able to request any parameter not just as a single value, but as a TypedValue. This should be the mechanism to obtain a DataType or MediaType of a given value.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10881","11/02/2016 13:37:05",1,"AsyncInterceptingMessageProcessor#processNextAsync not rethrowing exception ""Add the missing 'throw' in the catch block of processNextAsync""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10882","11/02/2016 14:44:14",0,"Unregister resources from Bitronix (ResourceRegistrar and ManagementRegistrar) ""In 3.6.2 the queue and resources are not being unregistered from the Bitronix registries. In 3.8.2 the queue is unregistered but the database connector is not, so redeploying an application with a db connector will cause a replication in the """"uniqueName"""". ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10885","11/02/2016 18:11:31",13,"Support operation UX ""Add support for the new Operation UX guidelines""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10887","11/03/2016 17:44:52",0,"GrizzlyHttpClient#createGrizzlyRequest: separate RequestBuilderCreation from its actual configuration ""Seaparate the creation and the configuration""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10889","11/04/2016 15:05:18",8,"Soap Service: Create interceptor to parse embedded attachment in SOAP response. ""Currently, we are parsing the response in different ways if the client supports MTOM or doesn't because a response with embedded attachments does not parse the attachments before building the final response body. We should try to create an interceptor that loads the attachments prior to the final response body gets build and then we can treat every response the same way.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10892","11/04/2016 18:38:32",0,"Classloading: MuleArtifactUrlConnection must be enhanced to support any mule artifact ""The current implementation `MuleArtifactUrlConnection` supports mule plugin artifacts but it has to be enhanced to support any other artifact such as: services, plugin servers, applications and domains. This will allow us to stop unzipping any artifact mule relies on when doing a deployment (no more exploded apps, neither plugins, neither ). To do so, we need to also be sure that mule stops writing in the local folders of any application (e.g.: `your-app/.mule/`). ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10893","11/04/2016 19:25:44",1,"Remove Studio distribution ""Remove Studio distribution""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10894","11/04/2016 20:44:53",2,"Add services support to domains ""Services are not currently available in domains.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10895","11/04/2016 20:45:35",0,"ConnectionValidationResult support for JSON serialization/deserialization ""Current version of the class has a field with the exception, this will not allow to be serialized and deserialized as JSON format when using it from Tooling Client.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10896","11/04/2016 21:14:15",8,"Extract classLoader model definition from artifact descriptors ""All the information used to create classLoaders is part of the artifact descriptors. This makes hard to used different ways to create artifact (zipped/unzipped) as the creation of the classLoaders is split on different places.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10900","11/07/2016 13:40:45",3,"Source callback parameters can be part of only one CallbackPhase ""Source Callback parameters have a {{CallbackParameterModelProperty}} indicating from which CallbackPhase (*OnError* or *OnSuccess*) they are a part. These parameters can be a part of both phases, but in the model property, just one phase is stored.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10901","11/07/2016 17:01:05",2,"@NullSafe does not work on POJO fields. ""Having a POJO that is not parameter group when using the @NullSafe annotation in one of its @Parameter fields is not injecting anything. We want the same behaviour that we have for operation @Parameters in this NullSafe annotated fields""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10902","11/07/2016 17:15:55",1,"Fix TCP tests to use system property instead of a flow var ""The following tests are still using a flow var to set the protocol and as a result are not actually being parameterised: TcpSendAndReceivePojoTestCase TcpSendAndReceiveStringTestCase""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10904","11/07/2016 19:46:43",5,"Provide a way for the extension developer to inject mule default encoding ""Provide a way for the extension developer to inject mule default encoding so we avoid code like this: We could annotate a parameter with @Encoding to automatically supply default mule's encoding if there is no value present."""," public void initialise() throws InitialisationException { if (encoding == null) { encoding = muleContext.getConfiguration().getDefaultEncoding(); } } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10905","11/07/2016 20:49:45",5,"Add support for implicit Keys Resolvers for Enum and Boolean MetadataKeyIds ""Add support for implicit Keys Resolvers for Enum and Boolean MetadataKeyIds""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10907","11/08/2016 14:43:01",2,"Function Types should be exposed as the generic type of it and not as a Function ""*Function Types should be exposed as the generic type of it and not as a Function* * In the same way as the {{ParameterResolver}}, the Type that appears in the Extension Model should not be the {{Function<>}} type, instead should be the generic type of it, for example: ** {{Function}}, should be exposed as {{SomePojo}}""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10910","11/08/2016 19:04:45",2,"Remove BlockingMessageProcessor since it's not actually used ""Right now, the core provider defining the block component is using a specific type definition and an object factory. However, the object type from the latter is a MessageProcessorChain while the type definition a BlockMessageProcessor.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10914","11/09/2016 13:12:38",2,"Change ResponseAssertionMessageProcessor to use tasks instead of threads for assertions ""When dispatching a task to a Scheduler, if the dispatching tasks finishes before the dispatched task starts, the dispatched one may end up running in the same thread as the dispatcher. To avoid this, we should put some token in the thread local of the thread running the task and use that for assertion, instead of asserting of the threads identity. This is causing flakyness in NonBlockingFullySupportedFunctionalTestCase""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10918","11/09/2016 18:56:05",0,"Until successful is losing session vars ""As a consequence of MULE-10100 where we prevented until successful from returning an event copy, the session vars altered within such component are lost. We copy the flow variables but not session ones which is causing the trouble.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10919","11/09/2016 19:14:37",8,"Parameter group resolution is super coupled to everything ""ParameterGroup resolution is coupled to model properties on each parameter which makes it super coupled to a lot of components. We need a way to do the same thing without being tied to the model properties of a parameter model. An awful example of this is the NullSafeValueResolverWrapper. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10920","11/09/2016 19:31:08",1,"Allow to configure timeouts for operations and connections on Tooling Client ""There is no way to set up timeout for tooling operations and connections to remote service too.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10921","11/09/2016 20:23:14",0,"FtpWork never processes file if lock is not granted ""When an FtpWork (FtpMessageReceiver) runs and cannot get the lock for the file (e.g. another FtpWork got the lock for another file with the same name; in another folder), the work finishes without removing the file from the scheduleFiles, causing it to never be processed. ""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10922","11/09/2016 20:31:55",2,"DefaultScheduler periodic scheduling methods not working ""When using DefaultSchedulers methods scheduleAtFixedRate or scheduleWithFixedDelay, the task is only executed the first time and never again.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10923","11/09/2016 21:32:45",5,"Add ShutdownHook to MuleDeployment rule ""Add ShutdownHook to MuleDeployment rule to be sure that aren't left running any runtime when a test is aborted doing a """"control + c""""""","",0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10925","11/10/2016 10:50:48",8,"Support http proxy policy injection without pointcuts ""This is full support for http proxy policies including: - Variables scoping - Source logic - Source output modification - Request logic - Request content modification ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10927","11/10/2016 10:57:53",8,"Support http policy specific pointcuts ""This is to add support in HTTP connector to provide information specific to it to be able to apply pointcuts specific to HTTP""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10928","11/10/2016 11:00:11",8,"Support parametrization of policies ""Policies support parametrization. For instance throttling policies allows to parametrize the number of request per seconds based on user input. This is to define a mechanism to define the parametrization of the policies when applied. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10930","11/10/2016 13:03:47",8,"Change Tooling REST API to allow doing connectivity testing using ConnectivityTestingServiceBuilder ""It will be required to expose (temporary) the service to do connectivity testing without deploying an application, therefore we will have to expose ConnectivityTestingServiceBuilder through this API.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10931","11/10/2016 13:05:45",8,"Tooling API allow to do connectivity testing using ConnectivityTestingServiceBuilder ""Expose API for MULE-10930 to allow doing connectivity testing without deploying an application. This API will be changed later to also do deploy for the application as the current API in client is done.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10932","11/10/2016 13:13:37",2,"Tooling API should allow to generate an Extension Model for a plugin ""Allow to generate the extension model for a plugin from Tooling API client.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10933","11/10/2016 13:18:22",2,"Add internal support for retrieving metadata in Tooling Client ""Tooling Client API would need to use for DataSense the Metadata for an operation, this operation would need to be implemented internally in the REST Client inside the tooling but should not be exposed to external clients.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10937","11/10/2016 14:26:03",8,"Separate deployment artifact implementations from deployment module ""Deployment model currently contains both deployment artifact implementations (artifact and factories) and deployment management logic (directory watcher, listeners, etc) We need to have deployment artifacts in a different module so tooling can use it without having to depend on the deployment logic, which has to be used on the container only""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10938","11/10/2016 14:34:07",1,"Add DW plugin to our tests dependencies ""We need to make it possible for everyone to use DW on their tests from now on.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10939","11/10/2016 14:44:27",8,"Cover all DW/MEL scenarios for ExpressionManager in tests ""Define infrastructure to run test in both modes.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10940","11/10/2016 14:49:29",2,"Define interaction between DataType and MetadataType (function) ""Need to start defining functions as bindings so we need to define how to type them.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10941","11/10/2016 15:43:36",2,"Review validate and exception uses ""The validate method used to throw an InvalidExpressionException so most uses remain that way, plus they rely on that to determine the failure instead of analysing the ValidationResult. We need to refactor all its uses.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10943","11/10/2016 17:53:11",3,"Parameter placement order have two different default values ""*Parameter placement have two different default values* * If a parameter doesn't use the {{@Placement}} annotation, the default order is {{0}} * If the parameter use the {{@Placemente}} annotation, but without defining the order value, the value to be configured in the ext model will be {{-1}} *Review the same for:* * Tabs * Groups * Other layout information with default values""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10944","11/10/2016 17:55:29",0,"Some hamcrest assertions are using mockito matchers ""Fix the tests""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10945","11/10/2016 18:07:34",1,"Populate Layout information for Transactional Action parameters ""*Populate Layout information for Transactional Action parameters* * The {{Transactional Action}} parameter is injected when using a {{Transactional Connection}}, due that is injected by the SDK and not defined by the extension developer, there is no chance to be able to define a custom layout information. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10947","11/11/2016 15:31:22",0,"Support mutation of java objects ""When working with policies, it needs to be possible to mutate the request attributes or the payload that is going to be sent by the http:request operation or the response of the http:listener source. It must be possible to reset headers, add headers, remove headers from attributes.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10951","11/14/2016 02:20:06",0,"Tooling client does not support application deployment if there is not default domain ""In order to test this you can remove the default domain from domains folder in mule installation. org.mule.tooling.service.api.DeploymentException: Couldn't deploy the application at org.mule.tooling.agent.rest.client.RestAgentToolingService.deployApplication(RestAgentToolingService.java:112) at org.mule.tooling.client.internal.DefaultToolingRuntimeClient.deployApplication(DefaultToolingRuntimeClient.java:61) at org.mule.integration.test.tooling.client.ConnectivityTestCase.deployEmailApp(ConnectivityTestCase.java:144) at org.mule.integration.test.tooling.client.ConnectivityTestCase.cachingSuccessConnectionTesting(ConnectivityTestCase.java:112) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runner.JUnitCore.run(JUnitCore.java:137) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) Caused by: org.mule.tooling.agent.rest.client.exceptions.ToolingServiceAPIException: HTTP 500 Internal Server Error{""""errorType"""":""""class org.mule.runtime.deployment.model.api.DeploymentException"""",""""errorMessage"""":""""Domain \u0027default\u0027 has to be deployed in order to deploy Application \u0027tooling-4a47ffd0-aa10-11e6-af37-a0999b1354f3\u0027"""",""""errorDetail"""":""""org.mule.runtime.deployment.model.api.DeploymentException: Domain \u0027default\u0027 has to be deployed in order to deploy Application \u0027tooling-4a47ffd0-aa10-11e6-af37-a0999b1354f3\u0027\n\tat org.mule.runtime.module.deployment.internal.application.DefaultApplicationFactory.createAppFrom(DefaultApplicationFactory.java:91)\n\tat org.mule.runtime.module.deployment.internal.application.DefaultApplicationFactory.createArtifact(DefaultApplicationFactory.java:79)\n\tat org.mule.runtime.module.tooling.internal.DefaultToolingService.createApplication(DefaultToolingService.java:57)\n\tat com.mulesoft.agent.services.tooling.MuleAgentToolingService.deployToolingApplication(MuleAgentToolingService.java:233)\n\tat com.mulesoft.agent.services.tooling.MuleAgentToolingService.deployToolingApplication(MuleAgentToolingService.java:170)\n\tat com.mulesoft.agent.external.handlers.tooling.ToolingRequestHandler.lambda$deployToolingApplication$2(ToolingRequestHandler.java:150)\n\tat com.mulesoft.agent.util.ResponseHelper.response(ResponseHelper.java:88)\n\tat com.mulesoft.agent.external.handlers.tooling.ToolingRequestHandler.deployToolingApplication(ToolingRequestHandler.java:148)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat java.lang.reflect.Method.invoke(Method.java:497)\n\tat org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)\n\tat org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151)\n\tat org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171)\n\tat org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:152)\n\tat org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104)\n\tat org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:387)\n\tat org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:331)\n\tat org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:103)\n\tat org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:271)\n\tat org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)\n\tat org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)\n\tat org.glassfish.jersey.internal.Errors.process(Errors.java:315)\n\tat org.glassfish.jersey.internal.Errors.process(Errors.java:297)\n\tat org.glassfish.jersey.internal.Errors.process(Errors.java:267)\n\tat org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:297)\n\tat org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:254)\n\tat org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1028)\n\tat org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:372)\n\tat org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:381)\n\tat org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:344)\n\tat org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:221)\n\tat org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696)\n\tat org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1515)\n\tat com.mulesoft.agent.rest.RequestLoggingFilter.doFilter(RequestLoggingFilter.java:95)\n\tat org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486)\n\tat org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:519)\n\tat org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:138)\n\tat org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:564)\n\tat org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:213)\n\tat org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1097)\n\tat org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:448)\n\tat org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:175)\n\tat org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1031)\n\tat org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136)\n\tat org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)\n\tat org.eclipse.jetty.server.Server.handle(Server.java:446)\n\tat org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:271)\n\tat org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:246)\n\tat org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358)\n\tat org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601)\n\tat org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532)\n\tat java.lang.Thread.run(Thread.java:745)\n""""} at org.mule.tooling.agent.rest.client.tooling.applications.Applications.put(Applications.java:83) at org.mule.tooling.agent.rest.client.RestAgentToolingService.deployApplication(RestAgentToolingService.java:106) ... 34 more""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10953","11/14/2016 12:08:43",1,"Provide a lookup method for SchedulerService in MuleContext ""This is to avoid performing the lookup in the registry and handling RegistationException each time the service is needed.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10955","11/14/2016 12:37:13",1,"When shutting down a scheduler, it takes the timeout time even in there's no pending work to do ""This causes unneeded delay in the execution of the tests, as well as a potential issue when shutting down applications.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10957","11/14/2016 15:00:21",2,"Error accessing variables within a transform element ""When trying to access the variables within a DW script, it fails because of an issue handling TypedValue class. It seems that the problem is related to the fact that the variables binding is a type value with other type values inside.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10958","11/14/2016 15:48:28",13,"Support Sources in JMS Extension ""Support Sources in JMS Extension""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10959","11/14/2016 15:49:13",13,"Support Transactions in JMS Extension ""Support Transactions in JMS Extension * Implies the support of binding sessions to the transaction thread * How the transactional action is related to the ACK Modes * Make it happen""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10960","11/14/2016 15:49:33",8,"Support error handling scenarios between policies and flows ""This is to properly define behaviour and support the error scenarios when executing the next operation. What error type propagate when the flow/operation execution fails?. Should we allow the user to handle error in the policies for request operations?.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10966","11/14/2016 17:06:36",1,"Artifact plugins must include full dependency information ""Artifact plugins currently provide the list of plugins names that are required as dependencies in order to deploy a given plugin. That name is not enough as there could be multiple versions of a given plugin, which could or could not match with a the required version. So, plugins must include the complete information of to identify another plugin. Each dependency must include, instead of the name, the folowing information: """," groupIp:artifactId:version ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10968","11/14/2016 18:00:22",5,"WSC can't load embedded wsdl schemas on the types tag. ""Having a WSDL with a types tag like this one: that defines an inner schema in the wsdl file, we are not taking it in count and all the types that are described there are not going to be loaded."""," .. ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10969","11/14/2016 19:12:21",3,"HTTP UI improvements ""HTTP Request: - """"API Configuration"""" -> """"API Specification"""" - """"Configuration overrides"""" should be moved to their own tab instead of going under """"Advanced"""". - path should default to """"/"""" - host should have an example value of 0.0.0.0 - port should have an example value of 8081 - charset is represented as an object plus a checkbox which is called """"present"""" - not sure what the fix is, but need to discuss and clean this up. - Response Settings should be a new Response tab, not a group HTTP Listener: - HTTP path should be on the top of the form - charset is represented as an object plus a checkbox which is called """"present"""" (see above) - configuration overrides should be a group, not a tab (especially since it only has one configuration option) - Response Settings should be a new Response tab, not a group - Error Response Settings should be a new Error Response tab, not a group""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10970","11/15/2016 12:45:33",8,"Make all message processor AnnotatedObject ""We need to guarantee that annotations are available for most components since having that in place will allow us to later add new features, for example.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10974","11/15/2016 16:27:59",2,"JDK Resources are not being found when running a test with MuleArtifactClassloader ""Running a test that requires a resource bundle that lives in the JDK, when the classloader cooked for testing is not delegating the look up of resources to its parent if the resource is not found.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10975","11/15/2016 17:43:51",0,"AbstractAggregator eventGroups object store ignores the object store configuration in the registry ""On AbstractAggregator#internalEventsGroupsObjectStoreFactory the store should be looked up from the registry rather than from the deprecated static methods. That way, when a core extension replaces the ObjectStores in the registry, the aggregator takes those instead of the defaults.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10977","11/15/2016 18:35:12",3,"java.lang.Object is persisted as a type in the extension model JSON ""The following JSON is generated: When the ExtensionModelJsonSerializer travels all the MetadataTypes for registering purposes, it ends up registering everything, even types such as java.lang.Object."""," """"types"""": [ { """"format"""": """"java"""", """"type"""": """"Object"""", """"annotations"""": { """"typeId"""": """"java.lang.Object"""", """"classInformation"""": { """"hasDefaultConstructor"""": true, """"isInterface"""": false, """"isInstantiable"""": true, """"isAbstract"""": false, """"isFinal"""": false, """"implementedInterfaces"""": [], """"parent"""": """""""", """"genericTypes"""": [] }, """"typeAlias"""": { """"value"""": """"Object"""" } }, """"fields"""": [] }, ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10980","11/15/2016 19:26:18",1,"Content parameters should not be available as attributes in the DSL ""What the title says. Applies to content parameters""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10985","11/16/2016 19:36:30",2,"Parallel deployment causes runtime contention on Logger. ""We found that after the deployment worker threads are being blocked on """"org.mule.module.launcher.log4j2.LoggerContextCache.getLoggerContext(ClassLoader)"""" this was introduced when the feature for parallel deployment was introduced.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10989","11/17/2016 03:20:15",0,"Incorrect OS encoding displayed in the console ""h3. Description As a result of a change in MULE-7655, the OS Encoding is being reported as the system's File Separator. It would be ideal if the Encoding was displayed. h3. Steps to reproduce # Start up a mule application # Observe the Application reports the OS Encoding as '/' Log: {code} ********************************************************************** * Application: default * * OS encoding: /, Mule encoding: UTF-8 * * * * Agents Running: * * Batch module default engine * * JMX Agent * * Wrapper Manager * ********************************************************************** {code} h3. Workaround Ignore the output and manually check the file.encoding property. h3. Notes See: {{org.mule.util.ApplicationStartupSplashScreen.*doHeader*}} (_Line: 23_) {code:java} protected void doHeader(MuleContext context) { header.add(""""Application: """" + context.getConfiguration().getId()); header.add(String.format(""""OS encoding: %s, Mule encoding: %s"""", SystemUtils.FILE_SEPARATOR, context.getConfiguration().getDefaultEncoding())); header.add("""" """"); } {code} """," ********************************************************************** * Application: default * * OS encoding: /, Mule encoding: UTF-8 * * * * Agents Running: * * Batch module default engine * * JMX Agent * * Wrapper Manager * ********************************************************************** protected void doHeader(MuleContext context) { header.add(""""Application: """" + context.getConfiguration().getId()); header.add(String.format(""""OS encoding: %s, Mule encoding: %s"""", SystemUtils.FILE_SEPARATOR, context.getConfiguration().getDefaultEncoding())); header.add("""" """"); } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10995","11/17/2016 17:02:15",2,"Negative threadWaitTimeout used with SEDA processing strategy fails rather than waiting forever to enqueue. ""Negative threadWaitTimeout used with SEDa processing strategy fails rather than waiting forever.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10996","11/17/2016 17:28:07",0,"Content-Length header case conflicts with streaming ""Because we are reacting to having """"Content-Length"""" as header (for querying and removal) having a different case has undesired consequences in terms of streaming. This happens for all headers so we need a general approach.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-10999","11/17/2016 19:47:38",0,"Update xmlbeans dependency to our fork in mule-common ""We've created a fork of xmlbeans to fix an issue since it has no support anymore. Now the mule-common dependency should be updated.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11001","11/17/2016 20:09:11",2,"ArtifactClassLoaderRunner - Lookup policies for Plugin in Region should honor dependencies ""The region build by the isolated class loader factory is not considering the dependencies between plugins therefore plugins are ended up with a lookup policy CHILD_FIRST instead of CHILD_ONLY and PARENT_FIRST (first one if the plugin doesn't depend in another one that goes to the region too and the second one is when the plugin declares the dependency so it can access to a the dependent plugin exported classes).""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11007","11/17/2016 22:11:22",5,"Decouple MulePluginModelJsonSerializer from mule-api into a mule-api-persistence module ""The mule-api project holds a representation of a Mule plugin model and it's serializer from/to JSON. Ideally, that class should be moved to a different project, similar to what the mule-extensions-api has, where there's the domain objects in api, and a layer of persistence in a different module""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11016","11/18/2016 17:25:33",2,"Race condition when running repeatable scheduled jobs ""When using scheduledWithFixedDelay, a race cpndition may occur that causes the job to not run because a check is made before the state of the task is updated.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11018","11/18/2016 17:46:03",2,"Allow to give names to the Schedulers retrieved from SchedulerService ""Having a name in the scheduler will help generate better log entries. The tasks should also have some indication of where they were scheduled. Also pass flow name via `org.mule.runtime.core.api.processor.strategy.ProcessingStrategyFactory#create` and use for processing strategy schedulers.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11024","11/21/2016 14:39:04",8,"Move schema-related objects from extensions-spring-support to extensions-api ""Schema classes from extensions-spring-support are mandatory when using XML extensions, as they are consumed through SPI when generating schemas in the ModuleDelegatingEntityResolver class (particularly, the one implementing SchemaResourceFactory interface, SchemaXmlResourceFactory). Without this refactor, it's impossible to consume this class (SchemaXmlResourceFactory) from the testing framework (AbstractMuleTestCase) through SPI, failing when running the tests.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11026","11/21/2016 15:24:06",1,"Quartz scheduler is too verbose ""Every time you start or stop Mule, you get a lot of log lines from the Scheduler service. The log should be reduced to only the necessary lines. Start Log: Stop log: """," INFO 2016-11-21 12:18:37,239 [WrapperListener_start_runner] org.mule.service.scheduler.internal.DefaultSchedulerService: Starting org.mule.service.scheduler.internal.DefaultSchedulerService@243c2036... INFO 2016-11-21 12:18:37,289 [WrapperListener_start_runner] org.quartz.impl.StdSchedulerFactory: Using default implementation for ThreadExecutor INFO 2016-11-21 12:18:37,319 [WrapperListener_start_runner] org.quartz.core.SchedulerSignalerImpl: Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl INFO 2016-11-21 12:18:37,320 [WrapperListener_start_runner] org.quartz.core.QuartzScheduler: Quartz Scheduler v.2.2.3 created. INFO 2016-11-21 12:18:37,323 [WrapperListener_start_runner] org.quartz.simpl.RAMJobStore: RAMJobStore initialized. INFO 2016-11-21 12:18:37,324 [WrapperListener_start_runner] org.quartz.core.QuartzScheduler: Scheduler meta-data: Quartz Scheduler (v2.2.3) 'SchedulerService' with instanceId 'NON_CLUSTERED' Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. NOT STARTED. Currently in standby mode. Number of jobs executed: 0 Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 1 threads. Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered. INFO 2016-11-21 12:18:37,324 [WrapperListener_start_runner] org.quartz.impl.StdSchedulerFactory: Quartz scheduler 'SchedulerService' initialized from an externally provided properties instance. INFO 2016-11-21 12:18:37,324 [WrapperListener_start_runner] org.quartz.impl.StdSchedulerFactory: Quartz scheduler version: 2.2.3 INFO 2016-11-21 12:18:37,325 [WrapperListener_start_runner] org.quartz.core.QuartzScheduler: Scheduler SchedulerService_$_NON_CLUSTERED started. INFO 2016-11-21 12:18:37,334 [WrapperListener_start_runner] org.mule.service.scheduler.internal.DefaultSchedulerService: Started org.mule.service.scheduler.internal.DefaultSchedulerService@243c2036 INFO 2016-11-21 12:28:20,555 [WrapperListener_stop_runner] org.mule.service.scheduler.internal.DefaultSchedulerService: Stopping org.mule.service.scheduler.internal.DefaultSchedulerService@7952df0f... INFO 2016-11-21 12:28:20,555 [WrapperListener_stop_runner] org.quartz.core.QuartzScheduler: Scheduler SchedulerService_$_NON_CLUSTERED shutting down. INFO 2016-11-21 12:28:20,555 [WrapperListener_stop_runner] org.quartz.core.QuartzScheduler: Scheduler SchedulerService_$_NON_CLUSTERED paused. INFO 2016-11-21 12:28:20,991 [WrapperListener_stop_runner] org.quartz.core.QuartzScheduler: Scheduler SchedulerService_$_NON_CLUSTERED shutdown complete. INFO 2016-11-21 12:28:20,992 [WrapperListener_stop_runner] org.mule.service.scheduler.internal.DefaultSchedulerService: Stopped org.mule.service.scheduler.internal.DefaultSchedulerService@7952df0f ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11029","11/21/2016 16:27:51",5,"Parsers are not validating the presence of a required parameter ""For instance, has a required color parameter but *null* is assigned. See SubTypesMappingParserTestCase""","org.mule.test.subtypes.extension.CarDoor",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11031","11/21/2016 18:47:30",2,"Cannot reference flowVars directly using DW ""Though it is possible to have an expression like """"variables.myFlowVar"""", """"myFlowVar"""" directly does not work. This is a problem not only in terms of usability but compatibility since that was supported in MEL. The problem is that we are only binding the entire variable map but not each individually.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11033","11/21/2016 18:59:24",2,"NPE when deserializing NO_DYNAMIC_METADATA_AVAILABLE json response ""When trying to deserialize the following json message a NPE is thrown: NPE: """," { """"componentName"""": """""""", """"failures"""": [ { """"failureCode"""": """"NO_DYNAMIC_METADATA_AVAILABLE"""", """"message"""": """"Component [ProcessorId{flowName\u003d\u0027emailFlow\u0027, componentPath\u003d0}] is not a MetadataProvider or MetadataEntityProvider, no information available"""", """"reason"""": """"org.mule.runtime.core.internal.metadata.InvalidComponentIdException: Component [ProcessorId{flowName\u003d\u0027emailFlow\u0027, componentPath\u003d0}] is not a MetadataProvider or ..."""", """"failureComponent"""": """"COMPONENT"""" } ] } DEBUG 2016-11-21 15:14:53,230 [ForkJoinPool.commonPool-worker-1] org.mule.tooling.agent.rest.client.RestAgentToolingService: GET:tooling/applications/tooling-5a4ccad0-b016-11e6-b046-803f5d0a9b09/flows/emailFlow/components/0/metadata java.lang.NullPointerException at org.mule.runtime.extension.api.persistence.metadata.ComponentResultJsonSerializer$InputMetadata.toDescriptorResult(ComponentResultJsonSerializer.java:275) at org.mule.runtime.extension.api.persistence.metadata.ComponentResultJsonSerializer$ComponentMetadataResult.toDescriptorResult(ComponentResultJsonSerializer.java:140) at org.mule.runtime.extension.api.persistence.metadata.ComponentResultJsonSerializer$ComponentMetadataResult.toComponentMetadataResult(ComponentResultJsonSerializer.java:98) at org.mule.runtime.extension.api.persistence.metadata.ComponentResultJsonSerializer.deserialize(ComponentResultJsonSerializer.java:73) at org.mule.tooling.agent.rest.client.tooling.applications.applicationId.components.componentId.metadata.Metadata.get(Metadata.java:63) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11034","11/21/2016 19:34:12",2,"Change SubflowMessageProcessorChain visibility to public ""In MUnit, we need to know if a processor obtained from the registry is a SubflowMessageProcessorChain (the one inside SubflowMessageProcessorChainBuilder), in order to be able to set the mule context and initialize it. This is to cover the scenario where someone wants to run a subFlow from our java test cases (FunctionalMunitSuite).""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11036","11/21/2016 21:11:55",2,"Allow the creation of custom schedulers in the SchedulerService ""Allow the creation of custom schedulers with custom thread pools.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11037","11/21/2016 21:28:06",3,"Mule service scheduler log file is being created under domain scope ""Steps to reproduce: 1. Unpack Mule distribution 2. Start Mule with {{./bin/mule}} 3. Stop Mule 4. Run {{ls -la logs}} 5. A log file named {{mule-domain-mule-service-scheduler-4.0-SNAPSHOT}} is being created. The Scheduler Service log should be included in the {{mule_ee.log}}. If we want to have a different log for each service, it shouldn't be related to {{mule-domain}}""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11041","11/22/2016 14:59:11",3,"WS Consumer exceptions should implement ErrorMessageAwareException ""When receiving a WS error it is useful the SOAP response so the user has more details about the failure.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11047","11/22/2016 19:47:40",8,"Remove dependency to HTTP extension plugin once HTTP service is implemented and compatibility module support migrated to use the service ""mule-transport-module-support depends on HTTP extension. Once this dependency is removed and the module started to use the HTTP Service instead, the dependency as plugin to the HTTP extension plugin should be removed from the plugin.properties files in all the transports too.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11049","11/22/2016 20:56:56",1,"Remove SHITTY Maven plugin from build ""Remove shitty-maven-plugin ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11051","11/23/2016 12:50:10",1,"Logger cannot be parsed after deploying from tooling client ""App: Stacktrace: org.mule.tooling.service.api.DeploymentException: Couldn't deploy the application org.mule.tooling.service.api.DeploymentException: Couldn't deploy the application at org.mule.tooling.agent.rest.client.RestAgentToolingService.deployApplication(RestAgentToolingService.java:112) at org.mule.tooling.client.internal.DefaultToolingRuntimeClient.deployApplication(DefaultToolingRuntimeClient.java:61) at org.mule.tooling.client.agent.impl.DefaultAgentDeploymentTooling.deploy(DefaultAgentDeploymentTooling.java:18) at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction$1.run(TestConnectorConnectionFromMuleConfigAction.java:104) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) Caused by: org.mule.tooling.agent.rest.client.exceptions.ToolingServiceAPIException: HTTP 500 Internal Server Error{""""errorType"""":""""class org.mule.runtime.deployment.model.api.DeploymentInitException"""",""""errorMessage"""":""""MuleRuntimeException: Could not create mule application since lazy init is enabled but there are component in the configuration that are not parsed with the new mechanism logger,logger""""} at org.mule.tooling.agent.rest.client.tooling.applications.Applications.put(Applications.java:83) at org.mule.tooling.agent.rest.client.RestAgentToolingService.deployApplication(RestAgentToolingService.java:106) ... 4 more java.lang.Throwable: org.mule.tooling.service.api.DeploymentException: Couldn't deploy the application at org.mule.tooling.agent.rest.client.RestAgentToolingService.deployApplication(RestAgentToolingService.java:112) at org.mule.tooling.client.internal.DefaultToolingRuntimeClient.deployApplication(DefaultToolingRuntimeClient.java:61) at org.mule.tooling.client.agent.impl.DefaultAgentDeploymentTooling.deploy(DefaultAgentDeploymentTooling.java:18) at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction$1.run(TestConnectorConnectionFromMuleConfigAction.java:104) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) Caused by: org.mule.tooling.agent.rest.client.exceptions.ToolingServiceAPIException: HTTP 500 Internal Server Error{""""errorType"""":""""class org.mule.runtime.deployment.model.api.DeploymentInitException"""",""""errorMessage"""":""""MuleRuntimeException: Could not create mule application since lazy init is enabled but there are component in the configuration that are not parsed with the new mechanism logger,logger""""} at org.mule.tooling.agent.rest.client.tooling.applications.Applications.put(Applications.java:83) at org.mule.tooling.agent.rest.client.RestAgentToolingService.deployApplication(RestAgentToolingService.java:106) ... 4 more at org.mule.tooling.metadata.utils.MetadataUtils.showErrorMessage(MetadataUtils.java:393) at org.mule.tooling.metadata.utils.MetadataUtils.showTestConnectionErrorMessage(MetadataUtils.java:384) at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction.displayResultMessage(TestConnectorConnectionFromMuleConfigAction.java:136) at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction.run(TestConnectorConnectionFromMuleConfigAction.java:125) at org.mule.tooling.messageflow.dialog.GlobalElementDialog$1.widgetSelected(GlobalElementDialog.java:403) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.mule.tooling.ui.modules.core.widgets.editors.GlobalRefEditor$AddGlobalElementAction.run(GlobalRefEditor.java:434) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) at org.eclipse.equinox.launcher.Main.run(Main.java:1515) at org.eclipse.equinox.launcher.Main.main(Main.java:1488) ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11054","11/23/2016 18:09:02",1,"Mule embedded distribution artifactId should be mule-embedded ""Mule embedded distribution has the same artifactId as Mule root POM. Mule embedded distribution artifactId should be renamed from {{mule}} to {{mule-embedded}}""","",1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11056","11/23/2016 18:09:53",0,"Tooling client and mule applications share the same log file ""When the user performs test connectivity or fetching for metadata keys using the tooling client the logs are printed in the same file that mule uses for applications this create a little noise in the log files""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11057","11/23/2016 21:00:33",1,"Extensions in XML that use ExtensionModel requires java classes when should not be mandatory ""Extensions in XML that use ExtensionModel requires java classes when should not be mandatory""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11065","11/24/2016 14:46:02",2,"Make all configuration components AnnotatedObject ""We need to guarantee that annotations are available for most components since having that in place will allow us to later add new features, for example.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11066","11/24/2016 15:05:16",1,"Connection Exceptions should not be wrapped inside of a RetryPolicyException is a NoRetryPolicy is selected ""*Connection Exceptions should not be wrapped inside of a RetryPolicyException is a NoRetryPolicy is selected* * Nowadays if an Operation/ConnProvider/etc throws a {{ConnectionException}} this will trigger the *reconnection logic* (No matter if is configured with a {{NoRetryPolicy}}) * If the retry fails, it will throw a {{RetryPolicyExhaustedException}} although the retry policy is never executed and hides the true exception.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11069","11/24/2016 16:18:15",8,"Spike: Interception API ""Spike to research and define the Interception API""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11071","11/24/2016 16:21:50",8,"Change Mule Runtime Tooling Client API in order to allow Data Sense integration ""Change Runtime Tooling Client API in order to allow integration for DataSense resolution.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11072","11/24/2016 16:27:45",8,"Message Processors should be AnnotatedObject ""Make all MP to be AnnotatedObjects in order to store information needed by interception API later.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11073","11/24/2016 19:56:54",1,"SPI errors not caught in Abstract BuilderFactories ""Turns out, when a class is not found or a problem occurs doing the SPI loading, an Error is thrown. Because of this, our code using """"catch Exception"""" is ignored.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11074","11/24/2016 20:28:13",5,"Cannot use @ParameterGroup in sources ""When using a ParameterGroup on a source, and having a source callback which also takes a parameter group or a complex pojo, then the SDK tries ton inject the parameter group into the wrong field. An example to reproduce is the HttpListener""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11081","11/25/2016 16:42:29",8,"Add support to declare ErrorTypes at ConnectionProvider level ""*Add support to declare ErrorTypes at ConnectionProvider level* ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11084","11/25/2016 17:40:55",3,"Uptade Schema to allow parameters to be set in any order ""Uptade Schema to allow parameters to be set in any order""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11085","11/25/2016 17:47:10",1,"Calling getMuleContext on an Application that failed to deploy throws NPE ""When calling getMuleContext on an application that failed to deploy it throws a NullPointerException because artifactContext is null.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11086","11/25/2016 17:49:53",5,"Improve ErrorModel serialization in ExtensionModels ""*Improve ErrorModel serialization in ExtensionModels* * Nowadays in an {{ExtensionModel}} the error models are serialized at *extension* level and also in each *operation* that declares it, not only serializing the error identifier, serializing the entire error hierarchy. * Improve the serialization (like MetadataTypes) to have a normalized JSON where the error models from operations are just references to the errors defined at extension level.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11087","11/25/2016 19:03:09",13,"Introduce first iteration of new JMS connector ""Merge first iteration, including spec and PR review""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11092","11/25/2016 21:41:12",2,"Classloading: plugin.properties should be dropped in favour of mule-plugin.json ""Current status allow different ways of describing plugins: xml, sdk, or the plugin itself (by hand). There must be a single way to identify a plugin, which will be the JSON mule-plugin.json descriptor to treat every plugin in the same way.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11093","11/25/2016 22:26:44",5,"Add error handling capabilities to the new WSC ""Add error handling to WSC.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11097","11/28/2016 12:15:24",8,"Reactor does not handle RejectedExecutionException's ""https://github.com/reactor/reactor-core/issues/275""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11098","11/29/2016 14:01:38",5,"Change the TLS context of the WSC configuration for an Object that handles security. ""Currently, the WSC can be configured with a TLS context that is used to Sign and/or Encrypt the SOAP messages, but no TLS actions are performed and it's just used to take the parameters that the object provides. The TLS context should be replaced with some parameter group that has similar attributes but that is not related with TLS""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11099","11/29/2016 14:24:28",13,"Callback phases should be explicit in the SourceModel ""The callback phases in the sources are now implemented behind the covers using model properties. They should be explicitly modeled in the SourceModel , since that information is needed by the new policies""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11100","11/29/2016 15:19:07",5,"WSC: Use the HTTP service as default transport for HTTP urls. ""The WSC is using OKHttp to make the Http request when working through http, we should remove that and use the service that mule provides if no specific configuration is provided.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11102","11/29/2016 16:37:43",2,"Minor changes in Extension API Maven Plugin to automate the release ""Added the release profile with the gpg, sources and javadocs plugins. Added the update_deps_version.sh script. This will allow avoiding using the mvn versions:update-property plugin which it wasn't intended to change to versions that haven't been released yet. Change the verify.groovy scripts of the IT tests to obtain the artifact versions from the pom and not being hardcoded.""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11105","11/29/2016 20:29:18",1,"Move Scheduler interface to mule-api ""Move interface Scheduler to api so it can be used from other services.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11108","11/30/2016 00:03:38",1,"ParameterRoleTypeAnnotation only present for content fields ""When an ObjectType is generated through the Ext-API, a ParameterRoleTypeAnnotation is added for the content fields. We should always add them and specify BEHAVIOUR role for the other parameters""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11111","11/30/2016 15:26:47",1,"Validate invalid extension namespace ""Namespaces like `test` cause conflicts with mule namespaces, so we should avoid them""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11114","11/30/2016 18:52:27",1,"Add DataWeave to Runtime distribution ""Add DataWeave module to Mule distribution""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11118","11/30/2016 19:59:50",0,"Return a 5xx response when thread pool is exhausted instead of ignoring the request ""The http connector silently ignores requests when overloaded. Even if not all of them can be answered (with success or error), at least some of the failures should be returned as a 503 status code.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11125","12/01/2016 17:58:42",2,"XMLInputFactory allows inline DTDs by default ""Disable inline DTDs which could be insecure.""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11128","12/01/2016 18:37:02",0,"LocationExecutionContextProvider doesn't mask passwords ""When an exception occurs and LocationExecutionContextProvider provides the tag which produced the error, it isn't accounting for that element containing sensitive information. It should consider that the tag could: * Contain an URL with credentials * Contain a password attribute In either case, that information should be masked""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11144","12/05/2016 17:24:58",5,"Exclusive Parameters validations fails if the parameters uses an Alias ""*Exclusive Parameters validations fails if the parameters uses an Alias* * When having an {{ExclusiveParameters}} with *isOneRequired* and the parameters are annotated with {{@Alias}} the validation fails saying: Although these parameters are configured correctly. * In runtime, the values are configured correctly, but at validation time, the validation uses the names without the alias: {{ref, type}} instead of {{ref, class}}. * Classes to see {{OperationMessageProcessorObjectFactory}}, {{AbstractExtensionObjectFactory}}, {{ExtensionUtils#getMemberName()}} * This is can be reproduced adding the {{isOneRequired}} to the {{ObjectSource}} parameter of the {{customValidation}} operation of the {{Validations Extension}}""","Parameter group 'Validator' requires that one of its optional parameters should be set but all of them are missing. One of the following should be set: [ref, class]",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11148","12/05/2016 22:04:12",8,"NoSuchMetodError hangs JVM ""When throwing NoSuchMethodError from inside a custom processor the JVM asumes this is a critical error and hangs the VM. Showing the following logs: In order to reproduce this you could have a flow like: With the following implementation for the processor: Now if I were to wrap that error in a messaging exception Then the vm will not hang """," DEBUG 2016-12-05 18:58:17,223 [SimpleSchedulerService.01] org.mule.test.runner.classloader.IsolatedClassLoaderFactory$1: Loading class 'java.lang.VirtualMachineError' with 'CHILD_FIRST' on 'org.mule.test.runner.classloader.IsolatedClassLoaderFactory$1[launcher]@66a53104' DEBUG 2016-12-05 18:58:17,223 [SimpleSchedulerService.01] org.mule.test.runner.classloader.IsolatedClassLoaderFactory$1: Loaded class 'java.lang.VirtualMachineError' from parent: sun.misc.Launcher$AppClassLoader@18b4aac2 DEBUG 2016-12-05 18:58:17,223 [SimpleSchedulerService.01] org.mule.test.runner.classloader.IsolatedClassLoaderFactory$1: Loading class 'java.lang.ThreadDeath' with 'CHILD_FIRST' on 'org.mule.test.runner.classloader.IsolatedClassLoaderFactory$1[launcher]@66a53104' DEBUG 2016-12-05 18:58:17,223 [SimpleSchedulerService.01] org.mule.test.runner.classloader.IsolatedClassLoaderFactory$1: Loaded class 'java.lang.ThreadDeath' from parent: sun.misc.Launcher$AppClassLoader@18b4aac2 public static class NoSuchMethodErrorFailure implements Processor { @Override public Event process(Event event) throws MuleException { throw new NoSuchMethodError(); } } new MessagingException(event, new NoSuchMethodError()); ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11149","12/06/2016 12:16:31",2,"Unify application deployment on Agent and Tooling Runtime Client API to receive a URL ""Improve the experience of the API by only having one deployment method that receives a URL.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11150","12/06/2016 12:48:05",3,"Duplicated parameter generated for source with @OnSucces and @OnError annotated methods ""When writing a source with the following operations, an error is shown indicating that the model is not valid {code} [ERROR] error on execute: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: Extension 'OnlySources' defines the ImmutableSourceModel 'AnotherSource' which has parameters with repeated names. Offending parameters are: [message] {code} This is the Source code: {code:java} @EmitsResponse public class AnotherSource extends Source { @UseConfig private BasicExtensionConfig config; /** * Source Parameter description */ @Parameter private String anotherSourceParameter; @Override public void onStart(SourceCallback sourceCallback) throws MuleException { } @Override public void onStop() { } @OnSuccess public void logSuccess( String successMessage){ } @OnError public void logError( String errorMessage, String details){ } } {code}"""," [ERROR] error on execute: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: Extension 'OnlySources' defines the ImmutableSourceModel 'AnotherSource' which has parameters with repeated names. Offending parameters are: [message] @EmitsResponse public class AnotherSource extends Source { @UseConfig private BasicExtensionConfig config; /** * Source Parameter description */ @Parameter private String anotherSourceParameter; @Override public void onStart(SourceCallback sourceCallback) throws MuleException { } @Override public void onStop() { } @OnSuccess public void logSuccess( String successMessage){ } @OnError public void logError( String errorMessage, String details){ } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11158","12/07/2016 13:56:12",1,"Concrete ParameterGroup validation throws unexpected exception ""The following exception is thrown when an abstract class is used in a ParameterGroup. The model error should be nicely communicated. """," [ERROR] diagnostic: error: java.lang.IllegalArgumentException: Component 'org.mule.runtime.api.meta.model.declaration.fluent.ConnectionProviderDeclarer@6bca6c4c' is not an instance of any known model type [configuration, connection provider, operation, org.mule.runtime.api.exception.MuleRuntimeException: java.lang.IllegalArgumentException: Component 'org.mule.runtime.api.meta.model.declaration.fluent.ConnectionProviderDeclarer@6bca6c4c' is not an instance of any known model type [configuration, conn at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:943) at org.mule.runtime.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.lambda$process$1(ExtensionResourcesGeneratorAnnotationProcessor.java:79) at java.util.Optional.ifPresent(Optional.java:159) at org.mule.runtime.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.process(ExtensionResourcesGeneratorAnnotationProcessor.java:77) at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794) at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705) at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91) at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035) at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176) at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856) at com.sun.tools.javac.main.Main.compile(Main.java:523) at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129) at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138) at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.executeWithExceptionsHandled(AbstractAnnotationProcessorMojo.java:545) at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.execute(AbstractAnnotationProcessorMojo.java:285) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: java.lang.IllegalArgumentException: Component 'org.mule.runtime.api.meta.model.declaration.fluent.ConnectionProviderDeclarer@6bca6c4c' is not an instance of any known model type [configuration, connection provider, operation, source] at org.mule.runtime.module.extension.internal.util.IntrospectionUtils.getComponentModelTypeName(IntrospectionUtils.java:672) at org.mule.runtime.module.extension.internal.introspection.describer.AnnotationsBasedDescriber.declaredAsGroup(AnnotationsBasedDescriber.java:583) at org.mule.runtime.module.extension.internal.introspection.describer.AnnotationsBasedDescriber.declareParameters(AnnotationsBasedDescriber.java:539) at org.mule.runtime.module.extension.internal.introspection.describer.AnnotationsBasedDescriber.declareFieldBasedParameters(AnnotationsBasedDescriber.java:516) at org.mule.runtime.module.extension.internal.introspection.describer.AnnotationsBasedDescriber.declareConnectionProvider(AnnotationsBasedDescriber.java:509) at org.mule.runtime.module.extension.internal.introspection.describer.AnnotationsBasedDescriber.lambda$declareConnectionProviders$6(AnnotationsBasedDescriber.java:464) at java.util.ArrayList.forEach(ArrayList.java:1249) at org.mule.runtime.module.extension.internal.introspection.describer.AnnotationsBasedDescriber.declareConnectionProviders(AnnotationsBasedDescriber.java:464) at org.mule.runtime.module.extension.internal.introspection.describer.AnnotationsBasedDescriber.declareConfiguration(AnnotationsBasedDescriber.java:281) at org.mule.runtime.module.extension.internal.introspection.describer.AnnotationsBasedDescriber.declareConfigurations(AnnotationsBasedDescriber.java:246) at org.mule.runtime.module.extension.internal.introspection.describer.AnnotationsBasedDescriber.describe(AnnotationsBasedDescriber.java:223) at org.mule.runtime.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.parseExtension(ExtensionResourcesGeneratorAnnotationProcessor.java:102) at org.mule.runtime.module.extension.internal.resources.ExtensionResourcesGeneratorAnnotationProcessor.lambda$null$0(ExtensionResourcesGeneratorAnnotationProcessor.java:80) at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:939) at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:162) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:958) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:938) ... 37 more [ERROR] error on execute: org.mule.runtime.api.exception.MuleRuntimeException: java.lang.IllegalArgumentException: Component 'org.mule.runtime.api.meta.model.declaration.fluent.ConnectionProviderDeclarer@6bca6c4c' is not an instance of any known model t ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11161","12/07/2016 19:35:56",0,"Update the cipher block used in PGP encryption ""Mule pgp encryptor is using an old cipher block CAST5. We should upgrade to more up-to-date AES-256 cipher.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11166","12/08/2016 13:29:55",8,"Perform spike on NonBlocking policies ""In order to support non blocking SDK operations, it'd be good to have policies applies in a Non blocking manner since right now the policies API is completely blocking. Perform a spike and see what it takes""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11167","12/08/2016 14:07:36",8,"Policies should be non blocking ""A spike was performed in MULE-11166 and there's a branch with a first attempt of achieving that. However, as stated on the linked issue, there're design principles in the current policies solution which prevent to go fully non blocking. We should overcome those limitations in order to allow NB policies.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11169","12/09/2016 17:41:53",5,"Define a way to provide information about classes and bean references for tooling ""When Mule Module developers want to create classes given a full qualified name, or define that a field is a reference to something, using plane strings leads to a poor UI and UX. Examples of this are the ObjectSource in the validation module: In order to differentiate a simple string fields from any of this scenarios, we need to provide all the information that tooling can use to support this kind of fields. For the field type, we could provide a annotation with the form of: For the ref field, we could indicate it with a annotation marker @Ref"""," @ExclusiveOptionals public class ObjectSource { @Parameter @Alias(""""class"""") @Optional private String type; @Parameter @Optional private String ref; public @interface ClassInfo { //TODO find better names java.lang.Class[] _extends() default {}; //This is the only way to make it optional java.lang.Class[] _implements() default {}; } public @interface ClassInfo { //TODO find better names String _extends() default """"""""; String[] _implements() default {}; } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11170","12/12/2016 11:52:55",1,"Split Tooling Runtime Client from API and implementation ""This will allow to release API and implementation with different versions.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11171","12/12/2016 11:59:06",1,"ArtifactClassLoaderRunner - WorspaceReader is only resolving SNAPSHOT between projects in reactor ""The implementation of WorkspaceReader used for resolving Maven artifacts in TestRunner is only looking for SNAPSHOT versions when resolving references between projects/discovered as part of the reactor. This issue affects when releasing a version of an artifact that uses the TestRunner due to versions at that point are no longer SNAPSHOTS.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11173","12/12/2016 12:09:27",8,"Spike: Allow ToolingRuntimeClient to load the Container class loader in order to support retrieving ExtensionModel ""Tooling Runtime Client should create the Container ClassLoader so it can later resolve ExtensionModel of an extension using deployment model from Mule.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11175","12/12/2016 15:04:32",8,"Spike: Functions in DW ""We need to define how functions will be passed to dw. This might regard creating function interfaces, a function DataType and the mechanism to make those 2 work. The goal is to provide a way to define dw functions through Java in the same way that ExpressionLanguageFunction did for MEL.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11180","12/12/2016 18:28:57",2,"ArtifactClassLoaderRunner - ClassLoaders should be injected with the application classloader set as TCCL ""While setting services for instance the service manager is created and started, this could trigger to initialize a service and these services could use SPI therefore the application context classloader should be set as TCCL from the runner while injecting them.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11181","12/12/2016 18:30:59",1,"ArtifactClassLoaderRunner - Add to API different builders for MuleContext implemented in functional test code ""The following classes in the module mule-tests-runner needs to be moved to the api package as they are required by third party modules (MUnit) : * org.mule.munit.runner.TestBootstrapServiceDiscovererConfigurationBuilder * org.mule.munit.runner.TestServicesMuleContextConfigurator * org.mule.munit.runner.MuleContextManager.TestClassLoaderRepository Please make sure this classes are part of the API""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11187","12/13/2016 14:56:49",3,"SourceModel deserialize returns null instead of Optional.empty() for sucessCallBack and errorCallback fields ""After deserializing an extension model with sources and no error or success callback, the SourceModel returns null values for the 2 optional fields. Expected: When not provided, the value should be Optional.empty, not null""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11188","12/13/2016 15:02:56",1,"SourceCallbackModel is deserialized as a TreeMap ""After deserializing the SourceModel, instead of having a SourceCallbackModel inside the optional value, it has a TreeMap generating a ClassCastException """," java.lang.ClassCastException: com.google.gson.internal.LinkedTreeMap cannot be cast to org.mule.runtime.api.meta.model.source.SourceCallbackModel ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11189","12/13/2016 18:38:16",3,"NPE when using ParameterGroup on Source OnSuccess ""Declaring a `@ParameterGroup` in the `@OnSuccess` of a Source produces a NullPointerException. Example Produced: If the ParameterGroup annotation is removed the method is invoked correctly."""," @OnSuccess public void onSuccess( @ParameterGroup(""""Reply Configuration"""") ReplyParameters overrides, SourceCallbackContext callbackContext) { java.lang.NullPointerException at org.mule.runtime.module.extension.internal.runtime.execution.MethodArgumentResolverDelegate.resolve(MethodArgumentResolverDelegate.java:127) at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.getParameterValues(ReflectiveMethodComponentExecutor.java:76) at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.lambda$execute$130(ReflectiveMethodComponentExecutor.java:72) at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:162) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:958) at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.execute(ReflectiveMethodComponentExecutor.java:70) at org.mule.runtime.module.extension.internal.runtime.source.ReflectiveSourceCallbackExecutor.execute(ReflectiveSourceCallbackExecutor.java:69) at org.mule.runtime.module.extension.internal.runtime.source.SourceAdapter$DefaultSourceCompletionHandler.lambda$onCompletion$103(SourceAdapter.java:141) at org.mule.runtime.module.extension.internal.runtime.source.SourceAdapter$DefaultSourceCompletionHandler.safely(SourceAdapter.java:156) at org.mule.runtime.module.extension.internal.runtime.source.SourceAdapter$DefaultSourceCompletionHandler.onCompletion(SourceAdapter.java:141) at org.mule.runtime.module.extension.internal.runtime.source.ModuleFlowProcessingTemplate.lambda$sendResponseToClient$260(ModuleFlowProcessingTemplate.java:69) at org.mule.runtime.module.extension.internal.runtime.source.ModuleFlowProcessingTemplate.runAndNotify(ModuleFlowProcessingTemplate.java:82) at org.mule.runtime.module.extension.internal.runtime.source.ModuleFlowProcessingTemplate.sendResponseToClient(ModuleFlowProcessingTemplate.java:69) at org.mule.runtime.core.execution.ModuleFlowProcessingPhase$1.lambda$run$213(ModuleFlowProcessingPhase.java:124) at java.util.Optional.ifPresent(Optional.java:159) at org.mule.runtime.core.functional.Either.apply(Either.java:89) at org.mule.runtime.core.execution.ModuleFlowProcessingPhase$1.run(ModuleFlowProcessingPhase.java:134) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.mule.service.scheduler.internal.RunnableFutureDecorator.run(RunnableFutureDecorator.java:54) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11192","12/13/2016 20:06:43",2,"Tooling Runtime Client handle multiple configurations when building ApplicationModel for DataSense ""Current implementation only supports reading the first configuration file defined by mule-deploy.properties. It would need to be change the ApplicationModel from DataSense API in order to allow building it from multiple configuration files. In addition to that, the mule-deploy.properties may not be present so default (by convention) config file name should be used.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11193","12/13/2016 22:46:33",1,"File and FTP field ordering cleanup ""* For all operations that require a Path, the order should be path, then content, then other fields in alphabetical order. * In the case of copy and move, source and target paths should be at the top * """"Match With"""" is confusing. Use the term """"File matching rules"""" as the header * For List, Recursive should go above the matching section * For read operation, remove the advanced tab since it's not needed.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11196","12/14/2016 16:04:16",8,"Return a 5xx response when thread pool is exhausted instead of ignoring the request ""The http connector silently ignores requests when overloaded. Even if not all of them can be answered (with success or error), at least some of the failures should be returned as a 503 status code. This issue is for 4.x, as the thread pool code changed from 3.x.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11197","12/14/2016 16:52:49",0,"Xa JMS applications interfere with each other when undeploying one of them ""As mentioned in SE-4799, when a Bitronix application is undeploy, that application and other ones using Xa Transactions start failing. These is caused by a race condition, since the writing of the journal is never protected by a lock, or synchronization. Proposed solution: make the poll method of XaTransactedJmsMessageReceiver synchronized.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11202","12/15/2016 01:59:45",1,"headers element should go before body element ""In the WSC consume operation, inside the message element, the correct element order should be: # headers # body # attachments instead of the current: # body # headers # attachments""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11207","12/15/2016 20:07:30",5,"CXF Module is not exporting the org.mule.apache.security package. ""The CXF module should export the org.mule.apache.security package. This is used when creating secured services, the WSS4J interceptos should be referenced from the XML as shown bellow, if those classes are not being exported the CXF module will throw a class not found exception. usage example: """," jks mulepassword security/trustStore ",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11208","12/15/2016 20:09:43",5,"When using the CXF module with MTOM, the wrong Content-Type is returned ""Downloading an attachment from an MTOM service started with the CXF Module, the wrong content type is being returned. ""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11209","12/15/2016 20:50:41",3,"Source callback parameters types are not exported ""Source callback parameters types are not exported""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11210","12/15/2016 20:52:54",3,"Nullsafe ignores the ParameterGroups inside the annotated POJO ""Nullsafe ignores the ParameterGroups inside the annotated POJO""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11211","12/15/2016 20:54:41",1,"Nullsafe fails takes a ParameterGroup as a required field of the annotated POJO ""Nullsafe fails takes a ParameterGroup as a required field of the annotated POJO""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11212","12/15/2016 22:29:00",3,"WSC Extension: With WSS Timestamp using a timeToLive lower than a second doesn't send the expire tag ""Using a timeToLive lower than a second makes the request produced by the WSC to not include the the expires tag. In the case this isn't supported by CXF it would be better to remove the Nanoseconds/Microseconds timeToLive units. For example using 999 milliseconds: +*Steps to reproduce:*+ * Changing in the WSS functional tests the config as the example above. * Make a request to http://localhost:${http.port.wsc}/test-security-timestamp * You will see that the request contains the timestamp tag but no the expires tag. """," #[payload] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11213","12/16/2016 13:53:00",0,"Migrate DB integration tests to new extension ""Migrate DB integration tests to new extension""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11214","12/16/2016 14:06:13",3,"Add concept of ""resolverName"" to the NamedTypeResolver ""Currently the TypeResolvers have a `categoryName`, that relates a key resolver to an output or input resolver. Since we now support multiple InputTypeResolvers for each operation, and In order for uniquely identifying a resolver associated to a Parameter without using it's class, we need that these input resolvers declare their own name. By default, the name of an OutputResolver should be `output` and for an InputResolver `input`, valdiating later that these names are overwriten if more than one Resolver of the same name is found inthe same category""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11215","12/16/2016 14:33:23",1,"Parameters annotated with Content should not validate DSL rules ""Parameters annotated with Content should not validate DSL rules like not having a `name` field""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11216","12/16/2016 15:01:58",1,"DB: Enable TypeInference for input parameters of BulkOperations ""DB: Enable TypeInference for input parameters of BulkOperations""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11221","12/16/2016 17:44:18",8,"Support Transactions in Sources ""Spike: Support Transactions in Sources, see #MULE-10961""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11222","12/16/2016 17:49:32",13,"Allow to retrieve an ExtensionModel element from its ComponentIdentifier representation ""Allow to retrieve an ExtensionModel element from its ComponentIdentifier representation. This implies that coming from a ComponentModel Application definition, and providing all the ExtensionModels associated to that Application, the user should be able to retrieve the ExtensionModel elements based only in the ComponentIdentifier of a node in the application.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11224","12/16/2016 18:18:52",5,"JMS: Add error handling ""- Improve exceptions to be more granular - Add Error types declaration to the module""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11226","12/16/2016 19:33:08",3,"add error handling capabilities in File connector ""Use the new error handling capabilities in the new file connector""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11227","12/16/2016 19:34:41",3,"Add error handling capabilities to the Ftp connector ""Use the new error handling capabilities in the new FTP connector""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11228","12/16/2016 19:50:12",3,"Add error handling to Email connector ""Add error handling capabilities to the new email connector""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11229","12/16/2016 20:11:37",13,"Spike on Mule Client ""Perform a spike on building the new mule client""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11231","12/16/2016 20:41:55",13,"Allow operation parameters which override config ones ""There's one common pattern in extensions: The logic behind this is if optionalSomeParameter is not provided, then it defaults to whatever config.someParameter says. However, because someParameter might be dynamic, the operation ends up requiring access to the Event in order to resolve that value. Because operations need to no longer be capable of accessing the Message nor the Event, we need to: * Have a way to mark that an operation parameter is an override of a config one * It should validate that both parameters are of the same type * It should allow both parameters to have different names * It should support the config parameter to be dynamic * It should be compatible with either (or both) parameters to belong to different parameter groups"""," ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11232","12/18/2016 04:16:07",1,"Tooling API should receive a Supplier for Tooling API URL configuration ""This will allow Studio to not start Mule when configuring the Tooling API runtime client but only when the client needs to get access to the Runtime.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11233","12/19/2016 20:16:37",8,"Replace DictionaryType with open ObjectType ""Once the DictionaryType is removed from the MetadataType model, we should replace its usage in the Extensions with an open ObjectType UPDATE: This has already been implemented in the Metadata Model by Achaval in branch MDM-31""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11234","12/19/2016 20:17:29",13,"Spike: Provide support for creating a serializable ElementModel from an ApplicationModel ""Provide a service for moving from a configured Application to it's DSL serialization.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11236","12/19/2016 21:41:54",3,"Allow parameters to have a type which belongs to a namespace different than the extension's ""Add a way in which it's possible to represent things like: This doesn't have to rely on imported types, since the most common use case for this will be: """," ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11237","12/19/2016 21:51:38",8,"Add language rules into the extension model ""Right now there're a number of synthetic things into an extension DSL which are considered language rules and are not reflected into the extension model. For example: * Non void operations get a target attribute * Pooled connection providers get a * Tls parameters don't contain a description of the type These and all other language rules need to be explicit in the extension model for tooling purposes""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11238","12/19/2016 22:03:45",8,"Allow parameter groups to be optionally be explicit in the DSL ""Right now parameter groups are invisible at the DSL level. It should be possible to optionally make them implicit. E.g: Translates to: This is specially important for the interaction with tooling when the group pojo contains fields annotated with @Content.. It should be disallowed for pojo parameters to contain @Content fields. That should only be allowed on parameter groups (dsl explicit or not). Notice that this also means that the current support for ContentTypeAnnotation, etc, needs to be removed"""," public void publish(@ParameterGroup(name=""""builder"""", showsInDsl=true) MessageBuilder builder) {} ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11240","12/20/2016 13:00:35",0,"Apply changes from CXF-7162 ""Apply the changes made in CXF as per https://issues.apache.org/jira/browse/CXF-7162""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11241","12/20/2016 14:11:06",0,"Add support for Option Resolvers ""Continue and implement what is specified in MULE-9613 and https://docs.google.com/document/d/1Vjd0cvWeETuuqhGveWfraWIwwX5CeIjtara-i2yWuKE/edit""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11243","12/21/2016 16:31:10",1,"Disable schema validations on LazyMuleArtifactContext ""It should be disable the xml/schema validation so ToolingService could deploy an application with an xml that may not be complete and allow doing connectivity testing.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11244","12/21/2016 17:50:59",5,"Expose Metadata result information such as resolver and category names in the MetadataService ""Nowadays it is impossible to obtain information about the MetadataResolvers from the outside. Such information is contained in the `MetadataResolverFactoryModelProperty` which is not externalizable (and shouldn't be). We have to provide a way for accessing Metadata Resolver information such as resolver name and category name. Two options for doing this is: 1) Implementing capabilities to extract that information from a component in the MetadataService. 2) Add that information to the MetadataDescriptors""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11245","12/21/2016 19:30:59",13,"Fix memory leak in Extension Spring Support test cases ""*Fix memory leak in Extension Spring Support test cases*""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11247","12/21/2016 21:40:37",5,"Populate all parameters with a layout order ""Nowadays, parameters can have a LayoutModel which specifies (among other things) its order. If no placement is specified for any element, it is assumed that the element's natural order will be respected but that's only an assumption. We need to populate the LayoutModel with that information having into account 3 different scenarios: 1) All parameters have an order specified. 2) No parameter has an order specified. 3) Some the parameters have an order specified and some of them not (take a decision for this case and document it).""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11248","12/21/2016 21:42:55",3,"Review ExtensionModel version and artifact locator ""Review if: * The extensionModel needs the concept of getVersion() at all * The extensionModel could benefit from some kind of artifacts locator/coordinates/whatever, or if on the contrary, only the deployment descriptors should contain that information.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11249","12/21/2016 21:50:00",3,"Review ImportedTypesModel and SubtypeModels ""Once MULE-11248 has been resolved, review how to reference the Imported types source extension and the base type in the subtypes model. Update: - For ImportedTypes, we will use the TypeCatalog in a given ResolvingContext to identify the Extension that declares the imported type. - Subtypes mapping of imported types as base type will work out of the box, as long as the type has been declared as imported. For this to work properly, we are assuming that dependencies between Extensions are handled by other actor, such as deployment or tooling, to ensure that the context with all the information is available for resolving the type's declaring extension.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11253","12/22/2016 13:50:17",8,"Add a way to remove application policies ""Application policies can be added/removed on runtime based on configuration changes. Current version supports adding, but removing policies is not done yet.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11256","12/22/2016 14:02:01",0,"Create POLICY artifact type ""org.mule.runtime.core.config.bootstrap.ArtifactType defines APP and DOMAIN types, along with an ALL type that implies both APP/DOMAIN. This type is used support different type of objects in the bootstrap properties and to selectthe proper context builder for an artifact. Now that policy artifact also define a context, a POLICY type must be defined and ALL type must be re-evalauted to see if still makes sense (there could be things that apply to APP/DOMAIN but no a POLICY)""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11257","12/22/2016 14:16:28",8,"Remove Event uses from HTTP extension ""SDK must be Event agnostic so we need to remove it's uses from the HTTP extension as much as possible (if something cannot be done then it must be notified so the use case can be addressed).""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11262","12/22/2016 18:20:57",0,"Update commons-net to 3.5 ""Update commons-net to latest version which includes the most recent bugfixes.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11263","12/22/2016 18:40:31",8,"Migrate OAuth http module usage to http service ""Migrate OAuth http module usage to http service""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11264","12/22/2016 18:57:44",8,"Replace MetadataDescriptor with OperationModel ""In the MetadataService, we currently return a : The information contained in the MetadataDescriptor is mostly the structure of the Operation with the types of each element. We'd like to change the Service API so instead of returning the Descriptor we return a new OperationModel typed accordingly to the resolved dynamic type""","MetadataResult",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11265","12/22/2016 19:15:50",0,"ArtifactClassLoaderRunner - Cannot handle classpath URLs escaped on Windows "" is not able to findClassPathURL when the URLs are escaped, for instance Windows environments when folder has a whitespace.""","DefaultWorkspaceReader",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11267","12/22/2016 21:52:24",2,"Migrate OAuth tests to MuleArtifactFunctionalTestCase ""Migrate OAuth tests to MuleArtifactFunctionalTestCase. Check required provided dependencies.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11269","12/23/2016 13:08:24",2,"Migrate OAuth param extractor MEL to DW ""Migrate all MEL specific code in OAuth to use th DW expression language.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11274","12/23/2016 20:47:22",0,"MVEL optimizer does not refresh when the payload type changes ""In out fork of MVEL, we added the feature that let us access an _invalid_ property of the payload (getting in return a `null` value) ([MULE-7510]). In this case, the optimizer creates the Accessors, having a NullAccessor in the place that property should be called. After the payload is transformed (to a type that has the mentioned property), the Accessors are not updated (SE-4960).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11275","12/23/2016 21:33:14",8,"NoClassDefFoundError using Groovy in RestAssured ""We are creating an SDK extension, and testing it with RestAssured. When running a test, the exception *NoClassDefFoundError: groovy/lang/GroovyObject* is raised. The stack trace is: Guillermo Fernandes helped me notice that *mule-module-spring-config-4.0* exports *Groovy*, but does not include the dependence. If we remove it from *mule-module.properties* in that module, then the error is: Guillermo found a possible temporary workaround: - Create in our testing resource folder, the file *excluded.properties* with the following content: """," java.lang.NoClassDefFoundError: groovy/lang/GroovyObject at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) at java.net.URLClassLoader.access$100(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:368) at java.net.URLClassLoader$1.run(URLClassLoader.java:362) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:361) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.findLocalClass(FineGrainedControlClassLoader.java:179) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:97) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at com.jayway.restassured.RestAssured.(RestAssured.java:335) at com.mulesoft.extension.policies.ip.IpFilterPolicyTestCase.ipFilterIpv4ConfigurationWhitelist(IpFilterPolicyTestCase.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74) Caused by: org.mule.runtime.module.artifact.classloader.exception.CompositeClassNotFoundException: Cannot load class 'groovy.lang.GroovyObject': [ Cannot load class 'groovy.lang.GroovyObject': [ Cannot load class 'groovy.lang.GroovyObject': [ groovy.lang.GroovyObject, Class 'groovy.lang.GroovyObject' not found in classloader for artifact 'launcher'.]]] at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 27 more Caused by: org.mule.runtime.module.artifact.classloader.exception.CompositeClassNotFoundException: Cannot load class 'groovy.lang.GroovyObject': [ Cannot load class 'groovy.lang.GroovyObject': [ groovy.lang.GroovyObject, Class 'groovy.lang.GroovyObject' not found in classloader for artifact 'launcher'.]] at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.findParentClass(FineGrainedControlClassLoader.java:144) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:87) ... 28 more Caused by: org.mule.runtime.module.artifact.classloader.exception.CompositeClassNotFoundException: Cannot load class 'groovy.lang.GroovyObject': [ groovy.lang.GroovyObject, Class 'groovy.lang.GroovyObject' not found in classloader for artifact 'launcher'.] at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.mule.runtime.module.artifact.classloader.FilteringArtifactClassLoader.loadClass(FilteringArtifactClassLoader.java:60) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.findParentClass(FineGrainedControlClassLoader.java:144) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:87) ... 31 more Caused by: java.lang.ClassNotFoundException: groovy.lang.GroovyObject at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.findLocalClass(FineGrainedControlClassLoader.java:179) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:97) ... 35 more java.lang.LinkageError: loader constraint violation: loader (instance of org/mule/runtime/module/artifact/classloader/MuleArtifactClassLoader) previously initiated loading for a different type with name """"groovy/lang/MetaClass"""" at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:467) at java.net.URLClassLoader.access$100(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:368) at java.net.URLClassLoader$1.run(URLClassLoader.java:362) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:361) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.findLocalClass(FineGrainedControlClassLoader.java:179) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:97) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.getDeclaredMethods(Class.java:1975) at org.codehaus.groovy.reflection.CachedClass$3$1.run(CachedClass.java:84) at java.security.AccessController.doPrivileged(Native Method) at org.codehaus.groovy.reflection.CachedClass$3.initValue(CachedClass.java:81) at org.codehaus.groovy.reflection.CachedClass$3.initValue(CachedClass.java:79) at org.codehaus.groovy.util.LazyReference.getLocked(LazyReference.java:46) at org.codehaus.groovy.util.LazyReference.get(LazyReference.java:33) at org.codehaus.groovy.reflection.CachedClass.getMethods(CachedClass.java:250) at groovy.lang.MetaClassImpl.addInterfaceMethods(MetaClassImpl.java:365) at groovy.lang.MetaClassImpl.fillMethodIndex(MetaClassImpl.java:289) at groovy.lang.MetaClassImpl.initialize(MetaClassImpl.java:2908) at org.codehaus.groovy.reflection.ClassInfo.getMetaClassUnderLock(ClassInfo.java:166) at org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:182) at com.jayway.restassured.internal.ResponseParserRegistrar.$getStaticMetaClass(ResponseParserRegistrar.groovy) at com.jayway.restassured.internal.ResponseParserRegistrar.(ResponseParserRegistrar.groovy) at com.jayway.restassured.RestAssured.(RestAssured.java:335) at com.mulesoft.extension.policies.ip.IpFilterPolicyTestCase.ipFilterIpv4ConfigurationWhitelist(IpFilterPolicyTestCase.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74) excluded.artifacts=org.codehaus.groovy:groovy:*:*:* extraBoot.packages=groovy ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11276","12/23/2016 22:48:31",2,"OAuth callback doesn't support external listener references ""When the callbacks listeners for OAuth are configured referencing an already existing http listener, the same server used by that listener must be used instead of creating a new one. This is working in 3.x, but we still need to figure out how to make it work in 4.x with the HTTP service.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11278","12/26/2016 11:49:40",2,"Upgrade Tanuki license ""Upgrade Tanuki Wrapper license since current expires in January 2017. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11284","12/26/2016 19:08:59",2,"Improve registration of global contexts ""Right now we have kept the """"search registry"""" approach to finding global binding contexts but this is very restrictive and we can't guarantee it will work for the SDK. We need to figure out a better way of doing this.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11287","12/27/2016 15:39:36",1,"Copy bulk operation classes from mule-commons to mule-api ""Mule commons dependecy must be removed from mule 4. In order to to that, classes used for bulk operations, must be copied to mule-api project. (mule 3.x still depends on these classes, so they can't be moved)""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11288","12/27/2016 17:00:47",1,"Add all metadata model dependencies as provided in the extensions parent poms ""add the metadata-model-xml, metadata-model-json and metadata-model-java as provided dependencies on the extensions parent pom""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11289","12/27/2016 17:18:04",0,"Rename all groupIds and validate that runtime dependencies are always provided. ""org.mule dependencies cannot have _compile_ scope. plugins declared dependencies that has a groupId that starts with _org.mule.runtime_ or _com.mulesoft.mule.runtime_ should always be provided to avoid the extension to be packaged with those jars. To enforce that we should validate it at package time.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11290","12/27/2016 18:12:37",1,"ExtensionModelLoaders should not be loaded for each MuleContext "" uses SPI for discovering in Container ClassLoader, this should only be made once instead of per each ExtensionManager created. Having this code in one place only and outside the ConfigurationBuilder will allow Tooling Runtime Client to use it instead of copying the same logic twice.""","org.mule.runtime.module.deployment.impl.internal.application.ApplicationExtensionsManagerConfigurationBuilderExtensionModelLoader",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11292","12/27/2016 19:36:12",13,"Functions, TypedValues and ParameterResolvers are not supported inside a Pojo ""*Functions, TypedValues and ParameterResolvers are not supported inside a Pojo* * To support {{Functions}}, {{TypedValues}} and {{ParameterResolvers}} model properties indicating this are used, due that for POJOs, model properties are not used, these resolvers can't be used. * Think if this kind of parameters makes sense to be used in POJOs or how we should give support for this.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11294","12/29/2016 11:31:56",1,"Review which org.mule.runtime.core.api.debug package must be maintained ""Package org.mule.runtime.core.api.debug contains API used to provide debugging capabilities to Mule components. Parts of it will be replaced with the interception API, but other components should be maintained and probably moved to mule-api""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11296","12/29/2016 12:04:50",5,"Socket extension is not using CustomClassLoadingLengthProtocol ""Sockets extension defines different TcpProtocols, and almost all of them are used, but org.mule.extension.socket.api.connection.tcp.protocol.CustomClassLoadingLengthProtocol is not. Probably this was an omision and must be added, otherwise that class must be removed.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11302","12/29/2016 18:20:00",0,"Default XML Transformer factory does nor support StAXSource ""The Xalan lib in the endorsed folder does not support StAXSource, but that is being given to it when trying to get a Document from an XMLStreamReader.""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11304","12/29/2016 22:28:01",5,"Cannot add @Alias annotation to operation parameter, function parameters and function names ""The Alias annotation does not include PARAMETER in its @Target's ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11307","12/30/2016 16:53:22",8,"Separate OAuth extension from the implementation ""This would allow for components to use OAuth authentication without needing to use the OAuth extension. As part of this, remove the dependency of OAuth with the Event interface to a minimum.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11309","12/30/2016 17:19:45",13,"Implement the Extensions Client. ""Develop a mule java client api to execute extensions operations. A first API approach could be something like this. (without adding the capability to pass an Event) Key points: * Smart Connectors support * Maybe the execute methods should receive an Event. * Operation parameters default values and null safeness"""," public interface MuleClient { Publisher> executeAsync(String operationId, OperationParameters parameters); Result execute(String operationId, OperationParameters parameters); } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11311","12/30/2016 17:30:08",3,"allowInlineDefinition annotation is ignored on packaging ""An operation defined with the following signature: Generates the following XML schema: Which allows the definition of the query both as a child element and as an attribute. The code is available here: https://github.com/mulesoft/mongo-connector/tree/d3e70daf96ee16652edb27f75e65e0f00e11662d """," public Document updateDocuments(@Connection MongoClient client, String collection, @Optional @XmlHints(allowInlineDefinition = false) Document query, @Content Document element, @Optional(defaultValue = """"true"""") boolean multi) Specify which configuration to use for this invocation. The name of a variable on which the operation's output will be placed ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11312","12/30/2016 20:00:28",8,"Test connection error when having two listener config with the same data ""If you try to execute test connection in this app: It seems it tries to start a server in the same port twice"""," ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11313","12/30/2016 20:42:30",8,"NPE doing test connection for http request with default values ""If you try to do test connection with this app you get a NPE stack trace """," java.lang.NullPointerException java.lang.NullPointerException at org.mule.extension.http.internal.request.HttpRequesterProvider.buildTcpProperties(HttpRequesterProvider.java:179) at org.mule.extension.http.internal.request.HttpRequesterProvider.connect(HttpRequesterProvider.java:163) at org.mule.extension.http.internal.request.HttpRequesterProvider.connect(HttpRequesterProvider.java:60) at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:58) at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:58) at org.mule.runtime.core.internal.connection.LifecycleAwareConnectionProviderWrapper.connect(LifecycleAwareConnectionProviderWrapper.java:61) at org.mule.runtime.core.internal.connection.CachedConnectionHandler.createConnection(CachedConnectionHandler.java:96) at org.mule.runtime.core.internal.connection.CachedConnectionHandler.getConnection(CachedConnectionHandler.java:87) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:153) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.lambda$testConnectivity$1(DefaultConnectionManager.java:136) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.doTestConnectivity(DefaultConnectionManager.java:143) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:129) at org.mule.runtime.module.extension.internal.tooling.ExtensionConnectivityTestingStrategy.testConnectivity(ExtensionConnectivityTestingStrategy.java:67) at org.mule.runtime.core.connectivity.DefaultConnectivityTestingService.testConnection(DefaultConnectivityTestingService.java:83) at org.mule.runtime.config.spring.LazyConnectivityTestingService.testConnection(LazyConnectivityTestingService.java:47) at com.mulesoft.agent.services.tooling.MuleAgentConnectivityTestingService.testConnection(MuleAgentConnectivityTestingService.java:77) at com.mulesoft.agent.external.handlers.tooling.ToolingRequestHandler.lambda$testConnection$4(ToolingRequestHandler.java:210) at com.mulesoft.agent.util.ResponseHelper.response(ResponseHelper.java:88) at com.mulesoft.agent.external.handlers.tooling.ToolingRequestHandler.testConnection(ToolingRequestHandler.java:209) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171) at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:152) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104) at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:387) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:331) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:103) at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:267) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:297) at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:254) at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1028) at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:372) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:381) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:344) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:221) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1515) at com.mulesoft.agent.rest.RequestLoggingFilter.doFilter(RequestLoggingFilter.java:95) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:519) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:138) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:564) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:213) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1097) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:448) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:175) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1031) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:446) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:271) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:246) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532) at java.lang.Thread.run(Thread.java:745) java.lang.Throwable: java.lang.NullPointerException at org.mule.extension.http.internal.request.HttpRequesterProvider.buildTcpProperties(HttpRequesterProvider.java:179) at org.mule.extension.http.internal.request.HttpRequesterProvider.connect(HttpRequesterProvider.java:163) at org.mule.extension.http.internal.request.HttpRequesterProvider.connect(HttpRequesterProvider.java:60) at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:58) at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:58) at org.mule.runtime.core.internal.connection.LifecycleAwareConnectionProviderWrapper.connect(LifecycleAwareConnectionProviderWrapper.java:61) at org.mule.runtime.core.internal.connection.CachedConnectionHandler.createConnection(CachedConnectionHandler.java:96) at org.mule.runtime.core.internal.connection.CachedConnectionHandler.getConnection(CachedConnectionHandler.java:87) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:153) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.lambda$testConnectivity$1(DefaultConnectionManager.java:136) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.doTestConnectivity(DefaultConnectionManager.java:143) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:129) at org.mule.runtime.module.extension.internal.tooling.ExtensionConnectivityTestingStrategy.testConnectivity(ExtensionConnectivityTestingStrategy.java:67) at org.mule.runtime.core.connectivity.DefaultConnectivityTestingService.testConnection(DefaultConnectivityTestingService.java:83) at org.mule.runtime.config.spring.LazyConnectivityTestingService.testConnection(LazyConnectivityTestingService.java:47) at com.mulesoft.agent.services.tooling.MuleAgentConnectivityTestingService.testConnection(MuleAgentConnectivityTestingService.java:77) at com.mulesoft.agent.external.handlers.tooling.ToolingRequestHandler.lambda$testConnection$4(ToolingRequestHandler.java:210) at com.mulesoft.agent.util.ResponseHelper.response(ResponseHelper.java:88) at com.mulesoft.agent.external.handlers.tooling.ToolingRequestHandler.testConnection(ToolingRequestHandler.java:209) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171) at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:152) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104) at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:387) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:331) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:103) at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:267) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:297) at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:254) at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1028) at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:372) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:381) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:344) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:221) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1515) at com.mulesoft.agent.rest.RequestLoggingFilter.doFilter(RequestLoggingFilter.java:95) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:519) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:138) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:564) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:213) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1097) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:448) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:175) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1031) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:446) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:271) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:246) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532) at java.lang.Thread.run(Thread.java:745) at org.mule.tooling.metadata.utils.MetadataUtils.showErrorMessage(MetadataUtils.java:394) at org.mule.tooling.metadata.utils.MetadataUtils.showTestConnectionErrorMessage(MetadataUtils.java:385) at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction.displayResultMessage(TestConnectorConnectionFromMuleConfigAction.java:162) at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction.run(TestConnectorConnectionFromMuleConfigAction.java:149) at org.mule.tooling.messageflow.dialog.GlobalElementDialog$1.widgetSelected(GlobalElementDialog.java:404) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4080) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3706) at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) at org.eclipse.jface.window.Window.open(Window.java:794) at org.mule.tooling.messageflow.editor.GlobalElementEditor.doCreate(GlobalElementEditor.java:454) at org.mule.tooling.messageflow.editor.GlobalElementEditor$9.widgetSelected(GlobalElementEditor.java:300) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313) at org.mule.tooling.ui.widgets.SquareButton.doButtonClicked(SquareButton.java:315) at org.mule.tooling.ui.widgets.SquareButton$5.handleEvent(SquareButton.java:174) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4080) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3706) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) at org.eclipse.equinox.launcher.Main.run(Main.java:1519) ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11314","12/30/2016 21:19:21",8,"Test connection issue with http listener, server is stopped ""Doing test connection with this app you get the following message Test connection failed: Server on host 127.0.0.1 and port 8081 is stopped. Server stopped"""," ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11315","12/31/2016 14:26:24",5,"Field setter for aliased inline parameter group fails to inject parsed value ""When a parameter group has a parameter with an Alias, like: And used as an inline group: then the aliased parameter `myName` is parsed correctly but fails to inject it in the Object, while the non-aliased parameter `age` is injected without a problem. """," public class PersonalInfo { @Parameter @Alias(""""myName"""") private String name; @Parameter private Integer age; public PersonalInfo getInlinePersonalInfo(@ParameterGroup(name = """"Personal Info Argument"""", showInline = true) PersonalInfo info) { return info; } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11316","01/02/2017 12:17:26",8,"Update the DslElementSyntax to be a tree representation of the component ""Currently, when using the DslSyntaxResolver to resolve the DSL of a top level component like an Operation or Source, the user has to manually iterate over the component's parameters in order to obtain the full tree-like representation of the element in the DSL. Changing the DSL to provide a nested view of the elements will simplify it's traversal and allow for easier consumption of the API""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11317","01/02/2017 15:21:28",8,"Add support for Literal parameters ""*Add support for Literal parameters* * Add a mechanism to be able to retrieve expression values for a certain parameter in the same way as {{ExpressionSupport.Literal}}""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11318","01/02/2017 15:35:15",5,"File and FTP list operations should return list of messages ""Drop TreeNode in favour of List""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11319","01/02/2017 15:36:34",5,"Add list-exclusive operation to file and ftp extensions ""support exclusive list""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11320","01/02/2017 15:45:20",1,"Add stop capability to ExtensionWalker ""Add stop capability to ExtensionWalker""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11322","01/02/2017 17:33:31",1,"Clean up POM unused properties ""Clean up POM unused properties""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11326","01/03/2017 13:40:31",1,"Update JUnit to 4.12 and disable timeout when debugging ""When debugging our 60 second timeout rule stops the program as when running tests in CI. This is inconvenient and can be disabled with a rule introduced in JUnit 4.12. This is unrelated to the transport/connection timeout.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11327","01/03/2017 15:15:42",2,"OAuth2 client module encodes redirect_uri twice in the body ""The oauth client module sends redirect_uri both as a query parameter and in the body as a form encoded parameter. The body version is url-encoded twice, not conforming with the RFC (which says it's optional, but if present should be equal to the query parameter version). Recently our oauth provider was fixed to url-decode parameters once instead of twice, because it's the same as doing nothing for parameters without special characters and fails when parameters have special characters. See SEC-277.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11329","01/03/2017 17:36:25",8,"Dynamically load Mule Runtime libraries on Tooling Runtime Client ""MULE-11173 was the spike related to this issue, this task is about doing the implementation for Tooling Runtime client to allow loading Mule Runtime libraries dynamically (provided by clients) in order to avoid including them as part of the classpath.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11332","01/03/2017 20:39:49",1,"ArtifactClassLoaderRunner - Is not considering exclusions declared on rootArtifact pom file ""In some cases it is required to exclude transitive dependencies and this is declared in the pom.xml file of the rootArtifact but AetherClasspathClassifier is not considering this when creating the Dependency object for each test scope dependency declared as direct dependency.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11338","01/04/2017 17:06:55",1,"Remove event dependency from Authentication interface and implementations ""The event doesn't seem to be used in the Authentication's""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11344","01/05/2017 16:02:07",8,"Make MuleEventContext Serializable ""Make MuleEventContext Serializable""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11347","01/05/2017 16:15:39",2,"Define expression language selection experience ""We need to decide how the EL will be selected when evaluating expressions.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11356","01/05/2017 20:57:29",2,"Have all compatibility artifacts in their own subfolder in the repo ""Have all compatibility artifacts in their own subfolder in the repo""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11358","01/06/2017 17:43:33",0,"Path Element is not correctly created for elements after a MessageFilter ""If there is any component after a MessageFilter, the path is not correctly created. The child number assigned is set to double of the difference between the component and the MessageFilter. For example: The path for """"flow"""" should be (...)/0/1, and it actually is (...)/1/3."""," ",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11359","01/06/2017 20:35:33",2,"Adapt container to work with new binary heavy package ""The Container should adapt to read the new binary package. The definition of such is detailed in this [document|https://docs.google.com/a/mulesoft.com/document/d/125WiY0yDxiCzjjY69ho8V_srq8n0pfA3J_SJlBkHBSI/edit?usp=sharing] in the section Phase 1. This is a general description of how it looks like: If you whish to generate the package you can already use the following maven plugin """," ├── plugins │ └── sdk-extension.zip │ └── api-kit-plugin.zip ├── lib │ └─ shared │ └─ my-plugin-related.jar │ └─ my-app-related.jar ├── classes │ └── *.raml │ └── log4j2.xml │ └── org │ └── MyClass.class │ └── plugins │ └── api │ └── *.raml │ └── wsdl ├── mule │ └── package │ └── mule-configuration(s).xml │ └── mule-configuration(s).xml ├── mule-app.properties ├── mule-deploy.properties ├── pom.xml ├── META-INF │ └── mule-src │ └── application-name └── org.mule.tools.maven mule-maven-plugin 3.0.0-SNAPSHOT true ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11360","01/06/2017 22:42:06",5,"Missing definition parser for parameter @Content of type InputStream ""Got this error: When deploying an application which uses an @Content parameter of type InputStream. The code for reproducing the failing test is [here|https://github.com/fbarrios/hello-world-connector-4.x/tree/6991a614e14db32565505778185276b203574806]. Changing the parameter type to Object and then casting as InputStream fixes the error: https://github.com/fbarrios/hello-world-connector-4.x/commit/d90f29c0214162e706fb2ad79865d639ce443fc1 """," Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.659 sec <<< FAILURE! - in org.mule.modules.helloworld.automation.functional.GetStreamDataTestCase testGetStreamDataFlow(org.mule.modules.helloworld.automation.functional.GetStreamDataTestCase) Time elapsed: 1.087 sec <<< ERROR! org.mule.runtime.api.lifecycle.InitialisationException: Configuration problem: The element 'stream' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/hello-world present on the classpath? Offending resource: URL [file:/Users/federicobarrios/mulesoft/connectors/hello-world-connector-4.x/target/test-classes/operation-get-stream-data.xml] Caused by: org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: The element 'stream' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/hello-world present on the classpath? Offending resource: URL [file:/Users/federicobarrios/mulesoft/connectors/hello-world-connector-4.x/target/test-classes/operation-get-stream-data.xml] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11361","01/09/2017 11:54:13",1,"Tooling API fails when trying to create the container classloader from Studio ""There is an issue in Equinox that when a resource is requested from a Bundle it returns twice the same URL. So, when the container classloader for Mule is created (without the MULE-11329 support yet) the following error is thrown: """," Caused by: java.lang.IllegalStateException: Module 'mule-api' was already defined at org.mule.runtime.container.internal.ClasspathModuleDiscoverer.discover(ClasspathModuleDiscoverer.java:44) at org.mule.runtime.container.internal.CompositeModuleDiscoverer.discover(CompositeModuleDiscoverer.java:38) at org.mule.runtime.container.internal.ContainerModuleDiscoverer.discover(ContainerModuleDiscoverer.java:36) at org.mule.runtime.container.internal.ContainerClassLoaderFactory.createContainerClassLoader(ContainerClassLoaderFactory.java:97) at org.mule.tooling.client.internal.DefaultExtensionModelModelService.resolveExtensionModel(DefaultExtensionModelModelService.java:109) at org.mule.tooling.client.internal.DefaultExtensionModelModelService.loadExtensionModel(DefaultExtensionModelModelService.java:88) ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11362","01/09/2017 12:25:59",1,"ArtifactClassLoaderRunner - Should avoid including services/plugins classified in Container CL ""MULE-11182 added support for classifiers in all the filters and this change has impacted the logic for Container URLs classifications, the ID used to filter services and plugins from direct dependencies was not including the classifier (now that it is a must in poms to include the classifier the logic could always use the full artifact ID). In addition to that, Aether will include transitive dependencies no matter if the patternExclusionFilter has a no match for a direct dependency. This is the expected behaviour for application classification due to we still want transitive (case of mule-test-functional->mule-core->x) but no in the container classification case.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11364","01/09/2017 14:57:55",2,"Replace TypedValue interface on mule-api with DefaultTypedValue from mule-core ""Mule-api contains TypedValue interface, which is implemented on DefaultTypeValue on the core. As it represents a value, it makes more sense to have TypedValue as a class, not an interface. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11367","01/09/2017 19:16:00",1,"Tooling API avoid M4 dependencies to mule-runtime artifacts from dataSense ""DataSense 4.0-SNAPSHOT has declared M4 dependencies temporarily. This should be changed but meanwhile we are going to override these dependencies on Tooling Client.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11370","01/09/2017 21:21:02",2,"Request builder parameters need to be ordered in UI ""Order should be: * Body * Headers * URI Parameters (text should be corrected from 'Uri Params"""") * Query Parameters (text should be corrected from 'Query Params"""") * Media Type""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11372","01/10/2017 01:25:18",1,"Remove JAAS module ""JAAS module will be removed from the code/distro to avoid exposing it on the API. Missing functionality will be replaced at some point with a new security extension. ""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11377","01/10/2017 22:07:59",2,"Change API for applying policies to allow policies templates ""Since we will continue to support mustache templates in the policies zip files and the API gateway agent will be responsible for resolving those templates, we need to change our API so the agent can have a chance to process the template if needed. The idea is to have a single API to cover both use cases: template or no template. The idea so far is that we just ask for the file (as InputStream or whatever) of the resolved template. If there's nothing to do then it will retrieve the policy config file as it is. Processing the template will not resolve the parametrization of the policy that is not related to mustache. That will be done by mule.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11378","01/10/2017 22:08:28",8,"Allow SDK operations and sources to return List ""Allow operations to return signatures of type List> which would output a list of Messages which payload is of type InputStream and attributes of type FileAttributes. At the same time allow sources to extend Source>, Attributes> which would be a source which returns a similar collection as the operation above.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11380","01/11/2017 16:17:32",1,"DynamicConfigurations not disposed when start() fails ""When calling DynamicConfigurationProvider#registerConfiguration, the configuration is both initialized and started, but if start fails it is not being disposed, causing all resources obatained in initialize to be leaked.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11383","01/11/2017 21:05:57",8,"Packaging: plugins, services, policies, and so on, must be packaged as JAR files ""All modules that contribute to the runtime (plugins, services, policies, etc.) must be packaged as JAR files rather than ZIP. Why we are picking JAR over ZIP files: * maven knows how to contribute JARs to the classpath without any custom plugin. It can be modified to support ZIP (contributing to the classpath) with a custom maven plugin, but that also implies implementing several plugins for IDEs such as Eclipse, IntelliJ, etc. * transitive dependencies will work out of the box (same rule as before, it can be done but with more custom code) * it plugs easier when a mule app depends on a plugin (or a plugin depends on a plugin) ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11386","01/12/2017 12:20:41",1,"When an exception is thrown by a scheduled task, it should be logged ""When an exception is thrown by a scheduled task, it should be logged""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11388","01/12/2017 13:15:23",2,"Migrate JBoss TX module parsers to Mule 4 mechanism ""Migrate JBoss TX module parsers to Mule 4 mechanism""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11390","01/12/2017 13:23:00",8,"Migrate JSON module parsers to Mule 4 mechanism ""Migrate JBoss TX module parsers to Mule 4 mechanism""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11392","01/12/2017 13:25:56",2,"Migrate Schedulers module parsers to Mule 4 mechanism ""Migrate JBoss TX module parsers to Mule 4 mechanism""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11396","01/12/2017 13:35:22",2,"Migrate TLS module parsers to Mule 4 mechanism ""Migrate TLS module parsers to Mule 4 mechanism ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11397","01/12/2017 13:36:22",8,"Migrate XML module parsers to Mule 4 mechanism ""Migrate JBoss TX module parsers to Mule 4 mechanism""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11400","01/12/2017 13:55:34",8,"Migrate HTTP transport parsers to Mule 4 mechanism ""Migrate HTTP transport parsers to Mule 4 mechanism""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11401","01/12/2017 13:57:00",2,"Migrate Sockets transport parsers to Mule 4 mechanism ""Migrate Sockets transport parsers to Mule 4 mechanism""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11404","01/12/2017 14:35:09",8,"Apply OperationUX to the WSC ""Apply OPERATION UX to the wsc""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11405","01/12/2017 14:36:28",3,"Extensions Client not disposing processor after executing ""DefaultExtensionsClient#createProcessor initializes and starts a processor, but that is never disposed. Add a scheduler to a heisenberg operation to have coverage for this scenario/""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11409","01/12/2017 18:36:07",1,"mule-module-proxy dependencies must be updated ""As part of MULE-11357, all mule plugins will install/deploy a single artifact. Right now mule-module-proxy depends on mule-module-http-ext-4.0-SNAPSHOT.jar and mule-module-sockets-4.0-SNAPSHOT.jar. Once MULE-11357 is done, the artifact that the plugins will generate are mule-module-http-ext-4.0-SNAPSHOT-mule-plugin.jar and mule-module-sockets-4.0-SNAPSHOT-mule-plugin.jar respectively. For the time being, both artifacts will publish both jars, but it's just a workaround to not breaking GW build.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11411","01/12/2017 20:20:31",5,"Too much contention in TraversableStream when using file store buffer ""When using file store buffer, there's way too much contention on the file store. Add a second level of in memory buffering for each cursor.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11412","01/12/2017 21:10:07",5,"MuleContext, services and configs not injected into Pojos nested in a config ""Take for instance OAuth grant types. Having a MuleContext field with @Inject, the field is null when iniitalize is called. This also happens with @UseConfig Current workaround is to propagate the MuleContext from the HttpRequesterProvider (https://github.com/mulesoft/mule/pull/3940/files#diff-bf73dd2c2b906c68a00d1d8ec0c1d7d3R141)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11413","01/13/2017 12:04:44",2,"Fix DW dependency for FunctionalTestCase ""Since DW is a plugin and FunctionalTestCase has no support for those, the EL fails to load and all tests, including ExtensionsFunctionalTestCase, cannot use DW as EL.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11414","01/13/2017 13:29:04",13,"Review JMS Extension Migration ""*Review JMS Extension Migration* * Review and find gaps in the migration of the JMS Transport to JMS Extension""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11416","01/13/2017 15:06:01",0,"WS Consumer Module: Should use Mule TLS implementation to read the Remote WSDL instead of using the Java classes directly ""The WS Consumer doesn't use the TLS configuration of the HTTP requester because it uses the Java Classes directly instead of the Mule Implementation. This was fixed by MULE-11298, we only add tests here.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11418","01/13/2017 16:29:07",13,"Improve JMS Extension acknowledgement mechanism ""*Improve JMS Extension acknowledgment mechanism* *Improvements* * In the *JMSListener* in the {{@OnError}} method execute a {{session.recover()}} to communicate to the JMS Broker that an error occurred and the message should be redelivered. * When the user configures a {{AUTO}} acknowledgment mode, the listener should execute an ACK in the {{@OnSuccess}} method. ** Take care that the JMS specification says when a {{AUTO}} acknowledgment mode is selected, the JMS Client will produce an ACK if the execution of the {{listen()}} is executed correctly, but as the listener once receive the message, dispatch this one asynchronously to the flow, the {{listen()}} method always is performed successfully, producing automatically an ACK not depending on the result of the flow. ** To work around what is explained above, when the user select an {{AUTO ACK}}, the extension communicates to the client that a {{CLIENT_ACK}} has been chosen, so the client doesn't produce the ACK automatically, then in the {{@OnSuccess}} check the ACK Mode, and if is an """"Extension"""" Auto ACK, manually execute an ACK. * Nowadays is impossible to have a *JMS Listener* with *MANUAL ACK Mode*, and later doing the ACK Manually because the *listener* and the *ACK Operation* can't share the same connection, and as consequence the same session. This will make the *ACK* operation always fails because the new connection won't find a session to make the message an ACK. Also doing a *consume* and a *ack* doesn't have a deterministic result, due that in both operations a different connection could be configured. ** As a possible solution implement something like {{HttpRequesterConnectionManager}} for HTTP Connector https://github.com/mulesoft/mule/pull/3923/files. That is having a shared state between all the configurations where the messages/sessions are referenced to be able to do an ACK without depending of the injected connection in the ACK Operation. * Change the *ackId* of the JMSAttributes from a *Optional* to a *String*, due that this implies that the Mule user will need to unwrap the optional value at runtime. * Review the implications of a {{transacted}} ACK Mode. * With client ack mode, the messages are generated from a same session, the JMS spec defines that the ACK is done over a session, not over a particular message, so doing a ACK over a message will not only produce the ACK over this one althought the messages of the entire session doesn't matter if these had been sucessfully processed or are still in flight. The same can happen doing the recover the session, this method can affect on more that one message.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11420","01/13/2017 17:07:54",5,"TypedValue and ParameterResolver can't be used inside a Pojo annotated with @Nullsafe and Content ""*TypedValue and ParameterResolver can't be used inside a Pojo annotated with @Nullsafe* * Nullsafe annotated pojos uses a different mechanism to create {{ValueResolvers}} which doesn't consider {{TypedValue}} and {{ParameterResolver}} parameters. * Not considering this cases, this mechanism creates value resolvers that evaluate expressions to create TypedValue type.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11426","01/14/2017 03:01:04",1,"Loading ExtensionModels in Studio takes too long ""We found that either the Extension support from Mule Runtime or the class loading stuff takes a too long when loading an extension model from Tooling and Tooling is running under an Eclipse Plugin classpath. It could be related with the scan classpath that Extension support does in order to discover the class annotated with the @Extension. This issue is about to resolve this performance issue and make it work for Studio/Eclipse OSGi environments.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11429","01/16/2017 13:52:45",13,"Auto Generate extensions documentation ""Auto generate documentation when the extension is built. Mimic what devkit currently has""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11431","01/16/2017 14:06:34",2,"Decouple email connector from MuleMessage ""PagingProviderEmailDelegate manually generates a list of Messages. It shouldn't.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11432","01/16/2017 14:58:20",3,"Disallow operations to receive the current Event and Message ""This should also include removing the concept of Function. Coordinate with [~afelisatti] before executing this task. Also add a validation that no operation tries to receive the event or the message ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11433","01/16/2017 15:20:50",13,"Useful error never informed by connectivity testing ""When performing connectivity testing, the extensions almost never inform a useful connection code. UNKNOWN is constantly resolved""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11435","01/16/2017 15:39:42",13,"Support application declaration as interface between tooling and componentModel ""Support application declaration as interface between tooling and componentModel""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11439","01/16/2017 19:19:55",3,"Different values in a connection don't trigger a new connect() for cached providers ""When trying different scenarios for dynamic configs in the HTTP request part I stumbled upon the fact that performing 2 requests varying a dynamic host (which is a connection param) resulted in the second being the same as the first. In org.mule.test.module.http.functional.requester.HttpRequestDynamicConfigTestCase#requestsGoThroughClient1 the following requests demonstrate the issue: Notice that the first request goes to localhost and without any more changes to the config parameters the next goes to 1.1.1.1 which should fail but instead is successful because it ends up reusing the first connection. Though a combination of config and connection params should be taken into account to define whether to reuse the cached connection, it seems the connection ones are ignored."""," Event result = flowRunner(""""client1"""") .withVariable(""""basePath"""", """"api/v1"""") .withVariable(""""follow"""", true) .withVariable(""""send"""", """"AUTO"""") .withVariable(""""host"""", """"localhost"""") .withVariable(""""path"""", """"clients"""") .withVariable(""""method"""", GET) .withPayload(TEST_MESSAGE) .run(); assertThat(result.getMessage(), hasPayload(is(DEFAULT_RESPONSE))); assertThat(method, is(GET.toString())); assertThat(uri, is(""""/api/v1/clients"""")); assertThat(body, is("""""""")); assertThat(headers.keys(), hasItem(HOST)); assertThat(headers.get(HOST), hasItem(containsString(""""localhost:""""))); result = flowRunner(""""client1"""") .withVariable(""""basePath"""", """"api/v1"""") .withVariable(""""follow"""", true) .withVariable(""""send"""", """"AUTO"""") .withVariable(""""host"""", """"1.1.1.1"""") .withVariable(""""path"""", """"clients"""") .withVariable(""""method"""", GET) .withPayload(TEST_MESSAGE) .run(); ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11440","01/16/2017 19:48:39",8,"Provide a way to set the SecurityContext in SDK ""In order to eliminate all MuleEvent uses from HTTP, there must be a way to replace the HttpBasicAuthenticationFilter. Though a custom version could be built to replicate it's superclass, it's impossible to set the required SecurityContext without accessing the Event.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11441","01/16/2017 20:00:08",1,"Adapt to DW new syntax ""Some syntax changes have been introduced to DW, so we need to adapt our tests to them.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11442","01/16/2017 20:04:36",3,"Tooling Client cant resolve transitive mule plugin dependencies from zip files when loading extension. ""When loading an extension model from a zip file we need to provide an ArtifactResolver implementation that resolves a given Artifact to a File, if we provide the dependency zip file it won't load the extension properly.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11443","01/16/2017 20:07:30",2,"Create DSL-API converter for string to enums ""Add support for converting string to enums.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11450","01/18/2017 13:38:23",8,"Migrate performance tests to JMH ""Contiperf framework is not compatible with JUnit 4.12+, so all tests need to be migrated to JMH which is also a more solid framework.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11451","01/18/2017 14:51:36",1,"Remove DynamicPipeline ""DynamicPipeline and its implementations should be removed.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11455","01/18/2017 18:07:04",0,"JMS connector doesn't allow subclasses to change send() parameters ""Some connectors like WMQ need to change send() parameters based on endpoint configuration attributes or outbound properties.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11460","01/18/2017 23:31:41",0,"Make CPU-intensive pool a ForkJoinPool ""ForkJoinPool seems to be a great fit for the computation pool. When it is so, the mechanism it has to keep the parallelism may be put to allow a wait policy when scheduling from cpuintensive into a busy cpuLight pool""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11461","01/19/2017 10:23:57",8,"Review and add message processing trace logging where needed ""Review and add logging where needed""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11470","01/19/2017 16:42:59",2,"Make HTTP messages body a TypedValue ""The HTTP message body is an Object right now but we should have it be a TypedValue so that the MediaType is no longer needed.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11472","01/19/2017 16:46:35",8,"Implement support for interception message processor from the Debugger ""Debugger should use the interception support added in MULE-11346 with a different API due to the debugger should be able to modify session/flow variables along with the message too.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11484","01/20/2017 14:30:27",5,"ParameterGroup's order are not populated automatically is a value was not configured manually ""*ParameterGroup's order are not populated automatically is a value was not configured* * Following the work of https://www.mulesoft.org/jira/browse/MULE-11247 , also the {{ParameterGroup}} should be populated with the order information. * If the order is configured manually (Using the {{@Placement}} annotation), the value is populated correctly in the model. * The solution should contemple that the *General* parameter group should be always the first group.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11487","01/20/2017 16:49:00",2,"Review if org.mule.runtime.core.management.stats.ProcessingTime is required ""Mule 3.x uses org.mule.runtime.core.management.stats.ProcessingTime and org.mule.runtime.core.management.stats.ProcessingTimeWatcher to calculate the time used to process a given event. A ProcessingTime is attached to each event when the event is created. ProcessingTimeWatcher uses weakReferences to those ProcessingTime instances to detect when a given event has been processed. This approach has issues on mule 3, but it won't work on mule 4 as the event is immutable, to every change in the event requires to create a new one, so the ProcessingTime will be released every time the event is changed. Mule 4 has EventContext#success and EventContext#onError methods that could be used to replace the ProcessingTime management""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11489","01/20/2017 20:15:54",2,"Review name attribute on child elements ""Define if the rule of not having name attributes in child element must continue to exists or it should be removed. And as part of this task remove the rule if necessary. Seems that the gain of having that rule is not much and allowing to use it in the dsl of child elements may simplify the DSL.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11491","01/20/2017 23:35:59",2,"Rename block to try ""We should rename """"block"""" to """"try"""" as it's the most familiar term in our user base. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11493","01/23/2017 15:23:50",2,"Allow to release versions of Tooling Runtime Client implementation for a already released Mule version ""Current approach implemented maps Mule version with Tooling Runtime Client implementation and Agent Rest Client. The scenario where a bug was found in the implementation of Tooling Runtime Client should be handled by releasing a new version of the Client without affecting clients of the API as they always request a Tooling Runtime Client for a Mule version. Some sort of override properties file could be added in order to map the last client version that works for a Mule version.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11494","01/23/2017 15:26:45",1,"Add a way to validate transitive dependencies for Tooling Runtime Client ""As transitive dependencies will change and we have to enforce API and implementation in different artifacts we have to have a way to keep control of these dependency graph.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11495","01/23/2017 17:30:58",8,"Change ConnectionExceptionCode to ErrorType ""*Change ConnectionExceptionCode to ErrorType* * Nowadays the {{ConnectionValidationResult}} exposes a {{ConnectionExceptionCode}} to communicate the type of error happened when creating/validating an exception. * This {{ConnectionExceptionCode}} is an *Enum* which provides a set of different codes, but these codes get short when describing some specific situations, and the error ends being {{UNKOWN}} or another code that doesn't make too much sense. * To improve this, change the {{ConnectionExceptionCode}} to an {{ErrorType}}""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11496","01/23/2017 19:26:02",8,"Create an ExtensionModel for core components of Mule ""Currently, mule's core components like Logger or SetPayload doesn't have an extension-model that represents them. In order to unify the handling between SDK extensions and core components, both for runtime and tooling, we need to provide the extension models of each component accordingly.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11498","01/23/2017 20:21:55",0,"SFTP connector uses ""."" for listing and some implementations don't support it ""The current implementation of SFTP uses """"."""" to denote a directory for listing files even after other paths (like """"/a/path/.""""). The RFC says it's optional to support it (""""should"""" keyword), and removing it works for all servers tested.""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11499","01/24/2017 02:26:46",0,"MavenBundleDescriptorLoader forces zip type even for jar dependencies ""Because all mule plugins that are loaded with the org.mule.runtime.module.deployment.impl.internal.plugin.MavenBundleDescriptorLoader are forcing the type to zip, it is impossible to resolve transitive dependencies to other mule plugins, when trying to load the extension model. The type should be jar, or the code should check that if the packaging is mule-extension, the type is jar and not zip.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11503","01/24/2017 20:05:55",1,"Disable scheduling of incoming requests in HTTP connector ""Disable scheduling of incoming requests in HTTP connector""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11505","01/24/2017 21:31:27",2,"Implement cached IO scheduler that grows that uses async hand-off with queue. ""- Should use a bounded queue for hand-off - Should not have max size. - Should grow on demand - -Should start rejecting work when resources start getting tight.- -> MULE-13936""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11506","01/25/2017 12:46:04",8,"ModuleExceptionHandler should consider error type hierarchy ""ErrorTypes have the notion of hierarchy but that however is not contemplated by the ModuleExceptionHandler when an error is thrown. The operation's ErrorTypeProvider is used to match exactly the thrown error and so one must defined each and everyone regardless of whether or not they belong to a hierarchy. In my case, I had RESPONSE_VALDIATION error type and several """"children"""" like BAD_REQUEST, but if only RESPONSE_VALIDATION was defined in the provider throwing BAD_REQUEST would fail. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11507","01/25/2017 14:10:28",2,"Improve ""parse"" behaviour for DW ""With MEL, component like the logger could define a """"message"""" attribute that would then be """"parsed"""" which allowed String and expressions to be composed together (one could write message=""""My message"""" or message=""""My #['message']"""" which would result in the same output). Since we've decided to deprecate the """"parse"""" method and only allow straight up String in DW it is quite annoying to have to put a String (in the logger example, one has to write message=""""'My message'""""). It would be ideal to find a way to avoid that """"double"""" String thing.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11511","01/25/2017 17:38:36",1,"Ignore flaky JMS topic bridge test ""Ignore flaky JMS topic bridge test""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11512","01/25/2017 17:41:09",5,"JMS TopicBridgeTestCase: replace consumer with listener to avoid flakyness ""JSM TopicBridgeTestCase: replace consumer with listener to avoid flakyness""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11513","01/25/2017 17:48:54",3,"MetadataKeyIdModelProperty shouldn't be public ""The MetadatKeyIdModelProperty states the type and parameter name of the parameter containing the MetadataKeyId annotation. This is useful for the runtime, but tooling consumer can't do much with this info, and should always rely on the MetadataKeyPartModelProperty. Problems arise regarding the keyId model property in the context of multi level datasense, since the """"parameterName"""" in the mp actually references the name of the containing parameter group. It references the argument and not the parameter in the model (which is what we need in the runtime, but makes no sense for the external consumer)""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11516","01/25/2017 21:16:21",0,"Define optimum bufferSize for cursor streams ""We need to do performance test/analysis to define the optimum size of the cursor stream's buffer""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11519","01/26/2017 10:55:37",8,"Define mechanism to patch the runtime and apps ""Define mechanism to patch the runtime and apps""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11521","01/26/2017 12:59:22",8,"Define interception handlers registration mechanism ""Handler Factories may be registered at the context (for all the runtime) or for individual applications. The order of the handlers in the chain must be predictable too.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11524","01/26/2017 13:03:06",2,"Automatically @Inject fields in the handler factories ""This should happen during registration?""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11525","01/26/2017 13:03:54",2,"Support compatibility fields from the event on interception ""Some interceptions may want to change session variables. We need to define how to use the privileged compatibility api for this. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11527","01/26/2017 13:10:56",8,"Parameters should be resolved only once if before doesn't make any changes while intercepting the processor ""Current approach for interception needs to resolve parameters before calling the interceptor as this is input while doing interception to make decision on how interceptor would handle a before operation either if the processor is skipped. If the interceptor doesn't make any changes to the variables/message the parameters would be resolved once again when processor is executed.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11529","01/26/2017 14:48:27",8,"Define interception API ""The API for interception should be added to mule-api and it should allow to do before/after and around interceptions.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11530","01/26/2017 14:49:13",1,"JMS: Fails to set UserMessageProperty when using TypedValues ""JMS: Fails to set UserMessageProperty when using TypedValues Excepton occurs when runing `JmsAbstractQueueBridge`"""," javax.jms.MessageFormatException: Only objectified primitive objects, String, Map and List types are allowed but was: org.mule.runtime.api.metadata.TypedValue@1fe9cbdc type: class org.mule.runtime.api.metadata.TypedValue at org.apache.activemq.command.ActiveMQMessage.checkValidObject(ActiveMQMessage.java:538) at org.apache.activemq.command.ActiveMQMessage.setObjectProperty(ActiveMQMessage.java:504) at org.apache.activemq.command.ActiveMQMessage.setObjectProperty(ActiveMQMessage.java:488) at org.mule.extensions.jms.api.message.MessageBuilder.setJmsPropertySanitizeKeyIfNecessary(MessageBuilder.java:207) at org.mule.extensions.jms.api.message.MessageBuilder.lambda$setUserProperties$3(MessageBuilder.java:199) at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) at org.mule.extensions.jms.api.message.MessageBuilder.setUserProperties(MessageBuilder.java:199) at org.mule.extensions.jms.api.message.MessageBuilder.build(MessageBuilder.java:147) at org.mule.extensions.jms.api.operation.JmsPublish.publish(JmsPublish.java:80) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:203) at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.lambda$execute$89(ReflectiveMethodComponentExecutor.java:73) at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:162) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:958) at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.execute(ReflectiveMethodComponentExecutor.java:72) at org.mule.runtime.module.extension.internal.runtime.operation.ReflectiveMethodOperationExecutor.execute(ReflectiveMethodOperationExecutor.java:54) at org.mule.runtime.module.extension.internal.runtime.execution.ReactiveOperationExecutionWrapper.execute(ReactiveOperationExecutionWrapper.java:55) at org.mule.runtime.module.extension.internal.runtime.execution.InterceptableOperationExecutorWrapper.execute(InterceptableOperationExecutorWrapper.java:56) at org.mule.runtime.module.extension.internal.runtime.operation.DefaultExecutionMediator.lambda$executeWithInterceptors$123(DefaultExecutionMediator.java:119) at reactor.core.publisher.MonoCreate.subscribe(MonoCreate.java:47) at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:62) at reactor.core.publisher.MonoMapFuseable.subscribe(MonoMapFuseable.java:64) at reactor.core.publisher.MonoOtherwiseIfEmpty.subscribe(MonoOtherwiseIfEmpty.java:44) at reactor.core.publisher.MonoOtherwise.subscribe(MonoOtherwise.java:44) at reactor.core.publisher.Mono.block(Mono.java:1172) at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$null$50(OperationMessageProcessor.java:154) at org.mule.runtime.core.policy.DefaultPolicyManager.lambda$createOperationPolicy$1(DefaultPolicyManager.java:105) at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$null$51(OperationMessageProcessor.java:161) at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:162) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$apply$53(OperationMessageProcessor.java:148) at org.mule.runtime.core.api.rx.Exceptions$CheckedFunction.apply(Exceptions.java:169) at org.mule.runtime.core.api.rx.Exceptions.lambda$checkedFunction$4(Exceptions.java:80) at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:111) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onNext(FluxPeekFuseable.java:173) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onNext(FluxPeekFuseable.java:173) at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.runAsync(FluxPublishOn.java:426) at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.run(FluxPublishOn.java:526) at reactor.core.scheduler.ExecutorServiceScheduler$ScheduledRunnable.run(ExecutorServiceScheduler.java:196) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.mule.service.scheduler.internal.RunnableFutureDecorator.run(RunnableFutureDecorator.java:64) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11533","01/26/2017 16:49:07",5,"JMS: Add support for TypedValues ""JMS: Add support for TypedValues""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11534","01/26/2017 17:37:55",0,"XmlMetaDataFieldFactory returns empty field list for element with complexType/any ""For an element definition in a schema such as: metaDataFields is empty after calling XmlMetaDataFieldFactory#loadFields"""," ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11537","01/26/2017 20:00:02",5,"DslElementModel: Add default values and expose the value in the element ""DslElementModel: Add default values and expose the value in the element""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11540","01/26/2017 21:47:02",1,"Have an ExpressionManager interface in API ""In order to inject the ExpressionManager into services and other places, it has to be declared in mule-api.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11541","01/26/2017 22:55:21",1,"Move HttpConstants and HttpHeaders to http-service-api ""Move it to the service api so it may be accessed by users of the http service""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11542","01/27/2017 11:32:10",0,"Tooling API should have only one ArtifactResolver interface ""It would be better to only have one interface to be implemented by customers when using Tooling API for resolving external dependencies.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11543","01/27/2017 13:47:54",8,"Add SSL as an ErrorType provided by Mule ""*Add SSL as an ErrorType provided by Mule* * Several connectors uses SSL for their connections, and in all these cases SSL Errors can be thrown, add the capability in Mule and in the SDK to provider an {{ErrorType}} associated with SSL Exceptions.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11544","01/27/2017 13:57:47",1,"java.util.Map is listed in the types of an ExtensionModel ""An Object with typeId java.util.Map is in the listo of types provided by an extension when it shouldn't ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11545","01/27/2017 14:40:04",0,"Add powermock version to global pom ""As powermock is used on both CE and EE, we'll add it to dependency management to avoid possible differences in version used.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11546","01/27/2017 14:48:06",5,"Pojo with Map field DSLSyntax element is not generated correctly ""When consuming the DSL for a pojo with the following structure, the generated information is not correct. The generated DSL has a properties element, with an attribute name of key, and no information about having a child element with name property."""," public class PojoWithMap { @Parameter private Map properties; public Map getProperties() { return properties; } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11551","01/27/2017 19:02:43",8,"Define mechanism to inform shared libraries dependencies ""We need to define how we are going to identify """"shared"""" libraries provided by the application or domain.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11556","01/28/2017 21:12:22",1,"Mule exceptions thrown from an extension end up as UNKNOWN ""Since upon an exception we try mapping it to an error according to the failing processor and sdk extensions define one for each component, any mule exceptions thrown from an operation (e.g. a transformation error when evaluating the operations parameters) will end up mapped using the operations mappings. Under most circumstances this results in an UNKNOWN error from the extension namespace.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11558","01/29/2017 15:23:26",8,"Remove XML module ""XML module will be replaced at some point with a XML extension. Module will be removed from the code/distro to avoid exposing it on the API""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11563","01/30/2017 16:45:08",0,"Tooling API should not depend on xml APIs ""Tooling API has a few third-party dependencies, the ones related to xml should not be included: These libraries have issues when running Tooling API from Studio/OSGi"""," /lib/stax-api-1.0.1.jar /lib/stringtemplate-3.2.1.jar /lib/xercesImpl-2.11.0.jar /lib/xml-apis-1.4.01.jar /lib/xmlbeans-2.6.0.jar ",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11565","01/30/2017 17:31:55",8,"Fix ElementDeclaration handling of open objectTypes ""Fix ElementDeclaration handling of open objectTypes so we can represent unknown keys in objectType""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11566","01/30/2017 17:51:21",2,"Rename AnnotatedObject to Component ""Rename AnnotatedObject to Component(?)""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11568","01/30/2017 18:39:08",8,"Implement a way to determine the ComponentType of a component ""Also review other implementations of ComponentIdentifier#getComponentType() Also, review SCOPE vs ROUTER in CompoenntType""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11570","01/30/2017 19:25:32",1,"Make host and port required for HTTP request ""Host and port should be required on HTTP request to align it with how other connectors work. Users can override them still at the request level. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11574","01/31/2017 14:26:06",8,"Integration tests fail to execute because a classloading problem with extensions ""When running the integration tests from maven in isolation it fails with: Caused by: java.lang.ClassNotFoundException: org.mule.extension.file.common.api.exceptions.FileError While if the whole project is compile with maven, they work. The complete stack trace is: initializationError(org.mule.test.xml.functional.BeanPropertyExtractorTestCase) Time elapsed: 0 sec <<< ERROR! java.lang.TypeNotPresentException: Type org.mule.extension.file.common.api.exceptions.FileError not present at sun.reflect.annotation.TypeNotPresentExceptionProxy.generateException(TypeNotPresentExceptionProxy.java:46) at sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:84) at com.sun.proxy.$Proxy44.value(Unknown Source) at org.mule.runtime.module.extension.internal.loader.enricher.ErrorsDeclarationEnricher.lambda$enrich$0(ErrorsDeclarationEnricher.java:72) at java.util.Optional.ifPresent(Optional.java:159) at org.mule.runtime.module.extension.internal.loader.enricher.ErrorsDeclarationEnricher.enrich(ErrorsDeclarationEnricher.java:69) at org.mule.runtime.extension.internal.loader.ExtensionModelFactory.lambda$enrichModel$1(ExtensionModelFactory.java:191) at java.lang.Iterable.forEach(Iterable.java:75) at org.mule.runtime.extension.internal.loader.ExtensionModelFactory.enrichModel(ExtensionModelFactory.java:191) at org.mule.runtime.extension.internal.loader.ExtensionModelFactory.create(ExtensionModelFactory.java:142) at org.mule.runtime.extension.api.loader.ExtensionModelLoader.loadExtensionModel(ExtensionModelLoader.java:68) at org.mule.test.runner.infrastructure.ExtensionsTestInfrastructureDiscoverer.discoverExtension(ExtensionsTestInfrastructureDiscoverer.java:92) at org.mule.test.runner.api.ExtensionPluginMetadataGenerator.getExtensionModel(ExtensionPluginMetadataGenerator.java:162) at org.mule.test.runner.api.ExtensionPluginMetadataGenerator.generateExtensionManifest(ExtensionPluginMetadataGenerator.java:177) at org.mule.test.runner.api.AetherClassPathClassifier.generateExtensionMetadata(AetherClassPathClassifier.java:640) at org.mule.test.runner.api.AetherClassPathClassifier.buildPluginUrlClassifications(AetherClassPathClassifier.java:426) at org.mule.test.runner.api.AetherClassPathClassifier.classify(AetherClassPathClassifier.java:149) at org.mule.test.runner.api.ArtifactIsolatedClassLoaderBuilder.build(ArtifactIsolatedClassLoaderBuilder.java:290) at org.mule.test.runner.ArtifactClassLoaderRunner.createClassLoaderTestRunner(ArtifactClassLoaderRunner.java:223) at org.mule.test.runner.ArtifactClassLoaderRunner.(ArtifactClassLoaderRunner.java:131) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:107) at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:33) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) Caused by: java.lang.ClassNotFoundException: org.mule.extension.file.common.api.exceptions.FileError at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(CoreReflectionFactory.java:114) at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:125) at sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:49) at sun.reflect.annotation.AnnotationParser.parseSig(AnnotationParser.java:439) at sun.reflect.annotation.AnnotationParser.parseClassValue(AnnotationParser.java:420) at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:349) at sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286) at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120) at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72) at java.lang.Class.createAnnotationData(Class.java:3521) at java.lang.Class.annotationData(Class.java:3510) at java.lang.Class.getAnnotation(Class.java:3415) at org.mule.runtime.module.extension.internal.loader.java.MuleExtensionAnnotationParser.getExtension(MuleExtensionAnnotationParser.java:61) at org.mule.runtime.module.extension.internal.loader.java.JavaModelLoaderDelegate.declare(JavaModelLoaderDelegate.java:152) at org.mule.runtime.module.extension.internal.loader.java.JavaExtensionModelLoader.declareExtension(JavaExtensionModelLoader.java:109) at org.mule.runtime.extension.api.loader.ExtensionModelLoader.loadExtensionModel(ExtensionModelLoader.java:67) ... 26 more""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11575","01/31/2017 15:38:30",8,"Migrate use of blocking API by transports to use non-blocking API that supports new interceptors. Part 1. ""This would allow the transaction support to use the reactor api, effectively deprecating and possibly removing the process method. The outcome of this spike would be a determination of whether its more convenient to do this migration (MULE-11023) or to add an interception mechanism for the blocking Processor API.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11582","01/31/2017 19:04:39",5,"SDK should provide the working directory property ""When initialising the extension, we would like to know the working directory. Nowadays this information can be retrieved by searching it in the Registry.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11584","01/31/2017 19:20:43",13,"Forbid the use of Content in POJOs fields that are not groups ""Forbid the use of Content in POJOs fields that are not groups""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11587","01/31/2017 19:47:56",1,"poolingProfile being created without prefix by XMLGenerationService ""When using the XMLGenerationService to convert a db config with a my-sql-connection connectionProvider the poolingProfile parameter is being created without prefix. {code:title=database config} {code}"""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11588","01/31/2017 20:16:21",13,"Enable bidirectional XML generation/parsing ""Since Mozart uses the DSL Resolver along with the XML Generation Service to write XMLs, we need a new service to be able to parse a given mule XML into the same object structure.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11594","02/01/2017 18:17:20",8,"Move asciidoc generator from the documentation mojo to tooling-client ""Our plugins documentation it's based on an asciidoc file that is generated from an ExtensionModel, that code lives in the mule-extensions-maven-plugin and it's used to generate the final html documentation page. This should be extracted to a new module in the tooling-client that it's only in charge of generating the asciidoc from a tooling extension model so exchange can use this and generate the asciidoc using the tooling-client.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11596","02/01/2017 18:27:01",8,"Documentation Generator: parse HTML snippets to Asciidoc elements ""When getting a description from the extension model that contains HTML snippes like bold or italic we should convert those snippets to asciidoc so they can reflect in the generated documentation. Snippets to parse: * bold * italic * li * pre * ul * ol * code * {@link SomeType} * ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11598","02/01/2017 19:19:46",2,"HTTP Listener error responses don't include content-length nor last chunk ""When a 400 or 500 error code is returned by the HTTP listener, the response if malformed. It should contain Content-Length or add a last chunk (currently it says """"Transfer-Encoding: chunked"""" but omits the last one).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11599","02/01/2017 19:21:19",13,"Support for defining DW functions ""A way of registering DW functions to be evaluated in an extension should be provided. See `org.mule.runtime.api.el.ExpressionFunction`""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11602","02/01/2017 22:11:02",0,"Export org.yaml.snakeyaml.introspector package from spring-config module ""The package {{org.yaml.snakeyaml.introspector}} should be exported too as mule-module-spring-config is already exporting a sub-set of {{yaml}} packages and class {{org.yaml.snakeyaml.introspector.Property}} should be visible too. If not a class not found exception is thrown when a other artifacts try to use {{yaml}}.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11603","02/02/2017 12:18:30",0,"Add DW performance tests ""As MVEL has, we need to add benchmark performance tests for DW.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11605","02/02/2017 13:41:02",2,"Remove or improve org.mule.runtime.core.api.Event#getVariableValueOrNull for performance ""Remove{{ org.mule.runtime.core.api.Event#getVariableValueOrNull}} for performance""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11608","02/02/2017 19:39:51",5,"Guarantee the order of Infrastructure parameters in the schema ""Guarantee the order of Infrastructure parameters in the schema""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11609","02/02/2017 19:49:02",8,"ArtifactFunctionalTestCase - Add support for application test resources ""When the artifact is an application, it should consider that it can have target/class and target/test-classes. From both urls, the analysis should be done of what resources, classes and packages to export.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11610","02/02/2017 20:46:37",8,"Implicit resolvers doesn't use the same resolving mechanism that for a defined element ""*Implicit resolvers doesn't use the same resolving mechanism that a defined element*. We should change completely how we handle implicit dynamic connection providers, since current approach is not ideal. Currently, we evaluate the CP using only the first event, and then always return that resolved instance. This is not ok for dynamic CP, since we need new events to also be used for evaluation. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11611","02/02/2017 21:10:45",3,"NullSafeValueResolverWrapper doesn't communicate the dynamism correctly ""*NullSafeValueResolverWrapper doesn't communicate the dynamism correctly* Only checks the dynamism from the delegate and not from the fallback, due that fallback can have dynamic default values."""," @Override public boolean isDynamic() { return delegate.isDynamic(); }",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11612","02/02/2017 21:14:24",8,"ImplicitConnectionProviderValueResolver doesn't communicate the dynamism correctly ""*ImplicitConnectionProviderValueResolver doesn't communicate the dynamism correctly* This value resolver has the following override With a hard coded *false* value, refactor this value resolver to communicate correctly the dynamism depending in the dynamism of the generated result set."""," /** * @return {@code false} */ @Override public boolean isDynamic() { return false; }",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11614","02/03/2017 15:17:34",0,"Document new expressions for common uses cases ""We need to list all the common uses cases for expressions and translate them to DW. For example: * flowVars = variables * message.payload = payload * message.dataType = dataType * comparing two strings * accessing an objects variable This will not only help document the changes but also identify thins to change/improve.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11615","02/03/2017 17:21:32",13,"Move extensions out of the core. ""We should move all core extensions out of the core. This implies: * migrating them to a new repository * set up the necessary CI jobs * create a new Internal Extensions Parent Pom, with all the internal plugins and dependencies required. * check extensions that were used in integration tests (those test should be moved to another repo) ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11617","02/03/2017 17:23:32",1,"Add missing extensions descriptions ""Currently JMS, OAuth, Sockets, WSC descriptions are empty. We should consider making it a mandatory element since this will most probably be the description that exchange, studio or any other tooling consuming the extension model will show as a summary.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11619","02/03/2017 17:47:50",8,"Test Connectivity returns null instead of a proper error message ""When doing test connectivity with invalid credentials, a null error type is retrieved (since the internal mule app tries to start and fails). We need test connectivity to skip this validation and perform the real one once the app is up and running.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11624","02/03/2017 18:28:11",1,"Verify Mule error types overriding for Extensions does not happen ""Discuss Mule error types overriding for Extensions""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11625","02/03/2017 18:31:08",2,"Unwrap TypedException before creating a MessagingException ""Unwrap TypedException before creating a MessagingException so the user sees the real cause and not the wrapper.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11627","02/03/2017 19:07:13",0,"Update Tooling Runtime whitelist to include lib/wlang-1.2.0-SNAPSHOT.jar ""A new transitive dependency has been added so assembly whitelist has to be updated""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11629","02/03/2017 19:27:34",5,"Spike on a Soap Client ""Spike on a soap client that serves as a mule service to consume SOAP operations, and provided Metadata for it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11630","02/03/2017 20:06:12",8,"Support artifact plugins on domains ""Currently, it is not supported to define a config of an SDK based extensions on a domain. It should be ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11631","02/03/2017 20:14:21",2,"Change HTTP extension namespace to http ""Right now, to track migration and had an incremental replacement between module and extension, the extension has httpn as namespace. Once the module is gone it can be changed to http again. The main issue here will be replacing it in the tests.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11636","02/03/2017 21:15:53",2,"Add support on Tooling Runtime Client to have custom types for DataSense ""Allow to retrieve the custom types xml needed by DataSense.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11642","02/06/2017 12:19:59",8,"OAuth config is not initialized at application startup ""OAuth authorization grant type authenticator needs to create some http listeners on startup. Since the OAuth authenticator is declared inside an http requester config, and that config is dynamic, the OAuth authenticator is not initialized until the requester config is initialized, which doesn't happen until it tries to send a request. This is a serious usability problem, since the only way to workaround this bug and create the required http listeners is to try to send a request through the requester to force the initialization of the oauth authenticator. This is currently worked around in the tests by forcing the initialization calling the http request operation. (See https://github.com/mulesoft/mule/blob/mule-4.x/extensions/oauth/src/test/java/org/mule/test/oauth2/AbstractOAuthAuthorizationTestCase.java#L99).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11643","02/06/2017 12:23:56",8,"Nested Pojos with static configurations have its lifecycle tied to its container config ""This affects the usability of the OAuth extension. See the description of MULE-11642. Also, this will affect all other users of the OAuth service, since the OAuth objects will have to be initialized before the component that uses OAuth is attempted to be used.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11644","02/06/2017 12:53:16",2,"Bundle spring version required by CXF module in compatibility plugin ""When spring is completely isolated in core, cxf will still need to keep its own spring version. We need to ensure that 2 different spring versions isolated cause no trouble.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11647","02/06/2017 15:27:39",8,"Add support for handling stream payloads on TryIt ""The way Streams are handle by TryIt is to show the class name for those payloads, instead it should use the new capability added to Mule to open a cursor in order to transform it to an String representation therefore notifications could be readable.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11651","02/06/2017 20:08:41",8,"HTTP request lost when a failing one is processed first ""org.mule.test.module.spring.security.SecureHttpPollingFunctionalTestCase features a server with basic auth receiving 2 requests triggered by a poll almost simultaneously. One of them has valid credentials while the other does not. Problem is that, although both requests are clearly received and processed by the listener, if the first to be processed (in terms of the flow) is the invalid one then the other is lost and ends up failing afterwards. Though this is happening in that test it would seem it's a more pressing issue in the execution engine that could affect all sources.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11652","02/06/2017 20:25:51",8,"Provide a mechanism to define a privileged API ""Some plugins and tools used on Mule 4 will require access to parts of the API that we don't want to make public for everyone. This API will be accessible only to """"privileged"""" plugins. Privileged plugins will be whitelisted on the core""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11654","02/06/2017 20:34:17",8,"Define privileged API ""Define which classes/packages must be part of the privileged API. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11681","02/07/2017 14:00:37",8,"Tooling API define DTOs for DataSense Service ""Tooling Runtime API is exposing DataSense API, as agreed the API for Tooling should define a DTO and utility classes for it.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11685","02/07/2017 14:59:48",2,"Provide non streaming options for HTTP client ""Since the HTTP extension must support streaming under all circumstances (it's the safest bet) the HttpClient API of the service only supports those scenarios. It's quite annoying for simple uses to have to either use the blocking API or run the non blocking on an IO thread when a quick response and consumption is desired. We should provide non streaming options both blocking and non blocking for those cases.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11686","02/07/2017 15:00:41",8,"Move component and it's dependencies to compatibility module ""This is to move and it's dependencies like: - <*-entry-point-resolver> - // This one may require integration the new spring module - - - etc. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11693","02/07/2017 15:37:30",8,"Migrate idempotent message filter ""Define an error type for this filter.""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11697","02/07/2017 16:03:59",0,"Move queue-profile and queue-store to VM transport ""Move queue-profile and queue-store to VM transport and all the elements that extend those types""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11705","02/07/2017 17:14:21",0,"Clean up debugger API ""Debug API must be clean up after MULE-10834 is solved""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11707","02/07/2017 18:18:48",2,"Remove reconnect-custom-strategy element ""Remove composite-source element""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11708","02/07/2017 18:22:31",2,"Remove reconnect-notifier and reconnect-custom-notifier element ""Remove reconnect-notifier and reconnect-custom-notifier element""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11709","02/07/2017 18:25:00",8,"Remove *-processing-strategy elements ""Remove reconnect-notifier and reconnect-custom-notifier element""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11710","02/07/2017 18:25:43",2,"Remove custom-transaction elements ""Remove reconnect-notifier and reconnect-custom-notifier element""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11711","02/07/2017 18:27:38",2,"Remove jrun-transaction-mamanger, resin-transaction-mamanger and jndi-transaction-manager elements ""Remove jrun-transaction-mamanger, resin-transaction-mamanger, custom-transaction-manager and jndi-transaction-manager elements""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11714","02/07/2017 18:32:32",2,"Remove interceptor-stack elements ""Remove interceptor-stack elements""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11715","02/07/2017 18:32:33",8,"Analyze how to provide package version on each exported package ""As the version of packages used on mule artifacts could be not the same when different artifact versions are used, it would be a good thing to detect in advance whether a package exported by the container will work on a given artifact.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11716","02/07/2017 18:34:29",8,"Move set, remove, copy for attachments, properties, session properties to compatibility module ""Move set, remove, copy for attachments, properties, session properties and variables to compatibility module""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11720","02/07/2017 18:45:10",1,"Remove default-exception-strategy element ""Remove default-exception-strategy element""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11721","02/07/2017 18:46:10",0,"Remove custom-exception-strategy elements ""Remove custom-exception-strategy element""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11722","02/07/2017 18:47:28",2,"Remove custom-connector element ""Remove custom-connector element""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11981","02/07/2017 18:49:00",8,"Make Off Heap streaming EE only ""Filestore Stream buffer should only be available in EE""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11724","02/07/2017 18:49:53",8,"Remove *-object-store elements ""Remove *-object-store elements. Tests cases must use the object store module instead of the core elements.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11728","02/07/2017 18:55:17",0,"Remove dynamic-round-robin, dynamic-all, dynamic first-successful elements ""Remove dynamic-round-robin, dynamic-all, dynamic first-successful elements""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11729","02/07/2017 18:56:13",2,"Remove *-router elements ""Remove *-router elements. This were old routers used by services.   ""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11730","02/07/2017 18:57:12",2,"Remove *-all-strategy elements ""Remove *-all-strategy elements. This are elements used by services""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11732","02/07/2017 18:58:58",2,"Remove custom-lifecycle-adapter-factory element ""Remove custom-lifecycle-adapter-factory element""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11733","02/07/2017 18:59:22",2,"Cannot inject LockFactory ""I attempted to refactor the ObjectStore Extension to inject ObjectStoreManager and LockFactory individually instead of the MuleContext. While functional tests still worked, running a Mule app in a standalone runtime failed, throwing the attached stacktrace. Please contact me if you need help reproducing this. Thanks!""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11735","02/07/2017 19:02:18",8,"Implement object streaming ""Implement object streaming""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11739","02/07/2017 19:16:43",8,"Make ImportedTypes not dependent on Extension name ""Make ImportedTypes not dependent on Extension name. This implies using the TypeCatalog for resolving the Extension that declares a given type in the DslResolvingContext. We are assuming all the necessary information for actually importing the type (that is, having the declaring Extension in the context) is provided by some external actor, and that dependency resolution does not rely on the Extension model import declarations.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11744","02/07/2017 19:51:00",0,"Add component resolution to DataSense service on Tooling Runtime Client API ""DataSenseService should allow to resolves data sense component information for a componentPath.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11750","02/07/2017 20:25:55",8,"Add URL option to HTTP request ""Instead of being able to override a configs host and port, we should allow an url attribute. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11752","02/07/2017 20:31:03",5,"WSC doesnt pick WSDL files from the current classpath ""Creating an app using the WSC connector doesn't work if the WSDL location is relative to the project. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11754","02/07/2017 20:45:26",2,"Update the names of the threads according to the executing task ""For monitoring and troubleshooting, it would be good to have task information on the thread.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11756","02/08/2017 01:34:27",8,"EventContext should be aware of ""Right now, it is possible to subscribe to an EventContext and get notifications when completed. CHild context allow that behaviour to work through flow-refs. We need a way of allowing the same thing when an event goes through one (or many) blocks. Also consider the case of a flow-ref which executes asynchronously.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11760","02/08/2017 14:56:53",1,"Move LockFactory to mule-api ""Move LockFactory interface and its dependencies to mule-api.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11761","02/08/2017 15:25:17",13,"Create the new Soap Service ""As a first approach we need to implement the client side, moving most of the code that is in the WSC to this module""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11762","02/08/2017 17:31:33",8,"Wrong implicit config created when using an exclusive operation ""When using an HTTP request without referencing a config one would expect an implicit request config to be used but a listener one is created instead, failing because such config cannot be implicit. The http request operation is defined as exclusive of the requester config thus that config should be created as it's implicit one.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11763","02/08/2017 18:40:21",2,"Wrong exception on ElementDeclaration validation ""Wrong exception on ElementDeclaration validation""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11765","02/08/2017 19:58:58",8,"Invalid XA JDBC Connections are created after an XA Transaction ""*Invalid XA JDBC Connections are created after an XA Transaction* * After the execution of an XA transaction, the {{jdbcConnectionFactory}} returns the same {{StandardXAConnection}} with an invalid internal state making the connector fail when starting a transaction. ""","Caused by: java.lang.NullPointerException at org.enhydra.jdbc.standard.StandardXAConnection.doStart(StandardXAConnection.java:293) at org.enhydra.jdbc.standard.StandardXAConnection.start(StandardXAConnection.java:361) at bitronix.tm.internal.XAResourceHolderState.start(XAResourceHolderState.java:220) at bitronix.tm.internal.XAResourceManager.enlist(XAResourceManager.java:111) at bitronix.tm.BitronixTransaction.enlistResource(BitronixTransaction.java:130) at com.mulesoft.mule.runtime.bti.transaction.TransactionWrapper.enlistResource(TransactionWrapper.java:48) at org.mule.runtime.core.transaction.XaTransaction.enlistResource(XaTransaction.java:246) at org.mule.runtime.module.extension.internal.runtime.transaction.XAExtensionTransactionalResource.enlist(XAExtensionTransactionalResource.java:57) at org.mule.runtime.core.transaction.XaTransaction.bindResource(XaTransaction.java:229) at org.mule.runtime.module.extension.internal.runtime.connectivity.ExtensionsConnectionAdapter.getTransactedConnectionHandler(ExtensionsConnectionAdapter.java:121) at org.mule.runtime.module.extension.internal.runtime.connectivity.ExtensionsConnectionAdapter.getConnection(ExtensionsConnectionAdapter.java:62) at org.mule.runtime.module.extension.internal.runtime.connectivity.ConnectionInterceptor.getConnection(ConnectionInterceptor.java:64) at org.mule.runtime.module.extension.internal.runtime.connectivity.ConnectionInterceptor.before(ConnectionInterceptor.java:45) at org.mule.runtime.module.extension.internal.runtime.operation.DefaultExecutionMediator.before(DefaultExecutionMediator.java:162) at org.mule.runtime.module.extension.internal.runtime.operation.DefaultExecutionMediator.lambda$executeWithInterceptors$104(DefaultExecutionMediator.java:118) at reactor.core.publisher.MonoCreate.subscribe(MonoCreate.java:47) at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:62) at reactor.core.publisher.Mono.block(Mono.java:1188) at org.mule.runtime.module.extension.internal.runtime.operation.InterceptingExecutionMediator.execute(InterceptingExecutionMediator.java:50) at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.executeOperation(OperationMessageProcessor.java:189) at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.doProcess(OperationMessageProcessor.java:182) at org.mule.runtime.module.extension.internal.runtime.operation.InterceptingOperationMessageProcessor.doProcess(InterceptingOperationMessageProcessor.java:66) at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$null$36(OperationMessageProcessor.java:155) at org.mule.runtime.core.policy.DefaultPolicyManager.lambda$createOperationPolicy$64(DefaultPolicyManager.java:105) at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$null$37(OperationMessageProcessor.java:162) at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:162) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$apply$39(OperationMessageProcessor.java:149) at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.rx.Exceptions.lambda$checkedFunction$3(Exceptions.java:85) at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:111) at reactor.core.publisher.FluxJust$WeakScalarSubscription.request(FluxJust.java:101) at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.request(FluxMapFuseable.java:172) at reactor.core.publisher.MonoNext$NextSubscriber.request(MonoNext.java:104) at reactor.core.publisher.BlockingSingleSubscriber.onSubscribe(BlockingSingleSubscriber.java:50) at reactor.core.publisher.MonoNext$NextSubscriber.onSubscribe(MonoNext.java:66) at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onSubscribe(FluxMapFuseable.java:94) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:69) at reactor.core.publisher.FluxMapFuseable.subscribe(FluxMapFuseable.java:67) at reactor.core.publisher.MonoNext.subscribe(MonoNext.java:41) at reactor.core.publisher.Mono.block(Mono.java:1188) at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.process(OperationMessageProcessor.java:140) at org.mule.runtime.core.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:29) at org.mule.runtime.core.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:65) at org.mule.runtime.core.execution.MessageProcessorExecutionTemplate.execute(MessageProcessorExecutionTemplate.java:43) at org.mule.runtime.core.processor.TransactionalInterceptingMessageProcessor.lambda$process$0(TransactionalInterceptingMessageProcessor.java:45) at org.mule.runtime.core.execution.ExecuteCallbackInterceptor.execute(ExecuteCallbackInterceptor.java:15) at org.mule.runtime.core.execution.CommitTransactionInterceptor.execute(CommitTransactionInterceptor.java:31) at org.mule.runtime.core.execution.CommitTransactionInterceptor.execute(CommitTransactionInterceptor.java:21) at org.mule.runtime.core.execution.HandleExceptionInterceptor.execute(HandleExceptionInterceptor.java:31) at org.mule.runtime.core.execution.HandleExceptionInterceptor.execute(HandleExceptionInterceptor.java:15) at org.mule.runtime.core.execution.BeginAndResolveTransactionInterceptor.execute(BeginAndResolveTransactionInterceptor.java:61) at org.mule.runtime.core.execution.ResolvePreviousTransactionInterceptor.execute(ResolvePreviousTransactionInterceptor.java:41) at org.mule.runtime.core.execution.SuspendXaTransactionInterceptor.execute(SuspendXaTransactionInterceptor.java:46) at org.mule.runtime.core.execution.ValidateTransactionalStateInterceptor.execute(ValidateTransactionalStateInterceptor.java:34) at org.mule.runtime.core.execution.IsolateCurrentTransactionInterceptor.execute(IsolateCurrentTransactionInterceptor.java:37) at org.mule.runtime.core.execution.ExternalTransactionInterceptor.execute(ExternalTransactionInterceptor.java:44) at org.mule.runtime.core.execution.RethrowExceptionInterceptor.execute(RethrowExceptionInterceptor.java:24) at org.mule.runtime.core.execution.RethrowExceptionInterceptor.execute(RethrowExceptionInterceptor.java:13) at org.mule.runtime.core.execution.TransactionalErrorHandlingExecutionTemplate.execute(TransactionalErrorHandlingExecutionTemplate.java:120) at org.mule.runtime.core.execution.TransactionalErrorHandlingExecutionTemplate.execute(TransactionalErrorHandlingExecutionTemplate.java:27) at org.mule.runtime.core.processor.TransactionalInterceptingMessageProcessor.process(TransactionalInterceptingMessageProcessor.java:48) at org.mule.runtime.core.api.processor.Processor.lambda$apply$9(Processor.java:53) at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.rx.Exceptions.lambda$checkedFunction$3(Exceptions.java:85) at org.mule.runtime.core.internal.util.rx.Operators.lambda$nullSafeMap$7(Operators.java:35) at reactor.core.publisher.FluxHandle$HandleSubscriber.onNext(FluxHandle.java:94)",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11766","02/08/2017 20:13:06",0,"DefaultExtensionManager's method attemptToCreateImplicitConfigurationInstance should be syncronized ""The synchronization in DefaultImplicitConfiguration.createImplicitConfiguration is not enough to ensure that another thread did not beat the actual thread to create the instance. The code: Could fail from race condition, if the actual thread verifies the condition before the ExtensionStateTracker registers the ConfigurationInstanceProvider in the other thread. """," //check that another thread didn't beat us to create the instance if (!extensionRegistry.getExtensionState(extension).getConfigurationInstanceProviders().isEmpty()) { return null; } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11768","02/08/2017 21:39:05",2,"Make response and error-response for listener ParameterGroups ""The @Content annotation will be banned from Pojos, this affects the HTTP listener's response and error-response components so they must be migrated to ParameterGroups.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11773","02/08/2017 22:20:14",5,"Parameters of Interface types should be forced to have API implementations ""Parameters of Interface types should be forced to have API implementations. If we have an operation like: where Car is an interface like: Then, unless we provide a public implementation of this Car interface, the only way the app user can create the parameter for this operation is to create its own implementation using a Java Component. This won't work nicely with DW. We should enforce that *any interface used in a Parameter* has to be a baseType of a SubtypesMapping declaration, thus providing at least one implementation in the API of the Extension. *Output should have no restriction on this.* """," public void create(Car car) public interface Car{ String getBrand(); Engine getEngine(); } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11774","02/08/2017 22:29:02",5,"MetadataTypes generated for Interfaces should expose the getters as fields ""Currently, we always generate an empty ObjectType when dealing with interfaces, instead of inferring the fields of that object based on the getters. This is not an issue for input parameters (see #MULE-11773), but *is an issue for the OutputModel*, since Tooling won't be able to provide a real representation of the output payload nor the Attributes of a Result. If we have an interface like: Then the MetadataType generated for this should be an ObjectType with two fields, one of simple type String and one of ObjectType Engine. """," public interface Car{ String getBrand(); Engine getEngine(); } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11776","02/09/2017 13:55:55",13,"Make the WSC use the Soap Service ""Make the WSC use the Soap Service This implies: * Using the new API * Find any gaps on the Service API * Adapt all tests.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11777","02/09/2017 14:01:22",8,"Soap Service: Add the ability to use custom underlying transports. ""Add the ability to use custom underlying transports such as HTTPS, JMS""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11779","02/09/2017 14:15:40",8,"Spec on Soap Connect ""Spec on Soap Connect.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11780","02/09/2017 14:25:15",8,"Move the Soap Service specific tests from the WSC to the Soap Service. ""As we don't have an easy way to start a soap server with custom configurations for testing, the soap service is tested through the WSC, we should move those soap service specific tests to the service module.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11781","02/10/2017 14:26:36",1,"Update Reactor lib version to 3.0.5-release ""Update Reactor lib version to 3.0.5-release""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11784","02/10/2017 17:49:02",2,"Update HTTP migration doc ""The HTTP migration doc has not been touched since M2 and as a result is very outdated. We need to update it with new examples, review it's content and remove anything that makes no sense anymore, specially considering it might be used to document the extension.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11789","02/10/2017 19:03:23",8,"Lightweight package support ""This is to support the deployment of an application that has no dependencies on it. All the dependencies are declared and must be lookup using an API. We can suppose that the API for looking up for dependencies is already implemented. This is required for Mozart so it doesn't have to send the app with the whole dependencies set each time there's a change on it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11790","02/10/2017 19:03:28",13,"Implement OAuth support in SDK ""Placeholder task. Need to split""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11796","02/10/2017 20:51:09",0,"Remove code duplication on DefaultExtensionModelModelService ""DefaultExtensionModelModelService from mule-runtime-tooling-client duplicates code that is already available on Mule container module. More specifically, all the code used to create modules is already available on Mule's org.mule.runtime.container.internal.ClasspathModuleDiscoverer""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11797","02/10/2017 21:21:14",8,"Extension's XSD should be generated in runtime ""Right now the XSD is generated at build time. We should make it so that it's generated when the extension is loaded. This functionality also needs to be exposed through an API so that other components can dynamically obtain an extension's XSD""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11799","02/10/2017 21:25:01",1,"Prevent triple state booleans ""The SDK allows for parameters of boxed boolean types. This generates the possibility of a triple state boolean: true, false, undefined. This produces a bad UX in tooling. We should: * Disallow Boolean parameters * Force optional boolean parameters to have a default value of """"false"""" ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11803","02/10/2017 21:39:26",8,"Allow privileged extensions to enrich their ExtensionModel ""Privileged extensions can contribute declaration enrichers which enrich their own ExtensionModels. This should be part of the Privileged API and only selected extensions should be able to do this.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11804","02/10/2017 21:55:19",8,"Make ServerNotificationHandler part of the API ""This is to move the ServerNotificationHandler infrastructure to the Mule API so extensions can be injected with it and trigger custom notifications. This is needed for the custom notifications of the HTTP module.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11808","02/11/2017 00:18:37",8,"Implement SDK based VM connector ""Spike on implementing VM connector for Mule 4""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11810","02/11/2017 00:57:01",8,"Standardize DSL for routers ""DSL for routers is a more complicated than it should. When a single processor per route can be used, then it looks like this: If later on, the processor1 must be modified to add some additional logic, the DSL has to be updated like this: This makes the DSL more complex than it should and that complexity is also consumed by tooling. The proposal is to change all routers to have always a wrapper element for each route. So it would look like: """," ",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11814","02/11/2017 17:20:08",13,"Migrate XML module to an SDK extension ""Migrate XML module to an SDK extension""","",0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11831","02/14/2017 21:43:07",3,"Reduce NestedProcessor to its minimum expression ""Until a replacement is introduced in 4.x, minimize the NestedProcessor interface to it's minimum expression: process() and process(Result). Also, remove the concepts of @RestrictedTo and @Extensible""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11832","02/14/2017 22:18:14",13,"Add missing DataSense features on WSC ""Add missing DataSense features on WSC""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11834","02/15/2017 02:06:39",3,"DSL: If defaultValue is explicit, write it in the XML ""DSL: If defaultValue is explicit, write it in the XML""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11836","02/16/2017 05:16:40",1,"Tooling API shouldn't throw an exception if an error happens while resolving Metadata for a DataSense request ""When resolving DataSense the dynamic Metadata could fail, in that case the exception shouldn't be propagated and a failure should be passed to DataSense so it could resolve static.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11837","02/17/2017 22:27:37",8,"Simplify declaration to make everything a parameter ""Make the ElementDeclaration of components like flows and artifact support every inner component as a parameter.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11838","02/17/2017 22:29:28",8,"Support flow paths in ElementDeclaration ""Support flow paths in ElementDeclaration to allow lookup using the same coordinates everywere""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11839","02/17/2017 22:34:48",13,"Support core components in the Extension Model ""In order to support every mule component in the extension model, some new concepts have to be added, like: - Scopes - Routers - Aggregators ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11843","02/20/2017 16:25:05",2,"Http Server scheduler is shutdown before the connections are closed ""When an http server is closed, its connections are closed too, sending the `Connection: Close` header. But in order to send that, it still needs the executor for the io work, which was already closed when the server was stopped.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11844","02/20/2017 18:22:27",3,"The dynamic-config-policy element is not part of the extension model ""In the XSD of the extensions, the configurations have an element *dynamic-config-policy*. Because it is not included in the extension model, it is impossible for tooling to generate an UI for it so that users can configure it. This element should be included as part of the model if we want users to define it. We should also move the element to mule's core namespace.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11848","02/20/2017 23:18:46",5,"Replace direct buffers with pooled heap buffers ""Direct buffers depend on garbage collection for the memory to be released, plus allocating bunch of them for small buffer sizes is not truly performant.u They should be replaced with pooled heap buffersjhh""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11850","02/21/2017 13:11:18",0,"Paths for processors in dynamically referenced subflows are not recalculated ""Since the dynamically referenced subflows' are remembered to if there were already calculated, if the referenced subflow (2) had a reference to another subflow (3), the first time it is called it will work. If in another execution, the flow continues in another subflow (4) witch also refers to the subflow (3), the path will be null (it will not be calculated, since it was set as already calculated). Solution: do not remember paths for ""","DynamicMessageProcessorContainer",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11851","02/21/2017 15:43:07",2,"Remove skipDistributions property from pom files ""Pom files from distribution modules contain a skipDistributions property used to skip the execution of some plugins. But there is also a distributions profile that is used to include/exclude distribution modules form the build. ""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11854","02/21/2017 16:19:51",2,"Remove dependency from HTTP service to HTTP module ""HTTP service is currently depending on code from the old HTTP module. HTTP module should be removed from CE code, so the dependency must be removed. Code form the module that is required on the service must be copied to the service, then other usages of the HTTP module in CE must use the HTTP service. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11855","02/21/2017 16:59:13",5,"NullPointerException with JMS Listener ""The following configuration is throwing a NullPointerException when starting the runtime. The null pointer stacktrace is: It seems that JmsListener property 'consumerType' is lacking a default value"""," Caused by: java.lang.NullPointerException at org.mule.extensions.jms.api.source.JmsListener.onStart(JmsListener.java:141) ~[mule-module-jms-4.0-SNAPSHOT-mule-plugin/:?] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11863","02/21/2017 20:35:58",8,"Replace Extension TypeAlias with Metadata TypeAlias ""Replace uses of extension TypeAlias annotation with metadata model TypeAlias annotation.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11868","02/22/2017 17:47:25",2,"Add invalidate() method in OAuthDancer ""Add an invalidate method, receiving the resourceOwnerId where applicable, in the dancers.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11870","02/22/2017 18:25:12",0,"Support CRL in the HTTP listener ""Implement certificate validation through revocation lists for clients connecting to the HTTP listener.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11871","02/22/2017 18:43:31",2,"Add a method in the dancer to get the current state for a resourceOwner ""The returned object should be an immutable view of the current state. It must include things like what url was used for authentication, aparte from the state available already in the store.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11876","02/23/2017 15:22:57",2,"Provide a standard way to build a BindingContext from an InterceptionEvent ""This is to improve the usability of using expressions from an interceptor""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11883","02/24/2017 13:42:52",2,"Remove dependency from HTTP module to sockets transport ""HTTP module is depending on the old sockets transports, which is not private. Dependency must be removed""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11887","02/24/2017 18:41:48",0,"Add the concept of function namespace ""We need a way for different modules/plugins to contribute functions without worrying about name clashing. For that, we need some kind of mechanism that acts like a function namespace. DW currently has the concept of module but we need a way to hook that up with the runtime and analyze how it would impact the expression's syntax. Once this is done, we need to add support for it on the SDK Functions feature""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11891","02/26/2017 00:05:07",1,"NotPermittedException in http sends status 405 (method not allowed) instead of 403 (forbidden) ""When a user is authenticated bu requests something he's not allowed too, an 403 (Forbidden) status code has to be returned. Currently, Mule is returning 405, which is for when the method (GET, PUT, etc) is not allowed.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11897","03/01/2017 00:04:37",2,"When filter throws exception, the handler loses the reference to the filter ""Since the Error type/exception type mapping is based on the component that threw the exception, losing the failing filter causes the exception to not be handled correctly. Examples are: * AuthorizationFilterTestCase#testAuthenticatedButNotAuthorized * XmlSendTestCase There, the component at the moment the exception is being handled is the component following the one that threw the exception.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11906","03/02/2017 18:37:16",8,"WSC: use option resolvers to find service address ""The WSC should use the Value Resolvers to find the service address if possible. In the cases where there is not a valid address in the WSDL for example: """"Human_Resources"""" is not a well-formed address per se. the field must accept custom values, this way when no valid address has been resolved the user can specify the correct one. All this implies that the current ADDRESS parameter in the WSC connection providers moves from being @Optional to a required parameter. """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11911","03/03/2017 12:36:29",2,"Race condition with asynchronous retry policy in testConnectivity() ""When a configuration has an asynchronous retry policy, it may happen that the LifecycleAwareConfigurationInstance is stopped while the connectivity testing is still running, causing it to work with an invalid state. Also, in the case that a connectivity testing takes a long time, it may happen that a second connectivity testing is done while the previous is still running.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11912","03/03/2017 13:53:56",13,"Support Scope model in SDK ""Allow operations such as validation:all to be rendered as a ScopeModel""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11913","03/03/2017 13:56:39",13,"Support for router operations in SDK ""Support for router operations which are rendered as a RouterModel""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11914","03/03/2017 14:54:15",0,"Email transport does not invoke exception strategy when flow processing strategy is synchronous ""When an error occurs while trying to route the message received, and there was an Catch Exception Strategy configured, it is not being invoked. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11915","03/03/2017 15:21:34",2,"LockFactory is not initialized before initializing an object that uses it ""This is seen in LifecycleAwareConfigurationInstance. When it is initialized, the injected LockFactory has not been initialized yet. It is expected when initializing/starting an object that all of its dependencies have been initialized/started respectively.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11917","03/03/2017 19:01:45",0,"Error message evaluating a Dataweave Expression is not shown in the app log. ""Error message evaluating a Dataweave Expression is not shown in the app log. It only shows the expression that failed but not the error that is sent by Dataweave: {quote} Message : Execution of the expression """" %dw 1.0 %output application/java --- payload.entry map ((entry , indexOfEntry) -> { DATE_OF_BIRTH: entry.resource.birthDate, GENDER: """"M"""" when (entry.resource.gender) == """"male"""" otherwise """"F"""", LAST_NAME: entry.resource.name[0].family[0], FIRST_NAME: entry.resource.name[0].given[0], CONCAT_NAME: entry.resource.name[0].given[0] ++ """" """" ++ entry.resource.name[0].family[0], PHONE: entry.resource.telecom.value[0], PATIENT_ID: entry.resource.id }) """" failed. {quote} This should be showed similar to this after the fix: {quote} Message : Execution of the expression """" %dw 1.0 %output application/java --- payload.entry map ((entry , indexOfEntry) -> { DATE_OF_BIRTH: entry.resource.birthDate, GENDER: """"M"""" when (entry.resource.gender) == """"male"""" otherwise """"F"""", LAST_NAME: entry.resource.name[0].family[0], FIRST_NAME: entry.resource.name[0].given[0], CONCAT_NAME: entry.resource.name[0].given[0] ++ """" """" ++ entry.resource.name[0].family[0], PHONE: entry.resource.telecom.value[0], PATIENT_ID: entry.resource.id }) """" failed with this error """"Unexpected character ']' at payload@[2:1] (line:column), expected false or true or null or {...} or [...] or number. at """"use"""": """"home"""", {quote}""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11919","03/03/2017 20:33:55",2,"MULE_HOME & MULE_BASE getting set twice in Mule startup ""When you start Mule Standalone with {{./bin/mule}}, the environment variables MULE_HOME and MULE_BASE are being set twice. Log: """," MULE_HOME is set to /opt/mule-enterprise-standalone-4.0-SNAPSHOT MULE_BASE is set to /opt/mule-enterprise-standalone-4.0-SNAPSHOT Running in console (foreground) mode by default, use Ctrl-C to exit... MULE_HOME is set to /opt/mule-enterprise-standalone-4.0-SNAPSHOT MULE_BASE is set to /opt/mule-enterprise-standalone-4.0-SNAPSHOT Running Mule Enterprise Edition... ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11933","03/07/2017 12:56:57",8,"Update all Mule component's parameters to be compatible with DW ""*Review all Mule components parameters to be compatible with DW* * Review scopes (for-each), routers (choice), filters, and every component parameter and validate if they provide the correct expected *DataType* when evaluating a DW expression. ** E.g.: the {{}} implementation to automatically save the variable with the MimeType that the evaluated expression provides.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11934","03/07/2017 15:12:07",1,"errors for operation are empty if extension doesn't have @ErrorTypes ""I have an operation with a method that has a @Throws annotation: If the extension doesn't have the @ErrorTypes annotation, the `errors` field for that operation is empty in the generated extension model json file. It should fail when building the extension, saying that the @ErrorTypes is required when using @Throws. The consistency between the ErrorTypeProviders and the enum with the ErrorTypes should be enforced and validated too."""," @Throws(MyErrorTypeProvider.class) public void method(@Content Object payload) { ... } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11936","03/07/2017 17:56:46",0,"IllegalArgumentException: Can not set final java.lang.String field org.mule.runtime.api.metadata.DefaultMetadataKey.id to org.mule.runtime.extension.api.metadata.NullMetadataKey ""IllegalArgumentException when trying to serialize a NullMetadataKey""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11937","03/07/2017 19:12:00",3,"Multiline parameter documentation is truncated in the extension model ""When an operation method with parameters, and with javadoc for a parameter that is so long it continues in the next line, when generating the json extension model for that parameter only the first line is put in the *description* field.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11939","03/08/2017 13:50:59",2,"HTTP extension does not leverage cursor streaming ""HTTP Extension is not able to use new Cursor Streaming ability provided by SDK. Try to set a custom streaming strategy and see it fails: """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11941","03/08/2017 17:13:11",8,"Operation, Scope and Router models should extend ProcessorModel ""Currently, ScopeModel and RouterModel extend OperationModel. Although not incorrect, the model will be more clear an extensible if those three extend a new ProcessorModel abstraction, which extends ComponentModel""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11942","03/08/2017 17:21:03",5,"Missing information about metadata key when resolving operation metadata ""When resolving operation metadata the key which was used to resolve the metadata was not set to the MetadataAttributes therefore there was no information about it. This has been partially fixed by adding the following line has been added to {{org.mule.runtime.module.extension.internal.metadata.MetadataMediator}}: {{attributesBuilder.withKey(newKey(keyValue.toString()).build());}} Still this is not the correct fix as the keyValue at this point is an object and the information related to the key cannot be obtained and mapped to a {{MetadataKey}}. ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11943","03/08/2017 19:20:21",8,"Make the core extension model available through the tooling client ""Provide a way in the tooling client to use the extension model for core components introduced with MULE-11496.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11945","03/09/2017 13:21:13",1,"Fix threading flaky tests ""Fix the following flaky tests: * ExpiryMonitorTestCase * TextFileStoreTestCase * DefaultSchedulerQuartzTestCase * DefaultSchedulerScheduleTestCase * DefaultSchedulerTerminationTestCase""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11954","03/09/2017 20:08:40",5,"Create extension model loader for models created manually ""While creating a plugin (not an extension), there should be a way to add an extension model to it, so the tooling can generate the UI. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11957","03/10/2017 16:07:06",1,"LazyMuleArtifactContext initializeComponents do not rebuild minimal apps in some scenarios ""On initializeComponents in LazyMuleArtifactContext it could happen that minimal app is not regenerated and ends being inconsistent with location in request.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11958","03/10/2017 17:18:45",3,"Error when trying to read certificate signature on SFTP ""When running on Oracle JDK 8u121, some SFTP tests are randomly failing with the following error: Inner exception is: Verification of signature fails because leading 0 are removed (that was not validated before). http://stackoverflow.com/questions/41987227/signature-length-not-correct-when-calling-pgponepasssignature-verify http://stackoverflow.com/questions/30907205/jsch-not-working-with-certain-sftp-servers Related info: https://bugs.openjdk.java.net/browse/JDK-8174719"""," com.jcraft.jsch.JSchException: Session.connect: java.security.SignatureException: Invalid encoding for signature at com.jcraft.jsch.Session.connect(Session.java:558) at com.jcraft.jsch.Session.connect(Session.java:183) at org.mule.extension.ftp.internal.sftp.connection.SftpClient.connect(SftpClient.java:151) at org.mule.extension.ftp.internal.sftp.connection.SftpClient.login(SftpClient.java:133) at org.mule.extension.ftp.SftpTestHarness.createDefaultSftpClient(SftpTestHarness.java:91) at org.mule.extension.ftp.SftpTestHarness.doBefore(SftpTestHarness.java:66) at org.mule.extension.AbstractFtpTestHarness.before(AbstractFtpTestHarness.java:51) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.lang.Thread.run(Thread.java:745) java.io.IOException: Invalid encoding: redundant leading 0s at sun.security.util.DerInputBuffer.getBigInteger(DerInputBuffer.java:152) at sun.security.util.DerValue.getBigInteger(DerValue.java:512) at sun.security.provider.DSA.engineVerify(DSA.java:281) at sun.security.provider.DSA.engineVerify(DSA.java:244) at java.security.Signature$Delegate.engineVerify(Signature.java:1219) at java.security.Signature.verify(Signature.java:652) at com.jcraft.jsch.jce.SignatureDSA.verify(SignatureDSA.java:145) at com.jcraft.jsch.KeyExchange.verify(KeyExchange.java:271) at com.jcraft.jsch.DHECN.next(DHECN.java:178) at com.jcraft.jsch.Session.connect(Session.java:326) at com.jcraft.jsch.Session.connect(Session.java:183) at org.mule.extension.ftp.internal.sftp.connection.SftpClient.connect(SftpClient.java:151) at org.mule.extension.ftp.internal.sftp.connection.SftpClient.login(SftpClient.java:133) at org.mule.extension.ftp.internal.sftp.connection.SftpConnectionProvider.connect(SftpConnectionProvider.java:77) at org.mule.extension.ftp.internal.sftp.connection.SftpConnectionProvider.connect(SftpConnectionProvider.java:37) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11961","03/11/2017 16:15:16",1,"Prepare HTTP service for extension ""Some minor changes need to be made so that the HttpServiceImplementation can be extended.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11963","03/13/2017 15:04:30",5,"Improve error message for JmsAcknowledgement operations when the SessionInformation doesn't exist anymore ""*Improve error message for JmsAcknowledgement operations when the SessionInformation doesn't exist anymore* * Nowadays when a manual ACK or Session Recover is executed, the SessionInformation retrieved using an *ackId*, if the session has been already recovered or acknowledged, this SessionInformation is eliminated. * When a manual ACK/Session Recover is executed there is no way to detect if the acction is not possible due the possible three scenarios: ** The session has been acknowledged ** The session has been recovered ** The ackId is invalid""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11964","03/13/2017 15:34:03",8,"Review JMS Listener's consumers usage implementation ""*Review JMS Listener's consumers usage implementation* * In 3.x the JMS Listener can be configured to listen for messages using multiple consumers at the same time, this capability was removed in 4.x. * In 4.x to be able to maintain the """"Sync"""" capability of the listener, the different consumers must be from different sessions, so we can maintain the unitary ACK/Session recover over just one message. * Re-adding this capability implies: ** If it is possible to create a session per consumer. ** A rework in the JMS Listener to support multiple consumers. ** How this is going to work when the destination is a TOPIC""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11971","03/14/2017 13:10:52",0,"Improve DW performance ""Current tests show a significant performance issue in DW when compare to MEL, mostly caused by repeated iterations than can be avoided. We need to analyse the tests and address the bottlenecks found. For simple evaluation of payload current numbers (March 14) are: *MEL:* Time: 580 nS/op Allocation: 1850 Bytes/op *DW:* Time: 4100 nS/op Allocation: 6900 Bytes/op ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11975","03/14/2017 18:57:49",2,"Make plugin dependencies work with compile scope ""Currently, plugin dependencies are required to be declared as *provided* to be correctly handled by the test classifier. The should have compile scope.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13445","03/15/2017 14:55:01",1,"Avoid usage of SPI on ThreadPoolFactory ""ThreadPoolFactory from mule 3.x has support to provide different thread pools depending on whether the runtime was a CE or EE version. As compatibility is now EE only, there is no need to maintain this functionality and the code would be more easy to read and performant without using SPI""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11978","03/15/2017 16:19:31",8,"CursorStreamProvider is closed too early ""As a side effect of MULE-11881, SSAuthenticationAgainstMultipleProvidersTestCase in the compatibility plugin is broken. This is because the provider is being closed before the listener gets to open a new cursor to send the response.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11980","03/15/2017 18:31:52",0,"Apply package renaming from compatibility plugin ""Some classes from compatibility referenced on CE code were moved to a different package. Need to fix these references: * org.mule.compatibility.core.context.notification.EndpointMessageNotification * org.mule.compatibility.core.api.context.notification.EndpointMessageNotificationListener""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11982","03/15/2017 20:44:37",8,"Boot packages needs to be removed and modules must explicitly define what they export ""ContainerClassLoaderFactory.BOOT_PACKAGES defines a set of packages exported by container modules that must always be loaded by the container class loader. This means that, if a service has a dependency to javax.mail but javax.mail packages are defined as BOOT_PACKAGES, then the service class loader will not try to load the javax.mail class never and will always delegate to the container class loader. The problem is that, if the dependency with that package is not longer bundled in lib/opt in the container, then the service, even if it bundles javax.mail, it won't be able to load the class resulting in a NoDefClassFoundException.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11986","03/15/2017 22:10:38",1,"Declaration fails to serialize list of strings ""Declaration fails to serialize list of strings""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11987","03/15/2017 22:42:15",2,"Periodic jobs are cancelled when a trigger happens when the threadpool is busy ""When running a periodic job, if one of the runs is to be executed at the moment its target scheduler is busy (no idle threads), a RejectedExecutionException is thrown and because of that, the job is cancelled not running ever again. The execution should be skipped and tried to run again at the next trigger.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11994","03/16/2017 19:50:44",3,"Default values not shown for ObjectTypes in generated docs ""Look at the ftp connector generated docs. Things like the PoolingProfile have all their fields described, but the default values are not shown. They should.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-11997","03/17/2017 13:00:59",3,"Define API for service configuration/override ""Define an API for service override. There are two use cases: * The runtime wants to override itself. E.g: Overriding the StreamingManager implementation in EE * A custom distribution wants to override something via core extension. E.g.: Override the queue manager when in cluster mode, override the object store manager when in CH""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12001","03/17/2017 23:46:50",5,"ArtifactDeclarationLoader support for EE namespace ""ArtifactDeclarationLoader support for EE namespace in infrastructure parameters""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12002","03/17/2017 23:54:57",1,"Revisit DslSyntaxUtils as part of the API ""Revisit DslSyntaxUtils as part of the API""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12003","03/18/2017 00:00:23",1,"Change the default value for output type field in the HTTP Request ""Change the default value for output type field in the HTTP Request (advance > other setting > output type field) from Any to Stream""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12004","03/20/2017 02:37:39",8,"[Perf] Review GC tunning for Mule 4 when used from Tooling Client ""As part of the root cause analysis for MULE-11950 I found that when using Mule Runtime to deploy and deploy several times applications on Mule 4 the classloaders for each application is disposed/closed but the classes are not unloaded from the JVM. After a while and doing the deploy/undeploy operation for more 150 times the response times for the JVM starts to be 4 or 5 times greater than it was for the first deploys. For the time being Tooling has defined that the Metaspace should be sized to 256m but this ticket is about finding the root cause of this and define if needed the correct GC tunning for Mule.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12010","03/20/2017 15:16:31",8,"Bundle import/export of declaration in a single Artifact serializer ""Bundle import/export of declaration in a single Artifact serializer. Currently we have one way to import the declaration from an xml, and one way to export, in a diferent api. We should have a single bundle that allows both import/export of declarations AND dslElementModels. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12011","03/20/2017 15:53:16",8,"Spike on Support Transactions in Sources ""Spike on Support Transactions in Sources""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12012","03/20/2017 16:02:14",5,"Review Source Transactions ""Review Source Transactions""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12017","03/21/2017 14:47:30",0,"JMSAppender not property closed after application is undeployed ""When an application uses JMSAppender to log through JMS, the current log4j version (2.5) doesn't close the connection to the queue when the logger context is stopped. This is fixed in 2.7.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12021","03/21/2017 18:58:29",8,"Remove services to their own repositories ""We need to determine a way to provide pathces/fixes for services artifacts. For plugins/extensions this will be achieved by having them in their own repo, with their own lifecycle and releasing the whole plugin instead of doing a patch. It has yet to be determined what to do for services in a similar scenario""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12239","03/21/2017 22:27:42",8,"When objects form a plugin are being registered, the context classloader is the one from the app instead of the plugin ""For non-extension plugins, it should be enforced that the classloader to use when loading plugin classes and resources (for instance, when putting those in the registry) is the classloader of the plugin. Currently it is the classloader for the app, This is currently worked around by exporting additional stuff from said plugins os its internal stuff can be loaded from the appllication classloader. Those exports should be trimmed as part of this fix. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12029","03/22/2017 17:32:45",8,"Pom properties are not being resolved when loading the dependencies from the pom file ""When properties are used to define a dependency version within a plugin or an application inside the pom file, then it fails to resolve the dependencies. The problem is that we are not creating the resolved model for maven, we are just loading the file content into a Model instance.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12030","03/22/2017 17:53:54",2,"Make mule.test.mel.default sysporp set the default not exclusively ""Currently, the *mule.test.mel.default* sysprop is forcing MEL as the expression language, even for DW full scripts or one-line dw expressions with the *dw:* prefix. The sysprop should only affect expressions without prefix.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12033","03/23/2017 00:29:31",8,"Set the stage for introducing object streaming ""Make necessary refactors and changes so that we can introduce object streaming while leveraging and reusing all the infrastructure created for the CursorStream functionality, specially the one which prevents leaks""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12036","03/23/2017 13:50:57",5,"Validate WSC connection ""Properly validate the connection by making an HTTP request to the provided address.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12037","03/23/2017 14:13:21",1,"Update external extensions parent pom with Mule services dependencies ""Update external extensions parent pom with services dependencies""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12039","03/23/2017 16:16:28",8,"Change how configuration resolution works ""The configuration resolution for operations without an explicit reference is sometimes confusing: a. If you don't have a validation configuration, it will create and use a default one. b. If you have only 1 validation configuration, it will be automatically used as the default one. c. If you have more than 1, you need to specify on each validation operation what configuration to use. Consider the following 3-step scenario using the validations extension: 1) You initially develop Validation_A, which has no need for a validation configuration. Therefore you leave config-ref blank. Validation A works successfully. 2) Later, you develop Validation_B, which needs Validation_Configuration_1. Validation_B references Validation_Configuration_1, and it works. However, now, without changing anything about Validation_A, it now uses a completely different validation configuration, and it may not work. 3) Even later, you develop Validation_C, which needs Validation_Configuration_2. Validation_C references Validation_Configuration_2, and it works. However, now, while still not changing anything about Validation_A, it fails completely (and it goes uncaught until runtime!!!). As it works now, making a change completely unrelated to a working validation can cause that validation not to work. After talking with my fellow developers, we agreed: a validation with no config-ref should work the same way no matter how many validation configurations exist within the project. We can see a case for a validation always being required to define a config-ref. Or we can see a case for a validation with no config-ref always using the default configuration. But we do not think it makes sense for a validation with no config-ref to work differently (and potentially break) depending on how many unreferenced validation configurations are in the project. We need to change to: * Operations without a config-ref will share the same implicit config (when possible), even if several explicit configs are defined * Operations with an explicit config ref with honour that config, even if an implicit one was created.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12042","03/23/2017 16:37:43",8,"Empty Failure Expression evaluated positive in Catch Message Exception ""Description When a until-succcessful scope is within a catch message exception it completes an unexpected behaviour wheh the failure expression is empty. The failure expression will be evaluated only if the flow didn't throw an exception. In order to fail only when a specific type of error is thrown. However when the contents of the failureExpression is empty, it's default is to populate the failure expression with """"exception-type:"""". if (failureExpression != null) { failureExpressionFilter = new ExpressionFilter(failureExpression); } else { failureExpressionFilter = new ExpressionFilter(""""exception-type:""""); } This means that the failure expression seems to always run. ""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12043","03/23/2017 17:58:56",2,"In AbstractXPathExpressionEvaluator, replace the cache WeakHashMap with a guava cache ""AbstractXPathExpressionEvaluator uses a WeakHashMap for caching, but the keys are String's and it is recommended for WeakHashMap entries to do equals by identity, which is not the case here. It should be changed to a guava cache, with a max size instead of depending on the garbage collector.""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12046","03/23/2017 19:27:16",0,"IMAP decode special character in username and password twice ""AbstractMailConnector decodes username and password although they were already decoded while creating the DefaultInboundEndpoint. This usually does not have any bad effect, except when the password includes a '%' character.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12048","03/23/2017 21:44:12",1,"Container should not export /META-INF/mule-module.properties files ""Container is exporting /META-INF/mule-module.properties files, apparently those files are used on the isolated test runner in order to properly create the classloader for the test. But is not correct that those files are exported, is required to review why they should be exported and find another way to do the same without doing it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12049","03/24/2017 12:20:33",2,"Different javascript engine are used on unit and isolated tests ""Unit tests on the scheduler service are using the javascript engine provided by the JDK. On the container or isolated tests, however, the used engine is the one that come from the scripting module, ie, Rhino. The problem appears to be related to the fact that the nashorn implementation is being filtered on the container classloader, so the service is not able to load it and falls back to Rhino.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12051","03/24/2017 17:00:41",8,"All functional tests from CE must use the isolated test runner ""There are many functional test cases on CE that are running without isolation, ie, they are not extending from MuleArtifactFunctionalTestCase but from FunctionalTestCase or ExtensionFunctionalTestCase. Those test must be migrated to properly test the components""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12255","03/25/2017 23:40:38",2,"Migrate testing namespaces to plugins ""There are namespaces used for testing, i.e.: *mule-test.xsd*, The functionality provided by such namespaces must be migrated to a plugin and use the new parsers Break the dependency of the classes in the test plugin with the *Component* interface.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12055","03/27/2017 14:16:41",8,"MULE-7211: SftpAutoDeleteTestCase (flaky test) ""endpointAutoDeleteFalse[explicit-connector]""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12056","03/27/2017 16:06:03",2,"Move combine-collections-transformer to compatibility module ""Move combine-collections-transformer to compatibility module""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12057","03/27/2017 16:12:33",2,"DataWeave should be used to encrypt payloads in idempotent-secure-hash-message-validator ""DataWeave should be used to encrypt payloads in idempotent-secure-hash-message-validator. Also, the tests should test this functionality. Check: https://github.com/mulesoft/data-weave/issues/121  ""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12061","03/27/2017 18:39:09",5,"Remove the RouteModel and replace with ScopeModel ""Remove the RouteModel and replace with ScopeModel ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12066","03/28/2017 12:04:53",5,"Support XA transactions in SDK extensions at source level "" *Support XA transactions in SDK extensions at source level* * With https://www.mulesoft.org/jira/browse/MULE-12011 and https://www.mulesoft.org/jira/browse/MULE-11221 Sources started to be able to participate in transactions. * But nowadays the sources are not able to init an *XA transaction*. The support of XA transactions implies: ** The Source should be communicated which kind of transaction the Mule developer want to create: *LOCAL*, *MULTI*, *XA* and depending on this value, the kind of transaction that should be created.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12068","03/28/2017 14:57:39",8,"Add TransformerFactory to our XMLSecureFactories ""Some months ago we reviewed all usages of potentially susceptible classes to XXE vulnerabilities. Recently, our reference wiki page included TransformerFactory and SAXTransformerFactory. See https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Prevention_Cheat_Sheet We should add the corresponding fixes for prevention, and determine if they are actually issues affecting us. Sources to check: - modules/xml/src/main/java/org/mule/module/xml/filters/SchemaValidationFilter.java: Validator, SchemaFactory - modules/json/src/main/java/org/mule/module/json/transformers/TransformerInputs.java: SchemaFactory, TransformerFactory - modules/xml/src/main/java/org/mule/module/xml/transformer/AbstractXmlTransformer.java: TransformerFactory - modules/xml/src/main/java/org/mule/module/xml/transformer/XsltTransformer.java: TransformerFactory - modules/ws/src/main/java/org/mule/module/ws/consumer/WSDLUtils.java: TransformerFactory - modules/xml/src/main/java/org/mule/module/xml/util/XMLUtils.java: TransformerFactory - modules/xml/src/main/java/org/mule/module/xml/expression/JaxpXPathExpressionEvaluator.java: XPathExpression - modules/xml/src/main/java/org/mule/module/xml/xpath/JaxpXPathEvaluator.java: XPathExpression""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12075","03/29/2017 15:50:02",8,"Serialization issues in EventContext ""When a child context is serialized an deserialized, its reference to the parent context is lost. The newly deserialized child context has a cloned parent context, so when trying to notify its parent, all who are expecting on the parent context miss the notification. This is manifested with the following tests, that must be added in *DefaultEventContextTestCase*: Also, when running in integration tests, the transient fields are not reinitialized after the deserialization (*readObject* is not called)"""," @Test @Description(""""Parent EventContext only completes once response publisher completes with no value and all child contexts are """" + """"complete."""") public void childSuccessWithNoResultAfterSerialization() throws Exception { EventContext parent = create(getTestFlow(muleContext), """"""""); EventContext child = serializeDeserializeChildContext(DefaultEventContext.child(parent)); child.success(); parent.success(); assertNullResponse(child); assertCompletionDone(child); assertNullResponse(parent); assertCompletionDone(parent); } @Test @Description(""""Parent EventContext only completes once response publisher completes with no value and all child contexts are """" + """"complete, even when child context completes after parent context response."""") public void childDelayedSuccessWithNoResultAfterSerialization() throws Exception { EventContext parent = create(getTestFlow(muleContext), """"""""); EventContext child = serializeDeserializeChildContext(DefaultEventContext.child(parent)); parent.success(); assertNullResponse(parent); assertCompletionNotDone(parent); assertCompletionNotDone(child); child.success(); assertNullResponse(child); assertCompletionDone(child); assertCompletionDone(parent); } @Test @Description(""""Parent EventContext only completes once response publisher completes with error and all child contexts are """" + """"complete."""") public void childErrorAfterSerialization() throws Exception { EventContext parent = create(getTestFlow(muleContext), """"""""); EventContext child = serializeDeserializeChildContext(DefaultEventContext.child(parent)); RuntimeException exception = new RuntimeException(); child.error(exception); parent.error(exception); assertResponseNotDone(child); assertCompletionDone(child); assertResponseNotDone(parent); assertCompletionDone(parent); } private EventContext serializeDeserializeChildContext(EventContext context) throws IOException, ClassNotFoundException { final ByteArrayOutputStream byteArrayOutputStream = new ByteArrayOutputStream(); try (ObjectOutputStream oos = new ObjectOutputStream(byteArrayOutputStream)) { oos.writeObject(context); return (EventContext) new ObjectInputStream(new ByteArrayInputStream(byteArrayOutputStream.toByteArray())).readObject(); } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12077","03/29/2017 19:20:33",8,"Allow operations to override parameters from config ""Operations which override a param from the config is a very common pattern. However, right now, the user needs to: i) declare the parameter ii) check if it was provided iii) if not, fetch the value from the config Besides being cumbersome, it requires null handling which is something we would like to avoid with certain types such as booleans. We need a feature in which we could declare the parameter to be an override of the config: Take aways: * The operation must require a configuration. If it doesn't, compilation should fail * The parameter MUST have the same name as the config parameter being overriden * The parameter will automatically be marked as optional and will not have a default. Using @Optional in tandem with @ConfigOverride will be invalid * Other annotations such as @ExpressionSupport are valid The SDK will automatically do the value resolution, injecting either the operation's own value or whatever value was assigned on the config """," public InputStream request(@ConfigOverride @ExpressionSupport(REQUIRED) int port) { } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12078","03/29/2017 19:33:01",5,"Auto paging operations must have a fetchSize parameter ""All auto paging operations must have a fetchSize parameter which needs to be injected into the PagingProvider. It has to be automatically injected by the SDK""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12079","03/29/2017 19:37:02",5,"Auto paging operations should not have a @Connection parameter ""Right now, auto paging operations fail if they don't include a connection parameter. This is not only wrong (since most operations only need the connection inside the paging provider) but can also lead to problems since the developer could get confused and use the connection received in the operation instead of the one in the paging provider. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12080","03/29/2017 19:41:43",8,"Verify that dynamic metadata works well with auto paging operations ""Verify that auto paging operations with a custom output resolver correctly notify their metadata. The user should provide an output resolver for the pages items, but the communicated MetadataType should be an array of such type. you have to: * Verify that tests like this exist for non paged operations (List) * Add tests for similar auto paging operation (PagingProvider) * Add test for non paged operation with output resolver (List -> List) * Add similar test for paged operation with output resolver (PagingProvider -> List) If any of the above don't work, make them.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12136","03/29/2017 20:00:27",5,"Implement off heap object streaming ""Add a file store option for object streaming""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12084","03/30/2017 12:00:26",0,"Refactor connectivity testing service to use maven dependencies ""Due to the changes related to using maven for dependencies in applications, the connectivity service is broken. We need to update it to use maven.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12088","03/30/2017 15:04:09",1,"Fix extension's string formats and unused generics ""Fix extension's string formats""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12089","03/30/2017 15:20:07",0,"Parser enters an exception loop on flow-ref ""The test EEStreamingExtensionTestCase has the following config: The test passes with this configuration. However, that configuration could be simplified like this: After introducing the flow-ref, the test starts failing like this: (log was trimmed because of text length limitations, this actually enters a loop until the test times out) """," ================================================================================ = Testing: fileStoreStreaming = ================================================================================ WARN 2017-03-30 11:16:59,406 [Time-limited test] org.mule.runtime.config.spring.MuleXmlBeanDefinitionReader: Ignored XML validation warning org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://www.mulesoft.org/schema/mule/marvel/current/mule-marvel.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not . at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) ~[xercesImpl-2.11.0.jar:?] at org.apache.xerces.util.ErrorHandlerWrapper.warning(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaWarning(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument1(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.XMLSchemaValidator.findSchemaGrammar(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.XMLSchemaValidator.getGlobalElementDecl(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.SubstitutionGroupHandler.getMatchingElemDecl(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.models.XSDFACM.oneTransition(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.XMLSchemaValidator.emptyElement(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) [spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleDocumentLoader.loadDocument(MuleDocumentLoader.java:86) [classes/:?] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadDocument(XmlBeanDefinitionReader.java:429) [spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:391) [spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) [spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) [spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) [spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleArtifactContext.createInitialApplicationComponents(MuleArtifactContext.java:305) [classes/:?] at org.mule.runtime.config.spring.MuleArtifactContext.loadBeanDefinitions(MuleArtifactContext.java:290) [classes/:?] at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129) [spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:541) [spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:452) [spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:113) [classes/:?] at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:90) [classes/:?] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:49) [classes/:?] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:45) [classes/:?] at org.mule.runtime.core.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:130) [classes/:?] at org.mule.runtime.core.lifecycle.RegistryBrokerLifecycleManager.fireInitialisePhase(RegistryBrokerLifecycleManager.java:54) [classes/:?] at org.mule.runtime.core.registry.AbstractRegistryBroker.initialise(AbstractRegistryBroker.java:45) [classes/:?] at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:121) [classes/:?] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:77) [classes/:?] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:74) [classes/:?] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.invokePhase(MuleContextLifecycleManager.java:62) [classes/:?] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:56) [classes/:?] at org.mule.runtime.core.DefaultMuleContext.initialise(DefaultMuleContext.java:315) [classes/:?] at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:220) [classes/:?] at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:82) [classes/:?] at org.mule.tck.junit4.AbstractMuleContextTestCase.createMuleContext(AbstractMuleContextTestCase.java:235) [classes/:?] at org.mule.tck.junit4.AbstractMuleContextTestCase.setUpMuleContext(AbstractMuleContextTestCase.java:155) [classes/:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_112] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_112] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_112] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_112] at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) [junit-4.12.jar:4.12] at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) [junit-4.12.jar:4.12] at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) [junit-4.12.jar:4.12] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_112] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112] Caused by: java.io.FileNotFoundException: http://www.mulesoft.org/schema/mule/marvel/current/mule-marvel.xsd at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1872) ~[?:1.8.0_112] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) ~[?:1.8.0_112] at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) ~[xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) ~[xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(Unknown Source) ~[xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(Unknown Source) ~[xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.opti.SchemaDOMParser.parse(Unknown Source) ~[xercesImpl-2.11.0.jar:?] ... 59 more WARN 2017-03-30 11:16:59,769 [Time-limited test] org.mule.runtime.config.spring.MuleXmlBeanDefinitionReader: Ignored XML validation warning org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://www.mulesoft.org/schema/mule/marvel/current/mule-marvel.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not . at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) ~[xercesImpl-2.11.0.jar:?] at org.apache.xerces.util.ErrorHandlerWrapper.warning(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaWarning(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument1(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.XMLSchemaValidator.findSchemaGrammar(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.XMLSchemaValidator.getGlobalElementDecl(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.SubstitutionGroupHandler.getMatchingElemDecl(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.models.XSDFACM.oneTransition(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.xs.XMLSchemaValidator.emptyElement(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) [xercesImpl-2.11.0.jar:?] at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) [spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleDocumentLoader.loadDocument(MuleDocumentLoader.java:86) [classes/:?] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadDocument(XmlBeanDefinitionReader.java:429) [spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:391) [spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) [spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) [spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) [spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleArtifactContext.createInitialApplicationComponents(MuleArtifactContext.java:305) [classes/:?] at org.mule.runtime.config.spring.MuleArtifactContext.loadBeanDefinitions(MuleArtifactContext.java:290) [classes/:?] at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129) [spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:541) [spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:452) [spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:113) [classes/:?] at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:90) [classes/:?] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:49) [classes/:?] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:45) [classes/:?] at org.mule.runtime.core.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:130) [classes/:?] at org.mule.runtime.core.lifecycle.RegistryBrokerLifecycleManager.fireInitialisePhase(RegistryBrokerLifecycleManager.java:54) [classes/:?] at org.mule.runtime.core.registry.AbstractRegistryBroker.initialise(AbstractRegistryBroker.java:45) [classes/:?] at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:121) [classes/:?] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:77) [classes/:?] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:74) [classes/:?] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.invokePhase(MuleContextLifecycleManager.java:62) [classes/:?] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:56) [classes/:?] at org.mule.runtime.core.DefaultMuleContext.initialise(DefaultMuleContext.java:315) [classes/:?] at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:220) [classes/:?] at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:82) [classes/:?] at org.mule.tck.junit4.AbstractMuleContextTestCase.createMuleContext(AbstractMuleContextTestCase.java:235) [classes/:?] at org.mule.tck.junit4.AbstractMuleContextTestCase.setUpMuleContext(AbstractMuleContextTestCase.java:155) [classes/:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_112] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_112] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_112] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_112] at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) [junit-4.12.jar:4.12] at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) [junit-4.12.jar:4.12] at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) [junit-4.12.jar:4.12] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_112] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112] Caused by: java.io.FileNotFoundException: http://www.mulesoft.org/schema/mule/marvel/current/mule-marvel.xsd ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12090","03/30/2017 15:49:56",3,"Obtain flow and app name on SDK operation ""In the policies migration to SDK extensions, we found the need to have accessible the flowName and appName in the operation. We don't need to expose this information however, having them as private variables of the configuration will suffice for our use cases.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12091","03/30/2017 16:25:57",3,"Ensure that PagingProvider always gets the same connection when used in a transaction ""When auto paging is used in a transaction, each call to getPage() needs to receive the same transaction. In theory, this should be working right now. Write a test to ensure it. If the test doesn't pass, make it so.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12092","03/30/2017 16:26:40",8,"Split synchronous processing strategy into blocking and direct strategies ""Now that Event doesn't have a sync flag, operations have no way of blocking when blocking behaviour is configured at flow level or is required due to transactions. Rather than operations using event.isSynchronous() operations, where possible, should be non-blocking be default and rather the flow, via the processing strategy should block and wait for the response of these operations. """"synchronous"""" processing strategy in config should be an alias for BlockingProcessingStrategy.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12093","03/30/2017 16:28:56",3,"PagingProvider should support sticky connections ""Although not the most frequent case, some API's require that the same connection that got the first page is the one requiring the second one. An example of that is JDBC. PagingProvider should have an option to hint that the same connection should always be used. This must be an optional setting and the default should be that different connections are supported.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12095","03/30/2017 16:33:10",3,"Remove support for intercepting operations in the SDK ""Intercepting operations are evil and we don't need them anymore now that we have super awesome streaming""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12099","03/30/2017 20:05:36",2,"Remove dead-letter-queue ""Remove dead-letter-queue element and related functionality from redelivery-policy and until-successful.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12100","03/30/2017 21:02:43",1,"JMS throws NPE when receiving a message without ContentType ""JMS throws NPE when receiving a message without ContentType""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12102","03/31/2017 14:13:51",2,"Cleanup API to use ReactiveProcessor instead of publisher function ""Cleanup processing strategy API to use ReactiveProcessor instead of publisher function""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12103","03/31/2017 15:00:46",5,"imap list is returning a List instead of a List ""Check this is not the case with Pop3 as well. Also check why none of the SDK tests failed.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12107","03/31/2017 19:48:44",8,"Add Dynamic Metadata resolution support in Soap Connect. ""Basically, for a given Service and Operation, we should provide Input and Output types similar to what the WSC provides. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12110","03/31/2017 20:55:02",0,"Migrate collection-splitter to new parser in Mule 4 M5 ""Migrate collection-splitter to new parser in Mule 4 M5""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12113","03/31/2017 22:03:02",2,"Scheduler should not have implicit behaviuor ""Currently the following is supported in XML and has implicit behaviour that can only be discovered via docs or running the app. IMO, The scheduler strategy and also ideally the scheduler frequency should both be explicit in XML config and during the configuration UX when a scheduler is used to start a flow. If we want there to be a default in tooling, so that user sees and accepts a default strategy, rather than being forced to configure one then that make sense, but allowing no strategy to be seen/configured doesn't make sense. In order to support a default strategy that can be accepted rather than needing to be explicitly chosen we may need to add the ability to hint a default strategy in extension model.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12115","03/31/2017 22:37:19",0,"Expose DataSenseMetadataCacheProvider in DataSenseService ""DataSenseService should expose cached metadata provider APIs.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12116","04/02/2017 19:00:00",2,"Provide support to start server plugins from embedded API ""The embedded Mode API should provide support to start a container with Server plugins such as the debugger. ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12118","04/03/2017 15:28:40",13,"Add support for multiple consumers for JMS Listener ""*Add support for multiple consumers for JMS Listener* * Create a new session per consumer. * Review the Listener vs Polling Consumer logic * Review the semaphore implementation to work with multiple consumers""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12120","04/03/2017 16:06:25",8,"Embedded container fails to resolve version range ""The embedded container brakes with the following exception When the .M2 repository for that artifact /Users/damiansima/.m2/repository/org/jruby/jruby-core Looks like this: It's not yet clear how I manage to get that .m2, I reckon it was a side effect of studio when my application's pom contained a dependency to mule-module-all. In either case the container should know how to deal with such errors and worst case scenario end the execution properly and without an aether error."""," java.lang.RuntimeException: java.lang.RuntimeException: There was a problem resolving the dependency tree for the container [org.mule.runtime:mule-runtime-impl-bom:pom:4.0.0-SNAPSHOT] at org.mule.runtime.module.embedded.api.EmbeddedContainerFactory.create(EmbeddedContainerFactory.java:118) at org.mule.munit.remote.RemoteRunner.buildContainer(RemoteRunner.java:134) at org.mule.munit.remote.RemoteRunner.runSuite(RemoteRunner.java:104) at org.mule.munit.remote.RemoteRunner.run(RemoteRunner.java:80) at org.mule.munit.remote.RemoteRunner.main(RemoteRunner.java:66) Caused by: java.lang.RuntimeException: There was a problem resolving the dependency tree for the container [org.mule.runtime:mule-runtime-impl-bom:pom:4.0.0-SNAPSHOT] at org.mule.runtime.module.embedded.internal.Repository.assemblyDependenciesForArtifact(Repository.java:142) at org.mule.runtime.module.embedded.internal.MavenContainerClassLoaderFactory.create(MavenContainerClassLoaderFactory.java:53) at org.mule.runtime.module.embedded.api.EmbeddedContainerFactory.create(EmbeddedContainerFactory.java:57) ... 4 more Caused by: org.eclipse.aether.collection.DependencyCollectionException: Failed to collect dependencies at org.mule.runtime:mule-modules-all:pom:4.0.0-SNAPSHOT -> org.mule.runtime:mule-module-scripting:jar:4.0.0-SNAPSHOT -> org.mule.runtime:mule-module-scripting-jruby:jar:4.0.0-SNAPSHOT -> org.jruby:yecht:jar:jruby:1.1 -> org.jruby:jruby-core:jar:1.7.22 -> org.jruby:yecht:jar:1.0 -> org.jruby:jruby-core:jar:[1.7.0,1.8.0) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316) at org.mule.runtime.module.embedded.internal.Repository.assemblyDependenciesForArtifact(Repository.java:118) ... 6 more Caused by: org.eclipse.aether.resolution.VersionRangeResolutionException: No versions available for org.jruby:jruby-core:jar:[1.7.0,1.8.0) within specified range at org.eclipse.aether.internal.impl.DefaultDependencyCollector.filterVersions(DefaultDependencyCollector.java:648) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:394) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.doRecurse(DefaultDependencyCollector.java:504) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:458) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.doRecurse(DefaultDependencyCollector.java:504) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:458) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.doRecurse(DefaultDependencyCollector.java:504) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:458) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.doRecurse(DefaultDependencyCollector.java:504) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:458) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.doRecurse(DefaultDependencyCollector.java:504) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:458) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.doRecurse(DefaultDependencyCollector.java:504) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:458) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:254) ... 8 more ├── 1.7.0 │   ├── _remote.repositories │   ├── jruby-core-1.7.0.pom │   └── jruby-core-1.7.0.pom.sha1 ├── 1.7.0.preview1 │   ├── _remote.repositories │   ├── jruby-core-1.7.0.preview1.pom │   └── jruby-core-1.7.0.preview1.pom.sha1 ├── 1.7.0.preview2 │   ├── _remote.repositories │   ├── jruby-core-1.7.0.preview2.pom │   └── jruby-core-1.7.0.preview2.pom.sha1 ├── 1.7.1 │   ├── _remote.repositories │   ├── jruby-core-1.7.1.pom │   └── jruby-core-1.7.1.pom.sha1 ├── 1.7.10 │   ├── _remote.repositories │   ├── jruby-core-1.7.10.pom │   └── jruby-core-1.7.10.pom.sha1 ├── 1.7.11 │   ├── _remote.repositories │   ├── jruby-core-1.7.11.pom │   └── jruby-core-1.7.11.pom.sha1 ├── 1.7.12 │   ├── _remote.repositories │   ├── jruby-core-1.7.12.pom │   └── jruby-core-1.7.12.pom.sha1 ├── 1.7.13 │   ├── _remote.repositories │   ├── jruby-core-1.7.13.pom │   └── jruby-core-1.7.13.pom.sha1 ├── 1.7.14 │   ├── _remote.repositories │   ├── jruby-core-1.7.14.pom │   └── jruby-core-1.7.14.pom.sha1 ├── 1.7.15 │   ├── _remote.repositories │   ├── jruby-core-1.7.15.pom │   └── jruby-core-1.7.15.pom.sha1 ├── 1.7.16 │   ├── _remote.repositories │   ├── jruby-core-1.7.16.pom │   └── jruby-core-1.7.16.pom.sha1 ├── 1.7.16.1 │   ├── _remote.repositories │   ├── jruby-core-1.7.16.1.pom │   └── jruby-core-1.7.16.1.pom.sha1 ├── 1.7.16.2 │   ├── _remote.repositories │   ├── jruby-core-1.7.16.2.pom │   └── jruby-core-1.7.16.2.pom.sha1 ├── 1.7.17 │   ├── _remote.repositories │   ├── jruby-core-1.7.17.pom │   └── jruby-core-1.7.17.pom.sha1 ├── 1.7.18 │   ├── _remote.repositories │   ├── jruby-core-1.7.18.pom │   └── jruby-core-1.7.18.pom.sha1 ├── 1.7.19 │   ├── _remote.repositories │   ├── jruby-core-1.7.19.pom │   └── jruby-core-1.7.19.pom.sha1 ├── 1.7.2 │   ├── _remote.repositories │   ├── jruby-core-1.7.2.pom │   └── jruby-core-1.7.2.pom.sha1 ├── 1.7.20 │   ├── _remote.repositories │   ├── jruby-core-1.7.20.pom │   └── jruby-core-1.7.20.pom.sha1 ├── 1.7.20.1 │   ├── _remote.repositories │   ├── jruby-core-1.7.20.1.pom │   └── jruby-core-1.7.20.1.pom.sha1 ├── 1.7.21 │   ├── _remote.repositories │   ├── jruby-core-1.7.21.pom │   └── jruby-core-1.7.21.pom.sha1 ├── 1.7.22 │   ├── _remote.repositories │   ├── jruby-core-1.7.22.jar │   ├── jruby-core-1.7.22.jar.sha1 │   ├── jruby-core-1.7.22.pom │   └── jruby-core-1.7.22.pom.sha1 ├── 1.7.23 │   ├── _remote.repositories │   ├── jruby-core-1.7.23.pom │   └── jruby-core-1.7.23.pom.sha1 ├── 1.7.24 │   ├── _remote.repositories │   ├── jruby-core-1.7.24.pom │   └── jruby-core-1.7.24.pom.sha1 ├── 1.7.25 │   ├── _remote.repositories │   ├── jruby-core-1.7.25.pom │   └── jruby-core-1.7.25.pom.sha1 ├── 1.7.26 │   ├── _remote.repositories │   ├── jruby-core-1.7.26.pom │   └── jruby-core-1.7.26.pom.sha1 ├── 1.7.3 │   ├── _remote.repositories │   ├── jruby-core-1.7.3.pom │   └── jruby-core-1.7.3.pom.sha1 ├── 1.7.4 │   ├── _remote.repositories │   ├── jruby-core-1.7.4.pom │   └── jruby-core-1.7.4.pom.sha1 ├── 1.7.5 │   ├── _remote.repositories │   ├── jruby-core-1.7.5.pom │   └── jruby-core-1.7.5.pom.sha1 ├── 1.7.6 │   ├── _remote.repositories │   ├── jruby-core-1.7.6.pom │   └── jruby-core-1.7.6.pom.sha1 ├── 1.7.7 │   ├── _remote.repositories │   ├── jruby-core-1.7.7.pom │   └── jruby-core-1.7.7.pom.sha1 ├── 1.7.8 │   ├── _remote.repositories │   ├── jruby-core-1.7.8.pom │   └── jruby-core-1.7.8.pom.sha1 ├── 1.7.9 │   ├── _remote.repositories │   ├── jruby-core-1.7.9.pom │   └── jruby-core-1.7.9.pom.sha1 ├── maven-metadata-central.xml ├── maven-metadata-central.xml.sha1 ├── maven-metadata-mule.xml ├── maven-metadata-mule.xml.sha1 ├── maven-metadata-sonatype-nexus-snapshots.xml ├── maven-metadata-sonatype-nexus-snapshots.xml.sha1 ├── maven-metadata-sonatype.xml ├── maven-metadata-sonatype.xml.sha1 └── resolver-status.properties ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12121","04/03/2017 16:19:43",3,"Replace XMLGenerationService from tooling client to ArtifactSerializationService ""Replace XMLGenerationService from tooling client to ArtifactSerializationService""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12123","04/03/2017 17:16:05",2,"Add processing strategy resilience tests ""Add tests that process streams of events both success/error and mix""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12126","04/03/2017 20:43:06",5,"The SDK should communicate to the Expression Manager the expected DataType ""*The SDK should communicate to the Expression Manager the expected DataType* * Nowadays when an extension parameter value is evaluated the AttributeEvaluator doesn't communicate the expected DataType of the evaluation. * This is required for DW transformation when doing a transformation from and to different MimeTypes. * We need to take care of the Object/InputStream/(and surely other cases) cases that *SHOULD not* be communicated to prevent non-expected behavior in DW transformations. * Common POJOs and simple types should be communicated ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12129","04/03/2017 23:18:42",1,"Fails to parse valid XML config ""Deploy the following application which only contains a Spring bean definition and a file:config component. Deployment fails with the following error: {code} Caused by: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.deployment.model.api.DeploymentInitException: SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'file:config'. {code} Note that if you comment either the bean definition or the file:config element, the application deploys successfully. When nothing is commented, deployment fails. Config: {code:xml} {code}"""," Caused by: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.deployment.model.api.DeploymentInitException: SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'file:config'. ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12138","04/04/2017 19:58:00",1,"HTTP: ""Allowed methods"" field missing Summary and Example ""HTTP: """"Allowed methods"""" field missing Summary and Example. When configuring the connector there is no hint stating that the allowed methods should be passed as a """"comma separated list of HTTP methods""""""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12143","04/04/2017 21:38:37",2,"ExpressionExecutor proxy wraps exceptions causing invalid DW expression to throw error of type UNKNOWN instead of EXPRESSION ""An expression for example like: #[invalidExp] which is invalid fails with an error of type UNKNOWN, but it should fail with a EXPRESSION type. TestCase: *set-invalid-dw-config.xml* file """," public class SetInvalidDWTestCase extends AbstractIntegrationTestCase { @Override protected String getConfigFile() { return """"set-invalid-dw-config.xml""""; } @Test public void setInvalidDW() throws Exception { try { flowRunner(""""setPayload"""").withPayload(TEST_MESSAGE).run(); } catch (MessagingException e) { System.out.println(e.getEvent().getError().get().getErrorType()); } } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12147","04/04/2017 22:16:06",0,"Add proxy support for SFTP connector in 3.x ""The SFTP connector currently doesn't support proxies, but the implementation offers them so we just have to provide an interface.""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12148","04/05/2017 00:07:23",0,"Hidden error message in expression evaluation error ""When using DataWeave as an expression language, when some types of exceptions are thrown, the error message from DW is hidden, so not useful description of the error is available to the user. """," ERROR 2017-04-03 19:15:53,517 [SchedulerService_io.07] org.mule.runtime.core.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : null (java.lang.reflect.UndeclaredThrowableException). Payload Type : org.mule.runtime.core.internal.streaming.bytes.factory.AbstractCursorStreamProviderFactory$ManagedCursorStreamProvider Element : https-for-each-flow/processors/7 @ http-extension-requester:null:48 Element XML : -------------------------------------------------------------------------------- Root Exception stack trace: com.mulesoft.weave.el.RangeLocatableException at com.mulesoft.weave.el.WeaveExpressionExecutor.evaluate(WeaveExpressionExecutor.scala:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.mule.runtime.module.service.LifecycleFilterServiceProxy.invoke(LifecycleFilterServiceProxy.java:44) at com.sun.proxy.$Proxy21.evaluate(Unknown Source) at org.mule.runtime.core.el.DataWeaveExpressionLanguage.evaluate(DataWeaveExpressionLanguage.java:103) at org.mule.runtime.core.el.DataWeaveExpressionLanguage.evaluate(DataWeaveExpressionLanguage.java:82) at org.mule.runtime.core.el.ExtendedExpressionLanguageAdapter.evaluate(ExtendedExpressionLanguageAdapter.java:83) at org.mule.runtime.core.el.DefaultExpressionManager.evaluate(DefaultExpressionManager.java:127) at org.mule.runtime.core.el.DefaultExpressionManager.evaluate(DefaultExpressionManager.java:116) at org.mule.runtime.core.el.DefaultExpressionManager.parse(DefaultExpressionManager.java:224) at org.mule.runtime.core.el.DefaultExpressionManager.parse(DefaultExpressionManager.java:207) at org.mule.runtime.core.api.processor.LoggerMessageProcessor.log(LoggerMessageProcessor.java:76) at org.mule.runtime.core.api.processor.LoggerMessageProcessor.lambda$process$0(LoggerMessageProcessor.java:62) at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.util.StreamingUtils$1.applyChecked(StreamingUtils.java:48) at org.mule.runtime.core.api.util.StreamingUtils$1.applyChecked(StreamingUtils.java:44) at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.util.StreamingUtils.withCursoredEvent(StreamingUtils.java:68) at org.mule.runtime.core.api.processor.LoggerMessageProcessor.process(LoggerMessageProcessor.java:61) at org.mule.runtime.core.api.processor.Processor.lambda$apply$0(Processor.java:53) at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.rx.Exceptions.lambda$checkedFunction$3(Exceptions.java:85) at org.mule.runtime.core.internal.util.rx.Operators.lambda$nullSafeMap$0(Operators.java:35) at reactor.core.publisher.FluxHandle$HandleSubscriber.onNext(FluxHandle.java:94) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxResume$ResumeSubscriber.onNext(FluxResume.java:73) at reactor.core.publisher.FluxHandle$HandleSubscriber.onNext(FluxHandle.java:103) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxResume$ResumeSubscriber.onNext(FluxResume.java:73) at reactor.core.publisher.FluxHandle$HandleSubscriber.onNext(FluxHandle.java:103) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:691) at reactor.core.publisher.FluxResume$ResumeSubscriber.onNext(FluxResume.java:73) at reactor.core.publisher.FluxFlatMap$FlatMapMain.innerNext(FluxFlatMap.java:749) at reactor.core.publisher.FluxFlatMap$FlatMapInner.onNext(FluxFlatMap.java:945) at reactor.core.publisher.FluxResume$ResumeSubscriber.onNext(FluxResume.java:73) at reactor.core.publisher.FluxResume$ResumeSubscriber.onNext(FluxResume.java:73) at reactor.core.publisher.FluxSwitchIfEmpty$SwitchIfEmptySubscriber.onNext(FluxSwitchIfEmpty.java:68) at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:119) at reactor.core.publisher.MonoPeekTerminal$MonoTerminalPeekSubscriber.onNext(MonoPeekTerminal.java:175) at reactor.core.publisher.MonoCreate$DefaultMonoSink.success(MonoCreate.java:99) at org.mule.runtime.module.extension.internal.runtime.operation.DefaultExecutionMediator.lambda$null$4(DefaultExecutionMediator.java:130) at reactor.core.publisher.MonoPeekTerminal$MonoTerminalPeekSubscriber.onNext(MonoPeekTerminal.java:167) at reactor.core.publisher.MonoCreate$DefaultMonoSink.success(MonoCreate.java:99) at org.mule.runtime.module.extension.internal.runtime.execution.ReactorCompletionCallback.success(ReactorCompletionCallback.java:35) at org.mule.extension.http.internal.request.HttpRequester$1.lambda$onCompletion$0(HttpRequester.java:115) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.mule.service.scheduler.internal.AbstractRunnableFutureDecorator.doRun(AbstractRunnableFutureDecorator.java:89) at org.mule.service.scheduler.internal.RunnableFutureDecorator.run(RunnableFutureDecorator.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12154","04/05/2017 18:39:34",1,"Path parameter in file:write operation should be required ""Should be required""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12155","04/05/2017 18:43:59",1,"Wrong warning logged with simple expression ""A simple logging expression such as produces the following warning in the logs The message is not only wrong, when it does apply it should only be logged once, not in every simple message (see org.mule.runtime.core.util.OneTimeWarning)"""," WARN 2017-04-05 14:40:55,145 [SchedulerService_cpuLight.03] org.mule.runtime.core.el.DefaultExpressionManager: Expression parsing is deprecated, regular evaluations should be used instead. ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12157","04/05/2017 18:48:38",1,"Non descriptive error message when connected operation doesn't have a provider ""When an extension declares an operation with requires a connection, but the extension itself doesn't have any connection provider, the error thrown is not descriptive at all. The error should: * Be descriptive * Be thrown in compile time * Verify that it works with sources too""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12158","04/05/2017 18:50:51",1,"Auto paging and cursor iterators should have a getSize() ""In 3.x, auto paged iterators used to have a size() method so that MEL could be used to extract the total size. Auto paged iterators and cursor iterators in mule 4 inherit this behaviour. However, for compatibility with the new EL, the method should be renamed to getSize()""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12161","04/05/2017 19:12:41",1,"Streaming config is not validated to be coherent ""It is currently possible to do things like this: * It is possible to have an initial size bigger than the max size * An increment size greater than the maxSize * test any other crazy combinations you can think off"""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12164","04/05/2017 22:56:29",2,"Extensions documenter doesn't document correctly Message Sources ""*Extensions documenter doesn't document correctly Message Sources* * Missing parameter description text * Missing {{@Summary}} text""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12165","04/06/2017 15:02:23",8,"Echo application is blocked reserving and unreserving direct memory, which also causes OOM. ""Profilling the echo application with default configuration with the http connector, it shows a big contention when freeing memory, some allocating and a small percentaje of the requests fails do OOM error, looks like this is related to direct-memory which is not used by the streaming capability, but may be releated.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12177","04/07/2017 13:46:14",8,"Review extensions dependencies ""We must review all extensions dependencies to ensure we remove any unnecessary things that will make the final application package too heavy. This must be done on all extensions prior to Beta release.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12180","04/07/2017 18:37:14",8,"Remove async Until Successful functionality and make sync until successful non blocking ""- async until-successful is removed from mule core DSL instead flow A -> JMS/VM -> Flow B is recommended. (edited) - we could not put async until-successful in compatibility, but auto-migration to isn’t quite the same functionally (no persistence), and auto-migration to flow+vm+flow may not be trivial - sync until-successful need to be kept until we replace it with retry in in 4.x. In the mean time make it non-blocking.""","",0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12182","04/07/2017 19:04:01",0,"Provide a way to give a name to the application in embedded mode ""Embedded container is creating a folder structure to deploy the temp application in order to start the container. It does so and it also creates the folders apps/app. It then uses this """"app"""" folder to create the application descriptor in: org.mule.runtime.module.deployment.impl.internal.application.ApplicationDescriptorFactory#loadFromJsonDescriptor This translates in the logs as The folder name inside apps should be related to a parameter send to the embedded container factory or taken from the name mule-application.json: """," ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Starting app 'app' + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12183","04/07/2017 20:01:37",0,"AbstractAsyncRequestReplyRequester should not add correlation sequence to correlationID ""If request reply is inside a component that adds correlation sequence (e.g. for each), then the replied message cannot be recieved, because it is expecting the message without the correlation sequence added.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12187","04/10/2017 16:06:41",0,"Make embedded test case be able to access a maven repo with mule artifacts ""This is so if there's a maven test case using an app with a dependency not declared in the pom file of the embedded test case, it will be able to retrieve it from the public maven repo of mule""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12189","04/10/2017 17:49:42",8,"Region class loader must check that different artifacts are not exporting the same package ""Region class loader maintains a mapping that indicates which class loader must be used to load a given package. Every time a class loader is added to the region, this class loader's exported packages are added to the map, overriding any previous mapping for that particular package. This is a bug as packages exported by an app can be overridden by packages exported on a plugin. In particular, this problem was observed when migrating test using test extensions to run with the isolated test runner. In particular, extensions export classes from org.mule.tck.message and other packages, which are exported by the test (aka application) However, this bug cannot be easily fixed as other modules depend on it in order to work. Extensions have bot unit and functional test cases in the same module. This causes that the test export the same package as the production code (as unit tests are written on the same package). Then, when the extension plugin classloader is added to the test region, the region mapping is updated with that classloader.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12191","04/10/2017 19:09:24",2,"Make Infrastructure and QName model properties public ""Make Infrastructure and QName model properties public""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12192","04/10/2017 20:01:42",5,"Review QName and Infrastructure model properties ""Review QName and Infrastructure model properties""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12196","04/10/2017 23:50:24",3,"Avoid types without ID in the type catalog ""Avoid types without ID in the type catalog""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12201","04/11/2017 17:54:43",8,"App hangs when there is a dw evaluation error in the error-response ""When there is an evaluation error in the error-response of the listener, for example when evaluating inexistent variables trying to set a value to the httpStatus, the app hangs. Steps to reproduce: Deploy the following config, and hit the endpoint. As a result, the set-variable fails, trowing an exception. Then the error-response fails to evaluate the expression and the app hangs. These are the logs of that unhandled behaviour: """," ERROR 2017-04-11 13:51:25,445 [SchedulerService_cpuLight.01] org.mule.runtime.core.execution.ModuleFlowProcessingPhase: Unhandled exception processing requestorg.mule.runtime.core.api.expression.ExpressionRuntimeException: """"Script 'httpStatus ' has errors: Unable to resolve reference of VariableReferenceNode(httpStatus). at 1 : 1"""" evaluating expression: """"#[httpStatus]"""". ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12205","04/11/2017 20:34:46",0,"Support equals and hashcode in Location object ""Support equals and hashcode in Location object""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12206","04/12/2017 14:39:23",0,"SedaStageInterceptingMessageProcessor thread should clear RequestContext ""The thread in SedaStageInterceptingMessageProcessor does not clear the RequestContext, so MuleEvents could be leaked in the ThreadLocalMap (since the thread runs until application is stopped). Although the thread runs in a WorkerContext, it does not stops running until the application stops, so RequestContext.clear is only executed after that. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12207","04/12/2017 16:56:54",8,"Implement connectivity testing for Soap Connect extensions ""Implement connectivity testing for Soap Connect extensions: Currently, the ForwardingSoapClient doesn't provide a way to validate the connections because the Soap Service doesn't provide a way. The same happens in the WSC. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12593","04/12/2017 18:52:50",1,"Remove YourKit libraries and scripts ""Decide if we will continue shipping YourKit libraries in the lib/native folder, and upgrade to a newer version that supports the latest JDKs and features of YourKit. The current version that we are shipping was released in 2010 and meant for Java 6. Links: Version history - https://www.yourkit.com/download/older.html Compatibility - https://www.yourkit.com/docs/kb/tech_req.jsp UPDATE: We finally decided to remove the yourkit libraries ""","",0,0,0,1,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12211","04/12/2017 22:52:26",3,"Add Soap Connect Extension Validators ""Add validators for Soap Connect: E.g: cannot use @Soap with @Configuration.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12212","04/14/2017 00:50:47",2,"Review if the approach used to separated mule API from the implementation is the right one ""Mule API has org.mule.runtime.api.message.Message interface. Instances of that class are created using a org.mule.runtime.api.message.AbstractMuleMessageBuilderFactory implementation which is found via SPI. Mule API jar does not contain any implementation of the that factory. In a previous version of org.mule.runtime.api.message.Message class, there was a NULL_MESSAGE constant which, in order to be built, it required a builder to be available on the class path. Because of some change required to provide a privileged API, the container classloader has to be used to find the message factory, instead of using the current thread's context classloader. This change, made visible a problem with the API/implementation approach as under some scenarios, there is no message builder factory available. For example, the extensions maven plugin used to build SDK extensions, depends on Mule API only. When extensions has org.mule.runtime.api.message.Message on their API, then the plugin will need to load that class to do some processing. This will fail, as before, if there is any message constant that require to be build on the Mule API side. For these reasons, will have to review if the approach used to separated mule API from the implementation is the right one.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12213","04/14/2017 14:35:58",3,"OpUx transformation outputs blank value ""In a flow which payload is a list of maps, the following works well: One file is written per map in the list, in csv mode. This other chain should be perfectly equivalent: However, the above outputs empty files only"""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12215","04/17/2017 12:32:36",3,"Create the concept of Literal ""Add a way to obtain parameter values as they were entered in the DSL. No transformation nor expression evaluation. When used in configs, those parameters should not cause the config to be dynamic, even if values are expressions""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12216","04/17/2017 16:21:33",2,"Eliminate thread contention due to use of java.lang.ClassLoader#getSystemClassLoader in ArtifactAwareContextSelector ""I have not yet measured the raw impact of this contention, but ideally it should not even exist,""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12218","04/17/2017 16:30:53",2,"Reduce overhead of debug log statements by using isDebugEnabled ""Currently logging in EventContext implementations uses getClass(), without a isDebugEnabled contain creating unnecessary overhead.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12223","04/17/2017 18:42:06",1,"'File already exists' exception when building extension ""If you build an extension using the extensions-maven-plugin, you often get a """"File already exists"""" message, unless you perform a Maven clean. The plugin should overwrite the generated files to avoid this error. Log: """," 13:27:59 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.mule.runtime.plugins:mule-extensions-maven-plugin:1.0.0-SNAPSHOT:extension-descriptor (default-extension-descriptor) on project mule-module-ftps: There was an issue copying the descriptor file from [/scratch/jenkins/workspace/Pull-Requests-4.x-EE-Freestyle-Project/extensions/ftps/target/classes/META-INF/mule-plugin.json] to [/scratch/jenkins/workspace/Pull-Requests-4.x-EE-Freestyle-Project/extensions/ftps/target/temporal-mule-plugin.json] 13:27:59 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) 13:27:59 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) 13:27:59 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) 13:27:59 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) 13:27:59 at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185) 13:27:59 at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:181) 13:27:59 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 13:27:59 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 13:27:59 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 13:27:59 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 13:27:59 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 13:27:59 at java.lang.Thread.run(Thread.java:745) 13:27:59 Caused by: org.apache.maven.plugin.MojoExecutionException: There was an issue copying the descriptor file from [/scratch/jenkins/workspace/Pull-Requests-4.x-EE-Freestyle-Project/extensions/ftps/target/classes/META-INF/mule-plugin.json] to [/scratch/jenkins/workspace/Pull-Requests-4.x-EE-Freestyle-Project/extensions/ftps/target/temporal-mule-plugin.json] 13:27:59 at org.mule.extension.maven.ExtensionDescriptorMojo.execute(ExtensionDescriptorMojo.java:95) 13:27:59 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) 13:27:59 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) 13:27:59 ... 11 more 13:27:59 Caused by: java.nio.file.FileAlreadyExistsException: /scratch/jenkins/workspace/Pull-Requests-4.x-EE-Freestyle-Project/extensions/ftps/target/temporal-mule-plugin.json 13:27:59 at sun.nio.fs.UnixCopyFile.copy(UnixCopyFile.java:551) 13:27:59 at sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:253) 13:27:59 at java.nio.file.Files.copy(Files.java:1274) 13:27:59 at org.mule.extension.maven.ExtensionDescriptorMojo.execute(ExtensionDescriptorMojo.java:93) 13:27:59 ... 13 more ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12224","04/17/2017 18:51:53",5,"Provide support for scope as top level elements ""Extension model should provide support to flag scope elements as top level elements""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12230","04/17/2017 20:22:10",0,"FtpConnector should take into account that Files could have been consumed ""If the files in an FTP Server are consumed between it is checked wether it is a directory or a File (e.g. an external Ftp Client), then the block in FtpConnector:670 is executed resulting in a ArrayIndexOutOfBoundException""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12232","04/17/2017 21:44:22",3,"Introduce the concept of FlowListener ""Advanced operations need to be able to be notified of the owning flow's result, in order to do log, audit, resource deallocation, etc. Currently, the mechanism for doing that is intercepting message processors, which are evil. We need a new mechanism which doesn't require intercepting and instead leverages the new callbacks from the reactive engine""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12240","04/18/2017 17:16:04",0,"Memory leak in embedded container ""Successive runs of the embedded container consumes the heap, please ask for a heap dump as its size is over 6 gb""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12243","04/18/2017 19:14:57",8,"JMS should publish messages with String Representable MimeTypes as StringMessages ""JMS extension publishes a message based on an application/json payload as StreamMessage with MM_MESSAGE_CONTENT_TYPE property application/json. When that message is consumed the mimeType returned is an application/json that wraps an ArrayList that contains the published application/json content instead. *Application to reproduce* {code:xml} App details #[payload] {code} *Console error* """," App details #[payload] ERROR 2017-04-18 12:46:40,760 [SchedulerService_cpuLight.06] org.mule.runtime.core.exception.DefaultMessagingExceptionStrategy: ******************************************************************************** Message : """"Java Object Source does not support Input Stream"""" evaluating expression: """"%dw 2.0 %output application/json --- payload"""". (org.mule.runtime.core.api.expression.ExpressionRuntimeException). Element : amq-consume/processors/1 @ crm-notification-process:null:38 (Transform Message) Element XML : %dw 2.0%output application/json---payload (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12244","04/18/2017 20:08:32",5,"Exclusive Optional parameters are not communicated for parameter groups inside POJOs ""*Exclusive Optional parameters are not communicated for parameter groups inside POJOs* * The information about *Exclusive Optional* parameters is communicated in the ParameterGroupModel, due that for Types this model doesn't exist, the information is lost. * This happens for {{TypeClassifier}} of DB Connector. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12245","04/18/2017 20:09:43",8,"Remove endorsed XML libraries ""We've been using Apache Xalan with Xerces for a long time, but Java 1.7 (and 1.8) provides newer alternatives with more security features. See this post (maybe a bit exaggerated, but the general idea is probably correct): http://www.odi.ch/weblog/posting.php?posting=689 The purpose of this issue is to determine how many tests are broken, and if the migration is easy then doing it. Regarding APIs, all standard factories should be compatible but comparisons of XML fragments in our tests may fail due to differences in spacing, order, namespaces, etc. Conclusions: - It was possible to remove them. - We are still using Woodstox XMLInputFactory and Saxon TransformerFactory in some places, but explicitly. - licm (License Manager) required modifications. - By including Woodstox or Saxon JARs in the classpath we are changing the default XMLInputFactory and TransformerFactory implementations. But as we use them through XMLSecureFactories for security settings, at least in our code we use the Java provided implementations. User applications and other code will use Woodstox/Saxon if loaded, and it can't be changed unless we remove their META-INF/service providers.""","",0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12253","04/19/2017 19:52:20",3,"AllowInlineDefinition is true for interfaces without any known implementation ""If the user doesn't declare an XmlHint for the parameter, we use the default, which leads to an inconsistent Extension model that declares that an interface without any known implementation can be declared as an inline parameter. Example of the `dataSourceRef` parameter of Db: """," { """"type"""": { """"format"""": """"java"""", """"type"""": """"Object"""", """"annotations"""": { """"typeId"""": """"javax.sql.DataSource"""", """"classInformation"""": { """"hasDefaultConstructor"""": false, """"isInterface"""": true, """"isInstantiable"""": false, """"isAbstract"""": true, """"isFinal"""": false, """"implementedInterfaces"""": [ """"javax.sql.CommonDataSource"""", """"java.sql.Wrapper"""" ], """"parent"""": """""""", """"genericTypes"""": [] }, """"typeAlias"""": { """"value"""": """"DataSource"""" } }, """"fields"""": [] }, """"hasDynamicType"""": false, """"required"""": true, """"expressionSupport"""": """"SUPPORTED"""", """"role"""": """"BEHAVIOUR"""", """"dslConfiguration"""": { """"allowsInlineDefinition"""": true, """"allowsReferences"""": true, """"allowTopLevelDefinition"""": false }, """"layoutModel"""": { """"password"""": false, """"text"""": false, """"query"""": false, """"order"""": 1 }, """"name"""": """"dataSourceRef"""", """"description"""": """"Reference to a JDBC DataSource object. This object is typically created using Spring.\nWhen using XA transactions, an XADataSource object must be provided."""", """"modelProperties"""": {} } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12265","04/20/2017 16:47:49",5,"Provide support to declare typed restrictions on Scopes models ""There are some scopes that only make sense within other specific ones. This is the case of the error-handler within a flow or try, or the on-error elements within an error-handler. There is however no way to indicate this in the extension model.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12267","04/20/2017 18:49:57",0,"NotificationUtils not checking for null parentElement ""Since the fix done in MULE-11358, repeated children will have null MessageProcessorPathElement as Parent. So, in NotificationUtils.addMessageProcessorPathElements, there could appear a parentElement as null (coming from AbstractInterceptingMessageProcessorBase), which should be checked. The processors will still have path setted because this only happens to duplicates. ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12270","04/20/2017 21:34:57",0,"JMS connector fails to receive CursorStreamProvider ""JMS Connector provider does not work with Cursor Streams The following configuration fails: """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12272","04/21/2017 14:46:22",1,"JMS Error not returned in response ""When an error is thrown by the JMS extension, you only get an error message but not the real cause of the error, meaning it's not useful for the user. For example, using the following flow: Will throw the following error *to the console* when no message is available: But the *HTTP response* with error code 500 only contains the following: The same behavior is seen in other operations."""," ERROR 2017-04-21 10:37:27,103 [SchedulerService_io.07] org.mule.extensions.jms.api.operation.JmsConsume: An error occurred while consuming a message from destination [asdf] of type [QUEUE]: org.mule.extensions.jms.api.exception.JmsTimeoutException: Failed to retrieve a Message, operation timed out An error occurred while consuming a message from destination [asdf] of type [QUEUE]: ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12274","04/21/2017 15:14:47",2,"Rename on-error-continue so it's clear flow does not continue with next processor ""Also means we can implement real continue later as is.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12275","04/21/2017 15:27:21",8,"JMS publish and receive operation should be non-blocking ""This is lack of functionality as this is supported in 3.8""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12276","04/21/2017 15:50:16",1,"MuleLoggerContext: getLogger inconsistent to hasLogger ""With MULE-9457 the method was overridden but not Additionally the naming in the Logger Map was changed. Log4j2 original: LoggerContextKey.create(name) = """"com.company...YourClass.org.apache.logging.log4j.message.ParameterizedMessageFactory"""" MuleSoft: """"com.company...YourClass"""" This yields to hasLogger(name) returning false always. Either update name in the map to LoggerContextKey.create(name) or override hasLogger as well."""," org.apache.logging.log4j.core.LoggerContext.getLogger(String, MessageFactory) org.apache.logging.log4j.core.LoggerContext.hasLogger(String) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12277","04/21/2017 17:49:00",3,"ParameterGroup validation is not taking into account the showInDsl attribute ""If you have 2 or more parameter groups of the same type, and you mark all to be shown in the DSL, the extension doesn't compile. Method The error shown is: Since the second POJO is marked with the @ParameterGroup(showInDsl = true), no parameters with repeated names should be reported"""," public String operationWithPojo(@Config BasicExtensionConfig config, @ParameterGroup(name = """"Ingredient"""") Ingredient ingredientAtOperation, @ParameterGroup(name = """"Ingredient shown in DSL"""", showInDsl = true) Ingredient ingredientShowInDsl) { return null; } [ERROR] Failed to execute goal org.bsc.maven:maven-processor-plugin:2.2.4:process (process) on project extension-with-parameter-group: Error executing: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: Extension 'ParameterGroup' has definition errors: [ERROR] ERRORS: [ERROR] * The operation 'operationWithPojo' has parameters with repeated names. Offending parameters are: [amount,no-expression-field,type] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12278","04/21/2017 17:54:37",8,"Create archetype for SDK extensions. ""Create a Maven Archetype for SDK extensions, this way users can scaffold a project from scratch and start working on it.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12279","04/21/2017 17:58:51",3,"Group already declared error when declared only once ""When building an Extension with @ParameterGroup(showInDsl=true) for a parameter and a connection provider of the same type, an error is shown with the following information: The operation: The connection provider: """," [ERROR] Failed to execute goal org.bsc.maven:maven-processor-plugin:2.2.4:process (process) on project extension-with-parameter-group: Error executing: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.extension.api.exception.IllegalParameterModelDefinitionException: Parameter group ‘Provider show in DSL’ has already been declared on connection provider ‘connection’ -> [Help 1] public String operationWithPojo(@Config BasicExtensionConfig config, @ParameterGroup(name = """"Ingredient"""") Ingredient ingredientAtOperation, @ParameterGroup(name = """"Ingredient shown in DSL"""", showInDsl = true) Ingredient ingredientShowInDsl) { return null; } public class BasicConnectionProvider implements ConnectionProvider { @Parameter private Ingredient ingredientAtProvider; @Parameter @ParameterGroup(name = """"Provider show in DSL"""", showInDsl = true) private Ingredient ingredientAtProviderShowInDsl; @Override public DummyConnection connect() throws ConnectionException { return null; } @Override public void disconnect(DummyConnection connection) { } @Override public ConnectionValidationResult validate(DummyConnection connection) { return null; } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12289","04/24/2017 16:07:17",8,"Failing tests on Windows ""The following tests are failing on Windows 10 OS. * mule-core module: ** ExceptionUtilsTestCase.testFullStackTraceWithoutMessage ** JdkVersionUtilsTestCase.testIsSupportedJdkVersion ** JdkVersionUtilsTestCase.testRecommendedJdkVersion ** JdkVersionUtilsTestCase.testValidateJdk5 ** PersistentObjectStorePartitionTestCase.skipAndMoveCorruptedOrUnreadableFiles ** QueuePersistenceObjectStoreTestCase.queueFilesAreRemovedWhenSerializationFails * mule-modules module: ** XsltResultDocumentTestCase.writeToSameFileSeveralTimes ** MuleResourceResolverTestCase.testsExistentFileSystemResourceWithBaseUri""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12291","04/24/2017 19:34:10",2,"ComponentModel config file name must point to the relative path file rather than the file ""Current ComponentModel has a method called org.mule.runtime.api.component.location.ComponentLocation#getFileName which points to the file of the modeled element when it should have the relative path to the file as it will be mandatory to properly look for it when debugging ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12292","04/24/2017 19:42:27",5,"DB pool limit does not throttle the connections but throws error instead. ""The current default of the connections pool of the DB extension is 5, when testing with more, the requests fails with the message """"Could not obtain connection from data source"""", which does not correlates to the reality. Also, this limit is not found on 3.6-3.8 connector, which uses one connection per call, as DB calls may take a long time, this value may need to be increased and also added to the migration doc.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12294","04/24/2017 23:08:07",0,"Fix package names on schedulers module ""Packages names on schedulers module are wrong, instead of having the org.mule.runtime.modules.schedulers prefix, they must use org.mule.runtime.module.scheduler""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12295","04/24/2017 23:24:28",5,"Make MuleArtifactFunctionalTestCase work with Soap Extensions from the IDE. ""Currently extensions need the mule-plugin.json in order to get the correct ExtensionModelLoader to be loaded, When running with maven this is not a problem because maven generates the mule-plugin.json at compile time so its the testing framework is able to locate it and load the extension correctly, but when the extension is not compiled and does not have the generated resources in place the IDE will not generate those resources since that is configured in the components.xml. Currently there is a method in the ExtensionModelLoaderFinder class that when the mule-plugin.json does not exist it will default to de DefaultJavaExtensionModelLoader(). This should be chaged so when there is no mule-plugin.json a mechanism is triggered in order to find the correect loader."""," private ExtensionModelLoader findLoaderFromMulePlugin(Artifact plugin) { try { MulePluginBasedLoaderFinder finder = new MulePluginBasedLoaderFinder(extensionMulePluginJson); return finder.getLoader(); } catch (FileNotFoundException e) { return new DefaultJavaExtensionModelLoader(); } } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12304","04/25/2017 18:26:27",1,"Incorrect folder structure in internal Maven repository ""The Maven repository folder structure has a duplicate nested folder: """," {MULE_HOME}/repository/.mule/.mule/plugins ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12307","04/25/2017 18:52:39",2,"make mule-app-plugins-maven-plugin to leave the pom file in the proper place ""The plugin mule-app-plugins-maven-plugin Is leaving the pom file inside of mule-artifact folder which is not correct it should follow the maven convention *META-INF/maven/groupid/artifactid/*""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12310","04/26/2017 16:03:56",8,"Add domain based system tests ""Currently, the tests that inherit from *DomainFunctionalTestCase* don't run in an isolated environment. Apart from that, those tests have mocked services (for instance, the SchedulerService) instead of the actual service, which prevents from testing some scenarios.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12314","04/26/2017 21:06:48",8,"Content parameters of different type and same name should not be allowed ""*Content parameters of different type and same name should not be allowed* * Nowadays we are allowing different content parameters of different type but with the same name, the problem of this is that a content parameter, due to child element support, will register a bean definition with a certain name and type. * If another content parameter uses the same name, will probably use the bean definition from another type, this will lead to in runtime, depending on the configured type fail or not ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12316","04/26/2017 22:26:46",1,"Path resolution not working for repository location ""The path resolution with wildcards for the muleRuntimeConfig.maven.repositoryLocation is not working. This cmd works: But this one doesn't work: """," ./bin/mule -M-DmuleRuntimeConfig.maven.repositoryLocation=/Users/alejandroiannucci/.m2/repository ./bin/mule -M-DmuleRuntimeConfig.maven.repositoryLocation=~/.m2/repository ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12320","04/27/2017 13:59:19",8,"App that fails deploying take too much time to show the error ""App that fails deploying take too much time to show the error. For example when you don't set a placeholder for the port or with ouauth when it can't obtain the token in client credentials.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12321","04/27/2017 14:19:27",2,"When an app with OAuth Client Credentials can't connect at deployment it doesn't show the HTTP requester response as in 3.x ""When an app with OAuth Client Credentials doens't can connect at deployment it doesn't show the HTTP requester response as in 3.x""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12322","04/27/2017 16:38:12",8,"Flow should not continue processing in non-blocking processor response thread. ""Flow should not continue processing in non-blocking processor response thread.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12325","04/27/2017 17:12:01",8,"Review Scatter-gather UX ""Need to review the UX of SC in Mule 4: * Review which DW expressions should be use to obtain the result of each route * When a route fails, review how to get both the error and the exception * Apply changes * Run all tests""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12328","04/27/2017 19:31:48",1,"Privileged access check is done differently on the container and test runner ""Artifact ID for plugins is being populated differently when plugins are created on standalone or the isolated test runner. On standalone mode, the artifact name is took from the plugin descriptor, while in the test runner the name is took from the full artifact maven ID (groupId, artifactId, version, etc)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12342","04/28/2017 18:10:31",0,"Sources may not receive onSuccess/onError ""In ModuleFlowProcessingPhase there are two consumers (for success and error) to send the events after a flow ends. If it's a source, then onSuccess/onError are dynamically called respectively to produce a response (like for the http extension). Now, inside getSuccessConsumer and getErrorConsumer the parameters required for each invocation are obtained through callbacks (see MessageSourceResponseParametersProcessor) which may for instance run dataweave. These expressions can fail for some and not all events, and when they do, the corresponding source callback won't be invoked. This is more problematic for the case of """"error"""", as a failure on """"success"""" will still try to call the error consumer. When onError parameters can't be obtained, the source is not notified and can't complete processing (for instance, http needs to tell grizzly that the request was handled - with or without emitting a response -, otherwise the extension will stall). A possible solution would be another callback, like onComplete that will always be called with the SourceCallbackContext and no extra parameters. Another one could be making dynamic parameters nullable and let the same onError handle them.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12345","04/28/2017 22:26:55",2,"Maven depenency resolution doesn't output logs ""When an app is being deployed and Mule starts downloading its dependencies from a remote repository, no log is being displayed about what is going on, and the user is left with the message: """," INFO 2017-04-28 18:22:56,730 [WrapperListener_start_runner] org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer: ================== New Exploded Artifact: http-extension-requester ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12355","05/02/2017 05:13:28",1,"OAuth operations are always executed in a blocking manner ""In order to refresh tokens and retry operations when they throw AccessTokenExpiredException, the OAuthOperationMessageProcessor class is written in a way which always forces the operation to block, even if they're not blocking. This should be refactored so that non blocking OAuth operations are in fact executed in a non blocking manner""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12356","05/02/2017 06:23:20",2,"Test Infrastructure doesn't handle services correctly ""Consider the pom for extension-spring-support. The mule-service-http artifact is listed as a dependency twice: 1) first as a provided service 2) as a test service This leads to the following problems: * If ran as is, an exception is thrown saying that there're two bean definitions for the HttpService * If the test dependency is removed, then the test fails with NoClassDefError of the HttpService * The the test dependency is kept but not as service, the first problem appears again. In order to get it working, I had to comment a validation on org.mule.runtime.config.spring.SpringMuleContextServiceConfigurator#createCustomServices which should be bring back when this issue is fixed.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12357","05/02/2017 09:57:42",2,"Upgrade reactor to version 2.0.7 ""Upgrade reactor to version 2.0.7""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12358","05/02/2017 12:52:18",2,"Reduce verbose output of ProcessingStrategy test cases ""Reduce verbose output of ProcessingStrategy test cases""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12360","05/02/2017 14:28:09",8,"XsltTransformer should close underlying InputStream when using XMLStreamReader ""As Javadoc says the underlying input stream is not going to be closed, therefore the transformer should take care of this: http://docs.oracle.com/javaee/5/api/javax/xml/stream/XMLStreamReader.html""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12361","05/02/2017 15:01:33",8,"Update ExpressionManager to accept expressions that resolves to null when indicating the expected DataType ""Update ExpressionManager to accept expressions that resolves to null when indicating the expected DataType""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12362","05/02/2017 15:46:00",0,"mule-core should use same asm library as the one packaged with distribution ""core has a different version of asm therefore tests are running within that version instead of the one that finally goes to the distribution.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12363","05/02/2017 18:07:09",3,"Missing CDATA on import of ArtifactDeclaration ""Missing CDATA on import of ArtifactDeclaration""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12364","05/02/2017 18:27:38",8,"Review use of boxed booleans in extensions ""Go through all extensions and remove triple state booleans""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12367","05/02/2017 18:42:23",3,"File and FTP connectors should not require match-with ""the match-with wrapper should not be necessary. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12368","05/02/2017 18:43:35",5,"CursorProvider management should happen on the pipeline ""(complete)""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12369","05/02/2017 18:45:12",3,"Runtime should know how to transform java 8 dates to java 7 dates ""(complete)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12370","05/02/2017 19:12:04",1,"Cherry pick M5 fix for Qname and infrastructure model property ""Cherry pick M5 fix for Qname and infrastructure model property""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12371","05/02/2017 19:29:46",3,"Hidden error messages on JMS operations ""When an error is thrown by the JMS Publish operation, the actual error is wrapped inside a generic error which hides the actual cause. Example: The only way to access the actual cause of the error is using: *{{error.cause.cause.message}}*, which is not user friendly. The cause of the error should be available via: *{{error.description}}* Stacktrace of the error: """," { """"errorType"""": { """"parentErrorType"""": { """"parentErrorType"""": { """"parentErrorType"""": null, """"identifier"""": """"ANY"""", """"namespace"""": """"MULE"""" }, """"identifier"""": """"ANY"""", """"namespace"""": """"JMS"""" }, """"identifier"""": """"PUBLISHING"""", """"namespace"""": """"JMS"""" }, """"errorMessage"""": null, """"cause"""": { """"localizedMessage"""": """"An error occurred while sending a message to [foo]: """", """"cause"""": { """"localizedMessage"""": """"User muleman is not authorized to write to: queue://foo"""", """"errorCode"""": null, """"cause"""": { ... }, """"message"""": """"User muleman is not authorized to write to: queue://foo"""", """"linkedException"""": null, """"stackTrace"""": [ ... ], """"suppressed"""": [] }, """"type"""": """"PUBLISHING"""", """"message"""": """"An error occurred while sending a message to [foo]: """", """"stackTrace"""": [ ... ], """"suppressed"""": [] }, """"description"""": """"An error occurred while sending a message to [foo]: """", """"detailedDescription"""": """"An error occurred while sending a message to [foo]: """" } ERROR 2017-05-02 15:18:31,658 [[MuleRuntime].io.07] org.mule.extensions.jms.internal.operation.JmsPublish: An error occurred while sending a message to [foo]: javax.jms.JMSSecurityException: User muleman is not authorized to write to: queue://foo at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1399) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1428) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.ActiveMQSession.syncSendPacket(ActiveMQSession.java:2081) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.ActiveMQMessageProducer.(ActiveMQMessageProducer.java:124) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.ActiveMQSession.createProducer(ActiveMQSession.java:1112) ~[activemq-client-5.14.1.jar:5.14.1] at org.springframework.jms.connection.CachingConnectionFactory$CachedSessionInvocationHandler.getCachedProducer(CachingConnectionFactory.java:400) ~[spring-jms-4.1.6.RELEASE.jar:4.1.6.RELEASE] at org.springframework.jms.connection.CachingConnectionFactory$CachedSessionInvocationHandler.invoke(CachingConnectionFactory.java:336) ~[spring-jms-4.1.6.RELEASE.jar:4.1.6.RELEASE] at com.sun.proxy.$Proxy99.createProducer(Unknown Source) ~[?:?] at org.mule.extensions.jms.internal.support.Jms20Support.createProducer(Jms20Support.java:111) ~[mule-module-jms-4.0.0-SNAPSHOT-mule-plugin.jar:?] at org.mule.extensions.jms.internal.connection.JmsConnection.createProducer(JmsConnection.java:129) ~[mule-module-jms-4.0.0-SNAPSHOT-mule-plugin.jar:?] at org.mule.extensions.jms.internal.operation.JmsPublish.publish(JmsPublish.java:96) ~[mule-module-jms-4.0.0-SNAPSHOT-mule-plugin.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_131] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_131] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_131] at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:203) ~[spring-core-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.lambda$execute$0(ReflectiveMethodComponentExecutor.java:73) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:162) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:958) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.execute(ReflectiveMethodComponentExecutor.java:72) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.operation.ReflectiveMethodOperationExecutor.execute(ReflectiveMethodOperationExecutor.java:54) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.execution.ReactiveOperationExecutionWrapper.execute(ReactiveOperationExecutionWrapper.java:55) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.execution.InterceptableOperationExecutorWrapper.execute(InterceptableOperationExecutorWrapper.java:56) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.operation.DefaultExecutionMediator.lambda$executeWithInterceptors$7(DefaultExecutionMediator.java:120) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at reactor.core.publisher.MonoCreate.subscribe(MonoCreate.java:47) ~[reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:62) ~[reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.MonoMapFuseable.subscribe(MonoMapFuseable.java:60) ~[reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.MonoOtherwiseIfEmpty.subscribe(MonoOtherwiseIfEmpty.java:44) ~[reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.MonoOtherwise.subscribe(MonoOtherwise.java:44) ~[reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.Mono.block(Mono.java:1188) ~[reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$null$0(OperationMessageProcessor.java:146) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.policy.DefaultPolicyManager.lambda$createOperationPolicy$1(DefaultPolicyManager.java:107) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$null$1(OperationMessageProcessor.java:153) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:162) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$apply$3(OperationMessageProcessor.java:140) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.api.rx.Exceptions.lambda$checkedFunction$3(Exceptions.java:83) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:111) [reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.runAsync(FluxPublishOn.java:401) [reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.run(FluxPublishOn.java:489) [reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.scheduler.ExecutorServiceScheduler$ScheduledRunnable.run(ExecutorServiceScheduler.java:206) [reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_131] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_131] at org.mule.service.scheduler.internal.AbstractRunnableFutureDecorator.doRun(AbstractRunnableFutureDecorator.java:88) [mule-service-scheduler-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.service.scheduler.internal.RunnableFutureDecorator.run(RunnableFutureDecorator.java:56) [mule-service-scheduler-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131] Caused by: java.lang.SecurityException: User muleman is not authorized to write to: queue://foo at org.apache.activemq.security.AuthorizationBroker.addProducer(AuthorizationBroker.java:199) ~[activemq-broker-5.14.1.jar:5.14.1] at org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:108) ~[activemq-broker-5.14.1.jar:5.14.1] at org.apache.activemq.broker.MutableBrokerFilter.addProducer(MutableBrokerFilter.java:113) ~[activemq-broker-5.14.1.jar:5.14.1] at org.apache.activemq.broker.TransportConnection.processAddProducer(TransportConnection.java:653) ~[activemq-broker-5.14.1.jar:5.14.1] at org.apache.activemq.command.ProducerInfo.visit(ProducerInfo.java:108) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:336) ~[activemq-broker-5.14.1.jar:5.14.1] at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:200) ~[activemq-broker-5.14.1.jar:5.14.1] at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:125) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:301) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:233) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215) ~[activemq-client-5.14.1.jar:5.14.1] ... 1 more ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12372","05/02/2017 19:33:56",1,"Incorrect error mapping for SecurityException ""When a {{java.lang.SecurityException}} is thrown on a jms:publish operation, this error is wrapped in a {{TypedException}} with type """"PUBLISHING"""", which doesn't allow the user to handle properly this type of errors. Security exceptions should have their own error types or be mapped to the SECURITY type provided by Mule. Log: """," ERROR 2017-05-02 15:18:31,658 [[MuleRuntime].io.07] org.mule.extensions.jms.internal.operation.JmsPublish: An error occurred while sending a message to [foo]: javax.jms.JMSSecurityException: User muleman is not authorized to write to: queue://foo at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:52) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1399) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1428) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.ActiveMQSession.syncSendPacket(ActiveMQSession.java:2081) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.ActiveMQMessageProducer.(ActiveMQMessageProducer.java:124) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.ActiveMQSession.createProducer(ActiveMQSession.java:1112) ~[activemq-client-5.14.1.jar:5.14.1] at org.springframework.jms.connection.CachingConnectionFactory$CachedSessionInvocationHandler.getCachedProducer(CachingConnectionFactory.java:400) ~[spring-jms-4.1.6.RELEASE.jar:4.1.6.RELEASE] at org.springframework.jms.connection.CachingConnectionFactory$CachedSessionInvocationHandler.invoke(CachingConnectionFactory.java:336) ~[spring-jms-4.1.6.RELEASE.jar:4.1.6.RELEASE] at com.sun.proxy.$Proxy99.createProducer(Unknown Source) ~[?:?] at org.mule.extensions.jms.internal.support.Jms20Support.createProducer(Jms20Support.java:111) ~[mule-module-jms-4.0.0-SNAPSHOT-mule-plugin.jar:?] at org.mule.extensions.jms.internal.connection.JmsConnection.createProducer(JmsConnection.java:129) ~[mule-module-jms-4.0.0-SNAPSHOT-mule-plugin.jar:?] at org.mule.extensions.jms.internal.operation.JmsPublish.publish(JmsPublish.java:96) ~[mule-module-jms-4.0.0-SNAPSHOT-mule-plugin.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_131] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_131] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_131] at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:203) ~[spring-core-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.lambda$execute$0(ReflectiveMethodComponentExecutor.java:73) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:162) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:958) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.execute(ReflectiveMethodComponentExecutor.java:72) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.operation.ReflectiveMethodOperationExecutor.execute(ReflectiveMethodOperationExecutor.java:54) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.execution.ReactiveOperationExecutionWrapper.execute(ReactiveOperationExecutionWrapper.java:55) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.execution.InterceptableOperationExecutorWrapper.execute(InterceptableOperationExecutorWrapper.java:56) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.operation.DefaultExecutionMediator.lambda$executeWithInterceptors$7(DefaultExecutionMediator.java:120) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at reactor.core.publisher.MonoCreate.subscribe(MonoCreate.java:47) ~[reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:62) ~[reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.MonoMapFuseable.subscribe(MonoMapFuseable.java:60) ~[reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.MonoOtherwiseIfEmpty.subscribe(MonoOtherwiseIfEmpty.java:44) ~[reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.MonoOtherwise.subscribe(MonoOtherwise.java:44) ~[reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.Mono.block(Mono.java:1188) ~[reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$null$0(OperationMessageProcessor.java:146) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.policy.DefaultPolicyManager.lambda$createOperationPolicy$1(DefaultPolicyManager.java:107) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$null$1(OperationMessageProcessor.java:153) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:162) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$apply$3(OperationMessageProcessor.java:140) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.api.rx.Exceptions.lambda$checkedFunction$3(Exceptions.java:83) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:111) [reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.runAsync(FluxPublishOn.java:401) [reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.run(FluxPublishOn.java:489) [reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at reactor.core.scheduler.ExecutorServiceScheduler$ScheduledRunnable.run(ExecutorServiceScheduler.java:206) [reactor-core-3.0.5.RELEASE.jar:3.0.5.RELEASE] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_131] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_131] at org.mule.service.scheduler.internal.AbstractRunnableFutureDecorator.doRun(AbstractRunnableFutureDecorator.java:88) [mule-service-scheduler-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.service.scheduler.internal.RunnableFutureDecorator.run(RunnableFutureDecorator.java:56) [mule-service-scheduler-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131] Caused by: java.lang.SecurityException: User muleman is not authorized to write to: queue://foo at org.apache.activemq.security.AuthorizationBroker.addProducer(AuthorizationBroker.java:199) ~[activemq-broker-5.14.1.jar:5.14.1] at org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:108) ~[activemq-broker-5.14.1.jar:5.14.1] at org.apache.activemq.broker.MutableBrokerFilter.addProducer(MutableBrokerFilter.java:113) ~[activemq-broker-5.14.1.jar:5.14.1] at org.apache.activemq.broker.TransportConnection.processAddProducer(TransportConnection.java:653) ~[activemq-broker-5.14.1.jar:5.14.1] at org.apache.activemq.command.ProducerInfo.visit(ProducerInfo.java:108) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:336) ~[activemq-broker-5.14.1.jar:5.14.1] at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:200) ~[activemq-broker-5.14.1.jar:5.14.1] at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:125) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:301) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:233) ~[activemq-client-5.14.1.jar:5.14.1] at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:215) ~[activemq-client-5.14.1.jar:5.14.1] ... 1 more ERROR 2017-05-02 15:18:31,694 [[MuleRuntime].cpuLight.03] org.mule.runtime.core.exception.OnErrorPropagateHandler: ******************************************************************************** Message : org.mule.extensions.jms.api.exception.JmsPublishException: An error occurred while sending a message to [foo]: (org.mule.runtime.core.exception.TypedException). Element : null (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12376","05/03/2017 14:29:12",0,"Remove transaction constraint classes ""Classes from org.mule.runtime.core.transaction.constraints are only referenced on org.mule.runtime.core.api.transaction.TransactionConfig API but never really used. Remove them""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12381","05/03/2017 17:33:11",2,"Unclear error message when no Maven repository is configured ""When you deploy a lightweight application and you don't configure any Maven repository to pull the dependencies from, The app deployment fails with the following error: If no Maven repository is configured, the user must know that they are missing that configuration with a clear error message"""," ERROR 2017-05-03 13:29:12,810 [WrapperListener_start_runner] org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Failed to deploy exploded artifact: 'jms-extension', + + see below + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ java.lang.RuntimeException: There was an issue resolving the dependency tree for the plugin [/opt/mule-enterprise-standalone-4.0.0-SNAPSHOT/apps/jms-extension] at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:173) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] at org.mule.runtime.module.deployment.impl.internal.maven.AbstractMavenClassLoaderModelLoader.createClassLoaderModel(AbstractMavenClassLoaderModelLoader.java:123) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.maven.AbstractMavenClassLoaderModelLoader.load(AbstractMavenClassLoaderModelLoader.java:93) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.MavenClassLoaderModelLoader.load(MavenClassLoaderModelLoader.java:63) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.MavenClassLoaderModelLoader.load(MavenClassLoaderModelLoader.java:38) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.ApplicationDescriptorFactory.getClassLoaderModel(ApplicationDescriptorFactory.java:217) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.ApplicationDescriptorFactory.lambda$loadFromJsonDescriptor$4(ApplicationDescriptorFactory.java:176) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at java.util.Optional.ifPresent(Optional.java:159) ~[?:1.8.0_131] at org.mule.runtime.module.deployment.impl.internal.application.ApplicationDescriptorFactory.loadFromJsonDescriptor(ApplicationDescriptorFactory.java:175) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.ApplicationDescriptorFactory.create(ApplicationDescriptorFactory.java:103) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultApplicationFactory.createArtifact(DefaultApplicationFactory.java:107) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultApplicationFactory.createArtifact(DefaultApplicationFactory.java:51) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployExplodedApp(DefaultArchiveDeployer.java:239) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:89) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:40) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher.deployExplodedApps(DeploymentDirectoryWatcher.java:246) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher.start(DeploymentDirectoryWatcher.java:146) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.MuleDeploymentService.start(MuleDeploymentService.java:133) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.launcher.MuleContainer.start(MuleContainer.java:196) [mule-module-launcher-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_131] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_131] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_131] at org.mule.runtime.module.reboot.MuleContainerWrapper.start(MuleContainerWrapper.java:47) [mule-module-boot-ee-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4242) [wrapper-3.5.29.jar:3.5.29] Caused by: org.eclipse.aether.collection.DependencyCollectionException: Failed to collect dependencies at org.mule.modules:mule-module-http-ext:jar:mule-plugin:4.0.0-SNAPSHOT at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316) ~[aether-impl-1.0.2.v20150114.jar:?] at org.mule.maven.client.internal.AetherMavenClient.assemblyDependenciesFromPom(AetherMavenClient.java:424) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:190) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:165) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] ... 24 more Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.mule.modules:mule-module-http-ext:jar:mule-plugin:4.0.0-SNAPSHOT at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:282) ~[maven-aether-provider-3.3.9.jar:3.3.9] at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:198) ~[maven-aether-provider-3.3.9.jar:3.3.9] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.resolveCachedArtifactDescriptor(DefaultDependencyCollector.java:535) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.getArtifactDescriptorResult(DefaultDependencyCollector.java:519) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:409) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:254) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316) ~[aether-impl-1.0.2.v20150114.jar:?] at org.mule.maven.client.internal.AetherMavenClient.assemblyDependenciesFromPom(AetherMavenClient.java:424) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:190) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:165) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] ... 24 more Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.mule.modules:mule-module-http-ext:pom:4.0.0-SNAPSHOT at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) ~[aether-impl-1.0.2.v20150114.jar:?] at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:267) ~[maven-aether-provider-3.3.9.jar:3.3.9] at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:198) ~[maven-aether-provider-3.3.9.jar:3.3.9] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.resolveCachedArtifactDescriptor(DefaultDependencyCollector.java:535) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.getArtifactDescriptorResult(DefaultDependencyCollector.java:519) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:409) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:254) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316) ~[aether-impl-1.0.2.v20150114.jar:?] at org.mule.maven.client.internal.AetherMavenClient.assemblyDependenciesFromPom(AetherMavenClient.java:424) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:190) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:165) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] ... 24 more Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.mule.modules:mule-module-http-ext:pom:4.0.0-SNAPSHOT at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:434) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223) ~[aether-impl-1.0.2.v20150114.jar:?] at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:267) ~[maven-aether-provider-3.3.9.jar:3.3.9] at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:198) ~[maven-aether-provider-3.3.9.jar:3.3.9] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.resolveCachedArtifactDescriptor(DefaultDependencyCollector.java:535) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.getArtifactDescriptorResult(DefaultDependencyCollector.java:519) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:409) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:363) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:351) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:254) ~[aether-impl-1.0.2.v20150114.jar:?] at org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316) ~[aether-impl-1.0.2.v20150114.jar:?] at org.mule.maven.client.internal.AetherMavenClient.assemblyDependenciesFromPom(AetherMavenClient.java:424) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:190) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:165) ~[mule-maven-client-impl-1.0.0-SNAPSHOT.jar:?] ... 24 more ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12382","05/03/2017 18:20:30",8,"WSC fails to parse local XSD imports. ""WSC fails to parse local XSD imports.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12386","05/03/2017 22:30:40",1,"java.util.MissingFormatArgumentException when no pom is found for an extension ""When the maven client fails to get a pom from jar, an exception is thrown: """," Caused by: java.util.MissingFormatArgumentException: Format specifier ‘%s’ at java.util.Formatter.format(Formatter.java:2519) at java.util.Formatter.format(Formatter.java:2455) at java.lang.String.format(String.java:2928) at org.mule.maven.client.internal.util.MavenUtils.getPomUrlFromJar(MavenUtils.java:48) at org.mule.maven.client.internal.util.MavenUtils.getPomModelFromJar(MavenUtils.java:101) at org.mule.maven.client.internal.util.MavenUtils.getPomModel(MavenUtils.java:66) at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:148) at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:139) at org.mule.runtime.module.deployment.impl.internal.maven.AbstractMavenClassLoaderModelLoader.createClassLoaderModel(AbstractMavenClassLoaderModelLoader.java:123) at org.mule.runtime.module.deployment.impl.internal.maven.AbstractMavenClassLoaderModelLoader.load(AbstractMavenClassLoaderModelLoader.java:93) at org.mule.runtime.module.deployment.impl.internal.artifact.MavenClassLoaderModelLoader.load(MavenClassLoaderModelLoader.java:66) at org.mule.runtime.module.deployment.impl.internal.artifact.MavenClassLoaderModelLoader.load(MavenClassLoaderModelLoader.java:38) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.getClassLoaderModel(ArtifactPluginDescriptorFactory.java:132) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.lambda$loadFromJsonDescriptor$22(ArtifactPluginDescriptorFactory.java:87) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory$$Lambda$313/503458347.accept(Unknown Source) at java.util.Optional.ifPresent(Optional.java:159) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.loadFromJsonDescriptor(ArtifactPluginDescriptorFactory.java:86) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.lambda$create$20(ArtifactPluginDescriptorFactory.java:72) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory$$Lambda$312/1231096494.apply(Unknown Source) at java.util.Optional.map(Optional.java:215) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.create(ArtifactPluginDescriptorFactory.java:72) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorLoader.load(ArtifactPluginDescriptorLoader.java:42) ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12389","05/04/2017 15:55:45",1,"Move Pooling Profile to ""Pooling"" Tab ""Instead of putting Pooling Profile on the Advanced Tab, it should be on a separate tab named Pooling and not in a group.""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12395","05/04/2017 19:53:05",0,"Cannot load extension model in Windows ""Tooling client fails to load extensions on Windows machines because the path are not written correctly. """," ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. !ENTRY org.mule.tooling.core 4 0 2017-05-04 15:41:04.265 !MESSAGE Unexpected error loading extension from: C:\Users\ldebello\.m2\repository\org\mule\modules\mule-module-sockets\4.0.0-SNAPSHOT\mule-module-sockets-4.0.0-SNAPSHOT-mule-plugin.jar !STACK 0 org.mule.tooling.client.api.exception.ToolingException: Error while loading ExtensionModel for plugin: C:\Users\ldebello\.m2\repository\org\mule\modules\mule-module-sockets\4.0.0-SNAPSHOT\mule-module-sockets-4.0.0-SNAPSHOT-mule-plugin.jar at org.mule.tooling.client.internal.DefaultExtensionModelModelService.loadExtensionModel(DefaultExtensionModelModelService.java:171) at org.mule.tooling.core.utils.ExtensionModelLoaderUtils.getExtensionModelFromJar(ExtensionModelLoaderUtils.java:106) at org.mule.tooling.core.module.internal.runner.DownloadTask.doRun(DownloadTask.java:96) at org.mule.tooling.core.module.internal.runner.SingleDownloadTask.doRun(SingleDownloadTask.java:1) at org.mule.tooling.core.module.internal.runner.Task.run(Task.java:48) at org.mule.tooling.core.module.internal.runner.SingleDownloadTask.run(SingleDownloadTask.java:1) at org.mule.tooling.core.module.internal.runner.ArtifactResolvingRunner$ArtifactJob.run(ArtifactResolvingRunner.java:146) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.mule.runtime.module.artifact.descriptor.ArtifactDescriptorCreateException: The plugin descriptor 'META-INF\mule-artifact\mule-plugin.json' on plugin file 'C:\Users\ldebello\.m2\repository\org\mule\modules\mule-module-sockets\4.0.0-SNAPSHOT\mule-module-sockets-4.0.0-SNAPSHOT-mule-plugin.jar' is not present at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.lambda$create$1(ArtifactPluginDescriptorFactory.java:73) at java.util.Optional.orElseThrow(Optional.java:290) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.create(ArtifactPluginDescriptorFactory.java:73) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorLoader.load(ArtifactPluginDescriptorLoader.java:42) at org.mule.tooling.client.internal.DefaultExtensionModelModelService.loadExtensionModel(DefaultExtensionModelModelService.java:168) ... 7 more !ENTRY org.mule.tooling.core 4 0 2017-05-04 15:41:04.280 !MESSAGE Unexpected error loading extension from: C:\Users\ldebello\.m2\repository\org\mule\modules\mule-module-sockets\4.0.0-SNAPSHOT\mule-module-sockets-4.0.0-SNAPSHOT-mule-plugin.jar !STACK 0 ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12399","05/04/2017 21:04:32",3,"Validate Pojos used as Subtypes ""Imagine you have a base subtype relationship between pojo A and B (A is the parent and B the child). You use your base type A as a parameter or return type, what ends up happening is that all the SDK validations are run against A (for instance, having all the getters for the field), but no validation is run against B. In all the situations that a base type is validated, we should also validate its subtypes.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12403","05/05/2017 14:31:42",0,"Cannot load extension model in Windows, pom.xml not found ""The tooling client is failing to locate the pom.xml file, and because of this, it cannot load the extension model. We checked the jar in the local repository, and the pom.xml existed under the folder maven/org.mule.modules/mule-module-sockets """," org.mule.tooling.client.api.exception.ToolingException: Error while loading ExtensionModel for plugin: C:\Users\greob\.m2\repository\org\mule\modules\mule-module-sockets\4.0.0-SNAPSHOT\mule-module-sockets-4.0.0-SNAPSHOT-mule-plugin.jar at org.mule.tooling.client.internal.DefaultExtensionModelModelService.loadExtensionModel(DefaultExtensionModelModelService.java:171) at org.mule.tooling.core.utils.ExtensionModelLoaderUtils.getExtensionModelFromJar(ExtensionModelLoaderUtils.java:106) at org.mule.tooling.extension.api.SingleExtensionModuleHandler.(SingleExtensionModuleHandler.java:61) at org.mule.tooling.extension.api.ModuleHandlerFactory.createHandlerFor(ModuleHandlerFactory.java:17) at org.mule.tooling.extension.api.ModuleHandlerFactory.createHandlerFor(ModuleHandlerFactory.java:1) at org.mule.tooling.core.module.ModuleContributionManager.getExternalModule(ModuleContributionManager.java:444) at org.mule.tooling.core.module.internal.runner.DownloadTask.doRun(DownloadTask.java:117) at org.mule.tooling.core.module.internal.runner.SingleDownloadTask.doRun(SingleDownloadTask.java:1) at org.mule.tooling.core.module.internal.runner.Task.run(Task.java:48) at org.mule.tooling.core.module.internal.runner.SingleDownloadTask.run(SingleDownloadTask.java:1) at org.mule.tooling.core.module.internal.runner.ArtifactResolvingRunner$ArtifactJob.run(ArtifactResolvingRunner.java:146) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.lang.RuntimeException: The file 'pom.xml' was missing while looking within the artifact mule-module-sockets-4.0.0-SNAPSHOT-mule-plugin.jar (it should be placed under [META-INF/maven/${groupId}/${artifactId}/pom.xml]) at org.mule.maven.client.internal.util.MavenUtils.getPomUrlFromJar(MavenUtils.java:47) at org.mule.maven.client.internal.util.MavenUtils.getPomModelFromJar(MavenUtils.java:100) at org.mule.maven.client.internal.util.MavenUtils.getPomModel(MavenUtils.java:65) at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:146) at org.mule.maven.client.internal.AetherMavenClient.resolveArtifactDependencies(AetherMavenClient.java:137) at org.mule.runtime.module.deployment.impl.internal.maven.AbstractMavenClassLoaderModelLoader.createClassLoaderModel(AbstractMavenClassLoaderModelLoader.java:123) at org.mule.runtime.module.deployment.impl.internal.maven.AbstractMavenClassLoaderModelLoader.load(AbstractMavenClassLoaderModelLoader.java:93) at org.mule.runtime.module.deployment.impl.internal.artifact.MavenClassLoaderModelLoader.load(MavenClassLoaderModelLoader.java:66) at org.mule.runtime.module.deployment.impl.internal.artifact.MavenClassLoaderModelLoader.load(MavenClassLoaderModelLoader.java:38) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.getClassLoaderModel(ArtifactPluginDescriptorFactory.java:131) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.lambda$loadFromJsonDescriptor$2(ArtifactPluginDescriptorFactory.java:86) at java.util.Optional.ifPresent(Optional.java:159) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.loadFromJsonDescriptor(ArtifactPluginDescriptorFactory.java:85) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.lambda$create$0(ArtifactPluginDescriptorFactory.java:70) at java.util.Optional.map(Optional.java:215) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.create(ArtifactPluginDescriptorFactory.java:70) at org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorLoader.load(ArtifactPluginDescriptorLoader.java:42) at org.mule.tooling.client.internal.DefaultExtensionModelModelService.loadExtensionModel(DefaultExtensionModelModelService.java:168) ... 11 more ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12404","05/05/2017 17:35:55",5,"If an error occurs resolving the @OnSuccess parameters the error is never exposed ""*If an error occurs resolving the @OnSuccess parameters the error is never exposed* * The case comes when the SDK is trying to resolve the parameter's values, and for example one of the values is resolved from an expression and this expression is invalid. * When this happens no exception is exposed, no error log information will be displayed. * If the *listener* has an {{@OnError}} method, this will be called, if not, no method will be called and the Mule Developer won't see any exception. * In case that the resolution error occurs on the {{@OnError}} method, the following log line will be displayed, which is totally different from any other normal Mule Error"""," ERROR 2017-05-05 13:32:42,908 [[MuleRuntime].cpuLight.02] org.mule.runtime.core.execution.ModuleFlowProcessingPhase: Unhandled exception processing requestorg.mule.runtime.core.api.expression.ExpressionRuntimeException: """"Unexpected character 's' at payload@[1:1] (line:column), expected false or true or null or {...} or [...] or number but was s. at string ^"""" evaluating expression: """"#[payload]"""". ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12405","05/05/2017 18:40:42",5,"Use MetadataCache for SoapOperationMetadata in WSC ""Use MetadataCache for SoapOperationMetadata in WSC, since the metadata is resolved for the whole operation but retrieved by part (headers, body, attachments). The cache allows us to save the operation metadata for the first elemente resolved and let the other two use the cached value instead of re-introspecting the wsdl. In order to do this we should provide a json serializer for the SoapOperationMetadata directly from the soap-api, and use that serialized value as the stored value in the cache, ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12406","05/05/2017 23:02:11",1,"HTTP, Oauth and Soap services have wrong package name ""I came to realise that the package of those services (http, oauth and soap) have package """"org.mule.services"""" instead of """"org.mule.service"""". We need to fix that.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12407","05/06/2017 06:56:43",2,"Define how to deal with splitting of application/xml content ""Currently there is no way to do a foreach or splitter over an String with application/xml using an expression that may return several XML parts. We need to define how it should work with XML. This issue must make the test annotated with Ignore(""""MULE-12407"""") pass""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12414","05/08/2017 17:37:47",2,"Event Builder allows null message ""Event builder must validate that the message is not null when creating the event.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12420","05/08/2017 21:56:48",1,"Move scripting plugin to a separated github repository ""Move scripting plugin to a separated github repository so it can have a release cycle different from the container.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12427","05/09/2017 21:05:52",0,"Application should expose only shared resources to plugins ""Resources on the app which come from not shared libs are still found by plugins. For example in compatibility IntegrationTestCaseRunnerConfig, if it shares """"org.mule.tests:mule-tests-unit"""" and """"org.mule.tests:mule-tests-functional"""", then for some reason, the plugins classloaders try to load the org.mule.test.config.dsl.ParserComponentBuildingDefinitionProvider which is defined on test-integration, which is not exported. Apparently the problem is that the app exports META-INF/services/org.mule.runtime.dsl.api.component.ComponentBuildingDefinitionProvider, because it is part of mule-test-functional. That resource is also present on mule-test-integration.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12429","05/09/2017 23:34:54",1,"Streaming buffer is wrongfully exceeded ""When the streaming buffer size matches the payload size exactly, it wrongfully throws BufferSizeExceddedException.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12430","05/10/2017 11:23:20",2,"Scatter-gather router does not handle errors correctly and invokes error handler multiple times ""Scatter-gather router does not handle errors correctly and invokes error handler multiple times""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12433","05/10/2017 17:14:58",1,"CursorStream should throw IOException ""CursorStream throws an IllegalArgumentException when assertNotDisposed is called during a read or seek, which causes trouble because those ops are supposed to throw IOException, meaning such an error will not be handled properly most likely.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12434","05/10/2017 18:59:52",5,"Poll extension model is invalid ""Poll extension model is invalid, thus preventing tooling from using the ArtifactDecalration serializer. The new model will eliminate the need of an schedulers module and unify both strategies as a subtypes case. Final DSL will be: """," ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12438","05/10/2017 23:35:45",5,"Cannot override default value for explicit primary content ""While making some changes in HTTP, I annotated with @Optional(defaultValue = """"#[error.description]"""") an attribute already annotated with @Content(primary = true). Though the extension model was correct, when resolved on runtime #[payload] was used. Furthermore, when removing the explicit primary thing, no expression was evaluated and null was resolved (perhaps because there was no other primary?).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12448","05/11/2017 17:12:57",8,"Sources error handling is inconsistent ""When changing the default error handler, it became clear that the HTTP listener error-response had to be updated which uncovered the fact that source error handling is extremely inconsistent. Under some scenarios error handling is called, under others the source handles the error directly while worst of all sometimes the app hangs. We need to review all scenarios and settle on the behaviour. Focus should be on sources using the default error handler.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12603","05/11/2017 18:26:34",0,"Improved HTTP layout ""Based on user studies which we've done, we need to improve the layout of the HTTP connector as people were not able to get successful with it. Details TBD ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12451","05/11/2017 19:36:52",1,"Cleanup test dependencies from poms ""Change dependencies to core-tests for dependencies to test support modules Remove transient test dependencies""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12452","05/11/2017 21:07:16",5,"Errors thrown from SDK extensions are not handled properly ""Throwing an java.lang.Error such as an Assertion error from inside an SDK extension get's wrapped in an Exception inside *org.mule.runtime.module.extension.internal.runtime.exception.ExceptionHandlerManager#wrapInException* This is causing that the source of the failure gets to the error lookup as an exception instead of the original Error. Which in turns causes error handler to execute because the error is not mapped as critical ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12454","05/11/2017 22:21:03",1,"Redefine expression language API ""Core module defines ExpressionLanguageExtension interface that can be implemented on external modules to provide extensions to MEL expression language. There are currently two extensions provided on validation module and batch EE module. In order to remove MEL from core, this API has to be moved to a separated module that can be referenced on the mentioned modules  ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12455","05/12/2017 03:54:02",3,"Hidden error cause in E-mail connector ""When the e-mail connector throws an UnsupportedDataTypeError, the actual cause of the error is not easily available to the user: Current error message is: {{Error while sending email: IOException while sending message (org.mule.extension.email.api.exception.EmailException).}} But the real and more useful error message can be found in the stacktrace: {{javax.activation.UnsupportedDataTypeException: no object DCH for MIME type application/json}} Complete log: """," ERROR 2017-05-11 09:25:04,398 [[MuleRuntime].cpuLight.03] org.mule.runtime.core.exception.OnErrorPropagateHandler: ******************************************************************************** Message : Error while sending email: IOException while sending message (org.mule.extension.email.api.exception.EmailException). Payload Type : org.mule.runtime.core.internal.streaming.bytes.ManagedCursorStreamProvider FlowStack : at ftpSendEmailJsonAttachment(ftpSendEmailJsonAttachment/processors/2 @ mozart-scenarios:null:717) Element : ftpSendEmailJsonAttachment/processors/2 @ mozart-scenarios:null:717 Element XML : #[[{id: attributes.name,contentType: """"application/json"""",content: payload.value} as Object {class: """"org.mule.extension.email.api.EmailAttachment""""}]] Email Content -------------------------------------------------------------------------------- Root Exception stack trace: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type application/json at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:896) at javax.activation.DataHandler.writeTo(DataHandler.java:317) at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1383) at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:852) at javax.mail.internet.MimeMultipart.writeTo(MimeMultipart.java:453) at com.sun.mail.handlers.multipart_mixed.writeTo(multipart_mixed.java:81) at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:889) at javax.activation.DataHandler.writeTo(DataHandler.java:317) at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1383) at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1743) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1259) at javax.mail.Transport.send0(Transport.java:191) at javax.mail.Transport.send(Transport.java:120) at org.mule.extension.email.internal.commands.SendCommand.send(SendCommand.java:56) at org.mule.extension.email.internal.sender.SendOperation.send(SendOperation.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:203) at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.lambda$execute$0(ReflectiveMethodComponentExecutor.java:78) at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:163) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:958) at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.execute(ReflectiveMethodComponentExecutor.java:77) at org.mule.runtime.module.extension.internal.runtime.operation.ReflectiveMethodOperationExecutor.execute(ReflectiveMethodOperationExecutor.java:61) at org.mule.runtime.module.extension.internal.runtime.execution.ReactiveOperationExecutionWrapper.execute(ReactiveOperationExecutionWrapper.java:62) at org.mule.runtime.module.extension.internal.runtime.execution.InterceptableOperationExecutorWrapper.execute(InterceptableOperationExecutorWrapper.java:61) at org.mule.runtime.module.extension.internal.runtime.operation.DefaultExecutionMediator.lambda$executeWithInterceptors$7(DefaultExecutionMediator.java:124) at reactor.core.publisher.MonoCreate.subscribe(MonoCreate.java:51) at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:60) at reactor.core.publisher.MonoMapFuseable.subscribe(MonoMapFuseable.java:59) at reactor.core.publisher.MonoSwitchIfEmpty.subscribe(MonoSwitchIfEmpty.java:44) at reactor.core.publisher.MonoOnErrorResume.subscribe(MonoOnErrorResume.java:44) at reactor.core.publisher.Mono.block(Mono.java:1300) at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$null$0(OperationMessageProcessor.java:154) at org.mule.runtime.core.policy.DefaultPolicyManager.lambda$createOperationPolicy$1(DefaultPolicyManager.java:107) at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$null$1(OperationMessageProcessor.java:161) at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:163) at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) at org.mule.runtime.module.extension.internal.runtime.operation.OperationMessageProcessor.lambda$apply$3(OperationMessageProcessor.java:147) at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.rx.Exceptions.lambda$checkedFunction$3(Exceptions.java:87) at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:107) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onNext(FluxPeekFuseable.java:188) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onNext(FluxPeekFuseable.java:188) at reactor.core.publisher.FluxSubscribeOnValue$ScheduledScalar.run(FluxSubscribeOnValue.java:160) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.mule.service.scheduler.internal.AbstractRunnableFutureDecorator.doRun(AbstractRunnableFutureDecorator.java:88) at org.mule.service.scheduler.internal.RunnableFutureDecorator.run(RunnableFutureDecorator.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ******************************************************************************** ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12457","05/12/2017 14:32:45",1,"Remove distribution management from Soap parent pom. ""Remove distribution management from Soap parent pom so that childs do not inherit that configuration.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12459","05/12/2017 19:02:39",1,"OAuth extension fails if it doesn't provide default set of scopes ""if defaultScopes are not provided on the @AuthorizationCode annotation, then the extension fails""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12465","05/12/2017 22:43:28",2,"Thread contention on System.getProperty in ModuleFlowProcessingPhase ""Thread contention on System.getProperty in ModuleFlowProcessingPhase""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12466","05/13/2017 00:03:43",1,"AuthCodeState should give more information ""Although at first it was thought as unnecesary, the AuthorizationCodeState needs to also provide access to: * The authorizatio url * The access token url * The consumer key * The consumer secret""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12467","05/13/2017 03:59:33",5,"Collection/Map DataTypes lack generics ""Changes were recently introduced to indicate the EL the expected DataType of an evaluation so that when a parameter is resolved the EL can do type coercion or fail accordingly if necessary. We have also introduced the MapDataType. However, this is not being considered and Collections/Maps lack the generic data that would allow the EL to know that all items on a list should be ints, for example, or that the keys of a Map should be Strings and the values some POJO.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12473","05/15/2017 15:44:19",3,"email config elements should have the -config suffix ""The email config elements should end with the -config elements. The SDK should actually automatically enforce this""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12474","05/15/2017 15:48:02",3,"WSC: Improve authentication representation in the extension ""Right now, in order to represent the different authentication method supported by the WSC, the extension is using a list with subtypes. This is not an accurate representation of what the users can do, as they should always configure 1 of each subtype, and they should not be allowed to configure more than once each. If we change the list of subtypes, to single optional fields for each type, not only we are reflecting what the users should be doing, but improve the experience when configuring it.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12475","05/15/2017 15:56:46",0,"Support smart connectors that rely on EE elements ""A smart connector might rely on some EE elements (such as *transform*, *cache*, or any other EE plugin) in which case the tooling client must be responsible of loading the needed JARs to be sure all resources are available. Right now, it fails discovering the schemas for the DW *transform* element, but this will be an issue if some Java services are EE only, in which case Java SDK connectors will fail as well to load the extension model. This jira blocks MULE-12440""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12476","05/15/2017 16:01:13",5,"Set definitive default streaming buffer sizes ""Determine the best streaming buffer sizes defaults and impact the code""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12477","05/15/2017 16:18:30",8,"Additional streaming performance work ""Take additional profiling sessions, Tackle additional issues that arise.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12480","05/15/2017 16:37:11",5,"support custom http:listener in OAuth enabled extensions ""Support custom http listener in the callback definition""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12483","05/15/2017 19:32:38",2,"Old javax.mail bundled with HTTP connector ""HTTP connector bundles javax.mail 1.4.3 which was released in 2010. We must include a newer version. (1.5.6 released in 2016).""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12485","05/15/2017 19:57:32",2,"Remove listener interpretRequestErrors feature ""The interpretRequestErrors feature was mistakenly conceived as a way to deal with proxies where the request would fail. However, a proper proxy should not treat any status code as a failure but propagate that response (using a success status code validator from 0 to 599). We need to remove the feature since it's useless and will only create confusion.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12488","05/16/2017 15:10:39",5,"Soap Connect: Give the capability to inject custom headers to the requests. ""Give the capability to inject custom headers to the requests.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12489","05/16/2017 15:44:18",8,"Review ignored distribution tests whose issues are in status resolved ""*Tests in scope* * DbTestCase#addBlob() * HttpRequesterTestCase#testHttpForEachWithDifferentKindOfPayloads() * HttpRequesterTestCase#testHttpsWithBasicAuthObtainingJsonAndThenApplyingTransformWith5mbInput() * ToolingServiceTestCase#connectivityTestingUsingJdbcDriver() *Status* [Ignored distribution tests review status|https://docs.google.com/a/mulesoft.com/spreadsheets/d/1mbatcGVq_lxyks5xDdVBCMFpbsZob1aCdgLklzwellM/edit?usp=sharing] ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12490","05/16/2017 20:26:30",8,"Issue with mule-config.json ""In order to use the lightweight package we need to configure the mule instance with the settings.xml and m2 repo. Doing this using the system properties works as expected However trying to use the mule-config.json in the conf folder, it seems does not work because the application model cannot be build. Note: I am testing this in windows. """," commandList.addAll(Arrays.asList(""""-M-DmuleRuntimeConfig.maven.repositoryLocation="""" + mavenConfiguration.getLocalRepositoryPath(), """"-M-DmuleRuntimeConfig.maven.mavenSettingsLocation="""" + mavenConfiguration.getSettingsPath())); { """"muleRuntimeConfig"""" : { """"mavenSettingsLocation"""" : """"C:\\Users\\ldebello\\.m2\\settings.xml"""", """"repositoryLocation"""": """"C:\\Users\\ldebello\\.m2\\repository"""", """"maven"""" : { """"repositories"""": { """"mavenCentral"""": { """"url"""": """"https://repo.maven.apache.org/maven2/"""" } } } } } ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12491","05/16/2017 20:30:52",2,"Validate loading extension models with different loader types ""Plugins could use different loaders for ExtensionModels, this ticket is about validating that those loaders work on Tooling Client.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12492","05/16/2017 20:32:20",2,"Tooling client is not deleting the temporal apps ""It seems applications cannot be dispose because keeps some files in /tmp/tooling/. Note: I am in windows OS.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12494","05/16/2017 20:53:38",0,"Move ObjectStore to Mule API ""Move ObjectStore to API in order enable the new object store connector""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12495","05/16/2017 22:21:01",2,"Remove mule.tls.disableSystemPropertiesMapping functionality ""Aether configuration requires using the JVM default trust store. Since this runs at the beginning of all tests, it can interfere with the tests verifying the use of mule.tls.disableSystemPropertiesMapping, a property introduced for backwards compatibility that makes mule map the HTTP transport trust store as a JVM property (java.net.ssl.trustStore) and makes no TLS configuration required for HTTP clients in tests. We need to get rid of that property and functionality since it's wrong (it was only added in case clients depended on it). ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12498","05/17/2017 17:40:27",1,"Groovy should not be loaded on the container classloader ""Groovy jar is being deployed on MULE_HOME/lib/opt but is not used on the container. That jar is used in order to run the launcher script only, so it should be located in a lib folder that is not included in the container classloader. ""","",1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12499","05/17/2017 18:48:48",8,"Cannot retrieve metadata from an EE processor ""As of today, the tooling client is not being able to provide definitions for core EE message processors and this makes it impossible to retrieve DataSense for an EE processor, such as DW transform, as the component is not properly loaded and the component location has the form {{flowName/0}} instead of {{flowName/processors/0}}. This also creates a shift in the indexes used for the flow processors in general affecting requests for other components in the same flow.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12500","05/17/2017 18:48:52",8,"Remove endorsed XML libraries in 4.x ""Make the same changes from MULE-12245 in Mule 4.x. It shouldn't be very different, but there are more repositories to change.""","",0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12501","05/17/2017 18:49:50",0,"Make MuleProcessController extensible ""This is needed in order to be able to do system tests of EE specific functionality (i.e.: server plugins).""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12502","05/17/2017 19:46:28",0,"Filter inside When changes When expression ""SE-5854 If a Filter is defined inside a When element, then the Filter expression is set as the expression in the When element. That is ok, since there are tests that check that functionality but the problem arises when """"expression"""" is already set inside When and it get replaced. Besides, the expression change will be made with the Filter in any position inside When children. This happens when the parent of the Filter element is checked in FilterRefDefinitionParser:56 and no MessageProcessorWrappingBeanAssembler is created for when beanAssembler.copyBeanToTarget() (ParentDefinitionParser:66) is called. ""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12509","05/18/2017 16:41:55",8,"Create a single Jenkins Pipeline running all projects to validate feature changes ""Create a single Jenkins Pipeline running all projects to validate feature changes""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12513","05/18/2017 20:40:22",2,"NoSucheMethodError while using email connector ""Using new email connector in a try it test case (tooling), results on NoSuchMethodError, because javax.email package is defined in Boot packages, and email connector needs a newer version of it. App: """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12515","05/18/2017 21:21:49",3,"Email Send operation should receive a TypedValue instead of a EmailBody ""*Email Send operation should receive a TypedValue instead of a EmailBody* * The usage of the {{EmailBody}} produces issues in performance because the {{content}} is a {{String}} the entire content will be loaded on memory. * Set manually the {{encoding}} and {{mimeType}} is not consistent with the rest of the connectors that takes the {{mimeType}} from the given value (HTTP, JMS) * Using String as the content will produce issues when transforming from others mimeTypes ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12516","05/18/2017 21:24:51",3,"WebService consumer should receive InputStreams as the inputs of the Invoke operation ""*WebService consumer should receive InputStreams as the inputs of the Invoke operation* * This should be done to prevent performance issues, due that receiving a String will make load the entire String on memory instead of consuming from an InputSream * The usage of Strings will produce issues in transformations of different mimeTypes""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12518","05/19/2017 12:52:28",2,"SchedulerService does not support queue size of 0 ""SchedulerService does not support queue size of 0""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12519","05/19/2017 12:55:08",2,"SchedulerService should not use ThrottledScheduler if maxConcurrency > pool size ""Currently ThrottledScheduler introduces significant thread contention doe to synchonrized block. This can potentially be improved, but it's best to avoid using ThottledScheduler completely when maxConcurrency > poolSize""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12520","05/19/2017 18:09:27",3,"Serialisation of transform operation fails with custom parameters ""The artifact declaration serializer fails when attempting to serialize a declaration containing a transform operation that is configured with custom parameters.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12521","05/19/2017 18:18:53",2,"Expose servers protocol ""In order to establish a base url for a given server we need to expose it's protocol (ip and port are already available).""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12524","05/19/2017 19:56:51",5,"Soap Connect fails to dispose http clients when more than one service is connected ""When the ForwardingSoapClient loads more than once SoapClient it leaks resources cause is not disposing properly the related resources while doing the onRemove() or disconnect(). ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12525","05/19/2017 21:09:33",8,"ArtifactDeclaration should represent the ParameterGroups model ""ArtifactDeclaration should represent the ParameterGroups""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12526","05/19/2017 21:39:03",3,"HTTP Listener source allows config-ref as optional ""HTTP Listener source allows config-ref as optional ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12527","05/19/2017 21:58:35",2,"ProcessorInterceptor API does not send componentLocation ""The API org.mule.runtime.api.interception.ProcessorInterceptor does not send the componentLocation of the processor being intercepted to each of the methods of the API. These things are necessary at the point of interception to decide if action should be taken or not.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12528","05/19/2017 22:49:47",2,"Race condition when stopping an ExtensionSource while it's being recconnected ""Reconnection on ExtensionSource must not be attempted if a stop is in process.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12530","05/21/2017 21:44:03",1,"Upgrade commons-beanutils to 1.9.3 ""Upgrade commons-beanutils to version 1.9.3 to leverage the latest bugfixes.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12534","05/22/2017 15:30:19",5,"When using TypedValue the SDK provides a CursorProvider instead of a Cursor ""*When using TypedValue the SDK provides a CursorProvider instead of a Cursor* * This affects JMS and HTTP * HTTP also has a bug when consuming the stream, because it returns the {{@OnSuccess}} method before consuming the entire stream. h2. EXAMPLE JMS: JmsMessageBuilder In this case, if the payload is a {{CursorStreamProvider}} the SDK should not inject a {{TypedValue}} The same happens in HTTP, but as HTTP when an unknown value is given, it will use the transformation service, so it will not suffer this issue but is not the correct way to do it. ""","public class JmsMessageBuilder { /** * The body of the {@link Message} */ @Parameter @XmlHints(allowReferences = false) @Content(primary = true) @Summary(""""The body of the Message"""") private TypedValue body; ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12537","05/22/2017 16:42:28",0,"Smart Connector source and package project must be as similar as a mule application as possible ""The structure of any smart connector must be as similar as possible as a mule application, which means it must have a *mule* folder where all the XMLs are dropped from. Today's project's folder has the following: when ideally should be and the generated package must also respect that convention (which means that the JAR file will have a *mule* folder with all of its files there, and the deployment must be able to look for them accorindly)""","➜ smart-connectors git:(master) tree smart-connector-using-core smart-connector-using-core ├── pom.xml └── src └── main └── resources └── module-using-core.xml 3 directories, 3 files ➜ smart-connectors git:(master)➜ smart-connectors git:(master) tree smart-connector-using-core smart-connector-using-core ├── pom.xml ├── mule └── module-using-core.xml └── src └── main └── resources 3 directories, 3 files ➜ smart-connectors git:(master)",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12538","05/22/2017 17:50:47",1,"Configure Garbage Collection parameters for JDK 8 in Mule 4 ""Starting with Mule 4.0, we only support Java 8 for running Mule. Garbage collection configuration needs to be optimized to run with JDK 8. The following messages need to be eliminated: """," Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: Using the ParNew young collector with the Serial old collector is deprecated and will likely be removed in a future release ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12541","05/22/2017 19:15:55",1,"Upgrade log4j2 to 2.8.2 ""Upgrade log4j2 to 2.8.2""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12556","05/23/2017 02:23:25",2,"Upgrade opensaml to 2.6.4 ""Upgrade opensaml to 2.6.4 in the SOAP service.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12559","05/23/2017 09:25:33",2,"BlockingTransferInputStream should implement read(byte[] b, int off, int len) ""BlockingTransferInputStream should implement read(byte[] b, int off, int len)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12560","05/23/2017 13:25:22",2,"Improve performance of ObjectToString transformer ""The approach used to convert InputStream to String in 4.0.0 has been changed and is less performant than in 3.x. Revert this change and add micro-benchmark to confirm.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12561","05/23/2017 14:34:12",8,"Improve datasense performance ""Currently the whole cycle of executing datasense from studio is taking too long. We need to profile a little bit to improve the experience ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12562","05/23/2017 16:46:27",1,"Reduce logging level of certain components ""Mule team, can we move the following messages to debug level: * AbstractDataTypeBuilderFactory * SpringXmlConfigurationBuilder""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12567","05/23/2017 19:52:49",0,"Performance improvements on DW integration ""Echo scenario is a 6% faster with mel instead of default dw.""","",0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12570","05/23/2017 21:58:48",3,"Wrong ExtensionModel generation when adding errors to an operation ""See test ExtensionModelJsonGeneratorTestCase. When validating the generated extension model for the marvel extension there are additional error information added to operations unrelated to the one with error types.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12573","05/24/2017 14:50:49",2,"Extract embedded-api to its own repo ""The embedded API is versioned differently than the impl, so it must be in its own repo to allow for an independent release lifecycle.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12574","05/24/2017 15:38:32",3,"Add ""kind"" to Source and ErrorHandlers in ExtensionModel serialization ""Add """"kind"""" to Source and ErrorHandlers in ExtensionModel serialization. Currently, not all the ComponentModels are serialized with its kind, it would be better to declare the explicitly even if it's more verbose.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12576","05/24/2017 15:48:36",2,"Tooling Client Integration test for email ObjectStreams ""After MULE-12513 is fixed, finish ignored test in TryItTestCase""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12579","05/24/2017 17:34:16",5,"Create a StreamingHelper for operations ""We need to provide tools for handling repeatable streaming resources which are embedded into structures of arbitrary complexity""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12588","05/24/2017 21:51:59",8,"Support Sources that send asynchronous responses ""Some sources such as send responses asynchronously. When the response content is an InputStream and repeatable streams are enabled, there's a race condition betweent the runtime that closes the CursorStreamProvider (mainly because it doesn't know that http:listner is still asynchronously consuming the stream) and the listener which is actually replying. To do so, we need to support asynchronous response sources, so that the event is not completed until the source has actually finished sending the response.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12594","05/25/2017 00:31:39",8,"HTTP Listener: cannot create listeners for paths when one starts with the other ""Attempting to create a pair of http listeners like this: I get an error like """," ... ... Caused by: org.mule.runtime.api.exception.MuleRuntimeException: Already exists a listener matching that path and methods. Listener matching ListenerRequestMatcher{path='/ab/', methodRequestMatcher='MethodRequestMatcher{methods=[GET]}'} new listener ListenerRequestMatcher{path='/ab/', methodRequestMatcher='MethodRequestMatcher{methods=[GET]}'} at org.mule.service.http.impl.service.server.HttpListenerRegistry$ServerAddressRequestHandlerRegistry.validateCollision(HttpListenerRegistry.java:173) at org.mule.service.http.impl.service.server.HttpListenerRegistry$ServerAddressRequestHandlerRegistry.addRequestHandler(HttpListenerRegistry.java:102) at org.mule.service.http.impl.service.server.HttpListenerRegistry.addRequestHandler(HttpListenerRegistry.java:55) at org.mule.service.http.impl.service.server.grizzly.GrizzlyHttpServer.addRequestHandler(GrizzlyHttpServer.java:104) at org.mule.extension.http.internal.listener.HttpListener.onStart(HttpListener.java:235) ... 31 more ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12596","05/25/2017 16:00:29",2,"Tooling client must dispose unused apps after certain threshold ""If tooling client connection fails (for example), the application could still be up in the agent side, indefinitely. ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12613","05/26/2017 20:11:10",1,"Support patching module jars ""On current version of Mule, the container fails do start when it detects two modules with the same name. This check make us unable to deploy patches jars for modules. While a full patching solution is needed, we need at least a quick workaround to make this possible.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12614","05/26/2017 20:12:50",2,"OAuth service must support multitenancy between the same ObjectStore ""It is needed to hold tokens from different tenants on the same object store. It is needed for the OAuth service to optionally allow specifying prefix (and maybe even suffix) for the resorceOwnerId.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12616","05/26/2017 20:37:02",1,"Avoid exposing API config parameter ""Need to comment out the API config stuff so that's it's not visible until we do it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12945","05/26/2017 21:24:12",2,"Branch all the repositories for Mozart Beta ""Branch all the repositories for Mozart Beta ""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12619","05/27/2017 02:16:20",1,"ExtensionModel declarer allows invalid XML naming ""It's possible to use the HasOperationDeclarer (or any other declarer if I'm not mistaken) to create invalid XML components from the ExtensionModel by parameterizing wrong values, such as `declarer.withOperation(""""this is not << XML valid and yet works"""");`, Ideally, the API should either blow up throwing an exception or hypenizing the String (if possible, as parameterizing empty string is also invalid). Despite this issue is hard to reproduce from a Java connector, if @Alias is used as `@Alias(""""jaja <> le23 23 23 """"` it will end up in wrong XML namign operations, configurations, parameters, etc., ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12620","05/27/2017 02:54:46",5,"Connectivity test for SFTP doesn't show actual error ""Connectivity test for SFTP doesn't show the resolved path where it is trying to connect to. You know that the connectivity test failed, but in no place of the stacktrace you can see which is the actual path trying to be connected. This means that if the path has placeholders or expressions, you are not able to properly troubleshoot the error. """," Caused by: org.mule.extension.ftp.api.FTPConnectionException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused (Connection refused) (org.mule.runtime.extension.api.exception.ModuleException) at org.mule.extension.ftp.internal.sftp.connection.SftpConnectionProvider.handleJSchException(SftpConnectionProvider.java:158) ~[?:?] at org.mule.extension.ftp.internal.sftp.connection.SftpConnectionProvider.connect(SftpConnectionProvider.java:89) ~[?:?] at org.mule.extension.ftp.internal.sftp.connection.SftpConnectionProvider.connect(SftpConnectionProvider.java:38) ~[?:?] at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:59) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.ErrorTypeHandlerConnectionProviderWrapper.connect(ErrorTypeHandlerConnectionProviderWrapper.java:60) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:59) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.LifecycleAwareConnectionProviderWrapper.connect(LifecycleAwareConnectionProviderWrapper.java:61) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.PoolingConnectionManagementStrategy$ObjectFactoryAdapter.makeObject(PoolingConnectionManagementStrategy.java:142) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188) ~[commons-pool-1.6.jar:1.6] at org.mule.runtime.core.internal.connection.PoolingConnectionManagementStrategy.borrowConnection(PoolingConnectionManagementStrategy.java:95) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.PoolingConnectionManagementStrategy.getConnectionHandler(PoolingConnectionManagementStrategy.java:69) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.DefaultConnectionManager.getConnection(DefaultConnectionManager.java:218) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.DefaultConnectionManager.lambda$testConnectivity$1(DefaultConnectionManager.java:137) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.DefaultConnectionManager.doTestConnectivity(DefaultConnectionManager.java:153) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:129) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance$1.doWork(LifecycleAwareConfigurationInstance.java:188) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.retry.policies.AbstractPolicyTemplate.execute(AbstractPolicyTemplate.java:57) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.testConnectivity(LifecycleAwareConfigurationInstance.java:215) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.start(LifecycleAwareConfigurationInstance.java:164) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.api.lifecycle.LifecycleUtils.startIfNeeded(LifecycleUtils.java:189) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.startConfig(LifecycleAwareConfigurationProvider.java:189) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.lambda$null$3(LifecycleAwareConfigurationProvider.java:107) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.DefaultLifecycleManager.fireStartPhase(DefaultLifecycleManager.java:59) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.lambda$start$4(LifecycleAwareConfigurationProvider.java:105) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:175) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.start(LifecycleAwareConfigurationProvider.java:104) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) ~[?:?] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_131] at org.mule.runtime.core.internal.lifecycle.phases.DefaultLifecyclePhase.applyLifecycle(DefaultLifecyclePhase.java:186) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryLifecycleCallback.doApplyLifecycle(RegistryLifecycleCallback.java:95) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryLifecycleCallback.onTransition(RegistryLifecycleCallback.java:70) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryLifecycleManager.fireLifecycle(RegistryLifecycleManager.java:113) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker.fireLifecycle(AbstractRegistryBroker.java:74) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:125) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:68) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:65) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:57) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.DefaultMuleContext.start(DefaultMuleContext.java:354) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.start(DefaultMuleApplication.java:146) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:939) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:175) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:958) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:938) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:110) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.start(DeployableArtifactWrapper.java:99) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:24) ~[mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] ... 14 more Caused by: org.mule.runtime.extension.api.exception.ModuleException: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused (Connection refused) at org.mule.extension.ftp.api.FTPConnectionException.(FTPConnectionException.java:30) ~[?:?] at org.mule.extension.ftp.internal.sftp.connection.SftpConnectionProvider.handleJSchException(SftpConnectionProvider.java:158) ~[?:?] at org.mule.extension.ftp.internal.sftp.connection.SftpConnectionProvider.connect(SftpConnectionProvider.java:89) ~[?:?] at org.mule.extension.ftp.internal.sftp.connection.SftpConnectionProvider.connect(SftpConnectionProvider.java:38) ~[?:?] at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:59) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.ErrorTypeHandlerConnectionProviderWrapper.connect(ErrorTypeHandlerConnectionProviderWrapper.java:60) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:59) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.LifecycleAwareConnectionProviderWrapper.connect(LifecycleAwareConnectionProviderWrapper.java:61) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.PoolingConnectionManagementStrategy$ObjectFactoryAdapter.makeObject(PoolingConnectionManagementStrategy.java:142) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188) ~[commons-pool-1.6.jar:1.6] at org.mule.runtime.core.internal.connection.PoolingConnectionManagementStrategy.borrowConnection(PoolingConnectionManagementStrategy.java:95) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.PoolingConnectionManagementStrategy.getConnectionHandler(PoolingConnectionManagementStrategy.java:69) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.DefaultConnectionManager.getConnection(DefaultConnectionManager.java:218) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.DefaultConnectionManager.lambda$testConnectivity$1(DefaultConnectionManager.java:137) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.DefaultConnectionManager.doTestConnectivity(DefaultConnectionManager.java:153) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:129) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance$1.doWork(LifecycleAwareConfigurationInstance.java:188) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.retry.policies.AbstractPolicyTemplate.execute(AbstractPolicyTemplate.java:57) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.testConnectivity(LifecycleAwareConfigurationInstance.java:215) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.start(LifecycleAwareConfigurationInstance.java:164) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.api.lifecycle.LifecycleUtils.startIfNeeded(LifecycleUtils.java:189) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.startConfig(LifecycleAwareConfigurationProvider.java:189) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.lambda$null$3(LifecycleAwareConfigurationProvider.java:107) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.DefaultLifecycleManager.fireStartPhase(DefaultLifecycleManager.java:59) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.lambda$start$4(LifecycleAwareConfigurationProvider.java:105) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:175) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.start(LifecycleAwareConfigurationProvider.java:104) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) ~[?:?] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_131] at org.mule.runtime.core.internal.lifecycle.phases.DefaultLifecyclePhase.applyLifecycle(DefaultLifecyclePhase.java:186) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryLifecycleCallback.doApplyLifecycle(RegistryLifecycleCallback.java:95) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryLifecycleCallback.onTransition(RegistryLifecycleCallback.java:70) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryLifecycleManager.fireLifecycle(RegistryLifecycleManager.java:113) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker.fireLifecycle(AbstractRegistryBroker.java:74) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:125) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:68) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:65) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:57) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.DefaultMuleContext.start(DefaultMuleContext.java:354) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.start(DefaultMuleApplication.java:146) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:939) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:175) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:958) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:938) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:110) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.start(DeployableArtifactWrapper.java:99) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:24) ~[mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] ... 14 more Caused by: com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused (Connection refused) at com.jcraft.jsch.Util.createSocket(Util.java:394) ~[?:?] at com.jcraft.jsch.Session.connect(Session.java:215) ~[?:?] at com.jcraft.jsch.Session.connect(Session.java:183) ~[?:?] at org.mule.extension.ftp.internal.sftp.connection.SftpClient.connect(SftpClient.java:166) ~[?:?] at org.mule.extension.ftp.internal.sftp.connection.SftpClient.login(SftpClient.java:148) ~[?:?] at org.mule.extension.ftp.internal.sftp.connection.SftpConnectionProvider.connect(SftpConnectionProvider.java:87) ~[?:?] at org.mule.extension.ftp.internal.sftp.connection.SftpConnectionProvider.connect(SftpConnectionProvider.java:38) ~[?:?] at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:59) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.ErrorTypeHandlerConnectionProviderWrapper.connect(ErrorTypeHandlerConnectionProviderWrapper.java:60) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:59) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.LifecycleAwareConnectionProviderWrapper.connect(LifecycleAwareConnectionProviderWrapper.java:61) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.PoolingConnectionManagementStrategy$ObjectFactoryAdapter.makeObject(PoolingConnectionManagementStrategy.java:142) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188) ~[commons-pool-1.6.jar:1.6] at org.mule.runtime.core.internal.connection.PoolingConnectionManagementStrategy.borrowConnection(PoolingConnectionManagementStrategy.java:95) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.PoolingConnectionManagementStrategy.getConnectionHandler(PoolingConnectionManagementStrategy.java:69) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.DefaultConnectionManager.getConnection(DefaultConnectionManager.java:218) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.DefaultConnectionManager.lambda$testConnectivity$1(DefaultConnectionManager.java:137) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.DefaultConnectionManager.doTestConnectivity(DefaultConnectionManager.java:153) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:129) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance$1.doWork(LifecycleAwareConfigurationInstance.java:188) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.retry.policies.AbstractPolicyTemplate.execute(AbstractPolicyTemplate.java:57) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.testConnectivity(LifecycleAwareConfigurationInstance.java:215) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.start(LifecycleAwareConfigurationInstance.java:164) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.api.lifecycle.LifecycleUtils.startIfNeeded(LifecycleUtils.java:189) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.startConfig(LifecycleAwareConfigurationProvider.java:189) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.lambda$null$3(LifecycleAwareConfigurationProvider.java:107) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.DefaultLifecycleManager.fireStartPhase(DefaultLifecycleManager.java:59) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.lambda$start$4(LifecycleAwareConfigurationProvider.java:105) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:175) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.start(LifecycleAwareConfigurationProvider.java:104) ~[mule-module-extensions-support-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) ~[?:?] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_131] at org.mule.runtime.core.internal.lifecycle.phases.DefaultLifecyclePhase.applyLifecycle(DefaultLifecyclePhase.java:186) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryLifecycleCallback.doApplyLifecycle(RegistryLifecycleCallback.java:95) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryLifecycleCallback.onTransition(RegistryLifecycleCallback.java:70) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryLifecycleManager.fireLifecycle(RegistryLifecycleManager.java:113) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker.fireLifecycle(AbstractRegistryBroker.java:74) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:125) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:68) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:65) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:57) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.DefaultMuleContext.start(DefaultMuleContext.java:354) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.start(DefaultMuleApplication.java:146) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:939) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:175) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:992) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:958) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.core.util.ClassUtils.withContextClassLoader(ClassUtils.java:938) ~[mule-core-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:110) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.start(DeployableArtifactWrapper.java:99) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:24) ~[mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] ... 14 more Caused by: java.net.ConnectException: Connection refused (Connection refused) at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_131] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_131] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:1.8.0_131] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:1.8.0_131] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_131] at java.net.Socket.connect(Socket.java:589) ~[?:1.8.0_131] at java.net.Socket.connect(Socket.java:538) ~[?:1.8.0_131] at java.net.Socket.(Socket.java:434) ~[?:1.8.0_131] at java.net.Socket.(Socket.java:211) ~[?:1.8.0_131] at com.jcraft.jsch.Util$1.run(Util.java:362) ~[?:?] at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_131] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12626","05/29/2017 15:40:17",1,"Remove evaluateExpression from notification ""After Studio moves to the interception API, we should remove our method MessageProcessorNotification#evaluateExpression (and corresponding one in EnrichedNotificationInfo).""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12627","05/29/2017 15:41:10",5,"Make soap connect EE ""Make soap connect EE ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12628","05/29/2017 15:45:19",2,"Rename scheduler components ""Rename `scheduling-strategy` inner child element to reduce verbosity and avoid redundancy. `fixed-frequency-scheduler` -> `fixed-frequency` `cron-scheduler` -> `cron`""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12629","05/29/2017 16:39:40",3,"Cannot have OAuth multitenancy in the same ObjectStore ""(insert)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12633","05/29/2017 18:34:14",8,"Create BOM for EE and use it on Tooling ""Currently, we are using a POM on tooling side that includes all modules. We should have a differentiated POM for EE version (so eventually CE version of Tooling will run on a CE version of the Agent)""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12634","05/29/2017 20:56:27",2,"Add a getNamedParts() method in MultiPartPayload ""MultiPartPayload currently has a getPart(String partName), but that is not usable from within DataWeave. DataWeave needs a proper getter method that returns a Map.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12635","05/29/2017 21:01:50",2,"Maven Configuration is not taken from the tooling client ""While using the org.mule.tooling.client.internal.DefaultToolingRuntimeClientBuilder , when users override the maven configuration, this information is not propagated to the org.mule.tooling.client.api.extension.ExtensionModelService, making it impossible to solve extensions that don't use the default tooling client configuration""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12641","05/30/2017 13:24:46",3,"If @Errors annotation is not defined, the extension doesn't get enriched by any kind of error ""*If @Errors annotation is not defined, the extension doesn't get enriched by any error* * Nowadays the extension can be enriched automatically by several kinds of errors types automatically, e.g., CONNECTIVITY, SOURCE, etc. * But those are not being populated if the {{@Errors}} annotation is not used.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12645","05/30/2017 15:51:50",1,"Use standard license header mechanism in mule-api ""Use standard license header mechanism in mule-api as it's done in mule.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12649","05/30/2017 17:55:07",8,"Deployment should also consider remote repositories defined in pom.xml ""There will be cases where applications packaged on lightweight mode would need to download dependencies from remote repositories that are declared in the same pom.xml. This is a best practice when working with Maven and it should be handled by deployment module.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12651","05/30/2017 18:59:45",8,"Extensions resolution should fetch transitive dependencies ""When an application have http or ftp as dependencies it is not solving sockets when fetching extensions within tooling client or deploying an application.""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12652","05/30/2017 19:54:31",0,"Fix flaky ExceptionHandlingTestCase ""The problem is between the persistent object store and the deserialization mechanism.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12654","05/30/2017 22:37:45",2,"Improve application URL supplier calls in DataSense requests ""For every datasense request, the supplier is being call 3 times. 1 for extensions calculations, 1 for datasense static fetching, 1 for datasense dynamic We need to reduce the amount of times that we are fetching the zip. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12656","05/31/2017 16:04:46",5,"Descriptions are not populated in the extension model ""The description for some parameters is not being populated. For example in the e-mail connector, several parameters and operations have no description. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12657","05/31/2017 16:30:56",8,"Resolve extension models internally in tooling client services ""Resolve extension models internally as it's being done in the datasense service so tooling can stop depending on extension models to consume tooling client services. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12659","05/31/2017 17:34:17",3,"ResourceOwnerId should be optional ""The resourceOwnerId parameter in the OAuth connection providers is set as required but should be optional and have no default. Then, when the OauthConncetionProvider tries to use it to fetch the access token from the Dancer, it should consider the possibility of that parameter being null.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12661","05/31/2017 17:51:22",1,"Fix ArtifactSerializationServiceTestCase tests ""ArtifactSerializationTestCase tests for json have been failing for many builds""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12664","05/31/2017 20:20:05",5,"Fix SOAP Connect message builder to match WSC builder ""Fix SOAP Connect message builder to match WSC builder. - Add wrapper element with inline group - Rename `request` to `body`""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12666","05/31/2017 21:04:16",2,"Missing identifier in ComponentPath for OnError components ""The component path for an error handler with an on-error child is missing the `onError` identifier""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12669","05/31/2017 22:13:33",1,"Fix ConfigurationBasedDslElementModelSerializerTestCase ""Fix ConfigurationBasedDslElementModelSerializerTestCase""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12671","06/01/2017 15:29:23",3,"WSC is not providing a way to pass transport headers ""WSC is not providing a way to pass transport headers""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12673","06/01/2017 17:28:53",8,"Fix cases when an exception occurs in an error handler ""Currently when an exception is thrown from an error handler, it's not propagated even if wrapped inside another error handler. Also, in the case of interceptors such as CXF, as the event is not correctly preserved (it's null) the final error response isn't a valid SOAP message (the XML tags aren't inserted around the original error description).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12674","06/01/2017 21:19:22",5,"SDK fails to create Parameter Group if this contains a parameters of TypedValue and a T ""*SDK fails to create Parameter Group if this contains a parameters of TypedValue and a T* * if a Parameter Group has the following parameters: The SDK will fail to build this construction due that {{val2}} will use a ValueResolver to create {{TypedValue}} instances or vice versa. * The origin of this problems surges in {{ExtensionObjectTypeHandler}}, where if a TypedValue field is found, the handler will unwrap the generic type and set the field type of that generic type, example: {{TypedValue -> String}}, and then in the SDK to know that this field was originally a {{TypedValue}} to be able to build it correctly, the {{TypedValueTypeAnnotation}} to know that that field is not a {{String}}, but a {{TypedValue}}. * Due that JavaTypeLoader has a {{ParsingContext}} where it caches temporally the already parsed Types, if a {{TypedValue}} is parsed, a String type will be stored with the {{TypedValueTypeAnnotation}}, the if the plain String parameter gets parsed, the already cached builder will be taken, (the one with the annotatioin)"""," @Parameter TypedValue val1; @Parameter InputStream val2; ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12680","06/02/2017 21:38:32",0,"Server Notifications should expose SecurityContext/Authentication ""Gateway need access to SecurityContext/Authentication from Server Notifications to be able to send information to analytics""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12681","06/02/2017 21:57:58",0,"Add test cases for Interception API with Smart Connectors ""We need to have coverage of Interception API interacting with Smart Connectors. As part of this, the test smart connectors need to be included in the reactor of *mule-integration-tests*""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12682","06/02/2017 22:33:23",2,"ErrorHandler model should be a Router instead of a Scope ""Currently, the errorHandler component is defined as a Scope in Mule's ExtensionModel, but a Router fits better it's definition, since the onError* would act as Routes.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12684","06/04/2017 00:44:20",8,"Make Email DW and MediaType friendly ""*Make Email DW and MediaType friendly* This implies: * Change how Email consumes the body and attachments when sending emails, starting consuming TypedValue<> to be able to infer the MediaType of each content. * Change how Email list emails, exposing automatically the MediaType of each body and attachments that receive.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12685","06/05/2017 00:01:38",1,"Review the need for system property ""mule.objectstore.user.transient"" ""The system property """"mule.objectstore.user.transient"""" is used in DefaultObjectStoreFactoryBean#createDefaultUserObjectStore(). Check the need for it and either remove or document it.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12686","06/05/2017 00:19:34",0,"Remove redundant mule module files from extensions ""Sockets and validation extensions contain mule-module.properties files which are not used""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12688","06/05/2017 14:43:21",5,"Make WSC DW and MediaType friendly ""Make WSC DW and MediaType friendly""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12689","06/05/2017 20:08:23",2,"Extensions maven plugin fails on uber reactor when building the first connector ""When building the uber reactor project, the first connector to be built fails with the error: This seems to be related to a problem in maven when a project uses a plugin that depends on a module of the same reactor. This is the case for connectors -> mule-extensions-maven-plugin -> mule-api This is reported in maven as https://issues.apache.org/jira/browse/MNG-5787 (the problem persists with maven 3.3.9 though)"""," at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:166) ... 21 more Caused by: java.lang.NoClassDefFoundError: org/mule/runtime/api/deployment/persistence/MulePluginModelJsonSerializer at org.mule.extension.maven.loader.MulePluginJsonDescriberLoader.loadMulePluginDescriber(MulePluginJsonDescriberLoader.java:38) at org.mule.extension.maven.ExtensionModelMojo.execute(ExtensionModelMojo.java:57) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) ... 21 more Caused by: java.lang.ClassNotFoundException: org.mule.runtime.api.deployment.persistence.MulePluginModelJsonSerializer at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) ... 24 more ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12690","06/05/2017 20:15:39",5,"SOAPService should consume and expose the MediaType of the downloaded attachments ""*SOAPService should consume and expose the MediaType of the downloaded attachments* * Juani, you know what to do""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12691","06/05/2017 21:02:26",5,"SDK: same name parameters of different types should not be allowed. ""When an operation has 2 parameter groups with parameters that have the same name but its type is different the SDK should trow an error at compile time since this is not going to work because of the how the parsers are made. For example having an operation Ope1 with this structure: * Ope1 ** ParamGroup1 *** @Content String param1 *** anotherParam ** ParamGroup2 *** Int param1 param1 in the ParamGroup1 should clash with param1 in ParamGroup2 Ale you know what to do. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12693","06/05/2017 23:29:26",0,"Mule Maven Client is locking jar files ""When getting the URLs from inside a jar file, the mule-maven-client is not closing the JarFile, creating a resource leak. The issue is located at method org.mule.maven.client.internal.util.FileUtils#getUrlsWithinJar""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12694","06/06/2017 03:38:34",0,"Mule Maven Client is locking pom files ""When reading pom files, the mule-maven-client is not closing the FileReader, creating a resource leak. The issue is located at method org.mule.maven.client.internal.util.MavenUtils#getPomModelFolder""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12700","06/06/2017 15:04:31",1,"Missing @OnTerminate error message doesn't help you solve it ""When you have an extension with @OnSurccess or @OnError, users are forced to have an @OnTerminate annotated method. But if the users have no @OnTerminate method, the error reported doesn't help you as it simply states: Callback could mean anything, especially to new users. It should be straight forward and tell you that you have @OnSuccess and @OnError annotated methods and that to solve it you ned to add an @OnTerminate annotated method."""," The source [AnotherSource] defines a Success or Error Callback. If at least one of these are defined, a Terminate Callback should also be defined. ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12701","06/06/2017 15:54:57",2,"Change log level for maven client ""When deploying an application, the logs are full of maven client warnings that only generate noise to the users and give you the impression that the deployment is failing. We should change the log level of the component, or redirect it to another log and not the console. {code}"""," ********************************************************************** * Started domain 'default' * ********************************************************************** INFO 2017-06-06 11:34:43,190 [WrapperListener_start_runner] org.mule.runtime.module.deployment.internal.ArtifactArchiveInstaller: Exploding a Mule artifact archive: file:/usr/mule/apps/smart-test.jar INFO 2017-06-06 11:34:43,587 [WrapperListener_start_runner] org.mule.maven.client.internal.AetherMavenClient: About to fetch required dependencies for com.mycompany:smart-test:pom:1.0-SNAPSHOT. This may take a while... INFO 2017-06-06 11:34:44,713 [DefaultMetadataResolver-0-3] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml' from https://repository-master.mulesoft.org/nexus/content/repositories/snapshots/ WARN 2017-06-06 11:34:44,713 [DefaultMetadataResolver-0-2] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/releases/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata-mule-releases.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.connectors:mule-http-connector:1.0.0-SNAPSHOT/maven-metadata.xml in mule-releases (https://repository-master.mulesoft.org/nexus/content/repositories/releases/)) WARN 2017-06-06 11:34:44,910 [DefaultMetadataResolver-0-0] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/groups/mule-ee-dependencies/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata-mule-ee-dependencies.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.connectors:mule-http-connector:1.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-dependencies (https://repository-master.mulesoft.org/nexus/content/groups/mule-ee-dependencies/)) WARN 2017-06-06 11:34:44,911 [DefaultMetadataResolver-0-1] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/groups/enterprise/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata-mule-ee-enterprise.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.connectors:mule-http-connector:1.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-enterprise (https://repository-master.mulesoft.org/nexus/content/groups/enterprise/)) WARN 2017-06-06 11:34:45,072 [DefaultMetadataResolver-0-2] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/ci-releases/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata-mule-ee.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.connectors:mule-http-connector:1.0.0-SNAPSHOT/maven-metadata.xml in mule-ee (https://repository-master.mulesoft.org/nexus/content/repositories/ci-releases/)) WARN 2017-06-06 11:34:45,073 [DefaultMetadataResolver-0-3] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/ci-snapshots/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata-mule-ee-snapshots.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.connectors:mule-http-connector:1.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-snapshots (https://repository-master.mulesoft.org/nexus/content/repositories/ci-snapshots/)) WARN 2017-06-06 11:34:45,084 [DefaultMetadataResolver-0-0] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/releases-ee/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata-mule-ee-releases.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.connectors:mule-http-connector:1.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-releases (https://repository-master.mulesoft.org/nexus/content/repositories/releases-ee/)) WARN 2017-06-06 11:34:45,247 [DefaultMetadataResolver-0-3] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/ext-releases/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata-mule-ee-thirdparty.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.connectors:mule-http-connector:1.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-thirdparty (https://repository-master.mulesoft.org/nexus/content/repositories/ext-releases/)) WARN 2017-06-06 11:34:45,256 [DefaultMetadataResolver-0-0] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/codehaus-snapshots/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata-codehaus-plugin-snapshots.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.connectors:mule-http-connector:1.0.0-SNAPSHOT/maven-metadata.xml in codehaus-plugin-snapshots (https://repository-master.mulesoft.org/nexus/content/repositories/codehaus-snapshots/)) INFO 2017-06-06 11:34:46,097 [DefaultMetadataResolver-0-2] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml' from https://repository.mulesoft.org/nexus/content/repositories/snapshots/ WARN 2017-06-06 11:34:46,099 [DefaultMetadataResolver-0-2] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'http://maven-facade.ue1.kprod.k8s.prodx.msap.io/api/v1/maven/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata-anypoint-exchange.xml' (org.eclipse.aether.transfer.MetadataTransferException: Could not transfer metadata org.mule.connectors:mule-http-connector:1.0.0-SNAPSHOT/maven-metadata.xml from/to anypoint-exchange (http://maven-facade.ue1.kprod.k8s.prodx.msap.io/api/v1/maven): maven-facade.ue1.kprod.k8s.prodx.msap.io: unknown error) WARN 2017-06-06 11:34:46,145 [DefaultMetadataResolver-0-3] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'http://dev.modusintegration.com/repositories/releases/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata-modus-repository-releases.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.connectors:mule-http-connector:1.0.0-SNAPSHOT/maven-metadata.xml in modus-repository-releases (http://dev.modusintegration.com/repositories/releases/)) WARN 2017-06-06 11:34:46,270 [DefaultMetadataResolver-0-2] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository.mulesoft.org/releases/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata-mulesoft-releases.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.connectors:mule-http-connector:1.0.0-SNAPSHOT/maven-metadata.xml in mulesoft-releases (https://repository.mulesoft.org/releases/)) WARN 2017-06-06 11:34:46,340 [DefaultMetadataResolver-0-0] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'http://dev.modusintegration.com/repositories/snapshots/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata-modus-repository-snapshots.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.connectors:mule-http-connector:1.0.0-SNAPSHOT/maven-metadata.xml in modus-repository-snapshots (http://dev.modusintegration.com/repositories/snapshots/)) INFO 2017-06-06 11:34:46,362 [DefaultMetadataResolver-0-1] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml' from https://repository.mulesoft.org/nexus/content/repositories/private/ INFO 2017-06-06 11:34:46,987 [DefaultMetadataResolver-0-3] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/maven-metadata.xml' from https://repository.mulesoft.org/snapshots/ WARN 2017-06-06 11:34:47,198 [WrapperListener_start_runner] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/groups/mule-ee-dependencies/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/mule-http-connector-1.0.0-20170605.235434-359.pom <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/mule-http-connector-1.0.0-20170605.235434-359.pom' (org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.mule.connectors:mule-http-connector:pom:1.0.0-20170605.235434-359 in mule-ee-dependencies (https://repository-master.mulesoft.org/nexus/content/groups/mule-ee-dependencies/)) WARN 2017-06-06 11:34:47,373 [WrapperListener_start_runner] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/groups/enterprise/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/mule-http-connector-1.0.0-20170605.235434-359.pom <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/mule-http-connector-1.0.0-20170605.235434-359.pom' (org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.mule.connectors:mule-http-connector:pom:1.0.0-20170605.235434-359 in mule-ee-enterprise (https://repository-master.mulesoft.org/nexus/content/groups/enterprise/)) WARN 2017-06-06 11:34:47,549 [WrapperListener_start_runner] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/releases/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/mule-http-connector-1.0.0-20170605.235434-359.pom <> /usr/mule/apps/smart-test/repository/org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/mule-http-connector-1.0.0-20170605.235434-359.pom' (org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact org.mule.connectors:mule-http-connector:pom:1.0.0-20170605.235434-359 from/to mule-releases (https://repository-master.mulesoft.org/nexus/content/repositories/releases/): Unauthorized (401)) INFO 2017-06-06 11:34:47,742 [WrapperListener_start_runner] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/connectors/mule-http-connector/1.0.0-SNAPSHOT/mule-http-connector-1.0.0-20170605.235434-359.pom' from https://repository-master.mulesoft.org/nexus/content/repositories/snapshots/ WARN 2017-06-06 11:34:47,920 [DefaultMetadataResolver-1-0] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/groups/mule-ee-dependencies/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-ee-dependencies.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-dependencies (https://repository-master.mulesoft.org/nexus/content/groups/mule-ee-dependencies/)) INFO 2017-06-06 11:34:47,923 [DefaultMetadataResolver-1-3] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml' from https://repository-master.mulesoft.org/nexus/content/repositories/snapshots/ WARN 2017-06-06 11:34:47,923 [DefaultMetadataResolver-1-1] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/groups/enterprise/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-ee-enterprise.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-enterprise (https://repository-master.mulesoft.org/nexus/content/groups/enterprise/)) WARN 2017-06-06 11:34:47,925 [DefaultMetadataResolver-1-2] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/releases/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-releases.xml' (org.eclipse.aether.transfer.MetadataTransferException: Could not transfer metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml from/to mule-releases (https://repository-master.mulesoft.org/nexus/content/repositories/releases/): Unauthorized (401)) WARN 2017-06-06 11:34:48,094 [DefaultMetadataResolver-1-0] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/ci-releases/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-ee.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mule-ee (https://repository-master.mulesoft.org/nexus/content/repositories/ci-releases/)) WARN 2017-06-06 11:34:48,096 [DefaultMetadataResolver-1-1] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/releases-ee/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-ee-releases.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-releases (https://repository-master.mulesoft.org/nexus/content/repositories/releases-ee/)) WARN 2017-06-06 11:34:48,103 [DefaultMetadataResolver-1-3] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/ci-snapshots/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-ee-snapshots.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-snapshots (https://repository-master.mulesoft.org/nexus/content/repositories/ci-snapshots/)) INFO 2017-06-06 11:34:48,255 [DefaultMetadataResolver-1-2] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml' from https://repository.mulesoft.org/nexus/content/repositories/private/ INFO 2017-06-06 11:34:48,263 [DefaultMetadataResolver-1-0] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml' from https://repository.mulesoft.org/nexus/content/repositories/snapshots/ WARN 2017-06-06 11:34:48,269 [DefaultMetadataResolver-1-1] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/ext-releases/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-ee-thirdparty.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-thirdparty (https://repository-master.mulesoft.org/nexus/content/repositories/ext-releases/)) WARN 2017-06-06 11:34:48,272 [DefaultMetadataResolver-1-3] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/codehaus-snapshots/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-codehaus-plugin-snapshots.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in codehaus-plugin-snapshots (https://repository-master.mulesoft.org/nexus/content/repositories/codehaus-snapshots/)) WARN 2017-06-06 11:34:48,272 [DefaultMetadataResolver-1-1] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'http://maven-facade.ue1.kprod.k8s.prodx.msap.io/api/v1/maven/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-anypoint-exchange.xml' (org.eclipse.aether.transfer.MetadataTransferException: Could not transfer metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml from/to anypoint-exchange (http://maven-facade.ue1.kprod.k8s.prodx.msap.io/api/v1/maven): maven-facade.ue1.kprod.k8s.prodx.msap.io) WARN 2017-06-06 11:34:48,427 [DefaultMetadataResolver-1-2] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'http://dev.modusintegration.com/repositories/releases/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-modus-repository-releases.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in modus-repository-releases (http://dev.modusintegration.com/repositories/releases/)) WARN 2017-06-06 11:34:48,434 [DefaultMetadataResolver-1-0] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'http://dev.modusintegration.com/repositories/snapshots/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-modus-repository-snapshots.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in modus-repository-snapshots (http://dev.modusintegration.com/repositories/snapshots/)) INFO 2017-06-06 11:34:48,438 [DefaultMetadataResolver-1-1] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml' from https://repository.mulesoft.org/snapshots/ WARN 2017-06-06 11:34:48,445 [DefaultMetadataResolver-1-3] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository.mulesoft.org/releases/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mulesoft-releases.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mulesoft-releases (https://repository.mulesoft.org/releases/)) INFO 2017-06-06 11:34:48,602 [DefaultMetadataResolver-1-2] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml' from https://repository.mulesoft.org/nexus/content/repositories/public/ WARN 2017-06-06 11:34:48,626 [DefaultMetadataResolver-1-0] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'http://repo.spring.io/snapshot/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/maven-metadata-spring-snapshot.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-core-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in spring-snapshot (http://repo.spring.io/snapshot/)) INFO 2017-06-06 11:34:48,824 [WrapperListener_start_runner] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/extensions/mule-core-modules-parent/4.0.0-SNAPSHOT/mule-core-modules-parent-4.0.0-20170606.060043-31.pom' from https://repository-master.mulesoft.org/nexus/content/repositories/snapshots/ WARN 2017-06-06 11:34:49,011 [DefaultMetadataResolver-2-1] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/groups/enterprise/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-ee-enterprise.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-enterprise (https://repository-master.mulesoft.org/nexus/content/groups/enterprise/)) WARN 2017-06-06 11:34:49,013 [DefaultMetadataResolver-2-0] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/groups/mule-ee-dependencies/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-ee-dependencies.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-dependencies (https://repository-master.mulesoft.org/nexus/content/groups/mule-ee-dependencies/)) INFO 2017-06-06 11:34:49,017 [DefaultMetadataResolver-2-3] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml' from https://repository-master.mulesoft.org/nexus/content/repositories/snapshots/ WARN 2017-06-06 11:34:49,017 [DefaultMetadataResolver-2-2] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/releases/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-releases.xml' (org.eclipse.aether.transfer.MetadataTransferException: Could not transfer metadata org.mule.extensions:mule-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml from/to mule-releases (https://repository-master.mulesoft.org/nexus/content/repositories/releases/): Unauthorized (401)) WARN 2017-06-06 11:34:49,190 [DefaultMetadataResolver-2-0] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/ci-snapshots/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-ee-snapshots.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-snapshots (https://repository-master.mulesoft.org/nexus/content/repositories/ci-snapshots/)) WARN 2017-06-06 11:34:49,192 [DefaultMetadataResolver-2-1] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/ci-releases/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-ee.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mule-ee (https://repository-master.mulesoft.org/nexus/content/repositories/ci-releases/)) WARN 2017-06-06 11:34:49,193 [DefaultMetadataResolver-2-3] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/releases-ee/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-ee-releases.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-releases (https://repository-master.mulesoft.org/nexus/content/repositories/releases-ee/)) INFO 2017-06-06 11:34:49,249 [DefaultMetadataResolver-2-2] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml' from https://repository.mulesoft.org/nexus/content/repositories/private/ INFO 2017-06-06 11:34:49,363 [DefaultMetadataResolver-2-0] org.mule.maven.client.internal.AetherRepositoryState: Transfer SUCCEEDED for 'org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml' from https://repository.mulesoft.org/nexus/content/repositories/snapshots/ WARN 2017-06-06 11:34:49,365 [DefaultMetadataResolver-2-3] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/codehaus-snapshots/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata-codehaus-plugin-snapshots.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in codehaus-plugin-snapshots (https://repository-master.mulesoft.org/nexus/content/repositories/codehaus-snapshots/)) WARN 2017-06-06 11:34:49,366 [DefaultMetadataResolver-2-1] org.mule.maven.client.internal.AetherRepositoryState: Transfer FAILED for 'https://repository-master.mulesoft.org/nexus/content/repositories/ext-releases/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata.xml <> /usr/mule/apps/smart-test/repository/org/mule/extensions/mule-modules-parent/4.0.0-SNAPSHOT/maven-metadata-mule-ee-thirdparty.xml' (org.eclipse.aether.transfer.MetadataNotFoundException: Could not find metadata org.mule.extensions:mule-modules-parent:4.0.0-SNAPSHOT/maven-metadata.xml in mule-ee-thirdparty (https://repository-master.mulesoft.org/nexus/content/repositories/ext-releases/)) .... {code}""",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12702","06/06/2017 16:20:08",1,"Add the possibility to provide a Charset when consuming a stream from the IOUtils ""In the debugger, when generating a readable payload from an input stream, we take into account the charset configured by the user. We need to add in org.mule.runtime.core.api.util.IOUtils a method to generate a String form a stream providing a java.nio.charset.Charset ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12703","06/06/2017 16:26:29",0,"Expression language does not handle context properties ""The {{p()}} DW function is not working in 4.0 so you are not able to retrieve system properties. Sample flow: Start Mule with {{./bin/mule -M-Dmule.simpleLog=true}} and see the exception: {code:none} WARN 2017-06-06 12:19:41,889 [[MuleRuntime].cpuLight.02] org.mule.runtime.core.el.DefaultExpressionManager: Expression parsing is deprecated, regular evaluations should be used instead. ERROR 2017-06-06 12:19:43,243 [[MuleRuntime].cpuLight.02] org.mule.runtime.core.exception.OnErrorPropagateHandler: ******************************************************************************** Message : """"Script 'p('aRandomProperty') ' has errors: Unable to resolve reference of p. at 1 : 1"""" evaluating expression: """"#[p('aRandomProperty')]"""".. Payload : null Payload Type : null FlowStack : at someFlow(someFlow/processors/0 @ default:null:15) Element : someFlow/processors/0 @ default:null:15 Element XML : -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.runtime.api.el.ExpressionExecutionException: Script 'p('aRandomProperty') ' has errors: Unable to resolve reference of p. at 1 : 1 at org.mule.weave.v2.el.WeaveExpressionLanguage.doEvaluate(WeaveExpressionLanguage.scala:111) at org.mule.weave.v2.el.WeaveExpressionLanguage.evaluate(WeaveExpressionLanguage.scala:79) at org.mule.runtime.core.el.DataWeaveExpressionLanguageAdaptor.lambda$evaluate$3(DataWeaveExpressionLanguageAdaptor.java:131) at org.mule.runtime.core.el.DataWeaveExpressionLanguageAdaptor.sanitizeAndEvaluate(DataWeaveExpressionLanguageAdaptor.java:177) at org.mule.runtime.core.el.DataWeaveExpressionLanguageAdaptor.evaluate(DataWeaveExpressionLanguageAdaptor.java:131) at org.mule.runtime.core.el.ExpressionLanguageAdaptorHandler.evaluate(ExpressionLanguageAdaptorHandler.java:99) at org.mule.runtime.core.el.DefaultExpressionManager.evaluate(DefaultExpressionManager.java:131) at org.mule.runtime.core.el.DefaultExpressionManager.evaluate(DefaultExpressionManager.java:121) at org.mule.runtime.core.el.DefaultExpressionManager.parse(DefaultExpressionManager.java:235) at org.mule.runtime.core.api.processor.LoggerMessageProcessor.log(LoggerMessageProcessor.java:76) at org.mule.runtime.core.api.processor.LoggerMessageProcessor.lambda$process$0(LoggerMessageProcessor.java:62) at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.util.StreamingUtils$1.applyChecked(StreamingUtils.java:51) at org.mule.runtime.core.api.util.StreamingUtils$1.applyChecked(StreamingUtils.java:47) at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.util.StreamingUtils.withCursoredEvent(StreamingUtils.java:71) at org.mule.runtime.core.api.processor.LoggerMessageProcessor.process(LoggerMessageProcessor.java:61) at org.mule.runtime.core.api.processor.Processor.lambda$apply$0(Processor.java:53) at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.rx.Exceptions.lambda$checkedFunction$3(Exceptions.java:87) at org.mule.runtime.core.internal.util.rx.Operators.lambda$nullSafeMap$0(Operators.java:37) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onNext(FluxHandleFuseable.java:141) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxJust$WeakScalarSubscription.request(FluxJust.java:90) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.request(FluxHandleFuseable.java:208) at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:1482) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onSubscribe(FluxOnErrorResume.java:67) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onSubscribe(FluxHandleFuseable.java:126) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxHandleFuseable.subscribe(FluxHandleFuseable.java:64) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onNext(FluxConcatMap.java:242) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerNext(FluxConcatMap.java:272) at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onNext(FluxConcatMap.java:782) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:108) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onNext(FluxHandleFuseable.java:150) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxJust$WeakScalarSubscription.request(FluxJust.java:90) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.request(FluxHandleFuseable.java:208) at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:1482) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onSubscribe(FluxOnErrorResume.java:67) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onSubscribe(FluxHandleFuseable.java:126) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxHandleFuseable.subscribe(FluxHandleFuseable.java:64) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onSubscribe(FluxConcatMap.java:212) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onSubscribe(FluxPeekFuseable.java:164) at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onSubscribe(FluxMapFuseable.java:90) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onSubscribe(FluxPeekFuseable.java:164) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onSubscribe(FluxPeekFuseable.java:164) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:86) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:86) at reactor.core.publisher.FluxMapFuseable.subscribe(FluxMapFuseable.java:63) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:86) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxHandle.subscribe(FluxHandle.java:49) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onNext(FluxConcatMap.java:242) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerNext(FluxConcatMap.java:272) at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onNext(FluxConcatMap.java:782) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:108) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onNext(FluxHandleFuseable.java:150) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxJust$WeakScalarSubscription.request(FluxJust.java:90) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.request(FluxHandleFuseable.java:208) at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:1482) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onSubscribe(FluxOnErrorResume.java:67) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onSubscribe(FluxHandleFuseable.java:126) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxHandleFuseable.subscribe(FluxHandleFuseable.java:64) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onSubscribe(FluxConcatMap.java:212) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onSubscribe(FluxPeekFuseable.java:164) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onSubscribe(FluxPeekFuseable.java:164) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:86) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:86) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onNext(FluxConcatMap.java:236) at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.runBackfused(FluxPublishOn.java:431) at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.run(FluxPublishOn.java:472) at reactor.core.scheduler.ExecutorServiceScheduler$ExecutorServiceSchedulerRunnable.run(ExecutorServiceScheduler.java:325) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.mule.service.scheduler.internal.AbstractRunnableFutureDecorator.doRun(AbstractRunnableFutureDecorator.java:88) at org.mule.service.scheduler.internal.RunnableFutureDecorator.run(RunnableFutureDecorator.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) {code}s"""," WARN 2017-06-06 12:19:41,889 [[MuleRuntime].cpuLight.02] org.mule.runtime.core.el.DefaultExpressionManager: Expression parsing is deprecated, regular evaluations should be used instead. ERROR 2017-06-06 12:19:43,243 [[MuleRuntime].cpuLight.02] org.mule.runtime.core.exception.OnErrorPropagateHandler: ******************************************************************************** Message : """"Script 'p('aRandomProperty') ' has errors: Unable to resolve reference of p. at 1 : 1"""" evaluating expression: """"#[p('aRandomProperty')]"""".. Payload : null Payload Type : null FlowStack : at someFlow(someFlow/processors/0 @ default:null:15) Element : someFlow/processors/0 @ default:null:15 Element XML : -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.runtime.api.el.ExpressionExecutionException: Script 'p('aRandomProperty') ' has errors: Unable to resolve reference of p. at 1 : 1 at org.mule.weave.v2.el.WeaveExpressionLanguage.doEvaluate(WeaveExpressionLanguage.scala:111) at org.mule.weave.v2.el.WeaveExpressionLanguage.evaluate(WeaveExpressionLanguage.scala:79) at org.mule.runtime.core.el.DataWeaveExpressionLanguageAdaptor.lambda$evaluate$3(DataWeaveExpressionLanguageAdaptor.java:131) at org.mule.runtime.core.el.DataWeaveExpressionLanguageAdaptor.sanitizeAndEvaluate(DataWeaveExpressionLanguageAdaptor.java:177) at org.mule.runtime.core.el.DataWeaveExpressionLanguageAdaptor.evaluate(DataWeaveExpressionLanguageAdaptor.java:131) at org.mule.runtime.core.el.ExpressionLanguageAdaptorHandler.evaluate(ExpressionLanguageAdaptorHandler.java:99) at org.mule.runtime.core.el.DefaultExpressionManager.evaluate(DefaultExpressionManager.java:131) at org.mule.runtime.core.el.DefaultExpressionManager.evaluate(DefaultExpressionManager.java:121) at org.mule.runtime.core.el.DefaultExpressionManager.parse(DefaultExpressionManager.java:235) at org.mule.runtime.core.api.processor.LoggerMessageProcessor.log(LoggerMessageProcessor.java:76) at org.mule.runtime.core.api.processor.LoggerMessageProcessor.lambda$process$0(LoggerMessageProcessor.java:62) at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.util.StreamingUtils$1.applyChecked(StreamingUtils.java:51) at org.mule.runtime.core.api.util.StreamingUtils$1.applyChecked(StreamingUtils.java:47) at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.util.StreamingUtils.withCursoredEvent(StreamingUtils.java:71) at org.mule.runtime.core.api.processor.LoggerMessageProcessor.process(LoggerMessageProcessor.java:61) at org.mule.runtime.core.api.processor.Processor.lambda$apply$0(Processor.java:53) at org.mule.runtime.core.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.rx.Exceptions.lambda$checkedFunction$3(Exceptions.java:87) at org.mule.runtime.core.internal.util.rx.Operators.lambda$nullSafeMap$0(Operators.java:37) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onNext(FluxHandleFuseable.java:141) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxJust$WeakScalarSubscription.request(FluxJust.java:90) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.request(FluxHandleFuseable.java:208) at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:1482) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onSubscribe(FluxOnErrorResume.java:67) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onSubscribe(FluxHandleFuseable.java:126) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxHandleFuseable.subscribe(FluxHandleFuseable.java:64) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onNext(FluxConcatMap.java:242) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerNext(FluxConcatMap.java:272) at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onNext(FluxConcatMap.java:782) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:108) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onNext(FluxHandleFuseable.java:150) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxJust$WeakScalarSubscription.request(FluxJust.java:90) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.request(FluxHandleFuseable.java:208) at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:1482) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onSubscribe(FluxOnErrorResume.java:67) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onSubscribe(FluxHandleFuseable.java:126) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxHandleFuseable.subscribe(FluxHandleFuseable.java:64) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onSubscribe(FluxConcatMap.java:212) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onSubscribe(FluxPeekFuseable.java:164) at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onSubscribe(FluxMapFuseable.java:90) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onSubscribe(FluxPeekFuseable.java:164) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onSubscribe(FluxPeekFuseable.java:164) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:86) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:86) at reactor.core.publisher.FluxMapFuseable.subscribe(FluxMapFuseable.java:63) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:86) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxHandle.subscribe(FluxHandle.java:49) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onNext(FluxConcatMap.java:242) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerNext(FluxConcatMap.java:272) at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onNext(FluxConcatMap.java:782) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:108) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onNext(FluxHandleFuseable.java:150) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxJust$WeakScalarSubscription.request(FluxJust.java:90) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.request(FluxHandleFuseable.java:208) at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:1482) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onSubscribe(FluxOnErrorResume.java:67) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onSubscribe(FluxHandleFuseable.java:126) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxHandleFuseable.subscribe(FluxHandleFuseable.java:64) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onSubscribe(FluxConcatMap.java:212) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onSubscribe(FluxPeekFuseable.java:164) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onSubscribe(FluxPeekFuseable.java:164) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:86) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:86) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onNext(FluxConcatMap.java:236) at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.runBackfused(FluxPublishOn.java:431) at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.run(FluxPublishOn.java:472) at reactor.core.scheduler.ExecutorServiceScheduler$ExecutorServiceSchedulerRunnable.run(ExecutorServiceScheduler.java:325) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.mule.service.scheduler.internal.AbstractRunnableFutureDecorator.doRun(AbstractRunnableFutureDecorator.java:88) at org.mule.service.scheduler.internal.RunnableFutureDecorator.run(RunnableFutureDecorator.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12706","06/06/2017 20:57:37",2,"Source errors should not be available in on-error-continue ""Newly introduced sources error types should not be available in on-error-continue handlers since execution cannot be completed successfully. We need to make those configurations impossible.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12708","06/06/2017 22:56:01",1,"ObjectStore connector missing ""clear"" operation ""ObjectStore connector is missing the """"clear"""" operation which is present in the API""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12710","06/07/2017 14:19:50",1,"Provide access to container bootstrap utils to artifacts ""Need to define a module for container bootstrap and provide access to the utilities classes to mule artifacts""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12711","06/07/2017 14:39:03",0,"Provide replacement for sprint import ""The component Spring import will sease to work in Mule 4. There is still a need to import file and other components in such a way. One of the reasons is provide support for MUnit which requires to describe which parts of the application needs to be imported. Bear in mind that the application config files now live in /mule of the application packages and not in the classes folder, though by default those files will not be on the classpath""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12712","06/07/2017 15:20:49",1,"ExclusiveParameters are using field name instead of the alias ""If you take a look at the extension model json, yo will see that the names used for the parameters don't take the alias into account.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12713","06/07/2017 15:33:59",2,"Default Error Handler not consistently initialized ""When calling MuleContext#getDefaultErrorHandler(), some callers properly initialize it and some others (MuleClientFlowConstruct) don't""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12737","06/07/2017 17:50:38",2,"one-liner set-variable returns a different object than declaring output application/java ""one-liner set-variable returns a different object than if output application/java is declared. In this case {code:xml} #[payload] {code} the object returned is not serializable. If instead set-variable is stated like this {code:xml} {code} object is serializable *App details* {code:xml} #[payload] #[syncTimestamp] {code} *Console output* """," #[payload] #[payload] #[syncTimestamp] INFO 2017-06-06 17:48:43,580 [[MuleRuntime].cpuLight.09] org.mule.runtime.core.api.processor.LoggerMessageProcessor: """"Next sync resuming from 2017-06-06 05:48:43"""" ERROR 2017-06-06 17:48:43,618 [[MuleRuntime].cpuLight.09] org.mule.runtime.core.exception.OnErrorPropagateHandler: ******************************************************************************** Message : The value 'org.mule.runtime.core.internal.streaming.bytes.ManagedCursorStreamProvider@6aa23eb4' of type org.mule.runtime.core.internal.streaming.bytes.ManagedCursorStreamProvider could not be transformed to the desired type java.io.Serializable Payload Type : org.mule.runtime.core.internal.streaming.bytes.ManagedCursorStreamProvider FlowStack : at sync-flow(sync-flow/processors/11 @ poll-dbquery-transform-dbwrite:null:196) Element : sync-flow/processors/11 @ poll-dbquery-transform-dbwrite:null:196 Element XML : #[syncTimestamp] -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.runtime.core.api.transformer.TransformerException: The value 'org.mule.runtime.core.internal.streaming.bytes.ManagedCursorStreamProvi ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12723","06/07/2017 21:02:37",0,"Add TransactionStatus to Transaction type in Tooling API ""Need to add this field for when runtime/agent can give us that information""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12724","06/08/2017 03:20:05",2,"Add HTTP client streaming test cases ""Though most HTTP scenarios are tested through the HTTP extension, since it only uses non blocking requests there are currently no blocking tests cases validating the streaming functionality. We need to add them to the service to make sure users will be successful regardless of the blocking/non blocking streaming/memory configuration.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12728","06/08/2017 16:06:36",1,"Fix flaky ConnectorMessageErrorNotificationTestCase ""ConnectorMessageErrorNotificationTestCase is failing locally because of a small timeout, need to increase it to avoid flakiness.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12734","06/08/2017 18:08:40",13,"Dummy implementations for Test Connectivity in core extensions ""- Http: HttpRequesterProvider - Db: DbConnectionProvider, affects all Db connections - File: LocalFileConnectionProvider - Email: AbstractSenderProvider""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12735","06/08/2017 18:28:01",8,"Update FirstSucessful and any other routers to use errorType matchers instead of just failureExpression ""Update FirstSucessful to use errorType matchers instead of just failureExpression""","",0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12741","06/09/2017 14:44:49",8,"Unify different overload errors within a single parent error type ""- back-pressure (flow is slower than producer) - streaming memory - JVM OOM This will allow some source to handle these errors equally if required (HTTP maybe) while allowing other to differentiate between them.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12747","06/09/2017 18:04:35",1,"@Query text does not allow for dynamic values. ""When an operation is @Query, the `@MetadataKeyId String query` text is not evaluating expressions. This is not working only on operations annotated with Query """," #[payload] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12759","06/12/2017 04:14:25",0,"Compilation warnings should be logged with the corresponding level ""It seems we are logging warning using the error log. Logs should be consistent with the severity of the message. If there are no errors or warning, nothing should be logged at all"""," 09-Jun-2017 20:43:17 [ERROR] WARNINGS: NONE 09-Jun-2017 20:43:17 [ERROR] -> [Help 1] ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12762","06/12/2017 15:45:04",0,"Maven client must support offline mode ""Maven client used internally to resolve dependencies, should be able to work offline to avoid downloading artifact and metadata from external repositories. This is useful, for example, when running test (both unit/functional and system) to avoid having local artifacts overridden with newer versions.""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12764","06/12/2017 17:08:22",5,"Document WSC ""Doc it""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12765","06/12/2017 17:09:38",5,"Document File connector ""Doc it""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12766","06/12/2017 18:31:20",2,"Move to Grizzly AHC ""We need to change our dependency of AHC to the Grizzly sponsored one: Not only have they fixed some of our reported issues but it will be the supported artefact from now on. Because of the former, we'll need to remove our custom code to address the issues which includes all changes in https://github.com/mulesoft/mule/pull/4990 and https://github.com/mulesoft/mule/pull/4217."""," org.glassfish.grizzly grizzly-http-client ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12767","06/12/2017 18:41:30",2,"Use DataSense failure instead of returning null on ToolingDataSenseMetadataProvider ""Instead of returnin `null`, return `failure`""","",0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12768","06/12/2017 21:05:53",8,"Message sources need to be able to define how they want the Flow to handle back pressure. ""Currently the way in which a Flow reacts to overload depends on i) source thread ii) processing strategy in use iii) thread pool used by processing strategy because it's logic internal to SchedulerService that determines if/when a source thread should block based on relative thread types. Not all processing strategies start with the scheduling of tasks to a Scheduler and instead a Flow should be able to respond to back-pressure and handle it regardless of logic internal to schedulers. The Flow can either always fail with an OVERLOAD exception on back-pressure, can always WAIT or use one of the two strategies based on the MessageSource. - Always WAIT is not an option because some sources like HTTP, need to fail fast with a 503 response rather than block selector threads. - Always fail with OVERLOAD exception is an option, but it means i) there is overhead associated with creating, throwing and handling the exception and error. ii) the source needs would need to implement it's on retry. - Have the MessageSource or ExtensionMessageSource expose the desired strategy ERROR/WAIT/DROP and the Flow implement this at the point in which the Event is dispatched to the reactor stream avoiding the need to create of catch The signature needed would be"""" ERROR/WAIT/DROP MessageSource.getBackPressureAction()""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12769","06/12/2017 21:07:19",8,"Allow MessageSource back-pressure strategy to be defined by a Extension Source ""Implement SDK support for MULE-12768 Message sources need to be able to define how they want the Flow to handle back pressure.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12773","06/12/2017 21:47:54",1,"Typo on FILE:ILLEGAL_PATH error message ""FILE:ILLEGAL_PATH error message contains a typo. It should read *doesn't exist.* instead of """"doesn't exists."""" """," ******************************************************************************** Message : org.mule.extension.file.common.api.exceptions.IllegalPathException: Path '/Users/hwittemoller/dev/git/mule-uber/mule-ee/distributions/tests/target/servers/PollFromObjectStoreTestCase/mule-enterprise-standalone-4.0.0-SNAPSHOT/apps/poll-object-store/classes/nonexistingfile.json' doesn't exists. Payload : null Payload Type : null FlowStack : at db-load-flow(db-load-flow/processors/1 @ poll-object-store:null:170) Element : db-load-flow/processors/1 @ poll-object-store:null:170 Element XML : ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12770","06/12/2017 22:09:42",8,"Sdk should validate that required parameters can't receive null values ""Sdk should validate that required parameters can't receive null values""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12771","06/12/2017 22:29:57",8,"Parametrize ObjectStoreStoreRetrieveAndRemoveTestCase flows and add negative cases ""ObjectStoreStoreRetrieveAndRemoveTestCase flows need to be parametrized to enable error triggering. Error handling scenarios will involve the following operations * file:read * db:bulk-insert * db:select * os:store ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12775","06/12/2017 23:18:11",1,"Artifact xml serializer not adding the core namespace by default ""When generating the xml of an artifact that does not contain any core processors, the artifact xml serializer is failing to add the core namespace to the xml as well as the schema location. xmlns=""""http://www.mulesoft.org/schema/mule/core"""" http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12776","06/12/2017 23:26:00",1,"JMS degraded 70% in mule4 (dup of PERF-1430) ""see PERF-1430""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12779","06/13/2017 16:00:48",3,"Wrong name is generated in the DSL element name for uppercase words ""When there are uppercase words in the @ParameterGroup name, the generated XML element name is not the right one. Uppercase words are being split instead of being handled as one. Example: """," @ParameterGroup(name = “Ingredient shown in DSL”, showInDsl = true) // Generates ingredient-shown-in-d-s-l // Expected ingredient-shown-in-dsl ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12781","06/13/2017 17:35:05",5,"Review JMS ack modes ""Review JMS ack modes ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12782","06/13/2017 17:42:34",2,"Contention on ExceptionUtils.getCause - Upgrade commons lang to >=3.1 ""Mule currently uses commons lang 2, which has a contention issue doe to an unneeded synchronization on ExceptionUtils.getCause. Use ExceptionUtils from version >=3.1, but keep the current version for backward compatibility (packages are different so that should be no problem).""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12783","06/13/2017 17:57:36",1,"Normalize extensions artifacts names ""All pom names should either be Foo Module or Foo Connector. Not Mule Foo Connector, Foo Extensions or nothing of that sort""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12784","06/13/2017 18:34:25",5,"ObjectType.getFields doesn't return the fields in the order writen in the extension-model.json ""In an extension with subtypes, the org.mule.metadata.api.model.ObjectType.getFields() doesn't return the fields in the order written in the extension-model.json For simple types, this may not be an issue, but if the Object has other objects inside, the order must be exactly the same. Today we cannot check for a model property to determine the order, so we need to use the order in which the fields are returned as the source of truth. Currently there seems to be a difference which may lead to errors when generating the UI and writting down the child elements Check the extension: https://github.com/mulesoft/mule-tooling-mock-connector/tree/mule-4.x/extension-with-subtypes But iterating the fields return first the pages field, and second the id"""," The json of a type is: { """"format"""": """"java"""", """"type"""": """"Object"""", """"annotations"""": { """"typeId"""": """"org.mule.modules.subtypes.model.Magazine"""", """"classInformation"""": { """"hasDefaultConstructor"""": true, """"isInterface"""": false, """"isInstantiable"""": true, """"isAbstract"""": false, """"isFinal"""": false, """"implementedInterfaces"""": [], """"parent"""": """"org.mule.modules.subtypes.model.BasePojo"""", """"genericTypes"""": [] }, """"xmlHints"""": { """"allowInlineDefinition"""": true, """"allowTopLevelDefinition"""": true, """"allowReferences"""": true }, """"typeAlias"""": { """"value"""": """"Magazine"""" } }, """"fields"""": [ { """"key"""": { """"name"""": """"id"""" }, """"model"""": { """"type"""": """"String"""", """"annotations"""": { """"typeId"""": """"java.lang.String"""" } } }, { """"key"""": { """"name"""": """"pages"""" }, """"model"""": { """"type"""": """"Number"""", """"annotations"""": { """"typeId"""": """"java.lang.Integer"""" } } } ] } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12785","06/13/2017 19:05:09",5,"Remove the @DataTypeParameters annotation ""*@DataTypeParameters should be removed* The Mime Type parameters outputMimeType and outputEncoding should be always generated when the return type of an operation is an Object, a StringType or a BinaryType allowing the user to override whatever mimetype is set by mule""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12786","06/13/2017 19:07:01",3,"File/FTP read and list should not receive a MediaType as parameter ""*File/FTP read and list should not receive a MediaType as parameter* The current behavior of *MediaType* is to receive the MediaType of the Payload at the moment of executing the operation, a thing that is wrong for this operations. In case the user want to provide a certain MediaType for the output @DataTypeParameters should be used.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12789","06/13/2017 20:38:10",8,"Implicit config does not instanciate default parameter groups ""When using an implicit config, the parameter groups result in a null value instead of instanciating a """"Nullsafe"""" group with the corresponding default values. In JmsConfig we have But the implicit config created results in: """," /** * Configuration parameters for consuming {@link Message}s from a JMS {@link Queue} or {@link Topic} */ @Expression(NOT_SUPPORTED) @Placement(tab = """"Consumer"""") @ParameterGroup(name = """"Consumer Config"""", showInDsl = true) private JmsConsumerConfig consumerConfig; /** * Configuration parameters for sending {@link Message}s to a JMS {@link Queue} or {@link Topic} */ @Expression(NOT_SUPPORTED) @Placement(tab = """"Producer"""") @ParameterGroup(name = """"Producer Config"""", showInDsl = true) private JmsProducerConfig producerConfig; configInstance = {org.mule.extensions.jms.internal.config.JmsConfig@12362} encoding = null contentType = """"*/*"""" consumerConfig = null producerConfig = null ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12792","06/13/2017 22:07:59",3,"Messaging sources should not expose an ackMode=""NONE"" ""The ackMode 'NONE' has nothing to do with JMS acknowledgement mode as defined by the JMS spec and wasn't used in Mule 3 either. In Mule 4 it is being used to define fire-and-forget behaviour and therefore switch between the 3.x (one-way) behaviour where the JMS MessageListener does not wait for the flow to complete vs. the 4.x (consistent) behaviour where the JMS MessageListener does wait for the flow to complete to ensure that any errors in the Flow, unless they are handled, result in a nack. One of the main goals of work to remove exchange patterns and processing strategies was to remove all implicit, or flag-defined threading or fire-and-forget behaviour so that all sources receive the response from the flow and use it to ack/nack. The only way the user should be able to explicitly perform a fire-and-forget such that the source acks before the flow completes is via the explicit use of . Also if it did make sense to configure this on a source, which it doesn't, this flag should be available in all sources that don't use a response such as file and ftp too, otherwise it's inconsistent. Due to this, this mode should be removed in all messaging connectors where it exists today and documentation as well as performance tests should use .""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12795","06/14/2017 10:38:56",8,"Update JMS caching strategy defaults for decent OOTB performance ""By default JMS session caching is just 1, whereas in Mule 3.8 it is unbounded and as such defined implicitly by the number of worker threads in the Flow. Using a default of just 1 impacts OOTB performance significantly. Also in 3.x cacheConsumers was off by default to avoid consumer leaks with publish-consume and temporary reply queues, yet it is on by default in 4.x. This needs to be tested fully with publish-consume, temp queues and load before changing this.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12798","06/14/2017 16:11:07",2,"Allow parameter groups repeat Display Name ""Allow parameter groups repeat Display Name""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12799","06/14/2017 16:13:25",8,"Move ArtifactDeclaration to a new API ""ArtifactDeclaration should be a Tooling concept, therefore it has to be moved to an API that can be used by Tooling API and removed dependency from Mule Runtime.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12800","06/14/2017 16:30:31",8,"Define an ApplicationProvider instead of Supplier for Tooling Artifacts ""This will allow to notify when an application has been deployed by Tooling (required to resolve an operation against the Runtime) and also allow later to add more specific updates on applications (when a config only has changed, etc). As part of this task the getApplicationId should be removed.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12802","06/14/2017 17:47:21",5,"JMS Publish does not need to use PooledConnectionProvider ""This impact performance because i) it has default pool size of 5 ii) even if you increase size, it's still overhead/contention on pool""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12805","06/14/2017 18:34:41",1,"Upgrade JSCh to 0.1.54 ""Upgrade JSCh to 0.1.54""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12806","06/14/2017 18:48:48",3,"Do not validate required parameters on Datasense resolution ""Do not validate required parameters on Datasense resolution""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12809","06/14/2017 21:36:47",3,"Make MetadataTestCase use LazyMetadataService ""Make MetadataTestCase use LazyMetadataService""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12810","06/15/2017 02:31:04",1,"Upgrade DataSense dependency in tooling to 4.0.0-SNAPSHOT ""Upgrade the dependency to the new version published by datasense""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12815","06/15/2017 16:14:40",5,"Create service to generate XSDs for an application ""Currently extensions include the XSDs in the output JAR, but it won't be the case anymore soon. This is because they are generated when required in ModuleDelegatingEntityResolver. Studio probably requires this so we should provide an API to obtain the XSDs required by an application, generating them if appropriate (in case of extensions).""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12817","06/15/2017 17:31:31",3,"Add LICENCE file to new projects ""Add LICENCE file to connector projects""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12818","06/15/2017 17:50:50",0,"Xml Schema Validator filter changes mimetype ""Same as SE-6155""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12821","06/15/2017 20:18:29",1,"Upgrade abdera-client to 1.1.3 ""Upgrade abdera-client to 1.1.3""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12823","06/15/2017 23:02:23",3,"Wrong DSL definition for boolean parameters ""Wrong DSL definition for boolean parameters""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12826","06/15/2017 23:25:42",8,"ParameterModel should be able to point to another mule elements ""Figure out a way to have parameters which point to component names. Examples: * listenerConfig parameter should point to a http:listener-config * objectStore should point to a os:object-store Although the ExtensionModel should (somehow) say this, at the DSL and Java level, the parameters will be simple Strings.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12828","06/16/2017 13:28:57",2,"The version of Xerces used in endorsed directory performs service provider lookup for each new DocumentBuilder ""This is due to lookup of org.apache.xerces.xni.parser.XMLParserConfiguration for each new DocumentBuilder. The version of xecers in jdk7/8 does not do this, but rather has a fixed implementation. Best way to resolve this until we stop using endorsed version of xerces is to set the system property: -Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeAwareParserConfiguration This has a significant performance impact when using XML expression functions.""","",1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12829","06/16/2017 14:09:36",8,"Allow Top Level Pojos to point to a config ""Support for both static and dynamic pojos""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12831","06/16/2017 15:23:41",8,"Complete ObjectStore connector ""add support for connection providers add support for persisent, ttl, etc support multiple stores support defining stores.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12832","06/16/2017 15:39:04",1,"Avoid generating stacktraces for exceptions when verbose is disabled ""Generating stacktraces for exceptions is expensive in cpu time. Stacktraces should only be filled when there is certainty they are going to be logged/shown somewhere.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12833","06/16/2017 16:28:37",3,"Review WSC fields in configuration ""Review Expresion Supported fields in configuration Config Ref shoud be named requesterConfigRef ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12836","06/16/2017 18:23:31",1,"Fix version in BETA tests """"","org.mule.runtime.module.extension.internal.resources.MulePluginDescriptorGeneratorTestCase.generate org.mule.test.module.extension.connector.PetStoreMissingRequiredParameterInConfigTestCase.fail org.mule.integration.test.tooling.client.ExtensionModelTestCase.loadMuleCoreExtensionModel org.mule.runtime.module.extension.internal.CoreExtensionModelTestCase.consistentWithManifest org.mule.runtime.module.extension.internal.loader.java.JavaDeclarationDelegateTestCase.describeTestModule org.mule.runtime.module.extension.internal.loader.java.JavaDeclarationDelegateTestCase.heisenbergPointer org.mule.runtime.module.extension.internal.loader.java.JavaDeclarationDelegateTestCase.heisenbergPointerPlusExternalConfig org.mule.runtime.module.extension.internal.resources.manifest.ExtensionManifestGeneratorTestCase.generate",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12844","06/16/2017 18:30:07",2,"Embedded container cannot delete folder when stopping app in Windows ""When stopping the embedded container, it tries to perform a deleteTree in the container base folder. In Windows, the deletion is not successful, so the next time a container is started it cannot create the domains/default folder. This causes, for example, that MUnit cannot run two consecutive suites. An example can be tested in the org.mule.runtime.module.embedded.EmbeddedContainerTestCase. A test for this could be something like: In JUnit it might work due to the creation of a temporary folder, but if one changes the containerBaseFolder to another location (for example inside the project) the issue can be reproduced."""," public void twoApplicationWithConnector() throws Exception { doWithinApplication(getFolderForApplication(""""http-echo""""), port -> { try { String httpBody = """"test-message""""; HttpResponse response = post(format(""""http://localhost:%s/"""", port)).body(httpBody).asString(); assertThat(response.getBody(), is(httpBody)); } catch (UnirestException e) { throw new RuntimeException(e); } }, emptyMap()); doWithinApplication(getFolderForApplication(""""http-echo""""), port -> { try { String httpBody = """"test-message""""; HttpResponse response = post(format(""""http://localhost:%s/"""", port)).body(httpBody).asString(); assertThat(response.getBody(), is(httpBody)); } catch (UnirestException e) { throw new RuntimeException(e); } }, emptyMap()); } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12849","06/18/2017 14:37:32",1,"Add @threadSafe to extension-maven-plugin mojos ""Ensure the mojos of the extension plugin are thread safe and annotate them to avoid the warnings when doing parallelmaven builds.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12850","06/18/2017 14:43:32",1,"Connectors point to the wrong version of their parent pom ""Currently, connectors are pointing to as the parent pom, but the version in https://github.com/mulesoft/mule-core-modules-parent/blob/master/pom.xml#L15 is 1.0.0-SNAPSHOT"""," org.mule.extensions mule-core-modules-parent 4.0.0-SNAPSHOT ",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12856","06/19/2017 12:28:38",13,"Implement Parameters Options Resolver in SDK's Side ""*Implement Parameters Options Resolver in SDK's Side* This implies: * Create proper annotations * Create proper interfaces * Create mechanism (reuse the ones in Metadata) no execute the resolving. * Expose this mechanism through ExtensionComponent for Operations and sources and in the same way as {{ConfigurationProviderMetadataAdapter}} does for Configs and Conn Providers""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12857","06/19/2017 12:33:03",8,"Implement Parameters Options Resolver in Mule's Side ""*Implement Parameters Options Resolver in Mule's Side* This implies: * The creation of a {{Parameter Options Resolver Service}} (similar to the metadata one) ** Take care about the lazy version ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12858","06/19/2017 12:34:22",8,"Implement Parameter Options Resolver in Tooling Client's Side ""Implement Parameter Options Resolver in Tooling Client's Side Whatever is done for Metadata""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12862","06/19/2017 17:45:03",3,"Communicate Nullsafe defaultImplementation in the ExtensionModel ""Communicate Nullsafe defaultImplementation in the ExtensionModel""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12863","06/19/2017 18:12:45",3,"WS Consumer errors are hidden in the stacktrace ""When WS consumer throws a connectivity testing error, you need to search the stacktrace for the actual cause of the error, instead of seeing the error in the first error message description. In the following example, the real cause of the error is: """"The provided WSDL [https://graphical.weather.gov/xml/DWMLgen/wsdl/ndfdXML.wsdl] is RPC style, RPC WSDLs are not supported"""" {code:none} org.mule.runtime.api.exception.MuleRuntimeException: java.lang.RuntimeException: org.mule.runtime.api.lifecycle.LifecycleException: Could not perform connectivity testing for config ‘Web_Service_Consumer_Config’ org.mule.runtime.api.exception.MuleRuntimeException: java.lang.RuntimeException: org.mule.runtime.api.lifecycle.LifecycleException: Could not perform connectivity testing for config ‘Web_Service_Consumer_Config’ at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:852) at org.mule.runtime.config.spring.LazyMuleArtifactContext.initializeComponent(LazyMuleArtifactContext.java:121) at org.mule.runtime.config.spring.LazyMetadataService.initializeComponent(LazyMetadataService.java:121) at org.mule.runtime.config.spring.LazyMetadataService.getMetadataKeys(LazyMetadataService.java:52) at com.mulesoft.agent.services.metadata.MuleAgentMetadataService.lambda$getMetadataKeys$0(MuleAgentMetadataService.java:55) at com.mulesoft.agent.services.metadata.MuleAgentMetadataService.withMetadataService(MuleAgentMetadataService.java:126) at com.mulesoft.agent.services.metadata.MuleAgentMetadataService.getMetadataKeys(MuleAgentMetadataService.java:55) at com.mulesoft.agent.external.handlers.metadata.MetadataRequestHandler.lambda$getMetadataKeys$0(MetadataRequestHandler.java:121) at com.mulesoft.agent.util.ResponseHelper.response(ResponseHelper.java:88) at com.mulesoft.agent.external.handlers.metadata.MetadataRequestHandler.getMetadataKeys(MetadataRequestHandler.java:119) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171) at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:152) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104) at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:387) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:331) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:103) at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:267) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:297) at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:254) at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1028) at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:372) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:381) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:344) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:221) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1515) at com.mulesoft.agent.rest.RequestLoggingFilter.doFilter(RequestLoggingFilter.java:95) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:519) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:138) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:564) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:213) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1097) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:448) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:175) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1031) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:446) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:271) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:246) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.RuntimeException: org.mule.runtime.api.lifecycle.LifecycleException: Could not perform connectivity testing for config ‘Web_Service_Consumer_Config’ at org.mule.runtime.config.spring.LazyMuleArtifactContext.applyLifecycle(LazyMuleArtifactContext.java:100) at org.mule.runtime.config.spring.LazyMuleArtifactContext.createComponents(LazyMuleArtifactContext.java:80) at org.mule.runtime.config.spring.LazyMuleArtifactContext.lambda$initializeComponent$0(LazyMuleArtifactContext.java:129) at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:848) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) ... 55 more Caused by: org.mule.runtime.api.lifecycle.LifecycleException: Could not perform connectivity testing for config ‘Web_Service_Consumer_Config’ at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:143) at org.mule.runtime.core.lifecycle.DefaultLifecycleManager.fireStartPhase(DefaultLifecycleManager.java:59) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.lambda$start$4(LifecycleAwareConfigurationProvider.java:105) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.start(LifecycleAwareConfigurationProvider.java:104) at org.mule.runtime.core.api.lifecycle.LifecycleUtils.startIfNeeded(LifecycleUtils.java:189) at org.mule.runtime.config.spring.LazyMuleArtifactContext.applyLifecycle(LazyMuleArtifactContext.java:98) ... 62 more Caused by: org.mule.runtime.core.api.DefaultMuleException: Could not perform connectivity testing for config ‘Web_Service_Consumer_Config’ at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.testConnectivity(LifecycleAwareConfigurationInstance.java:217) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.start(LifecycleAwareConfigurationInstance.java:164) at org.mule.runtime.core.api.lifecycle.LifecycleUtils.startIfNeeded(LifecycleUtils.java:189) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.startConfig(LifecycleAwareConfigurationProvider.java:189) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.lambda$null$3(LifecycleAwareConfigurationProvider.java:107) at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ... 69 more Caused by: org.mule.runtime.core.retry.RetryPolicyExhaustedException: Connectivity test failed for config ‘Web_Service_Consumer_Config’ at org.mule.runtime.core.retry.policies.AbstractPolicyTemplate.execute(AbstractPolicyTemplate.java:83) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.testConnectivity(LifecycleAwareConfigurationInstance.java:215) ... 74 more Caused by: org.mule.runtime.api.connection.ConnectionException: Connectivity test failed for config ‘Web_Service_Consumer_Config’ at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance$1.doWork(LifecycleAwareConfigurationInstance.java:193) at org.mule.runtime.core.retry.policies.AbstractPolicyTemplate.execute(AbstractPolicyTemplate.java:57) ... 75 more Caused by: org.mule.runtime.api.connection.ConnectionException: The provided WSDL [https://graphical.weather.gov/xml/DWMLgen/wsdl/ndfdXML.wsdl] is RPC style, RPC WSDLs are not supported at org.mule.service.soap.client.SoapCxfClientFactory.getIntrospecter(SoapCxfClientFactory.java:60) at org.mule.service.soap.client.SoapCxfClientFactory.create(SoapCxfClientFactory.java:38) at org.mule.extension.ws.internal.connection.SoapClientConnectionProvider.connect(SoapClientConnectionProvider.java:135) at org.mule.extension.ws.internal.connection.SoapClientConnectionProvider.connect(SoapClientConnectionProvider.java:48) at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:59) at org.mule.runtime.core.internal.connection.ErrorTypeHandlerConnectionProviderWrapper.connect(ErrorTypeHandlerConnectionProviderWrapper.java:60) at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:59) at org.mule.runtime.core.internal.connection.LifecycleAwareConnectionProviderWrapper.connect(LifecycleAwareConnectionProviderWrapper.java:61) at org.mule.runtime.core.internal.connection.CachedConnectionHandler.createConnection(CachedConnectionHandler.java:95) at org.mule.runtime.core.internal.connection.CachedConnectionHandler.getConnection(CachedConnectionHandler.java:86) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:163) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.lambda$testConnectivity$1(DefaultConnectionManager.java:146) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.doTestConnectivity(DefaultConnectionManager.java:153) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:129) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance$1.doWork(LifecycleAwareConfigurationInstance.java:188) ... 76 more org.mule.tooling.ui.modules.core.metadata.notifications.DataSenseJobNotificationPopup$MoreInfoSelectionAdapter.widgetSelected(DataSenseJobNotificationPopup.java:232) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256) org.eclipse.swt.widgets.Widget.sendEvent_aroundBody2(Widget.java:1501) org.eclipse.swt.widgets.Widget$AjcClosure3.run(Widget.java:1) org.eclipse.rcptt.tesla.recording.aspects.RecordingAspect.ajc$around$org_eclipse_rcptt_tesla_recording_aspects_RecordingAspect$2$2f127892proceed(RecordingAspect.aj:94) org.eclipse.rcptt.tesla.recording.aspects.RecordingAspect.ajc$around$org_eclipse_rcptt_tesla_recording_aspects_RecordingAspect$2$2f127892(RecordingAspect.aj:118) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501) org.eclipse.swt.widgets.Widget.sendEvent_aroundBody4(Widget.java:1524) org.eclipse.swt.widgets.Widget$AjcClosure5.run(Widget.java:1) org.eclipse.rcptt.tesla.recording.aspects.RecordingAspect.ajc$around$org_eclipse_rcptt_tesla_recording_aspects_RecordingAspect$1$bd9fb3e7proceed(RecordingAspect.aj:39) org.eclipse.rcptt.tesla.recording.aspects.RecordingAspect.ajc$around$org_eclipse_rcptt_tesla_recording_aspects_RecordingAspect$1$bd9fb3e7(RecordingAspect.aj:82) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1513) org.eclipse.swt.widgets.Widget.sendSelectionEvent_aroundBody10(Widget.java:1574) org.eclipse.swt.widgets.Widget$AjcClosure11.run(Widget.java:1) org.eclipse.rcptt.tesla.recording.aspects.RecordingAspect.ajc$around$org_eclipse_rcptt_tesla_recording_aspects_RecordingAspect$10$4cdd93e9proceed(RecordingAspect.aj:256) org.eclipse.rcptt.tesla.recording.aspects.RecordingAspect.ajc$around$org_eclipse_rcptt_tesla_recording_aspects_RecordingAspect$10$4cdd93e9(RecordingAspect.aj:277) org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1568) org.eclipse.swt.widgets.Link.textView_clickOnLink_atIndex(Link.java:793) org.eclipse.swt.widgets.Display.windowProc_aroundBody28(Display.java:6051) org.eclipse.swt.widgets.Display$AjcClosure29.run(Display.java:1) org.eclipse.rcptt.tesla.swt.aspects.EventFilterAspect.ajc$around$org_eclipse_rcptt_tesla_swt_aspects_EventFilterAspect$1$602baf3eproceed(EventFilterAspect.aj:17) org.eclipse.rcptt.tesla.swt.aspects.EventFilterAspect.ajc$around$org_eclipse_rcptt_tesla_swt_aspects_EventFilterAspect$1$602baf3e(EventFilterAspect.aj:19) org.eclipse.swt.widgets.Display.windowProc(Display.java:6038) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1135) org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1127) org.eclipse.swt.widgets.Control.mouseDown(Control.java:2624) org.eclipse.swt.widgets.Display.windowProc_aroundBody24(Display.java:5733) org.eclipse.swt.widgets.Display$AjcClosure25.run(Display.java:1) org.eclipse.rcptt.tesla.swt.aspects.EventFilterAspect.ajc$around$org_eclipse_rcptt_tesla_swt_aspects_EventFilterAspect$1$602baf3eproceed(EventFilterAspect.aj:17) org.eclipse.rcptt.tesla.swt.aspects.EventFilterAspect.ajc$around$org_eclipse_rcptt_tesla_swt_aspects_EventFilterAspect$1$602baf3e(EventFilterAspect.aj:19) org.eclipse.swt.widgets.Display.windowProc(Display.java:5668) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2140) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2402) org.eclipse.swt.widgets.Display.windowProc_aroundBody24(Display.java:5797) org.eclipse.swt.widgets.Display$AjcClosure25.run(Display.java:1) org.eclipse.rcptt.tesla.swt.aspects.EventFilterAspect.ajc$around$org_eclipse_rcptt_tesla_swt_aspects_EventFilterAspect$1$602baf3eproceed(EventFilterAspect.aj:17) org.eclipse.rcptt.tesla.swt.aspects.EventFilterAspect.ajc$around$org_eclipse_rcptt_tesla_swt_aspects_EventFilterAspect$1$602baf3e(EventFilterAspect.aj:19) org.eclipse.swt.widgets.Display.windowProc(Display.java:5668) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5226) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5375) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3703) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:498) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) org.eclipse.equinox.launcher.Main.run(Main.java:1519) org.eclipse.equinox.launcher.Main.main(Main.java:1492) {code}"""," org.mule.runtime.api.exception.MuleRuntimeException: java.lang.RuntimeException: org.mule.runtime.api.lifecycle.LifecycleException: Could not perform connectivity testing for config ‘Web_Service_Consumer_Config’ org.mule.runtime.api.exception.MuleRuntimeException: java.lang.RuntimeException: org.mule.runtime.api.lifecycle.LifecycleException: Could not perform connectivity testing for config ‘Web_Service_Consumer_Config’ at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:852) at org.mule.runtime.config.spring.LazyMuleArtifactContext.initializeComponent(LazyMuleArtifactContext.java:121) at org.mule.runtime.config.spring.LazyMetadataService.initializeComponent(LazyMetadataService.java:121) at org.mule.runtime.config.spring.LazyMetadataService.getMetadataKeys(LazyMetadataService.java:52) at com.mulesoft.agent.services.metadata.MuleAgentMetadataService.lambda$getMetadataKeys$0(MuleAgentMetadataService.java:55) at com.mulesoft.agent.services.metadata.MuleAgentMetadataService.withMetadataService(MuleAgentMetadataService.java:126) at com.mulesoft.agent.services.metadata.MuleAgentMetadataService.getMetadataKeys(MuleAgentMetadataService.java:55) at com.mulesoft.agent.external.handlers.metadata.MetadataRequestHandler.lambda$getMetadataKeys$0(MetadataRequestHandler.java:121) at com.mulesoft.agent.util.ResponseHelper.response(ResponseHelper.java:88) at com.mulesoft.agent.external.handlers.metadata.MetadataRequestHandler.getMetadataKeys(MetadataRequestHandler.java:119) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171) at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:152) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104) at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:387) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:331) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:103) at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:267) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:297) at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:254) at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1028) at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:372) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:381) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:344) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:221) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1515) at com.mulesoft.agent.rest.RequestLoggingFilter.doFilter(RequestLoggingFilter.java:95) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:519) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:138) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:564) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:213) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1097) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:448) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:175) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1031) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:446) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:271) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:246) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.RuntimeException: org.mule.runtime.api.lifecycle.LifecycleException: Could not perform connectivity testing for config ‘Web_Service_Consumer_Config’ at org.mule.runtime.config.spring.LazyMuleArtifactContext.applyLifecycle(LazyMuleArtifactContext.java:100) at org.mule.runtime.config.spring.LazyMuleArtifactContext.createComponents(LazyMuleArtifactContext.java:80) at org.mule.runtime.config.spring.LazyMuleArtifactContext.lambda$initializeComponent$0(LazyMuleArtifactContext.java:129) at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:848) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) ... 55 more Caused by: org.mule.runtime.api.lifecycle.LifecycleException: Could not perform connectivity testing for config ‘Web_Service_Consumer_Config’ at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:143) at org.mule.runtime.core.lifecycle.DefaultLifecycleManager.fireStartPhase(DefaultLifecycleManager.java:59) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.lambda$start$4(LifecycleAwareConfigurationProvider.java:105) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.start(LifecycleAwareConfigurationProvider.java:104) at org.mule.runtime.core.api.lifecycle.LifecycleUtils.startIfNeeded(LifecycleUtils.java:189) at org.mule.runtime.config.spring.LazyMuleArtifactContext.applyLifecycle(LazyMuleArtifactContext.java:98) ... 62 more Caused by: org.mule.runtime.core.api.DefaultMuleException: Could not perform connectivity testing for config ‘Web_Service_Consumer_Config’ at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.testConnectivity(LifecycleAwareConfigurationInstance.java:217) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.start(LifecycleAwareConfigurationInstance.java:164) at org.mule.runtime.core.api.lifecycle.LifecycleUtils.startIfNeeded(LifecycleUtils.java:189) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.startConfig(LifecycleAwareConfigurationProvider.java:189) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.lambda$null$3(LifecycleAwareConfigurationProvider.java:107) at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ... 69 more Caused by: org.mule.runtime.core.retry.RetryPolicyExhaustedException: Connectivity test failed for config ‘Web_Service_Consumer_Config’ at org.mule.runtime.core.retry.policies.AbstractPolicyTemplate.execute(AbstractPolicyTemplate.java:83) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.testConnectivity(LifecycleAwareConfigurationInstance.java:215) ... 74 more Caused by: org.mule.runtime.api.connection.ConnectionException: Connectivity test failed for config ‘Web_Service_Consumer_Config’ at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance$1.doWork(LifecycleAwareConfigurationInstance.java:193) at org.mule.runtime.core.retry.policies.AbstractPolicyTemplate.execute(AbstractPolicyTemplate.java:57) ... 75 more Caused by: org.mule.runtime.api.connection.ConnectionException: The provided WSDL [https://graphical.weather.gov/xml/DWMLgen/wsdl/ndfdXML.wsdl] is RPC style, RPC WSDLs are not supported at org.mule.service.soap.client.SoapCxfClientFactory.getIntrospecter(SoapCxfClientFactory.java:60) at org.mule.service.soap.client.SoapCxfClientFactory.create(SoapCxfClientFactory.java:38) at org.mule.extension.ws.internal.connection.SoapClientConnectionProvider.connect(SoapClientConnectionProvider.java:135) at org.mule.extension.ws.internal.connection.SoapClientConnectionProvider.connect(SoapClientConnectionProvider.java:48) at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:59) at org.mule.runtime.core.internal.connection.ErrorTypeHandlerConnectionProviderWrapper.connect(ErrorTypeHandlerConnectionProviderWrapper.java:60) at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:59) at org.mule.runtime.core.internal.connection.LifecycleAwareConnectionProviderWrapper.connect(LifecycleAwareConnectionProviderWrapper.java:61) at org.mule.runtime.core.internal.connection.CachedConnectionHandler.createConnection(CachedConnectionHandler.java:95) at org.mule.runtime.core.internal.connection.CachedConnectionHandler.getConnection(CachedConnectionHandler.java:86) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:163) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.lambda$testConnectivity$1(DefaultConnectionManager.java:146) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.doTestConnectivity(DefaultConnectionManager.java:153) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:129) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance$1.doWork(LifecycleAwareConfigurationInstance.java:188) ... 76 more org.mule.tooling.ui.modules.core.metadata.notifications.DataSenseJobNotificationPopup$MoreInfoSelectionAdapter.widgetSelected(DataSenseJobNotificationPopup.java:232) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256) org.eclipse.swt.widgets.Widget.sendEvent_aroundBody2(Widget.java:1501) org.eclipse.swt.widgets.Widget$AjcClosure3.run(Widget.java:1) org.eclipse.rcptt.tesla.recording.aspects.RecordingAspect.ajc$around$org_eclipse_rcptt_tesla_recording_aspects_RecordingAspect$2$2f127892proceed(RecordingAspect.aj:94) org.eclipse.rcptt.tesla.recording.aspects.RecordingAspect.ajc$around$org_eclipse_rcptt_tesla_recording_aspects_RecordingAspect$2$2f127892(RecordingAspect.aj:118) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501) org.eclipse.swt.widgets.Widget.sendEvent_aroundBody4(Widget.java:1524) org.eclipse.swt.widgets.Widget$AjcClosure5.run(Widget.java:1) org.eclipse.rcptt.tesla.recording.aspects.RecordingAspect.ajc$around$org_eclipse_rcptt_tesla_recording_aspects_RecordingAspect$1$bd9fb3e7proceed(RecordingAspect.aj:39) org.eclipse.rcptt.tesla.recording.aspects.RecordingAspect.ajc$around$org_eclipse_rcptt_tesla_recording_aspects_RecordingAspect$1$bd9fb3e7(RecordingAspect.aj:82) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1513) org.eclipse.swt.widgets.Widget.sendSelectionEvent_aroundBody10(Widget.java:1574) org.eclipse.swt.widgets.Widget$AjcClosure11.run(Widget.java:1) org.eclipse.rcptt.tesla.recording.aspects.RecordingAspect.ajc$around$org_eclipse_rcptt_tesla_recording_aspects_RecordingAspect$10$4cdd93e9proceed(RecordingAspect.aj:256) org.eclipse.rcptt.tesla.recording.aspects.RecordingAspect.ajc$around$org_eclipse_rcptt_tesla_recording_aspects_RecordingAspect$10$4cdd93e9(RecordingAspect.aj:277) org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1568) org.eclipse.swt.widgets.Link.textView_clickOnLink_atIndex(Link.java:793) org.eclipse.swt.widgets.Display.windowProc_aroundBody28(Display.java:6051) org.eclipse.swt.widgets.Display$AjcClosure29.run(Display.java:1) org.eclipse.rcptt.tesla.swt.aspects.EventFilterAspect.ajc$around$org_eclipse_rcptt_tesla_swt_aspects_EventFilterAspect$1$602baf3eproceed(EventFilterAspect.aj:17) org.eclipse.rcptt.tesla.swt.aspects.EventFilterAspect.ajc$around$org_eclipse_rcptt_tesla_swt_aspects_EventFilterAspect$1$602baf3e(EventFilterAspect.aj:19) org.eclipse.swt.widgets.Display.windowProc(Display.java:6038) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1135) org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1127) org.eclipse.swt.widgets.Control.mouseDown(Control.java:2624) org.eclipse.swt.widgets.Display.windowProc_aroundBody24(Display.java:5733) org.eclipse.swt.widgets.Display$AjcClosure25.run(Display.java:1) org.eclipse.rcptt.tesla.swt.aspects.EventFilterAspect.ajc$around$org_eclipse_rcptt_tesla_swt_aspects_EventFilterAspect$1$602baf3eproceed(EventFilterAspect.aj:17) org.eclipse.rcptt.tesla.swt.aspects.EventFilterAspect.ajc$around$org_eclipse_rcptt_tesla_swt_aspects_EventFilterAspect$1$602baf3e(EventFilterAspect.aj:19) org.eclipse.swt.widgets.Display.windowProc(Display.java:5668) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2140) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2402) org.eclipse.swt.widgets.Display.windowProc_aroundBody24(Display.java:5797) org.eclipse.swt.widgets.Display$AjcClosure25.run(Display.java:1) org.eclipse.rcptt.tesla.swt.aspects.EventFilterAspect.ajc$around$org_eclipse_rcptt_tesla_swt_aspects_EventFilterAspect$1$602baf3eproceed(EventFilterAspect.aj:17) org.eclipse.rcptt.tesla.swt.aspects.EventFilterAspect.ajc$around$org_eclipse_rcptt_tesla_swt_aspects_EventFilterAspect$1$602baf3e(EventFilterAspect.aj:19) org.eclipse.swt.widgets.Display.windowProc(Display.java:5668) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5226) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5375) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3703) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:498) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) org.eclipse.equinox.launcher.Main.run(Main.java:1519) org.eclipse.equinox.launcher.Main.main(Main.java:1492) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12866","06/19/2017 21:29:23",1,"HTTP Stream Response: remove switch ""HTTP Stream Response: make stream response false by default HTTP Request - http stream response currently is true by default make it false by default ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12868","06/19/2017 22:09:41",5,"DslElementModel should communicate default group values ""DslElementModel should communicate default group values""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12869","06/19/2017 22:35:53",5,"Failure to run SOAP-based apps: 'basic-connection' does not have an associated Bean Definition Parser ""h6. Steps to reproduce * Create a Mule app containing a *SOAP connector: either Workday or ServiceNow*. * Deploy it in Studio 7 or a 4.x Standalone Runtime (SNAPSHOT or BETA). * The deploy fails with the following exception: """," ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Failed to deploy artifact 'workday', see below + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ org.mule.runtime.deployment.model.api.DeploymentException: Failed to deploy artifact [workday] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:33) ~[mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployArtifact(DefaultArchiveDeployer.java:272) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployPackagedArtifact(DefaultArchiveDeployer.java:154) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployPackagedArtifact(DefaultArchiveDeployer.java:226) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployPackagedArtifact(DefaultArchiveDeployer.java:75) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployPackagedArtifact(DefaultArchiveDeployer.java:40) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher.deployPackedApps(DeploymentDirectoryWatcher.java:236) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher.start(DeploymentDirectoryWatcher.java:145) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.MuleDeploymentService.start(MuleDeploymentService.java:133) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.launcher.MuleContainer.start(MuleContainer.java:196) [mule-module-launcher-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_131] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_131] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_131] at org.mule.runtime.module.reboot.internal.MuleContainerWrapper.start(MuleContainerWrapper.java:49) [mule-module-boot-ee-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4242) [wrapper-3.5.29.jar:3.5.29] Caused by: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.deployment.model.api.DeploymentInitException: BeanDefinitionParsingException: Configuration problem: The element 'basic-connection' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/workday present on the classpath? Offending resource: URL [file:/home/corar/dev/ide/AnypointStudio/plugins/org.mule.tooling.server.4.0.0.ee_7.0.0.201706152223/mule/apps/workday/mule/mule-config.xml] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:852) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:110) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:66) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] ... 15 more Caused by: org.mule.runtime.deployment.model.api.DeploymentInitException: BeanDefinitionParsingException: Configuration problem: The element 'basic-connection' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/workday present on the classpath? Offending resource: URL [file:/home/corar/dev/ide/AnypointStudio/plugins/org.mule.tooling.server.4.0.0.ee_7.0.0.201706152223/mule/apps/workday/mule/mule-config.xml] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.doInit(DefaultMuleApplication.java:201) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.init(DefaultMuleApplication.java:167) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:848) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:110) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:66) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] ... 15 more Caused by: org.mule.runtime.core.api.config.ConfigurationException: Configuration problem: The element 'basic-connection' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/workday present on the classpath? Offending resource: URL [file:/home/corar/dev/ide/AnypointStudio/plugins/org.mule.tooling.server.4.0.0.ee_7.0.0.201706152223/mule/apps/workday/mule/mule-config.xml] (org.mule.runtime.api.lifecycle.InitialisationException) at org.mule.runtime.module.deployment.impl.internal.artifact.ArtifactContextBuilder.lambda$build$1(ArtifactContextBuilder.java:399) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.ArtifactContextBuilder.build(ArtifactContextBuilder.java:329) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.doInit(DefaultMuleApplication.java:194) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.init(DefaultMuleApplication.java:167) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:848) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:110) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:66) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] ... 15 more Caused by: org.mule.runtime.api.lifecycle.InitialisationException: Configuration problem: The element 'basic-connection' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/workday present on the classpath? Offending resource: URL [file:/home/corar/dev/ide/AnypointStudio/plugins/org.mule.tooling.server.4.0.0.ee_7.0.0.201706152223/mule/apps/workday/mule/mule-config.xml] at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:93) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:49) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:45) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryBrokerLifecycleManager.fireInitialisePhase(RegistryBrokerLifecycleManager.java:54) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker.initialise(AbstractRegistryBroker.java:45) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:121) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:68) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:65) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:57) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.DefaultMuleContext.initialise(DefaultMuleContext.java:329) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:220) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:82) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.ArtifactContextBuilder.lambda$build$1(ArtifactContextBuilder.java:396) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.ArtifactContextBuilder.build(ArtifactContextBuilder.java:329) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.doInit(DefaultMuleApplication.java:194) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.init(DefaultMuleApplication.java:167) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:848) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:110) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:66) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] ... 15 more Caused by: org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: The element 'basic-connection' does not have an associated Bean Definition Parser. Is the module or extension associated with http://www.mulesoft.org/schema/mule/workday present on the classpath? Offending resource: URL [file:/home/corar/dev/ide/AnypointStudio/plugins/org.mule.tooling.server.4.0.0.ee_7.0.0.201706152223/mule/apps/workday/mule/mule-config.xml] at org.springframework.beans.factory.parsing.FailFastProblemReporter.fatal(FailFastProblemReporter.java:60) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MissingParserProblemReporter.fatal(MissingParserProblemReporter.java:27) ~[mule-module-spring-config-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.springframework.beans.factory.parsing.ReaderContext.fatal(ReaderContext.java:68) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.parsing.ReaderContext.fatal(ReaderContext.java:55) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.NamespaceHandlerSupport.findParserForElement(NamespaceHandlerSupport.java:85) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:74) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleHierarchicalBeanDefinitionParserDelegate.parseCustomElement(MuleHierarchicalBeanDefinitionParserDelegate.java:206) ~[mule-module-spring-config-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.config.spring.MuleHierarchicalBeanDefinitionParserDelegate.parseDefinitionOrReference(MuleHierarchicalBeanDefinitionParserDelegate.java:133) ~[mule-module-spring-config-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.config.spring.MuleHierarchicalBeanDefinitionParserDelegate.lambda$parseCustomElement$1(MuleHierarchicalBeanDefinitionParserDelegate.java:191) ~[mule-module-spring-config-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.config.spring.dsl.spring.BeanDefinitionFactory.resolveComponentRecursively(BeanDefinitionFactory.java:165) ~[mule-module-spring-config-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.config.spring.MuleHierarchicalBeanDefinitionParserDelegate.parseCustomElement(MuleHierarchicalBeanDefinitionParserDelegate.java:162) ~[mule-module-spring-config-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.config.spring.MuleHierarchicalBeanDefinitionParserDelegate.parseCustomElement(MuleHierarchicalBeanDefinitionParserDelegate.java:258) ~[mule-module-spring-config-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1417) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:180) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleBeanDefinitionDocumentReader.parseBeanDefinitions(MuleBeanDefinitionDocumentReader.java:77) ~[mule-module-spring-config-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:144) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:100) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:510) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:392) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) ~[spring-beans-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.MuleArtifactContext.createInitialApplicationComponents(MuleArtifactContext.java:332) ~[mule-module-spring-config-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.config.spring.MuleArtifactContext.loadBeanDefinitions(MuleArtifactContext.java:317) ~[mule-module-spring-config-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129) ~[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:541) ~[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:452) ~[spring-context-4.1.9.RELEASE.jar:4.1.9.RELEASE] at org.mule.runtime.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:113) ~[mule-module-spring-config-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistry.initialise(AbstractRegistry.java:89) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:49) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker$1.onTransition(AbstractRegistryBroker.java:45) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.lifecycle.RegistryBrokerLifecycleManager.fireInitialisePhase(RegistryBrokerLifecycleManager.java:54) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.registry.AbstractRegistryBroker.initialise(AbstractRegistryBroker.java:45) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:121) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:68) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:65) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:57) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.DefaultMuleContext.initialise(DefaultMuleContext.java:329) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:220) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:82) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.ArtifactContextBuilder.lambda$build$1(ArtifactContextBuilder.java:396) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.ArtifactContextBuilder.build(ArtifactContextBuilder.java:329) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.doInit(DefaultMuleApplication.java:194) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.init(DefaultMuleApplication.java:167) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:848) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:110) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:66) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] ... 15 more INFO 2017-06-19 18:19:07,883 [WrapperListener_start_runner] org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Mule is up and kicking (every 5000ms) + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ INFO 2017-06-19 18:19:07,892 [WrapperListener_start_runner] org.eclipse.jetty.server.ServerConnector: Started ServerConnector@7558108d{HTTP/1.1}{0.0.0.0:40731} INFO 2017-06-19 18:19:07,894 [WrapperListener_start_runner] org.mule.runtime.module.deployment.internal.StartupSummaryDeploymentListener: ********************************************************************** * - - + DOMAIN + - - * - - + STATUS + - - * ********************************************************************** * default * DEPLOYED * ********************************************************************** ******************************************************************************************************* * - - + APPLICATION + - - * - - + DOMAIN + - - * - - + STATUS + - - * ******************************************************************************************************* * workday * default * FAILED * ******************************************************************************************************* ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12871","06/20/2017 03:59:17",5,"A config should not be considered as dynamic if a static expression is used ""*A config should not be considered as dynamic if a static expression is used* * If a connection/configuration uses the expression: {{#\[\{ key : 'val1', key2 : 'val2'\}\]}} as the value of a parameter, where the expression is not event dependent, the configuration should be considered as a static one. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12874","06/20/2017 15:39:02",3,"Split XmlHints in a two annotations, one for Parameter and one for Types ""XmlHints currently has three parameters: allowInlineDefinition, allowReferences and allowTopLevelDefinition `allowReferences` only make sense for parameters while `allowTopLevelDefinition` only make sense for types. We can see they are two faces of the same coin, viewed from different sides. A parameter can allow references only if it's type allows to be defined as a topLevel element. We should split in two annotations with the same name but different package and target type to better guide our users on when does each option apply: 'org.mule.runtime.extension.api.annotation.param.dsl.xml.XmlHints': - target FIELD and PARAMETER - allowInlineDefinition, allowReferences 'org.mule.runtime.extension.api.annotation.type.dsl.xml.XmlHints': - target TYPE - allowInlineDefinition, allowTopLevelDefinition *This _will_ break connectors code, but should have no impact in its final DSL*""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12880","06/21/2017 15:56:16",8,"Cannot load extension models in Windows ""Currently, the extension models are not loaded for any extension. It seems to be an issue with the paths and how we interact with them. It is failing to get the tools jar from the JDK. The path of that is trying to use is *C:\Program Files\Java\jre1.8.0_131/../lib/tools.jar* """," org.mule.tooling.core.utils.ExtensionModelLoaderUtils.getExtensionModelFromJar(ExtensionModelLoaderUtils.java:83) at org.mule.tooling.core.module.internal.runner.DownloadTask.doRun(DownloadTask.java:88) at org.mule.tooling.core.module.internal.runner.SingleDownloadTask.doRun(SingleDownloadTask.java:1) at org.mule.tooling.core.module.internal.runner.Task.run(Task.java:56) at org.mule.tooling.core.module.internal.runner.SingleDownloadTask.run(SingleDownloadTask.java:1) at org.mule.tooling.core.module.internal.runner.ArtifactResolvingRunner$ArtifactJob.run(ArtifactResolvingRunner.java:146) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.mule.maven.client.api.BundleDependenciesResolutionException: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact com.sun:tools:jar:1.8.0_131 at specified path C:\Program Files\Java\jre1.8.0_131/../lib/tools.jar at org.mule.maven.client.internal.AetherMavenClient.resolveBundleDescriptorDependencies(AetherMavenClient.java:181) at org.mule.tooling.client.bootstrap.ToolingRuntimeClientBootstrap.resolveDependency(ToolingRuntimeClientBootstrap.java:139) at org.mule.tooling.client.bootstrap.ToolingRuntimeClientBootstrap.createClassLoader(ToolingRuntimeClientBootstrap.java:97) Add Comment Collapse ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12886","06/21/2017 18:26:22",0,"Change logger default log level to INFO ""What title says :)""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12887","06/21/2017 19:08:16",1,"SchedulingStrategy parameter should be required ""Parameter should be required""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12891","06/21/2017 21:07:19",1,"Failure to validate extension model ""When trying to start the attached application, the following error is thrown: """," ERROR 2017-06-21 16:55:11,298 [WrapperListener_start_runner] org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Failed to deploy artifact 'http-extension-requester', + + see below + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ org.mule.runtime.deployment.model.api.DeploymentException: Failed to deploy artifact [http-extension-requester] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:33) ~[mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployArtifact(DefaultArchiveDeployer.java:272) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployExplodedApp(DefaultArchiveDeployer.java:261) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:89) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:40) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher.deployExplodedApps(DeploymentDirectoryWatcher.java:246) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher.start(DeploymentDirectoryWatcher.java:146) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.MuleDeploymentService.start(MuleDeploymentService.java:133) [mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.launcher.MuleContainer.start(MuleContainer.java:196) [mule-module-launcher-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_131] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_131] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_131] at org.mule.runtime.module.reboot.internal.MuleContainerWrapper.start(MuleContainerWrapper.java:49) [mule-module-boot-ee-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4242) [wrapper-3.5.29.jar:3.5.29] Caused by: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.deployment.model.api.DeploymentInitException: IllegalModelDefinitionException: Extension 'FTP' has definition errors: ERRORS: * Parameters with name [content] declared in [write, send] with tag name [content] are declared as Content but have different types [java.io.InputStream, java.lang.Object] WARNINGS: NONE at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:852) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:110) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:66) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] ... 14 more Caused by: org.mule.runtime.deployment.model.api.DeploymentInitException: IllegalModelDefinitionException: Extension 'FTP' has definition errors: ERRORS: * Parameters with name [content] declared in [write, send] with tag name [content] are declared as Content but have different types [java.io.InputStream, java.lang.Object] WARNINGS: NONE at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.doInit(DefaultMuleApplication.java:201) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.init(DefaultMuleApplication.java:167) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:848) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:110) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:66) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] ... 14 more Caused by: org.mule.runtime.core.api.config.ConfigurationException: Extension 'FTP' has definition errors: ERRORS: * Parameters with name [content] declared in [write, send] with tag name [content] are declared as Content but have different types [java.io.InputStream, java.lang.Object] WARNINGS: NONE (org.mule.runtime.extension.api.exception.IllegalModelDefinitionException) at org.mule.runtime.core.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:43) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory$1.configure(DefaultMuleContextFactory.java:88) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:217) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:82) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.ArtifactContextBuilder.lambda$build$1(ArtifactContextBuilder.java:396) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.ArtifactContextBuilder.build(ArtifactContextBuilder.java:329) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.doInit(DefaultMuleApplication.java:194) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.init(DefaultMuleApplication.java:167) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:848) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:110) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:66) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] ... 14 more Caused by: org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: Extension 'FTP' has definition errors: ERRORS: * Parameters with name [content] declared in [write, send] with tag name [content] are declared as Content but have different types [java.io.InputStream, java.lang.Object] WARNINGS: NONE at org.mule.runtime.extension.internal.loader.ExtensionModelFactory.create(ExtensionModelFactory.java:166) ~[mule-extensions-api-1.0.0-BETA-SNAPSHOT.jar:?] at org.mule.runtime.extension.api.loader.ExtensionModelLoader.loadExtensionModel(ExtensionModelLoader.java:72) ~[mule-extensions-api-1.0.0-BETA-SNAPSHOT.jar:?] at org.mule.runtime.module.deployment.impl.internal.policy.ArtifactExtensionManagerFactory.discoverExtensionThroughJsonDescriber(ArtifactExtensionManagerFactory.java:131) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.policy.ArtifactExtensionManagerFactory.lambda$create$0(ArtifactExtensionManagerFactory.java:76) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at java.util.ArrayList.forEach(ArrayList.java:1249) ~[?:1.8.0_131] at org.mule.runtime.module.deployment.impl.internal.policy.ArtifactExtensionManagerFactory.create(ArtifactExtensionManagerFactory.java:71) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.ArtifactExtensionManagerConfigurationBuilder.doConfigure(ArtifactExtensionManagerConfigurationBuilder.java:49) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:39) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory$1.configure(DefaultMuleContextFactory.java:88) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.doCreateMuleContext(DefaultMuleContextFactory.java:217) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:82) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.ArtifactContextBuilder.lambda$build$1(ArtifactContextBuilder.java:396) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.ArtifactContextBuilder.build(ArtifactContextBuilder.java:329) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.doInit(DefaultMuleApplication.java:194) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.init(DefaultMuleApplication.java:167) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:848) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) ~[mule-core-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:110) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.init(DeployableArtifactWrapper.java:66) ~[mule-module-deployment-model-impl-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:23) ~[mule-module-deployment-4.0.0-BETA-SNAPSHOT.jar:4.0.0-BETA-SNAPSHOT] ... 14 more ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12894","06/21/2017 21:49:03",1,"Fix OpenSAML dependencies in Soap Service ""OpenSAML appears to not be used anymore in the Soap Service so we should remove the dependency along with the transitive ones.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12895","06/21/2017 22:56:19",2,"Tooling Client fails to resolve transitive dependencies/extension models ""Tooling Client fails to resolve transitive dependencies/extension models. When trying to serialize a app declaration with WSC or HTTP it fails with: Caused by: org.mule.runtime.api.exception.MuleRuntimeException: Failed to serialize the declaration for the artifact [null]: The Extension [Sockets] is not present in the current context at org.mule.runtime.config.spring.dsl.model.internal.DefaultArtifactDeclarationXmlSerializer.serializeArtifact(DefaultArtifactDeclarationXmlSerializer.java:144) at org.mule.runtime.config.spring.dsl.model.internal.DefaultArtifactDeclarationXmlSerializer.serialize(DefaultArtifactDeclarationXmlSerializer.java:74) at org.mule.tooling.client.internal.artifact.DefaultArtifactSerializationService.toXml(DefaultArtifactSerializationService.java:63) ... 126 common frames omitted Caused by: java.lang.IllegalArgumentException: The Extension [Sockets] is not present in the current context at org.mule.runtime.extension.api.dsl.syntax.resolver.DefaultImportTypesStrategy.lambda$null$0(DefaultImportTypesStrategy.java:38) at java.util.Optional.orElseThrow(Optional.java:290) at org.mule.runtime.extension.api.dsl.syntax.resolver.DefaultImportTypesStrategy.lambda$getImportedTypes$1(DefaultImportTypesStrategy.java:38) at java.util.stream.Collectors.lambda$toMap$58(Collectors.java:1321) at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) at org.mule.runtime.extension.api.dsl.syntax.resolver.DefaultImportTypesStrategy.getImportedTypes(DefaultImportTypesStrategy.java:36) at org.mule.runtime.extension.internal.dsl.syntax.XmlDslSyntaxResolver.(XmlDslSyntaxResolver.java:113) at org.mule.runtime.extension.api.dsl.syntax.resolver.DslSyntaxResolver.getDefault(DslSyntaxResolver.java:75) at org.mule.runtime.config.spring.dsl.model.internal.DefaultDslElementModelFactory.lambda$new$1(DefaultDslElementModelFactory.java:33) at java.util.stream.Collectors.lambda$toMap$58(Collectors.java:1321) at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) at org.mule.runtime.config.spring.dsl.model.internal.DefaultDslElementModelFactory.(DefaultDslElementModelFactory.java:33) at org.mule.runtime.config.spring.dsl.model.DslElementModelFactory.getDefault(DslElementModelFactory.java:39) at org.mule.runtime.config.spring.dsl.model.internal.DefaultArtifactDeclarationXmlSerializer.serializeArtifact(DefaultArtifactDeclarationXmlSerializer.java:96) ... 128 common frames omitted""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12901","06/22/2017 12:28:16",8,"Sometimes, a fatal error is thrown while loading extension models ""While loading te extension models sometimes we get this fatal error, crashing studio even before it finishes loading. """," # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fff974f7fc9, pid=73929, tid=34311 # # JRE version: Java(TM) SE Runtime Environment (8.0_66-b17) (build 1.8.0_66-b17) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.66-b17 mixed mode bsd-amd64 compressed oops) # Problematic frame: # C [libsystem_platform.dylib+0x4fc9] _platform_memmove$VARIANT$Unknown+0x29 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try """"ulimit -c unlimited"""" before starting Java again # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # --------------- T H R E A D --------------- Current thread (0x00007fd99e5e0000): JavaThread """"ForkJoinPool.commonPool-worker-1"""" daemon [_thread_in_native, id=34311, stack(0x000000013077b000,0x000000013087b000)] siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x0000000127502000 Registers: RAX=0x00007fd99bb24e00, RBX=0x00000001274fbe6d, RCX=0x0000000000001408, RDX=0x000000000000756d RSP=0x00000001308789c0, RBP=0x00000001308789c0, RSI=0x0000000127502000, RDI=0x00007fd99bb2af65 R8 =0x00007fd99ba2e600, R9 =0x0000000000000005, R10=0x0000000077945a06, R11=0x00007fd874628f65 R12=0x0000000000000000, R13=0x00000000636f732f, R14=0x000000002f67726f, R15=0x000000000000656c RIP=0x00007fff974f7fc9, EFLAGS=0x0000000000010202, ERR=0x0000000000000004 TRAPNO=0x000000000000000e Top of Stack: (sp=0x00000001308789c0) 0x00000001308789c0: 0000000130878a30 000000010f6ce02d 0x00000001308789d0: 0000006c00000002 0000000000000065 0x00000001308789e0: 000000000000652f 00007fd99bb24e00 0x00000001308789f0: 000000000000756d 00007fd99ddf9220 0x0000000130878a00: 00007fd99fc53cd0 00007fd99ddf9220 0x0000000130878a10: 00007fd997bd9c00 0000000000000410 0x0000000130878a20: 00000000a35119de 00007fd99fc7f1b0 0x0000000130878a30: 0000000130878a90 000000010f6ce554 0x0000000130878a40: 0000000130878ad6 0000000130878ad5 0x0000000130878a50: 0000002600000000 00000027015e0000 0x0000000130878a60: 0000000130878aae 0000000130878ef8 0x0000000130878a70: 0000000000000027 0000000130878aae 0x0000000130878a80: 00007fd99ddf9220 00007fd99e5e01f8 0x0000000130878a90: 0000000130878ee0 000000010f6cd34f 0x0000000130878aa0: 0000009700000005 454d000700000001 0x0000000130878ab0: 6d2f464e492d4154 697472612d656c75 0x0000000130878ac0: 6c756d2f74636166 6e6967756c702d65 0x0000000130878ad0: 0000006e6f736a2e 0000000111ad479c 0x0000000130878ae0: 00000007ab62ea18 0000000000000000 0x0000000130878af0: 0000000000000000 0000000111afd8d7 0x0000000130878b00: 00000007ab62e890 0000009700000005 0x0000000130878b10: 0000000100000092 00000007637c3b58 0x0000000130878b20: 0000000130878b60 0000000124a60470 0x0000000130878b30: 00000001117ccc20 0000000530878c40 0x0000000130878b40: 0000000700000092 0000000000000000 0x0000000130878b50: 00000007ab62f038 00000007ab62f070 0x0000000130878b60: 00000007ab62f000 00007fd99e5e0000 0x0000000130878b70: 0000000130879200 0000000000000001 0x0000000130878b80: 0000000124d55438 0000000000000061 0x0000000130878b90: 00007fd99e5e0000 00007fd99e5e0000 0x0000000130878ba0: 0000000124d56d60 00007fd99e5e0000 0x0000000130878bb0: 0000000124d56d60 0000000124d56d60 Instructions: (pc=0x00007fff974f7fc9) 0x00007fff974f7fa9: f3 48 89 f8 49 39 d3 72 1b 48 83 fa 60 76 2f 48 0x00007fff974f7fb9: 81 fa 00 40 00 00 0f 82 bb 00 00 00 48 89 d1 fc 0x00007fff974f7fc9: f3 a4 5d c3 48 39 fe 74 f9 48 01 d6 48 01 d7 48 0x00007fff974f7fd9: 83 fa 60 0f 82 5c 01 00 00 e9 79 01 00 00 48 83 Register to memory mapping: RAX=0x00007fd99bb24e00 is an unknown value RBX=0x00000001274fbe6d is an unknown value RCX=0x0000000000001408 is an unknown value RDX=0x000000000000756d is an unknown value RSP=0x00000001308789c0 is pointing into the stack for thread: 0x00007fd99e5e0000 RBP=0x00000001308789c0 is pointing into the stack for thread: 0x00007fd99e5e0000 RSI=0x0000000127502000 is an unknown value RDI=0x00007fd99bb2af65 is an unknown value R8 =0x00007fd99ba2e600 is an unknown value R9 =0x0000000000000005 is an unknown value R10=0x0000000077945a06 is an unknown value R11=0x00007fd874628f65 is an unknown value R12=0x0000000000000000 is an unknown value R13=0x00000000636f732f is an unknown value R14=0x000000002f67726f is an unknown value R15=0x000000000000656c is an unknown value Stack: [0x000000013077b000,0x000000013087b000], sp=0x00000001308789c0, free space=1014k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [libsystem_platform.dylib+0x4fc9] _platform_memmove$VARIANT$Unknown+0x29 C [libzip.dylib+0x302d] newEntry+0x2c8 C [libzip.dylib+0x3554] ZIP_GetEntry2+0xd4 C [libzip.dylib+0x234f] Java_java_util_zip_ZipFile_getEntry+0xcf J 503 java.util.zip.ZipFile.getEntry(J[BZ)J (0 bytes) @ 0x00000001119b740e [0x00000001119b7340+0xce] J 6359 C2 java.util.zip.ZipFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry; (86 bytes) @ 0x00000001121c4c88 [0x00000001121c4900+0x388] J 7108 C1 sun.net.www.protocol.jar.URLJarFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry; (69 bytes) @ 0x0000000112d64404 [0x0000000112d64320+0xe4] J 7076 C1 sun.net.www.protocol.jar.JarURLConnection.connect()V (147 bytes) @ 0x0000000112d3cbac [0x0000000112d3c660+0x54c] J 7115 C1 sun.net.www.protocol.jar.JarURLConnection.getInputStream()Ljava/io/InputStream; (97 bytes) @ 0x0000000112d6befc [0x0000000112d6be60+0x9c] j org.mule.runtime.core.internal.util.JarUtils.loadFileContentFrom(Ljava/io/File;Ljava/lang/String;)Ljava/util/Optional;+15 j org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.create(Ljava/io/File;)Lorg/mule/runtime/deployment/model/api/plugin/ArtifactPluginDescriptor;+54 j org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.create(Ljava/io/File;)Lorg/mule/runtime/module/artifact/descriptor/ArtifactDescriptor;+2 j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver.lambda$null$3(Ljava/util/Set;Ljava/util/List;Lorg/mule/runtime/module/artifact/descriptor/BundleDependency;)V+73 j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver$$Lambda$382.accept(Ljava/lang/Object;)V+16 J 11808 C1 java.lang.Iterable.forEach(Ljava/util/function/Consumer;)V (39 bytes) @ 0x00000001139cf61c [0x00000001139cf320+0x2fc] j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver.lambda$getArtifactsWithDependencies$4(Ljava/util/Set;Ljava/util/List;Lorg/mule/runtime/deployment/model/api/plugin/ArtifactPluginDescriptor;)V+15 j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver$$Lambda$380.accept(Ljava/lang/Object;)V+16 J 12132 C1 java.util.stream.ForEachOps$ForEachOp$OfRef.accept(Ljava/lang/Object;)V (11 bytes) @ 0x0000000113ad839c [0x0000000113ad8280+0x11c] J 11310 C2 java.util.stream.ReferencePipeline$2$1.accept(Ljava/lang/Object;)V (27 bytes) @ 0x00000001138b20dc [0x00000001138b2060+0x7c] J 11310 C2 java.util.stream.ReferencePipeline$2$1.accept(Ljava/lang/Object;)V (27 bytes) @ 0x00000001138b20dc [0x00000001138b2060+0x7c] J 11721 C1 java.util.Iterator.forEachRemaining(Ljava/util/function/Consumer;)V (30 bytes) @ 0x00000001137e282c [0x00000001137e25e0+0x24c] J 11722 C1 java.util.Spliterators$IteratorSpliterator.forEachRemaining(Ljava/util/function/Consumer;)V (58 bytes) @ 0x00000001137dcd2c [0x00000001137dca00+0x32c] J 11904 C2 java.util.stream.AbstractPipeline.wrapAndCopyInto(Ljava/util/stream/Sink;Ljava/util/Spliterator;)Ljava/util/stream/Sink; (18 bytes) @ 0x0000000113a3bdf0 [0x0000000113a3bd00+0xf0] J 12239 C1 java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(Ljava/util/stream/PipelineHelper;Ljava/util/Spliterator;)Ljava/lang/Object; (7 bytes) @ 0x0000000113b3048c [0x0000000113b30320+0x16c] J 11712 C2 java.util.stream.AbstractPipeline.evaluate(Ljava/util/stream/TerminalOp;)Ljava/lang/Object; (94 bytes) @ 0x00000001139b19d4 [0x00000001139b18c0+0x114] J 12261 C1 java.util.stream.ReferencePipeline.forEach(Ljava/util/function/Consumer;)V (11 bytes) @ 0x0000000113b3b44c [0x0000000113b3b140+0x30c] j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver.getArtifactsWithDependencies(Ljava/util/List;Ljava/util/Set;)Ljava/util/List;+69 j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver.resolvePluginsDependencies(Ljava/util/List;)Ljava/util/List;+31 j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver.resolve(Ljava/util/List;)Ljava/util/List;+2 j org.mule.runtime.deployment.model.internal.tooling.ToolingPluginClassLoaderBuilder.build()Lorg/mule/runtime/module/artifact/classloader/ArtifactClassLoader;+31 j org.mule.tooling.client.internal.DefaultExtensionModelService.resolveExtensionModel(Lorg/mule/runtime/deployment/model/api/plugin/ArtifactPluginDescriptor;)Ljava/util/Optional;+53 j org.mule.tooling.client.internal.DefaultExtensionModelService.loadExtensionModel(Ljava/io/File;)Ljava/util/Optional;+121 j org.mule.tooling.client.internal.ExtensionModelServiceCache.lambda$loadExtensionModel$1(Lorg/mule/tooling/client/api/extension/ExtensionModelService;Ljava/io/File;)Ljava/util/Optional;+2 j org.mule.tooling.client.internal.ExtensionModelServiceCache$$Lambda$302.call()Ljava/lang/Object;+8 j com.google.common.cache.LocalCache$LocalManualCache$1.load(Ljava/lang/Object;)Ljava/lang/Object;+4 j com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(Ljava/lang/Object;Lcom/google/common/cache/CacheLoader;)Lcom/google/common/util/concurrent/ListenableFuture;+24 j com.google.common.cache.LocalCache$Segment.loadSync(Ljava/lang/Object;ILcom/google/common/cache/LocalCache$LoadingValueReference;Lcom/google/common/cache/CacheLoader;)Ljava/lang/Object;+4 j com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(Ljava/lang/Object;ILcom/google/common/cache/CacheLoader;)Ljava/lang/Object;+379 j com.google.common.cache.LocalCache$Segment.get(Ljava/lang/Object;ILcom/google/common/cache/CacheLoader;)Ljava/lang/Object;+138 j com.google.common.cache.LocalCache.get(Ljava/lang/Object;Lcom/google/common/cache/CacheLoader;)Ljava/lang/Object;+17 j com.google.common.cache.LocalCache$LocalManualCache.get(Ljava/lang/Object;Ljava/util/concurrent/Callable;)Ljava/lang/Object;+19 j org.mule.tooling.client.internal.ExtensionModelServiceCache.loadExtensionModel(Ljava/io/File;Lorg/mule/tooling/client/api/extension/ExtensionModelService;)Ljava/util/Optional;+12 j org.mule.tooling.client.internal.CachedExtensionModelService.loadExtensionModel(Ljava/io/File;)Ljava/util/Optional;+9 j org.mule.tooling.core.utils.ExtensionModelLoaderUtils.loadExtensionModel(Lorg/mule/tooling/client/bootstrap/ToolingRuntimeClientBootstrap;Ljava/io/File;Lorg/mule/maven/client/api/model/MavenConfiguration;)Lorg/mule/tooling/core/utils/Tuple;+32 j org.mule.tooling.core.utils.ExtensionModelLoaderUtils.lambda$3(Lorg/mule/tooling/client/bootstrap/ToolingRuntimeClientBootstrap;Lorg/mule/maven/client/api/model/MavenConfiguration;Ljava/io/File;)Lorg/mule/tooling/core/utils/Tuple;+3 j org.mule.tooling.core.utils.ExtensionModelLoaderUtils$$Lambda$108.apply(Ljava/lang/Object;)Ljava/lang/Object;+12 J 8990 C2 java.util.stream.ReferencePipeline$3$1.accept(Ljava/lang/Object;)V (23 bytes) @ 0x000000011340bbfc [0x000000011340bba0+0x5c] j java.util.ArrayList$ArrayListSpliterator.forEachRemaining(Ljava/util/function/Consumer;)V+99 j java.util.stream.AbstractPipeline.copyInto(Ljava/util/stream/Sink;Ljava/util/Spliterator;)V+32 J 6598 C1 java.util.stream.AbstractPipeline.wrapAndCopyInto(Ljava/util/stream/Sink;Ljava/util/Spliterator;)Ljava/util/stream/Sink; (18 bytes) @ 0x00000001120eb6b4 [0x00000001120eb480+0x234] j java.util.stream.ReduceOps$ReduceTask.doLeaf()Ljava/util/stream/ReduceOps$AccumulatingSink;+15 j java.util.stream.ReduceOps$ReduceTask.doLeaf()Ljava/lang/Object;+1 j java.util.stream.AbstractTask.compute()V+129 j java.util.concurrent.CountedCompleter.exec()Z+1 j java.util.concurrent.ForkJoinTask.doExec()I+10 j java.util.concurrent.ForkJoinPool$WorkQueue.runTask(Ljava/util/concurrent/ForkJoinTask;)V+21 j java.util.concurrent.ForkJoinPool.runWorker(Ljava/util/concurrent/ForkJoinPool$WorkQueue;)V+35 j java.util.concurrent.ForkJoinWorkerThread.run()V+24 v ~StubRoutines::call_stub V [libjvm.dylib+0x2ea35e] JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*)+0x6ae V [libjvm.dylib+0x2eaaec] JavaCalls::call_virtual(JavaValue*, KlassHandle, Symbol*, Symbol*, JavaCallArguments*, Thread*)+0x164 V [libjvm.dylib+0x2eac98] JavaCalls::call_virtual(JavaValue*, Handle, KlassHandle, Symbol*, Symbol*, Thread*)+0x4a V [libjvm.dylib+0x345215] thread_entry(JavaThread*, Thread*)+0x7c V [libjvm.dylib+0x560b83] JavaThread::thread_main_inner()+0x9b V [libjvm.dylib+0x56227e] JavaThread::run()+0x1c2 V [libjvm.dylib+0x482cd6] java_start(Thread*)+0xf6 C [libsystem_pthread.dylib+0x405a] _pthread_body+0x83 C [libsystem_pthread.dylib+0x3fd7] _pthread_body+0x0 C [libsystem_pthread.dylib+0x13ed] thread_start+0xd C 0x0000000000000000 Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) J 503 java.util.zip.ZipFile.getEntry(J[BZ)J (0 bytes) @ 0x00000001119b7398 [0x00000001119b7340+0x58] J 6359 C2 java.util.zip.ZipFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry; (86 bytes) @ 0x00000001121c4c88 [0x00000001121c4900+0x388] J 7108 C1 sun.net.www.protocol.jar.URLJarFile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry; (69 bytes) @ 0x0000000112d64404 [0x0000000112d64320+0xe4] J 7076 C1 sun.net.www.protocol.jar.JarURLConnection.connect()V (147 bytes) @ 0x0000000112d3cbac [0x0000000112d3c660+0x54c] J 7115 C1 sun.net.www.protocol.jar.JarURLConnection.getInputStream()Ljava/io/InputStream; (97 bytes) @ 0x0000000112d6befc [0x0000000112d6be60+0x9c] j org.mule.runtime.core.internal.util.JarUtils.loadFileContentFrom(Ljava/io/File;Ljava/lang/String;)Ljava/util/Optional;+15 j org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.create(Ljava/io/File;)Lorg/mule/runtime/deployment/model/api/plugin/ArtifactPluginDescriptor;+54 j org.mule.runtime.module.deployment.impl.internal.plugin.ArtifactPluginDescriptorFactory.create(Ljava/io/File;)Lorg/mule/runtime/module/artifact/descriptor/ArtifactDescriptor;+2 j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver.lambda$null$3(Ljava/util/Set;Ljava/util/List;Lorg/mule/runtime/module/artifact/descriptor/BundleDependency;)V+73 j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver$$Lambda$382.accept(Ljava/lang/Object;)V+16 J 11808 C1 java.lang.Iterable.forEach(Ljava/util/function/Consumer;)V (39 bytes) @ 0x00000001139cf61c [0x00000001139cf320+0x2fc] j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver.lambda$getArtifactsWithDependencies$4(Ljava/util/Set;Ljava/util/List;Lorg/mule/runtime/deployment/model/api/plugin/ArtifactPluginDescriptor;)V+15 j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver$$Lambda$380.accept(Ljava/lang/Object;)V+16 J 12132 C1 java.util.stream.ForEachOps$ForEachOp$OfRef.accept(Ljava/lang/Object;)V (11 bytes) @ 0x0000000113ad839c [0x0000000113ad8280+0x11c] J 11310 C2 java.util.stream.ReferencePipeline$2$1.accept(Ljava/lang/Object;)V (27 bytes) @ 0x00000001138b20dc [0x00000001138b2060+0x7c] J 11310 C2 java.util.stream.ReferencePipeline$2$1.accept(Ljava/lang/Object;)V (27 bytes) @ 0x00000001138b20dc [0x00000001138b2060+0x7c] J 11721 C1 java.util.Iterator.forEachRemaining(Ljava/util/function/Consumer;)V (30 bytes) @ 0x00000001137e282c [0x00000001137e25e0+0x24c] J 11722 C1 java.util.Spliterators$IteratorSpliterator.forEachRemaining(Ljava/util/function/Consumer;)V (58 bytes) @ 0x00000001137dcd2c [0x00000001137dca00+0x32c] J 11904 C2 java.util.stream.AbstractPipeline.wrapAndCopyInto(Ljava/util/stream/Sink;Ljava/util/Spliterator;)Ljava/util/stream/Sink; (18 bytes) @ 0x0000000113a3bdf0 [0x0000000113a3bd00+0xf0] J 12239 C1 java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(Ljava/util/stream/PipelineHelper;Ljava/util/Spliterator;)Ljava/lang/Object; (7 bytes) @ 0x0000000113b3048c [0x0000000113b30320+0x16c] J 11712 C2 java.util.stream.AbstractPipeline.evaluate(Ljava/util/stream/TerminalOp;)Ljava/lang/Object; (94 bytes) @ 0x00000001139b19d4 [0x00000001139b18c0+0x114] J 12261 C1 java.util.stream.ReferencePipeline.forEach(Ljava/util/function/Consumer;)V (11 bytes) @ 0x0000000113b3b44c [0x0000000113b3b140+0x30c] j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver.getArtifactsWithDependencies(Ljava/util/List;Ljava/util/Set;)Ljava/util/List;+69 j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver.resolvePluginsDependencies(Ljava/util/List;)Ljava/util/List;+31 j org.mule.runtime.deployment.model.internal.plugin.BundlePluginDependenciesResolver.resolve(Ljava/util/List;)Ljava/util/List;+2 j org.mule.runtime.deployment.model.internal.tooling.ToolingPluginClassLoaderBuilder.build()Lorg/mule/runtime/module/artifact/classloader/ArtifactClassLoader;+31 j org.mule.tooling.client.internal.DefaultExtensionModelService.resolveExtensionModel(Lorg/mule/runtime/deployment/model/api/plugin/ArtifactPluginDescriptor;)Ljava/util/Optional;+53 j org.mule.tooling.client.internal.DefaultExtensionModelService.loadExtensionModel(Ljava/io/File;)Ljava/util/Optional;+121 j org.mule.tooling.client.internal.ExtensionModelServiceCache.lambda$loadExtensionModel$1(Lorg/mule/tooling/client/api/extension/ExtensionModelService;Ljava/io/File;)Ljava/util/Optional;+2 j org.mule.tooling.client.internal.ExtensionModelServiceCache$$Lambda$302.call()Ljava/lang/Object;+8 j com.google.common.cache.LocalCache$LocalManualCache$1.load(Ljava/lang/Object;)Ljava/lang/Object;+4 j com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(Ljava/lang/Object;Lcom/google/common/cache/CacheLoader;)Lcom/google/common/util/concurrent/ListenableFuture;+24 j com.google.common.cache.LocalCache$Segment.loadSync(Ljava/lang/Object;ILcom/google/common/cache/LocalCache$LoadingValueReference;Lcom/google/common/cache/CacheLoader;)Ljava/lang/Object;+4 j com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(Ljava/lang/Object;ILcom/google/common/cache/CacheLoader;)Ljava/lang/Object;+379 j com.google.common.cache.LocalCache$Segment.get(Ljava/lang/Object;ILcom/google/common/cache/CacheLoader;)Ljava/lang/Object;+138 j com.google.common.cache.LocalCache.get(Ljava/lang/Object;Lcom/google/common/cache/CacheLoader;)Ljava/lang/Object;+17 j com.google.common.cache.LocalCache$LocalManualCache.get(Ljava/lang/Object;Ljava/util/concurrent/Callable;)Ljava/lang/Object;+19 j org.mule.tooling.client.internal.ExtensionModelServiceCache.loadExtensionModel(Ljava/io/File;Lorg/mule/tooling/client/api/extension/ExtensionModelService;)Ljava/util/Optional;+12 j org.mule.tooling.client.internal.CachedExtensionModelService.loadExtensionModel(Ljava/io/File;)Ljava/util/Optional;+9 j org.mule.tooling.core.utils.ExtensionModelLoaderUtils.loadExtensionModel(Lorg/mule/tooling/client/bootstrap/ToolingRuntimeClientBootstrap;Ljava/io/File;Lorg/mule/maven/client/api/model/MavenConfiguration;)Lorg/mule/tooling/core/utils/Tuple;+32 j org.mule.tooling.core.utils.ExtensionModelLoaderUtils.lambda$3(Lorg/mule/tooling/client/bootstrap/ToolingRuntimeClientBootstrap;Lorg/mule/maven/client/api/model/MavenConfiguration;Ljava/io/File;)Lorg/mule/tooling/core/utils/Tuple;+3 j org.mule.tooling.core.utils.ExtensionModelLoaderUtils$$Lambda$108.apply(Ljava/lang/Object;)Ljava/lang/Object;+12 J 8990 C2 java.util.stream.ReferencePipeline$3$1.accept(Ljava/lang/Object;)V (23 bytes) @ 0x000000011340bbfc [0x000000011340bba0+0x5c] j java.util.ArrayList$ArrayListSpliterator.forEachRemaining(Ljava/util/function/Consumer;)V+99 j java.util.stream.AbstractPipeline.copyInto(Ljava/util/stream/Sink;Ljava/util/Spliterator;)V+32 J 6598 C1 java.util.stream.AbstractPipeline.wrapAndCopyInto(Ljava/util/stream/Sink;Ljava/util/Spliterator;)Ljava/util/stream/Sink; (18 bytes) @ 0x00000001120eb6b4 [0x00000001120eb480+0x234] j java.util.stream.ReduceOps$ReduceTask.doLeaf()Ljava/util/stream/ReduceOps$AccumulatingSink;+15 j java.util.stream.ReduceOps$ReduceTask.doLeaf()Ljava/lang/Object;+1 j java.util.stream.AbstractTask.compute()V+129 j java.util.concurrent.CountedCompleter.exec()Z+1 j java.util.concurrent.ForkJoinTask.doExec()I+10 j java.util.concurrent.ForkJoinPool$WorkQueue.runTask(Ljava/util/concurrent/ForkJoinTask;)V+21 j java.util.concurrent.ForkJoinPool.runWorker(Ljava/util/concurrent/ForkJoinPool$WorkQueue;)V+35 j java.util.concurrent.ForkJoinWorkerThread.run()V+24 v ~StubRoutines::call_stub --------------- P R O C E S S --------------- Java Threads: ( => current thread ) 0x00007fd99e595800 JavaThread """"DefaultMetadataResolver-29-3"""" daemon [_thread_in_native, id=62991, stack(0x0000000139794000,0x0000000139894000)] 0x00007fd99e595000 JavaThread """"DefaultMetadataResolver-29-2"""" daemon [_thread_in_native, id=64527, stack(0x0000000139481000,0x0000000139581000)] 0x00007fd99e594000 JavaThread """"DefaultMetadataResolver-29-1"""" daemon [_thread_in_native, id=66335, stack(0x000000013937e000,0x000000013947e000)] 0x00007fd99e31c800 JavaThread """"DefaultMetadataResolver-29-0"""" daemon [_thread_in_native, id=66591, stack(0x000000013927b000,0x000000013937b000)] 0x00007fd9959aa800 JavaThread """"DefaultMetadataResolver-28-3"""" daemon [_thread_in_native, id=75027, stack(0x0000000137116000,0x0000000137216000)] 0x00007fd9950bb800 JavaThread """"DefaultMetadataResolver-28-2"""" daemon [_thread_in_native, id=72979, stack(0x0000000137013000,0x0000000137113000)] 0x00007fd99e0e3800 JavaThread """"DefaultMetadataResolver-28-1"""" daemon [_thread_in_native, id=69647, stack(0x0000000136f10000,0x0000000137010000)] 0x00007fd99e0ee000 JavaThread """"DefaultMetadataResolver-28-0"""" daemon [_thread_in_native, id=14611, stack(0x0000000136bd6000,0x0000000136cd6000)] 0x00007fd994266000 JavaThread """"DefaultMetadataResolver-27-3"""" daemon [_thread_in_native, id=70415, stack(0x0000000136ad3000,0x0000000136bd3000)] 0x00007fd99e322800 JavaThread """"DefaultMetadataResolver-27-2"""" daemon [_thread_blocked, id=69391, stack(0x0000000136890000,0x0000000136990000)] 0x00007fd99d51b000 JavaThread """"DefaultMetadataResolver-27-1"""" daemon [_thread_blocked, id=72203, stack(0x000000013678d000,0x000000013688d000)] 0x00007fd99d265800 JavaThread """"DefaultMetadataResolver-27-0"""" daemon [_thread_blocked, id=71435, stack(0x000000013668a000,0x000000013678a000)] 0x00007fd99688a800 JavaThread """"DefaultMetadataResolver-26-3"""" daemon [_thread_in_native, id=71179, stack(0x0000000136587000,0x0000000136687000)] 0x00007fd99cecf000 JavaThread """"DefaultMetadataResolver-26-2"""" daemon [_thread_blocked, id=70923, stack(0x0000000136484000,0x0000000136584000)] 0x00007fd99bf62000 JavaThread """"DefaultMetadataResolver-26-1"""" daemon [_thread_blocked, id=65059, stack(0x0000000135cff000,0x0000000135dff000)] 0x00007fd99baf9000 JavaThread """"DefaultMetadataResolver-26-0"""" daemon [_thread_blocked, id=66083, stack(0x0000000135bfc000,0x0000000135cfc000)] 0x00007fd99888b800 JavaThread """"BasicRepositoryConnector-repository-master.mulesoft.org-25-1"""" daemon [_thread_blocked, id=75283, stack(0x0000000134f07000,0x0000000135007000)] 0x00007fd99ba2d000 JavaThread """"BasicRepositoryConnector-repository-master.mulesoft.org-25-0"""" daemon [_thread_in_native, id=72723, stack(0x0000000134e04000,0x0000000134f04000)] 0x00007fd99d33a800 JavaThread """"[ThreadPool Manager] - Idle Thread"""" daemon [_thread_blocked, id=69131, stack(0x000000013500a000,0x000000013510a000)] 0x00007fd99618d000 JavaThread """"ForkJoinPool.commonPool-worker-7"""" daemon [_thread_blocked, id=59651, stack(0x0000000134d01000,0x0000000134e01000)] 0x00007fd99e520000 JavaThread """"ForkJoinPool.commonPool-worker-6"""" daemon [_thread_blocked, id=59139, stack(0x0000000134bfe000,0x0000000134cfe000)] 0x00007fd994289800 JavaThread """"ForkJoinPool.commonPool-worker-5"""" daemon [_thread_blocked, id=58747, stack(0x0000000134afb000,0x0000000134bfb000)] 0x00007fd99d639800 JavaThread """"ForkJoinPool.commonPool-worker-4"""" daemon [_thread_blocked, id=40303, stack(0x00000001349f8000,0x0000000134af8000)] 0x00007fd99be5c000 JavaThread """"ForkJoinPool.commonPool-worker-3"""" daemon [_thread_blocked, id=34567, stack(0x0000000134613000,0x0000000134713000)] 0x00007fd99e5e1000 JavaThread """"ForkJoinPool.commonPool-worker-2"""" daemon [_thread_blocked, id=15623, stack(0x0000000134510000,0x0000000134610000)] =>0x00007fd99e5e0000 JavaThread """"ForkJoinPool.commonPool-worker-1"""" daemon [_thread_in_native, id=34311, stack(0x000000013077b000,0x000000013087b000)] 0x00007fd99eab6800 JavaThread """"EventAdmin Async Event Dispatcher Thread"""" daemon [_thread_blocked, id=56619, stack(0x000000013256b000,0x000000013266b000)] 0x00007fd99d244800 JavaThread """"Java indexing"""" daemon [_thread_blocked, id=49171, stack(0x000000012f570000,0x000000012f670000)] 0x00007fd995b02000 JavaThread """"Worker-2"""" [_thread_blocked, id=48643, stack(0x00000001328b4000,0x00000001329b4000)] 0x00007fd9987f0800 JavaThread """"Worker-1"""" [_thread_blocked, id=48415, stack(0x0000000131c39000,0x0000000131d39000)] 0x00007fd9978b1800 JavaThread """"EMF Reference Cleaner"""" daemon [_thread_blocked, id=47879, stack(0x0000000130478000,0x0000000130578000)] 0x00007fd998fe9800 JavaThread """"Provisioning Event Dispatcher"""" daemon [_thread_blocked, id=45315, stack(0x000000012ea7f000,0x000000012eb7f000)] 0x00007fd99688c800 JavaThread """"Worker-0"""" [_thread_blocked, id=45079, stack(0x000000012dc00000,0x000000012dd00000)] 0x00007fd99802c800 JavaThread """"Worker-JM"""" [_thread_blocked, id=44559, stack(0x000000012ef6c000,0x000000012f06c000)] 0x00007fd9952d1800 JavaThread """"Bundle File Closer"""" daemon [_thread_blocked, id=43787, stack(0x000000012e44f000,0x000000012e54f000)] 0x00007fd9956ad000 JavaThread """"[Timer] - Main Queue Handler"""" daemon [_thread_blocked, id=43271, stack(0x000000012e34c000,0x000000012e44c000)] 0x00007fd995650000 JavaThread """"Start Level: Equinox Container: 3ea59165-9107-45f4-90e0-8ae4c2feefe2"""" daemon [_thread_blocked, id=41219, stack(0x000000012d537000,0x000000012d637000)] 0x00007fd995651000 JavaThread """"Framework Event Dispatcher: org.eclipse.osgi.internal.framework.EquinoxEventPublisher@e322ec9"""" daemon [_thread_blocked, id=40735, stack(0x000000012d434000,0x000000012d534000)] 0x00007fd995277800 JavaThread """"Active Thread: Equinox Container: 3ea59165-9107-45f4-90e0-8ae4c2feefe2"""" [_thread_blocked, id=40499, stack(0x000000012dd07000,0x000000012de07000)] 0x00007fd993098000 JavaThread """"Service Thread"""" daemon [_thread_blocked, id=23043, stack(0x000000012a3b6000,0x000000012a4b6000)] 0x00007fd99381f000 JavaThread """"C1 CompilerThread3"""" daemon [_thread_blocked, id=22531, stack(0x000000012a2b3000,0x000000012a3b3000)] 0x00007fd993020000 JavaThread """"C2 CompilerThread2"""" daemon [_thread_blocked, id=22019, stack(0x000000012a1b0000,0x000000012a2b0000)] 0x00007fd99284b800 JavaThread """"C2 CompilerThread1"""" daemon [_thread_blocked, id=21507, stack(0x000000012a0ad000,0x000000012a1ad000)] 0x00007fd992846000 JavaThread """"C2 CompilerThread0"""" daemon [_thread_blocked, id=20995, stack(0x0000000129faa000,0x000000012a0aa000)] 0x00007fd992823800 JavaThread """"VM JFR Buffer Thread"""" daemon [_thread_blocked, id=20483, stack(0x0000000129ea7000,0x0000000129fa7000)] 0x00007fd992822000 JavaThread """"JFR request timer"""" daemon [_thread_blocked, id=19971, stack(0x0000000129d30000,0x0000000129e30000)] 0x00007fd995042800 JavaThread """"JDWP Command Reader"""" daemon [_thread_in_native, id=19459, stack(0x0000000129c21000,0x0000000129d21000)] 0x00007fd995042000 JavaThread """"JDWP Event Helper Thread"""" daemon [_thread_blocked, id=18947, stack(0x0000000129b1e000,0x0000000129c1e000)] 0x00007fd995022800 JavaThread """"JDWP Transport Listener: dt_socket"""" daemon [_thread_blocked, id=18435, stack(0x0000000129a1b000,0x0000000129b1b000)] 0x00007fd995022000 JavaThread """"Signal Dispatcher"""" daemon [_thread_blocked, id=17931, stack(0x0000000129918000,0x0000000129a18000)] 0x00007fd993035800 JavaThread """"Finalizer"""" daemon [_thread_blocked, id=13571, stack(0x00000001273b1000,0x00000001274b1000)] 0x00007fd993812800 JavaThread """"Reference Handler"""" daemon [_thread_blocked, id=13059, stack(0x00000001272ae000,0x00000001273ae000)] 0x00007fd993804000 JavaThread """"main"""" [_thread_blocked, id=1811, stack(0x00007fff4fee7000,0x00007fff506e7000)] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12906","06/22/2017 18:59:30",8,"Extensions that use the soap service fails with Provider com.ctc.wstx.stax.WstxInputFactory not found ""Soap Connect Extensions fail with: Provider com.ctc.wstx.stax.WstxInputFactory not The XmlInputFactory.newInstance() is being executed with the Soap extension Classloader that does not have the Woodstox classes. As a workaround including woodstox in the extension pom.xml will make it work ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12910","06/22/2017 20:21:56",3,"File connector errors being mapped to MULE:UNKNOWN ""The following File connector errors been mapped to MULE:UNKNOWN h2. javax.activation.MimeTypeParseException Triggered by passing a value of """"invalid"""" to the file:read outputMimeType attribute. h2. java.nio.file.FileSystemException Triggered by setting mode OVERWRITE and passing a directory as path value to the file:write operation. h2. java.nio.file.AccessDeniedException Triggered by setting a path to a non writable folder to the file:rename operation. """," {ERRORTYPE=MULE:UNKNOWN, DESCRIPTION=MediaType cannot be parsed: invalid} ERROR 2017-06-22 16:17:35,061 [[MuleRuntime].io.07] org.mule.runtime.core.exception.OnErrorPropagateHandler: ******************************************************************************** Message : MediaType cannot be parsed: invalid (java.lang.IllegalArgumentException).. Payload Type : org.mule.runtime.core.internal.util.message.ResultsToMessageList FlowStack : at main-flow(main-flow/processors/3 @ file-extension:null:158) Element : main-flow/processors/3 @ file-extension:null:158 Element XML : -------------------------------------------------------------------------------- Root Exception stack trace: javax.activation.MimeTypeParseException: Unable to find a sub type. at javax.activation.MimeType.parse(MimeType.java:102) at javax.activation.MimeType.(MimeType.java:63) at org.mule.runtime.api.metadata.MediaType.parse(MediaType.java:84) {ERRORTYPE=MULE:UNKNOWN, DESCRIPTION=Exception was found writing to file '/Users/hwittemoller/dev/git/mule-uber/mule-ee/distributions/tests/target/servers/FileExtensionErrorHandlingTestCase/mule-enterprise-standalone-4.0.0-SNAPSHOT/apps/file-extension/classes/write/to'} ERROR 2017-06-26 17:58:57,982 [[MuleRuntime].io.07] org.mule.runtime.core.exception.OnErrorPropagateHandler: ******************************************************************************** Message : Exception was found writing to file '/Users/hwittemoller/dev/git/mule-uber/mule-ee/distributions/tests/target/servers/FileExtensionErrorHandlingTestCase/mule-enterprise-standalone-4.0.0-SNAPSHOT/apps/file-extension/classes/write/to' (org.mule.runtime.api.exception.MuleRuntimeException).. Payload Type : org.mule.runtime.core.internal.streaming.bytes.ManagedCursorStreamProvider FlowStack : at main-flow(main-flow/processors/13 @ file-extension:null:195) Element : main-flow/processors/13 @ file-extension:null:195 Element XML : -------------------------------------------------------------------------------- Root Exception stack trace: java.nio.file.FileSystemException: /Users/hwittemoller/dev/git/mule-uber/mule-ee/distributions/tests/target/servers/FileExtensionErrorHandlingTestCase/mule-enterprise-standalone-4.0.0-SNAPSHOT/apps/file-extension/classes/write/to: Is a directory {ERRORTYPE=MULE:UNKNOWN, DESCRIPTION=Exception was found renaming '/var/folders/t_/zlsf2yb56dvbhff9rsrccw5w0000gn/T/junit8909602778879002288/nonWritableTargetDirectory' to 'anotherFolderName'} ERROR 2017-06-27 15:47:30,178 [[MuleRuntime].io.07] org.mule.runtime.core.internal.exception.OnErrorPropagateHandler: ******************************************************************************** Message : Exception was found renaming '/var/folders/t_/zlsf2yb56dvbhff9rsrccw5w0000gn/T/junit8909602778879002288/nonWritableTargetDirectory' to 'anotherFolderName' (org.mule.runtime.api.exception.MuleRuntimeException).. Payload Type : org.mule.runtime.core.internal.util.message.ResultsToMessageList FlowStack : at main-flow(main-flow/processors/9 @ file-extension:null:187) Element : main-flow/processors/9 @ file-extension:null:187 Element XML : -------------------------------------------------------------------------------- Root Exception stack trace: java.nio.file.AccessDeniedException: /var/folders/t_/zlsf2yb56dvbhff9rsrccw5w0000gn/T/junit8909602778879002288/nonWritableTargetDirectory -> /var/folders/t_/zlsf2yb56dvbhff9rsrccw5w0000gn/T/junit8909602778879002288/anotherFolderName ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12911","06/22/2017 20:41:14",8,"MetadataKeys and Value resolvers should type the parameters ""*MetadataKeys and Options resolvers should type the parameters* * In the same way as Metadata resolvers return a ComponentModel with the resolved type as the input or ouput, the MetadataKeys and Options resolver should """"type"""" -> add a model property indicating the possible values for these parameter. * This JIRA is highly related to -> https://www.mulesoft.org/jira/browse/MULE-12855""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12914","06/22/2017 21:35:59",1,"Mask password args in system tests. ""The passwords of the maven repos are being logges as tehy are currently""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12916","06/22/2017 22:30:13",0,"MuleDeployment should delete distributions quietly ""MuleDeployment should delete distributions quietly""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12918","06/23/2017 00:10:09",3,"Soap Connect: Invoke Operation is being added to the extension model twice ""Soap Connect: Invoke Operation is being added to the extension model twice""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12924","06/23/2017 15:22:01",0,"Fix extension model test ""assertion: should be change to: to avoid having unnecesary failures due to any changes on versions""","expectedException .expectMessage(containsString(""""Could not find artifact org.mule.connectors:mule-email-connector:jar:mule-plugin:1.0.0-SNAPSHOT""""));expectedException .expectMessage(containsString(""""Could not find artifact org.mule.connectors:mule-email-connector:jar:mule-plugin:1.0.0-SNAPSHOT""""));",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12930","06/23/2017 20:12:48",2,"Cannot do datasense for JMS connector ""It's not possible to do datasense over JMS connector since the extension model cache is closing the class loader after returning the extension model""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12934","06/26/2017 13:11:55",0,"Cannot load extension model for JMS connector ""See ignored test in StaticDataSenseTestCase. To load the extension model, the JMS connector depends on the JMS API to be in the classpath but it's currently being defined as provided dependency. Since the JMS connector won't work unless the jms-api is in the classpath and is the 2.x version of it, then it seems it should come with the connector. We need to review how classloading would work in this case since adding activemq in the app classpath would also contribute the JMS spec.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12937","06/26/2017 20:03:47",8,"Artifacts using heavy package must should not depend on maven for classloader model resolution ""Artifacts packaged with all their dependencies (ie: heavy packages) still depend on the artifact pom.xml and Maven in order to resolve the classloader model. This is a problem as it requires access to the same set of dependencies that where used to resolve the artifact at compile time. So, maven artifacts that were discarded during the compile time (because they were excluded or there was a newer version of the artifact) are still required on runtime. (wasting space) A better approach is to resolve the dependencies on compile time, generate a maven repository only with the required jars, and then generate metadata that indicates which files must be loaded in the artifact's classloader model. (this could use a new classloader model loader)""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12941","06/27/2017 12:22:51",1,"Bootstrap properties should not be exported ""Bootstrap properties resources are still exported on the core module.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12942","06/27/2017 15:22:06",1,"MetadataContext returns a ConfigurationInstance instead of the Configuration it self ""MetadataContext returns a ConfigurationInstance instead of the Configuration it self""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12946","06/27/2017 16:19:59",5,"ClassLoader leak on DeclarationEnrichers generate an OOM Metaspace when calculating Metadata for DataSense ""When doing DataSense for Salesforce connector a OOM Metaspace has happened. The first reason for this was a classloader leak in the connector, once that was removed more were found related to DeclarationEnrichers as they are keeping a reference to classes from the Extension and the ClassLoader itself. I found the first *on org.mule.runtime.module.extension.internal.loader.enricher.DynamicMetadataDeclarationEnricher* once that one was fixed a found another one *on org.mule.runtime.module.extension.internal.loader.enricher.ImportedTypesDeclarationEnricher*. See screenshots attached with VisualVM.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12947","06/27/2017 16:48:04",1,"file:move error messages say 'Can't copy ... ' instead of 'Can't move ...' ""file:move error messages says 'Can't copy ... ' instead of 'Can't move ...' """," ERROR 2017-06-27 12:56:14,876 [[MuleRuntime].io.07] org.mule.runtime.core.internal.exception.OnErrorPropagateHandler: ******************************************************************************** Message : org.mule.extension.file.common.api.exceptions.IllegalPathException: Can't copy '/Users/hwittemoller/dev/git/mule-uber/mule-ee/distributions/tests/target/servers/FileExtensionErrorHandlingTestCase/mule-enterprise-standalone-4.0.0-SNAPSHOT/apps/file-extension/classes/move/file.json' to '/Users/hwittemoller/dev/git/mule-uber/mule-ee/distributions/tests/target/servers/FileExtensionErrorHandlingTestCase/mule-enterprise-standalone-4.0.0-SNAPSHOT/apps/file-extension/classes/move/nonExistentDirectory' because the destination path doesn't exists. Payload Type : org.mule.runtime.core.internal.util.message.ResultsToMessageList FlowStack : at main-flow(main-flow/processors/7 @ file-extension:null:183) Element : main-flow/processors/7 @ file-extension:null:183 Element XML : -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.runtime.api.exception.MuleRuntimeException: Can't copy '/Users/hwittemoller/dev/git/mule-uber/mule-ee/distributions/tests/target/servers/FileExtensionErrorHandlingTestCase/mule-enterprise-standalone-4.0.0-SNAPSHOT/apps/file-extension/classes/move/file.json' to '/Users/hwittemoller/dev/git/mule-uber/mule-ee/distributions/tests/target/servers/FileExtensionErrorHandlingTestCase/mule-enterprise-standalone-4.0.0-SNAPSHOT/apps/file-extension/classes/move/nonExistentDirectory' because the destination path doesn't exists ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12948","06/27/2017 16:49:31",8,"Expand External Lib functionality ""Allow to also specify that a dependency is needed""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12949","06/27/2017 16:52:07",8,"Refresh socket extension ""Bump it to incorporate all the UX changes since the inception moment""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12952","06/27/2017 18:30:21",1,"file:move not throwing error when file already exists on directory ""file:move not throwing error when overwrite=""""false"""", no renameTo value is provided and file already exists on directory *App details* To reproduce run com.mulesoft.mule.distributions.server.integration.scenarios.errorhandling.FileExtensionErrorHandlingTestCase#moveErrorIfFileAlreadyExistsNoRenameToIsGivenAndOverwriteIsFalse"""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12953","06/27/2017 19:00:20",2,"Mule Core operations don't expose any error models ""Several Mule Core's operations (like """"logger"""", """"foreach"""", """"splitter"""") don't expose any error models ([https://github.com/mulesoft/mule/blob/mule-4.x/modules/extensions-support/src/main/resources/META-INF/mule-extension-model.json#L572)] although they do throw (ie. an invalid expression in a logger message)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12954","06/27/2017 20:55:05",1,"file:copy not throwing error when file already exists on directory ""file:copy not throwing error when overwrite=""""false"""", no renameTo value is provided and file already exists on directory *App details* To reproduce run com.mulesoft.mule.distributions.server.integration.scenarios.errorhandling.FileExtensionErrorHandlingTestCase#copyFileAlreadyExistsIfTargetPathAlreadyExistsAndOverwriteIsFalse"""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12955","06/27/2017 21:06:01",0,"DW: Support instantiation through builders ""Considering most of our API interfaces implementations are hidden and immutable, DW should interpret their builders in order to instantiate them. If we settle on a builder convention this could work for any interfaces.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12961","06/28/2017 15:40:34",8,"WSC: Add support for WS-SecurityPolicy. ""Add support for WS-SecurityPolicy in 3.9.x and 3.8.x. Here you can find how CXF supports this to add it to the Soap Service. [http://cxf.apache.org/docs/ws-securitypolicy.html] Then we should expose some configuration for the WSC.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12965","06/29/2017 04:10:54",1,"CraftedExtensionModelLoader should set ClassLoaderModelProperty ""ExtensionModel loaded with crafted loader should also have the ClassLoaderModelProperty set.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12969","06/29/2017 18:58:02",0,"Inconsistent behaviour in foreach with collection attribute ""The foreach by default uses the org.mule.routing.Foreach$CollectionMapSplitter to split the collections. If you use a batch size greater than 1, this returns a list of objects, however, if the payload is a map or you use the collection attribute, the generated payload is a list of messages. I've seen that the difference is that then you don't set the collection attribute in the foreach scope and the payload is not a map, then this fragment of the code is triggered: [https://github.com/mulesoft/mule/blob/mule-3.8.4/core/src/main/java/org/mule/routing/Foreach.java#L289] That uses an [EventToMessageSequenceSplittingStrategy|https://github.com/mulesoft/mule/blob/mule-3.8.4/core/src/main/java/org/mule/util/collection/EventToMessageSequenceSplittingStrategy.java#L31] which by the code returns a list of objects and then is wrapped in a CollectionMessageSequence. On the other hand, the ExpressionSplitter which is used if the collection attribute is set always returns a CollectionMessageSequence wrapping a list of mule messages: [https://github.com/mulesoft/mule/blob/mule-3.8.4/core/src/main/java/org/mule/routing/ExpressionSplitter.java#L61].""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12970","06/29/2017 20:32:43",1,"Error generating parameter validation error message. ""Error generating the exception error message here: https://github.com/mulesoft/mule/blob/mule-4.x/modules/extensions-support/src/main/java/org/mule/runtime/module/extension/internal/loader/java/ParameterModelsLoaderDelegate.java#L162 Caused by: java.lang.IllegalArgumentException: Component 'org.mule.runtime.api.meta.model.declaration.fluent.ConnectionProviderDeclarer@7603abce' is not an instance of any known model type [configuration, connection provider, operation, source, source callback] at org.mule.runtime.extension.api.util.NameUtils.getComponentModelTypeName(NameUtils.java:313) at org.mule.runtime.module.extension.internal.loader.java.ParameterModelsLoaderDelegate.declaredAsGroup(ParameterModelsLoaderDelegate.java:161) at org.mule.runtime.module.extension.internal.loader.java.ParameterModelsLoaderDelegate.declare(ParameterModelsLoaderDelegate.java:100) at org.mule.runtime.module.extension.internal.loader.java.ParameterModelsLoaderDelegate.declare(ParameterModelsLoaderDelegate.java:84) at org.mule.runtime.module.extension.internal.loader.java.ConnectionProviderModelLoaderDelegate.declareConnectionProvider(ConnectionProviderModelLoaderDelegate.java:103) at org.mule.runtime.module.extension.internal.loader.java.ConnectionProviderModelLoaderDelegate.lambda$declareConnectionProviders$0(ConnectionProviderModelLoaderDelegate.java:53) at java.util.ArrayList.forEach(ArrayList.java:1249) at org.mule.runtime.module.extension.internal.loader.java.ConnectionProviderModelLoaderDelegate.declareConnectionProviders(ConnectionProviderModelLoaderDelegate.java:53) at org.mule.runtime.module.extension.internal.loader.java.ConfigModelLoaderDelegate.declareConfiguration(ConfigModelLoaderDelegate.java:76) at org.mule.runtime.module.extension.internal.loader.java.ConfigModelLoaderDelegate.declareConfigurations(ConfigModelLoaderDelegate.java:46) at org.mule.runtime.module.extension.internal.loader.java.DefaultJavaModelLoaderDelegate.declare(DefaultJavaModelLoaderDelegate.java:120) at org.mule.runtime.module.extension.internal.loader.java.AbstractJavaExtensionModelLoader.declareExtension(AbstractJavaExtensionModelLoader.java:121) at org.mule.runtime.extension.api.loader.ExtensionModelLoader.loadExtensionModel(ExtensionModelLoader.java:71) at org.mule.runtime.module.extension.internal.resources.BaseExtensionResourcesGeneratorAnnotationProcessor.parseExtension(BaseExtensionResourcesGeneratorAnnotationProcessor.java:106) at org.mule.runtime.module.extension.internal.resources.BaseExtensionResourcesGeneratorAnnotationProcessor.lambda$null$0(BaseExtensionResourcesGeneratorAnnotationProcessor.java:85) at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:848) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12972","06/30/2017 03:23:09",8,"Refactor MetadataCache API on Tooling ""We have identified that the cache API exposed as it is in Tooling has conflicts with the whole story of having a Tooling API in order to avoid clients to use mule-api.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12977","07/02/2017 21:36:46",2,"DefaultImplementingTypeModelProperty is not populated for streaming strategy parameter models ""In order to properly generate the UI for streaming strategy, its parameter model needs to be populated with the DefaultImplementingTypeModelProperty. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12980","07/03/2017 16:10:40",3,"Operation metadatakey is usind the ID as display name for @Soap based extension ""When creating a @Soap based extension, the keys retrieved have a display name for the services, but the operations display name is the same as the Id. For example: Issue_Management service generates a key with name *Issue_Management* and display *Issue Management* Get_Records operation generates a key with name *Get_Records* and display name *Get_Records* Both display names should be generated using the same format""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12981","07/03/2017 17:21:08",3,"@DefaultEncoding annotation does not work without @Parameter ""HttpListener requires the default encoding of the application and it's taking it from the MuleContext. In order to decouple HttpListener from MuleContext I tried to use @DefaultEncoding but it does not work if the attribute is not also annotated with @Parameter. In this case the default encoding is needed but is not configurable.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12983","07/03/2017 19:33:45",8,"Embedded container does not resolve local artifacts ""When running the embedded container from inside MUnit    The container deploys the application when doing so it disregards the applications dependencies installed locally and those packaged and it always tries to resolve them from the remote reopositories.    The only way to avoid this is to only set a remote repository as your local, if you convine your local m2 with other repositories there is no waranty that the artifacts will be resolved from the local.    To make this clear, the embedded container should look for the application dependencies in the repository packaged with the application     ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12986","07/04/2017 00:56:35",2,"Refactor HTTP input data ""Now that HTTP no longer parses responses/requests, we need to make sure it's not evaluating input data either to match those types it used to work with. We need to decide whether we force InputStreams or continue to handle Objects that we turn to ByteArrays if need be.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12987","07/04/2017 00:58:12",1,"Line ending formatter validation fails in windows ""Format validation is checking line endings are unix styles, which causes the validation to fail on windows.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12991","07/04/2017 21:18:52",1,"Soap connect missing default value for body ""Soap connect missing default value for body""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12993","07/05/2017 12:52:56",0,"Include and export javax.jms on the API ""As the EE version of the container requires to include and export javax.jms, in order to provide the same user experience for both CE/EE users (regarding how to build apps), the CE container must do the same. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12997","07/05/2017 14:47:47",2,"ExpressionLanguage should expose GroupCorrelation ""ExpressionLanguage should expose GroupCorrelation""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-12998","07/05/2017 14:49:29",2,"Event API is inconsistent and implementation is not immutable after addition of properties and parameters. ""Event API is inconsistent and implementation is not immutable after addition of properties and parameters. * variables has method for names, value, but not map, whereas properties/params returns map. * map returned is not immutable either. Ideal solution is to use same pattern for additions""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13000","07/05/2017 16:37:26",8,"ObjectFactoryClassRepository is destroying proxies for container entities ""When doing connectivity testing the dispose of an application is also destroying from the ObjectFactoryClassRepository the callback for org.mule.runtime.module.extension.internal.config.dsl.connection.ConnectionProviderObjectFactory therefore if there was another application already deployed when trying to do connectivity testing it fails as the lazy mule artifact context cannot initialize the connection provider bean. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13002","07/05/2017 20:11:20",8,"Move/migrate uses of component to compatibility module ""This is to move and it's dependencies like: - <*-entry-point-resolver> - // This one may require integration the new spring module - - - etc. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13003","07/05/2017 20:34:55",2,"Review mutability of Authentication object ""Authentication object is now being exposed through DW (MULE-12226). But this object is still mutable. It should be reviewed the possibility of making it immutable""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13008","07/06/2017 17:43:58",1,"Review ""catch all"" policy in error handlers considering source errors ""SOURCE_RESPONSE typed errors (including children) are not handleable by on-error-continue, which sort of makes them non """"catch all"""". This means that if an empty handler is defined (catch ANY) some types won't be handled. We may need to consider adding a propagate in those cases or check whether that is working already since ANY is injected.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13009","07/06/2017 17:54:21",8,"Inconsistent error propagation in extension operations depending on operation type ""Inconsistent error propagation in extension operations depending on operation type. In order for tests to pass the following is required to maintain a difference in behaviour between blocking an non-blocking operations. Need to work out what correct behaviour is and update tests etc.   """," OperationMessageProcessor: return doProcess(operationEvent, operationContext) .onErrorMap(e -> !(e instanceof MessagingException), e -> { // MULE-13009 Inconsistent error propagation in extension operations depending on operation type if (operationModel.isBlocking()) { return new MessagingException(event, e); } else { return new MessagingException(event, e, this); } }); ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13010","07/06/2017 18:00:23",8,"SDK should no longer deal in terms of Attributes ""At some point, the Mule Message was composed by a payload TypeValue and Attributes pojo. The Attributes pojo then got replaced by another TypedValue, but the SDK didn't follow.   We need to align these things and potentially kill the Attributes pojo ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13011","07/07/2017 15:23:16",0,"Add privileged API for plugin artifacts ""There are scenarios, where a plugin A must be extended on another plugin B, and to be able to do it, iB must use some A classes that makes no sense to be available on the A's public API. To avoid exposing those classes, will be better to have a privileged API that the plugin A can define to enable extension on those scenarios. Similar to what is supported on container's modules.""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13015","07/07/2017 18:23:41",2,"Move CE distributions out of the mule project ""Move CE distributions to a new mule-distributions project""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13016","07/07/2017 18:42:01",1,"Fix scheduler polling tests ""Fix the polling scheduler tests""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13017","07/07/2017 18:42:42",2,"Tooling Runtime Client should allow to use an Executor to control threads ""Clients of Tooling Runtime should be able to provide an executor service to control threads and allow them to track logs by using ThreadLocal variables as many frameworks do.  ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13021","07/07/2017 21:17:01",0,"ModuleException message is lost ""ModuleException has a couple of constructors that take a message meant to override the cause exception one yet when reaching the ModuleExceptionHandler the ModuleException is unwrapped and that message is lost.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13024","07/10/2017 17:42:48",8,"Review and fix the list of exported packages for Mule Extensions API ""*Review and fix the list of exported packages for Mule Extensions API* Configuring the Maven plugin that checks the exported packages the analysis throws the following report: To configure the Maven Plugin in Mule Extensions API add the following plugin in each module of Ext API: """," [INFO] Following packages were not analyzed: org.mule.runtime.extension.api.type org.mule.runtime.extension.api.dsl.model org.mule.runtime.extension.api.dsl org.mule.runtime.extension.api.declaration.spi org.mule.runtime.extension.api.declaration org.mule.runtime.extension.api.dsl.converter org.mule.runtime.extension.api.model.property org.mule.runtime.extension.api.annotation.capability [INFO] Packages that must be exported: org.mule.runtime.extension.internal.util org.reactivestreams org.mule.metadata.java.api.handler org.mule.metadata.java.internal.handler org.mule.tools.maven mule-module-maven-plugin ${muleModuleMavenPluginVersion} analyze verify analyze ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13025","07/10/2017 20:17:40",1,"Enable Test Connectivity on SOAP connectors ""SOAP Connect connectors do not support Test Connectivity. We need to have it so we can offer the same features Mule 3 connectors had.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13028","07/11/2017 09:42:40",8,"All routers should use processor chains rather than processors as their routes ""All routers should use processor chains rather than processors as their routes""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13029","07/11/2017 16:06:47",8,"Expose the Event in NestedProcessor process result in privileged API ""Expose the Event in NestedProcessor process result in privileged API""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13030","07/11/2017 16:39:45",1,"Possible deadlock in RegionClassLoader ""While working on another task, i stumbled upon the following deadlock:  RegionClassLoader shouldn't be calling *getClassLoadingLock* since it doesn't do the actual class load (it is delegated). Also, the loading of the class is not protected from changes in the inner state from calls to *addClassLoader* or *removeClassLoader*, so a ReadWriteLock should be a better option for this case."""," Found one Java-level deadlock: ============================= """"Log4j2-TF-1-AsyncLoggerConfig-6"""": waiting to lock monitor 0x00007fc47c5628f8 (object 0x00000007461c0f98, a org.mule.runtime.deployment.model.internal.application.MuleApplicationClassLoader), which is held by """"[MuleRuntime].io.07"""" """"[MuleRuntime].io.07"""": waiting to lock monitor 0x00007fc47c562798 (object 0x00000007461c1018, a org.mule.runtime.module.artifact.classloader.RegionClassLoader), which is held by """"Log4j2-TF-1-AsyncLoggerConfig-6"""" Java stack information for the threads listed above: =================================================== """"Log4j2-TF-1-AsyncLoggerConfig-6"""": at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.findLocalClass(FineGrainedControlClassLoader.java:163) - waiting to lock <0x00000007461c0f98> (a org.mule.runtime.deployment.model.internal.application.MuleApplicationClassLoader) at org.mule.runtime.module.artifact.classloader.RegionClassLoader.findLocalClass(RegionClassLoader.java:182) - locked <0x00000007461c1018> (a org.mule.runtime.module.artifact.classloader.RegionClassLoader) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:86) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.findParentClass(FineGrainedControlClassLoader.java:135) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:89) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.apache.logging.log4j.core.impl.ThrowableProxy.loadClass(ThrowableProxy.java:563) at org.apache.logging.log4j.core.impl.ThrowableProxy.toExtendedStackTrace(ThrowableProxy.java:689) at org.apache.logging.log4j.core.impl.ThrowableProxy.(ThrowableProxy.java:164) at org.apache.logging.log4j.core.impl.ThrowableProxy.(ThrowableProxy.java:141) at org.apache.logging.log4j.core.impl.ThrowableProxy.(ThrowableProxy.java:122) at org.apache.logging.log4j.core.impl.Log4jLogEvent.getThrownProxy(Log4jLogEvent.java:564) at org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverter.format(ExtendedThrowablePatternConverter.java:63) at org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:38) at org.apache.logging.log4j.core.layout.PatternLayout$PatternSerializer.toSerializable(PatternLayout.java:333) at org.apache.logging.log4j.core.layout.PatternLayout.toText(PatternLayout.java:232) at org.apache.logging.log4j.core.layout.PatternLayout.encode(PatternLayout.java:217) at org.apache.logging.log4j.core.layout.PatternLayout.encode(PatternLayout.java:57) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.directEncodeEvent(AbstractOutputStreamAppender.java:177) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.tryAppend(AbstractOutputStreamAppender.java:170) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:161) at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156) at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:129) at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:120) at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84) at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:448) at org.apache.logging.log4j.core.async.AsyncLoggerConfig.asyncCallAppenders(AsyncLoggerConfig.java:115) at org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:112) at org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:98) at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) """"[MuleRuntime].io.07"""": at org.mule.runtime.module.artifact.classloader.RegionClassLoader.findLocalClass(RegionClassLoader.java:176) - waiting to lock <0x00000007461c1018> (a org.mule.runtime.module.artifact.classloader.RegionClassLoader) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:86) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.findParentClass(FineGrainedControlClassLoader.java:135) at org.mule.runtime.module.artifact.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:89) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at org.mule.mvel2.optimizers.AbstractOptimizer.forNameWithInner(AbstractOptimizer.java:167) at org.mule.mvel2.optimizers.AbstractOptimizer.tryStaticAccess(AbstractOptimizer.java:80) at org.mule.mvel2.compiler.PropertyVerifier.getBeanProperty(PropertyVerifier.java:260) at org.mule.mvel2.compiler.PropertyVerifier.analyze(PropertyVerifier.java:117) at org.mule.mvel2.compiler.ExpressionCompiler.verify(ExpressionCompiler.java:396) at org.mule.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:284) at org.mule.mvel2.compiler.ExpressionCompiler.compile(ExpressionCompiler.java:63) at org.mule.mvel2.MVEL.compileExpression(MVEL.java:821) at org.mule.runtime.core.el.mvel.MVELExpressionExecutor$1.load(MVELExpressionExecutor.java:59) at org.mule.runtime.core.el.mvel.MVELExpressionExecutor$1.load(MVELExpressionExecutor.java:55) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3527) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2319) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2282) - locked <0x000000079af82410> (a com.google.common.cache.LocalCache$StrongAccessEntry) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2197) at com.google.common.cache.LocalCache.get(LocalCache.java:3937) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3941) at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4824) at com.google.common.cache.LocalCache$LocalLoadingCache.getUnchecked(LocalCache.java:4830) at org.mule.runtime.core.el.mvel.MVELExpressionExecutor.getCompiledExpression(MVELExpressionExecutor.java:94) at org.mule.runtime.core.el.mvel.MVELExpressionExecutor.validate(MVELExpressionExecutor.java:83) at org.mule.runtime.core.el.mvel.MVELExpressionLanguage.validate(MVELExpressionLanguage.java:258) at org.mule.runtime.core.el.mvel.MVELExpressionLanguage.evaluateInternal(MVELExpressionLanguage.java:237) at org.mule.runtime.core.el.mvel.MVELExpressionLanguage.evaluateUntyped(MVELExpressionLanguage.java:147) at org.mule.runtime.core.el.mvel.MVELExpressionLanguage.evaluate(MVELExpressionLanguage.java:224) at org.mule.runtime.core.el.mvel.MVELExpressionLanguage.evaluate(MVELExpressionLanguage.java:213) at org.mule.runtime.core.el.mvel.MVELExpressionLanguage.evaluate(MVELExpressionLanguage.java:208) at org.mule.runtime.core.el.ExpressionLanguageAdaptorHandler.evaluate(ExpressionLanguageAdaptorHandler.java:87) at org.mule.runtime.core.el.DefaultExpressionManager.evaluate(DefaultExpressionManager.java:155) at org.mule.runtime.core.el.DefaultExpressionManager.evaluate(DefaultExpressionManager.java:148) at org.mule.runtime.core.api.util.AttributeEvaluator.lambda$new$0(AttributeEvaluator.java:69) at org.mule.runtime.core.api.util.AttributeEvaluator$$Lambda$1521/1085497935.apply(Unknown Source) at org.mule.runtime.core.api.util.AttributeEvaluator.resolveTypedValue(AttributeEvaluator.java:115) at org.mule.runtime.module.extension.internal.runtime.resolver.ExpressionValueResolver.resolve(ExpressionValueResolver.java:69) at org.mule.runtime.module.extension.internal.runtime.resolver.TypeSafeValueResolverWrapper.lambda$initialise$0(TypeSafeValueResolverWrapper.java:57) at org.mule.runtime.module.extension.internal.runtime.resolver.TypeSafeValueResolverWrapper$$Lambda$1509/870463738.resolve(Unknown Source) at org.mule.runtime.module.extension.internal.runtime.resolver.TypeSafeValueResolverWrapper.resolve(TypeSafeValueResolverWrapper.java:45) at org.mule.runtime.module.extension.internal.runtime.resolver.TypeSafeExpressionValueResolver.resolve(TypeSafeExpressionValueResolver.java:57) at org.mule.runtime.module.extension.internal.runtime.objectbuilder.DefaultObjectBuilder.resolve(DefaultObjectBuilder.java:87) at org.mule.runtime.module.extension.internal.runtime.objectbuilder.DefaultObjectBuilder.build(DefaultObjectBuilder.java:80) at org.mule.runtime.module.extension.internal.runtime.resolver.ObjectBuilderValueResolver.resolve(ObjectBuilderValueResolver.java:48) at org.mule.runtime.module.extension.internal.runtime.resolver.ResolverSet.resolveValue(ResolverSet.java:108) at org.mule.runtime.module.extension.internal.runtime.resolver.ResolverSet.resolve(ResolverSet.java:100) at org.mule.runtime.module.extension.internal.runtime.source.SourceAdapter$DefaultSourceCompletionHandler.createResponseParameters(SourceAdapter.java:198) at org.mule.runtime.module.extension.internal.runtime.source.ModuleFlowProcessingTemplate.lambda$getSuccessfulExecutionResponseParametersFunction$0(ModuleFlowProcessingTemplate.java:45) at org.mule.runtime.module.extension.internal.runtime.source.ModuleFlowProcessingTemplate$$Lambda$1746/874365794.applyChecked(Unknown Source) at org.mule.runtime.core.api.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.internal.policy.DefaultPolicyManager.lambda$null$0(DefaultPolicyManager.java:78) at org.mule.runtime.core.internal.policy.DefaultPolicyManager$$Lambda$1743/207924922.get(Unknown Source) at org.mule.runtime.core.internal.execution.ModuleFlowProcessingPhase.lambda$policySuccess$7(ModuleFlowProcessingPhase.java:161) at org.mule.runtime.core.internal.execution.ModuleFlowProcessingPhase$$Lambda$1745/1585407947.apply(Unknown Source) at org.mule.runtime.core.api.functional.Either.reduce(Either.java:72) at org.mule.runtime.core.internal.execution.ModuleFlowProcessingPhase.lambda$runPhase$1(ModuleFlowProcessingPhase.java:131) at org.mule.runtime.core.internal.execution.ModuleFlowProcessingPhase$$Lambda$1657/1825729859.apply(Unknown Source) at reactor.core.publisher.MonoThenMap$ThenMapMain.onNext(MonoThenMap.java:120) at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:962) at reactor.core.publisher.MonoThenMap$ThenMapMain$ThenMapInner.onNext(MonoThenMap.java:237) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:108) at reactor.core.publisher.FluxDefaultIfEmpty$DefaultIfEmptySubscriber.onNext(FluxDefaultIfEmpty.java:92) at reactor.core.publisher.FluxHide$SuppressFuseableSubscriber.onNext(FluxHide.java:127) at reactor.core.publisher.FluxSwitchIfEmpty$SwitchIfEmptySubscriber.onNext(FluxSwitchIfEmpty.java:67) at reactor.core.publisher.MonoNext$NextSubscriber.onNext(MonoNext.java:76) at reactor.core.publisher.FluxFlatMap$FlatMapMain.drainLoop(FluxFlatMap.java:612) at reactor.core.publisher.FluxFlatMap$FlatMapMain.drain(FluxFlatMap.java:491) at reactor.core.publisher.FluxFlatMap$FlatMapInner.onNext(FluxFlatMap.java:916) at reactor.core.publisher.FluxReplay$SizeBoundReplayBuffer.replayFused(FluxReplay.java:836) at reactor.core.publisher.FluxReplay$SizeBoundReplayBuffer.replay(FluxReplay.java:866) at reactor.core.publisher.ReplayProcessor.onNext(ReplayProcessor.java:523) at reactor.core.publisher.MonoProcessor.drainLoop(MonoProcessor.java:473) at reactor.core.publisher.MonoProcessor.onNext(MonoProcessor.java:321) at org.mule.runtime.core.AbstractEventContext.success(AbstractEventContext.java:124) - locked <0x00000007991e0980> (a org.mule.runtime.core.DefaultEventContext) at org.mule.runtime.core.internal.construct.AbstractPipeline.lambda$null$1(AbstractPipeline.java:209) at org.mule.runtime.core.internal.construct.AbstractPipeline$$Lambda$1701/1384125150.accept(Unknown Source) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:165) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerNext(FluxConcatMap.java:272) at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onNext(FluxConcatMap.java:782) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:108) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerNext(FluxConcatMap.java:272) at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onNext(FluxConcatMap.java:782) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:108) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onNext(FluxHandleFuseable.java:150) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxJust$WeakScalarSubscription.request(FluxJust.java:90) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.request(FluxHandleFuseable.java:208) at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:1482) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onSubscribe(FluxOnErrorResume.java:67) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onSubscribe(FluxHandleFuseable.java:126) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxHandleFuseable.subscribe(FluxHandleFuseable.java:64) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onNext(FluxConcatMap.java:242) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerNext(FluxConcatMap.java:272) at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onNext(FluxConcatMap.java:782) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:108) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onNext(FluxHandleFuseable.java:150) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxJust$WeakScalarSubscription.request(FluxJust.java:90) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.request(FluxHandleFuseable.java:208) at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:1482) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onSubscribe(FluxOnErrorResume.java:67) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onSubscribe(FluxHandleFuseable.java:126) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxHandleFuseable.subscribe(FluxHandleFuseable.java:64) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onNext(FluxConcatMap.java:242) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerNext(FluxConcatMap.java:272) at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onNext(FluxConcatMap.java:782) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:108) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:173) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:72) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onNext(FluxHandleFuseable.java:150) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:428) at reactor.core.publisher.FluxJust$WeakScalarSubscription.request(FluxJust.java:90) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.request(FluxPeekFuseable.java:371) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.request(FluxHandleFuseable.java:208) at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:1482) at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onSubscribe(FluxOnErrorResume.java:67) at reactor.core.publisher.FluxHandleFuseable$HandleFuseableSubscriber.onSubscribe(FluxHandleFuseable.java:126) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onSubscribe(FluxPeekFuseable.java:404) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:82) at reactor.core.publisher.FluxHandleFuseable.subscribe(FluxHandleFuseable.java:64) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onSubscribe(FluxConcatMap.java:212) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onSubscribe(FluxPeekFuseable.java:164) at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onSubscribe(FluxPeekFuseable.java:164) at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:67) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:86) at reactor.core.publisher.FluxPeekFuseable.subscribe(FluxPeekFuseable.java:86) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:117) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:82) at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxOnErrorResume.subscribe(FluxOnErrorResume.java:46) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:416) at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onNext(FluxConcatMap.java:236) at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.runBackfused(FluxPublishOn.java:431) at reactor.core.publisher.FluxPublishOn$PublishOnSubscriber.run(FluxPublishOn.java:472) at reactor.core.scheduler.ExecutorServiceScheduler$ExecutorServiceSchedulerRunnable.run(ExecutorServiceScheduler.java:325) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.mule.service.scheduler.internal.AbstractRunnableFutureDecorator.doRun(AbstractRunnableFutureDecorator.java:88) at org.mule.service.scheduler.internal.RunnableFutureDecorator.run(RunnableFutureDecorator.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Found 1 deadlock. ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13031","07/11/2017 16:47:36",0,"Move HTTP test from integrations to connector ""It's getting really difficult to change HTTP related code because one has to change the connector AND integrations since the tests are mostly there. The tests were separated at one point because it was an OSGI thing but now it's no longer necessary. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13032","07/11/2017 16:52:12",8,"Review all interfaces builders to match DW standard ""DW will now instantiate interfaces through a static builder() method. We need to decide and make sure all builders follow the same standard.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13037","07/11/2017 21:03:05",3,"Make TLS inside POJOs work the same as parameter ""Right now, mule-oauth-module is using the TLS inside a POJO, but the parameter model generated is not marked as an infrastructure parameter and because of that the DSLSyntax information is completely wrong.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13041","07/12/2017 17:39:28",8,"Allow non-repeatable streams to be registered for closure when Flow completes ""Allow non-repeatable streams to be registered for closure when Flow completes""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13051","07/13/2017 04:19:49",2,"Disable statistics when deploying a Tooling application ""When deploying an application for Tooling it no needed to have statistics enabled, this can be disabled from MuleContext.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13052","07/13/2017 11:26:59",8,"Migrate Splitter and Foreach implementation to non-blocking ""Migrate Splitter and Foreach implementation to non-blocking""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13059","07/13/2017 20:54:50",8,"Update Extension DTO to support missing features ""*Update Extension DTO to support missing features* * Element References * Path * Whatever""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13060","07/13/2017 20:56:37",0,"Upgrade Allure report framework ""Upgrade Allure framework to latest version""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13063","07/14/2017 16:01:46",1,"Schema generation for Enum should rely on name and not in toString values ""Schema generation for Enum should rely on name and not in toString values, so if we have:   \   Then the schema should use consistently """"VALUE"""" as defaultValue and union element instead of mixin """"VALUE"""" and """"Value"""""""," public enum SomeEnum \{  VALUE(""""Value"""")  private String id;   VersioningStatus(String id) \{      this.id = id;    }    public String toString() \{      return id;    } } \",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13064","07/14/2017 16:23:18",1,"Wrong method name in ArtifactArchiveInstaller ""The method _desinstallArtifact_ should be renamed to _uninstallArtifact_ or something similar, but the word desinstall does not exist.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13065","07/14/2017 17:22:23",2,"Privileged API packages must take into account other exported privileged APIs ""If I define in mule-api a package as privileged and then try to use it from mule-core it fails. After discussing this with [~pablokraan] it seems to be a known issue where privileged APIs are not taken into account as the should by the API analyzer.    Searching for this issue ID in the code it will show a TODO with the exported packaged in mule-core that should be exported in mule-api instead.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13067","07/14/2017 19:34:36",0,"Default Oauth2 token expression fails if JSON has multiple lines ""The regex uses hardcoded spaces between parts of the json attributes, but it doesn't work when using \s. A first pass removing all blank characters works, before calling regex().""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13070","07/14/2017 21:19:01",13,"Enrichers are applied in wrong order ""Right now, the Loader's enrichers are executed before the ExtensionModelFactory ones. This should be the other way around. Plus, we also need the concept of POST enrichers, which are enrichers also defined in the ExtensionModelFactory, but which run after the loader enrichers""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13074","07/14/2017 21:23:17",13,"Value Resolvers should stack up ""It's not possible to combine a ParameterResolver with a TypedValue. Although this is just a concrete example which is affecting http and vm connectors, this applies to an infinity of possible combinations. We need to change how we apply resolvers, so that we have one single component which knows how to stack resolvers together.  For example:   ParameterResolver> should resolve to the following chain: valueResolver -> typeValueResolver -> ParameterResolver. In christian, from right to left. There's another case to consider which is annotations such us @DefaultEncoding. For these one we need to think what to do, but I believe they should be applied before the right to left chain is resolved.  ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13088","07/14/2017 22:48:54",2,"Component location not properly computed for ForEach router ""Component location is not being correctly computed... In example: """," ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13090","07/16/2017 03:14:13",1,"ComponentBuildingDefinition for Try is not setting default values for transactionalAction and transactionType ""This is causing an error when resolving metadata for Tooling: """," Failed to resolve dynamic model. component: COMPONENT, element: , code: UNKNOWN - Reason: org.mule.runtime.api.exception.MuleRuntimeException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ErrorHandling': Cannot create inner bean '(inner bean)#12751855' of type [org.mule.runtime.config.spring.factories.TryProcessorFactoryBean$$EnhancerByCGLIB$$c7a14319] while setting bean property 'messageProcessors' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#12751855': FactoryBean threw exception on object creation; nested exception is java.lang.IllegalArgumentException: Action null is not recognised as a begin action.  ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13094","07/17/2017 16:34:24",2,"Embedded Container: If app fails to deploy, trying to deploy same app again ends instantly ""If an app is deployed and fails, (for example due to a missing file referenced in an import). And then you try to deploy the application again (but now we different files), the embedded container ends immediately without deploying the application nor throwing any exception. Not sure exactly where the problem comes from, but it may come in the org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer#deployExplodedArtifact method, specifically when checking isUpdatedZombieArtifact.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13097","07/17/2017 19:26:42",5,"SDK: Inject connection on PagingProvider#close() method ""Currently the connection is not being injected in the PagingProvider#close(), it would be ideal to have it in case the user needs it to perfom something when closing the PagingProvider.  the email connector for example would take advantage of this feature""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13101","07/17/2017 21:42:52",5,"Email connector pop3 does not delete all emails with deleteAfterRetrieve ""Email connector pop3 does not delete all emails with deleteAfterRetrieve""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13102","07/18/2017 03:33:19",8,"Sources transaction support is fundamentally broken ""Right now, Sources can use the @COnnection annotation in order to get a connection, which might be transactional. This has two problems: * Because an established connection is being injected instead of a ConnectionProvider, sources which rely on the listener pattern such as JMS are very difficult to implement. The ones which rely on the consumers pattern such as VM are plain and simply impossible * Also because of this, the transaction is begun once the message is pushed to the flow, but most transactional sources require the transaction to start on the source itself. For example, JMS and VM need the transaction started when the message is polled, not when it's pushed We need to change sources so that they can obtain multiple connections, with transactions begun when necessary  ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13103","07/18/2017 14:59:20",0,"Remove backward compatible method on Tooling API for extension models, DataSense and Metadata ""Once MULE-13044 is done the methods for ExtensionModel, DataSense and Metadata should be removed. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13104","07/18/2017 15:03:07",8,"Rework error handler invocation to be event context based rather than rely on handler propagation ""Rework error handler invocation to be event context based rather than rely on handler propagation""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13106","07/18/2017 16:39:05",8,"Migrate aggregators and resequencer to non-blocking ""Migrate aggregators and resequencer to non-blocking""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13112","07/18/2017 18:11:35",8,"CXF compatibility module does not support DW expressions on properties ""As gateway WSDL proxy I would like to dynamically resolve values for proxy-service configuration properties, like for example: Wsdl function is already registered by GW in the DefaultExpressionManager provided by mule, but proxy-service is initialized in a not DW context aware."""," ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13114","07/18/2017 18:54:00",1,"Add a flag to skipDocumentation generation ""Add a flag to skipDocumentation generation""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13115","07/18/2017 19:11:40",2,"Cannot test connection when using global references inside the config or the connection provider ""When doing a test connection of the HTTP Listener, or the Request, if you configure a global reference to the TLS, the app fails because it cannot find the TLS config in the registry. This applies to any parameter that can be configured as a reference. The following app should have executed the test connection sucessfully yet it fails """," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13119","07/18/2017 19:45:57",2,"Unable to use registered DW functions when extension prefix has dash (-) ""If an extension has a dash in its prefix (in our case munit-tools). When trying to evaluate a DW function registered for that extension (in our case munit-tools::equalTo). The evaluation fails, it tries to evaluate the _munit_ separately from the _tools_ word.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13122","07/18/2017 21:24:20",2,"Allow key parameters not exposed in XML configuration to be configured via system properties ""This is for exceptional cases where these values need to be changes and also to allow tuning and testing, to improve defaults in future versions.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13124","07/18/2017 22:56:25",2,"Hide registry from EL and create function to access beans ""We need to remove the registry functionality from binded server/app and instead provide a function to access the spring beans defined.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13131","07/18/2017 23:38:31",2,"HttpListenerConnectionManager should not used dedicated acceptor thread on hardware with small number of cores ""HttpListenerConnectionManager should not used dedicated acceptor thread on hardware with small number of cores""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13132","07/19/2017 03:22:58",0,"Add support to access privileged API class from test case ""We need to add support for being able to access a privileged API class from our test infrastructure""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13133","07/19/2017 13:37:01",2,"AttributesDefinition for tlsContext for HTTP extension is not setting the referenceSimpleParameter ""When Mule is building the MinimalApplication for Tooling the applicationModel and its componentModels are traversed in order to check the AttributesDefinitions and get which parameter has a reference to another componentModel. When HTTP listener-connection has a tlsContext parameter (not inline declared) the method on AttributeDefinitionVisitor#onReferenceSimpleParameter visitor is not being called therefore the dependencies cannot be inferred.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13143","07/20/2017 15:10:11",1,"Add commons-lang3 dependency to file-commons extension ""commons-lang is used in the toString of FileAttributes, but the dependency is not there. The module compiles because it depends on mule-core, but on runtime that lib is isolated.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13144","07/20/2017 16:11:33",8,"Add targetOutput to all operations in the SDK ""Since most of the time users just want to work with the payload of the returned message by the operations, we need to, by default, assign the payload to the variables and not the whole message. Optionally, the user must be able to set a """"targetValue"""" (other names are welcome) so he can assign the message instead of the payload. Possible values would be MESSAGE and PAYLOAD ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13146","07/20/2017 16:24:24",2,"Review elements in the XML that are intercepting and blacklist them ""We need to go through all the XML components that are intercepting, create a list of them, and plan to upgrade them in GA to not be intercepting. Those components that, by making them not intercepting, would require changes in the XML must be documented so Studio can blacklist them for the RC. This will allow us to do the update in GA of those components without breaking backward compatibility at the XML level. For instance, the splitter element should no longer be intercepting, should be an scope. That would cause the XML to change so we have to add it to the blacklist.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13147","07/20/2017 16:31:32",2,"Avoid having spring-module as privileged plugin ""Temporarilly adding spring-module as privileged enable to provide access to privileged classes. This must be removed and make classes part of the API or avoid to use them from the plugin""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13150","07/20/2017 17:28:35",2,"javax.xml.bind.DatatypeConverterImpl generates a class loader leak when used by plugins ""javax.xml.bind.DatatypeConverterImpl keeps a reference to the application classloader when a plugin used by the application has as compile dependency com.sun.xml.bind:jaxb-impl. We should find a way to avoid this, one approach could be to load the class when Mule initialized and use the System ClassLoader.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13151","07/20/2017 17:36:56",8,"Tooling should allow access the application class loader to resolve resources ""For DataSense and also for configuration properties Tooling would need to load the Application classloader.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13158","07/21/2017 16:41:09",1,"File: Improve workingDir parameter definition ""Currently, when configuring the File extension connection provider, the working directory is not marked with @Path annotation, making it show just as a string field editor. The Javadoc has the information that when it is not configured the user.home will be used, but since the parameter has a @Summary, this information is lost. Please, update the @Summary to contains this information.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13160","07/21/2017 18:27:16",8,"CleanUp ObjectStore API ""ObjectStore API as inherited from 3.x is a mess: * ObjectStoreManager * ListableObjectStore * User ObjectStore * Constants hell * Unclear extension path All of the following need to be address or simply removed.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13161","07/21/2017 21:44:17",3,"Extension Documentation Generator does not document configless operations ""Extension Documentation Generator does not document configless operations""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13164","07/23/2017 23:21:59",2," Inconsistent null return from one-way VM inbound endpoint. ""When there is no error, a one-way vm inbound endpoint returns null, but in the case of an handled error it returns the message.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13172","07/24/2017 17:09:14",5,"WSC should not use MultiPartPayload anymore ""MultipartPayload -> don't""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13175","07/24/2017 19:59:07",1,"Upgrade ahc and grizzly to 1.13 and 2.3.31 respectively ""Upgrade ahc and grizzly to 1.13 and 2.3.31 respectively""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13180","07/25/2017 01:21:53",3,"Migrate code to use new cursor stream provider mechanism ""ManagedCursorStreamProvider does not implement InputStream yet there is still code in Mule, including in org.mule.extension.http.internal.listener.HttpResponseFactory#create and potentially elsewhere that depends on InputStream instanceof test to determine behaviour. Fixed on HTTP but still other components could have this problem.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13181","07/25/2017 10:08:32",2,"Differentiate between end-to-end and hop-by-hop headers in Http Attributes to avoid user needing to filter manually ""Not differentiating between these forcing the user, who may not have the required knowledge to filter headers within the flow. This would be much simplified if we had getHeaders() getAllHeaders() getHeaders should not included: - Connection - Keep-Alive - Public - Proxy-Authenticate - Transfer-Encoding - Upgrade - Content-Length (spec doesn't dictate this, but this cannot be conserved and Mule may mutate payload invalidating value, so best not to ever propagate).""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13182","07/25/2017 10:39:14",2,"Remove failureExpression attribute from routers that currently support it ""Remove failureExpression attribute from routers that currently support it""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13184","07/25/2017 14:25:08",2,"Validate ""name"" is not used as a parameter model name ""Currently, it is possible to declare a """"name"""" parameter model in a config using the fluent API. The user can generate the model and no errors will be shown even when running the mule app, but since the convention is that all global elements have a name parameter model by default, they should not be allowed to add it, as the tools already consuming the model are already adding it. Spring module is creating such an extension model.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13187","07/25/2017 19:33:54",3,"ArtifactSerializationService is failing to handle custom parameters in flow tags ""When defining an artifactDeclaration with custom parameters in a flow declaration (at flow level), the ArtifactSerializationService is failing to serialize the custom parameters in the xml.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13188","07/25/2017 20:34:00",13,"ValueProviderService creates a connection although this may not be required ""*ValueProviderService creates a connection although this may not be required* * This happens because the LazyValueProviderService relies on the {{LazyMuleArtifactContext}} to initialize just the components that are required, but the problem is that the whole dependency graph is resolved for a component. * Email case, we need just to initialize the {{email:send}} operation, not the connection or configuration, because these are not used and the resolution could fail if the configuration is not created correctly. * Also, this will be a blocker for WSC because the value provider works in the ConnectionProvider, so when {{LazyMuleArtifactContext}} tries to resolve a value, it will try to start the connection, which will lead to a resolving failure because the connection provider won't have required values.uuiu""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13189","07/25/2017 21:35:22",0,"EL returns String instead of Enum instance when accessing a variable ""When evaluating `vars.initialHealth` in Heisenberg extension tests, DW is returning the String of that Enum, """"CANCER"""" instead of the Enum instanced bound. As a result, if the String is, as originally, """"Cancer"""" you will get a transformation error because the StringToEnum transformer cannot handle it. DW should simply return the Enum. To reproduce, change the `HealthStatus` Enum ids to lower case and run `org.mule.test.module.extension.config.ParameterizedConfigParserTestCase`.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13192","07/26/2017 11:35:44",1,"Remove global processor-chain ""Remove global processor-chain. This has been deprecated since 3.2.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13196","07/26/2017 15:25:17",0,"Classloader issue with metadata propagation ""Whenever you propagation is executed in Studio, you get a classloader issue because of some dom classes: """," !MESSAGE An internal error occurred during: """"Resolving metadata propagation..."""". !STACK 0 java.lang.NoClassDefFoundError: org/w3c/dom/ElementTraversal at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:760) at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:273) at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:632) at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:586) at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:538) at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:525) at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:345) at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:423) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.apache.xerces.parsers.AbstractDOMParser.startDocument(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.startDocument(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl.startEntity(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.startDocumentParsing(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:76) at org.mule.runtime.config.spring.MuleDocumentLoader.loadDocument(MuleDocumentLoader.java:82) at org.mule.datasense.api.metadataprovider.XmlConfigurationDocumentLoader.loadDocument(XmlConfigurationDocumentLoader.java:20) at org.mule.tooling.client.internal.BaseApplicationModelFactory.lambda$loadConfigFile$1(BaseApplicationModelFactory.java:84) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:199) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:840) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:806) at org.mule.tooling.client.internal.BaseApplicationModelFactory.loadConfigFile(BaseApplicationModelFactory.java:76) at org.mule.tooling.client.internal.ApplicationModelFactoryFromExpandedFolder.lambda$readConfigs$2(ApplicationModelFactoryFromExpandedFolder.java:100) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) at org.mule.tooling.client.internal.ApplicationModelFactoryFromExpandedFolder.readConfigs(ApplicationModelFactoryFromExpandedFolder.java:105) at org.mule.tooling.client.internal.ApplicationModelFactoryFromExpandedFolder.lambda$processAppLocation$3(ApplicationModelFactoryFromExpandedFolder.java:114) at java.util.Optional.map(Optional.java:215) at org.mule.tooling.client.internal.ApplicationModelFactoryFromExpandedFolder.processAppLocation(ApplicationModelFactoryFromExpandedFolder.java:114) at org.mule.tooling.client.internal.ApplicationModelFactoryFromExpandedFolder.createApplicationModel(ApplicationModelFactoryFromExpandedFolder.java:61) at org.mule.tooling.client.internal.DefaultDataSenseService.getApplicationModel(DefaultDataSenseService.java:228) at org.mule.tooling.client.internal.DefaultDataSenseService.lambda$internalResolveDataSense$3(DefaultDataSenseService.java:252) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1582) at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) Caused by: java.lang.ClassNotFoundException: org.w3c.dom.ElementTraversal cannot be found by org.mule.tooling.mule.dependencies_7.0.0.qualifier at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 53 more ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13198","07/26/2017 17:38:02",5,"FTP list content is empty after first read ""If the cursor for a given file is opened and consumed, next time is opened the content results empty. Attaching a test that reproduce this in MULE-13198 for ftp connector. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13204","07/27/2017 12:42:51",2,"Remove dom4j and jaxen exported packages from core libs ""Remove the following packages from the exported packages list: * org.dom4j.rule * org.dom4j * org.dom4j.tree * org.jaxen * org.jaxen.expr * org.jaxen.expr.iter * org.jaxen.saxpath The are exported by spring/extensions support""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13209","07/27/2017 17:23:57",2,"Cleanup scatter-gather configuration ""1) Use (also make changes to first-successful) 2) Don't allow individual processors 3) Remove parallel attribute. 4) Remove custom aggregation strategy 5) Move AggregationStrategy out of API if required.""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13211","07/27/2017 19:27:24",1,"Correlation information is not exposed in the interception API. ""From the debugger side we use the correlation id to switch between debugging contexts when there is more than one message going through the flow. Right now the InterceptionEvent does not expose that information.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13212","07/27/2017 21:15:45",2,"Move GroupCorrelation to Message ""When dealing with collections of messages that have been aggregated in a foreach of scatter-gather router it is important to be able to identify which message is which, in terms of which part it corresponds to or which route it is a result of. Sometimes it may be possible to aggregate into a List and use the index, but this is not a robust solution as when there are errors, the success list won't including a result for each input message, and if the results need to be streamed or processed unordered then this approach is not possible. The solution is to more GroupCorrelation to Message, such that when Messages are aggregated and then processed (for example for custom merging of results in DW), the messages can be accessed by sequence number or an optional label. Also: - Add Optional label. - Make Sequence not-optional.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13213","07/27/2017 22:18:48",2,"Remove redundant component path element in routers that now use ""Remove redundant component path element in routers that now use ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13215","07/28/2017 14:49:45",8,"Define ForkJoinStrategy API and implement must-have strategies for RC ""Define AggregationStrategy API and implement must-have strategies for RC - legacy - join - collect (only limited functionality)""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13216","07/28/2017 14:51:56",8,"Rework scatter-gather to be non-blocking and use ForkJoinStrategy API ""Rework to be non-blocking and use aggregation API""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13217","07/28/2017 14:52:37",8,"Rework foreach to be non-blocking and decoupled from splitter ""Rework foreach to be non-blocking and use aggregation API""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13223","07/30/2017 23:11:20",2,"MultiMap simple selector is not consistent with DW ""When multiple values are available for a key, MultiMap currently returns the last value. This is inconsistent with DataWeave where the first value is the one returned. We need to make them consistent since most of the time MultiMap will be access through DataWeave the simple selector will work differently than in all other scenarios.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13224","07/31/2017 14:03:41",2,"Remove script transformer and use script component instead ""Scripting plugin was added as privileged in order to provide access to privileged transformer classes as the plugin provide scripting transformer that requires access to it. Scripting transformer must be removed and usages replaced by scripting component, after that, the scripting plugin can be removed from the privileged API  ""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13225","07/31/2017 15:45:51",2,"Add required product type property in mule-artifact.json file ""We need a property in mule-artifact.properties that let us decide what is the required product type (CE, EE) to run an artifact.  This cannot be done through dependencies since the application may be using the ee namespace which does not require any particular dependency in the pom file. So the idea is to add a field in mule-artifact.properties of the artifact to define the required feature, CE or EE Mule Runtime. This can be used by MUnit, Studio to run the application using the appropriate runtime.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13228","07/31/2017 18:32:32",5,"Expose source's config and connection parameters ""Our use case is to be able to retrieve path, protocol, host and port of a HTTP Listener. - Part of the path of the HTTP Listener is defined as a parameter of the source. This can be achieved since MULE-11955. - Base path (the remaining part of the path) is defined as a parameter of the source's config. - Host, protocol, and port are defined as parameters of the config's connection. So, we need a way to access the last two groups of parameters: parameters of the configuration and parameters of the connection""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13230","07/31/2017 21:32:04",1,"MetadataOutputDelegate generating metadata type with wrong type annotation ""  When using sql connector, select operation to retrieve array of resulting records... Expected payload metadatype was: But it generates... """," %type _:Java = @typeId(""""value"""" : """"org.mule.runtime.api.message.Message"""") { """"payload"""" : [@typeId(""""value"""" : """"recordModel"""") { """"PICTURE""""? : @typeId(""""value"""" : """"java.sql.Blob"""") @classInformation(""""hasDefaultConstructor"""" : false, """"isInterface"""" : true, """"isInstantiable"""" : false, """"isAbstract"""" : true, """"isFinal"""" : false, """"implementedInterfaces"""" : [], """"parent"""" : """""""", """"genericTypes"""" : []) @typeAlias(""""value"""" : """"Blob"""") { } }], """"attributes"""" : Void } %type _:Java = @typeId(""""value"""" : """"org.mule.runtime.api.message.Message"""") { """"payload"""" : @typeId(""""value"""" : """"java.util.Map"""") [@typeId(""""value"""" : """"recordModel"""") { """"PICTURE""""? : @typeId(""""value"""" : """"java.sql.Blob"""") @classInformation(""""hasDefaultConstructor"""" : false, """"isInterface"""" : true, """"isInstantiable"""" : false, """"isAbstract"""" : true, """"isFinal"""" : false, """"implementedInterfaces"""" : [], """"parent"""" : """""""", """"genericTypes"""" : []) @typeAlias(""""value"""" : """"Blob"""") { } }], """"attributes"""" : Void } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13236","08/01/2017 19:27:06",2,"DataSenseService cannot resolve properties in Tooling Client test cases ""Using properties loaded through Spring's {{context:property-placeholder}} the Connectivity test runs OK but the MetaData key test fails: The bug can be reproduced with this project: [connectors-integration-tests|https://github.com/mulesoft-labs/connectors-integration-tests/tree/06f2748665a13ead1a8a3d6ec1a499adce5d6bd8] by running the Salesforce suite: {{mvn clean -Dit.test=SalesforceIT verify}} This is the test code: [SalesforceIT.java|https://github.com/mulesoft-labs/connectors-integration-tests/blob/06f2748665a13ead1a8a3d6ec1a499adce5d6bd8/src/test/java/org/mule/module/netsuite/integration/SalesforceIT.java] This is the test application: [mule-config.xml|https://github.com/mulesoft-labs/connectors-integration-tests/blob/06f2748665a13ead1a8a3d6ec1a499adce5d6bd8/src/test/resources/salesforce-app/mule/mule-config.xml]"""," 15:17:32.477 [Thread-2] DEBUG org.mule.tooling.runtime.process.controller.command.ConsoleMuleCommand - INFO 2017-08-01 15:17:32,422 [qtp1496413775-107] org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication: 15:17:32.477 [Thread-2] DEBUG org.mule.tooling.runtime.process.controller.command.ConsoleMuleCommand - ********************************************************************** 15:17:32.477 [Thread-2] DEBUG org.mule.tooling.runtime.process.controller.command.ConsoleMuleCommand - * Started app 'tooling-aeec7590-76e5-11e7-9f8c-a0cec80751c5' * 15:17:32.477 [Thread-2] DEBUG org.mule.tooling.runtime.process.controller.command.ConsoleMuleCommand - * Application plugins: * 15:17:32.477 [Thread-2] DEBUG org.mule.tooling.runtime.process.controller.command.ConsoleMuleCommand - * - Salesforce * 15:17:32.477 [Thread-2] DEBUG org.mule.tooling.runtime.process.controller.command.ConsoleMuleCommand - * Application libraries: * 15:17:32.478 [Thread-2] DEBUG org.mule.tooling.runtime.process.controller.command.ConsoleMuleCommand - * - classes * 15:17:32.478 [Thread-2] DEBUG org.mule.tooling.runtime.process.controller.command.ConsoleMuleCommand - ********************************************************************** org.mule.tooling.client.api.exception.ToolingException: java.lang.NullPointerException at org.mule.tooling.client.internal.ApplicationModelFactoryFromExpandedFolder.readConfigs(ApplicationModelFactoryFromExpandedFolder.java:103) at org.mule.tooling.client.internal.ApplicationModelFactoryFromExpandedFolder.lambda$processAppLocation$3(ApplicationModelFactoryFromExpandedFolder.java:110) at java.util.Optional.map(Optional.java:215) at org.mule.tooling.client.internal.ApplicationModelFactoryFromExpandedFolder.processAppLocation(ApplicationModelFactoryFromExpandedFolder.java:110) at org.mule.tooling.client.internal.ApplicationModelFactoryFromExpandedFolder.createApplicationModel(ApplicationModelFactoryFromExpandedFolder.java:58) at org.mule.tooling.client.internal.DefaultDataSenseService.getApplicationModel(DefaultDataSenseService.java:227) at org.mule.tooling.client.internal.DefaultDataSenseService.lambda$resolveComponentDataSense$1(DefaultDataSenseService.java:180) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1582) at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) Caused by: java.lang.NullPointerException at java.util.Properties$LineReader.readLine(Properties.java:434) at java.util.Properties.load0(Properties.java:353) at java.util.Properties.load(Properties.java:341) at org.mule.runtime.config.spring.dsl.model.ApplicationModel.configurePropertyPlaceholderResolver(ApplicationModel.java:436) at org.mule.runtime.config.spring.dsl.model.ApplicationModel.(ApplicationModel.java:316) at org.mule.tooling.client.internal.BaseApplicationModelFactory.loadApplicationModel(BaseApplicationModelFactory.java:122) at org.mule.tooling.client.internal.ApplicationModelFactoryFromExpandedFolder.readConfigs(ApplicationModelFactoryFromExpandedFolder.java:92) ... 12 more 15:17:34.557 [main] DEBUG org.mule.tooling.runtime.process.controller.UnixMuleProcessController - Checking if Mule Runtime is running 15:17:34.562 [main] DEBUG org.mule.tooling.runtime.process.controller.UnixMuleProcessController - Stopping Mule Runtime 15:17:34.563 [main] DEBUG org.mule.tooling.runtime.process.controller.UnixMuleProcessController - Destroying service wrapper process ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13237","08/01/2017 20:23:03",5,"Validate that tlsContext is present either as a reference or as a child. ""Right now there is no validation and if you don't configure the tlsContext in the xml, the connector using the tlsContextFactory will throw an NPE.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13244","08/02/2017 21:09:03",8,"Remove the description concept from all annotations ""Annotations such as @Extension should not have a description attribute. Remove and use jdocs instead. Verify that those descriptions are properly obtained""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13245","08/02/2017 21:16:46",8,"Revamp SDK support for validators ""Some extensions such as JSON and XML need to contribute with validators. Need to rethink the overall approach to that so that those validators are consistent across the board""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13247","08/03/2017 00:18:39",8,"Find a way to represent synthethic types ""Right now we don't have a good way to represent synthethic types such as the streaming strategy.  Find the solution which better suites Studio, Flow Designer and is compatible with DW""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13249","08/03/2017 14:13:54",1,"Annotation processor should not reference implementation classes from com.sun ""The  org.mule.runtime.module.extension.internal.capability.xml.schema.ExtensionAnnotationProcessor is making explicit references to com.sun. implementation classes instead of using the interfaces of the annotation processing APIs. This will prevent us from developing any IDE support as it happened with the DevKit plugin in the past. We had to remove all usages of com.sun for it to work. There should be no need to explicitely import the implementations from that specific JDK as everything that is being done can be achieved using the actual APIs provided for processing annotations. Any use of com.sun should not be encouraged and removed.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13254","08/03/2017 16:55:05",2,"Leak resolving metadata on try scope ""When resolving datasense for a processor inside the error handler of a try scope, it fails creating the scope because there are no processors within the try element and the factory bean fails. Since it's during the creation of the component, it never gets created. Later on, no a dispose of the artifact, mule tries to get from the registry all the objects to dispose and it fails again since spring tries to create the singleton object of the try. This error prevents the execution of stop and dispose over the rest of the components leaving threads running with references to the application class loader.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13255","08/03/2017 17:05:38",2,"Invalid versioning for Mule Module Maven Plugin ""The following is scattered all across the uber: org.mule.tools.maven mule-module-maven-plugin $\{muleModuleMavenPluginVersion} The version placeholder is resolved to 1.0-SNAPSHOT but should be 1.0.0-SNAPSHOT""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13259","08/03/2017 17:42:26",2,"Use TypedValue length in HTTP service/connector ""Use TypedValue length in HTTP service/connector""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13264","08/04/2017 16:06:53",2,"Test Runner exposes test resources from plugin classloader ""When running on standalone, Mule doesn't allow to access the application resources from the plugin classloader. However, when using the isolated runner, the lookup in the end falls back ti the surefire classloader, which has access to the test resources and allows to load them. They must be filtered out to emulate the behavior of standalone.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13272","08/04/2017 22:52:28",5,"TargetValue attribute should accept expression ""Remove TargetType enum and accept expression which must be evaluated against a reduced binding context containing message, attributes and payload.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13273","08/06/2017 00:00:39",1,"JMS ActiveMQ brokerUrl is not visible from main view ""JMS ActiveMQ brokerUrl is not visible from main view due to unnecessary dropdowns. Remove invalid options from the connector.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13282","08/07/2017 20:07:34",2,"Add a mechanism from the API to access MetadataService, ConnectivityService and ValueProviderService ""We need to add a mechanism to access those services from the API since we are not exposing them anymore.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13284","08/07/2017 21:04:50",0,"Maven settings proxy and mirror configurations are not considered for resolving dependencies ""When using mule-maven-client to resolve dependencies, the configuration under and in settings.xml is not yet taken into account.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13289","08/09/2017 20:51:42",8,"ConnectivityTesting should not use retry policy ""It should not honor any retry policy when running connectivity testing""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13290","08/09/2017 21:44:10",2,"Extension model is missing types and extensions declare own any ""The extension model is mistakenly declaring certain error types such as critical and missing others. Additionally, every extension is declaring it's own ANY type.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13291","08/09/2017 22:20:11",2,"Implement ""raise-error"" ""We need to create a component to raise errors with a certain ID and message.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13293","08/10/2017 15:49:32",3,"Allow relative path for IdentityFile ""IdentityFiles in src/main/resources are not recognised and will trigger an exception: *Root Exception was: File 'mule_sftp' not found. Type: class java.lang.IllegalArgumentException* {color:#205081}3.8.4{color} {color:#205081}4.0.0-BETA.4{color} """," ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13300","08/10/2017 22:39:10",0,"Transitive dependencies of plugin not resolved ""When the following conditions meet for a mule-plugin: * It depends on another mule-plugin * It depends on another jar * Those both dependencies, in turn, depend an another artifact, the same for both * The dependency of the plugin is declared before the other dependency The classloader for the plugin do not contain the transitive dependecny. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13301","08/11/2017 16:34:07",2,"Remove ignore from MUnitComponentPathTestCase ""Remove ignore from MUnitComponentPathTestCase once MUnit is updated""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13309","08/14/2017 10:22:41",3,"Same error is reported multiple times when compiling an invalid extension ""When compiling an extension with multiple errors (in this case 2) the errors are logged several times. The same message is shown 4 times: - The errors should be shown only once. - WARNINGS: NONE message should not be displayed if there are no warnings. - We shouldn't display WARNINGS using error log level. *Full error log* """," org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: Extension 'MapStringString' has definition errors: ERRORS: * 'configuration' config contains content parameters. Content parameters are not allowed on configuration components * 'connection provider' connection contains content parameters. Content parameters are not allowed on connection provider components WARNINGS: NONE [ERROR] diagnostic: error: org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: Extension 'MapStringString' has definition errors:   ERRORS:       * 'configuration' config contains content parameters. Content parameters are not allowed on configuration components       * 'connection provider' connection contains content parameters. Content parameters are not allowed on connection provider components     WARNINGS: NONE   org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: Extension 'MapStringString' has definition errors:   ERRORS:       * 'configuration' config contains content parameters. Content parameters are not allowed on configuration components       * 'connection provider' connection contains content parameters. Content parameters are not allowed on connection provider components     WARNINGS: NONE   Caused by: org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: Extension 'MapStringString' has definition errors:   ERRORS:       * 'configuration' config contains content parameters. Content parameters are not allowed on configuration components       * 'connection provider' connection contains content parameters. Content parameters are not allowed on connection provider components     WARNINGS: NONE       at org.mule.runtime.extension.internal.loader.ExtensionModelFactory.create(ExtensionModelFactory.java:182)       at org.mule.runtime.extension.api.loader.ExtensionModelLoader.loadExtensionModel(ExtensionModelLoader.java:72)       at org.mule.runtime.module.extension.internal.resources.BaseExtensionResourcesGeneratorAnnotationProcessor.parseExtension(BaseExtensionResourcesGeneratorAnnotationProcessor.java:107)       at org.mule.runtime.module.extension.internal.resources.BaseExtensionResourcesGeneratorAnnotationProcessor.lambda$null$0(BaseExtensionResourcesGeneratorAnnotationProcessor.java:86)       at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:787)       at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:199)       at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:840)       at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:806)       at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:786)       at org.mule.runtime.module.extension.internal.resources.BaseExtensionResourcesGeneratorAnnotationProcessor.lambda$process$1(BaseExtensionResourcesGeneratorAnnotationProcessor.java:85)       at java.util.Optional.ifPresent(Optional.java:159)       at org.mule.runtime.module.extension.internal.resources.BaseExtensionResourcesGeneratorAnnotationProcessor.process(BaseExtensionResourcesGeneratorAnnotationProcessor.java:78)       at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794)       at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705)       at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91)       at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035)       at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176)       at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)       at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856)       at com.sun.tools.javac.main.Main.compile(Main.java:523)       at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129)       at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138)       at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.executeWithExceptionsHandled(AbstractAnnotationProcessorMojo.java:545)       at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.execute(AbstractAnnotationProcessorMojo.java:285)       at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)       at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)       at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)       at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)       at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)       at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)       at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)       at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)       at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)       at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)       at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)       at java.lang.reflect.Method.invoke(Method.java:497)       at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)       at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)       at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)       at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) [ERROR] error on execute: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: Extension 'MapStringString' has definition errors: ERRORS:     * 'configuration' config contains content parameters. Content parameters are not allowed on configuration components     * 'connection provider' connection contains content parameters. Content parameters are not allowed on connection provider components WARNINGS: NONE [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4.085 s [INFO] Finished at: 2017-08-14T11:05:00+02:00 [INFO] Final Memory: 36M/496M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.bsc.maven:maven-processor-plugin:2.2.4:process (process) on project extension-with-map-of-string-string: Error executing: org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.extension.api.exception.IllegalModelDefinitionException: Extension 'MapStringString' has definition errors: [ERROR] ERRORS: [ERROR] * 'configuration' config contains content parameters. Content parameters are not allowed on configuration components [ERROR] * 'connection provider' connection contains content parameters. Content parameters are not allowed on connection provider components [ERROR] [ERROR] WARNINGS: NONE [ERROR] -> [Help 1] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13310","08/14/2017 16:36:27",2,"Fix MessageProcessorNotificationTestCase.firstSuccessful ""After changes in MULE-11553 the post notifications in first-successful are not being sent. If DefaultMessageProcessorChainBuilder.LazyProcessor.apply is comment out, then notifications work. ""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13313","08/14/2017 21:56:21",0,"Dependency resolution for Mule plugins is not honoring semantic versioning on mule-maven-client ""When the following conditions meet for an application: * It depends on a mule-plugin X version 1.0 ** mule-plugin X depends on mule-plugin Z version 1.0 * It depends also on mule-plugin Y version 1.0 ** mule-plugin Y depends on mule-plugin Z version 1.1 * The expected dependency graph for the application should include: ** mule-plugin X version 1.0 ** mule-plugin Y version 1.0 ** mule-plugin Z version 1.1 No matter if the nearest algorithm or the dependency was defined before (in application's pom.xml) the rule for defining conflicts for mule-plugin versions should be by semantic versioning instead of default Maven's rules. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13314","08/15/2017 03:24:09",1,"Wrong DataType set adapting repeatable stream ""When an InputStream is transformed into a CursorStreamProvider, the DataTYpe still says InputStream, which leads to failing transformations""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13317","08/15/2017 17:28:43",0,"Support calling operations defined in the same module ""There should be a way to call operations defined in the same module ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13318","08/15/2017 18:53:42",5,"Name Clash validator doesn't validate clashing between elements ""*Name Clash validator doesn't validate clashing between elements* Cases: * Content parameters and other elements like Operations, Sources, Etc * Content parameters with other elements with childElement support * Operations/Sources/Configurations *  with other elements with childElement support ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13322","08/15/2017 21:16:00",8,"Error type not logged when exception is not ME ""Some code was added to MessagingException to log the error type but it depends on that exception being the one logged. However, the most specific exception is the one logged so often it does not show up. We need to rework it so that it's added as info instead, which is propagated among exceptions when the root is searched for. This is important because it can hint the user regarding errors missing in their handling also help us identify them. To reproduce, run org.mule.test.integration.exceptions.OnErrorContinueTestCase#onErrorTypeMatchSeveral for example and see the logs where MULE:UNKNOWN should be shown.   We should some a way of testing all this. Somehow we should support asserting the message logged when an exception is thrown and also force different exception chains to check logging behaviour."""," ================================================================================ = Testing: onErrorTypeMatchSeveral = ================================================================================ WARN 2017-08-15 17:13:37,437 [Time-limited test] org.mule.runtime.core.api.security.tls.TlsProperties: File tls-default.conf not found, using default configuration. ERROR 2017-08-15 17:13:38,557 [[MuleRuntime].io.05] org.mule.runtime.core.internal.exception.OnErrorContinueHandler: ******************************************************************************** Message : Error. Element : java.lang.Object@555d65c5 @ app (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** ERROR 2017-08-15 17:13:40,580 [[MuleRuntime].io.06] org.mule.runtime.core.internal.exception.OnErrorContinueHandler: ******************************************************************************** Message : Expression """"mel:payload.nope"""" returned null but a value was required. Element : onErrorTypeMatchSeveral/processors/0/route/1/processors/1 @ OnErrorContinueTestCase#onErrorTypeMatchSeveral:null:123 Element XML : (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ********************************************************************************",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13326","08/16/2017 14:02:18",0,"Http non-blocking error handler nor cleaning thread local ""The problem might be caused by a combination of load and theads shortage, which might be causing processes to run on grizzly's timeout thread. The leak itself, as seen from the reports, is the theadlocal of the timeout thread keeping a reference to a MuleEvent.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13359","08/16/2017 16:03:13",5,"WSC: NPE when doing Test Connection ""*Steps to reproduce* # Create a WSC config with the followed settings *WSDL*: http://services.mythicalcorp.com:86/OrderService.svc?wsdl *Service*: service *Port*: BasicHttpBinding_IOrderService # Test Connection *Issue*: The followed NPE is thrown and the test connection fails """," org.mule.runtime.api.exception.MuleRuntimeException: java.lang.RuntimeException: org.mule.runtime.api.lifecycle.LifecycleException: Could not perform connectivity testing for config 'Web_Service_Consumer_Config' org.mule.runtime.api.exception.MuleRuntimeException: java.lang.RuntimeException: org.mule.runtime.api.lifecycle.LifecycleException: Could not perform connectivity testing for config 'Web_Service_Consumer_Config' at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:852) at org.mule.runtime.config.spring.LazyMuleArtifactContext.initializeComponent(LazyMuleArtifactContext.java:121) at org.mule.runtime.config.spring.LazyConnectivityTestingService.testConnection(LazyConnectivityTestingService.java:42) at com.mulesoft.agent.services.tooling.MuleAgentConnectivityTestingService.testConnection(MuleAgentConnectivityTestingService.java:77) at com.mulesoft.agent.external.handlers.tooling.ToolingRequestHandler.lambda$testConnection$7(ToolingRequestHandler.java:319) at com.mulesoft.agent.util.ResponseHelper.response(ResponseHelper.java:88) at com.mulesoft.agent.external.handlers.tooling.ToolingRequestHandler.testConnection(ToolingRequestHandler.java:318) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171) at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:152) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104) at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:387) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:331) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:103) at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:267) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:297) at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:254) at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1028) at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:372) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:381) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:344) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:221) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1515) at com.mulesoft.agent.rest.RequestLoggingFilter.doFilter(RequestLoggingFilter.java:95) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:519) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:138) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:564) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:213) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1097) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:448) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:175) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1031) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:446) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:271) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:246) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: org.mule.runtime.api.lifecycle.LifecycleException: Could not perform connectivity testing for config 'Web_Service_Consumer_Config' at org.mule.runtime.config.spring.LazyMuleArtifactContext.applyLifecycle(LazyMuleArtifactContext.java:100) at org.mule.runtime.config.spring.LazyMuleArtifactContext.createComponents(LazyMuleArtifactContext.java:80) at org.mule.runtime.config.spring.LazyMuleArtifactContext.lambda$initializeComponent$0(LazyMuleArtifactContext.java:129) at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:848) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:867) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) ... 52 more Caused by: org.mule.runtime.api.lifecycle.LifecycleException: Could not perform connectivity testing for config 'Web_Service_Consumer_Config' at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:143) at org.mule.runtime.core.lifecycle.DefaultLifecycleManager.fireStartPhase(DefaultLifecycleManager.java:59) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.lambda$start$4(LifecycleAwareConfigurationProvider.java:105) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:176) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:901) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.start(LifecycleAwareConfigurationProvider.java:104) at org.mule.runtime.core.api.lifecycle.LifecycleUtils.startIfNeeded(LifecycleUtils.java:189) at org.mule.runtime.config.spring.LazyMuleArtifactContext.applyLifecycle(LazyMuleArtifactContext.java:98) ... 59 more Caused by: org.mule.runtime.core.api.DefaultMuleException: Could not perform connectivity testing for config 'Web_Service_Consumer_Config' at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.testConnectivity(LifecycleAwareConfigurationInstance.java:217) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.start(LifecycleAwareConfigurationInstance.java:164) at org.mule.runtime.core.api.lifecycle.LifecycleUtils.startIfNeeded(LifecycleUtils.java:189) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.startConfig(LifecycleAwareConfigurationProvider.java:189) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationProvider.lambda$null$3(LifecycleAwareConfigurationProvider.java:107) at org.mule.runtime.core.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:130) ... 66 more Caused by: org.mule.runtime.core.retry.RetryPolicyExhaustedException: Connectivity test failed for config 'Web_Service_Consumer_Config' at org.mule.runtime.core.retry.policies.AbstractPolicyTemplate.execute(AbstractPolicyTemplate.java:83) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.testConnectivity(LifecycleAwareConfigurationInstance.java:215) ... 71 more Caused by: org.mule.runtime.api.connection.ConnectionException: Connectivity test failed for config 'Web_Service_Consumer_Config' at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance$1.doWork(LifecycleAwareConfigurationInstance.java:193) at org.mule.runtime.core.retry.policies.AbstractPolicyTemplate.execute(AbstractPolicyTemplate.java:57) ... 72 more Caused by: org.mule.runtime.api.connection.ConnectionException: null (java.lang.NullPointerException) at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:63) at org.mule.runtime.core.internal.connection.ErrorTypeHandlerConnectionProviderWrapper.connect(ErrorTypeHandlerConnectionProviderWrapper.java:60) at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:59) at org.mule.runtime.core.internal.connection.LifecycleAwareConnectionProviderWrapper.connect(LifecycleAwareConnectionProviderWrapper.java:61) at org.mule.runtime.core.internal.connection.CachedConnectionHandler.createConnection(CachedConnectionHandler.java:95) at org.mule.runtime.core.internal.connection.CachedConnectionHandler.getConnection(CachedConnectionHandler.java:86) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:163) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.lambda$testConnectivity$1(DefaultConnectionManager.java:146) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.doTestConnectivity(DefaultConnectionManager.java:153) at org.mule.runtime.core.internal.connection.DefaultConnectionManager.testConnectivity(DefaultConnectionManager.java:129) at org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance$1.doWork(LifecycleAwareConfigurationInstance.java:188) ... 73 more Caused by: java.lang.NullPointerException at org.mule.service.soap.introspection.WsdlSchemasCollector.addSchema(WsdlSchemasCollector.java:80) at org.mule.service.soap.introspection.WsdlSchemasCollector.lambda$null$3(WsdlSchemasCollector.java:93) at java.util.Vector.forEach(Vector.java:1249) at org.mule.service.soap.introspection.WsdlSchemasCollector.lambda$addImportedSchemas$4(WsdlSchemasCollector.java:90) at java.util.HashMap$Values.forEach(HashMap.java:980) at org.mule.service.soap.introspection.WsdlSchemasCollector.addImportedSchemas(WsdlSchemasCollector.java:90) at org.mule.service.soap.introspection.WsdlSchemasCollector.addSchema(WsdlSchemasCollector.java:83) at org.mule.service.soap.introspection.WsdlSchemasCollector.lambda$null$3(WsdlSchemasCollector.java:93) at java.util.Vector.forEach(Vector.java:1249) at org.mule.service.soap.introspection.WsdlSchemasCollector.lambda$addImportedSchemas$4(WsdlSchemasCollector.java:90) at java.util.HashMap$Values.forEach(HashMap.java:980) at org.mule.service.soap.introspection.WsdlSchemasCollector.addImportedSchemas(WsdlSchemasCollector.java:90) at org.mule.service.soap.introspection.WsdlSchemasCollector.addSchema(WsdlSchemasCollector.java:83) at org.mule.service.soap.introspection.WsdlSchemasCollector.lambda$collectFromTypes$2(WsdlSchemasCollector.java:73) at java.util.Vector.forEach(Vector.java:1249) at org.mule.service.soap.introspection.WsdlSchemasCollector.collectFromTypes(WsdlSchemasCollector.java:70) at org.mule.service.soap.introspection.WsdlSchemasCollector.collectSchemas(WsdlSchemasCollector.java:60) at org.mule.service.soap.introspection.WsdlSchemasCollector.collect(WsdlSchemasCollector.java:47) at org.mule.service.soap.introspection.WsdlIntrospecter.getSchemas(WsdlIntrospecter.java:157) at org.mule.service.soap.client.SoapCxfClientFactory.create(SoapCxfClientFactory.java:39) at org.mule.extension.ws.internal.connection.SoapClientConnectionProvider.connect(SoapClientConnectionProvider.java:136) at org.mule.extension.ws.internal.connection.SoapClientConnectionProvider.connect(SoapClientConnectionProvider.java:48) at org.mule.runtime.core.internal.connection.ConnectionProviderWrapper.connect(ConnectionProviderWrapper.java:59) ... 83 more ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13329","08/16/2017 17:48:57",5,"WSC fails to resolve metadata for wsdl. ""The provided wsdl contains one operation that throws an exception when resolving metadata for it. Use the attached wsdl with the following configuration: Service: GCS6010CService Port: GCS6010Port Error is: org.mule.runtime.api.metadata.MetadataResolvingException: Could not load part element name [ \{http://www.GCS6010CO.com/schemas/GCS6010COInterface} GCS6010CDATA] ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0 +"MULE-13332","08/17/2017 04:36:43",1,"ERR_INVALID_RESPONSE when using HTTP listener an a DW transformation that has errors ""Provided configuration has an HTTP listener (GET) and does a transformation, it is expecting to get a query parameter and if users don't pass this param the script fails but the response cannot be interpreted by browser as it has the following content: Headers: This in Google Chrome ends up with a page saying that ERR_INVALID_RESPONSE which is very annoying. Seems that content-type: application/java is causing this issue, wondering if there is a better way to handle it."""," """"4| {""""msg"""":""""Hello """" ++ attributes.queryParams.name ++ """" how are you doing today?""""} ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ You called the function '++' with these arguments: 1: String (""""Hello """") 2: Null (null) But it expects one of these combinations: (Array, Array) (Date, Time) (Date, LocalTime) (Date, TimeZone) (LocalDateTime, TimeZone) (LocalTime, Date) (LocalTime, TimeZone) (Object, Object) (String, String) (Time, Date) (TimeZone, LocalDateTime) (TimeZone, Date) (TimeZone, LocalTime) Trace: at '++' in (anonymous:4:17) at '++' in (anonymous:4:48) at 'main' in (anonymous:4:1)"""" evaluating expression: """"%dw 2.0 output application/json --- {""""msg"""":""""Hello """" ++ attributes.queryParams.name ++ """" how are you doing today?""""}"""". 500 Server Error connection →close content-length →781 content-type →application/java; charset=UTF-8 date →Wed, 16 Aug 2017 23:29:40 GMT",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13334","08/17/2017 13:14:50",2,"Log entry for source errors does not show the location of the failing source ""When the MessagingException for a source error is created, it should pass along the failing source, so it is properly appended to the log for troubleshootung.   Currenty it shos just *Element: null*""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13336","08/17/2017 15:26:18",1,"Update Grizzly to version 2.3.33 ""We need to update the Grizzly version to 2.3.33 since that one fixes a performance issue quite severe and a regression introduced by that fix.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13341","08/17/2017 16:35:04",1,"Rename the maven plugin used to package plugins/extension/services ""We are using the """"mule-app-plugins-maven-plugin"""" plugin to package different artifact (plugins/services) and """"mule-extensions-maven-plugin"""" to package """"extension plugins"""". As this plugins will be moved to be part of the mule-maven-plugin, we need at least to get the proper names to avoid confusion in the future.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13342","08/17/2017 16:37:31",1,"Review package and runtime structure of application/domain/plugins/policy artifacts ""Need to review the final format of the mentioned artifacts before the final RC to avoid introducing backward compatibility issues in the near future.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13345","08/17/2017 16:50:45",8,"Tooling should be able to load Mule Runtime Services in order to avoid class loading issues ""DataSense and Weave should accessed through its Services interfaces. Tooling should be able to create the class loader and load services as Runtime does.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13347","08/17/2017 17:15:06",2,"Remove use of flow error handler in async scope ""Remove use of flow error handler in async""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13350","08/17/2017 20:55:26",1,"Transaction Exception when using vm:listener without transactions ""If a listener founds no messages and no transaction is begun, a transaction exception is thrown""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13353","08/18/2017 13:54:55",1,"Migrate exceptionPayload from message to new error handling mechanism ""Right now, the implementation of error propagation relying on the ExceptionPayload being set on the message is still present in the Message. This is used only by the compatibility module. Uses in the compatibility module must be migrated to the new Mule 4 error handling mechanism and the ExceptionPayload from the message removed.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13354","08/18/2017 17:57:18",8,"Introduce split-aggregate router consistent with scatter-gather ""Consistent with scatter-gather and using ForkJoinStrategies but operating on split parts instead of routes.""","",0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13356","08/18/2017 19:57:11",1,"Application's log config logs to console when no appender is configured ""When an application contains a log4j2.xml configuration file that defines loggers but no appenders, the log output is directed to the console. It makes more sense, if in those scenarios, the output is directed to the default application log file instead.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13361","08/22/2017 15:18:57",0,"Make TNS (aka: this) references be implicit in a ""Once MULE-13317 is implemented, there will be possible to call operations defined within the same module, but the current approach forces the user to add a specific prefix as xmlns:tns with its correpondant namespace Uri and location. Ideally, all of that can be inferred by the runtime code, making the developer's life easier.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13364","08/22/2017 22:46:48",2,"Getting java.lang.NoClassDefFoundError and java.lang.IncompatibleClassChangeErrorafter including CGLIB on core ""After the adding of CGLIB as a dependency of mule-core, the execution of the uber project started to fail with errors as  java.lang.NoClassDefFoundError and java.lang.IncompatibleClassChangeError related to using CGLIB classes.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13367","08/23/2017 14:39:53",1,"Replace ""maven"" descriptor loaders ID ""Descriptor loaders ID """"maven"""" used to identify bundleDescriptorLoader and classLoaderModelLoaders in the artifact descriptors has to be renamed to """"mule"""". The reason is that, at least in the case of the classloaderModelLoder, we are using """"maven"""" as the ID, but we are not always using Maven to load it. We support heavy/light packaging of artifacts. Both are currently using """"maven"""" as the ID, but in the case of heavy package, we are using the classloader-model.json to load the classloader model instead of using Maven.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13369","08/23/2017 16:29:57",1,"Disallow reserve characters in global element names ""We need to disallow the use of '/', '[' and ']' as allowed characters in global elements name attributes. This is required so we don't have to scape characters in the component location paths which would make the use of them by clients much more cumbersome. ""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13373","08/23/2017 21:30:18",0,"Implement a way to have access to the MuleContext of the policies ""Gateway needs to have access to the MuleContext of the policies in order to enable ServerNotifications for it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13376","08/23/2017 21:56:40",0,"Adding validation method to DataWeave service ""Adding validation method to DataWeave service.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13378","08/23/2017 22:29:54",0,"Wrong classloader being disposed when multiple policy templates are present ""When a policy is undeployed, the first present template is being disposed (and its classloader) instead of the one corresponding to that particular policy""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13380","08/24/2017 17:41:09",0,"Provide a way to unregister ExceptionReader from ExceptionHelper ""If an extension/application registers an Exception Reader and it isn;t remove un underlay, a class loader leak occurs.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13383","08/24/2017 22:28:45",2,"Fix ExceptionReader exceptionReaders list ""ExceptionHelper.exceptionReaders is global for the runtime, but a reader specific for a plugin/app can be registered.   The problem happens when a plugin Reader can process exceptions from the runtime and said plugin is used by more than one application. In that case, the reader selection could be messed up. The registered readers must be partitioned by app.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13385","08/25/2017 02:05:47",2,"HTTP server does not close connection with chunked encoding ""Since all content-length/transfer-encoding header logic remains in the HTTP connector, the service server suffers the consequences there mitigated. For example, when used with a simple ByteArrayEntity it sends chunked encoding but never closes the connection meaning no """"0"""" message is sent and clients wait out for it. Silver lining is the client does not explode but takes longer to complete.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13388","08/25/2017 19:15:39",8,"Spike to support DataSense on MUnit components ""MUnit defines different resources for the application that would be needed in order to define the ApplicationModel needed by DataSense, this story is about researching and implementing support for it.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13389","08/25/2017 21:01:43",0,"Provide a reusable utils to query properties from a class artifact's pom ""This is needed for querying pom properties from embedded test cases.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13390","08/25/2017 21:14:48",2,"Missing annotations to describe synthetic type's names ""There's a field named """"type"""" that can be found in severals extensions under TLS -> trust-store -> type, that has a synthetic type that looks like the following: Those types are missing some annotation (typeAlias?) that we can use to show to the users. Synthetic types are displayed in the same way as regular subtypes, as options in a dropdown, but these above end up rendered as blank options since there's no description/label/annotation we can use as display name."""," { """"key"""": { """"name"""": """"type"""" }, """"model"""": { """"type"""": """"Union"""", """"of"""": [ { """"type"""": """"String"""", """"annotations"""": { """"typeId"""": """"java.lang.String"""", """"enum"""": { """"type"""": """"[Ljava.lang.String;"""", """"values"""": [ """"jks"""", """"jceks"""", """"pkcs12"""" ] } } }, { """"type"""": """"String"""" } ] } ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13391","08/26/2017 00:54:02",1,"Clean up BulkOperationResult API ""Clean up that API""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13393","08/27/2017 22:29:18",0,"DeployableFileBuilder is including repository folder in artifact jar even with light package ""DeployableFileBuilder, used for building tests artifacts jars, has an option to make the artifact heavy or light. But when light is selected, the final jar still has the repository folder in it.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13394","08/28/2017 15:07:14",8,"Reconnect forever retry policy doesn't reconnect at all ""*Reconnect forever retry policy doesn't reconnect at all* * If you choose the {{reconnect-forever}} retry policy, a {{SimpleRetryPolicy}} is created with the value of  {{-1}}. * This {{SimpleRetryPolicy}} doesn't have any kind of special logic to handle this case and threats as a common one and no retry is executed. *Update:* If the Retry is executed in a blocking way, it works correctly, because it checks if the value is {{-1}} but, if is executed in a non blocking way, it will update the value to {{0}} and stop before any retry is executed [https://github.com/mulesoft/mule/blob/mule-4.x/core/src/main/java/org/mule/runtime/core/internal/retry/policies/SimpleRetryPolicy.java#L60]""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13395","08/28/2017 18:03:13",8,"Fix ignored test DeploymentServiceTestCase#deploysApplicationWithPluginDependingOnPlugin ""After MULE-13393, test deploysApplicationWithPluginDependingOnPlugin of DeploymentServiceTestCase class is failing because now as the test jar is light, it tries to get the plugin from maven repo, and is not there since it needs to be installed first""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13396","08/28/2017 19:22:11",0,"ClassCastException: org.codehaus.plexus.util.xml.Xpp3Dom cannot be cast to org.codehaus.plexus.util.xml.Xpp3Dom when using Tooling Runtime Client ""When loading Tooling Runtime Client on Studio, a class cast exception due to class loading issue is happening: Full stacktrace: """," java.lang.ClassCastException: org.codehaus.plexus.util.xml.Xpp3Dom cannot be cast to org.codehaus.plexus.util.xml.Xpp3Dom at org.mule.runtime.module.deployment.impl.internal.application.DeployableMavenClassLoaderModelLoader.lambda$exportSharedLibrariesResourcesAndPackages$4(DeployableMavenClassLoaderModelLoader.java:91) java.lang.ClassCastException: org.codehaus.plexus.util.xml.Xpp3Dom cannot be cast to org.codehaus.plexus.util.xml.Xpp3Dom at org.mule.runtime.module.deployment.impl.internal.application.DeployableMavenClassLoaderModelLoader.lambda$exportSharedLibrariesResourcesAndPackages$4(DeployableMavenClassLoaderModelLoader.java:91) at java.util.Optional.ifPresent(Optional.java:159) at org.mule.runtime.module.deployment.impl.internal.application.DeployableMavenClassLoaderModelLoader.exportSharedLibrariesResourcesAndPackages(DeployableMavenClassLoaderModelLoader.java:88) at org.mule.runtime.module.deployment.impl.internal.application.DeployableMavenClassLoaderModelLoader.addArtifactSpecificClassloaderConfiguration(DeployableMavenClassLoaderModelLoader.java:72) at org.mule.runtime.module.deployment.impl.internal.maven.AbstractMavenClassLoaderModelLoader.loadUrls(AbstractMavenClassLoaderModelLoader.java:280) at org.mule.runtime.module.deployment.impl.internal.maven.AbstractMavenClassLoaderModelLoader.createLightPackageClassLoaderModel(AbstractMavenClassLoaderModelLoader.java:221) at org.mule.runtime.module.deployment.impl.internal.maven.AbstractMavenClassLoaderModelLoader.createClassLoaderModel(AbstractMavenClassLoaderModelLoader.java:111) at org.mule.runtime.module.deployment.impl.internal.maven.AbstractMavenClassLoaderModelLoader.load(AbstractMavenClassLoaderModelLoader.java:103) at org.mule.runtime.module.deployment.impl.internal.maven.AbstractMavenClassLoaderModelLoader.load(AbstractMavenClassLoaderModelLoader.java:63) at org.mule.runtime.module.deployment.impl.internal.artifact.AbstractDeployableDescriptorFactory.getClassLoaderModel(AbstractDeployableDescriptorFactory.java:173) at org.mule.runtime.module.deployment.impl.internal.artifact.AbstractDeployableDescriptorFactory.lambda$loadFromJsonDescriptor$3(AbstractDeployableDescriptorFactory.java:102) at java.util.Optional.ifPresent(Optional.java:159) at org.mule.runtime.module.deployment.impl.internal.artifact.AbstractDeployableDescriptorFactory.loadFromJsonDescriptor(AbstractDeployableDescriptorFactory.java:101) at org.mule.runtime.module.deployment.impl.internal.artifact.AbstractDeployableDescriptorFactory.create(AbstractDeployableDescriptorFactory.java:66) at org.mule.tooling.client.internal.application.DefaultApplicationService.createApplicationClassLoader(DefaultApplicationService.java:53) at org.mule.tooling.client.internal.application.DefaultApplication.lambda$newApplicationClassLoaderLazyValue$0(DefaultApplication.java:255) at org.mule.runtime.api.util.LazyValue.lambda$new$1(LazyValue.java:44) at org.mule.runtime.api.util.LazyValue.get(LazyValue.java:69) at org.mule.tooling.client.internal.application.DefaultApplication.getArtifactClassLoader(DefaultApplication.java:126) at org.mule.tooling.client.internal.application.DefaultApplication.getApplicationName(DefaultApplication.java:120) at org.mule.tooling.client.internal.DefaultDataSenseService.buildDataSenseApplicationModel(DefaultDataSenseService.java:176) at org.mule.tooling.client.internal.DefaultDataSenseService.lambda$internalResolveDataSense$3(DefaultDataSenseService.java:116) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1582) at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13397","08/28/2017 20:26:43",8,"SourceConnectionProvider doesn't work as expected ""*SourceConnectionProvider doesn't work as expected* * _SourceConnectionProvider_ is what is injected into the Sources to be able to create connections. * {{testConnectivity(Connection connection)}} it should make a test connection with the given connection as the parameter, but what does, is not use the connection and finally fails with an StackOverflow due to a nonstop recursive call. * {{disconnect(Connection connection}})  it should disconnect and stop the connection but it depends on the kind of the specified ConnectionProvider strategy: ** If cached or pooled, it will just release it, but won't destroy it. ** If none, it will disconnect it totally. * The problem with the disconnect if you want to stop it totally you can't because the connection provider logic in charge of doing that won't be executed.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13399","08/28/2017 23:06:31",2,"ExtensionManager not stopped while undeploying operation ""Because CompositeExtensionManager doesn't propagate lifecycle to its child extension manager, a memory leak can occur while undeploying operations.  ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13400","08/29/2017 14:47:56",2,"All schedulers view allows changing their state ""The scheduling service provides a way of obtaining all schedulers for monitoring purposes. However, this view is not truly read only so users can actually retrieve all schedulers and stop all of them, for example. We need to avoid this because people are already mistakenly using that to stop their schedulers when leaking them and if done in prod it could be a severe problem.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13401","08/29/2017 14:56:55",1,"Adapt multipart test once DW bugs are fixed ""Several bugs have been reported to DW regarding multipart handling, including: * mixed subtype having wrong content disposition type * failure to read content because content type is not inferred * Binary being forced as type of unknown mime types * errors trying to read nameless part As a result some tests are ignored and in others the scripts contain workarounds so when those are fixed they'll need updating.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13404","08/29/2017 17:58:40",5,"VM Listener fails to release transacted message with numberOfConsumers greater than 1 ""See VMTxTestCase.listenerRollback(). When the fake scheduler service was used or if numberOfconsumers=""""1"""" is configured in the vm:listener, then it works. Logging the execution of the transaction methods, it seems a message is poll from the queue within a transaction but the transaction is never rolled back.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13405","08/29/2017 18:09:34",8,"Cleanup MuleContextListener and DeploymentListener ""MuleContextListener and DeploymentListener must be updated so they don't provide access to MuleContext. The also need to provide access to the application objects that are part of the API in the right notification method. For instance, the ConfigurationComponentLocator service should not be acceded during MuleContextListener.onCreate(..) since it won't have a valid state at that point. This is related to MULE-13375""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13408","08/29/2017 19:02:40",2,"Fix flaky test org.mule.test.module.scheduler.cron.CronSchedulerTestCase.test ""Test fails from time to time h3. Error Message reactor.core.Exceptions$ReactiveException: java.lang.AssertionError: Expected: is <5> but: was <7> at reactor.core.Exceptions.propagate(Exceptions.java:219) at org.mule.runtime.core.api.rx.Exceptions.propagateWrappingFatal(Exceptions.java:177) at org.mule.runtime.core.api.util.func.CheckedSupplier.handleException(CheckedSupplier.java:32) at org.mule.runtime.core.api.util.func.CheckedSupplier.get(CheckedSupplier.java:27) at org.mule.tck.probe.JUnitLambdaProbe.test(JUnitLambdaProbe.java:40) at org.mule.tck.probe.JUnitProbe.isSatisfied(JUnitProbe.java:34) at org.mule.tck.probe.PollingProber.poll(PollingProber.java:60) at org.mule.tck.probe.PollingProber.check(PollingProber.java:51) at org.mule.test.module.scheduler.cron.CronSchedulerTestCase.test(CronSchedulerTestCase.java:69) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.AssertionError: Expected: is <5> but: was <7> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) at org.junit.Assert.assertThat(Assert.java:956) at org.junit.Assert.assertThat(Assert.java:923) at org.mule.test.module.scheduler.cron.CronSchedulerTestCase.lambda$test$0(CronSchedulerTestCase.java:71) at org.mule.runtime.core.api.util.func.CheckedSupplier.get(CheckedSupplier.java:25) ... 19 more h3. Stacktrace java.lang.AssertionError: reactor.core.Exceptions$ReactiveException: java.lang.AssertionError: Expected: is <5> but: was <7> at reactor.core.Exceptions.propagate(Exceptions.java:219) at org.mule.runtime.core.api.rx.Exceptions.propagateWrappingFatal(Exceptions.java:177) at org.mule.runtime.core.api.util.func.CheckedSupplier.handleException(CheckedSupplier.java:32) at org.mule.runtime.core.api.util.func.CheckedSupplier.get(CheckedSupplier.java:27) at org.mule.tck.probe.JUnitLambdaProbe.test(JUnitLambdaProbe.java:40) at org.mule.tck.probe.JUnitProbe.isSatisfied(JUnitProbe.java:34) at org.mule.tck.probe.PollingProber.poll(PollingProber.java:60) at org.mule.tck.probe.PollingProber.check(PollingProber.java:51) at org.mule.test.module.scheduler.cron.CronSchedulerTestCase.test(CronSchedulerTestCase.java:69) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.AssertionError: Expected: is <5> but: was <7> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) at org.junit.Assert.assertThat(Assert.java:956) at org.junit.Assert.assertThat(Assert.java:923) at org.mule.test.module.scheduler.cron.CronSchedulerTestCase.lambda$test$0(CronSchedulerTestCase.java:71) at org.mule.runtime.core.api.util.func.CheckedSupplier.get(CheckedSupplier.java:25) ... 19 more at org.mule.tck.probe.PollingProber.check(PollingProber.java:52) at org.mule.test.module.scheduler.cron.CronSchedulerTestCase.test(CronSchedulerTestCase.java:69) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.lang.Thread.run(Thread.java:748)  ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13409","08/29/2017 20:44:49",0,"Add properties that are mapped to config provider rather than config ""To complete the JIRA around MULE-12545, it would be ideal to mark s as configProviders""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13411","08/29/2017 21:35:24",1,"Foreach counter type should be number and not string ""Foreach counter type should be number and not string to support == with Datsense.""","",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13421","08/30/2017 20:18:01",0,"MavenUtils is locking pom files ""When reading pom files, the MavenUtils in mule repository is not closing the FileReader, creating a resource leak. The issue is located at method org.mule.runtime.module.deployment.impl.internal.maven.MavenUtils#getPomModelFolder""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13422","08/30/2017 20:24:57",3,"SDK registers invalid errors for extension sources. ""The SDK is registering invalid errors for extension sources, for example """"MULE:SOURCE_ERROR_RESPONSE_GENERATE"""" which is an internal error. Maybe a simple solution would be to just modify the ExtensionErrorsRegistrant#getErrorType method to use instead of the Check tests!   ---- There are some tests ignored because of this issue in ErrorHandlingConfigurationFailuresTestCase. please fix  """," errorTypeRepository.getErrorType() errorTypeRepository.lookupErrorType() ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13429","08/31/2017 15:18:44",2,"Separate wrapping logic from ErrorMessageAwareException ""When ErrorMessageAwareException was first introduced, a wrapping logic was added to it. However, this proved to be only necessary for compatibility purposes. It's confusing to use and since it will be the way of propagating error messages we need to fix it ASAP.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13432","08/31/2017 17:28:09",2,"java.lang.StackOverflowError while loading resource with plugin class loader ""Once XSD were removed there is code that is still trying to load xds and end up in an stackoverflow.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13435","08/31/2017 17:51:25",2,"DataSense medatadata fails when the application is running ""Description The metadata generation fails when the application is running. Steps to reproduce 1- Create an application with a single flow with a listener and a logger. 2- Run the application. 3- Go to the listener configuration and then just click OK to trigger the metadata calculation. 4- An error message will appear saying that it can't start the application because the address is already in use.  ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13440","08/31/2017 20:50:21",13,"Support hooks for before/after execution of chain inner components ""Support hooks for before/after execution of chain inner components""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13443","09/01/2017 17:48:58",2,"Upgrade CXF to 2.7.19-MULE-002 patch release. ""Since some fixes were cherrypicked in our fork and a new release is available, we must update this library in runtime.""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13450","09/02/2017 22:53:37",1,"Do reactiveInterceptorAdapter initialization once per chain ""The injection of ReactiveInterceptorAdapater's must be done at flow initialization instead of event processing.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13453","09/03/2017 20:31:34",1,"ToolingException: Error while getting URI ""When DataSense tries to resolve the classes root folder an URISyntaxException is thrown: """," org.mule.tooling.client.api.exception.ToolingException: Error while getting URI at org.mule.tooling.client.internal.DefaultDataSenseService.lambda$null$7(DefaultDataSenseService.java:202) at java.util.Optional.map(Optional.java:215) at org.mule.tooling.client.internal.DefaultDataSenseService.lambda$buildDataSenseApplicationModel$8(DefaultDataSenseService.java:198) at org.mule.datasense.api.metadataprovider.DefaultApplicationModel.lambda$findResource$0(DefaultApplicationModel.java:63) at java.util.Optional.map(Optional.java:215) at org.mule.datasense.api.metadataprovider.DefaultApplicationModel.findResource(DefaultApplicationModel.java:63) at org.mule.datasense.impl.DataSenseProviderResolver.lambda$new$2(DataSenseProviderResolver.java:129) at java.util.Optional.map(Optional.java:215) at org.mule.datasense.impl.DataSenseProviderResolver.(DataSenseProviderResolver.java:125) at org.mule.datasense.impl.DataSenseApplicationModel.build(DataSenseApplicationModel.java:75) at org.mule.datasense.api.metadataprovider.CachedDataSenseProvider.createDataSenseApplicationModel(CachedDataSenseProvider.java:47) at org.mule.datasense.api.metadataprovider.CachedDataSenseProvider.(CachedDataSenseProvider.java:31) at org.mule.tooling.client.internal.DefaultDataSenseService.getDataSenseProvider(DefaultDataSenseService.java:215) at org.mule.tooling.client.internal.DefaultDataSenseService.lambda$internalResolveDataSense$3(DefaultDataSenseService.java:119) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1582) at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) Caused by: java.net.URISyntaxException: Illegal character in path at index 25: file:/home/martin/runtime -studio.product/.tooling/acdasdgadf24985013-d508-4d9b-a837-212cbc6a60e8/classes/ at java.net.URI$Parser.fail(URI.java:2848) at java.net.URI$Parser.checkChars(URI.java:3021) at java.net.URI$Parser.parseHierarchical(URI.java:3105) at java.net.URI$Parser.parse(URI.java:3053) at java.net.URI.(URI.java:588) at java.net.URL.toURI(URL.java:946) at org.mule.tooling.client.internal.DefaultDataSenseService.lambda$null$7(DefaultDataSenseService.java:200) ... 19 more",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13454","09/04/2017 12:19:24",8,"Add domain bundle deployment ""Domain bundle consist of a domain artifact and the set of applications that belong to that it. Deployment service must support the deployment of domain bundles, this implies: * Detecting new bundles * Redeploy domain/applications when a new domain bundle is found * Notify the deployment status of domain bundles * Provide an API to request deployment of domain bundles from the deployment service""","",0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13455","09/04/2017 12:46:49",1,"Remove deployment support for 3.x style domain bundle ""Domain deployment is still using the 3.x bundle format where applications are contained inside the domain artifact. A new domain bundle deployment will be added on MULE-13454. In the meantime the support to deploy the old bundle format must be removed.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13456","09/04/2017 13:33:38",8,"Fix flaky test org.mule.test.core.context.notification.processors.ComponentLocationTestCase.flowWithAsync ""Test fails frequently on the continuous build and locally Here is the log Error Message Expected: an empty collection but: <[IO - [ComponentLocationTestCase#flowWithAsync].io@org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.doInitialise:297@668bb2ff{ executor: java.util.concurrent.ThreadPoolExecutor@1ca2c01b[Running, pool size = 16, active threads = 0, queued tasks = 0, completed tasks = 191] shutdown: false }]> Stacktrace java.lang.AssertionError: Expected: an empty collection but: <[IO - [ComponentLocationTestCase#flowWithAsync].io@org.mule.runtime.module.extension.internal.runtime.config.LifecycleAwareConfigurationInstance.doInitialise:297@668bb2ff{ executor: java.util.concurrent.ThreadPoolExecutor@1ca2c01b[Running, pool size = 16, active threads = 0, queued tasks = 0, completed tasks = 191] shutdown: false }]> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) at org.junit.Assert.assertThat(Assert.java:956) at org.junit.Assert.assertThat(Assert.java:923) at org.mule.tck.junit4.AbstractMuleContextTestCase.verifyAndStopSchedulers(AbstractMuleContextTestCase.java:417) at org.mule.tck.junit4.AbstractMuleContextTestCase.disposeContext(AbstractMuleContextTestCase.java:382) at org.mule.tck.junit4.AbstractMuleContextTestCase.disposeContextPerTest(AbstractMuleContextTestCase.java:357) at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.lang.Thread.run(Thread.java:748) Standard Output ================================================================================ = Testing: flowWithAsync = ================================================================================ WARN 2017-09-04 08:22:23,122 [[MuleRuntime].timer] org.mule.service.scheduler.internal.DefaultScheduler: org.mule.runtime.core.api.scheduler.SchedulerBusyException scheduling next execution of task org.mule.runtime.core.api.util.monitor.ExpiryMonitor(repeatable). Message was: Task org.mule.runtime.core.api.util.monitor.ExpiryMonitor(repeatable) rejected from java.util.concurrent.ThreadPoolExecutor@48406d9d[Running, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 0]""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13458","09/04/2017 16:07:39",0,"TNS references with global elements are not macro expanding correctly ""When using TNS references (cyclic) in a module with global elements the references to the global elements went nuts.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13459","09/04/2017 16:38:08",8,"Add the concept of Stereotype to connection providers ""Complete later""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13460","09/04/2017 17:13:21",3,"Add get all keys to actual object store implementation ""Please provide a way to retrieve all keys as in 3.x Use case: As a user I want to retrieve a list of objects stored previously using object store. The idea is to provide an APIKit example to documentation for the RC, as in 3.x and this is the only pending implementation.  ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13466","09/04/2017 22:20:55",0,"Refactor code in smart connectors ""the module that does the macro expansion is messy.  Fix it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13479","09/07/2017 19:22:00",1,"Bump to JDK8 ""Bump mule-common to JDK8""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13482","09/07/2017 21:54:18",0,"ToolingAetherServiceRegister not a subtype ""Tooling Runtime Client is having class loading issues when loading Aether classes for mule-maven-client: Full stacktrace: """," java.util.ServiceConfigurationError: org.mule.maven.client.internal.AetherServiceRegister: Provider org.mule.tooling.client.aether.ToolingAetherServiceRegister not a subtype java.util.ServiceConfigurationError: org.mule.maven.client.internal.AetherServiceRegister: Provider org.mule.tooling.client.aether.ToolingAetherServiceRegister not a subtype at java.util.ServiceLoader.fail(ServiceLoader.java:239) at java.util.ServiceLoader.access$300(ServiceLoader.java:185) at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) at java.util.ServiceLoader$1.next(ServiceLoader.java:480) at org.mule.maven.client.internal.AetherRepositoryState.loadAetherServiceRegister(AetherRepositoryState.java:151) at org.mule.maven.client.internal.AetherRepositoryState.createRepositorySystem(AetherRepositoryState.java:140) at org.mule.maven.client.internal.AetherRepositoryState.createRepositorySession(AetherRepositoryState.java:96) at org.mule.maven.client.internal.AetherRepositoryState.(AetherRepositoryState.java:86) at org.mule.maven.client.internal.AetherRepositoryState.(AetherRepositoryState.java:70) at org.mule.maven.client.internal.AetherMavenClient.getRepositoryState(AetherMavenClient.java:106) at org.mule.maven.client.internal.AetherMavenClient.getRepositoryState(AetherMavenClient.java:98) at org.mule.maven.client.internal.AetherMavenClient.resolveBundleDescriptor(AetherMavenClient.java:246) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) at org.mule.maven.client.internal.AetherMavenClient.resolvePluginBundleDescriptorsDependencies(AetherMavenClient.java:267) at org.mule.tooling.client.internal.artifact.DefaultArtifactSerializationService.resolveExtensionModels(DefaultArtifactSerializationService.java:134) at org.mule.tooling.client.internal.artifact.DefaultArtifactSerializationService.createDslResolvingContext(DefaultArtifactSerializationService.java:129) at org.mule.tooling.client.internal.artifact.DefaultArtifactSerializationService.fromXml(DefaultArtifactSerializationService.java:87) at com.mulesoft.mozart.appgenerator.components.imports.xml.DefaultMuleXMLReader.extractProjectXML(DefaultMuleXMLReader.java:63) ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13485","09/08/2017 02:49:34",0,"Improve macro expansion go from O(n^2) to a better order ""Macro expansion for smart connectors takes n*n, improve it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13491","09/08/2017 18:46:26",0,"Tooling Runtime Client - NoClassDefFoundError: com/beust/jcommander/internal/Lists ""Tooling Runtime Client is having class loading issues when loading descriptors if the parent class loader (Eclipse) doesn't have the jcommander included in classpath. Still the jcommand class should not be used on Tooling Client classes: """," Caused by: java.lang.NoClassDefFoundError: com/beust/jcommander/internal/ListsFull Caused by: java.lang.NoClassDefFoundError: com/beust/jcommander/internal/Lists at org.mule.tooling.client.internal.ToolingDescriptorLoaderRepository.(ToolingDescriptorLoaderRepository.java:45) at org.mule.tooling.client.internal.MuleArtifactResourcesRegistry.init(MuleArtifactResourcesRegistry.java:70) at org.mule.tooling.client.internal.MuleArtifactResourcesRegistry.(MuleArtifactResourcesRegistry.java:59) at org.mule.tooling.client.internal.DefaultToolingRuntimeClientBuilder.build(DefaultToolingRuntimeClientBuilder.java:85) at org.mule.tooling.client.bootstrap.ExtendedBuilder.build(ExtendedBuilder.java:72) ",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13492","09/08/2017 18:51:21",2,"Use Java source version 1.8 in pom for 3.9 ""Mule 3.9 will support Java 8, not 7. So we should change the corresponding build version in the POMs.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13494","09/08/2017 20:41:29",8,"Cleanup Event downcasts ""Remove the downcasts to BaseEvent, BaseEventContext, InternalEvent and PrivilegedEvent added as part of MULE-13363. This will include some review/move of stuff currently in api to internal.   The change that introduced this is https://github.com/mulesoft/mule/pull/5678""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13497","09/08/2017 22:32:04",2,"PrivateObjectStore should not have a storeName parameter ""It's to confusing to explain the difference with the name on the os:object-store one. Plus, it's very easy to generate it automatically.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13507","09/11/2017 17:01:13",2,"DW Functions namespace should have package in lowercase ""DW Functions namespace should have package in lowercase, and only the last element of the namespace in PascalCase.  We are now setting everything in PascalCase, including the package.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13509","09/11/2017 18:35:27",0,"Add a watermark test case ""Add a test which simulates a watermark use case.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13513","09/12/2017 13:46:18",5,"SOAP Service does not support One Way operations ""When calculating output metadata with SOAP Service, I am getting a NullPointerException. 1. Get the code from here: https://github.com/mulesoft/oracle-ebs-connector/commit/bd817b2cc3bfdf971274ac68c8020994f815bd7e 2. Build the connector with {{mvn clean install -DskipTests}} 3. Set a breakpoint on PLSQLTypeMetaDataResolver, line 60 (getOutputType method). 4. Run PlSqlMetadataTestCase in debug mode. 5. When the breakpoint reaches the aforementioned line, evaluate it. It will throw a NullPointerException, with the following stacktrace: This is using the absolute latest SDK (1.0.0-SNAPSHOT), since it fixes another bug we were having, MULE-13481. It should be noted that when the Output Metadata logic fails, Input Metadata, although successfully calculated, is discarded and not provided. I'm not sure if this is by design, but I just wanted to point that out."""," java.lang.NullPointerException at org.mule.service.soap.metadata.OutputTypeIntrospecterDelegate.getMessage(OutputTypeIntrospecterDelegate.java:25) at org.mule.service.soap.introspection.WsdlDefinition.getBodyPart(WsdlDefinition.java:119) at org.mule.service.soap.metadata.BodyMetadataResolver.getMetadata(BodyMetadataResolver.java:40) at org.mule.service.soap.metadata.DefaultSoapMetadataResolver.getOutputMetadata(DefaultSoapMetadataResolver.java:48) at org.mule.modules.oracle.internal.metadata.plsql.PLSQLTypeMetaDataResolver.getOutputType(PLSQLTypeMetaDataResolver.java:60) at org.mule.modules.oracle.internal.metadata.plsql.PLSQLTypeMetaDataResolver.getOutputType(PLSQLTypeMetaDataResolver.java:23) at org.mule.runtime.module.extension.internal.metadata.MetadataOutputDelegate.getOutputMetadata(MetadataOutputDelegate.java:127) at org.mule.runtime.module.extension.internal.metadata.MetadataOutputDelegate.getOutputMetadataDescriptor(MetadataOutputDelegate.java:79) at org.mule.runtime.module.extension.internal.metadata.MetadataMediator.getMetadata(MetadataMediator.java:176) at org.mule.runtime.module.extension.internal.metadata.MetadataMediator.getMetadata(MetadataMediator.java:121) at org.mule.runtime.module.extension.internal.runtime.ExtensionComponent.lambda$null$14(ExtensionComponent.java:289) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:137) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:840) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:806) at org.mule.runtime.module.extension.internal.runtime.ExtensionComponent.lambda$getMetadata$15(ExtensionComponent.java:288) at org.mule.runtime.module.extension.internal.runtime.ExtensionComponent.runWithMetadataContext(ExtensionComponent.java:328) at org.mule.runtime.module.extension.internal.runtime.ExtensionComponent.getMetadata(ExtensionComponent.java:288) at org.mule.runtime.core.internal.metadata.MuleMetadataService.lambda$getComponentMetadataWithKey$6(MuleMetadataService.java:238) at org.mule.runtime.core.internal.metadata.MuleMetadataService.exceptionHandledMetadataFetch(MuleMetadataService.java:188) at org.mule.runtime.core.internal.metadata.MuleMetadataService.getComponentMetadataWithKey(MuleMetadataService.java:237) at org.mule.runtime.core.internal.metadata.MuleMetadataService.getOperationMetadata(MuleMetadataService.java:120) at org.mule.modules.oracle.automation.functional.AbstractMetadataTestCase.getOperationModel(AbstractMetadataTestCase.java:23) at org.mule.modules.oracle.automation.functional.AbstractMetadataTestCase.inputMetadataTest(AbstractMetadataTestCase.java:59) at org.mule.modules.oracle.automation.functional.PlSqlMetadataTestCase.createInput(PlSqlMetadataTestCase.java:33) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.mule.test.runner.ArtifactClassLoaderRunner.lambda$run$1(ArtifactClassLoaderRunner.java:408) at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:787) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:137) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:840) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:806) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:786) at org.mule.test.runner.ArtifactClassLoaderRunner.run(ArtifactClassLoaderRunner.java:408) at org.junit.runner.JUnitCore.run(JUnitCore.java:137) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:117) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:262) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:84) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13516","09/12/2017 15:01:52",2,"TestRunner not validating override of lookup strategy ""When a plugin exports a package already exported as privileged by the runtime, the applications fail with the error: But the integration tests that tests the same code run without problem. The integration tests must fail consistently in the same way as an application. Also, the message mentions `system package`, but in this case it should say it is privileged."""," java.lang.IllegalArgumentException: Attempt to override lookup strategy for system package: org.mule.runtime.core.privileged.event at org.mule.runtime.container.internal.MuleClassLoaderLookupPolicy.validateLookupPolicies(MuleClassLoaderLookupPolicy.java:64) ~[mule-module-container-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.container.internal.MuleClassLoaderLookupPolicy.extend(MuleClassLoaderLookupPolicy.java:120) ~[mule-module-container-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.deployment.model.internal.application.MuleApplicationClassLoaderFactory.getApplicationClassLoaderLookupPolicy(MuleApplicationClassLoaderFactory.java:65) ~[mule-module-deployment-model-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.deployment.model.internal.application.MuleApplicationClassLoaderFactory.create(MuleApplicationClassLoaderFactory.java:46) ~[mule-module-deployment-model-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.deployment.model.internal.application.MuleApplicationClassLoaderFactory.create(MuleApplicationClassLoaderFactory.java:28) ~[mule-module-deployment-model-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.artifact.api.classloader.TrackingDeployableArtifactClassLoaderFactory.create(TrackingDeployableArtifactClassLoaderFactory.java:42) ~[mule-module-artifact-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.deployment.model.internal.application.ApplicationClassLoaderBuilder.createArtifactClassLoader(ApplicationClassLoaderBuilder.java:73) ~[mule-module-deployment-model-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.deployment.model.internal.AbstractArtifactClassLoaderBuilder.build(AbstractArtifactClassLoaderBuilder.java:131) ~[mule-module-deployment-model-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.deployment.model.internal.application.ApplicationClassLoaderBuilder.build(ApplicationClassLoaderBuilder.java:68) ~[mule-module-deployment-model-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultApplicationFactory.createArtifact(DefaultApplicationFactory.java:130) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultApplicationFactory.createArtifact(DefaultApplicationFactory.java:103) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.impl.internal.application.DefaultApplicationFactory.createArtifact(DefaultApplicationFactory.java:52) ~[mule-module-deployment-model-impl-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.createArtifact(DefaultArchiveDeployer.java:407) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployPackagedArtifact(DefaultArchiveDeployer.java:147) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployPackagedArtifact(DefaultArchiveDeployer.java:257) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployPackagedArtifact(DefaultArchiveDeployer.java:82) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DefaultArchiveDeployer.deployPackagedArtifact(DefaultArchiveDeployer.java:44) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher.deployPackedApps(DeploymentDirectoryWatcher.java:236) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher.start(DeploymentDirectoryWatcher.java:145) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.deployment.internal.MuleDeploymentService.start(MuleDeploymentService.java:138) [mule-module-deployment-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.mule.runtime.module.launcher.MuleContainer.start(MuleContainer.java:217) [mule-module-launcher-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_144] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_144] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_144] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_144] at org.mule.runtime.module.reboot.internal.MuleContainerWrapper.start(MuleContainerWrapper.java:49) [mule-module-boot-ee-4.0.0-SNAPSHOT.jar:4.0.0-SNAPSHOT] at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4242) [wrapper-3.5.29.jar:3.5.29] ",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13521","09/12/2017 21:57:22",3,"JMS does not communicate properly it's ExternalLibs ""JMS does not communicate properly it's ExternalLibs, thus the IDEs cannot help the user to configure the application.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13530","09/14/2017 02:29:38",2,"Queue and ObjectStore managers not properly overriden when in Cluster ""The SpringRegistryConfigurator is handling the entries in the customization service wrongfully, causing queues and object store to not work correctly when in cluster.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13532","09/14/2017 15:27:26",2,"EmbeddedContainer should allow to do an Application lazyInit with parsing validations on ""EmbeddedContainer should allow to do an Application lazyInit with parsing validations on""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13533","09/14/2017 15:28:40",1,"Support includeTestDependencies when resolving classloader model as deployment property ""Support to includeTestDependencies from deployment ""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13535","09/14/2017 15:30:52",3,"Remove ParameterRoleTypeAnnotation ""No longer makes sense, fields are always BEHAVIOUR""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13540","09/14/2017 16:55:22",8,"Remove processor from API ""Processor should not be part of core API. Only internal/privileged usages. Provide support to give callback to test:processor if necessary""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13546","09/14/2017 19:32:38",0,"Support deployment time configuration in Mule 4 ""Move changes done in 3.x to support customization of deployment with properties to mule 4""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13548","09/14/2017 20:53:46",1,"Ensure the following components can be injected ""Ensure the following Classes can be injected by @Inject in any bean that required so. This also includes those beans that are bootstraped: * ErrorTypeRepository * ExtendedExpressionManager * SchedulerService * MuleRegistry   ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13552","09/15/2017 16:16:57",2,"SFTP SecureRandom implementation hangs on OpenJDK 8 ""OpenJDK 8 on Linux is configured by default to use securerandom.source=file:/dev/random This implementation will hang when the entropy pool is empty, until there is enough environmental noise. See [http://bugs.java.com/view_bug.do?bug_id=6521844] To reproduce, just run the FTP connector tests on Ubuntu 16.04 and OpenJDK8_u131 and see they will hang while generating the SecureRandom. A workaround, is to change the SecureRandom implementation on the OpenJDK. This can be achieved by editing the {{java.security}} file inside {{/etc/java-8-openjdk/security}} and commenting the following line {{securerandom.source=file:/dev/random}} or changing it to {{securerandom.source=file:/dev/urandom}}   The SFTP connector should be able to select an appropriate SecureRandom implementation to avoid this issue. If this is not possible, it should be properly documented.  ""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13555","09/15/2017 20:04:37",3,"Extension cannot extend a stereotype from another extension ""StereotypeDefinition interface is missing the concept of namespace. Otherwise, it's impossible to do something like this:     In the example above, there's no way to specify that the parent definition is to have the FTP namespace. This is made even worse by the fact that the stereotype that I'm trying to extend is an implicit one. Things that should happen: * StereotypeDefinition should have the concept of namespace * It should not be necessary for an extension to implement the getNamespace() method on each of their StereotypeDefinition implementations * No extension should be able to declare a stereotype of a namespace other than its own, but they should be able to use a stereotype from another extension * MuleStereotypeDefinition class should no longer be a marker interface but an actual class which namespace is a final method returning MULE  """," public class FtpsConnectionStereotypeDefinition implements StereotypeDefinition { @Override public String getName() { return CONNECTION_DEFINITION.getName(); } @Override public Optional getParent() { return of(new StereotypeDefinition() { @Override public String getName() { return CONNECTION_DEFINITION.getName(); } @Override public Optional getParent() { return of(CONNECTION_DEFINITION); } }); } }",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13557","09/15/2017 21:19:03",1,"Jar content cannot be read by URL.openStream() on Windows ""Jar content cannot be read by URL.openStream() on Windows This is making CompressedTypeResolverLoaderTestCase tests on metadata-model-api module fail on {{org.mule.metadata.catalog.internal.builder.TypesResolverBuilder#createFromUrl}} when executing _schemaUri.toURL().openStream()_ with message _JAR entry schemas/type1-schema.json not found in C:\Users\HERNAN~1.WIT\AppData\Local\Temp\junit7575768859740793034\catalog-001.jar_ Tests are successfully executed on Ubuntu. Also if resource is on jar root no exception is thrown.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13561","09/18/2017 16:44:49",3,"Extensions Generated Documentation does not include descriptios for types. ""When generating the extensions documentation. the types are not being populated with description nor if they are required or not.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13570","09/18/2017 22:54:53",2,"Missing default values in Core Extension Model ""Default values are missing from some operations when walking over the core extension model. For instance, frequency, start delay and time unit default values are missing in the scheduler operation.  Also, we need configuration-properties in the core extension model so we can add  to the config""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13571","09/18/2017 23:55:58",2,"Request hanged if response statusCode is less than 200 ""When setting the response/error-response status code in the listener, if the number is less than 200, the request gets hanged. There are certain statuses that may have particular behaviour. We should analyse what to do on each of them, but the main goal here is to fail when receiving the invalid ones.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13574","09/19/2017 20:59:27",0,"Fix ContainerConfigurationTestCase ""Fix ContainerConfigurationTestCase after agent changes the response of the API""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13575","09/19/2017 21:22:33",8,"File connector tests using locks fail on Windows ""File locks and permissions in File connector appear to be causing issues when running on Windows. To reproduce, run the following tests which are failing on Windows: """," FileListTestCase.listWithoutReadPermission FileReadTestCase.readLockReleasedOnContentConsumed FileReadTestCase.readWithLockAndWithoutEnoughPermissions FileRenameTestCase.failOnOverwriteANonReadableDirectory",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13592","09/21/2017 16:45:34",0,"Remove mention to spring on api packages for mule-module-spring-config ""The api package for the module contains spring, there should not be mentions to spring on the package: A possible change could be """," org.mule.runtime.config.spring.api org.mule.runtime.config.dsl.api",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13593","09/21/2017 19:34:33",5,"SDK Non Blocking operations only work with the ReflectiveOperationExecutor ""*SDK is not following the Liskov Substitution Principle for privileged non blocking extensions.* When having a privileged extension that contains a non blocking operation with a custom executor, the operation defined in the `Operation` class receives a CompletionCallback in order to mark the operation as non blocking, but when implementing the actual executor such callback is not used so we end up waiting forever to that callback to be executed. this can be seen in ReactiveOperationExecutionWrapper#process , which is used to execute nonblocking operation ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13595","09/21/2017 20:20:49",0,"Resource File not found in Tooling Test ""The situation is as follows: We have a connector (Kafka, see [https://github.com/mulesoft/kafka-connector/tree/develop-4.x)] that has 2 connection properties (keyStoreLocation and trustStoreLocation) that are Files. When setting the relative path of the files and configuring the mule-artifact.json file to export them, they work as expected when running the application. But when we try to do a Test Connection, they fail with a NullPointerException due to the class loader returning null when fetching those properties. We've also created a Tooling Client Test ([https://github.com/mulesoft/connectors-integration-tests/blob/kafka/src/test/java/org/mule/module/netsuite/integration/KafkaIT.java)] that is also failing due to the same error.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13599","09/22/2017 15:25:03",3,"WSC is putting the body DataType in the response object instead of in the body field ""WSC is putting the body DataType in the response object instead of in the body field This is breaking Message History when serializing the whole payload.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13600","09/22/2017 15:31:09",2,"Fix ExpiredShutdownTimeoutRequestResponseTestCase Tests ""*Fix ExpiredShutdownTimeoutRequestResponseTestCase Tests* There are two tests failing and we lost track of when both of this started failing. # testScriptComponent()  # testExpressionTransformer() ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13601","09/22/2017 15:51:57",1,"Add missing License Header in core extensions ""Add missing License Header in core extensions""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13606","09/22/2017 21:32:49",3,"Soap connect is fetching services multiple times ""Soap connect is fetching services multiple times""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13607","09/23/2017 01:33:17",2,"HTTP requester is using body media type to determine response one ""While attempting some other changes I realised the HTTP request component was using the request body mime type in case the received response didn't return a content type. This is fundamentally wrong since sending a JSON payload does not mean expecting one back. It is specified that when an HTTP message has no content type then application/octet-stream should be used as default (https://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html#sec7.2.1).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13608","09/23/2017 04:05:12",3,"ClassNotFoundException in HTTP Request ""Trying to configure """"HTTP Request"""" setting to any URL i.e [http://www.google.com|http://www.google.com/] throws an exception. App:   Stacktrace: """," Failed to resolve dynamic model. component: COMPONENT, element: , code: UNKNOWN - Reason: java.lang.IllegalArgumentException: Could not load class org.mule.extension.http.internal.request.RequestConnectionParams at org.mule.metadata.java.api.utils.JavaTypeUtils.lambda$getType$0(JavaTypeUtils.java:127) at java.util.Optional.map(Optional.java:215) at org.mule.metadata.java.api.utils.JavaTypeUtils.getType(JavaTypeUtils.java:123) at org.mule.metadata.java.api.utils.JavaTypeUtils.getType(JavaTypeUtils.java:115) at org.mule.runtime.module.extension.internal.runtime.resolver.NullSafeValueResolverWrapper$1.visitObject(NullSafeValueResolverWrapper.java:86) at org.mule.metadata.api.model.impl.DefaultObjectType.accept(DefaultObjectType.java:65) at org.mule.runtime.module.extension.internal.runtime.resolver.NullSafeValueResolverWrapper.of(NullSafeValueResolverWrapper.java:82) at org.mule.runtime.module.extension.internal.loader.utils.ImplicitObjectUtils.buildImplicitResolverSet(ImplicitObjectUtils.java:59) at org.mule.runtime.module.extension.internal.runtime.config.DefaultImplicitConnectionProviderFactory.lambda$new$1(DefaultImplicitConnectionProviderFactory.java:58) at org.mule.runtime.module.extension.internal.runtime.config.DefaultImplicitConnectionProviderFactory.createImplicitConnectionProvider(DefaultImplicitConnectionProviderFactory.java:73) at org.mule.runtime.module.extension.internal.runtime.resolver.ImplicitConnectionProviderValueResolver.resolve(ImplicitConnectionProviderValueResolver.java:46) at org.mule.runtime.module.extension.internal.runtime.resolver.ImplicitConnectionProviderValueResolver.resolve(ImplicitConnectionProviderValueResolver.java:30) at org.mule.runtime.module.extension.internal.runtime.config.ConfigurationInstanceFactory.createConfiguration(ConfigurationInstanceFactory.java:91) at org.mule.runtime.module.extension.internal.runtime.config.DefaultImplicitConfigurationProviderFactory.createImplicitConfigurationProvider(DefaultImplicitConfigurationProviderFactory.java:74) at org.mule.runtime.module.extension.internal.manager.DefaultExtensionManager.createImplicitConfiguration(DefaultExtensionManager.java:209) at org.mule.runtime.module.extension.internal.manager.DefaultExtensionManager.getConfiguration(DefaultExtensionManager.java:167) at org.mule.runtime.module.deployment.impl.internal.policy.CompositeArtifactExtensionManager.getConfiguration(CompositeArtifactExtensionManager.java:92) at org.mule.runtime.module.extension.internal.runtime.ExtensionComponent.lambda$getConfiguration$27(ExtensionComponent.java:396) at java.util.Optional.orElseGet(Optional.java:267) at org.mule.runtime.module.extension.internal.runtime.ExtensionComponent.getConfiguration(ExtensionComponent.java:396) at org.mule.runtime.module.extension.internal.runtime.ExtensionComponent.getMetadataContext(ExtensionComponent.java:349) at org.mule.runtime.module.extension.internal.runtime.ExtensionComponent.runWithMetadataContext(ExtensionComponent.java:325) at org.mule.runtime.module.extension.internal.runtime.ExtensionComponent.getMetadata(ExtensionComponent.java:274) at org.mule.runtime.core.internal.metadata.MuleMetadataService.lambda$getComponentMetadata$5(MuleMetadataService.java:232) at org.mule.runtime.core.internal.metadata.MuleMetadataService.exceptionHandledMetadataFetch(MuleMetadataService.java:188) at org.mule.runtime.core.internal.metadata.MuleMetadataService.getComponentMetadata(MuleMetadataService.java:231) at org.mule.runtime.core.internal.metadata.MuleMetadataService.getOperationMetadata(MuleMetadataService.java:128) at org.mule.runtime.config.spring.internal.LazyMetadataService.lambda$getOperationMetadata$1(LazyMetadataService.java:69) at java.util.Optional.orElseGet(Optional.java:267) at org.mule.runtime.config.spring.internal.LazyMetadataService.getOperationMetadata(LazyMetadataService.java:69) at com.mulesoft.agent.services.metadata.MuleAgentMetadataService.lambda$getOperationMetadata$1(MuleAgentMetadataService.java:65) at com.mulesoft.agent.services.metadata.MuleAgentMetadataService.withMetadataService(MuleAgentMetadataService.java:126) at com.mulesoft.agent.services.metadata.MuleAgentMetadataService.getOperationMetadata(MuleAgentMetadataService.java:65) at com.mulesoft.agent.external.handlers.metadata.MetadataRequestHandler.lambda$getOperationMetadata$2(MetadataRequestHandler.java:162) at com.mulesoft.agent.util.ResponseHelper.response(ResponseHelper.java:88) at com.mulesoft.agent.external.handlers.metadata.MetadataRequestHandler.getOperationMetadata(MetadataRequestHandler.java:160) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171) at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:152) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104) at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:387) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:331) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:103) at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:267) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:297) at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:254) at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1028) at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:372) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:381) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:344) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:221) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1515) at com.mulesoft.agent.rest.RequestLoggingFilter.doFilter(RequestLoggingFilter.java:95) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:519) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:138) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:564) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:213) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1097) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:448) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:175) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1031) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:446) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:271) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:246) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.ClassNotFoundException: org.mule.extension.http.internal.request.RequestConnectionParams at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:420) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:382) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at org.apache.commons.lang3.ClassUtils.getClass(ClassUtils.java:923) at org.mule.metadata.java.api.utils.JavaTypeUtils.lambda$getType$0(JavaTypeUtils.java:125) ... 81 more .",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13619","09/25/2017 15:43:42",1,"Enable Lazy init to run XSD validations ""Lazy init allow an invalid application to start as this is not a problem for tooling use case. For the MUnit use case if an application containing an invalid XML (invalid because it doesn't match the XSD definition) deployment/starting of the application should fail with the proper error. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13623","09/25/2017 20:06:26",2,"muleRuntimeConfig.maven.repositoryLocation property ignored when set in command line ""Using command line property to set repository location doesn't affects mule. ./bin/mule M-DmuleRuntimeConfig.maven.repositoryLocation=/Users/username/.m2/repository When following line is executed, the mavenConfig is built with a default value based on muleBase directory: https://github.com/mulesoft/mule/blob/mule-4.x/modules/global-config/src/main/java/org/mule/runtime/globalconfig/api/GlobalConfigLoader.java#L61""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13628","09/26/2017 17:40:27",2,"Create ExtensionModel DTO Serializer ""Create ExtensionModel DTO Serializer so it can be used by Mozart and Exchange. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13631","09/26/2017 21:48:42",5,"Processing two Chains in parallel halts execution ""Given the following operation: {code} public void myRouters(@Optional BeforeCall beforeCall, @Optional AfterCall afterCall, RouterCompletionCallback callback) { Result result1 = Result.builder().build(); Result result2 = result1.copy().build(); Thread thread1 = new Thread(new RunChainThread(beforeCall.getChain(), result1)); Thread thread2 = new Thread(new RunChainThread(beforeCall.getChain(), result2)); thread1.start(); thread2.start(); try { thread1.join(); thread2.join(); } catch (InterruptedException e) { callback.error(e); } callback.success(Result.builder().build()); } private class RunChainThread implements Runnable { private final Chain chain; private final Result result; RunChainThread(Chain chain, Result result) { this.chain = chain; this.result = result; } @Override public void run() { Latch latch = new Latch(); chain.process(result, (result -> { System.out.println(""""Finished running """" + result); latch.release(); }), (error, result) -> { System.out.println(""""Finished with error """" + error); latch.release(); }); try { latch.await(); } catch (InterruptedException e) { e.printStackTrace(); } } } {code} Where BeforeCall and AfterCall are *Router*. And having the following flow in a FunctionalTestCase {code:xml} {code}  Makes the execution halt Things to take into account: * The processing of the chain is made blocking * Wrapping the chain in a synchronized block solves the issue  """," public void myRouters(@Optional BeforeCall beforeCall, @Optional AfterCall afterCall, RouterCompletionCallback callback) { Result result1 = Result.builder().build(); Result result2 = result1.copy().build(); Thread thread1 = new Thread(new RunChainThread(beforeCall.getChain(), result1)); Thread thread2 = new Thread(new RunChainThread(beforeCall.getChain(), result2)); thread1.start(); thread2.start(); try { thread1.join(); thread2.join(); } catch (InterruptedException e) { callback.error(e); } callback.success(Result.builder().build()); } private class RunChainThread implements Runnable { private final Chain chain; private final Result result; RunChainThread(Chain chain, Result result) { this.chain = chain; this.result = result; } @Override public void run() { Latch latch = new Latch(); chain.process(result, (result -> { System.out.println(""""Finished running """" + result); latch.release(); }), (error, result) -> { System.out.println(""""Finished with error """" + error); latch.release(); }); try { latch.await(); } catch (InterruptedException e) { e.printStackTrace(); } } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13636","09/27/2017 22:19:59",1,"wsdlLocation is in the wrong group in WSC. ""wsdlLocation is in the wrong group in WSC.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13637","09/28/2017 00:27:47",5,"String and Binary operations should always have a mime type ""Operations which return a String or an INputStream should always be forced to specify a mimeType. That miemType needs to be automatically set on the return value but needs to also be overridable from a Result object""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13647","09/28/2017 17:36:33",1,"Use Deployment Properties to disable logging on tooling applications ""Revert MULE-13253""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13659","09/28/2017 20:40:57",2,"Add the concept of ConnectionProvider which doesn't support connectivity testing ""ExtensionModel needs to communicate that to allow tooling not to show the testing button""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13660","09/28/2017 20:47:36",1,"SimpleUnitTestScheduler keeps recurrent tasks running after stop() ""Ensure that when a test is finished, all recurrent tasks created as part of that test are cancelled.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13665","09/29/2017 14:08:41",2,"Move BaseEventContext to privileged API ""-Also, rename it to CoreEventContext.- Check usages in MUnit and apikit""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13667","09/29/2017 15:53:39",2,"Component locations file is not well populated ""The component locations in the application model provide the file in which the element is located as well as the line number. Sometimes this value only holds the name of the file. Some other times this value holds the relative path of the file. Suppose the file is located under src/main/mule/my/pacage/file.xml, it can come as: * *file.xml* * *my/pacage/file.xml* It should always be the full(relative) path: *my/pacage/file.xml*    ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13668","09/29/2017 16:00:02",2,"Lazy Init should refresh ConfigurationComponentLocator ""Lazi init should refresh the content of the ConfigurationComponentLocator before each initialisation.  This way the locator should only show those element that belong to the current minimal app.  Now, as it's not being refreshed, successive runs in the same container accumulates components in the ConfigurationComponentLocator causing that searches in the locator return components in unstable states (not init for instance). ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13670","09/29/2017 18:16:56",2,"Make sure all serializable classes have serial version uid ""Make sure all serializable classes have the serialversionUid defined so they can still be read after being changed in future versions.""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13671","09/29/2017 21:41:57",5,"Split FTP and SFTP connectors ""Split them up""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13673","09/29/2017 22:03:22",1,"Wrong prefix used when generating extension documentation ""Wrong prefix used when generating extension documentation""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13675","10/02/2017 13:14:08",2,"Cannot use ConfigurationComponentLocator to get a component of the default error handler for a flow ""When using a default error handler, its chain is used as a template to create an error hadler in the flows. When using ConfigurationComponentLocator, it is impossible to get the processors of the default error handler for a flow. The components hava a path like: Note there is no *processors* as expected and an extra index. Also, when using such path to query the component, the template is retrieved instead of an actual processor in a flow. So, at leats the lifecycle status of it is wrong (see ignored test ErrorHandlerLifecycleTestCase#testLifecycleDefaultErrorHandler)"""," defaultEH/0/0 ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13677","10/02/2017 14:21:31",0,"Add a way to export additional container packages for integration tests ""Some integration tests for the container need to access packages that are not part of the API. There has to be a way to be able to export those packages for testing purposes as it is not possible to refactor all the tests to avoid it. This new feature must be available only until those tests can be adapted to avoid using non public APIs.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13679","10/02/2017 14:59:42",2,"Remove reactor operator error hook ""The current mechanism for handling error in reactor relies on registering a hook to translate any exception to a MessagingException. It should be migrated to use https://projectreactor.io/docs/core/release/api/reactor/util/context/Context.html keeping into account that many plugins with just api access may want to use that. Ref: http://projectreactor.io/docs/core/release/reference/docs/index.html#context""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13682","10/02/2017 15:59:08",5,"Rework Email Errors ""*Rework Email Errors* Email errors don't cover a lot of cases, we need to review it ASAP.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13686","10/02/2017 18:34:19",2,"ExtensionModel DTO missing the ErrorModel attribute ""ErrorModel DTO is not being used, although it has been implemented. Add test to validate. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13687","10/02/2017 18:37:11",2,"ExtensionModel DTO missing the ErrorModel attribute ""ErrorModel DTO is not being used, although it was implemented. Add test to validate. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13694","10/03/2017 03:23:57",8,"Provide support for fetching all the xsd dependencies from a xsd file ""We should include a new functionality to obtain all the dependencies (import/include) from a XSD file in order to copy all the necessary files when the user uses that kind of files.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13695","10/03/2017 12:48:56",1,"Wrong validation of product type in mule-artifact.json files ""When an artifact indicates an invalid required product (like MULE_CE when only MULE and MULE_EE are valid) the error message obtained when the plugin is used is the following: When it should say something like """"MULE_CE is not a valid product"""""""," classLoaderModelWithPluginDependency(org.mule.runtime.module.deployment.impl.internal.application.ApplicationDescriptorFactoryTestCase)  Time elapsed: 0.059 sec  <<< ERROR! java.lang.IllegalStateException: The artifact test-plugin does not specifies a requiredProduct ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13696","10/03/2017 13:59:16",0,"Update to Agent Version 1.9.0 on Tooling Client "".""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13701","10/03/2017 15:59:13",8,"Add a way to patch partially Mule 4 services ""Like in Mule 3.x plugins, it would be useful to be able to provide partial patches for services like DataWeave. Currently this forces to provide full patch replacements for services, making it very complex to handle and tracking multiple fixes in the same installation. It could be implemented as a new directory that takes precedence in the classloader, like lib/user for provided libraries.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13702","10/03/2017 16:13:25",2,"Fix flaky tests that uses test maven artifacts ""Tests like ApplicationDescriptorFactoryTestCase and  DomainDescriptorFactoryTestCase use Mule artifacts that depend on connectors that are not part of the project Maven's reactor. (ex: HTTP and Sockets connectors) This causes that those tests to be flaky, as those dependencies are not always on the Maven repo used to build the project and aether is not able to download them for some reason. Besides that problem, Mule CE must not depend on any connector to avoid implicit cyclic dependencies and building against out of data versions""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13703","10/03/2017 18:37:46",2,"ExtensionModelJsonSerializer is removing errorModels for Mule Core ExtensionModel ""When serializing and deserializing Mule Core extensionModel the errors are not persisted. ExtensionModel object has: But the json output only has one and empty array in all the errors fields: Even if the same json serialized is deserialzed the ExtensionModel instance has no errors (assuming that at least the whole hierarchy should be dynamically generated). """," errors = {LinkedHashSet@4886} size = 26 0 = {ImmutableErrorModel@5727} """"MULE:ANY"""" 1 = {ImmutableErrorModel@5728} """"MULE:EXPRESSION"""" 2 = {ImmutableErrorModel@5729} """"MULE:TRANSFORMATION"""" 3 = {ImmutableErrorModel@5730} """"MULE:CONNECTIVITY"""" 4 = {ImmutableErrorModel@5731} """"MULE:RETRY_EXHAUSTED"""" 5 = {ImmutableErrorModel@5732} """"MULE:REDELIVERY_EXHAUSTED"""" 6 = {ImmutableErrorModel@5733} """"MULE:STREAM_MAXIMUM_SIZE_EXCEEDED"""" 7 = {ImmutableErrorModel@5734} """"MULE:TIMEOUT"""" 8 = {ImmutableErrorModel@5735} """"MULE:UNKNOWN"""" 9 = {ImmutableErrorModel@5736} """"MULE:ROUTING"""" 10 = {ImmutableErrorModel@5737} """"MULE:COMPOSITE_ROUTING"""" 11 = {ImmutableErrorModel@5738} """"MULE:VALIDATION"""" 12 = {ImmutableErrorModel@5739} """"MULE:DUPLICATE_MESSAGE"""" 13 = {ImmutableErrorModel@5740} """"MULE:SECURITY"""" 14 = {ImmutableErrorModel@5741} """"MULE:SERVER_SECURITY"""" 15 = {ImmutableErrorModel@5742} """"MULE:CLIENT_SECURITY"""" 16 = {ImmutableErrorModel@5743} """"MULE:NOT_PERMITTED"""" 17 = {ImmutableErrorModel@5744} """"MULE:SOURCE"""" 18 = {ImmutableErrorModel@5745} """"MULE:SOURCE_RESPONSE"""" 19 = {ImmutableErrorModel@5746} """"MULE:SOURCE_ERROR_RESPONSE_GENERATE"""" 20 = {ImmutableErrorModel@5747} """"MULE:SOURCE_ERROR_RESPONSE_SEND"""" 21 = {ImmutableErrorModel@5748} """"MULE:SOURCE_RESPONSE_GENERATE"""" 22 = {ImmutableErrorModel@5749} """"MULE:SOURCE_RESPONSE_SEND"""" 23 = {ImmutableErrorModel@5750} """"MULE:CRITICAL"""" 24 = {ImmutableErrorModel@5751} """"MULE:OVERLOAD"""" 25 = {ImmutableErrorModel@5752} """"MULE:FATAL_JVM_ERROR"""" """"errors"""": [],",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13715","10/04/2017 22:03:20",2,"Logger component does not support parse in DW ""Logger component does not support parse in DW""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13720","10/05/2017 15:31:19",5,"WSC value providers should use the same mechanism as the runtime to parse de wsdl ""WSC value providers should use the same mechanism as the runtime to parse de wsdl""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13723","10/05/2017 17:20:02",0,"Support out-of-browser applications in OAuth module redirect url ""In case an out of browser redirection, avoid creating the http listener.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13725","10/05/2017 19:18:17",5,"No way to limit VM Listener message consumption ""VM Listener consumers are consuming messages from the queue right after dispatching the message to the flow. This causes that if I have maxConcurrency=""""1"""" in the flow and numberOfConsumers=""""1"""" in the listener, the listener will still consume messages from the queue and fail when dispatching the message to the flow with an OVERLOAD error type. I should have a way to consume messages one by one without losing them. There are a couple of system tests ignored because of this.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13727","10/05/2017 23:43:09",1,"Update spring schemas to 3.9 ""Update spring schemas to 3.9 ""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13732","10/06/2017 13:16:06",8,"GraphTransformerResolver is not handling correctly concurrency access ""GraphTransformerResolver is not correctly synchronizing the access to the graph implementation through the strategy (graph implementation does not support concurrency). """," Root Exception stack trace: java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) at java.util.ArrayList$Itr.next(ArrayList.java:851) at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042) at org.mule.transformer.graph.TransformationGraphLookupStrategy.findTransformationPaths(TransformationGraphLookupStrategy.java:110) at org.mule.transformer.graph.TransformationGraphLookupStrategy.findTransformationPaths(TransformationGraphLookupStrategy.java:122) at org.mule.transformer.graph.TransformationGraphLookupStrategy.findTransformationPaths(TransformationGraphLookupStrategy.java:122) at org.mule.transformer.graph.TransformationGraphLookupStrategy.findTransformationPaths(TransformationGraphLookupStrategy.java:122) at org.mule.transformer.graph.TransformationGraphLookupStrategy.findTransformationPaths(TransformationGraphLookupStrategy.java:122) at org.mule.transformer.graph.TransformationGraphLookupStrategy.findTransformationPaths(TransformationGraphLookupStrategy.java:122) at org.mule.transformer.graph.TransformationGraphLookupStrategy.lookupConverters(TransformationGraphLookupStrategy.java:61) at org.mule.transformer.graph.GraphTransformerResolver.resolve(GraphTransformerResolver.java:57) at org.mule.registry.TypeBasedTransformerResolver.resolve(TypeBasedTransformerResolver.java:96) at org.mule.registry.MuleRegistryHelper.resolveTransformer(MuleRegistryHelper.java:263) at org.mule.registry.MuleRegistryHelper.lookupTransformer(MuleRegistryHelper.java:231) at org.mule.devkit.processor.ExpressionEvaluatorSupport.transform(ExpressionEvaluatorSupport.java:454) at org.mule.devkit.processor.ExpressionEvaluatorSupport.evaluateAndTransform(ExpressionEvaluatorSupport.java:273) at com.ravago.edi.connectors.httpravagoservice.generated.processors.HttpCallMessageProcessor.doProcess(HttpCallMessageProcessor.java:151) at org.mule.devkit.processor.DevkitBasedMessageProcessor.process(DevkitBasedMessageProcessor.java:89)",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13733","10/06/2017 14:36:34",0,"Avoid the need of the UBER_BRANCH in extensions-maven-plugin ""Avoid having to maintain an extra branch for mule-extensions-plugin, while keeping a practical way to disable extension model generation in uber builds for reduced build time.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13739","10/06/2017 19:43:10",5,"Wrong HTTP and WSC stereotypes ""In the WSC connection provider there's a field with the following stereotype model: And the HTTP's request config has the following stereotype: The stereotype model in the WSC field should have the http namespace in upper case, and the type of the stereotype of the HTTP config should be """"requestConfig"""" instead of """"CONFIG"""". Also, there's an inconsistency between regular parameters and fields (ie, inside a pojo), because the parameterModel accepts an array of allowedStereotypes, while the fields accept only one stereotypeModel."""," """"stereotype"""": { """"stereotypeModel"""": { """"type"""": """"requestConfig"""",     """"namespace"""": """"http"""",     """"parent"""": {       """"type"""": """"MODULE_CONFIG"""",      """"namespace"""": """"MULE""""     } } } """"stereotype"""": { """"type"""": """"CONFIG"""",   """"namespace"""": """"HTTP"""",   """"parent"""": {     """"type"""": """"MODULE_CONFIG"""",     """"namespace"""": """"MULE""""   } }",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13743","10/09/2017 12:25:01",8,"Support for Dynamic metadata for SourceCallback response parameters ""Add support for Dynamic metadata for the types of these response parameters, since metadata makes no sense for configuration parameters, but add's value for parameters that support expressions, which is the case for the response parameters.  ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13749","10/09/2017 21:42:47",2,"FixedFrequencyScheduler and CronScheduler should be API but has package Internal ""{{org.mule.runtime.core.internal.source.polling.FixedFrequencyScheduler}} and {{org.mule.runtime.core.internal.source.polling.CronScheduler}} should be moved to `core.api`""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13750","10/09/2017 21:51:18",2,"UntilSucessful and FirstSuccessful are missing from Mule ExtensionModel ""UntilSucessful and FirstSuccessful are missing from Mule ExtensionModel,""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13755","10/10/2017 22:35:39",1,"Is not possible to determine if a serialized MuleDeployableModel is valid ""When a MuleDeployableModel is deserialized form a mule-artifact.json is not possible to determine if the json file contained a given attribute or not.  For example, if a mule-artifact.json does not contains the configs attribute, then the generated  MuleDeployableModel will have a null configs attribute, until the getConfigs method is invoked. At this point, an empty list will be assigned to that field. So, if we want to determine if the configs element was configured or not, there is no way to distinguish a non configured attribute from an attribute configured with an empty list. This distinction is needed from the packager plugin in order to determine whether or not a default value has to be autogenerated for it.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13757","10/10/2017 23:17:22",1,"@Export annotation not exporting resources ""When using the @Export in a SDK extension and specifying both classes and resources, the resources don't end up being exported in the mule-artifact.json Example Extension definition Resolved json """," @Extension(name = """"SoapFault"""") @Export(classes = MyClass.class, resources = {""""Soap.dwl""""}) public class SoapFaultExtension { } { """"extensionModelLoaderDescriptor"""": { """"id"""": """"java"""", """"attributes"""": { """"type"""": """"com.mulesoft.extension.gateway.soap.fault.SoapFaultExtension"""", """"version"""": """"1.0.0-SNAPSHOT"""" } }, """"name"""": """"SoapFault"""", """"requiredProduct"""": """"MULE"""", """"classLoaderModelLoaderDescriptor"""": { """"id"""": """"mule"""", """"attributes"""": { """"privilegedExportedPackages"""": [], """"privilegedArtifactIds"""": [], """"exportedPackages"""": [ """"com.mulesoft.extension.gateway.soap.fault"""" ], """"exportedResources"""": [] } }, """"bundleDescriptorLoader"""": { """"id"""": """"mule"""", """"attributes"""": {} }, """"minMuleVersion"""": """"4.0.0"""" } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13760","10/11/2017 14:09:51",1,"ConfigOverride type annotation should be private ""Make it private""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13773","10/11/2017 19:44:09",8,"OOM Metaspace while resolving DataSense on Tooling Runtime Client ""Seems that when Tooling Runtime Client has heavy load the approach of keeping ClassLoaders alive for ExtensionModels is generating a Metaspace issue.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13774","10/11/2017 19:48:50",2,"Add notifications to HTTP request ""Notifications were removed from the HTTP requester because the API to handle them from extensions had not been defined yet. We need to bring those back.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13782","10/12/2017 17:58:51",2,"Tests plugins must be used on tests only ""There are a couple of Mule plugins used for testing purposes or for compatiblity plugin. We need to add extra checks to avoid having those plugins deployed on a productive application, as they are intended to be used only by us.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13783","10/12/2017 18:14:48",2,"Update logger to use DW logging function ""Update logger to use DW logging function""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13784","10/12/2017 18:49:21",1,"Remove support for properties descriptors in service and server plugins ""Container still supports services and server plugins packaged using the old model. This support must be removed before going GA.""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13785","10/12/2017 18:49:22",1,"Remove support for properties descriptors in service and server plugins ""Container still supports services and server plugins packaged using the old model. This support must be removed before going GA.""","",0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13790","10/13/2017 15:34:34",1,"Configs in MuleApplicationModel should be a Set not a List ""Right now the MuleApplicationModel has the configs field which is a list, but this may lead to inconsistent behavior since it allows duplicate values. The field should be a Set.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13791","10/13/2017 16:31:39",1,"Add minMuleVersion method to ExtensionModel DTO ""Add minMuleVersion method to ExtensionModel DTO""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13792","10/13/2017 18:21:24",3,"Soap Service: add flag to log request/response ""Soap Service: add flag to log request/response""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13797","10/13/2017 21:37:37",1,"Create maven plugin to packager Mule server plugins ""Need a maven plugin to package server plugins for Mule 4""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13802","10/17/2017 14:12:40",2,"Clean up notification helpers to improve performance ""Review, cleanup and simply to avoid the use of caches where not needed in order to improve performance. - NotificationHelper - NotificationFiringProcessingPhase - (maybe others too)""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13804","10/17/2017 18:23:35",5,"extension-model.json still ship in extension binary ""extension-model.json is still shipped in the binary. Just like the schema, it needs to only be generated as a test-resource but not shipped in the end product""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13815","10/18/2017 15:48:36",5,"DslSyntaxResolver should not use class to resolve information about it ""When resolving DslSyntax the class should not be used in order to run this on contexts where class loader for extension is not available.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13818","10/18/2017 20:57:38",1,"Missing DefaultImplementingTypeModelProperty from Tooling API ""Add mapping and include in API DefaultImplementingTypeModelProperty.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13819","10/18/2017 21:51:11",1,"MuleDeployableArtifactClassLoader not registered as parallelCapable ""This may cause contention in classloading.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13820","10/18/2017 22:33:08",5,"Soap Service is not passing the real soapAction but the soap operation name ""Soap Service is not passing the real soapAction but the soap operation name""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13826","10/19/2017 13:32:38",1,"Create error message in HttpListenerPolicyPointcutParametersFactory lazily ""Create error message in HttpListenerPolicyPointcutParametersFactory lazily ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13824","10/19/2017 13:45:32",1,"Add ability to evaluate error message lazily when using preconditions. ""Add ability to evaluate error message lazily when using preconditions.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13827","10/19/2017 14:06:13",2,"Remove unnecessary internal message processors in AbastractPipeline and DefaultFlow ""Remove unnecessary internal message processors in AbastractPipeline and DefaultFlow ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13828","10/19/2017 14:27:03",1,"Avoid resolving notification simple name whenever a notification is instantiated ""Avoid resolving notification simple name whenever a notification is instantiated""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13831","10/19/2017 16:48:32",8,"Use shared reactor stream(s) rather than once per event for performance and back-pressure ""Create reactor stream once per source thread rather than once per event. This issue is required for: - Performance (but also requires MULE-14113) - To support back-pressure. There are a number of options: - Use single shared stream and synchronize onNext - Use single shared stream with ringBuffer - Use a shared stream for each source thread. Before implementing this, some tests to decide the best approach for performance will be required. Also need to determine if back-pressure per source thread works in some scenarios, or if we will always need more global back-pressure. It will be hard to do performance testing of the different options without MULE-14113 complete.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13833","10/19/2017 18:11:54",2,"Change default sslType to use the JVM's one. ""Current default sslType is being set to TLSv1 which is old and removed from our infrastructure. Though this does not mean it's being used it does alter the default cipher suites to use in socket scenarios since the list will be very limited. I believe we should use the JVM's default instead.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13835","10/19/2017 21:03:18",8,"Make the Schema and ExtensionModel generated at compile time ""Make the Schema and ExtensionModel generated at compile or package time. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13836","10/19/2017 21:04:22",5,"SDK Router to be void ""In MUnit we have an operation called spy which is implemented with an SDK Router  We would like to have that router to return the same even that received regardless what happened in each possible route.  Assuming we have *E1* (event 1) entering the following SDK spy router, where before-call & after-call are routes:  We wish that the event coming out of the spy to be *E1.*  That is, variables, attributes, properties, sessions, message and its payload to remain those that were in E1"""," ",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13837","10/19/2017 21:59:56",1,"Avoid validating flow name for each new source request event ""Avoid validating flow name for each new source request event""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13841","10/20/2017 03:03:45",0,"Allow to reuse runner config without inherit all the config attributes ""ArtifactClassLoaderRunnerConfig annotation used to configure test that run with ArtifactClassLoaderRunner are currently scanned and the attributes for all the found configurations are merged into a new config. This approach is useful to inherit some attributes like testInclusions/inclusions or providedExclusions but not so useful for attributes like sharedRuntimeLibs and  extraPrivilegedArtifacts. The difference between those attributes is that the latest ones are validated against the pom for each executed test, requiring that the dependencies defined on those attributes are also defined on the pom. As some base test classes are reused from other modules, we want to reuse the code on those tests, but not necessarily to have the same classloader configuration. (shared libs for example) So, the idea is to inherit all the attributes that define inclusions/exclusions but only use the attributes that define dependencies from only one configuration.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13842","10/20/2017 12:18:42",2,"Stereotype name is lost after deserialization of tooling client model ""Stereotype models generated from a POJO field cannot be properly consumed because the name is lost and you only get the information about the namespace and the parent stereotype. This is affecting the WSC, as the HTTP requester config reference in the transport never reaches to studio, and cannot properly generate the link between the WSC and the HTTP extension models""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13847","10/20/2017 16:35:32",1,"Upgrade maven-shade-plugin to 3.1.0 ""Using previous version has the bug https://issues.apache.org/jira/browse/MSHADE-258 which causes the build of the extensions-maven-plugin to fail""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13850","10/20/2017 19:07:22",2,"Make dependencies to distro and agent explicit in tooling modules ""Some tooling modules require the mule distribution to run tests, referencing the maven dependency from a maven plugin. But not having those dependencies as dependencies of the module causes that module to not wait for the distro build when building the uber, but tries to download it from the repo. This may cause problems because tooling tests end up running with an out-of-date distro.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13852","10/21/2017 15:00:32",2,"Create master branch and 0.9.x on Tooling Runtime Client ""This will allow to deliver the two versions of Tooling (0.9.x and 1.x). Also define the mapping for implementation version on 0.9.x and review deployment scripts.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13853","10/21/2017 16:50:45",3,"MetadataKey Serializer brokes with MetadataKeys with more than two levels ""*MetadataKey Serializer brokes with MetadataKeys with more than two levels* * The *MetadataKeyTypeAdapter* is not reusing correctly the *gson* instance and looses the capability of deserialize correctly child keys. """," java.lang.RuntimeException: Unable to invoke no-args constructor for interface org.mule.runtime.api.metadata.MetadataKey. Register an InstanceCreator with Gson for this type may fix this problem. at com.google.gson.internal.ConstructorConstructor$14.construct(ConstructorConstructor.java:226) at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:206) at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdapterRuntimeTypeWrapper.java:40) at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:82) at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:61) at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:116) at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:216) at com.google.gson.Gson.fromJson(Gson.java:879) at com.google.gson.Gson.fromJson(Gson.java:944) at com.google.gson.Gson.fromJson(Gson.java:917) at org.mule.runtime.extension.internal.persistence.metadata.MetadataKeyTypeAdapter.lambda$read$0(MetadataKeyTypeAdapter.java:68) at java.lang.Iterable.forEach(Iterable.java:75) at org.mule.runtime.extension.internal.persistence.metadata.MetadataKeyTypeAdapter.read(MetadataKeyTypeAdapter.java:68) at org.mule.runtime.extension.internal.persistence.metadata.MetadataKeyTypeAdapter.read(MetadataKeyTypeAdapter.java:26) at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdapterRuntimeTypeWrapper.java:40) at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:82) at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:61) at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdapterRuntimeTypeWrapper.java:40) at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:187) at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:145) at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:116) at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:216) at com.google.gson.Gson.fromJson(Gson.java:879) at com.google.gson.Gson.fromJson(Gson.java:844) at com.google.gson.Gson.fromJson(Gson.java:793) at org.mule.runtime.extension.api.persistence.metadata.MetadataKeysResultJsonSerializer.deserialize(MetadataKeysResultJsonSerializer.java:53) at org.mule.runtime.extension.api.persistence.MetadataKeyResultPersistenceTestCase.test(MetadataKeyResultPersistenceTestCase.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.junit.runner.JUnitCore.run(JUnitCore.java:160) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.google.gson.internal.UnsafeAllocator$1.newInstance(UnsafeAllocator.java:48) at com.google.gson.internal.ConstructorConstructor$14.construct(ConstructorConstructor.java:223) ... 49 more Caused by: java.lang.InstantiationException: org.mule.runtime.api.metadata.MetadataKey at sun.misc.Unsafe.allocateInstance(Native Method) ... 54 more",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13856","10/23/2017 18:47:39",8,"Begin a TX inside of another should make the app fail instead of commit the original TX ""With the current Mule Config: *Current Behaviour*: When trying to execute the second *try* scope, the original TX will be committed, as consequence the *operations1* will be executed inside the first TX, *operations2* will be executed in the second TX, and *operations3* which statically should be executed inside the first TX, it will be executed outside of any TX because the corresponded TX is already closed. *Expected Behaviour* : If a TX is tried to be opened inside other TX this should fail. *Things to consider*: * *ALWAYS_BEGIN* loses any kind of sense to keep existing, because in any case that you force to create a new TX, or it will be created because no previously was created this means the same behaviour as *BEGIN_OR_JOIN*. * The current behaviour of the *ALWAYS_BEGIN* as the JavaDocs say is the equivalent of the J2EE's *RequiresNew*, but the expected behaviour if the *RequiresNew* is totally different when a new one is required, the original TX is suspended for the execution of the new one, behaviour that doesn't occur in Mule. * If *ALWAYS_BEGIN* keeps existing, and this construction is invalid, this could be validated in a future when """"compiling"""" the application."""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13860","10/23/2017 20:12:16",2,"Unable to fetch the CorrelationId from message ""*Unable to fetch the CorrelationId from message* In Mule4 the user is unable to fetch the Correlation ID of the message. Review if this is still necessary for Mule 4""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13863","10/23/2017 22:20:34",2,"Notifications fail in test:processor when flow executions wait ""In the test HttpListenerOverloadTestCase, remove enableNotifications=""""false"""" from http-listener-overload-config.xml so that notifications are enabled and run it.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13864","10/23/2017 22:39:47",2,"LinkageError when disposing app with policy ""When an app with a policy applied is disposed, a stack trace with a LinkageError appears: This can be reviewed executing most of the tests in ApplicationPolicyDeploymentTestCase in mule's project. The stack trace appears in the console"""," ERROR 2017-10-23 18:32:02,547 [Time-limited test] org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher: Error stopping artifact appWithExtensionPlugin-1.0.0-mule-application java.lang.LinkageError: loader (instance of org/mule/runtime/module/artifact/api/classloader/MuleDeployableArtifactClassLoader): attempted duplicate class definition for name: """"org/mule/module/artifact/classloader/DefaultResourceReleaser"""" at java.lang.ClassLoader.defineClass1(Native Method) ~[?:1.8.0_121] at java.lang.ClassLoader.defineClass(ClassLoader.java:763) ~[?:1.8.0_121] at java.lang.ClassLoader.defineClass(ClassLoader.java:642) ~[?:1.8.0_121] at org.mule.runtime.module.artifact.api.classloader.MuleArtifactClassLoader.createCustomInstance(MuleArtifactClassLoader.java:121) ~[classes/:?] at org.mule.runtime.module.artifact.api.classloader.MuleArtifactClassLoader.createResourceReleaserInstance(MuleArtifactClassLoader.java:134) ~[classes/:?] at org.mule.runtime.module.artifact.api.classloader.MuleArtifactClassLoader.dispose(MuleArtifactClassLoader.java:94) ~[classes/:?] at org.mule.runtime.module.artifact.api.classloader.RegionClassLoader.disposeClassLoader(RegionClassLoader.java:268) ~[classes/:?] at org.mule.runtime.module.artifact.api.classloader.RegionClassLoader.lambda$dispose$3(RegionClassLoader.java:258) ~[classes/:?] at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) ~[?:1.8.0_121] at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) ~[?:1.8.0_121] at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374) ~[?:1.8.0_121] at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) ~[?:1.8.0_121] at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) ~[?:1.8.0_121] at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) ~[?:1.8.0_121] at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) ~[?:1.8.0_121] at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:1.8.0_121] at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) ~[?:1.8.0_121] at org.mule.runtime.module.artifact.api.classloader.RegionClassLoader.dispose(RegionClassLoader.java:257) ~[classes/:?] at org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication.dispose(DefaultMuleApplication.java:358) ~[classes/:?] at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:792) ~[classes/:?] at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:215) ~[classes/:?] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:845) ~[classes/:?] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:811) ~[classes/:?] at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:791) ~[classes/:?] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.executeWithinArtifactClassLoader(DeployableArtifactWrapper.java:140) ~[classes/:?] at org.mule.runtime.module.deployment.impl.internal.artifact.DeployableArtifactWrapper.dispose(DeployableArtifactWrapper.java:44) ~[classes/:?] at org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher.stopArtifacts(DeploymentDirectoryWatcher.java:206) [classes/:?] at org.mule.runtime.module.deployment.internal.DeploymentDirectoryWatcher.stop(DeploymentDirectoryWatcher.java:193) [classes/:?] at org.mule.runtime.module.deployment.internal.MuleDeploymentService.stop(MuleDeploymentService.java:161) [classes/:?] at org.mule.runtime.module.deployment.internal.AbstractDeploymentTestCase.tearDown(AbstractDeploymentTestCase.java:403) [test-classes/:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_121] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_121] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_121] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_121] at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) [junit-4.12.jar:4.12] at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) [junit-4.12.jar:4.12] at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) [junit-4.12.jar:4.12] at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) [junit-4.12.jar:4.12] at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) [junit-4.12.jar:4.12] at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) [junit-4.12.jar:4.12] at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) [junit-4.12.jar:4.12] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_121] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13867","10/24/2017 18:43:38",2,"Enum config parameters are not set correctly ""We are migrating ServiceNow from RC to SNAPSHOT. Its SoapServiceProvider implementation, BasicServiceProvider, has this configurable parameter: When attempting to run the functional tests, it's trying to set that default string into the config, and fails because the attribute is not a string. This used to work fine in RC. Log is attached. Steps to reproduce: 1. Get the code from https://github.com/mulesoft/servicenow-wsdl-connector/tree/SNOWW-71 2. Run any of the functional tests If an automation-credentials.properties file is needed, let me know."""," @Parameter @Placement(order = 5) @Optional(defaultValue = """"ISTANBUL"""") @DisplayName(""""ServiceNow Version"""") private ServiceNowVersion serviceNowVersion; ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13871","10/24/2017 22:33:43",5,"VM consume operation collides with listener ""Publish operation validates that no message is posted to a queue for which a listener doesn't exist. However, the consume operation exists. This generates two problems: * Race condition between the consume operation and the listener * If two apps in a domain are using VM to communicate with each other and one gets undeployed, the other would fail to publish messages because there's no listener anymore. This validation needs to be lifted. On the contrary, the consume operation has to validate it's not trying to pull from a queue for which a listener exists.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13873","10/25/2017 00:55:04",3,"SFDC Connector failing while trying to delete records by id ""Referred to the attached Mule App, SFDC Connector fails while trying to delete a record by id. As: is being ignored, the dafault value #*[payload]* is taken. The result is the following exception:     Steps to reproduce: # Unzip sfdc-example.zip # Import to Studio 7.rc with File - Import Projects from System or Archive # Run the Mule App # Make a POST call to [http://localhost:8081/]    """," ERROR 2017-10-24 20:49:19,865 [[MuleRuntime].io.06] org.mule.runtime.core.internal.exception.OnErrorPropagateHandler: ******************************************************************************** Message               : """"Cannot coerce Object ({Id: """"00136000005O90gAAC"""" as String {class: """"java.lang.String""""}, """"type"""": """"Acc...) to Array"""" evaluating expression: """"payload"""". (org.mule.runtime.core.api.expression.ExpressionRuntimeException). Error Type            : MULE:EXPRESSION Element               : sfdc-exampleFlow/processors/1 @ sfdc-example:sfdc-example.xml:24 (Delete Account) Element XML           : #[[payload.Id]]     (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13874","10/25/2017 02:20:24",2,"DefaultScheduler#shutdownNow returns tasks that have already ran ""The tasks that are returned in shutdownNow are stored in the scheduler. It is storing the tasks that shouldn't be returned ant they end up taking a lot of memory that is not GC'd.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13876","10/25/2017 15:40:17",2,"MetadataKeyIdModelProperty NotExportedClassException on Tooling Client when loading extension model """""," Failed to resolve dynamic model. component: COMPONENT, element: , code: UNKNOWN - Reason: org.mule.tooling.client.api.exception.ToolingException: Error while getting Metadata org.mule.runtime.extension.internal.persistence.ExtensionModelSerializationException: Error loading [org.mule.runtime.extension.internal.property.MetadataKeyIdModelProperty] ModelProperty. Class not found in the current classloader at org.mule.runtime.extension.internal.persistence.ModelPropertyMapTypeAdapter.getClassForModelProperty(ModelPropertyMapTypeAdapter.java:102) at org.mule.runtime.extension.internal.persistence.ModelPropertyMapTypeAdapter.read(ModelPropertyMapTypeAdapter.java:84) at org.mule.runtime.extension.internal.persistence.ModelPropertyMapTypeAdapter.read(ModelPropertyMapTypeAdapter.java:41) at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:116) at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:216) at com.google.gson.Gson.fromJson(Gson.java:879) at com.google.gson.Gson.fromJson(Gson.java:944) at org.mule.runtime.extension.internal.persistence.ComponentResultTypeAdapter.read(ComponentResultTypeAdapter.java:95) at org.mule.runtime.extension.internal.persistence.ComponentResultTypeAdapter.read(ComponentResultTypeAdapter.java:40) at com.google.gson.Gson.fromJson(Gson.java:879) at com.google.gson.Gson.fromJson(Gson.java:844) at com.google.gson.Gson.fromJson(Gson.java:793) at org.mule.runtime.extension.api.persistence.metadata.ComponentResultJsonSerializer.deserialize(ComponentResultJsonSerializer.java:47) at org.mule.tooling.agent.rest.client.tooling.applications.applicationId.components.componentId.metadata.Metadata.get(Metadata.java:71) at org.mule.tooling.agent.rest.client.RestAgentToolingService.getMetadata(RestAgentToolingService.java:395) at org.mule.tooling.agent.rest.client.RestAgentToolingService.getOperationMetadata(RestAgentToolingService.java:373) at org.mule.tooling.client.internal.InternalMetadataProvider.lambda$getOperationMetadata$1(InternalMetadataProvider.java:84) at org.mule.tooling.client.internal.application.DefaultApplication.doInvoke(DefaultApplication.java:234) at org.mule.tooling.client.internal.application.DefaultApplication.evaluateWithRemoteApplication(DefaultApplication.java:157) at org.mule.tooling.client.internal.InternalMetadataProvider.getOperationMetadata(InternalMetadataProvider.java:82) at org.mule.tooling.client.internal.ToolingDataSenseMetadataProvider.getOperationMetadata(ToolingDataSenseMetadataProvider.java:65) at org.mule.datasense.api.metadataprovider.CachedDataSenseProvider$CachedDataSenseMetadataProvider.lambda$getOperationMetadata$1(CachedDataSenseProvider.java:81) at org.mule.tooling.client.internal.DataSenseMetadataCacheAdapter.lambda$getOperationMetadata$0(DataSenseMetadataCacheAdapter.java:43) at org.mule.tooling.metadata.cache.TrackingCacheDecorator.lambda$0(TrackingCacheDecorator.java:44) at org.mule.tooling.metadata.cache.DefaultMetadataCache.lambda$0(DefaultMetadataCache.java:68) at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660) at org.mule.tooling.metadata.cache.DefaultMetadataCache.getOrCreateFromToolingClient(DefaultMetadataCache.java:66) at org.mule.tooling.metadata.cache.DefaultMetadataCache.getOperationMetadata(DefaultMetadataCache.java:56) at org.mule.tooling.metadata.cache.TrackingCacheDecorator.getOperationMetadata(TrackingCacheDecorator.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.mule.tooling.client.internal.MetadataCacheProxy.invoke(MetadataCacheProxy.java:41) at org.mule.tooling.client.internal.MetadataCacheProxy.getOperationMetadata(MetadataCacheProxy.java:51) at org.mule.tooling.client.internal.DataSenseMetadataCacheAdapter.getOperationMetadata(DataSenseMetadataCacheAdapter.java:41) at org.mule.datasense.api.metadataprovider.CachedDataSenseProvider$CachedDataSenseMetadataProvider.getOperationMetadata(CachedDataSenseProvider.java:78) at org.mule.datasense.impl.phases.annotators.DynamicOperationAnnotator.resolveMetadata(DynamicOperationAnnotator.java:22) at org.mule.datasense.impl.phases.annotators.BaseDynamicAnnotator.lambda$null$1(BaseDynamicAnnotator.java:43) at java.util.Optional.map(Optional.java:215) at org.mule.datasense.impl.phases.annotators.BaseDynamicAnnotator.lambda$null$2(BaseDynamicAnnotator.java:36) at java.util.Optional.map(Optional.java:215) at org.mule.datasense.impl.phases.annotators.BaseDynamicAnnotator.lambda$resolveComponentModel$3(BaseDynamicAnnotator.java:33) at java.util.Optional.flatMap(Optional.java:241) at org.mule.datasense.impl.phases.annotators.BaseDynamicAnnotator.resolveComponentModel(BaseDynamicAnnotator.java:30) at org.mule.datasense.impl.phases.annotators.BaseExtensionAnnotator.lambda$annotate$5(BaseExtensionAnnotator.java:31) at java.util.Optional.ifPresent(Optional.java:159) at org.mule.datasense.impl.phases.annotators.BaseExtensionAnnotator.annotate(BaseExtensionAnnotator.java:30) at org.mule.datasense.impl.phases.annotators.OperationAnnotator.lambda$annotate$0(OperationAnnotator.java:18) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374) at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) at org.mule.datasense.impl.phases.annotators.OperationAnnotator.annotate(OperationAnnotator.java:18) at org.mule.datasense.impl.phases.annotators.OperationCallAnnotator.lambda$annotate$0(OperationCallAnnotator.java:34) at java.util.Optional.ifPresent(Optional.java:159) at org.mule.datasense.impl.phases.annotators.OperationCallAnnotator.annotate(OperationCallAnnotator.java:31) at org.mule.datasense.impl.phases.annotators.AnnotatorsRegistry.lambda$annotate$0(AnnotatorsRegistry.java:25) at java.util.ArrayList.forEach(ArrayList.java:1249) at org.mule.datasense.impl.phases.annotators.AnnotatorsRegistry.annotate(AnnotatorsRegistry.java:25) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.visit(AnnotatingMuleAstVisitor.java:44) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.visit(AnnotatingMuleAstVisitor.java:28) at org.mule.datasense.impl.model.ast.MessageProcessorNode.accept(MessageProcessorNode.java:90) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.annotate(AnnotatingMuleAstVisitor.java:131) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.visit(AnnotatingMuleAstVisitor.java:58) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.visit(AnnotatingMuleAstVisitor.java:28) at org.mule.datasense.impl.model.ast.MessageProcessorNode.accept(MessageProcessorNode.java:90) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.annotate(AnnotatingMuleAstVisitor.java:131) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.lambda$visit$11(AnnotatingMuleAstVisitor.java:119) at java.util.Optional.ifPresent(Optional.java:159) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.visit(AnnotatingMuleAstVisitor.java:119) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.visit(AnnotatingMuleAstVisitor.java:28) at org.mule.datasense.impl.model.ast.MuleFlowNode.accept(MuleFlowNode.java:56) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.annotate(AnnotatingMuleAstVisitor.java:131) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.lambda$visit$1(AnnotatingMuleAstVisitor.java:76) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374) at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.visit(AnnotatingMuleAstVisitor.java:75) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.visit(AnnotatingMuleAstVisitor.java:28) at org.mule.datasense.impl.model.ast.MuleApplicationNode.accept(MuleApplicationNode.java:43) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.annotate(AnnotatingMuleAstVisitor.java:131) at org.mule.datasense.impl.phases.typing.AnnotatingMuleAstVisitor.annotate(AnnotatingMuleAstVisitor.java:127) at org.mule.datasense.impl.phases.typing.AstTyping.annotate(AstTyping.java:32) at org.mule.datasense.impl.phases.typing.AstTyping.annotate(AstTyping.java:27) at org.mule.datasense.impl.DataSenseApplicationModel.resolve(DataSenseApplicationModel.java:159) at org.mule.datasense.impl.DefaultDataSense.resolve(DefaultDataSense.java:266) at org.mule.tooling.client.internal.DefaultDataSenseService.lambda$internalResolveDataSense$1(DefaultDataSenseService.java:132) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:215) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:845) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:811) at org.mule.tooling.client.internal.DefaultDataSenseService.internalResolveDataSense(DefaultDataSenseService.java:131) at org.mule.tooling.client.internal.DefaultDataSenseService.resolveDataSense(DefaultDataSenseService.java:98) at org.mule.tooling.client.internal.DefaultDataSenseService.invokeMethod(DefaultDataSenseService.java:222) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.mule.tooling.client.bootstrap.internal.reflection.Dispatcher.invoke(Dispatcher.java:68) at org.mule.tooling.client.bootstrap.internal.reflection.Dispatcher.dispatchRemoteMethod(Dispatcher.java:113) at org.mule.tooling.client.bootstrap.internal.wrapper.DataSenseServiceWrapper.resolveDataSense(DataSenseServiceWrapper.java:44) at org.mule.tooling.client.agent.impl.DefaultAgentPropagationToolingService.resolvePropagation(DefaultAgentPropagationToolingService.java:83) at org.mule.tooling.client.agent.impl.DefaultAgentPropagationToolingService.resolveFlowPropagation(DefaultAgentPropagationToolingService.java:62) at org.mule.tooling.ui.modules.core.metadata.MetadataPropagationResolver$PropagationJob.run(MetadataPropagationResolver.java:192) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.mule.runtime.module.artifact.api.classloader.exception.CompositeClassNotFoundException: Cannot load class ‘org.mule.runtime.extension.internal.property.MetadataKeyIdModelProperty’: [ Cannot load class ‘org.mule.runtime.extension.internal.property.MetadataKeyIdModelProperty’: [ Class ‘org.mule.runtime.extension.internal.property.MetadataKeyIdModelProperty’ not found in classloader for artifact ‘container’.]] at org.mule.runtime.module.artifact.api.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:98) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at org.apache.commons.lang3.ClassUtils.getClass(ClassUtils.java:923) at org.apache.commons.lang3.ClassUtils.getClass(ClassUtils.java:989) at org.apache.commons.lang3.ClassUtils.getClass(ClassUtils.java:972) at org.mule.runtime.extension.internal.persistence.ModelPropertyMapTypeAdapter.getClassForModelProperty(ModelPropertyMapTypeAdapter.java:99) ... 101 more Caused by: org.mule.runtime.module.artifact.api.classloader.exception.CompositeClassNotFoundException: Cannot load class ‘org.mule.runtime.extension.internal.property.MetadataKeyIdModelProperty’: [ Class ‘org.mule.runtime.extension.internal.property.MetadataKeyIdModelProperty’ not found in classloader for artifact ‘container’.] at org.mule.runtime.module.artifact.api.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:98) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.mule.runtime.module.artifact.api.classloader.FineGrainedControlClassLoader.findParentClass(FineGrainedControlClassLoader.java:135) at org.mule.runtime.module.artifact.api.classloader.FineGrainedControlClassLoader.loadClass(FineGrainedControlClassLoader.java:89) ... 108 more Caused by: org.mule.runtime.module.artifact.api.classloader.exception.NotExportedClassException: Class ‘org.mule.runtime.extension.internal.property.MetadataKeyIdModelProperty’ not found in classloader for artifact ‘container’. at org.mule.runtime.module.artifact.api.classl...",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13877","10/25/2017 15:42:47",2,"ComponentModel#getNameAttribute for configuration tag return null ""Have a mule config with a configuration tag (for instance, for setting a global error handler). When calling ConfigurationComponentLocator#findAllLocations(), the location for the configuration returns the string """"null"""". I traced this to ComponentLocationVisitor line 98, where it returns null.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13884","10/25/2017 20:36:52",2,"Exception are logged everytime you invoke metadata propagation ""Whenever Studio invokes the tooling client to get propagation in an app, the following exception is logged: The app has the following lof4j.xml configuration: This is the default configuration we are creating for every single app."""," 2017-10-25 16:26:31,137 Worker-6 ERROR Unable to invoke factory method in class class org.apache.logging.log4j.core.async.AsyncLoggerConfig$RootLogger for element AsyncRoot. java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:132) at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:952) at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:892) at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:884) at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:508) at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:232) at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:244) at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:545) at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:617) at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634) at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45) at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194) at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:122) at org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:43) at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46) at org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:29) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383) at org.mule.extension.socket.api.connection.tcp.protocol.AbstractByteProtocol.(AbstractByteProtocol.java:32) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at org.apache.commons.lang3.ClassUtils.getClass(ClassUtils.java:923) at org.mule.metadata.java.api.utils.JavaTypeUtils.lambda$getType$0(JavaTypeUtils.java:125) at java.util.Optional.map(Optional.java:215) at org.mule.metadata.java.api.utils.JavaTypeUtils.getType(JavaTypeUtils.java:123) at org.mule.runtime.extension.api.util.ExtensionMetadataTypeUtils.getType(ExtensionMetadataTypeUtils.java:81) at org.mule.runtime.extension.api.util.ExtensionMetadataTypeUtils.getType(ExtensionMetadataTypeUtils.java:66) at org.mule.runtime.module.extension.internal.util.IntrospectionUtils.isInstantiable(IntrospectionUtils.java:561) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) at org.mule.runtime.module.extension.internal.config.dsl.DefaultExtensionBuildingDefinitionProvider.registerTopLevelParameters(DefaultExtensionBuildingDefinitionProvider.java:289) at org.mule.runtime.module.extension.internal.config.dsl.DefaultExtensionBuildingDefinitionProvider.registerExportedTypesTopLevelParsers(DefaultExtensionBuildingDefinitionProvider.java:262) at org.mule.runtime.module.extension.internal.config.dsl.DefaultExtensionBuildingDefinitionProvider.lambda$registerExtensionParsers$0(DefaultExtensionBuildingDefinitionProvider.java:149) at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:792) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:215) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:845) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:811) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:791) at org.mule.runtime.module.extension.internal.config.dsl.DefaultExtensionBuildingDefinitionProvider.registerExtensionParsers(DefaultExtensionBuildingDefinitionProvider.java:108) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) at org.mule.runtime.module.extension.internal.config.dsl.DefaultExtensionBuildingDefinitionProvider.init(DefaultExtensionBuildingDefinitionProvider.java:84) at org.mule.runtime.config.internal.util.ComponentBuildingDefinitionUtils.lambda$registerComponentBuildingDefinitions$0(ComponentBuildingDefinitionUtils.java:51) at java.lang.Iterable.forEach(Iterable.java:75) at org.mule.runtime.config.internal.util.ComponentBuildingDefinitionUtils.registerComponentBuildingDefinitions(ComponentBuildingDefinitionUtils.java:44) at org.mule.tooling.client.internal.DefaultApplicationModelFactory.createComponentBuildingDefinitionRegistry(DefaultApplicationModelFactory.java:172) at org.mule.tooling.client.internal.DefaultApplicationModelFactory.lambda$loadApplicationModel$5(DefaultApplicationModelFactory.java:158) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:215) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:845) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:811) at org.mule.tooling.client.internal.DefaultApplicationModelFactory.loadApplicationModel(DefaultApplicationModelFactory.java:155) at org.mule.tooling.client.internal.DefaultApplicationModelFactory.createApplicationModel(DefaultApplicationModelFactory.java:76) at org.mule.tooling.client.internal.application.DefaultApplication.lambda$newApplicationModelLazyValue$2(DefaultApplication.java:282) at org.mule.runtime.api.util.LazyValue.lambda$new$1(LazyValue.java:44) at org.mule.runtime.api.util.LazyValue.get(LazyValue.java:69) at org.mule.tooling.client.internal.application.DefaultApplication.getApplicationModel(DefaultApplication.java:244) at org.mule.tooling.client.internal.DefaultDataSenseService.buildDataSenseApplicationModel(DefaultDataSenseService.java:175) at org.mule.tooling.client.internal.DefaultDataSenseService.internalResolveDataSense(DefaultDataSenseService.java:122) at org.mule.tooling.client.internal.DefaultDataSenseService.resolveDataSense(DefaultDataSenseService.java:98) at org.mule.tooling.client.internal.DefaultDataSenseService.invokeMethod(DefaultDataSenseService.java:222) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.mule.tooling.client.bootstrap.internal.reflection.Dispatcher.invoke(Dispatcher.java:68) at org.mule.tooling.client.bootstrap.internal.reflection.Dispatcher.dispatchRemoteMethod(Dispatcher.java:113) at org.mule.tooling.client.bootstrap.internal.wrapper.DataSenseServiceWrapper.resolveDataSense(DataSenseServiceWrapper.java:44) at org.mule.tooling.client.agent.impl.DefaultAgentPropagationToolingService.resolvePropagation(DefaultAgentPropagationToolingService.java:83) at org.mule.tooling.client.agent.impl.DefaultAgentPropagationToolingService.resolveFlowPropagation(DefaultAgentPropagationToolingService.java:62) at org.mule.tooling.ui.modules.core.metadata.MetadataPropagationResolver$PropagationJob.run(MetadataPropagationResolver.java:189) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.lang.NoClassDefFoundError: com/lmax/disruptor/EventFactory at org.apache.logging.log4j.core.config.AbstractConfiguration.getAsyncLoggerConfigDelegate(AbstractConfiguration.java:202) at org.apache.logging.log4j.core.async.AsyncLoggerConfig.(AsyncLoggerConfig.java:82) at org.apache.logging.log4j.core.async.AsyncLoggerConfig$RootLogger.createLogger(AsyncLoggerConfig.java:227) ... 85 more Caused by: java.lang.ClassNotFoundException: com.lmax.disruptor.EventFactory at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 88 more ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13889","10/26/2017 15:13:42",3,"Stereotype information is lost when used in extension types ""The object store extension contributes with 2 object stores, both annotated with the following annotation: But this information is not being serialized into the JSON that represents it making impossible for the tooling client to retrieve it. Because of this, the object store extension cannot be used properly from Studio, as we don't have the necessary information to link all the elements."""," .... @Stereotype(ObjectStoreStereotype.class) public class PrivateObjectStore extends ExtensionObjectStore { .... ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13894","10/26/2017 17:16:16",8,"DataSense not working for plugins that defined Routes with SDK ""Tooling Client is not able to load the componentBuidlingDefinitionProvider for plugins that define Routes. It is trying to access a class for resolving the parsers for Route: """," private void parseRoute(NestedRouteModel routeModel) { DslElementSyntax routeDsl = dslResolver.resolve(routeModel); Class type = routeModel.getModelProperty(ImplementingTypeModelProperty.class) .map(ImplementingTypeModelProperty::getType) .orElseThrow(() -> new IllegalStateException(""""Missing route information"""")); ----> Breaks at this point as extensionModel used here is the serialized (public) with this model property MetadataType metadataType = typeLoader.load(type); addParameter(getChildKey(routeModel.getName()), new DefaultObjectParsingDelegate().parse(routeModel.getName(), (ObjectType) metadataType, routeDsl)); try { new RouteComponentParser(baseDefinitionBuilder, routeModel, metadataType, getContextClassLoader(), routeDsl, dslResolver, parsingContext).parse() .forEach(this::addDefinition); } catch (Exception e) { throw new MuleRuntimeException(new ConfigurationException(e)); } }",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13891","10/26/2017 17:46:43",5,"Non repeatable streams are not managed to guarantee closing them ""When using non repeatable streams these are not managed since none of the repeatable capabilities will be """"injected"""". However, another part of that management is guaranteeing that the streams are closed once the root event is completed. As a consequence, when the scheduler is unavailable and a MULE:OVERLOAD error raised there's no way to close the payload stream. In the case of the HTTP request operation, zombie streams end up taking over all selector threads and blocking.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13893","10/26/2017 22:43:48",1,"Upgrade reactor to 3.1.1 ""https://github.com/reactor/reactor-core/releases/tag/v3.1.1.RELEASE""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13896","10/27/2017 16:18:34",8,"Improve how URIs are created ""URI creation is done in several classes (e.g. HttpResponseToResult, HttpRequestFactory, NameResolvingRequestBuilder), so many are being created more than once.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13897","10/27/2017 16:26:49",2,"Mule Maven plugins must shade mule dependencies ""Otherwise, the mule-uber build fails.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13902","10/27/2017 21:25:16",5,"Support initialisable operation parameters ""Operations can only take parameters defined as method arguments, which are only available when the operation is invoked. There are cases in which it is necessary to have some parameters already resolved during the lifecycle phase. We should support annotating fields with @Parameters (no expressions supported).   Those parameters should already be resolved at deployment time.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13905","10/28/2017 16:08:54",1,"Fix flaky error handling unit tests ""Fix those flaky tests""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13906","10/29/2017 02:30:06",2,"Update system test to use a server plugin packaged with the maven plugin ""Migrate com.mulesoft.mule.distributions.server.plugin.MuleManagementTestCase to use server plugins with the new format instead of the one using the old properties descriptor.  Ideally, those server plugins have to be packaged using the mule-server-plugin-maven-plugin""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13913","10/30/2017 18:06:20",1,"Move WSDL parser to 1.0.0-SNAPSHOT ""Move WSDL parser to 0.9.0-SNAPSHOT""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13915","10/30/2017 21:18:34",5,"Streaming Temporal files reused if mule is restarted ""Because of the naming algorithm used when generating the streaming buffer files, if the runtime is restarted, the content from past streams is used instead of the ones from the current streams""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13919","10/31/2017 17:42:17",2,"Plugin classloader not re-used when policy has it as a transitive dependency ""When a policy has a direct dependency on a plugin that the app also has, then the plugin classloader is reused. This is not happening when that plugin is not a direct dependency but a transitive one. For example, a policy that defines APIKIT, which has HTTP as transitive. Was not able to create a test to reproduce this, but we have one in our repo that is failing because of this: https://github.com/mulesoft/mule-raml-validator-policy/blob/1.x/integration-tests/src/test/java/com/mulesoft/anypoint/templates/RamlValidatorPolicyTestCase.java #badEndpointRequest Placing a breakpoint in *org.mule.extension.http.api.policy.HttpListenerPolicyParametersTransformer* in the line you can verify that *HttpPolicyResponseAttributes* class, was loaded by two different classloaders (one the App's plugin, and the other, the policy's plugin)"""," } else if(message.getAttributes().getValue() instanceof HttpPolicyResponseAttributes) { ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13920","10/31/2017 17:53:39",5,"@Stereotypes annotation is not being exported ""@Stereotypes annotation is not being exporteed, there is something is the routers schema generation that is failing when this annotation is being exported.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13921","10/31/2017 18:21:50",1,"Add Value Providers for SubSubProtocols in Derby Connection Provider ""Add Value Providers for SubSubProtocols in Derby Connection Provider""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0 +"MULE-13922","10/31/2017 19:32:04",8,"NoClassDefFoundError: org/mule/runtime/core/internal/connection/HasDelegate ""When running any functional test in Oracle EBS Connector, we are getting the attached stacktrace. The same happens when attempting to run a Mule application using the connector in Mozart QAX. Not 100% sure if this is an SDK issue or if it's something in the connector. But I know the RC connector used to work. Steps to reproduce: 1. Checkout oracle-ebs-connector develop branch. This is the latest commit at this moment: https://github.com/mulesoft/oracle-ebs-connector/commit/f74044c6171ed1d3f847e4b5b298b9832bb9b143 2. mvn clean install -DskipTests 3. Attempt to run any functional test case, such as CrudDeltaServicesMetadataTestCase.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13923","10/31/2017 21:17:35",3,"If an SDK Java operation has an Alias with an invalid character a ConfigurationException is thrown ""If an operation declares an invalid alias an error is thrown: The following error is thrown: It would be better to handle this while extension model is generated and hyphenized  """," public final class JmsAcknowledge {   private static final Logger LOGGER = getLogger(JmsAcknowledge.class);   @Inject   private JmsSessionManager sessionManager;   /**    * Allows the user to perform an ACK when the {@link AckMode#MANUAL} mode is elected while consuming the {@link Message}.    * As per JMS Spec, performing an ACK over a single {@link Message} automatically works as an ACK for all the {@link Message}s    * produced in the same {@link JmsSession}.    *    * @param ackId The AckId of the Message to ACK    * @throws JmsAckException if the {@link JmsSession} or {@link JmsConnection} were closed, or if the ID doesn't belong    * to a session of the current connection    */   @Throws(JmsAckErrorTypeProvider.class)   @Alias(value = """"my#ack"""")   public void ack(@Summary(""""The AckId of the Message to ACK"""") String ackId) { ================================================================================ = Testing: sessionIsAutomaticallyRecoverOnErrorFlow                            = ================================================================================ java.lang.AssertionError: An exception was caught but it wasn't expected for the test Caught exception was: org.mule.runtime.core.api.config.ConfigurationException: org.mule.runtime.api.exception.MuleRuntimeException: There were '5' errors while parsing the given file 'ack/jms-ack.xml'. Full list: org.xml.sax.SAXParseException; systemId: http://www.mulesoft.org/schema/mule/jms/current/mule-jms.xsd; lineNumber: 908; columnNumber: 191; s4s-att-invalid-value: Invalid attribute value for 'type' in element 'element'. Recorded reason: cvc-datatype-valid.1.2.1: 'My#ackType' is not a valid value for 'QName'. org.xml.sax.SAXParseException; systemId: http://www.mulesoft.org/schema/mule/jms/current/mule-jms.xsd; lineNumber: 909; columnNumber: 37; s4s-att-invalid-value: Invalid attribute value for 'name' in element 'complexType'. Recorded reason: cvc-datatype-valid.1.2.1: 'My#ackType' is not a valid value for 'NCName'. org.xml.sax.SAXParseException; systemId: http://www.mulesoft.org/schema/mule/jms/current/mule-jms.xsd; lineNumber: 909; columnNumber: 37; s4s-att-must-appear: Attribute 'name' must appear in element 'complexType'. org.xml.sax.SAXParseException; lineNumber: 25; columnNumber: 55; cvc-complex-type.2.4.a: Invalid content was found starting with element 'jms:ack'. One of '{""""http://www.mulesoft.org/schema/mule/core"""":abstract-message-processor, """"http://www.mulesoft.org/schema/mule/core"""":abstract-mixed-content-message-processor}' is expected. org.xml.sax.SAXParseException; lineNumber: 47; columnNumber: 38; cvc-complex-type.2.4.a: Invalid content was found starting with element 'jms:ack'. One of '{""""http://www.mulesoft.org/schema/mule/core"""":abstract-message-processor, """"http://www.mulesoft.org/schema/mule/core"""":abstract-mixed-content-message-processor, """"http://www.mulesoft.org/schema/mule/core"""":response, """"http://www.mulesoft.org/schema/mule/core"""":abstract-exception-strategy}' is expected. org.mule.runtime.core.api.config.ConfigurationException: org.mule.runtime.api.exception.MuleRuntimeException: There were '5' errors while parsing the given file 'ack/jms-ack.xml'.",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13926","10/31/2017 21:37:49",3,"VM listener drops messages in overflow scenarios ""If the listener generates messages faster than the flow can process them, MULE-13925 and MULE-13924 manifest and the messages are lost. As a work around, use a with a transactional instead""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13927","11/01/2017 10:24:30",5,"CorrelationId is not propagated from connector sources to Flow ""When a JMS/AMQP or other messaging connector source is used the inbound correlationID (as defined in the relevant specification) should be propagated to the Flow by creating the EventContext using this external correlationID instead of passing null and allowing it to generate a UUID. This is important because: - It is a regression from 3.x - The EventContext javadoc states that external correlationId is available via getCorrelationId() - This was discussed in detail with use case and reviewed by support when new eventContext/event/message model was defined and current implementation does not match what was defined. - From a user perspective, it is important that if an external correlationId is present that this is seen in log entries and in insights/analytics records instead of a UUID in the platform. - From a supportability perspective not maintaining the external correlationID makes it much harder for users and our support team to find/resolve issues. This applies to all connectors where the concept of correlationId is present in the spec, but we should also consider using """"X-Correlation-ID"""" if present in inbound HTTP messages too. (this is not a standard but is best practice) A future improvement should allow the correlationID to be customised in the source using a DW expression DW, but the default behaviour should be to use an external correlationID. See MULE-13930. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13928","11/01/2017 10:49:20",8,"CorrelationId should be propagated from flow to other flows or systems via connector operations ""When a JMS/AMQP or other messaging connector operation is used (e.g. jms:publish) the Flow correlationID should be propagated via the outbound message as an external correlationID (as defined in the relevant specification). This is important both from a functional perspective to allow for traceability of transactions across multiple flows and external applications via analytics/insights, log output and customer use of Splunk and other such tools. But is also very important for the supportability of customer solutions by our support team. Given traceability and supportability is a cross-cutting concern of huge value to users of our platform, propagation of correlationID's for this purpose should happen by default and the user should not need to i) turn it on specifically ii) have any specific knowledge of what specific headers should be configured manually in order to achieve the necessary propagation to achieve traceability and supportability. This applies to all connectors where the concept of correlationId is present in the spec, but we should seriously consider also using """"X-Correlation-ID"""" on outbound HTTP messages too. (this is not a standard but is best practice). See: http://hilton.org.uk/blog/microservices-correlation-id https://blog.logentries.com/2016/12/the-value-of-correlation-ids/ See: MULE-14085 We already allow for the correlationID to be customised using a DW expression (in some connectors) but the default behaviour, if this is not configured, should be to propagate the flow correlationID. Note that to achieve traceability/supportability and functionally match Mule 3 in this regard MULE-13927 is also needed. A future improvement, if there is need for it, would be to not only allow the outbound correlationId to be customized, but to allow it's use to be disabled completely. See MULE-14086.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13932","11/01/2017 14:54:48",1,"Information of the event is not exposed on the BatchNotification ""For the debugger to work I need to know when a batch job is started and when it's finished. As the interception API does not provide this I added the notifications back to get this information. Right now the BatchNotification does not expose any data on the event that was the source of that job which I need (the correlation id specifically) in order to continue the execution for a particular event.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13935","11/01/2017 18:13:20",0,"In Message Filter, unacceptedMessageProcessor is not being notified ""Having the following configuration:   The logger inside the subflow is not being notified through the _MessageProcessorNotificationListener_ This causes that Studio cannot debug MPs inside the subflow and that munit cannot report coverage of the MPs inside the subflow."""," ",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13937","11/01/2017 20:34:25",2,"ConstructModel class is not consistent with ComponentModel in tooling api ""The Construct class (https://github.com/mulesoft/mule-tooling-api/blob/master/mule-runtime-tooling-api/src/main/java/org/mule/tooling/client/api/extension/model/construct/ConstructModel.java#L24) does not include errorModel related information and its getDisplayModel method is inconsistent with the rest of the componentModel implementations as it should return an Optional instead of the sole object.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0 +"MULE-13942","11/02/2017 17:07:45",1,"Race condition on Executors startup with SynchronousQueue ""When using a SynchronousQueue on an Executor, even if calling prestartAllCoreThreads(), a race condition may occur where the worker threads are started but before it starts to take elements from the queue, the user of the Executor dispatches some task to it.

In that case, the task will be rejected. To avoid this, a wait is forced until the core thread is actually taking tasks from the queue.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13947","11/02/2017 20:00:59",1,"Add search methods by name to ConfigurationModel and ExtensionModel DTO on Tooling API ""Create a way to find an OperationModel in a ConfigurationModel by name. ([link title|https://github.com/mulesoft/mule-api/blob/master/src/main/java/org/mule/runtime/api/meta/model/operation/HasOperationModels.java#L41]) Create a way to find a ConfigurationModel in an ExtensionModel by name. ([link title|https://github.com/mulesoft/mule-api/blob/master/src/main/java/org/mule/runtime/api/meta/model/ExtensionModel.java#L97])""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0 +"MULE-13949","11/03/2017 00:58:20",2,"Tooling MetadataCache should allow clients to know if metadata resolution has failed ""This will allow clients to avoid caching failure metadata results. Or if needed they could allow customers to invalidate the failure metadata.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0 +"MULE-13950","11/03/2017 12:47:25",1,"NullPointerException in performance tests that create a MuleContext ""When running the benchmark tests that create a MuleContext, a NullPointerException occurs in the ObjectStoreManager initialization""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13951","11/03/2017 13:58:25",1,"Tooling client bootstrap hangs because of missing org.slf4j.impl.StaticMDCBinder ""Tooling client bootstrap hangs at start because of missing MDC binder: Error: """," [INFO] Building tooling client for version 4.0.0-SNAPSHOT [INFO] SLF4J: Failed to load class """"org.slf4j.impl.StaticMDCBinder"""". [INFO] SLF4J: Defaulting to no-operation MDCAdapter implementation. [INFO] SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details. [INFO] Finished after 12 seconds [INFO] [WARNING] [INFO] java.lang.reflect.InvocationTargetException [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [INFO] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [INFO] at java.lang.reflect.Method.invoke(Method.java:498) [INFO] at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:294) [INFO] at java.lang.Thread.run(Thread.java:748) [INFO] Caused by: java.lang.NullPointerException [INFO] at org.apache.logging.slf4j.Log4jMDCAdapter.setContextMap(Log4jMDCAdapter.java:58) [INFO] at org.slf4j.MDC.setContextMap(MDC.java:264) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [INFO] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [INFO] at java.lang.reflect.Method.invoke(Method.java:498) [INFO] at org.mule.tooling.client.bootstrap.internal.reflection.Dispatcher$ToolingCallable.call(Dispatcher.java:208) [INFO] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [INFO] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [INFO] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [INFO] ... 1 more ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13953","11/03/2017 16:43:04",1,"Serialization error for MavenConfiguration on Tooling API ""An error ocurred while bootstraping Tooling: """," java.lang.IllegalStateException: Nesting problem. at com.google.gson.stream.JsonWriter.beforeValue(JsonWriter.java:656) at com.google.gson.stream.JsonWriter.open(JsonWriter.java:325) at com.google.gson.stream.JsonWriter.beginObject(JsonWriter.java:308) at org.mule.tooling.client.internal.serialization.MavenConfigurationTypeAdapter.write(MavenConfigurationTypeAdapter.java:42) at org.mule.tooling.client.internal.serialization.MavenConfigurationTypeAdapter.write(MavenConfigurationTypeAdapter.java:28) at com.google.gson.Gson.toJson(Gson.java:669) at com.google.gson.Gson.toJson(Gson.java:648) at com.google.gson.Gson.toJson(Gson.java:603) at com.google.gson.Gson.toJson(Gson.java:583) at org.mule.tooling.client.internal.serialization.SerializationUtils.serialize(SerializationUtils.java:93) at org.mule.tooling.client.bootstrap.internal.wrapper.BuilderWrapper.withMavenConfiguration(BuilderWrapper.java:60) at org.mule.tooling.client.bootstrap.internal.wrapper.ToolingRuntimeClientBuilderFactoryWrapper.create(ToolingRuntimeClientBuilderFactoryWrapper.java:78)",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0 +"MULE-13954","11/03/2017 16:49:58",2,"Tests using TransactedPollingMessageReceiver generate very big logs ""The receiver is continuously polling which fails because a transaction is not active. Tha exceptions is handled and logged. Since the polling is continuous, the logging generated is very big.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13956","11/03/2017 18:12:34",2,"Mule should not log OVERLOAD errors caused by flow back-pressure at ERROR level ""Mule should not log OVERLOAD errors at ERROR level to ensure that when mule is overloaded is performance is not degraded.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13965","11/03/2017 22:12:52",1,"HttpServerRule port range starts at 0 ""Fix HttpServerRule and FreePortFinder""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13966","11/03/2017 22:34:29",2,"Lookup function is propagating previous message mime type ""It should only handle java inputs but it's taking those values with the mime type of the previous message.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13971","11/06/2017 14:04:07",1,"Improve performance of cluster UUID generation ""Improve performance of cluster UUID generation""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13973","11/06/2017 14:57:18",1,"Improve header handling performance in ResponseCompletionHandler ""Avoid querying the headers map after iterating it, to avoid the performance cost of the case insensitiveness of headers.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13977","11/06/2017 19:05:39",1,"ClassDefNotFound when using MetadataCache ""When using MetadataCache the proxy tries to create an internal class and when using this on different contexts (isolated, such Eclipse/Studio) the implementation class has to be exported too. Instead Tooling API should already provide an implementation on API for this class. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0 +"MULE-13979","11/06/2017 20:14:24",2,"Find a workaround for not having to detect policy logger context in runtime ""After resolution of MULE-13918, an additional conditional for detecting if a classloader owner is a policy was added in ArtifactAwareContextSelector. This might reduce performance a bit since this is calculated at runtime. The idea is to find a way to cache this, to avoid that calculation""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13983","11/07/2017 16:59:29",0,"Metadata propagation for output variables on a batch job does not work. ""After defining custom metadata for the output variables on a batch job, those variables are not propagated through the flow.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0 +"MULE-13987","11/07/2017 19:54:50",8,"PoC on how make the SDK work with the AST ""Think about all the things are required to make the SDK work with AST and be able to support the SDK IDE. In a long-term this work should imply: # The AbstractAnnotationProcessor should work with either Java Classes and AST. # Improve Error Reporting ## Indicate which are the fields/classes/methods/annotations with issues ## Errors should be communicated as errors, warnings as warnings ## Work over SyntaxValidators and how current validators will work with the AST.  ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13994","11/08/2017 12:15:45",2,"Registry object is not accesible from DW script ""Try using registry from the a DW script (logger). It does not recognize the """"registry"""" keyword. It should be part of the binding context as in the scripting module""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13997","11/08/2017 12:30:07",8,"Use IO pool to execute blocking policies ""Currently all policies run on selector.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-13998","11/08/2017 12:32:14",2,"Optimize implementation of MULE-13756 for setting TCCL ""Current implementation using zipWith() has overload""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14005","11/08/2017 15:18:06",8,"Core extensions disposed before flows finish ""When running SchedulerClusterAppTestCase a message appears in the log showing that the Hazelcast core extension was disposed before the flow scheduler executed for the last time. This might happen in other cases too.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14009","11/08/2017 17:37:19",1,"Mule context not disposed if doTearDown method fails ""If an AbstractMuleContextTestCase overrides de doTearDown() method and it fails, the muleContext of the test is not disposed before bubbling the exception up""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14011","11/08/2017 23:09:31",1,"ClassCastException: org.mule.runtime.api.meta.model.display.DisplayModel cannot be cast to org.mule.metadata.api.annotation.TypeAnnotation ""When using DSLSyntaxResolver for MUnit Tools munit-tools-2.0.0-SNAPSHOT the following exception on Tooling serialization layer is thrown: """," java.lang.ClassCastException: org.mule.runtime.api.meta.model.display.DisplayModel cannot be cast to org.mule.metadata.api.annotation.TypeAnnotation at org.mule.tooling.client.internal.serialization.SerializationUtilsImpl$TypeAnnotationsMapConverter.marshal(SerializationUtilsImpl.java:300) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshallField(AbstractReflectionConverter.java:274) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$2.writeField(AbstractReflectionConverter.java:250) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$2.(AbstractReflectionConverter.java:213) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.doMarshal(AbstractReflectionConverter.java:144) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:90) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:66) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshallField(AbstractReflectionConverter.java:274) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$2.writeField(AbstractReflectionConverter.java:250) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$2.(AbstractReflectionConverter.java:213) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.doMarshal(AbstractReflectionConverter.java:144) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:90) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:66) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshallField(AbstractReflectionConverter.java:274) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$2.writeField(AbstractReflectionConverter.java:250) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$2.(AbstractReflectionConverter.java:213) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.doMarshal(AbstractReflectionConverter.java:144) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:90) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:66) at com.thoughtworks.xstream.converters.collections.MapConverter.marshal(MapConverter.java:79) at org.mule.tooling.client.internal.serialization.SerializationUtilsImpl$TypeAnnotationsMapConverter.marshal(SerializationUtilsImpl.java:320) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshallField(AbstractReflectionConverter.java:274) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$2.writeField(AbstractReflectionConverter.java:250) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$2.(AbstractReflectionConverter.java:213) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.doMarshal(AbstractReflectionConverter.java:144) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:90) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshallField(AbstractReflectionConverter.java:274) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$2.writeField(AbstractReflectionConverter.java:250) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$2.(AbstractReflectionConverter.java:213) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.doMarshal(AbstractReflectionConverter.java:144) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:90) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1319) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1308) at com.thoughtworks.xstream.XStream.toXML(XStream.java:1281) at com.thoughtworks.xstream.XStream.toXML(XStream.java:1268) at org.mule.tooling.client.internal.serialization.SerializationUtilsImpl.serialize(SerializationUtilsImpl.java:361) at org.mule.tooling.client.internal.dsl.ServiceDelegatingDslSyntaxResolver.invokeMethod(ServiceDelegatingDslSyntaxResolver.java:105)",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14015","11/09/2017 17:56:27",2,"Race condition on .mule directory creation using parallel deployment ""Under parallel deployment there's a race condition between checking for the existence of the .mule directory and its creation: with unfortunate timing an application may fail to deploy due to the IllegalStateException   a possible solution could be checking if the dir exists after the call to mkdirs() returns false, and only throw the exception if it does not exist"""," if (this.artifactTempFolder.exists()) { cleanNativeLibs(); } else { if (!this.artifactTempFolder.mkdirs()) { throw new IllegalStateException(String.format(""""Unable to create application '%s' folder"""", this.artifactTempFolder.getAbsolutePath())); } } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14022","11/10/2017 03:27:53",2,"Introduce the concept of Path location classification ""The PathModel needs to be enhanced so that parameters representing a file path can have more information regarding where those paths are going to point to. This will be helpful for tooling. A location attribute will be added to the PathModel. This attribute is an enum: * EMBEDDED: The path points to a resource inside the mule app. UI should render this as a file picker * EXTERNAL: The path points to a resource outside of the mule application. Most likely (but not necessarily) in the file system or an external URL. No file picker, just a regular text box * ANY: Resource can point to any of the above. A file picker can be offered, but the user needs to be able to also specify any random path""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14025","11/10/2017 15:12:53",5,"Can't get SP result with MSSQL ""Consider this case: It fails with: This is because MSSQL doesn't support multiple open ResultSets. This works with the 3.x connector because streaming is disabled by default. Now that streaming is always on, it always fails. We need to change it so that streaming is automatically disabled if the RDBMS doesn't support multiple open results. The driver's GAV is: """," { call proxies.api_address_s ('NewsItems') }  Error trying to load driver: com.microsoft.sqlserver.jdbc.SQLServerDriver : Cannot load class 'com.microsoft.sqlserver.jdbc.SQLServerDriver' i've seen some q's on this online but adding pom dependency hasn't fixed it. com.microsoft.sqlserver mssql-jdbc 6.3.4.jre8-preview pepes; org.mule.runtime.core.api.config.ConfigurationException: There was '1' error while parsing the given file 'test-extension-mule-app.xml'. Full list: org.xml.sax.SAXParseException; systemId: http://www.mulesoft.org/schema/mule/slack/current/mule-slack.xsd; lineNumber: 176; columnNumber: 71; src-resolve: Cannot resolve the name 'mule:mapType' to a(n) 'simpleType definition' component. Caused by: org.mule.runtime.api.exception.MuleRuntimeException: There was '1' error while parsing the given file 'test-extension-mule-app.xml'. Full list: org.xml.sax.SAXParseException; systemId: http://www.mulesoft.org/schema/mule/slack/current/mule-slack.xsd; lineNumber: 176; columnNumber: 71; src-resolve: Cannot resolve the name 'mule:mapType' to a(n) 'simpleType definition' component.",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14095","11/16/2017 16:49:42",5,"Soap Connect default transport should not be bounded in mule soap support ""Soap Connect default transport should not be bounded in mule soap support""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14097","11/16/2017 18:58:32",2,"PagingProviders are closed two times ""*PagingProviders are closed two times* For some reason when a paging provider is closed by the SDK, it gets closed twice, this may lead to unexpected behaviours if the connector developer expects that the close will be called once.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14104","11/17/2017 16:26:06",1,"Adapt test cases considering DW error message trunking ""Need to fix test cases that were matching with equals since now error messages will be truncated to avoid large blobs.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14107","11/17/2017 19:32:31",8,"Spec for aggregators and resequencer ""Specification for aggregators and resequencer routers in Mule 4""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14108","11/17/2017 21:02:04",2,"If a temporary application resource couldn't be deleted a warning message should be displayed ""Whenever a temporary resource from an application from {{.mule}} folder Mule is throwing an error instead of just log a warning message that says that the resource couldn't be deleted and may generate an OOM. This is reproducible on Windows environments as Linux/MacOS allow to delete a file no matter if a process is still using it.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14110","11/17/2017 21:55:11",5,"Add support for chainless routes in extension model ""Chain are mandatory in routes right now, therefore you cannot have reference routes as in the """"on-error"""" component.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14111","11/17/2017 21:58:07",3,"Add support to indicate whether an error is handleable or not in extension model ""Today, all errors are equals as to their role in Mule. However, some errors cannot be handled by users, such as UNKNOWN and CRITICAL. Since these are no different in the extension model tooling services cannot tell which could be suggested in handlers and which should be hidden.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14112","11/18/2017 03:32:53",1,"Iterators are not converted into repeatable iterators when using StreamingUtils ""*Iterators are not converted into repeatable iterators when using StreamingUtils* * When using StreamingUtils to find all the streams and iterators to convert them into repeatable ones, doesn't take into account {{Iterators}}, just {{StreamingIterators}}, which is wrong. * See: [https://github.com/mulesoft/mule/blob/mule-4.x/modules/extensions-support/src/main/java/org/mule/runtime/module/extension/internal/runtime/streaming/DefaultStreamingHelper.java#L87] ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14113","11/20/2017 12:57:50",8,"Rework MessageProcessorChain to use error mode instead of concatMap for error handling. ""Rework MessageProcessorChain to use error mode instead of concatMap for error handling. See SPIKE: MULE-14080 Depends on: https://github.com/reactor/reactor-core/issues/629""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14119","11/21/2017 21:52:45",1,"Fix Mule-Extensions-Maven-Plugin tests ""Mule-Extensions-Maven-Plugin tests fail almost consistently.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14122","11/22/2017 14:04:22",3,"Pointing to modules parent 1.1.0-SNAPSHOT still generates minMuleVersion 4.0.0 ""Creating an extension with the parent pom pointing to mule-core-modules-parent version 1.0.0-SNAPSHOT, generates a mule-artifact.json in the target which has a minMuleVersion 4.0.0. This should be 4.1.0.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14124","11/22/2017 19:00:55",2,"Operation field parameters don't work if used with a ParameterGroup ""The work done in MULE-13902 did not consider the case of ParameterGroups""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14125","11/22/2017 19:35:15",1,"Fix integrations CompositeSourceStartDelayTestCase ""The test is verifying a functionality that at best will remain in compatibility and at worst will never work in Mule 4, it's flaky so we'll delete it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14129","11/24/2017 15:01:07",0,"ArtifactClassLoaderRunner - Use semantic versioning for resolving plugins ""Current logic for test runner when classifying the plugins is not honoring semantic logic and not taking into account transitive versions of plugins as it goes over each plugin and reads the direct dependencies. There are issues with this as if we use Mule Maven Client logic that honors the algorithm for resolving plugins will leave out the cases when plugins have scope tests.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14134","11/27/2017 13:58:49",8,"For TopLevelObjectStore, DSLSyntax information doesn't match the TypeDslAnnotation information ""For the Object Store module, there are 2 types that define a private object store and a top level object store. The private object store supports inline definition, while the top level object store doesn't. But the information retrieved after resolving the DslSyntax element states that the top level object store supports it. This information should match or the UI generated by Studio and Mozart will allow the users to write invalid XML apps""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14137","11/27/2017 15:38:27",5,"Implement Partial fetching in Multilevel DataSense ""Enable partial fetching, with free levels included""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14141","11/28/2017 14:46:09",0,"Support ConnectivityTesting on Domains ""Add support to do connectivity testing on domain artifacts.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14145","11/29/2017 00:07:51",1,"TopLevel parameters not parsed when used as reference ""If an extension defines a top level object, which is also used in an operation as reference only, then the parser for that top level object is never generated.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14151","12/01/2017 13:59:28",0,"AbstractExecutableComponent doesn't complete/terminate created Eventcontexts ""When using AbstractExecutableComponent#execute methods, the created eventContexts are never terminated, causing any termination callbacks to not be executed. This manifests as a problem when declaring generic termination callbacks to do clean up tasks, such as first intended to implement MULE-13700 (see TODOs referencing this issue) or the repeatable streams cleanup.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14155","12/04/2017 13:12:44",8,"Flowstack on policies ""When executing a component in a policy chain, the flowstack at that point must reflect that, indication on which part of the policy (source or operation, before or after) it is located.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14164","12/04/2017 21:39:56",5,"Provide a FlowExecutor for SDK Modules ""Provide a FlowExecutor for SDK Modules: https://docs.google.com/document/d/1rTFJCh9yodcLnj9z6E0IqlpzPt17_RJraDUfYhhuXi8/edit#heading=h.5qzxde9sr307""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14171","12/05/2017 18:36:10",3,"SDK loses the Map DataType generics ""*SDK loses the Map DataType generics* * When returning Maps in an operation, the SDK doesn't consider the generics when generating the output datatype.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14173","12/05/2017 19:54:41",2,"Add a splash information about the thread configurations calculated by Mule 4 ""In Mule 4, the io scheduler max size will be calculated based on the hardware available. because of this, it is important to display this information so the customer can tell which configuration was picked up by the runtime.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14176","12/06/2017 19:45:15",2,"When melDefault property is set to true, dw: prefix in expressions is ignored ""In the described case, the expression is evaluated with MEL instead of DW as one would expect.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14183","12/07/2017 15:25:03",8,"Remove patching scenarios ""With the inclusion of deployment of patched artifacts on mule 4.0.0, some inconsistencies were introduced in the way artifacts are identified and how deployment notifications are sent. Artifacts are identified by the file/folder name, so when a patch for app1.0.0 is deployed, it will be installed in app-1.0.1 and the identifier for the patched app will be app-1.0.1. When the patch is deployed, the old one must be undeployed, so this must send undeployment notifications. These notifications will use the app-1.0.0 ID. This makes hard to correlate all the notifications send on this deployment. (and in particular, it makes hard to implement MULE-14118 in a consistent way). The deployment must manage the patching scenarios (on both the folder and artifact ID) in a similar way to the used to manage the artifact data folder (see DeployableArtifactDescriptor#getDataFolderName), that consist of removing the bug fix version  from the folder/ID.  Additionally, as the full version is not part of the ID, it could make sense to include a new field on the deployment notifications to provide this value""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14184","12/07/2017 16:15:05",8,"Support notifications in the SDK ""As part of MULE-13774, a spec and POC was done to support the firing of notifications in the SDK. This task is to take that POC and fully implement the feature, including the HTTP part.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14188","12/07/2017 19:38:50",5,"Character parameters are not supported ""*Character parameters are not supported* The SDK doesn't consider the possibility of having Character parameters and it fails when executing the operation. *Operation*: *Runtime:* *Tooling*: """," /** * Optional data element separator character. The configured value is used by Optional for all output messages, but * can be overridden at the message level. */ @Parameter @Optional(defaultValue = """"|"""") @Placement(tab = Tabs.DOCUMENT, order = 2) @DisplayName(""""Field separator character"""") private Character fieldSeparator;Root Exception stack trace: java.lang.IllegalArgumentException: argument type mismatch at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:203) at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.lambda$execute$0(ReflectiveMethodComponentExecutor.java:76) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:215) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:813) at org.mule.runtime.module.extension.internal.runtime.execution.ReflectiveMethodComponentExecutor.execute(ReflectiveMethodComponentExecutor.java:75) at org.mule.runtime.module.extension.internal.runtime.operation.ReflectiveMethodOperationExecutor.execute(ReflectiveMethodOperationExecutor.java:64) at org.mule.runtime.module.extension.internal.runtime.execution.InterceptableOperationExecutorWrapper.execute(InterceptableOperationExecutorWrapper.java:60) at org.mule.runtime.module.extension.internal.runtime.operation.DefaultExecutionMediator.lambda$null$3(DefaultExecutionMediator.java:142) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:215) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:813) at org.mule.runtime.module.extension.internal.runtime.operation.DefaultExecutionMediator.lambda$executeWithInterceptors$9(DefaultExecutionMediator.java:142) at reactor.core.* (9 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (2 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (2 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (41 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (47 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.tck.SimpleUnitTestSupportLifecycleSchedulerDecorator.lambda$wrap$7(SimpleUnitTestSupportLifecycleSchedulerDecorator.java:156) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) Failed to resolve dynamic model. component: COMPONENT, element: , code: UNKNOWN - Reason: org.mule.runtime.api.exception.MuleRuntimeException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'HL7_Extension_Config': FactoryBean threw exception on object creation; nested exception is java.lang.RuntimeException: java.lang.IllegalArgumentException: Can not set java.lang.Character field com.mulesoft.connectors.hl7.extension.internal.param.DocumentParams.fieldSeparator to java.lang.String Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'HL7_Extension_Config': FactoryBean threw exception on object creation; nested exception is java.lang.RuntimeException: java.lang.IllegalArgumentException: Can not set java.lang.Character field com.mulesoft.connectors.hl7.extension.internal.param.DocumentParams.fieldSeparator to java.lang.String",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14189","12/10/2017 22:15:01",1,"Add the capability of attaching multiple icons in an extension ""*Add the capability of attaching multiple icons in an extension* Nowadays the extension developer can only attach one icon for the extension, modify the mule extension maven plugin to be able to attach multiple icons.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14192","12/11/2017 17:28:29",8,"Spec for aggregators ""Specification for aggregators module in Mule 4""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0 +"MULE-14195","12/12/2017 14:27:44",3,"Don't let the user define Result without Generics as Operation return type ""*Don't let the user define Result without Generics as Operation return type* * Force to the user define the generics of *Result* if this is used as the return type of an operation, so the developer is forced to think which is the return payload and attributes types.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14196","12/12/2017 15:19:47",13,"Create AST Type Loader ""Create AST Type Loader""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14197","12/12/2017 15:22:36",8,"Adapt Problems Reporter to work with the AST. ""Adapt Problems Reporter to work with the AST.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14201","12/12/2017 22:48:04",1,"Document ExecutableComponent's errors ""There's currently nothing indicating that a specific exception is generated.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14202","12/13/2017 13:45:02",3,"Tooling services doesn't work if operation contains a List as parameter with reference support ""*Tooling services (AKA: DataSense & ValueProviders) doesn't work if operation contains a List as parameter with reference support and is not filled.* In this case there is an Operation with a *List* as parameter which accepts expressions as references and is not completed because is not a parameter that participates of the DataSense resolution, but the mule app fails to start because is not filled. ""","Failed to resolve dynamic model. component: COMPONENT, element: , code: UNKNOWN - Reason: org.mule.runtime.api.exception.MuleRuntimeException: java.lang.IllegalArgumentException: key cannot be null or blank Caused by: java.lang.IllegalArgumentException: key cannot be null or blank at org.mule.runtime.api.util.Preconditions.checkArgument(Preconditions.java:25) at org.mule.runtime.module.extension.internal.runtime.resolver.RegistryLookupValueResolver.(RegistryLookupValueResolver.java:41) at org.mule.runtime.module.extension.internal.config.dsl.object.DefaultValueResolverParsingDelegate.parse(DefaultValueResolverParsingDelegate.java:40) at org.mule.runtime.module.extension.internal.config.dsl.object.DefaultValueResolverParsingDelegate.parse(DefaultValueResolverParsingDelegate.java:21) at org.mule.runtime.module.extension.internal.config.dsl.ExtensionDefinitionParser$6.lambda$defaultVisit$1(ExtensionDefinitionParser.java:823) at java.util.Optional.orElseGet(Optional.java:267) at org.mule.runtime.module.extension.internal.config.dsl.ExtensionDefinitionParser$6.defaultVisit(ExtensionDefinitionParser.java:822) at org.mule.metadata.api.visitor.MetadataTypeVisitor.visitArrayType(MetadataTypeVisitor.java:64) at org.mule.metadata.api.model.impl.DefaultArrayType.accept(DefaultArrayType.java:38) at org.mule.runtime.module.extension.internal.config.dsl.ExtensionDefinitionParser.getValueResolverFromMetadataType(ExtensionDefinitionParser.java:775) at org.mule.runtime.module.extension.internal.config.dsl.ExtensionDefinitionParser.getStaticValueResolver(ExtensionDefinitionParser.java:756) at org.mule.runtime.module.extension.internal.config.dsl.ExtensionDefinitionParser.resolverOf(ExtensionDefinitionParser.java:693) at org.mule.runtime.module.extension.internal.config.dsl.ExtensionDefinitionParser.lambda$parseAttributeParameter$6(ExtensionDefinitionParser.java:894) at org.mule.runtime.config.internal.dsl.spring.ComponentConfigurationBuilder$ValueExtractorAttributeDefinitionVisitor.onConfigurationParameter(ComponentConfigurationBuilder.java:286) at org.mule.runtime.dsl.api.component.AttributeDefinition.accept(AttributeDefinition.java:52) at org.mule.runtime.config.internal.dsl.spring.ComponentConfigurationBuilder$ConfigurableAttributeDefinitionVisitor.onMultipleValues(ComponentConfigurationBuilder.java:234) at org.mule.runtime.dsl.api.component.AttributeDefinition.accept(AttributeDefinition.java:74) at org.mule.runtime.config.internal.dsl.spring.ComponentConfigurationBuilder.processConfiguration(ComponentConfigurationBuilder.java:70) at org.mule.runtime.config.internal.dsl.spring.CommonBeanDefinitionCreator.processObjectConstructionParameters(CommonBeanDefinitionCreator.java:302) at org.mule.runtime.config.internal.dsl.spring.CommonBeanDefinitionCreator.processComponentDefinitionModel(CommonBeanDefinitionCreator.java:251) at org.mule.runtime.config.internal.dsl.spring.CommonBeanDefinitionCreator.handleRequest(CommonBeanDefinitionCreator.java:111) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:41) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:45) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:45) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:45) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:45) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:45) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:45) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:45) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:45) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionCreator.processRequest(BeanDefinitionCreator.java:45) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionFactory.resolveComponentBeanDefinition(BeanDefinitionFactory.java:316) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionFactory.resolveComponent(BeanDefinitionFactory.java:189) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionFactory.resolveComponentRecursively(BeanDefinitionFactory.java:172) at org.mule.runtime.config.internal.dsl.spring.BeanDefinitionFactory.resolveComponentRecursively(BeanDefinitionFactory.java:168) at org.mule.runtime.config.internal.MuleArtifactContext.lambda$createApplicationComponents$16(MuleArtifactContext.java:492) at org.mule.runtime.config.internal.model.ApplicationModel.executeOnComponentTree(ApplicationModel.java:862) at org.mule.runtime.config.internal.model.ApplicationModel.lambda$executeOnComponentTree$34(ApplicationModel.java:864) at java.util.ArrayList.forEach(ArrayList.java:1249) at org.mule.runtime.config.internal.model.ApplicationModel.executeOnComponentTree(ApplicationModel.java:863) at org.mule.runtime.config.internal.model.ApplicationModel.executeOnEveryMuleComponentTree(ApplicationModel.java:839) at org.mule.runtime.config.internal.MuleArtifactContext.createApplicationComponents(MuleArtifactContext.java:476) at org.mule.runtime.config.internal.LazyMuleArtifactContext.lambda$createComponents$8(LazyMuleArtifactContext.java:191) at org.mule.runtime.core.api.util.ClassUtils.lambda$withContextClassLoader$10(ClassUtils.java:794) at org.mule.runtime.core.api.util.ExceptionUtils.tryExpecting(ExceptionUtils.java:215) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:847) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:813) at org.mule.runtime.core.api.util.ClassUtils.withContextClassLoader(ClassUtils.java:793) at org.mule.runtime.config.internal.LazyMuleArtifactContext.createComponents(LazyMuleArtifactContext.java:176) at org.mule.runtime.config.internal.LazyMuleArtifactContext.initializeComponent(LazyMuleArtifactContext.java:153) at org.mule.runtime.config.internal.LazyMetadataService.initializeComponent(LazyMetadataService.java:128) at org.mule.runtime.config.internal.LazyMetadataService.getOperationMetadata(LazyMetadataService.java:68) at com.mulesoft.agent.services.metadata.MuleAgentMetadataService.lambda$getOperationMetadata$1(MuleAgentMetadataService.java:65) at com.mulesoft.agent.services.metadata.MuleAgentMetadataService.withMetadataService(MuleAgentMetadataService.java:126) at com.mulesoft.agent.services.metadata.MuleAgentMetadataService.getOperationMetadata(MuleAgentMetadataService.java:65) at com.mulesoft.agent.external.handlers.metadata.MetadataRequestHandler.lambda$getOperationMetadata$2(MetadataRequestHandler.java:162) at com.mulesoft.agent.util.ResponseHelper.response(ResponseHelper.java:88) at com.mulesoft.agent.external.handlers.metadata.MetadataRequestHandler.getOperationMetadata(MetadataRequestHandler.java:160) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171) at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:152) at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104) at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:387) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:331) at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:103) at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) at org.glassfish.jersey.internal.Errors.process(Errors.java:315) at org.glassfish.jersey.internal.Errors.process(Errors.java:297) at org.glassfish.jersey.internal.Errors.process(Errors.java:267) at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:297) at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:254) at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1028) at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:372) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:381) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:344) at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:221) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1515) at com.mulesoft.agent.rest.RequestLoggingFilter.doFilter(RequestLoggingFilter.java:95) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1486) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:519) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:138) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:564) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:213) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1097) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:448) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:175) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1031) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:446) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:271) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:246) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:532) at java.lang.Thread.run(Thread.java:748) .",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14203","12/13/2017 14:53:36",2,"Make IO thread pool have an optimal core size ""As a workaround for MULE-14179 the core size of the IO pool was reduced to 0. Based on the performance impact (recreation/disposal of threads), determine an appropriate number of threads to use for core pool size. Bear in mind that some custom implementation of the ThreadPoolExecitor/BlockingQueue will have to be done, in order to avoid reintrouducing MULE-14179 or MULE-13942""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14204","12/13/2017 15:23:00",2,"Error count of flow statistics not tracked ""The flow error count is not being tracked. The following methos always return 0: This is because the attribute statistics of _AbstractExceptionListener_ is always null when the application doesn't have an exception strategy."""," FlowConstructStatistics#getExecutionErrors() FlowConstructStatistics#getFatalErrors() ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14213","12/13/2017 19:46:07",8,"Upgrade Mockito in CE, API, Extensions API ""Upgrade Mockito to the latest version that doesn't break backwards compatibility""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14260","12/14/2017 17:34:15",8,"Add the ability to specify the data folder location for an application ""In Mule 3 it was possible to deploy an updated version of an application using the exact folder/zip name of a previous one in order to reuse the temp data folder. In Mule 4 since the data folder gets created based on the GAV of the artifact (without consider patch version) then it's no possible to do this unless the updated application GAV is the same one as the previous app or only differs on the patch version which it would be just a hack to make it work. We need to properly define a mechanism so an updated version of an application that changes the major or minor version, can reuse the same data folder.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14267","12/15/2017 19:35:41",0,"Parser sets rootContainerName for non Component children of prototype objects ""A definition provider may define an element to be parsed to, for instance, a Collection type. In that case, setting the root container will cause an error when spring tries to set the annotations attribute to the created collection.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14272","12/15/2017 22:45:30",1,"[Model] Allow operations to not have a target ""The extension declarer automatically adds everything related to the target feature. However, some operations may not require that, as is the case of the transform processor which defines it's own targets. It should be possible to indicate that somehow so that the extension model does not feature those unsupported attributes.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14276","12/18/2017 15:15:03",2,"Move modules/dsl-api to a separated repository ""Module is using 1.0.0 version instead of 4.0.0/4.1.0 as in the rest of the mule repository. Need to extract this code to a separate repository, create a build plan and update the uber project""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14277","12/18/2017 15:16:01",2,"Move modules/http-policy-api to a separated repository ""Module is using 1.0.0 version instead of 4.0.0/4.1.0 as in the rest of the mule repository. Need to extract this code to a separate repository, create a build plan and update the uber project""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14278","12/18/2017 15:16:48",2,"Move modules/policy-api to a separated repository ""Module is using 1.0.0 version instead of 4.0.0/4.1.0 as in the rest of the mule repository. Need to extract this code to a separate repository, create a build plan and update the uber project  ""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14279","12/18/2017 15:26:02",1,"API broken by MULE-14171 ""API was broken while fixing MULE-14171. The original issue must be fixed without changing the API""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14280","12/18/2017 15:28:38",2,"API broken by MULE-14082 ""API was broken while fixing +MULE-14082+. The original issue must be fixed without changing the API""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14281","12/18/2017 15:32:43",2,"API broken by MULE-10912 ""API was broken while fixing MULE-10912. The original issue must be fixed without changing the API""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14288","12/19/2017 19:58:23",8,"SDK sources need to be cluster aware ""to be filled""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14294","12/20/2017 15:12:11",2,"NPE when setting a payload, using on-error-continue in an operation policy ""The following NPE appears when using a set-payload inside of an on-error-continue in an operation policy. This behaviour does not happen when using on-error-propagate. A way to reproduce this issues, is by using this policy: NPE: """," ERROR 2017-12-19 21:49:03,511 [[MuleRuntime].io.02: [app-1.0.0-mule-application].set-payload.BLOCKING @54780c40] org.mule.runtime.core.internal.exception.OnErrorPropagateHandler: ******************************************************************************** Message : The mapper returned a null value. Element : set-payload/processors/1 @ app-1.0.0-mule-application:mule-config.xml:32 Element XML : Error type : MULE:UNKNOWN -------------------------------------------------------------------------------- Root Exception stack trace: java.lang.NullPointerException: The mapper returned a null value. at java.util.Objects.requireNonNull(Objects.java:228) at reactor.core.* (14 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (2 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (7 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.internal.event.AbstractEventContext.signalPublisherSink(AbstractEventContext.java:289) at org.mule.runtime.core.internal.event.AbstractEventContext.lambda$getResponsePublisher$10(AbstractEventContext.java:272) at reactor.core.* (12 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (7 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (2 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (12 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (12 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (6 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (48 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (12 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (12 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (6 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (77 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (2 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (18 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (53 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (2 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (12 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (2 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (1 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (2 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (6 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at org.mule.runtime.core.privileged.processor.chain.* (2 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at reactor.core.* (10 elements filtered from stack; set debug level logging or '-Dmule.verbose.exceptions=true' for everything)(Unknown Source) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.mule.service.scheduler.internal.AbstractRunnableFutureDecorator.doRun(AbstractRunnableFutureDecorator.java:95) at org.mule.service.scheduler.internal.RunnableFutureDecorator.run(RunnableFutureDecorator.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ******************************************************************************** ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14296","12/20/2017 15:39:33",2,"Double exception received to error handler when there is an Internal Server Error ""Steps to reproduce: -deploy: - a proxy - an operation policy to handle the request of the proxy - a server that throws an exception when it is called. After hitting the proxy, the request is performed to the server. The operation policy detects an Internal Server Error because of the exception in the server, but after that, a second (Unknown) error is thrown. As the second exception happens when running the error handling of the policy, all the error handling fails. """," ERROR 2017-12-20 12:28:59,931 [[app-1.0.0-mule-application].http.requester.http-request-config.01 SelectorRunner] org.mule.runtime.core.internal.exception.OnErrorPropagateHandler: ******************************************************************************** Message : HTTP POST on resource 'http://localhost:27095/server-error-in-response' failed: internal server error (500). Error type : HTTP:INTERNAL_SERVER_ERROR Element : error-in-server/processors/1 @ OperationNoException-1-error-in-server:mule-config.xml:45 Element XML : (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** ERROR 2017-12-20 12:28:59,933 [[app-1.0.0-mule-application].http.requester.http-request-config.01 SelectorRunner] org.slf4j.LoggerFactory: HTTP POST on resource 'http://localhost:27095/server-error-in-response' failed: internal server error (500). org.mule.runtime.core.internal.policy.FlowExecutionException: HTTP POST on resource 'http://localhost:27095/server-error-in-response' failed: internal server error (500). Caused by: org.mule.extension.http.api.request.validator.ResponseValidatorTypedException: HTTP POST on resource 'http://localhost:27095/server-error-in-response' failed: internal server error (500). Caused by: org.mule.runtime.api.exception.MuleRuntimeException: HTTP POST on resource 'http://localhost:27095/server-error-in-response' failed: internal server error (500). DEBUG 2017-12-20 12:28:59,935 [[app-1.0.0-mule-application].http.requester.http-request-config.01 SelectorRunner] org.mule.runtime.core.internal.event.AbstractEventContext: ChildEventContext { id: 0-7e2d45f0-e59a-11e7-bb2e-aa0f76692fec1585670020; correlationId: 0-7e2d45f0-e59a-11e7-bb2e-aa0f76692fec; flowName: error-in-server; componentLocation: no-exception-thrown/source/processors/0; responseDone completed with error. DEBUG 2017-12-20 12:28:59,935 [[app-1.0.0-mule-application].http.requester.http-request-config.01 SelectorRunner] org.mule.runtime.core.internal.event.AbstractEventContext: ChildEventContext { id: 0-7e2d45f0-e59a-11e7-bb2e-aa0f76692fec1585670020; correlationId: 0-7e2d45f0-e59a-11e7-bb2e-aa0f76692fec; flowName: error-in-server; componentLocation: no-exception-thrown/source/processors/0; handling messaging exception. ERROR 2017-12-20 12:28:59,936 [[app-1.0.0-mule-application].http.requester.http-request-config.01 SelectorRunner] org.mule.runtime.core.internal.exception.OnErrorContinueHandler: ******************************************************************************** Message : HTTP POST on resource 'http://localhost:27095/server-error-in-response' failed: internal server error (500). Element : error-in-server/processors/1 @ OperationNoException-1-error-in-server:mule-config.xml:45 Element XML : Error type : MULE:UNKNOWN -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.runtime.api.exception.MuleRuntimeException: HTTP POST on resource 'http://localhost:27095/server-error-in-response' failed: internal server error (500). ******************************************************************************** ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14299","12/20/2017 17:33:24",2,"Update reactor to 3.20-M1 with error handling support ""This depends if 3.1.3 release includes error handling support or not.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14300","12/20/2017 17:35:47",2,"NullPointerException running API compatibility check maven plugin ""After the inclusion of the Revapi plugin to ensure API compatiblity, when the Mule uber project is being built, a NullPinterException is being thrown. Apparently the error is related to the usage of the uber profile: """," mvn clean install -DskipTests -Puber mvn clean install -DskipTests -T6 -Puber -fae",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14301","12/20/2017 18:05:04",1,"Scope/Routes error callback called twice ""The callback error method in SDK scopes and routers is called twice because of the following code in org.mule.runtime.module.extension.internal.runtime.operation.ImmutableProcessorChainExecutor.Executor#execute: The result of the first doOnError will be an error so I think that's why the next doOnError evaluates as well."""," public void execute() { from(processWithChildContext(event, chain, ofNullable(chain.getLocation()))) .doOnSuccess(this::handleSuccess) .doOnError(MessagingException.class, error -> this.handleError(error, error.getEvent())) .doOnError(error -> this.handleError(error, event)) .subscribe(); } ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14302","12/21/2017 18:10:30",5,"SDK implemented functions fail to receive TypedValue wrapped elements. ""When a weave function is implemented with the SDK and receives a  TypedValue as parameter, either directly or in the generic of a collection, it fails with a ClassCastExeception saying, for example, that Integer cannot be cast to TypedValue.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14305","12/22/2017 12:39:26",0,"Source errors do not contain app location info when logged ""When the error described in MULE-14168 occures, the element path and element XML of the source where the error occurs is not logged""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14310","12/22/2017 20:17:28",2,"Empty configuration name causes extension to fail ""If the name attribute is not specified in a configuration annotation, building of the extension fails: The error is not clear also: """," @Configuration public class PgpConfiguration { } [ERROR] diagnostic: error: org.mule.runtime.api.exception.MuleRuntimeException: java.lang.IllegalArgumentException: An stereotype name is required org.mule.runtime.api.exception.MuleRuntimeException: org.mule.runtime.api.exception.MuleRuntimeException: java.lang.IllegalArgumentException: An stereotype name is required Caused by: org.mule.runtime.api.exception.MuleRuntimeException: java.lang.IllegalArgumentException: An stereotype name is required Caused by: java.lang.IllegalArgumentException: An stereotype name is required at org.mule.runtime.api.util.Preconditions.checkArgument(Preconditions.java:25) at org.mule.runtime.api.meta.model.stereotype.ImmutableStereotypeModel.(ImmutableStereotypeModel.java:31) at org.mule.runtime.api.meta.model.stereotype.StereotypeModelBuilder.build(StereotypeModelBuilder.java:51) at org.mule.runtime.module.extension.internal.loader.enricher.stereotypes.StereotypesDeclarationEnricher$EnricherDelegate$1.onConfiguration(StereotypesDeclarationEnricher.java:98) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14311","12/24/2017 14:42:38",8,"Make ExtensionResourcesGeneratorAnnotationProcessor work in compile time ""Now the ExtensionResourcesGeneratorAnnotationProcessor works in the package phase, this let the annotation processor work with classes. The annotation processor should stop working with the classes and definitely work with the AST.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14312","12/26/2017 01:05:33",5,"Add the capability of mark components as deprecated ""*Add the capability of mark operations as deprecated* Sometimes an operation or source can be deprecated because you need to implement something new, but you don't want to break backwards compatibility and also you don't want new users to keep using the operation, so the solution is to mark the operation/source/router/etc as deprecated. A deprecated component should mean: * The user is discouraged from using the component. * The IDE may hide it from the UI Palette * Communicate by all possible ways that the user must not use that component. * Also can it be deprecated parameters or connections""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14313","12/26/2017 14:49:39",13,"Replace class references with the Type abstraction in the extension java loader ""Replace class references with the Type abstraction in the extension java loader""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14315","12/26/2017 16:55:07",3,"Move AST Loader to another module ""Move AST Loader to another package ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14317","12/26/2017 17:56:51",1,"Update required java and maven versions in .md files ""Many aspects of the .md files are outdated""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14320","12/27/2017 15:28:24",2,"MessageProcessor post-invoke notification missing when an error occurs ""When an error happens on transform Mule Runtime is missing a post-invoke notification.""","",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14321","12/27/2017 16:02:30",1,"API broken by MULE-14288 ""API was broken while working MULE-14288. The original issue must be completed without changing the API ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14322","12/27/2017 16:05:21",0,"API broken by MULE-14124 ""API was broken while working MULE-14124. The original issue must be completed without changing the API ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14323","12/27/2017 16:07:21",1,"API broken by MULE-14048 ""API was broken while working MULE-14048. The original issue must be completed without changing the API ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14324","12/27/2017 16:09:22",1,"API broken by MULE-13927 ""API was broken while working MULE-13927. The original issue must be completed without changing the API ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14326","12/27/2017 18:52:07",3,"Improve notifications serialization ""Just like errors, notifications could be optimise to only declare them once at the extension level and then referencing them in operation and sources.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14328","12/27/2017 19:24:17",8,"Invalid API defined on mule-metadata-model because of missing mule-module-maven-plugin ""Some modules defined on mule-metadata-model define a mule-module.properties, but the APIs declared on those modules is not being validated, as the mule-module-maven-plugin is not declared on corresponding pom.xml file. A first attempt to include the mentioned plugin (along with the revapi maven plugin to check API consistency across versions) shown that the modules are incorrectly defined, ie, the list of exported modules is not complete or it exports unwanted packages. So, API must be cleaned up, but need to check first if those APIs are really needed.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14334","12/28/2017 15:45:10",2,"Move MessageProcessors from privileged package to an accessible one ""Move MessageProcessors.flatMap to a package accessible by APIKit""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14335","12/28/2017 17:01:30",5,"ObjectStore connector does not work properly with lazy init ""In the following configuration The os operation contains fails when running with lazy init due to the objectStore attribute not being recognised as a reference attribute to a bean"""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0 +"MULE-14337","12/28/2017 18:48:28",2,"Only support back-preasure configuration in HTTP ""Until we clearly define an implementation for each of the back preasure strategies, we should only support WAIT as an option in all sources. Having a default implementation for other strategies make no sense since each of them require proper treatment and if we don't do that then we would be breaking backwards compatibility in the future""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14342","12/28/2017 20:20:03",1,"API broken by MULE-13774 ""The introduction of notifications in the SDK cause several API problems. Though most seem like candidates to ignore, we need to review them carefully.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14343","12/28/2017 22:23:15",8,"Create an Extension Object Field handler for the AST Type Loader ""Create an Extension Object Field handler for the AST Type Loader""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14346","12/29/2017 16:44:24",0,"Support lazyInit for Domains ""LazyInit is only support for applications with default domain only or domains, this ticket is about supporting lazyInit for an application that depends on domains that are not empty (case of default one).""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14350","12/30/2017 03:11:42",1,"Make BackPressureContext differentiate between DROP and FAIL back pressure ""Leverage MULE-14284 to allow BPContext to differentiate between FAIL and DROP (currently it always says DROP)""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14353","01/02/2018 14:37:19",1,"NPE when creating an ImmutableOperationModel without notifications ""Changes added to ExtensionModel implementation classes are not backward compatible so whenever a new instance of the ImmutableOperationModel is created within an old model (that doesn't have notifications) an NPE is thrown.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14358","01/02/2018 20:27:17",1,"APIKit needs access to MessageProcessors class ""APIKit needs access to MessageProcessors but this class is located in a privileged mule package. Allow APIKIT access to org.mule.runtime.core.privileged.processor package""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14361","01/03/2018 20:42:30",2,"For each executes first processor even that an execution failed ""While doing a test on Tooling client, with a configuration like: Even though that in the first iteration the http request fails, we received notifications from the logger as it's being executed the more than once. Putting a breakpoint on the LoggerMessageProcessor shows that the logger is being executed the whole 3 times, instead of only once. """," ",1,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14373","01/04/2018 16:06:45",2,"Define annotations to exclude java elements from the API ""We need a way to mark which parts of what is exposed on the API is NOT considered API. This could sound counterintuitive, but consider this examples: • Interfaces that are not supposed to be implemented by clients, they are only provided in the API for consumption only • Classes that are not supposed to be extended by clients, they are provided in the API as a generic type for consumption only • Classes that are not supposed to be instantiated by clients, they are provided in the API as a generic type for consumption only • Methods that are not supposed to be overridden by clients, they are provided for internal usage only • Types that not supposed to be directly referenced by clients""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14374","01/04/2018 16:08:48",8,"Update mave-revapi-extension to support mule-api-annotations ""Add support to mule-revapi-extension to ignore API differences based on the annotations defined on mule-api-annotations""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14375","01/04/2018 16:09:04",2,"FunctionalTestCase#getConfigFile should always support / slash ""Right now, the getConfigFile() method in the FunctionalTestCase class, must be used with the slash corresponding to the OS (/ for UNIX and \ for Windows). But this means that a forward slash / cannot be used in Windows. The forward slash should always work, as it does in Java. This should also work when looking for resources, not only in the FunctionalTestCase.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14377","01/04/2018 18:06:49",1,"Change default back pressure strategy to WAIT only ""By default, only the WAIT strategy should be added automatically""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14386","01/05/2018 17:26:54",3,"Soap Connect extensions not comunicating HTTP Stereotype in http config paraemter ""Soap Connect extensions not comunicating HTTP Stereotype in http config paraemter""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14387","01/05/2018 19:51:56",3,"Extension documenter fails on document on elements that make usage of @Alias ""*Extension documenter fails on document on elements that make usage of @Alias* * When a param, operation, or whatever uses {{@Alias}} the documenter fails to document the parameter because it uses the Model name to find the Java Element, which won't be found in the case that the Alias is different from the element name.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14388","01/05/2018 20:37:16",8,"Extensions Client must use the correct event when used in an operation ""There're flaky test in the WSC build. Make sure they are not because of an actual race condition in the component and fix.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14391","01/06/2018 21:19:04",1,"Change the way that repeated model names are validated ""*Change the way that repeated model names are validated* Currently to validate the repetition of model names a validation is made on {{AbstractComplexModel}} when instantiating an {{ExtensionModel}} throwing an IllegalModelException. Throwing an exception when building the extension model makes impossible to have a Model Validator that could communicate correctly the repetition of model names, and in the AST Loader, indicate the configurations with infractions.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14394","01/08/2018 14:11:08",2,"Notification listener errors should not be propagated to runtime ""Notification listener exceptions should not be propagated to runtime. Currently, exceptions are caught, but errors aren't, this needs updating to catch Throwable and not Exception.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"MULE-14395","01/08/2018 15:45:24",1,"Update IO scheduler pool size based on capacity performance tests ""Update IO scheduler pool size based on capacity performance tests {{org.mule.runtime.scheduler.io.threadPool.maxSize=cores + ((mem - 245760) / 5120)}}""","",0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14402","01/08/2018 23:00:26",8,"Error handler of operation policies can't handle invalid requests ""There is no possible way to handle invalid requests from the error handler of the operation policy. An invalid request would be, for example, making a request to an inexistent resource (500 server error), or receiving a 403 from the server. After executing the 'execute-next' operator, if the request is invalid, the operation result is catched by the application error handler instead of using the policy one. This test reproduces the problem: https://github.com/mulesoft/mule-ee/commit/9ba58d92f083f26f061f544a0a69f3c7ef9b2f4b""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14409","01/09/2018 15:40:26",8,"Introduce PollingSource ""to be added ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14415","01/10/2018 15:02:23",8,"Variables set by should be exposed outside route ""When using inside a route (aggregation-complete route in an aggregator for example), the value set can't be accessed outside the route. We need it to work this way for the aggregators module.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14426","01/11/2018 18:31:45",2,"Add secure configuration properties for 4.x ""Implement secure-configuration-properties, analog to configuration-properties but encrypted.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14431","01/11/2018 20:41:54",1,"Transformers should use IO pool if they may read or write a stream ""Transformers should use IO pool if they may read or write a stream""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14435","01/12/2018 13:29:46",2,"Policies: HTTP Requester status code validator doesn't log processor location ""When an http requester sends a request and receives an error status, the logged error is: Note that the {{Element}} and {{Element XML}} entires show {{(None)}} instead of the location of the requester operation.""","ERROR 2018-01-12 10:19:37,411 [[HttpProxyPolicyInvalidRequestHandledTestCase#policyErrorHandlerIsAccessedAfterDoingInvalidRequest].http.requester.requestConfig.01 SelectorRunner] org.mule.runtime.core.internal.exception.OnErrorPropagateHandler: ******************************************************************************** Message : HTTP POST on resource 'http://localhost:9675/invalid' failed: internal server error (500). Error type : HTTP:INTERNAL_SERVER_ERROR Element : (None) Element XML : (None) (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14436","01/12/2018 15:20:26",1,"Make extensions parent pom use the AST Extension Loader ""Change the extensions parent pom to make they start using the AST based extension loader.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14443","01/14/2018 15:35:10",2,"Fix tests broken by DW error message changes ""Some tests have broken because DW has changed it's error message to indicate possible bugs in the app, particularly for invalid expressions. Most of those tests were asserting against whole error messages instead of checking for the specific errors they caused.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14444","01/14/2018 17:28:23",1,"VM Connector exports internal classes ""Current Exported Packages: Is required to review which class is used as API and making the entire package to be exported."""," """"exportedPackages"""": [ """"org.mule.extensions.vm.internal"""", """"org.mule.extensions.vm.api"""" ],",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0 +"MULE-14446","01/14/2018 17:38:38",2,"OAuth Module exports internal classes ""Current exported pacakges: """," """"exportedPackages"""": [ """"org.mule.extension.oauth2.internal.authorizationcode.state"""", """"org.mule.extension.oauth2.internal.clientcredentials"""", """"org.mule.extension.oauth2.internal.tokenmanager"""", """"org.mule.extension.oauth2.internal.authorizationcode"""" ] ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0 +"MULE-14451","01/15/2018 17:09:15",1,"Change default response streaming to false in HTTP service ""This must be turned off until on par performance can be achieved with streaming since it will affect users of the HTTP client.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14453","01/15/2018 17:47:24",0,"When creating ApplicationModel and ComponentModels inner beans should have a name so they can be later retrieved ""mule-aggregators-module added a new kind of reference, an aggregator listener can reference to an aggregator that is a source component. This needed to be handled by LazyInit and DataSense in order to support it. At the same time the org.mule.runtime.config.internal.BeanDependencyResolver had to be patched to work on this case as whenever the code to resolve dependencies from ApplicationModel was also returning as bean name the aggregatorName (needed for LazyInit) but the aggregator which is a source is created as inner child bean with Spring therefore the name declared on the aggregator is not the name that goes to the Spring bean and it couldn't be retrieved later in order to set as dependency.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14461","01/16/2018 16:41:14",0,"transactional element not propagating flowConstruct ""TransactionalInterceptingMessageProcessor must propagate the flowConstruct to the exception listener.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14465","01/16/2018 20:48:59",3,"Make the SDK Validate extension's exported packages ""Validate extensions exported packages""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14470","01/17/2018 01:09:21",1,"Avoid pattern matching for every notification fired ""This will do pattern matching of this string for each and every notification created/fired. This has an impact on performance. If we do what to format string like this then it should only happen if argument is invalid. {{ checkArgument(expectedDataType.isCompatibleWith(actualDataType), format(""""The action data type (%s) does not match the actual data type received (%s)"""", expectedDataType, actualDataType)); }}""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14471","01/17/2018 11:18:27",2,"Add field in mule-artifact.json to declare configuration properties that must be secure ""In Mule 3 it was possible to declare which properties must be handled as secure by the platform through a property in mule-app.properties (https://docs.mulesoft.com/runtime-manager/secure-application-properties). We need a similar approach for Mule 4 in order to maintain the same functionality until we properly implement discovery of artifacts configuration at deployment time.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14474","01/17/2018 14:52:39",3,"Add the information about metadata category at the parameter model level ""When a connector has several metadata categories, the API allows us to retrieve all keys associated with a config. The result is a Map>. But the fields marked as metadata keys do not have a property that allows us to determine the category associated with the key. We need this information in order to retrieve the correct set of keys associated with an operation""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14477","01/17/2018 16:31:01",2,"Nested flows/subflows not being initialized when executing tests on MUnit ""Having a munit test that executes a flow containing nested flow references, fails due that those flows are not initialized.  ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14478","01/17/2018 16:33:33",2,"Make ParameterGroupObjectBuilder#fieldsCache shared ""when different ParameterGroupObjectBuilder objects are build, each populates it's own fields cache, even if the class for which they are being requested is the same. This produces a performance penalty.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14500","01/18/2018 16:02:19",2,"Migration guide entry for enrichment in Mule 4 ""Migration guide entry for enrichment in Mule 4""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14501","01/18/2018 16:03:38",2,"Documentation for target and targetValue attributes in Mule 4 ""Documentation for target and targetValue attributes in Mule 4""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14508","01/18/2018 19:51:49",1,"Immutable transformations are chained in MultiMap ""Since we cannot guarantee that a certain MultiMap is immutable, there are several places where we are forcing that transformation, to the point where it could turn into a chain of going through elements over and over when it's already been made immutable.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14509","01/18/2018 20:17:03",1,"Extra host and port copies to get URI ""The current implementation of GrizzlyRequestAdapter getUri method, though it caches the result to only calculate it once, accesses the host and port in a manner that makes Grizzly save those results. We could easily avoid that.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14512","01/19/2018 14:06:59",3,"StackOverflow when compiling an extension with recursive structures ""When compiling an extension with recursive structures the build fails with a stack overflow error: """," [ERROR] Failed to execute goal org.bsc.maven:maven-processor-plugin:2.2.4:process (process) on project extension-with-resursive-structures: Error executing: java.lang.StackOverflowError -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.bsc.maven:maven-processor-plugin:2.2.4:process (process) on project extension-with-resursive-structures: Error executing at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286) at org.apache.maven.cli.MavenCli.main(MavenCli.java:197) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.execute(AbstractAnnotationProcessorMojo.java:292) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) ... 20 more Caused by: java.lang.RuntimeException: java.lang.StackOverflowError at com.sun.tools.javac.main.Main.compile(Main.java:553) at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129) at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138) at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.executeWithExceptionsHandled(AbstractAnnotationProcessorMojo.java:545) at org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.execute(AbstractAnnotationProcessorMojo.java:285) ... 22 more Caused by: java.lang.StackOverflowError at java.security.AccessController.doPrivileged(Native Method) at sun.reflect.annotation.AnnotationParser.annotationForMap(AnnotationParser.java:303) at com.sun.tools.javac.model.AnnotationProxyMaker.generateAnnotation(AnnotationProxyMaker.java:87) at com.sun.tools.javac.model.AnnotationProxyMaker.generateAnnotation(AnnotationProxyMaker.java:79) at com.sun.tools.javac.code.AnnoConstruct.getAnnotation(AnnoConstruct.java:179) at org.mule.runtime.ast.internal.VariableElementAST.getAnnotation(VariableElementAST.java:52) at org.mule.runtime.ast.internal.ASTType.lambda$null$6(ASTType.java:159) at java.util.stream.MatchOps$1MatchSink.accept(MatchOps.java:90) at java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958) at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126) at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:230) at java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:196) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.anyMatch(ReferencePipeline.java:449) at org.mule.runtime.ast.internal.ASTType.lambda$getAnnotatedFields$7(ASTType.java:159) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) at org.mule.runtime.ast.internal.ASTType.getAnnotatedFields(ASTType.java:160) at org.mule.runtime.module.extension.api.loader.java.type.ParameterizableTypeElement.getParameters(ParameterizableTypeElement.java:32) at org.mule.runtime.ast.internal.ExtensionTypeObjectFieldHandler.handle(ExtensionTypeObjectFieldHandler.java:54) at org.mule.metadata.ast.internal.TypeMirrorLoaderVisitor.visitDeclared(TypeMirrorLoaderVisitor.java:134) at org.mule.metadata.ast.internal.TypeMirrorLoaderVisitor.visitDeclared(TypeMirrorLoaderVisitor.java:44) at com.sun.tools.javac.code.Type$ClassType.accept(Type.java:944) at org.mule.metadata.ast.internal.handler.ArrayTypeHandler.handle(ArrayTypeHandler.java:48) at org.mule.metadata.ast.internal.TypeMirrorLoaderVisitor.visitDeclared(TypeMirrorLoaderVisitor.java:119) at org.mule.metadata.ast.internal.TypeMirrorLoaderVisitor.visitDeclared(TypeMirrorLoaderVisitor.java:44) at com.sun.tools.javac.code.Type$ClassType.accept(Type.java:944) at org.mule.metadata.ast.api.ASTTypeLoader.load(ASTTypeLoader.java:77) at org.mule.runtime.ast.internal.ASTType.asMetadataType(ASTType.java:200) at org.mule.runtime.ast.internal.ExtensionTypeObjectFieldHandler.setFieldType(ExtensionTypeObjectFieldHandler.java:83) at org.mule.runtime.ast.internal.ExtensionTypeObjectFieldHandler.handle(ExtensionTypeObjectFieldHandler.java:63) at org.mule.metadata.ast.internal.TypeMirrorLoaderVisitor.visitDeclared(TypeMirrorLoaderVisitor.java:134) at org.mule.metadata.ast.internal.TypeMirrorLoaderVisitor.visitDeclared(TypeMirrorLoaderVisitor.java:44) at com.sun.tools.javac.code.Type$ClassType.accept(Type.java:944) .... ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14514","01/19/2018 18:12:45",1,"Update processing strategy subscriber count based on performance testing ""Update processing strategy subscriber count based on performance testing""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14516","01/19/2018 21:19:01",1,"NameClashValidator fail when function parameters clash with another name ""If a Function has a Parameter which is a Pojo and it's name clashes with another TopLevelElement or ComponentName, the NameClashValidator will fail to validate the extension model.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14520","01/22/2018 13:54:04",1,"HTTP: CaseInsensitiveMultiMap loses case insensitiveness after making it immutable ""When using the result of calling toImmutableMultiMap on a CaseInsensitiveMultiMap, the returned MultiMap is not case insensitive.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14524","01/22/2018 17:45:00",2,"Schedulers don't indicate which one is exhausted ""When a scheduler is exhausted, a RejectedExecutionException is thrown which results in an OVERLOAD error being raised and logged by the CRITICAL handler. This provides information on the error and it's location yet it says nothing about which scheduler has failed to schedule work, making it difficult to asses at once what could be wrong.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"MULE-14526","01/22/2018 20:02:37",2,"Optimize to avoid contention in emission of event to flow ""Remove contention in emission of event to flow""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14534","01/23/2018 20:31:48",1,"Extension's processor plugin configuration doesn't consider generated sources ""Extension's processor plugin configuration doesn't consider generated sources""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14540","01/25/2018 16:10:09",0,"Use an independent lock to synchronize the lifecycle of the MuleContext ""This is a part that was done as part of MULE-13000 in mule 4.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14544","01/25/2018 19:39:40",2,"Provide a singleton MultiMap instance ""This is in order to avoid the creation of empty maps everywhere just to pass an empty map.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14552","01/26/2018 19:20:41",1,"Allow to override the location of the scheduler config file via system property ""do it""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"MULE-14553","01/26/2018 19:59:42",2,"TypeWrapper should not load class until needed ""Performance changes made by MULE-14495 introduced a dependency to the classes that breaks ToolingServices as the provided dependencies by users need to be on classpath now. ""","org.mule.tooling.client.bootstrap.internal.reflection.Dispatcher$ToolingCallable.call(Dispatcher.java:223)\n\t... 4 more\nCaused by: org.mule.runtime.module.artifact.api.classloader.exception.CompositeClassNotFoundException: Cannot load class 'com.sap.conn.jco.JCoException': [\n\tcom.sap.conn.jco.JCoException, \n\tCannot load class 'com.sap.conn.jco.JCoException': [\n\tClass 'com.sap.conn.jco.JCoException' has no package mapping for region 'tooling-extension-model9231dce1-02ce-11e8-8773-7a19b8cc04b0\/tooling-extension-model'., \n\tClass 'com.sap.conn.jco.JCoException' not found in classloader for artifact 'container'.]]\n\tat ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14556","01/26/2018 21:13:31",3,"Add Icons in all the extensions ""None of the actual connectors packages their connectors inside the mule plugin, start doing this.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14558","01/26/2018 21:18:29",1,"Unclear error with missing parameter in scheduler configuration ""In scheduler-pools.conf commented the line for org.mule.runtime.scheduler.io.workQueue.size. After restarting the runtime it fails to start successfully with an unclear error message. Adding -Dmule.verbose.exceptions=true will point that the error is related to scheduler configuration. The expected result should be that there is an error indicating which parameter is invalid or undefined.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"MULE-14560","01/28/2018 21:05:27",2,"Not understandable exception is thrown when a transformation fails over a String with '%d' ""If a transformation of a {{String}} value with a {{%d}} value fails, (like the header of DW: {{%dw 2.0}} ) makes the creation of the transformation exception fail. This could be reproduced because of: https://www.mulesoft.org/jira/browse/MULE-14561. """," ******************************************************************************** Message : d != org.mule.runtime.core.api.transformer.TransformerException. Element : new_flow/processors/1 @ test-app-ynvq:mule-config.xml:18 (Invoke Static) Element XML : #[%dw 2.0 output application/java--- {arg0: [""""val1"""", """"val2""""] as Array {class : """"[Ljava.lang.String""""}}] Error type : MULE:UNKNOWN Payload Type : java.lang.String -------------------------------------------------------------------------------- Root Exception stack trace: java.util.IllegalFormatConversionException: d != org.mule.runtime.core.api.transformer.TransformerException at java.util.Formatter$FormatSpecifier.failConversion(Formatter.java:4302) at java.util.Formatter$FormatSpecifier.printInteger(Formatter.java:2793) at java.util.Formatter$FormatSpecifier.print(Formatter.java:2747) at java.util.Formatter.format(Formatter.java:2520) at java.util.Formatter.format(Formatter.java:2455) at java.lang.String.format(String.java:2940) at org.mule.runtime.api.i18n.I18nMessageFactory.createStaticMessage(I18nMessageFactory.java:164) at org.mule.runtime.core.api.DefaultTransformationService.internalTransform(DefaultTransformationService.java:84) at org.mule.runtime.core.api.DefaultTransformationService.lambda$transform$0(DefaultTransformationService.java:156) at org.mule.runtime.core.api.util.func.CheckedSupplier.get(CheckedSupplier.java:25) at org.mule.runtime.core.api.DefaultTransformationService.transformThrowingRuntimeException(DefaultTransformationService.java:166) at org.mule.runtime.core.api.DefaultTransformationService.transform(DefaultTransformationService.java:156) at org.mule.runtime.module.extension.internal.runtime.resolver.TypeSafeTransformer.transform(TypeSafeTransformer.java:42) at org.mule.runtime.module.extension.internal.runtime.resolver.TypeSafeValueResolverWrapper.lambda$initialise$0(TypeSafeValueResolverWrapper.java:66) at org.mule.runtime.module.extension.internal.runtime.resolver.TypeSafeValueResolverWrapper$CachedResolver.lambda$new$1(TypeSafeValueResolverWrapper.java:94) at org.mule.runtime.module.extension.internal.runtime.resolver.TypeSafeValueResolverWrapper$CachedResolver.resolve(TypeSafeValueResolverWrapper.java:102) at org.mule.runtime.module.extension.internal.runtime.resolver.TypeSafeValueResolverWrapper.resolve(TypeSafeValueResolverWrapper.java:50) at org.mule.runtime.module.extension.internal.runtime.resolver.NullSafeValueResolverWrapper.resolve(NullSafeValueResolverWrapper.java:197) at org.mule.runtime.module.extension.internal.runtime.resolver.ResolverUtils.resolveRecursively(ResolverUtils.java:88) at org.mule.runtime.module.extension.internal.runtime.resolver.ResolverUtils.resolveValue(ResolverUtils.java:107) at org.mule.runtime.module.extension.internal.runtime.resolver.ResolverSet.resolve(ResolverSet.java:108) at org.mule.runtime.module.extension.internal.runtime.operation.ComponentMessageProcessor.getResolutionResult(ComponentMessageProcessor.java:477) at org.mule.runtime.module.extension.internal.runtime.operation.ComponentMessageProcessor.lambda$apply$4(ComponentMessageProcessor.java:204) at org.mule.runtime.core.api.util.func.CheckedFunction.apply(CheckedFunction.java:19) at org.mule.runtime.core.api.rx.Exceptions.lambda$checkedFunction$2(Exceptions.java:84) at reactor.core.publisher.FluxFlatMap$FlatMapMain.onNext(FluxFlatMap.java:347)",1,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14561","01/28/2018 22:19:45",5,"Expressions containing a opening bracket are not considered as a expression ""The following expression is not considered as a one:      \{\{#['[']}} *(This is just a reduced expression, but happens with any expression that contains a closing bracket in some place of the expression)* Considering the value as non-expression makes the value be considered as String, with all that this entails. ---------- The original expression: This is a big problem because: # The user doesn't have a workaround. # The user won't know why the expression doesn't get evaluated # In this particular case is worse because of: https://www.mulesoft.org/jira/browse/MULE-14560  """," #[%dw 2.0 output application/java --- { arg0: [""""val1"""", """"val2""""] as Array {class : """"[Ljava.lang.String""""} }]",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14565","01/30/2018 17:41:05",3,"Load static REMOTELY_CLOSED_EXCEPTION ""Load REMOTELY_CLOSED_EXCEPTION using service classloader""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14566","01/30/2018 19:58:17",2,"Use a CG free thread context implementation for logging ""https://logging.apache.org/log4j/2.x/manual/garbagefree.html""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14569","01/31/2018 15:43:58",2,"Ensure that exported resources in artifact descriptor always use linux file separator ""Mule artifact descriptor (mule-artifact.json) contains the list of artifact's resources that are exported. These resource path's must be declared using Linux file separator. As the descriptor can be manually edited, instead of just failing when the resources are not correctly written, the runtime can convert them to the expected format. ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14572","01/31/2018 18:48:26",2,"Scheduler#scheduleAtFixedRate cancels task if triggered while previous is still running ""When Scheduler#scheduleAtFixedRate is called on a Custom Scheduler with maxConcurrentTasks=1 or a pool with just 1 thread and a SynchronousQueue,   if a tasks takes longer than the rate, the next one is rejected, but then no more tasks are triggered. Any subsequent tasks must be triggered normally after a rejection.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"MULE-14573","01/31/2018 21:35:35",1,"Improve flaky until successful test cases ""org.mule.test.core.NonBlockingFunctionalTestCase.untilSuccessfulWithRetryExceptionAfter org.mule.test.routing.UntilSuccessfulTestCase.executeSynchronously""","",0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14577","02/01/2018 13:25:20",2,"Delayed task is triggered when target scheduler is busy is lost ""This happens when using the Scheduler#schedule method and the scheduler is busy at the trigger time. The task must be run when a thread in the scheduler is available instead of being lost.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"MULE-14581","02/01/2018 17:05:41",1,"Reduce level of log for RejectedExecutionExceptions that occur when shutdown timeout is exceeded. ""Reduce level of log for RejectedExecutionExceptions that occur when shutdown timeout is exceeded.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14582","02/01/2018 18:25:41",1,"Error has no string representation ""When one tries to log the error to see what happen, you get the default object toString. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14587","02/02/2018 18:02:43",2,"Properly handle InterruptedException in blocking processors api ""On MessageProcessors#processToApply, when an InterruptedException is thrown, it is not properly handled. It must set the interrupted flag on the thread.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14590","02/04/2018 12:56:33",1,"ThrottlingScheduler active tasks count breaks when tasks are cancelled. ""ThrottlingScheduler active tasks count breaks when tasks are cancelled.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"MULE-14594","02/08/2018 19:05:50",2,"Document raise-error component ""We need to document how the component works and the use cases.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14599","02/12/2018 03:30:41",3,"Unexpected extensionNameNoSpaces archetype parameter value ""When creating a new extension using Archetype, an unexpected parameter `_extensionNameNoSpaces_` value is being asked by maven. It should actually be derived from already specified `_extensionName_` parameter. _Note: Module generation completes successfully._ +*Command Run -*+ _mvn archetype:generate -DarchetypeCatalog=http://repository.mulesoft.org/releases/ -DarchetypeGroupId=org.mule.extensions -DarchetypeArtifactId=mule-extensions-archetype -DarchetypeVersion=1.1.0 -DgroupId=com.javastreets -DartifactId=mule-modules-test2 -*DextensionName=test*_   _*Here is the output:*_ [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Maven Stub Project (No POM) 1 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] >>> maven-archetype-plugin:2.4:generate (default-cli) > generate-sources @ standalone-pom >>> [INFO] [INFO] <<< maven-archetype-plugin:2.4:generate (default-cli) < generate-sources @ standalone-pom <<< [INFO] [INFO] [INFO] --- maven-archetype-plugin:2.4:generate (default-cli) @ standalone-pom --- [INFO] Generating project in Interactive mode [INFO] Archetype repository not defined. Using the one from [org.mule.extensions:mule-extensions-archetype:1.0.0 -> https://repository.mulesoft.org/nexus/content/repositories/releases] found in catalog http://repository.mulesoft.org/releases/ [INFO] Using property: groupId = com.javastreets [INFO] Using property: artifactId = mule-modules-test2 [INFO] Using property: version = 1.0.0-SNAPSHOT [INFO] Using property: package = org.mule.extension [INFO] Using property: extensionName = test Feb 11, 2018 10:23:07 PM org.apache.velocity.runtime.log.JdkLogChute log INFO: FileResourceLoader : adding path '.' Feb 11, 2018 10:23:07 PM org.apache.velocity.runtime.log.JdkLogChute log {color:#ff0000}_*INFO: Null reference [template 'extensionNameNoSpaces', line 1, column 1] : $\{extensionName.replace(""""-"""", """" """").replace("""" """", """""""").replaceAll(""""(?i)extension"""", """""""").replaceAll(""""(?i)connector"""", """""""").trim()} cannot be resolved.*_{color} {color:#ff0000}_*Define value for property 'extensionNameNoSpaces': $\{extensionName.replace(""""-"""", """" """").replace("""" """", """""""").replaceAll(""""(?i)extension"""", """""""").replaceAll(""""(?i)connector"""", """""""").trim()}: :*_{color} {color:#ff0000}_*Confirm properties configuration:*_{color} {color:#ff0000}_*groupId: com.javastreets*_{color} {color:#ff0000}_*artifactId: mule-modules-test2*_{color} {color:#ff0000}_*version: 1.0.0-SNAPSHOT*_{color} {color:#ff0000}_*package: org.mule.extension*_{color} {color:#ff0000}_*extensionName: test*_{color} {color:#ff0000}_*extensionNameNoSpaces: $\{extensionName.replace(""""-"""", """" """").replace("""" """", """""""").replaceAll(""""(?i)extension"""", """""""").replaceAll(""""(?i)connector"""", """""""").trim()}*_{color} {color:#ff0000} _*Y: :*_{color} {color:#ff0000}_*[INFO] ----------------------------------------------------------------------------*_{color} [INFO] Using following parameters for creating project from Archetype: mule-extensions-archetype:1.1.0 [INFO] ---------------------------------------------------------------------------- [INFO] Parameter: groupId, Value: com.javastreets [INFO] Parameter: artifactId, Value: mule-modules-test2 [INFO] Parameter: version, Value: 1.0.0-SNAPSHOT [INFO] Parameter: package, Value: org.mule.extension [INFO] Parameter: packageInPathFormat, Value: org/mule/extension [INFO] Parameter: package, Value: org.mule.extension [INFO] Parameter: version, Value: 1.0.0-SNAPSHOT [INFO] Parameter: groupId, Value: com.javastreets [INFO] Parameter: extensionName, Value: test [INFO] Parameter: extensionNameNoSpaces, Value: test [INFO] Parameter: artifactId, Value: mule-modules-test2 [WARNING] Don't override file /Volumes/MM/codebase/mule/mule4/mule-modules-test2/src/main/java/org/mule/extension [WARNING] Don't override file /Volumes/MM/codebase/mule/mule4/mule-modules-test2/src/test/java/org/mule/extension [WARNING] Don't override file /Volumes/MM/codebase/mule/mule4/mule-modules-test2/src/test/resources [INFO] project created from Archetype in dir: /Volumes/MM/codebase/mule/mule4/mule-modules-test2 [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9.094 s [INFO] Finished at: 2018-02-11T22:23:15-05:00 [INFO] Final Memory: 21M/314M [INFO] ------------------------------------------------------------------------     _*Maven Envrionment -*_  _*mvn -version*_ _*Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T03:58:13-04:00)*_ _*Maven home: /Users/manik/.sdkman/candidates/maven/current*_ _*Java version: 1.8.0_161, vendor: Oracle Corporation*_ _*Java home: /Users/manik/.sdkman/candidates/java/8u161-oracle/jre*_ _*Default locale: en_US, platform encoding: UTF-8*_ _*OS name: """"mac os x"""", version: """"10.13.3"""", arch: """"x86_64"""", family: """"mac""""*_""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14600","02/12/2018 04:08:01",3,"Mule Extension Archetype is not Camel Casing Extension Name for Classes ""When an extension module is generated using mule-extension-archetype, extension name is not camel cased while generated classes.  Example command -  mvn archetype:generate -DarchetypeCatalog=http://repository.mulesoft.org/releases/ -DarchetypeGroupId=org.mule.extensions -DarchetypeArtifactId=mule-extensions-archetype -DarchetypeVersion=1.1.0 -DgroupId=com.javastreets -DartifactId=mule-modules-zip5 -Dpackage=com.javastreets -Dversion=0.0.1-SNAPSHOT *-DextensionName=zip5* -DextensionNameNoSpaces=zip5   Generated Classed -  mule-modules-zip5 ├── README.md ├── pom.xml └── src ├── main │   ├── java │   │   └── com │   │   └── javastreets │   │   └── internal │   │   ├── zip5Configuration.java │   │   ├── zip5Connection.java │   │   ├── zip5ConnectionProvider.java │   │   ├── zip5Extension.java │   │   └── zip5Operations.java │   └── resources └── test ├── java │   └── com │   └── javastreets │   └── zip5OperationsTestCase.java └── resources └── test-mule-config.xml This is NOT the behavior when modules are generated using plugin - mvn org.mule.extensions:mule-extensions-archetype-maven-plugin:generate with extension name as zip3, Class Names generated are - │   │   └── internal │   │   ├── Zip3Configuration.java │   │   ├── Zip3Connection.java │   │   ├── Zip3ConnectionProvider.java │   │   ├── Zip3Extension.java │   │   └── Zip3Operations.java ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14602","02/14/2018 19:28:01",8,"Make the generated connector documentation compliant with the Mulesoft Docs renderer. ""Make the generated connector documentation compliant with the Mulesoft Docs renderer. Here is a list of typos and fixes required to make the generated docs compliant with the asciidoc renderer used in our docs web page. https://docs.google.com/spreadsheets/d/11idVtarnmRbBqw4EOLawrUqojNYAOsFCiLCbMHPHmV8 We should fix/review all the entries""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14603","02/14/2018 21:12:25",8,"Expression Regex fails on detect expression when this have an unbalanced opening bracket ""The following expression is not considered as a one:      \{\{#['[']}} *(This is just a reduced expression, but happens with any expression that contains a closing bracket in some place of the expression)* Considering the value as non-expression makes the value be considered as String, with all that this entails. The problem is inside -> {{org.mule.runtime.core.privileged.util.TemplateParser}} ---------- The original expression: This is a big problem because: # The user doesn't have a workaround. # The user won't know why the expression doesn't get evaluated # In this particular case is worse because of: https://www.mulesoft.org/jira/browse/MULE-14560  """," #[%dw 2.0 output application/java --- { arg0: [""""val1"""", """"val2""""] as Array {class : """"[Ljava.lang.String""""} }]",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14606","02/15/2018 23:46:22",2,"Email connector doesn't work with IMAP gmail OOTB ""Email connector doesn't work with IMAP gmail OOTB""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14615","02/20/2018 20:29:41",5,"DB Connector returns Clob objects instead of InputStreams ""*DB Connector returns a Clob object instead of returning an InputStream* * DB Connector when doing a SELECT to a Table which contains Clob values, nowadays the raw Clobs are returned to the flow and those are unhandables using DW.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0 +"MULE-14616","02/20/2018 21:30:35",2,"StreamingHelper doesn't support TypedValue properties ""*StreamingHelper doesn't support TypedValue properties* When processing a Map containing InputStreams wrapped in TypedValues the StreamingHelper doesn't consider these cases and doesn't generate a Repeteable stream of it.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14620","02/21/2018 17:01:47",5,"Extension Loader load incorrectly generic types. ""*AST Extension Loader fails to find the connection type for DynamoDB Connector* * The AST Loader is lost when walking between generics in the hierarchy of Connection Providers that the connector provides. * Find and fix it /shrug =========== Update: Also happens when the following thing : {{SomeListener extends AbstractListener}} {{AbstractListener extends Source}}""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0 +"MULE-14627","02/22/2018 13:57:42",3,"SDK should log when trying to reconnect a connection for an operation ""*SDK should log when trying to reconnect a connection for an operation* * Nowadays when a Source stops and request for a working connection this is logged: communicating that a reconnection is being done. The problem comes that when this is done for an operation, nothing is being logged. """," ERROR 2018-02-22 10:55:34,725 [SimpleUnitTestSupportScheduler.04] org.mule.runtime.core.api.retry.policy.ConnectNotifier: Failed to connect/reconnect: Message Source Reconnection. Root Exception was: FAAAAIL. Type: class org.mule.runtime.api.connection.ConnectionException ERROR 2018-02-22 10:55:36,734 [SimpleUnitTestSupportScheduler.04] org.mule.runtime.core.api.retry.policy.ConnectNotifier: Failed to connect/reconnect: Message Source Reconnection. Root Exception was: FAAAAIL. Type: class org.mule.runtime.api.connection.ConnectionException ERROR 2018-02-22 10:55:38,740 [SimpleUnitTestSupportScheduler.04] org.mule.runtime.core.api.retry.policy.ConnectNotifier: Failed to connect/reconnect: Message Source Reconnection. Root Exception was: FAAAAIL. Type: class org.mule.runtime.api.connection.ConnectionException",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14632","02/22/2018 21:21:01",3,"WSC: Invalid property name on class java.lang.String. ""WSC: Invalid property name on class java.lang.String.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14636","02/23/2018 21:16:59",5,"HTTP Connector is not including in its type catalog the declaration for Origin type ""The extension DTO for """"org.mule.connectors:mule-http-connector:1.1.0"""" does not include in its types and entry for """"Origin"""" which used to declare subTypes: This is not allowing Tooling to get associate these subTypes to an extension, therefore it is not going to be rendered. """," @SubTypeMapping(baseType = Origin.class, subTypes = {EveryOrigin.class, SingleOrigin.class}) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14640","02/26/2018 19:51:59",8,"Various variable scoping errors between Operation Policies, Source Policies and Flow's error handlers ""While fixing MULE-14414 I found out that variables set in the on error propagate of a policy operation, then it would be accesible from the flow's on error continue/propagate. Just in case, the error wasn't introduced by the fix in MULE-14414. I added a test in mule-ee: (ignored) (Edit) While looking through this issue, I found many variable scoping issues: - Flow variables that were visible in operation policies and source policies' error handlers - operation policies and source policies' variables that were visible in the flow's error handler - Operation policies' error handler variables that were visible in the flow's error handler - Operation Policies' variables that weren't visible to source policies' error handler Some more issues similar to the described above. ""","HttpProxyPolicyInvalidRequestVariableScopeTestCase#policyErrorHandlerIsAccessedAfterDoingInvalidRequest",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14661","03/01/2018 19:07:55",3,"Archetype not using connector name in the generated packages ""Archetype not using connector name in the generated packages. today is generating this `org.mule.extension.internal` and it should be something like this `org.mule.extension..internal` :B""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14677","03/06/2018 19:51:38",5,"Need a way to specify differnet defualts for the primaryNodeOnly parameter ""By default, the primaryNodeOnly parameter defaults to false, which makes sense most of the times. However, some cases like the jms:listener need to default to true. We need a way to enable this.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14680","03/07/2018 19:54:32",2,"Aggregators module README.md suggests a dependency with no classifier ""The README.md of the aggregators modules is telling users that in order to add it to a project the can just add the dependency: When it should be: """," org.mule.modules mule-aggregators-module 1.1.0-SNAPSHOT   org.mule.modules mule-aggregators-module 1.1.0-SNAPSHOT mule-plugin ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0 +"MULE-14681","03/08/2018 14:02:33",0,"Returned stream is closed when using pooled connections ""When an operation returns an InputStream which depends on an open connection, the SDK will close that connection by default. That means that for the stream to keep open for the rest of the flow, the user must manually implement certain design patterns like: * Manually obtaining a new connection that is bundled into a custom input stream (e.g: FTP connector) * Use a cached connection provider which returns a client, which in turn knows how to obtain the connection (e.g: HTtp connector) This problem has already been solved for the case of auto paging operations (e.g: db:select), we need to extrapolate the same solution to the InputStream case. Something to consider is that in the InputStream case, a corner case exists which doesn't on the auto paging one. That case is that the operation might end up returning a stream which is NOT associated with the connection (e.g: EDI Connectors which first writes to a temp file and then streams from it)""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14683","03/08/2018 17:49:46",0,"Mime Type Disappears Dissapears in VM inbound when under load ""DataType of the message is lost when messages are batch in a VM inbound endpoint.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14686","03/08/2018 20:54:34",1,"Expiration of an ObjectStore doesn't run if there is another one running ""When 2 ObjectStore expirations are triggered near in time, the second one to be triggered is skipped and a warning is logged. In that case, both expirations should run in parallel.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14693","03/09/2018 18:19:45",2,"Minor performance improvements ""Some minor improvements on CPU usage based on the snapshot for the HTTP requester cases.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14694","03/09/2018 19:35:18",3,"Cannot access application resources from KeyResolver for Configurations "" When resolving the component keys the Thread.current().getContextClassLoader() is not being set therefore the connector's code implementation cannot rely on it and has to use the class loader that loaded the resolver class. It should do it as that sets the context class loader correctly.""","org.mule.runtime.module.extension.internal.runtime.config.ConfigurationProviderToolingAdapter#addComponentKeysorg.mule.runtime.module.extension.internal.runtime.ExtensionComponent#getMetadataKeys",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14696","03/09/2018 20:31:49",8,"Static Metadata resolvers doesn't work with nonblocking operations ""*Static Metadata resolvers doesn't work with nonblocking operations* Having an Operation like that uses {{@OutputJsonType}}: Will make the compilation fail saying: """," @MediaType(MediaType.APPLICATION_JSON) @OutputJsonType(schema = """"schemas/retrieve-applications.json"""") public void someOp( CompletionCallback competitionCallback){ } [ERROR] * Extension 'SomeExtension' specifies a/an operation named 'someOp' with type 'class java.lang.Object' as return type. Components that return a type such as Object or Map (or a collection of any of those) must have defined an OutputResolver ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14698","03/10/2018 01:08:30",2,"Data format documentation for DW is wrong/incomplete ""The current docs regarding the supported data formats has a number of problems: * the URL encoded docs are incomplete and have no full read/write example * the multipart docs are wrong, it features an example using postman but mistakenly identifies each part and does not really feature a full read/write example. Additionally, the migration docs lack an entry on message attachments that links to DW's multipart doc, HTTP migration docs and possibly Email docs. This means Mule 3 users cannot clearly see how to approach migrating attachment usage.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14700","03/12/2018 13:27:20",2,"Artifact deployment phases are not displayed on Mule logs when deploying applications from Tooling Runtime Client ""Only the following messages are displayed whenever an artifact is deployed from Tooling Runtime Client: There should entries for """"new artifact"""", """"install"""", """"dispose""""."""," ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Initializing app + + 'tooling-application-37f2a2a0-255b-11e8-ac4d-c4b301b71ca + + 3' + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ INFO 2018-03-11 15:37:15,459 [qtp1229465464-82] org.mule.runtime.module.deployment.impl.internal.application.DefaultMuleApplication: ********************************************************************** * Started app * * 'tooling-application-37f2a2a0-255b-11e8-ac4d-c4b301b71ca3' * * Application libraries: * * - tooling-domain-3601cf20-255b-11e8-ac4d-c4b301b71ca3 * ********************************************************************** ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14705","03/12/2018 20:39:48",1,"Fix tests broken by DW error stack changes ""Some tests broke due to changes in DW's stack printing during errors.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14709","03/13/2018 20:35:43",2,"Add MEL migration examples ""Need to complete and publish all examples in the MEL migration doc.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14710","03/13/2018 20:58:50",8,"Define tools and tasks required to simplify UX around classloading isolation ""This task is to define the whole UX around classloading isolation and potencial issues, for instance: * When there's a CNFE, what information should we show to the user for troubleshotting at design time? * When it's using a java module or any other extension that requires access to resources within the app, how we can simplify experience so we automatically export resources through the packager * etc.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14721","03/14/2018 14:35:55",1,"Minor tweaks to use of reactor based on feedback ""Based on feedback from reactor team""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14723","03/14/2018 15:11:11",1,"Provide a way for intercepting processors to override the publisher of the event context "".""","",0,1,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14724","03/14/2018 15:31:53",2,"Initial Mule 4 architecture documentation / TB splitted - Cont. ""Initial Mule 4 architecture documentation / TB splitted * Define mechanism to document architecture * Main Mule Runtime components diagrams * Main Mule Runtime activity diagrams * Some other stuff""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14735","03/14/2018 21:41:35",8,"Avoid iterating parameters map on operation policies ""The iteration adds performance overhead""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14736","03/15/2018 15:03:09",1,"Custom scheduler shutdown from a thread from the same scheduler fails ""This may lead to a memory leak of the scheduler's thread group when a scheduler is being cancelled from within one of its threads. This seems to be a common way for reactor to handle some situations. When this happens, the stack leading to the shutdown call is:   ""","  org.mule.service.scheduler.internal.threads.SchedulerThreadPools$CustomScheduler.shutdownWrapUp(SchedulerThreadPools.java:554) [mule-service-scheduler-1.1.4-SNAPSHOT-mule-service/:?] at org.mule.service.scheduler.internal.threads.SchedulerThreadPools$CustomScheduler.shutdown(SchedulerThreadPools.java:512) [mule-service-scheduler-1.1.4-SNAPSHOT-mule-service/:?] at reactor.core.publisher.EventLoopProcessor.cancel(EventLoopProcessor.java:488) [reactor-core-3.2.0.M1-MULE-001.jar:3.2.0.M1-MULE-001] at reactor.core.publisher.EventLoopProcessor.decrementSubscribers(EventLoopProcessor.java:570) [reactor-core-3.2.0.M1-MULE-001.jar:3.2.0.M1-MULE-001] at reactor.core.publisher.WorkQueueProcessor$WorkQueueInner.run(WorkQueueProcessor.java:570) [reactor-core-3.2.0.M1-MULE-001.jar:3.2.0.M1-MULE-001] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_131] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_131] at org.mule.service.scheduler.internal.AbstractRunnableFutureDecorator.doRun(AbstractRunnableFutureDecorator.java:107) [mule-service-scheduler-1.1.4-SNAPSHOT-mule-service/:?] at org.mule.service.scheduler.internal.RunnableFutureDecorator.run(RunnableFutureDecorator.java:54) [mule-service-scheduler-1.1.4-SNAPSHOT-mule-service/:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131] ERROR 2018-03-15 11:17:03,957 [[version_manager].version_manager-main.ring-buffer.01] org.mule.service.scheduler.internal.threads.SchedulerThreadPools: Unable to destroy ThreadGroup '[version_manager].version_manager-main.ring-buffer' of Scheduler '[version_manager].version_manager-main.ring-buffer @27f2d1cf' (java.lang.IllegalThreadStateException). Remaining threads in the group are: * [version_manager].version_manager-main.ring-buffer.01 ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"MULE-14740","03/15/2018 19:19:31",3,"Credentials leak in error messages ""DB connector is printing out the whole connections URL in the exception payload in case of any exception without stripping out/masking out the DB passwords... this becomes a security vulnerability Cannot get connection for URL jdbc:oracle:thin:username/password@sdsoralpd0a-scan.dev-data.qts.fni:1521/dt2dtasvc : IO Error: Unknown host specified Credentials should be masked. Also check other logs or possible places where the same thing might happen""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0 +"MULE-14749","03/16/2018 17:09:37",1,"Logger extension model claims DEBUG is default ""Changes were made in MULE-12886 to make the log level INFO by default. However, it is set to DEBUG by the MuleExtensionModelDeclarer.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14750","03/16/2018 18:13:17",0,"Add the capability of configuring the Service Name for an Oracle Connection ""Add the capability of configuring the Service Name for an Oracle Connection Mule Ticket for SE-1791""","",0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0 +"MULE-14757","03/19/2018 17:19:19",2,"Foreach with child with different processing types behaves asynchronously ""When mixing compoennts with different processing types inside a freach (for instance, logger and scripting), or just putting a non CPU-LITE processor, each child is executed asynchronously. This breaks the scenario where each iten has side effects (for instance, a file write) and that state is needed after the foreach, resulting in a race condition.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14760","03/19/2018 19:23:11",2,"HTTP request connection limit reached error is not descriptive ""When the maxConnections attribute is set and the number of requests exceed it, the following HTTP:CONNECTIVITY error is seen: The """"No slot available"""" message has been copied from AHC code and does not match the semantics we are given to the feature. It should be something like: Maximum connection limit reached, request cannot be processed."""," Root Exception stack trace: com.ning.http.client.filter.FilterException: No slot available for processing Request http://10.15.2.149:80/RulesService/api/workers/1823884/longevityScores?companyId=15&geocode=020000000 GET headers: X-Correlation-ID:0-dc1849b3-27a0-11e8-9adf-02b6df4edb32 Content-Type:application/json Content-Length:0 with AsyncHandler org.mule.service.http.impl.service.client.async.ResponseAsyncHandler@2ef6ce14 at org.mule.service.http.impl.service.client.CustomTimeoutThrottleRequestFilter.filter(CustomTimeoutThrottleRequestFilter.java:48) at com.ning.http.client.AsyncHttpClient.preProcessRequest(AsyncHttpClient.java:538) at com.ning.http.client.AsyncHttpClient.executeRequest(AsyncHttpClient.java:510) at org.mule.service.http.impl.service.client.GrizzlyHttpClient.sendAsync(GrizzlyHttpClient.java:338) at com.mulesoft.service.http.impl.service.client.EEGrizzlyHttpClient.sendAsync(EEGrizzlyHttpClient.java:119) at org.mule.extension.http.internal.request.HttpRequesterConnectionManager$ShareableHttpClient.sendAsync(HttpRequesterConnectionManager.java:116) at org.mule.extension.http.internal.request.client.HttpExtensionClient.send(HttpExtensionClient.java:71) at org.mule.extension.http.internal.request.HttpRequester.doRequestWithRetry(HttpRequester.java:104) at org.mule.extension.http.internal.request.HttpRequester.lambda$doRequestWithRetry$3(HttpRequester.java:130) ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14763","03/19/2018 21:55:27",2,"Upgrade Jetty to 9.2.24.v20180105 ""Jetty must be upgraded to a supported version.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14768","03/21/2018 14:53:03",2,"Extension with an operation with raw List return type breaks at compile time. ""*Extension with an operation with raw List return type breaks at compile time.* Output is: [ERROR] diagnostic: error: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 org.mule.runtime.api.exception.MuleRuntimeException: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14773","03/21/2018 21:00:14",2,"Update first-successful and round-robin Mule 4 documentation ""We need to update first-successful and round-robin documentation for Mule 4""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14778","03/22/2018 21:04:11",1,"NameUtils should a compiled regular expression for camelScatterConcat function ""https://github.com/mulesoft/mule-api/blob/master/src/main/java/org/mule/runtime/api/util/NameUtils.java#L91 when doing split should use a compiled regular expression.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14779","03/22/2018 21:14:39",8,"Spike for an Application Model API including spec. - Part1 ""This is the spike which outcome is going to be a first version of the API and an specification explaining it and the use cases to be solved with it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14788","03/23/2018 15:09:14",1,"TypeAwareConfigurationFactory should lazily add annotations to the configurationType ""TypeAwareConfigurationFactory is adding annotations to the configurationType when the factory is instantiated instead of when the factory is used. This means that cglib would be used when no needed (case for loading an extension model).""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14789","03/23/2018 16:13:27",5,"DB input parameters names are not parsed correctly ""If you have an input parameter named `first-name` the `-` char is breaking the parser, so it results in an error like: """," ERROR 2018-03-23 09:13:23,525 [[MuleRuntime].io.05: [employee-api-mysql-v1-0-3].post:\employee:application\json:employee-api-spec-config.BLOCKING @7f6a31ec] [event: 0-f5f03990-2e9b-11e8-89a3-186590d286b3] org.mule.runtime.core.internal.exception.OnErrorPropagateHandler: ******************************************************************************** Message : Parameter 'first' was not bound for query 'INSERT INTO `employee`.`employee` (`first-name`) VALUES (:first-name)'. Element : post:\employee:application\json:employee-api-spec-config/processors/1 @ employee-api-mysql-v1-0-3:employee-api-spec-v1-0-3.xml:136 (Insert Employee) Element XML : INSERT INTO `employee`.`employee` (`first-name`) VALUES (:first-name) #[{ 'first-name' : payload.first_name }] Error type : MULE:UNKNOWN ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0 +"MULE-14794","03/23/2018 20:22:57",1,"Update DW dependency to 2.1.3-SNAPSHOT ""Upgrade DW dependency that includes fixes for some flaky tests, among other things""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14801","03/24/2018 22:39:10",2,"SimpleRetryPolicy: Use mule schedulers with Mono.delay instead of reactor ones ""This also happens on PrivilegedNonBlockingComponentExecutor. Make sure the Mono is properly disposed also.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14814","03/27/2018 17:35:48",1,"HTTP migration doc should cover RAML usage ""The HTTP migration docs do not cover the fact that RAML metadata is no longer supported and that REST Connect should be now used in those scenarios. We need to add a note on that and link to https://docs.mulesoft.com/anypoint-exchange/to-deploy-using-rest-connect""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14822","03/28/2018 19:07:19",2,"ConfigurationException: Element 'tokenManagerConfig-MyConfigName' is not defined in the Mule Registry ""When using oauth module in the context of lazy init (MUnit) the attribute definition for tokenManager on {{oauth:client-credentials-grant-type}} is not defined a simple reference parameter therefore the initialization of the tokenManager referenced entity is not being done and fails with a {{ConfigurationException: Element 'tokenManagerConfig-MyConfigName' is not defined in the Mule Registry}}. The reason why it is not being marked as reference is that it is declared to support expressions on the operation parameter reference. ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0 +"MULE-14836","04/03/2018 14:40:38",2,"Failure to evaluate parse expressions for logger when intercepting ""When having a parse expression in a logger, for example: The expression fails with the attached message. This is causing any MUnit test that has this kind of logger to fail, since we intercept every processor of the application."""," ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14837","04/03/2018 14:51:52",5,"Fix DB flaky tests ""Fix following tests cases: Fix following tests cases: |!https://muleesb.ci.cloudbees.com/static/4eadad58/images/16x16/document_add.png! [org.mule.extension.db.integration.connectivity.DataSourcePoolingTestCase.limitsConnections[DERBY]|https://muleesb.ci.cloudbees.com/job/Mule-DB-Connector/lastCompletedBuild/org.mule.connectors$mule-db-connector/testReport/org.mule.extension.db.integration.connectivity/DataSourcePoolingTestCase/limitsConnections_DERBY_/]|20 sec|1| |!https://muleesb.ci.cloudbees.com/static/4eadad58/images/16x16/document_add.png! [org.mule.extension.db.integration.source.RowListenerTestCase.idempotentListen[DERBY]|https://muleesb.ci.cloudbees.com/job/Mule-DB-Connector/lastCompletedBuild/org.mule.connectors$mule-db-connector/testReport/org.mule.extension.db.integration.source/RowListenerTestCase/idempotentListen_DERBY_/]|5.6 sec|1| |!https://muleesb.ci.cloudbees.com/static/4eadad58/images/16x16/document_add.png! [org.mule.extension.db.integration.source.RowListenerTestCase.listenPlanets[DERBY]|https://muleesb.ci.cloudbees.com/job/Mule-DB-Connector/lastCompletedBuild/org.mule.connectors$mule-db-connector/testReport/org.mule.extension.db.integration.source/RowListenerTestCase/listenPlanets_DERBY_/]|5.5 sec|1| |!https://muleesb.ci.cloudbees.com/static/4eadad58/images/16x16/document_add.png! [org.mule.extension.db.integration.source.RowListenerTestCase.listenPlanetsWithWatermark[DERBY]|https://muleesb.ci.cloudbees.com/job/Mule-DB-Connector/lastCompletedBuild/org.mule.connectors$mule-db-connector/testReport/org.mule.extension.db.integration.source/RowListenerTestCase/listenPlanetsWithWatermark_DERBY_/]| ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0 +"MULE-14844","04/03/2018 19:39:30",2,"SDK should validate that the given default value of an Enum parameter is a valid value ""*SDK should validate that the given default value of an Enum parameter is a valid value* When configuring a Default value for an Enum parameter the SDK can easily validate that the given value is a valid one.  Nowadays the value is not validated letting produce cryptic errors at runtime:    """," org.xml.sax.SAXParseException; systemId: http://www.mulesoft.org/schema/mule/ibm-mq/current/mule-ibm-mq.xsd; lineNumber: 139; columnNumber: 207; cvc-datatype-valid.1.2.3: 'WMQ_CLIENT_JMS_COMPLIANT' is not a valid value of union type 'com.mulesoft.connectors.ibmmq.IBMTargetClientEnumType'. org.xml.sax.SAXParseException; systemId: http://www.mulesoft.org/schema/mule/ibm-mq/current/mule-ibm-mq.xsd; lineNumber: 139; columnNumber: 207; a-props-correct.2: Invalid value constraint value 'WMQ_CLIENT_JMS_COMPLIANT' in attribute 'targetClient'. ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14846","04/03/2018 22:14:50",13,"Move Soap Service Implementation to a new module decoupled from mule. ""*Move Soap Service Implementation to a new module decoupled from mule.* This will: * enable WSC and Soapkit to move faster without depending on an specific runtime version. * share the RT code base between service, soapkit, wsc -> bugs are fixed only once :) * WSC / Soapkit / Service can use different versions of the library if required. ""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0 +"MULE-14847","04/04/2018 13:46:41",2,"Operation retry with transaction changes thread ""When retrying an operation and a transaction is active, the retry may be run in another thread, breaking the transactional context. Transaction support requires that transactional flows do not switch threads.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14853","04/05/2018 19:51:37",2,"Fix ConstrainedConnectorExceptionStrategyMule2126TestCase in 3.8.x ""Test fails after the MULE-8175: Upgrade Xerces to 2.11.2 due to a format change in parse error message""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14854","04/05/2018 21:15:40",3,"ExtensionModel generator takes into account static methods in operations ""Added some static methods in the PetStore test extension for testing some scenarios and that made the extension model generation tests fail. Revert these code changes: * [https://github.com/mulesoft/mule/commit/eac0f0691462aae50026971d48bf9f68ca908b02#diff-10201da405805070c55f2c5b8575575eR42] * [https://github.com/mulesoft/mule/commit/eac0f0691462aae50026971d48bf9f68ca908b02#diff-b900c1d8a06eb1e8f92ee10c477b7dd7R772]  ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14855","04/06/2018 14:13:28",8,"ConfigReference String parameter is not lazy initialized properly ""Having the following parameter {code} @ConfigReference(namespace = """"HTTP"""", name = """"REQUEST_CONFIG"""") @Parameter private String requesterConfig; {code} During lazy initialization it does not initialize, even then adding ExpressionSupport(NOT_SUPPORTED). This results in MUnit tests failing. An example with WSC: {code:xml} {code}"""," @ConfigReference(namespace = """"HTTP"""", name = """"REQUEST_CONFIG"""") @Parameter private String requesterConfig; ",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-14856","04/06/2018 14:51:58",2,"Fix BasicHttpProxyToHttpsTestCase ""BasicHttpProxyToHttpsTestCase tests started failing after the upgrade of Jetty to 9.2.24.v20180105 performed in MULE-14763""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-15290","07/04/2018 17:55:29",8,"Spike for an Application Model API including spec. - Part2 ""This is the spike which outcome is going to be a first version of the API and an specification explaining it and the use cases to be solved with it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-16654","04/04/2019 17:06:16",0,"Allow to enable logs on tooling applications in order to allow troubleshooting ""Application deployed for Tooling have the logs muted. We should allow to override this by System Property in order to allow Tooling to do troubleshooting.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 +"MULE-18312","04/17/2020 14:31:52",0,"LazyMuleArtifactContext ignores custom Global Error Handler ""LazyMuleArtifactContext ignore custom Global Error Handler definition when this configuration is located after failing flow. _Configuration component definition_ is one of core's component and should be always enabled to ensure it will be loaded at first independently wherever it's located in mule's application definition.  ""","",1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1