When you use MessageBinding, service method signature should looks
like described here :
http://xfire.codehaus.org/Message+Binding


On 6/29/07, Arian Rodrigo Pasquali <[EMAIL PROTECTED]> wrote:




I´m trying to deploy a web service with message style, but it's not working
for me.

I fallow what is described at user guide
(http://xfire.codehaus.org/Message+Binding), but when I use
MessageBindingProvider xfire throws a NullPointerException when I register
my service.

  ObjectServiceFactory factory = new ObjectServiceFactory(new
MessageBindingProvider());
factory.setStyle("message");




//here xfire throws an exception when I try to register the service if it
uses MessageBindingProvider.

getController().getServiceRegistry().register(service);



Am I supposed to declare a service.xml??

I can´t use service.xml because I´d like to deploy dynamic web services.
With document, rpc and wrapped style it's pretty easy, but message style
doesn´t use the default BindingProvider, right?

Is it possible with message style???



stacktrace:

17:32:18,359 DEBUG [XFireSOAPServlet] Register the service in the
ServiceRegistry

17:32:18,749 ERROR [XFireServletController] Couldn't invoke servlet request.

java.lang.NullPointerException

        at
org.codehaus.xfire.wsdl11.builder.WSDLBuilder.writeParameters(WSDLBuilder.java:567)

        at
org.codehaus.xfire.wsdl11.builder.WSDLBuilder.createInputParts(WSDLBuilder.java:548)

        at
org.codehaus.xfire.wsdl11.builder.WSDLBuilder.createInputMessage(WSDLBuilder.java:373)

        at
org.codehaus.xfire.wsdl11.builder.WSDLBuilder.createAbstractInterface(WSDLBuilder.java:234)

        at
org.codehaus.xfire.wsdl11.builder.WSDLBuilder.write(WSDLBuilder.java:161)

        at
org.codehaus.xfire.wsdl11.builder.WSDLBuilderAdapter.write(WSDLBuilderAdapter.java:40)

        at
org.codehaus.xfire.DefaultXFire.generateWSDL(DefaultXFire.java:104)

        at
org.codehaus.xfire.transport.http.XFireServletController.generateWSDL(XFireServletController.java:380)

        at
org.codehaus.xfire.transport.http.XFireServletController.doService(XFireServletController.java:125)

        at
org.codehaus.xfire.transport.http.XFireServlet.doGet(XFireServlet.java:107)

        at
javax.servlet.http.HttpServlet.service(HttpServlet.java:595)

        at
javax.servlet.http.HttpServlet.service(HttpServlet.java:688)

        at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)

        at
org.mortbay.jetty.servlet.ServletHandler.dispatch(ServletHandler.java:666)

        at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)

        at
org.mortbay.http.HttpContext.handle(HttpContext.java:1530)

        at
org.mortbay.http.HttpContext.handle(HttpContext.java:1482)

        at
org.mortbay.http.HttpServer.service(HttpServer.java:909)

        at
org.mortbay.http.HttpConnection.service(HttpConnection.java:816)

        at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982)

        at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:833)

        at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)

        at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)





my service class looks like this: public class MyService {
  public String test(String param) {
    // test
    return "ok";
  }
}


Do anyone have any idea what´s wrong?




 Arian Rodrigo Pasquali
 Célula Colaboração - Desenvolvimento
 [EMAIL PROTECTED]
 Tel. +55 (47) 3802-8446
 www.neogrid.com




--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.

---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to