All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Pannecoeck <jpa@mgb-tech.com>
To: openembedded-devel@lists.openembedded.org
Subject: GNU Classpath and the XMPP Smack API
Date: Thu, 29 Jan 2009 14:43:02 +0100	[thread overview]
Message-ID: <4981B266.6010501@mgb-tech.com> (raw)

Hi all,

No clue where the fire this question, but since I'm using OE with GNU 
Classpath and JamVM 1.5 I thought I could ask my question here... Since 
finding a solution for my problem is quite hard. And maybe someone who 
is reading this mailinglist has had this problem before.

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.

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

And now I'm having a "No response from the server" exception during the 
NonSASLAuthentication.authenticate method.

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!

Thanks in advance,
Jan Pannecoeck



             reply	other threads:[~2009-01-29 13:48 UTC|newest]

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

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=4981B266.6010501@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.