S
sjellin.dovetail
Guest
Hi Geir, I stand to correction but from what I recall / struggled with is when using the REST Adapter - anything you don't explicitly map is lost between tomcat and the appserver. I believe in PASOE there is a real webhandler where you can do more generic mapping to a single handler or via a simple file map urls to specific handlers and still be able have access to the raw request. I really want to get to PASOE just for the simpler REST mapping and access to more of the request. One comment on your structure - the HTTP Method tells what the consumer what is being done - don't reencode it in the URL. as an example of the API I have ../[FRWUat|FRWLive]/rest/FreightWare/V1 - this gives me uat or live rest is forced, FreightWare is the app, V1 is the current ever growing V1 of the API. GET ../Waybills{ID} gets a single waybill but also returns a lot of data about the waybill GET ../Waybills (gets one or more depending on criteria passed in the body) - minimal data at header level only. PUT ../Waybills/{ID} - update a single waybill POST ../Waybills - create 1 or more waybill based on JSON struct. DELETE - I generally do based on a single ID. I use a similar pattern for everything unless the particular function doesn't match the pattern. If you like I send you a link to one of the publicly accessible clients API's to have a look if you think it might help.
Continue reading...
Continue reading...