Re: jsp to .Net question

[Ron Cordell <roncordell@attbi.com>]

On Thursday 20 March 2003 10:10, web dev wrote:
> hi all,
>   I have a requirement to access webservices
> (currently available on the .net platform) through JSP
>  pages.
> -Is it a good idea to access web services through jsp
> directly
> - or use JSPs only for the layout purpose and use
> servlets internally to interact with the web services.
> - or is there any other better way of accomplishing
> this

Leave JSP's for presentation ONLY, and use a servlet dispatcher and POJO 
(plain old java objects) to handle the web services.

> - I am not considering the usage of EJBs at this
> point. The entire business logic available through web
> services (this code access a legacy database). Some
> enhancements can be made to this code to add
> additional functionality. Hence, I do not see a need
> for entity beans.
> is this assumption correct?

Are you talking about using entity beans to access the database directly or 
are you talking about using session beans? If you need to support distributed 
transactions to data in the legacy database, and your webservices can 
participate in that transaction, then you probably need to use the 
transaction manager of the j2ee container to help with this, depending on 
what coordinates the transactions.

> - also, since the session object is reachable through
> JSPs and servlets, I am assuming that there is no need
> for using session beans as well.
> - It would be a complete j2ee application with
> JSP->servlets->ejbs ... but I think with web services
> on the .net platform doing all the work of accessing
> the legacy DB and implementing the business
> services.....using EJBs further could be an overkill.
>
> I would greatly appreciate your comments in this
> regard.
>

Again, it depends on how you slice this application. If you are using JSP and 
servlets to do only reading of data to the webservices exposed on the .dotnet 
platform, then you probably don't need ejb's (session or entity beans). If, 
on the other hand, you are coordinating work from outside the 
webservices/dotnet, i.e., from within the JSP/servlet side, then you might 
want to consider other ways to access the legacy data and coordinate work, 
*if distributed transactional access is required*. In this case you might 
consider the added complexity of a j2ee container. Servlet container != j2ee 
container, don't forget. Keep it as simple as possible!

> thanks
> Raj
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com

-- 
  5:21pm  up 10 days, 20:08,  4 users,  load average: 0.10, 0.30, 0.92