Open GoogleCodeExporter opened 8 years ago
I find the reason, but not the solution.
In asmack there is a patch that replaces all instances of MXParser by an
instance of a Parser returned by XMLPullFactory. This instance is actually an
instance of KXmlParser. MXParser and KXmlParser both implement XmlPullParser
interface but in reality they do not have the same behavior. When getText() is
used and the next element is a TAG, MKParser returns a string containing the
TAG, but KXmlParser returns null (after a check to the interface doc, the
correct behavior is to return null).
At this time I have no solution, I am trying to use KXmlParser to obtain the
wanted behavior. After all, this is the MXParser used in smack that does not
respect the interface spec.
I do not know how use XmlPullParser, so if someone wants to help me, thanks in
advance :) The problem is in the file
org.jivesoftware.smackx.pubsub.provider.ItemProvider.java
Paulo
Original comment by pg.ens...@gmail.com
on 24 Jun 2010 at 3:44
Could you post the corresponding XML? Thanks in advance....
Original comment by rtreffer@gmail.com
on 26 Aug 2010 at 7:16
The corresponding XML is posted in the first message, with the result of the
parsing. It fails with all XML I tried. If you want another peace of XML, do
not hesitate to tell me.
I found a solution to make it work for me, but I am not sure this is very
clean. I post the code in attached files.
Paulo
Original comment by pg.ens...@gmail.com
on 26 Aug 2010 at 7:52
Attachments:
Thanks for the fix!!!
Original comment by hur...@gmail.com
on 14 Mar 2012 at 8:49
Hello guys,
thanks for the solution, this is great!
Attached you find "my version" of the fix.
In addition to the previous fix, in includes the "node" attribute and the
"xmlns" of the paylods root element.
regards
sni
Original comment by stefan.n...@gmail.com
on 4 Jun 2012 at 7:21
Attachments:
[deleted comment]
Fixed in aSmack 0.8.1: See https://github.com/Flowdalic/asmack/issues/3
Filled as upstream bug
[SMACK-415|http://issues.igniterealtime.org/browse/SMACK-415]
Original comment by fschm...@gmail.com
on 19 Feb 2013 at 10:56
Original issue reported on code.google.com by
pg.ens...@gmail.com
on 23 Jun 2010 at 3:04