Re: Architecting a heterogeneous Sling + Java EE application

[Robert Munteanu <ro...@apache.org>]

Hi Dmitry,

Sorry, this somehow slipped, see my answers below

On Fri, 2017-09-01 at 02:48 +0300, Dmitry wrote:
> Hi Robert,
> 
> Thanks a lot for an exhaustive explanation, things got much clearer
> now. But could you please elaborate a bit on the 3rd deployment
> option,
> specifically on what's the difference in general from the WAB
> scenario
> initially proposed by me? I thought "deploy OSGi (web-)bundle to
> Felix"
> and "deploy OSGi bundle to Sling" were equal notions, but turns out
> they aren't? (I guess the difference will be at least in using OSGi
> HttpService with the former scenario vs. Sling ResourceProvider with
> the latter.) Does it have something to do with the aforementioned
> "Sling provisioning"? Where can I read about it?

To me WABs are a transitional middle ground towards moving fully to
OSGi. I have not used them so far but by reading the spec I see that:

- a WAB requires application server support - a Web Extender
- a WAB still uses web.xml and the 'classic' JEE structure

It may make more sense to you to go the WAB route first but I suggest
you at least keep your options open and migrate to a pure OSGi setup.

Looking forward to hearing more about your progress, once there's news
about it :-)

Thanks,

Robert