[jira] Resolved: (AXISCPP-509) Current CVS code doesn't build in windows

[ http://issues.apache.org/jira/browse/AXISCPP-509?page=history ] Roshan Weerasuriya resolved AXISCPP-509: Resolution: Fixed Fix Version: current (nightly) Fixed the issue > Current CVS code doesn't build in windows > -

[jira] Closed: (AXISCPP-509) Current CVS code doesn't build in windows

[ http://issues.apache.org/jira/browse/AXISCPP-509?page=history ] Roshan Weerasuriya closed AXISCPP-509: -- Issue is OK > Current CVS code doesn't build in windows > - > > Key: AXISCPP-509 >

[jira] Commented: (AXISCPP-509) Current CVS code doesn't build in windows

[ http://issues.apache.org/jira/browse/AXISCPP-509?page=comments#action_60334 ] Roshan Weerasuriya commented on AXISCPP-509: Adding the PlatformSpecific files to the VC project and setting vc setting seems to correct this problem in my mech

[jira] Created: (AXISCPP-509) Current CVS code doesn't build in windows

Current CVS code doesn't build in windows - Key: AXISCPP-509 URL: http://issues.apache.org/jira/browse/AXISCPP-509 Project: Axis-C++ Type: Bug Components: Client - Engine Reporter: Roshan Weerasuriya The current CVS c

[jira] Assigned: (AXISCPP-509) Current CVS code doesn't build in windows

[ http://issues.apache.org/jira/browse/AXISCPP-509?page=history ] Roshan Weerasuriya reassigned AXISCPP-509: -- Assign To: Roshan Weerasuriya > Current CVS code doesn't build in windows > - > > Key:

[jira] Assigned: (AXISCPP-465) Bug in SoapSerializer::addOutputParam

[ http://issues.apache.org/jira/browse/AXISCPP-465?page=history ] Roshan Weerasuriya reassigned AXISCPP-465: -- Assign To: Roshan Weerasuriya > Bug in SoapSerializer::addOutputParam > - > > Key: AXISCPP

[jira] Commented: (AXISCPP-465) Bug in SoapSerializer::addOutputParam

[ http://issues.apache.org/jira/browse/AXISCPP-465?page=comments#action_59585 ] Roshan Weerasuriya commented on AXISCPP-465: This makes the samples to give garbage results, eg: Calculator gives garbage value. > Bug in SoapSerializer::addOu

[jira] Created: (AXISCPP-465) Bug in SoapSerializer::addOutputParam

Bug in SoapSerializer::addOutputParam - Key: AXISCPP-465 URL: http://issues.apache.org/jira/browse/AXISCPP-465 Project: Axis-C++ Type: Bug Components: Serialization Reporter: Roshan Weerasuriya hi Adrian and All, (Adrian

[jira] Assigned: (AXISCPP-376) createSOAPHeaderBlock() allows to create Prefix and Localname with spaces in header bolck

[ http://issues.apache.org/jira/browse/AXISCPP-376?page=history ] Roshan Weerasuriya reassigned AXISCPP-376: -- Assign To: Roshan Weerasuriya (was: Rangika Mendis) > createSOAPHeaderBlock() allows to create Prefix and Localname with spaces in >

[jira] Closed: (AXISCPP-365) Change method parameters constant

[ http://issues.apache.org/jira/browse/AXISCPP-365?page=history ] Roshan Weerasuriya closed AXISCPP-365: -- fixed this issue > Change method parameters constant > - > > Key: AXISCPP-365 > URL: http:/

[jira] Resolved: (AXISCPP-365) Change method parameters constant

[ http://issues.apache.org/jira/browse/AXISCPP-365?page=history ] Roshan Weerasuriya resolved AXISCPP-365: Resolution: Fixed Added the functionality > Change method parameters constant > - > > Key: A

[jira] Commented: (AXISCPP-353) BasicNode->setValue does not set a new value but appends to any current value

[ http://issues.apache.org/jira/browse/AXISCPP-353?page=comments#action_58544 ] Roshan Weerasuriya commented on AXISCPP-353: You see this because "pIHeaderBlock2" has two text childs effectively. > BasicNode->setValue does not set a new val

[jira] Commented: (AXISCPP-353) BasicNode->setValue does not set a new value but appends to any current value

[ http://issues.apache.org/jira/browse/AXISCPP-353?page=comments#action_58488 ] Roshan Weerasuriya commented on AXISCPP-353: hi Andrew, I investigated this issue. The reason for why you see (or get) it as a appended text is described below

[jira] Commented: (AXISCPP-353) BasicNode->setValue does not set a new value but appends to any current value

[ http://issues.apache.org/jira/browse/AXISCPP-353?page=comments#action_58489 ] Roshan Weerasuriya commented on AXISCPP-353: So I think this is not a bug. Shall I close this issue? > BasicNode->setValue does not set a new value but appends

[jira] Closed: (AXISCPP-360) compilation error when using APIs in BasicNode

[ http://issues.apache.org/jira/browse/AXISCPP-360?page=history ] Roshan Weerasuriya closed AXISCPP-360: -- Fixed the issue, there was no change required to fix this issue. > compilation error when using APIs in BasicNode > -

[jira] Resolved: (AXISCPP-360) compilation error when using APIs in BasicNode

[ http://issues.apache.org/jira/browse/AXISCPP-360?page=history ] Roshan Weerasuriya resolved AXISCPP-360: Resolution: Fixed Fixed the issue. > compilation error when using APIs in BasicNode > --

[jira] Commented: (AXISCPP-397) Better support for client-side handlers

[ http://issues.apache.org/jira/browse/AXISCPP-397?page=comments#action_58351 ] Roshan Weerasuriya commented on AXISCPP-397: A Handler can do this directly if it can get access to the Transport object, because the SoapTransport API has set/

[jira] Commented: (AXISCPP-397) Better support for client-side handlers

[ http://issues.apache.org/jira/browse/AXISCPP-397?page=comments#action_58350 ] Roshan Weerasuriya commented on AXISCPP-397: A handler can do this directly if it can get access to the Transport object, because the SoapTransport API has set/

[jira] Assigned: (AXISCPP-341) createNamespaceDecl() and addNamespaceDecl() allows duplicate namespace declaration within a Tag.

[ http://issues.apache.org/jira/browse/AXISCPP-341?page=history ] Roshan Weerasuriya reassigned AXISCPP-341: -- Assign To: Roshan Weerasuriya > createNamespaceDecl() and addNamespaceDecl() allows duplicate namespace > declaration within a Tag. >

[jira] Assigned: (AXISCPP-353) BasicNode->setValue does not set a new value but appends to any current value

[ http://issues.apache.org/jira/browse/AXISCPP-353?page=history ] Roshan Weerasuriya reassigned AXISCPP-353: -- Assign To: Roshan Weerasuriya > BasicNode->setValue does not set a new value but appends to any current value > ---

[jira] Commented: (AXISCPP-385) use common name for API that set/get URI in different classes

[ http://issues.apache.org/jira/browse/AXISCPP-385?page=comments#action_57713 ] Roshan Weerasuriya commented on AXISCPP-385: URI Please. John Hawkins Samisa Abeysinghe <[EMAIL PROTECTED]> 18/01/2005 08:52 Please respond to "Apache A

[jira] Commented: (AXISCPP-375) setPrefix() in IAttribute class does not check whether the given namespace prefix is declared or not

[ http://issues.apache.org/jira/browse/AXISCPP-375?page=comments#action_57705 ] Roshan Weerasuriya commented on AXISCPP-375: hi James, If the namespace is not declared we have two options: 1) Put a restriction on user, so that he should al

[jira] Assigned: (AXISCPP-377) setting a attribute to the SOAP method from the stub using "setSOAPMethodAttribute" makes the server crash

[ http://issues.apache.org/jira/browse/AXISCPP-377?page=history ] Roshan Weerasuriya reassigned AXISCPP-377: -- Assign To: Roshan Weerasuriya > setting a attribute to the SOAP method from the stub using > "setSOAPMethodAttribute" makes the server

[jira] Created: (AXISCPP-377) setting a attribute to the SOAP method from the stub using "setSOAPMethodAttribute" makes the server crash

setting a attribute to the SOAP method from the stub using "setSOAPMethodAttribute" makes the server crash -- Key: AXISCPP-377 URL: http://issues.apache.org/jira/browse/AXISCP

[jira] Commented: (AXISCPP-374) No usage information for setSOAPMethodAttribute() functions in API docs

[ http://issues.apache.org/jira/browse/AXISCPP-374?page=comments#action_57584 ] Roshan Weerasuriya commented on AXISCPP-374: I figured out that there is a problem like this. If you set a attribute to the SOAP Method using this setSOAPMethod

[jira] Commented: (AXISCPP-374) No usage information for setSOAPMethodAttribute() functions in API docs

[ http://issues.apache.org/jira/browse/AXISCPP-374?page=comments#action_57580 ] Roshan Weerasuriya commented on AXISCPP-374: hi Manohar, This method can be used at any time which the user needs. There are no pre-requirements to be done bef

[jira] Assigned: (AXISCPP-374) No usage information for setSOAPMethodAttribute() functions in API docs

[ http://issues.apache.org/jira/browse/AXISCPP-374?page=history ] Roshan Weerasuriya reassigned AXISCPP-374: -- Assign To: Roshan Weerasuriya > No usage information for setSOAPMethodAttribute() functions in API docs > -

[jira] Commented: (AXISCPP-374) No usage information for setSOAPMethodAttribute() functions in API docs

[ http://issues.apache.org/jira/browse/AXISCPP-374?page=comments#action_57574 ] Roshan Weerasuriya commented on AXISCPP-374: hi Manohar, what do you exactly mean by "how to verify the values set by these APIs"? And also you say "However, t

[jira] Assigned: (AXISCPP-376) createSOAPHeaderBlock() allows to create Prefix and Localname with spaces in header bolck

[ http://issues.apache.org/jira/browse/AXISCPP-376?page=history ] Roshan Weerasuriya reassigned AXISCPP-376: -- Assign To: Roshan Weerasuriya > createSOAPHeaderBlock() allows to create Prefix and Localname with spaces in > header bolck >

[jira] Assigned: (AXISCPP-375) setPrefix() in IAttribute class does not check whether the given namespace prefix is declared or not

[ http://issues.apache.org/jira/browse/AXISCPP-375?page=history ] Roshan Weerasuriya reassigned AXISCPP-375: -- Assign To: Roshan Weerasuriya > setPrefix() in IAttribute class does not check whether the given namespace > prefix is declared or no

[jira] Commented: (AXISCPP-370) setUri() API in the IAttribute class does not updated the namespace URI associated with the attribute prefix in SOAP Message

[ http://issues.apache.org/jira/browse/AXISCPP-370?page=comments#action_57547 ] Roshan Weerasuriya commented on AXISCPP-370: hi Andrew, >is AxisString the same as > AxisChar*? AxisString is std::basic_string >A small note about AxisString.

[jira] Closed: (AXISCPP-370) setUri() API in the IAttribute class does not updated the namespace URI associated with the attribute prefix in SOAP Message

[ http://issues.apache.org/jira/browse/AXISCPP-370?page=history ] Roshan Weerasuriya closed AXISCPP-370: -- Fixed > setUri() API in the IAttribute class does not updated the namespace URI > associated with the attribute prefix in SOAP Message > ---

[jira] Resolved: (AXISCPP-370) setUri() API in the IAttribute class does not updated the namespace URI associated with the attribute prefix in SOAP Message

[ http://issues.apache.org/jira/browse/AXISCPP-370?page=history ] Roshan Weerasuriya resolved AXISCPP-370: Resolution: Fixed Added the functionality. The new usage would look like: InteropTestPortType ws(endpoint, APTHTTP1_1);

[jira] Closed: (AXISCPP-372) Do we need the addNamespaceDecl() method in the "IHeaderBlock" interface

[ http://issues.apache.org/jira/browse/AXISCPP-372?page=history ] Roshan Weerasuriya closed AXISCPP-372: -- Commented this API method > Do we need the addNamespaceDecl() method in the "IHeaderBlock" interface > --

[jira] Resolved: (AXISCPP-372) Do we need the addNamespaceDecl() method in the "IHeaderBlock" interface

[ http://issues.apache.org/jira/browse/AXISCPP-372?page=history ] Roshan Weerasuriya resolved AXISCPP-372: Resolution: Fixed commented this API method. > Do we need the addNamespaceDecl() method in the "IHeaderBlock" interface > ---

[jira] Commented: (AXISCPP-372) Do we need the addNamespaceDecl() method in the "IHeaderBlock" interface

[ http://issues.apache.org/jira/browse/AXISCPP-372?page=comments#action_57541 ] Roshan Weerasuriya commented on AXISCPP-372: Ok, so we will remove this "addNamespaceDecl()" from the API of IHeaderBlock > Do we need the addNamespaceDecl() me

[jira] Assigned: (AXISCPP-372) Do we need the addNamespaceDecl() method in the "IHeaderBlock" interface

[ http://issues.apache.org/jira/browse/AXISCPP-372?page=history ] Roshan Weerasuriya reassigned AXISCPP-372: -- Assign To: Roshan Weerasuriya > Do we need the addNamespaceDecl() method in the "IHeaderBlock" interface >

[jira] Created: (AXISCPP-372) Do we need the addNamespaceDecl() method in the "IHeaderBlock" interface

Do we need the addNamespaceDecl() method in the "IHeaderBlock" interface Key: AXISCPP-372 URL: http://issues.apache.org/jira/browse/AXISCPP-372 Project: Axis-C++ Type: Improvement Components:

[jira] Assigned: (AXISCPP-370) setUri() API in the IAttribute class does not updated the namespace URI associated with the attribute prefix in SOAP Message

[ http://issues.apache.org/jira/browse/AXISCPP-370?page=history ] Roshan Weerasuriya reassigned AXISCPP-370: -- Assign To: Roshan Weerasuriya > setUri() API in the IAttribute class does not updated the namespace URI > associated with the attribut

[jira] Created: (AXISCPP-370) setUri() API in the IAttribute class does not updated the namespace URI associated with the attribute prefix in SOAP Message

setUri() API in the IAttribute class does not updated the namespace URI associated with the attribute prefix in SOAP Message Key: AXISCPP-370 URL: http://

[jira] Assigned: (AXISCPP-363) createStdAttribute() uses an undeclared namespace prefix 'env' when SOAP_VER_1_2 is passed as the SOAP_VERSION.

[ http://issues.apache.org/jira/browse/AXISCPP-363?page=history ] Roshan Weerasuriya reassigned AXISCPP-363: -- Assign To: Roshan Weerasuriya > createStdAttribute() uses an undeclared namespace prefix 'env' when > SOAP_VER_1_2 is passed as the S

[jira] Assigned: (AXISCPP-364) Bug in IHeaderBlock

[ http://issues.apache.org/jira/browse/AXISCPP-364?page=history ] Roshan Weerasuriya reassigned AXISCPP-364: -- Assign To: Roshan Weerasuriya > Bug in IHeaderBlock > --- > > Key: AXISCPP-364 > URL: http://issues.a

[jira] Assigned: (AXISCPP-365) Change method parameters constant

[ http://issues.apache.org/jira/browse/AXISCPP-365?page=history ] Roshan Weerasuriya reassigned AXISCPP-365: -- Assign To: Roshan Weerasuriya > Change method parameters constant > - > > Key: AXISCPP-365 >

[jira] Created: (AXISCPP-369) Samples doesn't build due removing the outdated secure parameter from Call::initialize

Samples doesn't build due removing the outdated secure parameter from Call::initialize -- Key: AXISCPP-369 URL: http://issues.apache.org/jira/browse/AXISCPP-369 Project: Axis-C++ Typ

[jira] Commented: (AXISCPP-360) compilation error when using APIs in BasicNode

[ http://issues.apache.org/jira/browse/AXISCPP-360?page=comments#action_57343 ] Roshan Weerasuriya commented on AXISCPP-360: The methods in the BasicNode are not constant methods. The BasicNode object which you have creted is a constant obj

[jira] Assigned: (AXISCPP-360) compilation error when using APIs in BasicNode

[ http://issues.apache.org/jira/browse/AXISCPP-360?page=history ] Roshan Weerasuriya reassigned AXISCPP-360: -- Assign To: Roshan Weerasuriya > compilation error when using APIs in BasicNode > -- > >

[jira] Assigned: (AXISCPP-357) createImmediateChild() and createChild() APIs in the IHeaderBlock does not create namespace declaration

[ http://issues.apache.org/jira/browse/AXISCPP-357?page=history ] Roshan Weerasuriya reassigned AXISCPP-357: -- Assign To: Roshan Weerasuriya > createImmediateChild() and createChild() APIs in the IHeaderBlock does not > create namespace declara

[jira] Commented: (AXISCPP-355) Mistake in the document for createSOAPHeaderBlock() API

[ http://issues.apache.org/jira/browse/AXISCPP-355?page=comments#action_57338 ] Roshan Weerasuriya commented on AXISCPP-355: Corrected this issue in the actual Stub.hpp/cpp classes. Now will have to generate the api docs and update the stub

[jira] Closed: (AXISCPP-356) Unable to specify the prefix when creating a HeaderBlock throguh Stubs

[ http://issues.apache.org/jira/browse/AXISCPP-356?page=history ] Roshan Weerasuriya closed AXISCPP-356: -- Fixed this issue > Unable to specify the prefix when creating a HeaderBlock throguh Stubs > -

[jira] Commented: (AXISCPP-356) Unable to specify the prefix when creating a HeaderBlock throguh Stubs

[ http://issues.apache.org/jira/browse/AXISCPP-356?page=comments#action_57336 ] Roshan Weerasuriya commented on AXISCPP-356: The "ws" object in the above example code is a instance of the User stub. > Unable to specify the prefix when creat

[jira] Resolved: (AXISCPP-356) Unable to specify the prefix when creating a HeaderBlock throguh Stubs

[ http://issues.apache.org/jira/browse/AXISCPP-356?page=history ] Roshan Weerasuriya resolved AXISCPP-356: Resolution: Fixed Added this functionality. Now the user can do this through the Stub. Also after adding the namespace (and the prefi

[jira] Assigned: (AXISCPP-356) Unable to specify the prefix when creating a HeaderBlock throguh Stubs

[ http://issues.apache.org/jira/browse/AXISCPP-356?page=history ] Roshan Weerasuriya reassigned AXISCPP-356: -- Assign To: Roshan Weerasuriya > Unable to specify the prefix when creating a HeaderBlock throguh Stubs > --

[jira] Created: (AXISCPP-356) Unable to specify the prefix when creating a HeaderBlock throguh Stubs

Unable to specify the prefix when creating a HeaderBlock throguh Stubs -- Key: AXISCPP-356 URL: http://issues.apache.org/jira/browse/AXISCPP-356 Project: Axis-C++ Type: New Feature Components: Basi

[jira] Resolved: (AXISCPP-350) Require support to Add name spaces dynamically

[ http://issues.apache.org/jira/browse/AXISCPP-350?page=history ] Roshan Weerasuriya resolved AXISCPP-350: Resolution: Fixed Added the API methods: Could you a code similar to the following in a Handler: IHandlerSoapSerializer* pISZ;

[jira] Assigned: (AXISCPP-354) Prefixing Header Blocks

[ http://issues.apache.org/jira/browse/AXISCPP-354?page=history ] Roshan Weerasuriya reassigned AXISCPP-354: -- Assign To: Roshan Weerasuriya > Prefixing Header Blocks > --- > > Key: AXISCPP-354 > URL: http://

[jira] Closed: (AXISCPP-354) Prefixing Header Blocks

[ http://issues.apache.org/jira/browse/AXISCPP-354?page=history ] Roshan Weerasuriya closed AXISCPP-354: -- Fixed the issue > Prefixing Header Blocks > --- > > Key: AXISCPP-354 > URL: http://issues.apache.org/ji

[jira] Closed: (AXISCPP-350) Require support to Add name spaces dynamically

[ http://issues.apache.org/jira/browse/AXISCPP-350?page=history ] Roshan Weerasuriya closed AXISCPP-350: -- Fixed > Require support to Add name spaces dynamically > -- > > Key: AXISCPP-350 >

[jira] Resolved: (AXISCPP-354) Prefixing Header Blocks

[ http://issues.apache.org/jira/browse/AXISCPP-354?page=history ] Roshan Weerasuriya resolved AXISCPP-354: Resolution: Fixed Added this functionlity to the API You can use some thing like following in your handler: pISZ->addNamespaceToEnve

[jira] Resolved: (AXISCPP-352) virtual BasicNode* IHeaderBlock::getChild(int iChildPosition) does not return NULL if childposition is given as 0 or negative value

[ http://issues.apache.org/jira/browse/AXISCPP-352?page=history ] Roshan Weerasuriya resolved AXISCPP-352: Resolution: Fixed Resolved this problem > virtual BasicNode* IHeaderBlock::getChild(int iChildPosition) does not > return NULL if

[jira] Closed: (AXISCPP-352) virtual BasicNode* IHeaderBlock::getChild(int iChildPosition) does not return NULL if childposition is given as 0 or negative value

[ http://issues.apache.org/jira/browse/AXISCPP-352?page=history ] Roshan Weerasuriya closed AXISCPP-352: -- Fixed this issue > virtual BasicNode* IHeaderBlock::getChild(int iChildPosition) does not > return NULL if childposition is given as 0 or

[jira] Assigned: (AXISCPP-352) virtual BasicNode* IHeaderBlock::getChild(int iChildPosition) does not return NULL if childposition is given as 0 or negative value

[ http://issues.apache.org/jira/browse/AXISCPP-352?page=history ] Roshan Weerasuriya reassigned AXISCPP-352: -- Assign To: Roshan Weerasuriya > virtual BasicNode* IHeaderBlock::getChild(int iChildPosition) does not > return NULL if childpositio

[jira] Assigned: (AXISCPP-350) Require support to Add name spaces dynamically

[ http://issues.apache.org/jira/browse/AXISCPP-350?page=history ] Roshan Weerasuriya reassigned AXISCPP-350: -- Assign To: Roshan Weerasuriya > Require support to Add name spaces dynamically > -- > >

[jira] Commented: (AXISCPP-350) Require support to Add name spaces dynamically

[ http://issues.apache.org/jira/browse/AXISCPP-350?page=comments#action_57290 ] Roshan Weerasuriya commented on AXISCPP-350: This requirement is to do this through Hanlders > Require support to Add name spaces dynamically >