Thanks Jacques.

This gives me something else to look at. I want to force a loop back to the 
database on drop-down lists to introduce a delay or example of poor coding. I 
want to test and see if I can pick-up the code that is a problem and issue an 
alert.

Thanks again,
Joe




-----Original Message-----
From: Jacques Le Roux [mailto:[email protected]] 
Sent: Tuesday, January 28, 2014 2:58 PM
To: [email protected]
Subject: Re: Breaking Ajax Requests

I don't know what you really want to do. But since OFBiz relies only on jQuery 
for its Ajax requests (thanks to our refactoring done with R11.04, older 
versions differ), the easiest way would be to use the non minified version of 
jQuery and to place your code inside the part which handles the Ajax requests 
there. I mean the deepest part of it, to be sure to catch all possible 
variations of Ajax requests in jQuery.

To use the non minified version of jQuery, simply replace (trunk) <set 
field="layoutSettings.javaScripts[+0]" 
value="/images/jquery/jquery-1.10.2.min.js" global="true"/>

in concerned screens (you can doit everywhere for your tests and then refine if 
needed).

It's not jQuery specific, but you migh be interested by the Webtools Metrics 
also:
https://demo-trunk.ofbiz.apache.org/webtools/control/ViewMetrics
https://cwiki.apache.org/confluence/display/OFBTECH/Metrics

HTH

Jacques

On Tuesday, January 28, 2014 4:14 PM, [email protected] wrote
> Hello,
> 
> I'm in the process of configuring monitoring for OFBiz. Does anyone know 
> where the best place would be to break Ajax requests?
> I'm looking to catch when an update, based on field drop-down 
> selection that I could break. The goal is to catch problems with updates to 
> user pages when selecting drop-down list criteria or any changes that update 
> a user page.
> 
> I have tried breaking the selectall.js and GetDependentValues.js and 
> it didn't work. In fact, if you rename these files so they are missing, the 
> application still works. Any ideas would be greatly appreciated.
> 
> Thanks,
> Joe

Reply via email to