headers
Chris Mullins | 2 May 02:06

MU-Conference bug (0.6)

When I try to join a password protected conference, I send:

<presence xml:lang="en" to="testing1 <at> conference.someserver.com/chrism">
  <x xmlns="jabber:x:avatar">
    <hash>4c2dfaf57559ffe57e8dd382f0799f1ad5e7ae80</hash>
  </x>
  <x xmlns="http://jabber.org/protocol/muc">
    <password>chris</password>
  </x>
</presence>

The presence of two "x" nodes in there, causes the server to reply back
with an error. 

If I eliminate the Avatar node, things are fine. 

This likely means that MU-Conference isn't checking for namespaces on
the "x" node, which seems like a pretty serious bug.

--
Chris Mullins
Permalink | Reply | 7 comments |
headers
aliban@gmx.net | 2 May 08:21
Picon

Re: java library for jabber client development

you may also contact me at JID: edrin <at> jabber.org. I am currently using 
JSO a lot, as there is no better lib I could find.

Eugeny N Dzhurinsky schrieb:
> Hello!
>
> Could somebody please suggest some jabber library for java, which is proven to
> work with gatweays? I tried SMACK - but seems like this library is unable to
> parse some IQ packets (in fact it was unable to recognize IQ packet sent after
> transport registration is completed), Feridian looks much better - but I'm
> fighting with  strange JiBX-related issues, for JSO (Jabber Stream Objects)
> there's lack of documentation, jabber wookie is something I can't even
> understand how it is supposed to work.
>
> Thanks in advance!
>
>
Permalink | Reply | 0 comments |
headers
Peter Saint-Andre | 2 May 17:10

Re: MU-Conference bug (0.6)

Chris Mullins wrote:
> When I try to join a password protected conference, I send:
> 
> <presence xml:lang="en" to="testing1 <at> conference.someserver.com/chrism">
>   <x xmlns="jabber:x:avatar">
>     <hash>4c2dfaf57559ffe57e8dd382f0799f1ad5e7ae80</hash>
>   </x>
>   <x xmlns="http://jabber.org/protocol/muc">
>     <password>chris</password>
>   </x>
> </presence>
> 
> The presence of two "x" nodes in there, causes the server to reply back
> with an error. 

What error?

> If I eliminate the Avatar node, things are fine. 

What happens if you switch the order of elements?

> This likely means that MU-Conference isn't checking for namespaces on
> the "x" node, which seems like a pretty serious bug.

Or that it doesn't like unknown namespaces. Or something.

Peter

--

-- 
Peter Saint-Andre
(Continue reading)

Permalink | Reply | 0 comments |
headers
Grégoire Menuel | 2 May 17:18
Picon
Picon

Re: MU-Conference bug (0.6)

Le mercredi 2 mai 2007, Chris Mullins a écrit :
> When I try to join a password protected conference, I send:
>
> <presence xml:lang="en" to="testing1 <at> conference.someserver.com/chrism">
>   <x xmlns="jabber:x:avatar">
>     <hash>4c2dfaf57559ffe57e8dd382f0799f1ad5e7ae80</hash>
>   </x>
>   <x xmlns="http://jabber.org/protocol/muc">
>     <password>chris</password>
>   </x>
> </presence>
>
> The presence of two "x" nodes in there, causes the server to reply back
> with an error.
>
> If I eliminate the Avatar node, things are fine.
>
> This likely means that MU-Conference isn't checking for namespaces on
> the "x" node, which seems like a pretty serious bug.

This is a known and already corrected bug. In fact mu-conference was checking 
the xmlns of the x node, but only read the first x node.

See http://mail.jabber.org/pipermail/mu-conference/2006-September/000665.html 
for a patch.

--

-- 
Grégoire Menuel
xmpp:omega <at> im.apinc.org
GPG: 1024D/D3BF3B20
(Continue reading)

Permalink | Reply | 5 comments |
headers
Chris Mullins | 2 May 18:42

RE: MU-Conference bug (0.6)

Great to hear that it's already been fixed. 

What's the schedule for releasing 0.7 of MU-Conference? 

--
Chris Mullins

-----Original Message-----
From: jdev-bounces <at> jabber.org [mailto:jdev-bounces <at> jabber.org] On Behalf Of Grégoire Menuel
Sent: Wednesday, May 02, 2007 8:19 AM
To: Jabber software development list
Subject: Re: [jdev] MU-Conference bug (0.6)

Le mercredi 2 mai 2007, Chris Mullins a écrit :
> When I try to join a password protected conference, I send:
>
> <presence xml:lang="en" to="testing1 <at> conference.someserver.com/chrism">
>   <x xmlns="jabber:x:avatar">
>     <hash>4c2dfaf57559ffe57e8dd382f0799f1ad5e7ae80</hash>
>   </x>
>   <x xmlns="http://jabber.org/protocol/muc">
>     <password>chris</password>
>   </x>
> </presence>
>
> The presence of two "x" nodes in there, causes the server to reply back
> with an error.
>
> If I eliminate the Avatar node, things are fine.
>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Grégoire Menuel | 2 May 22:14
Picon
Picon

Re: MU-Conference bug (0.6)

Le mercredi 2 mai 2007, Chris Mullins a écrit :
> Great to hear that it's already been fixed.
>
> What's the schedule for releasing 0.7 of MU-Conference?

I didn't plan it yet, but I think it will be soon. I just want to be sure that 
the current code is in full compliance with the XEP 0045 before I release it. 
By the way, if you encounter a bug in mu-conference you can use the bug 
tracker at https://gna.org/bugs/?group=mu-conference

--

-- 
Grégoire Menuel
xmpp:omega <at> im.apinc.org
GPG: 1024D/D3BF3B20
Permalink | Reply | 3 comments |
headers
Chris Mullins | 2 May 22:26

RE: MU-Conference bug (0.6)

I tried to do that first, but I can't submit a bug unless I create an account and register.

... and I didn't want to create "yet another" account somewhere, that I'll forget about and likely never use
again. If you could enable anonymous bug posting, that would help...

--
Chris Mullins

-----Original Message-----
From: jdev-bounces <at> jabber.org [mailto:jdev-bounces <at> jabber.org] On Behalf Of Grégoire Menuel
Sent: Wednesday, May 02, 2007 1:14 PM
To: Jabber software development list
Subject: Re: [jdev] MU-Conference bug (0.6)

Le mercredi 2 mai 2007, Chris Mullins a écrit :
> Great to hear that it's already been fixed.
>
> What's the schedule for releasing 0.7 of MU-Conference?

I didn't plan it yet, but I think it will be soon. I just want to be sure that 
the current code is in full compliance with the XEP 0045 before I release it. 
By the way, if you encounter a bug in mu-conference you can use the bug 
tracker at https://gna.org/bugs/?group=mu-conference

--

-- 
Grégoire Menuel
xmpp:omega <at> im.apinc.org
GPG: 1024D/D3BF3B20
(Continue reading)

Permalink | Reply | 2 comments |
headers
Grégoire Menuel | 2 May 22:30
Picon
Picon

Re: MU-Conference bug (0.6)

Le mercredi 2 mai 2007, Chris Mullins a écrit :
> I tried to do that first, but I can't submit a bug unless I create an
> account and register.
>
> ... and I didn't want to create "yet another" account somewhere, that I'll
> forget about and likely never use again. If you could enable anonymous bug
> posting, that would help...

Done.

--

-- 
Grégoire Menuel
xmpp:omega <at> im.apinc.org
GPG: 1024D/D3BF3B20
Permalink | Reply | 1 comment |
headers
Brendan Taylor | 3 May 01:32
Picon
Gravatar

Testing clients (general architecture)

Hi list.

I'm one of the XSF's GSoC 2007 students. I'm going to be implementing
Encrypted Sessions (XEP-0116) and a test suite for it this summer.

I've found a fair amount of information out there about test suites for
servers. Unfortunately, there doesn't seem to be much about testing clients.

So, client developers: what general architecture for a test suite would
be most useful to you? It needs to work for any client interested in
implementing the XEP, and I would like to make it as simple to use as
possible.

My current plan is to make a server component that will respond to
several JIDs, each representing a different test case. Tests that
require the suite to initiate a process will be initiated with a
message sent to the suite. If you think it's worthwhile, logs of the raw
XMPP traffic will be made available (via HTTP?).

Your thoughts?
--

-- 
<http://necronomicorp.com/bct>
Permalink | Reply | 4 comments |
headers
Peter Saint-Andre | 3 May 17:55

Re: Testing clients (general architecture)

Brendan Taylor wrote:
> Hi list.
> 
> I'm one of the XSF's GSoC 2007 students. I'm going to be implementing
> Encrypted Sessions (XEP-0116) and a test suite for it this summer.
> 
> I've found a fair amount of information out there about test suites for
> servers. Unfortunately, there doesn't seem to be much about testing clients.
> 
> So, client developers: what general architecture for a test suite would
> be most useful to you? It needs to work for any client interested in
> implementing the XEP, and I would like to make it as simple to use as
> possible.
> 
> My current plan is to make a server component that will respond to
> several JIDs, each representing a different test case. Tests that
> require the suite to initiate a process will be initiated with a
> message sent to the suite. If you think it's worthwhile, logs of the raw
> XMPP traffic will be made available (via HTTP?).
> 
> Your thoughts?

Is this part of your GSoC project or just a nice thing you want to do? :)

First, I am not a client developer, so take what I say with a generous 
helping of salt.

It seems to me that part of the challenge with client testing is that 
clients interact with a broader range of entities than servers do. In 
many ways it's easier to test and write servers than it is to test and
(Continue reading)

Permalink | Reply | 3 comments |

Gmane