I think #2 would depend largely not just on the application, but on the methodology used to write the initial application. (For instance, my company's moving to using servlets mostly as wrappers to expose/access POJOs as we're trying to keep open options for exposing similar functionality through web-services.)
As for #1, like all things, it depends on how entrenched the given developer is in their ways. Switching over to POJOs requires more a change in how one looks at the architecture of an application rather than any difficult leap in learning a technology.
Theodore Jonathan Casser
SCJP/SCSNI/SCBCD/SCWCD/SCDJWS/SCMAD/SCEA/MCTS/MCPD... and so many more letters than you can shake a stick at!
Why is it difficult ? In fact it is much easier to move to POJO. Switching over to POJOs requires more a change in how one looks at the architecture of an application rather than any difficult leap in learning a technology.
I see. Understanding the concept as a whole is important.
I am using two POJOs in my application, One is User and another is Salary. And i am extending User in my Salary POJO, But one i try to query something in User POJO Hibernate throwing some errors like Property of User POJO is not there in Salary POJO.
Like userName is not a property of Salary POJO.
Why this happening, Is there any solution for this?
Thanks in Advance.
posted 14 years ago
Without seeing the the code, the Hibernate mappings, the query and the stack trace showing the error it is difficult to say that is going wrong.