Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!

Augg Stine

Greenhorn
+ Follow
since Mar 24, 2004
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Augg Stine

Data logic & Business logic
if ur application is heavy on data logic than the business logic in the sense that it handles huge data. But at the same time, it doesn’t involve complex business logics & doesn’t represent a complicated transaction system, it is better to go for servlets itself.

Network call with EJB
Internally, J2EE uses the Java Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP) to enable remote, distributed method calls and applications. While this approach provides benefits, it also generates a large amount of overhead, with a corresponding performance hit as stubs are referenced, parameters go through the marshaling process, and objects are tossed around the network.

Implementing middle tier services
EJB has a middle tier, which implements services such as instance pooling, transactions, security etc. The required services can be implemented in the non-EJB environment and tailored to the needs of our application with the required changes in the settings & the code without going for EJB.
Example:
Proper handling of objects, which makes Garbage Collection efficiently happening through out, user transaction etc.

EJBs are costly in terms of development.
We require having a set of deployment descriptors and Home & Remote interfaces. We require taking care of setting the right TX attribute for the business methods. And also, Deployment & maintenance will be costly in terms of time and resources.
In the case of java components, we don’t require to do what ever mentioned above.

But, when we have IDEs like WSAD, this point is not fully valid as these IDEs facilitate many things that we require to do.

Resource pooling without EJBs
Almost all major J2EE servers allow us to get connection pooling and thread pooling whether we use java components or EJB components.
No it is not a value object.
This Process Object class might use value Object
Hi Kyle,
I would write some thing abt this process object.
I have got a business method in Session Facade. This mehod has to do many validation before actually inserting some thing to DB.
This validation has got some to & fro kind of between my application server & the DB.
What i do here is that i will all these validation over a no. of methods in some thing called ProcessObject. When all the validation & the required insertions are over, this PO will return the requireed value to the Business Method.
People say that If i do n't use this PO, & if i do all these on the session bean itself, it will be costly in terms of performance.
is that right??? I don't think so ...
regards/ Augg
Hi all
Is there any design pattern called 'Process Object'??
The framework in which i was working some time back, had it this way.
Swing app. --> Flow Contoller (Stateless session) --> Event --> Session Facade --> Process Obj --> DAO / Entity Bean
In this, I have got the Process Object which is a java class which would have no. of methods being called for a single method in the Session Facade Business methods.
believe that you could understand what the PO exactly does???
But i really don't understand what is the use of this??
And also, it is not listed out in the sun site under the J2EE design Patterns.
love to hear any thing on this.
thank u in advance

regards,
Augg
java Bean is an ordinary class.
But EJB is designed to run in the J2EE framework & act as an enterprise component.
Hope i'm clear to you
regards/ Augg
hi
I think that it is 99% due to EJB, which is not deployed on the server.
check it out once again
regards,
Augg
for one instance, we can go for swing rather web ...
it is ur rich GUI.
I srongly believe that maintaining session thru stateful session bean will be very much costly in terms of performance. instead we could use stateless session beans with http session implemented in servlets
rgds/ Augg
We are not implementing that we make a way for the container to implement.
When we r deploying the EJB, the container creates some .class files one of which would implement the component interface that the container could manage the EJB effectively.
I think that this partially answers ur question
rgds/ Augg
Also i appreciate Mr. RajaniKanth Bhargava who has done a great job even after seeing the prior comments.
Hi Sajet,
I was just going thru all the comments posted in this thread.
I really appreciate ur hard work & passion to learn more.
DOn't worry ... go ahead ...
U will learn more ...
All the beat

- Augg
hi,
I don't think that it is cache problem.
I think that it is a problem with our JSP.
Can u include the following code in ur jsp at the very begining and try ...
<%
//Remove the Cache from Browser.
response.setHeader("Cache-Control","no-cache"); //HTTP 1.1
response.setHeader("Pragma","no-cache"); //HTTP 1.0
response.setDateHeader ("Expires", 0); //prevents caching at the proxy
%>
hi
What is the TX attribute, u have given for ur sesion & entity bean.
I believe that the Business method in session bean is calling the entity bean and both come under a single TX.
And also, Plz check whether UR DB table has got updated and only ur jsp is not refreshed???

regards,
Augg
Hi,
it is all because of a big boss "Container".
In a table, if i have 100 fields, i can tell the container to take care of any no. of fields. So that the container takes cares of those fields i.e. the container is responsible for their persistence, their isolation level, transaction etc ..