MONGO_HOME=/Users/Aparna/Development/Projects/NoSQL/MongoDB
$MONGO_HOME/mongodb/bin/mongod --replSet nosqlmatters --dbpath $MONGO_HOME/mongodata/replica1 --port 27017 --rest --directoryperdb --fork --logpath $MONGO_HOME/log/replica1.log
$MONGO_HOME/mongodb/bin/mongod --replSet nosqlmatters --dbpath $MONGO_HOME/mongodata/replica2 --port 27018 --rest --directoryperdb --fork --logpath $MONGO_HOME/log/replica2.log
$MONGO_HOME/mongodb/bin/mongod --replSet nosqlmatters --dbpath $MONGO_HOME/mongodata/replica3 --port 27019 --rest --directoryperdb --fork --logpath $MONGO_HOME/log/replica3.log
Based on JAX-RS specification; @Path annotation is not mandatory on Resource classes. But many implementations seem to deviate from the specification.
But shouldn’t reference implementation adhere to the specification?
Resource classes are POJOs that have at least one method annotated with @Path or a request method designator.
layout | title | author |
---|---|---|
post |
Context Dependency Injection - Are you doing it right? |
aparnachaudhary |
CDI specification allows Field, Property (aka setter) and constructor injection. Like many developers out there, I also habitually use field injection. I must admit I never gave enough thought about it. But recently I saw a bean with more than 10 injection points and started to ponder over Dependency Injection.
The following blog post discusses why you should prefer constructor injection over field or setter injection. In the later part of the post, we will see how jQAssistant can be used to find beans with too many injection points or to enforce use of constructor injection.
/profile=full/subsystem=logging/root-logger=ROOT:write-attribute(name=level,value=TRACE) |
-
Example - https://www.gitbook.com/book/jaceklaskowski/mastering-apache-spark/discussions
-
Blog Hugo based - https://georgecushen.com/create-your-website-with-hugo/
-
Blog Travis Jekyll - http://pauldambra.github.io/using-travis-to-build-jekyll.html
-
How much time to invest in code refactoring?
-
Typically for new projects, assuming you are curating code well, no dedicated effort
-
Second year of the projects - start investing 10% of team effort on code refactoring
-
Increase this effort by 10% every upcoming year
-
-
Spagetti codebase