|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
More Genericity Needed
Submitted by timsabin on Wed, 11/26/2008 - 16:59.
Back to:
www.javaworld.com/javaworld/jw-10-2004/jw-1004-soa.html.
What is needed is more genericity in the ServiceRouter. All it needs to be is an XML parser to parse a config file, blindly instantiate the named service manager, and run a pre-specified method (execute ()?). This would allow for an infinite number of service managers. It also makes the ServiceRouter 100% binding-free, with the exception of an interface that all service managers must implement. Write me at tim@timsabin.com for an example implementation of this.