Sorry, impossible to say with this data... If you can reproduce the
problem with a 10-20 lines sample and post it here, it would probably
be easier.
-m
Try adding this to the account object:
address: "st...@wars.com",
resource: "lucas"
Normally these two are computed based on jid, but since you're passing
a raw object instead of an account object, they're not. (A good
reason to use the account system in xmpp4moz instead of rolling your
own. ;) )
-m
...which is out of date. :)
> and the new code
> look like this:
>
> var account = XMPP.accounts;
> account.jid = "st...@wars.com/lucas";
> account.password = "coolstars";
> account.address = "st...@wars.com";
> account.resource = "lucas";
> account.connectionHost = 'talk.google.com';
> account.connectionPort = '443';
>
> alert("Is this ok?"); //------> (A)
> XMPP.up(account,
> function() {
> alert("is this ok again?"); //------------> (B)
> processLoginSuccess();
> );
>
> (A) still appeared.... but (B) didn't.
>
> also, can you redirect me to any doc regarding the xmpp4moz's account
> system? Can't find it on this group or sameplace.cc.
There's no doc about that, just configure an account through SamePlace
then pass it's id (in the form node@domain, without /resource) to
XMPP.up().
-m
Well yes, that's how SamePlace does it. :) Look at wizard.js.
> Also, when you do "XMPP.up()" (without any parameter) a small dialog
> pops up where we can select accounts. Is that part of Sameplace or
> XMPP4MOZ? Can we use that to configure accounts?
It's part of xmpp4moz but the "configure" bit is part of SamePlace.
Also keep in mind that there's a good chance that xmpp4moz and
SamePlace will be merged (probably with a flag to not load part or
whole of SamePlace, for those who don't need it) so there's nothing
wrong with starting to use pieces of SamePlace.now, you'll have them
at your disposal anyway later.
-m