Hi, as an unseasoned spring user, I'm still not sure if this is the right approach. The goal of my current project is to split up a monolithic system into different modules (reusable by other future applications). Some of these modules are to be resources of another. These modules will each have their own Spring application context using resources exposed by JNDI (of the app server). They will also communicate using JMS (of the app server). Simply put, I don't want everything defined in the application context since they may be reused by future projects, nor do I want JMS to be tied to a specific application context. Is this reasoning plausible? Or would you guys suggest a better way of doing it?
Login or Sign Up
- Log in with