Issues invoking webservice hosted on Aqualogic Proxy service.

Question

Hi,
This is my first "Hello world..." forum experience.
I'm facing problems while invoking webservice hosted on Aqualogic Proxy Service in my local machine;
I'm using Weblogic 10 (Oracle Service Bus 10gR3 ).
1) I've used weblogic's "weblogic.wsee.tools.anttasks.ClientGenTask" to generate java code from wsdl file
2) Created a stand-alone client
code fragment :
try{
ServiceActivationNoticationService notificationService = new ServiceActivationNoticationService_Impl("http://localhost:7001/ServiceActivationInterface/FroxyServices/ServiceNotification".concat("?WSDL"));
ServiceActivationNoticationPortType notificationServicePortType = notificationService.getServiceNotification();
Empty response = ((ServiceActivationNoticationPortType_Stub)notificationServicePortType).serviceNotification(notification);
catch(){
System.err.println(ex.toString());
logger.debug("Service Notification Exception...", ex);
throw new Exception("Service Notification Exception...", ex);
Comiling successfully but when I run I'm getting the follwing exceptions:
Caused by: java.lang.NullPointerException
     at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType$ElementQNameProperty.access$000(ByNameRuntimeBindingType.java:314)
     at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.getMatchingElementProperty(ByNameRuntimeBindingType.java:253)
     at com.bea.staxb.runtime.internal.ByNameUnmarshaller.findMatchingElementProperty(ByNameUnmarshaller.java:71)
     at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:43)
     at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshal(AttributeUnmarshaller.java:38)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:174)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalType(UnmarshalResult.java:212)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalElement(UnmarshalResult.java:227)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshalElement(UnmarshallerImpl.java:166)
     at weblogic.wsee.bind.runtime.internal.LiteralDeserializerContext.unmarshalElement(LiteralDeserializerContext.java:87)
     at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeElement(BaseDeserializerContext.java:180)
     at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeElement(BaseDeserializerContext.java:115)
     at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:490)
     at weblogic.wsee.codec.soap11.SoapDecoder.decodeReturn(SoapDecoder.java:400)
     at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:170)
     at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:121)
     at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:175)
     at weblogic.wsee.ws.dispatch.client.CodecHandler.decodeOutput(CodecHandler.java:126)
     at weblogic.wsee.ws.dispatch.client.CodecHandler.decode(CodecHandler.java:103)
     at weblogic.wsee.ws.dispatch.client.CodecHandler.handleResponse(CodecHandler.java:80)
     at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:236)
     at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:220)
     at weblogic.wsee.ws.dispatch.client.ClientDispatcher.handleResponse(ClientDispatcher.java:159)
     at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:114)
     at weblogic.wsee.ws.WsStub.invoke(WsStub.java:89)
     at weblogic.wsee.jaxrpc.StubImpl._invoke(StubImpl.java:331)
     ... 3 more
But If I create a soap message manully and invoke the same webservice, it works fine.
Please reply soon....
Thanks in Advance.

Answer 1

Hi James,
Thanks for your reply, and directing me to appropriate threads.
The problem is with one of wsdl element.
My requirement is an empty element:
so I've created
<element name="empty">
<xsd:complexType>
<xsd:sequence/>
</xsd:complexType>
</element>
when I use this element for output type as below...
<wsdl:input message="service" type="xxx:service"/>
<wsdl:output message="emptyResponse" type="xxx:empty"/>
weblogic clientgen code is able invoke service successfully but the response is causing problem.
But when I changed empty element to
<element name="empty">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="abcd" type="xsd:string" minOccurs="0"/> I'll not use this at all.
</xsd:sequence>
</xsd:complexType>
</element>
Everything is working fine now in this case. ************************************************************************
But I'm not sure what's wrong with
<element name="empty">
<xsd:complexType>
<xsd:sequence/>
</xsd:complexType>
</element> because specifications says this is the way to define an empty element type.
What's wrong with this....
Thanks.... to Hello world! Response....