Hi
We are building axis2c on AIX and we are facing some build problems.
There were lot of compilation issues. I was able to solve them by following
the instructions from this Jira issue.
http:
//mail-archives.apache.org/mod_mbox/ws-axis-c-dev/200810.mbox/%3C1C5078180E92E9
I think required libraries for Rampart/c are not in your path i.e. openssl.
Try depends.exe and make sure all the dlls required by rampart/c is in path.
Supun
On Thu, Mar 12, 2009 at 5:19 AM, Raymond Zhou raywang...@yahoo.com wrote:
Hi All,
I downloaded axis2/c 1.4 binary build and rampart/c
Shared library loading routines are platform dependent. You may need to
change them according to your platform.
Supun.
On Thu, Mar 12, 2009 at 12:21 PM, PP patelprad...@gmail.com wrote:
Hi
We are building axis2c on AIX and we are facing some build problems.
There were lot of compilation
Hi,
Rampart/C 1.2 binary was built using openssl 0.9.8d. It will only work with
versions 0.9.8d or 0.9.8e. If you have any other version, you have to get
the Rampart/C source and build.
Regards,
Shankar
On Thu, Mar 12, 2009 at 5:49 AM, Raymond Zhou raywang...@yahoo.com wrote:
Hi All,
I
Hi All,
I am using axis2/c Version 1.5 and rampart/c version 1.2 to build a WS client.
I built a debug version binaries from source code. When I go through the
rampart/c test cases,
I am getting this access violation consistently. It happens only when I made a
mistake, for example, using
Please check weather the client and server policies are matching. It seems
that server doesn't accept time stamp and client generates a time stamp.
Supun
On Fri, Mar 13, 2009 at 10:51 AM, Raymond Zhou raywang...@yahoo.com wrote:
Hi All,
I am using axis2/c Version 1.5 and rampart/c version
downloads for axis2 (1.3) are corrupted
---
Key: AXIS2-4268
URL: https://issues.apache.org/jira/browse/AXIS2-4268
Project: Axis 2.0 (Axis2)
Issue Type: Test
Affects Versions: M1
Environment:
[
https://issues.apache.org/jira/browse/AXIS2-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681321#action_12681321
]
Dobri Kitipov commented on AXIS2-3265:
--
Hi everybody,
I think this is fixed. I can see
I have written both a request handler and a response handler for calling a
web service using Apache Axis 1.4.
The request handler is working, but when the web service returns a soap
fault, my response handler is not getting called (I have set breakpoints in
both the onFault and invoke methods of
[
https://issues.apache.org/jira/browse/AXIS2-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3265.
--
Resolution: Fixed
If that is the case let's close this.
Thank you,
Deepal
[
https://issues.apache.org/jira/browse/AXIS2-4268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-4268.
--
Resolution: Fixed
How about using Axis2 1.4 ?
Thank you!
Deepal
downloads for axis2
[
https://issues.apache.org/jira/browse/AXIS2-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-4261.
--
Resolution: Fixed
Thank you very much for submitting the path, if you can please try
These articles on The OxygenTank http://wso2.org by Eran Chinthaka
should be helpful to understand Axis2 code generation its
parameters:
1.
http://wso2.org/library/tutorials/reference-guide-axis2-code-generation-parameters-part-1
2.
Axis2 - XMLBeasn path naming inconsistencies
Key: AXIS2-4269
URL: https://issues.apache.org/jira/browse/AXIS2-4269
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Tools
[
https://issues.apache.org/jira/browse/AXIS2-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Barrs updated AXIS2-4269:
Summary: Axis2 - XMLBeans path naming inconsistencies (was: Axis2 -
XMLBeasn path naming
[
https://issues.apache.org/jira/browse/AXIS2-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681412#action_12681412
]
Andreas Veithen commented on AXIS2-4261:
Note that the previous version of the
Prefix used to escape restricted words in part of a namespace is hardcoded,
unconfigurable.
---
Key: AXIS2-4270
URL: https://issues.apache.org/jira/browse/AXIS2-4270
[
https://issues.apache.org/jira/browse/AXIS2-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-3791.
-
Resolution: Duplicate
DUP of AXIS2-3908
Endlesloop in AxisServlet init
[
https://issues.apache.org/jira/browse/AXIS2-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12681592#action_12681592
]
Charith Dhanushka Wickramarachchi commented on AXIS2-4261:
--
Hi
hi,
I did not have much time to spend with Axis2 since I was busy with some
other work.
But not I am getting some time.
Are there any pending blockers for 1.5? if so I can have look at them.
Otherwise can start testing with the branch.
Can we do the release by the end of March?
thanks,
Amila.
20 matches
Mail list logo