[
http://issues.apache.org/jira/browse/AXIS2-1457?page=comments#action_12443502 ]
Chamikara Jayalath commented on AXIS2-1457:
---
Hi Matt,
See your point.
I think we should do a solution similar to your first proposal.
AFAIK the reason
[
http://issues.apache.org/jira/browse/AXIS2-1457?page=comments#action_12443993 ]
Chamikara Jayalath commented on AXIS2-1457:
---
Hi Chinthaka, Matt,
I think that should be the ideal solution. Service Dispatching and Operation
dispatchin
The place CommonsHTTPTransportSender sets RESPONSE_WRITTEN to true causes a
race condition
--
Key: AXIS2-2655
URL: https://issues.apache.org/jira/browse/AXIS2-2655
ServiceClient.cleanup() should shutdown each module
---
Key: AXIS2-2760
URL: https://issues.apache.org/jira/browse/AXIS2-2760
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: cli
[
https://issues.apache.org/jira/browse/AXIS2-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508125
]
Chamikara Jayalath commented on AXIS2-2851:
---
Applied the patch.
Chamikara
> Move RESPONSE_WRITTEN flag fr
ClusterManager based abstraction to replicate the state of the Context
hierarachy
-
Key: AXIS2-2083
URL: https://issues.apache.org/jira/browse/AXIS2-2083
Project: Axis 2.
[
https://issues.apache.org/jira/browse/AXIS2-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471734
]
Chamikara Jayalath commented on AXIS2-2147:
---
Hi Matt,All,
In case U hvn't seen already the reason is the l
[
https://issues.apache.org/jira/browse/AXIS2-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chamikara Jayalath resolved AXIS2-2083.
---
Resolution: Fixed
Yeah. Checked in.
> ClusterManager based abstraction to replicate
Global Outflow information should be available for pre-dispatch handlers in
the InFlow
---
Key: AXIS2-309
URL: http://issues.apache.org/jira/browse/AXIS2-309
Project: Apache Axis 2.0 (Axis2
When trying to browse a servie url the message ' Oh! this place seems to be
empty!!!' is given
--
Key: AXIS2-338
URL: http://issues.apache.org/jira/browse/AXIS2-338
Project: Apache A
[ http://issues.apache.org/jira/browse/AXIS2-212?page=all ]
Chamikara Jayalath resolved AXIS2-212:
--
Resolution: Fixed
This is not a bug anymore. Releasing the thread seems to be better than holding
it. Holding will comsume too much resources
[
http://issues.apache.org/jira/browse/AXIS2-123?page=comments#action_12375262 ]
Chamikara Jayalath commented on AXIS2-123:
--
I'm working for a Sandesha2 release and dont have much extra time for engaging
in this :-(
Would be really glad if someone
Making the integration itests work correctly
Key: AXIS2-631
URL: http://issues.apache.org/jira/browse/AXIS2-631
Project: Apache Axis 2.0 (Axis2)
Type: Test
Components: Integration
Reporter: Chamikara Jayalath
Mo
[
http://issues.apache.org/jira/browse/AXIS2-631?page=comments#action_12377084 ]
Chamikara Jayalath commented on AXIS2-631:
--
It seems that it is not a necessity for all the endpoints to follow the default
wsdl given in the whitemesa site. Some endp
[
http://issues.apache.org/jira/browse/AXIS2-670?page=comments#action_12377967 ]
Chamikara Jayalath commented on AXIS2-670:
--
What do u mean by not applying? The value set in options is used in the
ServiceClient 'sendReceive' method.
(it seems lik
[
http://issues.apache.org/jira/browse/AXIS2-670?page=comments#action_12377999 ]
Chamikara Jayalath commented on AXIS2-670:
--
Currently the interval is only used for the two channel blocking case. This is
used as the interval a blocking req/res invo
CallbackReceiver should not be a instance variable of the ServiceClient
---
Key: AXIS2-726
URL: http://issues.apache.org/jira/browse/AXIS2-726
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components
[ http://issues.apache.org/jira/browse/AXIS2-726?page=all ]
Chamikara Jayalath updated AXIS2-726:
-
Attachment: ServiceClient.patch
Proposed solution
> CallbackReceiver should not be a instance variable of the ServiceClient
>
[
http://issues.apache.org/jira/browse/AXIS2-725?page=comments#action_12383352 ]
Chamikara Jayalath commented on AXIS2-725:
--
You can avoid this by sharing your configuration context between the
invocations.
But if ur requirement is to use different
Support for Publisher-Subscriber specifications
---
Key: AXIS2-793
URL: http://issues.apache.org/jira/browse/AXIS2-793
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Reporter: Chamikara Jayalath
There doesn't see
[ http://issues.apache.org/jira/browse/AXIS2-793?page=all ]
Chamikara Jayalath updated AXIS2-793:
-
Attachment: pubsub-savan.zip
This contains the code for the Axis2 Pub-Sub implementation I'm working on. The
code comes under the name Savan. Currentl
[
http://issues.apache.org/jira/browse/AXIS2-123?page=comments#action_12319765 ]
Chamikara Jayalath commented on AXIS2-123:
--
I'm trying to implement a WSIF provider for Axis2. Iv developed a working
provider with minimum and most basic functionalit
UUID generator
--
Key: AXIS2-188
URL: http://issues.apache.org/jira/browse/AXIS2-188
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Reporter: Chamikara Jayalath
To create a UUID geneartor.
--
This message is automatically generated by JIRA.
-
If
[
http://issues.apache.org/jira/browse/AXIS2-188?page=comments#action_12320527 ]
Chamikara Jayalath commented on AXIS2-188:
--
Sandesha2 implementation need a UUID generator for generating sequence ids.
But for now it can survive from MIMEOutputUtil
[
http://issues.apache.org/jira/browse/AXIS2-42?page=comments#action_12323053 ]
Chamikara Jayalath commented on AXIS2-42:
-
Sandesha currently badly needs message context serialization support. But
serialization should be minimum to get a resonable p
calling setPausedTrue() on message contexts causes the incoming thread to
immediately return.
-
Key: AXIS2-212
URL: http://issues.apache.org/jira/browse/AXIS2-212
Project: Apache Axi
[ http://issues.apache.org/jira/browse/AXIS2-42?page=all ]
Chamikara Jayalath resolved AXIS2-42:
-
Resolution: Fixed
I have developed the functionality to serialize the complete context hierarchy.
We have clearly identified the non-serializable
A module should be able to add a response message within the InFlow
---
Key: AXIS2-235
URL: http://issues.apache.org/jira/browse/AXIS2-235
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Reporter:
[
http://issues.apache.org/jira/browse/AXIS2-235?page=comments#action_12330252 ]
Chamikara Jayalath commented on AXIS2-235:
--
Ya. It obviously can be done with a new message receiver. But only the
RMModules knows about this behaviour. So when engagi
[
http://issues.apache.org/jira/browse/AXIS2-235?page=comments#action_12331090 ]
Chamikara Jayalath commented on AXIS2-235:
--
Thats how we are currently doing it. It has just one problem. If the
MessageReceiver is RobustInOnly, and a fault get thro
[ http://issues.apache.org/jira/browse/AXIS2-235?page=all ]
Chamikara Jayalath resolved AXIS2-235:
--
Resolution: Fixed
< see my last comment >
> A module should be able to add a response message within the InFlow
> -
A cloning mechanism for SOAPEnvelopes and OMElements
Key: AXIS2-255
URL: http://issues.apache.org/jira/browse/AXIS2-255
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Components: om
Reporter: Chamikara
Modules need the configurationContext object(s) in initialization
-
Key: AXIS2-268
URL: http://issues.apache.org/jira/browse/AXIS2-268
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: dep
[
http://issues.apache.org/jira/browse/AXIS2-268?page=comments#action_12331350 ]
Chamikara Jayalath commented on AXIS2-268:
--
This is needed only in system restoring. This is not needed in the first
startup. (and may not be possible due to the unava
Can't add user defined phases before the PostDispatch phase
---
Key: AXIS2-294
URL: http://issues.apache.org/jira/browse/AXIS2-294
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: deployment
Report
[
http://issues.apache.org/jira/browse/AXIS2-294?page=comments#action_12355734 ]
Chamikara Jayalath commented on AXIS2-294:
--
OK. Please make it a new feature :)
BTW it is great if it shows an error message other than an exception.
Thanx,
Chamikar
36 matches
Mail list logo