Trying to get a clean run

[rafanami]

Good afternoon, I've tried the module (did a fork and clone), and tried to run the vows tests like this:

macbook-pro-de-rafael-nami:node-donkey rafanami$ vows tests/processors/test-choice.js

But I had this exception below:
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: Cannot find module '../../lib/node-donkey/processors/Filter'
at Function._resolveFilename (module.js:334:11)
at Function._load (module.js:279:25)
at Module.require (module.js:357:17)
at require (module.js:368:17)
at Object. (.../node-donkey/tests/processors/test-choice.js:5:14)
at Module._compile (module.js:432:26)
at Object..js (module.js:450:10)
at Module.load (module.js:351:31)
at Function._load (module.js:310:12)
at Module.require (module.js:357:17)

I've done the npm install of the dependencies described in package.json, but it failed too. And I have vows globally installed in my computer. What can be going wrong? I'll keep trying changing the test code and giving feedback.

[rafanami]

Verified in the code, there's no Filter nor Multicast class in the package. Is there something in other branches?

[biamontidv]

Hi rafanami,

thanks for taking the time to look at node-donkey!
sorry for the late reply, but I was away during the weekend.
yes that's correct there are no such objects in the processors. Before going any further, I just want to mention that has been months since last time I had time to work on this and that at that time it was still much work in progress (things not yet committed, etc etc) ...
Furthermore, there are now interesting modules out there (e.g. wire.js, when.js) that I feel would provide the right foundation. So I intend to start to work again on this, refactoring code.
I don't know if you just want to use the module or if you like the idea and would like to contribute. If that's so, then maybe we can discuss further how to proceed.
In the meantime, I'll try to dig out the old code and see what the missing commits are.

[biamontidv]

Hi again,

I had a quick look and it seems that the tests are wrong.
For the missing objects, that's correct to be missing: in fact, they are currently not needed. If you look into the endpoints (under components), you'll see that they are responsible for 'creating' the right processors. For example, now the filter endpoint actually just execute the match comparison itself.

I'll come back to you with a working example

[biamontidv]

Hi,

try to do the following:

• in the node-modules folder of node-donkey, create symlinks to the folders direct, file, log and obj in components, naming them as donkey-<foldername> (this is needed for dynamic dependency resolution so you can add other components, but I don't like it as it is.... another thing to change)
• in the file examples/route.js change the var filename to the correct path to the simple.xml route definition
• try to run node examples/route.js

Let me know :)

[rafanami]

Hi.
I've verified the code, indeed I've found out about the symlink problem, and the testcases are completely outdated - there are some properties that are not existing anymore now that the *Endpoints are creating processors. But the symlink I didn't do yet, I'll try again right now and change the code to close the issue.

[rafanami]

I'll take a look in these new libraries that you've described. The thing that I've liked donkey is because I've already have Camel background, so it was a natural fit for starting up (I was thinking on creating myself a version to node).