DROWN is a serious vulnerability that affects HTTPS and other services that rely on SSL and TLS, some of the essential cryptographic protocols for Internet security. DROWN allows attackers to break the encryption and read or steal sensitive communications, including passwords, credit card numbers, trade secrets, or financial data. Our measurements indicate 33% of all HTTPS servers are vulnerable to the attack.
Source:
https://access.redhat.com/security/vulnerabilities/drown
Primefaces is a open source UI component library for JSF based application. One such component to show data in tables is datatable. Datatable has a lot of features like paging, sorting, selection, lazy loading etc. Paging is a feature by which huge amount of data is displayed in pages. Some times there are cases to work with the page change event and also to set a page programmatically. Following is an extract from the stackoverflow answer to get the page change event using listener with the backing bean method handling the event:
<p:dataTable var="myVar" paginator="true" widgetVar="mydatatable" rows="1" value="#{myBean.listOfObjects}">
<p:ajax event="page" update="buttons" listener="#{myBean.update}" oncomplete="setTimeout(function(){ alert("Page Change Completed"); }, 0);" />
...
...
</p:dataTable>public void update(PageEvent event) {
int var = event.getPage();
...
...
...
}This works great, when the paging button is clicked the “update” method is called with the PageEvent object as argument, and using that object one can get a lot of info about the datatable like get the current page etc.
Now how about setting the page explicitly on the datatable in some other piece of backend code, Following are the 2 ways to set the page programmatically:
— set page by executing following client side code:
PF('widgetVar').getPaginator().setPage(pageindex);this can be done in any backend Java code using the RequestContext’s execute method
RequestContext.getCurrentInstance().execute("PF('widgetVar').getPaginator().setPage(pageno)");but be aware that when this method executes all the callbacks on the page event <p:ajax> element gets executed. Like in the above code “oncomplete” will be called and an alert with message will be shown.
— to avoid this callback to be called there is another way to set the page as shown below:
final DataTable d = (DataTable) FacesContext.getCurrentInstance().getViewRoot()
.findComponent("myDataTable");
int first = 0;
d.setFirst(first);
remember that the “first” argument is the index of the of the row to be displayed and not the page number. The above code can be executed from any backend bean and the callbacks do not get executed.
Further Reading:
I am a bit late on this post but its still May which marks the beginning of a faster web protocol. Chrome and Firefox already are capable for HTTP/2. Also while we wait for Servlet 4.0 to have HTTP/2, Jetty has already done quite some work on it. Apache HttpClient is also still awaited to use the new protocol. Following is how the protocol has evolved as derived from Akamai website.
Well it seems that the combination of HTTP/2 + HTML 5 is going to make a huge difference the way the pages load in our browsers now. Cant wait to see it all happen!!
Further Reading:
http://www.infoworld.com/article/2916551/java/http-2-jumpstart-introduction-for-java-developers.html
Its free as of now the “Skype Translator preview app”, i think its worth a try with a friend that does not know your language.
 | Andry on Ftplet – Servlet for Apa… |
 | Viktor on [Java FX 2] Stage with rounded… |
 | Other World on [Docker for Windows] Certifica… |
 | Marek on [Java FX 2] Stage with rounded… |
 | arpan on [Docker for Windows] Certifica… |
{apilevel.com} 