Hi
I am using Jetty 6.1.11 on the server side.
I managed to have dojo 1.1 and cometd to work inside AIR only in one
simple case. In the simple version I could connect to a local push
server subscribe and publish.
Then I tried to do the same on my real app. This time, the user needs
to be logged in on a tomcat server before he can log to the push
server. The login to tomcat goes well, I get back an ID, and then try
to connect to the push server. As I said, it appears like the program
is "stuck" in the dojox.init funcion.
I used JS alerts to debug dejo in AIR. In the init function, I have
something like that :
//CODE
if(!this._isXD){
if(props.ext){
if(props.ext["json-comment-filtered"]!==true && props.ext["json-
comment-filtered"]!==false){
props.ext["json-comment-filtered"] = true;
}
}else{
props.ext = { "json-comment-filtered": true };
}
alert("stop 1");
props.supportedConnectionTypes = dojo.map(this.connectionTypes.pairs,
"return item[0]");
alert("stop 2");
}
The firt alert is launched but I never reach the second one. That's
why I say it looks "stuck".
In both scenarios, I have an error message :
Value undefined : result of expression mll[x]) is not object.
- line 409
- message " Value undefined (result of expression mll[x]) is not
object."
- name "TypeError"
- sourceId 3
- sourceURL "app:/lib/dojo/dojo.js.uncompressed.js"
- stackTrace [Array 4]
I understand that the init function is implemented asynchronously so
code shouldn't get stuck there, I am just saying what I observe.
Does this make sens to someone ?
Thanks for your help :-)
On 14 août, 01:15, Greg Wilkins <
gr...@mortbay.com> wrote:
> BGM,
>
> what server side are you using ?
>
> Do you have dojo 1.1 working from javascript with your server (try the
> chat demo, it is only a few lines).
>
> no calls should ever "stuck" as cometd is implemented asynchronously.
>
> regards
>
> bold greymonkey wrote:
> > Hi
>
> > I am trying to create an AdobeAIRwidget using dojox.cometd for push.
> > I get stuck with the dojox.cometd.init function which I try to call
> > during onLoad. I don't know what happens, the application just gets
> > stuck in the init function. No error message (or maybe there are some
> > but I can't see them since dojo doesn't print inAIRintrospector).
>
> > I useAIR1.1 and dojo 1.1 beta 1 as explained on the Dojo website.
> > This should be the minimal version to supportair. However, I have