386 KiB
386 KiB
| 1 | issuekey | title | description | storypoint |
|---|---|---|---|---|
| 2 | STUDIO-95 | Support for request/reply | request/reply http://www.mulesoft.org/documentation/display/current/Routing+Message+Processors#RoutingMessageProcessors-RequestReply Mockups here: http://corp.wiki.mulesource.com/display/WP/Request-Reply#Request-Reply-Mockups | 13 |
| 3 | STUDIO-280 | Cannot import a Studio project from Git without errors | Steps to reproduce: 1. Create a simple Mule Studio project (for instance: the Echo example) 2. Push it into GitHub, pull/clone the repository into your local instance 3. Open up a brand new workspace 4. Goto Import/Git/Projects from Git 5. Select the local copy of your GitHub repository 6. Select import existing projects 7. Select the project created above 8. The import fails due to missing directories (see screenshot) Note that if I do Import --> Mule project it works but then it doesn't recognise that it is a project managed by git so I cannot commit changes. This is blocking me for the work I am doing with examples. Edit: workaround: perform a Clean operation on the project. | 3 |
| 4 | STUDIO-382 | Changes to Java code do not get hot deployed | Java source changes don't get picked up right now automatically (see STUDIO-381) however, even if a redeploy is triggered the latest java changes are not deployed | 5 |
| 5 | STUDIO-459 | Unable to add a response when creating a second flow in the same mflow | Unable to add a response when creating a second flow. Steps to reproduce: 1) Open Studio and create a project from an existing template: Order Discounter. 2) In that same mflow file create another flow. Drag and drop HTTP RQ-RS, echo, flow reference, All router and component, echo and file, then file. 3) Try to add a response (echo component) like the one displayed for the template flow. Unable to add a response, instead of that it lets me add the component between HTTP and SOAP component. See screen shot. | 8 |
| 6 | STUDIO-618 | Namespaces in the XML view are not being removed when you remove all the elements of a kind | When you add an element and then you remove it, the reference to the schema file is not being removed from the XML namespaces. Steps to reproduce: 1.- Create a project in Studio with a flow in it and go to the Global Elements tab. 2.- Add for example a global Jetty endpoint with the default values. 3.- Go to the XML view and check that the xml code for the endpoint is there with reference to the mule-jetty.xsd in the namespaces 4.- Go back to the global elements tab and delete the endpoint. Issue: Now if you go back to the XML view, the code for the endpoint is not there as ti should but the reference to the mule-jetty.xsd is still there and it shouldn't as there is no jetty element in the flow or in the global elements tab. Be very careful when implementing this as the reference in the namespaces should be remve if there is no other instance of the element kind in a flow or as a global element such as a global endpoint or connector, but if there is no reference to an element kind (ex: some jetty element) there is no reason for the namespace to be there. | 8 |
| 7 | STUDIO-781 | Would save time to be given the option to create a class in addition to selecting an existing class inside a widget dialog box (e.g., Component) | Add a button in the ClassFieldEditor to create the class inline. | 5 |
| 8 | STUDIO-782 | View the class code just by clicking on the class name displayed in the widget dialog box | Currently, to view the class code (e.g., component) specified in the widget configuration, I have to leave the dialog box to find it. A very desirable feature would be to view the class code (as a separate tab in the editor ) just by clicking on the class name displayed in the widget dialog box. | 5 |
| 9 | STUDIO-837 | Reference to the subflow get lost when changing the subflow name (Exception Strategy) | Steps to reproduce: 1.- Create a project in STUDIO with a flow and a sub-flow 2.- Go to the Flow properties window and set the Exception Subflow ref combo to the subflow that you have. Clic OK. 3.- Change the name of the subflow. 4.- Open the flow properties window, the subflow ref is blank Expected behavior: the reference should be preserved no matters if the user decides to change the subflow name. | 8 |
| 10 | STUDIO-853 | Studio can be a lot smarter when handling logic expressions. I'd rather not see AND, OR, NOT filters in the palette | it seems we could have a single filter element in the flow control section that has one dialog that allows people to select an expression (this works for wildcard and regex) and have a section below to allow the user to add new filters with AND, OR or NOT. I think this provides much better usability as there is now only a single filter element not a whole palette. And it makes working with logic filters more natural for the user. i.e.it feels odd to have to start with an AND filter and then configure the expressions | 34 |
| 11 | STUDIO-1212 | Response section is not displayed | My config is as follows: <flow name="TicketFlowFlow1" doc:name="TicketFlowFlow1"> <composite-source> <http:inbound-endpoint exchange-pattern="request-response" host="localhost" port="8081" doc:name="HTTP"/> <vm:inbound-endpoint exchange-pattern="request-response" path="helloworld" responseTimeout="10000" mimeType="text/plain" doc:name="VM"/> </composite-source> <component class="com.mulesoft.Component1" doc:name="Java"/> <http:outbound-endpoint exchange-pattern="request-response" host="localhost" port="8081" doc:name="HTTP"/> <response> <component class="com.mulesoft.Component2" doc:name="Java"/> </response> </flow> But the response is not displayed (see the pic attached) | 5 |
| 12 | STUDIO-1311 | Able to drag and drop composite source and poll as response elements | I am able to drag and drop composite source and poll as response elements of a flow. This is not correct: we should not let the user be able to drop composite source and poll there. When dropping them as response elements an empty response box is created and in the XML configuration this is written: <response/> I am attaching a screen shot. | 3 |
| 13 | STUDIO-1333 | There is no specification when there is a global endpoint or a connector created in the global elements table, they are just called the same and it is confusing | This is a usability issue: There is no specification when there is a global endpoint or a connector created in the global elements table, they are just called the same and it is confusing. Steps to reproduce: 1. Create an FTP global endpoint. 2. Create an FTP connector. They have the same type and name in the global elements table (For the name there is already a Jira opened for that). Type should specify if it is a global endpoint or a connector. Nowadays I think that type is useless, it doesn't say anything to the user. It just says "FTP (EE)" for global endpoint or connector. Same happens for the rest of the global endpoints and connectors and this is pretty confusing!!! | 13 |
| 14 | STUDIO-1415 | Executing simple lookup table configuration is showing error message | Created a Java to XML mapping and configured a lookup table with 2 fields: subject(Key) and email. Executed the Preview an error message was displayed: "Message:Transform Failed!" (see attached screenshot) | 8 |
| 15 | STUDIO-1428 | Unable to create new mappings using new excel format xlsx | Unable to create a new mapping using an excel spreadsheet with the new format .xlsx To reproduce: - Create new mapping - Input: Select MS Excel - Add the .xlsx spreadsheet attached to this issue - Output: Select anything - Click Finish button (error is displayed in the error log) See attached screenshot of error. | 8 |
| 16 | STUDIO-1435 | Multiple xml validation errors in Studio editor | 1. Element JAX-WS Service is not allowed to be child element of HTTP. Oh, it is allowed, and often times it makes perfect sense to have it as a child element rather than subsequent one. False alarm. 2. Flow should start with inbound endpoint No, it does not have to. 3. Response is not allowed to be child of element HTTP Of course, it is allowed :) | 5 |
| 17 | STUDIO-1538 | Undo option (command + z / Ctrl + z ) does not work if you remove a global element | Steps to reproduce: 1.- Go to the global elements tab and create any element. 2.- Remove it. 3.- Press Ctrl + z or Command + z Issue: the element does not appears again | 8 |
| 18 | STUDIO-1676 | Suggest to stop the corresponding running mule instance when deleting a project | Steps to reproduce: 1 - Create a project 2 - Run it as a mule application 3 - Try to delete the project, including files. An error dialog will pop up, related to mule still using the files and directories that are being deleted. To complete his desire to delete the project, the user will have to abort the operation (undo won't undo anything at all), stop mule, and try again. Studio should prompt for the user's consent to stop the running mule instance if there is one running the applications of a project that is being deleted, so that the Delete operation does not fail, or otherwise gets cancelled. | 5 |
| 19 | STUDIO-1694 | Default of "Auto delete" in the File endpoint is hidden in a non-usable way | To see or edit the "Auto delete" option of the File connector you have to: - Go to the end point properties - The choose "Reference" - Add a reference in Global References->Connector Reference - The autodelete option is there (see the attached screenshot) | 8 |
| 20 | STUDIO-1738 | Add JAXB support | It would be nice if you could support jaxb operations from GUI such as jaxb-xml-to-object-transformer jaxb-context etc. | 2 |
| 21 | STUDIO-1759 | More easily navigate between XML and GUI | It should be much easier to navigate from the GUI to the appropriate XML element or flow block within the XML. Furthermore, it would be great to go the other way as well, to click on an XML element and bring the user directly to a highlighted flow element within the GUI. | 13 |
| 22 | STUDIO-1811 | Studio is not validating that certain scopes should start only with inbound or outbound endpoints | (edit) This bug was first discovered for exception strategies. This is the description for that case: When using the Message Flow tab, you can't drop inbound-only-endpoints into exception strategies (the UI forbids it). But you are able to do so through the XML, and there isn't any validation or indication that this is invalid. Example: {code:xml}<catch-exception-strategy> <imap:inbound-endpoint host="localhost" port="143" responseTimeout="10000" doc:name="IMAP"/> </catch-exception-strategy>{code} This is invalid (IMAP is inbound, and only inbound), but there are no error markers whatsoever present. It should: * be underlined in the XML * present a problem in the Problems pane * be drawn with the red-x in the Message Flow tab This is also valid for any other kind of scope that has the restriction to start only with inbound or outbound endpoints. Some sample snippets that should fail, but dont: {code:xml}<sub-flow name="asdfFlow4" doc:name="asdfFlow4"> <imap:inbound-endpoint host="localhost" port="143" responseTimeout="10000" doc:name="IMAP" /> </sub-flow>{code} {code:xml}<composite-source> <smtp:outbound-endpoint host="localhost" port="25" responseTimeout="10000" doc:name="SMTP" /> </composite-source>{code} {code:xml}<poll frequency="1000"> <imap:inbound-endpoint host="localhost" port="143" responseTimeout="10000" doc:name="IMAP" /> </poll>{code} | 5 |
| 23 | STUDIO-2000 | Error unzipping MuleStudio in Windows in a long path | When unzipping MuleStudio in a long path (For example under Desktop or Document and Settings) the errors shown in the attached screenshots may be shown. The password protected error seems to be a Windows bug as explained in http://blogs.msdn.com/b/robcaron/archive/2006/09/14/755306.aspx The problem is that this seems to be a Windows limitation and there is no much that can be changed in Studio to fix the issue (most of the failing files are eclipse classes) The workaround is to install Studio in a simpler and shorter directory (For example C:\MuleStudio) We need to add this in the release notes and see how to document it better for users. Some other stuff to test: # Does this happens with Winzip or Winrar (Or is only a problem of the default zip utility that comes with Windows) # Once extracted in C:\MuleStudio, can the directory me moved to another location? # Which specific versions of Windows present this issue? | 21 |
| 24 | STUDIO-2104 | Unable to drag a Twitter neither a Salesforce Streaming from the palette into the composite source | Unable to drag a Twitter neither a Salesforce Streaming from the palette into the composite source. Composite source can contain only message sources, therefore we should be able to drag and drop Salesforce and Twitter streaming into the composite source. | 2 |
| 25 | STUDIO-4050 | Studio cannot be pinned to the taskbar | Unlike other windows programs, Studio cannot be pinned to the taskbar for quick access. I am aware that this is a problem with Eclipse in general, but I wanted to make it clear it is an usability issue for our users. When I right-click on the taskbar icon of a running Studio, I only see one option: close window. | 8 |
| 26 | STUDIO-2779 | Studio Online Help Enhancements | 1) Adding new content created by Antonio/Doc-team for dynamic help. 2) Adjusting widget IDs to make sure that they are associated with dynamic help content. 3) Displaying the dynamic help tab by default in Studio upon first start. | 8 |
| 27 | STUDIO-2787 | Fixing MES Studio behavior for fields that use Collections | http://www.mulesoft.org/jira/browse/DEVKIT-240 | 8 |
| 28 | STUDIO-2781 | Studio Support for WebSockets | As defined by the specification. | 8 |
| 29 | STUDIO-2782 | Adding Reference to CH Analytic end-point on Studio Start | Whenever Studio starts, we should send a GET request to the following URL: http://<ch-app-hrl>/e?&_p=<studio-id>&_n=<example-name> Where <studio-id> is a unique ID associated with the downloaded Studio instance, and <example-name> is the name of the example. The CloudHub hosted service should in turn make a call to a KissMetrics event of the same name as the example using the following URL: http://trk.kissmetrics.com/e?_k=b276fa8e23213db7fba9868b5d3ba750344cdbb1&_p=123&_n=studiostartedevent The CloudHub service then effectively acts as a proxy between Studio and the KissMetrics event. In case that the CloudHub service is not available or that there is no connectivity to the CloudHub service from the machine on which the example is being executed, the URL call-out should fail gracefully with no noticeable effect from the Studio user's point of view. | 8 |
| 30 | STUDIO-2784 | Addition of DB2 and MS SQL Server to the list of databases on Studio JDBC connector configuration window - Studio 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. | 8 |
| 31 | STUDIO-2147 | Only queryKey is marked as mandatory for JDBC endpoint while Address is a valid attribute if queryKey is not specified | Only queryKey is marked as mandatory for JDBC endpoint while Address is a valid attribute if queryKey is not specified. A query should be referenced from the JDBC endpoint by queryKey or Address. Nowadays when you have specified the Address attribute and not the queryKey you get an error saying Please specify a query. | 2 |
| 32 | STUDIO-2154 | error adding context:property-place-holder | Since it's not possible to add a context:property-place-holder tag from the pallete, I switched to the editor view and used auto competion to generate this declaration: <context:property-placeholder location="mule.properties" /> Studio added the xmlns automatically, but the xsi:location looked like this: xsi:schemaLocation="http://www.springframework.org/schema/context null After fixing the location manually, the app started fine | 5 |
| 33 | STUDIO-2162 | cloudhub integration needs progress bar, cancel button and run in backgroun | when deploying an app in cloudhub, the actual file upload can take a while depending on the connection and the app size. During that time, there's no way of knowing if the app is still responsive and you can't do anything else. Also, if after pushing the button I just realized I forgot something I can't abort the proces. Lastly, it'd be nice to have the Run in backgroun option that many eclipse dialogs have. | 2 |
| 34 | STUDIO-2179 | Components and flow arrow inside response block should be displayed in the reverse order | A flow shows the request and response message flow inside a flow using arrows with different direction: request goes from left to right, response foes from right to left. That is not the case when there is a "response" component which is part of the response flow: the arrows inside the response go from left to right like in the request flow. I would expect the components inside the response element are displayed in reverse order so the arrow that shows the direction of the flow goes from right to left. | 34 |
| 35 | STUDIO-2235 | Direct-edit display name has a strange behavior under Windows | In Windows, when direct-editing the display name of an element in the canvas, the "editing box" has a couple of strange behaviors: * When writing the name from scratch (erase everything and start writing), the FIRST character shows, but upon typing the second character, the first one will not be visible (though it is still there). * When the display name is empty, the editing box shows from the middle expanding to the right (this is platform independent). It would be nicer if it showed centered on the element image. | 5 |
| 36 | STUDIO-2278 | DM field editor navigation | It should be really cool that when on the field editor or the data source editor when you hit the tab key you get to the other column or at lease the other row. Now a days it just focus on the OK button, so you have to move with the mouse to navigate the grid | 2 |
| 37 | STUDIO-2294 | Exception Strategy inside choice making trouble | When you try to insert a reference exception strategy inside a choice, nothing happens in the message flow view, but, on the backend, in the xml view, the exception strategy is being added. See both screenshots | 5 |
| 38 | STUDIO-2299 | When deleting a field, everything seem to be deleted due to collapse | When you are mapping fields, and realized that you have added one field that is not going to be used and delete it, all the map is automatically collapsed, giving the idea that everything was deleted. End user may not realized that it's just a collapse/expand issue. | 8 |
| 39 | STUDIO-2309 | When looking for JDBC in the Global Elements filter, nothing is shown | Go to the Global elements tab, clic on create and write JDBC in the filter. | 8 |
| 40 | STUDIO-2310 | Entity IDs are not being generated correctly | (Setting XMLGeneration as Component, but this does not really relate to the application XML generation -mule config- ) Entity IDs in the .mflow are being (again) generated as long random strings. Steps to reproduce: # Create a project/flow. # Drop an IMAP and a Logger. # Open the .mflow with a text editor. * You will see that the entity IDs are this long unrepresentative strings. Some additional information: Upon making any other modification on the flow, the entity-ids will be regenerated as expected (<comp.name>##). | 8 |
| 41 | STUDIO-2312 | Warning icon shown in GUI but not in XML | The UI shows that the SAP Transformer has a warning, but nothing is displayed in the error log or the XML view. See attached screenshot. Is the problem related to the SAP editor XML definition? | 8 |
| 42 | STUDIO-2315 | Bad maven project import in studio using studio:studio | I tried to import a project using studio:studio and I had a couple of issues when trying to generate and deployable archetype using export: 1 - Project does not included maven dependencies in lib folder 2 - Export complains if folders src/main/resources or src/test/java or src/test/resources does not exists. Attached you can find the project I was trying to import / export | 5 |
| 43 | STUDIO-2321 | Data Mapper DB Lookup Table, java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic is still active | Using the same Lookup Table multiple times in one mapping transformer led to exception during runtime. | 8 |
| 44 | STUDIO-2327 | Studio randomly crashes when multiple flows are re ordered and referencing one another. | Hi Our user is still seeing these crashing issues with Studio even after applying all of the updates. Here is what they've told me. They have a project with a main flow and multiple sub flows. They think part of the issue may be how Mule is updating the multiple flow files because They’ve gotten the error in a few scenarios (although they don’t have full replication steps yet): Steps that caused it this time: 1. The flow being referenced changes names, and the original name and new name both show up in the flow reference drop down. 2. I try to reference a second sub flow that is above the first sub flow (I have multiple sub flows in the file). Once I add in the flow reference for subflow1 to call subflow2 then I get the error. a. Note: when I moved subflow2 below subflow1, the issue corrected itself. Here’s the error they got: !ENTRY org.eclipse.ui 4 0 2012-09-20 08:31:27.045 !MESSAGE There has been an error in the application. Please report this incident to studio-feedback@mulesource.com Save Failed !STACK 0 java.lang.AssertionError at org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor$MergingContext$Merger.merge(MultiPageMessageFlowEditor.java:1456) at org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor.mergeElements(MultiPageMessageFlowEditor.java:1659) at org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor.formCommands(MultiPageMessageFlowEditor.java:1352) at org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor.fixUpSource(MultiPageMessageFlowEditor.java:796) at org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor.updateSourceFromFlow(MultiPageMessageFlowEditor.java:768) at org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor.doSave(MultiPageMessageFlowEditor.java:674) at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:151) at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:277) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:759) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:756) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2600) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:285) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:264) <SNIP> Thanks, Nicol | 8 |
| 45 | STUDIO-2367 | There are problems when you zoom out in a flow | Steps to reproduce: 1.- Create a project with a config file and several flows in it. 2.- Add some exception strategies also 3.- Zoom out by pressing Ctrl - or Command - Issue: you can see some elements drawn in the right side, check screenshot and video. https://www.dropbox.com/s/gbpqme7iggsk0hv/2012-09-27%2012.34.22.mp4 Also when doing drag and drop the feedback image has weird behaviour, there is a lot of distance between the mouse and the feedback image. | 8 |
| 46 | STUDIO-2368 | When doing drag and drop you are not able to scroll across the long canvas | Steps to reproduce: 1.- Create a config file with many flows in it. 2.- Try to scroll down when doing drag and drop Issue: you are stock and not able to scroll, take into account the use case when you zoom in and out. | 5 |
| 47 | STUDIO-2376 | Static Component in a poll is removed when generic endpoint connector is changed or removed in Message Flow | I tested it in the following way: 1. Created two global endpoints a. name = “GE1”, address = “stdio://out” b. name = “GE2”, address = “file:///tmp/test” 2. Created a new flow. 3. Added a polling component with a frequency of 10 seconds. a. Added a static-component with return-data = “Hello World”. 4. Added a generic outbound-endpoint with a reference to GE1. 5. Ran the project and verified everything works properly. In the Flow designer: 1. Double-clicked on the generic outbound-endpoint. 2. Added something to the documentation tab 3. Saved the flow. Expected : Flow changed with documentation and everything remains intact Actual: Flow changed with documentation and static-compontent disapears The customer followed these steps: 1. Created two global endpoints. a. name = “GlobalEndpoint1”, address = “stdio://out” b. name = “GlobalEndpoint2”, address = “file:///tmp/test” 2. Created a new flow. 3. Added a polling component with a frequency of 10 seconds. a. Added a static-component with return-data = “Hello World”. 4. Added a generic outbound-endpoint with a reference to GlobalEndpoint1. 5. Ran the project and verified everything works properly. In the Flow designer: 1. Double-clicked on the generic outbound-endpoint. 2. Changed the endpoint reference to GlobalEndpoint2. 3. Saved the flow. | 3 |
| 48 | STUDIO-2383 | JDBC EE namespace appended to almost everything | The JDBC EE namespace is being automatically appended to everything in my config file. Even if I delete those chunks of code, they will reappear. E.g.: {code} ... <jdbc-ee:connector name="SecureDB" dataSource-ref="secureJDBCDataSource" validateConnections="true" queryTimeout="-1" pollingFrequency="0" doc:name="Database"/> <context:property-placeholder xmlns:jdbc-ee="http://www.mulesoft.org/schema/mule/ee/jdbc" location="mule.${mule.env}.properties"/> <spring:beans> <spring:bean xmlns:jdbc-ee="http://www.mulesoft.org/schema/mule/ee/jdbc" id="sysprop" name="sysprop" class="org.mule.config.spring.util.SystemPropertyInitializingBean"> <spring:property name="systemProperties"> <spring:map> <spring:entry key="javax.net.ssl.trustStorePassword" value="MuleSoft1"/> <spring:entry key="javax.net.ssl.trustStore" value="${app.home}/truststore"/> </spring:map> </spring:property> </spring:bean> <spring:bean xmlns:jdbc-ee="http://www.mulesoft.org/schema/mule/ee/jdbc" id="secureJDBCDataSource" name="secureJDBCDataSource" class="org.enhydra.jdbc.standard.StandardDataSource" depends-on="sysprop" destroy-method="shutdown"> <spring:property name="driverName" value="${db.secure.driverClass}"/> <spring:property name="url" value="${db.secure.url}"/> <spring:property name="user" value="${db.secure.user}"/> <spring:property name="password" value="${db.secure.password}"/> </spring:bean> </spring:beans> <data-mapper:config xmlns:jdbc-ee="http://www.mulesoft.org/schema/mule/ee/jdbc" name="EBS_to_Avalara_Get_Tax_Request_Transformer" transformationGraphPath="ebs_to_avalara_get_tax_request_mapping.grf" doc:name="DataMapper"/> ... {code} | 1 |
| 49 | STUDIO-2418 | Losing the Undo option when moving from flow to the xml view and back to the xml view | When modifying something in the Flow view and moving to the XML view and then back to the Flow view, the Undo option is no longer available. This is an usability issue. | 34 |
| 50 | STUDIO-2428 | Mule config file from src/test/resources get copied in src/main/app | If you create a functional test case that uses an xml config contained in the folder src/test/resources, as soon as you open it, an mflow will be generated, the correspondent config xml will be added to the src/main/app and it will be added to the mule-deploy.properties file. | 2 |
| 51 | STUDIO-2438 | XSDs with namespaces and XML without namespaces issue | When the XSD has namespaces and the received XML doesn't, DataMapper doesn't do the mappings correctly. | 8 |
| 52 | STUDIO-2445 | DB lookup fields displayed in the Mappings view does not have the correct field names | When creating a DB lookup table in data mapper and entering the fields we want to extract from the database (name, surname, etc) when going back to the Mapping View, the field are displayed with default names like field1, field2, field2, etc. See attached screenshot and .grf | 8 |
| 53 | STUDIO-2450 | DataMapper Encrypting database lookup password over and over again | When configuring a database lookup in a datamapper component and encrypting the password, each time the user clicks the Finish button from the configuration, the user is requested for the encryption password and the password is re-encrypted over and over again. | 8 |
| 54 | STUDIO-2456 | properties-ref in context:property-placeholder is not allowed and silently removed | properties-ref attribute in context:property-placeholder is not allowed and Mule Studio silently removes it when saving in graphical view, replacing it with an empty location attribute. | 8 |
| 55 | STUDIO-2461 | In the SOAP dialog box, when operation is set to JAX-WS client, no browse button exists for setting the client class | In the SOAP dialog box, when operation is set to JAX-WS client, no browse button exists for setting the client class. | 5 |
| 56 | STUDIO-2481 | Salesforce connector losing Global Element Properties information | The Salesforce connector y losing information from its global element properties (URL and proxy port) when going back from the XML view to the message flow. To reproduce: - Create new project - Add the salesforce connector to the project - Double click the Saleforce connector - In Generic / Config Reference click the Add button (green cross) - Click the Salesforce connector and click OK - Close the connector and go to the XML view - Now go back to the message flow view - Double click the connector to edit properties - Click the edit button in the Config Reference used - URL and Proxy Port and no longer displayed by default (see attached screenshot) | 1 |
| 57 | STUDIO-2482 | Choice Router cannot edit routes in Win32XP | The Choice router has un-editable fields for the expressions. Can workaround by going to XML, but we still need to support this browser. A lot of big companies are scared of new technology. | 1 |
| 58 | STUDIO-2484 | DataMapper: Exception raised when trying to map the MuleMessage Interface | Steps to reproduce: 1.- Create a flow with a DataMapper and open the wizard. 2.- When configuring the wizards select to map a Pojo 3.- Select Java Object and search for the class MuleMessage Interface 4.- Clic OK Issue: the followed exception is raised. {code} java.lang.reflect.InvocationTargetException org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421) org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) com.mulesoft.mule.datamapper.ui.wizard.SchemaGeneratorDialog.generateSchema(SchemaGeneratorDialog.java:31) com.mulesoft.mule.datamapper.ui.wizard.BeanIntrospectorDialog.okPressed(BeanIntrospectorDialog.java:138) org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472) org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:3783) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1398) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1383) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1195) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3629) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3284) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) com.mulesoft.mule.datamapper.ui.wizard.BeanMetadataPropertiesPanel$1.widgetSelected(BeanMetadataPropertiesPanel.java:108) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:3783) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1398) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1383) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1195) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3629) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3284) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) com.mulesoft.mule.datamapper.ui.view.DataMapperView.launchDMWizard(DataMapperView.java:568) com.mulesoft.mule.datamapper.ui.view.DataMapperEditPartRequestHandler.handleReadAccessRequest(DataMapperEditPartRequestHandler.java:71) org.mule.tooling.messageflow.editpart.RequestHandlerManager.handleReadAccessRequest(RequestHandlerManager.java:50) org.mule.tooling.messageflow.editpart.EntityEditPart.performRequest(EntityEditPart.java:145) org.eclipse.gef.tools.SelectEditPartTracker.performOpen(SelectEditPartTracker.java:194) org.eclipse.gef.tools.SelectEditPartTracker.handleDoubleClick(SelectEditPartTracker.java:137) org.eclipse.gef.tools.AbstractTool.mouseDoubleClick(AbstractTool.java:1069) org.eclipse.gef.tools.SelectionTool.mouseDoubleClick(SelectionTool.java:525) org.eclipse.gef.EditDomain.mouseDoubleClick(EditDomain.java:231) org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseDoubleClicked(DomainEventDispatcher.java:291) org.eclipse.draw2d.LightweightSystem$EventHandler.mouseDoubleClick(LightweightSystem.java:518) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:189) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:3783) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1398) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1383) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1195) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3629) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3284) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) org.eclipse.equinox.launcher.Main.run(Main.java:1408) Caused by: java.lang.ExceptionInInitializerError java.lang.Class.forName0(Native Method) java.lang.Class.forName(Class.java:247) com.opensys.cloveretl.component.tree.bean.schema.generator.SchemaGenerator.h(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.generator.SchemaGenerator.f(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.generator.SchemaGenerator.b(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.generator.SchemaGenerator$Visitor.visit(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.model.TypedObject.acceptVisitor(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.generator.SchemaGenerator$Visitor.visit(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.model.TypedObjectRef.acceptVisitor(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.model.TypedObject.acceptVisitor(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.generator.SchemaGenerator$Visitor.visit(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.model.TypedObjectRef.acceptVisitor(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.model.TypedObject.acceptVisitor(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.generator.SchemaGenerator$Visitor.visit(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.model.TypedObjectRef.acceptVisitor(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.generator.SchemaGenerator.generateObjectSchema(Unknown Source) com.opensys.cloveretl.component.tree.bean.schema.generator.SchemaGenerator.generateSchema(Unknown Source) com.mulesoft.mule.datamapper.ui.wizard.BeanIntrospectorEditor.generateSchema(BeanIntrospectorEditor.java:181) com.mulesoft.mule.datamapper.ui.wizard.BeanIntrospectorDialog$2.generateSchema(BeanIntrospectorDialog.java:141) com.mulesoft.mule.datamapper.ui.wizard.SchemaGeneratorDialog$GenerateSchema.run(SchemaGeneratorDialog.java:52) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: org.mule.api.MuleRuntimeException: Couldn't find config via SPI mechanism. Corrupted Mule core jar? org.mule.config.pool.ThreadPoolFactory.newInstance(ThreadPoolFactory.java:57) org.mule.config.ImmutableThreadingProfile.<init>(ImmutableThreadingProfile.java:36) org.mule.api.config.ThreadingProfile.<clinit>(ThreadingProfile.java:120) ... 21 more {code} | 8 |
| 59 | STUDIO-2487 | Studio doesn't support complex type nor lists | These are actually 5 bugs in one, so brace yourself... errors are coming... First, install this cloud connector https://github.com/mulesoft/google-connectors-suite/tree/master/gmail-connector 1) First of all, all the List attributes get the same label description "String". 2) If i leave some of them empty, each time Studio regenerates the code, the empty ones get a default #[payload] value 3) The UI is very very slow 4) Complex types that are not complex cannot be defined in the UI. I only get the option to reference them 5) Autocompletion doesn't work either for the complex types that are not lists. | 1 |
| 60 | STUDIO-2492 | Multiple Runtimes: Unknown node definition when using EE components on a project created with a CE Runtime | Precondition: you should have a Mule Studio workspace where you have installed a CE Mule Server. Steps to reproduce: # Create a project using the CE server. # Switch the project runtime to a EE server. # Try to use any EE-only component (Business Events, JDBC, FTP, Cache) * Nothing will happen visually, the component is not added. An exception is logged in the Error Log (see below) {code}java.lang.RuntimeException: Unknown node definition: http://www.mulesoft.org/schema/mule/ee/tracking/custom-event at org.mule.tooling.core.module.MuleModuleManager.getDefinition(MuleModuleManager.java:638) at org.mule.tooling.messageflow.editpart.CompartmentLaneEditPart.buildResponseModel(CompartmentLaneEditPart.java:289) at org.mule.tooling.messageflow.editpart.CompartmentLaneEditPart.buildDisplayModel(CompartmentLaneEditPart.java:180) at org.mule.tooling.messageflow.editpart.CompartmentLaneEditPart.getModelChildren(CompartmentLaneEditPart.java:146) at org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:754) at org.mule.tooling.messageflow.editpart.CompartmentLaneEditPart.refreshChildren(CompartmentLaneEditPart.java:158) at org.mule.tooling.messageflow.editpart.CompartmentLaneEditPart.update(CompartmentLaneEditPart.java:110) at java.util.Observable.notifyObservers(Observable.java:142) at org.mule.tooling.model.messageflow.decorator.EntityDecorator.fireEvent(EntityDecorator.java:69) at org.mule.tooling.model.messageflow.decorator.CompartmentLaneDecorator.addEntityBefore(CompartmentLaneDecorator.java:131) at org.mule.tooling.messageflow.command.NodeCreateCommand.addCreatedNode(NodeCreateCommand.java:51) at org.mule.tooling.messageflow.command.PatternCreateCommand.execute(PatternCreateCommand.java:81) at org.eclipse.gef.commands.CommandStack.execute(CommandStack.java:197) at org.eclipse.gef.tools.AbstractTool.executeCommand(AbstractTool.java:425) at org.eclipse.gef.tools.AbstractTool.executeCurrentCommand(AbstractTool.java:438) at org.eclipse.gef.tools.CreationTool.performCreation(CreationTool.java:266) at org.eclipse.gef.tools.CreationTool.handleButtonUp(CreationTool.java:186) at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1201) at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301) at org.mule.tooling.messageflow.editor.MessageFlowEditor$4.mouseUp(MessageFlowEditor.java:601) at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380) at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:213) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3783) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1398) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1383) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1195) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3629) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3284) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575) at org.eclipse.equinox.launcher.Main.run(Main.java:1408){code} | 1 |
| 61 | STUDIO-2535 | Whenever the project has a change, Connections Explorer should warn the user to save the project changes before executing test connection | Whenever the project has a change, Connections Explorer should warn the user to save the project changes before executing test connection. | 3 |
| 62 | STUDIO-2586 | DataMapper: Exception generated when using an invalid JSON file | Steps to reproduce: 1.- Create a JSON to XML mapping 2.- Use a base JSON file with a bad structure 3.- Generate defaults for the XML Issue: this exception is thrown in the error log {code} java.lang.RuntimeException: java.lang.RuntimeException: Provided JSON file contains syntax errors: Expected EOF at line 2 column 1 com.mulesoft.mule.datamapper.ui.wizard.JSONMetadataPropertiesPanel$FromExampleMetadataGenerator.generateMetadata(JSONMetadataPropertiesPanel.java:180) com.mulesoft.mule.datamapper.ui.wizard.BaseMetadataPropertiesPanel.generateMetadata(BaseMetadataPropertiesPanel.java:231) com.mulesoft.mule.datamapper.ui.wizard.InputOutputSelectionPage$14.widgetSelected(InputOutputSelectionPage.java:516) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1531) org.eclipse.swt.widgets.Link.textView_clickOnLink_atIndex(Link.java:117) org.eclipse.swt.widgets.Display.windowProc(Display.java:5807) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1093) org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1085) org.eclipse.swt.widgets.Control.mouseDown(Control.java:2538) org.eclipse.swt.widgets.Display.windowProc(Display.java:5493) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2102) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2299) org.eclipse.swt.widgets.Display.windowProc(Display.java:5557) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5002) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5151) 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:3616) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) com.mulesoft.mule.datamapper.ui.view.DataMapperView.launchDMWizard(DataMapperView.java:568) com.mulesoft.mule.datamapper.ui.view.DataMapperView$5.launchNewDataMapperFlow(DataMapperView.java:228) com.mulesoft.mule.datamapper.ui.editor.DataMapperEditor$3.handleEvent(DataMapperEditor.java:218) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1531) org.eclipse.swt.widgets.Link.textView_clickOnLink_atIndex(Link.java:117) org.eclipse.swt.widgets.Display.windowProc(Display.java:5807) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1093) org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1085) org.eclipse.swt.widgets.Control.mouseDown(Control.java:2538) org.eclipse.swt.widgets.Display.windowProc(Display.java:5493) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2102) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2299) org.eclipse.swt.widgets.Display.windowProc(Display.java:5557) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5002) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5151) 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:3616) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) org.eclipse.equinox.launcher.Main.run(Main.java:1438) Caused by: java.lang.RuntimeException: Provided JSON file contains syntax errors: Expected EOF at line 2 column 1 com.mulesoft.mule.datamapper.ui.editor.metadata.service.impl.JsonSchemaGenerator.createSchema(JsonSchemaGenerator.java:63) com.mulesoft.mule.datamapper.ui.wizard.JSONMetadataPropertiesPanel$FromExampleMetadataGenerator.generateMetadata(JSONMetadataPropertiesPanel.java:162) ... 76 more Caused by: com.google.gson.JsonSyntaxException: com.google.gson.stream.MalformedJsonException: Expected EOF at line 2 column 1 com.google.gson.JsonParser.parse(JsonParser.java:65) com.mulesoft.mule.datamapper.ui.editor.metadata.service.impl.JsonSchemaGenerator.createSchema(JsonSchemaGenerator.java:57) ... 77 more Caused by: com.google.gson.stream.MalformedJsonException: Expected EOF at line 2 column 1 com.google.gson.stream.JsonReader.syntaxError(JsonReader.java:1298) com.google.gson.stream.JsonReader.peek(JsonReader.java:390) com.google.gson.JsonParser.parse(JsonParser.java:60) ... 78 more {code} | 8 |
| 63 | STUDIO-2603 | Add Processor Chain to the palette | If when using a 'choice' you use a filter inside a 'when' condition, if the filter is not inside a 'processor chain' them the ESB will fail when deploying the app. The processor chain is already supported from the XML we only need to add it to the palette and add the description to the configuration window. | 8 |
| 64 | STUDIO-2604 | Reference Exception strategy should be able to be dropped inside a choice exception strategy | I should be able to drop a 'Reference Exception Strategy' inside a 'Choice Exception Strategy' | 5 |
| 65 | STUDIO-2618 | When using connectivity test feature, libraries should be automatically loaded to the project | When using connectivity test feature, needed connectors libraries should be automatically added to the project path instead of showing an error. Same for metadata. | 8 |
| 66 | STUDIO-2625 | Transactional: is not being displayed when using the CE runtime | The transactional component has 3 options. - Simple Transaction - XA Transaction - Multi Transaction When the runtime used is CE, only the Simple transaction option should be displayed and the icon should be the common green. When the runtime is EE, the 3 options should be displayed and the icon should be light green. | 5 |
| 67 | STUDIO-2628 | Transactional endpoints are missing the NOT_SUPPORTED action | As part of the implementation of the new transactional element we need to add an action to the transactional endpoints. When configuring a transaction in the followed endpoints: JMS, JDBC and VM. An action called "Not Supported" should be displayed in the drop down list. When this action is selected the followed attribute should be added to the XML: action="NOT_SUPPORTED". | 3 |
| 68 | STUDIO-2636 | Documentation generation doesn't work when Flow name contains strange characters | For example if the flow name is: "Flow That Does This (and also this)" the generated doc links are not working. Even if there was a component in that flow that has documentation, it is not displayed anywhere. | 5 |
| 69 | STUDIO-2638 | No universal way to make comments across GUI and XML | This jira is a bit unusual.. The problem I find is that because I am limited on the comments I can make on the studio canvas on message processors (name:doc) I end up also writing comments in the xml, this spreading out of comments to describe what the application is doing can be confusing.. I believe we need to come up with a strategy and common way of making comments, this could potentially be addressed by : http://www.mulesoft.org/jira/browse/STUDIO-2550 What I like about making notes in the xml is that I can view all the notes without having to click into components or hovering my mouse over them in the GUI.... I would probably use the description attribute to give detailed description of what the message processor does and then I would like to sometimes be able to put a 1/2 line brief description of what it does somewhere on the canvas. because doc:name attribute does not do text wrap and descriptions over a few words make the canvas look messy and forces message processors to spread out this is not a good way of labelling.. Sorry for this Jira. | 34 |
| 70 | STUDIO-2639 | Export to DOCs brings an NPE if you clic when no project is opened | Steps to reproduce: 1.- Open Studio in a new workspace 2.- Close the welcome screen and then clic in the export to DOC button issue: the followed NPE appears in the error log: {code} java.lang.NullPointerException org.mule.tooling.studoc.dialogs.MuleDocumentationExportDialog.open(MuleDocumentationExportDialog.java:234) org.mule.tooling.studoc.handlers.ExportStudioDocumentationHandler.execute(ExportStudioDocumentationHandler.java:71) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829) org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815) org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3980) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3619) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) org.eclipse.equinox.launcher.Main.run(Main.java:1438) {code} | 1 |
| 71 | STUDIO-2643 | Studio deployer needs to support classloader override | We're trying to use Studio for a project that uses a cloud connector with a dependency to jettison that requires classloading override as described in this page: http://www.mulesoft.org/documentation/display/MULE3USER/Classloader+Control+in+Mule So, I edited the mule-deploy.properties file and added this: loader.override=org.codehaus.jettison,org.springframework.batch,com.thoughtworks.xstream This is ignored by the current deployer. I built the app using maven and deployed it manually on Mule. The Mule deployer did pay attention to the flag and the application deployed fine. We need support for this on Studio ASAP or we'll be forced to tell a client to stop using it. | 5 |
| 72 | STUDIO-2655 | Lossing enpoint reference to a global endpoint across different flow files | How to re-crecreate: (1) Create global endpoints (i.e. file:endpoint)in a dedicated flow file to store all global components. (2) Then reference the global endpoints across from separate flow files. (3) Complete the flow and test it to make sure it is working. (4) Using the graphical editor(Message Flow tab) to edit the Display Name of each node. At this point all the references will be removed, the flow will be broken. The explanation: We are trying to introduce the test driven development using the FunctionalTest. For this, we need to put all the endpoints together with their connectors to a separate dedicated flow file. Then in the src/test/resources, we create a test flow file that contains the corresponding endpoints (with the same name) that will replace the real endpoints in the functional test. However, the MuleStudio fail to recognise the global endpoints ferenced from across the separate flow file. Even worse, it keeps removing them while it is perfectlu legal in terms of mule. Suggestion of fix: option 1: Able to recognise the global endpoints across different flow files Option 2: Just ignore the attributes and values it does not understand and put a warning sign instead of removing them. This may be preferable since MuleStudio may not understand all the added feature of the Mule components... For example, MessagePropertiesTransformer has the scope attribute, this will be removed by the MuleStudio because it does not understand it. Also it will be nice not to try to create mflow files for the files in src/test/resources, so that it will not complain about the uniqueue reference etc.... I know this should be another JIRA ticket :) | 5 |
| 73 | STUDIO-2662 | Resize DM new input argument dialog so the expression field is visible | <ditto> | 3 |
| 74 | STUDIO-2666 | Validation error when refering to a global EJB | When defining a global EJB like this: {code:xml} <spring:beans> <jee:remote-slsb id="testServiceBean" jndi-name="ejb:/ejbToCall-0.0.1-SNAPSHOT//TestService!com.acxiom.commonsoap.ejbtocall.TestServiceRemote" business-interface="com.acxiom.commonsoap.ejbtocall.TestServiceRemote"> <jee:environment>java.naming.factory.url.pkgs = org.jboss.ejb.client.naming</jee:environment> </jee:remote-slsb> </spring:beans> {code} And referencing it from a component, like the following: {code:xml} <component doc:name="Java"> <spring-object bean="testServiceBean" /> </component> {code} Studio marks the bean attribute of the spring-object element as an error, saying: Reference to unknown global element:testServiceBean However this configuration is valid, and the application runs without problems. | 8 |
| 75 | STUDIO-2671 | Studio 3.4 refers to Mule 3.2 schemas in the XML catalog | See the attached screen shot to grok the issue. | 5 |
| 76 | STUDIO-2672 | Automatically add schemas to the XML catalog for referenced libraries | One can add Mule modules to the Referenced Libraries either manually or with Maven. Not all these modules are DevKit built. It would be great if Studio could scan the JARs, recognize the Mule modules and add entries to the XML catalog (for both versioned and current schema locations). That would enable XML code completion for anything users could add to their project, giving them a good user experience for the case the added module doesn't have support for the visual flow editor. | 21 |
| 77 | STUDIO-2673 | Contribution sources points to non existent jar | Here's a sample plugin.xml <?xml version="1.0" encoding="UTF-8" standalone="no"?><plugin><extension point="org.mule.tooling.core.contribution"><externalContribution contributionJar="mule-module-servicesource-1.0-SNAPSHOT.jar" contributionJavaDocs="mule-module-servicesource-1.0-SNAPSHOT-javadoc.jar" contributionLibPathInMule="/plugins" contributionLibs="mule-module-servicesource-1.0-SNAPSHOT.zip" contributionNamespace="http://www.mulesoft.org/schema/mule/servicesource" contributionNamespaceFile="http://www.mulesoft.org/schema/mule/servicesource/1.0/mule-servicesource.xsd" contributionNamespacePrefix="servicesource" contributionSources="mule-module-servicesource-1.0-SNAPSHOT-src.jar" contributionType="cloud-connector" contributionVersion="1.0-SNAPSHOT" minimumVersion="3.2" name="ServiceSource" path="editors.xml" version="1.0"/></extension></plugin> mule-module-servicesource-1.0-SNAPSHOT-src.jar which doesn't exist between devkit's generated update site. Either devkit has a bug or studio is taking the sources from the wrong place | 5 |
| 78 | STUDIO-2678 | Create error when XML is invalid | When saving an invalid configuration XML, an error message pops up that explains what the error is and at what line number it is located. This error isn't reported in the Eclipse Problems view nor it is marked by red marker in the XML editor. It would help if those could be done. | 8 |
| 79 | STUDIO-2680 | Consider enabling search for task tags by default | By default, task tags is not enabled in General>Editors>Structured Test Editors>Task Tags. Activating it by default would provide task tags support in XML configuration files. | 3 |
| 80 | STUDIO-2682 | XML matching tag highlighting does not work | Even though "Matching Tag" is enabled in General>Editor>Text Editors>Annotation, the matching tag (for ex. </flow> when positioned on <flow>) doesn't get highlighted. | 5 |
| 81 | STUDIO-2685 | ALL mflows are deleted when modifying the buildpath | Take any project, go to the build path options and make whatever modification, such as adding items to the classpath. After you click ok, the .classpath file is rewriten and all mflows are deleted from the filesystem. You can actually see the delete operation if you go git status. I've verified this in both Studio 3.3.2 and 3.3.4.M3 | 8 |
| 82 | STUDIO-2686 | <set-variable> and <flow-ref> should have their doc:name attributes default to more relevant values | Right now by default when you add tags such as <set-variable> or <flow-ref> their doc:name attributes default to things like Variable or Flow Reference. Unless the user provides something specific, they should default to something more representative of the processor. For example, in case of the * in case of the flow-ref, it should have the name of the flow you're referencing * in case of set-variable or set-property, it could be something like <<name:expression> * In case of the foreach it could have the collection expression And so forth... This should work if i'm creating the processor using the visual view but also if i'm just coding like a champ on the xml view. | 8 |
| 83 | STUDIO-2693 | Error database connector name needs to be unique | Studio complaining with both database connectors and database source that the name needs to be unique when there is only one connector, so it is unique. This may be happening with other endpoints but I have only seen it with Database elements. | 5 |
| 84 | STUDIO-2694 | Classes from included java build path projects not available at runtime | Step to reproduce: * Download the attached projects and import them into studio * Edit the build path of the mule project and add the test-dependency project as a required project * Run the flow This will trigger the exception: Caused by: java.lang.ClassNotFoundException: com.mulesoft.support.Sarasa The same usecase works in studio 1.3.1 | 13 |
| 85 | STUDIO-2700 | Datamapper dependencies are not added to the studio generated pom | When trying to run tests with maven using the studio generated pom file I run into the following issues: Invalid content was found starting with element 'data-mapper:config' Then I add this: <dependency> <groupId>com.mulesoft.muleesb.modules</groupId> <artifactId>mule-module-data-mapper</artifactId> <version>${mule.version}</version> <scope>provided</scope> </dependency> And run into this: Error creating bean with name '(inner bean)': Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/mule/module/reboot/EEMuleContainerBootstrap (org.mule.api.lifecycle.InitialisationException) | 5 |
| 86 | STUDIO-2706 | Object builder should work with static meta-data | - As a Studio user, I would like to be able to use the Object Builder with Static meta-data | 13 |
| 87 | STUDIO-2716 | Mule Debugger and Java Debugger collide | When debugging a mule flow ctrl+shift+i opens up a mule evaluation window that allows you to test mule expression. This is all fine. However, when debugging a java transformer, the same shortcut should open the java evaluation window as in regular eclipse. What happens is that the mule debugger inspection tool opens instead. Studio should intercept all debugger related shortcuts and route them to the java/mule debugger accordingly depending on the context | 3 |
| 88 | STUDIO-2718 | flow ref editor should be alpha sorted and allow filtering | When editing a flow ref, the select box that list the available flows is not alpha sorted. A filter textbox above it would also be extremely helpful | 3 |
| 89 | STUDIO-2720 | Support for referencing external resources | I've imported a project build with Maven into Studio. The project includes (in the project pom, as one of it's dependencies) a module with some particular flows and other resources such as spring beans or connectors. In the project's pom: <dependency> <groupId>org.mule.modules.MODULE-NAME</groupId> <artifactId>MODULE-ARTEFACT</artifactId> <version>MODULE-VERSION</version> </dependency> Inside the module (some examples): . . . <flow name="NotificationOfError"> <-- Some process here --> </flow> . . . <https:connector name="httpsConnector"> <https:tls-key-store path="keystore" keyPassword="${keystore.password}" storePassword="${keystore.password}" /> </https:connector> . . . <spring:bean id="jdbcDataSource" class="org.enhydra.jdbc.standard.StandardDataSource" destroy-method="shutdown"> <spring:property name="driverName" value="${db.driver}" /> <spring:property name="url" value="${db.url}" /> <spring:property name="user" value="${db.user}" /> <spring:property name="password" value="${db.password}" /> </spring:bean> . . . Once imported the project to Studio, although the module's jar has been referenced into the Referenced Libraries, the resources are not been validated when trying to acces them inside the project. | 13 |
| 90 | STUDIO-2721 | When publishing to application repository, application name accepts characters which are not allowed by MMC and action fails | How to reproduce: *) Build an application which includes a flow that contains a space in its name (eg. Spell Checker from http://www.mulesoft.org/documentation/display/MULE3START/Basic+Studio+Tutorial) *) Publish to Application Repository from Studio interface, notice that the suggested Application name contains a space (make sure it does to reproduce this issue) Expected behavior: Application is deployed Current behavior: A message reading 'Could not deploy to domain. HTTP/1.1 400 Bad Request' is displayed, with no further explanation on how to correct the problem Note: you can see which characters are disallowed if you manually try to add an application to the repository from the MMC console (currently they appear to be \/*"?<>|+'- space and some others, please check with current version) Suggested change: validate from the UI that the name given to the application abides by the restrictions, and suggest a different name (maybe with the same rules used to determine the project name, so it would be spell_checker instead of Spell Checker for the Basic Tutorial example) | 2 |
| 91 | STUDIO-2733 | Cloud Connectors are missing from plugin | These cloud connectors are missing from the plugin: twitter twilio sfdc mongo magento cmis The result is I get an exception along the lines of: org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://www.mulesoft.org/schema/mule/sfdc/current/mule-sfdc.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. | 5 |
| 92 | STUDIO-2737 | Setting the serviceClass attribute in a SOAP message processor (JAX-WS Service) produces garbage text | Setting the SOAP service class attribute through the Mule Studio interface produces garbage data: <cxf:jaxws-service serviceClass="interface HelloInterface [in [Working copy] HelloInterface.java [in mulestudio.test [in src/main/java [in soap-interface-bug]]]] String sayHello(String)" doc:name="SOAP"/> To reproduce: 1) Drag and drop a SOAP message processor 2) Make sure that "Operation" is set to "JAX-WS service". 3) Attempt to set a service class | 5 |
| 93 | STUDIO-2742 | Endpoint exchange-pattern is automatically set to one-way after explicity stating it should be request-response | Endpoint exchange patterns are set to "one-way" when adding a new endpoint to an existing flow or changing the properties of other scopes, endpoints or message processors. To reproduce: 1) Create a new flow 2) Add any endpoint which defaults to one-way (such as VM or JMS) 3) Set this endpoint's exchange pattern to "request-response". 4) Close the project 5) Re-open the project and the XML file. 6) Add an endpoint after the one mentioned in Step 2. 7) Save. 8) The endpoint mentioned in Step 2 should now have it's exchange-pattern changed to "one-way". | 8 |
| 94 | STUDIO-2748 | In New Project wizard, New Mule Flow dialog doesn't replace whitespaces in the project name with underscores for the flow filename | Steps to reproduce: 1. Goto File -> New -> Other 2. Select Mule Project and click on "Next >" 3. Type in the name field "Ajax Spell Checker" and click on "Next >" The New Mule Flow dialog has the File name field set to the project name but it doesn't replace the whitespaces with underscores. | 3 |
| 95 | STUDIO-2751 | Cannot use transaction ee:xa-transactional or ee:multi-transactional from a test case | Getting the following error in the console when trying to run a test case that uses ee:xa-transactional or ee:multi-transactional: ERROR 2013-02-13 13:24:53,863 [Thread-1] com.mulesource.licm.impl.TrueLicenseHelper: Couldn't validate license key! | 8 |
| 96 | STUDIO-2753 | ALL processor ignores news processors in certain situations | Steps to reproduce: 1. Drag the ALL processor to a flow in the drawing area 2. Add a processor to the ALL 3. Add a processor to the ALL in a seperate path 4. Goto the Configuration XML tab 5. Goto the Message Flow tab 6. Add another processor to the first path 7. Switch to the Configuration XML tab The processor in step 6 isn't shown in the XML. Switching back to the Message Flow tab doesn't show the processor neither, that is, the change in step 6 is lost. Note that if I save instead of doing step 7, I get an error dialog telling me that Studio failed to save. | 8 |
| 97 | STUDIO-2756 | Export can't handle jar files when not in workspace | I have a project that has a jar file in a lib directory (more precisely, the mysql driver). The project is located in /Users/marianogonzalez/Documents/source/myproject. If I try to export the project to mule or upload it to cloudhub, I get an error saying that it can't find /Users/marianogonzalez/MuleStudio/workspace/myproject/lib/mysql.jar | 5 |
| 98 | STUDIO-2757 | Run history | When in your workspace you have more that one project you use to run several of them. As a result you start getting a history in the run/debug button of the IDE with the last app run. In eclipse when you close a project the apps related to that project get deleted from the button history so as not to confuse the user. In Studio even though you close the project the run history doesn't get clean. | 3 |
| 99 | STUDIO-2774 | Should not display confirmation dialogue upon successful retrieval of meta-data. | Once meta-data is successfully retrieved, we should not display a success dialogue. Dialogue should only be shown on failure. | 1 |
| 100 | STUDIO-2773 | ObjectBuilder usability improvements | - Values left as empty in the object builder should not show-up in the XML. - Object builder reference column usability. - We can't get rid of the reference column all-together. - Object builder structure should look like DM (and reuse DM UI if possible) | 13 |
| 101 | STUDIO-2772 | DataMapper should not show meta-data objects as KV pairs, but as an Object | When a data structure contains XMLGregorianCalendar, its type representation should not require the explicit definition of a factory in Studio (this should happen automatically). Furthermore, XMLGregorianCalendar should be automatically mappable to Date in DM. | 5 |
| 102 | STUDIO-2783 | XMLGregorianCalendar should be automatically mappable and Date->XMLGregorialCalendar mappings should be possible with simple mapping. | When a data structure contains XMLGregorianCalendar, its type representation should not require the explicit definition of a factory in Studio (this should happen automatically). Furthermore, XMLGregorianCalendar should be automatically mappable to Date in DM. | 13 |
| 103 | STUDIO-2833 | Remove archived examples from Studio | * 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. | 2 |
| 104 | STUDIO-2777 | Remove examples marked as Archive from Studio | * 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. | 2 |
| 105 | STUDIO-2841 | Place all examples in GIT | * 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. | 3 |
| 106 | STUDIO-2760 | Updating the set of connectors available in the connections explorer | The list of connectors shown in the Connections Explorer view is incomplete. The following is a list of connectors which cannot be chosen by the user when they try to add a new connector by clicking the "plus" sign in the Connections Explorer. - Ajax - File - HTTP Polling - HTTP\HTTPS - Jetty - Quartz - RMI - SAP - SSL (TLS) - Servlet - TCP Polling - UDP - VM - WMQ Connector - Active MQ - Mule MQ In addition, the list of cloud connectors is empty. | 5 |
| 107 | STUDIO-2763 | Dragging and dropping a Rollback Exception Strategy into a flow messes up the Message Flow canvas | Dragging and dropping a rollback exception strategy moves the text but not the whole widget. Steps to reproduce: 1) Create a flow scope 2) Create a global rollback exception strategy 3) Click on the text inside the exception strategy and drag it inside the flow. BUG: The text moves but the exception strategy remains global. | 5 |
| 108 | STUDIO-2775 | Studio Phase I support for APIkit | REST module spec is: http://corp.wiki.mulesource.com/display/WP/Simplified+REST+Service+Creation Studio L&F should be as per the attached mockups. | 13 |
| 109 | STUDIO-2795 | A Rollback Exception Strategy on a flow prevents the generation of documentation for that flow | A Rollback Exception Strategy on a flow prevents the generation of documentation for that flow | 5 |
| 110 | STUDIO-2812 | Global endpoint and connector descriptions of certain transports are identical. | The descriptions of a global endpoint and a connector found in the properties page of certain transports are the same. As an example, the description of a POP3 connector is as follows: "The POP3 Endpoint allows Mule applications to retrieve email from a POP3 email server ... " This happens with: - IMAP - Jetty - POP3 - RMI - SFTP - Servlet - UDP | 5 |
| 111 | STUDIO-2817 | Excel To JSON template looks for the wrong type of excel spreadsheet | In the excel-to-json template, the File inbound-endpoint is looking for a file with the extension ".xlsx". However, the file in "src/test/resources" has the extension ".xls". The result is that the file is not consumed. | 5 |
| 112 | STUDIO-2820 | New JDBC endpoint turns all previous JDBC endpoints to one-way in visual editor | Steps to reproduce: ------------------- 1) Import the attached project 2) Drag and drop an HTTP endpoint from the palette to create e new flow 3) Switch to XML editor and copy the last JDBC endpoint to the clipboard 4) Paste the clipboard contents after the HTTP Inbound endpoint created in step 2 5) Switch to visual editor 6) Take a close look at the JDBC endpoints in the previous flows... See the two arrows indicating request-response? 7) Save the config file in the visual editor. 8) Ta-Da! All JDBC endpoints are now ONE-WAY! | 8 |
| 113 | STUDIO-2824 | Select the sort direction connector queries | As a Studio developer, I want to select a sort field and sort direction for my query (if the connector supports it) so that I can find data in my application that I'm looking for. Acceptance criteria: * I can sort by CreatedDate ascending or descending with Salesforce * Sorting is not enabled if connector does not support it. | 5 |
| 114 | STUDIO-2825 | Display and customize generated connector queries | As a Studio developer, I want to see the generated query for my connector and customize it so that I can understand what is going on and can do advanced queries, such as joins. Acceptance Criteria: * Salesforce SOQL expressions are displayed * I can edit a SOQL expression * I can reset a customized SOQL expression and go back to the generated query and receive a warning if I'm about to do so * I cannot edit any of the items used to generate the query if I have customized the query * The query editor is not displayed if the connector does not support it. | 8 |
| 115 | STUDIO-2827 | Mule 3.4 Pairing with 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 within a Studio instance. From there on: - The HTTP endpoints of all Studio projects, when running within the embedded Studio runtime, should be managable with the paired registry instance. - When the application is deployed on a stand-alone ESB instance, the registry with which the project will be paired will be defined as per the ESB pairing configuration and not as per project's Studio configuration. Detailed specs described here: http://corp.wiki.mulesource.com/display/PRODMGMT/Registry+Interaction+and+License+Management+Support | 8 |
| 116 | STUDIO-2828 | 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 within a Studio instance. From there on: - The HTTP endpoints of all Studio projects, when running within the embedded Studio runtime, should be managable with the paired registry instance. - When the application is deployed on a stand-along ESB instance, the registry with which the project will be paired will be defined as per the ESB pairing configuration and not as per project's Studio configuration. Detailed specs described here: http://corp.wiki.mulesource.com/display/PRODMGMT/Registry+Interaction+and+License+Management+Support | 8 |
| 117 | STUDIO-2829 | Mule 3.4 Dynamic Lookup with Registry | As a Studio 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 | 5 |
| 118 | STUDIO-2831 | Public docs on enabling/creating a connector with meta-data support | ... | 3 |
| 119 | STUDIO-2832 | Studio Welcome Page Update | Updated Studio welcome page. At a minimum the front page should contain a description of the included runtime and the fact that other runtimes can be obtained. | 8 |
| 120 | STUDIO-2842 | Cloud Connectors that do Not have Meta-data Should Work with new meta-data enabled version of Studio without issues | Connectors which were built with the new DevKit, and which do not have any meta-data annotations, should work as they were working before, without the introduction of meta-data. | 8 |
| 121 | STUDIO-2850 | Maven - POM.XML dependencies update when other components than CCs are used | As the present POM.XML is only automatically updated when CCs are used. However, all changes within the Studio canvas should lead to the automatic update of POM.XML. | 8 |
| 122 | STUDIO-2863 | Maven - Import existing Maven project into Studio | As a Maven developer, I would like to import an existing (non-Studio) maven Mule project into Studio and start using Studio to develop. | 8 |
| 123 | STUDIO-2865 | Retrieved metadata from operations must be available through different Studio session. | As a user I want to have the operation metadata I retrieve available in different Studio sessions. (Operations Metadata must be cached on disk) | 8 |
| 124 | STUDIO-2868 | Getting exception when attempting to add a SalesForce Cloud Connector | An exception is thrown when attempting to add a salesforce cloud connector to a flow file. The following error message is returned: "Cannot get Mule ESB - Studio Artifacts!" Steps to reproduce: 1) Create a new mule project and select the option to create a pom.xml file. 2) Go to the "Global references" tab 3) Attempt to add a Salesforce Cloud connector (not the one with OAuth authentication) | 8 |
| 125 | STUDIO-2875 | DataMapper fields not alphabetized for Maps/POJOs | When creating a mapping from a Salesforce object to a CSV, my Salesforce fields were not alphabetically, making it very hard to navigate. As such, when the input/output of a DataMapper is a Map, then the fields of the structure should be sorted alphabetically. | 5 |
| 126 | STUDIO-2885 | Incorrect XML is generated when changing the transaction demarcation of nested transactions | XML is incorrectly generated when a flow contains nested transactions Say you have two transaction scopes, the second being inside the first. The XML would look as follows: {code:xml} <transactional ... > <transactional ... > ... </transactional> </transactional> {code} When changing the demarcation of the first transaction, such as Multi-Transactional, the generated XML would be incorrectly generated as follows: {code:xml} <ee:multi-transactional ...> <transactional ...> ... </ee:multi-transactional> </transactional> {code} Steps to reproduce: 1) Create two transaction scopes, where one is nested inside the other. 2) Place a widget inside the inner-most transaction scope 3) Attempt to change the demarcation of the outer transaction scope. This bug causes the Message Flow canvas and the generated XML to go out of sync. Attempting to delete every transaction scope from the Message Flow canvas after reproducing this bug does not remove the XML. | 8 |
| 127 | STUDIO-2887 | Data sources can be viewed from Connection Explorer | Data sources can be viewed from Connection Explorer. According to docs, only cloud connectors and connectors should be viewed | 3 |
| 128 | STUDIO-2888 | Problem saving after project move | Steps to reproduce: 1.- Install eGit plugin 2.- Create a project 3.- Right clic on it, Team > Share Project 4.- Create a git repository and share the project 5.- Make a modification in the project and then Save Issue: the followed NPE is raised. {code} java.lang.NullPointerException org.eclipse.wst.sse.ui.StructuredTextEditor.updateEncodingMemento(StructuredTextEditor.java:3192) org.eclipse.wst.sse.ui.StructuredTextEditor.doSave(StructuredTextEditor.java:1897) org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor.doSave(MultiPageMessageFlowEditor.java:718) org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:151) org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:277) org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:759) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:756) org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2649) org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:285) org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:264) org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:156) org.eclipse.ui.internal.EditorManager.savePart(EditorManager.java:1399) org.eclipse.ui.internal.WorkbenchPage.savePart(WorkbenchPage.java:3420) org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3433) org.eclipse.ui.internal.handlers.SaveHandler.execute(SaveHandler.java:54) org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.filterEvent(Display.java:1072) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4133) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1495) org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1491) org.eclipse.swt.widgets.Table.sendKeyEvent(Table.java:3064) org.eclipse.swt.widgets.Control.keyDown(Control.java:2371) org.eclipse.swt.widgets.Composite.keyDown(Composite.java:600) org.eclipse.swt.widgets.Table.keyDown(Table.java:1920) org.eclipse.swt.widgets.Display.windowProc(Display.java:5495) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2102) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2299) org.eclipse.swt.widgets.Display.windowProc(Display.java:5557) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5002) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5151) 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:3616) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) org.eclipse.equinox.launcher.Main.run(Main.java:1438) {code} | 8 |
| 129 | STUDIO-2900 | Support for Multiple Versions of Cloud Connectors within Studio | As a Studio user, I would like to be able to open multiple projects in Studio which each use different versions of Cloud Connectors. The Cloud Connector's version could go back to a version as old as 2 years prior to the time at which the version of Studio being used. | 13 |
| 130 | STUDIO-2904 | Select metadata object in data mapper type configuration | As a developer, I want to be able to tell data mapper to use the structure from any object my connector is aware of for the mapping. For example, let's say I want to query Salesforce and that query returns a List of Account objects. Because Studio is not yet aware of the query structure and what object it returns, I need a way to specify that the input to a mapping is a List of Accounts. Right now I can only select connector metadata from an operation that is already metadata aware. So, I should be able to browse all the objects my connector is aware of (i.e. MetadataKeys) and then select that I want my data mapper input/output to be either one of those objects or a List of one of those objects. | 8 |
| 131 | STUDIO-2905 | Meta-data terminology and DataSense Branding | Throughout Studio's customer visible elements, the term meta-data should be replaced with DataSense - the official name for this product feature. Specifically: - In the connector pane, 'Use Metadata' should be replaced with "Enable DataSense". - In the connection explorer, 'reset metadata cache' should be 'Clear DataSense Metadata'. - And in all informational windows, the term DataSense should be used instead. | 3 |
| 132 | STUDIO-2910 | Dragging elements inside the ALL processor generates incorrect XML | Steps to reproduce: 1) Drag an ALL processor to the Message Flow canvas 2) Place a widget and a logger on one path 3) Place another widget and logger on another path 4) Drag one of the loggers onto the other path 5) Go to the XML view. You should see errors in your XML. | 5 |
| 133 | STUDIO-2922 | Arrows are rendered incorrectly when a composite source contains an endpoint whose exchange-pattern is request-response | When a composite source contains one or more inbound-endpoints with an exchange pattern of "request-response" and is followed by a message processor, the arrows are rendered incorrectly. Steps to reproduce: 1) Create a composite source and place an HTTP inbound-endpoint 2) Make sure that the endpoint's exchange pattern is set to "request-response" 3) Add any number of processors/endpoints after the inbound endpoint | 5 |
| 134 | STUDIO-2923 | NullPointerException when adding a query in a JDBC endpoint or connector | Steps to reproduce: 1) Create a JDBC inbound endpoint 2) Open its properties page by double clicking on it 3) Go to the Queries tab 4) Input a query key and press tab while the textbox is still in focus | 8 |
| 135 | STUDIO-2926 | Update Mule-common library to include enhanced error management and new maps features | Update Mule-common library to version 0.9.0 to include enhanced error management and new maps features | 5 |
| 136 | STUDIO-2928 | Generate default option should be disabled when there are no fields to generate from | When creating a Data Mapping flow, there is an option which generates default input/output fields based on output/input fields respectively. This option should be disabled when there are no fields to generate from. When there are no input fields, the "Generate default" option in the output section should be disabled, and vice-versa. In addition, it would help the user if the "Generate default" option is renamed to "Generate default from output" for the input section, and "Generate default from input" for the output section. | 3 |
| 137 | STUDIO-2932 | Selecting the text() attribute of XML elements in data mapping files causes a NullPointerException | Steps to reproduce: 1) Create a new Data Mapping flow file. Make sure that at least the input or output is XML. 2) Add a new field to the XML input (or output) and set its type to "Element". 3) Double click on the "text()" attribute which is created automatically with the element. | 3 |
| 138 | STUDIO-2933 | Nested attributes are created when adding an XML element with a name identical to an existing attribute | Steps to reproduce: 1) Create a new Data Mapping flow file. Make sure that at least the input or output is XML and contains an attribute (let's call it "name"). 2) Add a new field with the same name and set its type to "Element". You should get an attribute "name", with another attribute called "text()" as a child. Deleting the "name" attribute causes an XML element with the same name to appear. | 8 |
| 139 | STUDIO-2940 | Cannot open non-Studio Mule projects in Eclipse when Studio plugins installed | I have updated my Eclipse distribution with the Studio plugins [2/28/13 5:05:07 PM] Reza Shafii: things worked great, until I tried to open a non-studio project's Mule flow config, that's when I got this exception: [2/28/13 5:05:08 PM] Reza Shafii: ava.lang.NullPointerException org.mule.tooling.core.io.MuleResourceUtils.getFlowFileFromConfigFile(MuleResourceUtils.java:345) org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor.addPages(MultiPageMessageFlowEditor.java:378) org.eclipse.ui.forms.editor.FormEditor.createPages(FormEditor.java:138) org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348) org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670) org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465) org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:289) org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2945) org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2850) org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2842) org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2793) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2789) org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2773) org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2764) org.eclipse.ui.ide.IDE.openEditor(IDE.java:651) org.eclipse.ui.ide.IDE.openEditor(IDE.java:610) org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:355) org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:164) org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:249) org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:228) org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:275) org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:251) org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:376) org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.open(PackageExplorerPart.java:538) org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:866) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:864) org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1152) org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1256) org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:275) org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:269) org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:309) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) org.eclipse.equinox.launcher.Main.run(Main.java:1410) [2/28/13 5:05:33 PM] Reza Shafii: I should be able to work with a non-Studio Mule project in Eclipse even if the Mule plugins are installed... [2/28/13 5:06:17 PM] Reza Shafii: It seems that the problem is that it associates the flow xml with the Studio editor by default [2/28/13 5:06:26 PM] Reza Shafii: if I use the XML editor explictly then things work | 8 |
| 140 | STUDIO-2941 | Integrate Custom Compiled Cloud Connectors into Studio | We will have to integrate custom cloud connectors into Studio... again. This will take time since it implies changing how Cloud Connectors are fetched, using local items (kinda "hard coded"). | 5 |
| 141 | STUDIO-2943 | Maven: NPE when pom is not parseable | Whenever the pom is malformed, therefore causing it not to be parseable, it will raise an NPE when saved. | 5 |
| 142 | STUDIO-2945 | NPE when creating the first CE project on a new workspace | When downloading the CE runtime, creating a new workspace and creating a new CE project, if the user drops a database component and switches to EE the user is not warned that the namespace will change and if he drops a new database component and tries to save, the mule builder throws a NPE. Step to reproduce: - Download CE runtime - Create new workspace - Create new CE project - add a database component - Switch to EE in the mule-config.xml - add another database component - Save de project | 13 |
| 143 | STUDIO-2946 | Editing configuration deletes all processor configured fields | When you edit the configuration of a global element opening the screen from the Pattern Properties screen after saving you lose all fields configuration made to the flow. Steps to reproduce: 1) Create a flow and set some of the fields required for the operation. 2) From the screen where you edit the variables (Pattern Properties) open the Global Configuration edit screen to modify the connector connection information. 3) Change the values of some of the configurable fields. 4) Save and check the XML view. Expected: We can see the configuration changes and the flow didn't change. Actual: All the configuration made at step 1 will be lost. Also, when you enter to the Global Elements configuration screen after saving, all values that were not edited, are shown as empty instead of the default. | 5 |
| 144 | STUDIO-2947 | Ability to handle errors with individual records in data mapper | As a developer, I want to be able to handle individual records that have errors in my data mapping. Currently I can only stop processing everything, or I can silently ignore the errors. If this option is enabled, the exception strategy would be invoked for invidual records. Spec details TBD form Pablo Abad | 8 |
| 145 | STUDIO-2950 | DataSense should use the proper type field depending on the connector. | DataSense asumes that the type field with the sOBject type for example is always called type. This is not the case, as many connectors use a different field to this end. DataSense should use the correct one, not asume it is called 'type' | 5 |
| 146 | STUDIO-2953 | Avoid trying to get metadata when the connector reference is not configured | When the config reference is null, Studio must not try to get metadata. This generates null values in the cache, that must be avoided. | 1 |
| 147 | STUDIO-2955 | When modifying the pom.xml the .mflow file somehow gets updated and you need to save it again before running the project | Steps to reproduce: 1.- Create a project with a pom file 2.- Check that the mflow file is saved. 3.- Open the pom file, add a modification and save Issue: the mflow file is updated and you didn't perform any modification to it | 8 |
| 148 | STUDIO-2956 | Maven: add an option to manually refresh the projects dependencies | This is for the cases when the pom is handled when studio is closed and the user wants to update the classpath. | 3 |
| 149 | STUDIO-2959 | Connectivity Testing/Get Metadata Types is not using the values in the configuration dialog for Global Connectors | Connectivity Testing/Get Metadata Types is not using the values in the configuration dialog for Global Connectors. It should use the newly entered values. | 2 |
| 150 | STUDIO-2964 | Metadata Cache Consistency | Ensure consistency of the metadata cache. When a project is deleted, the elements from that project should be removed, for example. The same happens when elements are removed from any flow, etc. | 8 |
| 151 | STUDIO-2965 | Add support for POJOs in the Object builder and persist them in the XML | Add support for displaying and editing POJOs in the object builder. The changes made to a POJO in the object builder should be reflected in the XML. | 13 |
| 152 | STUDIO-2967 | Maven: should detect if Maven is installed and prevent the user from enabling maven support/fail at doing maven things | Actually if the user does not have Maven installed, or has the path to his maven installation configured incorrectly, things explode in an uncontrolled way. We need to work on this so as to prevent the user from using Maven features if he does not have Maven installed. | 8 |
| 153 | STUDIO-2968 | Maven: subsequent addition of new components may block because of pom being updated | If the user drops, for example, an Ajax endpoint, a scripting component and an SMTP outbound endpoint, he will be blocked in the third step because Studio is still running the first studio:studio. Studio should detect that there is already a Job updating the dependencies of the classpath, cancel it, and start a new one (avoiding to block the user). | 8 |
| 154 | STUDIO-2969 | Set up the continuous automated testing | We need to get the Jubula tests running by bamboo at nights. | 8 |
| 155 | STUDIO-2970 | Integrate the cloud connectors snapshot repository into the build | We need to integrate the new repository and set up things so that we can alter between the snapshots and the releases repository. | 3 |
| 156 | STUDIO-2972 | Maven: studio:studio duplicated referenced libraries with the ones in the Runtime (when they are transitive dependencies) | Direct dependencies that are included in the runtime are not duplicated, but this filter/rule is not applied to transitive dependencies (if a dependency has a mule transport as transitive dependency, it will be duplicated in the classpath) | 13 |
| 157 | STUDIO-2973 | Remove Clover ETL import functionality | The Clover ETL options shouldn't be displayed in the Import / Export dialog | 5 |
| 158 | STUDIO-2976 | Scrip Component is not displaying the script text | Steps to reproduce: 1.- Create the travel agent template project. 2.- Open the groovy script configuration window Issue: the script is not displayed in the UI | 3 |
| 159 | STUDIO-2977 | Renaming a file by using refactor option deletes all the scripts in the file | Steps to reproduce: 1.- Create the Travel Agent project 2.- Check the xml file and the scripts in it. 3.- Right clic on the Travel Agent.mflow and clic on refactor > rename 4.- Rename the file to Travel Agent2.mflow 5.- Go to the XML view Issue: all the CDATA components have lost their script. | 5 |
| 160 | STUDIO-2979 | Combining all transformers into a single component. | Currently all transformer components are listed separately, however, combining them into a single component after which the particular type of transformation can be selected will greatly simplify usability. | 13 |
| 161 | STUDIO-2981 | Combining Filters into a single Component | Combination of all filter components into a single one. User would then pick the type of filter after dropping the filter element into the canvas. | 13 |
| 162 | STUDIO-2982 | Combining language components and transformers into as single one | Combination of all language transformers and components into a single building block. User would then be able to pick a single component (say: Custom Logic) and then decide whether it is a component or transformer, then pick the language to use. | 13 |
| 163 | STUDIO-2987 | Metadata doesn't propagate past an enricher | Since an enricher does not change the payload - it normally just puts stuff in a flowVar, we should be able to propagate metadata past it. | 2 |
| 164 | STUDIO-2988 | POM-added JAR dependencies are not added to exported archive | Steps to reproduce 1. created a project in Studio 2. added a dependency to the pom.xml* 3. The dependency is added to the project and I can find the packages and classes when writing Java (good) 4. However,when I export (File-> Export->Mule package) the Jar is not included oss-MacBook-Pro-4:projects ross$ unzip -l ~/Desktop/maven-test2.zip Archive: /Users/ross/Desktop/maven-test2.zip Length Date Time Name -------- ---- ---- ---- 119 03-12-13 10:39 mule-deploy.properties 13473 03-12-13 10:39 pom.xml 0 03-12-13 10:39 classes/ 1285 03-12-13 10:39 classes/maven-test2.xml 0 03-12-13 10:39 META-INF/ 0 03-12-13 10:39 META-INF/flows/ 5020 03-12-13 10:39 META-INF/flows/maven-test2.mflow 0 03-12-13 10:39 META-INF/src/ 0 03-12-13 10:39 META-INF/src/main/ 0 03-12-13 10:39 META-INF/src/main/java/ 129 03-12-13 10:39 META-INF/src/main/java/Test.java 364 03-12-13 10:39 classes/Test.class 1285 03-12-13 10:39 maven-test2.xml 84 03-12-13 10:39 classes/mule-app.properties 0 03-12-13 10:39 plugins/ 7747039 02-20-13 03:22 plugins/mule-module-sqs-2.2.0.zip 440 03-12-13 10:39 META-INF/.project 21266 03-12-13 10:39 META-INF/.classpath 84 03-12-13 10:39 mule-app.properties 119 03-12-13 10:39 classes/mule-deploy.properties 200 03-12-13 10:39 META-INF/mule-project.xml -------- ------- 7790907 21 files * I used this jar <dependency> <groupId>com.fasterxml.uuid</groupId> <artifactId>java-uuid-generator</artifactId> <version>3.1.3</version> </dependency> | 2 |
| 165 | STUDIO-4863 | For composite filters, Studio's UI doesn't allow names, validations require it and throw error | When adding composite filters (Or, And, Not) and adding a component sub-filter , the UI for the sub-filter does not have a field for the Name of this sub-filter. However, the validation on the generated XML complains about this sub-element not having a name. See screenshots | 5 |
| 166 | STUDIO-2991 | Change export documentation icon | Change the icon of the export documentation feature in the toolbar. | 1 |
| 167 | STUDIO-2994 | Include new examples in Studio | We need to include the following three new examples (developed by SE team) within the set of examples that are distributed with Studio: - New Hello World Example - APIs R Us Example - SaaS Integration Example | 8 |
| 168 | STUDIO-2996 | Connectivity fails when using placeholders | If placeholders are used to provided credentials to the connector and the connection is tested, error is returned. *Steps to reproduce* 1. Place the following lines on the mule-app.properties twitter.accessKey=729170916-itUkhAOVAmKEUHYy0tMHPat1xPKFzZpJVYo0UJPq twitter.accessSecret=15rDkwpWyuoO08RzT4KfT7WuBhTnZn4WUPDbr1x2how twitter.consumerKey=2cnPj2sizrD9fkjB7123Q twitter.consumerSecret=8Ak7G3iflelVdYj85JlpfBm2odR4NNCLaYp102zmqo 2. Create a Twitter Global Element and populate its fields using the following placeholders: ${twitter.accessKey} ${twitter.accessSecret} ${twitter.consumerKey} ${twitter.consumerSecret} Test the connection. Error is returned. | 5 |
| 169 | STUDIO-2999 | DataMapper example is not working fine | Steps to reproduce: 1.= Create the excel to JSON template project 2.- Run the project 3.- Feed the flow with the provided xls file Issue: the followed exception is raised in the console {code} ******************************************************************************** Message : Cannot process event as "connector.http.mule.default" is stopped Code : MULE_ERROR-166 -------------------------------------------------------------------------------- Exception stack is: 1. Cannot process event as "connector.http.mule.default" is stopped (org.mule.api.lifecycle.LifecycleException) org.mule.lifecycle.processor.ProcessIfStartedMessageProcessor:42 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/lifecycle/LifecycleException.html) -------------------------------------------------------------------------------- Root Exception stack trace: org.mule.api.lifecycle.LifecycleException: Cannot process event as "connector.http.mule.default" is stopped at org.mule.lifecycle.processor.ProcessIfStartedMessageProcessor.handleUnaccepted(ProcessIfStartedMessageProcessor.java:42) at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:48) at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ******************************************************************************** {code} | 2 |
| 170 | STUDIO-3002 | DataSense: NPE when clicking OK in the object builder without configuring the object | Steps to reproduce: 1.- Create a SFC connection 2.- Configure a CC in the canvas, and set the operation to Create 3.- Select any sObject Type 4.- Clic the radio button to create the object manually, and clic in the object button 5.- Clic OK without configuring any parameter in the object Issue: the followed NPE is raised: {code} java.lang.NullPointerException org.mule.tooling.ui.modules.core.metadata.BuildMetadataActionHandler.edit(BuildMetadataActionHandler.java:56) org.mule.tooling.ui.modules.core.widgets.meta.ChildControllerFieldEditor.onEdit(ChildControllerFieldEditor.java:73) org.mule.tooling.ui.modules.core.widgets.meta.ChildControllerFieldEditor$1.widgetSelected(ChildControllerFieldEditor.java:60) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3980) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3619) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) org.mule.tooling.messageflow.editpart.PatternEditPart.editRequested(PatternEditPart.java:132) org.mule.tooling.messageflow.editpart.EntityEditPart.performRequest(EntityEditPart.java:145) org.eclipse.gef.tools.SelectEditPartTracker.performOpen(SelectEditPartTracker.java:194) org.eclipse.gef.tools.SelectEditPartTracker.handleDoubleClick(SelectEditPartTracker.java:137) org.eclipse.gef.tools.AbstractTool.mouseDoubleClick(AbstractTool.java:1069) org.eclipse.gef.tools.SelectionTool.mouseDoubleClick(SelectionTool.java:527) org.eclipse.gef.EditDomain.mouseDoubleClick(EditDomain.java:231) org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseDoubleClicked(DomainEventDispatcher.java:291) org.eclipse.draw2d.LightweightSystem$EventHandler.mouseDoubleClick(LightweightSystem.java:518) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:196) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3980) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3619) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) org.eclipse.equinox.launcher.Main.run(Main.java:1438) {code} | 1 |
| 171 | STUDIO-3003 | Generate Documentation is not working with Order Processing template project | Steps to reproduce: 1.- Create the Order Processing template project 2.- Export the project to documentation Issue: the process is cancelled automatically and the documentation is not generated, the followed NPE is raised: {code} org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) org.eclipse.swt.SWT.error(SWT.java:4361) org.eclipse.swt.SWT.error(SWT.java:4276) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3944) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3621) org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173) org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) org.mule.tooling.studoc.handlers.ExportStudioDocumentationHandler$1$1.run(ExportStudioDocumentationHandler.java:88) org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164) org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3944) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3621) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) org.eclipse.equinox.launcher.Main.run(Main.java:1438) Caused by: java.lang.NullPointerException org.mule.tooling.studoc.utils.DocElementHelper.retrieveXmlRelatedPart(DocElementHelper.java:165) org.mule.tooling.studoc.utils.DocElementHelper.createDocElement(DocElementHelper.java:98) org.mule.tooling.studoc.utils.DocElementHelper.generateDocElements(DocElementHelper.java:173) org.mule.tooling.studoc.utils.DocElementHelper.generateDocElements(DocElementHelper.java:181) org.mule.tooling.studoc.utils.DocElementHelper.generateDocElements(DocElementHelper.java:181) org.mule.tooling.studoc.utils.DocElementHelper.generateDocElements(DocElementHelper.java:181) org.mule.tooling.studoc.model.DocConfigFactory$1.run(DocConfigFactory.java:43) org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180) org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) org.eclipse.swt.widgets.Display.syncExec(Display.java:4605) org.mule.tooling.studoc.model.DocConfigFactory.createDocConfig(DocConfigFactory.java:39) org.mule.tooling.studoc.handlers.ExportStudioDocumentationHandler$2.run(ExportStudioDocumentationHandler.java:160) org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) ... 32 more {code} | 3 |
| 172 | STUDIO-3010 | Rollback Exception Strategy is not well drawn in the canvas | When the expression is to long the drawing of the box is not correct, check the attached screenshot. | 5 |
| 173 | STUDIO-3031 | Get Studio interop use cases tested and to a green satus | Priority 1 use cases listed within the Studio table here: http://corp.wiki.mulesource.com/display/interop/Interoperability+Home+Page | 13 |
| 174 | STUDIO-3019 | Metadata does not get the appropiate metadata for arguments different than the one marked as default payload | Metadata does not get the appropiate metadata for arguments different than the one marked as default payload. This is problematic for elements that have many lists, for example, in the editor. Metadata should bring the specific metadata for each argument. | 8 |
| 175 | STUDIO-3021 | APIkit - Interface/Service File Support | As an APIkit developer, I should be able to create a Mule project in Studio, add XML files to my flow folder and add APIkit interfaces. Studio should not display errors when I do this and my project should build and run with the APIkit interfaces available so long as I have ensured that the JAR dependencies are satisfied, either through Maven or Eclipse (depending on the project's build type) | 8 |
| 176 | STUDIO-3024 | Object Builder: I shouldn't be able to set the string attribute name | Steps to reproduce: 1.- Create a SFCD connection, add an endpoint and configure a get Updated Object operation. 2.- Configure the sObject type to Account 3.- Open the object builder and configure some strings Issue: you are able to set names in the Name columns but this names are not reflected in the XML so, or the user shouldn't be able to change the names or the names should be reflected in the XML. | 2 |
| 177 | STUDIO-3027 | Replace new Studio Help Files | Update the Studio help files with the ones in the attached file. | 1 |
| 178 | STUDIO-3034 | Dynamic Endpoint Naming and Shape | The dynamic endpoint component in Studio should be modified as follows: - Name should be changed from 'Dynamic Router' to 'Anypoint Service Registry'. - Color should be changed from yellow to blue. - Component should be moved from flow-control to end-point section. - Service Name should be changed to Service ID. The icon symbol can stay as is. | 3 |
| 179 | STUDIO-3035 | Improving the way lists are managed and displayed in the Object builder. | Improving the way lists are managed and displayed in the Object builder. Some big refactorings will be required. | 5 |
| 180 | STUDIO-3040 | Maven: when no maven installation is found the error message shows a null location | Check screenshot | 1 |
| 181 | STUDIO-3041 | Maven: deleting maven from /usr/share while studio is opened is letting users to create mvn projects. | When deleting maven from /usr/share while having studio opened is not being validated letting the users to create incomplete maven projects. | 8 |
| 182 | STUDIO-3042 | Export to deployable archive should include transitive project dependencies | When exporting to a deployable archive, classes and jars from referenced projects should be included in the resulting zip file. | 8 |
| 183 | STUDIO-3047 | Add value-ref support to the Object builder for objects that cannot be persisted in the XML | Nowadays, the xml config allows to persist until 3 levels of nested elements (complex elements). For example, if we have a structure in the object builder which have more than 3 levels, only the first 3 levels will be persisted. So, the user should be able to set a value-ref to those elements in the Object builder which are at the level 3 and which have children. This way, the those complex elements can have a reference to another element. However, children of those elements will still be shown in the object builder, but their values can't be edited. | 8 |
| 184 | STUDIO-3051 | When using the CE runtime the JDBC icon shown in the connection explorer is the EE icon | Steps to reproduce: 1.- Create a project with a JDBC connector using the EE runtime 2.- Save and install the CE runtime 3.- Change the runtime of the project to CE Issue: after refreshing everything you have the JDBC EE icon shown in the connection explorer even if you are using the CE runtime. Check screenshot. | 2 |
| 185 | STUDIO-3052 | Transaction Action NOT_SUPPORTED is missing in autocompletion | check screenshot | 1 |
| 186 | STUDIO-3053 | Welcome Page MuleStudio icon link is not working | If you click on the "MuleStudio" icon on the top left of the screen, you get the error message displayed in the screenshot. | 5 |
| 187 | STUDIO-3054 | Validation warning in XPath expression | Validation for the following component, generates an invalid warning: {code} <message-properties-transformer scope="session" doc:name="Store SAP ID in Session"> <add-message-property key="SapCustomerNumber" value="#[xpath:/jco/export/field[@name='CUSTOMERNO']]" /> </message-properties-transformer> {code} The warning is: *Expected ], but found:* | 8 |
| 188 | STUDIO-3055 | Import a zip that has _MACOSX folder inside (right click - compress in finder) does not work | When importing a zip that was exported with general export it fails and it used to work Edit: importing a zip that was compressed with finder and somehow has a _MACOSX folder, does not work /project-folder.zip --project-folder --_MACOSX | 5 |
| 189 | STUDIO-3056 | Magento metadata not being fetched | Metadata is only been fetched for the following operations: set-shopping-cart-customer-addresses update-shopping-cart-product create-order-shipment create-order-invoice remove-shopping-cart-product add-shopping-cart-product | 5 |
| 190 | STUDIO-3057 | Upgrade SAP connector to 2.1.0 | Upgrade to latest SAP version. | 5 |
| 191 | STUDIO-3061 | Connector not added to the classpath | I'm using a nightly build from March 27th. I've a pom file in my project but maven support is disabled. When i drag & drop any connector from the palette to any flow, the connector lib should be added to the classpath, but it's not. | 1 |
| 192 | STUDIO-3064 | XML could not be parsed after deleting a logger component from an All flow control | When having a processor chain then an 'All' flow control with 4 loggers inside (saved project), if the user deletes 1 of the logger components and moves to the XML view without saving and then goes back the the Message Flow view, and error message is displaying saying that the XML cannot be parsed. To reproduce: - Import attached project - Delete 1 of the logger component - Without saving, go to the XML view and then back to the Message Flow view | 5 |
| 193 | STUDIO-3065 | Studio fails to show the right spot of an error in the ui editor | Studio fails to show the right spot of an error in the ui editor. While coding I had a flow with and http inbound a groovy transformer and after those two flow ref. I change the names of the flows, where the flow-ref where pointing. As a result the flow ref stopt working which is ok. BUT although the xml view showed the correct error (check attached image) the UI showed the errors to the left. Is liked the actual errors where moved two processors to the left. | 13 |
| 194 | STUDIO-3066 | Cannot store value-ref in the xml using property collections for cloud connectors | Cannot store value-ref in the xml using property collections for cloud connectors. Please test using the object builder and salesforce. | 8 |
| 195 | STUDIO-3073 | Saving a Mapping in DataMapper | Following the issue faced on save a file. Steps to reproduce. 1. Pick a field in DataMapper and past a mapping in field without drag & drop just copy & paste. 2. Now click on flow panel - a pop-up comes do you want to save the mapping hit yes. 3. Then go back to top and hit Save all project files 4. Now go back to DataMapper it would load the mapping again and notice the field mapping is lost. | 3 |
| 196 | STUDIO-3077 | Studio Feedback: modify error message dialog to point the users to the forums or jira instead of pointing to the studio-feedback email | We need to modify the error message displayed when and error cames up to tell the user to open a Jira file or make a post in our forums | 2 |
| 197 | STUDIO-3085 | Problem with Legacy Modernization Example | The SFDC location is declared twice and the version of the schema is wrong, it's 4.0 and it should be 5.0. Attached is the example with the fixes. | 2 |
| 198 | STUDIO-3086 | Drag and Drop not working with Scrolling | When drag and drop a component and you wish to place it at a place that requires the screen to scroll, studio doesn't do it. This is, it doesn't scroll when you drag and drop. The fast way to reproduce this is to create a really long flow and try to move a component from the end to the begining | 13 |
| 199 | STUDIO-3087 | Import (backward compatibility) : scan application xml's for usage of CC in order to add the libraries to the classpath when importing | TBD | 5 |
| 200 | STUDIO-3088 | Remove @SupressWarning from the com.mulesoft.se.orders.OrderSummary.java class as it is causing warnings in the Order Processing template project | Attaching the project, we only need to remove the @SuppressWarnings("unused") From that class because this is causing the project to have a warning | 2 |
| 201 | STUDIO-3096 | Import project from pom wizard disappears when pom.xml doesn't 'compile' | If the pom file is not valid, an error should be displayed to the user before exiting the wizard. | 3 |
| 202 | STUDIO-3103 | Modifying the project name in the mule-project.xml file generates problems in many places in Studio | The project name in the mule-config.xml file is just a label. It should not be used to do anything. Add the concept of project label and return the java project name when using getName(). | 3 |
| 203 | STUDIO-3104 | Studio 3.4 Working with 3.3.3 EE ESB Embedded Runtime | User should be able to install and download a 3.3.3 EE ESB runtime within Studio and be able to use it for new projects. All 3.3.3 Studio/ESB functionality should work with this runtime. | 13 |
| 204 | STUDIO-3118 | Change the way Studio handles ESB runtime changes | When changing the project esb runtime you get a asked once for each flow in the project if you want to modify the namespaces already present in the files. This is annoying and bad User Experience. Streamline this experience. | 3 |
| 205 | STUDIO-3126 | Add a 'Don't warn me again' checkbox to the warning popup that communicates that the maven installation could not be found | Add a 'Don't warn me again' checkbox to the warning popup that communicates that the maven installation could not be found. | 3 |
| 206 | STUDIO-3128 | Showing blank image in DataMapper errors logger in Windows 7 | Showing blank image in the DataMapper error log using windows 7 OS. See attached image. | 5 |
| 207 | STUDIO-3138 | SFDC Connector not retrieving OpportunityLineItem Metadata | OpportunityLineItem does not get datasensified. Manual creation of object not allowed. | 5 |
| 208 | STUDIO-3144 | Allow creation of a new preview file if there is none selected | Give the possibility to create a new input file if there is no one selected in the preview tab. It could be useful in a future to add templates to this feature | 8 |
| 209 | STUDIO-3145 | Delete Multiple Fields in the user-defined wizard component | At wizard when you are creating the metadata fields in the user-defined component there is no possibility to delete a group of fields. | 8 |
| 210 | STUDIO-3146 | Debugger doesn't work after <all> | Trying to inspect an expression using the Inspect shortcut after an <all> processor doesn't work. Please see attached project and screenshot. | 2 |
| 211 | STUDIO-3147 | Setting the JMS transaction action in 3.4.0 of studio is not saved. Nor setting the action in the jms transaction is read by the Mule Studio. Ends up defaulting to NONE. | It appears that the JMS transaction Action is not working: Setting it in the Mule Studio and saving does not work. The action is not set in the XML; Nor setting the jms transaction in Configuration XML editor is reflected back into the Message Flow UI/Graphical editor. Also, see the message: "Attribute action1 of nested element Transaction is required" but don't know how to set it to make this message go away. | 3 |
| 212 | STUDIO-3148 | Studio crashes when creating a new project if having more than one runtime installed in Windows | Steps to reproduce: Course A: # Start with a clean Studio, install the CE runtime. # Restart Studio # Go to new mule project * Mule Studio freezes, and if you restart it there will be a lot of entries on the error log. Course B: # Start with a clean Studio # Create a project (clean or example), leave the editor open # Install the CE runtime and restart Studio * Studio won't start again, pointing to an error log file in the workspace | 13 |
| 213 | STUDIO-3149 | Autocomplete doesn't work with functions arguments | when you try to pass argument to functions in the script tab the autocomplete doesnt work. | 5 |
| 214 | STUDIO-3152 | Clear application data | As a user, I want to be able to reset the object store or remove any other persistent data for my project. Acceptance Criteria: * User can right click on project and click "Clear Application Data" on a project . This will delete the default user object store on disk. *Old Description* Looks like the default implementation of the object store in mule has change to a persistent implementation. Although this is not a major problem, it has its problems. Mainly as most of us are not aware of this fact the problem is that we shut down the app and studio and when we restarted the info is still there. It'll be a cool feature to add a button to studio that clean this persistent storage in the file system. As a work around, Mariano Merlo found that the storage is being held in: ${workspace}/.mule/.mule/${project}/objectstore And if you delete it you are good to go. But most people are not as smart as he is. | 5 |
| 215 | STUDIO-3154 | Improve version validation between ESB and CCs | If we are going to support Studio 3.4 with older runtimes, we need to add a validation when creating a project using ESB 3.3.3 or ESB 3.3.2 and using cloud connectors build with 3.4.0. If the user tries to add a CC build with 3.4.0 in an Studio project using an older runtime an error message should be displayed, warning the user about the incompatibility issue. | 8 |
| 216 | STUDIO-3156 | Add jars from another project in workspace causes FileNotFoundException | Check SE-122 | 5 |
| 217 | STUDIO-3158 | Studio throws weird exception when getting metadata | After upgrading to a new connector version, the attached project started to throw the following exception when trying to test connector or to get metadata. Funny thing is that the exact same code, with the exact same connector worked just fine when added to a brand new project. org.mule.common.MuleArtifactFactoryException: Error initializing org.mule.config.spring.SpringXmlConfigurationMuleArtifactFactory.doGetArtifact(SpringXmlConfigurationMuleArtifactFactory.java:149) org.mule.config.spring.SpringXmlConfigurationMuleArtifactFactory.getArtifactForMessageProcessor(SpringXmlConfigurationMuleArtifactFactory.java:56) org.mule.config.spring.SpringXmlConfigurationMuleArtifactFactory.getArtifactForMessageProcessor(SpringXmlConfigurationMuleArtifactFactory.java:39) org.mule.tooling.metadata.api.utils.MetadataRetriever.getExternalMetadata(MetadataRetriever.java:65) org.mule.tooling.ui.modules.core.metadata.MetadataManager.getMetadata(MetadataManager.java:43) org.mule.tooling.ui.modules.core.metadata.GetMetadataAction$1$1.run(GetMetadataAction.java:64) java.lang.Thread.run(Thread.java:722) Caused by: org.mule.api.config.ConfigurationException: Line 3 in XML document from is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 3; columnNumber: 305; cvc-complex-type.2.4.a: Invalid content was found starting with element 'servicesource:create-dynamic'. One of '{"http://www.mulesoft.org/schema/mule/core":annotations, "http://www.mulesoft.org/schema/mule/core":description, "http://www.mulesoft.org/schema/mule/core":abstract-message-source, "http://www.mulesoft.org/schema/mule/core":abstract-inbound-endpoint, "http://www.mulesoft.org/schema/mule/core":abstract-message-processor, "http://www.mulesoft.org/schema/mule/core":abstract-outbound-endpoint, "http://www.mulesoft.org/schema/mule/core":abstract-mixed-content-message-processor, "http://www.mulesoft.org/schema/mule/core":response}' is expected. (org.mule.api.lifecycle.InitialisationException) org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:52) org.mule.config.builders.AbstractResourceConfigurationBuilder.configure(AbstractResourceConfigurationBuilder.java:78) org.mule.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:103) org.mule.context.DefaultMuleContextFactory.createMuleContext(DefaultMuleContextFactory.java:59) org.mule.config.spring.SpringXmlConfigurationMuleArtifactFactory.doGetArtifact(SpringXmlConfigurationMuleArtifactFactory.java:129) ... 6 more Caused by: org.mule.api.lifecycle.InitialisationException: Line 3 in XML document from is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 3; columnNumber: 305; cvc-complex-type.2.4.a: Invalid content was found starting with element 'servicesource:create-dynamic'. One of '{"http://www.mulesoft.org/schema/mule/core":annotations, "http://www.mulesoft.org/schema/mule/core":description, "http://www.mulesoft.org/schema/mule/core":abstract-message-source, "http://www.mulesoft.org/schema/mule/core":abstract-inbound-endpoint, "http://www.mulesoft.org/schema/mule/core":abstract-message-processor, "http://www.mulesoft.org/schema/mule/core":abstract-outbound-endpoint, "http://www.mulesoft.org/schema/mule/core":abstract-mixed-content-message-processor, "http://www.mulesoft.org/schema/mule/core":response}' is expected. org.mule.registry.AbstractRegistry.initialise(AbstractRegistry.java:117) org.mule.config.spring.SpringXmlConfigurationBuilder.createSpringRegistry(SpringXmlConfigurationBuilder.java:119) org.mule.config.spring.SpringXmlConfigurationBuilder.doConfigure(SpringXmlConfigurationBuilder.java:73) org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:46) ... 10 more Caused by: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 3 in XML document from is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 3; columnNumber: 305; cvc-complex-type.2.4.a: Invalid content was found starting with element 'servicesource:create-dynamic'. One of '{"http://www.mulesoft.org/schema/mule/core":annotations, "http://www.mulesoft.org/schema/mule/core":description, "http://www.mulesoft.org/schema/mule/core":abstract-message-source, "http://www.mulesoft.org/schema/mule/core":abstract-inbound-endpoint, "http://www.mulesoft.org/schema/mule/core":abstract-message-processor, "http://www.mulesoft.org/schema/mule/core":abstract-outbound-endpoint, "http://www.mulesoft.org/schema/mule/core":abstract-mixed-content-message-processor, "http://www.mulesoft.org/schema/mule/core":response}' is expected. org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302) org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174) org.mule.config.spring.MuleApplicationContext.loadBeanDefinitions(MuleApplicationContext.java:113) org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130) org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:537) org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:451) org.mule.config.spring.SpringRegistry.doInitialise(SpringRegistry.java:89) org.mule.registry.AbstractRegistry.initialise(AbstractRegistry.java:109) ... 13 more Caused by: org.xml.sax.SAXParseException; lineNumber: 3; columnNumber: 305; cvc-complex-type.2.4.a: Invalid content was found starting with element 'servicesource:create-dynamic'. One of '{"http://www.mulesoft.org/schema/mule/core":annotations, "http://www.mulesoft.org/schema/mule/core":description, "http://www.mulesoft.org/schema/mule/core":abstract-message-source, "http://www.mulesoft.org/schema/mule/core":abstract-inbound-endpoint, "http://www.mulesoft.org/schema/mule/core":abstract-message-processor, "http://www.mulesoft.org/schema/mule/core":abstract-outbound-endpoint, "http://www.mulesoft.org/schema/mule/core":abstract-mixed-content-message-processor, "http://www.mulesoft.org/schema/mule/core":response}' is expected. org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source) org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source) org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) org.apache.xerces.parsers.XMLParser.parse(Unknown Source) org.apache.xerces.parsers.DOMParser.parse(Unknown Source) org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75) org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:388) ... 22 more | 8 |
| 218 | STUDIO-3161 | Drag and Drop: Async is not allowing you to drop Message Routers or other scopes inside of it | Steps to reproduce: 1.- Create a flow with an Async MP 2.- Try to drop any Message Router or other scopes inside the Async Issue: you are not allow to do it at least that first you drop an Endpoint or other MP inside. | 3 |
| 219 | STUDIO-3165 | Problem with 1.3.x Cloud Connectors in Studio 3.4.0 | When installing a Cloud Connector from the 1.3.x UpdateStie to be used with ESB 3.3.3 over Studio 3.4.0, if you add a CC to your flow the CC location is not added to the XML causing a parse exception in runtime. Steps to reproduce: 1.- Take Studio 3.4.0 and uninstall Salesforce connector. 2.- From the local bamboo updateSite install the 3.3.3 ESB runtime 3.- From the 1.3.x Connectors updateSite (.../releases/1) install the latest salesforce connector found there. 4.- Create a project using 3.3.3 runtime 5.- Add any endpoint and a Salesforce connector, go to the XML tab Issue: the location declaration of the salesforce connector has not been added to the xml. Note, this is only happening when using 3.3.3 or 3.3.2 runtimes in Studio 3.4.0 - This works fine when using 3.4.0 runtime or when using the previous version of Studio 1.3.2. | 5 |
| 220 | STUDIO-3167 | Support hybrid metadata models | Right now DataSense supports two types of metadata: * Static: Which is completely obtained from Instrospection of pojos * Dynamic: Completely obtained from @MetadataRetriever method Connectors such as Netsuite or ServiceSource present a hybrid case, in which most of the metadata is static, but the pojos that the connector handle have an internal map to represent custom fields. Right now there's no support OOTB for this and the case needs to be handled manually at the metadata retriever, forcing the user to instrospect the object by hand. Also, if forces the connector to have two versions for each processor. For example, consider the following: public MyPojo create(@Optional @Default("#[payload]") MyPojo pojo) { ... } There's no way to make use of DataSense in that processor. Then, you're forced to add a second processor that looks like this: public Map<String, Object> dynamicCreate(@MetadataKeyParam String type, @Optional @Default("#[payload]) Map<String, Object>) { ... } PROPOSAL One solution that I can think of for this problem is to enable this hybrid cases by creating a new annotation called @MetadataDynamic or something like that. Then, the connector's pojos can annotate the map of dynamic fields with that annotation. Then, Studio/Devkit can scan for that annotation and automatically generate instrospection Medatata for that pojo, so that the metadata provider can only worry about custom types. This annotation should also be used to leverage DataSense in processors using such pojos so that we don't have to make dynamicXXX processors | 13 |
| 221 | STUDIO-3172 | Getting a Null Pointer Exception when building | This project was created using Studio 3.4 SNAPSHOT. Trying this one in 3.4 GA, it builds ok. But when trying it in 3.4 Nightly, i'm getting a NPE. The project is quite big to upload... you can download directly from: https://github.com/mulesoft/kindling2sharepoint | 5 |
| 222 | STUDIO-3176 | Recreate mapping from DataSense | I created a mapping using DataSense. Then, the metadata of the entity was changed. As a user, I want DataMapper to be able to refetch that metadata and re create the mapping | 3 |
| 223 | STUDIO-3180 | Maven project creation (studio:studio) sometimes hangs on Windows | Sometimes when trying to create a maven project in windows, the wizard hangs trying to download the artifacts. I leave a computer all night trying to finish the creation of the project and never ended but I was able to cancel it and execute the same maven goal manually and it worked. | 8 |
| 224 | STUDIO-3181 | DataSense support for properties placeholders | We need to define the experience of how to handle properties placeholder when using DataSense and Connectivity Testing. Work in progress... # *Properties files should be read from*: ** src/main/app ** $MULE_HOME/conf ** <context:property-placeholder location="classpath:.../path/file.properties"/> - this element can be global or a child element of <spring:beans, and the location can be specified as a classpath: reference or as a path to the file. Some examples below: {code:xml} <context:property-placeholder location="classpath:my-mule-app.properties, file:///etc/mule/conf/my-mule-app-override.properties" /> {code} {code:xml} <spring:beans> <context:property-placeholder location="classpath:my-mule-app.properties, classpath:my-mule-app-override.properties" /> </spring:beans> {code} # *UI* ** The table should list all the properties used in the Element Window, that can be use to retrieve metadata or test the connection. I don't think at the time being that there is a need to show properties used listed in another tabs or properties that are not used in these features ** For each item in the table we should display a list of the posible values retrieved from all the properties files. It would be good if we can also show, as in the mockup, the name of the file. ** If we are going to cache the values set by the user using the checkbox we need to define a way to clear the cache, or a way for the user to reconfigure this again. ** The combo should be also editable so that the user can manually write the values that he wants to set. # *Encrypted properties*, documentation [here| http://www.jasypt.org/encrypting-configuration.html] Example of a properties file using encrypted values: {code} datasource.driver=com.mysql.jdbc.Driver datasource.url=jdbc:mysql://localhost/reportsdb datasource.username=reportsUser datasource.password=ENC(G6N718UuyPE5bHyWKyuLQSm02auQPUtm) {code} Even if the value is shown as encrypted we should offer a way to the user to use DataSense and use the correct credentials to retrieve the Metadata. One simple way would be to make the table editable so that the user can manually write the pasword. *Acceptance criteria*: * Metadata and Connectivity testing should work using properties placeholders ${}, those properties files can be located in src/main/app in the $MULE_HOME\conf, if accesible, or the location can be manually specified in the xml using this tag <context:property-placeholder .. />. | 8 |
| 225 | STUDIO-3188 | Editing a Rule: uses New Rule dialog box | When you go to edit an existing Rule in an element mapping the dialog box shows up with the title "New Rule" and the instruction "Create a new XPath Rule". | 3 |
| 226 | STUDIO-3205 | Connections View usability improvements | 1.- When you have a project with multiple configuration files and you are in the connection view in the 'all' tab, all the mflows that have global elements are displayed with the arrow in the left to be expand but the only mflows that shows elements are the ones that have connectors. So, the arrow in the left should be shown only in these mflows, not in the ones that have only beans, transformers or another kind of global elements. 2.- When you are working in a project with several mflow files, when you open a different mflow within the same project, all the arrows in the connection view are collapsed. If I haven't change the project this shouldn't happend. Attached is a project to test these points. | 5 |
| 227 | STUDIO-3212 | Choice control continually losing 'when' predicate on save of project | I am having a very frustrating issue with the Choice controls in my iApp. I have 3 Choice controls in separate flows, and every time I save the iApp to run it, the "when" predicate of the Choice control is lost. I attach my iApp XML to this ticket. This is the a snippet of the XML I am attempting to attach to the Choice control (via the Choice UI, not the XML directly): <choice doc:name="Choice"> <when expression="#[payload < 0]"> <logger message="CREATING NEW PRODUCT" level="INFO" doc:name="Logger"/> <scripting:transformer doc:name="createProductObject"> <scripting:script engine="Groovy"> <![CDATA[println 'BLAH ' + message.getInvocationProperty('catId') Map product = message.getPayload() //String[] catIds = [message.getOutboundProperty('catId')] as String[] //product.put('catIds', catIds) product.put('CatId', message.getInvocationProperty('catId')) return product ]]></scripting:script> </scripting:transformer> <magento:create-product config-ref="Magento" type="simple" set="#[payload.CatId]" sku="#[payload.ProductCode]" storeViewIdOrCode="default" doc:name="createProduct"> <magento:attributes description="#[payload.Description]" short_description="#[payload.Author__c + ' / ' + payload.Publication_Date__c]"> <magento:stock_data qty="#[payload.Inventory__c]"/> </magento:attributes> </magento:create-product> </when> <otherwise > <logger message="UPDATING CURRENT PRODUCT" level="INFO" doc:name="Logger"/> <magento:update-product config-ref="Magento" storeViewIdOrCode="default" doc:name="updateProduct"> <magento:catalog-product-entity ref="#[payload]"/> </magento:update-product> </otherwise> </choice> | 5 |
| 228 | STUDIO-3213 | Debugger halts on phantom breakpoints | When using the debugger, I notice that the iApp continues to halt at breakpoints that I have removed. That is, a breakpoint from a previous debugger session persists in to the current debugger session even when I have cleared the breakpoint and restarted the debugger. I include a screenshot with this issue to show what I am seeing. | 8 |
| 229 | STUDIO-3218 | DataMapper should be easier to execute from a TestCase | Right now it's very difficult to do testing on Studio. You need to override the getStartUpProperties() method and hack your way into the test case picking up grf files. This should work out of the box | 5 |
| 230 | STUDIO-3219 | Separation between test flows and app flows is needed | Right now there's no way of separating testing flows from real flows. I should be able to create mflows that are only for testing and that do not get deployed on runtime. If I go an manually create a config file on src/test/resources, studio would still pick it up and translate it to an mflow. Even if this weren't true, I want to be able to use the visual editor to make my tests | 5 |
| 231 | STUDIO-3220 | It should be easier to load config files when running a unit test | Right now it's very hard to execute a test and load all the xml by processing the mule-deploy.properties like this: @Override protected final String getConfigResources() { Properties props = this.loadProperties("/mule-deploy.properties"); String resources = props.getProperty("config.resources"); String additional = this.doGetConfigResources(); return StringUtils.isBlank(additional) ? resources : resources + "," + additional; } This should all work out of the box | 5 |
| 232 | STUDIO-3221 | Problem with XML validator | Steps to reproduce: 1.- Create a project and add an HTTP endpoint and a Salesforce CC 2.- Open the Salesforce CC, and create a global CC config, leave default values and clic OK in both windows. 3.- Save 4.- Go to global Elementes view and open the CC configuration window Issue: the "Name should be unique" error appears, so Studio is validating the name of the Global CC against the doc:name of the non global elelement. This in a invalid error. | 5 |
| 233 | STUDIO-3233 | Use the value defined in Maven Settings > MAVEN_OPTS when importing a Maven-based Mule Project from pom.xml | MAVEN_OPTS can be used for different things, including activating specific profiles with system properties. Studio correctly uses MAVEN_OPTS at build time but not at import time. | 2 |
| 234 | STUDIO-3238 | When installing a new runtime, the runtime version in all your current projects in the workspace is changed | Steps to reproduce: 1.- Open studio 3.4 and create some examples. 2.- Check the mule-project.xml and the runtime version. 3.- Install a new runtime from the Update Site. Issue: after restarting studio all the runtime version in your projects are changed to the runtime version that you installed. | 5 |
| 235 | STUDIO-3253 | Service registry lookup using a consumer key | The Service Registry lookup message processor should allow for the lookup of service endpoints using a consumer key. This should be done through a new lookup type called 'consumer key' which would accept three fields: "Service ID" "Service Version" "Consumer Key" Acceptance tests is that user is able to configure a consumer key lookup, then using a consumer key generated from the registry execute the lookup, successfully get the matching endpoint(s), and perform the invocation. | 5 |
| 236 | STUDIO-3254 | APIkit Studio project creation wizard for new model | The APIkit updates for Mule Studio should be updated to use the new APIkit model. Acceptance for this story is the demonstration of the existing (as per private beta 2 version) of the APIkit Studio support but using the new APIkit model. Additionally, a user friendly editor for the new language/markup of choice for APIkit (looking like it will be YAML) should also be incorporated into Studio with auto-complete of elements within the editor. | 8 |
| 237 | STUDIO-3259 | Support SCM merge | Studio Mule projects should be more team collaboration friendly. Today the main issue is related to merging mflow file. http://corp.wiki.mulesource.com/display/STUDIO/Studio+project+refactor+-+SCM-mflow+related+tasks | 5 |
| 238 | STUDIO-3260 | Studio support for new OAuth configuration | As a Studio user, I will like to have support for the new OAuth configuration. Studio editors should support generating the improved user experience XML. | 2 |
| 239 | STUDIO-3262 | DataSense for SAP | Need to support the XML data model for SAP. | 5 |
| 240 | STUDIO-3263 | Move popup property editors to bottom window to be consistent | Move all editors as property editors (they no longer should be pop ups) Steps: * Merge with develop branch * Test / Analyze DataSense Support * Do UX tests | 5 |
| 241 | STUDIO-3265 | APIkit 0.2 causes DataMapper issues | I installed APIkit 0.2 and now when I define a datamapper processor, the config does not get created and the MP does not point to a config. The grf file does get created. I also cannot define a lookup table on any existing grf file anymore | 3 |
| 242 | STUDIO-3267 | Update Salesforce Connector to support Queries | Update the SalesForce Cloud Connector to support the new DataSense query model. | 5 |
| 243 | STUDIO-3266 | Basic Query Editor | Mockups: corp.wiki.mulesource.com/display/WP/Connector+Query+Model Acceptance criteria: * Can select object to query * Can select fields to query * Generated connector query displayed * 2 way editing between XML and UI * Use case 2a * An error message should be displayed if zero fields are selected See also STUDIO-2825 & STUDIO-2826 for more advanced criteria. | 13 |
| 244 | STUDIO-3269 | Update Salesforce Connector to support Paging | Update Salesforce connector to support new paging model. * queryAll/queryMore become deprecated * query uses queryAll/queryMore underneath the covers * Must be able to specify the batch size * Limit/count can still be used, if there are multiple pages, it'll still auto page within those limits ? | 5 |
| 245 | STUDIO-3272 | Define DataSense Query Model | We need to: * Define DataSense Query Model * Provide Mockups * Provide Estimates for Query DataSense Model | 3 |
| 246 | STUDIO-3274 | Maven - Studio should provide a way to see the logs of the studio:studio executions to check what went wrong if something failed | Currently if studio:studio failed to run, the user needs to go to the command line and run it themselves in order to see what is going wrong before fixing it. As a developer using maven, i want to see the maven output of things being executed in a console, so that I can control/troubleshoot the execution. | 3 |
| 247 | STUDIO-3275 | Maven - there is no feedback or indication if studio:studio failed to run (when running in the background) | As a developer using maven, I want to be notified if my project's classpath is not up to date with my pom because studio:studio not being able to run. | 3 |
| 248 | STUDIO-3276 | SCM - Generate a simple .gitignore file with the project at the moment of creation | We should ignore the /flows folder by default. | 3 |
| 249 | STUDIO-3278 | SCM - Polish the "mflow-less" experience | Actually when you import/open a project, only one of the mflows is generated Evaluate the implicances of starting off with no mflows (check out project and open it in studio) | 8 |
| 250 | STUDIO-3279 | As a Studio Developer, I want to be able to contribute sections to the New Mule Project wizard | TBD | 5 |
| 251 | STUDIO-3283 | Remove old plugin files after updating Studio through an update site | When updating Studio through the update site mechanism (Cloud Connectors or Studio components) the old plugins are kept. This makes the installation size grow a lot. For example after upgrading from 3.4.0 to the may 10th release the installation grow up to 730 MB! Remove this old plugin files. | 8 |
| 252 | STUDIO-3285 | Metadata in Dynamic Lookup should only be displayed when lookup type is "Service" | On the Anypoint Service Registry component, the Endpoint Metadata should only be displayed when the Lookup Type selected is "Service". | 2 |
| 253 | STUDIO-3288 | CE JDBC connector changing to EE JDBC when editing graphical mode | When using CE runtime and having a CE JDBC connector, if the user edits something in the Flow View and goes to the XML the CE JDBC connector now is a EE JDBC connector. To reproduce: - Create new CE project - Paste the following XML and Save: {code} <?xml version="1.0" encoding="UTF-8"?> <mule xmlns:jdbc="http://www.mulesoft.org/schema/mule/jdbc" xmlns:smtp="http://www.mulesoft.org/schema/mule/smtp" xmlns:mulexml="http://www.mulesoft.org/schema/mule/xml" xmlns:file="http://www.mulesoft.org/schema/mule/file" xmlns:quartz="http://www.mulesoft.org/schema/mule/quartz" xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:spring="http://www.springframework.org/schema/beans" version="CE-3.4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd http://www.mulesoft.org/schema/mule/quartz http://www.mulesoft.org/schema/mule/quartz/current/mule-quartz.xsd http://www.mulesoft.org/schema/mule/jdbc http://www.mulesoft.org/schema/mule/jdbc/current/mule-jdbc.xsd"> <spring:beans> <spring:bean id="jdbcDataSource" class="org.enhydra.jdbc.standard.StandardDataSource" destroy-method="shutdown"> <spring:property name="driverName" value="com.ibm.db2.jcc.DB2Driver"></spring:property> <spring:property name="url" value="jdbc:db2://appsdvdb.newpig.com:50000/speeddev"></spring:property> </spring:bean> </spring:beans> <jdbc:connector name="jdbcConnector" dataSource-ref="jdbcDataSource" pollingFrequency="10000" doc:name="JDBC"> <jdbc:query key="selectLoadedMules" value="SELECT * FROM MCSITEM"></jdbc:query> </jdbc:connector> <flow name="Database_ExampleFlow1" doc:name="Database_ExampleFlow1"> <quartz:inbound-endpoint jobName="myServiceJob" repeatInterval="60000" cronExpression="0 * * ? * THU" doc:name="Quartz" responseTimeout="10000" repeatCount="2"> <quartz:event-generator-job></quartz:event-generator-job> </quartz:inbound-endpoint> <smtp:outbound-endpoint host="mail1.newpig.com" to="steves@newpig.com" from="Mule Quartz Process" subject="Quartz SQL run test process" responseTimeout="10000" doc:name="SMTP"></smtp:outbound-endpoint> </flow> </mule> {code} - Go to the Flow view and edit anithing by double clickin any component and clicking OK without changing anything. - Go to the XML view - Bug | 5 |
| 254 | STUDIO-3299 | Add copy and paste support of message processors in the visual editor | This feature allows the user to easily copy and paste elements in the studio visual editor. Copy and paste of elements can be performed by two ways: 1- Keeping the Alt key pressed while dragging an element to an specific location, and, when it is dropped, it is pasted. The element is pasted at the drop location. 2- Doing command + C (an element or a group of element must be selected first) and then, in another container, pressing command + V (container is a flow, a scope, or the mule configuration itself). Note that this option of doing copy paste is not as accurate as the first one, since the elements are only pasted at the end of the container. This feature also allows to copy and paste multiple elements. | 13 |
| 255 | STUDIO-3300 | Enum combos are not properly reset when changing operation | The issue can be reproduced with netsuite connector, switching from a addRecord operation to a find Records operation. Select one operation that has an enum as a parameter. Save the configuration. Change to another operation that also has enums, but where the selected option is not present and save the result. Try to start the application: Result: org.xml.sax.SAXParseException: cvc-datatype-valid.1.2.3: 'INVENTORY_TRANSFER' is not a valid value of union type 'SearchRecordTypeEnumEnumType'. Expected: When the user changes the operation...it could just default to the first items of the value, if the option that was previously selected is not in the new list of options. NOTE: The only scenario where the value should be preserved is if the value is a MEL | 8 |
| 256 | STUDIO-3301 | Data Mapper JDBC connection - did not recover on its own | If for some reason, app experienced connection issue with database, DataMapper cannot refresh connection even after everything has recovered. | 13 |
| 257 | STUDIO-3306 | The consumer key of the dynamic element should only be shown in versions above 3.4 | We need to add some validation which apply to the dynamic element and the UI for its attributes. The UI of this element will be tied to the version of the runtime that is being used, so the consumer key stuff will be shown just when you are using a 3.5 ESB runtime but they should not be shown when using 3.4.0. | 1 |
| 258 | STUDIO-3309 | Update third party licence document | Update third party licence document We need to review our current list of 3rd party libraries (https://docs.google.com/a/mulesoft.com/spreadsheet/ccc?key=0AtuXBVwHpOTddEF6OVNCeDl0eDRjZXkxN0ZvQ01Qb3c#gid=17) and revised as follows: Include only libraries that are packaged with the product. For example, we list the MySQL driver, but it is actually not packaged with the product. Review libraries licensing and identify cases where only an GPL license is available - if any. Clean-up libraries that are no longer needed. Update public doc page accordingly. Place content in Bloomfire and maintain going forward. | 5 |
| 259 | STUDIO-3312 | Start, stop and execute polls via debugger | Mockups: http://corp.wiki.mulesource.com/display/WP/Poll+2.0 | 5 |
| 260 | STUDIO-3313 | Define scope name for record based processing | Since we need to add in a record-level exception strategy and summary report for processing batches of records, we need to decide whether or not we need a new element or for-each for that. | 2 |
| 261 | STUDIO-3314 | Properties editor DataSense integration | Define and implement how DataSense expirience will be with the new properties editor. | 8 |
| 262 | STUDIO-3316 | How to show help in properties editors | How will documentation/help be integrated with properties editors. | 5 |
| 263 | STUDIO-3317 | Finish QueryBuilder UI | Mockups: http://corp.wiki.mulesource.com/display/WP/Connector+Query+Model Acceptance Criteria: * No extra vertical layout space * No icons for accounts & fields * Field type is shown in field list (see mockups) * Field list is not shown if the connector does not support editing fields * Selecting a field blocks other UI actions in the form until the field metadata is loaded (see mockups) * All field lists are alphabetized * Filters ** Entering in a String results in DSQL with quotes around the string value ** It should be possible to put in an expression into any field ** Only the operators that the connector supports and that are applicable for the fields show up (based on the connector metadata) * If DataSense query is not parseable (invalid format), then display a message describing the error (see mockup) * If the DataSense query is unsupported by the GUI editor (i.e. it has OR expressions), then display the message "The current query has operators that are not supported by the visual editor. Editing this query will cause your current query to be lost." | 8 |
| 264 | STUDIO-3318 | Adapt Studio metadata model to support caching individual types for connectors. | Studio currently stores metadata at the operation level. CC->operation->types. We need to store the type information at the connector level so we can easily use it for query builder and the 'Select Metadata Object' feature. | 5 |
| 265 | STUDIO-3319 | Fix Studio classloader issue when mule-common depends on another library. | There is a problem in the way Studio is handling the mule-common classloader and its dependencies in order to use the Service the esb provides to interact with the Mule instance for DataSense. We need to fix this classloader in order to support the new version of mule-common that includes a dependency with antlr. | 5 |
| 266 | STUDIO-3331 | Studio should store/read correctly the cloud connector versions (assuming multiple plugins available for one cloud connector) | We need Studio to store/read correctly the cloud connector when adding/reading it to/from the class path. | 5 |
| 267 | STUDIO-3332 | Studio should choose accordingly among more than one suitable connector for a given runtime | Studio to choose accordingly among more than one suitable connector for a given runtime (case: 2 connectors, one 3.3+ and another one 3.4+, and we have a 3.5 runtime) | 5 |
| 268 | STUDIO-3333 | Improve message flow outline | A new outline with a tree structure will allow easier visualization and navigability of the mule configs. Expected features: *filter *go to selected element on double-click or enter key | 2 |
| 269 | STUDIO-3334 | wsdl2java is generating POJO:s without setters | When using the wsdl2java feature in studio it generates POJOs that are not supported by DataMapper, with missing setters for lists. There is a way around if the objects are generated with maven but it would be great if something similar could be accomplished via the UI. This is a link to how this is done via maven: https://gist.github.com/meiwin/2779731 | 2 |
| 270 | STUDIO-3335 | Response block not working | The Response block is not working. When you drop an element in the response section of request-response block, it should wrap it in a response block and add it in the flow. | 1 |
| 271 | STUDIO-3337 | requireClientAuthentication not recognised as attribute of https:tls-server in https connector | attribute requireClientAuthentication not recognised as being part of https:tls-server.. red line in Studio under attribute. | 2 |
| 272 | STUDIO-3344 | Auto-completion and syntax highlighting of YAML API Speficiation in Studio UI | As an Studio APIkit developer, I would like to have the APIkit YAML editor perform auto-completion and syntax highlighting of my APIkt interface definition. | 13 |
| 273 | STUDIO-3350 | NPE when deleting a project | Steps to reproduce: 1.- Make a clone of the followed project: https://github.com/mulesoft/servicesource-dataloader 2.- Do an Import with maven of the project 3.- After the project is imported, delete the project without deleting the files. Issue: The followed NPE is raised, {code} java.lang.NullPointerException org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor.checkForProjectMove(MultiPageMessageFlowEditor.java:331) org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor.resourceChanged(MultiPageMessageFlowEditor.java:297) org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:261) org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:390) org.eclipse.core.internal.resources.Resource.broadcastPreDeleteEvent(Resource.java:2030) org.eclipse.core.internal.resources.Resource.delete(Resource.java:788) org.eclipse.core.internal.resources.Project.delete(Project.java:344) org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:160) org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) {code} | 1 |
| 274 | STUDIO-3355 | Definition element in SAP gets duplicated | When defining the embedded XML template inside the SAP outbound endpoint, on each change, moving from Graphical view to XML view will duplicate the child element. | 2 |
| 275 | STUDIO-3361 | Support POJO based query builders | Acceptance criteria: * Works with at least one POJO based connector. | 5 |
| 276 | STUDIO-3362 | Native queries with query editor | Acceptance Criteria: * User can edit the native query and select the query object type for propagating through the flow * If native query is selected, then the edit query button is not available * If the user has already entered in a DataSense query, the native query must be generated from it, it does not need to work the othe rway around | 8 |
| 277 | STUDIO-3363 | DataSense query editor full text search support | Acceptance Criteria * Need to show it working in conjunction with Google contacts connector * Should be possible to work in conjunction with and without filters. | 5 |
| 278 | STUDIO-3364 | Allow user to set Studio project system properties | As a user, I want to set the system properties needed to start my application whether it's via Run As, Debug As, or DataSense. http://corp.wiki.mulesource.com/display/WP/Studio+and+Environments | 5 |
| 279 | STUDIO-3365 | Deploy to CloudHub sandboxes | As a CloudHub developer, I want to be able to deploy my application to CloudHub sandboxes. Mockups: http://corp.wiki.mulesource.com/display/WP/Studio+and+Environments Sandbox API: corp.wiki.mulesource.com/display/ION/Sandboxes+-+API | 5 |
| 280 | STUDIO-3366 | NPE when importing a project with a missing Message Processor / Cloud Connector | Steps to reproduce: 1.- Look for a project that uses Cloud Connectors not installed in your current version of Studio. 2.- Import the project Issue: as a result, the project is imported but you get the followed NPE {code} java.lang.NullPointerException at org.mule.tooling.core.builder.messageflow.MuleConfigurationXmlGenerator.startMultiSource(MuleConfigurationXmlGenerator.java:751) at org.mule.tooling.core.builder.messageflow.MuleConfigurationXmlGenerator.processCompartmentLane(MuleConfigurationXmlGenerator.java:422) at org.mule.tooling.core.builder.messageflow.MuleConfigurationXmlGenerator.processCompartment(MuleConfigurationXmlGenerator.java:380) at org.mule.tooling.core.builder.messageflow.MuleConfigurationXmlGenerator.processFlow(MuleConfigurationXmlGenerator.java:350) at org.mule.tooling.core.builder.messageflow.MuleConfigurationXmlGenerator.process(MuleConfigurationXmlGenerator.java:87) at org.mule.tooling.core.builder.messageflow.FlowToMuleTransformer.transform(FlowToMuleTransformer.java:43) at org.mule.tooling.core.builder.messageflow.FlowToMuleTransformer.transform(FlowToMuleTransformer.java:52) at org.mule.tooling.core.builder.TransformerUtils.transformFlowFile(TransformerUtils.java:86) at org.mule.tooling.core.builder.IncrementalBuildVisitor$1.visit(IncrementalBuildVisitor.java:51) at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:126) {code} | 3 |
| 281 | STUDIO-3368 | Hide query builder if user disabled DataSense | If user doesn't have DataSense, don't show query builder. | 2 |
| 282 | STUDIO-3369 | Remove icons from lists of accounts and fields | Remove icons from lists in Query Builder | 1 |
| 283 | STUDIO-3377 | In Linux when using Salesforce the sObject type is lost when refreshing the UI | Steps to reproduce: 1.- This is happening in Linux, in Windows and OS X seems to be working fine, so grab a Linux and Studio 2.- Create a project and a flow with and HTTP and a Salesforce connector. 3.- Clic in the Salesforce CC and configure the connector config ref by adding a global Salesforce configuration with valid credentials 4.- Select the Create Operation 5.- Set the Type to Topic 6.- Change the focus of the Salesforce conector, Metadata should be refreshed. Note if you go to the XML the type is added. 7.- In the canvas, clic again over the salesforce CC. Issue: the sObject type was removed, now if you go again to the XML the type is lost. | 3 |
| 284 | STUDIO-3382 | Connectivity Testing Improve error message | If a connector doesn't include a min mule version, when the user runs a connectivity test the error is not very usefull. Test connection failed: Invalid global element. Cannot access the global element to test. java.lang.Throwable | 8 |
| 285 | STUDIO-3385 | handleOutputResultSets should be available on the JDBC-EE connector | The handleOutputResultSets attribute should be available in Mule >3.3.3 and >3.4.0 (see JIRA EE-3093) currently Mule Studio (3.4) marks this as an invalid attribute. | 1 |
| 286 | STUDIO-3391 | Support http static resource handler in Studio | Please add support for HTTP Static Resource Handler to Studio (both GUI and XML). | 3 |
| 287 | STUDIO-3395 | Add new APIkit flow component into Studio | Add a new flow component for APIkit into Studio. This component is similar to an ordinary flow, but it adds two attributes: resource and action. The config XML for this new element should looks like: {code:xml} <apikit:flow name="flowName" resource="/leagues" action="get"> <set-payload value="#[registry:list-of-leagues]"/> </apikit:flow> {code} Besides, a new properties editor must be created for this new flow. | 5 |
| 288 | STUDIO-3396 | Add new Rest Processor element into Studio | The XML config code for the new element must be: {code:xml} <apikit:rest-processor config="pathToAYamlFile"/> {code} | 2 |
| 289 | STUDIO-3403 | Add a new routing strategy in the Dynamic Router | A new routing strategy should be added to the routing strategy combo named: dynamic-round-robin. The configuration is the same as in the other two options: dynamic-first-successful and dynamic-all. The new element will look like: {code} <dynamic-round-robin> .. </dynamic-round-robin> {code} By making the round robin it's own routing strategy, the 'Service Round Robin' checkbox should be removed. | 2 |
| 290 | STUDIO-3410 | Add support for Retina display | Currently fonts are displayed in low-res which does not look good on Macs with Retina displays. The fix is trivial: http://stackoverflow.com/questions/13003511/eclipse-juno-and-retina-resolution | 2 |
| 291 | STUDIO-3415 | Integrate ESB release & Cloud Connectors | Build tasks + QA on integrating release versions of everything into Studio. | 3 |
| 292 | STUDIO-3430 | When you open Studio for the first time you get a part already exists error in the error log | Steps to reproduce: 1.- Build and open Studio 2.- Go to the error log Issue: you get 2 Part already exists error {code} Part already exists in page layout: org.eclipse.ui.console.ConsoleView. Part already exists in page layout: org.eclipse.jdt.ui.PackageExplorer. {code} | 1 |
| 293 | STUDIO-3443 | DataMapper does not release memory | Each time you click on the datamapper mp in the message flow view, the graph is executed, taking (aprox) 50MB ram to do it. The problem is that the memory is never released. Then, you click again, and you have 50MB ram less. You reach a point when studio is consuming 2GB ram, and studio stops working. | 13 |
| 294 | STUDIO-3445 | Add new Router Processor element into Studio | Add new Router Processor element into Studio. This also imply adding a new global element to be referenced by a config-ref. The generated XML config should look like follow: {code:xml} <apikit:config name="router config" raml="/User/home/sample.yaml" consoleEnabled="true" consolePath="console" doc:name="Router"/> <flow name="MainFlow" doc:name="MainFlow"> <apikit:router config-ref="router config" doc:name="Router"/> </flow> {code} Where config is the global config to be referenced by the router element. The consoleEnabled and consolePath attributes contain as default values "true" and "console" respectively. | 3 |
| 295 | STUDIO-3448 | Modify and refactor APIKit plugin | This includes moving the API definition wizard to the RAML editor plugin, removing all Mule dependencies from the wizard, and changes to the generation of all Studio wizards to contribute to a generic perspective. | 5 |
| 296 | STUDIO-3482 | Hide native query editor support | There will connectors that won't support native query language. In these cases DevKit should flag them and Studio should hide/disable the native query textarea. | 5 |
| 297 | STUDIO-3484 | New Properties Editors: when pressing CMD + S or CTRL + S the changes in the editor should be reflected in the file, and the file should be saved | For example when configuring a query this is very annoying, 1.- Open a SFDC CC, 2.- Select the query operation 3.- Configure a query Now, in order to save that query you need first to change the focus of the Message Processor, after that file is updated then you need to save it. Or you can clic in the save icon in the Message Processor, then the file is updated then you need to save it. I would expect to press CMD + S or CTRL + S and all to be saved. The file should be updated and saved. | 34 |
| 298 | STUDIO-3485 | APIKIT: Drag and Dropping apikit router to the flow is breaking the project | After drag and droping apikit router into a project the following error is displayed and no other component can be drag and drop after that. {code} java.lang.RuntimeException: Unknown node definition: http://www.mulesoft.org/schema/mule/apikit/router org.mule.tooling.core.module.MuleModuleManager.getDefinition(MuleModuleManager.java:643) org.mule.tooling.core.module.MuleModuleManager.getDefinition(MuleModuleManager.java:622) org.mule.tooling.messageflow.editpart.CompartmentLaneEditPart.getDefinition(CompartmentLaneEditPart.java:357) org.mule.tooling.messageflow.editpart.CompartmentLaneEditPart.buildResponseModel(CompartmentLaneEditPart.java:284) org.mule.tooling.messageflow.editpart.CompartmentLaneEditPart.buildDisplayModel(CompartmentLaneEditPart.java:177) org.mule.tooling.messageflow.editpart.CompartmentLaneEditPart.getModelChildren(CompartmentLaneEditPart.java:142) org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:762) org.mule.tooling.messageflow.editpart.CompartmentLaneEditPart.refreshChildren(CompartmentLaneEditPart.java:154) org.mule.tooling.messageflow.editpart.CompartmentLaneEditPart.update(CompartmentLaneEditPart.java:106) java.util.Observable.notifyObservers(Observable.java:142) org.mule.tooling.model.messageflow.decorator.EntityDecorator.fireEvent(EntityDecorator.java:69) org.mule.tooling.model.messageflow.decorator.CompartmentLaneDecorator.addEntity(CompartmentLaneDecorator.java:84) org.mule.tooling.messageflow.command.NodeCreateCommand.addCreatedNode(NodeCreateCommand.java:48) org.mule.tooling.messageflow.command.PatternCreateCommand.execute(PatternCreateCommand.java:74) org.eclipse.gef.commands.CommandStack.execute(CommandStack.java:199) org.eclipse.gef.dnd.AbstractTransferDropTargetListener.handleDrop(AbstractTransferDropTargetListener.java:339) org.eclipse.gef.dnd.TemplateTransferDropTargetListener.handleDrop(TemplateTransferDropTargetListener.java:115) org.eclipse.gef.dnd.AbstractTransferDropTargetListener.drop(AbstractTransferDropTargetListener.java:183) org.eclipse.jface.util.DelegatingDropAdapter$3.run(DelegatingDropAdapter.java:211) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) org.eclipse.jface.util.DelegatingDropAdapter.drop(DelegatingDropAdapter.java:209) org.eclipse.swt.dnd.DNDListener.handleEvent(DNDListener.java:90) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4136) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271) org.eclipse.swt.dnd.DropTarget.drop(DropTarget.java:726) org.eclipse.swt.dnd.DropTarget.performDragOperation(DropTarget.java:740) org.eclipse.swt.dnd.DropTarget.dropTargetProc(DropTarget.java:454) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSView.dragImage(NSView.java:150) org.eclipse.swt.dnd.DragSource.drag(DragSource.java:397) org.eclipse.swt.dnd.DragSource$1.handleEvent(DragSource.java:218) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4136) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3982) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3621) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) org.eclipse.equinox.launcher.Main.run(Main.java:1438){code} | 1 |
| 299 | STUDIO-3497 | Add DSQL support for Full Text Search queries | # Design DSQL to represent full text query # Modify Mule Common to support this | 3 |
| 300 | STUDIO-3501 | DSQL should support spaces in field name | *Requirement*: Fields which have a space in the name should be supported (whether it's by convention or other means). An example is Marketo custom fields. | 5 |
| 301 | STUDIO-3502 | Design DSQL changes to support DataSense Query Improvements | Need to create technical specs so that DSQL supports: * Full text search * Selecting all fields when fields selection is not possible (For example using '*', like in SELECT * FROM ...) * Fields which name contain spaces (for example: SELECT a FROM b where [field space] = 10) Goal: Approved spec. | 5 |
| 302 | STUDIO-3503 | Query Builder UI support for non field selection | As a Studio user I should be able to create a DSQL query graphically for cases where field selection is not supported for a type. If field level selection is not supported, then the studio interface should not acceptance it and DSQL should only allow "*" (or whatever definition is made in [STUDIO-3502] as valid field selection. | 5 |
| 303 | STUDIO-3505 | Poll: improve watermark validation | When using watermark in a poll the flow the processing strategy of the flow should be set to synchronous. Studio should validate this. | 3 |
| 304 | STUDIO-3507 | Merge new DataMapper threading model | Merge and test new version of datamapper with new threading model. Use cases: - XML to XML Goal: - Understand improvements of the new threading model Clover provided. - Improve performance on DataMapper - Characterized performance. | 8 |
| 305 | STUDIO-3509 | Spec Hybrid Metadata | Spec out the solution for hybrid metadata connectors: * Netsuite * Zuora This should cover the whole experience from DevKit to Studio/DataMapper | 5 |
| 306 | STUDIO-3513 | Apikit: src/main/api folder is not being imported from previously exported mule projects | When the user imports a mule project, the src/main/api folder with the yaml files are not automatically imported. | 1 |
| 307 | STUDIO-3514 | Apikit: When importing a Mule project with apikit router component the apikit library is not added to the project | When importing a mule project that has an apikit router component in it, studio is not adding the apikit library to the project. | 1 |
| 308 | STUDIO-3522 | Release 3.4.1 | We need to package: * Studio Andes + Bug Fixing * Mule ESB Andes + Latest devkit support patch * Mule ESB 3.4.1 * Latest versions of Cloud Connectors built with latest DevKit * Update site of Studio Andes + Bug Fixing in 3.5 update site | 5 |
| 309 | STUDIO-3527 | Remove JDBC jars from Clover distribution | See private comment for description. | 3 |
| 310 | STUDIO-3529 | tracking:enable-default-events="false" is removed from the flow configuration | If I write tracking:enable-default-events="false" in the xml editor view after saving and moving to the message flow editor, the tracking:enable-default-events="false" is removed. this affects cloudhub users who needs to have tracking:enable-default-events="false" in order to disable flows in event tracking feature. | 2 |
| 311 | STUDIO-3532 | Autodelete attribute get removed from the sftp connector if you edit the flow from the visual UI | Step to reproduce: * Past the following connector configuration {code:xml} <sftp:connector name="sftpConnector" doc:name="SFTP" validateConnections="true" autoDelete="false"/> {code} * Get to the UI view and add anything to the flow. When you go back to the xml the autoDelete will be gone | 1 |
| 312 | STUDIO-3535 | Studio is trying to reach external system for arguments with no dynamic metadata available | Studio is trying to reach external system for arguments with no dynamic metadata available. This used to work in 3.4 but got broken in 3.5-Andes. | 5 |
| 313 | STUDIO-3536 | QueryBuilder dialog has slow refresh | QueryBuilder dialog has slow refresh rate leading to strange behaviour with the list components. | 3 |
| 314 | STUDIO-3539 | AssertionFailedError when using Zuora with QueryBuidler | # Install Zuora connector; # create a connector config-ref with credentials # Select find operation # go to query builder # select Account object You receive the following exception: org.eclipse.core.runtime.AssertionFailedException: null argument: org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:597) org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1011) org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:703) org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1351) org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:391) org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:917) org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:620) org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:820) org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:797) org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:644) org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:768) org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1548) org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:833) org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1532) org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443) org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403) org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) org.eclipse.jface.viewers.CheckboxTreeViewer.preservingSelection(CheckboxTreeViewer.java:416) org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1525) org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:280) org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1690) org.mule.tooling.ui.modules.core.metadata.query.SelectAllFilteredTree.setInput(SelectAllFilteredTree.java:260) org.mule.tooling.ui.modules.core.metadata.query.QueryBuilderInnerEditor$6.selectionChanged(QueryBuilderInnerEditor.java:407) org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:162) org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2188) org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1211) org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1241) org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:239) org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:233) org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:403) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4136) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3982) org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4871) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5241) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1093) org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2052) org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1085) org.eclipse.swt.widgets.Control.mouseDown(Control.java:2538) org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2007) org.eclipse.swt.widgets.Display.windowProc(Display.java:5495) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2102) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2299) org.eclipse.swt.widgets.Display.windowProc(Display.java:5559) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5004) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5153) 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:3618) org.eclipse.jface.window.Window.runEventLoop(Window.java:825) org.eclipse.jface.window.Window.open(Window.java:801) org.mule.tooling.ui.modules.core.metadata.query.QueryCustomEditor$3.widgetSelected(QueryCustomEditor.java:298) org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4136) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3982) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3621) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) org.eclipse.equinox.launcher.Main.run(Main.java:1438) Zuora connector code is under the query branch: https://github.com/mulesoft/zuora-connector/tree/query | 3 |
| 315 | STUDIO-3540 | Phantom errors in Mule Studio project | The attached Mule Studio project (Using 3.5-Andes) shows red cross error indications on the 'get:/teams/{teamId}' flow and a number of other flows. This even though there is no actual errors. Project can be found here: https://docs.google.com/file/d/0B7wrJmCfHowWZlVEU3JQYlVtMEE/edit?usp=sharing | 8 |
| 316 | STUDIO-3614 | APIkit flows can not be visually debugged with Visual Flow Debugger | Using Mule 3.5.0-andes and a flow which is named according to the convention of verb:/path/to/resource and OAuth validators are in use, the Message Processors on this flow can be stepped through with Debugger, but they are not painted graphically so one cannot tell on which Processor the Debugger has stopped. | 3 |
| 317 | STUDIO-3569 | Associate the XML editor with WSDL files | it would be nice that by default WSDL files could be opened with the XML editor instead of the text editor as it is currently. | 2 |
| 318 | STUDIO-3573 | Test upgrade from Studio 3.4 to Studio Bighorn | Test upgrade from Mule Studio 3.4 to Mule Studio 3.5.0-Andes. | 13 |
| 319 | STUDIO-3576 | Refactor Studio framework to support top level elements via Framework XML files. | Refactor Studio framework to support top level elements via Framework XML files. Clean up code regarding flows, subflows and exception strategies. Create the corresponding xml files for these elements. | 8 |
| 320 | STUDIO-3583 | Query Builder: changing the selected type doesn't reset the selected fields | Steps to reproduce: # Open the query builder dialog # Select any type (type1) # Select any field from that type (lets say, Account) # Change the selected TYPE (type2) # Select any field from that other type (lets say, Lead) # Hit OK * Expected: a query with only the latest selected field and type is formed (SELECT Lead from type2) * Actual: a query with both fields is generated (SELECT Account,Lead from type2) | 3 |
| 321 | STUDIO-3593 | SAP Inbound endpoints configures TID handler for sRFC type | When type is srfc, then no TID handler is required in the endpoint configuration (The connector will ignore it) | 2 |
| 322 | STUDIO-3597 | NullPointerException when doing test connection in SAP | NullPointer in method getExternalContributionsFrom of class CoreUtils | 2 |
| 323 | STUDIO-3617 | Integrate Mock cloud connectors to the Studio build | Integrate the new mock cloud connectors to the studio build so that we can develop tests against them and run them through maven | 3 |
| 324 | STUDIO-3621 | Cron syntax support for <poll> in Studio | Support new cron syntax in Studio. See James for mockups. Acceptance criteria: * If editing a <poll> with the old frequency syntax, it should use the new syntax going forward. | 5 |
| 325 | STUDIO-3623 | Re-write tooltips for new watermark feature | The tool-tips for the new watermark are very complex. I propose the following changes: Variable Name: This attribute signals both the object store key that will be used to store this watermark as also the name of the flow variable in which its value will be exposed to the user. NEW: Define the variable name. Default Expression: In case that the key above can't be found in the object store, the default expression is used to generate a value. This is useful in the case of the very first poll. NEW: Define where the poll should start. Update Expression: The result of this expression will be used to update the watermark once the execution is finished. NEW: Updates the watermark expression after the poll runs. (OPTIONAL) Object Store: A reference to the object store you wish to use to store the watermarks. If not provided, the default object store will be used. NEW: Specify an object store other than the default. (OPTIONAL) | 1 |
| 326 | STUDIO-3624 | Service auto-discovery studio behaviour | As a Studio developer, I would like to be able to use the Service auto-discovery feature of the Anypoint Service Registry as follows: - Be able graphically configure the service configuration information as a global element by configuring it through the global element tab. - Be able to configure, through the XML tab, any ASR supported inbound endpoint with a <sr:auto-register-as> element. Any Mule flow configured as such should work withouth errors or unkown elements showing as I switch back and forth between the Studio XML and graphical views. | 8 |
| 327 | STUDIO-3677 | APIkit example name, description | - Think through and come up with a good name and description for the APIkit project example. | 1 |
| 328 | STUDIO-3633 | Double metadata fetching in Query Builder editors | While creating a DSQL query, if you drag from a type (in the Types list) and drop into another element from the same list, two progress bar will be shown, instead of just only one. It seems like is trying to fetch the same metadata (for that specific type) twice. | 5 |
| 329 | STUDIO-3641 | ASR Scenario2 file for 3.4.0 does not open in Andes version of Studio even when set to 3.4.0 runtime | This file: http://mulesoft-public.s3.amazonaws.com/examples/scenario2_R2.zip works fine in my old installation of Studio 3.4.0. (To open it, you have to unzip it first and then import it as a Mule project from external location.) When I try the same thing on my Andes version of Studio, I cannot import this file, even though the runtime is set to 3.4.0 EE. I get the attached error message. | 5 |
| 330 | STUDIO-3642 | Jar files in other projects added to classpath of current project are not exported | If you add to the classpath of the current project a jar file located in other project in the same workspace, it doesn't get exported and an exception is thrown. | 1 |
| 331 | STUDIO-3643 | Drop a Flow ref into a poll scope update the XML but not the UI | If you drop a flow ref into an empty poll scope the flow ref never appears in the UI but it appears in the XML. If you switch to XML change something in the component and then switch to UI again the element appears normally. | 5 |
| 332 | STUDIO-3651 | Query builder: ability to browse and select the single fields inside each pojo | The user should be able to select individual fields of pojo fields in the query builder resulting in SELECT PojoName.FieldName from type. Also the user should be able to select the whole pojo resulting in SELECT PojoName FROM type. | 5 |
| 333 | STUDIO-3654 | ConfigurationException thrown when selecting watermark on poll | When selecting watermark on poll, the processing strategy for the flow must be sync, but it isn't so keeps throwing configuration exception. The solution should be set the flow as sync when the watermark option is selected. | 5 |
| 334 | STUDIO-3656 | Add support in Studio to allow the contribution of external folders to export and import wizards | These days, import and export wizards jobs only manage mule projects folders. That's, the static folders that a mule project has. As an Studio developer, I would like to have the possibility to contribute folders (i.e. src/main/api folder) to a project structure from an external plugin, and those folders should be included when a project is imported or exported. | 5 |
| 335 | STUDIO-3662 | When importing a project from zip and choosing an ESB runtime different than the one in the project, the runtime is inconsistent | Steps to reproduce: # Create a project with X runtime # Export it to deployable archive # Import it back again, using Y runtime * The project ends up having an ESB Runtime with the name of Y, but with the jars of X | 2 |
| 336 | STUDIO-3667 | create a new project from a template lets you create an empty project without ends the wizard | -open the new project wizard (file->new -> new Mule Project) -write a project name and a description -select the "create project based on a existing template" checkbox -change the selected runtime the template selection is lost and the wizard lets you finish it or go to next without a template selected. This generates a valid empty project without configurations. | 3 |
| 337 | STUDIO-3668 | APIKit 'Generate Flows' option improvements | The Generate Flows option of APIkit in Studio should appear as an option both on the top level project folder as well as on individual RAML files. When the top level project folder is selected, then all of the RAML files in the project should have their flows generated. Furthermore, the option should appear within an 'APIkit' sub-menu and not as a stand-alone option within the main selection menu. | 5 |
| 338 | STUDIO-3669 | Pre-populate the options of the APIkit router when only a single option exists | As a Studio designer, when configuring the APIkit router through the Studio wizard, I would like to have all of the fields (method, flow, resource, and any other that may apply) pre-populated with their value when only a single possible value exists. | 3 |
| 339 | STUDIO-3671 | Service auto-discovery icon and name in Studio | - We should name the global element for Service discovery: Service Auto-Discovery - We should have an new icon which represents an ASR service for this component | 1 |
| 340 | STUDIO-3676 | Return type of native queries is lost when project is reloaded. | Return type of native queries is lost when project is reloaded. The cache information is stored ok, though. | 5 |
| 341 | STUDIO-3695 | Removing SAP libraries does not update mule-project.xml in development environment (running from Eclipse) | Removing SAP libraries does not update mule-project.xml in development environment (running from Eclipse). This is caused by a difference in how the bundles are present in the framework when they are part of the project that is being run. This works well with a built Studio. | 3 |
| 342 | STUDIO-3710 | Use only the selected connector's jars in Connectivity Testing and DataSense | Use only the selected connector's jars in Connectivity Testing and DataSense. Today all the connectors are added to the service classpath, leading to potential jar version clashes and incompatibilities. For example, add only the Salesforce libraries to the classpath when testing connectivity or using DataSense. | 8 |
| 343 | STUDIO-3782 | Studio allows you to create a new project when there is one already present with the same name | When creating a new Mule project, Studio allows you to use a name of another project which is already present on disk (but not in your workspace). Steps to reproduce: 1) Create a new Mule Project and call it "MyProject" 2) Delete this project from the workspace but do not remove the project's contents from your disk 3) Attempt to create a new project with the same name. Mule should at least let you know that another project with the same name is already present in your workspace. | 3 |
| 344 | STUDIO-3797 | Runtime classloader should have the same order as the onprem ESB | Rigth now the order in which we create the server classloader, it is not the same order as the ESB. Currently the plugin.xml file of our runtimes look like: {code} <classpath label="Resources directory" path="mule/data-mapper"> </classpath> <libraryFolder includeInContainer="false" label="Tooling Support" path="mule/tooling/" populateContentsInMavenRepo="false"> </libraryFolder> <libraryFolder includeInContainer="true" label="Boot Libraries" path="mule/boot/" populateContentsInMavenRepo="true"> <inclusion regex=".*\.jar"> </inclusion> <exclusion regex=".*licm-studio.*\.jar"> </exclusion> </libraryFolder> <libraryFolder includeInContainer="true" label="Endorsed Libraries" path="mule/endorsed/" populateContentsInMavenRepo="false"> </libraryFolder> <libraryFolder includeInContainer="true" label="Mule Core Libraries" path="mule/mule/" populateContentsInMavenRepo="true"> <exclusion regex=".*mule-ee-parent-poms.*"> </exclusion> <exclusion regex=".*mule-local-install\.jar"> </exclusion> <inclusion regex=".*mule.*\.jar"> </inclusion> </libraryFolder> <libraryFolder includeInContainer="true" label="Optional Libraries" path="mule/opt/" populateContentsInMavenRepo="true"> <inclusion regex=".*\.jar"> </inclusion> </libraryFolder> <libraryFolder includeInContainer="true" label="User" path="mule/user/" populateContentsInMavenRepo="true"> <inclusion regex=".*mule-tests-functional.*\.jar"> </inclusion> </libraryFolder> <libraryFolder includeInContainer="true" label="Mule Core Libraries (per app)" path="mule/mule/per-app/" populateContentsInMavenRepo="true"> <inclusion regex=".*mule.*\.jar"> </inclusion> </libraryFolder> <libraryFolder includeInContainer="false" label="Mule Addons" path="mule/addons/" populateContentsInMavenRepo="true"> <inclusion regex=".*"> </inclusion> </libraryFolder> {code} We need to order it correctly, but first need to analyze what's the correct order. | 5 |
| 345 | STUDIO-3815 | Improve the dialog when attempting to relaunch a currently running mule application | When a user has a mule app running, they can attempt to start the app again. When they do this, a dialog pops up warning that they "have a running instance of an embedded Mule ESB runtime". It then provides information on how to shutdown the currenlty running server. I propose that we just redeploy the project... | 3 |
| 346 | STUDIO-3818 | New default debugging perspective | This is an improvement for the debugging perspective, this is more like the Java debugging and it gives you visibility of the console and the debugging and the flow and the different files, all at the same time. It's much better when you do poll debugging. | 5 |
| 347 | STUDIO-3832 | The 8K bug: datamapper only process csv headers lower than 8k characters. | when generates the metadata, DM, only can process headers of 8k of lenght. | 5 |
| 348 | STUDIO-3834 | Controlled Error Policy raised ClassCastException when try to load Mapping Properties | in a mapping, edit the input properties. Change the error policy to Controlled and assign a max errors number. save it. When you try to load again the properties it will throw an Exception. | 5 |
| 349 | STUDIO-3835 | Analyze top level element changes/refactor to support Batch | We need to evaluate and come to a decision whether we are: # Refactoring all top level elements # Adding batch on top of what we have right now # Creating new support for top level elements and only implement batch with the new model | 5 |
| 350 | STUDIO-3836 | Mule ESB Threads are not always stopped | The notification server not always goes down. This will require changes in ESB code. | 5 |
| 351 | STUDIO-3839 | Create Jubula plugin to support new Property Editors | Need to add functionality to be able to test the new editors. Acceptance Criteria: - Running our current test suite with the new plugin | 13 |
| 352 | STUDIO-3843 | Integrate Mock connector to Studio build | Add Mock connector to Studio build. | 3 |
| 353 | STUDIO-3844 | Fix flaky Import/Export Tests | Fix existing tests and add more. | 5 |
| 354 | STUDIO-3845 | Two-way editing tests for all Transports | Create a 2-way editing automated tests for all transports | 5 |
| 355 | STUDIO-3846 | Define the user experience when changing Runtime (downgrade/upgrade connectors) | Offer the user the chance to change all connectors when he changes the runtime. | 2 |
| 356 | STUDIO-3847 | Batch Module Mockups | Close Batch UI mockups | 3 |
| 357 | STUDIO-3852 | Property editor should open for new components dropped into workspace | When a user drops a new component into the workspace, the properties editor should automatically open for the new component. | 5 |
| 358 | STUDIO-3857 | Improve locking in DataSense Caches | Improve locking in the dataSense caches in order to reduce locking because of accesses to the cache. | 8 |
| 359 | STUDIO-3858 | Add a timeout to DataSense related connection threads | Add a timeout to DataSense related connection threads. Add a preference panel to allow configuration of this value. Set the default to 60 seconds. If set to 0 or -1, there is no time limit. | 8 |
| 360 | STUDIO-3859 | "Enable DataSense" connector option not taken into account if the file containing the connector is not saved | If the file containing the connector with the "Enable DataSense" option set to true is not saved, this option is not taken into account and static metadata is used. :( | 3 |
| 361 | STUDIO-3867 | Doc name not been displayed in some cases | When using the "Message Flow" view for developing in Studio, I cannot see the Doc name I've set. For example, I have this code snippet: {code:xml} <objectstore:retrieve config-ref="ObjectStore" key="#[string:#[sessionVars['tenantId']].pollingStatus]" defaultValue-ref="#[string:IDLE]" doc:name="Retrieve polling status"/> {code} But the UI for this processor shows me: "objectstore:retrieve" (Check the image attached for details) | 5 |
| 362 | STUDIO-3877 | Migrate DataMapper performance improvements to Mule 3.4.2 | Merge performance improvements in Mule 3.4.2 | 5 |
| 363 | STUDIO-3879 | Analyze autocompletion for all elements text boxes | Analyze what will take to implement STUDIO-3291. | 13 |
| 364 | STUDIO-3880 | Allow disabling stats collections from Studio preferences | When Studio starts it sends a message indicating this. Users should be able to disable this behavior. | 2 |
| 365 | STUDIO-3881 | Repair Jubula sanity tests and Endpoint tests | Repair Jubula sanity tests and Endpoint tests | 5 |
| 366 | STUDIO-3882 | Create Jubula automated tests for the Services Essential training: LABS 1, 2 and 3 | Create Jubula automated tests for the Services Essential training Labs 1, 2, and 3 | 13 |
| 367 | STUDIO-3883 | New Project Dialog Mockups | Overhaul the new project dialog and improve UX. Also will impact Studio examples. | 2 |
| 368 | STUDIO-3884 | Palette Simplification: Connector/Endpoint Simplification | Brainstorm and propose ways to simplify the current connector/cloudconnector/endpoints framework. | 5 |
| 369 | STUDIO-3885 | Clean up help menu and contextual help | Clean up the Help menu, and tidy up the contextual help | 3 |
| 370 | STUDIO-3888 | Make mule examples compatible with version control (AKA remove the zips) | remove the zips and make it work | 8 |
| 371 | STUDIO-3889 | Batch UI | Implement Batch UI. | 13 |
| 372 | STUDIO-3890 | XML autocompletion for Batch XML component | Add XML autocompletion support for Batch | 5 |
| 373 | STUDIO-3899 | add support for 3.4.2 examples | add support for 3.4.2 compatible examples and make it work | 5 |
| 374 | STUDIO-3917 | improve MEL parser | improve mel parser to recognize fields, method calls, parameters, keywords and regions. In order to improve the proposals | 8 |
| 375 | STUDIO-3922 | Create Mule 3.4.2 runtime plugin | This runtime has the same changes as 3.5.0 so that we can improve Classpath issues. | 3 |
| 376 | STUDIO-3924 | Schema validation filter is missing two attributes | The filter is missing the following two attributes: * errorHandler-ref * resourceResolver-ref The XSD is as follow: {code} <xsd:attribute name="resourceResolver-ref" type="xsd:string"> <xsd:annotation> <xsd:documentation> Reference to a Spring bean that implements <code>org.w3c.dom.ls.LSResourceResolver</code>. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:attribute name="errorHandler-ref" type="xsd:string"> <xsd:annotation> <xsd:documentation> Reference to a Spring bean that implements <code>org.xml.sax.ErrorHandler</code>. </xsd:documentation> </xsd:annotation> </xsd:attribute> {code} | 1 |
| 377 | STUDIO-3929 | Improve "New Project" creation process | Improve new project creation experience through changing the "New Mule Project" wizard. Scope of changes includes: Consolidating wizard steps into one easy screen (excluding the "Java Project" dialogs) Removing example projects Improve deployment runtime selection Default hide the maven specification | 3 |
| 378 | STUDIO-3930 | Add "New Mule Project from Example" wizard | Mule Example Projects are being removed from the "New Mule Project" wizard, and need to find a new home. They will become a new "Mule Project from Example" option in the "New" wizard (under the Mule folder, see mockups for clarification) This entails building a new wizard populated with example project properties. | 3 |
| 379 | STUDIO-3939 | Opening Project in Project Explorer immediately expands folders to expose flow files | When a user double clicks on closed project in the Package Explorer, the project should expand and allow a user to immediately open a flow file. (Currently, user must expand project, then expand the flows file) | 3 |
| 380 | STUDIO-3940 | NPE from preview panel when a mapping to XML fails | *create a mapping from something to XML. *Do it fail for any reason. | 3 |
| 381 | STUDIO-3941 | JSON to Object transformer should have return type on main page | In working with the JSON to Object transformer, I'm finding that it is most useful to have that Return Class in a place that doesn't make it seem weird. The Mapper reference I think might want to have it's own separate tab if people want to use that. IMHO return type is a lot less advanced than a mapper reference. | 8 |
| 382 | STUDIO-3942 | Change the name for Batch containers (input and on-complete) | The new containers names are: * input * on-complete Also, the accept record attribute on the step should be updated (See EE-3494) | 3 |
| 383 | STUDIO-3943 | Integrate Batch with Debugger | As a Studio user I want to debug inside batch components. | 8 |
| 384 | STUDIO-3944 | Add basic DataSense propagation to batch | There should be DataSense propagation inside batch components. This basic propagation should treat the different batch components as a single flow. * The payload for the batch step should be an element of the List in the last block in the input section * The payload for the batch aggregate section should be List of the preceeding component * The payload for the on-complete section will be a BatchJobResult | 5 |
| 385 | STUDIO-3945 | Add support for batch aggregator | As a Studio user I want to use in the UI batch aggregator element. | 2 |
| 386 | STUDIO-3946 | Add support for batch message sources | As a Studio user I want to be able to configure batch message sources. Currently only one-way inbound endpoints will be supported. | 5 |
| 387 | STUDIO-3947 | Batch steps should only be allowed inside batch process scope | Today there is no validation and batch steps can be added in multiple places. This should also be checked during drag&drop. | 2 |
| 388 | STUDIO-3948 | Dragging batch job into canvas should pre-populate with 1 step | Dragging batch job into canvas should pre-populate with 1 step so as to improve usability. | 1 |
| 389 | STUDIO-3949 | Create the step container when a component is drag & droped inside the batch process scope | Create the step container when a component is drag & droped inside the batch process scope | 2 |
| 390 | STUDIO-3950 | Threading profile for batch | As a user I want to configure the threading profile for batch {code} TODO: paste XML snippet. {code} | 1 |
| 391 | STUDIO-3952 | DataSense integration with Autocompletion | Auto completion engine should be able to offer DataSense information. | 5 |
| 392 | STUDIO-3956 | Changing runtime usability improvements | As a user I will like that changing the runtime offer better options to automatically upgrade all connectors. | 3 |
| 393 | STUDIO-3967 | Add set record variable component | Add the set record variable component | 3 |
| 394 | STUDIO-3968 | Add support for new DataSense failure types | For better user feedback we should add two new Failure Types to Common lib and then use it in Studio: * UNKNOWN_METADATA_KEY: When the provided metadata key is invalid or inexistant * NO_DATASENSE_AVAILABLE: When datasense cannot be retrieved or is not supported for a specific configuration (For example OAuth or SAP XML version 1) | 5 |
| 395 | STUDIO-3970 | Create an automatic backup of the Jubula Database in the Amazon S3 | All Jubula automated tests are saved in a Database in a VM on our local sever, create a backup job for this DB | 3 |
| 396 | STUDIO-3972 | Change CloudHub Runtime name to CloudHub Mule Runtime (Dec 2013) | Change the server label for new release. | 1 |
| 397 | STUDIO-3973 | UI improvements to the Connections Explorer view | Improvements that should be made: - Place the toolbar to the right of the search filter. - Align the viewers closer to the filter and the toolbar. - Change the background color of the toolbar and filter's parent so that it will look well in Windows OS. - Change the margins between widgets | 2 |
| 398 | STUDIO-4000 | Upgrade SAP Connector to 2.1.1 | Upgrade SAP Connector to 2.1.1 | 3 |
| 399 | STUDIO-4031 | Add support for new Watermark attributes | Add support for new attributes as defined in: MULE-7113 | 2 |
| 400 | STUDIO-4062 | Studio changes required for ASR rebranding | - Modify the agent configuration screens so that all instances of Anypoint Service Registry are changed to "Anypoint Platform" - Need to change the default URL of the host from *agent-registry.mulesoft.com* to *anypoint-agent.mulesoft.com* - Modify the Anypoint Service Registry component's name to "Service Lookup" within the Studio pallette. Note: Created equivalent Studio story but could not rank it. | 2 |
| 401 | STUDIO-4044 | Input, process records and on-complete section should be vertically aligned | It would look a lot cleaner if the elements in the input, process records, and on-complete section were vertically aligned. See screenshot. | 5 |
| 402 | STUDIO-4051 | [Core Studio] Remove duplicate elements in core.xml | There are many duplicate elements in core.xml Duplicate entry detected! http://www.mulesoft.org/schema/mule/core/async - Please, remove it! Duplicate entry detected! http://www.mulesoft.org/schema/mule/core/flow-ref - Please, remove it! Duplicate entry detected! http://www.mulesoft.org/schema/mule/core/wendpointWithXaType - Please, remove it! Duplicate entry detected! http://www.mulesoft.org/schema/mule/core/message-properties-transformer - Please, remove it! Duplicate global entry detected! http://www.mulesoft.org/schema/mule/core/message-properties-transformer - Please, remove it! Duplicate entry detected! http://www.mulesoft.org/schema/mule/core/message-filter - Please, remove it! Duplicate entry detected! http://www.mulesoft.org/schema/mule/core/message-chunk-aggregator - Please, remove it! Duplicate entry detected! http://www.mulesoft.org/schema/mule/core/messageProcessorChainType - Please, remove it! Duplicate entry detected! http://www.mulesoft.org/schema/mule/core/message-chunk-splitter - Please, remove it! Duplicate entry detected! http://www.mulesoft.org/schema/mule/core/abstract-redelivery-policy - Please, remove it! Duplicate entry detected! http://www.mulesoft.org/schema/mule/core/idempotentMessageFilterType - Please, remove it! Duplicate entry detected! http://www.mulesoft.org/schema/mule/core/idempotent-message-filter - Please, remove it! Duplicate global entry detected! http://www.mulesoft.org/schema/mule/core/abstract-processing-strategy - Please, remove it! Duplicate global entry detected! http://www.mulesoft.org/schema/mule/core/asynchronous-processing-strategy - Please, remove it! Duplicate global entry detected! http://www.mulesoft.org/schema/mule/core/queued-asynchronous-processing-strategy - Please, remove it! Duplicate global entry detected! http://www.mulesoft.org/schema/mule/core/thread-per-processor-processing-strategy - Please, remove it! Duplicate global entry detected! http://www.mulesoft.org/schema/mule/core/queued-thread-per-processor-processing-strategy - Please, remove it! Duplicate global entry detected! http://www.mulesoft.org/schema/mule/core/custom-processing-strategy - Please, remove it! And many nested elements related to object-store. Please remove them, and test that everything keeps working fine. :) Remove it and test that | 5 |
| 403 | STUDIO-4059 | Replace Batch icons with the final ones. | Replace Batch icons with the final ones provided by James Hall. | 2 |
| 404 | STUDIO-4076 | Server definitions don't accept two localIds for different versions | Right now each server loads all definitions and filters when an element is retrieved from the definition. When creating the server definition we need to only add the elements related to that particular server version. This will allow to have two localIds for different servers with different behavior. | 5 |
| 405 | STUDIO-4079 | Element: Multi transaction is not allowed to be child of element VM | Multi-transaction support for VM endpoints was added to Mule ESB in version 3.3.0 When nesting the ee:multi-transaction element inside a VM inbound or outbound endpoint, Studio marks that element as wrong, with the message: *{color:red}Element: Multi transaction is not allowed to be child of element VM{color}* | 8 |
| 406 | STUDIO-4134 | DataMapper: Improve UI for user generated CSV window | Please see attached mockups. | 1 |
| 407 | STUDIO-4137 | Adjust field truncation and default rule expression checkboxes | The checkboxes appear to be mutually exclusive, but don't act that way. Please see attached mockup for guidance on implementation, and ping me with any questions you have. | 5 |
| 408 | STUDIO-4172 | Problem with Undo | Steps to reproduce: 1.- Create a project with 2 flows 2.- Select the 2 flows 3.- Delete them 4.- CMD + Z Issue: you get the followed exception {code} java.lang.IndexOutOfBoundsException: Index: 2, Size: 1 java.util.ArrayList.add(ArrayList.java:367) org.eclipse.gef.editparts.AbstractEditPart.reorderChild(AbstractEditPart.java:965) org.eclipse.gef.editparts.AbstractGraphicalEditPart.reorderChild(AbstractGraphicalEditPart.java:878) org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:776) org.mule.tooling.messageflow.editpart.MuleConfigurationEditPart.update(MuleConfigurationEditPart.java:79) java.util.Observable.notifyObservers(Observable.java:142) org.mule.tooling.model.messageflow.decorator.EntityDecorator.fireEvent(EntityDecorator.java:71) org.mule.tooling.model.messageflow.decorator.MuleConfigurationDecorator.addFlow(MuleConfigurationDecorator.java:39) org.mule.tooling.messageflow.command.DeleteFlowCommand.undo(DeleteFlowCommand.java:31) org.eclipse.gef.commands.CompoundCommand.undo(CompoundCommand.java:173) org.eclipse.gef.commands.CompoundCommand.undo(CompoundCommand.java:173) org.eclipse.gef.commands.CommandStack.undo(CommandStack.java:395) org.eclipse.gef.ui.actions.UndoAction.run(UndoAction.java:94) org.eclipse.jface.action.Action.runWithEvent(Action.java:498) org.eclipse.ui.actions.RetargetAction.runWithEvent(RetargetAction.java:230) org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119) org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Display.filterEvent(Display.java:1074) org.eclipse.swt.widgets.Display.sendEvent(Display.java:4135) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1495) org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1491) org.eclipse.swt.widgets.Canvas.sendKeyEvent(Canvas.java:497) org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1060) org.eclipse.swt.widgets.Display.windowProc(Display.java:5587) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) org.eclipse.swt.internal.cocoa.NSResponder.interpretKeyEvents(NSResponder.java:68) org.eclipse.swt.widgets.Composite.keyDown(Composite.java:587) org.eclipse.swt.widgets.Display.windowProc(Display.java:5497) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2102) org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2299) org.eclipse.swt.widgets.Display.windowProc(Display.java:5559) org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5004) org.eclipse.swt.widgets.Display.applicationProc(Display.java:5153) 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:3618) org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) org.eclipse.equinox.launcher.Main.run(Main.java:1438) {code} | 5 |
| 409 | STUDIO-4191 | Typo: DataMapper error message | Please fix the "required" typo in the datamapper error list window. See attached screenshot for location. | 1 |
| 410 | STUDIO-4192 | Cloud Connector: Deselect all default operations | By default every cloud connector has an operation selected, which often presents errors to users before they configure the operation. Users frequently get distracted by the errors and it causes friction. Please set the default operation to a simple grey message: "Please select an operation" and hide any and all operation info until the user has selected an operation. Mockups at http://corp.wiki.mulesource.com/display/WP/Configuration+Reference#ConfigurationReference-OperationDefaultSelection | 13 |
| 411 | STUDIO-4197 | DataMapper: Capitalize "File (N)ame:" | Capitalize "N" in "File name:" in the first screen of DataMapper. (See attached screenshot) | 1 |
| 412 | STUDIO-4207 | Propagation rules for properties | As a Studio user I want message properties, other than payload, to be propagated through the flow. | 5 |
| 413 | STUDIO-4208 | DataSense support for message properties | The DataSense Model should be extended to support metadata for message properties and variables (Today there is only support for payload) | 5 |
| 414 | STUDIO-4209 | DataSense support for enrichers | As a Studio user I will like to have an enricher changing the datasense model. We will need to define the rules for this, and what expressions at target level can be parsed to determine the destination of the metadata type. | 5 |
| 415 | STUDIO-4211 | onUnaccepted not available for idempotent-message-filter in studio | Support for onUnaccepted in idempotent-message-filter was added in #MULE-6556 However this attribute does not show up in the component properties when editing a idempotent-message-filter in the MuleStudio. Neither does it show in the auto completion. However the follwoing is still valid code and works as expected when executed: {code} <idempotent-message-filter onUnaccepted="DLQFlow" storePrefix="test" idExpression="#[payload]" doc:name="Idempotent Message"/> {code} | 5 |
| 416 | STUDIO-4215 | Define MVP for Mule Labs | Define MVP for Mule Labs | 3 |
| 417 | STUDIO-4216 | Design Web Services Consumer | This requires # Defining Stories and Dependencies # Close MVP # Create Mockups | 5 |
| 418 | STUDIO-4217 | Create Web Services Consumer Editor (UI) | As a user I will like to configure Web Services Component through Studio UI. * be able to discover a WSDL on my filesystem * be able to type in a URL for a WSDL * be able to choose the service, port, operation (based on WSDL) rather than type them in. * Have the service address automatically populated based on port that is chosen * Clearly see errors caused by invalid WSDL or WSDL not found. | 8 |
| 419 | STUDIO-4227 | DataMapper: Deleting a filter in visual map leaves the folder collapsed | There is an issue with Datamapper's filtering. Steps to recreate: 1. Set up a DM mapping (doesn't matter what you're mapping) 2. Start typing a filter (either the input or output, doesn't matter), but ensure that your filter will have a result 3. Delete the filter. 4. Notice how the folders are still collapsed. It would be ideal if the folders were expanded after deleting the filter. | 5 |
| 420 | STUDIO-4230 | File Endpoint: Change the "Output Pattern" field title | A number of users have experienced friction understanding where to specify a file name in an outbound endpoint. They don't understand that "output pattern" is a valid location to specify the name. I propose we change the title to "New File Name" (***I anticipate that my suggestion is not the best option, but I just want to throw it out to get a dialog started. Please feel to participate in the conversation through the comments.***) | 2 |
| 421 | STUDIO-4240 | Support synchronous UntilSuccessful | In Dolomite, the until-successful component was enhanced with a synchronous mode. Enhance the componen so that: * It has a synchronous attribute which defaults to false * It has an optional threading-profile element | 5 |
| 422 | STUDIO-4242 | Change operation in salesforce connector does not change correctly the parameter | When using the SFDC connector and using the Query operation (which has Datasense) and choosing DataSense query language, everything works fine. Now if I change the operation from Query to Query Single (having previously save the use of the operation Query), the parameter of the operation which is name "query" starts with dsql. Now if you leave it like this when the Query Single operation receives the parameters will fail for it does not understand the prepended "dsql:". Please check the attached immages | 13 |
| 423 | STUDIO-4243 | Anypoint Studio: Design new splash screen | James will work with Chris Payne to get a new "Anypoint Studio" splash screen designed. | 5 |
| 424 | STUDIO-4245 | Support for new scatter-gather component | Add support for the scatter-gather component defined in MULE-7207 * Support all the child elements and attributes for scatter-gather * Should work in debugger * Metadata should propagate left to right through scatter-gather * Metadata should be unknown after scatter-gather * Follow mockups: http://corp.wiki.mulesource.com/display/WP/Miscellaneous#Miscellaneous-ScatterGather | 5 |
| 425 | STUDIO-4246 | [DM] Support root abstract types | When Root Type is an abstract type user should input what implementation Type want to use. | 8 |
| 426 | STUDIO-4248 | [DM] Support Abstract types Dynamically | If there is an Abstract Types user may want to create different implementation based on the input type. The implementation will be picked at runtime. Implementation should support both xsi:type overriding and substitution groups. E.g. User will be able to click on an element and "change type". Then they will be presented with a list of derivative types to choose. | 8 |
| 427 | STUDIO-4250 | Add missing attributes socketMaxWait and connectionTimeout to TCP Connector | In TCP Connector Add attributes *socketMaxWait* since *3.3.0*: {code} <xsd:attribute name="socketMaxWait" type="mule:substitutableInt"> <xsd:annotation> <xsd:documentation> Sets the maximum amount of time (in milliseconds) the socket pool should block waiting for a socket before throwing an exception. When less than or equal to 0 it may block indefinitely (the default). </xsd:documentation> </xsd:annotation> </xsd:attribute> {code} and *connectionTimeout* since *3.5.0* {code} <xsd:attribute name="connectionTimeout" type="mule:substitutableInt"> <xsd:annotation> <xsd:documentation> Number of milliseconds to wait until an outbound connection to a remote server is successfully created. No timeout is configured by default. </xsd:documentation> </xsd:annotation> </xsd:attribute> {code} | 3 |
| 428 | STUDIO-4252 | Rename Mule Studio to Anypoint Studio | Rename Mule Studio to Anypoint Studio. * About Screen * Artifact names * Default installation location * Application name in Mac menu bar * Splash screen Also, find and replace all other text occurrences of "Mule Studio" | 5 |
| 429 | STUDIO-4259 | Use dot notation for all properties in MEL auto-complete | With the upcoming changes in MEL, we can use dot notation everywhere. | 5 |
| 430 | STUDIO-4260 | Adding autocompletion support for properties propagation | Add autocompletion support to flowVars, sessionVars, inbound and outbound properties. Supporting the propagation changes. | 5 |
| 431 | STUDIO-4263 | Repackage new MVEL libraries | Update our MVEL branch with latest MVEL changes. | 2 |
| 432 | STUDIO-4265 | Web Services: Create new icon | Design a Web Services Icon for the Palette and Canvas. | 5 |
| 433 | STUDIO-4282 | DB: Create Update Editor | Create Update Editor | 2 |
| 434 | STUDIO-4283 | DB: Create Delete Editor | Create Delete Editor | 2 |
| 435 | STUDIO-4294 | Must be able to discover a WSDL on my filesystem | Must be able to discover a WSDL on my filesystem so that the consumer can find my service metadata. | 3 |
| 436 | STUDIO-4296 | Must be able to type in a URL for a WSDL | Must be able to type in a URL for a WSDL so that the consumer can find my service metadata | 3 |
| 437 | STUDIO-4298 | DB: Add Metadata support for Insert | Add Metadata support for Insert | 2 |
| 438 | STUDIO-4299 | DB: Add Metadata support for Update | Add Metadata support for Update | 2 |
| 439 | STUDIO-4301 | DB: Add Metadata support for Delete | Add Metadata support for Delete | 2 |
| 440 | STUDIO-4311 | DB: Enable DataSense Normal Datasense propagation | Enable DataSense Normal Datasense propagation | 3 |
| 441 | STUDIO-4313 | DB: Deprecate old Database/JDBC Element | Old Database should be renamed to "JDBC (deprecated)". | 5 |
| 442 | STUDIO-4314 | DB: Add support for transactions | Add support for transactions | 1 |
| 443 | STUDIO-4315 | DB: Create palette and canvas icons for new database elements | Create palette and canvas icons for new database elements | 1 |
| 444 | STUDIO-4316 | DB: Define palette location for new database elements | Define palette location for new database elements | 1 |
| 445 | STUDIO-4338 | Framework: Implement a type/category filter language for describing which elements can exist inside a container | We need to iterate over the existing category/types filtering capabilities that were implemented in the framework for batch (containers). Currently containers can declare which category/types they accept or are accepted in, but only supporting one logical operation per sentence and with no sense of cardinality. These needs are also covered in a lot of other components such as scopes, composite sources, poll, etc. This is currently achieved in a lot of custom ways (with a lot of custom attributes like acceptsOnlyOne, hasMultipleChildren, allowsOnlyInbound, etc) leading to absolute chaos. We aim to build an expression language for building filters similar to regex language which allows to: * use logical operations * use nested sentences with parentheses * declare cardinality * handle types and categories | 8 |
| 446 | STUDIO-4346 | DataMapper: "Generate Default" should provide feedback when successful | When a user chooses to "Generate Default" in Datamapper, feedback should be provided when default generation has completed. See mockups for guidance (notice that the mockups represent a few phases of improvement): http://corp.wiki.mulesource.com/display/WP/Miscellaneous#Miscellaneous-DM%3AGenerateDefault | 5 |
| 447 | STUDIO-4348 | Enable collapsable elements when appropriate (i.e. All, Choice, Scopes) | When having complex flows, MP's like All, Choice and Scopes, clutter the interface too much. Studio should give the option to collapse such items for readability. | 21 |
| 448 | STUDIO-4349 | Studio debugger should generate MEL query when click on element | Studio debugger should auto-generate the MEL Query for the selected element in the "Debugger View". | 13 |
| 449 | STUDIO-4353 | Show Choice branch expression on-hover and allow in-line editing | When working with choice routers, currently its very cumbersome to really know which branch condition does what and we end up going to the XML view every time. It would be nice if we could just hover on top of the branch and studio would show the condition that is being applied for that condition branch. Additionally, would be even better if after clicking on that condition, Studio would let me edit that expression. | 13 |
| 450 | STUDIO-4354 | Show preview of referenced flow when hover on flow-ref | Sometimes (especially when maintaining an application) we need to track what is the application logic. However, when doing flow-refs it can be hard to track where is the referenced flow and then come back again to the calling flow. Thus, it would be nice if we could see a preview of the referenced flow when hovering on top of the flow-ref message processor. | 21 |
| 451 | STUDIO-4356 | Switching from Message Flow view TO Configuration XML view should focus on the corresponding XML element | When working with complex configuration files, we usually need to go back and forth between the graphical and xml view. It would be much more efficient if when switching to the XML view, Studio would automatically focus the XML section related to the graphical active element. | 34 |
| 452 | STUDIO-4358 | Web Service Consumer is not generating right metadata | The metadata that the web service consumer is generating does not represent the entire message of the operation. It Just propagate the first part of the message. | 2 |
| 453 | STUDIO-4365 | Web Services consumer :: In some cases the connection to the WSDL takes too long and there isn't a Cancel option | When attempting to connect to a WSDL and the connection takes too long, there is no way to cancel the operation and Studio does not respond. steps: Add a Web service consumer to the canvas and enter the following url in the WSDL field, or any url for a WSDL with a slow connection http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDL | 3 |
| 454 | STUDIO-4372 | Studio support for OAuth 2.0 Module inclusion in Mule | The OAuth 2.0 module will be merged with Mule EE starting with the Dolomite version (3.5.0-M4). As a user, I want Studio to support this configuration. OAuth 2.0 should appear as an option in the palette OOTB with 3.5.0-M4 and up, and if the user updates the OAuth 2.0 module through the update site, or adds/removes the module from the Mule application, the UI should be consistent with the functionality offered by the module. [~rrinaudo], [~dandiep] FYI. This is the Studio side of EE-3738 | 3 |
| 455 | STUDIO-4374 | Shortcut to switch between 'Message Flow' and 'Configuration XML' views | Switching between both views is very common and a shortcut would really improve that experience. | 8 |
| 456 | STUDIO-4375 | Unify connectors and endpoints across Studio (phase one) | Details here: https://docs.google.com/a/mulesoft.com/spreadsheet/ccc?key=0Ag_HMY-0TfqodGoxWHBfVFNkZ3kxS0FBSEtUQWswMkE&usp=drive_web | 8 |
| 457 | STUDIO-4376 | Rename SOAP to CXF in palette | Rename SOAP to CXF in palette | 1 |
| 458 | STUDIO-4377 | Support DataMapping with no/null payload | As a user, I want to be able to do DataMapping, even if I have a null payload so that I can map my input arguments to my output for creating web service queries. e.g. someone is polling a web service and using the watermark to create the query. | 8 |
| 459 | STUDIO-4380 | WebServices: apply XML changes to our current web service consumer | We need to apply the ESB XML changes to our current editor. Pending: add spec. | 13 |
| 460 | STUDIO-4381 | DB: Polish database editors | Add support for syntax highlight. Make the editor look similar to the one in SFDC Query. Add autocompletion for MEL expressions. Make it look better in general. | 5 |
| 461 | STUDIO-4382 | DB: Add support for connection pooling elements | Add support for connection pooling | 3 |
| 462 | STUDIO-4383 | Metadata Outline Should Support Describe XML Model | In order to make XMLMetaDataModel being display in the Metadata Outline. The object in commons needs to be self descriptive. In order to do this the logic around schema introspection needs to be implemented. | 5 |
| 463 | STUDIO-4384 | Support type grouping for Connectors with DataSense | Support Type grouping for Connectors and DataSense. Integrate with Dev-kit. | 8 |
| 464 | STUDIO-4393 | DB: Add palette search keywords to New Database connector | Add palette search keywords to New Database connector. Make it appear under suggestions when searching for sql, database, mysql, select, insert, etc. | 1 |
| 465 | STUDIO-4442 | DataMapper cannot process large XSD files | When using the XSD file attached in this issue and selecting *Root Element*: TXLife: * Creating the mapping takes very long * Studio runs out of memory {code} java.lang.OutOfMemoryError: Java heap space sun.text.UCompactIntArray.initPlane(UCompactIntArray.java:142) sun.text.UCompactIntArray.setElementAt(UCompactIntArray.java:55) java.text.RBTableBuilder.addOrder(RBTableBuilder.java:324) java.text.RBTableBuilder.build(RBTableBuilder.java:136) java.text.RBCollationTables.<init>(RBCollationTables.java:65) java.text.RuleBasedCollator.<init>(RuleBasedCollator.java:276) java.text.Collator.getInstance(Collator.java:251) java.text.Collator.getInstance(Collator.java:207) com.cloveretl.commons.bean.ListPropertySupport.<init>(ListPropertySupport.java:31) com.cloveretl.commons.bean.ListPropertySupport.<init>(ListPropertySupport.java:38) com.cloveretl.gui.model.GraphMetadata$A.<init>(GraphMetadata.java:731) com.cloveretl.gui.model.GraphMetadata$A.<init>(GraphMetadata.java:731) com.cloveretl.gui.model.GraphMetadata.<init>(GraphMetadata.java:105) com.cloveretl.gui.model.builder.ETLGraphBuilder.a(ETLGraphBuilder.java:302) com.cloveretl.gui.model.builder.ETLGraphBuilder.A(ETLGraphBuilder.java:180) com.cloveretl.gui.model.builder.ETLGraphBuilder.build(ETLGraphBuilder.java:155) com.cloveretl.gui.model.builder.ETLGraphBuilder.build(ETLGraphBuilder.java:147) com.cloveretl.gui.model.builder.ETLGraphBuilder.buildGraphModel(ETLGraphBuilder.java:142) com.mulesoft.mule.datamapper.ui.editor.DataMapperEditor$OpenGraphJob.run(DataMapperEditor.java:453) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} | 8 |
| 466 | STUDIO-4444 | Studio should have smarter validation for property-placeholders | In spring to allow multiple property placeholders, you need to use the attribute *ignore-unresolvable*. If not you get an error that the placeholder variables cannot be found: {code} Test connection failed: Invalid bean definition with name 'MySQL_properties' defined in null: Could not resolve placeholder 'mysql.password' in string value "${mysql.password}" (org.mule.api.lifecycle.InitialisationException) org.mule.common.MuleArtifactFactoryException: Error initializing org.mule.config.spring.SpringXmlConfigurationMuleArtifactFactory.doGetArtifact(SpringXmlConfigurationMuleArtifactFactory.java:203) {code} This is because Spring won't look for another placeholder definition unless the attribute ignore-unresolvable is set. A proper configuration will be that all property-placeholders look like: {code} <context:property-placeholder location="oracle.properties" ignore-unresolvable="true"/> {code} Studio should add a Warning to a config file indicating that there are multiple propery placeholders and that ignore-unresolvable is not set to true. | 8 |
| 467 | STUDIO-4460 | Support MEL auto-complete in choice | Choice should support autocompletion of expressions. | 5 |
| 468 | STUDIO-4462 | Support MEL auto-completion with DataSense query editor | When building conditions for a DataSense query, we should support auto-completion. * Filter values * DSQL/native query language text box | 5 |
| 469 | STUDIO-4466 | Classloader leaks prevention in DataSense | When using DataSense, leak prevention needs to happen around JDBC, Threads, Timers, MBeans, etc. to ensure that the DataSense classloader is garbage collected. | 13 |
| 470 | STUDIO-4471 | Add friendly name and description to DataMapper | A friendly name and a long description are getting added into the metadata model for fields. DataMapper and the payload explorer should use these to represent the payload. Needs mockup. | 34 |
| 471 | STUDIO-4482 | Move New DB connector back to CE Studio | Move New DB connector back to CE Studio | 2 |
| 472 | STUDIO-4484 | Changes in Mule Properties View can't be saved until the view loses focus | When editing fields in the Mule Properties View, in order to save the changes I've made, I need to focus other view for Studio to allow me to save the file. The ideal behaviour would be that it allowed me to save changes immediately after I change a field (without having to lose focus). | 21 |
| 473 | STUDIO-4485 | New Database: Move inner db operation child elements from xxx-sql to xxx-query and template-sql to template-query-ref | Change inner db operation child elements from xxx-sql to xxx-query and template-sql to template-query-ref in accordance with the new xsd changes. | 2 |
| 474 | STUDIO-4493 | Flow Ref: Display name should display name of referenced flow. | When a user selects a flow to reference in a flow ref, the display name should automatically update with the name of the selected flow. | 5 |
| 475 | STUDIO-4506 | Connection explorer: removing a configuration does not update the config reference drop down | When removing a configuration from the Connection explorer, the "config reference" drop down is not updated | 8 |
| 476 | STUDIO-4517 | SubstituableNames on the ESB schema allow property-placeholders but not expressions | Need to review all attributes in Mule XSD files that are defined as *type="substitutableName"* and mark them in Studio as fields that accept: * String literal value * Property Place-holder: ${prop.name} * *DO NOT* accept expressions: #[expr] | 21 |
| 477 | STUDIO-4538 | Connectors: Improve connector version selection | Users often mention that they get annoyed by the "Use newest version of connector?" popup (although they never click the "remember my selection" box)". Please see mockup for details of the improvement: http://corp.wiki.mulesource.com/display/WP/Connectors#Connectors-ChangeConnectorVersion | 13 |
| 478 | STUDIO-4543 | Rename "Documentation" Tab to "Notes" | Please change the name of the "Documentation" tab name to "Notes". This change should be coupled with the connector simplification to minimize the need for new screenshots in Documentation. See attached screenshot for location clarification. * Change Documentation tab to notes * Remove documentation group label right above Description * Remove Description label * Change Flow Use Case to Notes | 1 |
| 479 | STUDIO-4556 | New Database: Problem in the xml merge when changing the operation in the editor | When using the new db connector if you have a configured MP, change the operation in the operator and go to the xml, the xml is not well-formed, resulting in things like: <db:select> <- The new operation in the editor ... </db:stored-procedure> <- The old operation in the editor | 5 |
| 480 | STUDIO-4568 | Don't retrieve metadata if connector isn't configured | We should not try to retrieve the metadata if the required fields on the connector are not filled out. | 5 |
| 481 | STUDIO-4572 | editor view should automatically gain focus when MP is selected | When I select a message processor in the canvas, the editor is opened in the views panel but it doesn't get focus automatically. That means that it takes me two clicks to see the config of any processor which is not a good experience when developing, and also makes it harder to read a flow since I have to be constantly moving the mouse from up to bottom. | 34 |
| 482 | STUDIO-4600 | Properties/variables don't stay expanded when navigating between message processors | As a user, I want my properties and flow variables to stay expanded or collapsed when moving from block to block in Studio. | 8 |
| 483 | STUDIO-4611 | Preference pane cleanup | * Move web service cache settings to DataSense preferences. Should be under the heading "Web Service Consumer" * Authentication tab goes away, see STUDIO-7199 * Remove the API Manager 1.0 tab * Cloud Connectors should be called Connectors (including the text on the preference page) * Maven Settings -> Maven * Move runtimes from main page into runtimes panel (let's discuss to see if there's an easy way to make it link to the update site?) | 3 |
| 484 | STUDIO-4615 | DataSense not available in watermark | See attached screenshot. I have a poll element with a cloud connector that returns a pojo. When I'm writing the watermark expression, DataSesnse should be able to know exactly what the payload is and offer me auto completion capabilities. However, it does not | 3 |
| 485 | STUDIO-4689 | Move add message property to top of properties | The ordering in the message properties transformer isn't according to the most used operations. It should be add first, then delete. This is a usability issue in the pre-sales workshop. | 2 |
| 486 | STUDIO-4690 | Prototype new DataSense experience | Acceptance criteria: * DataMapper retrieval should not block the user (background retrieval) * Refresh button which refreshes object list * Refresh button which refreshes message processor metadata * Optional share metadata between processors * Should create a list of issues which need to resolve to complete this feature | 8 |
| 487 | STUDIO-4691 | Unify connectors and endpoints part 2 | Need to finish implementation of https://docs.google.com/a/mulesoft.com/spreadsheet/ccc?key=0Ag_HMY-0TfqodGoxWHBfVFNkZ3kxS0FBSEtUQWswMkE&usp=drive_web | 8 |
| 488 | STUDIO-4692 | Propagate metadata for record vars | Need to propogate record variable information across batch steps. | 5 |
| 489 | STUDIO-4694 | Add aggregation strategies to global elements | Support creating an aggregation strategy for the global elements. http://corp.wiki.mulesource.com/display/WP/Miscellaneous#Miscellaneous-ScatterGather * Be available in the global elements create tab * Aggregation strategies are show in list/chooser in scatter-gather * Can create/edit strategies directly from scatter-gather | 8 |
| 490 | STUDIO-4695 | Debugger support for record variables | Need to support record variables inside the debugger. | 3 |
| 491 | STUDIO-4701 | Watermark should set flow's processing strategy | Watermark functionality requires the owning flow to have a synchronous processing strategy, which is fine. However, synchronous is not (and should not be) the flow's default. That means that when I put a watermark in a flow and I start the application, I get a deployment exception saying that the flow should be synchronous. This is confusing to the user and requires him to read the logs, find the message, change the flow an try again. It would be great if upon enablement of watermark, studio could automatically set the flow's processing strategy to synchronous. | 13 |
| 492 | STUDIO-4703 | Improve Studio Analytics (KissMetrics) reports to include Studio version and OS | Improve Studio Analytics (KissMetrics) reports to include Studio version and OS. Report url should include: "?version=" + studioversion + "&fullVersion=" + fullStudioVersion +"&os=" + runningOS + "&javaVersion=" + javaVersion | 2 |
| 493 | STUDIO-4718 | Make DataSense combo-boxes searchable | When I'm looking to find an object in Salesforce, I expect that the combo box should be searchable when I start typing so I can quickly find what I'm looking for. | 5 |
| 494 | STUDIO-4734 | There is no general tab to clear application data when running junits | There is no general tab to clear application data when running junits. This complicates the run of, any kind of tests in particular any functional test case that runs an application that relies on OS. Please check attached documents | 5 |
| 495 | STUDIO-4742 | Improve UX of payload/variable/property selection in data mapper | We need to improve the UX as we all agree it's fairly confusing. TBD how exactly to do this. | 34 |
| 496 | STUDIO-4743 | Drag item from metadat explorer and create expression | As a user, I want to be able to drag an item from the DataSense explorer into a text box and have an expression generated for me. Acceptance criteria: * Must work with payload, variables, and properties * Must use "." syntax * Must properly escape properties, i.e. foo.'bar baz' * Must support Maps and POJOs * Must handle things correctly if you drag in an existing expression vs an empty text box * Must support XML - TODO: what's the valid way to do this? | 5 |
| 497 | STUDIO-4745 | Add preference for deprecated message processors | Users should be able to configure whether or not they want to show deprecated message processors. Acceptance Criteria: * If a message processor was deprecated in 3.5, it must be hidden/shown according to the preference in projects 3.5 and above * If a message processor was deprecated in 3.5, it must still be shown in 3.4 * Do the same behavior for XML autocompletion * For new installations, this should be checked by default | 5 |
| 498 | STUDIO-4749 | Push Cascade fixes to update site | * need to document changes and add them to release notes | 3 |
| 499 | STUDIO-4760 | Move endpoint to front of flow | Users have attempted to drag an endpoint from the end to the start of a flow. Studio should allow this action, and throw a warning if settings will be overwritten. Mockups here: http://corp.wiki.mulesource.com/display/WP/General+Improvements#GeneralImprovements-Moveendpointtofrontofflow | 8 |
| 500 | STUDIO-4762 | Navigation: Focus should jump to newly added message processors | When a user adds a new message processor to the flow, the focus should jump to the new MP and information should appear in the Mule Properties View. | 13 |
| 501 | STUDIO-4764 | Allow users to highlight and copy disabled text | Users have attempted to highlight and copy text in disabled fields, which is currently impossible. A recent example is the MySQL Database Config ref. | 21 |
| 502 | STUDIO-4818 | Datasense deadlok when configuring global element first | The problem is that the whole DataSense story is though for users that start adding an endpoint or operation to the canvas and then configuring the global config element. When creating the connector configuration first, users will end up in a deadlock. Steps to reproduce: 1) Start a new project/configuration file 2) Go to Global Element Tab 3) Create a new Salesforce Configuration 4) Configure proper connection parameters 5) Hit "Test Connection" or "OK" 6) As Salesforce Library is still not added to the project, Datasense cannot run because required SFDC jars are not part of the Classpath yet The only way to move forward is: 1) Disable datasense support 2) Hit OK (after ok is done, the SFDC Library will be added to the project) 3) Open the Global Element editor again 4) Enable DataSense, execute Test Connection and click OK to retrieve DS types | 3 |
| 503 | STUDIO-4828 | WSC :: Real world web services and schemas :: Testing | Studio QA - we have some great real world web services and schemas here. Can we get these into the QA plan and test them? Keep in mind that they're confidential. DanD. | 3 |
| 504 | STUDIO-4829 | Testing :: FHIR schemas brought into our QA | FHIR schemas brought into our QA: http://www.hl7.org/implement/standards/fhir/downloads.html | 3 |
| 505 | STUDIO-4837 | Update DM MEL functions to be null safe | Need to update the DM MEL functions so that if the receive null, they also return null. | 5 |
| 506 | STUDIO-4839 | On metadata retrieval failure, give users options | Options should be: 1) Don't retrieve metadata & disable 2) Edit connector configuration 3) Retry | 3 |
| 507 | STUDIO-4840 | Share metadata types across message processors | We should store metadata so we can reuse it across message processors whenever possible so the user doesn't constantly get bombarded with popups. | 5 |
| 508 | STUDIO-4842 | DataSense explorer should support record variables | Need to add support for showing record vars in the explorer. Record vars should be shown all the time. | 3 |
| 509 | STUDIO-4843 | Implement HA flag for performant vs reliable mode | Implement Studio work for EE-3877. See spec in http://corp.wiki.mulesource.com/display/WP/Mule+Cluster+Performance+Profile | 2 |
| 510 | STUDIO-4890 | Upgrade SAP Connector for Mule 3.4.x and 3.3.x to version 2.1.2 | Upgrade SAP connector for Mule 3.3 and 3.4 to be the latest released one. | 2 |
| 511 | STUDIO-4897 | [Usability] [DataSense] Cancelling a Retrive DataSense types operation triggers new retrievals | Cancelling a Retrive DataSense types operation pressing cancel on the dialog triggers new retrievals most of the time. | 5 |
| 512 | STUDIO-4920 | [Palette] Palette's toolbar filter erases the text when hitting enter | When filtering the elements in the palette by adding a filter (lets say "salesf") the components are filtered properly. But if the enter keyword is hit, the complete text disappears, erasing the complete filter. As hitting enter doesn't do anything (as the search was already done while entering the word "salesf"), it would be nice remove the action that erases the input. | 8 |
| 513 | STUDIO-4921 | If user searches for All in palette, suggest Scatter-Gather | With the deprecation/disappearance of the All component, we should suggest Scatter Gather in the palette when a user searches for All. | 3 |
| 514 | STUDIO-4922 | Mel autocompletion should avoid adding quotes when identifiers have valid characters | add variables with names: "foo", "foo1","foo 1" and "foo+a" when autocompletion from "flowVars." should autocomplete: flowVars.foo flowVars.foo1 flowVars.'foo 1' flowVars.'foo+a' | 34 |
| 515 | STUDIO-4924 | Radio Booleans: when changing the radio button, the one previously selected should be disabled and greyed | Check attached screenshot. The component and text under the Update Expression, should be greyed. | 3 |
| 516 | STUDIO-4975 | Generating mappings without isnull for 3.5 and above | Now that DM functions are null safe, we should generate mappings without isnull since it is much more performant. Previous runtimes should still behave the same way as before. | 5 |
| 517 | STUDIO-4978 | Spike: Retrieve DataSense as a background process | Per original mockups, we should update the UI asynchronously as we load metadata in the background. The plan is to divide it into two phases: Retrieve types in the background, then retrieve metadata structures in the background. | 13 |
| 518 | STUDIO-4979 | DataSense: Metadata retrieval is executed twice when using a salesforce query operation | Steps to reproduce: 1.- Configure the global Salesforce connector. 2.- In a Flow add a sfdc Message Processor and set the query operation 3.- Open the query builder and select a type 4.- Select some attributes 5.- Clic ok in the query builder and then save in the Salesforce config Issue: the metadata retrieval is called twice. | 3 |
| 519 | STUDIO-4980 | [Query Builder] UI misbehaving after DataSense type structure retrieval | The Querybuilder UI misbehaves after a DataSense type structure retrieval operation: trying to click on any element is 'delayed' and very confusing for the user. | 5 |
| 520 | STUDIO-5003 | Global Security Module configurations shouldn't be listed under 'Connector Configuration' Category | All the Security Message Processors that have Global elements, have their global elements listed under Connector Configuration, they should have their own category named Security. | 5 |
| 521 | STUDIO-5015 | When replacing production connector with test connector I get a 'name must not be unique' error in studio | When replacing production connector with test connector I get a 'name must be unique' error in studio. This connector name overloading technique is used in 'Mule in Action' (2nd edition) it is harmless since the two versions of the connector are not actually used at the same time. The technique is also very useful. However MuleStudio produces errors if it is used. | 21 |
| 522 | STUDIO-5019 | DataSense doesn't work with mule specific system properties like app.home | If the component to use has references to *mule.home* or *app.home* then DataSense fails with the error in the screenshot. *Element to Test* {code} <sap:outbound-endpoint exchange-pattern="request-response" type="function" functionName="BAPI_CUSTOMER_CREATEFROMDATA1" responseTimeout="10000" definitionFile="${app.home}/sap/customer-createfromdata1.xml" doc:name="Create customer in SAP (Standard BAPI)" evaluateFunctionResponse="true" connector-ref="SapConnector" outputXml="true" xmlVersion="2"/> {code} | 5 |
| 523 | STUDIO-5050 | Global elements :: only available in connector configuration after clicking in canvas | When creating a global element in the connections explorer, it is only available after clicking in canvas Steps to follow: Create a flow with an http and a Salesforce Create a Salesforce global element using the Connections Explorer Save changes Attempt to select the global configuration previously set by clicking in the Connector configuration list ISSUE: the salesforce global configuration does not appear in the list until clicking in the canvas See attached screenshot | 8 |
| 524 | STUDIO-5052 | Poll gives a warning about the payload in DataSense Explorer | See attached screenshot. I think that all message sources should have Payload: None for the input. | 5 |
| 525 | STUDIO-5058 | DataSense for watermark not available inside MPs inside a <poll> | 1. Create a <poll> with a watermark value 2. add a <logger> inside the <poll> 3. Type "#[flowVars." - there will not be a watermark value. | 5 |
| 526 | STUDIO-5065 | Release MUnit Studio plugin beta | Should be based on 3.5-M2. | 3 |
| 527 | STUDIO-5067 | Define plan for removing mflows | Output should be set of JIRAs to plan with for next sprint. | 13 |
| 528 | STUDIO-5119 | When installing the 3.3.3 ESB Runtime all your current project runtimes are changed to 3.3.3 | Steps to reproduce: 1.- In your current workspace with several projects go to the runtimes update site 2.- Select the ESB 3.3.3 Runtime and install it 3.- Create a new project with that runtime. Issue: after rebooting Studio, all the runtimes versions of your project are changed to 3.3.3 | 15 |
| 529 | STUDIO-5124 | ErrorMarkers inside a composite source doesn't show in the correct Message Processor | Steps to reproduce: 1.- Add a composite source 2.- Add 2 Ajax and configure the channel in the second one 3.- Save Issue: the second Ajax MP has the error marker from the first one. Check screenshot | 5 |
| 530 | STUDIO-5132 | [.mflow removal] Remove .mflow files from project editor, generate .mflow model in memory. | [.mflow removal] Remove .mflow files from project editor, generate .mflow model in memory. Need to define project navigator experience. | 13 |
| 531 | STUDIO-5135 | [.mflow removal] Migrate flows, subflows and exception strategies to the Containers framework | [.mflow removal] Migrate flows, subflows and exception strategies to the Containers framework (the one currently used by batch) | 13 |
| 532 | STUDIO-5136 | [.mflow removal] Replace old mflow memory model and update the XML <-> Graphical merge algorithm | [.mflow removal] Replace old mflow memory model and update the XML <-> Graphical merge algorithm. Need to define how this will be accomplished. | 13 |
| 533 | STUDIO-5140 | When the mule project server referenced in mule-project.xml is not present, default to the most recent one. | When the mule project server referenced in mule-project.xml is not present, default to the most recent one. Now, if you install a new runtime (an older one for example) and if the server referenced in the mule-project.xml is not installed, projects will default to that old server. The whole problem is a bit bigger and more complex to fix, but this fix will help greatly minimise it. | 2 |
| 534 | STUDIO-5142 | property element is marked as invalid when used as a child element of imap or pop3 inbound endpoints | *property* element is used to pass extra settings to imap and pop3 inbound endpoints, though Studio is marking those elements as invalid whenever it found them as child elements of that kind of endpoints. The messages shown in each case are: {code} Element: Property is not allowed to be child of element IMAP Element: Property is not allowed to be child of element POP3 {code} | 5 |
| 535 | STUDIO-5156 | Incorrect validation: reference to Unknown global element | Copy and paste the code enclosed in this Jira Save changes In the error panel you can see the following errors: Reference to unknown global element: SFDS_PROD Reference to unknown global element: SFDS Reference to unknown global element: OSAT Edit XML and replace the following: dataSource-ref with mms-dataSource-ref Save the changes Undo changes Save the changes ISSUE: the validation error is not displayed anymore | 8 |
| 536 | STUDIO-5193 | Global references: Connection Explorer is not refreshing the changes of the names | Steps to reproduce: 1.- Create 2 Mule Configuration Files. 2.- In one, create a global salesforce connector 3.- Go to the other one and add an HTTP Connector and a Salesforce 4.- From the salesforce, open the global Salesforce connector and update the Global Name 5.- Save all Issue: the name is not refreshed in the connection explorer. You have one name in the Connector ref and another one in the connection explorer for the same element. | 5 |
| 537 | STUDIO-5205 | DataMapper: Add support for JSON Schema | Add support for JSON Schema in DataMapper Acceptance criteria: * User can select JSON schema as an option for input or output * If JSON schema isn't parseable or the version isn't supported, we should display a clear error message as to the reason why. * Test suite which exercises all data types and structure capabilities of JSON schema NIce to have - support for filtering elements. | 8 |
| 538 | STUDIO-5222 | Mule Studio project specific context menu options displayed on Java and other non-Studio projects context menus | This context menus need to appear ONLY on MuleStudio projects: * DataSense. * Mule Management Console. * Maven Studio Support. * CloudHub. * Apikit. | 15 |
| 539 | STUDIO-5243 | Driver: Display message encouraging user to add driver when it is missing | When a user is missing a driver, show "Please add required driver before proceeding" to the dialog to encourage the user to add the driver. See attached screen for details. | 2 |
| 540 | STUDIO-5245 | Driver: Add "Quick Fix" functionality | Please implement "Quick Fix" in the problems tab for all driver related errors. | 8 |
| 541 | STUDIO-5301 | Spike on shared resources, launcher, and multi-project support | Need to do a spike on the requirements and feasability of multi-project and shared resources support via a new launcher. Acceptance Criteria: * Create spec & mockups for creating a domain and projects which are part of a domain. Should how we will limit domain projects from creating flows. * Create mockups for desired launcher experience which encapsulates: ** single project apps and domain apps ** deploying to a Mule instance in Studio * Get previous launcher code working again * Prototype refreshed UX of launcher * Define how old projects will be run * Define what import/export experience requirements are * Define set of tasks for next sprint * Create draft QA plan for review | 13 |
| 542 | STUDIO-5302 | Spike on RAML consumer | Need to spike on RAML consumer. Acceptance criteria * Mockups around configuring resources from RAML * Mockups around configuring resources without RAML * Prototype including ability to ** GET & POST to resources ** Create a "Connector configuration" * Create next set of tasks * Define experience to configure OAuth for RAML consumer and DevKit * Create draft of QA plan | 26 |
| 543 | STUDIO-5320 | Add support for JSON metadata model | Need to add in support for JSON schema to mule commons. Acceptance criteria: * JSON structure should appear in metadata viewer * DataMapper should recognize inputs/outputs from other connectors that support json schema. * Create a mock connector for json schema for testing & demos | 13 |
| 544 | STUDIO-5327 | [New Launcher] Define outcomes for scenarios when deploying and modifying domains | Write scenarios for domain+app deployment - what is the behavior of domains when modified and deployed? - what is the behavior when an app associated with a domain is modified and deployed? Acceptance Criteria: * Written scenarios * Rough mockups | 3 |
| 545 | STUDIO-5328 | Implement flows using containers | Implement flows using containers | 5 |
| 546 | STUDIO-5331 | Remove all references to the non-container Flow elements | This involves removing all references to the existing Flow elements (NodeDefinition/MessageFlowEntity/EditPart/Figure) | 1 |
| 547 | STUDIO-5350 | [New Launcher] Add applications status feedback | As a studio user I need to know the status of each developed application in the running runtime. Acceptance Criteria: * When application is running, it should be green * When application is not running, it should be grey * When application fails to deploy, it should be red * When it is deploying, it should be yellow | 8 |
| 548 | STUDIO-5351 | [New Launcher] Implement start, stop and redeploy application actions | As a studio user I need be able to start, stop and redeploy a developed application in the running runtime Acceptance Criteria: * Stop/start/redeploy acctions should give feedback while actions occurring (experience TBD) | 5 |
| 549 | STUDIO-5360 | Autocomplete with ENTER in a dialog, closes the dialog | To reproduce the bug: - Add a Custom Business Events to a flow - Double click in the new added component to edit the properties - Add a new property in settings - A dialog to complete the name/value of the property appears - Use the autocomplete (^Space), select a value from the list and hit ENTER Expected behavior: - The selected value from the automcomplete must be added to the text. Current behavior: - The ENTER keystroke it's captured by the dialog, so it closes This video captures the issue: https://docs.google.com/a/mulesoft.com/file/d/0B_zvjpQNtf7IQkIwb21uWUFWM3c/edit | 34 |
| 550 | STUDIO-5372 | Add loading widget when opening Library | When opening library, the user has no feedback that the page is loading. | 1 |
| 551 | STUDIO-5376 | Mule Config Flow Editor marks file as modified just by selecting an item | If I open flow.xml and just select an item within it then studio marks this file as modified even I made there no changes at all. This is pretty annoying. Please see the attached video. | 8 |
| 552 | STUDIO-5383 | [New Launcher] Display server information in header | As a user, I want to see the name of the server that I'm launching, so I have context into what version it is. Acceptance criteria: * Server name and version should be visible in header | 2 |
| 553 | STUDIO-5384 | [New Launcher] Define how new launcher co-exists with old runtimes & launcher | We need to define how new launcher co-exists with old runtimes & launcher. Acceptance criteria: * Written scenarios * Define how we will on-ramp users onto the new experience * Define how users of run configurations will achieve similar capabilities in new experience (e.g. run with HA, system properties, etc) | 3 |
| 554 | STUDIO-5385 | HTTP client request builder | As a user, I want to configure the HTTP message processors to use the request builder Acceptance criteria: * Can configure individual headers, query params and form params * Can configure the <query-params>, <header-params> and <form-params/> | 8 |
| 555 | STUDIO-5386 | HTTP client get/post/put/delete/execute message processors | As a user, I want to configure an outbound HTTP connector to do get, post, put, delete, and execute operations Acceptance criteria: * Two way editing works for the following items in the spec ** Get, post, put, delete and execute operations ** resource ** host and port ** follow redirects ** success and error status codes * If I select "execute" I can input my own HTTP method | 3 |
| 556 | STUDIO-5387 | HTTP client global configuration | As a user, I want to configure my global configuration, including * URL, port, and base path * RAML file Acceptance criteria: * two way editing works for the abovce areas as defined in the spec | 3 |
| 557 | STUDIO-5389 | HTTP client RAML based configuration | As a user, I want to use my RAML to assist in configuring the HTTP connector. Acceptance criteria: * List of resources in the RAML should be visible in the resource field * List of methods which are applicable to that resource should be visible * Should be able to write an expression to override the resource or method * Query, form and header params should be auto-populated from the RAML | 3 |
| 558 | STUDIO-5390 | HTTP client DataSense propagation for JSON schema | As a user, I want my JSON schema to propagate over DataSense when I select an oepration. | 5 |
| 559 | STUDIO-5391 | HTTP client DataSense propagation for XML schema | As a user, I want my RAML metadata to propagate XML schema information over DataSense. | 3 |
| 560 | STUDIO-5426 | [New Launcher] Improve application lifecycle support with new launcher and new runtime view | New projects should appear on the view, deleted projects should be undeployed and removed, etc. Support the whole lifecycle of a Studio project within the view. | 5 |
| 561 | STUDIO-5427 | [New Launcher] Add preference or run-configuration option for ESB agent port. | Add preference or run-configuration option for ESB agent port. | 3 |
| 562 | STUDIO-5430 | [New Launcher] Hook ESB JVM to the running Studio process | Hook ESB JVM to the running Studio process, so that when Studio is closed, the ESB JVM process is automatically killed. This is really needed to avoid having problems with used ports due to hanged processes. | 5 |
| 563 | STUDIO-5435 | HTTP client add support for oauth configuration | As a mule user we need a way to configure and use oauth with my http configuration | 5 |
| 564 | STUDIO-5436 | HTTP client add support for security configuration | Adding support to configure security in the http connector global configuration including SSL configuration and basic authentication | 5 |
| 565 | STUDIO-5437 | [New Launcher] Definition and spike on on Server Run Configuration and experience | We need to define the whole experience of launching applications. Right now when launching the second application it will use the same process of the one that's running. Evaluate a solution like: There is a Run Configuration for each server. In this configuration you can specify all the applications to add to the server. If launching an application outside this list, notify the user and add the application to that server or stop the current server and start over with only this application deployed. | 5 |
| 566 | STUDIO-5438 | Add metadata propagation for JSon by example | As a user using JSon by example in DataMapper I will like that this metadata gets propagated in the flow. | 8 |
| 567 | STUDIO-5481 | mule-deploy.properties should not be modified if the list of config files does not change | Mule-deploy.properties should not be modified if the list of config files does not change. Today, the property with the list of files to deploy is modified each time the server is run or the project exported. In addition, if there is a problem updating this file (it is read-only for example), it should be informed so as the user can decide what to do. This was requested by Intuit. | 5 |
| 568 | STUDIO-5486 | Examples in Library | Please adjust the "example" link on the welcome screen to point to examples in the library. (Library should open with a filter for examples) See attached screenshot for wording and location of link. Acceptance Criteria: # Remove all the Examples from the servers in Studio # Change the Create Example links to open the library and create the example from there. # When Updating Studio the New Example mechanism should be replaced # When creating an example, Studio should set the Server runtime version to the one that comes from the library. From library: # Library should filter examples by server with the information sent by Studio to the library # The user should not be prompt for his information each time that he wants to use an example | 13 |
| 569 | STUDIO-5499 | New Menu: Move Java Project, Project, and Example to "Other" | Please remove the following from the New menu: -Java Project -Project... -Example... They should be available in the the "Other..." window. Please see attached screenshot for details. | 8 |
| 570 | STUDIO-5517 | Datasense dropdown should allow a connector to only show the displayName of the generated keys | When building a connector with DataSense, the dropdown in Studio concatenates the displayName with the ID (between parenthesis). This is handy if for some scenarios, the same displayName is repeated but not the ID (salesforce-connector is one case). But for other scenarios, the ID is probably not necessary. It would be nice to have a way to tell Studio, from DevKit, to only show the displayName for the current connector | 3 |
| 571 | STUDIO-5563 | [HTTP Connector] <listener> and <listener-config> elements | Need to support listener and listener-config elements as defined in the spec. Acceptance Criteria: # UI should follow the mockups # New Message Processor in the palette and in the Global Element # This MP is a Message Source # DataSense support. # Autocompletion in the XML Support # Validation with the xsd | 21 |
| 572 | STUDIO-5576 | Improve Canvas watermark to give better first instructions to the User | We need to improve the Watermark in the canvas to let the user know * Where the message processors are, * That they can be drag and drop in the canvas * That the properties to configure them will be displayed * Where your project files are We would need a mockup for this. | 5 |
| 573 | STUDIO-5586 | Add support for installing library connectors | Studio should open the plugin installation functionality when the user installs a connector listed there. Acceptance Criteria: The user should be able to search for a CC in the library (this should be present in the Library) and open the installation dialog from there and successfully install the CC. This must be tested in Windows, Mac and Linux. This should be tested in Gasher (future Update Site) and Himalaya. | 13 |
| 574 | STUDIO-5587 | [New Launcher] Allow selection of more than one application in a Mule Run Configuration | Run configuration | 5 |
| 575 | STUDIO-5588 | [New Launcher] Allow selection of Mule Domains in a Mule Run Configuration. | Run configuration -When selecting a Mule Domain, all its dependent applications should be selected. | 5 |
| 576 | STUDIO-5589 | [New Launcher] Allow users to select a Mule Server in each Mule Run Configuration | Run configurations | 3 |
| 577 | STUDIO-5590 | [New Launcher] Migrate current run configurations to new ones | Run configurations | 5 |
| 578 | STUDIO-5592 | [New Launcher] Create Mule Domain project | - New Mule Domain action in all places where it should appear - Forbid creation of more than one config file. - Forbid renaming or deleting the mule-domain-config.xml file. Acceptance Criteria: # You can create a Domain project # The Domain XML File should be created by default # You should be able to edit the Domain file with an xml editor # You should be able to add / remove libraries to the project (jar files) | 13 |
| 579 | STUDIO-5593 | [New Launcher] Associate a Mule Project to its parent Mule Domain | As an Integration Developer you should be able to add a Mule Project to a Mule Domain Project so that when running the Domain project all the Mule projects associated with it are run. Acceptance Criteria: # From the mule-project.xml you should be able to specify that a project belongs to a Domain. # The Domain project has no information about which projects belongs to it. # There should be validations if the Domain project is missing or not present. # There is no runtime validation between the Domain runtime and the project runtime, for instance. # When running the Domain Project, the projects within the Domain are run. # The Runtime version from the Domain project is the one that has precedence NOTE: Today this only will work in EE. | 8 |
| 580 | STUDIO-5595 | [New Launcher] Mule Domain projects management : delete - update - change domain parent. | Domain * If domain is renamed, existing projects should reference the renamed domain * If domain is deleted, existing projects should display an error | 8 |
| 581 | STUDIO-5596 | [New Launcher] Package Mule Domain projects | Package the Domain project as it is defined in our documentation: http://www.mulesoft.org/documentation/display/current/Shared+Resources Acceptance Criteria: # This is a sub-task for import / export functionality | 8 |
| 582 | STUDIO-5597 | [New Launcher] Export/Import a Mule Project with reference to a Mule Domain | import/export Acceptance Criteria: # When exporting an application that reference to a domain, the Domain should be exported only with that application. # When importing this application, the Domain should be imported and the application and the reference should be preserved # If the Domain already exists in your workspace, and you import this kind of project, user should be prompt on what to do or not allowed to do it. | 3 |
| 583 | STUDIO-5598 | [New Launcher] Allow to reference elements defined in a Mule Domain from other Mule projects | this includes, validation and showing those elements in combos, etc. Acceptance Criteria: # Editors should be able to refer elements defined in the Domain. # When referencing this elements, there should not be errors in the XML # DataSense is handled in other Jira Note: Test with beans, unknown elements, test what happens when doing "go to reference". | 8 |
| 584 | STUDIO-5599 | [New Launcher] Edit Mule Domain project mule-project.xml file | xml Acceptance Criteria: # You should be able to edit the Project Name and change the runtime from the mule-project.xml in the Domain project | 3 |
| 585 | STUDIO-5601 | [New Launcher] Datasense support in Mule Domain projects | should use domain credentials if they are used in a datasense call. there is a problem with the caches. Acceptance Criteria: # User should be able to do Test Connection, bring Metadata, use the Query Builder using Connectors defined in the Domain. # The message processor should propagate the Metadata. Note: test adding JDBC Drivers to the domain project and use the Connector from the Mule Project. | 8 |
| 586 | STUDIO-5602 | [New Launcher] Classpath management in domain projects | domain Acceptance Criteria: # If the Drivers are hosted in the Domain project they should be accesible from the child projects. # This should support property files # Add Jar files to the domain projects, and use classes from the Jar file in the Child project # Use classes from the Domain in a Unit test in the Child project # Project should depend in Eclipse from the Domain so that the project shares the classpath To test: # Add drivers in both Domain and Child project # Test connection using drivers hosted in the Domain # Test with 3.5.0 and 3.6 # Use several projects depending on the same Domain Lot and lot and lot of testing :( | 21 |
| 587 | STUDIO-5603 | [New Launcher] Debugging support while using Mule Domains | Need to test that everything continues to work fine in debugger when using domains. No development work needed as far as we know. | 8 |
| 588 | STUDIO-5604 | [New Launcher] Debugging support using multi Mule Project applications | Need to test that everything continues to work fine in debugger when using multiple projects. No development work needed as far as we know. Acceptance Criteria: # Add breakpoints to different applications, Start both applications in the same runtime, trigger the application and check that the applications stops in the breakpoints. # Test with Polls in different applications. | 8 |
| 589 | STUDIO-5605 | [New Launcher] Deploy Mule domain applications to the embedded Mule Server. | Deploying a domain application should deploy all its dependant applications. Deploying single projects that depend on a domain should deploy that project and its related domain. Acceptance Criteria: # When running a project that belongs to a Domain, the Domain is run with only that application and not the other applications belonging to the Domain. # When running a Domain project, all the projects belonging to the Domain project are run # This will create a runtime configuration that will be persisted and use the next time the application is executed. | 8 |
| 590 | STUDIO-5610 | [New Launcher] Runtime View launchpad should allow to select/add/edit Mule Run configurations | LAUNCHER / UI changes Acceptance Criteria: # UI should follow the mockups # Instead of showing the Runtimes in the combo box (Runtimes view) the Run Configurations will be displayed. Only the recent ones and manage the same amount that Eclipse does ( ~ 10 ) | 8 |
| 591 | STUDIO-5616 | HTTP Connector - Add OAUTH Support | Add support for Oauth configuration creation Add It references in Request and Listener Components | 8 |
| 592 | STUDIO-5617 | HTTP Connector - Add Support For SSL Configuration | Add Support for SSL global configuration Add Support in Request and Listeners Configurations *It could be defined nested in the Request configuration | 13 |
| 593 | STUDIO-5618 | HTTP connector - Add support for Global Builders Configuration | Add Global Request Builder Configuration support Add Global Response Builder Configuration support It can be referenced from Request Builder | 8 |
| 594 | STUDIO-5619 | HTTP connector - Add support for Response builder | Add support for Response Builder configuration | 8 |
| 595 | STUDIO-5620 | Define packaging for RAML Connector | We need to define wether we are going to use an eclipse plugin or a different kind of packaging to handle RAML Connectors. | 5 |
| 596 | STUDIO-5621 | [New Launcher] Import/Export Mule Domain projects | import/export Check acceptance criteria STUDIO-5597 | 8 |
| 597 | STUDIO-5622 | Show response section in the Flow Container | Show response section in the Flow Container | 13 |
| 598 | STUDIO-5623 | HTTP Connector - Request - double scrolling generate issues to see the parameters | UX improvement. | 8 |
| 599 | STUDIO-5627 | Support back and forth navigation on the Mule Flow Editor. | Support back and forth navigation on the Mule Flow Editor using the back and forth arrows in the toolbar. | 8 |
| 600 | STUDIO-5637 | Add Mule EE 3.4.3 runtime to Studio | Add Mule EE 3.4.3 runtime to Studio * Create the runtime plugin * Run a sanity on top of October 2014 release * Publish to Runtimes update site | 5 |
| 601 | STUDIO-5641 | Add Anypoint Studio version to the About message dialog | Add version to the About dialog so that it can be map to the Jira version of Studio. | 1 |
| 602 | STUDIO-5645 | WS Consumer support for the new HTTP connector | Currently, the ws:consumer-config element has an optional connector-ref attribute, that allows to explicitly set the connector that should be used (from any Mule transport). A new optional attribute "connectorConfig" has been added, that allows to explicitly set a reference to an http:request-config element (from the new HTTP module). Studio should also allow to configure this new attribute. The current connector-ref attribute, and the new connectorConfig attribute are both optional, but mutually exclusive (this is validated at runtime). | 5 |
| 603 | STUDIO-5650 | http response builder generates invalid name/value pair for headers | Anypoint Studio uses a headerName attribute for the HTTP Response Builder component's header element which is not permitted by Mule ESB. If you alter the xml to the name/value pair that Mule ESB is expecting then Studio complains that "Required attribute headerName is not defined in header". {code} <http:response-builder status="200" contentType="text/xml" doc:name="HTTP Response Builder"> <http:header headerName="http.status" value="200"/> </http:response-builder> {code} Logs: {code} ERROR 2014-10-25 12:58:19,140 [main] org.mule.module.launcher.application.DefaultMuleApplication: null org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'headerName' is not allowed to appear in element 'http:header'. {code} | 3 |
| 604 | STUDIO-5657 | Add the verb PATCH to the HTTP endpoint | Studio is currently missing the verb PATCH from the HTTP transport: https://www.mulesoft.org/jira/browse/MULE-5940 | 1 |
| 605 | STUDIO-5661 | java.lang.IllegalStateException: Mule project is null in design context | The error logs shows the following error: {code} ENTRY org.mule.tooling.eventBus 4 0 2014-10-28 17:18:52.876 !MESSAGE Unexpected error. !STACK 0 java.lang.IllegalStateException: Mule project is null in design context at org.mule.tooling.core.MuleCorePlugin.getModuleManager(MuleCorePlugin.java:271) at org.mule.tooling.core.builder.messageflow.NodeDefinitionDisplayNameProvider.getDefinition(NodeDefinitionDisplayNameProvider.java:19) at org.mule.tooling.core.builder.messageflow.NodeDefinitionDisplayNameProvider.handles(NodeDefinitionDisplayNameProvider.java:14) at org.mule.tooling.model.messageflow.DefaultDisplayNameProvider.handles(DefaultDisplayNameProvider.java:41) at org.mule.tooling.model.messageflow.MessageFlowNode.getName(MessageFlowNode.java:92) at org.mule.tooling.messageflow.util.MulePathBuilder$MulePathBuilderVisitor.visitFlow(MulePathBuilder.java:137) at org.mule.tooling.model.messageflow.Flow.accept(Flow.java:35) at org.mule.tooling.messageflow.util.MulePathBuilder.buildPath(MulePathBuilder.java:91) at org.mule.tooling.messageflow.util.MulePathBuilder.load(MulePathBuilder.java:86) at org.mule.tooling.messageflow.util.MulePathBuilder.search(MulePathBuilder.java:64) at org.mule.tooling.messageflow.editor.MessageFlowEditor.updateEntityErrors(MessageFlowEditor.java:463) at org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor$OnValidateFinishedListener.updateErrorMarkers(MultiPageMessageFlowEditor.java:1589) at org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor$OnValidateFinishedListener.access$0(MultiPageMessageFlowEditor.java:1588) at org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor$OnValidateFinishedListener$1.call(MultiPageMessageFlowEditor.java:1581) at org.mule.tooling.messageflow.editor.MultiPageMessageFlowEditor$OnValidateFinishedListener$1.call(MultiPageMessageFlowEditor.java:1) at org.mule.tooling.utils.SilentRunner.run(SilentRunner.java:10) at org.mule.tooling.ui.widgets.util.WidgetUtils$1.run(WidgetUtils.java:98) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438) at org.eclipse.equinox.launcher.Main.main(Main.java:1414) {code} | 1 |
| 606 | STUDIO-5663 | Exception in Mac OSX Yosemite | {code} Error Description: Unexpected error. Error Stacktrace: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:635) at java.util.ArrayList.get(ArrayList.java:411) at java.util.Collections$UnmodifiableList.get(Collections.java:1211) at org.mule.tooling.messageflow.editor.MessageFlowEditor.createNavigationLocation(MessageFlowEditor.java:1013) at org.eclipse.ui.internal.NavigationHistory.addEntry(NavigationHistory.java:366) at org.eclipse.ui.internal.NavigationHistory.markLocation(NavigationHistory.java:214) at org.mule.tooling.messageflow.Activator$TrackableEditPartVisitor.track(Activator.java:285) at org.mule.tooling.messageflow.Activator$TrackableEditPartVisitor.visitEndpointNode(Activator.java:261) at org.mule.tooling.model.messageflow.EndpointNode.accept(EndpointNode.java:126) at org.mule.tooling.messageflow.Activator$1.onEditPartSelected(Activator.java:84) at org.mule.tooling.messageflow.events.EditPartSelectedEvent.dispatch(EditPartSelectedEvent.java:25) at org.mule.tooling.messageflow.events.EditPartSelectedEvent.dispatch(EditPartSelectedEvent.java:1) at org.mule.tooling.utils.eventbus.EventBus$1.call(EventBus.java:194) at org.mule.tooling.utils.eventbus.EventBus$1.call(EventBus.java:1) at org.mule.tooling.utils.SilentRunner.run(SilentRunner.java:10) at org.mule.tooling.utils.eventbus.EventBus.doFireEvent(EventBus.java:176) at org.mule.tooling.utils.eventbus.EventBus.fireEvent(EventBus.java:157) at org.mule.tooling.messageflow.editor.MessageFlowEditor$1.selectionChanged(MessageFlowEditor.java:212) at org.eclipse.gef.ui.parts.AbstractEditPartViewer.fireSelectionChanged(AbstractEditPartViewer.java:247) at org.eclipse.gef.ui.parts.AbstractEditPartViewer$1.run(AbstractEditPartViewer.java:131) at org.eclipse.gef.SelectionManager.fireSelectionChanged(SelectionManager.java:144) at org.eclipse.gef.SelectionManager.setSelection(SelectionManager.java:279) at org.eclipse.gef.ui.parts.AbstractEditPartViewer.setSelection(AbstractEditPartViewer.java:751) at org.mule.tooling.messageflow.editor.MessageFlowEditor$4.call(MessageFlowEditor.java:373) at org.mule.tooling.messageflow.editor.MessageFlowEditor$4.call(MessageFlowEditor.java:1) at org.mule.tooling.utils.SilentRunner.run(SilentRunner.java:10) at org.mule.tooling.core.StudioDesignContextRunner.runSilentWithMuleProject(StudioDesignContextRunner.java:17) at org.mule.tooling.core.StudioDesignContextRunner$1.run(StudioDesignContextRunner.java:45) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4607) at org.mule.tooling.core.StudioDesignContextRunner.runSilentWithMuleProjectInUI(StudioDesignContextRunner.java:41) at org.mule.tooling.messageflow.editor.MessageFlowEditor.reload(MessageFlowEditor.java:358) at org.mule.tooling.messageflow.editor.MessageFlowEditor.reload(MessageFlowEditor.java:331) at org.mule.tooling.messageflow.editor.MessageFlowEditor$2.onRefreshRequested(MessageFlowEditor.java:222) at org.mule.tooling.messageflow.events.RefreshRequestedEvent.dispatch(RefreshRequestedEvent.java:33) at org.mule.tooling.messageflow.events.RefreshRequestedEvent.dispatch(RefreshRequestedEvent.java:1) at org.mule.tooling.utils.eventbus.EventBus$1.call(EventBus.java:194) at org.mule.tooling.utils.eventbus.EventBus$1.call(EventBus.java:1) at org.mule.tooling.utils.SilentRunner.run(SilentRunner.java:10) at org.mule.tooling.utils.eventbus.EventBus.doFireEvent(EventBus.java:176) at org.mule.tooling.utils.eventbus.EventBus.fireEvent(EventBus.java:157) at org.mule.tooling.ui.contribution.debugger.service.MuleDebuggerService.setDebugging(MuleDebuggerService.java:289) at org.mule.tooling.ui.contribution.debugger.view.actions.TerminateCurrentLaunchAction.run(TerminateCurrentLaunchAction.java:22) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4136) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3982) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3621) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) 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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438) {code} | 1 |
| 607 | STUDIO-5664 | Invalid XML in a project creates a lot of error entries in the error log | If there is an empty XML file in a project or any other invalid XML file, then out functionality to detect Mule config files fails with an exception (expected case). The problem is that this exception gets logged in the error log several times and this is just confusing for the user. | 1 |
| 608 | STUDIO-5665 | Http Connector - Listener - Improve Metadata in URI Parameters | The idea is that datasense recognize the uri parameters keys with the Listener path attribute uri parameters. | 5 |
| 609 | STUDIO-5666 | HTTP connector - Listener and Request should be display as HTTP Connector in the palette | * HTTP Request and Listener should be combined and called "HTTP Connector" Acceptance Criteria: # Having only one HTTP Connector in the palette instead of HTTP Listener and HTTP Request # When dropping the HTTP Connector in the beginning of a flow (input) you should get an HTTP Listener # When dropping the HTTP Connector in the process area of the flow you should get an HTTP Request # Ideally the display name will reflect if it is a listener or a request | 13 |
| 610 | STUDIO-5667 | Rename Request/Listener config to Connector Configuration | See title | 1 |
| 611 | STUDIO-5668 | Spike on how collapsing should work with scopes and message routers | Define the experience and the mock ups | 3 |
| 612 | STUDIO-5676 | HTTP Connector - Deprecate Old Connector and it components | For mule 3.6 the old HTTP connector will be deprecated. * Old HTTP Connector should be called "HTTP Connector (deprecated) * Old HTTP connector should show up as a deprecated element in flow and be hidden when someone checks that hide deprecated elements preference | 5 |
| 613 | STUDIO-5698 | Add new icons for minimizing flows | Please use the attached icons for the "minimize scope" button. | 1 |
| 614 | STUDIO-5706 | UnsupportedOperationException when using domains | Launch Studio with any domain projects and you get these errors in the error log. org.eclipse.core.runtime.CoreException: Domain projects do not support test resource folders. org.mule.tooling.core.builder.TransformerUtils.addErrorsForFlow(TransformerUtils.java:127) org.mule.tooling.core.builder.TransformerUtils.validateConfigFile(TransformerUtils.java:94) org.mule.tooling.core.builder.ValidationBuildVisitor$1.call(ValidationBuildVisitor.java:38) org.mule.tooling.core.builder.ValidationBuildVisitor$1.call(ValidationBuildVisitor.java:1) org.mule.tooling.utils.SilentRunner.run(SilentRunner.java:16) org.mule.tooling.core.StudioDesignContextRunner.runSilentWithMuleProject(StudioDesignContextRunner.java:17) org.mule.tooling.core.builder.ValidationBuildVisitor.validate(ValidationBuildVisitor.java:33) org.mule.tooling.core.builder.ValidationBuildVisitor.visitFile(ValidationBuildVisitor.java:28) org.mule.tooling.core.utils.MuleProjectResourceVisitor.visit(MuleProjectResourceVisitor.java:19) org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:126) org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:85) org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82) org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127) org.eclipse.core.internal.resources.Resource.accept(Resource.java:95) org.eclipse.core.internal.resources.Resource.accept(Resource.java:52) org.eclipse.core.internal.resources.Resource.accept(Resource.java:124) org.eclipse.core.internal.resources.Resource.accept(Resource.java:108) org.mule.tooling.core.builder.MuleBuilder$1.run(MuleBuilder.java:91) org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.UnsupportedOperationException: Domain projects do not support test resource folders. org.mule.tooling.core.impl.model.MuleDomainProject.getTestResourcesFolder(MuleDomainProject.java:48) org.mule.tooling.core.io.MuleResourceUtils.isInAnyTestFolder(MuleResourceUtils.java:426) org.mule.tooling.ui.modules.core.widgets.AttributeContext.collectMuleConfigurations(AttributeContext.java:169) org.mule.tooling.ui.modules.core.widgets.AttributeContext.getGlobalEntries(AttributeContext.java:138) org.mule.tooling.ui.modules.core.widgets.utils.NameValidator.validate(NameValidator.java:78) org.mule.tooling.ui.modules.core.widgets.utils.NameValidator.validate(NameValidator.java:36) org.mule.tooling.ui.modules.core.widgets.AttributeModelWithHelper$1.validate(AttributeModelWithHelper.java:78) com.onpositive.commons.namespace.ide.ui.editors.xml.model.DomainValidatorVisitor.enterNode(DomainValidatorVisitor.java:185) com.onpositive.commons.namespace.ide.ui.editors.xml.model.DomainEditingModelObject.traverse(DomainEditingModelObject.java:121) com.onpositive.commons.namespace.ide.ui.editors.xml.model.DomainEditingModelObject.traverse(DomainEditingModelObject.java:126) org.mule.tooling.ui.modules.core.validation.MuleConfigurationValidator.doValidate(MuleConfigurationValidator.java:178) org.mule.tooling.ui.modules.core.validation.MuleConfigurationValidator.collectErrorMessages(MuleConfigurationValidator.java:167) org.mule.tooling.ui.modules.core.validation.MuleConfigurationValidator.validate(MuleConfigurationValidator.java:135) org.mule.tooling.core.builder.TransformerUtils.addErrorsForFlow(TransformerUtils.java:121) | 5 |
| 615 | STUDIO-5707 | [Launcher] Export package support with domains: add the ability to only export a project, without its parent domain | Add the ability to only export a project, without its parent domain | 5 |
| 616 | STUDIO-5711 | Select RAML in Library from HTTP connector | See mockups. | 5 |
| 617 | STUDIO-5714 | HTTP Response Builder: the builder can reference to itself. | If the builder can reference to itself it can be confusing, this is not a big issue only an usability improvement. I also guess that this will create a cycle reference in runtime that won't work. | 5 |
| 618 | STUDIO-5726 | HTTP endpoint :: Editor is displayed really slow | Having an HTTP endpoint in the canvas add a logger after it 1. Click in the logger 2. Click in the http endpoint ISSUE: it takes too long to display the HTTP editor | 5 |
| 619 | STUDIO-5727 | Palette: The return key erases the filter term | 1. In the palette, pick into the search field, and begin typing a filter 2. Press the return key 3. The filter disappears (which is unexpected... Typically return persists the filter term and updates results) Expected behavior when return key is pressed: Nothing happens. | 13 |
| 620 | STUDIO-5755 | [New Containers] Remove input/process dotted line separation in flows and add background color for source | Right now the flow container has a dashed line that separates the INPUT from the PROCESS part of the flow. The dashed line should be removed in favor of just changing the background color of the INPUT section. Pending mockups. | 8 |
| 621 | STUDIO-5756 | Hide launcher | Hide the launcher until next release. Buuuu. :( :'( | 3 |
| 622 | STUDIO-5757 | Add HTTP properties and variables into DataSense | The following should be visible in DataSense metadata: * HTTP Method * HTTP Version TODO: complete list | 5 |
| 623 | STUDIO-5758 | Rename Templates Library to Library | In the browser title, it should be Library, not Templates Library | 1 |
| 624 | STUDIO-5759 | Domains: Prevent Domains projects to be deployed to Cloudhub | Users shouldn't be able to deploy Domain projects to CH | 5 |
| 625 | STUDIO-5760 | Reenable plugins loading in Mule Server 3.4.x (debugger mainly) | (This is an internal task that needs tracking/re-testing some stuff mainly) In order to make domains/multi-app in Studio we changed how we launch Mule. This had the drawback that the method we now use for launching Mule didn't load mule plugins correctly (debugger). To reproduce: try to debug an application in 3.4.x runtimes, you never get notifications from breakpoints. | 5 |
| 626 | STUDIO-5761 | Drawing of the editors it's working too slowly in comparison with Gasher and with big projects it is imposible to use | I'm attaching a video, in the Left side you can see how Gasher release works and in the right side you can see the Nightly build. When having big projects it is taking too long to render an editor. Here is a Thread dump {code} 2014-11-14 10:37:47 Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.65-b04 mixed mode): "RMI TCP Connection(4)-192.168.79.1" daemon prio=5 tid=0x000000010309b000 nid=0x1828f runnable [0x00000001278cd000] java.lang.Thread.State: RUNNABLE java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:152) java.net.SocketInputStream.read(SocketInputStream.java:122) java.io.BufferedInputStream.fill(BufferedInputStream.java:235) java.io.BufferedInputStream.read(BufferedInputStream.java:254) - locked <0x00000007f5661bf8> (a java.io.BufferedInputStream) java.io.FilterInputStream.read(FilterInputStream.java:83) sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:538) sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:811) sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:670) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) java.lang.Thread.run(Thread.java:745) Locked ownable synchronizers: - <0x00000007f208b9e0> (a java.util.concurrent.ThreadPoolExecutor$Worker) "RMI TCP Connection(3)-192.168.79.1" daemon prio=5 tid=0x000000011e543800 nid=0xee0f in Object.wait() [0x00000001077ba000] java.lang.Thread.State: WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007f4c1fc70> (a java.lang.Object) java.lang.Object.wait(Object.java:503) org.netbeans.lib.profiler.global.TransactionalSupport.beginTrans(TransactionalSupport.java:107) - locked <0x00000007f4c1fc70> (a java.lang.Object) org.netbeans.lib.profiler.global.TransactionalSupport.beginTrans(TransactionalSupport.java:76) org.netbeans.lib.profiler.server.ProfilerInterface.classLoadHook(ProfilerInterface.java:926) java.net.AbstractPlainSocketImpl.close(AbstractPlainSocketImpl.java:502) - locked <0x00000007f208a0a8> (a java.lang.Object) java.net.SocksSocketImpl.close(SocksSocketImpl.java:1077) java.net.Socket.close(Socket.java:1441) - locked <0x00000007f208a000> (a java.lang.Object) - locked <0x00000007f2089fe0> (a java.net.Socket) sun.rmi.transport.tcp.TCPConnection.close(TCPConnection.java:222) sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:585) sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:811) sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:670) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) java.lang.Thread.run(Thread.java:745) Locked ownable synchronizers: - <0x00000007f208abc0> (a java.util.concurrent.ThreadPoolExecutor$Worker) "*** Profiler Agent Special Execution Thread 2" daemon prio=5 tid=0x000000011acac000 nid=0xfa07 runnable [0x0000000127cf3000] java.lang.Thread.State: RUNNABLE org.netbeans.lib.profiler.server.system.Classes.cacheLoadedClasses(Native Method) org.netbeans.lib.profiler.server.ProfilerInterface.cacheLoadedClasses(ProfilerInterface.java:1384) org.netbeans.lib.profiler.server.ProfilerInterface.getLoadedClasses(ProfilerInterface.java:798) org.netbeans.lib.profiler.server.ProfilerInterface.access$600(ProfilerInterface.java:71) org.netbeans.lib.profiler.server.ProfilerInterface$InitiateProfilingThread.initiateInstrumentation(ProfilerInterface.java:208) org.netbeans.lib.profiler.server.ProfilerInterface$InitiateProfilingThread.run(ProfilerInterface.java:138) Locked ownable synchronizers: - None "*** Profiler Agent Special Execution Thread 6" daemon prio=5 tid=0x000000011e917000 nid=0x1150f in Object.wait() [0x00000001279f3000] java.lang.Thread.State: WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007f4b8df80> (a java.lang.Object) java.lang.Object.wait(Object.java:503) org.netbeans.lib.profiler.server.ProfilerServer$SeparateCmdExecutionThread.run(ProfilerServer.java:289) - locked <0x00000007f4b8df80> (a java.lang.Object) Locked ownable synchronizers: - None "*** JFluid Monitor thread ***" daemon prio=5 tid=0x000000011ed76800 nid=0x18f07 sleeping[0x0000000126584000] java.lang.Thread.State: TIMED_WAITING (sleeping) java.lang.Thread.sleep(Native Method) org.netbeans.lib.profiler.server.Monitors$SurvGenAndThreadsMonitor.run(Monitors.java:186) Locked ownable synchronizers: - None "*** Profiler Agent Communication Thread" daemon prio=5 tid=0x000000012807c000 nid=0xf907 runnable [0x0000000125303000] java.lang.Thread.State: RUNNABLE java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:152) java.net.SocketInputStream.read(SocketInputStream.java:122) java.net.SocketInputStream.read(SocketInputStream.java:210) java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2293) java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2473) java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2543) java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2615) java.io.ObjectInputStream.read(ObjectInputStream.java:841) org.netbeans.lib.profiler.wireprotocol.WireIO.receiveCommandOrResponse(WireIO.java:88) org.netbeans.lib.profiler.server.ProfilerServer.listenToClient(ProfilerServer.java:1720) org.netbeans.lib.profiler.server.ProfilerServer.run(ProfilerServer.java:690) Locked ownable synchronizers: - None "RMI TCP Connection(2)-192.168.79.1" daemon prio=5 tid=0x00000001281e6800 nid=0x1924f runnable [0x00000001276c7000] java.lang.Thread.State: RUNNABLE java.net.SocketInputStream.read(SocketInputStream.java:152) java.net.SocketInputStream.read(SocketInputStream.java:122) java.io.BufferedInputStream.fill(BufferedInputStream.java:235) java.io.BufferedInputStream.read(BufferedInputStream.java:254) - locked <0x00000007f2458ca0> (a java.io.BufferedInputStream) java.io.FilterInputStream.read(FilterInputStream.java:83) sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:538) sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:811) sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:670) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) java.lang.Thread.run(Thread.java:745) Locked ownable synchronizers: - <0x00000007f2089da0> (a java.util.concurrent.ThreadPoolExecutor$Worker) "JMX server connection timeout 293" daemon prio=5 tid=0x000000011ec53800 nid=0xe213 in Object.wait() [0x0000000127448000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007f213fa90> (a [I) com.sun.jmx.remote.internal.ServerCommunicatorAdmin$Timeout.run(ServerCommunicatorAdmin.java:168) - locked <0x00000007f213fa90> (a [I) java.lang.Thread.run(Thread.java:745) Locked ownable synchronizers: - None "RMI Scheduler(0)" daemon prio=5 tid=0x000000011ad5f800 nid=0x1012b waiting on condition [0x0000000126f00000] java.lang.Thread.State: TIMED_WAITING (parking) sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00000007f2022938> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2082) java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1090) java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807) java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) java.lang.Thread.run(Thread.java:745) Locked ownable synchronizers: - None "RMI TCP Connection(1)-192.168.79.1" daemon prio=5 tid=0x000000011adb1800 nid=0x11a5f runnable [0x0000000126687000] java.lang.Thread.State: RUNNABLE java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:152) java.net.SocketInputStream.read(SocketInputStream.java:122) java.io.BufferedInputStream.fill(BufferedInputStream.java:235) java.io.BufferedInputStream.read(BufferedInputStream.java:254) - locked <0x00000007f20f27b8> (a java.io.BufferedInputStream) java.io.FilterInputStream.read(FilterInputStream.java:83) sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:538) sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:811) sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:670) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) java.lang.Thread.run(Thread.java:745) Locked ownable synchronizers: - <0x00000007f2088ec0> (a java.util.concurrent.ThreadPoolExecutor$Worker) "RMI TCP Accept-0" daemon prio=5 tid=0x000000011e80e800 nid=0x1a72b runnable [0x000000011dee1000] java.lang.Thread.State: RUNNABLE java.net.PlainSocketImpl.socketAccept(Native Method) java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398) java.net.ServerSocket.implAccept(ServerSocket.java:530) java.net.ServerSocket.accept(ServerSocket.java:498) sun.management.jmxremote.LocalRMIServerSocketFactory$1.accept(LocalRMIServerSocketFactory.java:52) sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:388) sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:360) java.lang.Thread.run(Thread.java:745) Locked ownable synchronizers: - None "Attach Listener" daemon prio=5 tid=0x00000001172fa000 nid=0x10733 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE Locked ownable synchronizers: - None "Worker-43" prio=5 tid=0x00000001202ed000 nid=0xf20f in Object.wait() [0x000000011cb93000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007d29a81c0> (a org.eclipse.core.internal.jobs.WorkerPool) org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188) - locked <0x00000007d29a81c0> (a org.eclipse.core.internal.jobs.WorkerPool) org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220) org.eclipse.core.internal.jobs.Worker.run(Worker.java:51) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x0000000117629800 nid=0x1a357 in Object.wait() [0x0000000126a0f000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007ee894ff8> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007ee894ff8> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x000000011ee2a000 nid=0x1a137 in Object.wait() [0x0000000127bf0000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007ee904108> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007ee904108> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x000000010197e800 nid=0x19d07 in Object.wait() [0x0000000126481000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007edfaac98> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007edfaac98> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x000000011e846000 nid=0x19913 in Object.wait() [0x00000001277ca000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007ec9ba998> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007ec9ba998> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x0000000104610800 nid=0x19503 in Object.wait() [0x00000001275c4000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007ebf67940> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007ebf67940> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "Worker-33" prio=5 tid=0x00000001019f8000 nid=0x18d03 in Object.wait() [0x00000001270d6000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007d29a81c0> (a org.eclipse.core.internal.jobs.WorkerPool) org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188) - locked <0x00000007d29a81c0> (a org.eclipse.core.internal.jobs.WorkerPool) org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220) org.eclipse.core.internal.jobs.Worker.run(Worker.java:51) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x00000001172a4800 nid=0x1890b in Object.wait() [0x000000012681f000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007ebad6260> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007ebad6260> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x00000001030e9800 nid=0x1830b in Object.wait() [0x0000000126c35000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007eb0450a0> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007eb0450a0> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x000000010236c000 nid=0x17b2f in Object.wait() [0x0000000125bfb000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007ea6f9420> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007ea6f9420> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x0000000105b49000 nid=0x17937 in Object.wait() [0x0000000125e62000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007e9fa2868> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007e9fa2868> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x0000000102691000 nid=0x1771f in Object.wait() [0x0000000125d5f000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007e980b890> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007e980b890> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x0000000104728000 nid=0x1752f in Object.wait() [0x0000000125899000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007e8d6fdb8> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007e8d6fdb8> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x00000001043ae800 nid=0x11b67 in Object.wait() [0x00000001259f2000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007e85608b8> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007e85608b8> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x00000001045b9800 nid=0x1730b in Object.wait() [0x0000000125af8000] java.lang.Thread.State: TIMED_WAITING (on object monitor) java.lang.Object.wait(Native Method) - waiting on <0x00000007e7cf5e90> (a java.util.Collections$SynchronizedRandomAccessList) org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:667) - locked <0x00000007e7cf5e90> (a java.util.Collections$SynchronizedRandomAccessList) Locked ownable synchronizers: - None "org.mule.tooling.messageflow.editor.xml.MuleXMLStructuredRegionProcessor" daemon prio=5 tid=0x00000001201db800 nid=0x11737 in Object.wait() [0x0... | 2 |
| 627 | STUDIO-5775 | Warn users of server version mismatch between the launching projects and the server configured in the launch configuration | Add a warning to users when the runtime version configured in the projects that are being launched is different from the one configured in the launch configuration. | 5 |
| 628 | STUDIO-5783 | External Links not working in RAML perspective | Open library from a HTTP connector. If you have an API object with Doc/Url and/or Open in Api Portal action, none of those external links are working. If you open the library from the normal perspective, looks for that same item and click on those links, they work. | 1 |
| 629 | STUDIO-5789 | Import/Export: Let the user rename the project when importing | When a user tries to import an exported zip that contains one project, the user should be able to rename it if. Multi-app/Domain exports will not offer this for the time being. | 8 |
| 630 | STUDIO-5828 | HTTP Request: fix the alignment of the text attribute in the Oauth configuration | Check screenshot | 13 |
| 631 | STUDIO-5844 | Create 3.6.0 CE runtime plugin | Need to create the 3.6.0 CE runtime plugin. Once completed, it will be available at: http://tooling-runtimes.s3.amazonaws.com/repository | 3 |
| 632 | STUDIO-5848 | When wrapping an inbound endpoint in a Poll, the endpoint does not change to outbound. | Steps to reproduce: 1-. Drop an AJAX inbound endpoint in the source compartment of a flow. 2-. Right click on the endpoint and Wrap it in a Poll. 3-. Go to the XML view. The element is successfully wrapped in a poll scope, but it still is a inbound endpoint. This is wrong, as Poll scopes, only accept outbound-endpoints. | 8 |
| 633 | STUDIO-5914 | Studio shows description element as a message processor in the flow canvas | Studio shows description element as a message processor in the flow canvas | 5 |
| 634 | STUDIO-5931 | Studio shows description element as a message processor in the flow canvas (develop) | Studio shows description element as a message processor in the flow canvas | 5 |
| 635 | STUDIO-5938 | New Project Dialog: capitalize "Version Control System (S)upport" title | Please capitalize "Version Control System (S)upport" in the new project dialog. See attached mockup with location. | 1 |
| 636 | STUDIO-5956 | [DataSense in Background] Improve cache locking. | * Check whether the read locks in the caches are needed. Check if write locks used are enough for concurrent access. | 8 |
| 637 | STUDIO-5957 | [DataSense in Background] Create a serial background process queue for DataSense jobs | All metadata related jobs should be posted to a process queue and served in FIFO fashion. Concurrent DS calls will not supported in the first release (or ever if not really needed). | 13 |
| 638 | STUDIO-5958 | [DataSense in Background] Jobs interdependencies and automatic cancellation | Failure of a Job due to invalid credentials, classpath problem, or any other failure, will result in the cancellation of all the jobs in the queue dependent on those same credentials. TBD. | 13 |
| 639 | STUDIO-5959 | [DataSense in Background] Error handling | Provide a non-blocking feedback that shows any error in the background execution of DataSense. This feedback may include: error, reason and provide a link to edit the source of the error. | 13 |
| 640 | STUDIO-5960 | [DataSense in Background] UI feedback | Provide visual cues that show that: * Types are being fetched (combo boxes) * Metadata is being retrieved (Input/Output trees) Type chooser UI will be accesible even while there is a type fetch in progress. So the user can enter a type manually if desired. However, there should be an indicator that something is happening, such as a spinning wheel or a "Fetching types" text in the combo options. TBD: What is the expected behaviour for the Refresh Metadata link and the Refresh Types button in the editors? Are the executions triggered by these elements executed in the background or in the foreground while blocking the UI? | 21 |
| 641 | STUDIO-5982 | HTTP request :: root RAML should be detected automatically | When using several files, all files with .raml extension are retrieved. It would be nice, to identify the main .raml file in order to avoid searching the correct one | 8 |
| 642 | STUDIO-5992 | Mule stops recognizing certain core elements from the namespace | There are times when working with APIKit that mule stops recognizing core elements such as set-property. During a MuleSoft training delivery 20-jan-2015 we had several students experience this. The only resolution we could come to is to regenerate the flows from APIKit. This happened several times at random points throughout individuals development. We did find one reproducible means of invoking the issue. (See attached screen-capture) Attached is the project seen which mule is failing to validate the xml (SAX parse exception) | 5 |
| 643 | STUDIO-5999 | HTTP request :: Value is automatically selected when going over with arrow key in Path list | 1. Using a Ramls such as Facebook, configure it 2. Using arrows go over the PATH list ISSUE: at some point , when stop going over the list, the value is automatically selected and combo is closed | 8 |
| 644 | STUDIO-6002 | Dragging MP inside the canvas is not always succesful | Having a flow with several Message processors, in the visual editor, drag any of them to another position in the flow. Try several times ISSUE: The dragging is not always successful. sometimes the MP is not selected and it is annoying | 8 |
| 645 | STUDIO-6003 | Dragging MPs inside a long flow in Windows is not possible because of the limited scrolling | In Windows create a flow with several Message processors (at least 12) Try to drag the first message processor to the last position in the flow ISSUE: it is not possible due to scrolling limitations in windows | 5 |
| 646 | STUDIO-6005 | Default exception strategy in Global Configuration doesn't offer the existing global exception strategies | Studio does not recognize global error handling strategies. They can be dragged into the gui (outside of a flow) and create a valid global error handling strategy but they do not show up in 'Global Elements'. I believe a side effect of this is you are unable to set a default exception handling strategy. Lastly note that even the xml says there is an error, but the project will compile and works in the runtime fine. | 5 |
| 647 | STUDIO-6011 | Debugger :: Add more room in Mule expression watches to add Multiple expressions | In the Debug view, when selecting Watch Mule expressions or when selecting Evaluate Mule expressions there is only a line to enter the expression. When having several expressions, it would be nice to have more room instead of only one line and then it will be possible to see the all the expressions entered | 5 |
| 648 | STUDIO-6012 | [Custom Metadata Definition] Improve cache structures and persistence | * Remove duplicated type structures in both caches. (Full types structures in the Types Cache vs. Message Processor input/output metadata in the message processor cache) | 13 |
| 649 | STUDIO-6085 | [DF] Clean up alignment and layout | Need to clean up the labels, icons, layout, fonts, and alignment of components in the properties view. Acceptance Criteria: * Should help new users understand what the different components in the UI do * Sample output fonts should be the same as the code view * Diego needs approve the layout/padding :) | 5 |
| 650 | STUDIO-6088 | [DF] Improved error reporting/layout for samples | Acceptance criteria: * clean way to display error messages and status of error messages * fonts should make sense with the rest of the UI | 3 |
| 651 | STUDIO-6090 | [DF] declare inputs when using auto complete | As a user, I want Studio to add in input declarations for my payload, flowVars, etc when I use auto-completion. | 5 |
| 652 | STUDIO-6091 | [DF] Implement current draft of language | TBD | 13 |
| 653 | STUDIO-6095 | [DF] Visual mapping design 2nd draft | TBD | 8 |
| 654 | STUDIO-6096 | [DF] Output view for Java objects | As a user, I want to see sample output for my java objects when doing transformations. * Text representation only | 3 |
| 655 | STUDIO-6097 | [DF] Package 3.7 snapshot with DFL runtime | See description. | 5 |
| 656 | STUDIO-6099 | Add support for multi-level data-sense key. | Several connectors such as PeopleSoft, Siebel, .Net, Oracle EBS need data sense for modeling objects + entities. A concrete use case is the following, PeopleSoft support entities called Component Interfaces that model objects with they operations. The workaround today is to create a datasense key that is the composition of both things. This means that if we have a component interface User will operations [create,delete,insert], we need to create a 3 keys ["User#create","User#delete","User#insert"]. This will also affect the usability of the new WSDL connector, https://docs.google.com/a/mulesoft.com/document/d/1vk-KbDpFsX5-C2a30LiC6HN37UN3uQx2XgCbPYbWubg/edit | 13 |
| 657 | STUDIO-6169 | Studio: Add support for auto discovery of the new http transport | . | 3 |
| 658 | STUDIO-6114 | HTTP Request does not support dash and underscore in raml global elements | more information here: http://forum.mulesoft.org/mulesoft/topics/failure-parsing-sample-raml-file-in-http-connector?utm_source=notification&utm_medium=email&utm_campaign=new_topic&utm_content=topic_link | 2 |
| 659 | STUDIO-6125 | Java project dependency of Mule Project | As I user I want to have a shared java library developed in a Java project in Studio, and be able to use this library and its dependencies in a Mule Project. * The way this will work is that the Mule project will be referencing in its classpath the Java project. * The Java project usually needs Mule ESB dependencies, so it should be possible to add the Mule Server User Library to the Java Project When exporting the Mule Project (for deployment in embedded server, deployment to CloudHub, or just for exporting the Mule deployable archive) the following should happen: * The Java project should be packaged in a JAR file which name is the same as the project name (if the Java Project name has characters that cannot be used in a file, then this will be removed) * The created jar file should be then be part of the *lib* directory inside the exported Mule application * If the Java Project has other dependencies (that are NOT a Mule Runtime or JVM), then these dependencies (jars) will also be copied to the *lib* folder of the exported Mule application | 5 |
| 660 | STUDIO-6127 | [DataSense in Background] Add visual cues when a DS Job is executing for the current editor | We need to have some kind of indication while there is a DataSense Job for the current editor. Showing an (animated?) spinning wheel or hourglass on type choosers and metadata trees would be fine. | 8 |
| 661 | STUDIO-6128 | [DataSense in Background] Cancel purely UI related DataSense retrieval jobs when leaving editor that launched them | There are DataSense background jobs that are launched only to show some information for the user in the current dialog. Currently, these jobs compete with all the other jobs for resources and live even after the editor that launched them is not shown anymore. Improve this logic by cancelling these kind of metadata retrieval jobs when leaving the editor that launched them. | 8 |
| 662 | STUDIO-6130 | [DF] tests have to be reviewed on merge | Test in files: org.mule.tooling.metadata.test/src/org/mule/tooling/metadata/api/test/DatabaseTestConnectionUITest.java org.mule.tooling.ui.modules.http.test/src/org/mule/tooling/rest/consumer/test/twe/HttpRequestTwoWayEditingTests.java org.mule.tooling.messageflow.test/src/org/mule/tooling/properties/editor/test/DataSenseExplorerTest.java org.mule.tooling.datamapper.core.test/src/com/mulesoft/mule/datamapper/ui/preview/ShowXmlTreeJobTest.java need to be reviewed when the branch is going to be merged. | 3 |
| 663 | STUDIO-6139 | [DataSense in Background] Error notifications dialog loses buttons when the message is too long. | If the error message is long, the notification error popup looses its buttons for editing credentials and showing more information. | 5 |
| 664 | STUDIO-6140 | [DataSense in Background] Make error text selectable. | Make error texts from the notification dialogs selectable so the user can copy/paste it. | 3 |
| 665 | STUDIO-6149 | [DataSense in Background] Make the DataSense explorer tree refresh every time a job finishes. | The current behaviour of the DS Explorer tree is to refresh when a job corresponding to the current editor finishes its execution. But as other jobs may introduce changes in the metadata propagation we need to remove this restriction so the tree is refreshed every time in order to reflect any new data from the propagation. | 1 |
| 666 | STUDIO-6150 | [DataSense in Background] Make the DataMapper editor refresh on job completion | Make the DataMapper editor refresh on every job completion so it can update its views and show the new metadata available. | 5 |
| 667 | STUDIO-6179 | [DF] Deep search for auto completion | If we have a deep structure, e.g.: { "root" : { "family" : { "name" : "dan" } } } When I type "name" in the code editor, I should get auto completion for $payload.root.family.name | 8 |
| 668 | STUDIO-6181 | [DF] Support auto completion of keys for Maps/Java objects | Need to support auto completion of keys for Java Maps/POJOs | 5 |
| 669 | STUDIO-6182 | [DF] Update grammar to reflect latest spec | Need to incorporate selector changes. | 3 |
| 670 | STUDIO-6184 | [DF] Show output schema in DF | need to show the output schema | 3 |
| 671 | STUDIO-6191 | [DF] Support searching by label | Related to STUDIO-6179, we need to be able to search by label. labels also need to show up in auto-suggest. | 8 |
| 672 | STUDIO-6219 | As an Integration Developer I want to be able to define the Metadata for Message Processors so that this Metadata it's propagated and it can be use for Design | Acceptance Criteria: # I should be able to define the Metadata in a File and HTTP Message Processors. (inbound) # The Metadata Should be propagated and I have to be able to use the Metadata in the Data Framework # Metadata should be persisted to disk # When importing / exporting projects, the metadata should be preserved | 21 |
| 673 | STUDIO-6220 | Allow adding required libraries to pom.xml file if the project is maven based | Allow adding required libraries to pom.xml file if the project is maven based (TBD) | 13 |
| 674 | STUDIO-6221 | [SVR] Apply light theme to Studio (Carl's & James' design) | Need to investigate how to skin eclipse to match Carl's and Jame's mockups found here: https://drive.google.com/a/mulesoft.com/folderview?id=0B6P6bhYyYtOXMWRCdWJMRmdzS28&usp=sharing | 21 |
| 675 | STUDIO-6263 | Create plugin for old DataMapper | Need to create a plugin for the DataMapper plugin. | 5 |
| 676 | STUDIO-6264 | [DF] Spike on visual mapper | Need to spike on visual mapping. Acceptance criteria: * Updated mockups * Set of tasks and plan for the release(s) * Start coding :) | 13 |
| 677 | STUDIO-6301 | [Dark\Light Theme] Change style in Properties Editors | All native controls has to be changed to something that can be styled with a css. Text Box Combo, Group, Text Areas.... Acceptance Criteria: - Properties Editors look fine and consistent in OS x, Linux and Windows. | 13 |
| 678 | STUDIO-6306 | [Custom Metadata Definition] Persist metadata definitions in the config XML file. | Persist metadata definitions in the config XML file. Spike on how to store flow vars custom metadata. | 8 |
| 679 | STUDIO-6331 | Transform: when having a big payload and maximizing the editor there are some UI issues | Steps to reproduce: 1.- Create a blank mapping, set types json to json 2.- Go to the payload tab and paste the followed JSON {code} {"count":66,"href":"/httpAuth/app/rest/builds","build":[{"id":154,"buildTypeId":"Tooling_SanityWin32","number":"16","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:154","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=154&buildTypeId=Tooling_SanityWin32"},{"id":150,"buildTypeId":"Tooling_SanityWin32","number":"15","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:150","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=150&buildTypeId=Tooling_SanityWin32"},{"id":148,"buildTypeId":"Tooling_SanityWin64","number":"23","status":"SUCCESS","state":"finished","href":"/httpAuth/app/rest/builds/id:148","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=148&buildTypeId=Tooling_SanityWin64"},{"id":146,"buildTypeId":"Tooling_SanityWin32","number":"14","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:146","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=146&buildTypeId=Tooling_SanityWin32"},{"id":144,"buildTypeId":"Tooling_SanityWin32","number":"13","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:144","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=144&buildTypeId=Tooling_SanityWin32"},{"id":142,"buildTypeId":"Tooling_SanityWin32","number":"12","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:142","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=142&buildTypeId=Tooling_SanityWin32"},{"id":140,"buildTypeId":"Tooling_SanityWin32","number":"11","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:140","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=140&buildTypeId=Tooling_SanityWin32"},{"id":136,"buildTypeId":"Tooling_SanityWin64","number":"22","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:136","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=136&buildTypeId=Tooling_SanityWin64"},{"id":130,"buildTypeId":"Tooling_SanityWin64","number":"18","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:130","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=130&buildTypeId=Tooling_SanityWin64"},{"id":128,"buildTypeId":"Tooling_SanityWin32","number":"8","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:128","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=128&buildTypeId=Tooling_SanityWin32"},{"id":124,"buildTypeId":"Tooling_SanityWin64","number":"16","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:124","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=124&buildTypeId=Tooling_SanityWin64"},{"id":122,"buildTypeId":"Tooling_SanityWin64","number":"15","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:122","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=122&buildTypeId=Tooling_SanityWin64"},{"id":120,"buildTypeId":"Tooling_SanityWin64","number":"14","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:120","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=120&buildTypeId=Tooling_SanityWin64"},{"id":118,"buildTypeId":"Tooling_SanityLinux32","number":"5","status":"SUCCESS","state":"finished","href":"/httpAuth/app/rest/builds/id:118","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=118&buildTypeId=Tooling_SanityLinux32"},{"id":117,"buildTypeId":"Tooling_SanityWin64","number":"13","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:117","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=117&buildTypeId=Tooling_SanityWin64"},{"id":116,"buildTypeId":"Tooling_SanityWin32","number":"7","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:116","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=116&buildTypeId=Tooling_SanityWin32"},{"id":115,"buildTypeId":"Tooling_SanityWin32","number":"6","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:115","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=115&buildTypeId=Tooling_SanityWin32"},{"id":113,"buildTypeId":"Tooling_SanityLinux32","number":"4","status":"SUCCESS","state":"finished","href":"/httpAuth/app/rest/builds/id:113","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=113&buildTypeId=Tooling_SanityLinux32"},{"id":111,"buildTypeId":"Tooling_SanityLinux32","number":"3","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:111","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=111&buildTypeId=Tooling_SanityLinux32"},{"id":109,"buildTypeId":"Tooling_SanityWin32","number":"5","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:109","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=109&buildTypeId=Tooling_SanityWin32"},{"id":107,"buildTypeId":"Tooling_SanityLinux32","number":"2","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:107","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=107&buildTypeId=Tooling_SanityLinux32"},{"id":105,"buildTypeId":"Tooling_SanityWin32","number":"4","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:105","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=105&buildTypeId=Tooling_SanityWin32"},{"id":103,"buildTypeId":"Tooling_SanityWin32","number":"3","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:103","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=103&buildTypeId=Tooling_SanityWin32"},{"id":101,"buildTypeId":"Tooling_SanityLinux32","number":"1","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:101","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=101&buildTypeId=Tooling_SanityLinux32"},{"id":99,"buildTypeId":"Tooling_SanityWin32","number":"2","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:99","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=99&buildTypeId=Tooling_SanityWin32"},{"id":97,"buildTypeId":"Tooling_SanityWin32","number":"1","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:97","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=97&buildTypeId=Tooling_SanityWin32"},{"id":91,"buildTypeId":"Tooling_Sanity","number":"34","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:91","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=91&buildTypeId=Tooling_Sanity"},{"id":89,"buildTypeId":"Tooling_Sanity","number":"33","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:89","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=89&buildTypeId=Tooling_Sanity"},{"id":87,"buildTypeId":"Tooling_SanityWin64","number":"12","status":"SUCCESS","state":"finished","href":"/httpAuth/app/rest/builds/id:87","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=87&buildTypeId=Tooling_SanityWin64"},{"id":85,"buildTypeId":"Tooling_SanityWin64","number":"11","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:85","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=85&buildTypeId=Tooling_SanityWin64"},{"id":83,"buildTypeId":"Tooling_Sanity","number":"32","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:83","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=83&buildTypeId=Tooling_Sanity"},{"id":81,"buildTypeId":"Tooling_SanityWin64","number":"10","status":"SUCCESS","state":"finished","href":"/httpAuth/app/rest/builds/id:81","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=81&buildTypeId=Tooling_SanityWin64"},{"id":77,"buildTypeId":"Tooling_SanityWin64","number":"8","status":"SUCCESS","state":"finished","href":"/httpAuth/app/rest/builds/id:77","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=77&buildTypeId=Tooling_SanityWin64"},{"id":75,"buildTypeId":"Tooling_SanityWin64","number":"7","status":"SUCCESS","state":"finished","href":"/httpAuth/app/rest/builds/id:75","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=75&buildTypeId=Tooling_SanityWin64"},{"id":73,"buildTypeId":"Tooling_Sanity","number":"31","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:73","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=73&buildTypeId=Tooling_Sanity"},{"id":71,"buildTypeId":"Tooling_Sanity","number":"30","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:71","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=71&buildTypeId=Tooling_Sanity"},{"id":69,"buildTypeId":"Tooling_SanityWin64","number":"6","status":"SUCCESS","state":"finished","href":"/httpAuth/app/rest/builds/id:69","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=69&buildTypeId=Tooling_SanityWin64"},{"id":67,"buildTypeId":"Tooling_Sanity","number":"29","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:67","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=67&buildTypeId=Tooling_Sanity"},{"id":64,"buildTypeId":"Tooling_Sanity","number":"28","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:64","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=64&buildTypeId=Tooling_Sanity"},{"id":62,"buildTypeId":"Tooling_Sanity","number":"27","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:62","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=62&buildTypeId=Tooling_Sanity"},{"id":60,"buildTypeId":"Tooling_Sanity","number":"26","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:60","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=60&buildTypeId=Tooling_Sanity"},{"id":56,"buildTypeId":"Tooling_SanityWin64","number":"3","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:56","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=56&buildTypeId=Tooling_SanityWin64"},{"id":54,"buildTypeId":"Tooling_Sanity","number":"25","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:54","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=54&buildTypeId=Tooling_Sanity"},{"id":50,"buildTypeId":"Tooling_Sanity","number":"23","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:50","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=50&buildTypeId=Tooling_Sanity"},{"id":48,"buildTypeId":"Tooling_Sanity","number":"22","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:48","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=48&buildTypeId=Tooling_Sanity"},{"id":46,"buildTypeId":"Tooling_SanityWin64","number":"2","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:46","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=46&buildTypeId=Tooling_SanityWin64"},{"id":44,"buildTypeId":"Tooling_SanityWin64","number":"1","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:44","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=44&buildTypeId=Tooling_SanityWin64"},{"id":42,"buildTypeId":"Tooling_Sanity","number":"21","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:42","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=42&buildTypeId=Tooling_Sanity"},{"id":40,"buildTypeId":"Tooling_Sanity","number":"20","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:40","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=40&buildTypeId=Tooling_Sanity"},{"id":36,"buildTypeId":"Tooling_Sanity","number":"18","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:36","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=36&buildTypeId=Tooling_Sanity"},{"id":32,"buildTypeId":"Tooling_Sanity","number":"16","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:32","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=32&buildTypeId=Tooling_Sanity"},{"id":30,"buildTypeId":"Tooling_Sanity","number":"15","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:30","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=30&buildTypeId=Tooling_Sanity"},{"id":28,"buildTypeId":"Tooling_Sanity","number":"14","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:28","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=28&buildTypeId=Tooling_Sanity"},{"id":26,"buildTypeId":"Tooling_Sanity","number":"13","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:26","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=26&buildTypeId=Tooling_Sanity"},{"id":24,"buildTypeId":"Tooling_Sanity","number":"12","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:24","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=24&buildTypeId=Tooling_Sanity"},{"id":22,"buildTypeId":"Tooling_Sanity","number":"11","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:22","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=22&buildTypeId=Tooling_Sanity"},{"id":20,"buildTypeId":"Tooling_Sanity","number":"10","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:20","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=20&buildTypeId=Tooling_Sanity"},{"id":18,"buildTypeId":"Tooling_Sanity","number":"9","status":"SUCCESS","state":"finished","href":"/httpAuth/app/rest/builds/id:18","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=18&buildTypeId=Tooling_Sanity"},{"id":16,"buildTypeId":"Tooling_Sanity","number":"8","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:16","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=16&buildTypeId=Tooling_Sanity"},{"id":14,"buildTypeId":"Tooling_Sanity","number":"7","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:14","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=14&buildTypeId=Tooling_Sanity"},{"id":12,"buildTypeId":"Tooling_Sanity","number":"6","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:12","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=12&buildTypeId=Tooling_Sanity"},{"id":10,"buildTypeId":"Tooling_Sanity","number":"5","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:10","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=10&buildTypeId=Tooling_Sanity"},{"id":8,"buildTypeId":"Tooling_Sanity","number":"4","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:8","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=8&buildTypeId=Tooling_Sanity"},{"id":6,"buildTypeId":"Tooling_Sanity","number":"3","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:6","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=6&buildTypeId=Tooling_Sanity"},{"id":4,"buildTypeId":"Tooling_Sanity","number":"2","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:4","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=4&buildTypeId=Tooling_Sanity"},{"id":2,"buildTypeId":"Tooling_Sanity","number":"1","status":"FAILURE","state":"finished","href":"/httpAuth/app/rest/builds/id:2","webUrl":"http://172.16.23.114:8111/viewLog.html?buildId=2&buildTypeId=Tooling_Sanity"}]} {code} 3.- Maximize the editor Issue: check screenshot. Also if you delete the payload and you paste the payload again you loose color hilighting | 5 |
| 680 | STUDIO-6338 | [Dark Theme] Enable icon switching with themes | Studio should support icon switching depending on the selected theme | 13 |
| 681 | STUDIO-6344 | Studio <transform> element support | Spec: https://docs.google.com/a/mulesoft.com/document/d/1ziulygSR_3ei9xpjLxbYlwiK7vsU6NKA3g2mMglHYho/edit# Acceptance criteria: * Need to support changing destination of the transform from the GUI - payload, flowVars, sessionVars, etc. * User should be able to switch context and see different transforms * There should be a way to remove a mapping - i.e. remove <set-variable/> from the <transform> | 21 |
| 682 | STUDIO-6356 | Metadata for Connectors is not shown on the explorer | When using a connector with dynamic datasense build with 3.6.1 DevKit, Input and output MetaData are always shown as unknown, even when the connector metadata is retrieved successfully. | 3 |
| 683 | STUDIO-6403 | Transform: deep search autocomplete does not suggest XML attributes | Steps to reproduce: Having an input XML with attributes, if you want to use autocomplete in the Weave script to set the value of a key with an attribute from the XML. The attributes is not shown in the list. | 3 |
| 684 | STUDIO-6415 | Update Studio Weave editor to remove $ from variables | See MDF-35 | 8 |
| 685 | STUDIO-6443 | Studio doesn't refresh connector metadata when the model is an XMLMetaDataModel | Using the new feature of DevKit that allows users to build WSDL based connectors, when two or more wsdl have the same operation name but different metadata, only the first one is retrieved always. The issue is that currently the keys retrieved from the connector are ignored when create the cache reference, so if a connector has 2 different wsdl, that have an update operation, even if the connector returns different keys, the metadata retrieved is not being properly handled. | 5 |
| 686 | STUDIO-6493 | Multi Level key is not saved when hitting apply or losing focus | When using a SOAP Connector built with DevKit, after the user changes the operation and it starts retrieving datasense, if he clicks on save or looses focus of the editor screen by clicking on the canvas, the changes are lost. | 5 |
| 687 | STUDIO-6730 | ServiceNow WSDL DataSense keys is quite slow | ServiceNow connector includes 46 WSDLs with sizes that range from 22k to 88k. WSDLs seems not to be too complex in relationship with the time required to load datasense. | 5 |
| 688 | STUDIO-6551 | Create new RAML file doesn't add ".raml" extension if the file name ends with RAML | Try to create a new RAML file from the UI menu *New* > *RAML API Definition* and specify the name "test-raml". Expected: A file is created with the name test-raml.raml Actual: The file created hast the name "test-raml" | 1 |
| 689 | STUDIO-6642 | Multi Level keys are not loaded when selecting an existing Global Configuration | When selecting existing configs, metadata key levels are not being populated. Steps to reproduce: 1. Create a flow using the "Get Account" operation from the provided connector "Minmule", configure it and select the 2 values required. 2. Create another flow. 3. Drag and drop the connector again. 4. In the new flow, selected the global config created at step 1. Expected: User should be able to selected the same values for the 2 fields. Actual: No options are available for the user to select and an errors shows telling the users that they need to specify a value, but we don't provide the possible elements that can be assigned. | 1 |
| 690 | STUDIO-6679 | None Multipart messages are detected as multipart | When a message has several parts, but the soap binding specifies that a message part is a header and not a body, Studio shows an error specifying the multipart is not supported, yet MetaData Explorer shows one body and one header as expected. | 3 |
| 691 | STUDIO-6773 | Studio allows to deploy an app with an ipv4 port already in use | Nowadays, studio is not forcing to use ipv4, so any app can be deployed using any already taken ipv4 port. As a consequence, you can deploy an app in Mule and then deploy the same app in Studio, without errors. Scenario 1 (using Mule 3.7): - Deploy the attached config in Mule 3.7.0. Notice that the port is hardcoded to 8082 - Deploy the same app in Studio. - Check the console and the terminal. Both logs show that the apps are deployed, without errors. Studio app should throw an exception saying that the port is already in use. - Go to a new terminal, and run the command "netstat -an | grep 8082". You will see that the 8082 is listening, with tcp4 and tcp46. (See image1.jpg) - If you make a request to http://localhost:8082, mule will answer that request, and studio will throw a Broken Pipe Exception. This issue does not happen if you run the apps in the inverted order (First studio, Second Mule). In that case, Mule throws an exception saying that the port is already in use. Scenario 2 (using ports of the other programs): - Go to a terminal and run the command "netstat -an" - Look for an already taken port using tcp4 (for example in image2.jpg you can see that the ports 49298 and 63342 are not available) - Deploy the attached app, changing the listener port to one of the previous ones. - The app is deployed instead of saying that the port is already in use. | 5 |
| 692 | STUDIO-6803 | DataWeave GUI Spike #2 | Goals: * Resolve open design questions ** Resolve fidelity questions - should we use native Eclipse controls? can we do it incrementally? ** How do we solve dealing with code we can't translate into a GUI? * Establish estimate for delivering MVP * Create tasks for next steps | 21 |
| 693 | STUDIO-6811 | [Custom Metadata Definition] Should support wrap existing types in a collection | As an user I would need to define a list of an already defined type as metadata in the message. | 8 |
| 694 | STUDIO-6845 | As a user I would like to have an option to customise the palette | As a user I would like to have an option to customise the palette so that I can choose what elements appear in it. This option should appear both as a preference page and as an accesible button in the palette view which will open the aforementioned preference page. The preference page will allow to: - Define new presets (A preset is a collection of categories and elements that are important to the user and that the user selects) - Remove new presets - Edit already created presets - Select categories and elements that will be stored in the preset When the user clicks "Apply" or "Ok" the palette must be updated with the elements of the selected preset. Some considerations to take into account about presets: - Presets will be stored as preferences as a workspace level. - Each preset is associated to a runtime version. Then, a preset can be used in projects with the same runtime version. - The preset preference page will not show presets that were created for a different runtime version than the current in-use project. For example, if a preset was created using a Mule project with 3.5 runtime, it will not be shown (in the preference page) when a user is working on a project that is using 3.7. - The preference page must present at least a "Default preset" and a "Weave Preset". The first one will show all the elements (categories and message processors) that exist in the current runtime, that's the runtime that is being used by the current Mule project. The second one will show all the elements BUT NOT the transformers, instead the new Weave transformer must be shown. Both presets CAN'T be edited. As a nice-to-have presets should be imported/exported in order to share them with others users. | 8 |
| 695 | STUDIO-6846 | As a user I would like to have a new Palette view | As a user I would like to have a new separated Palette view so that I can work with all the elements that are important for me in an user-friendly way. | 21 |
| 696 | STUDIO-6849 | [Multi Level Keys] Datasense retrieval is being triggered even when not all elements are populated | When using multi level key feature in a connector with 2 or more levels, metadata should not be retrieved until all values are populated, and when they are populated, datasense retrival is being triggered twice. Expected: Datasense should only be triggered when all fields are populated with some values. | 3 |
| 697 | STUDIO-6851 | Deploy to AMC design | We need to get tasks in both Studio and CloudHub backlogs to get the deploy to AMC done: * Priority one is only to support cloud version of AMC (On premises will come next) * Need to close version 1 of UX and mockups * Need to divide how work will be done across Studio and CH teams | 5 |
| 698 | STUDIO-6853 | Studio should propagate metadata correctly for DevKit connectors that return VOID | When DevKit returns a VOID metadata model for the output, this means that the output will be the same as the input (in some cases maybe the same as the input but in a different state, for example an InputStream that was consumed). More details can be found at DEVKIT-1473 | 8 |
| 699 | STUDIO-6861 | [DW-UI] JSON Support | Support arrays of simple elements | 13 |
| 700 | STUDIO-6862 | [DW-UI] Change Editor Layout | *) Remove code toolbar and editor tabs. Take into account *) How to add/remove a transformation (payload, flowVars, etc) *) How to modify transformations given name *) How to move between transformations *) How to indicate whether a transformations is saved inline or archive. *) How to run scaffolding. *) How to indicate if a transformation has errors. | 8 |
| 701 | STUDIO-6863 | [DW-UI] XML Support | - Support attributes - Support namespaces - Support repeating elements --Taking into account that map need to be generated in a different way --These elements should be marked someway | 5 |
| 702 | STUDIO-6864 | [DW-UI] Add Switch between Code and Graphical modes | *) Two Way Editing support, Taking into account not supported expressions in the graphical UI. *) Where should be the change mode button *) Mode change should display latest updates of transformation *) We should provide a concise way of changing from Code to UI and vice versa *) Graphical layout is going to be similar to actual DM layout (Input, Mapping, Output and a single line code editor) | 21 |
| 703 | STUDIO-6865 | [DW-UI] CSV Support | - JSON and XML support are required - Support unary operations (trim, capitalize, etc) - Support 'as' operator and its format | 13 |
| 704 | STUDIO-6866 | [DW-UI] Usability tests to determine possible issues with the “tubes” display | Criteria to determine this task as done: - At least 5 usability tests - Report of findings | 8 |
| 705 | STUDIO-6867 | [DW-UI] Java Support | Support 'as' operant and its format Support enums Support for Date types Support Collections | 13 |
| 706 | STUDIO-6868 | [DW-UI] Code Generation for special cases | After doing drag and drop the new elements has to keep the same order defined in the schema The tree should not be sorted by alphabetically Provide different actions when the user do drag and drop on objects Expand node when the parent object is already mapped | 13 |
| 707 | STUDIO-6869 | [DW-UI] Add coding support in graphical mode | *) The user should be able to select and edit the script assigned to an output field *) Added script should be validated (At least it should be parseable) *) TWE support (changes should be reflected in the graphical representation) | 13 |
| 708 | STUDIO-6870 | [DW-UI] Support selection in input/output trees | *) When a field is selected the assigned elements should be highlighted *) If an output field is selected the generated code should be displayed | 8 |
| 709 | STUDIO-6871 | [DW-UI] Get feedback from the code pane at the side of the graphical UI | This task is considered done if: - We have at least 20 data points with feedback about the code panel at the side - Report with findings | 13 |
| 710 | STUDIO-6872 | [DW-UI] Improve how connections and context are drawn | Improve rendering taking into account colors, position and selección highlighting | 21 |
| 711 | STUDIO-6873 | [DW-UI] Show indicators for each field that display if is mapped or not | Show indicators for each field that display if is mapped or not | 13 |
| 712 | STUDIO-6874 | [DW-UI] Determine how to guide the user to replace Lookup Tables | This task is considered done if: - We have mocks with the user journey from Data Mapper to DataWeave | 5 |
| 713 | STUDIO-6875 | [DW-UI] Add usage data collection to DataWeave transform | Add the following metrics to collect data during the MVP - Avg. transform view size - # of users using the beta light theme - Usage of multiple outputs: - # of transforms target to Payload + variables - Avg. number of outputs - Usage of “advanced” language features | 8 |
| 714 | STUDIO-6894 | XSLT message processor properties does not show context-property elements | There are no way to add, remove or edit <mulexml:context-property /> sub elements to a XSLT transformer in the graphical interface. To add or edit these sub-elements you need to switch to the "Configuration XML" tab. | 5 |
| 715 | STUDIO-6895 | Create 3.7.1 Studio runtime and Studio 5.2.1 with ESB 3.7.1 | * Create Studio ESB Runtime 3.7.1 * Create Binaries of Studio 5.2.1 with Mule ESB 3.7.1 as the embedded runtime * Move Stuio ESB Runtime 3.7.0 to runtimes update site | 3 |
| 716 | STUDIO-6904 | [SPIKE] Research on possible options for supporting custom UI for external contributions (connectors/modules) | As connectors behaviour becomes more complex, developers may need to have combos reacting to other combos changes, some others need to dynamically generate the UI based on the configuration and things returned from the sandbox. In this ticket we should do some research regarding: - Current capabilities of the editors.xml - The custom editor capabilities - What things can be considered an API - Define some strategies for external contributions to build their UI | 5 |
| 717 | STUDIO-6907 | APIKit menu entry rows on none mule projects | When doing a right click on a project, APIkit menu entry shows, even when the project is a simple java project. APIkit menu should only be shown on mule projects | 1 |
| 718 | STUDIO-6946 | [DW-UI] Add support for undo | This is one of the issues found during usability tests. When users create a mapping using DND, they need to have the option to undo the mapping. Acceptance criteria: - CTRL-Z has to work with the visual editor - Going to Edit->Undo has to work with the visual editor | 8 |
| 719 | STUDIO-6947 | [DW-UI] Show a DND hint when the visual editor is empty | This issue ocurred during the usability tests. When the user sees the Visual Editor for the first time; if he never used DM before is hard to figure out that you need to drag fields | 5 |
| 720 | STUDIO-6948 | [DW-UI] Automapping of collection fields | When the user maps a collection in the visual editor, the UI should try to auto-map the contained fields. | 5 |
| 721 | STUDIO-6949 | [DW-UI] Add a way to remove mappings | The visual editor doesn't have a way to remove mappings. | 8 |
| 722 | STUDIO-6960 | Add Validator icons | New icons for Validator module are attached. | 3 |
| 723 | STUDIO-6997 | Request for improvement on the Parse Template transformer- Make it dynamic | Loading the template file using Mule Expression- There is a scenario of using the template files dynamically and need to use via MEL expression in template path. If I set the file name in some variable and access the same via MEL expression then the template doesn't loads, rather than causes the exception and stops the flow execution. | 1 |
| 724 | STUDIO-7006 | Dynamic mysql not working | I have a simple flow: HttpConnector -> Flow Variable-> DB Connector[mysql] ->ObjectTOJson-> logger If I set the database field in flow variable and write the same in query( select #[flowVars.variable] from tableName;) then the output is malfunctioned. It is not reading the flow variable and below output: [{"chq_name":"chq_name"},{"chq_name":"chq_name"},{"chq_name":"chq_name"},{"chq_name":"chq_name"}], where chq_name is the filed in db table and has been set in flow variable. | 1 |
| 725 | STUDIO-7073 | Add Details Panel when selecting MetaData Types | When selecting metadata when configuring an http or jiust browsing the Catalog, there is no way to preview the structure. Now we will be able to see on the right of the keys list, the structure of the elements. | 1 |
| 726 | STUDIO-7075 | Studio fails to open mule configurations when the file has a Byte Order Marker | When a file has BOM markers, studio fails to load the mule configurations inside of it, generating lots of fake errors. Reference BOM: http://stackoverflow.com/questions/1772321/what-is-xml-bom-and-how-do-i-detect-it | 3 |
| 727 | STUDIO-7107 | Content assist slowness | The autocomplete was recalculating the metadata each time was executed. Now the metadata is only calculated one time and then is updated when the user changed it | 1 |
| 728 | STUDIO-7253 | Allow to finish the new Mule project wizard when the root Raml file is not valid | When creating a new APIkit project from a Raml file, it can be an URL or local file (not a zip one), it should be allowed to finish the wizard even though the API is not valid. The wizard must inform the user that the API is not valid, but the "Finish" button must be enabled. Then if the user press finish, it should import the root Raml file to the src/main/api folder and it should create an empty Mule configuration. | 3 |
| 729 | STUDIO-7360 | Add support for changes on connectors editor.xml | When a Processor has a POJO as a parameter, different options to complete it are shown depending on the modifiers of the parameter. Labels are: - None (if the parameter is not mandatory) - From Message - Create Object The proposed changes are: - Replace _From Message_ with _From Expression_ - If multiple POJOs configuration are present, only one should default to payload, leaving the rest of the _From Expression_ fields empty - Replace _None_ with _Default_ when the parameter is annotated with @Default. The default value should also be displayed on the label | 3 |
| 730 | STUDIO-7386 | API-GATEWAY Domain creation improvements in Studio | When creating a Gateway project Studio automatically creates the Domain API-Gateway with the corresponding Runtime version in the name The Id remains being API-Gateway The following scenarios should be verified: Create an API-Gateway project with different Runtime versions Acceptance criteria: The project is created successfully. The corresponding Domain is created with the following format: API-GATEWATE + Runtime version Import an API-Gateway project with different Runtime versions Acceptance criteria: The project is created successfully. The corresponding Domain is created with the following format: API-GATEWATE + Runtime version Import an API-Gateway project with different Runtime versions, with Domain existing in the zip file being imported Acceptance criteria: The project is created successfully. Domain? Export an API-Gateway project with different Runtime versions Acceptance criteria: The project is exported successfully. The corresponding Domain is not selected by default to be imported Create several API-Gateway project with different Runtime versions and execute the applications Acceptance criteria: The projects can be run successfully without any conflicts. Delete the Domain previously created for each version of the runtime and attempt to create it again Acceptance criteria: The Domain is created successfully for each version and the behaviour should be the same as the project creation Create an API-Gateway project for a certain Runtime version Domain project should be created for this version Change version of the domain project Create a new project with version used in step 1 Expected result: a new domain project should be created, for version used in step 1. Suggested name: api-gateway_2_0_1_1 | 5 |
| 731 | STUDIO-7436 | Allow studio to discover and instantiate ExtensionModels | Allow studio to discover and instantiate ExtensionModels | 8 |
| 732 | STUDIO-7479 | Create mule 4 Studio Runtimes | Discuss were it will be hosted. Verify if the structure of the distribution changed. Create mule 4 Studio Runtimes. | 3 |
| 733 | STUDIO-7487 | Spike to verify support extension child element naming conventions | Currently Studio is not prepared to support child elements with the same name as attributes in the parent. The code is full of places where it looks for -ref as part of the name. We need to review the code usage of this, and add the behaviour for this for pojos, list and maps | 5 |