Feature/bugfix query 20130314

Dear my friend.

I found some problems.
so I fixed it.

 1.the results should be sorted first before trimed. all entities retrieved by some condition (A> 0) can be sorted by other property.(order by B) but if some part is not taken into account when sorting, we can't get the result expected. (see EntityManagerImpl.java, RelationManagerImpl.java)
 2.The "reversed" property has been used with ambiguity. (see QueryProcessor.java)
 3.When I"install" using maven , "rest" component has some error since it's looking for an incorrect jar file. (see pom.xml)
 4.When we do run a complex query, the following problem is discovered
   - Complex query : has sort condition or one or more logical operator (AND/OR/NOT)

   First, If the number of entities exists more than "Limit" property's value and the query has one or more logical operator (AND/OR/NOT), it does not work correctly. because each node handle limited entities.
   Second, Cursor should be used to cut the final result, but it is used to dealing with the results of each node to cut.
 
Thanks.