[
https://issues.apache.org/jira/browse/AXIS2-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Madushan Jayasoma updated AXIS2-2920:
-
Attachment: jaxws_patch_08_07_2007.txt
JAX-WS 2.0 support for Apache
[
https://issues.apache.org/jira/browse/AXIS2-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Madushan Jayasoma updated AXIS2-2401:
-
Attachment: patch_06-04-2007.txt
This error occurred due
[
https://issues.apache.org/jira/browse/AXIS2-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Madushan Jayasoma updated AXIS2-2233:
-
Attachment: patch_ping_module_updated.txt
Here with I have attached
[
https://issues.apache.org/jira/browse/AXIS2-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Madushan Jayasoma updated AXIS2-2233:
-
Attachment: patch_ping_module_updated-2.txt
Pinging capability
[
https://issues.apache.org/jira/browse/AXIS2-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Madushan Jayasoma updated AXIS2-2244:
-
Attachment: patch_ping_sample.txt
Sample to illustrate the pinging
Sample to illustrate the pinging capability
---
Key: AXIS2-2244
URL: https://issues.apache.org/jira/browse/AXIS2-2244
Project: Axis 2.0 (Axis2)
Issue Type: New Feature
Reporter: Sameera
: Sameera Madushan Jayasoma
Attachments: patch_ping_module.txt
The pinging capability is implemented as a module, which can be engaged by
services to enable pinging. Pinging is an useful feature to
users/administrators to check the status of the web services deployed in axis2.
Basically
[
https://issues.apache.org/jira/browse/AXIS2-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Madushan Jayasoma updated AXIS2-2233:
-
Attachment: patch_ping_module.txt
Pinging capability to services
Hi all,
Implementation of the ping module is available in the following JIRA
https://issues.apache.org/jira/browse/AXIS2-2233
Sameera
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Versions: nightly
Reporter: Sameera Madushan Jayasoma
Priority: Minor
Hi,
There are some places in axis2 code which can have a negative impact on the
performance. Invoking some of these methods result in searching HashMaps.
Duplicating these kinds of methods is not a good idea
[
https://issues.apache.org/jira/browse/AXIS2-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Madushan Jayasoma updated AXIS2-2186:
-
Attachment: patch.txt
Removing redundant ( and heavy) method
[
https://issues.apache.org/jira/browse/AXIS2-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Madushan Jayasoma updated AXIS2-2186:
-
Attachment: patch.txt
Removing redundant ( and heavy) method
I've also found out some places in axis2 code which can have a
negative impact on the performance. For an example consider the
following code in the AbstractMessageReceiver class.
if (service.getParameter(Constants.SERVICE_OBJECT_SUPPLIER) != null) {
Parameter serviceObjectParam =
I have an on going prototype development of the ping module, but it is
not yet submitted as a patch. It satisfies following requirements as
they were discussed in this thread.
The ping module supports only the service level ping requests. Once a
service level ping request is received, it will
Hi all,
Here are the sample message formats for the ping request and ping response.
Ping Request
POST /axis2/services/SomeService HTTP/1.1
SOAPAction: ping //SOAPAction should be a unique one
..
?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope xmlns:soapenv=
Hi deepal,
The problem is that pinging at the handler level basically amounts to
just asking is there such a service?. Having it go to the message
receiver allows the ping to be responded to based on more useful data-
such as did the impl class or script or whatever load etc.. So its
really a
in this
ping method, one can check whether the required dependencies for the service
is available or not.
In order to identify ping requests soapaction can be used. Based on the
soapaction ping handler can invoke the ping method of message receiver.
Thanks
Sameera Madushan
Hi Dims, Deepal
Actually the idea is to develop a custom ping module with appropriate
handlers. One of the ping handlers should be added to the dispatch phase
before the 'InstanceDispatcher' (Inflow). If the service is deployed and it
is active, then ping handler can get the service status from
Hi Robert
Check this link, sometimes it may help you.
http://wso2.org/library/230
Sameera
On 2/7/07, Robert Chilvers [EMAIL PROTECTED] wrote:
Hi All;
I am not sure if this is the best place for this question, but I am stuck.
I have a Axis2 client which I created from a service's WSDL
Type: Bug
Components: documentation
Reporter: Sameera Madushan Jayasoma
Priority: Minor
Fix For: nightly
In the 4th queston of faq ( ../axis2/java/xdocs/faq.html#d4) following
correction is need to be done.
maven dist-std-bin Will generate
[
https://issues.apache.org/jira/browse/AXIS2-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameera Madushan Jayasoma updated AXIS2-1959:
-
Attachment: patch.txt
Mistake in ../axis2/java/xdocs/faq.html#d4
It seems that theare is no way to remove a declared namespace.
Thanks
Sameera.
On 11/21/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
Sameera Madushan wrote:
Hi all,
As far as I know , an OMNamespace can be declared using the
OMElement.declareNamespace() method.
Is there a way to remove
: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: samples, build,site docs
Affects Versions: 1.1
Reporter: Sameera Madushan Jayasoma
Priority: Minor
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact
)
Issue Type: Bug
Affects Versions: 1.1
Reporter: Sameera Madushan Jayasoma
Attachments: tingTong.wsdl
Herewith I have attached the necessary files in order to recreate the problelm.
I developed the wsdl for following operations.
1 .public Game tingTong(Game game
[ http://issues.apache.org/jira/browse/AXIS2-1190?page=all ]
Sameera Madushan Jayasoma updated AXIS2-1190:
-
Attachment: tingTong.wsdl
Problem in code generation when method overloading is present in WSDL
[ http://issues.apache.org/jira/browse/AXIS2-1174?page=all ]
Sameera Madushan Jayasoma updated AXIS2-1174:
-
Attachment: patch.txt
Some changes to the Axis2 Architecture guide
, build,site docs
Affects Versions: 1.0
Reporter: Sameera Madushan Jayasoma
Priority: Minor
There are some mistakes in the Axis2 Architecture document.
1. In the section Axis2 Default Processing Model
There should be four handlers as it is stated in this section
Reporter: Sameera Madushan Jayasoma
I have some found out some mistakes in the Axis2 user guide - page
Some of them were simple spelling mistakes.
Some of them were critical. Paths of some files were incorrect.
--
This message is automatically generated by JIRA.
-
If you think it was sent
[ http://issues.apache.org/jira/browse/AXIS2-1178?page=all ]
Sameera Madushan Jayasoma updated AXIS2-1178:
-
Attachment: patch.txt
Some mistakes found in the Axis2 userguide - page 3
Dear all,I developed a wsdl for two web service operations(mentioned below). Code generation process works fine.There is boolean variable called 'loginStatus' in the UserLoginReponse element. After the code generation I could see the following
UserLoginResponse.getLoginStatus().As I know in java
30 matches
Mail list logo