| Author |
Regarding EJB Project Structure
|
Juggy Obhi
Ranch Hand
Joined: Jul 02, 2007
Posts: 51
|
|
What should be a good design pattern/Structure for an EJB based Enterprise Project.
Currently i follow the following pattern:
An EAR with EJB Module and Web Module.
I make Web Module dependent on EJB module's Client Module. (Through Buildpath)
Can this be improved? I mean is it good to have dependency among Projects. should i export EJB Module's Client Module as a JAR then put it in Web Module. Will it improve the Design?
|
It does not matter how many times you fall,what matters is how many times you stand back.
|
 |
Reza Rahman
author
Ranch Hand
Joined: Feb 01, 2005
Posts: 559
|
|
Juggy,
What you have is just fine. Indeed, I don't even bother with an EJB client module.
Regards,
Reza
|
Independent Consultant — Author, EJB 3 in Action — Expert Group Member, Java EE 6 and EJB 3.1
|
|
Juggy Obhi
Ranch Hand
Joined: Jul 02, 2007
Posts: 51
|
|
Hi Reza,
Thanks for your advice and at the same time for your book EJB 3 in Action it helped me in getting 91%.
|
|
Reza Rahman
author
Ranch Hand
Joined: Feb 01, 2005
Posts: 559
|
|
Juggy,
My pleasure and thanks for the kind words. I have been considering writing an article on how to setup EJB 3 IDE based projects using our GlassFish example code. Maybe I should try to make it a higher priority...
Regards,
Reza
P.S.: If you get a chance, an Amazon review is highly appreciated. We have some excellent reviews, but still just a handful compared to some other major EJB 3 titles.
|
|
 |
|
|
subject: Regarding EJB Project Structure
|
|
|
0
