[jdev] Why is my jabber serverkickingout aremote useron anerror?

[Tom Kalafut]

I'm sorry I keep beating this dead horse, but does 2.0 (or the patch) no longer kick out the user in the line 294 check (if message error stanza sent to chat room JID { kick out user })?  It looks like the new version (or patch) only alleviates the line 473 check (per https://support.process-one.net/browse/EJAB-496).

Can someone please confirm this?

Thanks,
Tom

Tom Kalafut
I3/CG Crew Member
Trident Systems Inc.
tommyk at tridsys.com
(919)388-1264

============
The opinions expressed in this e-mail may not necessarily reflect the opinions of Trident Systems Inc.


-----Original Message-----
From: jdev-bounces at jabber.org [mailto:jdev-bounces at jabber.org] On Behalf Of Tom Kalafut
Sent: Thursday, February 21, 2008 1:10 PM
To: Jabber/XMPP software development list
Subject: Re: [jdev] Why is my jabber serverkickingout aremote useron anerror?

Because it's a 2.0, it's probably got a lot of different stuff that would it a PITA to re-integrate into our system.

But I may be able to try the patch.

Thanks,
Tom

Tom Kalafut
I3/CG Crew Member
Trident Systems Inc.
tommyk at tridsys.com
(919)388-1264

============
The opinions expressed in this e-mail may not necessarily reflect the opinions of Trident Systems Inc.


-----Original Message-----
From: jdev-bounces at jabber.org [mailto:jdev-bounces at jabber.org] On Behalf Of Peter Saint-Andre
Sent: Thursday, February 21, 2008 12:53 PM
To: Jabber/XMPP software development list
Subject: Re: [jdev] Why is my jabber server kickingout aremote useron anerror?

Tom Kalafut wrote:
> Thanks.
> 
> To be clear, I don't want anybody to get kicked.  

I don't either. :)

> I'm trying to work
> around the feature

"bug"

> so that I can report errors to local users without
> kicking the remote user who "reported" it.  It doesn't look like I
> can do this, so I was considering a message of type 'groupchat' with
> ERROR info in it as an ugly hack.

I agree that "ugly" is the right word. :)

> I'm not sure if upgrading to 2.0.0 is an option, since we don't
> control the releases of our main application (i.e. not the middleware
> that I'm working on here).  But I'll at least ask if we can upgrade.

Ah, ok. Are you even able to patch the existing system?

/psa