Author |
Message
|
isd_chh |
Posted: Thu Mar 12, 2009 3:31 am Post subject: Missing Builders in Project Properties (Builders) |
|
|
Newbie
Joined: 12 Mar 2009 Posts: 3
|
I am currently encountered problem in message broker Toolkit during generating the Deployment BAR file for my Message Flow project.
When I check the Project properties for my Message Flow project, at the Builders page, I found that there are Missing Builder error for the below 2 builder :-
(1) com.ibm.etools.mft.bar.barbuilder
(2) com.ibm.etools.mft.rdb.spxmibuilder
Could you please let me know how to overcome problem ? What is the actual cause ?
Do I did need to install 2 plug-in (bar.barbuilder & rdb.spxmibuilder)
? Where can I get the 2 plug-in ? |
|
Back to top |
|
 |
WMBEAI |
Posted: Thu Mar 12, 2009 3:48 am Post subject: |
|
|
Acolyte
Joined: 02 Mar 2009 Posts: 66
|
|
Back to top |
|
 |
mqjeff |
Posted: Thu Mar 12, 2009 4:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
No.
The Toolkit needs to be reinstalled. |
|
Back to top |
|
 |
isd_chh |
Posted: Fri Mar 13, 2009 12:38 am Post subject: |
|
|
Newbie
Joined: 12 Mar 2009 Posts: 3
|
What's version of Broker Toolkit contain the plug-ins as below ?
(1) com.ibm.etools.mft.bar.barbuilder
(2) com.ibm.etools.mft.rdb.spxmibuilder
WebSphere Message Broker (Toolkit) Version 6.1.0.2 can fix above issue ? |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Mar 13, 2009 3:25 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Every version of the Toolkit should include a barbuilder. I'm less sure about the spxmibuilder.
So EITHER your Toolkit install is *broken* and needs to be REINSTALLED, OR you are trying to use a project from a newer version of the Toolkit.
But if you were trying to use a v6.1 project from a v6.0 Toolkit, you would have said so, and someone would have said "You can't do that". |
|
Back to top |
|
 |
isd_chh |
Posted: Fri Mar 13, 2009 4:30 am Post subject: |
|
|
Newbie
Joined: 12 Mar 2009 Posts: 3
|
Will try to reinstall Broker Toolkit 6.1.0 and patch to test again ....[/url] |
|
Back to top |
|
 |
craigp |
Posted: Tue Aug 14, 2012 3:47 pm Post subject: |
|
|
Newbie
Joined: 28 Mar 2011 Posts: 8
|
I too have encountered a similar problem and it's manifested across several people on my team consistantly.
I was trying to track down:
Why does eclipse change the sort order of the project files for no apparent reason?
We initially started with 7.0.0.0 at our company.
We are now running: 7.0.0.3-20110825_1025
Old flow projects contain:
com.ibm.etools.mft.esql.lang.esqllangbuilder
com.ibm.etools.mft.mapping.builder.mappingbuilder
com.ibm.etools.mft.flow.msgflowxsltbuilder
com.ibm.etools.mft.flow.msgflowbuilder
com.ibm.etools.mft.bar.ext.barbuilder
com.ibm.etools.mft.bar.barbuilder
NEW projects do NOT contain:
com.ibm.etools.mft.bar.barbuilder
They still however contain:
com.ibm.etools.mft.bar.ext.barbuilder
com.ibm.etools.mft.bar.barbuilder comes up as "Missing Builder"
In "eclipse > project > properties > Builders" window.
Everything still works fine.
I suspect an older version used an old builder and the newer version has changed the builder but the old one is still remaining.
Whats really annoying about this is different people's eclipse instances tend to SORT the builders differently. This painful come SVN updates/commits/merges as there are a whole load of conflicts.
What I'm thinking about doing is removing the (old?) missing bar builder and seeing if that fixes the issue.
Can anyone confirm any specific changes in the builders across versions?
Does anyone know why the sort order of the builders would be abitrialy changed by the toolkit?
Can someone confirm what builders should be in 7.0.0.3?
Many Thanks.[/list] |
|
Back to top |
|
 |
lancelotlinc |
Posted: Wed Aug 15, 2012 5:26 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
Don't manually create or edit bar files. Its a sure way to painful time consumption.
A smart developer will always store his/her source code in source control. Get the latest source, and rebuild the bar with the most recent version of toolkit.
Make sure your effective level on your runtime is the same level as your toolkit. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Aug 15, 2012 5:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
lancelotlinc wrote: |
Get the latest source, and rebuild the bar with the most recent version of toolkit. |
From how I read the post, that's exactly the step that's experiencing an error. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Wed Aug 15, 2012 6:43 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
I guess I should emphasize the point about using automation to build bars: ie. Ant or equivalent.
If you are invoking mqsicreatebar, there is no reason to worry about the internals of the toolkit. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Aug 15, 2012 7:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
lancelotlinc wrote: |
I guess I should emphasize the point about using automation to build bars: ie. Ant or equivalent.
If you are invoking mqsicreatebar, there is no reason to worry about the internals of the toolkit. |
Unless the workspace isn't correct, and so the projects don't build regardless of whether you open them with the Toolkit in a ui mode or if you open the Toolkit through mqsicreatebar in a headless mode. |
|
Back to top |
|
 |
craigp |
Posted: Wed Aug 15, 2012 11:32 pm Post subject: |
|
|
Newbie
Joined: 28 Mar 2011 Posts: 8
|
Hi,
We don't manually create BAR files. We generally use the toolkit for small dev stuff and have a build server running in headless mode for "proper" builds. Its governed by Jenkins/ANT and has full test automation, unit tests, integration tests, SVN integration and automatic versioning of stuff.
Everything works. (Although coverage reports of flows and ESQL would be nice someday)
The .project files are checked in.
The toolkits (of different developers which are on the same version) are changing the sort order of the "builders" inside the .project files. This creates merge conflicts.
Additionally, one builder is reported as missing.
I'm wondering:
Why does the toolkit re-sort the file?
What builders are "supposed" to be there? (Was one removed on some toolkit version?)
Code: |
<buildSpec>
<buildCommand>
<name>com.ibm.etools.mft.esql.lang.esqllangbuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.ibm.etools.mft.mapping.builder.mappingbuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.ibm.etools.mft.flow.msgflowxsltbuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.ibm.etools.mft.flow.msgflowbuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.ibm.etools.mft.bar.ext.barbuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>com.ibm.etools.mft.bar.barbuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
|
|
|
Back to top |
|
 |
lancelotlinc |
Posted: Thu Aug 16, 2012 5:02 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
craigp wrote: |
We don't manually create BAR files. We generally use the toolkit for small dev stuff and have a build server running in headless mode for "proper" builds. Its governed by Jenkins/ANT and has full test automation, unit tests, integration tests, SVN integration and automatic versioning of stuff.Everything works. |
Wow ! I AM impressed ! Come with to see smdavies and you can have a pint on him. I'll buy the chips.
Nice going on the automation. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Aug 16, 2012 5:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
lancelotlinc wrote: |
craigp wrote: |
We don't manually create BAR files. We generally use the toolkit for small dev stuff and have a build server running in headless mode for "proper" builds. Its governed by Jenkins/ANT and has full test automation, unit tests, integration tests, SVN integration and automatic versioning of stuff.Everything works. |
Wow ! I AM impressed ! |
And again, this was kind of apparent from what had been said in the initial posts...  |
|
Back to top |
|
 |
|