date:20060325

Re: [Axis2][0.95][JDK1.4 and JDK 1.5] Still got security sample problems :)

2006-03-25 Thread Ruchith Fernando

Hi,

To ensure bouncycastle provider is picked up we insert it as the
second in the list of providers.
This done is each time the security handlers are invoked.

Can you please run the attached TestCipher.java snippet and verify the
above behaviour works in your _specific_ JDK version?
VERY IMPORTANT : Make sure you have bcprov-jdk13-131.jar in the classpath.

This is what I did to compile and run TestCipher.java from the same
dir that it is saved:

$ javac TestCipher.java

$ java -cp ~/.maven/repository/bouncycastle/jars/bcprov-jdk13-131.jar:.
TestCipher

Thanks,
Ruchith


On 3/26/06, Ali Sadik Kumlali <[EMAIL PROTECTED]> wrote:
> Hi Ruchith,
>
>  Thank you for your help. I want you to make sure that I didn't write my own
> code and only try to run the samples/security that comes with Axis2.
> Actually, I replaced it with the separately distributed sample listed in the
> site. I could not find a big difference other than a typo in service.xml,
> though.
>
>  Anyway, I re-checked my folder structure and build.xml according to your
> instructions, but could not find any difference. Moreover I tried followings
> with JDK 1.5:
>
>  1) Renamed c:\axis2\lib to c:\axis2\libx and ran the sample. As expected, I
>  got "c:\axis2\lib not found" ant error. Therefore, I made sure that
> build.xml is proper.
>
>  2) I did the same for c:\axis2\samples\security\lib folder and got the same
> error. Therefore, I made sure that build.xml is proper.
>
>  3) Put bcprov-jdk13-131.jar under c:\axis2\samples\security\lib and ran the
> sample. Got the "known error"[1].
>
>  4) Put bcprov-jdk13-131. jar under
> D:\programs\Java\jdk1.5.0_01\jre\lib\ext\ and ran the
> sample. Got the "known error"[1].
>
>  [1] known error:
>  
>
>  c:\axis2\samples\security>ant
>
>  Buildfile: build.xml
>
>  securitySample:
>   [java] org.apache.axis2.AxisFault: WSHandler: Encryption: error during
> mess
>  age processingorg.apache.ws.security.WSSecurityException:
> An unsupported signatu
>  re or encryption algorithm was used; nested exception is:
>   [java]
> org.apache.xml.security.encryption.XMLEncryptionException:
> Canno
>  t find any provider supporting AES/CBC/ISO10126Padding
>
>  [java] Original Exception was
> java.security.NoSuchAlgorithmException:
>  ...
>  
>
>  Thanks a lot.
>
>  Ali Sadik Kumlali
>
>
> Ruchith Fernando <[EMAIL PROTECTED]> wrote:
>
>  Hi,
>
> Seems like the bouncycastle.jar is not in the classpath of the client.
> This is the JCE provider we use instead of the default impl and it
> contains implementations of the required algorithms.
>
> Please check whether you have a directory named 'lib' within in the
> samples/security directory and it should contain bcprov-jdk13-131.jar
> file [1].
> Also please check whether the build.xml that you use has the following path
> def.
>
>
>
>
>
>
>
>
>
>
> And if those are available you can see that the ant build file
> properly loads all the jars in the 'lib' directory.
>
> Thanks,
> Ruchith
>
> [1] This directory also contains :
> commons-discovery-0.2.jar
> secUtil.jar
> wss4j-SNAPSHOT.jar
> xmlsec-1.2.1.jar
>
> On 3/25/06, Ali Sadik Kumlali wrote:
> > Dear all,
> >
> > Thanks to Axis2 team, 0.95 relase has finally announced on the site.
> >
> > Happily, there is an extra download for security sample which makes me
> feel
> > I finally get rid of security sample nightmare :)
> >
> > Unfortunately and surprisingly, I can't get security sample to work and
> > still get the same errors. I've listed all my journey with the new release
> > step by step.
> >
> > Hope, I'll somehow find a way to make it work :)
> >
> > Thanks,
> >
> > Ali Sadik Kumlali
> >
> >
> >
> ---
> > TRIALS WITH JDK 1.4
> >
> ---
> > Let's make sure the Java version:
> >
> > c:\axis2\samples\security>java -version
> > java version "1.4.2_02"
> > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_02-b03)
> > Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed mode)
> >
> > Let's run the sample:
> >
> > c:\axis2\samples\security>ant
> > Buildfile : build.xml
> >
> > securitySample:
> > [java] org.apache.axis2.AxisFault: WSHandler: Encryption: error during
> > mess
> > age processingorg.apache.ws.security.WSSecurityException:
> > An unsupported signatu
> > re or encryption algorithm was used; nested exception is:
> > [java]
> >
> org.apache.xml.security.encryption.XMLEncryptionException:
> & gt; Canno
>
> > t find any provider supporting AES/CBC/ISO10126Padding
> > < span style="font-family: courier;"> [java] Original Exception was
> > java.security.NoSuchAlgorithmException: Canno
> > t find any provider supporting AES/CBC/ISO10126Padding; nested exception
> > is:
> > [java]
> > org.apache.ws.security.WSSecurityException: WSHandler:
> > Encryptio
> > n: error during messa

[axis2 v0.95] wsdl2java stack overflow

2006-03-25 Thread Diego


Hi everybody,

using axis2 v0.95 wsdl2java I got a stack overflow exception with the 
following wsdl file.  The same wsdl file worked fine with all the 
previous axis and axis2 versions.


Thanks a lot for you help!

Diego

=
ant target
=

 
  
   
   
   
   
   
   
   
   
  
 

=
exception
=

wsdl2java-astrodas-peer:
 [java] Retrieving schema at 
'http://www.ivoa.net/xml/VOTable/v1.1', relative to 
'file:/Users/diego/Babylon/java/workspace/astrodas-test2/wsdl/'.

 [java] java.lang.StackOverflowError
 [java] at 
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:180)

 [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
 [java] at 
org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178)

 [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84)
 [java] at 
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)

 [java] at org.apache.tools.ant.Task.perform(Task.java:364)
 [java] at org.apache.tools.ant.Target.execute(Target.java:341)
 [java] at 
org.apache.tools.ant.Target.performTasks(Target.java:369)
 [java] at 
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
 [java] at 
org.apache.tools.ant.Project.executeTarget(Project.java:1185)
 [java] at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
 [java] at 
org.apache.tools.ant.Project.executeTargets(Project.java:1068)

 [java] at org.apache.tools.ant.Main.runBuild(Main.java:668)
 [java] at org.apache.tools.ant.Main.startAnt(Main.java:187)
 [java] at 
org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
 [java] at 
org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)

 [java] Caused by: java.lang.StackOverflowError
 [java] --- Nested Exception ---
 [java] java.lang.StackOverflowError

=
   wsdl file
=


http://astrodas.org/ws/peer";
xmlns:tns="http://astrodas.org/ws/peer";
   xmlns:tns1="http://astrodas.org/ws/model";
   xmlns:tns2="http://www.ivoa.net/xml/VOTable/v1.1";
   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>

 
  targetNamespace="http://astrodas.org/ws/model";>

   http://www.w3.org/2001/XMLSchema"; />
   http://www.ivoa.net/xml/VOTable/v1.1"; 
schemaLocation="http://www.ivoa.net/xml/VOTable/v1.1"; />

   
   
   

 type="xsd:integer" />
 type="xsd:integer" />
 type="xsd:string" />
 type="xsd:boolean" />


   
   

 type="xsd:integer" />
 type="xsd:string" />
 type="xsd:string" />
 type="xsd:string" />


   
   

 
  
   name="external-object" type="tns1:external-object" />
   type="xsd:string" />
   name="reliability" type="xsd:float" />
   type="xsd:double" />
  type="xsd:double" />

  
 

   
   

 
  name="mapping-annotation" type="tns1:mapping-annotation" />

 

   
   

 
  type="xsd:int" />

 

   
   
   

 
  type="xsd:string" />

 

   
   

 
  
 

   
  
 

 
 
  
 
 
  
 
 
 
  
 
 
  element="tns1:executeGlobalMappingTableQueryResponse" />

 

 
  
   Stores an array of annotations in the annotation 
backend database

   
   
  
  
   Executes a query on the global mapping table of 
the p2p network of annotation

   
   message="tns:executeGlobalMappingTableQueryResponseMessage" />

  
 

 
  http://schemas.xmlsoap.org/soap/http"; 
style="document" />

  
   
   

   
   

   
  
  
   
   

   
   

   
  
 

 
  
   location="http://localhost:8080/axis2/services/astrodas-peer"; />

RE: problem in accessing python Hello World Service

2006-03-25 Thread Kashif Saleem

Hi Anne,
Thanks for your response.I am attaching with this mail the HelloWorld 
Service and axis2 client.Its a simple HelloWorld service and I am using end 
point reference to access this service.There is no wsdl for it.

Kind Regards
Kashif Saleem


-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Sat 3/25/2006 3:45 PM
To: axis-user@ws.apache.org
Subject: Re: problem in accessing python Hello World Service
 
Please post the WSDL.

Based on the error messages, I'm guessing that the server is not expecting
the

http://example1.org/example1";>

element to appear in the message.

Anne

On 3/24/06, Kashif Saleem <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>I installed a ZSI 2.0_rc2  on machine geron045.ncl.ac.uk.I run the
> HelloWorld.py service on  the this machine i.e.
> http://geron045.ncl.ac.uk:8088/HelloWorld.py.This service has one
> operation called "HelloWorld" which accepts one argument and return this
> argument.
>
> Then from the another machine i.e "geron007.ncl.ac.uk" I tried to access
> this HelloWorld service which is deployed at
> http://geron045.ncl.ac.uk:8088/HelloWorld.py through AXIS2 client.I got
> the processed failure message.I monitor the soap messages going back and
> forth through TCPMON.The output for this is given below:
>
> Request:
>
> POST /HelloWorld.py HTTP/1.1
>
> User-Agent: Axis/2.0
>
> SOAPAction:
>
> Connection: Keep-Alive
>
> Host: geron045.ncl.ac.uk:8082
>
> Content-Length: 809
>
> Content-Type: text/xml; charset=UTF-8
>
>
> 
> http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";>
> http://schemas.xmlsoap.org/ws/2004/08/addressing";>
> http://localhost:8082/HelloWorld.pyhttp://schemas.xmlsoap.org/ws/2004/08/addressing";>
> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing
> ">0A2F12FAE0A1B8456E11432354035971
> 
> 
> http://example1.org/example1";>
> Axis2 Echo String 
> 
> 
> 
>
> Response:
>
> HTTP/1.0 500 Internal error
>
> Server: ZSI/1.1 BaseHTTP/0.3 Python/2.4.2
>
> Date: Fri, 24 Mar 2006 21:21:05 GMT
>
> Content-type: text/xml; charset="utf-8"
>
> Content-Length: 695
>
> http://schemas.xmlsoap.org/soap/encoding/"; xmlns:SOAP-ENV="
> http://schemas.xmlsoap.org/soap/envelope/"; xmlns:ZSI="
> http://www.zolera.com/schemas/ZSI/"; xmlns:xsd="
> http://www.w3.org/2001/XMLSchema"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance";>
> 
> 
> 
> 
> SOAP-ENV:Server
> 
> Processing Failure
> exceptions:TypeError
> Expecting typecode in result
> 
>
> /usr/lib/python2.4/site-packages/ZSI/dispatch.py:69:_Dispatch
> 
> 
> 
> 
>
> Just to clarify things further.I did one more thing,I removed the argument
> for the HelloWorld operation so now it is accepting no argument.And now
> when I tried to access the same service.I got the error  again.Bymonitoring 
> the soap messages going back and forth through
> TCPMON.This type the error changes to something else as given below:
>
>
> Request:
>
> POST /HelloWorld.py HTTP/1.1
>
> User-Agent: Axis/2.0
>
> SOAPAction:
>
> Connection: Keep-Alive
>
> Host: geron045.ncl.ac.uk:8082
>
> Content-Length: 740
>
> Content-Type: text/xml; charset=UTF-8
>
> 
> http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";>
> 
> http://schemas.xmlsoap.org/ws/2004/08/addressing";>
> http://localhost:8082/HelloWorld.py
> http://schemas.xmlsoap.org/ws/2004/08/addressing
> ">
> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing
> ">C1EB5D8FA2D3E2ABE811432360408471
> 
> 
> http://example1.org/example1"; />
> 
> 
>
>
> Response:
>
> HTTP/1.0 500 Internal error
>
> Server: ZSI/1.1 BaseHTTP/0.3 Python/2.4.2
>
> Date: Fri, 24 Mar 2006 21:31:42 GMT
>
> Content-type: text/xml; charset="utf-8"
>
> Content-Length: 708
>
>
> http://schemas.xmlsoap.org/soap/encoding/"; xmlns:SOAP-ENV="
> http://schemas.xmlsoap.org/soap/envelope/"; xmlns:ZSI="
> http://www.zolera.com/schemas/ZSI/"; xmlns:xsd="
> http://www.w3.org/2001/XMLSchema"; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance";>
> 
> 
> 
> 
> SOAP-ENV:Server
> Processing Failure
> 
> 
> exceptions:TypeError
> HelloWorld() takes no arguments (1 given)
> 
> /usr/lib/python2.4/site-packages/ZSI/dispatch.py:67:_Dispatch
> 
> 
> 
> 
> 
> 
>
>
> I am quite surprised by these errors.I am attaching with this mail my
> HelloWorld.py service and AXIS2 client code.I would appreciate if some guy
> would explain me the strange behavior of this simple scenario.
>
>
> Kind Regards
> Kashif Saleem
>
>
>
>
>
>





HelloWorld.py
Description: HelloWorld.py
/*
 * Copyright 2004,2005 The Apache Software Foundation.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *  http://www.apache.org/licenses/L

Re: [Axis2][0.95][JDK1.4 and JDK 1.5] Still got security sample problems :)

2006-03-25 Thread Ali Sadik Kumlali

Hi Ruchith,Thank you for your help. I want you to make sure that I didn't write my  own code and only try to run the samples/security that comes with  Axis2. Actually, I replaced it with the separately distributed sample  listed in the site. I could not find a big difference other than a typo  in service.xml, though.Anyway, I re-checked my folder structure and build.xml according to  your instructions, but could not find any difference. Moreover I tried  followings with JDK 1.5:1) Renamed c:\axis2\lib to c:\axis2\libx and ran the sample. As expected, I   got "c:\axis2\lib not found" ant error. Therefore, I made sure that build.xml is proper.2) I did the same for c:\axis2\samples\security\lib folder and got the  same error. Therefore, I made sure that build.xml is proper.3) Put bcprov-jdk13-131.jar under c:\axis2\samples\security\lib and ran the sample. Got the "known error"[1].4) Put bcprov-jdk13-131.
 jar
 under  D:\programs\Java\jdk1.5.0_01\jre\lib\ext\ and ran the sample. Got the "known error"[1].[1] known error:    c:\axis2\samples\security>ant  Buildfile: build.xmlsecuritySample:   [java] org.apache.axis2.AxisFault: WSHandler: Encryption: error during mess  age
 processingorg.apache.ws.security.WSSecurityException: An unsupported signatu  re or encryption algorithm was used; nested exception is:   [java] org.apache.xml.security.encryption.XMLEncryptionException: Canno  t find any provider supporting AES/CBC/ISO10126Padding   [java] Original Exception was java.security.NoSuchAlgorithmException:   ...  Thanks a lot.Ali Sadik Kumlali  Ruchith Fernando <[EMAIL PROTECTED]> wrote:  Hi,Seems like the bouncycastle.jar is not in the classpath of the client.This is the JCE provider we use instead of the default impl and itcontains implementations of the required algorithms.Please check whether you have a directory named 'lib' within in thesamples/security directory and it should contain bcprov-jdk13-131.jarfile [1].Also please check whether the build.xml that you use has the following path def.   
 And if those are available you can see that the ant build fileproperly loads all the jars in the 'lib' directory.Thanks,Ruchith[1] This directory also contains :commons-discovery-0.2.jarsecUtil.jarwss4j-SNAPSHOT.jarxmlsec-1.2.1.jarOn 3/25/06, Ali Sadik Kumlali  wrote:> Dear all,>>  Thanks to Axis2 team, 0.95 relase has finally announced on the site.>>  Happily, there is an extra download for security sample which makes me feel>  I finally get rid of security sample nightmare :)>>  Unfortunately and surprisingly, I can't get security sample to work and>  still get the same errors. I've listed all my journey with the new release>  step by step.>>  Hope, I'll somehow find a way to make it work :)>>  Thanks,>>  Ali Sadik Kumlali>>>
 --->  TRIALS WITH JDK 1.4> --->  Let's make sure the Java version:>>  c:\axis2\samples\security>java -version>  java version "1.4.2_02">  Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_02-b03)>  Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed mode)>>  Let's run the sample:>>  c:\axis2\samples\security>ant>  Buildfile : build.xml>>  securitySample:>   [java] org.apache.axis2.AxisFault: WSHandler: Encryption: error during> mess>  age processingorg.apache.ws.security.WSSecurityException:> An unsupported signatu>  re or encryption algorithm was used; nested exception is:>   [java]> org.apache.xml.security.encryption.XMLEncryptionException:&
 gt;
 Canno>  t find any provider supporting AES/CBC/ISO10126Padding>  < span style="font-family: courier;"> [java] Original Exception was> java.security.NoSuchAlgorithmException: Canno>  t find any provider supporting AES/CBC/ISO10126Padding; nested exception> is:>   [java]> org.apache.ws.security.WSSecurityException: WSHandler:> Encryptio>  n: error during message> processingorg.apache.ws.security.WSSecurityException: An>   unsupported signature or encryption algorithm was used; nested exception> is:>   [java]> org.apache.xml.security.encryption.XMLEncryptionEx ception:> Canno>  t find any provider supporting AES/CBC/ISO10126Padding>   [java] Original Exception was> java.security.NoSuchAlgorithmException: Canno>  t find any provider supporting AES/CBC/ISO10126Padding>   [java] at>
 org.apache.axis2.security.WSDoAllSender.invoke(WSDoAllSender.>  java:253)>>  ...>>> --->  TRIALS WITH JDK 1.5> --->  Let's make sure the Java version:>>  c:\axis2\samples\security>java -version>  java version "1.5.0_01">  Java(TM) 2 Runtime Envir

Re: [Axis2][0.95][JDK1.4 and JDK 1.5] Still got security sample problems :)

2006-03-25 Thread Ruchith Fernando

Hi,

Seems like the bouncycastle.jar is not in the classpath of the client.
This is the JCE provider we use instead of the default impl and it
contains implementations of the required algorithms.

Please check whether you have a directory named 'lib' within in the
samples/security directory and it should contain bcprov-jdk13-131.jar
file [1].
Also please check whether the build.xml that you use has the following path def.










And if those are available you can see that the ant build file
properly loads all the jars in the 'lib' directory.

Thanks,
Ruchith

[1] This directory also contains :
commons-discovery-0.2.jar
secUtil.jar
wss4j-SNAPSHOT.jar
xmlsec-1.2.1.jar

On 3/25/06, Ali Sadik Kumlali <[EMAIL PROTECTED]> wrote:
> Dear all,
>
>  Thanks to Axis2 team, 0.95 relase has finally announced on the site.
>
>  Happily, there is an extra download for security sample which makes me feel
>  I finally get rid of security sample nightmare :)
>
>  Unfortunately and surprisingly, I can't get security sample to work and
>  still get the same errors. I've listed all my journey with the new release
>  step by step.
>
>  Hope, I'll somehow find a way to make it work :)
>
>  Thanks,
>
>  Ali Sadik Kumlali
>
>
> ---
>  TRIALS WITH JDK 1.4
> ---
>  Let's make sure the Java version:
>
>  c:\axis2\samples\security>java -version
>  java version "1.4.2_02"
>  Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_02-b03)
>  Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed mode)
>
>  Let's run the sample:
>
>  c:\axis2\samples\security>ant
>  Buildfile : build.xml
>
>  securitySample:
>   [java] org.apache.axis2.AxisFault: WSHandler: Encryption: error during
> mess
>  age processingorg.apache.ws.security.WSSecurityException:
> An unsupported signatu
>  re or encryption algorithm was used; nested exception is:
>   [java]
> org.apache.xml.security.encryption.XMLEncryptionException:
> Canno
>  t find any provider supporting AES/CBC/ISO10126Padding
>  < span style="font-family: courier;"> [java] Original Exception was
> java.security.NoSuchAlgorithmException: Canno
>  t find any provider supporting AES/CBC/ISO10126Padding; nested exception
> is:
>   [java]
> org.apache.ws.security.WSSecurityException: WSHandler:
> Encryptio
>  n: error during message
> processingorg.apache.ws.security.WSSecurityException: An
>   unsupported signature or encryption algorithm was used; nested exception
> is:
>   [java]
> org.apache.xml.security.encryption.XMLEncryptionEx ception:
> Canno
>  t find any provider supporting AES/CBC/ISO10126Padding
>   [java] Original Exception was
> java.security.NoSuchAlgorithmException: Canno
>  t find any provider supporting AES/CBC/ISO10126Padding
>   [java] at
> org.apache.axis2.security.WSDoAllSender.invoke(WSDoAllSender.
>  java:253)
>
>  ...
>
>
> ---
>  TRIALS WITH JDK 1.5
> ---
>  Let's make sure the Java version:
>
>  c:\axis2\samples\security>java -version
>  java version "1.5.0_01"
>  Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
>  Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode)
>
>  Let's run the sample:
>
>  c:\axis2\samples\security>ant
>  Buildfile: build.xml
>
>  securitySample:
>   [java] Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apach
>  e/xpath/compiler/FuncLoader
>   [java] at
> org.apache.ws.security.WSSConfig.(WSSConfig.java:75)
>   [java] at
> org.apache.ws.security.WSSConfig.getNewInstance(WSSConfig.jav
>  a:98)
>   [java] at
> org.apache.ws.security.WSSConfig.(WSSConfig.java:48)
>   [java] at
> org.apache.ws.security.WSSecurityEngine.(WSSecurityEn
>  gine.java:51)
>  ...
>
>  I remembered Ruchith Fernando's advice related to JDK 1.5 & Xalan and
>  followed the link he gave:
>
> http://svn.apache.org/viewcvs.cgi/*checkout*/webservices/axis2/trunk/java/xdocs/faq.html.
>
>  Found an item mentioned to download xalan-2.7.0.jar. I downloaded it from:
>
>  http://www.apache.org/dist/java-repository/xalan/jars/
>
>  and put under c:\axis2\lib but got the same error. Searched in Google for
> org.apache.xpath.compiler.FuncLoader. What I found that the
> FuncLoader.class existed in xalan-2.6.0.jar not in xalan-2.7.0.jar.
>  Finally, downloaded xalan-2.6.0.jar and put under c:\axis2\lib. This time I
> got the same error found in JDK 1.4:
>
>  securitySample:
>   [java] org.apache.axis2.AxisFault: WSHandler: Encryption: error during
> mess
>  age processingorg.apache.ws.security.WSSecurityException:
> An unsupported signatu
>  re or encryption algorithm was used; nested exception is:
>   [jav

WG: Re: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2 in WSDL

2006-03-25 Thread Andreas Bobek

Hi Anne,

thank you for the specification.
I'm very interested in WSDL 1.1 to SOAP 1.2 binding. I need it to work 
with the Devices Profile (it's a MUST there).

I use axis-wsdl4j-1.2.jar (inside Axis2 libs). Does anybody know 
whether this is supporting 1.2 binding or 1.1 binding only?
Will 1.2 binding be supported in the final Axis2 release?

Thank you, Andreas.



- Originalnachricht -
Von: Anne Thomas Manes <[EMAIL PROTECTED]>
Datum: Samstag, März 25, 2006 5:11 pm
Betreff: Re: [Axis2-0.94] service deploy fails when ports bound to SOAP 
1.2 in WSDL
An: axis-user@ws.apache.org

> Axis supports SOAP 1.2, but perhaps the version of wsdl4j that 
> you're using
> doesn't.
> 
> FYI: Just found this new specification from IBM, Microsoft, 
> Oracle, and SAP:
> a formal definition of a SOAP 1.2 binding for WSDL 1.1:
> 
> http://www.oracle.com/technology/tech/webservices/pdf/WSDL11SOAP12.pdf
> 
> And also, a SOAP 1.1 binding for MTOM:
> 
> http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-
> soapbinding/ws-soap11.pdf
> 
> Anne
> 
> 
> On 3/24/06, Andreas Bobek <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > I have a WSDL file with a binding to SOAP 1.2 only, e.g. I use
> >
> > xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; instead of
> > xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/";
> >
> > Code generation works well.
> > Deploying with bindings to SOAP 1.1 works well, too.
> >
> > But when bind to SOAP 1.2 I get follow exception:
> >
> > org.apache.wsdl.impl.WSDLProcessingException: no port with soap 
> binding> found
> > at
> > org.apache.axis2.deployment.AxisServiceBuilder.getAxisService
> > (AxisServiceBui
> > lder.java:219)
> > at
> > org.apache.axis2.deployment.AxisServiceBuilder.getAxisService
> > (AxisServiceBui
> > lder.java:127)
> > at
> > 
> 
org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFil
e> (Ar
> > chiveReader.java:267)
> > at
> > 
> 
org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs> 
(Archi
> > veReader.java:333)
> > at
> > org.apache.axis2.deployment.DeploymentEngine.doDeploy(
> > DeploymentEngine.java:
> > 383)
> > ..
> >
> > which I think means WSDL-SOAP 1.2 is not known.
> >
> > Debugging inside AxisServiceBuilder:
> > javax.wsdl.extensions.UnknownExtensibilityElement
> > UnknownExtensibilityElement
> > ({http://schemas.xmlsoap.org/wsdl/soap12/}binding)
> >
> > Is this a limitation in Axis up to now?
> >
> > Thank you, Andreas Bobek.
> >
> >
>

Re: WSDL2WS for converting wsdl to c++ code

2006-03-25 Thread Anne Thomas Manes

You are trying to compile a WSDL that contains only message definitions. You need to compile the WSDL that contains the  element.AnneOn 3/23/06, 
Popuri, Monica <[EMAIL PROTECTED]> wrote:





 
Thanks for writing, attached is the wsdl and used xsd.
Regards


From: Anne Thomas Manes 
[mailto:[EMAIL PROTECTED]] Sent: Thursday, March 23, 2006 8:05 
PMTo: axis-user@ws.apache.orgSubject: Re: WSDL2WS for 
converting wsdl to c++ code
Can you post the WSDL?
On 3/23/06, Popuri, 
Monica <[EMAIL PROTECTED]> wrote:
Hi 
  All,I have a wsdl that uses my generated xsd and not standard xsd, 
  when Itry to convert the code to c++ using wsdl2ws utility in axis c++, I 
  getfollowing 
  error:C:\monica\axis\axis-c-1.6b-Win32-trace-src\lib\axis 
  >javaorg.apache.axis.wsdl.wsdl2ws.WSDL2Ws  -lc++ 
  -o.\outputc 
  -sserver"C:\monica\spec_parlay\parlayx_common_faults_2_0.wsdl"log4j:WARN 
  No appenders could be found for logger(org.apache.axis.i18n.ProjectR 
  esourceBundle).log4j:WARN Please initialize the log4j system 
  properly.org.apache.axis.wsdl.wsdl2ws.WrapperFault: the service does not 
  existsat 
  org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.getServiceEntry(Unknown 
  Source)at 
  org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.perprocess(UnknownSource)at 
  org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.generateWrappers(UnknownSource)at 
  org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.main (Unknown Source)Code 
  generation failed. Please see errors above.Please 
  assistRegards,Monica

Re: Axis does not supply correct namespace in SOAP message

2006-03-25 Thread Anne Thomas Manes

Just checking... but perhaps you have a typo in your WSDD? In your email you say the beanmapping says this: 
         
              xmlns:bedriftws="http://data.foo.bar.company"
qname="companyws:FoobarDO" 
              languageSpecificType="java:company.bar.foo.data.FoobarDO"/>but I think you want it to say this:
xmlns:bedriftws="http://data.foo.bar.company"
qname="bedriftws:FoobarDO"

languageSpecificType="java:company.bar.foo.data.FoobarDO"/>AnneOn 3/24/06, 
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Hi.
I have a WebService running on axis
and are trying to consume it from a .NET (C#) client, but all I get back
is NULL values.

I have search both this mailing list
and others and I can see that I am not the only one having this problem,
but I can't seem to find a real fix to the problem.
Some people says I should manually edit
the wsdl file and some mean I should manualy edit the .NET proxy, but I
don't like either solution sinse it fixes the
symptom not the real problem. 

The service takes a complex type and
an int as input and returns å complex type.
In the .wsdd file I have adden a beanMapping
that looks like this:

         
      
         
              xmlns:bedriftws="http://data.foo.bar.company"
         
              qname="companyws:FoobarDO"

         
              languageSpecificType="java:company.bar.foo.data.FoobarDO"
         
      />
which puts the type in the http://data.foo.bar.company

namespace. 
The default namespace is http://foo.bar.company

namespace.
The wsdl file is automatically generated
from axis like this: http://hostname/webapp/services/FoobarWS?wsdl

The schema definition of the returned
object in the wsdl looks like this: (The extension base i found in the
"http://framework.company"
namespace)

           
data.foo.bar.company"
xmlns="http://www.w3.org/2001/XMLSchema">   
           
   http://framework.company
"/>
  
           
   FoobarDO">
   
           
           
           
         
     
           
                
  
           
                   
  
           
                   
  
           
                

           
             
           
         
           
      

To me it looks like it's located in
the correkt namespace as defines in the beanMapping in the wsdd file.

The problem is that axis does not send
the response in the correkt namespace:
Eg. Soap response from axis:


   http://schemas.xmlsoap.org/soap/envelope/
"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
      
         foo.bar.company">
           

           
   
           
   Viskom testing testing testing
           

         
      
   

Here the .NET client clearly is trying
to find objects and values in the wrong namespace. The wsdl says it's in
http://data.foo.bar.company
and axis sends it in http://foo.bar.company

I have deployed the same app on a Websphere
server (without axis) and this works fine. The return message from Websphere
looks like this:


   http://schemas.xmlsoap.org/soap/envelope/
"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      
      
         
            
               data.foo.bar.company"/>
               data.foo.bar.company">Viskom
testing testing testing
            hentFoobarReturn>
         hentFoobarResponse
>
      
   

Here the correkt namespace is supplied
and the .NET client can read and deserialize it correctly.

So my question is:
        1)
Is this a bug in axis?
        2)
How to I go about fixing this?


Regards Alex

-- 
The content of this e-mail is intended solely for the use of the individual
or entity to whom it is addressed. If you have received this communication
in error, be aware that forwarding it, copying it or in any way disclosing
its content to  any other person, is strictly prohibited. If you have
received this communication in error, please notify the author by replying
to this e-mail immediately.This email has been scanned for the presence
of viruses!   http://www.storebrand.no

[Axis2][0.95][JDK1.4 and JDK 1.5] Still got security sample problems :)

2006-03-25 Thread Ali Sadik Kumlali

Dear all,Thanks to Axis2 team, 0.95 relase has finally announced on the site.Happily, there is an extra download for security sample which makes me feel  I finally get rid of security sample nightmare :)Unfortunately and surprisingly, I can't get security sample to work and   still get the same errors. I've listed all my journey with the new release   step by step.Hope, I'll somehow find a way to make it work :)Thanks,Ali Sadik Kumlali  ---  TRIALS WITH JDK 1.4  ---  Let's make sure the Java version:c:\axis2\samples\security>java -version  java version "1.4.2_02"  Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_02-b03)  Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed mode)Let's run the sample:c:\axis2\samples\security>ant  Buildfile
 :
 build.xmlsecuritySample:   [java] org.apache.axis2.AxisFault: WSHandler: Encryption: error during mess  age processingorg.apache.ws.security.WSSecurityException: An unsupported signatu  re or encryption algorithm was used; nested exception is:   [java] org.apache.xml.security.encryption.XMLEncryptionException: Canno  t find any provider supporting AES/CBC/ISO10126Padding  <
 span
 style="font-family: courier;"> [java] Original Exception was java.security.NoSuchAlgorithmException: Canno  t find any provider supporting AES/CBC/ISO10126Padding; nested exception is:   [java] org.apache.ws.security.WSSecurityException: WSHandler: Encryptio  n: error during message processingorg.apache.ws.security.WSSecurityException: An   unsupported signature or encryption algorithm was used; nested exception is:   [java] org.apache.xml.security.encryption.XMLEncryptionEx
 ception:
 Canno  t find any provider supporting AES/CBC/ISO10126Padding   [java] Original Exception was java.security.NoSuchAlgorithmException: Canno  t find any provider supporting AES/CBC/ISO10126Padding   [java] at org.apache.axis2.security.WSDoAllSender.invoke(WSDoAllSender.  java:253)...  ---  TRIALS WITH JDK 1.5  ---  Let's make sure the Java version:c:\axis2\samples\security>java -version  java version "1.5.0_01"  Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)  Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode)Let's run the sample:
 c:\axis2\samples\security>ant  Buildfile: build.xmlsecuritySample:   [java] Exception in thread "main" java.lang.NoClassDefFoundError: org/apach  e/xpath/compiler/FuncLoader   [java] at org.apache.ws.security.WSSConfig.(WSSConfig.java:75)   [java] at
 org.apache.ws.security.WSSConfig.getNewInstance(WSSConfig.jav  a:98)   [java] at org.apache.ws.security.WSSConfig.(WSSConfig.java:48)   [java] at org.apache.ws.security.WSSecurityEngine.(WSSecurityEn  gine.java:51)  ...I remembered Ruchith Fernando's advice related to JDK 1.5 & Xalan and   followed the link he gave: 
 http://svn.apache.org/viewcvs.cgi/*checkout*/webservices/axis2/trunk/java/xdocs/faq.html. Found an item mentioned to download xalan-2.7.0.jar. I downloaded it from:http://www.apache.org/dist/java-repository/xalan/jars/ and put under c:\axis2\lib but got the same error. Searched in Google for org.apache.xpath.compiler.FuncLoader. What I found that the FuncLoader.class existed in xalan-2.6.0.jar not in xalan-2.7.0.jar.   Finally, downloaded xalan-2.6.0.jar and put under c:\axis2\lib. This time I got the same error found in JDK 1.4:securitySample:   [java] org.apache.axis2.AxisFault: WSHandler: Encryption: error during mess  age processingorg.apache.ws.security.WSSecurityException: An unsupported signatu  re or encryption algorithm was used; nested exception is:   [java]
 org.apache.xml.security.encryption.XMLEncryptionException: Canno  t find any provider supporting AES/CBC/ISO10126Padding   [java] Original Exception was java.security.NoSuchAlgorithmException: Canno  t find any provider supporting AES/CBC/ISO10126Padding; nested exception is:   [java] org.apache.ws.security.WSSecurityException: WSHandler: Encryptio  n: error during message processingorg.apache.ws.security.WSSecurityException: An   unsupported signature or encryption algorithm was used; nested exception is:   [java] org.apache.xml.security.encryption.XMLEncryptionException: Canno  ...Again looked in FAQ and added security.provider.7=org.bouncycastle.jce.provider.BouncyCastleProviderline to  <
 br> 
 d:\programs\java\jre1.5.0_06\lib\security\java.security file. I made sure that java -version belonged to the java installation found under d:\programs\java\jre1.5.0_06. Therefore, I must had changed correc

Re: web-service String parameter encoding problem

2006-03-25 Thread Anne Thomas Manes

The embedded XML document must be escaped. That's why it looks funny.AnneOn 3/24/06, Anna Krajewska <[EMAIL PROTECTED]
> wrote:






Hi
 
I have a problem with String parameter encoding. I 
have a web-service that takes as a parameter java.lang.String which is 
serialized xml DOM document. This document has proper header:
 

 
but when I try to save my SOAPEnvelope with my 
own created BaseHandler:
 
Handler serviceHandler = 
msgContext.getService();MessageContext msgctx = 
msgContext.getCurrentContext();org.apache.axis.Message msg = 
msgctx.getCurrentMessage();
File file = new 
File("C:\\envelope.xml");FileOutputStream fos = new 
FileOutputStream(file);  msg.writeTo(fos);fos.flush();fos.close();
 
the whole SOAPEnvelope looks good but the xml 
document (String parameter) looks terrible. I don't know how to force axis to 
write that string for me also in UTF-8 encoding to the envelope - just as 
the whole envelope is encoded. Is it possible anyway?
 
HELP!
 
ania

Re: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2 in WSDL

2006-03-25 Thread Anne Thomas Manes

Axis supports SOAP 1.2, but perhaps the version of wsdl4j that you're using doesn't.FYI: Just found this new specification from IBM, Microsoft, Oracle, and SAP: a formal definition of a SOAP 1.2 binding for WSDL 1.1
:http://www.oracle.com/technology/tech/webservices/pdf/WSDL11SOAP12.pdfAnd also, a SOAP 1.1 binding for MTOM:
http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-soapbinding/ws-soap11.pdfAnneOn 3/24/06, Andreas Bobek <
[EMAIL PROTECTED]> wrote:Hi,I have a WSDL file with a binding to SOAP 
1.2 only, e.g. I usexmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" instead ofxmlns:soap11="
http://schemas.xmlsoap.org/wsdl/soap/"Code generation works well.Deploying with bindings to SOAP 1.1 works well, too.But when bind to SOAP 1.2 I get follow exception:org.apache.wsdl.impl.WSDLProcessingException
: no port with soap bindingfoundatorg.apache.axis2.deployment.AxisServiceBuilder.getAxisService(AxisServiceBuilder.java:219)atorg.apache.axis2.deployment.AxisServiceBuilder.getAxisService
(AxisServiceBuilder.java:127)atorg.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFile(ArchiveReader.java:267)atorg.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs
(ArchiveReader.java:333)atorg.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:383)..which I think means WSDL-SOAP 1.2 is not known.Debugging inside AxisServiceBuilder:
javax.wsdl.extensions.UnknownExtensibilityElementUnknownExtensibilityElement({http://schemas.xmlsoap.org/wsdl/soap12/}binding)Is this a limitation in Axis up to now?
Thank you, Andreas Bobek.

Re: problem in accessing python Hello World Service

2006-03-25 Thread Anne Thomas Manes

Please post the WSDL.Based on the error messages, I'm guessing that the server is not expecting the 
http://example1.org/example1">element to appear in the message. AnneOn 3/24/06, Kashif Saleem <
[EMAIL PROTECTED]> wrote:Hi all,   I installed a ZSI 2.0_rc2
  on machine geron045.ncl.ac.uk.I run the HelloWorld.py service on  the this machine i.e. http://geron045.ncl.ac.uk:8088/HelloWorld.py.This service has one operation called "HelloWorld" which accepts one argument and return this argument.
Then from the another machine i.e "geron007.ncl.ac.uk" I tried to access this HelloWorld service which is deployed at 
http://geron045.ncl.ac.uk:8088/HelloWorld.py through AXIS2 client.I got the processed failure message.I monitor the soap messages going back and forth through TCPMON.The output for this is given below:Request:
POST /HelloWorld.py HTTP/1.1User-Agent: Axis/2.0SOAPAction:Connection: Keep-AliveHost: geron045.ncl.ac.uk:8082Content-Length: 809
Content-Type: text/xml; charset=UTF-8http://schemas.xmlsoap.org/soap/envelope/
" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8082/HelloWorld.py
http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
http://schemas.xmlsoap.org/ws/2004/08/addressing">0A2F12FAE0A1B8456E11432354035971
http://example1.org/example1">Axis2 Echo String 
Response:HTTP/1.0 500 Internal errorServer: ZSI/1.1 BaseHTTP/0.3 Python/2.4.2Date: Fri, 24 Mar 2006 21:21:05 GMT
Content-type: text/xml; charset="utf-8"Content-Length: 695http://schemas.xmlsoap.org/soap/encoding/
" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ZSI="http://www.zolera.com/schemas/ZSI/
" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance
">SOAP-ENV:ServerProcessing Failure
exceptions:TypeErrorExpecting typecode in result/usr/lib/python2.4/site-packages/ZSI/dispatch.py:69:_Dispatch
Just to clarify things further.I did one more thing,I removed the argument for the HelloWorld operation so now it is accepting no 
argument.And now when I tried to access the same service.I got the error  again.By monitoring the soap messages going back and forth through TCPMON.This type the error changes to something else as given below:
Request:POST /HelloWorld.py HTTP/1.1User-Agent: Axis/2.0SOAPAction:Connection: Keep-AliveHost: geron045.ncl.ac.uk:8082Content-Length: 740
Content-Type: text/xml; charset=UTF-8http://schemas.xmlsoap.org/soap/envelope/
" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8082/HelloWorld.py
http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
http://schemas.xmlsoap.org/ws/2004/08/addressing">C1EB5D8FA2D3E2ABE811432360408471
http://example1.org/example1" />
Response:HTTP/1.0 500 Internal errorServer: ZSI/1.1 BaseHTTP/0.3 Python/2.4.2Date: Fri, 24 Mar 2006 21:31:42 GMTContent-type: text/xml; charset="utf-8"Content-Length: 708
http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/" xmlns:ZSI="http://www.zolera.com/schemas/ZSI/" xmlns:xsd="http://www.w3.org/2001/XMLSchema
" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
SOAP-ENV:ServerProcessing Failureexceptions:TypeErrorHelloWorld() takes no arguments (1 given)
/usr/lib/python2.4/site-packages/ZSI/dispatch.py:67:_Dispatch
I am quite surprised by these errors.I am attaching with this mail my HelloWorld.py service and AXIS2 client code.I would appreciate if some guy would explain me the strange behavior of this simple scenario.
Kind RegardsKashif Saleem

Re: the question about AIXS2 and AXIS1.3

2006-03-25 Thread SOA Work



In my opinion you should use axis2. axis2 is the future ;-)
I think especially for beginners axis2 is easier (for simple web services).

Although there are still arguments for axis.
- better documentation more tutorials (but axis2 is easier to deploy)
- if you want to use rpc/enc (should be avoided but is very useful sometimes)
- better integration with spring framework (only intresting if you use spring)

axis2 should be:
- easier
- better performance
- document centric web services

so long
Dominik

> -Ursprüngliche Nachricht-
> Von: axis-user@ws.apache.org
> Gesendet: 25.03.06 13:23:04
> An: "axis-user@ws.apache.org" 
> Betreff: the question about AIXS2 and AXIS1.3


> Hi,all
> 
> i am a new one learning webservice with AXIS1.3, but there are many 
> people talking about axis2. Now AIXS2 0.95 was released, and i want to know 
> at the time whether AXIS2 has implemented all the features in AIXS1.3 ?
> 
> 
> -
> 
> ·ÑžùÔ¬
> 
> 2006-03-25


__
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

the question about AIXS2 and AXIS1.3

2006-03-25 Thread 费根袁




Hi,all
    i am a new one 
learning webservice with AXIS1.3, but there are many people talking about 
axis2. Now AIXS2 0.95 was released, and i want to know at the time whether 
AXIS2 has implemented all the features in AIXS1.3 ?



费根袁
2006-03-25

Re: [Axis2][0.95][JDK1.4 and JDK 1.5] Still got security sample problems :)

[axis2 v0.95] wsdl2java stack overflow

RE: problem in accessing python Hello World Service

Re: [Axis2][0.95][JDK1.4 and JDK 1.5] Still got security sample problems :)

Re: [Axis2][0.95][JDK1.4 and JDK 1.5] Still got security sample problems :)

WG: Re: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2 in WSDL

Re: WSDL2WS for converting wsdl to c++ code

Re: Axis does not supply correct namespace in SOAP message

[Axis2][0.95][JDK1.4 and JDK 1.5] Still got security sample problems :)

Re: web-service String parameter encoding problem

Re: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2 in WSDL

Re: problem in accessing python Hello World Service

Re: the question about AIXS2 and AXIS1.3

the question about AIXS2 and AXIS1.3

14 matches

Site Navigation

Mail list logo

Footer information