AW: Abstract classes and inheritance

Knötzinger Markus Tue, 06 Dec 2005 04:49:13 -0800

Title: Abstract classes and inheritance

Ok,

finally I solved this issue.

First I want to mention that I'm using Axis 1.2.1

The major problem was, that while creating the stub, the inheriting class had not been produced.

(It was there, but only because I have two services in the same stub (or two stubs in the same package) and it was produced by the other one, which I haven't used, yet. That's why I didn't recognize the problem.)

But there was definiteley no entry in the XXXSoapBindingStub.java, so the stub didn't know the class.

On the other hand, the abstract class had been produced.

So why did that happen?

I found out the following:

In the service I did not use the the inheriting class in a method and I only used the abstract one as an array, like:

Message[] getMessage()

In this case, the inheriting class is not generated. It's different if you mention the abstract class somewhere in the service like this:

Message getMessage()

Then the inheriting class will be generated, too, and there will definiteley be an entry in the XXXSoapBindingStub.java

Now everything works fine! :-)

Well, I'm a newbie in Webservices and maybe I did something wrong that's supposed to be very simple,

but perhaps this helps other novices not to fall into the same trap.

Markus

-----Ursprüngliche Nachricht-----
Von: Knötzinger Markus [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 1. Dezember 2005 10:30
An: '[email protected]'
Betreff: AW: Abstract classes and inheritance

Hi,

I'm sorry, I have not got the hang of it, yet.

Markus

-----Ursprüngliche Nachricht-----
Von: Ales St [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 1. Dezember 2005 10:24
An: [email protected]
Betreff: Re: Abstract classes and inheritance

Hi,

do you solved your problem? Because I have got a similar problem, and I don't know how to solve it. If you selve it, write me please.

Thank you

                Ales

----- Original Message -----

From: Knötzinger Markus

To: '[email protected]'

Sent: Wednesday, November 30, 2005 4:05 PM

Subject: Abstract classes and inheritance

Hello everyone,

I got stuck with a problem concerning abstract classes.
I've got an abstract class called 'Message' and a concrete one called 'DefaultMessage' which does inherit 'Message'.
I've got a method getMessages() of return type Message[].
On the server implementation the method returns an array of type 'Message', but each member references to an instance of 'DefaultMessage'.

On the client side I get an array with proper length but null values. If I do not declare 'Message' as abstract it works only if 'DefaultMessage' does not contain any bean members.

The 'stubt version' of getMessages() returns instances of 'Message', not of 'DefaultMessage' which should be the case.
If I add a bean member (like 'defaultValue') to 'DefaultMessage' I get an Exception from the stub:

org.xml.sax.SAXException: Invalid element in test.messenger.service.Message - defaultValue

org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
org.apache.axis.client.Call.invoke(Call.java:2451)
org.apache.axis.client.Call.invoke(Call.java:2347)
org.apache.axis.client.Call.invoke(Call.java:1804)
test.messenger.service.MessengerUserSoapBindingStub.getActiveMessages(MessengerUserSoapBindingStub.java:362)
test.messenger.gui.model.ServiceManager.getNewMessages(ServiceManager.java:57)
....

The SOAP message looks ok.
It contains 'defaultValue' and defines the array elements as 'DefaultMessage'.

Any ideas?

Thanks a lot,
Markus

Here's my wsdd:

<service name="MessengerUser" provider="java:RPC" >
     
      <requestFlow>
        <handler type="soapmonitor"/>
      </requestFlow>

      <responseFlow>
        <handler type="soapmonitor"/>
      </responseFlow>

      <parameter name="className"           value="test.messenger.service.MessageUserService"/>
      <parameter name="wsdlPortType"        value="MessengerUser"/>
      <parameter name="allowedMethods"      value="*"/>
      <parameter name="scope"               value="Application"/>
      <parameter name="wsdlTargetNamespace" value="http://service.messenger.test"/>

      
      <beanMapping qname="myNS:Message"
                   xmlns:myNS="http://messenger.test"
                   languageSpecificType="java:test.messenger.Message"/>
      <beanMapping qname="myNS:Response"
                   xmlns:myNS="http://messenger.test"
                   languageSpecificType="java:test.messenger.Response"/>
      <beanMapping qname="myNS:DefaultMessage"
                   xmlns:myNS="http://messenger.test"
                   languageSpecificType="javatest.messenger.DefaultMessage"/>
      <beanMapping qname="myNS:DefaultResponse"
                   xmlns:myNS="http://messenger.test"
                   languageSpecificType="java:test.messenger.DefaultResponse"/>

      
      <beanMapping qname="myNS:MessengerException"
                   xmlns:myNS="http://messenger.test"
                   languageSpecificType="java:test.MessengerException"/>
      <beanMapping qname="myNS:MessageNotExistsException"
                   xmlns:myNS="http://messenger.test"
                   languageSpecificType="java:test.messenger.MessageNotExistsException"/>

</service>

</deployment>

###########################################

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/

###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/

AW: Abstract classes and inheritance

Reply via email to