›
Welcome to the SRP Forum! Please refer to the SRP Forum FAQ post if you have any questions regarding how the forum works.

error http frameworks setup

BarryStevensBarryStevens
in SRP HTTP Framework
get this eoor when I add a new resource and resource id.
clicked apply then clicked 'create api' and got this error


Comments

  • BarryStevensBarryStevens
    I see that it means compile error.
    I now see that extra code has been added to apijobclock , I assumed it was only creating api for newly added resources.

    this is what was added to the end of apijobclock existing code (got double defined compile errors)

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    API apijobclock.{resourceid}.HEAD
    API apijobclock.{resourceid}.GET
     
        HTTP_Resource_Services('LoremIpsum')
     
    end api
     
     
    API apijobclock.{resourceid}.POST
     
        HTTP_Resource_Services('LoremIpsum')
     
    end api
     
     
    API apijobclock.{resourceid}.PUT
     
        HTTP_Resource_Services('LoremIpsum')
     
    end api
     
     
    API apijobclock.job.HEAD
    API apijobclock.job.GET
     
        HTTP_Resource_Services('LoremIpsum')
     
    end api
     
     
    API apijobclock.job.POST
     
        HTTP_Resource_Services('LoremIpsum')
     
    end api
     
     
    API apijobclock.job.PUT
     
        HTTP_Resource_Services('LoremIpsum')
     
    end api
  • BarryStevensBarryStevens
    I remember I had changed the apijobclock earlier and just did 'apply' as the api was already created.
  • BarryStevensBarryStevens
    removed this, but it keeps adding it.
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    API apijobclock.{resourceid}.HEAD
    API apijobclock.{resourceid}.GET
        HTTP_Resource_Services('LoremIpsum')
    end api
     
    API apijobclock.{resourceid}.POST
        HTTP_Resource_Services('LoremIpsum')
    end api
    API apijobclock.{resourceid}.PUT
        HTTP_Resource_Services('LoremIpsum')
    end api



  • DonBakkeDonBakke
    @BarryStevens - This was a bug in a low-level service that only occurred when the name of your resource started with the same letters as your API root. In this case, your resources started out as "API" or "api" and your API root is also "api". I have a fix for this, but I do recommend not naming a resource with a prefix of "api". It's a bit redundant and doesn't define your resource in a meaningful way.
  • BarryStevensBarryStevens
    I did it so I could see them all grouped to-gether .
    I will change them to another prefix.
  • DonBakkeDonBakke
    You can drag the top-level resources up and down to group together.
  • BarryStevensBarryStevens
    Sorry, I meant in the ssp list
  • DonBakkeDonBakke
    Gotcha. Well, I do understand the desire to keep your stored procedures sorted. However, this approach sort of moves away from the appeal of Semantic URLs (and RESTful design) and turns it into more of an RPC (remote procedure call) design, which is what INET/O4W APIs are.
Sign In or Register to comment.