I had referenced Ted Wise's post Using Java 1.5 and Java 1.4 on Snow Leopard in a project, and happened to notice a comment from a week ago about someone having trouble getting Java 1.4 to work in Mac OS X 10.7/Lion, so I decided to check it out, since I might also run into it later.
Using Nerot for Scheduled Task-based Caching of RSS, HTTP Get, or Custom Java Method Execution Results
If you need guaranteed fast response time and simple caching on an unruly RSS feed, some other HTTP resource accessible via HTTP Get, or for that matter just about any Java static or instance method, check out Nerot.
First off, I want to thank Apple for being such big supporters of Java. You may have gone off and done your own thing, but as Java developers, we still have to give some serious kudos.
Today I glanced into /usr/share/java in a CentOS release 5.2 (Final) server with Tomcat and Java installed via RPM. It literally burned my eyes, and hopefully you can see why.My eyes first caught this:
[prettify] libgcj-4.1.1.jar libgcj-4.1.2.jar -> libgcj-4.1.1.jar libgcj-tools-4.1.1.jar libgcj-tools-4.1.2.jar -> libgcj-tools-4.1.1.jar [/prettify] Owww!!! It burns!
For the several years (at least since mobile devices were able to browse the net in some form or fashion), companies and organizations have been interested (and increasingly so) in making their sites/web applications mobile-friendly.
But from what little I know, supporting mobile devices is not just as easy as a single differentiation in format.
As a follow-up from the previous article on the Interaction-Flow-Service-Model Architectural Pattern (IFSM), let's talk about suggestions for developing a more modular flow layer.
- All non-flow-related logic should be pushed to service layer (or an additional service-logic layer).
- Aim for
There is one thing that I've overlooked until today, which is the importance of the division of the controller into application "flow(s)" and application "service(s)". For a good while now, I had been keeping controller code separate from service code (which in turn called the DAOs, that used Spring DAO, that used Hibernate, that interacted with the DB, etc.).
Do you have almost no test coverage or perhaps none at all? Join the crowd. Although no one wants to admit it, a good part of the world runs on untested code.
Looking for information on how to quickly develop new JSR-168 and JSR-286 compliant portlets in an IDE an article called Developing Portlets with NetBeans Portal Pack 2.0.Those instructions appear to mostly be geared for those looking to develop JSR-286 compliant portlets, so if that's your goal, those i