Re: JAX-WS webservice deployment
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Virtual Light wrote: > Were you working with the JAX-WS calculator example? That was one of two examples I messed with. One is the "default" service that you can build from MyEclipseIDE. - -- Peter L. Berghold Unix Professional [EMAIL PROTECTED] AIM: redcowdawg YIM: blue_cowdawg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFID1XdUM9/01RIhaARAjwFAJ4qr5cUNIeSOoorQUQ/y1H2BjVlUgCdF7qI LlT5fjTuB8ogpMYgzUUMOWc= =THX6 -END PGP SIGNATURE-
RE: JAX-WS webservice deployment
Not exactly. Were you working with the JAX-WS calculator example? This appears to be the standard example for this. I did not pull this one into eclipse and just built it with maven to look at what artifacts were generated and what was created upon deployment. > Date: Wed, 23 Apr 2008 09:42:05 -0400 > From: [EMAIL PROTECTED] > To: user@geronimo.apache.org > Subject: Re: JAX-WS webservice deployment > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Is there a "how to" out there somewhere that explains how this all > works? Reason I'm asking is I tried using a KISS example yesterday > from within the MyEclipseIDE development environment and it flat didn't > work. Since I'm sure there are obvious things I am missing I won't even > get into the error codes until I've seen more examples and have them > working. > > > - -- > Peter L. Berghold Unix Professional > [EMAIL PROTECTED] AIM: redcowdawg YIM: blue_cowdawg > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.5 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFIDzytUM9/01RIhaARAoABAJ4wKWgRHQxsEF4S4wqAQsHUCuCT7ACfZW6S > 4Va7GiE+JOWuSQKgA0Z810k= > =nSFw > -END PGP SIGNATURE-
Re: JAX-WS webservice deployment
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there a "how to" out there somewhere that explains how this all works? Reason I'm asking is I tried using a KISS example yesterday from within the MyEclipseIDE development environment and it flat didn't work. Since I'm sure there are obvious things I am missing I won't even get into the error codes until I've seen more examples and have them working. - -- Peter L. Berghold Unix Professional [EMAIL PROTECTED] AIM: redcowdawg YIM: blue_cowdawg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIDzytUM9/01RIhaARAoABAJ4wKWgRHQxsEF4S4wqAQsHUCuCT7ACfZW6S 4Va7GiE+JOWuSQKgA0Z810k= =nSFw -END PGP SIGNATURE-
RE: JAX-WS webservice deployment
Jarek, thanks for the response and confirmation of this. I had tried putting in the servlet tags for my service but as I said was getting errors so I was not certain if I needed to add them or if they were added for me during deployment. The errors that I was getting revolved around POJO deployment. That said I threw everything out and started again from scratch with a clean project and this time it appears that it does recognize the service as I can obtain the wsdl and can get the standard message when hitting the port. I am going to assume that my experimentation with deployment plans among other things caused some kind of corruption. Thanks again. Bill > Date: Tue, 22 Apr 2008 13:30:46 -0400 > From: [EMAIL PROTECTED] > To: user@geronimo.apache.org > Subject: Re: JAX-WS webservice deployment > > Yes, you need to add in the and entires > for your web service. What exceptions did you see? > > Jarek > > On Mon, Apr 21, 2008 at 3:23 PM, Virtual Light <[EMAIL PROTECTED]> wrote: > > > > I have a question about deploying JAX-WS webservices. I generated and > > deployed the simple sample jax-ws calculator and looked at what it had > > generated and what was deployed and in the simple case this will work fine. > > In my case I have a JAX-WS webservice for which I am supplying a web.xml > > file as I have entries for other servlets and parameters. In this case it > > does not appear that the web service is being deployed. Is it up to me in > > the case where I am supplying the web.xml file to make the servlet entries > > for the webservice? When I tried this I received various faults. I am > > using WebSphere CE which is Geronimo hard wired with tomcat. I did provide > > a geronimo deployment descriptor which is listed below along with the > > web.xml. The containing project is a Dynamic web project created in eclipse > > 3.3 Europa with a war file being the artifact. No EAR association. I have > > not been able to find anything definitive on what is needed. Any help > > appreciated. > > > > > > http://geronimo.apache.org/xml/ns/j2ee/web-1.1"; > > xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.1"; > > xmlns:sec="http://geronimo.apache.org/xml/ns/security-1.1"; > > xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.1";> > > > > > > default > > TestProfret1 > > 2.0 > > war > > > > > > /TestProfRet1 > > > > > > > > > > > > http://www.w3.org/2001/XMLSchema-instance"; > > xmlns="http://java.sun.com/xml/ns/javaee"; > > xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"; > > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee > > http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"; id="WebApp_ID" > > version="2.5"> > > TestProfRet1 > > > > > > EWSHttpMonServlet > > EWSHttpMonServlet > > > > com.elsevier.webservices.jws.ews.common.servlet.EWSHttpMonServlet > > > > applicationName > > Profile Retrieval Service > > > > > > initWebService > > true > > > > 2 > > > > > > > > > > ApplicationState > > ApplicationState > > > > > > com.elsevier.webservices.ews.common.servlet.ApplicationStateServlet > > > > > > > > WSTest > > WSTest > > > > > > com.elsevier.webservices.ews.common.servlet.WSTestServlet > > > > > > > > ApplicationState > > /admin/applicationState > > > > > > WSTest > > /test/* > > > > > > EWSHttpMonServlet > > /admin/httpmon > > > > > > > > index.html > > index.htm > > index.jsp > > default.html > > default.htm > > default.jsp > > > > > > > > SERVICE_CLASS > > java.lang.String > > > > com.elsevier.webservices.retrieval.profile.service.ProfileRetrievalService > > > > > > > > CONTEXT_CLASS > > java.lang.String > > > > com.elsevier.webservices.ews.common.context.EWSContext > > > > > > > > LOGGER_CHOICE > > java.lang.String > > > > com.elsevier.edit.common.logging.Logger > > > > > > > > IGNORE_HEADER > > java.lang.Boolean > > true > > > > > > > > INSTRUMENTATION_FACTORY > > java.lang.String > > > > com.elsevier.edit.common.instrumentation.Instrumentation > > > > > > > > > > com.lxnx.sysman.smapi.initializer.SysmanInitializerListener > > > > > >SmapiDebugLevel > >DEBUG > > > > > >SYSMAN_CONFIG_FILE > >/WEB-INF/SysmanConfig.xml > > > > > > index.html > > index.htm > > index.jsp > > default.html > > default.htm > > default.jsp > > > > > > > > Regards, > > Bill > >
Re: JAX-WS webservice deployment
Yes, you need to add in the and entires for your web service. What exceptions did you see? Jarek On Mon, Apr 21, 2008 at 3:23 PM, Virtual Light <[EMAIL PROTECTED]> wrote: > > I have a question about deploying JAX-WS webservices. I generated and > deployed the simple sample jax-ws calculator and looked at what it had > generated and what was deployed and in the simple case this will work fine. > In my case I have a JAX-WS webservice for which I am supplying a web.xml > file as I have entries for other servlets and parameters. In this case it > does not appear that the web service is being deployed. Is it up to me in > the case where I am supplying the web.xml file to make the servlet entries > for the webservice? When I tried this I received various faults. I am > using WebSphere CE which is Geronimo hard wired with tomcat. I did provide > a geronimo deployment descriptor which is listed below along with the > web.xml. The containing project is a Dynamic web project created in eclipse > 3.3 Europa with a war file being the artifact. No EAR association. I have > not been able to find anything definitive on what is needed. Any help > appreciated. > > > http://geronimo.apache.org/xml/ns/j2ee/web-1.1"; > xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.1"; > xmlns:sec="http://geronimo.apache.org/xml/ns/security-1.1"; > xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.1";> > > > default > TestProfret1 > 2.0 > war > > > /TestProfRet1 > > > > > > http://www.w3.org/2001/XMLSchema-instance"; > xmlns="http://java.sun.com/xml/ns/javaee"; > xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"; > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee > http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"; id="WebApp_ID" > version="2.5"> > TestProfRet1 > > > EWSHttpMonServlet > EWSHttpMonServlet > > com.elsevier.webservices.jws.ews.common.servlet.EWSHttpMonServlet > > applicationName > Profile Retrieval Service > > > initWebService > true > > 2 > > > > > ApplicationState > ApplicationState > > > com.elsevier.webservices.ews.common.servlet.ApplicationStateServlet > > > > WSTest > WSTest > > > com.elsevier.webservices.ews.common.servlet.WSTestServlet > > > > ApplicationState > /admin/applicationState > > > WSTest > /test/* > > > EWSHttpMonServlet > /admin/httpmon > > > > index.html > index.htm > index.jsp > default.html > default.htm > default.jsp > > > > SERVICE_CLASS > java.lang.String > > com.elsevier.webservices.retrieval.profile.service.ProfileRetrievalService > > > > CONTEXT_CLASS > java.lang.String > > com.elsevier.webservices.ews.common.context.EWSContext > > > > LOGGER_CHOICE > java.lang.String > > com.elsevier.edit.common.logging.Logger > > > > IGNORE_HEADER > java.lang.Boolean > true > > > > INSTRUMENTATION_FACTORY > java.lang.String > > com.elsevier.edit.common.instrumentation.Instrumentation > > > > > com.lxnx.sysman.smapi.initializer.SysmanInitializerListener > > >SmapiDebugLevel >DEBUG > > >SYSMAN_CONFIG_FILE >/WEB-INF/SysmanConfig.xml > > > index.html > index.htm > index.jsp > default.html > default.htm > default.jsp > > > > Regards, > Bill >
JAX-WS webservice deployment
I have a question about deploying JAX-WS webservices. I generated and deployed the simple sample jax-ws calculator and looked at what it had generated and what was deployed and in the simple case this will work fine. In my case I have a JAX-WS webservice for which I am supplying a web.xml file as I have entries for other servlets and parameters. In this case it does not appear that the web service is being deployed. Is it up to me in the case where I am supplying the web.xml file to make the servlet entries for the webservice? When I tried this I received various faults. I am using WebSphere CE which is Geronimo hard wired with tomcat. I did provide a geronimo deployment descriptor which is listed below along with the web.xml. The containing project is a Dynamic web project created in eclipse 3.3 Europa with a war file being the artifact. No EAR association. I have not been able to find anything definitive on what is needed. Any help appreciated. http://geronimo.apache.org/xml/ns/j2ee/web-1.1"; xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.1"; xmlns:sec="http://geronimo.apache.org/xml/ns/security-1.1"; xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.1";> default TestProfret1 2.0 war /TestProfRet1 http://www.w3.org/2001/XMLSchema-instance"; xmlns="http://java.sun.com/xml/ns/javaee"; xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"; xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"; id="WebApp_ID" version="2.5"> TestProfRet1 EWSHttpMonServlet EWSHttpMonServlet com.elsevier.webservices.jws.ews.common.servlet.EWSHttpMonServlet applicationName Profile Retrieval Service initWebService true 2 ApplicationState ApplicationState com.elsevier.webservices.ews.common.servlet.ApplicationStateServlet WSTest WSTest com.elsevier.webservices.ews.common.servlet.WSTestServlet ApplicationState /admin/applicationState WSTest /test/* EWSHttpMonServlet /admin/httpmon index.html index.htm index.jsp default.html default.htm default.jsp SERVICE_CLASS java.lang.String com.elsevier.webservices.retrieval.profile.service.ProfileRetrievalService CONTEXT_CLASS java.lang.String com.elsevier.webservices.ews.common.context.EWSContext LOGGER_CHOICE java.lang.String com.elsevier.edit.common.logging.Logger IGNORE_HEADER java.lang.Boolean true INSTRUMENTATION_FACTORY java.lang.String com.elsevier.edit.common.instrumentation.Instrumentation com.lxnx.sysman.smapi.initializer.SysmanInitializerListener SmapiDebugLevel DEBUG SYSMAN_CONFIG_FILE /WEB-INF/SysmanConfig.xml index.html index.htm index.jsp default.html default.htm default.jsp Regards, Bill