| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMB 6.1 or higher Coding and Naming Conventions |
« View previous topic :: View next topic » |
| Author |
Message
|
| EKhalil |
 Posted: Thu Feb 24, 2011 8:46 am Post subject: WMB 6.1 or higher Coding and Naming Conventions |
 |
|
Voyager
Joined: 29 Apr 2003
Posts: 99
Location: Boston, MA
|
| Is anyone aware of newly published WMB Coding and Naming Conventions ? |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Feb 24, 2011 9:27 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
What is wrong with the 'oldly' published ones or even better still, rolling your own if they don't suit your site?
_________________
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 |
|
|
| paintpot |
| Posted: Fri Feb 25, 2011 7:06 am Post subject: |
|
|
Centurion
Joined: 19 Sep 2005
Posts: 112
Location: UK
|
The only set I know of from IBM is:
ftp://public.dhe.ibm.com/software/integration/support/supportpacs/individual/ic04.pdf
and they are not very prescriptive. I think there was an even older version, but couldn't find it (maybe it was a previous of the above?).
Professional services will definitely have some, if you choose to pay up. Third party IBM partners also come tooled up if required. I've used neither, and have always 'rolled' / re-rolled my own (yawn).
Inconsistent code / poor naming standards in the toolkit samples is quite a flaw in my eyes - maybe we will see a change in WMB 8  |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Feb 25, 2011 9:02 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I don't know of any coding language won't enforce naming standards. For one thing there isn an ISO Standard which would be the sort of thing that would br the basis of what you are looking for,
Then there might be variants for different industries such as healthcare or banking FX.
However doing this would certainly put a cat amogst a lot of lawyers. There have been a number of very prominent lawsuits based upon the similarities of two pieces of code. If you enforced naming standrads then it would only be too easy to deny copying another person's or comanies code. .
"The Coding standard made me do it Honest Guv!"
The current Google vs Oracle spat and the SCO vs IBM saga are two that come to mind.
It is far better (IMHO and 35+ years of Sofware development) to implement
a set of standard that relevant to your organisation and more importantly ones that will be followed.
If you are working on a site that is 99.9% concerned with Flows that use SOAP it makes no sense at all to spend days or weeks working on a WMQ Object naming standard.
Standards should be (IMHO)
- Meaningful
- Relevant
- Open to review
- Don't get hung up on a few names.
- Follows Common Sense and KISS
The 'names' one is often a killer. I've been in endless meetings just to settl on the names of message flows. There was little attention given to what was in them consequently the level of technical debt that built up was truly gigantic.
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
