| Author |
Message
|
| Herbert |
 Posted: Wed Nov 25, 2009 6:31 am Post subject: SOAP Input - Promoting properties not possible? |
 |
|
Centurion
Joined: 05 Dec 2006
Posts: 146
Location: Leersum, The Netherlands
|
Hi,
Just wondering, does someone know why it is not possible to promote properties from the Basic tab for the SOAP Input node?
Kind Regards, Herbert |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Nov 25, 2009 3:23 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I don't believe that you can promote properties from any input node.
How would you dynamically set them as it is the first thing that gets executed in the flow...
What do you need to change? If it is the parsing, set the input to BLOB, you can dynamically parse in either a content redescriptor node or in a compute or java node.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Herbert |
| Posted: Thu Nov 26, 2009 2:17 am Post subject: |
|
|
Centurion
Joined: 05 Dec 2006
Posts: 146
Location: Leersum, The Netherlands
|
| fjb_saper wrote: |
| I don't believe that you can promote properties from any input node. |
This is possible for other input nodes.
| fjb_saper wrote: |
| How would you dynamically set them as it is the first thing that gets executed in the flow... |
I think promoted properties are handled during build/deploy time, not during run-time. It's not dynamically, it's configured on a other level during development.
| fjb_saper wrote: |
| What do you need to change? |
I did want to created a SOAP adapter for the project I working on. With standard error handling, monitoring, logging, etc. So that every flow in the project that uses SOAP input does this the same way. The URL and WSDL settings must be promoted in this scenario. It works great for other input nodes like MQ input. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 26, 2009 1:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Well, I guess at that point you may need to raise a PMR.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| AkankshA |
| Posted: Thu Nov 26, 2009 11:47 pm Post subject: Re: SOAP Input - Promoting properties not possible? |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| Herbert wrote: |
Hi,
Just wondering, does someone know why it is not possible to promote properties from the Basic tab for the SOAP Input node?
Kind Regards, Herbert |
Well, the properties which are not promotable are derived from wsdl and change of wsdl from dev to qct or prod env does not seem viable....
My 2 cents.. may be hursley ppl also thought same way...
_________________
Cheers |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Nov 27, 2009 4:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Properties that are promotable need to be configurable in the first place, i.e. settable on the BAR file.
Properties that are configurable are dealt with only at deploy time, not at build time.
It should seem reasonable that information about the specific WSDL file used is needed at build time, and not only at deploy time. |
|
| Back to top |
|
|
| Herbert |
| Posted: Fri Nov 27, 2009 6:49 am Post subject: |
|
|
Centurion
Joined: 05 Dec 2006
Posts: 146
Location: Leersum, The Netherlands
|
| mqjeff wrote: |
| Properties that are promotable need to be configurable in the first place, i.e. settable on the BAR file. |
From a developer point of view this is not a requirement for me. I use promoting a property a lot, however not with the intention to use it at deploy-time. (by configuring the bar-file)
I use it to prevent code-duplication, forcing standards, etc. In below construction I want to promote properties from the nodes in the sub-flow so I can set them when I use this sub-flow in the mainflows. I don’t want to promote those properties again from the mainflow to the bar file.
bar => mainflow => subflow => node1/node2/etc |
|
| Back to top |
|
|
| seeknee |
| Posted: Wed Jan 27, 2010 2:02 pm Post subject: |
|
|
Apprentice
Joined: 08 Aug 2002
Posts: 41
Location: Melbourne, Australia
|
| Herbert wrote: |
| mqjeff wrote: |
| Properties that are promotable need to be configurable in the first place, i.e. settable on the BAR file. |
From a developer point of view this is not a requirement for me. I use promoting a property a lot, however not with the intention to use it at deploy-time. (by configuring the bar-file)
I use it to prevent code-duplication, forcing standards, etc. In below construction I want to promote properties from the nodes in the sub-flow so I can set them when I use this sub-flow in the mainflows. I don’t want to promote those properties again from the mainflow to the bar file.
bar => mainflow => subflow => node1/node2/etc |
Did you ever manage to get this working, I am trying to do the same thing.
_________________
IBM Certified Specialist MQSeries
IBM Certified Specialist WebSphere MQ Integrator
IBM Certified Solution Designer WebSphere Business Integration Message Broker V5
"Good judgement comes from experience, and experience comes from poor judgement" |
|
| Back to top |
|
|
| park3927 |
| Posted: Thu Aug 12, 2010 6:29 pm Post subject: |
|
|
Newbie
Joined: 12 Aug 2010
Posts: 2
|
| Any update on this topic? I'm the similar situation as Herbert. If I can promote properties on basic tab of soap input node, it'll be great. I can manage the WSDL information from main flow |
|
| Back to top |
|
|
|
|
