I think he means chunking, and you can do that as follows
opts.setProperty(HTTPConstants.CHUNKED, false);
opts - an instance of Option which you use for the client.
Thanks,
Deepal
how do i do this ? what is chunching ?
Amila Suriarachchi wrote:
On Fri, Jan 8, 2010 at 4:17 AM,
Damitha,
Did you get a chance to check with Axis2/Java? it would be a good
interoperability testing.
Thanks,
Deepal
Samisa Abeysinghe wrote:
Looks good.
Have you committed?
Yes it is in svn
Thanks,
Damitha
Samisa...
On Tue, Dec 15, 2009 at 11:58 AM, Damitha Kumarage dami...@wso2.com
I think you are in the list, so you should be able to see this email.
hi every one,
I am new to this mail list, how are you!
There similar have a problem with me to receive from your mail, i have
not receive any mail from you util now, can anyone advise?
thanks.
--
Thank you!
[
https://issues.apache.org/jira/browse/AXIS2-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-4579:
Assignee: Amila Chinthaka Suriarachchi
Amila,
I think you are the only one who can
[
https://issues.apache.org/jira/browse/AXIS2-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-4518.
--
Resolution: Fixed
Martin has given the solution. Thanks Martin
This happen when you do not set the target epr, for that you need to do
option.setTo(new Endpointrefrence(address))
Hi Axis Team
We are trying to call one webservice using fireAndForget method, but
while invoking we are getting org.apache.axis2.AxisFault: Transport out has
not been set
I do not think we need to have a new website. Documentation is in Axis2
website, and with Axis2 TLP we are going to move transport back into
axis2, so no need to create a website just for few days.
Thanks,
Deepal
Folks,
I am ready to do the axis2 transports 1.0 release and I have an issue
[
https://issues.apache.org/jira/browse/AXIS2-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2782.
--
Resolution: Fixed
We have made all these changes and I think we have very good generic
[
https://issues.apache.org/jira/browse/AXIS2-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2803.
--
Resolution: Fixed
This is working fine if we use the transport session. Since .NET
[
https://issues.apache.org/jira/browse/AXIS2-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2929.
--
Resolution: Duplicate
This is duplicate with AXIS2-2766
Java2WSDL does not correctly
Hi Glen,
2) Add yourself to the list of project members on the wiki page if you are an
existing PMC member and would like to be on the new Axis2 PMC
By looking at the current wiki, feel like your point was not clear.
Thanks,
Deepal
Here is my +1 for this proposal.
Thanks,
--Glen
Here we go.
https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/transport/modules
Hello,
I was not able to find the current JMS transports source code in the
source repository. Could someone please help me.
I am one of the 10% who need the JMS support.
Thanks in advance,
I am not sure it is correct or wrong, but I add a separate sections for
the people who want to be a committer of the project but not be in the PMC.
http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal
Glen,
I'd like to join as a committer after the board approves the PMC.
Nadir
This is indeed a very happy and good news!! [this is something I was
trying since 2007 :-) ]. I too would like thank everyone who voted for
the thread as well as who contributes to the project.
Finally we all agreed to a very good plan, now let's execute it.
Thanks,
Deepal
Hi folks:
The
[
https://issues.apache.org/jira/browse/AXIS2-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-4085.
--
Resolution: Fixed
issues if fixed in the current SVN
While loop doesnot exit while
[
https://issues.apache.org/jira/browse/AXIS2-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12774794#action_12774794
]
Deepal Jayasinghe commented on AXIS2-4517:
--
I think we need to find the root
Great, that would be very good thing to have.
Deepal
I just wanted to give everyone a heads-up that we are going to start
upgrading the JAX-WS support to conform to the 2.2 spec relatively soon.
The spec update may be found at http://jcp.org/en/jsr/detail?id=224.
-Bill
--
Thank
+1 for the release.
Thanks,.
Deepal
OK, after adding the default 30-second timeout for connection starvation
issues, and confirming that Rampart now works fine with 1.5.1, let's try this
one more time. Please VOTE on releasing 1.5.1 - then we can get moving on
1.6!
You can find the
+1 for the release.
Thanks
Deepal
Hi Axis Developers,
After fixing the documentation and a few other small issues since the last
attempt at 1.5.1, I think we're ready to try again. I've also addressed the
forced build of Axiom issue with the CLOSE_WAIT fix - we now by default
clean up the
Thanks Amila, now it works.
On Mon, Oct 5, 2009 at 8:44 AM, Deepal jayasinghe deep...@gmail.com
mailto:deep...@gmail.com wrote:
Hi Devs;
I build the war from the trunk and try to deploy that, everything
works
fine. However when I try to list the services it gave me
Hi Devs;
I build the war from the trunk and try to deploy that, everything works
fine. However when I try to list the services it gave me the following
error. I think this has something to do with the changes that Andreas
did.
javax.servlet.ServletException: http is forbidden
at
Hi Devs;
I build the war from the trunk and try to deploy that, everything works
fine. However when I try to list the services it gave me the following
error. I think this has something to do with the changes that Andreas
did few months back.
javax.servlet.ServletException: http is forbidden
Amila and Andreas,
I think Andreas's argument is valid so let's go with this changes. I
also like to remove all the unwanted dependencies, because it is so hard
to set up the project (w.o using maven), and we have so many dependencies.
Thanks,
Deepal
Since Axis2 1.5 depends on Java 1.5, there
Afkham Azeez wrote:
Simply deactivating-redeploying-activating is not the ideal solution.
It should be;
maintenace-mode(service_foo)-redeploy(service_foo)-normal-mode(service_foo)
In maintenance mode, a service will not accept new requests, but will
complete servicing existing requests. So,
, there is a
difference between deactivating a service putting it into
maintenance-mode, unless deactivated services will complete the
requests being processed.
However, there will be a small downtime for this service.
Azeez
On Sun, Aug 30, 2009 at 4:02 AM, Deepal jayasinghe
deep
On Fri, Aug 28, 2009 at 8:30 PM, Andreas Veithen
andreas.veit...@gmail.com mailto:andreas.veit...@gmail.com wrote:
Guys,
Are we actually discussing the right question? Looking at the patch
proposed by Isuru, I have the impression that versioning is merely one
use case,
Hi Andreas,
It is so sad to hear this, I know you contributed a lot and helped to
move the project forward. When we implement a feature we can not
consider all the projects using it. Just think one more time, we really
need your help ., I really value your contribution.
Thanks,
Deepal
This may be a possible way of doing versioning. But IMHO not the best way.
Please have a look at here[1]. If we follow what you have mentioned
here then we need to add
all files of axis2 versions into one folder and rename them as
pom-1.5.xml, pom-1.4.xml etc.
I am worried that you have not
think my suggestion would do this.
This discussion should involve Axis2-dev, carbon-dev, synapse-dev. So please
start a discussion by engaging all these communities in a different thread
with the correct heading.
Amila, I did not see this in the first place could you please tell me
why we
Amila Suriarachchi wrote:
On Sat, Aug 29, 2009 at 4:24 PM, Andreas Veithen
andreas.veit...@gmail.com mailto:andreas.veit...@gmail.com wrote:
I would like to inform all of you that I decided to significantly
reduce my activity in the Axis2 project. Over the last months I have
On Sat, Aug 29, 2009 at 7:49 PM, Deepal jayasinghe deep...@gmail.com
mailto:deep...@gmail.com wrote:
If you feel so I am so sorry, it was not intensional, I really like
Axis2 not because I have contributed to it but because it is a useful
project. When I see someone try
Then there's the question of how to do the update - ideal is to let
messages that are already being processed be processed by the still
active version and to direct new messages to the new version. I'm not
sure that's implementable though .. or it would require one to bring
that concept
Hi Isuru,
Thank you for taking your time and looking to this issues, but I do not
agree the way you have address it, please see my comments below. The
reason I am telling this is, as I can see this has so many issues, and
you have made it complicated too :) . I believe you might know that we
have
the WSDL targetNamespace and/or the types namespace to contain the
version.
I agree, sometime you need to reflect the version form tns and URL.
Azeez
On Fri, Aug 28, 2009 at 1:34 PM, Deepal jayasinghe deep...@gmail.com
mailto:deep...@gmail.com wrote:
Hi Isuru,
Thank you for taking
The artifact name does not have to be unique with OSGi bundles. Due to
file system limitations, you cannot place two artifacts with the same
name in the same directory, but with OSGi you can place your artifacts
with the same name in different directories get them to successfully
deploy,
Andreas Veithen wrote:
On Fri, Aug 28, 2009 at 17:23, Deepal jayasinghedeep...@gmail.com wrote:
Afkham Azeez wrote:
Andreas, you are right. It is not only about the version number. The
hierarchy may semantically reflect the version number. It could be
used for many things. e.g. in a
I just went though the patch and which has a number of assumptions which
introduce so many issues. First as I can see it might break the
directory based deployment, the reason is the logic differentiate
sub-directory from a service just considering have services.xml. And
just look at the following
On Fri, Aug 28, 2009 at 3:18 PM, Deepal jayasinghe deep...@gmail.com
mailto:deep...@gmail.com wrote:
Anyway, I was not around when module versioning was implemented,
and I
strongly feel that trying to derive a version from an artifact is a
tried failed approach
On Fri, Aug 28, 2009 at 4:28 PM, Deepal jayasinghe deep...@gmail.com
mailto:deep...@gmail.com wrote:
I just went though the patch and which has a number of assumptions
which
introduce so many issues. First as I can see it might break the
directory based deployment
Yes this introduces new URL patterns. To be exact, the URI based
dispatcher treats the '/' character to separate service name and
operation name (if any). But in this new case, service name can have
'/' character.
Dont you think that is confusing ? how do you know whether it is service
Yes. If a subdirectory contains a services XML, it is sent to be
deployed. Otherwise it is sent through another iteration to find
services in the sub directory. Is it wrong? Am I missing something?
if by accident if I have two services.xml then I might have some
problem. The reason I am
Ok let me explain. In the URI based service dispatcher, lets say we
have the incoming URL services/foo/Echo. When it give this to
parseRequestURLForServiceAndOperation method to process, it returns
value[0] foo, value[1] Echo and value[2] foo/Echo.
Then it tries to find a service from
Yes exactly. That can be done. We can use some other charactor like
'-' to represent '/' charactors in the service name. That will avoid
most of the logics I've added to properly handle this. I can resend a
pathc using '-' if we can agree on that.
Then you do not need to anything ? I mean
Let me first describe how Hot update works in axis2, correct me if I
am wrong but from what I have figured out so far, axis2 repository
listener task calls unDeploy method of the deployer implementation
first and then calls the deploy method again to deploy the artifact
with the changes.
Yes
No I can't, I guess I have explained why I can't use it as well,
because I cannot differentiate the undeployment call for the hot
update and real undeployment. Well, what Amila suggested will work
though :-)
Of course you can if the file is there then that is hot-update else it
is un
[
https://issues.apache.org/jira/browse/AXIS2-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-4421.
--
Resolution: Invalid
We have fixed this issues in later version of Axis2. As you have
Amila Suriarachchi wrote:
On Fri, Aug 21, 2009 at 12:58 AM, Andreas Veithen
andreas.veit...@gmail.com mailto:andreas.veit...@gmail.com wrote:
If the user registered a transport receiver for http or https that is
not of type AxisServletListener, then this would obviously mean that
2) I think there is no need to start yelling around about merrily
chang[ing] APIs, things are going to become a big mess and engage
the community before making such drastic changes. I did lots of fixes
in Axiom and Axis2 since Synapse trunk switched from Axis2 SNAPSHOT to
1.5, and when
It is the fifth birthday of the project..
-- Deepal --
Some history of the project...
http://blogs.deepal.org/2009/08/happy-birthday-axis2.html
--
Thank you!
http://blogs.deepal.org
http://deepal.org
Amila,
Let's say we are trying to invoke a service called Echo inside an
application server (like tomcat), and further assume that we have a
service called Echo in the server as well. Then what happen is you are
going to change the server's service. I think that is not right.
Deepal
Hi Glen,
Sound like a good plan, let's do that way.
Thanks,
Deepal
On Tue, Aug 11, 2009 at 6:53 AM, Glen Danielsg...@thoughtcraft.com wrote:
Hi Deepal:
Deepal Jayasinghe wrote:
So, there are currently no JIRAs left targeted for 1.5.1, and there were at
least a few major fixes
-- Forwarded message --
From: Sally Khudairi s...@apache.org
Date: Fri, Aug 7, 2009 at 9:55 PM
Subject: Sign up for ApacheCon US by 14 August and save up to $500!
To: annou...@apache.org, annou...@apachecon.com
Sign up for ApacheCon US by 14 August and save up to $500!
This
[
https://issues.apache.org/jira/browse/AXIS2-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12740134#action_12740134
]
Deepal Jayasinghe commented on AXIS2-3852:
--
Only thing you can do
Please check with CFX mailing list.
Hi all,
does anyone know where I can download the tools that Apache CFX
provides? In particular
I am interested in using the WSDL2JS (Javascript) tool or any other
tool that generates scripts
instread of Java code.
Thanks and regards
Demetris
[
https://issues.apache.org/jira/browse/AXIS2-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-4440.
--
Resolution: Invalid
I am sorry I did not understand the question properly, Excluding
[
https://issues.apache.org/jira/browse/AXIS2-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12735282#action_12735282
]
Deepal Jayasinghe commented on AXIS2-4314:
--
Seems like the patch is outdated
[
https://issues.apache.org/jira/browse/AXIS2-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reassigned AXIS2-4314:
Assignee: Deepal Jayasinghe
service references are not completely removed
I'm a Axis2 user, I'm wonder with this mail and getting doubt about quality
of the project ? AFAIK Apache always keep good quality with high performance
with their projects but I'm not sure Axis2 try to keep that policy or try to
loose it ?
Well Apache is always community over code. So
If you configure the class path correctly, Axis2 should find your jar.
One way you could do is to put the jar into the WEB-INF/lib, in that way
you do not need to worry about putting the jar into the .aar
Thanks,
Deepal
I am deploying a web service using Tomcat 6.0 and Axis2 1.5.
[
https://issues.apache.org/jira/browse/AXIS2-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3482.
--
Resolution: Fixed
Test and confirmed, as well as I have even added a test case
[
https://issues.apache.org/jira/browse/AXIS2-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12724971#action_12724971
]
Deepal Jayasinghe commented on AXIS2-4398:
--
I tried to apply the patch, but got
Thank you very much for submitting the patch, but I would recommend you to
create a JIRA and attach the patch, I remember you send some more patchs
sometimes ago, and not sure anyone has applied them. So please create JIRA.
Thanks,
Deepal
On Mon, Jun 22, 2009 at 9:08 AM, Pétur Runólfsson
What the difference of writing a MR and a serializer/deserializer ?, I
do not see a big difference.
Deepal
On Fri, Jun 19, 2009 at 7:41 AM, Davanum Srinivasdava...@gmail.com wrote:
Guess it's time to port the pluggable serializer/deserializer mechanism from
Axis1 :)
-- dims
On 06/19/2009
bits and pieces of
Java-XML
Guess, i should not bring up Axis1 design. my fault.
thanks,
-- dims
On 06/19/2009 09:15 AM, Deepal Jayasinghe wrote:
What the difference of writing a MR and a serializer/deserializer ?, I
do not see a big difference.
Deepal
On Fri, Jun 19, 2009 at 7:41
serviceClient.engageModue(). But i dont want to write this code in my
program.
Yes, I do not see any issues, here. When you call serviceClient, then
you need to engage module for that client.
Thanks
Deepal
Thanks,
Swapna Soni.
Deepal Jayasinghe-2 wrote:
So thats mean when you engage the module from
[
https://issues.apache.org/jira/browse/AXIS2-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12719137#action_12719137
]
Deepal Jayasinghe commented on AXIS2-2856:
--
I agree, but the thing
[
https://issues.apache.org/jira/browse/AXIS2-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12719143#action_12719143
]
Deepal Jayasinghe commented on AXIS2-3084:
--
Could you please explain how to do
[
https://issues.apache.org/jira/browse/AXIS2-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12719214#action_12719214
]
Deepal Jayasinghe commented on AXIS2-4376:
--
Hi sebastien,
I am so sorry, we
As I know this is not a know issue, I know Rampart handler does
OM-DOM-OM conversion, which is performance killer. So I think Rampart
handler has to check whether a given module is engage for a give request
and then invoke the handler.
In the case of encryption it has to decrypt it, I think that
[
https://issues.apache.org/jira/browse/AXIS2-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe updated AXIS2-4337:
-
Priority: Blocker (was: Major)
Let's add all the transport to the war, if we are going
Yes, you need to download the transports jars and drop that into lib,
anyway I think we have to do a 1.5.1 release. So we will make sure that
it is there in the release.
Thanks,
Deepal
Bhat, Suma wrote:
Hi,
I am seeing the following exception on tomcat startup.
Jun 12, 2009 3:58:06
[
https://issues.apache.org/jira/browse/AXIS2-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12719012#action_12719012
]
Deepal Jayasinghe commented on AXIS2-4058:
--
Amila,
Seems like AXIS2-4350 caused
So thats mean when you engage the module from services.xml that does not
work?
I can not understand who breaks the working codes, anyway please create
a JIAR and attach whatever necessary to re-create the issue.
Thanks,
Deepal
Hi Team,
I have two webservices. One is server service and one
[
https://issues.apache.org/jira/browse/AXIS2-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12719020#action_12719020
]
Deepal Jayasinghe commented on AXIS2-4373:
--
I tried to apply the patch
[
https://issues.apache.org/jira/browse/AXIS2-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2101.
--
Resolution: Later
The engageModuleToOperation method on PhaseResolver is missing
[
https://issues.apache.org/jira/browse/AXIS2-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2099.
--
Resolution: Later
The class level comment on PhaseHolder is not very descriptive
[
https://issues.apache.org/jira/browse/AXIS2-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2100.
--
Resolution: Later
The class level comment on PhaseResolver is not very descriptive
[
https://issues.apache.org/jira/browse/AXIS2-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2098.
--
Resolution: Later
There are numerous public methods on MessageContext that do
[
https://issues.apache.org/jira/browse/AXIS2-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2559.
--
Resolution: Won't Fix
Jira cleanup
[AXIS2-1.2-RC2] Data Binding Error
[
https://issues.apache.org/jira/browse/AXIS2-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2473.
--
Resolution: Fixed
There are enough documentation on these
Give an answer to What
[
https://issues.apache.org/jira/browse/AXIS2-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2586.
--
Resolution: Fixed
I assume this issue is fixed, if not please reopen it.
Thanks
[
https://issues.apache.org/jira/browse/AXIS2-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12719028#action_12719028
]
Deepal Jayasinghe commented on AXIS2-2075:
--
Amila,
Are we there yet?
WSDL2Java
[
https://issues.apache.org/jira/browse/AXIS2-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12719027#action_12719027
]
Deepal Jayasinghe commented on AXIS2-2071:
--
Any idea about the status
[
https://issues.apache.org/jira/browse/AXIS2-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3085.
--
Resolution: Fixed
should be fixed this by now, we have done a number of improvements
[
https://issues.apache.org/jira/browse/AXIS2-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3084.
--
Resolution: Fixed
Unless we can get the element from Axiom as case insensitive, we can
[
https://issues.apache.org/jira/browse/AXIS2-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3082.
--
Resolution: Fixed
The generated wsdl doesn't validate the generated wsdl chokes
[
https://issues.apache.org/jira/browse/AXIS2-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2905.
--
Resolution: Won't Fix
New documentation on Message formatters/builders needed
[
https://issues.apache.org/jira/browse/AXIS2-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2856.
--
Resolution: Fixed
hmm, no one uses moduleConfig I guess
Module Config Changes
[
https://issues.apache.org/jira/browse/AXIS2-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2969.
--
Resolution: Fixed
That would be enough I guess. If you want you can see the rest from
[
https://issues.apache.org/jira/browse/AXIS2-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2930.
--
Resolution: Fixed
Please reopen if the issue is still there
AXIS2 - signature
[
https://issues.apache.org/jira/browse/AXIS2-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2813.
--
Resolution: Fixed
[Performance] set enableMTOM flag for RPCMessageReceivers
[
https://issues.apache.org/jira/browse/AXIS2-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2812.
--
Resolution: Fixed
[Performance] set enableMTOM flag in autogenerated services.xml
[
https://issues.apache.org/jira/browse/AXIS2-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2710.
--
Resolution: Won't Fix
Wont belong here, it is Rampart
xs:any throws when
[
https://issues.apache.org/jira/browse/AXIS2-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2819.
--
Resolution: Fixed
re-open if the issue is still there
Faulty handling of JMS
[
https://issues.apache.org/jira/browse/AXIS2-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3094.
--
Resolution: Fixed
Fixed
NPE thrown from OperationClient addMessageContext method
[
https://issues.apache.org/jira/browse/AXIS2-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3214.
--
Resolution: Fixed
This should be fixed now, we did so many release after
[
https://issues.apache.org/jira/browse/AXIS2-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2492.
--
Resolution: Fixed
Please re-open if the issue is still there
Deployment problem
[
https://issues.apache.org/jira/browse/AXIS2-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3195.
--
Resolution: Fixed
Let's re-open if the issue is still there, and this is belong
[
https://issues.apache.org/jira/browse/AXIS2-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-2790.
--
Resolution: Fixed
where is the analytic data, no one knows username and password
[
https://issues.apache.org/jira/browse/AXIS2-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-3274.
--
Resolution: Fixed
Please re-open if you still have the issue.
Thanks,
deepal
Axis2
1 - 100 of 3069 matches
Mail list logo
