Java Developer Magazine

I don’t know any other technology that has ever gotten as much of a beating as JavaFX did last week (here, here, and here). JavaFX has become a technology that developers love to hate. It’s like a pinata for developers. JavaFX was first announced at JavaOne 2007 (that’s 3 years ago). Many predicted its death even before version 1.0 was released in December 2008, and many continue to call for its demise. Last week also turned out to be the week where I presented Enterprise JavaFX at the Silicon Valley JavaFX JUG, and also the week that Steven Chin created a petition to open source JavaFX. Don’t get me wrong, JavaFX is very far from perfect. It has it’s problems and challenges (listed below) and its future is hanging on life support right now, but let’s start with the good. The good stuff JavaFX Script is a very powerful language. In fact, it’s a DSL (Domain Specific... (more)

Jinfonet Announces JReport 10

Jinfonet Software, a provider of Java reporting solutions, on Thursday unveiled JReport 10. This new version adds rich visualization and interactive reporting to a robust, agile BI platform, providing embedded operational reporting to developers and self-service reporting to end users. JReport 10 brings Agile Business Intelligence to the next level with rich visualization features.  Web 2.0 self-service reporting allows highly interactive reports to be accessible across the enterprise with superior performance and scalability. Rich visualization promotes better understanding of d... (more)

Top Ten Performance Problems

For your reference, we've compiled a list of the Top 10 Performance Problems as we have seen them over the years when working with our clients. I hope this list is enlightening – and I’ve included follow-up links to the blogs to help better understand how to solve these problems: #1: Too Many Database Calls The problem we see the most are too many database query per request/transaction. There are 3 specific phenomena to witness: More data is requested is than actually required in the context of the current transaction, e.g.: requesting all account information instead of those tha... (more)

Exploring Persistence Settings - Part 5

In Part 4 I discussed the Oracle Enterprise Pack for Eclipse and how it allows you to view, create, and manage JPA entity relationships. The Entity Editor provides a centralized view of all entity relationships, allows you to modify entity properties, and allows you to navigate between the object model, mapping associations, and database schema layers. In Part 5, I will explore persistence settings. The persistence.xml file defines the context for JPA persistence. In this step, you will use the JPA Persistence Configuration Editor to explore the persistence.xml file for your JPA... (more)

Unveiling the java.lang.Out OfMemoryError

When we encounter a java.lang.OutOfMemoryError, we often find that Java heap dumps, along with other artifacts, are generated by the Java Virtual Machine. If you feel like jumping right into a Java heap dump when you get a java.lang.OutOfMemoryError, don't worry, it's a normal thought. You may be able to discover something serendipitously, but it's not always the best idea to analyze Java heap dumps, depending on the situation you are facing. We first need to investigate the root cause of the java.lang.OutOfMemoryError. Only after the root cause is identified can we decide whether... (more)