Author |
Message
|
Ching |
Posted: Mon Dec 06, 2004 5:25 pm Post subject: Problems using control space in Message broker toolkit |
|
|
 Apprentice
Joined: 08 Nov 2004 Posts: 25 Location: Portland, OR
|
Hi,
Has anyone had problems using the control space (I think it's called 'content assist') ? Every so often, I can't use content assist, and then later it is functional again.
I'm using Message broker Version 5 with CSD3.
The flow I'm developing will format data to SAP.
I'm trying to set OutputRoot using content assist, but I get a message
that says 'no completions available.'
I usually do a refresh, rebuild, close and open the project, close and open
the Message broker toolkit to try to get message broker to pick up the message set with content assist.
Any ideas would be appreciated.
Thanks,
Ching |
|
Back to top |
|
 |
TonyD |
Posted: Mon Dec 06, 2004 7:29 pm Post subject: |
|
|
Knight
Joined: 15 May 2001 Posts: 540 Location: New Zealand
|
Other causes of this are forgetting to set 'Default Wire Format' when creating a Message Set or failing to reset 'Runtime Parser' value to the correct setting. |
|
Back to top |
|
 |
shanson |
Posted: Tue Dec 07, 2004 3:00 am Post subject: |
|
|
 Partisan
Joined: 17 Oct 2003 Posts: 344 Location: IBM Hursley
|
TonyD - can you explain why you think 'Default Wire Format' needs to be set? The content assist code is not sensitive to this property. |
|
Back to top |
|
 |
JT |
Posted: Tue Dec 07, 2004 6:21 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003 Posts: 1564 Location: Hartford, CT.
|
Quote: |
Every so often, I can't use content assist, and then later it is functional again. |
Next time, before taking drastic measures, try invoking Content Assist by clicking Edit on the toolbar and then clicking Content Assist. The intermittent problem may somehow be related to the keyboard mapping of the CTRL/Space key combination. |
|
Back to top |
|
 |
Ching |
Posted: Tue Dec 07, 2004 10:53 am Post subject: This a known bug |
|
|
 Apprentice
Joined: 08 Nov 2004 Posts: 25 Location: Portland, OR
|
Hi,
I've opened a PMR support ticket with IBM. Their tech support person
told me that this a KNOWN problem. Unfortunately, neither fix pack 3 or 4 do anything to fix this.
What's the best way to get around this? Without content assist, you have manually parse the message, and fill it in exactly. This doesn't seem very practical (or much fun).
Any ideas for a work around??
Thanks.
Ching |
|
Back to top |
|
 |
Ching |
Posted: Tue Dec 07, 2004 11:20 am Post subject: I got the content assist to work. |
|
|
 Apprentice
Joined: 08 Nov 2004 Posts: 25 Location: Portland, OR
|
I finally got the content assist to work.
After doing a refresh, rebuild, closing and opening the project, and closing and opening the Message broker toolkit, I tried something else.
In the Message set project, I changed the runtime parser from MRM to XML, saved it, and then changed it back to MRM.
Somehow that seemed to refresh something, and now I can see all the segments in the assist window.
Thanks for the suggestions!
Ching |
|
Back to top |
|
 |
shanson |
Posted: Wed Dec 08, 2004 2:24 am Post subject: |
|
|
 Partisan
Joined: 17 Oct 2003 Posts: 344 Location: IBM Hursley
|
Ching, the message set component keeps a cache of messages that the esql and mapping editors reference. It looks like the cache was stale and you found a way to refresh it. I'll ask someone to take a look at this. |
|
Back to top |
|
 |
bbakerman |
Posted: Sun Aug 14, 2005 4:48 pm Post subject: |
|
|
Apprentice
Joined: 17 Dec 2003 Posts: 41
|
shanson wrote: |
Ching, the message set component keeps a cache of messages that the esql and mapping editors reference. It looks like the cache was stale and you found a way to refresh it. I'll ask someone to take a look at this. |
Has anyone else found a definitive answer on this one. Sometimes my code assit works for MRM messages and some times it doesnt. I cant work out the "triiger" that makes it work.
I am on CSD6 and was on CSD 5 and still the same intermittent (more off than on) result.
MRM without content assist is not that useful from the ESQL coders point of view. |
|
Back to top |
|
 |
|