Re: Axis2/Rampart WS-Security performance

we did in Rounds 1, 2, and 3 before. This was to trigger the JVM 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

Re: Axis2/Rampart WS-Security performance

e take a couple of hours 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

Re: Axis2/Rampart WS-Security performance

d in investigating further, the full source code > for the performance comparison is available as a download from the > article. > > - Dennis > -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com

Re: [VOTE] Release Axis2 Transports 1.0.0

/synapse/branches/1.2> > https://svn.apache.org/repos/asf/webservices/commons/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

Re: Axis2 1.5 beta 2 fails during the building of the Scripting module

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

Re: Releasing transports 1.0 - dependency resolutions

d local back 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

Re: Releasing transports 1.0 - dependency resolutions

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

Re: Releasing transports 1.0 - dependency resolutions

Jarek Gawor wrote: On Tue, Mar 31, 2009 at 12:22 AM, Asankha C. Perera 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 wouldn't

Re: Releasing transports 1.0 - dependency resolutions

g about moving code back :-[ ? cheers asankha -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com

Javamail dependency

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

[jira] Resolved: (AXIS2-4212) ListenerManager Shutdown Hook Attempts to Unregister Itself

[ 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

[jira] Commented: (AXIS2-4212) ListenerManager Shutdown Hook Attempts to Unregister Itself

[ https://issues.apache.org/jira/browse/AXIS2-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679196#action_12679196 ] Asankha C. Perera commented on AXIS2-4212: -- I've done this to trun

Re: Is there a nightly build / Maven repo, for the Axis2 1.5 branch?

uld be happy 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, ht

[jira] Commented: (AXIS2-3514) HttpCoreNIOSender throws NullPointerException

[ https://issues.apache.org/jira/browse/AXIS2-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677645#action_12677645 ] Asankha C. Perera commented on AXIS2-3514: -- Michele For 1 I would actually

[jira] Commented: (AXIS2-4088) Async msg processing/ callback for msg ID not found

[ https://issues.apache.org/jira/browse/AXIS2-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677642#action_12677642 ] Asankha C. Perera commented on AXIS2-4088: -- See http://issues.apache.org/

[jira] Resolved: (AXIS2-1381) Need to enhance code generation from WSDL to support JMS extensions

[ 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 this is

[jira] Commented: (AXIS2-2993) the async message receiver could use NIO

[ https://issues.apache.org/jira/browse/AXIS2-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677236#action_12677236 ] Asankha C. Perera commented on AXIS2-2993: -- Hi Deepal Lets take this conc

[jira] Resolved: (AXIS2-4025) Using JMSMessageID as correlationID for JMS messages

[ 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 i

Re: Is there a nightly build / Maven repo, for the Axis2 1.5 branch?

and am going through 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

[jira] Resolved: (AXIS2-4088) Async msg processing/ callback for msg ID not found

[ 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 withi

[jira] Resolved: (AXIS2-4188) JMSSender not extendable

[ 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 contribute

[jira] Resolved: (AXIS2-3514) HttpCoreNIOSender throws NullPointerException

[ 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 withi

[jira] Resolved: (AXIS2-3661) ClientHandler prints the full stack trace if the client shuts down the connection

[ 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 withi

[jira] Resolved: (AXIS2-3496) org.apache.axis2.transport.nhttp.ServerWorker - Error processing POST request when the service throws an exception

[ 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. If the

[jira] Resolved: (AXIS2-3428) NullPointerException in HttpCoreNIOSender

[ 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 withi

[jira] Resolved: (AXIS2-3309) NPE throws when starting axis2server if NIO https transport is enabled in axis2.xml

[ 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. If the

[jira] Resolved: (AXIS2-2993) the async message receiver could use NIO

[ 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)

[jira] Resolved: (AXIS2-3473) HTTP NIO fails to process response

[ 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 withi

[jira] Resolved: (AXIS2-3460) AxisFault in ClientHandler (http NIO sender)

[ 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 withi

Is there a nightly build / Maven repo, for the Axis2 1.5 branch?

-- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot.com

Re: Axis2 doesn't play nice with PFP (payflow, paypal)

that to the next time you want to revisit Axis2 cheers asankha -- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot.com

Re: Axis2 doesn't play nice with PFP (payflow, paypal)

www.xyz.com 443" and see what happens? cheers asankha -- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot.com

[jira] Closed: (AXIS2-4213) Dead Letter Queue Based Recovery

[ 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 transpo

Re: svn commit: r734201 - in /webservices/axis2/trunk/java/modules: addressing/pom.xml saaj/pom.xml

e Axis2 project :-) Andreas On Wed, Jan 14, 2009 at 04:38, Asankha C. Perera 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, e.g. jaxws and metadata).

Re: svn commit: r734201 - in /webservices/axis2/trunk/java/modules: addressing/pom.xml saaj/pom.xml

e testing scope in maven -- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot.com

[jira] Created: (AXIS2-4196) AxisEngine meddles with concerns of the transports, and creates a thread when sending out a message

/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 the

Enhancements to the JMS transport in WS-Commons / Transports

. 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=724432&content-type=text%2Fhtml -- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot

[jira] Resolved: (AXIS2-3238) Encoding of text messages using SOAP over JMS

[ 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

[jira] Resolved: (AXIS2-3485) Failure to start JMS listener badly reported

[ 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

[jira] Resolved: (AXIS2-3774) WSDL is not getting generated with SOAP Over 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

[jira] Commented: (AXIS2-4025) Using JMSMessageID as correlationID for JMS messages

[ https://issues.apache.org/jira/browse/AXIS2-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654506#action_12654506 ] Asankha C. Perera commented on AXIS2-4025: -- Hi Cathal We have updated the

[jira] Resolved: (AXIS2-1665) JMS destination should not be dedicated to only a single service

[ 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

[jira] Resolved: (AXIS2-3088) Set header fields of JMS message

[ 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 as

[jira] Resolved: (AXIS2-4164) Allow to specify JMS username and password directly via properties in JMS Transport.

[ 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

[jira] Resolved: (AXIS2-545) WSDL port address for JMS

[ 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.. if not

[jira] Assigned: (AXIS2-3662) Can't use JMS transport from axis2.war on WebSphere Application Server 6.1

[ 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 W

[jira] Resolved: (AXIS2-3662) Can't use JMS transport from axis2.war on WebSphere Application Server 6.1

[ 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

Re: Committing patch contributed for MIME message parser and serializer based on Apache mime4j [WSCOMMONS-387]

PROTECTED]> wrote: 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. Ol

Re: [VOTE] Axis2 as TLP

in with your VOTE on this (and indicate binding/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://

Re: Committing patch contributed for MIME message parser and serializer based on Apache mime4j [WSCOMMONS-387]

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 pars

Re: Cluttering of debug logs for each Parameter add

, Nov 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 m

Re: Cluttering of debug logs for each Parameter add

.. 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 the

Cluttering of debug logs for each Parameter add

(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

Re: [VOTE] Andreas Veithen as a WS committer

+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 of

[VOTE] Andreas Veithen as a WS committer

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 A

Re: [Axis2] Moving all the transports into a common modules

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 transp

Re: Understanding asynchrounous request processing in Apache Synapse/Axis2/Http Core NIO

or a large response. Once you 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

Re: next axis2 release with healthy JMS support

CTED]> For additional commands, e-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

Re: [Axis2][1.4.1] Nandana as Release Manager (Re: Security hole in Axis2 1.4 + Rampart 1.4)

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 it

[jira] Resolved: (AXIS2-3887) The servlet transport does not set the HTTP response code to 500 when a SOAP fault is returned (unless an exception was thrown)

[ 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 d

[jira] Created: (AXIS2-3887) The servlet transport does not set the HTTP response code to 500 when a SOAP fault is returned (unless an exception was thrown)

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

Re: Extensions to Axis2/Java deployment engine

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. Synapse

Re: Extensions to Axis2/Java deployment engine

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

Re: Extensions to Axis2/Java deployment engine

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 t

Re: Extensions to Axis2/Java deployment engine

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

Re: Sample i/p message for Axis2 JMS

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

Re: [Axis2 1.3] SimpleMailListener denys SOAP11 content-ype

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] http://repo1.maven.org/maven2/org/apache/s

Re: Using Webservice via SMTP: SOAP message in body

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

Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse

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 core

Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse

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 th

Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse

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

Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse

Check this thread 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 http://marc.info/?t=1196846803000

Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse

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 t

Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse

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 car

[jira] Commented: (AXIS2-3662) Can't use JMS transport from axis2.war on WebSphere Application Server 6.1

[ https://issues.apache.org/jira/browse/AXIS2-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585893#action_12585893 ] Asankha C. Perera commented on AXIS2-3662: -- Hi George Actually I looked into

[jira] Commented: (AXIS2-3662) Can't use JMS transport from axis2.war on WebSphere Application Server 6.1

[ https://issues.apache.org/jira/browse/AXIS2-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584054#action_12584054 ] Asankha C. Perera commented on AXIS2-3662: -- The original post above stated

[jira] Commented: (AXIS2-3428) NullPointerException in HttpCoreNIOSender

[ https://issues.apache.org/jira/browse/AXIS2-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575069#action_12575069 ] Asankha C. Perera commented on AXIS2-3428: -- Deepal - Is point # 2 above cor

[jira] Commented: (AXIS2-3428) NullPointerException in HttpCoreNIOSender

[ https://issues.apache.org/jira/browse/AXIS2-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573768#action_12573768 ] Asankha C. Perera commented on AXIS2-3428: -- Michele I tried your test suite,

Re: Axis2 JMSListener on Websphere

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 JM

Re: Mail transport implementation for Synapse/Axis2

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

Mail transport implementation for Synapse/Axis2

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 the

Re: Getting axis2 transport out from the kernel

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 and

Re: Getting axis2 transport out from the kernel

need not be in a hurry 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: : 140.211.11.136 failed after I sent the message. Remote host said: 552 spam score (5.9

Re: Getting axis2 transport out from the kernel

Note: For some strange reason, this mail returned twice with the error: : 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 Guys..

Re: Getting axis2 transport out from the kernel

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

Re: [jira] Created: (AXIS2-3238) Encoding of text messages using SOAP over JMS

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 enhance

Re: So Long, and Thanks for All the Fish

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 contributi

Re: Transactional JMS.

Hi Maciej I am traveling this week and will not be able to reply in detail until the weekend. However I have made some enhancements to the JMS code - esp to re-use sessions when sending out. Currently the code is under a module called Synapse-transports for you to take a peek

Re: Supporting content types in Synapse and Axiom

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. A

Re: [ANN][Axis2] Axis2 1.3-RC1 release

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 Thes

[jira] Resolved: (AXIS2-2919) NIO-HTTPS transport throws a MalformedInputException

[ 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 the

[jira] Created: (AXIS2-2919) NIO-HTTPS transport throws a MalformedInputException

: 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

Re: Question about NIO HTTP sender and thread behaviour

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, Di

[jira] Commented: (AXIS2-2819) Faulty handling of JMS asynchronous calls

[ 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 to

[jira] Commented: (AXIS2-2819) Faulty handling of JMS asynchronous calls

[ 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 the

[jira] Assigned: (AXIS2-2864) JMS addressing (SOAPBody addressing) is broken. The new dispatchers can't resolve the required operation

[ https://issues.apache.org/jira/browse/AXIS2-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Asankha C. Perera reassigned AXIS2-2864: Assignee: Davanum Srinivas (was: Asankha C. Perera) Dims I don't think th

[jira] Commented: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections

[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509279 ] Asankha C. Perera commented on AXIS2-2816: -- Hi Mark Checked in the patch with visual verification. Please

[jira] Assigned: (AXIS2-2819) Faulty handling of JMS asynchronous calls

[ https://issues.apache.org/jira/browse/AXIS2-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Asankha C. Perera reassigned AXIS2-2819: Assignee: Glen Daniels (was: Asankha C. Perera) Glen, can you take a look at this

[jira] Commented: (AXIS2-2819) Faulty handling of JMS asynchronous calls

[ https://issues.apache.org/jira/browse/AXIS2-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506858 ] Asankha C. Perera commented on AXIS2-2819: -- This seems like a Addressing issue to me.. when we get a JMS

[jira] Resolved: (AXIS2-2816) JMS over WebsphereMQ doesn't support 'CLIENT' connections

[ https://issues.apache.org/jira/browse/AXIS2-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Asankha C. Perera resolved AXIS2-2816. -- Resolution: Fixed Fix Version/s: 1.3 Mark I have applied the patch after a

  1   2   3   >