0 Replies Latest reply on Mar 31, 2006 9:38 AM by Justin Babuscio

    Schema issue with Document-literal Web Service

    Justin Babuscio Newbie

      I have developed a web service that uses



      WSDL


      http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft
      -01.wsdl



      Schema


      http://docs.oasis-open.org/wsn/2004/06/wsn-WS-BaseNotification-1.2-draft
      -01.xsd



      These are taking directly from the Apache PubScribe project but altered for my purpose. I am developing a Publish-Subscribe type web service framework. I created JUnit client which uses the client side port. It creates a blank Subscribe message and then makes a call on the Server side subscribe port. It throws the exception



      {http://xml.apache.org/axis/}stackTrace:
      org.xml.sax.SAXException: Invalid element in com.jb.notificationproducer.Subscribe - ConsumerReference

      At
      org.jboss.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializ
      er.java:432)

      At
      org.jboss.axis.encoding.DeserializationContextImpl.startElement(Deserial
      izationContextImpl.java:1168)


      and then


      {http://xml.apache.org/axis/}stackTrace:
      org.xml.sax.SAXException: Invalid element in com.jb.notificationproducer.GetCurrentMessage - element

      At
      org.jboss.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializ
      er.java:432)

      At
      org.jboss.axis.encoding.DeserializationContextImpl.startElement(Deserial
      izationContextImpl.java:1168)



      Those are the exceptions thrown after trying make calls from the client side.


      I get the idea that the message is sent, and when compared on the server side to match the schema, it can't compare the complex types. I've read through forums about creating a ws4ee-deployment.xml to fix this but I'm not sure what I need to fix.

      Could somebody please help?

      Thanks