| Author |
Can we make EJB3 project on websphere application server
|
|
| SyedSaifuddin 2006-09-18, 1:31 pm |
| Hi Everybody
I come back to join websphere community after a very long time. Now I am confuse to decide whether to use EJB3 or hibernate for data persistance. If EJB3 is supported now I prefer EJB3.
Any comment on my preference is appreciated.
Thank You
Best Regards
Syed Saifuddin
WebSphereGuru
www.yousifi.com.kw
| |
| Alfonso Vicente 2006-09-18, 1:31 pm |
| I ask the same on 09/13/2006... the answer is no...
Alfonso Vicente
"SyedSaifuddin" <s_saifu@hotmail.com> escribió en el mensaje
news:2054056454.1158566272436.JavaMail.wassrvr@ltsgwas010.sby.ibm.com...
> Hi Everybody
>
> I come back to join websphere community after a very long time. Now I am
> confuse to decide whether to use EJB3 or hibernate for data persistance.
> If EJB3 is supported now I prefer EJB3.
>
> Any comment on my preference is appreciated.
>
> Thank You
> Best Regards
> Syed Saifuddin
> WebSphereGuru
> www.yousifi.com.kw
| |
| Randy Schnier 2006-09-18, 7:56 pm |
| For what it's worth, if you're comparing against hibernate you're
probably most interested in the Java Persistence API (JPA) spec rather
than EJB3 as a whole. Both the JPA spec and the EJB3 spec were
developed by the same JavaEE expert group, and both leverage annotations
and POJO-driven development as primary goals.
The latest versions of hibernate support the JPA spec APIs. If you
program to those APIs, you retain the flexibility to switch to a
different JPA provider in the future if desired. Writing to a
standardized JavaEE API gives you the greatest amount of flexibility, if
you don't require vendor-specific functions.
Alfonso Vicente wrote:
> I ask the same on 09/13/2006... the answer is no...
>
> Alfonso Vicente
>
>
> "SyedSaifuddin" <s_saifu@hotmail.com> escribió en el mensaje
> news:2054056454.1158566272436.JavaMail.wassrvr@ltsgwas010.sby.ibm.com...
>
>
| |
| Don Brady 2006-09-19, 1:35 pm |
| RIght I am successfully using Toplink Essentials JPA under WAS 6.1 /
AST 6.1, complete with full annotation support etc.......
On Mon, 18 Sep 2006 14:39:01 -0500, Randy Schnier
<rschnier@us.ibm.com> wrote:
[vbcol=seagreen]
>For what it's worth, if you're comparing against hibernate you're
>probably most interested in the Java Persistence API (JPA) spec rather
>than EJB3 as a whole. Both the JPA spec and the EJB3 spec were
>developed by the same JavaEE expert group, and both leverage annotations
>and POJO-driven development as primary goals.
>
>The latest versions of hibernate support the JPA spec APIs. If you
>program to those APIs, you retain the flexibility to switch to a
>different JPA provider in the future if desired. Writing to a
>standardized JavaEE API gives you the greatest amount of flexibility, if
>you don't require vendor-specific functions.
>
>Alfonso Vicente wrote:
| |
|
| .. or try running the OSGi bundled EasyBeans EJB3 container within WAS6.1 as it is an OSGi runtime (based on Eclipse Equinox)
regards,
Shane
| |
| SyedSaifuddin 2006-09-22, 1:25 pm |
| Thank You Everybody
I get the good understanding of what to do if I am using WebSphere Application Server.
In my understanding hibernate is better than EJB3 if u r on WebSphere.
Please correct me if I am doing mistake.
Thank You,
Best Regards,
Syed Saifuddin
Software Engineer
| |
| rschnier 2006-09-22, 1:25 pm |
| Well, actually writing your app to the JPA interfaces is the best option. As mentioned previously, the latest version(s) of hibernate support the JPA interfaces.
|
|
|
|