Hi devs,
I get the following error when I build the trunk. What may be the cause of
this error?.
Embedded error:
E:\apache\webservices\axis2\java\trunk\modules\jaxws-integration\target\test-classes\servicejars\AppleFinderService
not found.
Thanks,
Danushka
--
Danushka Menikkumbura
Technical
,
Hiranya
On Tue, Jan 19, 2010 at 12:21 PM, Danushka Menikkumbura danus...@wso2.com
wrote:
Hi devs,
I get the following error when I build the trunk. What may be the cause of
this error?.
Embedded error:
E:\apache\webservices\axis2\java\trunk\modules\jaxws-integration\target\test
[
https://issues.apache.org/jira/browse/AXIS2C-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12797568#action_12797568
]
Danushka Menikkumbura commented on AXIS2C-1429:
---
-pthread sets flags
it.
How do you handle this situation in your implementation?.
Danushka
--
Danushka Menikkumbura
Technical Lead, WSO2 Inc.
blog : http://danushka-menikkumbura.blogspot.com/
http://wso2.com/ - The Open Source SOA Company
I tested the binary artifact on Windows.
Here is my +1.
Danushka
--
Danushka Menikkumbura
Technical Lead, WSO2 Inc.
blog : http://danushka-menikkumbura.blogspot.com/
http://wso2.com/ - The Open Source SOA Company
are fine please vote for Axis2/C 1.6.0 release.
Here is my vote +1.
Thanks,
-Manjula
--
Danushka Menikkumbura
Technical Lead, WSO2 Inc.
blog : http://danushka-menikkumbura.blogspot.com/
http://wso2.com/ - The Open Source SOA Company
Hi Devs,
The op_client property reuse is set to false inside
axis2_op_client_add_msg_ctx so that this has to be enabled for every
single op_client call. Should not this be a client-level setting that
ought to be reset explicitly?.
Danushka
--
Danushka Menikkumbura
Technical Lead, WSO2 Inc
[
https://issues.apache.org/jira/browse/AXIS2C-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura closed AXIS2C-1104.
-
Name collision when using axutil_dir_windows.h
[
https://issues.apache.org/jira/browse/AXIS2C-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura closed AXIS2C-1131.
-
The build script fails when it is calling vcvars32.bat
[
https://issues.apache.org/jira/browse/AXIS2C-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura closed AXIS2C-1178.
-
Implement AMQP Transport
Key: AXIS2C
[
https://issues.apache.org/jira/browse/AXIS2C-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura closed AXIS2C-1191.
-
Add Documentation for AMQP Transport
[
https://issues.apache.org/jira/browse/AXIS2C-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura closed AXIS2C-1293.
-
Improve the AMQP Transport to work with Apache/Qpid M3
[
https://issues.apache.org/jira/browse/AXIS2C-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura closed AXIS2C-1291.
-
Incorrect WS-A Action in Dual-Channel Reply Message
[
https://issues.apache.org/jira/browse/AXIS2C-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura closed AXIS2C-1292.
-
Improve Configuration Context to Get/Set Properties
[
https://issues.apache.org/jira/browse/AXIS2C-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura closed AXIS2C-1298.
-
AMQP Transport Does not Work with Sandesha2/C
[
https://issues.apache.org/jira/browse/AXIS2C-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura closed AXIS2C-1299.
-
AMQP Dual-channel Non-blocking Sample Client Time Out
[
https://issues.apache.org/jira/browse/AXIS2C-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura closed AXIS2C-1300.
-
Move Const Definitions from axis2_svc_client.h to axis2_const.h
Reporter: Danushka Menikkumbura
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands
[
https://issues.apache.org/jira/browse/AXIS2C-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1298:
--
Attachment: AXIS2C-1298.receiver.patch
AMQP Transport Does not Work
[
https://issues.apache.org/jira/browse/AXIS2C-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1298:
--
Attachment: AXIS2C-1298.sender.patch
AMQP Transport Does not Work
[
https://issues.apache.org/jira/browse/AXIS2C-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1298:
--
Attachment: AXIS2C-1298.server.patch
AMQP Transport Does not Work
[
https://issues.apache.org/jira/browse/AXIS2C-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1298:
--
Attachment: AXIS2C-1298.util.patch
AMQP Transport Does not Work
[
https://issues.apache.org/jira/browse/AXIS2C-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12651018#action_12651018
]
Danushka Menikkumbura commented on AXIS2C-1298:
---
Please apply the attached
: Danushka Menikkumbura
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
[
https://issues.apache.org/jira/browse/AXIS2C-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1299:
--
Attachment: AXIS2C-1299.patch
AMQP Dual-channel Non-blocking Sample Client
[
https://issues.apache.org/jira/browse/AXIS2C-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12651026#action_12651026
]
Danushka Menikkumbura commented on AXIS2C-1299:
---
Apply the attached patch
Reporter: Danushka Menikkumbura
Move the following const definitions from axis2_svc_client.h to axis2_const.h
so that they can be used in modules, etc.
/** Name of anonymous service */
#define AXIS2_ANON_SERVICE __ANONYMOUS_SERVICE__
/** out-only MEP operation name */
#define
[
https://issues.apache.org/jira/browse/AXIS2C-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1300:
--
Attachment: AXIS2C-1300.1.patch
Move Const Definitions from
[
https://issues.apache.org/jira/browse/AXIS2C-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1300:
--
Attachment: AXIS2C-1300.2.patch
Move Const Definitions from
[
https://issues.apache.org/jira/browse/AXIS2C-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12651239#action_12651239
]
Danushka Menikkumbura commented on AXIS2C-1300:
---
Please apply the attached
-C
Issue Type: Improvement
Reporter: Danushka Menikkumbura
Attachments: AXIS2C-1300.1.patch, AXIS2C-1300.2.patch
Move the following const definitions from axis2_svc_client.h to axis2_const.h
so that they can be used in modules, etc.
/** Name of anonymous service
Incorrect WS-A Action in Dual-Channel Reply Message
---
Key: AXIS2C-1291
URL: https://issues.apache.org/jira/browse/AXIS2C-1291
Project: Axis2-C
Issue Type: Bug
Reporter: Danushka
[
https://issues.apache.org/jira/browse/AXIS2C-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1291:
--
Attachment: AXIS2C-1291.patch
Please apply the attached patch to fix
[
https://issues.apache.org/jira/browse/AXIS2C-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1291:
--
Component/s: samples
Incorrect WS-A Action in Dual-Channel Reply Message
: Danushka Menikkumbura
Improve configuration context API to get and set properties so that external
mutexes and direct access to the context base are avoided.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online
[
https://issues.apache.org/jira/browse/AXIS2C-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1292:
--
Attachment: AXIS2C-1292.h.patch
Apply this patch for header file changes
[
https://issues.apache.org/jira/browse/AXIS2C-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1292:
--
Attachment: AXIS2C-1292.c.patch
Apply this patch for implementation changes
Components: core/transport
Reporter: Danushka Menikkumbura
This version of the AMQP transport is equipped with the following features.
1. Work with Qpid Subscription Manager
2. Support for Dual-Channel (Blocking/Non-blocking)
3. One-way Robust
4. MTOM (and Base64 unoptimized)
5. Samples
[
https://issues.apache.org/jira/browse/AXIS2C-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12648225#action_12648225
]
Danushka Menikkumbura commented on AXIS2C-1293:
---
Please note
[
https://issues.apache.org/jira/browse/AXIS2C-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1293:
--
Attachment: AXIS2C-1293.receiver.patch
Improve the AMQP Transport to work
[
https://issues.apache.org/jira/browse/AXIS2C-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1293:
--
Attachment: AXIS2C-1293.util.patch
Improve the AMQP Transport to work
[
https://issues.apache.org/jira/browse/AXIS2C-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1293:
--
Attachment: AXIS2C-1293.sender.patch
Improve the AMQP Transport to work
[
https://issues.apache.org/jira/browse/AXIS2C-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1293:
--
Attachment: AXIS2C-1293.server.patch
Improve the AMQP Transport to work
[
https://issues.apache.org/jira/browse/AXIS2C-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1293:
--
Attachment: AXIS2C-1293.samples.echo.patch
Improve the AMQP Transport
[
https://issues.apache.org/jira/browse/AXIS2C-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1293:
--
Attachment: AXIS2C-1293.samples.mtom.patch
Improve the AMQP Transport
[
https://issues.apache.org/jira/browse/AXIS2C-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1293:
--
Attachment: AXIS2C-1293.samples.notify.patch
Improve the AMQP Transport
[
https://issues.apache.org/jira/browse/AXIS2C-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1293:
--
Attachment: AXIS2C-1293.samples.configure.patch
Improve the AMQP Transport
If you want to modify the replyTo at the transport level, for me it
indicates something is wrong some where. Can you please explain your
requirement in more detail?
Supun,
In the AMQP transport, the destination queues are generated at the
transport level. So the ReplyTo destination is
Supun,
When the destination is generated by sender, does the sender block
waiting for the remote broker to generating the destination? If that
is the case we can still move this destination generating logic to the
receiver and make the sender block waiting for receiver until it
generates the
When sending a message through AMQP doesn't the client know it is
sending through AMQP ?
It does.
If client knows it ideally it should pass some thing to addressing
handlers to modify the reply to header.
Is it a good thing to let the client programmer intervene with low-level
stuff?
Hi Devs,
We have been using the base context of conf_ctx to keep custom
properties. What we normally do is, get the base context and use its
(axis2_ctx) API to set/get properties. And we use external mutexes for
synchronization. Why don't we have get/set calls in conf_ctx API itself
so
the custom headers get freed when
the client options get freed, though.
Danushka
--
Danushka Menikkumbura
Technical Lead, WSO2 Inc.
blog : http://danushka-menikkumbura.blogspot.com/
http://wso2.com/ - The Open Source SOA Company
otherwise
*/
AXIS2_EXTERN axis2_status_t AXIS2_CALL
axis2_options_remove_all_custom_http_headers(
axis2_options_t*options,
const axutil_env_t* env);
--
Danushka Menikkumbura
Technical Lead, WSO2 Inc.
blog : http://danushka-menikkumbura.blogspot.com/
http://wso2.com
override options become operations clients'
options struct.
However I have never used this functionality.
Thanks Damitha!. I get the picture.
Danushka
--
Danushka Menikkumbura
Technical Lead, WSO2 Inc.
blog : http://danushka-menikkumbura.blogspot.com/
http://wso2.com/ - The Open Source SOA
So what is the option that you propose?
HTTP_HEADERS = array of (key = value) ?
An array of axis2_http_header_t*.
Danushka
--
Danushka Menikkumbura
Technical Lead, WSO2 Inc.
blog : http://danushka-menikkumbura.blogspot.com/
http://wso2.com/ - The Open Source SOA Company
:
axis2_options_add_custom_http_header(
axis2_options_t*options,
const axutil_env_t*env,
const axis2_char_t*name,
const axis2_char_t*value);
Danushka
--
Danushka Menikkumbura
Technical Lead, WSO2 Inc.
blog : http://danushka-menikkumbura.blogspot.com/
http
client options. This is how we pass things like soap action and
various addressing parameters to operation client at the moment.
Can we make it smarter than that?. And do you see any hidden
pitfalls in it?
Danushka
--
Danushka Menikkumbura
Technical Lead, WSO2 Inc.
blog : http://danushka
Hi,
I was able to fix MTOM caching stuff for both sender and receiving ends.
In sender side instead of loading the whole attachment it will send the
attachment + data as chunked. Only very small portion of the attachment
will be loaded in to the memory at any given time. In order to achieve
Components: core/transport
Affects Versions: Current (Nightly)
Reporter: Danushka Menikkumbura
In dual-channel scenarios, the service client (the listener manager) picks the
transport receiver based on the value of the service client option,
transport_in_protocol. By default this has
[
https://issues.apache.org/jira/browse/AXIS2C-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12609167#action_12609167
]
Danushka Menikkumbura commented on AXIS2C-1210:
---
Even TCP dual-channel
Type: Bug
Reporter: Danushka Menikkumbura
In the current dual-channel implementation, the message receiver is started
before the message is handed over to the transport sender. This implementation
can not support a transport receiver that depends on certain piece of
information
Hi All,
It is required to set transport-in-protocol as a service client
option in the case of dual channel scenarios. I think this should be
kept transparent to the client programmer and this setting may possibly
be done when we set the reply-to.
Thoughts Please ...
Danushka
--
Danushka
[
https://issues.apache.org/jira/browse/AXIS2C-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608958#action_12608958
]
Danushka Menikkumbura commented on AXIS2C-723:
--
Hi Senaka,
We do not need
[
https://issues.apache.org/jira/browse/AXIS2C-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12608645#action_12608645
]
Danushka Menikkumbura commented on AXIS2C-723:
--
Hi Damitha,
We already have
[
https://issues.apache.org/jira/browse/AXIS2C-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura resolved AXIS2C-1193.
---
Resolution: Fixed
Fix Version/s: Current (Nightly)
Documentation
[
https://issues.apache.org/jira/browse/AXIS2C-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura closed AXIS2C-1193.
-
Documentation is not Consistent
[
https://issues.apache.org/jira/browse/AXIS2C-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604777#action_12604777
]
Danushka Menikkumbura commented on AXIS2C-1193:
---
Hi Dushshantha
[
https://issues.apache.org/jira/browse/AXIS2C-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1193:
--
Attachment: AXIS2C-1193-manual.patch
Hi Dushshantha,
Please find
[
https://issues.apache.org/jira/browse/AXIS2C-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1193:
--
Attachment: AXIS2C-1193.patch
Please apply the attached patch to fix
[
https://issues.apache.org/jira/browse/AXIS2C-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1191:
--
Attachment: AXIS2C-1191-V2.patch
Sanjaya,
Try AXIS2C-1191-V2.patch and see
[
https://issues.apache.org/jira/browse/AXIS2C-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1191:
--
Attachment: AXIS2C-1191.patch
Please apply the attached patch to update docs
Nandika Jayawardana wrote:
I removed the duplicated code from svn. Please check whether it compiles now.
Hi Nandika,
It works fine. Thanks !!!.
Danushka
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
[
https://issues.apache.org/jira/browse/AXIS2C-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12603550#action_12603550
]
Danushka Menikkumbura commented on AXIS2C-1178:
---
Yes it works out of the box
Versions: Current (Nightly)
Reporter: Danushka Menikkumbura
Fix For: Current (Nightly)
Modify existing docs to have AMQP installation guide.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online
Rajika Kumarasiri wrote:
Seems the patch has been applied incorrectly. Each and every
source/header file repeat the same content twice giving re-definition
errors at compile time. Removing the duplicated entries would fix the
problem.
Hi Samisa,
Is it a goof on my part?. I do not see any
[
https://issues.apache.org/jira/browse/AXIS2C-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1178:
--
Attachment: AXIS2C-1178.patch.v2
Please ignore the patch AXIS2C-1178.patch
[
https://issues.apache.org/jira/browse/AXIS2C-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602903#action_12602903
]
Danushka Menikkumbura commented on AXIS2C-1178:
---
Thiago,
The AMQP
[
https://issues.apache.org/jira/browse/AXIS2C-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1178:
--
Attachment: README
INSTALL
AXIS2C-1178.patch
[
https://issues.apache.org/jira/browse/AXIS2C-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12602521#action_12602521
]
Danushka Menikkumbura commented on AXIS2C-1178:
---
Yeah Makefile.in
: build system (Windows)
Affects Versions: Current (Nightly)
Reporter: Danushka Menikkumbura
The build script fails giving the following error when it is run a number of
times on a single command shell.
The input line is too long.
The syntax of the command is incorrect.
This happens
[
https://issues.apache.org/jira/browse/AXIS2C-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1131:
--
Attachment: AXIS2C-1131.patch
Please apply the attached patch to resolve
This happened when I was trying to write an extension to PERL with the
aid of SWIG. I came across two issues as mentioned below.
1. The struct name DIR declared in axutil_dir_windows.h collides with
the DIR struct declared in dirent.h that comes with the standard PERL
installation.
2. I get
[
https://issues.apache.org/jira/browse/AXIS2C-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danushka Menikkumbura updated AXIS2C-1104:
--
Attachment: AXIS2C-1104.patch
Please find the attached patch to fix the issue
[
https://issues.apache.org/jira/browse/AXIS2C-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586752#action_12586752
]
Danushka Menikkumbura commented on AXIS2C-1104:
---
Please note that I prefixed
Versions: Current (Nightly)
Reporter: Danushka Menikkumbura
This happened when I was trying to write an extension to PERL with the aid of
SWIG. I came across two issues as mentioned below.
1. The struct name DIR declared in axutil_dir_windows.h collides with the DIR
struct declared
85 matches
Mail list logo
