| Author |
Message
|
| wmbfrz |
 Posted: Mon Jul 11, 2016 1:29 am Post subject: Behavior of components with common name in different Shared |
 |
|
Apprentice
Joined: 08 Jan 2010
Posts: 28
|
Hello,
Can anybody explain the runtime behavior of components with common name in different Shared Libraries? Lets say I have application A referring Shared library X deployed in an EG where another Shared Library Y is also deployed. Both X and Y have a subflow by the name mySubflow. Is it guaranteed that A will always work as per X.mySubflow in the runtime? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Jul 11, 2016 4:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If they're both in shared libraries and in the same broker schema, you'll have a name clash... Names in the shared libraries should be unique. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| stoney |
| Posted: Mon Jul 11, 2016 4:37 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2013
Posts: 140
|
Resources in shared libraries are always isolated and you cannot access a resource in a shared library without first referencing that shared library.
Application A will not be able to see the subflows in shared library Y unless you add a reference from application A to shared library Y.
If you try to reference both shared library X and shared library Y from application A, then you will get a deployment error.
This is because an application cannot reference two or more shared libraries with the same subflow in them. |
|
| Back to top |
|
|
| wmbfrz |
| Posted: Tue Jul 12, 2016 7:17 pm Post subject: |
|
|
Apprentice
Joined: 08 Jan 2010
Posts: 28
|
| stoney wrote: |
Resources in shared libraries are always isolated and you cannot access a resource in a shared library without first referencing that shared library.
Application A will not be able to see the subflows in shared library Y unless you add a reference from application A to shared library Y.
If you try to reference both shared library X and shared library Y from application A, then you will get a deployment error.
This is because an application cannot reference two or more shared libraries with the same subflow in them. |
Thanks. That's what i had in mind but thought better to have a second opinion.
Anyone who have observed otherwise or have relevant clarification to add are welcome to share further. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Jul 12, 2016 9:52 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| wmbfrz wrote: |
Thanks. That's what i had in mind but thought better to have a second opinion.
Anyone who have observed otherwise or have relevant clarification to add are welcome to share further. |
There have been posts in this thread from at least one person who works on the product at IBM so they should know what they are talking about.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
