Web Services

← All categories

• Q199: How do I create a REST GET endpoint in EK9?
• Q200: How do EK9 operators map to HTTP methods for CRUD?
• Q201: How do I create HTTP responses in EK9 services?
• Q202: How do I bind path parameters and request body in EK9 services?
• Q203: How do I wire services and components together in an EK9 application?
• Q657: How does service URI mapping work with :/path syntax?
• Q658: How do I extract path parameters in EK9 services?
• Q659: Why must every service method return HTTPResponse?
• Q660: How do CRUD operators map to URIs with path parameters?
• Q684: What are the rules for valid service URI paths and method mapping?
• Q685: What must service method bodies contain and what is prohibited?
• Q845: Why must all EK9 service methods return HTTPResponse?
• Q846: Why can't I use Float as a service method parameter in EK9?
• Q868: Why can't I use HTTPRequest as a path parameter type in EK9 services?
• Q869: Why must all EK9 service methods declare a return value?
• Q890: Why must service operations return HTTPResponse in EK9?
• Q944: What are the basic rules for EK9 service definitions?
• Q945: How do HTTP verbs, URI path variables, and parameter qualifiers work in EK9 services?
• Q946: How must path variable counts match parameters in EK9 services?
• Q1292: How does service security posture work with 'open' and 'constrain by'?
• Q1293: What happens when a constrain by reference cannot be resolved?
• Q1294: What types are valid in a constrain by clause?
• Q1295: Why does constrain by X and Y fail when both extend SecurityGate?
• Q1305: Why does EK9 reject two service methods that share the same HTTP path?
• Q1316: Why can't a helper method in an EK9 service be marked 'protected'?
• Q1322: Why does EK9 reject some operators inside a service definition?
• Q1323: Why does EK9 reject an HTTP access marker (:=: PATH) on a service operation's returning parameter?
• Q1324: Why does a QUERY/HEADER/PATH service parameter need a name qualifier in EK9?
• Q1325: Why does EK9 reject a qualifier name on a REQUEST or CONTENT service parameter?
• Q1326: Why does EK9 reject a service method that declares a return but has no implementation body?
• Q1327: Why must a service parameter bound with :=: REQUEST be typed as HTTPRequest in EK9?
• Q1328: Why can't I mix HTTPRequest with other parameters in an EK9 service operation?
• Q1329: Why must a CONTEXT-bound service parameter be typed HTTPContext in EK9?
• Q1330: Why can't I mix HTTPContext with QUERY or PATH parameters in an EK9 service method?
• Q1331: Why can't I bind HTTPContext to a QUERY parameter in an EK9 service?