About Question enthuware.ocejws.v6.2.293 :

Moderators: Site Manager, fjwalraven

Post Reply
austinor
Posts: 41
Joined: Mon Oct 27, 2014 11:35 pm
Contact:

About Question enthuware.ocejws.v6.2.293 :

Post by austinor » Tue Nov 04, 2014 7:07 am

For the question:
In a legacy enterprise system there are different applications and protocols. The company owning the enterprise system wants increase its business by allowing clients to connect over the internet. What is the quickest way to expose these legacy application services.

Supplied correct answer:

By creating an EJB based Web Service that exposes the required services and connects with the back-end system.
Does it have to be an EJB-based web service? If yes, why is that so? ... I mean, can't servlet-based JAX-WS web service also do?

austinor
Posts: 41
Joined: Mon Oct 27, 2014 11:35 pm
Contact:

Re: About Question enthuware.ocejws.v6.2.293 :

Post by austinor » Tue Nov 04, 2014 7:20 am

Is it because of the usual services provided by the EJB-container such as transaction management, connection pooling, session management, persistence, ... etc?

fjwalraven
Posts: 429
Joined: Tue Jul 24, 2012 2:43 am
Contact:

Re: About Question enthuware.ocejws.v6.2.293 :

Post by fjwalraven » Tue Nov 04, 2014 1:50 pm

Yes, you answered most of it yourself. (it is possible with a Servlet-based Web Service but preferably an EJB-based Web Service should be used)

Apart from the reasons you summed up: Servlets are not scalable like EJB's. Of every Servlet only one instance is created. EJB's are pooled and grabbed when needed.

Regards,
Frits

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest