AW: [JBoss-user] Remote Beans as Web Services

[Jung , Dr. Christoph]

Title: Nachricht

how did you deploy the service. through a wsr archive ?   How do you access the service? Through the AdminServlet?   unfortunately, the code seems to have changed such that I cannot exactly locate the line.    Do you run a 3.2 instance? That is my best guess and then, it is a problem of the adminservlet generating a correct msgContext for the  provider ... Have you tried asking the service for wsdl. Have you tried to hit the service immediately? In these cases, correct msgContexts should be provided.   CGJ    -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 13. März 2003 17:05 An: [EMAIL PROTECTED] Betreff: RE: [JBoss-user] Remote Beans as Web Services Sorry the stack trace looks like this. I'm not sure if the '*' is the problem as the tutorial works for a local version of the bean i.e. localhome and localInterface. I just made the bean remote.   16:04:32,481 ERROR [Engine] StandardWrapperValve[JBossAxisServlet]: Servlet.service() for servlet JBossAxisServlet threw exception java.lang.NullPointerException                 at org.jboss.net.axis.server.EJBProvider.getServiceClass(EJBProvider.java:162)                 at org.apache.axis.providers.java.JavaProvider.initServiceDesc(JavaProvider.java:535)                 at org.apache.axis.handlers.soap.SOAPService.getInitializedServiceDesc(SOAPService.java:322)                 at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:477)                 at org.apache.axis.deployment.wsdd.WSDDDeployment.getDeployedServices(WSDDDeployment.java:566)                 at org.apache.axis.configuration.FileProvider.getDeployedServices(FileProvider.java:322)                 at org.apache.axis.transport.http.AxisServlet.reportAvailableServices(AxisServlet.java:584)                 at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:256)                 at javax.servlet.http.HttpServlet.service(HttpServlet..java:740)                 at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:335)                 at javax.servlet.http.HttpServlet.service(HttpServlet..java:853)                 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)                 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)                 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)                 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)                 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)                 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)                 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)                 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)                 at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:531)                 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)                 at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)                 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)                 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)                 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)                 at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)                 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)                 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)                 at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)                 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)                 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)                 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)                 at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)                 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)                 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)                 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)                 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)                 at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)                 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)                 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)                 at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027)                 at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125)                 at java.lang.Thread.run(Thread.java:536)   Thanks, Mark.   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jung , Dr. Christoph Sent: 13 March 2003 14:26 To: '[EMAIL PROTECTED]' Subject: AW: [JBoss-user] Remote Beans as Web Services     -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 13. März 2003 13:39 An: [EMAIL PROTECTED] Betreff: [JBoss-user] Remote Beans as Web Services   Basically the EJBProvider class throws a null pointer exception.   when? where?   Asmentioned in several mails, the allowedMethods="*" can lead to exposing some of the non-business EJB methods which are non-WS-compliant. This leads to problems when trying to access WSDL.             ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/