Author |
Message
|
mattfarney |
Posted: Fri Feb 17, 2006 1:33 pm Post subject: Odd behavior in the Toolkit |
|
|
 Disciple
Joined: 17 Jan 2006 Posts: 167 Location: Ohio
|
I use batch files to compile and deploy message flows. Since I switched to this technique, the toolkit displays some of the valid flows and connections with the red error 'X'.
The functional behavior is fine, but I'm curious why the toolkit thinks they are a problem. The error specifies: cannot find <someflow>.msgflow. Those flows are specified in the compiled Bar and are in the same directory structure with no typos. If I open the file in the Toolkit manually (Broker Administration Navigator perspective), the red error 'X' goes away.
Anyone else seen this kind of behavior?
I'm guessing that the Eclipse workspace is not getting 'refreshed' for lack of a better word, but I cannot find any documentation on that.
-mf |
|
Back to top |
|
 |
dipankar |
Posted: Mon Feb 20, 2006 10:57 pm Post subject: |
|
|
Disciple
Joined: 03 Feb 2005 Posts: 171
|
connections with the red error 'X' only appears when message flow does not exist. Most probably you are using subflow. Is this correct?
If yes, try to open subflow from the parent flow. you will not able to open subflow.
Which version are u using?
reimport the message flow and see what happens this time. _________________ Regards |
|
Back to top |
|
 |
mattfarney |
Posted: Tue Feb 21, 2006 8:26 am Post subject: |
|
|
 Disciple
Joined: 17 Jan 2006 Posts: 167 Location: Ohio
|
It will usually bring up a subflow chooser box. Other times, it simply loads the file from the correct directory location and the X's go away.
These also seem to only happen once per instance. I believe the toolkit does some file monitoring. I wonder if raw imports (i.e. copy files over the existing workspace directories) causes the toolkit issues.
(Version 5.0)
-mf |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Feb 21, 2006 8:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
mattfarney wrote: |
I believe the toolkit does some file monitoring. I wonder if raw imports (i.e. copy files over the existing workspace directories) causes the toolkit issues. |
If you haven't refreshed the project, I bet this is the issue. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
mattfarney |
Posted: Tue Feb 21, 2006 8:53 am Post subject: |
|
|
 Disciple
Joined: 17 Jan 2006 Posts: 167 Location: Ohio
|
How do you that in the project or is it a command line interface? I looked for this and couldn't find it anywhere.
-mf |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Feb 21, 2006 10:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Right-click on the project in the navigator and select "refresh".
Or there are some preferences that will refresh your workspace and projects at certain times. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
|