Set the "User" manage property for the bean which wants to use the user bean. Say person bean wants to use the user bean
and also create the getter and setter for user in the person bean.
// getter/setter for user
Note: user property name in the person bean and the managed property name should match.
But you shouldn't. It's ugly, non-portable and violates the principle of Inversion of Control. Much cleaner and more flexible to link beans together by wiring them in the framework instead of hard-coding their connection with platform-specific functions.
Customer surveys are for companies who didn't pay proper attention to begin with.