Michael Jakl (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/VYSPER-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712014#action_12712014 > ] > > Michael Jakl commented on VYSPER-52: > ------------------------------------ > > You changed the order of the imports, is this on purpose, or some automatic > IDEA thing?
Sorry, this was not intended. I switched off 'optimize imports on the fly', so we don't run into unnecessary conflicts in the future. Thanks for the hint. Bernd > > Mine: >> import java.util.Map; >> import java.util.TreeMap; >> >> import org.apache.vysper.xmpp.addressing.Entity; > > > Repo: >> import org.apache.vysper.xmpp.addressing.Entity; >> >> import java.util.Map; >> import java.util.TreeMap; > >> Subscribe to a Node (XEP-0060 6.1) >> ---------------------------------- >> >> Key: VYSPER-52 >> URL: https://issues.apache.org/jira/browse/VYSPER-52 >> Project: VYSPER >> Issue Type: Sub-task >> Reporter: Michael Jakl >> Assignee: Michael Jakl >> Attachments: VYSPER-52.1.patch >> >> >> Example 30. Entity subscribes to a node >> <iq type='set' >> from='[email protected]/barracks' >> to='pubsub.shakespeare.lit' >> id='sub1'> >> <pubsub xmlns='http://jabber.org/protocol/pubsub'> >> <subscribe >> node='princely_musings' >> jid='[email protected]'/> >> </pubsub> >> </iq> >> >> 6.1.2 Success Case >> If the subscription request is successfully processed, the server MUST >> inform the requesting entity that it is now subscribed (which MAY include a >> service-generated SubID). >> Example 31. Service replies with success >> <iq type='result' >> from='pubsub.shakespeare.lit' >> to='[email protected]/barracks' >> id='sub1'> >> <pubsub xmlns='http://jabber.org/protocol/pubsub'> >> <subscription >> node='princely_musings' >> jid='[email protected]' >> subid='ba49252aaa4f5d320c24d3766f0bdcade78c78d3' >> subscription='subscribed'/> >> </pubsub> >> </iq> >
