date:20060326

[Axis2] Mime implementation for MTOM support

2006-03-26 Thread Kapila Dissanayake

Hi All,
 I implemented the MIME related sources in attachment folder. 
 Please review and commit.
Thanks and regards,
Kapila


attachments.tar.gz
Description: GNU Zip compressed data

Re: [Axis2] MTOM related changes for OM

2006-03-26 Thread Samisa Abeysinghe


Many thanks for the patch.
I applied the patch to svn, though this is not complete, so that we do 
not run into problems cuased due to regression.

Hope we could complete the rest soon :)

Samisa...

Kapila Dissanayake wrote:


Hi All,
I have done some changes to OM that is required to support MTOM.
Though this is not complete, it is in a compiling stage. The mime 
library related integration remains a TODO, and I am working on it. 
Still, it may be worth reviewing and commiting this code in.


Thanks and regards,
Kapila

On 3/26/06, *Kapila Dissanayake* [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED] wrote:


Hi All,
I implemented the MIME related sources in attachment folder.
Please review and commit.
Thanks and regards,
Kapila

Re: [Axis2] MTOM related changes for OM

2006-03-26 Thread Sahan Gamage

Hi Kapila,

Thanks for the patches.
Please send pathches to dev list. axis-c-dev@ws.apache.org

- Sahan


Samisa Abeysinghe wrote:

 Many thanks for the patch.
 I applied the patch to svn, though this is not complete, so that we do
 not run into problems cuased due to regression.
 Hope we could complete the rest soon :)

 Samisa...

 Kapila Dissanayake wrote:

 Hi All,
 I have done some changes to OM that is required to support MTOM.
 Though this is not complete, it is in a compiling stage. The mime
 library related integration remains a TODO, and I am working on it.
 Still, it may be worth reviewing and commiting this code in.

 Thanks and regards,
 Kapila

 On 3/26/06, *Kapila Dissanayake* [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED] wrote:

 Hi All,
 I implemented the MIME related sources in attachment folder.
 Please review and commit.
 Thanks and regards,
 Kapila

Failed to call delayed quotes sample web service by Axis C++ and VC 6

2006-03-26 Thread Bo Xie

Hi,

I tried to build SOAP C++ Windows Client to call delayed quotes web
service, but failed. Following are steps:
1. Generate .hpp/.cpp
--
E:\temp\TestAxisjava -classpath .\wsdl2ws.jar;.\commons-logging.jar;.\jaxrpc.ja
r;.\saaj.jar;.\wsdl4j.jar;.\wsdl2ws.jar;.\axis.jar;.\commons-discovery.jar
org.apache.axis.wsdl.wsdl2ws.WSDL2Ws
http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl
-lc++ -sclient

Code generation completed.
--
2.  TestAxis.cpp
--
#include stdafx.h
#include StockQuotePortType.hpp

int main(int argc, char* argv[])
{
   StockQuotePortType s;
   float f=s.getQuote(IBM);
   printf(The quote is %f\n,f);
   return 0;
}
--

3. When I debug the TestAxis project, it will throw an exception
Unhandled exception in TestAxis.exe: 0xC005: Access Violation in
Line 62 of StockQuotePortType.cpp
--Line 62--
if( AXIS_SUCCESS == m_pCall-checkMessage(
getQuoteResponse1,http://www.themindelectric.com/wsdl/net.xmethods.services.stockquote.StockQuote/;))
-

If you want the TestAxis VC project, please let me know.

Any suggestions are welcome and appreciated!

Best Regards,

Xie, Bo

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

2006-03-26 Thread Ali Sadik Kumlali

Hi Ruchith,I ran TestChiper and got SunJCE as output. Then changed my java.security file as following:security.provider.1=sun.security.provider.Sun  security.provider.2=org.bouncycastle.jce.provider.BouncyCastleProvider  security.provider.3=sun.security.rsa.SunRsaSign  security.provider.4=com.sun.net.ssl.internal.ssl.Provider  security.provider.5=com.sun.crypto.provider.SunJCE  security.provider.6=sun.security.jgss.SunProvider  security.provider.7=com.sun.security.sasl.ProviderAnd ran again. This time I got BC. With this configuration I ran securitySample and got the same error. To print all the settings, I changed build.xml as following:project name="sample
 s"
 default="securitySample"   path id="axis.classpath"   fileset dir="../../lib"   include name="*.jar"/   /fileset   fileset dir="lib"   include name="*.jar"/   /fileset   /path   property name="axis.classpath.prop" refid="axis.classpath"/   target name="securitySample"   echo message="[java.version]: ${java.version}" /   echo message="[java.home]: ${java.home}" / 
  echo  message="[java.class.path]:"  /echo-/echo   echo message="${java.class.path}" /   echo-/echo   echo message="[axis.classpath]:" /   echo-/echo   echo message="${axis.classpath.prop}" /   echo-/echo   java  classname="sample.security.C
 lient"
 classpathref="axis.classpath"  fork="true"   arg value="client_repo"/   arg value="8080"/   /java   /target  /projectIt gave me following output:c:\axis2\samples\securityant  Buildfile: build.xmlsecuritySample:   [echo] [java.version]: 1.5.0_01   [echo] [java.home]: D:\programs\Java\jdk1.5.0_01\jre   [echo] [java.class.path]:   [echo] -   [echo] D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-l  auncher.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-a  ntlr.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-apac  he-bcel.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-a  pache-bsf.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant  -apache-log4j.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib  \ant-apache-oro.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\l  ib\ant-apache-regexp.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.  6.2\lib\ant-apache-resolver.jar;D:\mydocuments\programlama\lib\apache\ant\apache  -ant-1.6.2\lib\ant-commons-logging.jar;D:\mydocuments\programlama\lib\apache\ant  \apache-ant-1.6.2\lib\ant-commons-net.jar;D:\mydocuments\programlama\lib\apache\  ant\apache-ant-1.6.2\lib\ant-icontract.jar;D:\mydocuments\programlama\lib\apache  \ant\apache-ant-1.6.2\lib\ant-jai.jar;D:\mydocuments\programlama\lib\apache\ant\  apache-ant-1.6.2\lib\ant-javamail.jar;D:\mydocuments\programlama\lib\apache\ant\  apache-ant-1.6.2\lib\ant-jdepend.jar;D:\mydocuments\programlama\lib\apache\ant\a  pache-ant-1.6.2\lib\ant-jmf.jar;D:\mydocuments\programlama\lib\apache\ant\apache  -ant-1.6.2\lib\ant-jsch.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant  -1.6.2\lib\ant-junit.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.  6.2\lib\ant-launcher.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.  6.2\lib\ant-netrexx.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6  .2\lib\ant-nodeps.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2  \lib\ant-starteam.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2  \lib\ant-stylebook.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.  2\lib\ant-swing.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\l  ib\ant-trax.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\a  nt-vaj.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-we  blogic.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-xa  lan1.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-xslp  .jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant.jar;D:\m  ydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\bcel-5.1.jar;D:\mydoc  uments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\xercesImpl.jar;D:\mydocum  ents\programlama\lib\apache\ant\apache-ant-1.6.2\lib\xml-apis.jar;D:\programs\Ja  va\jdk1.5.0_01\lib\tools.jar   [echo] -   [echo] [axis.classpath]:   [echo] -   [echo] C:\axis2\lib\XmlSchema-SNAPSHOT.jar;C:\axis2\lib\annogen-0  .1.0.jar;C:\axis2\lib\axiom-api-0.95.jar;C:\axis2\lib\axiom-impl-0.95.  jar;C:\axis2\lib\axis-wsdl4j-1.2.jar;C:\axis2\lib\axis2-adb-0.95.jar;C  :\axis2\lib\axis2-codegen-0.95.jar;C:\axis2\lib\axis2-doom-0.95.jar;C:

Re: [axis2] - 0.95 - WSDL2Java and OMElement

2006-03-26 Thread Ajith Ranabahu

Hi Ameet,
Are you sure you are using the correct templates for the codegenerator
? The OM pacakging was changed and the change is only reflected in the
latest release.

Ajith

On 3/24/06, Ameet Hasmucrai Amarchande [EMAIL PROTECTED] wrote:



 Hi all,



 I generated the classes for server side and client side with WSDL2Java using
 a wsdl file that I used with no problems with v0.94. After generating, when
 I try to build, it says that it cannot find symbol
 org.apache.axis2.om.OMElement. I have added all the packages from the axis
 lib, but still it cannot find that.



 Can anyone help me please?



 Thanks,



 Ameet Hasmucrai


--
Ajith Ranabahu

Re: Webservice (HTTP-GET, Image Transfer) Problem

2006-03-26 Thread StrongSteve


No one?

Please help!
--
View this message in context: 
http://www.nabble.com/Webservice-%28HTTP-GET%2C-Image-Transfer%29-Problem-t1335359.html#a3595106
Sent from the Axis - User forum at Nabble.com.

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

2006-03-26 Thread Ruchith Fernando

Hi Ali,

hmm this is very strange  since the TestCipher produced BC as
the output (i.e. bouncycastle is available as the default JCE
provider) you should be able to get the sample working if it is the
same JRE that is used by the security sample client.

Did you try this with JDK 1.4?

Thanks,
Ruchith

p.s. We were able to successfully run the security sample out of box
(with the correct services.xml) with the following configs:
Windows XP , JKD 1.4.2_02
Ubuntu Linux, JDK 1.4.2_08
Gentoo Linux, JDK 1.4.2_08


On 3/26/06, Ali Sadik Kumlali [EMAIL PROTECTED] wrote:
 Hi Ruchith,

  I ran TestChiper and got SunJCE as output. Then changed my java.security
 file as following:

  security.provider.1=sun.security.provider.Sun
 security.provider.2=org.bouncycastle.jce.provider.BouncyCastleProvider
  security.provider.3=sun.security.rsa.SunRsaSign
  security.provider.4=com.sun.net.ssl.internal.ssl.Provider
  security.provider.5=com.sun.crypto.provider.SunJCE
  security.provider.6=sun.security.jgss.SunProvider
  security.provider.7=com.sun.security.sasl.Provider

  And ran again. This time I got BC. With this configuration I ran
 securitySample and got the same error. To print all the settings, I changed
 build.xml as following:

  project name=sample s default=securitySample

  path id=axis.classpath
  fileset dir=../../lib
  include name=*.jar/
  /fileset
  fileset dir=lib
  include name=*.jar/
  /fileset
  /path
  property name=axis.classpath.prop refid=axis.classpath/
  target name=securitySample
  echo message=[java.version]: ${java.version} /
  echo message=[java.home]: ${java.home} /
  echo message=[java.class.path]: /

 echo-/echo
  echo message=${java.class.path} /

 echo-/echo
  echo message=[axis.classpath]: /

 echo-/echo
  echo message=${axis.classpath.prop} /

 echo-/echo
  java classname=sample.security.C lient
 classpathref=axis.classpath fork=true
  arg value=client_repo/
  arg value=8080/
  /java
  /target
  /project

  It gave me following output:


  c:\axis2\samples\securityant
  Buildfile: build.xml

  securitySample:
   [echo] [java.version]: 1.5.0_01
   [echo] [java.home]: D:\programs\Java\jdk1.5.0_01\jre
   [echo] [java.class.path]:
   [echo]
 -
   [echo]
 D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-l
 auncher.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-a
 ntlr.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-apac
 he-bcel.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-a
 pache-bsf.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant
 -apache-log4j.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib
 \ant-apache-oro.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\l
 ib\ant-apache-regexp.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.
 6.2\lib\ant-apache-resolver.jar;D:\mydocuments\programlama\lib\apache\ant\apache
 -ant-1.6.2\lib\ant-commons-logging.jar;D:\mydocuments\programlama\lib\apache\ant
 \apache-ant-1.6.2\lib\ant-commons-net.jar;D:\mydocuments\programlama\lib\apache\
 ant\apache-ant-1.6.2\lib\ant-icontract.jar;D:\mydocuments\programlama\lib\apache
 \ant\apache-ant-1.6.2\lib\ant-jai.jar;D:\mydocuments\programlama\lib\apache\ant\
 apache-ant-1.6.2\lib\ant-javamail.jar;D:\mydocuments\programlama\lib\apache\ant\
 apache-ant-1.6.2\lib\ant-jdepend.jar;D:\mydocuments\programlama\lib\apache\ant\a
 pache-ant-1.6.2\lib\ant-jmf.jar;D:\mydocuments\programlama\lib\apache\ant\apache
 -ant-1.6.2\lib\ant-jsch.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant
 -1.6.2\lib\ant-junit.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.
 6.2\lib\ant-launcher.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.
 6.2\lib\ant-netrexx.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6
 .2\lib\ant-nodeps.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2
 \lib\ant-starteam.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2
 \lib\ant-stylebook.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.
 2\lib\ant-swing.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\l
 ib\ant-trax.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\a
 nt-vaj.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-we
 blogic.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-xa
 lan1.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-xslp

[Axis2 0.95] Recursive data types and choice particles

2006-03-26 Thread Chuck Williams

Hi All,

Axis2 0.95 still does not handle recursive data types properly.  The
SchemaCompiler recurses infinitely and generates a stack overflow.  I've
attached my patch to fix this upgraded for 0.95.  This is a patch
against modules/codegen/src.

I see that much of the code to implement choice particles was committed,
but that the new parser does not handle them.  I need to get them
working again.  Is there already work underway to do this, and/or was an
approach determined?  If so, I'd appreciate any information about that. 
If not, I'll figure out how to do it with the new parser and send
another patch.

Thanks,

Chuck

Re: [Axis2 0.95] Recursive data types and choice particles

2006-03-26 Thread Chuck Williams





This time with the attachment:



Chuck Williams [EMAIL PROTECTED] wrote on 03/26/2006
01:41:54 AM:



  Hi All,

Axis2 0.95 still does not handle recursive data types properly.  The
SchemaCompiler recurses infinitely and generates a stack overflow.  I've
attached my patch to fix this upgraded for 0.95.  This is a patch
against modules/codegen/src.

I see that much of the code to implement choice particles was committed,
but that the new parser does not handle them.  I need to get them
working again.  Is there already work underway to do this, and/or was an
approach determined?  If so, I'd appreciate any information about that. 
If not, I'll figure out how to do it with the new parser and send
another patch.

Thanks,

Chuck

  




diff -urx '*~' codegen.src.orig/org/apache/axis2/schema/SchemaCompiler.java codegen.src.new/org/apache/axis2/schema/SchemaCompiler.java
--- codegen.src.orig/org/apache/axis2/schema/SchemaCompiler.java	2006-03-25 12:23:50.0 -1000
+++ codegen.src.new/org/apache/axis2/schema/SchemaCompiler.java	2006-03-25 21:55:26.0 -1000
@@ -381,7 +381,8 @@
 //set a name
 schemaType.setName(generatedTypeName.getLocalPart());
 writeComplexType((XmlSchemaComplexType)schemaType,
-(BeanWriterMetaInfoHolder)processedAnonymousComplexTypesMap.get(xsElt));
+(BeanWriterMetaInfoHolder)processedAnonymousComplexTypesMap.get(xsElt),
+null);
 //remove the reference from the anon list since we named the type
 processedAnonymousComplexTypesMap.remove(xsElt);
 innerElementMap.put(
@@ -423,7 +424,8 @@
 referenceSchemaType.setName(generatedTypeName.getLocalPart());
 
 writeComplexType((XmlSchemaComplexType)referenceSchemaType,
-(BeanWriterMetaInfoHolder)processedAnonymousComplexTypesMap.get(referencedElement));
+(BeanWriterMetaInfoHolder)processedAnonymousComplexTypesMap.get(referencedElement),
+null);
 //remove the reference from the anon list since we named the type
 processedAnonymousComplexTypesMap.remove(referencedElement);
 
@@ -600,12 +602,16 @@
 || baseSchemaTypeMap.containsKey(complexType.getQName())) {
 return;
 }
+
+// Must do this up front to support recursive types
+String fullyQualifiedClassName = writer.makeFullyQualifiedClassName(complexType.getQName());
+processedTypemap.put(complexType.getQName(), fullyQualifiedClassName);
 
 BeanWriterMetaInfoHolder metaInfHolder = processComplexType(complexType,parentSchema);
 
 //write the class. This type mapping would have been populated right now
 //Note - We always write classes for named complex types
-writeComplexType(complexType, metaInfHolder);
+writeComplexType(complexType, metaInfHolder, fullyQualifiedClassName);
 
 
 }
@@ -614,12 +620,12 @@
  * Writes a complex type
  * @param complexType
  * @param metaInfHolder
+ * @param fullyQualifiedClassName the name returned by makeFullyQualifiedClassName() or null if it wasn't called
  * @throws SchemaCompilationException
  */
-private void writeComplexType(XmlSchemaComplexType complexType, BeanWriterMetaInfoHolder metaInfHolder) throws SchemaCompilationException {
-String fullyQualifiedClassName = writer.write(complexType, processedTypemap, metaInfHolder);
-//populate the type map with the type QName
-processedTypemap.put(complexType.getQName(), fullyQualifiedClassName);
+private void writeComplexType(XmlSchemaComplexType complexType, BeanWriterMetaInfoHolder metaInfHolder, String fullyQualifiedClassName)
+throws SchemaCompilationException {
+writer.write(complexType, processedTypemap, metaInfHolder, fullyQualifiedClassName);
 processedTypeMetaInfoMap.put(complexType.getQName(),metaInfHolder);
 }
 
diff -urx '*~' codegen.src.orig/org/apache/axis2/schema/writer/BeanWriter.java codegen.src.new/org/apache/axis2/schema/writer/BeanWriter.java
--- codegen.src.orig/org/apache/axis2/schema/writer/BeanWriter.java	2006-03-25 12:23:50.0 -1000
+++ codegen.src.new/org/apache/axis2/schema/writer/BeanWriter.java	2006-03-25 21:55:26.0 -1000
@@ -1,5 +1,6 @@
 package org.apache.axis2.schema.writer;
 
+import javax.xml.namespace.QName;
 import org.apache.axis2.schema.BeanWriterMetaInfoHolder;
 import org.apache.axis2.schema.CompilerOptions;
 import org.apache.axis2.schema.SchemaCompilationException;
@@ -51,6 +52,12 @@
  * of the schema compiler may be exposed.
  */
 public Map getModelMap();
+
+/** Make the fully qualified class name for an element or named type
+ * @param qName the

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

2006-03-26 Thread Ali Sadik Kumlali

Hi Ruchith,With your helps, I've found the mistery at last!While I was thinking about the diffrences we might have, I gave "locale settings" a try and surprisingly it worked!Here is the mystery: "Security sample requires user language to be English". Therefore, -Duser.language=EN must be passed to JVM while application starts.To provide this support, I added jvmarg value="-Duser.language=EN"/ to the build.xml. Here is my  build.xml for the securitySample:project name="samples" default="securitySample"   path id="axis.classpath"   fileset dir="../../lib"   include name="*.jar"/   /fileset   fileset dir="lib"   include name="*.jar"/   /fileset   /path   property name="axis.classpath.prop" refid="axis.classpath"/   target name="securitySample"   echo message="[os.name]: ${os.name}" /   echo message="[os.version]: ${os.version}" /   echo message="[os.arch]: ${os.arch}" /   echo message="[ant.version]: ${ant.version}" /   echo message="[java.version]: ${java.version}" /   echo message="[java.home]: ${java.home}" /   echo message="[java.class.path]:" /echo-/echoecho message="${java.class.path}" /echo-/echoecho message="[axis.classpath]:" /echo-/echoecho message="${axis.classpath.prop}" /   
 echo-/echo java classname="sample.security.Client"  classpathref="axis.classpath" fork="true"jvmarg value="-Duser.language=EN"/arg value="client_repo"/   arg value="8080"/   /java   /target  /projectIt works for both JDK 1.4 and JDK 1.5. But, for JDK 1.5, I would like to remind you that xalan-2.7.0.jar does not work, since it causes java.lang.NoClassDefFoundError: org/apache/xpath/compiler/FuncLoader exception. So, I needed to put xalan-2.6.0.jar under both WEB-INF\lib\ and c:\axis2\lib.Anyway, thanks a lot for you take your valuable time for me.Ali Sadik KumlaliRuchith Fernando [EMAIL PROTECTED] wrote:  Hi Ali,hmm this is very strange  since the TestCipher produced "BC" asthe output (i.e. bouncycastle is available as the default JCEprovider) you should be able to get the sample working if it is thesame JRE that is used by the security sample client.Did you try this with JDK 1.4?Thanks,Ruchithp.s. We were able to successfully run the security sample out of box(with the correct services.xml) with the follo
 wing
 configs:Windows XP , JKD 1.4.2_02Ubuntu Linux, JDK 1.4.2_08Gentoo Linux, JDK 1.4.2_08On 3/26/06, Ali Sadik Kumlali  wrote: Hi Ruchith,  I ran TestChiper and got SunJCE as output. Then changed my java.security file as following:  security.provider.1=sun.security.provider.Sun security.provider.2=org.bouncycastle.jce.provider.BouncyCastleProvider  security.provider.3=sun.security.rsa.SunRsaSign  security.provider.4=com.sun.net.ssl.internal.ssl.Provider  security.provider.5=com.sun.crypto.provider.SunJCE  security.provider.6=sun.security.jgss.SunProvider  security.provider.7=com.sun.security.sasl.Provider  And ran again. This time I got BC. With this configuration I ran securitySample and got the same error. To print all the settings, I changed build.xml as following: -   -   -   -   classpathref="axis.classpath" fork="true"It gave me following output:  c:\axis2\samples\securityant  Buildfile: build.xml  securitySample:   [echo] [java.version]: 1.5.0_01   [echo] [java.home]: D:\programs\Java\jdk1.5.0_01\jre   [echo] [java.class.path]:   [echo] -   [echo] D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-l auncher.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-a
 ntlr.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-apac he-bcel.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-a pache-bsf.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant -apache-log4j.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib \ant-apache-oro.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\l ib\ant-apache-regexp.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1. 6.2\lib\ant-apache-resolver.jar;D:\mydocuments\programlama\lib\apache\ant\apache -ant-1.6.2\lib\ant-commons-logging.jar;D:\mydocuments\programlama\lib\apache\ant \apache-ant-1.6.2\lib\ant-commons-net.jar;D:\mydocuments\programlama\lib\apache\ ant\apache-ant-1.6.2\lib\ant-icontract.jar;D:\mydocuments\programlama\lib\apache

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

2006-03-26 Thread Ruchith Fernando

Hi Ali,

Great !!! ... thank you for trying the sample and finding the issue
... will update the FAQ with your findings.

Thanks,
Ruchith

On 3/26/06, Ali Sadik Kumlali [EMAIL PROTECTED] wrote:
 Hi Ruchith,

  With your helps, I've found the mistery at last!

  While I was thinking about the diffrences we might have, I gave locale
 settings a try and surprisingly it worked!

  Here is the mystery: Security sample requires user language to be
 English. Therefore, -Duser.language=EN must be passed to JVM while
 application starts.

  To provide this support, I added jvmarg value=-Duser.language=EN/ to
 the build.xml. Here is my build.xml for the securitySample:

  project name=samples default=securitySample

  path id=axis.classpath
  fileset dir=../../lib
  include name=*.jar/
  /fileset
  fileset dir=lib
  include name=*.jar/
  /fileset
  /path
  property name=axis.classpath.prop refid=axis.classpath/
  target name=securitySample
  echo message=[os.name]: ${os.name} /
  echo message=[os.version]: ${os.version} /
  echo message=[os.arch]: ${os.arch} /
  echo message=[ant.version]: ${ant.version} /

  echo message=[java.version]: ${java.version} /
  echo message=[java.home]: ${java.home} /
  echo message=[java.class.path]: /

 echo-/echo
  echo message=${java.class.path} /

 echo-/echo
  echo message=[axis.classpath]: /

 echo-/echo
  echo message=${axis.classpath.prop} /

 echo-/echo
  java classname=sample.security.Client
 classpathref=axis.classpath fork=true
  jvmarg value=-Duser.language=EN/

  arg value=client_repo/
  arg value=8080/
  /java
  /target
  /project

  It works for both JDK 1.4 and JDK 1.5. But, for JDK 1.5, I would like to
 remind you that xalan-2.7.0.jar does not work, since it causes
 java.lang.NoClassDefFoundError:
 org/apache/xpath/compiler/FuncLoader exception. So, I
 needed to put xalan-2.6.0.jar under both WEB-INF\lib\ and c:\axis2\lib.

  Anyway, thanks a lot for you take your valuable time for me.

  Ali Sadik Kumlali

 Ruchith Fernando [EMAIL PROTECTED] wrote:

  Hi Ali,

 hmm this is very strange  since the TestCipher produced BC as
 the output (i.e. bouncycastle is available as the default JCE
 provider) you should be able to get the sample working if it is the
 same JRE that is used by the security sample client.

 Did you try this with JDK 1.4?

 Thanks,
 Ruchith

 p.s. We were able to successfully run the security sample out of box
 (with the correct services.xml) with the follo wing configs:

 Windows XP , JKD 1.4.2_02
 Ubuntu Linux, JDK 1.4.2_08
 Gentoo Linux, JDK 1.4.2_08


 On 3/26/06, Ali Sadik Kumlali wrote:
  Hi Ruchith,
 
  I ran TestChiper and got SunJCE as output. Then changed my java.security
  file as following:
 
  security.provider.1=sun.security.provider.Sun
 
 security.provider.2=org.bouncycastle.jce.provider.BouncyCastleProvider
  security.provider.3=sun.security.rsa.SunRsaSign
  security.provider.4=com.sun.net.ssl.internal.ssl.Provider
  security.provider.5=com.sun.crypto.provider.SunJCE
  security.provider.6=sun.security.jgss.SunProvider
  security.provider.7=com.sun.security.sasl.Provider
 
  And ran again. This time I got BC. With this configuration I ran
  securitySample and got the same error. To print all the settings, I
 changed
  build.xml as following:
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  -
 
 
  -
 
 
  -
 
 
  -

 
  classpathref=axis.classpath fork=true
 
 
 
 
 
 
  It gave me following output:
 
 
  c:\axis2\samples\securityant
  Buildfile: build.xml
 
  securitySample:
  [echo] [java.version]: 1.5.0_01
  [echo] [java.home]: D:\programs\Java\jdk1.5.0_01\jre
  [echo] [java.class.path]:
  [echo]
  -
  [echo]
 
 D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-l
 
 auncher.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-a
 
 ntlr.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-apac
 
 he-bcel.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant-a
 
 pache-bsf.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib\ant
 
 -apache-log4j.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\lib
 
 \ant-apache-oro.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.6.2\l
 
 ib\ant-apache-regexp.jar;D:\mydocuments\programlama\lib\apache\ant\apache-ant-1.

Re: [Axis2][0.95] Source Distribution

2006-03-26 Thread Eran Chinthaka

Hi Xinjun,

We moved AXIOM from Axis2 project to WS-Commons project. So AXIOM is a
sub-project on its own now. So we do not distribute any more with Axis2.

But we  released AXIOM 0.95 version recently which you may download the
sources from.

Else, you can get the sources directly from
https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom/.

-- Chinthaka

Deepal Jayasinghe wrote:
 We did not distribute AXIOM -AIP and AXIOM-IMPL source with Axis2
 sources distribution.
 And you can download axiom sources from (
 http://ws.apache.org/commons/axiom/download.cgi )

 Xinjun Chen wrote:

   
 Hi,

 Could you Axis2 developers also include the AXIOM API and AXIOM-IMPL
 source in the source distribution of Axis2? Is there a seperate jar
 file for the source?

 Regards,
 Xinjun


  

 

   




signature.asc
Description: OpenPGP digital signature

Re: [Axis2][0.95] How to add a HeaderBlock

2006-03-26 Thread Eran Chinthaka

Xinjun Chen wrote:
 Hi,

 I am trying to add a HeaderBlock to a SOAPEnvelope in Axis2.
 It seems that Axis2 0.95 changed much from 0.94. So many package names
 and classes are changed. Will this happen in Axis2 1.0? Should I
 proceed with Axis2 0.95 or wait for Axis2 1.0?
   
We **may** do some api changes before 1.0, but by 1.0 the externally
visible api will definitely be finalized. So do not worry about it.
Even now, we haven't change much since last release. We introduced the
service client api, during 0.94 version.
 The OM module in 0.94 seems have been moved to Axiom API and Axiom-Impl.
   
Yeah, but this doesn't affect the api at all.
 How can I add a HeaderBlock using Axis2 0.95? 
Depends on which API you use.

If you are using ServiceClient api then;
ServiceClient.addHeader(OMElement); will do.

If you are using OperationClient api, then directly set the header to
envelope and set envlope to the message context which you add to the
operation client.

-- Chinthaka



signature.asc
Description: OpenPGP digital signature

Re: Please unsubscribe

2006-03-26 Thread Eran Chinthaka



Ezhil Gowthaman wrote:
 Hi,
 Please unsubscribe me from the list.
 I have sent email to [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED]. But, no luck,
Can't be. Dims, is this a bug in our mail handling util ?




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] SOAP 1.1 binding for MTOM

2006-03-26 Thread Davanum Srinivas

Main page:
http://www-128.ibm.com/developerworks/webservices/library/specification/ws-soapbinding/

-- dims

On 3/26/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
 FYI (Extracted from a mail from Anne) :

 http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-soapbinding/ws-soap11.pdf


 Chinthaka






--
Davanum Srinivas : http://wso2.com/blogs/

Re:[Axis2] Absolute Newbie Question: how to enable SOAP 1.2 support in the sample userguide code?

2006-03-26 Thread Eran Chinthaka

Hi Yang,

Set the soap version using following method.

options.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI);

HTH.

-- Eran Chinthaka

Yang Xiang wrote:
 I have just started playing with Axis2.0 and I need to know what are
 required to convert the samples/userguide code to be SOAP1.2 messages. I
 watched the HTTP traffic and they are still in SOAP1.1 format from the
 0.93 source release.  I am in dire need for a SOAP1.2 client to test one
 of our services.So the question is:
 
 What do I need to do to implement SOAP1.2 client support using Axis 2.0?
 
  
 
 Thanks in advance,
 
  
 
  
 
 Yang Xiang
 
 Quest Software
 
  
 




signature.asc
Description: OpenPGP digital signature

Re: [Axis2] [Axis2 0.94] Duplicated xmlns= added by StAXSOAPModelBuilder

2006-03-26 Thread Eran Chinthaka

Hi Xinjun,


I don't think this is a problem with the parser itself. I think we fixed
this. Please get the latest 0.95 release and check it.
If the problem still exists, please help me to reproduce the bug. I may
be able to fix it.

-- Eran Chinthaka

Xinjun Chen wrote:
 Hi Sajith,
 I try to set the InputFactory namespace awareness as the following.
 But the duplicated xmlns= exception persists.
 
 XMLInputFactory factory = XMLInputFactory.newInstance();
 factory.setProperty(XMLInputFactory.IS_NAMESPACE_AWARE,
 Boolean.TRUE);XMLStreamReader parser =
 factory.createXMLStreamReader(inStream);
 OMXMLParserWrapper builder =
 OMXMLBuilderFactory.createStAXSOAPModelBuilder(OMAbstractFactory.getSOAP11Factory(),
 parser);
 



signature.asc
Description: OpenPGP digital signature

[Axis2] [Fwd: Encountered ClassCastException while running Client]

2006-03-26 Thread Eran Chinthaka

Re-sending with the correct prefix.

 Original Message 
Subject: Encountered ClassCastException while running Client
Date: Mon, 20 Mar 2006 01:25:46 -
From: Kashif Saleem [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
References:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

Hi all,
   I followed the tutorial for writing client with data binding
approach.But I got the following exception when I ran my client:

[EMAIL PROTECTED]:~/Desktop/softwares/axis2/testsbml$ java -classpath
./build/classes/:./build/lib/XBeans-packaged.jar:$CLASSPATH
src/org/apache/axis2/userguide/TestClient
- Deploying module : addressing
java.lang.ClassCastException:
org.apache.xmlbeans.impl.values.XmlComplexContentImpl
at
uk.ac.ncl.basis.www.sbml_wsdl.HelloWorldRequest$Factory.newInstance(HelloWorldRequest.java:49)
at
src.org.apache.axis2.userguide.TestClient.main(TestClient.java:47)



I would apppreciate if someone could tell me the cause of this exception
and possible solution to fix it.


Kind Regards
Kashif Saleem



signature.asc
Description: OpenPGP digital signature

Re: problem in accessing python Hello World Service

2006-03-26 Thread Anne Thomas Manes

Do you know what message the Pyhton service is expecting?My guess is that it isn't expecting you to send the method name in the message.AnneOn 3/25/06, 
Kashif Saleem [EMAIL PROTECTED] wrote:
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 RegardsKashif Saleem-Original Message-From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]Sent: Sat 3/25/2006 3:45 PMTo: 
axis-user@ws.apache.orgSubject: Re: problem in accessing python Hello World ServicePlease post the WSDL.Based on the error messages, I'm guessing that the server is not expectingtheexample1:HelloWorld xmlns:example1=
http://example1.org/example1element to appear in the message.AnneOn 3/24/06, Kashif Saleem [EMAIL PROTECTED]
 wrote: Hi all,I installed a ZSI 2.0_rc2on machine geron045.ncl.ac.uk.I run the HelloWorld.py service onthe 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 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=
http://schemas.xmlsoap.org/soap/envelope/ xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing soapenv:Headerwsa:To xmlns:wsa=
 http://schemas.xmlsoap.org/ws/2004/08/addressing http://localhost:8082/HelloWorld.py
/wsa:Towsa:ReplyTo xmlns:wsa= http://schemas.xmlsoap.org/ws/2004/08/addressingwsa:Address 
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous/wsa:Address/wsa:ReplyTowsa:MessageID xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing
 0A2F12FAE0A1B8456E11432354035971/wsa:MessageID /soapenv:Header soapenv:Body example1:HelloWorld xmlns:example1=
http://example1.org/example1 example1:TextAxis2 Echo String /example1:Text /example1:HelloWorld /soapenv:Body /soapenv:Envelope
 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 SOAP-ENV:Envelope xmlns:SOAP-ENC= 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:Header /SOAP-ENV:Header SOAP-ENV:Body SOAP-ENV:Fault faultcodeSOAP-ENV:Server /faultcode faultstringProcessing Failure/faultstringdetailZSI:FaultDetail
 ZSI:stringexceptions:TypeError Expecting typecode in result /ZSI:string ZSI:trace/usr/lib/python2.4/site-packages/ZSI/dispatch.py:69:_Dispatch/ZSI:trace/ZSI:FaultDetail
 /detail /SOAP-ENV:Fault /SOAP-ENV:Body /SOAP-ENV:Envelope 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 erroragain.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 ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=
http://schemas.xmlsoap.org/soap/envelope/ xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing
 soapenv:Header wsa:To xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing 
http://localhost:8082/HelloWorld.py/wsa:To wsa:ReplyTo xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing wsa:Address
 http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous/wsa:Address/wsa:ReplyTowsa:MessageID xmlns:wsa=
http://schemas.xmlsoap.org/ws/2004/08/addressing C1EB5D8FA2D3E2ABE811432360408471/wsa:MessageID /soapenv:Header soapenv:Body
 example1:HelloWorld xmlns:example1=http://example1.org/example1 / /soapenv:Body /soapenv:Envelope
 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 SOAP-ENV:Envelope xmlns:SOAP-ENC= 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:Header

Re: WSDL2Java errors in 1.3 and 1.4 added vs 1.2.1

2006-03-26 Thread Anne Thomas Manes

Please file a bug report.On 3/22/06, Senin, Maxim [EMAIL PROTECTED] wrote:






Tried to use WSDL2Java ant task to generate Java client for MSN 
AdCenter = API. The Axis 1.2.1 would 
produce correct Java code, but 1.3 and 1.4 produceuncompilable code for 
native characters. For example, the WSDL 
contains
s:enumeration value=
CôtedIvoire / 
and 1.2.1 produces compilable field name, but later versions are 
not = compiling because they insert another symbol for ô:
 public 
static final java.lang.String _C├┤tedIvoire = 
C├┤tedIvoire;
The 1.2.1 was using the correct 
unicode code.
Does anyone have a solution?
Thanks,Maxim

RE: problem in accessing python Hello World Service

2006-03-26 Thread Kashif Saleem

Hi Anne,
As I mentioned earlier that the same request worked in other service 
operation with no argument as given below:


Request:

POST /web-services/kashif.py HTTP/1.1

User-Agent: Axis/2.0

SOAPAction: 

Connection: Keep-Alive

Host: basis.ncl.ac.uk:8080

Content-Length: 749

Content-Type: text/xml; charset=UTF-8



?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing;
soapenv:Headerwsa:To 
xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing;http://localhost:8080/web-services/kashif.py/wsa:Towsa:ReplyTo
 
xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing;wsa:Addresshttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous/wsa:Address/wsa:ReplyTowsa:MessageID
 
xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing;A98863E478E239A7CF11432173236951/wsa:MessageID
/soapenv:Header
soapenv:Bodyexample1:helloWorld 
xmlns:example1=http://example1.org/example1; /
/soapenv:Body
/soapenv:Envelope

Response:

HTTP/1.1 200 OK

Date: Fri, 24 Mar 2006 16:19:45 GMT

Server: Apache/1.3.33 (Debian GNU/Linux) mod_python/2.7.10 Python/2.3.4 
mod_fastcgi/2.4.2 mod_ssl/2.8.22 OpenSSL/0.9.7e

Keep-Alive: timeout=15, max=100

Connection: Keep-Alive

Transfer-Encoding: chunked

Content-Type: text/xml



257

?xml version=1.0 encoding=utf-8?
SOAP-ENV:Envelope
  xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;
  xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/;
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xmlns:xsd=http://www.w3.org/2001/XMLSchema;
  xmlns:ZSI=http://www.zolera.com/schemas/ZSI/; 
  SOAP-ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; 
SOAP-ENV:Body
helloWorldResponse
SOAP-ENC:string id=414285c0This is a hello world operation with no 
argument/SOAP-ENC:string
/helloWorldResponse
/SOAP-ENV:Body
/SOAP-ENV:Envelope



As I understand that there is some compatibility issues with Axis and ZSI.Any 
comments on that.

p.s Eran


Kind Regards
Kashif Saleem



-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Sun 26/03/2006 19:42
To: axis-user@ws.apache.org
Subject: Re: problem in accessing python Hello World Service
 
Do you know what message the Pyhton service is expecting?
My guess is that it isn't expecting you to send the method name in the
message.

Anne

On 3/25/06, Kashif Saleem [EMAIL PROTECTED] wrote:

 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

 example1:HelloWorld xmlns:example1=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
 
 
  ?xml version='1.0' encoding='UTF-8'?
  soapenv:Envelope xmlns:soapenv=
 http://schemas.xmlsoap.org/soap/envelope/;
  xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing;
  soapenv:Headerwsa:To xmlns:wsa=
  http://schemas.xmlsoap.org/ws/2004/08/addressing;
  http://localhost:8082/HelloWorld.py/wsa:Towsa:ReplyTo xmlns:wsa=
  http://schemas.xmlsoap.org/ws/2004/08/addressing;wsa:Address
  http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
 /wsa:Address/wsa:ReplyTowsa:MessageID
  xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing
  0A2F12FAE0A1B8456E11432354035971/wsa:MessageID
  /soapenv:Header
  soapenv:Body
  example1:HelloWorld xmlns:example1=http://example1.org/example1;
  example1:TextAxis2 Echo String /example1:Text
  /example1:HelloWorld
  /soapenv:Body
  /soapenv:Envelope
 
  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

Re: problem in accessing python Hello World Service

2006-03-26 Thread Anne Thomas Manes

Kashif,The first message is using document/literal. The second message is using rpc/encoded. I think you're saying that the first message doesn't work, but the second one does. Axis 2 does not yet support rpc/encoded. If the service requires rpc/encoded, then you will not be able to use Axis 2 to communicate with it. You can use Axis 1, though.
If you had a WSDL file, the problem would have been identified immediately.AnneOn 3/26/06, Kashif Saleem 
[EMAIL PROTECTED] wrote:Hi Anne,As I mentioned earlier that the same request worked in other service operation with no argument as given below:
Request:POST /web-services/kashif.py HTTP/1.1User-Agent: Axis/2.0SOAPAction:Connection: Keep-AliveHost: basis.ncl.ac.uk:8080
Content-Length: 749Content-Type: text/xml; charset=UTF-8?xml version='1.0' encoding='UTF-8'?soapenv:Envelope xmlns:soapenv=
http://schemas.xmlsoap.org/soap/envelope/ xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressingsoapenv:Headerwsa:To xmlns:wsa=
http://schemas.xmlsoap.org/ws/2004/08/addressinghttp://localhost:8080/web-services/kashif.py
/wsa:Towsa:ReplyTo xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressingwsa:Address
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous/wsa:Address/wsa:ReplyTowsa:MessageID xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing
A98863E478E239A7CF11432173236951/wsa:MessageID/soapenv:Headersoapenv:Bodyexample1:helloWorld xmlns:example1=http://example1.org/example1
 //soapenv:Body/soapenv:EnvelopeResponse:HTTP/1.1 200 OKDate: Fri, 24 Mar 2006 16:19:45 GMTServer: Apache/1.3.33 (Debian GNU/Linux) mod_python/2.7.10 Python/2.3.4 mod_fastcgi/2.4.2 mod_ssl/2.8.22 OpenSSL/0.9.7e
Keep-Alive: timeout=15, max=100Connection: Keep-AliveTransfer-Encoding: chunkedContent-Type: text/xml257?xml version=1.0 encoding=utf-8?
SOAP-ENV:Envelopexmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/xmlns:SOAP-ENC=
http://schemas.xmlsoap.org/soap/encoding/xmlns:xsi=http://www.w3.org/2001/XMLSchema-instancexmlns:xsd=
http://www.w3.org/2001/XMLSchemaxmlns:ZSI=http://www.zolera.com/schemas/ZSI/SOAP-ENV:encodingStyle=
http://schemas.xmlsoap.org/soap/encoding/ SOAP-ENV:BodyhelloWorldResponseSOAP-ENC:string id=414285c0This is a hello world operation with no argument/SOAP-ENC:string
/helloWorldResponse/SOAP-ENV:Body/SOAP-ENV:EnvelopeAs I understand that there is some compatibility issues with Axis and ZSI.Any comments on that.p.s Eran
Kind RegardsKashif Saleem-Original Message-From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]Sent: Sun 26/03/2006 19:42To: 
axis-user@ws.apache.orgSubject: Re: problem in accessing python Hello World ServiceDo you know what message the Pyhton service is expecting?My guess is that it isn't expecting you to send the method name in the
message.AnneOn 3/25/06, Kashif Saleem [EMAIL PROTECTED] wrote: 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 example1:HelloWorld xmlns:example1=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_rc2on machine 
geron045.ncl.ac.uk.I run the  HelloWorld.py service onthe 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?xml version='1.0' encoding='UTF-8'?
  soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/  xmlns:wsa=
http://schemas.xmlsoap.org/ws/2004/08/addressing  soapenv:Headerwsa:To xmlns:wsa=  http://schemas.xmlsoap.org/ws/2004/08/addressing
  http://localhost:8082/HelloWorld.py/wsa:Towsa:ReplyTo xmlns:wsa=  
http://schemas.xmlsoap.org/ws/2004/08/addressingwsa:Address  http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
 /wsa:Address/wsa:ReplyTowsa:MessageID  xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing  0A2F12FAE0A1B8456E11432354035971/wsa:MessageID
  /soapenv:Header  soapenv:Body  example1:HelloWorld

RE: problem in accessing python Hello World Service

2006-03-26 Thread Kashif Saleem

Dear Anne,
 Wsdl is given at the following location.
   http://basis.ncl.ac.uk/checkbasis.wsdl
 
Kind Regards
Kashif Saleem
 



From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Sun 26/03/2006 22:59
To: axis-user@ws.apache.org
Subject: Re: problem in accessing python Hello World Service


Kashif,

The first message is using document/literal. The second message is using 
rpc/encoded. I think you're saying that the first message doesn't work, but the 
second one does. 

Axis 2 does not yet support rpc/encoded. If the service requires rpc/encoded, 
then you will not be able to use Axis 2 to communicate with it. You can use 
Axis 1, though. 

If you had a WSDL file, the problem would have been identified immediately.

Anne


On 3/26/06, Kashif Saleem  [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]  
wrote: 

Hi Anne,
As I mentioned earlier that the same request worked in other 
service operation with no argument as given below: 


Request:

POST /web-services/kashif.py HTTP/1.1

User-Agent: Axis/2.0

SOAPAction:

Connection: Keep-Alive

Host: basis.ncl.ac.uk:8080

Content-Length: 749

Content-Type: text/xml; charset=UTF-8



?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope xmlns:soapenv= 
http://schemas.xmlsoap.org/soap/envelope/ 
http://schemas.xmlsoap.org/soap/envelope/  
xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing;
soapenv:Headerwsa:To xmlns:wsa= 
http://schemas.xmlsoap.org/ws/2004/08/addressing;http://localhost:8080/web-services/kashif.py
 /wsa:Towsa:ReplyTo 
xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing;wsa:Address 
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous 
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous 
/wsa:Address/wsa:ReplyTowsa:MessageID 
xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing 
A98863E478E239A7CF11432173236951/wsa:MessageID
/soapenv:Header
soapenv:Bodyexample1:helloWorld 
xmlns:example1=http://example1.org/example1  /
/soapenv:Body
/soapenv:Envelope

Response:

HTTP/1.1 200 OK

Date: Fri, 24 Mar 2006 16:19:45 GMT

Server: Apache/1.3.33 (Debian GNU/Linux) mod_python/2.7.10 Python/2.3.4 
mod_fastcgi/2.4.2 mod_ssl/2.8.22 OpenSSL/0.9.7e 

Keep-Alive: timeout=15, max=100

Connection: Keep-Alive

Transfer-Encoding: chunked

Content-Type: text/xml



257

?xml version=1.0 encoding=utf-8? 
SOAP-ENV:Envelope
  xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;
  xmlns:SOAP-ENC= http://schemas.xmlsoap.org/soap/encoding/ 
http://schemas.xmlsoap.org/soap/encoding/ 
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xmlns:xsd= http://www.w3.org/2001/XMLSchema 
http://www.w3.org/2001/XMLSchema 
  xmlns:ZSI=http://www.zolera.com/schemas/ZSI/;
  SOAP-ENV:encodingStyle= http://schemas.xmlsoap.org/soap/encoding/ 
http://schemas.xmlsoap.org/soap/encoding/  
SOAP-ENV:Body
helloWorldResponse
SOAP-ENC:string id=414285c0This is a hello world operation with no 
argument/SOAP-ENC:string 
/helloWorldResponse
/SOAP-ENV:Body
/SOAP-ENV:Envelope



As I understand that there is some compatibility issues with Axis and 
ZSI.Any comments on that.

p.s Eran


Kind Regards
Kashif Saleem



-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Sun 26/03/2006 19:42
To: axis-user@ws.apache.org
Subject: Re: problem in accessing python Hello World Service

Do you know what message the Pyhton service is expecting?
My guess is that it isn't expecting you to send the method name in the 
message.

Anne

On 3/25/06, Kashif Saleem [EMAIL PROTECTED] wrote:

 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

Re: problem in accessing python Hello World Service

2006-03-26 Thread Anne Thomas Manes

Kashif,I appreciate that you tried to create a WSDL file for me, but the WSDL you supplied doesn't correspond at all to any of the SOAP messages that you've posted thus far (and it certainly has more than just the one HelloWorld operation that you indicated in the first posting).
This WSDL uses rpc/literal, but that doesn't correspond to the SOAP message that you said worked (which used rpc/encoded). Also, the namespaces in the WSDL don't correspond to the namespaces in the SOAP messages.
I think the bottom line is that you Python service expect rpc/encoded, and Axis 2 doesn't support rpc/encoded.AnneOn 3/26/06, Kashif Saleem
 [EMAIL PROTECTED] wrote:
Dear Anne, Wsdl is given at the following location. http://basis.ncl.ac.uk/checkbasis.wsdlKind RegardsKashif Saleem
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]]Sent: Sun 26/03/2006 22:59To: axis-user@ws.apache.org
Subject: Re: problem in accessing python Hello World ServiceKashif,The first message is using document/literal. The second message is using rpc/encoded. I think you're saying that the first message doesn't work, but the second one does.
Axis 2 does not yet support rpc/encoded. If the service requires rpc/encoded, then you will not be able to use Axis 2 to communicate with it. You can use Axis 1, though.If you had a WSDL file, the problem would have been identified immediately.
AnneOn 3/26/06, Kashif Saleem  [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
  wrote:Hi Anne,As I mentioned earlier that the same request worked in other service operation with no argument as given below:Request:POST /web-services/kashif.py HTTP/1.1
User-Agent: Axis/2.0SOAPAction:Connection: Keep-AliveHost: basis.ncl.ac.uk:8080Content-Length: 749
Content-Type: text/xml; charset=UTF-8?xml version='1.0' encoding='UTF-8'?soapenv:Envelope xmlns:soapenv= 
http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/  xmlns:wsa=
http://schemas.xmlsoap.org/ws/2004/08/addressingsoapenv:Headerwsa:To xmlns:wsa= http://schemas.xmlsoap.org/ws/2004/08/addressing
http://localhost:8080/web-services/kashif.py /wsa:Towsa:ReplyTo xmlns:wsa=
http://schemas.xmlsoap.org/ws/2004/08/addressingwsa:Address http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous
 http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous /wsa:Address/wsa:ReplyTowsa:MessageID xmlns:wsa=
http://schemas.xmlsoap.org/ws/2004/08/addressing A98863E478E239A7CF11432173236951/wsa:MessageID/soapenv:Headersoapenv:Bodyexample1:helloWorld xmlns:example1=
http://example1.org/example1  //soapenv:Body/soapenv:EnvelopeResponse:HTTP/1.1 200 OKDate: Fri, 24 Mar 2006 16:19:45 GMT
Server: Apache/1.3.33 (Debian GNU/Linux) mod_python/2.7.10 Python/2.3.4 mod_fastcgi/2.4.2 mod_ssl/2.8.22 OpenSSL/0.9.7eKeep-Alive: timeout=15, max=100Connection: Keep-Alive
Transfer-Encoding: chunkedContent-Type: text/xml257?xml version=1.0 encoding=utf-8?SOAP-ENV:Envelopexmlns:SOAP-ENV=
http://schemas.xmlsoap.org/soap/envelope/xmlns:SOAP-ENC= http://schemas.xmlsoap.org/soap/encoding/
 http://schemas.xmlsoap.org/soap/encoding/ xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xmlns:xsd= http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema xmlns:ZSI=
http://www.zolera.com/schemas/ZSI/SOAP-ENV:encodingStyle= http://schemas.xmlsoap.org/soap/encoding/
 http://schemas.xmlsoap.org/soap/encoding/  SOAP-ENV:BodyhelloWorldResponseSOAP-ENC:string id=414285c0This is a hello world operation with no argument/SOAP-ENC:string
/helloWorldResponse/SOAP-ENV:Body/SOAP-ENV:EnvelopeAs I understand that there is some compatibility issues with Axis and ZSI.Any comments on that.
p.s EranKind RegardsKashif Saleem-Original Message-From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
]Sent: Sun 26/03/2006 19:42To: axis-user@ws.apache.orgSubject: Re: problem in accessing python Hello World ServiceDo you know what message the Pyhton service is expecting?
My guess is that it isn't expecting you to send the method name in themessage.AnneOn 3/25/06, Kashif Saleem [EMAIL PROTECTED]
 wrote: 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 example1:HelloWorld xmlns:example1=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_rc2on machine geron045.ncl.ac.uk.I run the  HelloWorld.py service onthe this machine i.e.  
http://geron045.ncl.ac.uk:8088/HelloWorld.py.This service has one  operation called HelloWorld which accepts

Re: Custom Deserializer is not being used when a SOAP Header is present in message

2006-03-26 Thread paul slade

In case anyone is interested I have determined the cause of this
issue.  The Handler I was using to validate a SOAP header was defined
at the Transport level (as opposed to within a particular service). 
The MessageContext object is in a different state when Handlers
defined at the Transport level are called when compared to Handlers
defined at the Service level.

By moving my Handler definition from the Transport level to the
Service level I was able to resolve the issue.   This is not ideal
since I really want to execute this Handler for each service
regardless of how the service is confgured.

I think if I put SOAPPart.getEnvelope() early on in my Handler invoke
method, I can ensure that the MessageContext is in the correct state
(since it forces the complete message to be parsed).  That is yet to
be tested.

paul

On 3/24/06, paul slade [EMAIL PROTECTED] wrote:
 I am running Axis 1.4 and using the MTOM support.

 I have an echo service that just takes a DataHandler as input and returns 
 it.

 When I use this service when there is no SOAPHeader included in the
 message it works happily.  When I use the service AND execute a
 Handler that adds a SOAP Header Element (for WS-Security) then I get a
 SAX exception.

 I have tried to go through the code and basically what seems to be
 happening (in the case there is a SOAP Header) is that the
 OperationDesc for the method I am calling is null within the
 RPCHandler that is trying to parse the element (from the message) that
 is of type DataHandler.

 When the OperationDesc is null Axis does not use the appropriate
 Deserializer.  It uses SimpleDeserializer when it should use
 JAFDataHandlerDeserializer.  This results in the SAX exception because
 the SimpleDeserializer does not expect nested elements.

 I have attached the following:

 1. good message and log file (good.txt).
 2. bad message and log file (bad.txt)

 You will notice that the SOAP body is the same for both good and bad
 scenarios.  It seems that the appearence of the SOAP Header that is
 causing issues.

 Any help would really be appreciated.

 paul

Re: [Axis2 0.95] SERIOUS BUG FIX + Recursive data types and choice particles

2006-03-26 Thread Chuck Williams





Ajith,

Thanks for the update. Since I need choice to upgrade to 0.95, I went
ahead and implemented it.

** In the course of this, I found a serious issue in 0.95. The
setting of the choice variable in ADBBeanTemplate is checked in,
but with the wrong code. It is always true, which messes up the pull
parser seriously. I.e., for non-choice beans, there are local trackers
and all but one are false, so code that looks for these will miss valid
properties!

There is another serious issue, in that a bug I reported earlier was
propagated into commons. Specifically, OMStAXWrapper does not obey the
contract of getElementText() -- it does not leave the reader at the end
element. I had to work around that bug in the parser, and hope it gets
fixed. There is a detailed comment with the workaround.

The attached patches resolve these issues:

  Correct the improper setting of choice that causes Axis2 to think
all adb beans are choices.
  
  Implement choice
  Fix recursive data types
  Probably fix general cases still in the parser for minOccurs=0
(e.g., the event following an empty array need not be the outer end
element) and where subelements with same name as parent element would
not work. (I didn't trigger these problems with tests, but they seem
to be there from looking at the code -- they are definitely not there
with the patch.)
  
  Fix pull parser for serialization of 0-length arrays
  Work around the OMStAXWrapper problem with getElementText()

All Axis2 tests pass, and our application which has complex wsdl runs
properly.

Thanks,

Chuck


Ajith Ranabahu wrote:

  Hi Chuck,
Sorry for the late answer but adding choice support is still underway.
We have marked choice support as a requirement for 1.0.
I'll see to that recursive datatypes are handled properly with your pach.

On 3/26/06, Chuck Williams [EMAIL PROTECTED] wrote:
  
  
 This time with the attachment:



 Chuck Williams [EMAIL PROTECTED] wrote on 03/26/2006 01:41:54 AM:



 Hi All,

Axis2 0.95 still does not handle recursive data types properly. The
SchemaCompiler recurses infinitely and generates a stack overflow. I've
attached my patch to fix this upgraded for 0.95. This is a patch
against modules/codegen/src.

I see that much of the code to implement choice particles was committed,
but that the new parser does not handle them. I need to get them
working again. Is there already work underway to do this, and/or was an
approach determined? If so, I'd appreciate any information about that.
If not, I'll figure out how to do it with the new parser and send
another patch.

Thanks,

Chuck






  
  

--
Ajith Ranabahu
  




diff -urx .svn adb.src.orig/org/apache/axis2/databinding/utils/ADBPullParser.java adb.src.new/org/apache/axis2/databinding/utils/ADBPullParser.java
--- adb.src.orig/org/apache/axis2/databinding/utils/ADBPullParser.java	2006-03-26 16:32:21.0 -1000
+++ adb.src.new/org/apache/axis2/databinding/utils/ADBPullParser.java	2006-03-26 16:51:33.0 -1000
@@ -281,12 +281,15 @@
 Object object = properties[currentIndex];
 if (object instanceof String[]) {
 
+if (((String[])object).length==0) {
+currentIndex += 2;
+return this.next();
+}
+
 complexStringArrayName = (QName) o;
 complexObjectArray = object;
 secondArrayIndex = 0;
 
-complexObjectArray = object;
-secondArrayIndex = 0;
 processingComplexADBNameValuePair = true;
 
 // use the simple name value pair processing recursively
@@ -297,6 +300,12 @@
 
 
 } else if (object instanceof Object[]) {
+
+if (((Object[])object).length==0) {
+currentIndex += 2;
+return this.next();
+}
+
 secondArrayIndex = 0;
 complexArray = (Object[]) object;
 complexArrayQName = (QName) o;
Only in adb.src.new/org/apache/axis2/databinding/utils: ADBPullParser.java~
diff -urx .svn codegen.src.orig/org/apache/axis2/schema/SchemaCompiler.java codegen.src.new/org/apache/axis2/schema/SchemaCompiler.java
--- codegen.src.orig/org/apache/axis2/schema/SchemaCompiler.java	2006-03-25 12:23:50.0 -1000
+++ codegen.src.new/org/apache/axis2/schema/SchemaCompiler.java	2006-03-25 21:55:26.0 -1000
@@ -381,7 +381,8 @@
 //set a name
 schemaType.setName(generatedTypeName.getLocalPart());
 writeComplexType((XmlSchemaComplexType)schemaType,
-(BeanWriterMetaInfoHolder)processedAnonymousComplexTypesMap.get(xsElt));
+(BeanWriterMetaInfoHolder)processedAnonymousComplexTypesMap.get(xsElt),
+null);

Re: [Axis2 0.95] SERIOUS BUG FIX + Recursive data types and choice particles

2006-03-26 Thread Ajith Ranabahu

Thanks for the quick response. Looking into the issues now


On 3/27/06, Chuck Williams [EMAIL PROTECTED] wrote:
  Thanks Ajith!  I've posted a new issue
 (http://issues.apache.org/jira/browse/AXIS2-523) with the
 patches rather than applying them to the separate issues since I didn't have
 the patches separated.  Hope this is not too troublesome.

  As I use jira for other Apache projects (e.g., Lucene), I should have known
 better.

  I greatly appreciate you efforts and that of the whole Axis2 team!

  Chuck



  Ajith Ranabahu [EMAIL PROTECTED] wrote on 03/26/2006 07:08:46
 PM:



  Hi Chuck,
 Thanks a lot for the update. I've already added the mentioned issues
 to the Jira. Just for the record, it is better if you can attach the
 patch into the Jira since Jira has this grant licence thing. So ASF is
 safe if the patch came through Jira.
 BTW we very much appreciate your efforts with Axis2. Hopefully we'll
 be able to have all the features you guys need in Axis2 1.0 release

 Ajith

 On 3/27/06, Chuck Williams [EMAIL PROTECTED] wrote:


  Ajith,

  Thanks for the update. Since I need choice to upgrade to 0.95, I went
 ahead and implemented it.

  ** In the course of this, I found a serious issue in 0.95. The
 setting of the choice variable in ADBBeanTemplate is checked in,
  but with the wrong code. It is always true, which messes up the pull
 parser seriously. I.e., for non-choice beans, there are local trackers
  and all but one are false, so code that looks for these will miss valid
 properties!

  There is another serious issue, in that a bug I reported earlier was
 propagated into commons. Specifically, OMStAXWrapper does not obey the
 contract of getElementText() -- it does not leave the reader at the end
 element. I had to work around that bug in the parser, and hope it gets
 fixed. There is a detailed comment with the workaround.

  The attached patches resolve these issues:


 Correct the improper setting of choice that causes Axis2 to think all adb
 beans are choices.

 Implement choice
 Fix recursive data types
 Probably fix general cases still in the parser for minOccurs=0 (e.g., the
 event following an empty array need not be the outer end element) and where
 subelements with same name as parent element would not work. (I didn't
 trigger these problems with tests, but they seem to be there from looking at
 the code -- they are definitely not there with the patch.)

 Fix pull parser for serialization of 0-length arrays
 Work around the OMStAXWrapper problem with getElementText() All Axis2 tests
 pass, and our application which has complex wsdl runs properly.

  Thanks,

  Chuck


  Ajith Ranabahu wrote:
  Hi Chuck,
 Sorry for the late answer but adding choice support is still underway.
 We have marked choice support as a requirement for 1.0.
 I'll see to that recursive datatypes are handled properly with your pach.

 On 3/26/06, Chuck Williams [EMAIL PROTECTED] wrote:


  This time with the attachment:



  Chuck Williams [EMAIL PROTECTED] wrote on 03/26/2006 01:41:54 AM:



  Hi All,

 Axis2 0.95 still does not handle recursive data types properly. The
 SchemaCompiler recurses infinitely and generates a stack overflow. I've
 attached my patch to fix this upgraded for 0.95. This is a patch
 against modules/codegen/src.

 I see that much of the code to implement choice particles was committed,
 but that the new parser does not handle them. I need to get them
 working again. Is there already work underway to do this, and/or was an
 approach determined? If so, I'd appreciate any information about that.
 If not, I'll figure out how to do it with the new parser and send
 another patch.

 Thanks,

 Chuck







 --
 Ajith Ranabahu






 --
 Ajith Ranabahu





--
Ajith Ranabahu

[Axis2] Mime implementation for MTOM support

Re: [Axis2] MTOM related changes for OM

Re: [Axis2] MTOM related changes for OM

Failed to call delayed quotes sample web service by Axis C++ and VC 6

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

Re: [axis2] - 0.95 - WSDL2Java and OMElement

Re: Webservice (HTTP-GET, Image Transfer) Problem

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

[Axis2 0.95] Recursive data types and choice particles

Re: [Axis2 0.95] Recursive data types and choice particles

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 :)

Re: [Axis2][0.95] Source Distribution

Re: [Axis2][0.95] How to add a HeaderBlock

Re: Please unsubscribe

Re: [Axis2] SOAP 1.1 binding for MTOM

Re:[Axis2] Absolute Newbie Question: how to enable SOAP 1.2 support in the sample userguide code?

Re: [Axis2] [Axis2 0.94] Duplicated xmlns= added by StAXSOAPModelBuilder

[Axis2] [Fwd: Encountered ClassCastException while running Client]

Re: problem in accessing python Hello World Service

Re: WSDL2Java errors in 1.3 and 1.4 added vs 1.2.1

RE: problem in accessing python Hello World Service

Re: problem in accessing python Hello World Service

RE: problem in accessing python Hello World Service

Re: problem in accessing python Hello World Service

Re: Custom Deserializer is not being used when a SOAP Header is present in message

Re: [Axis2 0.95] SERIOUS BUG FIX + Recursive data types and choice particles

Re: [Axis2 0.95] SERIOUS BUG FIX + Recursive data types and choice particles

28 matches

Site Navigation

Mail list logo

Footer information