The problem I have with all of this is that it just seems like we're putting the cart before the horse. But of course! That's what IT does: "Here's a really cool solution. Let's go find a problem to solve with it!" :) The definition of what an ESB does will be ever-changing, just as the definition of what an application server does has been ever-changing. It's a fruitless exercise to try to nail it down. I disagree. There are lots of smart people reading, why not collaborate, come up with a definition that we can agree upon based on our needs and then tell the vendors what an ESB is? We can change the definition as we need it to change. -- email: [EMAIL PROTECTED]
- [service-orientated-architecture] ESB Standard Definition Bill Barr
- Re: [service-orientated-architecture] ESB Standard Defini... Steve Jones
- Re: [service-orientated-architecture] ESB Standard De... Todd Biske
- RE: [service-orientated-architecture] ESB Standar... Bill Barr
- RE: [service-orientated-architecture] ESB Sta... Anil John
- RE: [service-orientated-architecture] ES... Bill Barr
- RE: [service-orientated-architecture... Anil John
- RE: [service-orientated-architec... Bill Barr
- Re: [service-orientated-architecture] ESB Standar... Jerry Zhu
- Re: [service-orientated-architecture] ESB Sta... Todd Biske
- Re: [service-orientated-architecture] ES... Jerry Zhu
- Re: [service-orientated-architecture... Steve Jones
- RE: [service-orientated-architec... Bill Barr
- Re: [service-orientated-architec... Steve Jones
