Option 5: is not a program restriction. It's a ejb best practices guideline.
"Typically, if a bean is accessible remotely, it should be coarse grained"
Please confirm. Thanks!
regards,
Prakash Yaji
About Question enthuware.oce-ejbd.v6.2.518 :
Moderator: admin
-
- Posts: 25
- Joined: Sun May 13, 2012 1:39 am
- Contact:
-
- Site Admin
- Posts: 10386
- Joined: Fri Sep 10, 2010 9:26 pm
- Contact:
Re: About Question enthuware.oce-ejbd.v6.2.518 :
Yes, that is why it says "should" and not "must".
HTH,
Paul.
HTH,
Paul.
-
- Posts: 25
- Joined: Sun May 13, 2012 1:39 am
- Contact:
Re: About Question enthuware.oce-ejbd.v6.2.518 :
Thank you for your clarification!admin wrote:Yes, that is why it says "should" and not "must".
HTH,
Paul.
-
- Posts: 1
- Joined: Sun Mar 19, 2017 2:37 am
- Contact:
Re: About Question enthuware.oce-ejbd.v6.2.518 :
Just a small note. I found answer 1 this not entirely correct. For me it could also be part of the correct answers: "An enterprise bean must not use any static fields."
Infact from an Oracle article: "Nonfinal static class fields are disallowed because enterprise bean instances will behave differently depending on whether or not they are distributed."
Infact from an Oracle article: "Nonfinal static class fields are disallowed because enterprise bean instances will behave differently depending on whether or not they are distributed."
-
- Site Admin
- Posts: 10386
- Joined: Fri Sep 10, 2010 9:26 pm
- Contact:
Re: About Question enthuware.oce-ejbd.v6.2.518 :
It disallows only non-final static fields. Final static fields are ok. The given statement is incorrect because it is talking about all static fields.
Who is online
Users browsing this forum: No registered users and 4 guests