| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| REST API Oddity...[SOLVED] |
« View previous topic :: View next topic » |
| Author |
Message
|
| missing_link |
 Posted: Fri Dec 09, 2016 1:17 am Post subject: REST API Oddity...[SOLVED] |
 |
|
Acolyte
Joined: 08 Jan 2004
Posts: 59
|
Having a bit of an odd issue with a REST API within toolkit. Everything was working fine, and now I get an error that the HTTP Input node is unconnected!!
Long story short, I've re-created a copy of the REST API project, imported the swagger spec, recreated all of the code (luckily only one method within the project), and all appears OK. I can build a bar file, deploy, test and all is OK. But as soon as I make any change to the swagger then I get the same error as above.
I had this issue a while ago with a different API which I tracked down to a quote in a field description. The current swagger validates ok in Swagger Editor so it should be OK (but then so did the other!).
Short of recreating the swagger from scratch and adding field by field (which I'm probably going to have to do!!)...has anyone else had a similar issue? I've looked through the FixPacks and can't see any obvious fix for this.
Currently on IIB 10.0.0.1 (yes i know we're up to FP7 with lots of enhancements in this space) but can't upgrade due to where we are in Project cycles, and I've made my concerns known.
thanks
Last edited by missing_link on Fri Dec 09, 2016 4:01 am; edited 1 time in total |
|
| Back to top |
|
 |
| timber |
| Posted: Fri Dec 09, 2016 1:48 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1280
|
| I encountered a similar problem, and I fixed it by opening the generated message flow and reattaching the missing connections. I suspect a little buglet somewhere in the toolkit. I probably should have opened a PMR, but then I would have been expected to reproduce it, answer lots of questions about it etc... |
|
| Back to top |
|
|
| missing_link |
| Posted: Fri Dec 09, 2016 1:54 am Post subject: |
|
|
Acolyte
Joined: 08 Jan 2004
Posts: 59
|
Yeah, tried that  but then get a java error when i try and save it!!! |
|
| Back to top |
|
|
| missing_link |
| Posted: Fri Dec 09, 2016 3:59 am Post subject: |
|
|
Acolyte
Joined: 08 Jan 2004
Posts: 59
|
Well it seems this time the break to the auto-generated flow happens when I promote properties from the SOAPRequest node and then modify the swagger spec. If I remove the promoted properties and modify the swagger then the main-flow repairs itself!!
Tried the same with an HTTPRequest node, but this works fine.
At least I can work around my "issue" |
|
| Back to top |
|
|
| timber |
| Posted: Fri Dec 09, 2016 1:25 pm Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1280
|
| Makes sense - I had promoted properties in my REST API too. Thanks for posting your findings for others to benefit from. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
