AdrianSzymczak / jabber-net

Automatically exported from code.google.com/p/jabber-net
0 stars 0 forks source link

Conference room configuration not applied #81

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Create a new conference room using ConferenceManager->GetRoom( jid )
2. Join the room to trigger the OnRoomConfig event, ie. room->Join()
3. Handle the OnRoomConfig event
4. Display the xdataform to collect user settings
5. Return the xdataform result, ie. return( form->GetResponse() )

What is the expected output? What do you see instead?
Expected would be a room at conference.jabber.org configured as the user 
has specified.
Actual is a default configured room.

What version of the product are you using? On what operating system?
2.1.0.710

Please provide any additional information below.

The initial room->Join() call does not actually result in a joining to the 
room, it does trigger the OnRoomConfig event, but in code I must execute a 
second room->Join() to get the RoomJoined event to fire and be able to 
invite other users.

Original issue reported on code.google.com by rnend...@gmail.com on 17 Sep 2009 at 9:06

GoogleCodeExporter commented 9 years ago
Note - the specific test is setting the whois to "anyone" using the xdataform, 
then 
inviting others to join the conference once the owner of the conference has 
configured the room and joined afterward.  The users will receive the 
invitation and 
be allowed to join, but will not receive RealJID's indicating the configuration 
settings are not being applied.

Original comment by rnend...@gmail.com on 18 Sep 2009 at 3:58

GoogleCodeExporter commented 9 years ago
Final note - the issue is resolved.

After connecting with invalid credentials, a JabberClient->Close() MUST be 
called, 
prior to attempting another JabberClient->Connect() operation.  If the first 
attempt 
fails to authenticate, and Close() is not called, then on a successful 
Connect() the 
client will connect, but the original session must be timing out on the server, 
causing interruption of the existing connection.  Simply calling Close() in the 
AuthError event resolves the problem.

Original comment by rnend...@gmail.com on 18 Sep 2009 at 5:34

GoogleCodeExporter commented 9 years ago
Regarding the conference room issue - also resolved ( kind-of ) now.

Behavior only appears when connecting to conference.jabber.org, when connecting 
to a 
local OpenFire server, the room configuration is applied server-side.

Original comment by rnend...@gmail.com on 18 Sep 2009 at 11:52