ProstDev provides different levels of expertise and knowledge to those who want to keep up with the IT world. Read our blog or watch our videos to learn more about DevOps, Testing, IoT (Internet of Things), APIs, Sorting Algorithms, Networks, Integration Technologies like MuleSoft, programming languages like DataWeave, Python, Java, or Groovy; software tools like Postman, Azure, Salesforce, NetSuite, Docker, and more!
Not only you can find information about different technologies, we also help you to get started in content creation so you can share your knowledge with the rest of the community. Contact us for more details about contributing, or send us your article for publishing!
I have an interesting issue - I follow your steps very judiciously, but when I try to deploy my application it gives my 500 - Internal Server Error with no much details. Mind giving an idea on what can the issue?
Alex, your content and presentation style are the most helpful I have seen and came at just the right time for me. Thank you for all the effort you have put into all of your videos!
Is this correct? %dw 2.0 output application/json var accumulator = 1 fun factorialOf(item, accumulator) = if(item <= 0) accumulator else factorialOf(item - 1, accumulator*item) var ans = payload splitBy " " map ((item, index) -> factorialOf(item as Number, accumulator)) reduce ($+$$) as String --- ans[20 to 25] as Number
that probably means you don't have access to Data Cloud on your Salesforce org. I believe it doesn't come with the free subscription, you'd have to check with an org admin who pays for salesforce
Hello Alex! Thank you for this information. It's very rare these days to find useful information in English that you can understand. Please keep going!
Hi Alex. First, thank you very much for creating these videos - they are a big help. I would add a suggestion if you didn't mind. Please make sure to show all the details - do not skip anything, no matter how small those details are. For the folks totally new to "mule" those are vital.
I really appreciate your feedback! Unfortunately, this series was recorded live and then cut-down for the RU-vid videos, so it makes sense that the details are missing :( you will be able to find them in the live-stream recordings on Twitch tho! I will be working on a refresh of this series to include more to-the-point content and also to refresh the information to the latest. Could you please let me know exactly which details I missed so I can be sure to add them in the new series?
@@ProstDev First of all, thank you so much for your response. I do enjoy your informative videos. The place that I wish you'd be a bit clearer is at 24:50. You said you'd create another global property where you'd reference the key name for the object store. I am still not quite sure, do we need yet another configuration properties file for that? I am going to go ahead and assume - yes. So sounds like we have ended up with 2(two) Configuration properties files: one for the Environment (like Dev or Local) and the other for the default.properties. Am I correct?
that is what I personally prefer to do with my projects but it doesn't mean it's necessarily the 'best practice'. If you prefer to have just the environment files (dev/local), you can use those and keep copy/pasting the values. A lot of projects do that to avoid creating the default.properties, which is entirely fine. Some things are more up to people's preference. For example, you can also use .yaml or .properties for your properties files and it just depends on personal preference which one to use. Thank you for being so detailed!
Hello Alex - thanks for this great series! I was wondering if you might be able to help - we are getting an error duing the deployment build step. I tried posting the full error earlier but youtube didn't like it and removed the comment. The error we are getting looks something like this: Unresolveable build extension: Plugin org.mule.tools.maven:mule-maven-plugin:4.2.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.mule.tools.maven:mule-maven-plugin:jar:4.2.0: Could not transfer artifact org.mule.tools.maven:mule-maven-plugin:pom:4.2.0 from/to maven-default-http-blocker. Blocked mirror for repositories: It then lists the mulesoft-releases and mulesoft-snapshot repositories. Do you have any idea what this error message could be related to? Many thanks!
Me ha servido mucho tu video. Tuve que usar otras formas al final, pero me ayudaste bastante a entender. Ya me funciona el proyecto en el que venía trabajando.
Hai i am facing this error while i deploy to cloudhub2.0 i am using window 11 Unknown lifecycle phase ".id=***". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1] cloud you tell what is this error
thanks for the suggestion! I'm not sure if this is possible to do with CI/CD though. Because you need to create the API in API Manager, retrieve the api id, and add the id to your Mule application. The policies could be automated through the UI, no need for CI/CD
Thanks for this amazing video, if I want to import the whole folder including types to postman, it didn’t work out, did you encounter this as well. Second question, by mentioning only ‘items’, is it a short way to say it’s a type of array? (Type array is redundant?)
You need to import only the JSON file to postman. The one under the postman folder. The items refer to what is the type of the things inside the array. Array of Strings, Array of Objects, Array of Numbers, etc. The items are Strings, Objects, Numbers, and so on.
Well, that is exactly what I was trying to do! I’m still trying to figure out how to set a custom name for the issues created, but apparently, it is not possible yet. I also took a look at Sentry API, but I didn’t catch any useful endpoint for that. This is definitely something they should improve
@@ProstDev if it can help someone, it seems that setting a custom name is not feasible. However, a workaround is to pass a text/plain payload to the log with the error description in the first line and a custom json starting from the second line. Not that great, but better. One more thing: it is possibile to set up environments in sentry by configuring sentry.properties file in our src>main>resources with just a property ‘environment=dev’. In that way, sentry will create a ‘dev’ env on our dashboard. That’s all I discovered 🤣
currently CDP connector version is 1.1.0 and we dont have any fresh release in recent months. CDP connector supports JDK 8 and 11. Can we expect CDP connector latest version with JDK17 support or higher version?
Been a few weeks learning and developing a Mule app for my company to connect to Snowflake using OData and setting some basic security over the important secrets. Thanks to all your videos (and the documentation, of course) I manged to finish the proof of concept today. Thank you very much!! Some of your old vids are a bit misleading now a days, but luckily, the comment sections of them include solutions for most of the problems. Thanks again for your work!
That should work as well: %dw 2.0 output application/json fun singleDigit(num:Number) = sumSingleDigit(sumSingleDigit(num splitBy "") splitBy "") fun sumSingleDigit(arr:Array) = sum(arr map() -> $ as Number) fun textToArray(text) = text splitBy " " map() -> $ as Number --- singleDigit(sum(textToArray(payload)))
I think it's not implemented yet to be native of ACB but I believe you could open several VS Code windows (one per mule project) and run them at the same time, just in different ports
@@ProstDev thanks for the reply. That was the first step I tried, but gave it another attempt. When I try to debug the second instance of VS code, I receive a somewhat cryptic error message. "EBUSY resource busy or locked, unlink C:\{username}\muleruntimes\mule-enterprise-standalone-4..\checker-qual-2.10.jar
oh that must be because it's using the same port to debug. I haven't gone through all the settings, but there must be a setting to modify the debug port per project. This will probably be fixed on the next release in June. But if I find out about this earlier I'll let you know for sure
@@ProstDev thanks. I tried moving the -M-Dmule.debugger.test.port=8000 out of the mule.default.Rutime arguments and append it to the launch.json file. In the first project I set the port to 8001 and in the other I used 8002. When I attempt to debug the second instance of VS Code, I immediately I receive a dialog error box with the message " EBUSY: resource busy or locked, unlink c:\{user}\muleRuntimes\mule-enterprise-standalone-4..\checker-qual-2.10.jar'" I have found some hits Googling the error, but haven't seen one related to ACB. the dialog does have a button to Open 'launch.json'
