Re: Fwd: Axis2 ADB Binding - Compiling All Schema

[Deepal jayasinghe]

Hi Deepal,
Can you/your team kindly provide your valuable suggestion on following. 
Is there any possibility of looking at your service aar file , then I 
can give your better answer for that.
Also in one of your replies you mentioned that Axis2 book is soon to 
come. How fr is that soon :)

Will take maximum of two months :)

Thank you!
Deepal

Thanks a lot


-- Forwarded message --
From: *searl* <[EMAIL PROTECTED] >
Date: Fri, Apr 25, 2008 at 1:32 AM
Subject: Re: Axis2 ADB Binding - Compiling All Schema
To: axis-user@ws.apache.org 


Hi,

This is something that I've wanted also.

leon

On Thu, 24 Apr 2008 17:35:00 +0530, lucky <[EMAIL PROTECTED] 
> wrote:

> HI,
> I am encountering one issue regarding the deployment of my web services.
I
> a
> have a number of WSDL files.Corresponding to each WSDL file I have 
an XSD

> which has schemas directly used in that WSDL.
>
> So say for WSDl A.wsdl I have A.xsd.; B.wsdl , B.xsd and so on. these
> xsd's
> intern refer to Base.xsd and some other XSDs.
> So base.xsd and other Xsds are common among all Web-Services. In some
rare
> cases A.wsdl may also refer to B.xsd.
>
> Problem -
> For each WSDL2Java I get a set of classes from Schema which I bundle 
with

> that Web-Service.
> I am not able to get the classses for complete schema in one go. I tried
> XSD2Java as well but there if I do it for A.xsd, I get classes for all
> referred schema's but not B.xsd etc if they are not referred to from
> A.xsd.
>
> How can I compile the whole schema in one go, irrespective of whether
they
> refer to each other or not and use that as a library for all my
> Web-Services.I am using ADB binding.
>
> Is there something obvious in Axis2 that I am missing? If any one knows
> the
> solution kindly assist.
>
> Thanks for your time.
--
Leon S. Searl, Software Research Engineer
Information and Telecommunication Technology Center, University of Kansas
Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612
Ph: 785-864-7820 Fax: 785-864-0387
http://www.ittc.ku.edu




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Fwd: Axis2 ADB Binding - Compiling All Schema

[lucky]

Hi Deepal,
Can you/your team kindly provide your valuable suggestion on following. Also
in one of your replies you mentioned that Axis2 book is soon to come. How fr
is that soon :)

Thanks a lot


-- Forwarded message --
From: searl <[EMAIL PROTECTED]>
Date: Fri, Apr 25, 2008 at 1:32 AM
Subject: Re: Axis2 ADB Binding - Compiling All Schema
To: axis-user@ws.apache.org


Hi,

This is something that I've wanted also.

leon

On Thu, 24 Apr 2008 17:35:00 +0530, lucky <[EMAIL PROTECTED]> wrote:
> HI,
> I am encountering one issue regarding the deployment of my web services.
I
> a
> have a number of WSDL files.Corresponding to each WSDL file I have an XSD
> which has schemas directly used in that WSDL.
>
> So say for WSDl A.wsdl I have A.xsd.; B.wsdl , B.xsd and so on. these
> xsd's
> intern refer to Base.xsd and some other XSDs.
> So base.xsd and other Xsds are common among all Web-Services. In some
rare
> cases A.wsdl may also refer to B.xsd.
>
> Problem -
> For each WSDL2Java I get a set of classes from Schema which I bundle with
> that Web-Service.
> I am not able to get the classses for complete schema in one go. I tried
> XSD2Java as well but there if I do it for A.xsd, I get classes for all
> referred schema's but not B.xsd etc if they are not referred to from
> A.xsd.
>
> How can I compile the whole schema in one go, irrespective of whether
they
> refer to each other or not and use that as a library for all my
> Web-Services.I am using ADB binding.
>
> Is there something obvious in Axis2 that I am missing? If any one knows
> the
> solution kindly assist.
>
> Thanks for your time.
--
Leon S. Searl, Software Research Engineer
Information and Telecommunication Technology Center, University of Kansas
Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612
Ph: 785-864-7820 Fax: 785-864-0387
http://www.ittc.ku.edu


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Cannot create Stub code from wsdl with wsdl2java.sh

[Uno Masaki]

Hi All,
 
I'm newbie to Axis2.
 
I'd like to create Java stub code from wsdl with Axis2 1.3
wsdl2java.sh,
however, I've got Exception (the details is below).

With Axis2 1.2 wsdl2java.sh, I've got OutOfMemoryError.

Both 1.3 and 1.2 ends with the same schema
'VZLProtocol.xsd'.

This schema is not supported by Axis2?

If possible, could you tell me a workaround for this
problem?


Regards,

Masaki UNO



*** Details ***

My Environment:
  Debian 4.0
  JDK 6u4
  Axis2 1.3
  wsdl uri:
http://www.swsoft.com/webservices/vza/4.0.0/VZA.wsdl


I executed below:

  wsdl2java.sh -uri
http://www.swsoft.com/webservices/vza/4.0.0/VZA.wsdl


I got Exception as below:


   Retrieving document at
'http://www.swsoft.com/webservices/vzl/4.0.0/VZL.wsdl',
relative to
'http://www.swsoft.com/webservices/vza/4.0.0/'.
   Retrieving document at 'VZLalertm.wsdl', relative to
'http://www.swsoft.com/webservices/vzl/4.0.0/VZL.wsdl'.
   Retrieving schema at 'VZLAlertm.xsd', relative to
'http://www.swsoft.com/webservices/vzl/4.0.0/VZLalertm.wsdl'.
   Retrieving schema at 'VZLCommonTypes.xsd', relative to
'http://www.swsoft.com/webservices/vzl/4.0.0/VZLAlertm.xsd'.
   ...
   
   ...
   Retrieving schema at
'http://www.swsoft.com/webservices/vzl/4.0.0/VZLCommonTypes.xsd',
relative to
'http://www.swsoft.com/webservices/vza/4.0.0/VZASupport.xsd'.
   Retrieving schema at
'http://www.swsoft.com/webservices/vzl/4.0.0/VZLProtocol.xsd',
relative to
'http://www.swsoft.com/webservices/vza/4.0.0/VZASupport.xsd'.
   Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException:
Error parsing WSDL
   at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:147)
   at
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
   at org.apache.axis2.wsdl.WSDL2Java.   Caused
by: org.apache.axis2.AxisFault: No service was not found
in the WSDL at
http://www.swsoft.com/webservices/vza/4.0.0/ with
targetnamespace
http://www.swsoft.com/webservices/vza/4.0.0
   at
org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:117)
   at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:141)
   ... 2 more



When I do above with wsdl2java.sh of Axis2 1.2,
I got OutOfMemoryError as below (specified option -Xmx
512M).


   Retrieving document at
'http://www.swsoft.com/webservices/vzl/4.0.0/VZL.wsdl',
relative to
'http://www.swsoft.com/webservices/vza/4.0.0/'.
   Retrieving document at 'VZLalertm.wsdl', relative to
'http://www.swsoft.com/webservices/vzl/4.0.0/VZL.wsdl'.
   Retrieving schema at 'VZLAlertm.xsd', relative to
'http://www.swsoft.com/webservices/vzl/4.0.0/VZLalertm.wsdl'.
   Retrieving schema at 'VZLCommonTypes.xsd', relative to
'http://www.swsoft.com/webservices/vzl/4.0.0/VZLAlertm.xsd'.
   ...
   
   ...
   Retrieving schema at
'http://www.swsoft.com/webservices/vzl/4.0.0/VZLCommonTypes.xsd',
relative to
'http://www.swsoft.com/webservices/vza/4.0.0/VZASupport.xsd'.
   Retrieving schema at
'http://www.swsoft.com/webservices/vzl/4.0.0/VZLProtocol.xsd',
relative to
'http://www.swsoft.com/webservices/vza/4.0.0/VZASupport.xsd'.
   Exception in thread "main" java.lang.OutOfMemoryError:
Java heap space
   at
org.apache.xerces.dom.DeferredDocumentImpl.createChunk(Unknown
Source)
   at
org.apache.xerces.dom.DeferredDocumentImpl.ensureCapacity(Unknown
Source)
   at
org.apache.xerces.dom.DeferredDocumentImpl.createNode(Unknown
Source)
   at
org.apache.xerces.dom.DeferredDocumentImpl.createDeferredDocument(Unknown
Source)
   at
org.apache.xerces.parsers.AbstractDOMParser.startDocument(Unknown
Source)
   at
org.apache.xerces.impl.dtd.XMLDTDValidator.startDocument(Unknown
Source)
   at
org.apache.xerces.impl.XMLDocumentScannerImpl.startEntity(Unknown
Source)
   at
org.apache.xerces.impl.XMLVersionDetector.startDocumentParsing(Unknown
Source)
   at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
   at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
   at
org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
   at
org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
   at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown
Source)
   at
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:299)
   at
org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(SchemaBuilder.java:1838)
   at
org.apache.ws.commons.schema.SchemaBuilder.handleImport(SchemaBuilder.java:1574)
   at
org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:170)
   at
org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:79)
   at
org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:353)
   at
org.apache.ws.commons.schema.XmlS

Re: Handler questions

[Jinyuan Zhou]

Thanks Deepal,
Thanks for the infomation Your artical shows the power of mechnism of
 phases and in flows  as well as some  pieces of details about handler and
phase. But it does not give a simple way how to put things together. I think
I have to read enough documents to figure that out my self. I remmeber it
was pretty easy to find simple exmaples about using mesasge handlers for
axis1 and some other jax rpc implementations. But for axis 2, it is not the
case.
Regards,
Jack

On Thu, Apr 24, 2008 at 10:20 PM, Deepal Jayasinghe <[EMAIL PROTECTED]>
wrote:

>
> Hi there,
> > Is there a quick way to apply handler/chain  to my webservices without
> > involving writing a module. I understand that  axis2 has a flexible
> > architecture about modules, flows, dispatchers. But I am looking for kind of
> > two-step process. 1. Writ a handler 2. modify services.xml.  May be I am
> > missing some thing?
> >
> I hope following will help you , if not please drop a mail I will provide
> whatever information you need.
> http://www.developer.com/services/article.php/3529321
>
> Thank you!
> Deepal
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 

Some people lived like they will never die
and died like they have never lived

Re: excluding pojo fields from wsdl

[keith chapman]

This feature was implemented after the 1.3 release. Hence if you use the
nightly or the 1.4 release (which should be out in a few days) you could do
this using a parameter as below.



 

 



Thanks,
Keith.






On Fri, Apr 25, 2008 at 7:50 PM, Glen Verran <[EMAIL PROTECTED]>
wrote:

> Hi there,
> I am still having trouble in finding a solution to the problem below.
> Is there another forum where I would be able to get assistance as soon
> as possible please?
> Thanks
> ~Glen
>
>
>
>
> -Original Message-
> From: Glen Verran [mailto:[EMAIL PROTECTED]
> Sent: 17 April 2008 13:05
> To: axis-user@ws.apache.org
> Subject: RE: excluding pojo fields from wsdl
>
> It seems that David Kraus and myself are in the same boat.  We both have
> the need to exclude methods and/or entire classes from being considered
> from the web service and WSDL in general and I cannot believe that this
> is something that nobody has encoutered.  I am assuming that the
> developers involved are moderating this list.
>
> I've just tried the methods posed in the article below, but they don't
> seem to work.  The class that I am referring to is not in the web
> service JAR itself.  It is in another jar which is located in my
> shared/lib folder in Tomcat, but this shouldn't make a difference at
> all.
>
> For the class below:
>
> @XmlTransient
> public class JaxbInternalMsg implements InternalMsg {
>
>  public String getEchoData() {
>return null;
>  }
>
>  public String getMsgType() throws GenericException {
>return null;
>  }
>
>  public void setEchoData(String echoData) {
>  }
>
>  public byte[] toExternal() throws GenericException {
>return null;
>  }
>
>  public String verboseToString() {
>return null;
>  }
>
> }
>
> I added the following in my services.xml file
>
> I first added this:
>
>  
> excludeProperties="msgType,echoData" />
>  
>
> Then I swopped out the above with this:
>
>  
>getMsgType
>getEchoData
>  
>
> Then I put both together and none worked!  I even added msgType and
> echoData variables to the class above and tried the different methods
> above.  Nothing.
>
> Is there anybody that can help both David and myself.  We would greatly
> appreciate it very much.
>
> Cheers
> ~Glen
>
>
>
> -Original Message-
> From: Deepal jayasinghe [mailto:[EMAIL PROTECTED]
> Sent: 17 April 2008 08:36
> To: axis-user@ws.apache.org
> Subject: Re: excluding pojo fields from wsdl
>
> Hi Kraus,
> Please have a look at the following article [section : How to exclude
> Bean properties?]
>
> http://wso2.org/library/2893
> >
> > I am using Axis2 1.2 and have deployed a simple service as a POJO. I
> > created my client using wsld2java based on the WSDL generated from the
>
> > POJO service.
> >
> >
> >
> > One of the objects, which is returned from a web service method, has
> > some */public/* */static/* fields. These fields are being included in
> > the WSDL. However, since these */static/* fields don't have
> > getters/setters, they weren't being serialized on return, which caused
>
> > an "Unexpected element return" error at the client. Adding
> > getters/setters gets rid of the problem, as long as the
> > getters/setters are not */static/* ( which is strange). In any case,
> > these */public/* */static/* fields do not need to be serialized, and
> > their inclusion in the WSDL causes problems. Using getters/setters is
> > very awkward since they aren't really needed since the fields really
> > should be */public static final/*, which I tried using.  I have also
> > tried using the java */transient/* keyword, but that doesn't seem to
> > work. I have also tried using */excludeProperties/*
> > (*/beanPropertyRules/*) in services.xml, and that didn't seem to work.
>
> > Is there a way to exclude these */public/* */static/* fields from the
> > WSDL generated from the deployed POJO?
> >
> >
> >
> > Example of return class below:
> >
> >
> >
> > Thanks, Dave
> >
> >
> >
> >
> >
> > *public* *class* EnumNormal {
> >
> >   *private* String _value;
> >
> >
> >
> >   *public* EnumNormal() {}
> >
> >
> >
> >   *public* EnumNormal(String value)
> >
> >   {
> >
> > _value = value;
> >
> >   }
> >
> >
> >
> >   *public* String getValue()
> >
> >   {
> >
> > *return* _value;
> >
> >   }
> >
> >
> >
> >   *public* *void* setValue(String value)
> >
> >   {
> >
> > _value = value;
> >
> >   }
> >
> >
> >
> >   *public* *static* String /firstEnumVal/ = "FirstEnumVal";
> >
> >   *public* *static* String /secondEnumVal/ = "SecondEnumVal";
> >
> >   *public* *static* String /thirdEnumVal/ = "ThirdEnumVal";
> >
> >   *public* *static* String /fourthEnumVal/ = "FourthEnumVal";
> >
> >   *public* *static* String /fifthEnumVal/ = "FifthEnumVal";
> >
> >
> >
> > }
> >
> >
> >
>
>
> --
> Thanks,
> Deepal
> 
> "The highest tower is built one brick at a time"
>
>
> --

Re: Alternatively to DataHandler

[Anne Thomas Manes]

The beauty of SOAP is that it hides your implementation from the
application on the other side of the wire. You can handle your binary
file your way (e.g., with a DataHandler), and the application on the
other side of the wire can handle it its way. The only thing that
matters is what goes on the wire.

So how are you sending it on the wire? Unfortunately, there are three
popular methods used to transfer binary data, and this is what causes
incompatibility. Are you using MTOM, SOAP with Attachments (SwA), or
DIME? I generally recommend using MTOM, although it's fairly new, and
many older systems don't support it. MTOM is partly compatible with
SwA -- i.e., an SwA system can read MTOM, although MTOM cannot
necessarily read SwA. DIME is completely different.

Older versions of Axis support SwA and DIME. The latest version Axis
1.4 also supports MTOM.
.NET 1.x (ASMX) with WSE supports DIME. .NET 2.0 with WSE supports
DIME and MTOM. .NET 3.x (WCF) supports MTOM.
Check your C++ SOAP engine to see what attachment systems it supports.

Anne


On Fri, Apr 25, 2008 at 8:20 AM, Capilla Castillo, Esther
<[EMAIL PROTECTED]> wrote:
> Hi all,
>  I'm use Axis1 and Axis2 to implement a Web Services that it's
>  transferring large files (250Mb). I've been using DataHandler, but I
>  don't know if the object DataHandler is compatible with other
>  technologies other than Java (.net, C++)
>  Does anyone know if the object DataHandler is compatible with these
>  technologies? And if not consistent, what alternative do you offer?
>
>  Thanks
>  Esther
>
>  -
>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: excluding pojo fields from wsdl

[Anne Thomas Manes]

The best way to manage what is included or excluded from your WSDL is
to edit the WSDL so that it exposes just what you want, then redeploy
the service using the useOriginalWsdl setting.

Anne

On Fri, Apr 25, 2008 at 10:20 AM, Glen Verran <[EMAIL PROTECTED]> wrote:
> Hi there,
>  I am still having trouble in finding a solution to the problem below.
>  Is there another forum where I would be able to get assistance as soon
>  as possible please?
>  Thanks
>  ~Glen
>
>
>
>
>  -Original Message-
>  From: Glen Verran [mailto:[EMAIL PROTECTED]
>  Sent: 17 April 2008 13:05
>  To: axis-user@ws.apache.org
>  Subject: RE: excluding pojo fields from wsdl
>
>  It seems that David Kraus and myself are in the same boat.  We both have
>  the need to exclude methods and/or entire classes from being considered
>  from the web service and WSDL in general and I cannot believe that this
>  is something that nobody has encoutered.  I am assuming that the
>  developers involved are moderating this list.
>
>  I've just tried the methods posed in the article below, but they don't
>  seem to work.  The class that I am referring to is not in the web
>  service JAR itself.  It is in another jar which is located in my
>  shared/lib folder in Tomcat, but this shouldn't make a difference at
>  all.
>
>  For the class below:
>
>  @XmlTransient
>  public class JaxbInternalMsg implements InternalMsg {
>
>   public String getEchoData() {
> return null;
>   }
>
>   public String getMsgType() throws GenericException {
> return null;
>   }
>
>   public void setEchoData(String echoData) {
>   }
>
>   public byte[] toExternal() throws GenericException {
> return null;
>   }
>
>   public String verboseToString() {
> return null;
>   }
>
>  }
>
>  I added the following in my services.xml file
>
>  I first added this:
>
>   
>   excludeProperties="msgType,echoData" />
>   
>
>  Then I swopped out the above with this:
>
>   
> getMsgType
> getEchoData
>   
>
>  Then I put both together and none worked!  I even added msgType and
>  echoData variables to the class above and tried the different methods
>  above.  Nothing.
>
>  Is there anybody that can help both David and myself.  We would greatly
>  appreciate it very much.
>
>  Cheers
>  ~Glen
>
>
>
>  -Original Message-
>  From: Deepal jayasinghe [mailto:[EMAIL PROTECTED]
>  Sent: 17 April 2008 08:36
>  To: axis-user@ws.apache.org
>  Subject: Re: excluding pojo fields from wsdl
>
>  Hi Kraus,
>  Please have a look at the following article [section : How to exclude
>  Bean properties?]
>
>  http://wso2.org/library/2893
>  >
>  > I am using Axis2 1.2 and have deployed a simple service as a POJO. I
>  > created my client using wsld2java based on the WSDL generated from the
>
>  > POJO service.
>  >
>  >
>  >
>  > One of the objects, which is returned from a web service method, has
>  > some */public/* */static/* fields. These fields are being included in
>  > the WSDL. However, since these */static/* fields don't have
>  > getters/setters, they weren't being serialized on return, which caused
>
>  > an "Unexpected element return" error at the client. Adding
>  > getters/setters gets rid of the problem, as long as the
>  > getters/setters are not */static/* ( which is strange). In any case,
>  > these */public/* */static/* fields do not need to be serialized, and
>  > their inclusion in the WSDL causes problems. Using getters/setters is
>  > very awkward since they aren't really needed since the fields really
>  > should be */public static final/*, which I tried using.  I have also
>  > tried using the java */transient/* keyword, but that doesn't seem to
>  > work. I have also tried using */excludeProperties/*
>  > (*/beanPropertyRules/*) in services.xml, and that didn't seem to work.
>
>  > Is there a way to exclude these */public/* */static/* fields from the
>  > WSDL generated from the deployed POJO?
>  >
>  >
>  >
>  > Example of return class below:
>  >
>  >
>  >
>  > Thanks, Dave
>  >
>  >
>  >
>  >
>  >
>  > *public* *class* EnumNormal {
>  >
>  >   *private* String _value;
>  >
>  >
>  >
>  >   *public* EnumNormal() {}
>  >
>  >
>  >
>  >   *public* EnumNormal(String value)
>  >
>  >   {
>  >
>  > _value = value;
>  >
>  >   }
>  >
>  >
>  >
>  >   *public* String getValue()
>  >
>  >   {
>  >
>  > *return* _value;
>  >
>  >   }
>  >
>  >
>  >
>  >   *public* *void* setValue(String value)
>  >
>  >   {
>  >
>  > _value = value;
>  >
>  >   }
>  >
>  >
>  >
>  >   *public* *static* String /firstEnumVal/ = "FirstEnumVal";
>  >
>  >   *public* *static* String /secondEnumVal/ = "SecondEnumVal";
>  >
>  >   *public* *static* String /thirdEnumVal/ = "ThirdEnumVal";
>  >
>  >   *public* *static* String /fourthEnumVal/ = "FourthEnumVal";
>  >
>  >   *public* *static* String /fifthEnumVal/ = "FifthEnumVal";
>  >
>  >
>  >
>  > }
>  >
>  >
>  >
>
>
>  --
>  Than

Re: NullPointerException when invoking Axis

[Anne Thomas Manes]

You must upgrade to at least Axis 1.3 (1.4 is preferable) if you want
to use "wrapped" style.

Anne

On Fri, Apr 25, 2008 at 11:08 AM, SDev <[EMAIL PROTECTED]> wrote:
>
>  Hi,
>
>  I'm using Axis 1.2.1. I've auto generated a web service which created a wsdl
>  that was clattered with references to
>  http://schemas.xmlsoap.org/soap/encoding/. Since
>  http://schemas.xmlsoap.org/soap/encoding/ is not supported by WS-I I changed
>  in the wsdd from:
>
>  
>
>  to
>
>use="literal">
>
>  This created the wsdl below without this namespace:
>
>  
>targetNamespace="http://se/rsv/at/art/arendelager/AtAlArendeLagerWS";
>  xmlns:apachesoap="http://xml.apache.org/xml-soap";
>  xmlns:impl="http://se/rsv/at/art/arendelager/AtAlArendeLagerWS";
>  xmlns:intf="http://se/rsv/at/art/arendelager/AtAlArendeLagerWS";
>  xmlns:tns1="http://arendelager.art.at.rsv.se";
>  xmlns:tns2="http://base.er.rsv.se";
>  xmlns:tns3="http://akthanterare.akt.at.rsv.se";
>  xmlns:tns4="http://arendeplan.art.at.rsv.se";
>  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>  xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>  
>   
> targetNamespace="http://arendelager.art.at.rsv.se";
>  xmlns="http://www.w3.org/2001/XMLSchema";>
>http://akthanterare.akt.at.rsv.se"/>
>http://base.er.rsv.se"/>
>http://xml.apache.org/xml-soap"/>
>http://se/rsv/at/art/arendelager/AtAlArendeLagerWS"/>
>http://arendeplan.art.at.rsv.se"/>
>
> 
>  
>   
>  
> 
>
>
> 
>  
>   
>  
> 
>
>
> 
>  
>   
>  
> 
>
>
> 
>  
>   
>  type="xsd:string"/>
>   
>  
> 
>
>
> 
>  
>   
>
>   
>  
> 
>
>
> 
>
>   
> targetNamespace="http://base.er.rsv.se";
>  xmlns="http://www.w3.org/2001/XMLSchema";>
>http://akthanterare.akt.at.rsv.se"/>
>http://xml.apache.org/xml-soap"/>
>http://se/rsv/at/art/arendelager/AtAlArendeLagerWS"/>
>http://arendelager.art.at.rsv.se"/>
>http://arendeplan.art.at.rsv.se"/>
>
> 
>  
>  
>  
>  
>  
>  
>  
>  
>  
> 
>
>
> 
>  
>type="tns2:ErMessageHeader"/>
>  
> 
>
>   
> targetNamespace="http://akthanterare.akt.at.rsv.se";
>  xmlns="http://www.w3.org/2001/XMLSchema";>
>http://base.er.rsv.se"/>
>http://xml.apache.org/xml-soap"/>
>http://se/rsv/at/art/arendelager/AtAlArendeLagerWS"/>
>http://arendelager.art.at.rsv.se"/>
>http://arendeplan.art.at.rsv.se"/>
>
> 
>  
>   
>
>   
>  
> 
>
>
> 
>  
>   
>  
> 
>
>   
> targetNamespace="http://se/rsv/at/art/arendelager/AtAlArendeLagerWS";
>  xmlns="http://www.w3.org/2001/XMLSchema";>
>http://akthanterare.akt.at.rsv.se"/>
>http://base.er.rsv.se"/>
>http://xml.apache.org/xml-soap"/>
>http://arendelager.art.at.rsv.se"/>
>http://arendeplan.art.at.rsv.se"/>
>
> 
>  
>   
>
>
>
>   
>  
> 
>
>
> 
>  
>   
>  type="tns1:AtAlArendeIntressentPK"/>
>
>   
>  
> 
>
>
> 
>  
>   
>  
> 
>
>
> 
>  
>   
>  
> 
>
>
> 
>type="xsd:anyType"/>
> 
>
>
> 
>  
>   
>
>   
>  
> 
>
>
> 
>  
>   
>
>
>
>
>  type="tns1:AtAlArendeIngivare"/>
>  type="impl:ArrayOf_xsd_anyType"/>
>  type="impl:ArrayOf_xsd_anyType"/>
>  type="tns4:AtApArendeTypsId"/>
>
>
>
>
>
>  type="impl:ArrayOf_xsd_anyType"/>
>
>
>
>
>   
>  
> 
>
>
> 
>  
>   
>
>   
>  
> 
>
>
> 
>  
>   
>  
> 
>
>   
> targetNamespace="http://xml.apache.org/xml-soap";
>  xmlns="http://www.w3.org/2001/XMLSchema";>
>http://akthanterare.akt.at.rsv.se"/>
>http://base.er.rsv.se"/>
>http://se/rsv/at/art/arendelager/AtAlArendeLagerWS"/>
>http://arendelager.art.at.rsv.se"/>
>http://arendeplan.art.at.rsv.se"/>
>
> 
>type="xsd:anyType"/>
> 
>
>   
> targetNamespace="http://arendeplan.art.at.rsv.se";
>  xmlns="http://www.w3.org/2001/XMLSchema";>
>http://akthanterare.akt.at.rsv.se"/>
>http://base.er.rsv.se"/>
>http://xml.apache.org/xml-soap"/>
>http://se/rsv/at/art/arendelager/AtAlArendeLagerWS"/>
>http://arendelager.art.at.rsv.se"/>
>
> 
>  
>   
>
>   
>  
> 
>
>
> 
>  
>   
>  
> 
>
>   
>   
>
>
>
>   
>
>
>
>
>
>   
>
>
>
>
>
>   
>
>name="skapaArendeRequest"/>
>
>  

Re: org.apache.axis2.AxisFault: HTTP Transport error : '501' - 'Not Implemented' message

[Daniel Hagen]

Hi Pinaki,

this looks like a HTTP issue to me where the SQUID Proxy between client 
and server does have a problem with the Chunked Transfer Encoding the 
client uses in conjunction with a HTTP POST request.


Squid's support for Chunked Transfer Encoding when communicating with 
the client is incomplete; I have seen the exact behaviour you described 
for HTTP PUT requests but was unaware that this also is the case for 
HTTP POST.


Maybe you could try to convince your webservice client not to use 
Chunked Transfer Encoding but to
- either close the HTTP connection after each request (which can be a 
performance problem when you are making many requests in a short time frame)

- or send a Content-Length along with the request

Another workaround would be to disable the use of a proxy if your 
environment allows you to connect to the Webservice server directly.


Best regards

Daniel

Pinaki Chandrasekhar schrieb:

Hello Friends,
I have been trying to figure out the problem for a few days and really need
some help.
My j2ee application integrates with IPX gateway for Short messaging service.
This is implemented as a WebService by IPX and they provided me with thge
precompiled client stub files ( compiled using axis 2.1.1.1)
I am new to web services and axis. I went through all the installation and
tutorial successfully with a helloworld ws example and the axis2userguide
example that is provided.
However I am stuck when I try integrating with my existing j2ee application.
My j2ee app is the client for the web service and I compiled it successfully
with the client stubs set on the classpath. But I keep getting this error
whenever it needs to send the message:
org.apache.axis2.AxisFault: HTTP Transport error : '501' - 'Not Implemented'

I have the server logs here for your reference.

I may be messing  things up in configuring the whole app on the server with
axis 2

I am using the Jboss-4.0.3Sp1 as the server and also have axis2 installed on
the same machine with the AXIS2_HOME set properly. I also have the axis.war
file deployed on the server.

Please, can someone help when to rectify the problem.

Thanks in advance,

pc



this is the server log when I send a short code through my phone. It goes to
the iPX gateway who reroute it back to my application. It seems like the
message is all getting prepared and throws up an error while about to send.

2008-04-23 10:31:15,769 INFO [ReceiveSMSServlet] Receive SMS Message

2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] SMS Received:1208917875769

2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] IPX Receive --->TimeStamp
: 20080423 04:32:44

2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] IPX Receive --->Operator :
DiGi

2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] IPX Receive --->MessageId
: 1-1703551585

2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] IPX Receive --->Message :
Store fs 009

2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] IPX
Receive --->DestinationAddress : 32088

2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] IPX
Receive --->OriginatorAddress : 60169063492

2008-04-23 10:31:15,769 DEBUG [ReceiveSMSServlet] Local
Context.PROVIDER_URL: java.naming.provider.url

2008-04-23 10:31:15,779 INFO [ContentControllerBean] get content for
requestCode = fs 009

2008-04-23 10:31:15,779 DEBUG
[org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Content#findByKeyword]
Executing SQL: SELECT DISTINCT t0_c.ContentId, t0_c.Keyword, t0_c.Tariff,
t0_c.Type, t0_c.Title, t0_c.Status, t0_c.creationDate FROM content t0_c
WHERE (t0_c.Keyword = ?)

2008-04-23 10:31:15,789 DEBUG
[org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand.Content] load
relation SQL: SELECT content.StoreId, store.Name, store.Status,
store.mobileNumber, store.freeRequestCount FROM content content, store store
WHERE (content.StoreId=store.StoreId) AND ((content.ContentId=?))

2008-04-23 10:31:15,799 DEBUG
[org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Media#findByContent]
Executing SQL: SELECT DISTINCT t0_m.MediaId, t0_m.fileSize, t0_m.fileName,
t0_m.Height, t0_m.Width FROM media t0_m, content t1_m_content WHERE
((t1_m_content.ContentId=?) AND t0_m.ContentId=t1_m_content.ContentId)

2008-04-23 10:31:15,809 DEBUG
[org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Store#findStore] Executing
SQL: SELECT DISTINCT t0_s.StoreId FROM store t0_s WHERE (t0_s.StoreId = ?)

2008-04-23 10:31:15,819 DEBUG
[org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.Setting#findSetting]
Executing SQL: SELECT t0_s.SettingId, t0_s.SmsServerPassword,
t0_s.SmsServer, t0_s.SmsUrl, t0_s.SmsLogin, t0_s.SmsPassword,
t0_s.SmsKeyword, t0_s.SmsShortcode, t0_s.SmsService, t0_s.wapGatewayUrl,
t0_s.freeDownload, t0_s.mTCost, t0_s.operatorPercentage, t0_s.iPXPercentage
FROM setting t0_s

2008-04-23 10:31:16,450 DEBUG [httpclient.wire.header] >> "POST
/api/services2/SmsUtilApiService HTTP/1.1[\r][\n]"

2008-04-23 10:31:16,490 DEBUG [httpclient.wire.header] >> "SOAPAction:
"tns:#sendWapPushSm"[\r][\n]"

2008-04-23 10:31:16,490 DEBUG [h

Problems with AXIOM API

[joern.albinger]

Hello,
 
I would like to read this Statement with the Axiom API .
 

http://www.w3.org/2003/05/soap-envelope";>
  
http://ws.apache.org/axis2";>
  Name
  lastElemt
  hihihiih
  hhuhuhu

  

 
.
 
I cannot read it. I want to creat a REST Service with Axis2. Please help.
How can I get the elements ?
 
Chears
Jörn