All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Pannecoeck <jpa@mgb-tech.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: GNU Classpath and the XMPP Smack API
Date: Thu, 29 Jan 2009 17:03:14 +0100	[thread overview]
Message-ID: <4981D342.9090209@mgb-tech.com> (raw)
In-Reply-To: <4981C586.4080202@gmx.net>

Hi,

Thansk for the reply, I've tried OpenJDK and Cacao before, but that was 
a little bit to adventures for me... :-) Maybe I'll try again later, if 
there really isn't a solution to get Smack working with GNU Classpath. 
So I'll wait a few days to see if someone here knows some solution ... I 
hope someone does! :-)

Jan Pannecoeck

Robert Schuster wrote:
> Hi,
>
> Jan Pannecoeck schrieb:
>   
>> As the subject is already telling you, I'm stuck trying to get the Smack
>> API working on my embedded device. The Smack library is written to
>> communicate using XMPP. I know already that smack is developed to work
>> under the Java Sun library, and that using GNU Classpath could cause
>> problems. But since they have managed to get it working at Android, with
>> the GNU Classpath, I think that it should be possible to run it also on
>> an OpenEmbedded device.
>>     
> Android is using Apache's JavaSE library called Harmony.
>
>
>   
>> I've got the latest version of the smack.jar that was patched for the
>> Android, but that still isn't working. I have had a bunch of different
>> errors like:
>>
>> - OEFException during the SSLSocket doHandshake method.
>> - KeyStoreException: jks during an SALSAuthentication
>>     
> First of all, the "Java Keystore" (jks) format isn't supported by GNU
> Classpath.
>
> Furthermore I know that SSL stuff often caused trouble but do not
> understand this enough to fix it on my own.
>
>   
>> I know this problem is quite big and my explanation is probably not that
>> great neither, but still I hope that someone has done this before and
>> succeeded in his mission. If someone could send me some more information
>> about this, or a working smack.jar (if possible with source code) that
>> would be great!!
>>
>> All help is welcome ofcourse!
>>     
> If you are adventurous you might try the Cacao+OpenJDK solution for your
> device.
> That would give you OpenJDK class library plus Cacao as the VM.
>
> In order to build it you need to add the Jalimo SVN repo as an overlay
> to OE. Disable the strict md5sum checking for now, since the files
> mentioned in the overlay are not in OE's official checksum.ini .
>
> Regards
> Robert
>
>
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>   



      reply	other threads:[~2009-01-29 16:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 13:43 GNU Classpath and the XMPP Smack API Jan Pannecoeck
2009-01-29 15:04 ` Robert Schuster
2009-01-29 16:03   ` Jan Pannecoeck [this message]

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=4981D342.9090209@mgb-tech.com \
    --to=jpa@mgb-tech.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.