Craig Walls: Message-Driven POJOs
Reading this article on the benefits of a POJO implementation instead of a full blown MDB EJB ie Message Driven Bean implementation along with app server. It starts to get into some of the benefits of using a less complicated infrastructure which I think is a good thing. It does raise the question in my mind, how do you account for and deploy POJO type applications. It's not as clean as deploying an app on an app server or even webMethods for that matter. Do you set up a dedicated infrastructure for POJO's or do you co-habitate with the app servers? What do others do? My thoughts are these types of apps can coexist with others. When talking JMS adapters, pushing out to the endpoints can make sense. Of course that can increase complexity, so management of those distributed objects must be accounted for. Any thoughts?