Skip to main content

jQuery - usage of Load

 <div id="someContainer"></div>

old way to get  the remote server's result:

  window.onload = function() {
        var xhr;

        if (window.ActiveXObject) {
          xhr = new ActiveXObject("Microsoft.XMLHTTP");
        }
        else if (window.XMLHttpRequest) {
          xhr = new XMLHttpRequest();
        }
        else {
          throw new Error("Ajax is not supported by this browser");
        }

        xhr.onreadystatechange = function() {
          if (this.readyState == 4) {
            if (this.status >= 200 && this.status < 300) {
              document.getElementById('someContainer')
                .innerHTML = this.responseText;
            }
          }
        };

        xhr.open('GET','someResource');
        xhr.send('');
      };

new way to get the data:


    $(function() {
        $('#someContainer').load('someResource');
    });


load(url,parameters,callback)
Initiates an Ajax request to the specified URL with optional request parameters. A callback
function can be specified that’s invoked when the request completes and the DOM has been
modified. The response text replaces the content of all matched elements.
Parameters
url (String) The URL of the server-side resource to which the request is sent,
optionally modified via selector (explained below).
parameters (String|Object|Array) Specifies any data that’s to be passed as request
parameters. This argument can be a string that will be used as the query string,
an object whose properties are serialized into properly encoded parameters to
be passed to the request, or an array of objects whose name and value
properties specify the name/value pairs.
If specified as an object or array, the request is made using the POST method.
If omitted or specified as a string, the GET method is used.
callback (Function) An optional callback function invoked after the response data has
been loaded into the elements of the matched set. The parameters passed to
this function are the response text, a status string (usually “success”), and the
XHR instance.
This function will be invoked once for each element in the wrapped set with the
target element set as the function context (this).
Returns
The wrapped set.

Comments

Popular posts from this blog

Quicksort implementation by using Java

 source: http://www.algolist.net/Algorithms/Sorting/Quicksort. The divide-and-conquer strategy is used in quicksort. Below the recursion step is described: 1st: Choose a pivot value. We take the value of the middle element as pivot value, but it can be any value(e.g. some people would like to pick the first element and do the exchange in the end) 2nd: Partition. Rearrange elements in such a way, that all elements which are lesser than the pivot go to the left part of the array and all elements greater than the pivot, go to the right part of the array. Values equal to the pivot can stay in any part of the array. Apply quicksort algorithm recursively to the left and the right parts - the previous pivot element excluded! Partition algorithm in detail: There are two indices i and j and at the very beginning of the partition algorithm i points to the first element in the array and j points to the last one. Then algorithm moves i forward, until an element with value greater or equal

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know. Symptom: 1.        The JVM became Out of memory when creating big consumption report 2.        Those JRTemplateElement-instances is still there occupied even if I logged out the system Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.     The clearobjects() method in ReportThread class has not been triggered when logging out Action I tried:      About the Virtualizer: 1.     Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.     Not use any FileVirtualizer for cache the report in the hard disk Result: The japserreport still creating the a large number of JRTemplateElement-instances in the memory        About the work around below,      I tried: item 3(in below work around list) – result: it helps to reduce  the size of the JRTemplateElement Object        

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold  highlighted in example below) which resolve the problems.   example: <band height="20" splitType="Stretch" > <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/>