Hi Guys!

One more time about creation of web service operation File.

I have a wsdl file C:\a\MyIvrApp\activationservice.wsdl and during wso operation creation in OD I receive an error

!STACK 0
org.apache.axis.wsdl.toJava.DuplicateFileException: Duplicate file name: C:\AAOD6.0\workspace\TestWebService\WEB-INF\src\connectivity\ws\beans\xxx\WebServiceResponse.java.
Hint: you may have mapped two namespaces with elements of the same name to the same package name.
at org.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:110)
at org.apache.axis.wsdl.toJava.JavaBeanWriter.generate(JavaBeanWriter.java:1405)
at org.apache.axis.wsdl.toJava.JavaTypeWriter.generate(JavaTypeWriter.java:113)
at org.apache.axis.wsdl.toJava.JavaGeneratorFactory$Writers.generate(JavaGeneratorFactory.java:421)
at org.apache.axis.wsdl.gen.Parser.generateTypes(Parser.java:547)
at org.apache.axis.wsdl.gen.Parser.generate(Parser.java:432)
at org.apache.axis.wsdl.gen.Parser.access$000(Parser.java:45)
at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:362)
at java.lang.Thread.run(Unknown Source)

In the same time I see no error while run wsdl2java in the command line.
C:\Distr\axis-bin-1_4\axis-1_4\lib>"C:\Program Files (x86)\Java\jre7\bin\java" -Djavax.net.ssl.trustStore="C:\AAOD6.0\apache-tomcat-6.0.37\lib\trusted_weblm_certs.jks" -Djavax.net.ssl.trustStorePassword="password" -Djavax.net.ssl.keyStoreType="jks" -cp "C:\Distr\axis-bin-1_4\axis-1_4\lib\*" org.apache.axis.wsdl.WSDL2Java -D -v -p xxx.zzz.yyy2 C:\a\MyIvrApp\activationservice.wsdl > log111.txt

So, I started to dig and found the following information:
https://issues.apache.org/jira/browse/AXIS-2606

In the command line I use the following Apache Axis
Apache Axis version: 1.4
Built on Apr 22, 2006 (06:55:48 PDT)

The OD has version 6.0.0.1301

So, I have a feeling that I cannot set my own axis to be used in OD. That is why I consider the following solution:
1. Generate Client using command line.
2. Add generated java code to the some package in my project.
3. Create manually in text editor file wsop. The problem here is that I do not understand what is the special suffix, for example <endpoint value="EncryptPinInterface_1512569606125_WS_ENDPOINT"/>. How I can generate 1512569606125?

Is it possible?
Is there any other connections/relation which I can miss?

Thanks in advance for your help!

Why don't you try the Axis 2 connector?

Because on the customer side all wso are based on axis.

Probably I will ask a stupid question but do you think that it won't be any impact on server side if I switch to axis2 on a client side?

Is there any restrictions or any other changes I need to do in the IVR code?

You can try it. I have not tried it before but supposedly it should work (in theory) since you are sending SOAP over the wire.

Hi Ross,
Finally the root cause was found.
And it is the same as I already described/discussed in another thread https://www.devconnectprogram.com/forums/posts/list/30/20549.page#top
In my case wsdl was created in the way that it had mapped two namespaces with elements of the same name to the same package name


Finally the wsdl was refactored to avoid this problem and web service itself was refactored.

Also, next development cycle I will definitely try axis2 connector. Do we have an example in applications examples with axis2 usage?

And I wanted to ask regarding axis version in OD: what axis version is used in latest version of OD?

OD supports Axis 1.4 and Axis2 1.6.2

Hi Ross,

Just to avoid misunderstanding...
So, do I correctly understand that
1. Avaya Aura® OD 6.0.0.1301 supports Apache Axis 1.4 and Apache Axis2 1.5
2. Avaya Aura® OD 7.2 supports Apache Axis 1.4 and Apache Axis2 1.6.2

yes.

Hi Ross,

Axis2 wso client part could be generated without any problem, but current IVR code tightly coupled with axis1 generated client and customer decided to restructure the wsdl.

But I think that I will try axis2 connector in the future projects.

Once again thanks a lot for recommendations and help in this question.