Hi,
I realized my problem by using LogHandler. By placing the MUCRoom
join directly after the connect(false) call, I didn't give any time
for the client to handle login before trying to join the room. By
registering a ConnectionListener and listening for StreamEventFinished
I was able to recv on the client until the login was complete and then
call join on the MUCRoom. Works!
I was using 0.9.8
Thanks,
Dan
On Jan 15, 2008 9:17 PM, Jakob Schröter <js@xxxxxxxxxx> wrote:
>
> On Monday January 14 2008, Daniel Starin wrote:
> > Hi,
> >
> > I am trying to connect to an existing MUC Room using gloox. What I
> > have done so far is create the client, call connect(false) on it and
> > then use that client object along with a ChatRoomHandler in a call to
> > the MUCRoom constructor. Then, I call mucRoom->join(). I follow the
> > join call with a recv() loop on the Client object. The problem is, I
> > don't see the presence of the Client in the MUCRoom which it joined.
> > When I look at the packets sent by the program, I see the presence
> > packet sent to <room name>@conference.<server> but, again, the client
> > doesn't actually show up there.
> >
> > I am using the ejabberd MUC component implementation for the server
> > and Gaim to create the default room and look for the joining client.
>
> Hi,
>
> Could you please post some code and/or the relevant snippets from the xml
> logs, which version of gloox, etc.
>
> cheers,
> Jakob
>
> --
> gloox-dev mailing list
> to unsubscribe:
> send a message with subject 'unsubscribe gloox-dev' to minimalist@xxxxxxxxxx
>