I believe these patches should be applied because as it appears to me, since it seems the error in question is invalid-namespace rather than bad-namespace-prefix (there isn't, I believe, even a prefix to speak of in this case).
Compare http://xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-09.html#streams-erro r-conditions-invalid-namespace to http://xmpp.org/internet-drafts/draft-saintandre-rfc3920bis-09.html#streams-erro r-conditions-bad-namespace-prefix
Since, for backwards compatibility, XMPP is strict about insisting on the "stream:" prefix being used (and not any other, even though XML Namespaces could care less), so you probably should also add a bad-namespace-prefix check as well, but this, I believe, is not it...
(I'm a relative noob to Java, etc., so my apologies if I'm missing something here...)
Removing the 'fix version' for all unresolved issues that were scheduled for version 7.8.2. We're releasing this version today - the remaining issues should be rescheduled later.
Assigning to Guus for comment
While working on and debugging the code, "bad-namespace-prefix" was returned, when the namespace was not "jabber:client".
According to the spec this is indeed wrong and should be "invalid-namespace".
or the content namespace declared as the default namespace is not supported (e.g., something other than "jabber:client" or "jabber:server")