Karaf's WebConsole as a web portal for all features?

[dantran]

Hello Karaf team,

I am thinking of tapping to Karaf's webconsole subproject to implement
my feature's specific WebUI.  This way I can reuse most of the
infrastructures like login, rolebase authorization..

is it the right direction?

Thanks

-Dan

[Łukasz Dywicki]

Hey Dan,
Sure you can re-use webconsole codebase. The login infrastructure basically delegates authorization to JAAS realm named karaf. If you will need any assistance wit extensions, just type to dev@. We are more than happy to help you. There are few base classes than you can extend to get basic L&F in place. To extend navigation you simply publish NavigationProvider implementations in OSGi service registry.

Best regards,
Lukasz

Wiadomość napisana przez Dan Tran w dniu 27 kwi 2012, o godz. 19:53:

> Hello Karaf team,
>
> I am thinking of tapping to Karaf's webconsole subproject to implement
> my feature's specific WebUI.  This way I can reuse most of the
> infrastructures like login, rolebase authorization..
>
> is it the right direction?
>
> Thanks
>
> -Dan

[dantran]

Hi Lukasz,

So I can just implement my own bundles with all hooks required by
webconsole.  How do you integrate? in term of packaging?  Do i need to
be part of WebConsole feature?

Thanks

-D



On Fri, Apr 27, 2012 at 2:54 PM, Łukasz Dywicki <[hidden email]> wrote:

> Hey Dan,
> Sure you can re-use webconsole codebase. The login infrastructure basically delegates authorization to JAAS realm named karaf. If you will need any assistance wit extensions, just type to dev@. We are more than happy to help you. There are few base classes than you can extend to get basic L&F in place. To extend navigation you simply publish NavigationProvider implementations in OSGi service registry.
>
> Best regards,
> Lukasz
>
> Wiadomość napisana przez Dan Tran w dniu 27 kwi 2012, o godz. 19:53:
>
>> Hello Karaf team,
>>
>> I am thinking of tapping to Karaf's webconsole subproject to implement
>> my feature's specific WebUI.  This way I can reuse most of the
>> infrastructures like login, rolebase authorization..
>>
>> is it the right direction?
>>
>> Thanks
>>
>> -Dan
>

[Andreas Pieber]

Hey Dan,

On Sat, Apr 28, 2012 at 02:02, Dan Tran <[hidden email]> wrote:
> So I can just implement my own bundles with all hooks required by
> webconsole.  How do you integrate?

Basically it's extending an interface and register it as osgi service;
best to look at the webconsole code or wait for lukasz' comment.

> in term of packaging?

Nothing to do here; the extensions are own packages.

>  Do i need to
> be part of WebConsole feature?

No you don't. You're your own bundle; the remaining issues are handled by osgi.

>
> Thanks
>
> -D
>
>
>
> On Fri, Apr 27, 2012 at 2:54 PM, Łukasz Dywicki <[hidden email]> wrote:
>> Hey Dan,
>> Sure you can re-use webconsole codebase. The login infrastructure basically delegates authorization to JAAS realm named karaf. If you will need any assistance wit extensions, just type to dev@. We are more than happy to help you. There are few base classes than you can extend to get basic L&F in place. To extend navigation you simply publish NavigationProvider implementations in OSGi service registry.
>>
>> Best regards,
>> Lukasz
>>
>> Wiadomość napisana przez Dan Tran w dniu 27 kwi 2012, o godz. 19:53:
>>
>>> Hello Karaf team,
>>>
>>> I am thinking of tapping to Karaf's webconsole subproject to implement
>>> my feature's specific WebUI.  This way I can reuse most of the
>>> infrastructures like login, rolebase authorization..
>>>
>>> is it the right direction?
>>>
>>> Thanks
>>>
>>> -Dan
>>

[dantran]

Thanks Andreas, I am looking at the webconsole source, and it is very promising.

Basically webconsole/osgi infrastructure allows various groups in my
company have their own mount points and navigation entries.


Thanks

-D


On Sun, Apr 29, 2012 at 9:09 AM, Andreas Pieber <[hidden email]> wrote:

> Hey Dan,
>
> On Sat, Apr 28, 2012 at 02:02, Dan Tran <[hidden email]> wrote:
>> So I can just implement my own bundles with all hooks required by
>> webconsole.  How do you integrate?
>
> Basically it's extending an interface and register it as osgi service;
> best to look at the webconsole code or wait for lukasz' comment.
>
>> in term of packaging?
>
> Nothing to do here; the extensions are own packages.
>
>>  Do i need to
>> be part of WebConsole feature?
>
> No you don't. You're your own bundle; the remaining issues are handled by osgi.
>
>>
>> Thanks
>>
>> -D
>>
>>
>>
>> On Fri, Apr 27, 2012 at 2:54 PM, Łukasz Dywicki <[hidden email]> wrote:
>>> Hey Dan,
>>> Sure you can re-use webconsole codebase. The login infrastructure basically delegates authorization to JAAS realm named karaf. If you will need any assistance wit extensions, just type to dev@. We are more than happy to help you. There are few base classes than you can extend to get basic L&F in place. To extend navigation you simply publish NavigationProvider implementations in OSGi service registry.
>>>
>>> Best regards,
>>> Lukasz
>>>
>>> Wiadomość napisana przez Dan Tran w dniu 27 kwi 2012, o godz. 19:53:
>>>
>>>> Hello Karaf team,
>>>>
>>>> I am thinking of tapping to Karaf's webconsole subproject to implement
>>>> my feature's specific WebUI.  This way I can reuse most of the
>>>> infrastructures like login, rolebase authorization..
>>>>
>>>> is it the right direction?
>>>>
>>>> Thanks
>>>>
>>>> -Dan
>>>

[Andreas Pieber]

yep, the main logic behind this is provided by pax wicket. IMHO it
depends what you want to do. If it's more a development infrastructure
you want to provide using the webconsole is a very great idea; in case
you would like to create an "own" application it might be better to
consider creating a new application. Pax-Wicket allows you to keep
both side by side. The entire mounting logic, osgi logic, and so forth
is coming from pax-wicket and not the webconsole.

Kind regards,
Andreas

On Sun, Apr 29, 2012 at 18:27, Dan Tran <[hidden email]> wrote:

> Thanks Andreas, I am looking at the webconsole source, and it is very promising.
>
> Basically webconsole/osgi infrastructure allows various groups in my
> company have their own mount points and navigation entries.
>
>
> Thanks
>
> -D
>
>
> On Sun, Apr 29, 2012 at 9:09 AM, Andreas Pieber <[hidden email]> wrote:
>> Hey Dan,
>>
>> On Sat, Apr 28, 2012 at 02:02, Dan Tran <[hidden email]> wrote:
>>> So I can just implement my own bundles with all hooks required by
>>> webconsole.  How do you integrate?
>>
>> Basically it's extending an interface and register it as osgi service;
>> best to look at the webconsole code or wait for lukasz' comment.
>>
>>> in term of packaging?
>>
>> Nothing to do here; the extensions are own packages.
>>
>>>  Do i need to
>>> be part of WebConsole feature?
>>
>> No you don't. You're your own bundle; the remaining issues are handled by osgi.
>>
>>>
>>> Thanks
>>>
>>> -D
>>>
>>>
>>>
>>> On Fri, Apr 27, 2012 at 2:54 PM, Łukasz Dywicki <[hidden email]> wrote:
>>>> Hey Dan,
>>>> Sure you can re-use webconsole codebase. The login infrastructure basically delegates authorization to JAAS realm named karaf. If you will need any assistance wit extensions, just type to dev@. We are more than happy to help you. There are few base classes than you can extend to get basic L&F in place. To extend navigation you simply publish NavigationProvider implementations in OSGi service registry.
>>>>
>>>> Best regards,
>>>> Lukasz
>>>>
>>>> Wiadomość napisana przez Dan Tran w dniu 27 kwi 2012, o godz. 19:53:
>>>>
>>>>> Hello Karaf team,
>>>>>
>>>>> I am thinking of tapping to Karaf's webconsole subproject to implement
>>>>> my feature's specific WebUI.  This way I can reuse most of the
>>>>> infrastructures like login, rolebase authorization..
>>>>>
>>>>> is it the right direction?
>>>>>
>>>>> Thanks
>>>>>
>>>>> -Dan
>>>>