Has anyone tried using XIFF 2.0 with the new Wildfire beta? We’'ve had no luck. The first problem was that WF now looks explicitly for “<stream:stream” on connect. We worked around that by having XIFF send <stream:strem, and then setting isFlashClient based on the presence of xmlns:stream=“http://www.jabber.com/streams/flash”.
Still didn’'t work - it appears that the null byte handling is just not working. The exception we get is:
org.jivesoftware.wildfire.nio.ConnectionHandler.messageReceived(ConnectionHandle r.java:126) Closing connection due to error while processing message
org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not \u0 (position: START_DOCUMENT seen \u0… @1:1)
at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1519)
at org.jivesoftware.wildfire.net.MXParser.nextImpl(MXParser.java:331)
at org.xmlpull.mxp1.MXParser.nextToken(MXParser.java:1100)
We’'re not really looking to upgrade to XIFF 3 yet - we use MTASC for compilation, among other things. The reason for upgrading the server is to work around an performance problem with groupchat - described in this thread: http://www.igniterealtime.org/forum/thread.jspa?threadID=24293&tstart=0
Thanks,
Jim Greer