|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Getting a warning message while creating a REST API -IIB V10 |
« View previous topic :: View next topic » |
Author |
Message
|
shashangupta |
Posted: Tue Aug 01, 2017 10:54 am Post subject: Getting a warning message while creating a REST API -IIB V10 |
|
|
Newbie
Joined: 01 Aug 2017 Posts: 2
|
I am getting the below warning message in the automatically generated REST API message flow while creating a REST API (by importing a swagger document) -
"This message flow is automatically generated. Do not edit this message flow. If you edit the message flow, your changes will be overwritten without a warning."
The IBM Integration Bus version we are using is V 10.0.0.7
What's the significance of this error? And under what conditions, code (what code) will be overwritten? |
|
Back to top |
|
 |
Vitor |
Posted: Tue Aug 01, 2017 11:25 am Post subject: Re: Getting a warning message while creating a REST API -IIB |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
shashangupta wrote: |
What's the significance of this error? |
It's not an error, it's a warning not to put custom code in the auto generated components.
It's the same concept as not putting custom ESQL in the IBM provided procedures.
shashangupta wrote: |
And under what conditions, code (what code) will be overwritten? |
Any code you put in the automatically generated components will be overwritten any time the Toolkit feels it necessary to regenerate them.
Basically put your user code in your user nodes and you'll be fine. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
shashangupta |
Posted: Tue Aug 01, 2017 11:45 am Post subject: |
|
|
Newbie
Joined: 01 Aug 2017 Posts: 2
|
Our requirement is to add some common subflows like exception and logging in the main auto generated message flow. What would be the best approach to do that? |
|
Back to top |
|
 |
Vitor |
Posted: Tue Aug 01, 2017 12:00 pm Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
shashangupta wrote: |
What would be the best approach to do that? |
- Let the autogenerated flow handle the error. I strongly doubt your common error flow handles every possible combination of error responses that can be included in a SWAGGER document, which means at best the API won't behave the way the clients think it will, and that will annoy them.
- Why are you logging a REST API? That's either going to be a very big log or a very underutilized API. If you want metrics on API usage, use an API management tool (ideally the API management tool you're already using to expose the REST API) _________________ Honesty is the best policy.
Insanity is the best defence. |
|
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
|
|
|
|