[jira] Commented: (AXIS2-3733) Autogenerated WSDL misses element if POJO function has no parameters

[ https://issues.apache.org/jira/browse/AXIS2-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12834356#action_12834356 ] nadir amra commented on AXIS2-3733: --- I would like to fix this and was wondering if anyone

[jira] Created: (AXISCPP-1064) Parser gets confused when expected element is not there

Parser gets confused when expected element is not there --- Key: AXISCPP-1064 URL: https://issues.apache.org/jira/browse/AXISCPP-1064 Project: Axis-C++ Issue Type: Bug

[jira] Resolved: (AXISCPP-1064) Parser gets confused when expected element is not there

[ https://issues.apache.org/jira/browse/AXISCPP-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-1064. - Resolution: Fixed Fixed under revision 902922

[jira] Closed: (AXISCPP-235) Provide C samples

[ https://issues.apache.org/jira/browse/AXISCPP-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-235. -- Resolution: Incomplete Closing this issue since description is incomplete. Provide C samples

[jira] Updated: (AXISCPP-1063) Add support for xsd:union

[ https://issues.apache.org/jira/browse/AXISCPP-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-1063: Component/s: XSD Types Add support for xsd:union -

[jira] Commented: (AXISCPP-899) tunnel https connections over http proxies

[ https://issues.apache.org/jira/browse/AXISCPP-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12776660#action_12776660 ] nadir amra commented on AXISCPP-899: Merged the code into SVN code-base. Will wait

[jira] Reopened: (AXIS2-4440) excludeOperations with static WSDL does not work

[ https://issues.apache.org/jira/browse/AXIS2-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra reopened AXIS2-4440: --- That is fine...which means the operation cannot be invoked. The semantics of excluding operations from

[jira] Created: (AXISCPP-1063) Add support for xsd:union

Add support for xsd:union - Key: AXISCPP-1063 URL: https://issues.apache.org/jira/browse/AXISCPP-1063 Project: Axis-C++ Issue Type: New Feature Reporter: nadir amra support xsd:union. -- This message

[jira] Created: (AXIS2-4440) excludeOperations with static WSDL does not work

excludeOperations with static WSDL does not work Key: AXIS2-4440 URL: https://issues.apache.org/jira/browse/AXIS2-4440 Project: Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.3,

[jira] Commented: (AXIS2-3724) WSDL complex type elements do not comply to JAXB Java bean

[ https://issues.apache.org/jira/browse/AXIS2-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12713688#action_12713688 ] nadir amra commented on AXIS2-3724: --- So is this going to be fixed anytime soon? Or can

[jira] Commented: (AXISCPP-964) SOAP request/response not UTF-8 encoded (but claims to be)

[ https://issues.apache.org/jira/browse/AXISCPP-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12673419#action_12673419 ] nadir amra commented on AXISCPP-964: The other option is to have user put character

[jira] Commented: (AXISCPP-964) SOAP request/response not UTF-8 encoded (but claims to be)

[ https://issues.apache.org/jira/browse/AXISCPP-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12673421#action_12673421 ] nadir amra commented on AXISCPP-964: And yes another option is to have user specify

[jira] Assigned: (AXISCPP-899) tunnel https connections over http proxies

[ https://issues.apache.org/jira/browse/AXISCPP-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra reassigned AXISCPP-899: -- Assignee: nadir amra tunnel https connections over http proxies

[jira] Created: (AXISCPP-1061) Client does not work when running ebcdic turkish code page

Client does not work when running ebcdic turkish code page -- Key: AXISCPP-1061 URL: https://issues.apache.org/jira/browse/AXISCPP-1061 Project: Axis-C++ Issue Type: Bug

[jira] Closed: (AXISCPP-1061) Client does not work when running ebcdic turkish code page

[ https://issues.apache.org/jira/browse/AXISCPP-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-1061. --- Resolution: Fixed Fiexed in revision 733631

[jira] Issue Comment Edited: (AXISCPP-100) enable axis c++ (engine) tracing

[ https://issues.apache.org/jira/browse/AXISCPP-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12647434#action_12647434 ] nadiramra edited comment on AXISCPP-100 at 11/20/08 2:16 PM: --

[jira] Created: (AXISCPP-1060) xsd:anyType as input or output with -wunwrapped generated bad code.

xsd:anyType as input or output with -wunwrapped generated bad code. - Key: AXISCPP-1060 URL: https://issues.apache.org/jira/browse/AXISCPP-1060 Project: Axis-C++ Issue

[jira] Closed: (AXISCPP-100) enable axis c++ (engine) tracing

[ https://issues.apache.org/jira/browse/AXISCPP-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-100. -- Resolution: Fixed Fix Version/s: current (nightly) OK, finally got this done. Tracing is now

[jira] Issue Comment Edited: (AXISCPP-100) enable axis c++ (engine) tracing

[ https://issues.apache.org/jira/browse/AXISCPP-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12647434#action_12647434 ] nadiramra edited comment on AXISCPP-100 at 11/13/08 2:52 PM: --

[jira] Closed: (AXISCPP-424) Throw trace

[ https://issues.apache.org/jira/browse/AXISCPP-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-424. -- Resolution: Fixed Fix Version/s: current (nightly) Resolved by AXISCPP-100 Throw trace

[jira] Closed: (AXISCPP-643) Trace the SOAP response message

[ https://issues.apache.org/jira/browse/AXISCPP-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-643. -- Resolution: Fixed Fix Version/s: current (nightly) Resolved by AXISCPP-100 Trace the SOAP

[jira] Closed: (AXISCPP-422) Trace calls to wrappers and handlers

[ https://issues.apache.org/jira/browse/AXISCPP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-422. -- Resolution: Fixed Resolved by AXISCPP-100 Trace calls to wrappers and handlers

[jira] Updated: (AXISCPP-729) Trace: Unwind the call stack when exceptions are thrown

[ https://issues.apache.org/jira/browse/AXISCPP-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-729: --- Issue Type: Improvement (was: Bug) Trace: Unwind the call stack when exceptions are thrown

[jira] Closed: (AXISCPP-646) Traced instance methods sometimes appear as static

[ https://issues.apache.org/jira/browse/AXISCPP-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-646. -- Resolution: Won't Fix Revamping trace support - instance at this time will not be traced. Traced

[jira] Closed: (AXISCPP-728) Trace: better multiline output

[ https://issues.apache.org/jira/browse/AXISCPP-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-728. -- Resolution: Won't Fix Trace: better multiline output --

[jira] Closed: (AXISCPP-641) Trace output parameters on methods

[ https://issues.apache.org/jira/browse/AXISCPP-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-641. -- Resolution: Won't Fix I am working on revamping tracing so that tracing will already be embedded in

[jira] Closed: (AXISCPP-423) Optionally instrument the testcases and generated code with trace

[ https://issues.apache.org/jira/browse/AXISCPP-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-423. -- Resolution: Won't Fix There really is no benefit to thisif we need to trace a test case, it can

[jira] Closed: (AXISCPP-744) Trace: no returnIndex set in SoapDeSerializer::getElement

[ https://issues.apache.org/jira/browse/AXISCPP-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-744. -- Resolution: Won't Fix I am revamping the tracing support so no instrumentation is required. The

[jira] Closed: (AXISCPP-941) windows compilerarg

[ https://issues.apache.org/jira/browse/AXISCPP-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-941. -- Resolution: Incomplete I guess I am not sure what has or has not been done. So I will close issue

[jira] Commented: (AXISCPP-882) Use C++ namespaces to prevent symbol collisions

[ https://issues.apache.org/jira/browse/AXISCPP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12638312#action_12638312 ] nadir amra commented on AXISCPP-882: Moving comment from AXISCPP-553 to here. I

[jira] Issue Comment Edited: (AXISCPP-882) Use C++ namespaces to prevent symbol collisions

[ https://issues.apache.org/jira/browse/AXISCPP-882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12638312#action_12638312 ] nadiramra edited comment on AXISCPP-882 at 10/9/08 9:03 AM: -

[jira] Updated: (AXISCPP-533) Inter shared library exception handling broken on Linux

[ https://issues.apache.org/jira/browse/AXISCPP-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-533: --- Comment: was deleted Inter shared library exception handling broken on Linux

[jira] Updated: (AXISCPP-533) Inter shared library exception handling broken on Linux

[ https://issues.apache.org/jira/browse/AXISCPP-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-533: --- Comment: was deleted Inter shared library exception handling broken on Linux

[jira] Resolved: (AXISCPP-1002) Support for xsd:anyType

[ https://issues.apache.org/jira/browse/AXISCPP-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-1002. - Resolution: Fixed Fix Version/s: current (nightly) Testing complete. Will close when I

[jira] Commented: (AXISCPP-1002) Support for xsd:anyType

[ https://issues.apache.org/jira/browse/AXISCPP-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12638136#action_12638136 ] nadir amra commented on AXISCPP-1002: - I believe it has been implemented in SVN

[jira] Updated: (AXISCPP-663) Element values not escaped when using getAnyObject()

[ https://issues.apache.org/jira/browse/AXISCPP-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-663: --- Summary: Element values not escaped when using getAnyObject() (was: Deserializing a Complex

[jira] Resolved: (AXISCPP-663) Element values not escaped when using getAnyObject()

[ https://issues.apache.org/jira/browse/AXISCPP-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-663. Resolution: Fixed Element values that contain restricted characters are now escaped. Changes are

[jira] Issue Comment Edited: (AXISCPP-1002) Support for xsd:anyType

[ https://issues.apache.org/jira/browse/AXISCPP-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628780#action_12628780 ] nadiramra edited comment on AXISCPP-1002 at 10/3/08 1:54 PM: --

[jira] Closed: (AXISCPP-1055) Memory Leak in SoapSerializer::addOutputParam()

[ https://issues.apache.org/jira/browse/AXISCPP-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-1055. --- Resolution: Invalid xsdValue is passed to Param object using: pParam-setValue(type, xsdValue);

[jira] Closed: (AXISCPP-1052) Memory Leak in XSD Types - missing virtual destructor definition in header files

[ https://issues.apache.org/jira/browse/AXISCPP-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-1052. --- Resolution: Fixed Thanks for the input. Fixed in SVN revision 700954

[jira] Closed: (AXISCPP-1057) Memory Leak in XercesHandler destructor

[ https://issues.apache.org/jira/browse/AXISCPP-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-1057. --- Resolution: Fixed Thanks for the input. Fixed in SVN revision 700965

[jira] Reopened: (AXISCPP-574) Not all of the cpp, c, hpp h files have Apache Copyright statements

[ https://issues.apache.org/jira/browse/AXISCPP-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra reopened AXISCPP-574: I am reopening issue in order to remove all copyrights from the generated code. I do not believe

[jira] Closed: (AXISCPP-574) Not all of the cpp, c, hpp h files have Apache Copyright statements

[ https://issues.apache.org/jira/browse/AXISCPP-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-574. -- Resolution: Fixed Not all of the cpp, c, hpp h files have Apache Copyright statements

[jira] Updated: (AXISCPP-574) Not all of the cpp, c, hpp h files have Apache Copyright statements

[ https://issues.apache.org/jira/browse/AXISCPP-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-574: --- Comment: was deleted Not all of the cpp, c, hpp h files have Apache Copyright statements

[jira] Commented: (AXISCPP-1002) Support for xsd:anyType

[ https://issues.apache.org/jira/browse/AXISCPP-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628419#action_12628419 ] nadir amra commented on AXISCPP-1002: - Just adding a little bit of information

[jira] Issue Comment Edited: (AXISCPP-1002) Support for xsd:anyType

[ https://issues.apache.org/jira/browse/AXISCPP-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12628419#action_12628419 ] nadiramra edited comment on AXISCPP-1002 at 9/4/08 11:18 AM: --

[jira] Resolved: (AXISCPP-552) Eleminate the WSDL tool expeting the Service to be mandatory in WSDL

[ https://issues.apache.org/jira/browse/AXISCPP-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-552. Resolution: Fixed Fix Version/s: current (nightly) Resolved by adding a -b (binding-name)

[jira] Resolved: (AXISCPP-1051) Bad code generated for several Cisco Call Manager WSDL

[ https://issues.apache.org/jira/browse/AXISCPP-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-1051. - Resolution: Fixed Fix Version/s: current (nightly) Issue resolved. Updates in SVN

[jira] Resolved: (AXISCPP-1050) generated bean constructor(), destructor() and reset() methods not consistent

[ https://issues.apache.org/jira/browse/AXISCPP-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-1050. - Resolution: Fixed Fix Version/s: current (nightly) Done. In addition, constructors no

[jira] Resolved: (AXISCPP-623) Support for the WSDL construct all

[ https://issues.apache.org/jira/browse/AXISCPP-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-623. Resolution: Fixed Fix Version/s: current (nightly) The solution was to put all-group

[jira] Resolved: (AXISCPP-888) Deserializer does give any indication of error when tags not in the WSDL are encountered.

[ https://issues.apache.org/jira/browse/AXISCPP-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-888. Resolution: Fixed Fix Version/s: current (nightly) In the complex type derializer, we now

[jira] Issue Comment Edited: (AXISCPP-623) Support for the WSDL construct all

[ https://issues.apache.org/jira/browse/AXISCPP-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12615410#action_12615410 ] nadiramra edited comment on AXISCPP-623 at 7/21/08 1:40 PM: -

[jira] Issue Comment Edited: (AXISCPP-888) Deserializer does give any indication of error when tags not in the WSDL are encountered.

[ https://issues.apache.org/jira/browse/AXISCPP-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12615412#action_12615412 ] nadiramra edited comment on AXISCPP-888 at 7/21/08 1:39 PM: -

[jira] Issue Comment Edited: (AXISCPP-888) Deserializer does give any indication of error when tags not in the WSDL are encountered.

[ https://issues.apache.org/jira/browse/AXISCPP-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12615412#action_12615412 ] nadiramra edited comment on AXISCPP-888 at 7/21/08 1:45 PM: -

[jira] Closed: (AXISCPP-1002) Support for xsi:type when serializing complex objects and arrays of complex objects.

[ https://issues.apache.org/jira/browse/AXISCPP-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-1002. --- Resolution: Incomplete Not sure exactly what the problem isthe commentary in the issue

[jira] Reopened: (AXISCPP-1002) Support for xsi:type when serializing complex objects and arrays of complex objects.

[ https://issues.apache.org/jira/browse/AXISCPP-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra reopened AXISCPP-1002: - I guess I am going to reopen and change the description os xsd:anyType. I assume that is the

[jira] Updated: (AXISCPP-1002) Support for xsd:anyType

[ https://issues.apache.org/jira/browse/AXISCPP-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-1002: Summary: Support for xsd:anyType (was: Support for xsi:type when serializing complex objects

[jira] Created: (AXISCPP-1050) generated bean constructor(), destructor() and reset() methods not consistent

generated bean constructor(), destructor() and reset() methods not consistent - Key: AXISCPP-1050 URL: https://issues.apache.org/jira/browse/AXISCPP-1050 Project: Axis-C++

[jira] Closed: (AXIS2-3920) Allow to disable HTTP binding at service level using a parameter in services.xml

[ https://issues.apache.org/jira/browse/AXIS2-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXIS2-3920. - Resolution: Duplicate Duplicate of AXIS2-3114 Allow to disable HTTP binding at service level using a

[jira] Issue Comment Edited: (AXISCPP-894) Elements in the generated request message is not namespace qualified even if value of 'elementFormDefault' attribute in the schema is 'qualified'

[ https://issues.apache.org/jira/browse/AXISCPP-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12613016#action_12613016 ] nadiramra edited comment on AXISCPP-894 at 7/15/08 7:42 PM: -

[jira] Closed: (AXISCPP-879) UDDI inquiry API 'get_tModelDetail()' does not return all the deatils of Technical Model correctly.

[ https://issues.apache.org/jira/browse/AXISCPP-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-879. -- Resolution: Cannot Reproduce Fix Version/s: current (nightly) Seems to be fixed. I had to

[jira] Resolved: (AXISCPP-894) Elements in the generated request message is not namespace qualified even if value of 'elementFormDefault' attribute in the schema is 'qualified'

[ https://issues.apache.org/jira/browse/AXISCPP-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-894. Resolution: Fixed Fix Version/s: current (nightly) Problem resolved. Basically the

[jira] Closed: (AXISCPP-607) Nested namespace prefixes

[ https://issues.apache.org/jira/browse/AXISCPP-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-607. -- Resolution: Fixed This particular issue relating to elements has been resolved by AXISCPP-894.

[jira] Closed: (AXISCPP-672) WSDL2Ws fails when message has no parts

[ https://issues.apache.org/jira/browse/AXISCPP-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-672. -- Resolution: Cannot Reproduce Fix Version/s: current (nightly) WSDL2Ws fails when message has

[jira] Closed: (AXISCPP-761) AXIS C++ allows empty URI for anyURI

[ https://issues.apache.org/jira/browse/AXISCPP-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-761. -- Resolution: Duplicate duplicated byAXISCPP-789. AXIS C++ allows empty URI for anyURI

[jira] Updated: (AXISCPP-987) wsdl parameter ordering not preserved

[ https://issues.apache.org/jira/browse/AXISCPP-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-987: --- Component/s: (was: WSDD Processing) WSDL processing - RPC WSDL

[jira] Commented: (AXISCPP-458) Unwrapped not supported.

[ https://issues.apache.org/jira/browse/AXISCPP-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12612147#action_12612147 ] nadir amra commented on AXISCPP-458: Found out attributes on wrapper element was not

[jira] Closed: (AXISCPP-1013) AxisConfiguration requires subsystem=console

[ https://issues.apache.org/jira/browse/AXISCPP-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-1013. --- Resolution: Fixed Completed under SVN revision 675233 AxisConfiguration requires

[jira] Closed: (AXISCPP-997) WSDL2WS Doesn't take care of safe names for types or defined in wsld file

[ https://issues.apache.org/jira/browse/AXISCPP-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-997. -- Resolution: Cannot Reproduce When I define a type such as auth-token, the generated type is

[jira] Updated: (AXISCPP-996) WSDL2ws support of Schema redefine tag

[ https://issues.apache.org/jira/browse/AXISCPP-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-996: --- Priority: Major (was: Blocker) I do not consider this a blocker. Lowering priority. WSDL2ws

[jira] Updated: (AXISCPP-771) Why Axis C++ doesn't support initialize_module() in dual mode, server and client at the same time?

[ https://issues.apache.org/jira/browse/AXISCPP-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-771: --- Priority: Major (was: Blocker) I do not consider this a blocker, lowering priority. Why Axis C++

[jira] Resolved: (AXISCPP-1044) The use of ref inside WSDL schemas is not supported.

[ https://issues.apache.org/jira/browse/AXISCPP-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-1044. - Resolution: Fixed Fix Version/s: current (nightly) Issue is now resolved - at least no

[jira] Resolved: (AXISCPP-458) Unwrapped not supported.

[ https://issues.apache.org/jira/browse/AXISCPP-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-458. Resolution: Fixed First let me say that wrapper-style vs. non-wrapper style is not a server-side

[jira] Issue Comment Edited: (AXISCPP-458) Unwrapped not supported.

[ https://issues.apache.org/jira/browse/AXISCPP-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12610269#action_12610269 ] nadiramra edited comment on AXISCPP-458 at 7/3/08 9:17 AM:

[jira] Resolved: (AXISCPP-716) Support for the attribute construct 'use'

[ https://issues.apache.org/jira/browse/AXISCPP-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-716. Resolution: Fixed This is now fixed under SVN revision 673900. Extension attributes are now

[jira] Closed: (AXISCPP-900) Attributes not settable for webservice incvocation

[ https://issues.apache.org/jira/browse/AXISCPP-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-900. -- Resolution: Fixed Fix Version/s: current (nightly) With the resolution of AXISCPP-458 , this

[jira] Closed: (AXISCPP-401) Complete C support after 1.5

[ https://issues.apache.org/jira/browse/AXISCPP-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-401. -- Resolution: Fixed Fix Version/s: current (nightly) I am closing this issue since implement C

[jira] Closed: (AXISCPP-983) Windows Mobile

[ https://issues.apache.org/jira/browse/AXISCPP-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-983. -- Resolution: Incomplete Not sure what needs to be done. If there is more information, let us know.

[jira] Closed: (AXISCPP-984) Windows CE

[ https://issues.apache.org/jira/browse/AXISCPP-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-984. -- Resolution: Incomplete Not sure what needs to be done. if there is something that needs to be done,

[jira] Closed: (AXISCPP-907) glitches in build system

[ https://issues.apache.org/jira/browse/AXISCPP-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-907. -- Resolution: Incomplete I am assuming there is nothing to fix here. If there is, please indicate

[jira] Created: (AXISCPP-1049) Add ability to do REST requests from client

Add ability to do REST requests from client --- Key: AXISCPP-1049 URL: https://issues.apache.org/jira/browse/AXISCPP-1049 Project: Axis-C++ Issue Type: New Feature Components: Client - API

[jira] Updated: (AXISCPP-458) Unwrapped not supported.

[ https://issues.apache.org/jira/browse/AXISCPP-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-458: --- Component/s: (was: WSDL processing - RPC) Fix Version/s: (was: 1.6 Alpha)

[jira] Commented: (AXISCPP-900) Attributes not settable for webservice incvocation

[ https://issues.apache.org/jira/browse/AXISCPP-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608490#action_12608490 ] nadir amra commented on AXISCPP-900: This will be fixed soon. Now that I understand

[jira] Updated: (AXISCPP-227) does not create classes with inheritance

[ https://issues.apache.org/jira/browse/AXISCPP-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-227: --- Component/s: WSDL processing - Doc does not create classes with inheritance

[jira] Closed: (AXISCPP-1048) WSDL2Ws code - deleted primitive return type pointers

[ https://issues.apache.org/jira/browse/AXISCPP-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-1048. --- Resolution: Fixed Fix Version/s: current (nightly) Actually the problem was in the

[jira] Closed: (AXISCPP-1040) Method declarations that have array parameters do not match method implementation

[ https://issues.apache.org/jira/browse/AXISCPP-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-1040. --- Resolution: Fixed Fix Version/s: current (nightly) Fixed. Method declarations that have

[jira] Closed: (AXISCPP-1039) Code Generation re-initializes array variables with the same name.

[ https://issues.apache.org/jira/browse/AXISCPP-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-1039. --- Resolution: Fixed Fix Version/s: current (nightly) This has been fixed for a while in the

[jira] Closed: (AXISCPP-1038) Compile source

[ https://issues.apache.org/jira/browse/AXISCPP-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-1038. --- Resolution: Won't Fix Use ant build process to generate the artifacts. Compile source

[jira] Closed: (AXISCPP-1033) No way to turn off: Warning - The configuration file was not found

[ https://issues.apache.org/jira/browse/AXISCPP-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-1033. --- Resolution: Fixed Fix Version/s: (was: 1.6 Beta) current (nightly)

[jira] Closed: (AXISCPP-1045) getting segmentation fault in the axiscpp::SoapDeSerializer::getElementAsString while running multiple client instances to access large XML list about 1500 nodes returned

[ https://issues.apache.org/jira/browse/AXISCPP-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-1045. --- Resolution: Cannot Reproduce Please use latest code in SVN...hopefully later this year a 1.6

[jira] Closed: (AXISCPP-966) WSDL2WS generate wrong code: redundant value reference * in Wrapper

[ https://issues.apache.org/jira/browse/AXISCPP-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-966. -- Resolution: Fixed Fix Version/s: current (nightly) I believe the initial issue is fixed. The

[jira] Updated: (AXISCPP-970) axis-c engine: nillable problem: when minOccurs=0 and nillable=false, the serailization does NOT follow W3C schema standard

[ https://issues.apache.org/jira/browse/AXISCPP-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-970: --- Comment: was deleted axis-c engine: nillable problem: when minOccurs=0 and nillable=false, the

[jira] Updated: (AXISCPP-970) axis-c engine: nillable problem: when minOccurs=0 and nillable=false, the serailization does NOT follow W3C schema standard

[ https://issues.apache.org/jira/browse/AXISCPP-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-970: --- Comment: was deleted axis-c engine: nillable problem: when minOccurs=0 and nillable=false, the

[jira] Commented: (AXISCPP-970) axis-c engine: nillable problem: when minOccurs=0 and nillable=false, the serailization does NOT follow W3C schema standard

[ https://issues.apache.org/jira/browse/AXISCPP-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598810#action_12598810 ] nadir amra commented on AXISCPP-970: For a truly optional element, one that is allowed

[jira] Updated: (AXISCPP-970) axis-c engine: nillable problem: when minOccurs=0 and nillable=false, the serailization does NOT follow W3C schema standard

[ https://issues.apache.org/jira/browse/AXISCPP-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-970: --- Comment: was deleted axis-c engine: nillable problem: when minOccurs=0 and nillable=false, the

[jira] Updated: (AXISCPP-970) axis-c engine: nillable problem: when minOccurs=0 and nillable=false, the serailization does NOT follow W3C schema standard

[ https://issues.apache.org/jira/browse/AXISCPP-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-970: --- Description: [Introduction]: Maybe you have known that, the axis-c-1.5final's nillable dealing is

[jira] Updated: (AXISCPP-333) WSDL2ws doesn't handle complex Array types correctly when nested or when returning as AXIS_OUT_PARAM

[ https://issues.apache.org/jira/browse/AXISCPP-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-333: --- Comment: was deleted WSDL2ws doesn't handle complex Array types correctly when nested or when

[jira] Resolved: (AXISCPP-333) WSDL2ws doesn't handle complex Array types correctly when nested or when returning as AXIS_OUT_PARAM

[ https://issues.apache.org/jira/browse/AXISCPP-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra resolved AXISCPP-333. Resolution: Fixed Fix Version/s: current (nightly) WSDL2ws doesn't handle complex Array

[jira] Closed: (AXISCPP-893) get_BusinessDetail() Inquiry API fails to return more than one BusinessEntity

[ https://issues.apache.org/jira/browse/AXISCPP-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra closed AXISCPP-893. -- Resolution: Cannot Reproduce get_BusinessDetail() Inquiry API fails to return more than one

[jira] Updated: (AXISCPP-630) Can Axis C++ 1.5 customize access URL without changing code?

[ https://issues.apache.org/jira/browse/AXISCPP-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-630: --- Component/s: Server - Apache module Can Axis C++ 1.5 customize access URL without changing code?

  1   2   3   4   5   >