|
I don't see how you could function without some sort of servlet or CGI application behind a web server though. All of the technologies the Yakov mentions would probably sit behind a web server of some kind. Most of what he mentioned I pulled together in the "Developing SOA Applications using Open Source Tools" at Common last month (you can find it at www.opensource4iseries.com if you are interested). Specifically the ActiveMQ/MOM/JMS stuff with Derby (JDBC) and a few other technologies (like Axis).
I still don't see that combination being easy to implement but leaving a J2EE container out of the mix makes life simpler. My clue that EJB's were evil was when I walked through the JMS tutorial and saw a 15 line Java program (easy to follow) followed by 15 deployment steps that deployed the class to the server. Made the racing guide gag in the Marx Brothers film "A Day at the Races" look simple.
Pete Helgren Jon Paris wrote:
Interesting article if you haven't seen it. http://java.sys-con.com/read/204697.htm But then I'm biased because I've always felt that App Servers are total overkill for small and medium load systems. Jon Paris Partner400 www.Partner400.comwww.RPGWorld.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.