| Author |
Message
|
| sammm |
 Posted: Thu Aug 01, 2013 7:00 am Post subject: IBMDefined auto-gen folders and XSD clashes |
 |
|
Newbie
Joined: 13 Jun 2013
Posts: 8
|
i'm developing a series of flows and subflows in v8.0.0.2 of WMB and we were getting some clashes with file names for our XSDs when LIBs being referenced by an APP had the same filenames & paths. we resolved this by moving things around but WMB still keeps generating "IBMDefined" folders with soap & soapenv11 schemas in them which are causing file/path clashes again. is there a way to stop/control this?
Many thanks
Martin |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Thu Aug 01, 2013 7:15 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Aug 01, 2013 7:22 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
| Are you using the default schema? If so, why? |
Why don't you explain why using the default schema is so bad/evil/<redacted>?
_________________
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 |
|
|
| sammm |
| Posted: Thu Aug 01, 2013 7:37 am Post subject: |
|
|
Newbie
Joined: 13 Jun 2013
Posts: 8
|
| ok - being new to this, i take it that's a bad thing. can you expand a little on what i should be doing? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Aug 01, 2013 7:39 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| smdavies99 wrote: |
| lancelotlinc wrote: |
| Are you using the default schema? If so, why? |
Why don't you explain why using the default schema is so bad/evil/<redacted>? |
Ok, I didn't want to jump to conclusions.
He may already be using package names to organize the code. If so, the distraction based on relevance to the OP's problem at hand may not be justified.
http://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html
| Quote: |
| Package names are written in all lower case to avoid conflict with the names of classes or interfaces. |
In any Eclipse project, including WebSphere Message Broker toolkit, when you create artifiacts, you fill in the package name you want (the edit box is called schema name), which is usually:
com.mycompany.middleware.projectname -- or whatever you want --
Never ever should one use the default schema.
http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/topic/com.ibm.etools.mft.doc/bc23150_.htm
| Quote: |
| A broker schema is a symbol space that defines the scope of uniqueness of the names of resources defined within it. The resources include message flows and other optional resources such as ESQL files, Javaâ„¢ files, and mapping files. |
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Aug 01, 2013 7:42 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Aug 01, 2013 8:07 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
com.mycompany.middleware.projectname -- or whatever you want --
Never ever should one use the default schema.
|
The OP might want to know why the default schema is so bad when using ESQL? ESQL does not have packages or classes so the OP might just be a tad confused.
The example above is for Java which as some of us know is the root of all evil  when it comes to computer languages.
_________________
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 |
|
|
| fatherjack |
| Posted: Thu Aug 01, 2013 8:08 am Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| lancelotlinc wrote: |
| smdavies99 wrote: |
| lancelotlinc wrote: |
| Are you using the default schema? If so, why? |
Why don't you explain why using the default schema is so bad/evil/<redacted>? |
Ok, I didn't want to jump to conclusions.
He may already be using package names to organize the code. If so, the distraction based on relevance to the OP's problem at hand may not be justified.
http://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html
| Quote: |
| Package names are written in all lower case to avoid conflict with the names of classes or interfaces. |
In any Eclipse project, including WebSphere Message Broker toolkit, when you create artifiacts, you fill in the package name you want (the edit box is called schema name), which is usually:
com.mycompany.middleware.projectname -- or whatever you want --
Never ever should one use the default schema.
http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/topic/com.ibm.etools.mft.doc/bc23150_.htm
| Quote: |
| A broker schema is a symbol space that defines the scope of uniqueness of the names of resources defined within it. The resources include message flows and other optional resources such as ESQL files, Javaâ„¢ files, and mapping files. |
|
And how does that explain why using the default schema is so bad?
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Aug 01, 2013 8:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
When you regenerate WSDLs or bindings or reimport wsdls, Toolkit can re-add the default xsds. Toolkit can also improperly add predefined soap formats to libraries when it doesn't need to.
I was aware of some work being done to fix this, but I'm not sure what the status of that is.
In the meantime, just manually delete the duplicate artifacts from Toolkit, and be aware that sometimes they get re-added. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Aug 01, 2013 9:34 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| fatherjack wrote: |
| lancelotlinc wrote: |
| smdavies99 wrote: |
| lancelotlinc wrote: |
| Are you using the default schema? If so, why? |
Why don't you explain why using the default schema is so bad/evil/<redacted>? |
Ok, I didn't want to jump to conclusions.
He may already be using package names to organize the code. If so, the distraction based on relevance to the OP's problem at hand may not be justified.
http://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html
| Quote: |
| Package names are written in all lower case to avoid conflict with the names of classes or interfaces. |
In any Eclipse project, including WebSphere Message Broker toolkit, when you create artifiacts, you fill in the package name you want (the edit box is called schema name), which is usually:
com.mycompany.middleware.projectname -- or whatever you want --
Never ever should one use the default schema.
http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/topic/com.ibm.etools.mft.doc/bc23150_.htm
| Quote: |
| A broker schema is a symbol space that defines the scope of uniqueness of the names of resources defined within it. The resources include message flows and other optional resources such as ESQL files, Javaâ„¢ files, and mapping files. |
|
And how does that explain why using the default schema is so bad? |
If you use the default schema, you may typically run into naming collisions. For example , when integrating Master Data Management, the default XSD exports do not contain namespaces. If you try to import those into Message Broker, you get naming collisions for commonly named variables. The best answer is to go re-export your XSDs from MDM with the namespace tick box selected.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| sammm |
| Posted: Thu Aug 01, 2013 11:08 am Post subject: |
|
|
Newbie
Joined: 13 Jun 2013
Posts: 8
|
All,
cheers for the input - no i've not done the training. like alot of people it's been 'on the job' with knowledge transfer.
i'll review what we've done based on the default namespaces info from you all,
again,
thanks for the help.
Martin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Aug 01, 2013 11:18 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
For what its worth, I have only used ESQL BROKER SCHEMAS a few times in more than 10 years of working with broker.
Using the default schema has not actually proved to be a problem to me.
Ironically, the few problems I have had have been calling functions defined in once schema from another.
_________________
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 |
|
|
| mqjeff |
| Posted: Fri Aug 02, 2013 5:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| This has nothing to do with Broker ESQL schemas. |
|
| Back to top |
|
|
| sammm |
| Posted: Fri Aug 02, 2013 6:33 am Post subject: |
|
|
Newbie
Joined: 13 Jun 2013
Posts: 8
|
@mqjeff - thats what we're seeing - deleting the duplicates does resolve the issue but they then get added back in at some points.
- Martin |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Aug 02, 2013 6:46 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| sammm wrote: |
@mqjeff - thats what we're seeing - deleting the duplicates does resolve the issue but they then get added back in at some points.
- Martin |
Which if you use package names, you would avoid the collisions in the first place and not have to worry about it.
@mqjeff - please clarify your answer. Its confusing to the OP.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
