Re: [Fwd: Re: Apache 2.0 vs Apache 1.3]

2005-05-05 Thread Rangika Mendis


I also think that it would be better to support only for Apache 2.

Regds
Rangika
On Thu, 2005-05-05 at 16:25 +, Samisa Abeysinghe wrote:
> Would appreciate thoughts on this.
> 
> Please see the mail tail below.
> 
> Thanks,
> Samisa...
> 
> -Forwarded Message-
> From: John Hawkins <[EMAIL PROTECTED]>
> To: Apache AXIS C Developers List 
> Subject: Re: Apache 2.0 vs Apache 1.3
> Date: Thu, 05 May 2005 11:17:27 +0100
> 
> 
> I've been thinking this too - we should go to the user list first.
> 
> 
> 
> 
> Samisa Abeysinghe
> <[EMAIL PROTECTED]>
> 
> 05/05/2005 16:30
>  Please respond to
>   "Apache AXIS C Developers List"
> To
> Apache AXIS C
> Developers List
> 
> cc
> 
>Subject
> Apache 2.0 vs
> Apache 1.3
> 
> 
> 
> 
> Hi all,
> 
> I have noticed widespread use of Apache 2.0 and the number of queries we
> are getting on Apache 1.3 is near 0.
> Given this, would it be a bad idea to support only Apache 2 on server
> side?
> This will simplify the docs as well.
> 
> Thoughts please.
> 
> Thanks,
> Samisa...



Re: SOAP Headers

2005-03-09 Thread Rangika Mendis
Title: Message



Hi Brian,
 
In m_pCall->setTransportProperty() we set the http 
header not the soap header.
 
If you want to 
create a soap header call, createHeaderBlock(AxisChar* 
pachLocalName, * AxisChar* pachUri, AxisChar* pachPrefix) 

 
eg: m_pCall->createHeaderBlock(AxisChar* 
pachLocalName, * AxisChar* pachUri, AxisChar* pachPrefix) 
;
 
 
 
Regards
Rangika

  - Original Message - 
  From: 
  Brian Abbott 
  
  To: axis-c-user@ws.apache.org 
  Sent: Wednesday, March 09, 2005 12:07 
  PM
  Subject: SOAP Headers
  
  Hi, 
  
   
  I am wondering how 
  I might go about setting the value of a SOAP Header element. I know I can 
  insert the attribute I want by inserting: 
   
  m_pCall->setTransportProperty(SOAPACTION_HEADER, 
  "VARNAME");
   
  but, how do I 
  actually set VARNAME's value?
   
  Thanks,
   
  Brian


Re: regarding bug in a Axis C++ Windows Installation Guide

2005-01-18 Thread Rangika Mendis
  Hi Samisa,

  Aren't we going to support Expat as a  core module in the future?

  If we're not then can remove it from the documentation.

  Regards,
  Rangika


  - Original Message -
  From: "Samisa Abeysinghe" <[EMAIL PROTECTED]>
  To: "Apache AXIS C User List" 
  Sent: Wednesday, January 19, 2005 8:06 AM
  Subject: Re: regarding bug in a Axis C++ Windows Installation Guide


  > Hi Rangika,
  > As we no longer support Expat as a core module, would it not be
  > more aprropriate to remove Expat referances from the doc alltogether?
  >I agree that the NOTE on top says it all, but at times, I too skip
  > those and jump into the doc content, with the intention of quick start
  > ;-)
  >
  > Thanks,
  > Samisa...
  >
  >
  > On Tue, 18 Jan 2005 16:51:56 +0600, Rangika Mendis
  > <[EMAIL PROTECTED]> wrote:
  > >
  > >
  > > Hi Chinthana,
  > >
  > > At the top of the windows Installation Page the sentences given below
are
  > > written.
  > >
  > >
  > >
  > >
  > > Note:The Expat XML Parser module is not currently maintained and also
  > > contains some bugs. So it is removed from the 1.4 release. Please
ignore any
  > > references to the Expat parser in the documentation. The documentation
will
  > > be updated regarding this later.
  > >
  > > Where ever "If you decide to use the Expat parser" sentence is written
  > > there's a note saying that "The Expat XML Parser module is not
currently
  > > maintained and also contains some bugs. For more information refer the
  > > contents section."
  > > Since the documentation will be updated later the use of expat parser
was
  > > not removed.
  > >
  > >
  > >
  > > Regards,
  > > Rangika
  > >
  > >
  > >
  > >
  > > - Original Message -
  > > From: Chinthana C. Dinapala
  > > To: axis-c-user@ws.apache.org
  > > Sent: Tuesday, January 18, 2005 2:19 PM
  > > Subject: regarding bug in a Axis C++ Windows Installation Guide
  > >
  > >
  > >
  > > Hi guys,
  > >
  > >
  > >
  > > There is a defect in Axis C++ Windows Installation Guide document.
  > >
  > > They have mention that we can have a choice to use either Expat XML
Parser
  > > or Xerces parser.
  > >
  > > But Use of Expat parser is outdated. So it is a bug in a doc.
  > >
  > >
  > >
  > > Thanks
  > >
  > >
  > >
  > >
  > >
  > > Chinthana Dinapala
  > >
  > > Associate Software Engineer
  > >
  > > Virtusa Corp.
  > > 16th Floor, West Tower
  > > World Trade Center
  > >
  > > Colombo 01
  > >
  > >
  > >
  > >
  > >
  > > Creating competitive advantage
  > >
  > >
  > >
  > >
  > > 
  >
> --

  > > This message, including any attachments, contains confidential
information
  > > intended for a specific individual and purpose, and is intended for
the
  > > addressee only. Any unauthorized disclosure, use, dissemination,
copying, or
  > > distribution of this message or any of its attachments or the
information
  > > contained in this e-mail, or the taking of any action based on it, is
  > > strictly prohibited. If you are not the intended recipient, please
notify
  > > the sender immediately by return e-mail and delete this message.
  > >
  > >
  > >
  > >
  >
> --
---
  > > This message, including any attachments, contains confidential
information
  > > intended for a specific individual and purpose, and is intended for
the
  > > addressee only. Any unauthorized disclosure, use, dissemination,
copying, or
  > > distribution of this message or any of its attachments or the
information
  > > contained in this e-mail, or the taking of any action based on it, is
  > > strictly prohibited. If you are not the intended recipient, please
notify
  > > the sender immediately by return e-mail and delete this message.
  > >
  > >
  > >
  >
  >




Re: regarding bug in a Axis C++ Windows Installation

2005-01-18 Thread Rangika Mendis




  Hi Sanjaya,
   
  axiscpp.conf is in C:\Program Files\Apache Group\Apache\Axis 
  . 
   
  
  Dushshantha,
   
  Is your apache2 
  installed in C:\Program 
  Files\Apache Group?
   
  Can you check whether 
  the paths that you have given in axiscpp.conf is correct.Because sometimes 
  when the paths & spellings are incorrect you get that 
  warning.
   
  If that doesn't 
  work.
   
  Type the following in 
  the command prompt 
  C:\Program 
  Files\Apache Group\Apache2\bin and then type Apache.
   
  Regards,
  Rangika
   
   - 
  Original Message - 
  
From: 
sanjaya 
singharage 
To: Apache AXIS C User List 
Sent: Tuesday, January 18, 2005 6:32 
PM
Subject: Re: regarding bug in a Axis 
C++ Windows Installation 

does axiscpp.conf exist in C:\Program 
Files\Apache Group\Apache\Axis ? 
 
sanjaya.

  - Original Message - 
  From: 
  Dushshantha Chandradasa 
  To: Apache AXIS C User List 
  Sent: Tuesday, January 18, 2005 5:41 
  PM
  Subject: regarding bug in a Axis C++ 
  Windows Installation 
  
  
   
  Hi 
  all,
   
  Found a problem 
  of starting Apache 2 server after installing Axis C++ using Windows 
  installation guide. 
   
  The command 
  prompt gives the following error massage.
   
   
   
   
  Regards,
  Dushshantha
  
  
  
  --This 
  message, including any attachments, contains confidential information 
  intended for a specific individual and purpose, and is intended for the 
  addressee only. Any unauthorized disclosure, use, dissemination, copying, 
  or distribution of this message or any of its attachments or the 
  information contained in this e-mail, or the taking of any action based on 
  it, is strictly prohibited. If you are not the intended recipient, please 
  notify the sender immediately by return e-mail and delete this message. 
  
  


  -This 
message, including any attachments, contains confidential 
information intended for a specific individual and purpose, and is 
intended for the addressee only. Any unauthorized disclosure, use, 
dissemination, copying, or distribution of this message or any of 
its attachments or the information contained in this e-mail, or the 
taking of any action based on it, is strictly prohibited. If you are 
not the intended recipient, please notify the sender immediately by 
return e-mail and delete this 
message.
  


  -This 
message, including any attachments, contains confidential 
information intended for a specific individual and purpose, and is 
intended for the addressee only. Any unauthorized disclosure, use, 
dissemination, copying, or distribution of this message or any of 
its attachments or the information contained in this e-mail, or the 
taking of any action based on it, is strictly prohibited. If you are 
not the intended recipient, please notify the sender immediately by 
return e-mail and delete this 
message.



Re: regarding bug in a Axis C++ Windows Installation Guide

2005-01-18 Thread Rangika Mendis




   
  
 
Hi Chinthana,
 
At the top of the windows Installation Page 
the sentences given below are written.
 

Note:The Expat XML Parser module is not currently 
maintained and also contains some bugs. So it is removed from the 1.4 
release. Please ignore any references to the Expat parser in the 
documentation. The documentation will be updated regarding this later. 
Where ever "If you decide to use the Expat parser" sentence is written 
there's a note saying that "The Expat XML Parser module is not currently 
maintained and also contains some bugs. For more information refer the 
contents section." 
Since the documentation will be updated later 
the use of expat parser was not removed. 
 
 
 
Regards,
Rangika
 
 
 
 
- Original Message - 
From: 
Chinthana 
C. Dinapala 
To: axis-c-user@ws.apache.org 
Sent: Tuesday, January 18, 2005 2:19 
PM
Subject: regarding bug in a Axis C++ 
Windows Installation Guide


Hi 
guys,
 
There is a defect 
in Axis C++ Windows Installation Guide 
document.
They have mention 
that we can have a choice to use either Expat XML Parser or Xerces 
parser.
But 
Use of Expat 
parser is outdated. So it is a bug in a doc.
 
Thanks
 
 
Chinthana 
Dinapala
Associate 
Software Engineer
Virtusa 
Corp. 16th Floor, 
West 
TowerWorld Trade Center
Colombo 
01


Creating 
competitive advantage  
 



--This 
message, including any attachments, contains confidential information 
intended for a specific individual and purpose, and is intended for the 
addressee only. Any unauthorized disclosure, use, dissemination, copying, or 
distribution of this message or any of its attachments or the information 
contained in this e-mail, or the taking of any action based on it, is 
strictly prohibited. If you are not the intended recipient, please notify 
the sender immediately by return e-mail and delete this message. 


  
  
-This 
  message, including any attachments, contains confidential information 
  intended for a specific individual and purpose, and is intended for 
  the addressee only. Any unauthorized disclosure, use, dissemination, 
  copying, or distribution of this message or any of its attachments or 
  the information contained in this e-mail, or the taking of any action 
  based on it, is strictly prohibited. If you are not the intended 
  recipient, please notify the sender immediately by return e-mail and 
  delete this 
message.



SoapSerializer was modified to support attachments.

2005-01-07 Thread Rangika Mendis




  
Hi All,
 
We added  functionalities to  the serializer to 
serialize soap attachments. The following files were added for that 
purpose.
 
1. SoapAttachmentHeaders
2. SoapAttachment
 
New API  allows to add Soap Attachment objects to the 
serializer. 
 
The following methods in IWrapperSoapSerializer.hpp can be 
used  to add attachment details to the Serializer.
 
virtual void addAttachment(const AxisChar* achId, 
ISoapAttachment* objAttach)=0;
 
 virtual void addAttachmentBody(const AxisChar* 
achId, xsd__base64Binary* pAttchBody)=0;
 
 virtual void addAttachmentHeader(const AxisChar* 
achId, const AxisChar* achHeaderName, const AxisChar* 
achHeaderValue)=0;
 
 /**    * creates and returns a 
SoapAttachment object to the caller of this methods. *  The 
user can use this object and fill in the attachment details. 
This *  method doesn't add the created SoapAttachment object 
to the Serializer. *  The user will have to add this object 
explictly by calling the addAttachment  *  method of the 
IWrapperSoapSerializer interface    
*     */ virtual 
ISoapAttachment* createSoapAttachement()=0;
 
These methods will be used by the web service wrapper 
class.
 
Any comments on this will be greatly 
appreciated.
 
Regards,
 
 Nithya & Rangika