Tag Archives: java

Chrome 42 and Java Plugin

Oracle Forms users might have noticed that the Oracle Forms Java applet does not work anymore in the latest Chrome browsers. Here’s how to enable it manually (until September 2015).

Java applets use a plugin technology called NPAPI within the browser to render the Oracle Forms application. Google sees the API as a stability and security risk. The Chrome development team has disabled NPAPI by default in Chrome 42 and will be completely removing the API from Chrome 45 in September 2015. It can be enabled manually until September.

NPAPI stands for Netscape Plugin Application Programing Interface and is being used by many browsers such as Firefox and Internet Explorer. It’s an old API introduced in 1995 to run plugins within the browser like for example MP3s, PDFs or Java applets with Oracle Forms. Most applications including playing MP3s and viewing PDFs are now already natively supported by the browsers and HTML5.

Since the plugin is disabled by default, it needs to be enabled manually again. This can be done using a few steps:

  1. Within the browser bar, type in the following URL: chrome://flags/#enable-npapi
  2. Click on the enable link underneath Enable NPAPI.
  3. Click on the relaunch button at the end of the page to restart the browser.

See the screenshot underneath for enabling NPAPI in Chrome 42 and up:


Note that this fix is a just a temporary solution, which will work until Chrome 45 in September. For a long term solution, we would recommend to use another browser like Firefox or Internet Explorer. Mozilla sees NPAPI as legacy, but is not planning to remove it any time soon. Microsoft will drop plugin support in their newest browser called Edge. With the amount of support decreasing over the coming few years, it might be time to start looking into an alternative like a migration to ADF or an open source solution.

See the following links for more information:

Blog by: Arvind Mohabir

The Rise of Single Page Applications (SPA) in your Enterprise: Fast and easy with QAFE!

A couple of years ago plugin technologies like Adobe Flex and Microsoft Silverlight were popular. Nowadays we see that HTML5 technology and corresponding Javascript libraries are showing the most amazing things in the Web! Things we could never imagine before.

The pace with which new Web Application frameworks are appearing has never been higher. It feels like every two weeks there is something new, cool and better.

The mindset of QAFE is to be independent of this trend, yet be able to use all new technologies.

That is why we liked reading this article on the Rise of Single Page Applications (which QAFE is from day one when we started with it), showing the mindset of how modern applications are being built and the reasons to do so.

To have a good idea of where we are with the web, this video of Pamela Fox (ex-Googler, now at Coursera) is a great intro:

(check out around 07m:00s for the explanation of what happened with the web).

When we started QAFE in 2007 we anticipated this happening: the day that Single Page Applications were going to be the standard for Web Applications. And the good news today is that with QAFE we made it accessible to everyone!

In a matter of minutes you’ll have a Single Page Application running in your browser.

Consider that most Enterprises have Oracle Forms applications: Wouldn’t it be great if that technology stack was modernized to a Single Page Application architecture, in such a way that even more is possible with that application! Imagine the other opportunities when this part of your application stack is modernized.

To Summarize: Want to have Single Page Applications in your Enterprise (and modernize your legacy stack) or in the Cloud, QAFE can help you out. If you’re a developer, please see

All questions, thoughts, ideas are most welcome.

Note: Even though page-oriented frameworks can use AJAX, they are have a totally different mindset, approach and architecture compared to Single Page Applications. See the article on the Rise of Single Page Applications.

QAFE & Agile

 At Oracle OpenWorld/JavaOne 2011, there was a presentation by Adam Bien. The subject was on “Real World Java EE Patterns Rethinking Best Practices” (here’s the book).

One of the interesting points made, was about the fact that customers don’t pay you as a developer to create an architecture that is ready for any situation. The customer pays you for the solution and you as a developer to focus on that.

Why would you create a whole architecture with Delegates, DOA, Service Locator if you are really not using it. Furthermore, JPA’s EntityManager is already quite powerful. Why make it more complex ?

We, QAFE Team, agree with Adam. Don’t use Design Patterns for the sake of Design Patterns, but only when there is a real need for it. The developer should apply the Agile way of developing where you continuously refactor code where necessary.

QAFE supports this idea in technical implementation but still considers the Design Patterns. Creating Classes and structures based on Design Patterns can be very cumbersome. But what if this architecture is already defined for you and you just have to use it and focus on your deliverables? That’s exactly what QAFE supports.

Oracle OpenWorld 2011, Larry Ellison, ADF and QAFE

Oracle OpenWorld 2011 was a great week. Now is the time to reflect. In one keynote Larry Ellison focused on the need for industry standards. Even Oracle’s own product like Oracle Forms was disregarded, since it doesn’t follow the Java/JEE standards. The portability to other platforms apparently is what customers and Oracle want.

We agree with that. A note needs to be made though. Although we (QAFE) develop conforming to standards, we also learned from the past. For example, EJB2.1 was also an industry standard but failed miserably.  Allthough JSF is an industry standard, it is not necessarily the best solution in the era of webtechnologies that we are in. See this link:

To give an example where the web is moving towards, see

The new trends seems to be HTML5 and lots of javascript libraries and javascript toolkits.

To summarize, from QAFE’s point of view, we agree with what Larry Ellison said except for the ADF. We believe that modern web technology is needed for the next generation of applications. Being future proof is something we define by nót choosing a specific technology, but by embracing áll.

Try our drag ’n drop QAML UI Builder!

If you request your free trial license key on you will notice we added the option to download the QAML UI Builder extension as well! The extension is an Eclipse (3.5) plug-in that allows the creation of a web application without hardly any knowledge of Java, HTML or QAML. As long as you can ‘draw’ it with this extension, QAFE does the rest and the app will be directly available in Flex or GWT (or whichever other supporting Web 2.0 environment). On your mark? Get set… start building!