EJB 2.0 best practices suggested a design pattern where data and behavior were were treated as independent concerns. Stone Age Development (SAD) using structs and procedural programming sounded bad so they were dubbed Transfer or Value Objects, emphasis on "Object".
My EJB 3.0 entities are now full-fledged objects versus SAD artifacts but I'm worried that I have too many @Transient methods. I get this nagging feeling that perhaps I'm violating some principal in not keeping the transient state in some other wrapper class. Is there a rational basis for my concern? I think it is just a regurgitated EJB 2.0 feeling that I should ignore.