[
https://issues.apache.org/jira/browse/AXIS2-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishanthan Thangarajah updated AXIS2-5239:
--
Fix Version/s: 1.7.0
> Upgrade Axis2 to use xmlschema2
> -
[
https://issues.apache.org/jira/browse/AXIS2-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishanthan Thangarajah reassigned AXIS2-5239:
-
Assignee: Kishanthan Thangarajah
> Upgrade Axis2 to use xmlschema2
> ---
Jake
I think you've touched upon a common ailment for all software
deployables..exhausting resources
There have been a few ideas kicked around..most notably
check if requested_allocation <=available_heap
the problem is determining available heap varies with each OS and ARCH type so..
a comp
Hi.
We are using version 1.6.2 of the Axis2/Java framework to generate C
code for use with Axis2/C, from some WSDL service descriptions. We have
noticed that the generated code does not always check the return value
of memory allocations, and there is therefore a risk of null pointer
de-referen