I had similar issues, Jitu provided some samples which uses (please refer to
last week Grizzly Updates post)
-Simple Http provider
-Grizzly Http provider
-Using Spring, Grizzly adapters
The samples are working but it appears that some more work needs to be done.
I had some difficulties in compiling the code but I got it resolved. Now i
am trying to understand the code, seems like i need to understand the
internals on the Endpoint creation.
I would think if we know how to create jax-ws Endpoint then there are lot of
opportunities to customize. I looked at the Internet for
com.sun.xml.ws.WSEndpoint javadoc, i dont seem to find anything at all
Sendhil
Survivant 00 wrote:
>
> Hello
>
> #1 - Grizzly Deployer only parse web.xml file format. It doesn't support
> others formats (maybe the next project will support it).
>
> #2 - and did you add the jars for jaws in the classpath ?
>
> #3 - for now, you will have to setup your ServletAdapter by hand unless
> you
> use web.xml format.
>
> PS : We are working on Grizzly to add easier support for embedded Servlet.
>
>
> Hope that can help you to start.
>
>
>
> 2009/9/4 JDice <rolls.royal25_at_gmail.com>
>
>> Surviant,
>> Here is the war file. There are two issues
>> 1. ServletDeployer throws exception at parsing sun-jaxws.xml when I give
>> th
>> epath of expanded WAR file.
>>
>> List<ServletAdapter> adapters =
>> parser.parse(sunJaxWsXml.toExternalForm(),
>> sunJaxWsXml.openStream());
>>
>> 2. Same exception when I try to invoke in embedded way. Here is example:
>>
>> ServletAdapter adapter =
>> *new* ServletAdapter();
>>
>> adapter.addServletListener(
>> "com.sun.xml.ws.transport.http.servlet.WSServletContextListener");
>>
>> adapter.setServletInstance(
>> *new* com.sun.xml.ws.transport.http.servlet.WSServlet());
>>
>> adapter.setRootFolder(
>> "/webapps");
>>
>> ws.addGrizzlyAdapter(adapter,
>> *new* String[]{"/addnumbers"});
>>
>> I wanted to use Grizzly in Embeded way in my app, and wanted deploy web
>> apps. Different webservice end point needed to be executed based on
>> invoking
>> different web service. If I use ServletDeployer it is not giving me much
>> control over adding any new adapters.
>>
>> What I want to to pass my app context to the servlet/servlet acdapter
>> context so that servlet adapters/servlets can delegate the request by
>> doing
>> some pre prosessing and delegate to my app. I can do this for HTTP
>> service
>> but not able to do this fo a webservice. I donno how can an JAX-WS
>> endpoint
>> implementation can access servlet context or any other message context?
>> That
>> is where I am struck. Any pointers or examples greatly hepls.
>>
>> As JAX_WS is picking up I can see Grizzly with JAX-WS can be a great
>> inegration for some one line me looking for a light weight webservice
>> container that can be embed also.
>>
>> Thanks in advance,
>> JDice
>>
>>
>>
>> On Wed, Sep 2, 2009 at 2:46 PM, Survivant 00
>> <survivant00_at_gmail.com>wrote:
>>
>>> I don't see the attachment
>>>
>>> 2009/9/2 JDice <>
>>>
>>>>
>>>> Same results with 1.9.18 here is the sample WAR file used. I would like
>>>> see
>>>> if anyone had examples of using JAX-WS, that would be great help.
>>>>
>>>>
>>>> Survivant 00 wrote:
>>>> >
>>>> > can you provide your .war file ?
>>>> >
>>>> > and please.. can you try with 1.9.18+
>>>> >
>>>> >
>>>> > 2009/8/31 PT <rolls.royal25_at_gmail.com>
>>>>
>>>> >
>>>> >> I wanted see if any one used Grizzly with JAX-WS. I can make it
>>>> work
>>>> >> using
>>>> >> Grizzly Servlet Deployer. But not able make it work in emmbed
>>>> >> GrizzlyWebServer adding ServletAdapter and setting WSContextListener
>>>> and
>>>> >> WSServlet. Any body did this is? if yes please provide me details.
>>>> Or
>>>> >> Any
>>>> >> other ways to integrate JAX-WS with Grizzly? Also a strange problem
>>>> with
>>>> >> GrizzlyServletDeployer is when I expanded war file and give the war
>>>> file
>>>> >> location I am consitantly getting following exception. I am using
>>>> >> *grizzly-http-servlet-deployer-1.9.17-SNAPSHOT.
>>>> >> *It works if I give just the WAR file. I used jar -xvf webap.war to
>>>> >> expand
>>>> >> the war file.
>>>> >> **
>>>> >> Exception :
>>>> >>
>>>> >> Aug 31, 2009 11:45:06 AM
>>>> >> com.sun.grizzly.http.servlet.deployer.GrizzlyWebServerDeployer
>>>> deploy
>>>> >>
>>>> >> INFO: Will deploy application path=\webapps\app1\WEB-INF\web.xml
>>>> >>
>>>> >> Aug 31, 2009 11:45:38 AM
>>>> >> com.sun.grizzly.http.servlet.deployer.GrizzlyWebServerDeployer
>>>> deploy
>>>> >>
>>>> >> INFO: deployed application path=\webapps\app1\WEB-INF\web.xml
>>>> >>
>>>> >> Aug 31, 2009 11:45:38 AM
>>>> >> com.sun.xml.ws.transport.http.servlet.WSServletContextListener
>>>> >> contextInitialized
>>>> >>
>>>> >> INFO: WSSERVLET12: JAX-WS context listener initializing
>>>> >>
>>>> >> Aug 31, 2009 11:46:11 AM
>>>> >> com.sun.xml.ws.transport.http.servlet.WSServletContextListener
>>>> >> contextInitialized
>>>> >>
>>>> >> SEVERE: WSSERVLET11: failed to parse runtime descriptor:
>>>> >> *java.net.UnknownHostException*: C*
>>>> >>
>>>> >> java.net.UnknownHostException
>>>> >> *: C
>>>> >>
>>>> >> at java.net.PlainSocketImpl.connect(Unknown Source)
>>>> >>
>>>> >> at java.net.Socket.connect(Unknown Source)
>>>> >>
>>>> >> at java.net.Socket.connect(Unknown Source)
>>>> >>
>>>> >> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>> >>
>>>> >> at sun.net.NetworkClient.openServer(Unknown Source)
>>>> >>
>>>> >> at sun.net.ftp.FtpClient.openServer(Unknown Source)
>>>> >>
>>>> >> at sun.net.ftp.FtpClient.openServer(Unknown Source)
>>>> >>
>>>> >> at sun.net.www.protocol.ftp.FtpURLConnection.connect(Unknown Source)
>>>> >>
>>>> >> at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(Unknown
>>>> >> Source)
>>>> >>
>>>> >> at java.net.URL.openStream(Unknown Source)
>>>> >>
>>>> >> at
>>>> >>
>>>> com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(
>>>> >> *WSServletContextListener.java:108*)
>>>> >>
>>>> >> at com.sun.grizzly.http.servlet.ServletContextImpl.initListeners(
>>>> >> *ServletContextImpl.java:152*)
>>>> >>
>>>> >> at com.sun.grizzly.http.servlet.ServletAdapter.configureServletEnv(
>>>> >> *ServletAdapter.java:440*)
>>>> >>
>>>> >> at com.sun.grizzly.http.servlet.ServletAdapter.start(
>>>> >> *ServletAdapter.java:277*)
>>>> >>
>>>> >> at com.sun.grizzly.tcp.http11.GrizzlyAdapterChain.start(
>>>> >> *GrizzlyAdapterChain.java:118*)
>>>> >>
>>>> >> at com.sun.grizzly.http.SelectorThread.initEndpoint(
>>>> >> *SelectorThread.java:1101*)
>>>> >>
>>>> >> at com.sun.grizzly.http.SelectorThread.listen(
>>>> >> *SelectorThread.java:1152*)
>>>> >>
>>>> >> at com.sun.grizzly.http.embed.GrizzlyWebServer.start(
>>>> >> *GrizzlyWebServer.java:585*)
>>>> >>
>>>> >> at
>>>> com.sun.grizzly.http.servlet.deployer.GrizzlyWebServerDeployer.launch(
>>>> >> *GrizzlyWebServerDeployer.java:1142*)
>>>> >>
>>>> >> at com.gdas.grizzly.SampleWebServer3.main(
>>>> >> *SampleWebServer3.java:26*)
>>>> >>
>>>> >> Aug 31, 2009 11:46:11 AM
>>>> com.sun.grizzly.http.servlet.ServletContextImpl
>>>> >> initListeners
>>>> >>
>>>> >> SEVERE:
>>>> >> *
>>>> >>
>>>> >> com.sun.xml.ws.transport.http.servlet.WSServletException
>>>> >> *: WSSERVLET11: failed to parse runtime descriptor: *
>>>> >> java.net.UnknownHostException*: C
>>>> >>
>>>> >> at
>>>> >>
>>>> com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(
>>>> >> *WSServletContextListener.java:118*)
>>>> >>
>>>> >> at com.sun.grizzly.http.servlet.ServletContextImpl.initListeners(
>>>> >> *ServletContextImpl.java:152*)
>>>> >>
>>>> >> at com.sun.grizzly.http.servlet.ServletAdapter.configureServletEnv(
>>>> >> *ServletAdapter.java:440*)
>>>> >>
>>>> >> at com.sun.grizzly.http.servlet.ServletAdapter.start(
>>>> >> *ServletAdapter.java:277*)
>>>> >>
>>>> >> at com.sun.grizzly.tcp.http11.GrizzlyAdapterChain.start(
>>>> >> *GrizzlyAdapterChain.java:118*)
>>>> >>
>>>> >> at com.sun.grizzly.http.SelectorThread.initEndpoint(
>>>> >> *SelectorThread.java:1101*)
>>>> >>
>>>> >> at com.sun.grizzly.http.SelectorThread.listen(
>>>> >> *SelectorThread.java:1152*)
>>>> >>
>>>> >> at com.sun.grizzly.http.embed.GrizzlyWebServer.start(
>>>> >> *GrizzlyWebServer.java:585*)
>>>> >>
>>>> >> at
>>>> com.sun.grizzly.http.servlet.deployer.GrizzlyWebServerDeployer.launch(
>>>> >> *GrizzlyWebServerDeployer.java:1142*)
>>>> >>
>>>> >> at com.gdas.grizzly.SampleWebServer3.main(
>>>> >> *SampleWebServer3.java:26*)
>>>> >>
>>>> >> Caused by:
>>>> >> *java.net.UnknownHostException*: C
>>>> >>
>>>> >> at java.net.PlainSocketImpl.connect(Unknown Source)
>>>> >>
>>>> >> at java.net.Socket.connect(Unknown Source)
>>>> >>
>>>> >> at java.net.Socket.connect(Unknown Source)
>>>> >>
>>>> >> at sun.net.NetworkClient.doConnect(Unknown Source)
>>>> >>
>>>> >> at sun.net.NetworkClient.openServer(Unknown Source)
>>>> >>
>>>> >> at sun.net.ftp.FtpClient.openServer(Unknown Source)
>>>> >>
>>>> >> at sun.net.ftp.FtpClient.openServer(Unknown Source)
>>>> >>
>>>> >> at sun.net.www.protocol.ftp.FtpURLConnection.connect(Unknown Source)
>>>> >>
>>>> >> at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(Unknown
>>>> >> Source)
>>>> >>
>>>> >> at java.net.URL.openStream(Unknown Source)
>>>> >>
>>>> >> at
>>>> >>
>>>> com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(
>>>> >> *WSServletContextListener.java:108*)
>>>> >>
>>>> >> ... 9 more
>>>> >>
>>>> >> Aug 31, 2009 11:46:11 AM com.sun.grizzly.Controller start
>>>> >>
>>>> >> INFO: Starting Grizzly Framework 1.9.17-SNAPSHOT - Mon Aug 31
>>>> 11:46:11
>>>> >> MST
>>>> >> 2009
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> Thanks,
>>>> >>
>>>> >> TP
>>>> >>
>>>> >
>>>> >
>>>> http://www.nabble.com/file/p25265512/jaxws-fromjava.warjaxws-fromjava.war
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/Grizzly-with-JAX-WS-tp25228543p25265512.html
>>>> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>>
>>>>
>>>
>>
>
>
> --
>
> Vous pouvez me suivre sur Twitter / You can follow me on Twitter :
> http://twitter.com/survivant
>
>
--
View this message in context: http://www.nabble.com/Grizzly-with-JAX-WS-tp25228543p25320817.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.