im using hibernate pojos for persistence in my application. And im using "open session in view" pattern. So you can guess that my POJOs map straight to the UI.
Everything goes smooth as long as my UI fields map straight to my POJOs. But the problem arises when there are some complex UI fields to show. e.g. when a concatenation of several properties map to single field on UI or some calculation over a field.
Now, its obvious that some sort of customized value object layer would be involved between the POJOs and the UI.
But i need an optimized way of doing so. Some design pattern or any best practice followed by hibernate.
Another option that i had in mind was to extend custom wrapper classes with POJOs but in that case after loading a POJO i would have to go by setting all the fields of that POJO into my wrapper class.
I wonder how the hibernate guys easily claim to map there POJOs straight to UI and not discuss the counter part.
Any help in this matter would be greatly appreciated.
Im sure there are a lot of guys out there like me looking for a solution for this issue.

You can always use the object assembler pattern.

Which framework are you using? Struts? JSF?

The reality is, your UI won't always map directly to JavaBeans. Indeed, everything from formatting of data, to simply providing an easy set of classes to UI developers, might mean a little 'massaging' of the object model might be needed. It doesn't always make life easy, but sometimes it needs to be done.

Can you give more specifics about your problem? Maybe a simplified example?

-Cameron McKenzie

Thnx for a quick reply Cameron.
Im using JSF framework. Actually what im trying to achieve is that there is a field in databse with timestamp data type.
Now, at some points in my application i have to show only the date part of that timestamp. So for that to happen i need some sort of customized pojo, cause i cant directly map that pojo's field to the UI.
Let alone this scenerio there are a number of other points in my application where i have to show computational data on behalf of a set of properties in a pojo.
And i would like some efficient methodology to achieve this paradigm.
One more thing, i like my UI to be free of such business domain logic. It should be as loosely coupled as possible. As a matter of fact it should only concentrate on its part of the job that is displaying the provided information.
Please share your personal experience, how u managed to get over this issue.