Sorry to bother again. I just googled the error and I found out that
the problem is with extending prototype.js by json.js. I had also same
sort of problem rico.js when used together with prototype.js

I just got the forum link that explains more detail 
http://www.ruby-forum.com/topic/96723

On Feb 23, 1:59 pm, "Ranjan" <[EMAIL PROTECTED]> wrote:
> Hi,
>    I could able to fix this issue. I learned from mozilla site that
> "the setRequestHeader must be called only after an open() call." I am
> using prototype.js to invoke url, I just commented
> setRequestHeader()method there and it started working. Though I need
> to find out where exactly I need to place setRequestHeader method.
>
> If anybody finds a better solution, please update me and it will save
> me from debugging more and spending time on the same :)
>
> regards,
> Ranjan
>
> On Feb 23, 1:33 pm, "Ranjan" <[EMAIL PROTECTED]> wrote:
>
> > Hi Tobie,
> >           Thanks for your reply. The page making this request also in
> > 8080 port but in a different URL i.e.
>
> >http://localhost:8080/AT/htmls/jsonemployee.html
>
> > Based on "Same Origin Policy", I also change page location 
> > tohttp://localhost:8080/AT/jsonemployee.htmlsothat servlet and html
> > page are in same URL.
> > But still I get the same error.
>
> > regards,
> > Ranjan
>
> > On Feb 23, 12:58 pm, "tobie" <[EMAIL PROTECTED]> wrote:
>
> > > Hi Ranjan,
>
> > > You're most probably breaking the Same Origin 
> > > Policy:http://en.wikipedia.org/wiki/Same_origin_policy
>
> > > i.e. for this to work, the page triggering the request must be on the
> > > same port.
>
> > > Best,
>
> > > Tobie


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to