public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: chris.gray@kiffer.be
To: "\"Lambrecht Jürgen\"" <J.Lambrecht@TELEVIC.com>
Cc: "ecos" <ecos-discuss@ecos.sourceware.org>,
	"Deroo Stijn" <s.deroo@televic.com>,
	"chris.gray@kiffer.be" <chris.gray@kiffer.be>,
	"Rutger Hofman" <rutger@cs.vu.nl>
Subject: [ECOS] Re: ecos and java and OSGI
Date: Thu, 14 Mar 2013 09:24:00 -0000	[thread overview]
Message-ID: <7bf21bd17d9359516fe28a24d851f3b3.squirrel@k-embedded-java.com> (raw)

Hello Jürgen,

> We want to use an OSGI framework in eCos. I see 2 solutions:
> - or run a JVM on ecos. What about MiKa (previously Wonka) or Kaffe? -
or a C version of OSGI
> Does anyone has done OSGI on eCos?

Mika would have to be re-ported to eCos, the port made by Andrea Scian in
2004 will have been subject to severe bit-rot I'm afraid.  But we can do
that for you if you have a bit of consulting budget.

Once that is working your OSGi problem is solved - plenty of people are
using Knopflerfish or Felix on top of Mika, so you shouldn't encounter
(m)any bugs.

Note that I am based in Antwerp, so Izegem counts as "international". ;-)

> - I only find for OSGI:
> http://sourceware.org/ml/ecos-discuss/2004-07/msg00223.html

Yup, that's Andrea.

> - And for MiKa:
> http://sourceware.org/ml/ecos-discuss/2010-09/msg00011.html

Didn't see this at the time.  It does bring up one thing you will have to
think about, which is how your native and Java components will work
together in the single eCos "application".  I favour a Java-centric
approach in which Mika *is* the application and all the native code
resides in bundles, but there may be reasons why you can't do this. 
Similarly for threads - if threads launched by the VM have to interact
with threads launched by native code then things can get a bit messy.

> - Kaffe on ecos 1.3.1, and the download link seems not to be valid on
http://ecos.sourceware.org/contrib.html

Don't think much is happening in the Kaffe world since Dalibor took a job
with Sun.

Best regards

Chris



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

                 reply	other threads:[~2013-03-14  9:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7bf21bd17d9359516fe28a24d851f3b3.squirrel@k-embedded-java.com \
    --to=chris.gray@kiffer.be \
    --cc=J.Lambrecht@TELEVIC.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=rutger@cs.vu.nl \
    --cc=s.deroo@televic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).