IIRC, pyAMF tries to turn all python objects into amf related ones upon
output. What you may be seeing here is that querysets aren't able to make it
through this conversion. Check your apache error logs for the stacktrace, if
you have one, or like Randy said, set Debug = True.
On Thu, Jun 25, 2009 at 6:23 AM, Randy Barlow <rbar...@americanri.com>wrote:
>
> Noxxan wrote:
> > I'm trying to place in my app an amf gateway,
> > so I make one gateway with code:
> >
> > #-*- coding: utf-8 -*-
> > from pyamf.remoting.gateway.django import DjangoGateway
> >
> > from my.views import some_view
> >
> > services = {
> > 'some_service.hello': some_view.get_smt,
> > }
> >
> > echoGateway = DjangoGateway(services)
> >
> > there's also file some_view.py, with content:
> >
> > #-*- coding: utf-8 -*-
> > from module.models import MyOwnModel
> >
> > def get_smt(request):
> > return MyOwnModel.objects.all()
> >
> > And here's the problem, I receive an error message:
> >
> > pyamf.remoting.RemotingError: HTTP Gateway reported status 500
> > Internal Server Error
> >
> > When I change return of get_smt view to, by example return 123,
> > error didn't occur.
> >
> > I have PyAmf 0.4.2, Python 2.5.2 and latest stable Django.
> >
> > What may causes the problem?
>
> Many things can cause the problem you are seeing. I would suggest to
> turn Debug=True, and then navigate to the URL for that view. You should
> be able to see a traceback, which will give you a better clue about what
> the problem is.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
