> On 8 Mar 2017, at 11:37, rama.g <ram...@utthunga.com> wrote:
> Dear Peterus
> We discarded OSGI enroute, decided to go with OSGI framework.
Well, OSGi enRoute IS an OSGi framework, there is nothing specia? OSGi enRoute
just collects best practices but is nothing but a normal OSGi framework with
open source bundles.
> We created plugins related to both backend (RESR APIS) and front end (angular
> JS static files) are bundled using OSGI framework. UI components are bundled
> separately.
So what is the difference? This is exactly the OSGi model?
> Using HTTP services we are able to register resources like HTML/JS/CSS static
> files in the main application. When a second plugin (which has static files
> same structure as that of main application) is created, we are unable to
> invoke the static files using localhost, getting 404 error
Why? I’ve seen applications with multiple bundles providing resources.
The OSGi enRoute supports a bundle that maps the static directory to the local
web server using the extender pattern. It allows overlapping directories with
different resources, it will merge them. Except for the caching and compression
that it does this is quite a simple mechanism. It clearly works in setups with
different static resource providers. It would be nice if you could find out why
you get a 404. In the case that it is really something in OSGi enRoute, which I
find very unlikely, then we could at least fix it?
A bit puzzled? Kind regards,
Peter Kriens
>
> Thanks and Regards
> Rama G
>
>
> From: osgi-dev-boun...@mail.osgi.org [mailto:osgi-dev-boun...@mail.osgi.org]
> On Behalf Of Peter Kriens
> Sent: Tuesday, March 07, 2017 6:36 PM
> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org>
> Subject: Re: [osgi-dev] OSGI support needed bundling web application
>
> A bit confused about the terminology … So let me verify:
>
> backend Java code wrapped in a bundle
> implementing a REST API
> frontend Angular Java code
>
> In enRoute the frontend would be stored in the application project. (In the
> static directory.) Your REST backend would be provided as a provider. The
> application project would depend on the provider so that if you resolve the
> REST provider is dragged in with its dependencies.
>
> Kind regards,
>
> Peter Kriens
>
>
>
>
>>
>> On 7 Mar 2017, at 12:23, rama.g <ram...@utthunga.com
>> <mailto:ram...@utthunga.com>> wrote:
>>
>> Dear Peter
>> You are right. this example. In this case both front end and backend are
>> bundled together. My use case is backend to be bundled separately, front end
>> to be bundled separately as they are developed by two different vendors.
>> My current scenario is that, backend rest APIs are bundled on OSGI
>> framework. Front end I have used OSGI Enroute?. I want an interface between
>> the backend plugin and frontend plugin. How can this be established
>>
>> Is it easy to port the backend from OSGI to OSGI Enroute
>>
>> Thanks and Regards
>> Rama G
>>
>> From: osgi-dev-boun...@mail.osgi.org <mailto:osgi-dev-boun...@mail.osgi.org>
>> [mailto:osgi-dev-boun...@mail.osgi.org
>> <mailto:osgi-dev-boun...@mail.osgi.org>] On Behalf Of Peter Kriens
>> Sent: Tuesday, March 07, 2017 4:08 PM
>> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org
>> <mailto:osgi-dev@mail.osgi.org>>
>> Subject: Re: [osgi-dev] OSGI support needed bundling web application
>>
>> Did you follow the OSGi enRoute tutorials? The application template seems to
>> do exactly what you want.
>>
>> Kind regards,
>>
>> Peter Kriens
>>
>>> On 7 Mar 2017, at 11:35, rama.g <ram...@utthunga.com
>>> <mailto:ram...@utthunga.com>> wrote:
>>>
>>> Dear sir / madam
>>> I need to know the kind of support OSGI framework provides to host web
>>> application for the given use case.
>>> I have my backend (rest APIs) developed independently using modular
>>> approach . I have set of User components developed using Angular java
>>> corresponding to each backend module. We are required to bundle the backend
>>> and UI components separately for ease of maintenance , but when I deploy
>>> the product to the user he should visualize as a single plugin (combination
>>> of backend and UI)
>>> Please suggest OSGI solution required to meet the above use case
>>>
>>> Assuming that the backend is already bundled in OSGI framework, suggest a
>>> method to bundle UI components which works in collaboration with the backend
>>>
>>> Thanks and Regards
>>> Rama G
>>>
>>> _______________________________________________
>>> OSGi Developer Mail List
>>> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
>>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>>
>> _______________________________________________
>> OSGi Developer Mail List
>> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
> https://mail.osgi.org/mailman/listinfo/osgi-dev
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
