Tag: NetBeans

NetCat 7.4 starts today

You may have noticed the upcoming version of NetBeans 7.3.1 (including GlassFish 4.0) will be available soon. But, do you prefer to take a look further on into the future of this IDE?

Today the start of the NetBeans Community Acceptance Testing program (NetCAT) [1] of next version (7.4) has been announced. If you like, get involved into that program. Develop on the bleeding edge and report your experience (bugs, enhancement suggestions, …) directly to the NetBeans team.

Do you want to know some features this version is going to offer? Read [2].

[1] http://wiki.netbeans.org/NetCAT
[2] http://wiki.netbeans.org/NetBeans_74_NewAndNoteworthy

 

NetBeans Java EE7

By now, GlassFish 4 is still not bundled to NetBeans daily builds. You have to install it separate as I described in an former article [1].

Do you want to know about the upcoming Java EE 7 support? A bunch of tasks and features is decribed in the the NetBeans wiki [2].

[1] http://blog.mueller-bruehl.de/netbeans/set-up-netbeans-for-java-ee7/
[2] http://wiki.netbeans.org/JavaEE7

 

JSF 2.2 Proposed Final Draft Posted

The JSF 2.2 Proposal Final Draft was posted by the expert group spec leader Ed Burns today. Read his blog about this issue [1]. The draft is available at the JCP JSR 344 page [2].

JSF 2.2 is included in GlassFish4. I’m still waiting for this GF4 being bundled with NetBeans daily builds. Continue reading “JSF 2.2 Proposed Final Draft Posted”

Set up NetBeans for Java EE7

NetBeans 7.3 is almost ready. I guess, it takes just a few day until it is available. Even though this version offers new great features [1], one thing is still missing: Support for Java EE7. You may wait for an update – or try the development version. This article describes, how to setup NetBeans with GlassFish 4 for use as early Java EE7 environment. Continue reading “Set up NetBeans for Java EE7”

NetBeans proposal: Unified method to create projects

During the current NetCAT game, I pointed out that division of projects into categories is not logical. While Ant based Java project resides under Java > Java Application (category > concrete project type), the Maven based one can be found under Maven > Java Application (Maven > concrete project type). I suggested to join both wizards and let user choose the build system in a new wizard step.

Jiří Kovalský (NetBeans quality manager) requested me to file an issue. I just did it. Issue #224999 [1]

If you want to second this, please feel free to vote for it.

[1] http://netbeans.org/bugzilla/show_bug.cgi?id=224999

 

Tutorial web development (with JSF) IX – Application “Books”, Part II

In part VII of this tutorial you’ll find some requirements of the book application. The application is live now, and you can find it here [1]. The information about the books and the reviews is stored in a database. JavaServer Faces is well suited for database   driven server applications. Thus, developing web applications with JSF normally includes developing with database techniques. In the context of Java EE 6, this usually would be Java Persistence API (JPA). And often it touches other techniques like Context and Dependency Injection (CDI), Bean Validation and other stuff. The book application will use a couple of this too. Continue reading “Tutorial web development (with JSF) IX – Application “Books”, Part II”

Tutorial web development (with JSF) VIII: Backstage

In a traditional application, usually the application itself is responsible for the presentation. Even if you should use a special display sever such as X, it is still controlled by the application.

Unlike in a web application. Here the data is passed to a browser, which takes care of the presentation. To do such, the server packs the content to display into in a (X) HTML document. In addition, the server may provide some layout information in the form of cascading style sheets (CSS). Then, everything else is up to the browser. And just as there are different browsers, the representation can be different. The continuous development of standards ensures here fortunately a gradual convergence. But, if the user keeps a local CSS here, then the presentation again might be different. Continue reading “Tutorial web development (with JSF) VIII: Backstage”

Rename property

In Java development, if you have a private attribute with corresponding public getter/setter pair, this is usually treated as just one property. NetBeans has the ability to rename this getter and all it’s occurrencies in the Java sources. The same way, NetBeans supports to rename the setter.

Within a JSF page, you just use this getter/setter pair as a single attribute. How shall NetBeans perform a rename? It can’t. But if NetBeans would rename both, getter and setter, with just one refactoring step, it would be able to rename it within the JSF page too.

If you like such a feature, please support my proposal for enhancement by voting for it here [1].

[1] http://netbeans.org/bugzilla/show_bug.cgi?id=224242

Vote for NetBeans enhancements

Alle Artikel sowohl auf Deutsch als auch auf Englisch – das ist relativ viel Aufwand. Programmiersprachen sind meist in Englisch und die meisten Entwickler verfügen über mindestens ausreichende Englisch-Kentnisse. Ich adressiere daher Entwickler-Themen nunmehr vornehmlich in Englisch. So aktuell auch zu von mir angeregten NetBeans-Erweiterungen.

Einfach den “English”-Button rechts unter Sprachen anklicken und die Artikel werden gelistet…

Update: Ich habe den Blog nun so eingestellt, dass alle englischen Artikel, für die keine Ãœbersetzung existiert, im Original angezeigt werden.