• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Rob Spoor
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Carey Brown
Bartenders:

J2ee1.4 and web services container

 
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Up_toDate Java Sapiens,
J2ee1.4 specification will come with web service support.
Will there be a "Web Service Container" apart from web and ejb container ? Or will that leverage the existing containers?
Will there be an altogether different component or Servlets and EJBs be used as a web service componenet?
ThanX
Mandan.
 
Ranch Hand
Posts: 1871
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
Please have a look at JSR 109 which is planned to be a part in the J2EE 1.4 specification.
I do not think that a separate container is required but I think that the new specification will build on existing facilities and provide for deployment etc
Here is what it proposes


Specifically, we will focus this JSR on:
The programming model for implementing a web service. This may include defining a new server side base classes and frameworks, specifying new APIs, defining new concrete subclasses of JSP, Servlet or an existing EJB type like MessageBean. Any extensions would be analogous to HttpServlet extending generic Servlet or the approach the Enterprise MediaBeans takes in defining subtypes of EntityBeans.
The client side programming model for using web services from Java. This would be analogous to the client programming model that EJB defines. This would explain how to use the APIs defined in JSRs 67, 93 and 101 in tandem. Again, the intent is to minimize new concepts introduced.
The specification would state how existing concepts, like the EJB transaction model, security for Servlets, EJBs, or HttpSession State materialize in web services usage and implementation.
Defining how to extend the basic Servlet/HTTP model to include dispatching web services over FTP, e-mail, etc. Again, this ideally references the existing JSRs/Java standards and focuses on the programming model and parts needed to support web services.
Define the concrete model for developing and deploying a web service on top of J2EE.

 
Mandan Happy
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Rahul,
Thats where I want to know more.
Why do you think that the existing container infrastructure and components are sufficient ?
I dont want to go by the spec since I believe that JSR 109 was done at rocket speed to get Web services incorporated in J2EE1.4 .
So is the case with the JAX-RPC final spec.(You see that it doesnt even provide serializers/deserializers for Collections.)
thanX
Mandan
Chennai
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic