We're updating the issue view to help you get more done. 

Illegal JID when configuring a created MUC room

Description

Submitting a new configuration to unlock a newly created MUC room results in

Environment

None

Acceptance Test - Entry

None

Activity

Show:
Daryl Herzmann
February 22, 2013, 9:43 PM
Edited

results in this traceback on trunk

Daryl Herzmann
February 23, 2013, 12:37 AM

With latest tinder we get

Guus der Kinderen
February 23, 2013, 11:09 AM

A snippet of the room configuration that is received by Openfire is this:

I'm not sure where that second, empty value element originates, but that's the one causing the problem.

Earlier today, I've committed a change that:

  • includes a new version of Tinder, that, apart from the more verbose debug messages () also has a new utility method that simplifies working with bare jid objects ().

  • adds more defensive code to Openfire, where collections of JIDs are being processed. Empty values are now ignored.

The above changes prevent the problem from occurring, as the empty value element is ignored.

Assignee

Guus der Kinderen

Reporter

Daryl Herzmann

Labels

None

Expected Effort

None

Components

Fix versions

Affects versions

Priority

Major
Configure