Hi Amila,
the complexType look's like this
<xsd:complexType name="customer">
<xsd:sequence>
<xsd:element name="customerID">
<xsd:simpleType>
<xsd:restriction base="xsd:token">
<xsd:minLength value="7"/>
<xsd:maxLength value="7"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
for the element customerID wsdl2java generates two classes
CustomerId_type0 and CustomerId_type1, both classes
look like the same expecting _type1 and _type0.
Is there a possibility to avoid this?
Is there a design-pattern or something else to handle wsdl-Files with
more then one port defined?
I have to build a webservice from a given wsdl-file (3 port) with a lot
of complex types, all 3 ports should
be reachable throw one service
http://localhost:8080/customer/services/Port1
http://localhost:8080/customer/services/Port2
http://localhost:8080/customer/services/Port3
in the old axis 1.4 this was possible, is this feature not longer
supported in axis2?
Thank you, Alex
Amila Suriarachchi schrieb:
On Mon, Jan 18, 2010 at 7:07 PM, Alex <[email protected]
<mailto:[email protected]>> wrote:
hi there,
Does axis2 V1.5.1 supports multiple ports from one wsdl-file like
the old axis 1.4?
No. One service can have only one porttype. if you have multiple port
types you need to have multiple ports.
During generating code with wsdl2java-tool only one port is
produced, but I need
all three ports in my service (the -g or -pn dosent' help).
Is there another solution to solve this problem.
Does axis2 V1.5.1 support receiving and sending SWA in DIME-Format?
I am not sure but certainly it supports SWA.
Why does wsdl2java-tool generates multiple java-classes for one
and the same xml-complex-type (adb Databinding)?
is this an anonymous complex type? for named complex types it
generates only one.
thanks,
Amila.
Thank you, Alex
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
