Robin wrote: > But there is a more fundamental thought. Java, C# are not XML, these > languages are object oriented and you will likely use internal object > models in your implementation. You will have to map your XML to > objects. > On the other side of the service, you will likely use a relational > database. Guess what, Java, C# are not relational minded either. You > will end up with a mapping between the Java code and the database too.
I find this statement to be very telling. The impedence mismatches are where value added software development has always been. Make a particular type of operation easier, or even possible, is where the flexibility of software trumps embedded, proprietary hardware every time. One of the many ways that people feel the pain of these impedence mismatches is through the attempts to use multiple systems' evolution to create the solution. At some point, you have to decide that the solution is above the "bus". But, many people find it much easier to change the signals on the bus then plug in a monitor for the signals and react to what is on the bus. It will be very interesting to see how innertwined the software and the "bus" become before people finally understand about SOA vs BOA. Gregg Wonderly ------------------------ Yahoo! Groups Sponsor --------------------~--> Most low income households are not online. Help bridge the digital divide today! http://us.click.yahoo.com/cd_AJB/QnQLAA/TtwFAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
