Component service discovery problem
From: Adrian Brański <adrian@xxxxxx>
Date: Fri, 7 Mar 2008 15:14:10 +0100 (CET)
Hi,

Today I have problem with component_example. Namely, after register
component I receive following errors:

log: level: 0, area: 131072, <iq from='888@xxxxxxxxxx/Psi'
to='ditrans.xxx.xxx.xx' type='get' id='aaeea'>
<query xmlns='http://jabber.org/protocol/disco#info'/></iq>
log: level: 0, area: 262144, <iq xmlns='jabber:client'
to='888@xxxxxxxxxx/Psi' id='aaeea' type='result'><query
xmlns='http://jabber.org/protocol/disco#info'><identity
category='component' type='generic'/><feature
var='http://jabber.org/protocol/disco#info'/><feature
var='http://jabber.org/protocol/disco#items'/><feature
var='jabber:iq:version'/><feature var='urn:xmpp:ping'/></query></iq>
log: level: 0, area: 131072, <iq type='error' from='888@xxxxxxxxxx/Psi'
id='aaeea'><query
xmlns='http://jabber.org/protocol/disco#info'><identity
category='component' type='generic'/><feature
var='http://jabber.org/protocol/disco#info'/><feature
var='http://jabber.org/protocol/disco#items'/><feature
var='jabber:iq:version'/><feature var='urn:xmpp:ping'/></query><error
code='400' type='modify'><bad-request
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>
log: level: 0, area: 262144, <iq xmlns='jabber:client'
to='888@xxxxxxxxxx/Psi' id='aaeea' type='error'><error
type='cancel'><service-unavailable
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>
log: level: 0, area: 131072, <iq type='error' from='888@xxxxxxxxxx/Psi'
id='aaeea'><error type='cancel'><service-unavailable
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error><error code='400'
type='modify'><bad-request
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>

Once again I'm almost sure the reason is missing "from" attribute in iq
result (from transport as it is in XEP-0030 specification). Do anyone
have any idea how to fix this?
I would be grateful for any suggestions.

Thanks.

-- 
Adrian Brański