locked
RTM Release RRS feed

  • Question

  • Hi,

    Congratualtions on the RTM release. Just a few problems after I upgraded:

    - Has the syntax changed for service operations? I can't seem to call my existing service operations from the browser anymore.

    - config.UseVerboseErrors = true; doesn't seem to give me verbose error messages anymore - I'm back to the 400 bad request type error messages.

    .... and is there a plan to be able to filter on EntityCollections? I'd like to be able to do something like:

    http://localhost:1417/DataService.svc/blog /tags/name = "dataservices"

    Thanks,
    Michael
    Tuesday, August 12, 2008 6:58 AM

Answers

  •  

    - Has the syntax changed for service operations? I can't seem to call my existing service operations from the browser anymore.

    >>> Things are pretty much the same as they were in Beta 1 (things changed in the Beta from prior versions - see the Beta 1 announcement on the astoria team blog for details).  When you hit the $metadata endpoint, does a <FunctionImport> with the name of the service operation show up? 


    - config.UseVerboseErrors = true; doesn't seem to give me verbose error messages anymore - I'm back to the 400 bad request type error messages.

    >>> We'll look into this.


    .... and is there a plan to be able to filter on EntityCollections? I'd like to be able to do something like:

    http://localhost:1417/DataService.svc/blog /tags/name = "dataservices"

     

    >>> it is on our radar, but no timeline has been assigned yet

    Tuesday, August 12, 2008 4:03 PM
  • "service operations which take a long/Int64 datatype as a parameter are no longer working"

    If you include an "L" in the query string, they will work.  For instance:

    http://localhost:54310/Services/MyService.svc/GetInfo?id=257L

    You'll need to do this for other requests as well:

    http://localhost:54310/Services/MyService.svc/Person(3L)

    L == long
    f == float
    F == double

    Hope that helps.

    Joe
    Wednesday, August 13, 2008 9:54 PM

All replies

  •  

    - Has the syntax changed for service operations? I can't seem to call my existing service operations from the browser anymore.

    >>> Things are pretty much the same as they were in Beta 1 (things changed in the Beta from prior versions - see the Beta 1 announcement on the astoria team blog for details).  When you hit the $metadata endpoint, does a <FunctionImport> with the name of the service operation show up? 


    - config.UseVerboseErrors = true; doesn't seem to give me verbose error messages anymore - I'm back to the 400 bad request type error messages.

    >>> We'll look into this.


    .... and is there a plan to be able to filter on EntityCollections? I'd like to be able to do something like:

    http://localhost:1417/DataService.svc/blog /tags/name = "dataservices"

     

    >>> it is on our radar, but no timeline has been assigned yet

    Tuesday, August 12, 2008 4:03 PM
  • Hi Mike,

    Thanks for your reply. I've investigated my service operation problem further and have witnessed that service operations which take a long/Int64 datatype as a parameter are no longer working. Even though these service operations are listed as <FunctionImport> when I hit the $metadata endpoint. My other service operations that take integers and strings still work.

    Is anyone else witnessing the same thing?

    Regards,
    Michael
    Wednesday, August 13, 2008 12:13 AM
  • "service operations which take a long/Int64 datatype as a parameter are no longer working"

    If you include an "L" in the query string, they will work.  For instance:

    http://localhost:54310/Services/MyService.svc/GetInfo?id=257L

    You'll need to do this for other requests as well:

    http://localhost:54310/Services/MyService.svc/Person(3L)

    L == long
    f == float
    F == double

    Hope that helps.

    Joe
    Wednesday, August 13, 2008 9:54 PM
  •  Joe McBride wrote:
    "service operations which take a long/Int64 datatype as a parameter are no longer working"

    If you include an "L" in the query string, they will work.  For instance:

    http://localhost:54310/Services/MyService.svc/GetInfo?id=257L

    You'll need to do this for other requests as well:

    http://localhost:54310/Services/MyService.svc/Person(3L)

    L == long
    f == float
    F == double

    Hope that helps.

    Joe

     

     double type parameters seems to be working without the F suffix.

    Monday, August 18, 2008 4:04 AM