maybe sling <http://sling.apache.org/site/index.html> can fit in all your requirements... but I agree with Christopher, all you requirements point to a J2EE application
Miguel On Tue, Mar 2, 2010 at 11:45 AM, Christopher Armstrong < [email protected]> wrote: > Hi > > I don't know what you are looking for from this list, but you are unlikely > to find it. > > At a quick glance, the requirements you mention below could be easily > fulfilled by a enterprise J2EE stack or written into a lightweight container > framework like Spring. > > Why do you need OSGi? > > You are also unclear on what you mean by "a separate process per JVM". All > Java applications, including a running OSGi framework, use one process per > JVM instance. If you mean a single process per requirement, that still is > not unusual - using something like JMS for integration would fit well with > such an architecture. > > Cheers > Chris > > On 02/03/2010, at 20:59 PM, Abhishek kapoor wrote: > > Dear Member, > > Thanks for reading this email. I need your kind help regarding convincing > my manager to adopt OSGI in our future development. > > Below is the current application architecture > > We are telecom company and at the moment we use separate JVM per process > for our middleware for Order management system. > > Below are the general overview of the all the process > 1) Fetch data [ JDBC]from DB do some processing insert the processed > data into DB > 2) One of the process send data outside our system through webservice > 3) One of the process receive data from outside and pushes into DB so > that our internal process can work accordingly > 4) Each process polls the data at given specified time for it > processing > > 5) Each process also use extensive logging > > Since it is a legacy system I do understand the above mentioned process > flow is horrible. I guess in past developers decided single process per JVM > to achieve modularity. > > > Any Help is appreciated > > Any case history related to telecom to convince my manager will highly > beneficial > > > Thanks > > San > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > > > -------- > Christopher Armstrong > [email protected] > > > > > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev >
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
