| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Expose only necessary fields |
« View previous topic :: View next topic » |
| Author |
Message
|
| saviobarr |
 Posted: Mon Jul 03, 2017 9:21 am Post subject: Expose only necessary fields |
 |
|
Centurion
Joined: 21 Oct 2014
Posts: 100
Location: Sao Paulo, Brazil
|
Hi everyone,
I have a Integration Service, which has an operation that exposes a type (xsd) with 40 fields, but the service consumer needs provide values for only 2 fields. Is there a way to show only the necessary fields of my huge xsd?
When I create a SoapUI project for my integration service, it shows all 40 fields in the request section, but only 2 fields will be passed in the request.
Thanks in advance.
Savio Barros
_________________
Go as far as you can go. Then go farther! |
|
| Back to top |
|
 |
| Armageddon123 |
| Posted: Mon Jul 03, 2017 10:21 am Post subject: |
|
|
Acolyte
Joined: 11 Feb 2014
Posts: 61
|
so, all other 38 fields must be optional . so you need to provide only the small xsd to consumer, consumer will get the whole xsd only if they do http get and suffixed with a query string ?wsdl. this can be disallowed by setting on soap nodes.
But still the consumer can try random input fields and possible it matches any of those 38 fields,, if that is a problem , then you must create a wrapper service on top of 40 fields service to only expose 2 fields and have it follow standard authentication/authorization procedures. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jul 03, 2017 10:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Or you could simply ignore the fact that the mapper shows all 40ish fields, and use it to only set the ones that need to be set.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| saviobarr |
| Posted: Mon Jul 03, 2017 11:03 am Post subject: |
|
|
Centurion
Joined: 21 Oct 2014
Posts: 100
Location: Sao Paulo, Brazil
|
| mqjeff wrote: |
| Or you could simply ignore the fact that the mapper shows all 40ish fields, and use it to only set the ones that need to be set. |
Yes. Currently I am using that approach, but the consumer team does not accept the fact that they can just ignore fields showed in the SoapUI request. Deal with people is always the worse part of each job 
_________________
Go as far as you can go. Then go farther! |
|
| 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
|
|
|
|
