POJO doesn't mean "class with no business logic", it means the class doesn't have dependencies on infrastructure or on a framework. (Some frameworks that use POJOs, like Hibernate and Spring, encourage their users to make their POJOs conform to some of the JavaBean conventions, mostly naming of getters and setters.) Services in Spring are POJOs (or close to being POJOs, some people might think the introduction of annotations was a step away from POJO purity), and they have business logic.
If a class doesn't contain any logic there is no value testing it. Typically those kinds of classes get covered by tests that exercise the real functionality, since they are used to hold data passed into or out of the business logic code.
If you really have to write tests for classes with only getters and setters, consider writing some code to generate these useless tests for you.