I'll have to thank you for being persistent in your trial to become familiar with the designer code... It is in the best interest of all that there are more contributors to the GPD. So indeed please go ahead and describe the process on a wiki page.
But as you may have already seen, the project layout has changed again overnight. So the wiki might page might need a change now and then. ;-)
Thanks and regards,
Koen
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958728#3958728
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958728
Hi Dave. Unfortunately the alpha (and beta) versions of JBossESB won't have clean enough support for content based routing. But it is on the plan for the GA release. How this fits into the architecture was outlined in the original architecture document from February (on the labs web site, I think). But now is a great time to start the discussion about how to move it from architectural theory into practice because we're now looking at how to bring the current ESB architecture in line with the February document.
Give me a chance to put some of the original ideas down here and then we can start looking at how what you've done could fit in.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958683#3958683
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958683
Hi!
Based on your description, I'd think this is a feature of the "L2 cache", not a bug.
The SVN traversal is probably the most expensive process in Kosmos, so I've introduced a so-called second level cache here. This is very simple: if the revision number did not change since the last traversal, it won't be traversed again, but the previous result will be returned from the cache! (This saves tremendous amount of time in most real-world scenarios.)
Can you check that if you commit a change to your repo the traversal will be done again?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958682#3958682
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958682
Its not ok to include multiple versions of a library in the main build. If a component needs another incompatible version is needs to be pulled out the build and integrated as a binary component with its conflicting version isolated via class loader scoping.
If the error is due to changes in the commons httpclient, what are the changes causing problems? Updating the testsuite would make it incompatible with the 4.0 branch code.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958649#3958649
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958649
sounds great! Ok, so just so we are clear - to make things easier to add new test modules to the testsuite module, you want a generic way of doing it, so in test module you only call two targets per module - package-tests and tests, and then on the module level we have diff targets integrated in these two, if necessary. I will try to get this changed by the end of the week, so we can use it for the CR3 testing and later port it to 2.6. I have also updated the CC build, just haven't gotten the chance to test it yet.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958642#3958642
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958642