Stephen B. Morris

Stephen Morris is an independent writer/consultant based in Ireland. Widely experienced in enterprise development and networking applications, Stephen has worked for some of the world's biggest networking companies. Projects include: JEE/J2SE-based network management systems, billing applications, financial systems, porting/developing SNMP entities, network device technologies, and several mobile computing applications. He holds a master's degree in computer science and holds three patents in the area of network management. In 2003, Stephen wrote his first book, Network Management, MIBs and MPLS: Principles, Design and Implementation (Prentice Hall). Stephen's second book followed in 2007, entitled: Moving Your Career Up the Value Chain: Building Specialized Development Skills in a Global Economy (InformIT). He has also written numerous articles and tutorials on network management and other topics for Informit, IBM developerWorks and O'Reilly (OnJava.com and Java.net).

Articles

Protect Your Legacy Code Investment with JNA
The promise of Java Native Access (JNA) is to bridge the worlds of Java and legacy code. Why is this so important? For one, JNA obviates the need to rewrite legacy code where the option of a rewrite exists. Also, JNA means that expensive proprietary bridging solutions are no longer needed. May. 20, 2009

Role-Based Code Upgrade
When you upgrade one feature that will only be used by a small set of users, why should you have to update the entire application for all your users? Stephen B. Morris proposes a model of updating just what's needed, and only for who needs it. Mar. 8, 2007

Aspect Oriented Programming and Internationalization
If you leave internationalization for the end of your project, chances are you're going to find it a challenge. But as a cross-cutting concern that's needed throughout an app, could I18N be seen as a task for aspect-oriented programming? Stephen B. Morris argues for this approach and shows how it can work. Jul. 25, 2006

Separation of Concerns and BPEL
Should a business process just be one more software feature? Not according to proponents of Business Process Execution Language (BPEL). Stephen B. Morris says that separating your business process code, via BPEL, from the rest of your business logic gives you robustness, pluggability, and customizability that's otherwise difficult to obtain. Feb. 14, 2006

java.net RSS Feeds