|
|
Recommended: Sing it, brah! 5 fabulous songs for developers
JW's Top 5
Featured White Papers
- Measuring Risk to Improve Java Software Quality
- 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
Sponsored Links
-
Graph databases are 1000x faster than relational.
Learn More!
-
Career opportunities at Harman- Careers That'll Rock Your Socks Off.
Learn More!
-
Developer-friendly Java PDF libraries by Qoppa Software
Live Demos
-
Stop blaming your app! Diagnose Java performance issues.
Free tool >
-
UrbanCode: Go From Continuous Integration to
Continuous DeliveryLearn More!
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.
About Us | Advertise | Contact Us | Terms of Service/Privacy | AdChoices
Copyright, 2006-2013 Infoworld, Inc. All rights reserved.