To debug Java Actions used in a Mendix Microflow you need to make some configuration changes to the way you start the Mendix runtime. This How-to will explain you how to manage this.
1. Editing the Server Configuration with extra JVM parameters
Within this part of the how to you will learn how to configure the security at prototype/demo level. Be aware that this level of security is only applicable for development/demo purposes. This level is available for quick development of demo applications. It simulates security, without more complex configuration of the data access. When deploying to the Mendix cloud, production security is mandatory.
1. Open the project settings.
2. Edit the configuration.
3. Go to the Server tab and add the following line to the ‘Extra JVM parameters’:
4. Next, start your application in Mendix.
2. Configuring remote debugging
In your Java IDE you need to configure remote debugging. The following screenshot shows the configuration in IntelliJ:
1. Start the debugger.
2. Place some breakpoints in your java code.
3. Start debugging.
3. Related content
- Finding the Root Cause of Runtime Errors
- Clearing Warning Messages in Mendix
- Testing web services using SoapUI
- Debugging Microflows
- Common Mendix SSO Errors
- Monitoring Mendix using JMX
- Debugging Java Actions
- Getting started with Nexus maven repository manager
- Using eclipse to debug your tomcat web application
- Profiling Mendix using JProfiler