[
https://issues.apache.org/jira/browse/AXISCPP-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-946.
--
Resolution: Cannot Reproduce
If this is still a problem, reopen. But I cannot reproduce.
client
[
https://issues.apache.org/jira/browse/AXISCPP-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra reopened AXISCPP-481:
Need to revisit this issue from client-side perspective. When some error
happens, we need to force
[
https://issues.apache.org/jira/browse/AXISCPP-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-1011.
---
Resolution: Fixed
Fix Version/s: current (nightly)
There were several problems in this area
[
https://issues.apache.org/jira/browse/AXISCPP-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-979.
--
lock() / unlock() mismatch in engine/HandlerLoader.cpp
[
https://issues.apache.org/jira/browse/AXISCPP-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-535.
--
Resolution: Cannot Reproduce
test is not being run so i see no reason to have keep this in books
Hi Franz,
While I did not specifically test for that scenario, I believe the
solution will work. The tests I put in tests the following type coming in
as start/end element:
s:complexType name=ArrayOfInfoString
s:attribute name=attributeA type=s:string use=optional/
[
https://issues.apache.org/jira/browse/AXISCPP-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-998.
--
wrong Host: HTTP request header when using HTTP proxy
[
https://issues.apache.org/jira/browse/AXISCPP-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-950.
--
simple_axis_server and AdminClient doesn't have execute permission
[
https://issues.apache.org/jira/browse/AXISCPP-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464565
]
nadir amra commented on AXISCPP-891:
Forgot to mention that in this case you will get an array object of size 0
[
https://issues.apache.org/jira/browse/AXISCPP-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra reopened AXISCPP-1011:
-
For a correct parse of SoapFaults and their details i had to make two
additional small changes
[
https://issues.apache.org/jira/browse/AXISCPP-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra updated AXISCPP-991:
---
Comment: was deleted
Deserializing complex type broken when start-end element tag is encountered
[
https://issues.apache.org/jira/browse/AXISCPP-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-991.
--
Resolution: Fixed
Fix Version/s: current (nightly)
I moved the fault comment ot axiscpp-1011
Franz, Yes, that was next on my list. Should be done this week.
Nadir K. Amra
Franz Fehringer [EMAIL PROTECTED] wrote on 01/08/2007 05:04:20 AM:
Hello Nadir,
This is very good news, thanks alot.
Now the remaining bummer for me is AXISCPP-991, where you and me
have made conflicting
is rather capable.
Are problems in this field known?
Thanks and best regards
Franz
Nadir Amra schrieb:
Franz,
I reverted the transport changes to what it was, for now.
I believe the errors you are getting are some sort of bugs in the HTTP
transport parsing that existed prior
[
https://issues.apache.org/jira/browse/AXISCPP-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-716.
--
Resolution: Fixed
Fix Version/s: current (nightly)
Problem is finally resolved. Default
[
https://issues.apache.org/jira/browse/AXISCPP-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462693
]
nadir amra commented on AXISCPP-716:
Just to keep you posted, I pretty much have completed this issue, just
[
https://issues.apache.org/jira/browse/AXISCPP-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462352
]
nadir amra commented on AXISCPP-995:
Oh, I forgot to add that I updated a test case, XSD_boolean, so
[
https://issues.apache.org/jira/browse/AXISCPP-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-995.
--
Resolution: Fixed
Fix Version/s: current (nightly)
The problem was that we were not detecting
[
https://issues.apache.org/jira/browse/AXISCPP-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-960.
--
Resolution: Fixed
Fix Version/s: current (nightly)
Revamped code so now things are simpler
[
https://issues.apache.org/jira/browse/AXISCPP-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461910
]
nadir amra commented on AXISCPP-966:
I need a sample wsdl file to resolve this problem.
WSDL2WS generate
[ http://issues.apache.org/jira/browse/AXISCPP-926?page=all ]
nadir amra closed AXISCPP-926.
--
Fix Version/s: current (nightly)
Resolution: Fixed
Server-side files now compile.
Server side files created by WSDL2Ws fails to compile
[ http://issues.apache.org/jira/browse/AXISCPP-968?page=all ]
nadir amra closed AXISCPP-968.
--
Fix Version/s: current (nightly)
Resolution: Fixed
WSDL2WS generate wrong code: complex array should not been deleted
[ http://issues.apache.org/jira/browse/AXISCPP-975?page=all ]
nadir amra closed AXISCPP-975.
--
Fix Version/s: current (nightly)
Resolution: Fixed
WSDL2WS: WrapWriter.java: returnParamName's localpart not split in some cases
[ http://issues.apache.org/jira/browse/AXISCPP-928?page=all ]
nadir amra closed AXISCPP-928.
--
Fix Version/s: current (nightly)
Resolution: Fixed
ret should not have been used. out + i should have been used. Now compiles
successfully, with correct
[ http://issues.apache.org/jira/browse/AXISCPP-1010?page=all ]
nadir amra reassigned AXISCPP-1010:
---
Assignee: nadir amra
new method Call:clearSOAPMethodAttributes()
---
Key: AXISCPP-1010
[ http://issues.apache.org/jira/browse/AXISCPP-716?page=all ]
nadir amra reassigned AXISCPP-716:
--
Assignee: nadir amra
Support for the attribute construct 'use'
-
Key: AXISCPP-716
[ http://issues.apache.org/jira/browse/AXISCPP-1004?page=all ]
nadir amra closed AXISCPP-1004.
---
Fix Version/s: current (nightly)
Resolution: Fixed
I believe this is now resolved. I resolved this by adding code in
WSDL2Ws.java,method
[ http://issues.apache.org/jira/browse/AXISCPP-980?page=all ]
nadir amra closed AXISCPP-980.
--
Fix Version/s: current (nightly)
Resolution: Cannot Reproduce
I took the latest code and ran the wsdl specified and did not have any problems
compiling
[ http://issues.apache.org/jira/browse/AXISCPP-1000?page=all ]
nadir amra reassigned AXISCPP-1000:
---
Assignee: nadir amra
Axis C++ 1.6 beta can't handle array return type correctly
Content-Transfer-Encoding: 7bit
[ http://issues.apache.org/jira/browse/AXISCPP-972?page=all ]
nadir amra resolved AXISCPP-972.
Fix Version/s: current (nightly)
(was: 1.6 Beta)
Resolution: Fixed
Resolved by simply changing
[ http://issues.apache.org/jira/browse/AXISCPP-912?page=all ]
nadir amra closed AXISCPP-912.
--
Resolution: Duplicate
duplicate of AXISCPP-898. If not, reopen.
only basic types allowed for attributes
[
http://issues.apache.org/jira/browse/AXISCPP-918?page=comments#action_12460839
]
nadir amra commented on AXISCPP-918:
I believe it has been included in SVN
generated copy constructor wrong/incomplete
[
http://issues.apache.org/jira/browse/AXISCPP-1011?page=comments#action_12460840
]
nadir amra commented on AXISCPP-1011:
-
Fault detail is also optional
faultactor is facultative in SoapFaults
[ http://issues.apache.org/jira/browse/AXISCPP-1011?page=all ]
nadir amra resolved AXISCPP-1011.
-
Resolution: Fixed
Marking as resolved until a testcase can be created, then it will be closed.
faultactor is facultative in SoapFaults
[
http://issues.apache.org/jira/browse/AXISCPP-849?page=comments#action_12460635
]
nadir amra commented on AXISCPP-849:
Actually, when there is a conflict between a variable identifier and a class,
_Ref is added to the variable identifier
[ http://issues.apache.org/jira/browse/AXISCPP-849?page=all ]
nadir amra updated AXISCPP-849:
---
Comment: was deleted
Stub compilation problems when WSDL contains complexTypes and elements of the
same name
[ http://issues.apache.org/jira/browse/AXISCPP-898?page=all ]
nadir amra resolved AXISCPP-898.
Fix Version/s: 1.6 Final
Resolution: Fixed
OK, all of my testing seems to be passing, and various customer problems
relating to the issue has been
[ http://issues.apache.org/jira/browse/AXISCPP-849?page=all ]
nadir amra closed AXISCPP-849.
--
Fix Version/s: 1.6 Final
(was: 1.6 Alpha)
Resolution: Fixed
Fixed this so that we now go through all the externalized classes
[ http://issues.apache.org/jira/browse/AXISCPP-1011?page=all ]
nadir amra reassigned AXISCPP-1011:
---
Assignee: nadir amra
faultactor is facultative in SoapFaults
---
Key: AXISCPP-1011
[
http://issues.apache.org/jira/browse/AXISCPP-914?page=comments#action_12460399
]
nadir amra commented on AXISCPP-914:
Franz ,
I am at a loss to explain memory corruption problems you are having. I had
made changes to the code
[ http://issues.apache.org/jira/browse/AXISCPP-849?page=all ]
nadir amra reopened AXISCPP-849:
Assignee: nadir amra (was: Fred Preston)
I am re-opening this issue because it is not a complete fix. Although the
fix resolves variable
[
http://issues.apache.org/jira/browse/AXISCPP-1010?page=comments#action_12459806
]
nadir amra commented on AXISCPP-1010:
-
Will be looking into this and other JIRA'slooks useful.
new method Call:clearSOAPMethodAttributes
[ http://issues.apache.org/jira/browse/AXISCPP-898?page=all ]
nadir amra updated AXISCPP-898:
---
Attachment: wsdl2ws.jar
I am attaching the wsdl2ws.jar file that I hope fixes the problem prior to
uploading the files to SVN. The fixes in the code has fixed
correctly.
Best regards
Franz
nadir amra (JIRA) schrieb:
[ http://issues.apache.org/jira/browse/AXISCPP-991?
page=comments#action_12454432 ]
nadir amra commented on AXISCPP-991:
I put a temporary fix so that if start_end tag was specified
Reporter: Michael Xiong
Assigned To: nadir amra
Priority: Critical
Fix For: 1.6 Beta
axis-c deserializer has a problem:
IWrapperSoapDeSerializer::getChardataAs 's declaration and
definition should be changed into by reference, not by value, in
order
Project: Axis-C++
Issue Type: Improvement
Components: WSDL processing - Doc
Affects Versions: 1.6 Beta
Reporter: nadir amra
Assigned To: nadir amra
Priority: Minor
Instead of having to list all the prototypes in the various CPP
[ http://issues.apache.org/jira/browse/AXISCPP-1009?page=all ]
nadir amra closed AXISCPP-1009.
---
Resolution: Fixed
Prototypes for Axis_Deserializer_xxx, Axis_Serializer_xxx, etc should be in
the header files
[ http://issues.apache.org/jira/browse/AXISCPP-100?page=all ]
nadir amra updated AXISCPP-100:
---
Component/s: Trace Utility
enable axis c++ (engine) tracing
Key: AXISCPP-100
URL: http
[
http://issues.apache.org/jira/browse/AXISCPP-898?page=comments#action_12455528
]
nadir amra commented on AXISCPP-898:
Just to update you in this issue, I believe I have come up with a robust fix
and will be putting up in SVN in the next
[
http://issues.apache.org/jira/browse/AXISCPP-991?page=comments#action_12454432
]
nadir amra commented on AXISCPP-991:
I put a temporary fix so that if start_end tag was specified with no attributes
(which I am hoping is the prevalent
Franz,
I reverted the transport changes to what it was, for now.
I believe the errors you are getting are some sort of bugs in the HTTP
transport parsing that existed prior to my changes but were masked due to
the current implementation of using a looping counter and ignoring 0-byte
reads
[ http://issues.apache.org/jira/browse/AXISCPP-923?page=all ]
nadir amra closed AXISCPP-923.
--
Fix Version/s: 1.6 Beta
Resolution: Fixed
Memory leak in HTTPChannel::ReportError
Key
[ http://issues.apache.org/jira/browse/AXISCPP-237?page=all ]
nadir amra closed AXISCPP-237.
--
Fix Version/s: 1.6 Beta
Resolution: Fixed
dlopen failures should show reason for failure
memory leak in error paths of xsd types
---
Key: AXISCPP-1008
URL: http://issues.apache.org/jira/browse/AXISCPP-1008
Project: Axis-C++
Issue Type: Bug
Reporter: nadir amra
Assigned
[ http://issues.apache.org/jira/browse/AXISCPP-898?page=all ]
nadir amra reassigned AXISCPP-898:
--
Assignee: nadir amra
simple problem with simpleTypes
---
Key: AXISCPP-898
URL: http
+{
+ writer.write(\tparam- + extensionBaseAttrib.
getParamNameAsMember() + = *( + typeName + *) pCharDa
ta;\n);
+}
}
writer.write(\treturn pIWSDZ-getStatus();\n);
[attachment feh.vcf deleted by Nadir Amra/Rochester/IBM
Project is probably more stable then axis2 at the moment, and is
continually being enhanced and fixes applied. Yes, you need to have an
axiscpp.conf file and you do have to set the AXISCPP_DEPLOY environment
variable. And I guess PATH environment variable should include paths to
the dlls or
[ http://issues.apache.org/jira/browse/AXISCPP-526?page=all ]
nadir amra updated AXISCPP-526:
---
Description:
It would be highly useful to be able to specify an independent response timeout
in addition to the connection timeout currently specifiable
[ http://issues.apache.org/jira/browse/AXISCPP-745?page=all ]
nadir amra closed AXISCPP-745.
--
Fix Version/s: unspecified
Resolution: Duplicate
Duplicate of AXISCPP-526
Use non-blocking receive in transport
Reporter: nadir amra
Assigned To: nadir amra
Priority: Minor
Fix For: 1.6 Beta
The copy constructors for SoapFaultException and OtherFaultException causes
warning messages to be issued on some platforms, causes an addition copy to be
made
[ http://issues.apache.org/jira/browse/AXISCPP-1007?page=all ]
nadir amra updated AXISCPP-1007:
Summary: Correct assignment operator (was: Correct copy constructors)
Description:
The assignment operators for SoapFaultException
[ http://issues.apache.org/jira/browse/AXISCPP-1007?page=all ]
nadir amra closed AXISCPP-1007.
---
Resolution: Fixed
Correct assignment operator
---
Key: AXISCPP-1007
URL: http://issues.apache.org
[ http://issues.apache.org/jira/browse/AXISCPP-1006?page=all ]
nadir amra reassigned AXISCPP-1006:
---
Assignee: nadir amra
The static const string 's declaration style is not very good(which will
cause g++ compiling warning) inside the generated
Haiping,
Just send me the .tar.gz and I can take a look and create individual fixes
and jira's. Then we can discuss any changes via jira's. Maybe a list of
the fixes and how it should be fixed strategically in the AXIS code-base
would be nice too :-) But that can be done later via jira
[ http://issues.apache.org/jira/browse/AXISCPP-1005?page=all ]
nadir amra closed AXISCPP-1005.
---
Resolution: Fixed
Memory leak in C-stub generation
Key: AXISCPP-1005
URL: http
[ http://issues.apache.org/jira/browse/AXISCPP-1003?page=all ]
nadir amra reassigned AXISCPP-1003:
---
Assignee: nadir amra
Enumeration with spaces in values generates invalid hpp file
[
http://issues.apache.org/jira/browse/AXISCPP-1003?page=comments#action_12443725
]
nadir amra commented on AXISCPP-1003:
-
I guess I have chosen the solution to be:
[type]_ENUM_[#]
For example,
static const FooType FooType_ENUM_1 = foo
Yes, please post the fixes or send directly to me and I can then merge in
the fixes for all to share. It would be appreciated.
Nadir K. Amra
Franz Fehringer [EMAIL PROTECTED] wrote on 10/20/2006 03:46:00 AM:
I sent the email direct to the original poster.
Was there any reaction om John
[
http://issues.apache.org/jira/browse/AXISCPP-1003?page=comments#action_12443991
]
nadir amra commented on AXISCPP-1003:
-
Michael, I will take your suggestion and be consistent with what java does,
which generates something like
[
http://issues.apache.org/jira/browse/AXISCPP-1004?page=comments#action_12443992
]
nadir amra commented on AXISCPP-1004:
-
Although I have done no work on the server side of things, I can probably
surmise why this is not working. Since
Just wondering how nightly builds are generated? Is this an automatic
process or does someone have to do something to get them to
http://people.apache.org/dist/axis/nightly/?
Nadir K. Amra
-
To unsubscribe, e-mail: [EMAIL
[ http://issues.apache.org/jira/browse/AXISCPP-1003?page=all ]
nadir amra resolved AXISCPP-1003.
-
Fix Version/s: 1.6 Beta
Resolution: Fixed
If all enum values are valid (can be used as a C/C++ identifer), it will be
used to generate enum's
:
Hello,
Is there any progress reagrding a Axis C++ 1.6 release (hopefully
containing a fix for my favourite JIRA AXISCPP-716)?
Best regards
Franz
[attachment feh.vcf deleted by Nadir Amra/Rochester/IBM
Beta
Reporter: nadir amra
Assigned To: nadir amra
Fix For: 1.6 Beta
For C-stub generation, when a complex structure contains an inner complex
structure, the the Axis_Create_() function creates the inner complex
structure by calling the appropriate function
[ http://issues.apache.org/jira/browse/AXISCPP-1005?page=all ]
nadir amra updated AXISCPP-1005:
Component/s: WSDL processing - Doc
(was: WSDD Processing)
Memory leak in C-stub generation
[
http://issues.apache.org/jira/browse/AXISCPP-1003?page=comments#action_12443705
]
nadir amra commented on AXISCPP-1003:
-
One way to fix this is ensureing that spaces get converted to '_'.
Probably a better way is for the enumeration
[
http://issues.apache.org/jira/browse/AXISCPP-1000?page=comments#action_12437044
]
nadir amra commented on AXISCPP-1000:
-
I can fix this but I guess I need some feedback from the expertsAXIS 2
folks and others. Please comment. I
[
http://issues.apache.org/jira/browse/AXISCPP-1000?page=comments#action_12437045
]
nadir amra commented on AXISCPP-1000:
-
Looking at the code, on the surface it seems to be a bug. Comparing doc
literal routines with encoded
cleanup in the relevant code recently this
one might be feasible for you?
Thanks and best regards
Franz
Nadir Amra schrieb:
I have never tried putting out a release but will try in October. If
someone else would be kind enough to give it a try, the sooner the
better.
Nadir K. Amra
[ http://issues.apache.org/jira/browse/AXISCPP-999?page=all ]
nadir amra closed AXISCPP-999.
--
Fix Version/s: 1.6 Beta
Resolution: Fixed
Segmentation fault in SOAPTransport.h
-
Key: AXISCPP-999
[ http://issues.apache.org/jira/browse/AXISCPP-999?page=all ]
nadir amra reassigned AXISCPP-999:
--
Assignee: nadir amra
Segmentation fault in SOAPTransport.h
-
Key: AXISCPP-999
URL
[ http://issues.apache.org/jira/browse/AXISCPP-994?page=all ]
nadir amra closed AXISCPP-994.
--
Resolution: Duplicate
AXISCPP-995
WSDL2Ws ignores attribute refs inside of attributeGroup
[ http://issues.apache.org/jira/browse/AXISCPP-998?page=all ]
nadir amra reassigned AXISCPP-998:
--
Assignee: nadir amra
wrong Host: HTTP request header when using HTTP proxy
---
Key
I can take a look at it but will not be able to for at least another
month since I am going on vacation.
Nadir K. Amra
Franz Fehringer [EMAIL PROTECTED] wrote on 08/15/2006 04:20:06 AM:
Hello Nadir,
After several rounds of improving and bug fixing (Johm Hawkins,
Adrian Dick and
I have never tried putting out a release but will try in October. If
someone else would be kind enough to give it a try, the sooner the better.
Nadir K. Amra
Kamlesh kumar [EMAIL PROTECTED] wrote on 08/14/2006 11:41:28 AM:
That's cool. Thanks for providing the complete fix.
BTW, Can
A more complete fix has been implemented, including a new method,
canParseMore() in the abstract base class that may be utilized in the
future. Basically bCanParseMore is saved in the class so that it is kept
across invocations...
Nadir K. Amra
Kamlesh kumar [EMAIL PROTECTED] wrote on
[
http://issues.apache.org/jira/browse/AXISCPP-770?page=comments#action_12427678
]
nadir amra commented on AXISCPP-770:
There was a problem with XMLParserXerces::next in that it invoked
m_pParser-parseNext(m_ScanToken) even when there may
[
http://issues.apache.org/jira/browse/AXISCPP-770?page=comments#action_12427679
]
nadir amra commented on AXISCPP-770:
I hope to have the code in SVN by Saturday morning, CDT.
const AnyElement* XMLParserXerces::next(bool isCharData
[ http://issues.apache.org/jira/browse/AXISCPP-770?page=all ]
nadir amra resolved AXISCPP-770.
Fix Version/s: 1.6 Beta
Resolution: Fixed
I adjusted the loop control for peek so it is now:
while (m_pParser-parseNext(m_ScanToken) AXIS_FAIL
I have fixed this problem. See AXISCPP-770 for details. Please try and
see if your problem persists by downloading code and testing.
Nadir K. Amra
Kamlesh kumar [EMAIL PROTECTED] wrote on 08/11/2006 09:41:21 PM:
The current implementation of XMLParserXerces ignores
the value returned
[ http://issues.apache.org/jira/browse/AXISCPP-973?page=all ]
nadir amra reassigned AXISCPP-973:
--
Assignee: nadir amra
WSDL2WS generate wrong code: for AXISCPP-972, getChardataAs((void*)...
should be getChardataAs((void
Content-Transfer-Encoding: 7bit
[ http://issues.apache.org/jira/browse/AXISCPP-972?page=all ]
nadir amra reassigned AXISCPP-972:
--
Assignee: nadir amra
axis-c deserializer has a problem:
axis-c deserializer: IWrapperSoapDeSerializer::getChardataAs 's
then we can avoid this issue. This value can be
initialized with the return value of
m_parser-parseFirst.
Let me know if I am not clear and I can try to provide
more details.
Thanks
-Kamlesh
--- Nadir Amra [EMAIL PROTECTED] wrote:
I have fixed this problem. See AXISCPP-770
Content-Transfer-Encoding: 7bit
[ http://issues.apache.org/jira/browse/AXISCPP-972?page=all ]
nadir amra resolved AXISCPP-972.
Fix Version/s: 1.6 Beta
Resolution: Fixed
Fixed this by changing prototype from:
getChardataAs (void * pValue, XSDTYPE
Content-Transfer-Encoding: 7bit
[ http://issues.apache.org/jira/browse/AXISCPP-972?page=all ]
nadir amra reopened AXISCPP-972:
I think I need to look into this a little bit more. I am closing the other
issues since basically it is a duplicate
[ http://issues.apache.org/jira/browse/AXISCPP-973?page=all ]
nadir amra reopened AXISCPP-973:
WSDL2WS generate wrong code: for AXISCPP-972, getChardataAs((void*)...
should be getChardataAs((void
[ http://issues.apache.org/jira/browse/AXISCPP-884?page=all ]
nadir amra updated AXISCPP-884:
---
Comment: was deleted
Couldn't output value from function parameter
-
Key: AXISCPP-884
[ http://issues.apache.org/jira/browse/AXISCPP-884?page=all ]
nadir amra reopened AXISCPP-884:
Couldn't output value from function parameter
-
Key: AXISCPP-884
[ http://issues.apache.org/jira/browse/AXISCPP-884?page=all ]
nadir amra closed AXISCPP-884.
--
Resolution: Duplicate
One issue should suffice for the getCharAsData problem. See AXISCPP-972.
Couldn't output value from function parameter
[ http://issues.apache.org/jira/browse/AXISCPP-947?page=all ]
nadir amra closed AXISCPP-947.
--
Resolution: Fixed
I assume this has been resolved. But there is already an issue (AXISCPP-75)
about the code needing to support conversion of data automagically
301 - 400 of 589 matches
Mail list logo
