to complete all scenarios - so ensure that your SSH
client timeout is disabled :D
cheers
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
to compile the
code with optimization - usually reached after around 10,000 iterations
of a method.
cheers
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
/branches/modules/transport/1.0.0
Here's my +1 to declaring the above dist as Axis2 Transports 1.0.0
Thanks,
Ruwan
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
Hi Amila
I could run all the test cases with jdk 1.5.
Shall we move the httpCore version to 4.0 since it has released now?
Yes, please do so..
thanks
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
these transports.. Most users would
use http only by default. Keeping them where they are allows anyone to
easily use them by uncommenting the sections from the default axis2.xml
cheers
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
to Axis2
transports. That allows you to release minor bug fix versions of these
separately if required as well
cheers
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
code back :-[ ?
cheers
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
Jarek Gawor wrote:
On Tue, Mar 31, 2009 at 12:22 AM, Asankha C. Perera asan...@apache.org wrote:
2) Move the base, local, tcp, and http transport modules back to Axis2
and release them with Axis2. That way the transports project would
only have the 'optional' transport modules and we
someone let me know if I shouldn't do this?.. and if so, why?
thanks
asankha
[1] http://forums.sun.com/thread.jspa?messageID=10657165
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
[
https://issues.apache.org/jira/browse/AXIS2-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12679196#action_12679196
]
Asankha C. Perera commented on AXIS2-4212:
--
I've done this to trunk and 1,5 branch
[
https://issues.apache.org/jira/browse/AXIS2-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-4212.
--
Resolution: Fixed
Assignee: Asankha C. Perera
Comitted to 1.5 and trunk, thanks
to change the version in
the 1_5 branch to 1.5-SNAPSHOT and publish the artifacts.
+1 from me.. I didn't see any objections to this proposal, so I think
its ok to go ahead, if you can tackle it.. will be helpful to many..
thanks
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
[
https://issues.apache.org/jira/browse/AXIS2-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12677642#action_12677642
]
Asankha C. Perera commented on AXIS2-4088:
--
See http://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/AXIS2-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12677645#action_12677645
]
Asankha C. Perera commented on AXIS2-3514:
--
Michele
For 1
I would actually
[
https://issues.apache.org/jira/browse/AXIS2-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3460.
--
Resolution: Won't Fix
Assignee: Asankha C. Perera
HTTP/S NIO is not within
[
https://issues.apache.org/jira/browse/AXIS2-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3473.
--
Resolution: Won't Fix
Assignee: Asankha C. Perera
HTTP/S NIO is not within
[
https://issues.apache.org/jira/browse/AXIS2-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-2993.
--
Resolution: Won't Fix
Assignee: Asankha C. Perera (was: Deepal Jayasinghe)
HTTP
[
https://issues.apache.org/jira/browse/AXIS2-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3309.
--
Resolution: Won't Fix
HTTP/S NIO is not within the Axis2 project anymore
[
https://issues.apache.org/jira/browse/AXIS2-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3428.
--
Resolution: Won't Fix
Assignee: Asankha C. Perera
HTTP/S NIO is not within
[
https://issues.apache.org/jira/browse/AXIS2-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3496.
--
Resolution: Won't Fix
HTTP/S NIO is not within the Axis2 project anymore
[
https://issues.apache.org/jira/browse/AXIS2-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3661.
--
Resolution: Won't Fix
Assignee: Asankha C. Perera
HTTP/S NIO is not within
[
https://issues.apache.org/jira/browse/AXIS2-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3514.
--
Resolution: Won't Fix
Assignee: Asankha C. Perera
HTTP/S NIO is not within
[
https://issues.apache.org/jira/browse/AXIS2-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-4188.
--
Resolution: Won't Fix
Assignee: Asankha C. Perera
If a patch is contributed, we
[
https://issues.apache.org/jira/browse/AXIS2-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-4088.
--
Resolution: Won't Fix
Assignee: Asankha C. Perera
HTTP/S NIO is not within
the list of transport
issues we need to fix in the JIRA's.. If there is anything critical that
needs to be fixed for transports 1.0 (that would ship with Axis2 1.5)
please mark it a blocker, and assign to me
thanks
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http
[
https://issues.apache.org/jira/browse/AXIS2-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-4025.
--
Resolution: Won't Fix
Assignee: Asankha C. Perera
The JMS transport
[
https://issues.apache.org/jira/browse/AXIS2-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12677236#action_12677236
]
Asankha C. Perera commented on AXIS2-2993:
--
Hi Deepal
Lets take this concrete
[
https://issues.apache.org/jira/browse/AXIS2-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-1381.
--
Resolution: Fixed
Fix Version/s: 1.4.1
This issue is very old.. AFAIK
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
that to the next time you want
to revisit Axis2
cheers
asankha
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
and see what happens?
cheers
asankha
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
[
https://issues.apache.org/jira/browse/AXIS2-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera closed AXIS2-4213.
Resolution: Won't Fix
Assignee: Asankha C. Perera
Hi Karthick
The JMS transport
the whole Axis2 project :-)
Andreas
On Wed, Jan 14, 2009 at 04:38, Asankha C. Perera asan...@apache.org wrote:
Hi Andreas
I had to revert this change (and the previous one) because they cause
the Axis2 build to fail (not in the modules you changed, but in
modules depending on those
only for the testing scope in maven
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
/AXIS2-4196
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: nightly
Reporter: Asankha C. Perera
Priority: Critical
One of the most used widely methods of Axis2, the AxisEngine.send() method
contains
[
https://issues.apache.org/jira/browse/AXIS2-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3662.
--
Resolution: Fixed
Fixed with WS-Commons transport revision 724432
The JMS transport
[
https://issues.apache.org/jira/browse/AXIS2-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera reassigned AXIS2-3662:
Assignee: Asankha C. Perera
Can't use JMS transport from axis2.war on WebSphere
[
https://issues.apache.org/jira/browse/AXIS2-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-545.
-
Resolution: Fixed
Assignee: Asankha C. Perera
Probably fixed ages ago
[
https://issues.apache.org/jira/browse/AXIS2-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-4164.
--
Resolution: Fixed
Fix Version/s: 1.5
Assignee: Asankha C. Perera
Fixed
[
https://issues.apache.org/jira/browse/AXIS2-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3088.
--
Resolution: Fixed
Fix Version/s: 1.5
Please set transport level headers
[
https://issues.apache.org/jira/browse/AXIS2-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-1665.
--
Resolution: Fixed
Fix Version/s: 1.5
Partly resolved with WS-Commons transport
[
https://issues.apache.org/jira/browse/AXIS2-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12654506#action_12654506
]
Asankha C. Perera commented on AXIS2-4025:
--
Hi Cathal
We have updated the JMS
[
https://issues.apache.org/jira/browse/AXIS2-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3774.
--
Resolution: Fixed
Fix Version/s: 1.5
Assignee: Asankha C. Perera
[
https://issues.apache.org/jira/browse/AXIS2-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3485.
--
Resolution: Fixed
Fix Version/s: 1.5
Fixed with WS-Commons transport revision
[
https://issues.apache.org/jira/browse/AXIS2-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3238.
--
Resolution: Fixed
Fix Version/s: 1.5
The problematic area reported has been
.
cheers
asankha
[1]
http://svn.apache.org/viewvc/webservices/commons/trunk/modules/transport/modules/jms/src/main/java/org/apache/axis2/transport/jms/package.html?revision=724432content-type=text%2Fhtml
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
:
On Thu, 2008-11-20 at 11:34 -0500, Davanum Srinivas wrote:
Oleg,
I totally agreed with you if you scroll back a few emails. Yes, we
need to fix *that*. Any patch to do that will be *very* welcome.
Ironically enough, this is precisely what the patch does.
Oleg
--
Asankha C
/non-binding depending on whether you are a PMC member).
Here's my +1 (binding).
Thanks,
--Glen
[1] http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
for the existing implementation. It
is pointless to have two MIME frameworks in Axiom. Just forget about the
patch.
Oleg
On Tue, Nov 18, 2008 at 9:46 PM, Asankha C. Perera [EMAIL PROTECTED] wrote:
Hi all
Last night I noticed that the patch contributed by Oleg for better MIME
parsing [1
13, 2008 at 11:04 PM, Asankha C. Perera
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Hi All
I am seeing loads and loads of the following log message, which
dumps the thread stack whenever a Parameter was added.. This
severely clutters the log files, and makes it difficult
(AxisConfigBuilder.java:101)
DEBUG_FRAME =
org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:707)
...
... ## TRUNCATED ## ..
...
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
level..
and it wont be nice to expect users to explicitly exclude this category
asankha
On Friday 14 November 2008, Asankha C. Perera wrote:
Hi All
I am seeing loads and loads of the following log message, which dumps
the thread stack whenever a Parameter was added.. This severely clutters
Hi all
I will be moving the Mail, JMS and the Base Transport abstraction into
the WS Commons project now.
Then on WS-Commons dev list (CC:ing axis2-dev), I will be calling for a
vote for commit rights to Andreas, so that he can help maintain the codebase
We will consider moving other
Folks
Andreas Veithen has been an active committer of the Apache Synapse
project from February, and has helped improve, add and enhance the
transport implementations that grew under the Synapse project for Apache
Axis2. Now as we move some of these transports into WS-Commons, I
propose that
+1 from me
asankha
Asankha C. Perera wrote:
Folks
Andreas Veithen has been an active committer of the Apache Synapse
project from February, and has helped improve, add and enhance the
transport implementations that grew under the Synapse project for
Apache Axis2. Now as we move some
confirm the temporary fix I provided you, I will check it into
the trunk with a JIRA so that it goes into the next release
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
-mail: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
Nandana,
+1 from me for you to be the Release Manager for 1.4.1
+1 for Nandana as the release manager
Nandana
I would also like to suggest
https://issues.apache.org/jira/browse/AXIS2-3887 for inclusion, as this
prevents Synapse from using the servlet transport effectively, since
URL: https://issues.apache.org/jira/browse/AXIS2-3887
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: transports
Affects Versions: 1.4
Reporter: Asankha C. Perera
Assignee: Asankha C. Perera
Steps:
Edit axis2-1.4/samples
[
https://issues.apache.org/jira/browse/AXIS2-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-3887.
--
Resolution: Fixed
Fix Version/s: nightly
fixed
The servlet transport does
Saminda
In general I feel most of the points you suggest would not be really
used by actual end users most of the time (if not all the time) -
especially those who use Axis2 in production. Shall we take this
discussion to the user list as well and see if these use cases you
describe would be
Dims
Would you object even if changes are incremental and don't affect
existing use cases / scenarios? Specifically, in a
non-osgi environment existing functionality is kept as-is?
No I will not object.. as long as the core code is not dependent on OSGi
libraries/API's etc as well (i.e.
Saminda
Thanks for the detailed reply.. Please see my comments below, I will
only take the top 5 points for each list I asked for to keep this
discussion short, as I believe these are in the order of importance/use
1. When aar/mar behavior is mimicked in an OSGi bundle, these bundles
be able
Saminda
Main aspect of OSGi is version and modularity
Can you list the top 5 advantages for Axis2 end users (who develop
services, or develop clients that consume services), and the top 5
advantages for those who embed Axis2 (such as Apache Synapse etc). I
think this would be very valuable
Hi
Can some one provide me the sample i/p message or Client program to
put message in to Message Queue. I have almost tried all combinations.
Have you looked at
http://svn.apache.org/viewvc/synapse/trunk/java/modules/samples/src/main/java/samples/userguide/GenericJMSClient.java?view=markup
observation.
asankha
On Wed, Jun 4, 2008 at 10:09 PM, Asankha C. Perera [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Supun
I think this is a known issue in IIS 5. Please refer the links
below
http://support.microsoft.com/kb/216493
http
Supun
I think this is a known issue in IIS 5. Please refer the links below
http://support.microsoft.com/kb/216493
http://www.somacon.com/p126.php
Sorry but I don't understand the logical relevance of the above with the
issue I report.. if .net services understands http 1.1, why doesn't
Hi All
When I talk to Axis2/C hosted on IIS, it returns a method not allowed
exception as shown below.. however, if the POST only uses the path
segment, the call succeeds.. Is this a bug with IIS or Axis2/C ?
If the message fails due to a Content-Length error etc, Axis2/C returns
a smiley
Supun / Samisa
We have send a request using the full URL with the POST method. But
it seems that IIS discards the request before it give the control to
the IIS module. So it seems like it is a bug in the IIS itself.
Apparently. the full URL works for GET but not for POST with IIS.
AFAIK, the
Samisa
We have send a request using the full URL with the POST method.
But it seems that IIS discards the request before it give the
control to the IIS module. So it seems like it is a bug in the IIS
itself.
Apparently. the full URL works for GET but not for POST with IIS.
AFAIK, the full
Telnetting is a pain when debugging. If we proxy Axis2/C echo sample
with Synapse, I hope we should be able to recreate this. Correct?
Yes, this should be fine.. let me know if you need any help setting up
Synapse..
asankha
Christopher
You can try the Mail transport implementation we have developed for
Apache Synapse. This can be made to replace the Axis2 Mail transport,
but dropping the JAR file [1] into your lib directory, and updating your
axis2.xml as follows:
[1]
Andreas Veithen wrote:
Christopher,
I think the mail transport implementation in Apache Synapse has
support for this. You can use this transport as a replacement for the
mail transport distributed with Axis2.
Yes, you just need to drop the JAR file found here
Deepal
As we discussed in the mailing list I created a prototype deployer
(TransportDeployer) for transport deployment..
This is cool and boy you are fast :-) !..
Axis2 transports also needs a few more changes though.. and I'm
re-thinking about the suggestion made by Sanjiva on moving the
Sanjiva
Sanjiva Weerawarana wrote:
- First of all, Asankha, why synapse-transports.jar?? That makes no
sense to me- so if you have a bug in the VFS code you'll rev all the
stuff? Why? There should be one jar per transport. Yes, lots of jar
files but so what?
- Asankha, you seem to think
Dims
- there should not be stale copies
- people who work on them should work where they want to.
+1 to both!
Right now it's Asankha and co. So we should just make Status Quo
permanent. It can be under Axis2 as a maven module or
under WS-Commons or maven module under synapse. I really don't
David
Asankha, is there something about doing this work in Axis2 that is
difficult for you and easily changed e.g. having a separate release
schedule for the 'extra transports',
One of the main issues here to consider is how easily we can fix issues,
create patches and release versions of the
Check this thread
http://mail-archives.apache.org/mod_mbox/synapse-dev/200710.mbox/[EMAIL PROTECTED]
as well titled Getting axis2 transport out from the kernel
asankha
Davanum Srinivas wrote:
Ruwan,
All i see is some discussion, which happens on a topic
Davanum Srinivas wrote:
Agreed that this is definitely a problem.
Next question, is do you want do this in Synapse Commons (do you have
one?) or WS Commons?
We already have all the transports in a separate Maven module, which is
published to Apache snapshots and Central repo.. As far as I am
[
https://issues.apache.org/jira/browse/AXIS2-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585893#action_12585893
]
Asankha C. Perera commented on AXIS2-3662:
--
Hi George
Actually I looked into two
[
https://issues.apache.org/jira/browse/AXIS2-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12584054#action_12584054
]
Asankha C. Perera commented on AXIS2-3662:
--
The original post above stated
[
https://issues.apache.org/jira/browse/AXIS2-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575069#action_12575069
]
Asankha C. Perera commented on AXIS2-3428:
--
Deepal - Is point # 2 above correct
[
https://issues.apache.org/jira/browse/AXIS2-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573768#action_12573768
]
Asankha C. Perera commented on AXIS2-3428:
--
Michele
I tried your test suite
Hi
Just FYI, some improvements have been made to the JMS transport and is
now available with the Synapse 1.1.1 release at
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/synapse/synapse-transports/1.1.1/synapse-transports-1.1.1.jar
This is an enhanced version of the same
Folks,
Since we delayed the release of Synapse 1.1.1 for a week to include the
HttpComponents 4.0-beta1 release, I made use of this time to implement a
feature requested by one of our users - Enhanced Mail support
(https://issues.apache.org/jira/browse/SYNAPSE-189)
As I am confident that
Reposting using the new Synapse mailing lists : [EMAIL PROTECTED]
and [EMAIL PROTECTED]
*
Asankha C. Perera wrote:
Folks,
Since we delayed the release of Synapse 1.1.1 for a week to include
the HttpComponents 4.0-beta1 release, I made use of this time to
implement a feature requested by one
manage the next release of Synapse (i.e. 1.1) the way things are
using a few tricks like putting our copy of the transport in-front of
the Axis2-kernel etc. at runtime.
Why do you need trickery? The transports are coming out of axis2.xml
.. why can you not simply put another transport in
Note: For some strange reason, this mail returned twice with the error:
axis-dev@ws.apache.org:
140.211.11.136 failed after I sent the message.
Remote host said: 552 spam score (5.9) exceeded threshold
and thus I am sending this as a new message instead of a reply to the thread
to support Synapse
thanks
asankha
On 05/10/2007, Asankha C. Perera [EMAIL PROTECTED] wrote:
Note: For some strange reason, this mail returned twice with the error:
axis-dev@ws.apache.org:
140.211.11.136 failed after I sent the message.
Remote host said: 552 spam score (5.9) exceeded
Sorry to drop in late on this one..
What would be ideal is just a separation of the Axis2 transports code
into a separate module within Axis2 - i.e. outside of the Kernel.
thanks
asankha
Ruwan Linton wrote:
Hi Chinthaka,
It does have API level problems and that is why we are running in to
+1
asankha
Nandika Jayawardana wrote:
+1
Thanks
Nandika
On 10/3/07, *Ruchith Fernando* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
+1
Thanks,
Ruchith
On 10/1/07, Kaushalye Kapuruge [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi Devs,
I have
Hi Leo
Thanks for the issue information. What if we set the content type used
when writing the message as a JMS header to the text message? do you
think this will solve the problem? Also could you attach the stack trace
for the error you receive
Currently I have performed quite a few
Dims
Thank you for all your contributions to the WS projects, esp for Synapse
and Axis2.
Look forward to seeing you back again soon, and wish you all the very best
best regards
asankha
Paul Fremantle wrote:
Dims
I think its a great shame you are leaving. I know we will miss your
Paul
I may be wrong, however, I haven't seen many people actually using JMS
Map messages.. The Axis2 JMS transport thus supports bytes and text
messages. So I would think this is a cool feature, but only few many
find it actually useful...
asankha
Paul Fremantle wrote:
One more thought.
: transports
Affects Versions: nightly
Reporter: Asankha C. Perera
Assignee: Asankha C. Perera
Priority: Critical
Fix For: 1.3
The NIO HTTPS transport is throwing a java.nio.charset.MalformedInputException
when a connection was being attempted
[
https://issues.apache.org/jira/browse/AXIS2-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-2919.
--
Resolution: Fixed
This was caused by a line that I had commented out to compile
Deepal
These are things I noted with the RC1:
1. missing log4j JAR from lib
2. better to add the lib folder itself to the start of the classpath
(axisserver.sh/bat) - this would help us place java keystores etc in the
lib for other purposes easily
3. place default log4j.properties in lib
Paul
This is what happens in Synapse.. but I do not promote the NIOSender to
simple clients as it is designed to send out many requests and not a
single message etc. So for a typical client scenario the NIO sender is
not suitable from how I see it.
asankha
Paul Fremantle wrote:
Asankha,
[
https://issues.apache.org/jira/browse/AXIS2-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510160
]
Asankha C. Perera commented on AXIS2-2819:
--
Mathieu
I do not think this is a blocker, so I would like
[
https://issues.apache.org/jira/browse/AXIS2-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510162
]
Asankha C. Perera commented on AXIS2-2819:
--
Mathieu
Can you try this with the latest (nightly) build
1 - 100 of 202 matches
Mail list logo