On Fri, Jan 25, 2013 at 2:36 PM, Łukasz Dywicki <l...@code-house.org> wrote:

> I'm not angry. I'm just telling the truth. Nobody told to you yet.


Thx for that,  I think I was really erring on the dark side before ;-)


> Why you think it's bound to OSGi? We have WAR packaging.  Overall
> destination was always to support other runtimes.


The war packaging does start an OSGi framework inside the war.  In addition
the console heavily depends on pax-wicket, which afaik, does need OSGi.  As
you said, injection is done through OSGi services.  My understanding (feel
free to correct me if I'm wrong) is that the camel plugins is injected with
a list of CamelContext coming from OSGi.  Which kinda means to me, that you
need to deploy your camel contexts in OSGi, next to the console itself.


> Charles was talking about that and he found even a name for it once it
> will get TLP (Orion). But it was so long ago you propably don't remember.


Maybe I missed something, but when the Orion proposal was raised, Karaf web
console did not really exist yet.

The proposal was to create a TLP for an OSGi web console with a real web
framework.   None of these ideas did sound good to me at that time (having
a TLP for an OSGi web console and rewriting the existing webconsole with a
web framework).  We disagree, but these 2 years did not really changed my
mind.
Now, a few people went ahead and rewrote an OSGi based web console, which
is nice, but it's still is an OSGi web console and I still don't like the
technical design decisions that were taken.

And more importantly, this console does not really help half of our camel
users which do not use OSGi.


>
> Cheers, :)
>

Np.  We've been trying to get the webconsole problems fixed since the
beginning with ServiceMix 3, so that's almost 6 years ago now.  it became
even more complicated with ServiceMix 4 switching to OSGi.  I think we have
a clean solution now that can work for all projects with hawtio.
Will the project last and pick up ? No one knows yet.  Not all projects are
bound to suceed.  The one that do usually solves real problems in a clean
way.  I think hawtio is a good bet now ... until someone comes up with a
better project.  That's how it works.


> Lukasz
>
>
> Wiadomość napisana przez Guillaume Nodet <gno...@gmail.com> w dniu 25 sty
> 2013, o godz. 14:08:
>
> > Lukasz, I'm sorry you're angry, but you're missing the point that the
> Karaf
> > web console is bound to OSGi even if it can be reused with Camel or
> > ActiveMQ.
> > So the Camel and ActiveMQ community will never drop their own console,
> > because the OSGi users is only a fraction of the user base.  Hawtio
> enable
> > all projects to cooperate on a single web console, at last.
> > So it serves a more general purpose imnsho.
>
>


-- 
------------------------
Guillaume Nodet
------------------------
Red Hat, Open Source Integration

Email: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

Reply via email to