Is that still the case

So sorry, if this is not the right place to ask this. I got my certification on may 2010. And have recently been given a chance to start a new project. So from requirement gathering stage. I have start to draw the data domAin model. However, some developers in my project has strongly disagree about drawing data domain model. Claim we should start program, and the jpa would do the work, as long as the layers is defined.

I am wandering whether is that really it? I learn the overall architectural through this SCEA process, I am so proud when I got this. But I think the guys in the team really put me off.... And am bit wounded

Bess,
There should still be a data design to reduce unnecessary work. Just because it is easy to code JPA doesn't replace the importance of planning. Unless they are doing agile database schema development. This would be talked about though. Agile isn't the absence of design.

I'm going to move this to our agile/process forum since it's not about the SCEA.

I am wandering whether is that really it? I learn the overall architectural through this SCEA process, I am so proud when I got this. But I think the guys in the team really put me off.... And am bit wounded

You will have to defend your decisions / design. Do not be put off that folks question it. They always will. As long as you have a reasonable counter argument, everything is good