Hi devs,
The following is a map of xml schema data types and the axis2/c data types
to used in the codegen. Currently most of them are not implemented correctly
and should be finished before the interop tests.
3.2 Primitive datatypes[1]
3.2.1 string - axis2_char_t *
3.2.2
bug in fuction axis2_http_svr_thread_is_running() in
src/core/transport/http/receiver/http_svr_thread.c
---
Key: AXIS2C-735
URL:
+1.
keith chapman wrote:
Hi Devs,
Currently the method signature for det/get documentation in
AxisDescriptio is as follows.
public String getDocumentation();
public void setDocumentation(String documentation);
As you can see it treats the documentation as a string. There are
Documentation/samples are not up-to-date with Callback API changes
--
Key: AXIS2-3306
URL: https://issues.apache.org/jira/browse/AXIS2-3306
Project: Axis 2.0 (Axis2)
Issue
[
https://issues.apache.org/jira/browse/AXIS2-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537890
]
Charitha Kankanamge commented on AXIS2-3307:
Please check bug id=AXIS2-3255 for more information.
Incorrect configuration in maven-wsdl2code-plugin.html doc
--
Key: AXIS2-3307
URL: https://issues.apache.org/jira/browse/AXIS2-3307
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Well, +1 except for the fact that you can't overload getDocumentation()
and just change the return type - so there's no way to deprecate that
one without adding another method like getDocumentationOM(). We could
either do that and avoid breaking existing stuff, or just change
SOAP header block attributes
Key: AXIS2-3308
URL: https://issues.apache.org/jira/browse/AXIS2-3308
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.3
+1 for changing getDocumentation to return OMNode (no deprecation, same will
have to go for setDocumentation). Although this is an API method its mostly
used from within for generating the WSDL.
Thanks,
Keith.
On 10/26/07, Glen Daniels [EMAIL PROTECTED] wrote:
Well, +1 except for the fact that
Hi Srinath,
Please have a look http://wso2.org/library/91,
This article test each other with
- Axis1 WSDL2Java generated code
- Axis2 WSDL2Java generated code with ADB data binding (Axis2's simple
built-in databinding)
- Axis2 WSDL2Java generated code with Apache XMLBeans data
Hi Sadakith;
Do you know how many clients where use for these figures?, Actually
Thilina pointed this out to me. But I did not figure out how many
clients were used.
Thanks
Srinath
On 10/26/07, Lahiru Sandakith [EMAIL PROTECTED] wrote:
Hi Srinath,
Please have a look
Removing String as an argument type seems like a bad idea to me for two
reasons:
1. Breaking API compatibility, if it is public, is not nice.
2. If I want to put a string there (which I think you are saying goes in
the documentation elements of the WSDL) you are making me create
another
Hi all,
We have a program that consumes external web services using Axis. I am
currently upgrading the program to use Axis2. Our program works with Web
Services that are of RPC Encoded Style as well ( besides doc/literal). I
followed the examples and the java documentation but I am not clear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Robert,
Yes it is not broken. But why do we wanna limp with it? If we had used a
separate, say String class without using java.lang.String, do you wanna
keep it, if java.lang.String serves the purpose.
Look at how pain it is to deal with numerous
14 matches
Mail list logo
