On Mar 26, 2009, at 3:11 PM, Bhakti Mehta wrote:
> Hi all,
> I am trying to follow
> http://weblogs.java.net/blog/jfarcand/archive/2009/03/glassfish_v3_ex.html
> and http://blogs.sun.com/dochez/
>
> I have an EjbWebserviceServlet which is registered to dispatch
> requests for ejb endpoints.
>
> If I have to implement a grizzly adapter I can have
> EjbWebserviceAdapter extending GrizzlyAdapter
> Then the service method of my adapter can do whatever I was doing in
> EjbWebserviceServlet.
> Questions.
>
> 1.What is the relation between HttpRequest/Response and
> GrizzlyRequest/Response? I assume you must be parsing an HttpRequest/
> Response and populating the GrizzlyRequest/Response right?
>
Jean Francois, can you help bahkti on this one...
> 2.I saw in both yours and Jerome's blogs that adapters can be
> registered by adding an adapter element in the xml file with context
> root.
> Then the file is in META-INF/lib of the jar which is deployed.
> How would I handle this in v3 at deploment time. Say I see an ejb
> endpoint and I want to map its context root to my
> EjbWebserviceAdapter. Can I do this programmatically
yes look at the RequestDispatcher contract in glassfish-api.
>
> 3. Please can you give some advice on how would this work. Say I
> deploy the ear file with webservices. Then there is someway I
> register that this endpoint is mapped to my Adapter. Where would
> this registration happen.
in the start() of your ApplicationContainer.
> Previously we used to register the EjbWebServiceServlet in
> WebContainer but I have observed that if I deploy a ear file the
> WebContainer never gets a chance to startup so I was asked to
> implement this adapter by Jerome.
>
>
> Thank a lot,
> Bhakti
>
>
>
>