X

Developer Partner Community

Debugging and Troubleshooting Visual Builder Logic by Shay Shmeltzer

Juergen Kress
PaaS & Middleware Partner Adoption

image

In every development cycle, developers are going to run into situations where things are not working as expected - this is where the debugging step comes into play. Oracle Visual Builder Cloud Service  uses a multi-tier architecture - so it is likely that you'll end up with the need to debug code in each one of the layers. In this short demo we give you some tips on how to debug your applications.

At its core, VBCS is a web UI tool, so for most of the UI layer debugging you are going to rely on the development tools offered to your by your browser. In the video below I'm using the Chrome browser and its development tools - but similar tools exists in other browsers too. These tools allow you to see the network traffic between your client's browser and the REST sources of data. They also provide a console that shows you error messages and notifications sent from your application. One of the things we added to VBCS is a verbose mode of output that gives you full details on what's going on in your app at every step.

Another layer that you might need to debug is the business object layer that exposes the REST services. If you are developing your business objects using VBCS, then you can use the built in logging mechanism for those. Read the complete article here.

 

Developer Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

clip_image003 Blog clip_image005 Twitter clip_image004 LinkedIn image[7][2][2][2] Facebook image Meetups

Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic Community,Oracle,OPN,Jürgen Kress

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.