| Author |
Message
|
| j.f.sorge |
 Posted: Tue Jul 21, 2009 5:51 am Post subject: private / protected ESQL functions / procedures? |
 |
|
Master
Joined: 27 Feb 2008
Posts: 218
|
Hi!
We have discussed if there is any possibility to create private / protected ESQL functions / procedures as you can do it in Java for example. InfoCenter does not show something like this.
Is there any possibility to do this in ESQL in WMB 6.0?
Thanks in advance!
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jul 21, 2009 6:15 am Post subject: Re: private / protected ESQL functions / procedures? |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| j.f.sorge wrote: |
Is there any possibility to do this in ESQL in WMB 6.0?
|
Not that I'm aware of. There was a discussion recently on the protection of ESQL code (for intelectual property reasons) that might illuminate your discussion.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| j.f.sorge |
| Posted: Tue Jul 21, 2009 6:49 am Post subject: Re: private / protected ESQL functions / procedures? |
|
|
Master
Joined: 27 Feb 2008
Posts: 218
|
| Vitor wrote: |
| j.f.sorge wrote: |
Is there any possibility to do this in ESQL in WMB 6.0?
|
Not that I'm aware of. There was a discussion recently on the protection of ESQL code (for intelectual property reasons) that might illuminate your discussion. |
I'm very sorry but I cannt find the discusion you mentioned. Can you please give me a hint?
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jul 21, 2009 7:02 am Post subject: Re: private / protected ESQL functions / procedures? |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| j.f.sorge wrote: |
| Vitor wrote: |
| j.f.sorge wrote: |
Is there any possibility to do this in ESQL in WMB 6.0?
|
Not that I'm aware of. There was a discussion recently on the protection of ESQL code (for intelectual property reasons) that might illuminate your discussion. |
I'm very sorry but I cannt find the discusion you mentioned. Can you please give me a hint? |
I was thinking of this one.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| j.f.sorge |
| Posted: Tue Jul 21, 2009 7:13 am Post subject: Thanks a lot |
|
|
Master
Joined: 27 Feb 2008
Posts: 218
|
Thanks a lot for the thread, but we were thinking about internal (utility) functions which can only be called within one broker schema. So we will give the functions a prefix that we all know it's an internal one.
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jul 21, 2009 7:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
There's certainly no reason you couldn't put different functions in different schemas. Not what I pictured when you said "private function" but I see what you're getting at.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| j.f.sorge |
| Posted: Tue Jul 21, 2009 7:24 am Post subject: |
|
|
Master
Joined: 27 Feb 2008
Posts: 218
|
| Vitor wrote: |
| There's certainly no reason you couldn't put different functions in different schemas. Not what I pictured when you said "private function" but I see what you're getting at. |
Yes, you may put it into different broker schema but you can always import a schema which allows you to use all functions in there.
Is there a possibility to disallow importing of a broker schema?
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jul 21, 2009 7:20 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| j.f.sorge wrote: |
| Vitor wrote: |
| There's certainly no reason you couldn't put different functions in different schemas. Not what I pictured when you said "private function" but I see what you're getting at. |
Yes, you may put it into different broker schema but you can always import a schema which allows you to use all functions in there.
Is there a possibility to disallow importing of a broker schema? |
This would be of no help in this case as you can still reference it by giving it the full long name (schema+function). 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| j.f.sorge |
| Posted: Tue Jul 21, 2009 11:24 pm Post subject: |
|
|
Master
Joined: 27 Feb 2008
Posts: 218
|
So we will add a prefix to the FUNCTION / PROCEDURE to name to mark it as private. It would be the easiest way to get around this problem.
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 22, 2009 12:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| j.f.sorge wrote: |
| So we will add a prefix to the FUNCTION / PROCEDURE to name to mark it as private. It would be the easiest way to get around this problem. |
Though it does not prevent anyone referencing it using the prefix. So you're back to enforcing standards via QA and so forth (which is of course no bad thing).
It's just not a technical solution in the way a private function is.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| j.f.sorge |
| Posted: Wed Jul 22, 2009 2:01 am Post subject: |
|
|
Master
Joined: 27 Feb 2008
Posts: 218
|
| Vitor wrote: |
| j.f.sorge wrote: |
| So we will add a prefix to the FUNCTION / PROCEDURE to name to mark it as private. It would be the easiest way to get around this problem. |
Though it does not prevent anyone referencing it using the prefix. So you're back to enforcing standards via QA and so forth (which is of course no bad thing).
It's just not a technical solution in the way a private function is. |
As I know the other WMB developers it'll be okay to say that functions with a special prefix should only be used internally. And you are totally right - enforcing standards is a must, but we only give a set of standard projects which get a version tag and every developer has to use this one. We don't have any ESQL code style check as we have it for Java...
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
