Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

J2EE version for the Assignment + Hibernate / Web Services

 
Goan Balchao
Ranch Hand
Posts: 93
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I had a question aout the assumptions / suppositions that can be made. As far as the ab ssignment is concerned, there is no mention of the J2EE version as long as the solution is a pure J2EE one.
As part of this assignment, I want to be able to dabble in new technologies and I am thinking of using Hibernate for my data access (instead of entity beans) abstracted by a layer of course and Web services to expose some of the business logic. I think EJB 2.1 gives an opportunity to expose Stateless Session Beans as Web Service Components.
If I detail the reasons as to the reasons of choosing a particular module say Spring or Hibernate or Web Services or even JBoss AOP for orthognal services like logging in my assumptions list, would I be ok ?
Has anyone tried deviating from the path ?
I am 100% sure, I wouldn't use Entity Beans for my data access logic in any future application that I work on.

Goan
 
Giju George
Ranch Hand
Posts: 333
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
.
If I detail the reasons as to the reasons of choosing a particular module say Spring or Hibernate or Web Services or even JBoss AOP for orthognal services like logging in my assumptions list, would I be ok ?

Goan[/QB]


One of the most important criteria is "the architecture must use J2EE environment". Spring, Hibernate etc.. are not part of J2EE
 
Theodore Casser
Ranch Hand
Posts: 1902
Hibernate Netbeans IDE PHP
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
To expand on what Giju George has said, I'd suggest sticking with the features of J2EE rather than going into other complimentary frameworks or other open-source Java technologies, if only to keep away from giving them something to nitpick about. The project can successfully be accomplished without Hibernate/Spring/Struts, etc.

That being said - to confirm what you're thinking, no, there's no 'required' version of J2EE for the project. I don't see any reason why you couldn't, in theory, use something more up-to-date than the version used in Part I. (Which is how SCJD works - you can use any production version of Java, if I understand correctly.)
 
Goan Balchao
Ranch Hand
Posts: 93
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the inputs. Yes, I would not like to nitpick much with Sun too I guess. What I'll do however is go through the EJB3 spec and persuse the changes that had in mind for the Persistence mecnhanism and see if it fits into the solution.
If not, I'll still use Hibernate and thorughly explain my reasons for doing so. All grading can go to H***. I am more concerned about utilizing the time spent in this assignment to do somthing meaningful rather than the normal design stuff that I do day to day anyway !
BTW, I have to disagree with Hibernate or Spring not being part of J2EE. They are not part of the J2EE spec per se, but they still are part of the J2EE solution, don't you agree ?

Akasmat.
 
Theodore Casser
Ranch Hand
Posts: 1902
Hibernate Netbeans IDE PHP
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Goan Balchao:
If not, I'll still use Hibernate and thorughly explain my reasons for doing so. All grading can go to H***. I am more concerned about utilizing the time spent in this assignment to do somthing meaningful rather than the normal design stuff that I do day to day anyway !


Well, that is your right, I suppose. However... I don't really see the point of doing an assignment if you don't care about the grading. But, as I've said in other posts, there's nothing that says you can't do it, and while I think that it's asking for trouble, you do have the correct thought that you should explain your reasons for using it if you do. Let us know what happens.

BTW, I have to disagree with Hibernate or Spring not being part of J2EE. They are not part of the J2EE spec per se, but they still are part of the J2EE solution, don't you agree ?


I don't, no. They're not part of Java EE in any shape, but are extensions built on the solutions using Java EE that help with design patterns and easing development. However, that doesn't make them part of Java EE any more than MySQL's JDBC drivers are part of Java SE.
[ October 22, 2005: Message edited by: Theodore Casser ]
 
Akar Rafidj
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think that Hibernate is now part of J2EE, it has been selected as persistence mechanism for EJB 3.0. The latest release of Hibernate is 3.1 rc2.
The final release will be ready soon.

Akar
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic