Is this bad OOP design?

Is it bad OOP design to have purely data objects? ie objects whos only purpose is to carry around data? (For example a user object who only has a username field, but has a usermanager class taking care of user-related stuff.)

Lets write a scheme program that generates java classes and interfaces in all varying degrees of difference. Some of the classes will implement the interfaces or extend each other, some will be in packages with each other, etc.

Eventually, the UML diagram of all of our generated OOP will look like the disneyland logo.

This will be the key for the final boss of the INTERNETS.