Win a copy of Java EE 8 High Performance this week in the Java/Jakarta EE forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Axis 1.4: not doing correct beanmapping on deployment wsdl  RSS feed

Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I'm using Axis 1.4 in java. When I create the deployment document I specified the beanmappings I want axis to published in the wsdl [1]. But when generating the wsdl they are not included as <complexType>, and just putting the classes that are directly referenced in the treatmentStageWS class.
I want to explicitly add other classes to the beanmapping because I have inheritance, and the childs are not being include automatically in the wsdl (what is logic).


<deployment xmlns="" xmlns:java="">
<service name = "treatmentStageWS" style="wrapped" use="literal" provider = "java:RPC">
<parameter name = "allowedMethods" value = "getTreatmentStage,getLastTreatmentStage"/>
<parameter name = "className" value=""/>
<parameter name="scope" value="Application"/>
<parameter name="wsdlTargetNamespace" value="http://localhost:8080/axis/services/treatmentStageWS"/>
<parameter name="namespaceUri" value="http://localhost:8080/axis/services/treatmentStageWS"/>
<parameter name="wsdlDocumentUrl" value="http://localhost:8080/axis/services/treatmentStageWS"/>

<beanMapping qname="ns2:KitForm" xmlns:ns2="treatmentStageWS" languageSpecificType="java:forms.KitForm"/>
<beanMapping qname="ns3:KitFormExtension" xmlns:ns3="treatmentStageWS" languageSpecificType="java:forms.KitFormExtension"/>

So in the wsdl deployed is just being included KitForm and not its child KitFormExtension.

Any idea for solving this problem?

Thanks in advance,
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!