Hi all,
I have a question that is more of a general OSGi nature. For a legacy application, that’s already running in an OSGi container, I’d like to provide a Web Service interface. - At the moment this application uses some non-standard, socket-based protocol. - It’s all pretty monolithic – all in one big bundle. My first idea was to simply expose the functionality of this application as an OSGi service and create a second bundle that consumes this OSGi service and exposes it as a Web Service. Does that sound reasonable? Not sure what the standard-approach is for such use cases. cheers, Richard
