Repository: juddi Updated Branches: refs/heads/master df037b02f -> a0bfccd6a
JUDDI-866 subscription notifier may fail to send messages under certain conditions. added null checks, updated readme to reflect recent (since 3.2) build parameter changes Project: http://git-wip-us.apache.org/repos/asf/juddi/repo Commit: http://git-wip-us.apache.org/repos/asf/juddi/commit/a0bfccd6 Tree: http://git-wip-us.apache.org/repos/asf/juddi/tree/a0bfccd6 Diff: http://git-wip-us.apache.org/repos/asf/juddi/diff/a0bfccd6 Branch: refs/heads/master Commit: a0bfccd6af1a25ddb3ca78d4f99d56bb580e8ff4 Parents: df037b0 Author: alexoree <[email protected]> Authored: Sun Oct 19 12:06:59 2014 -0400 Committer: alexoree <[email protected]> Committed: Sun Oct 19 12:06:59 2014 -0400 ---------------------------------------------------------------------- .../apache/juddi/subscription/SubscriptionNotifier.java | 2 ++ readme.txt | 12 +++++++----- 2 files changed, 9 insertions(+), 5 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/juddi/blob/a0bfccd6/juddi-core/src/main/java/org/apache/juddi/subscription/SubscriptionNotifier.java ---------------------------------------------------------------------- diff --git a/juddi-core/src/main/java/org/apache/juddi/subscription/SubscriptionNotifier.java b/juddi-core/src/main/java/org/apache/juddi/subscription/SubscriptionNotifier.java index d6e9d5f..7d06b0c 100644 --- a/juddi-core/src/main/java/org/apache/juddi/subscription/SubscriptionNotifier.java +++ b/juddi-core/src/main/java/org/apache/juddi/subscription/SubscriptionNotifier.java @@ -384,6 +384,8 @@ public class SubscriptionNotifier extends TimerTask { getSubscriptionResults.setChunkToken(chunkToken); resultList = subscriptionImpl.getSubscriptionResults(getSubscriptionResults, publisher); body.setSubscriptionResultsList(resultList); + if (resultListContainsChanges(resultList)) + //if (!IsEmpty(resultList)) notifier.notifySubscriptionListener(body); chunkToken=body.getSubscriptionResultsList().getChunkToken(); } http://git-wip-us.apache.org/repos/asf/juddi/blob/a0bfccd6/readme.txt ---------------------------------------------------------------------- diff --git a/readme.txt b/readme.txt index 04b4173..d5b5912 100644 --- a/readme.txt +++ b/readme.txt @@ -8,20 +8,22 @@ Here's some quick notes for building, testing and deploying JUDDI from source. 4) Make sure the Maven/bin folder and the JDK/bin folders are in the current path 5) execute "mvn clean install" -That should build the whole project and test all Java components. Depending on your computer's speed, it can take up to 15 minutes to build. +That should build the key modules of the project and test most of the Java components. Depending on your computer's speed, it can take up to 15 minutes to build. To enable additional output during the build and test project: mvn clean install -Ddebug=true +To build all of the project modules, including utilities and sample projects, run the majority of the integration tests and documentation (this is our CI build): + mvn clean install -Pdist + + To attach the debugger to the build process mvn -Dmaven.surefire.debug clean install It listens on port 5005 by default. More info on debugging maven projects is here http://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging.html -To setup an Eclipse environment with support for building using the Google Web Toolkit portlets in Pluto, see the blog entry here http://apachejuddi.blogspot.com/2013_02_01_archive.html -Eclipse will initially complain about maven plugins. +To setup an Eclipse environment, simply import the maven project. -To setup a Netbeans environment, the process is much simpler. -Install Netbeans and open the project. Compiling from Netbeans however doesn't work and you'll have to resort to command line builds +To setup a Netbeans environment, start netbeans and open the maven based project To build your changes locally and skip the the tests run: --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
