Re: Release plan for 0.90

[Asankha C. Perera]

Paul and others... I have included nhttp into dist-bin and you could get the latest code off svn to play around. The example #2 "ant proxystockquote" fails due to a limitation in AsyncWeb (see email attahced below).. but this is not very serious right now as I see and would go away once we complete our own non blocking http soon. Please let me know your feedback, and I will start updating docs for 0.90 now thanks asankha Asankha C. Perera wrote: Paul I have just checked in the changes for the new Policy framework with two sample services which could be deployed on an Axis2 instance and a sample Synapse configuration to demonstrate this. Though the first example works, the second example which demonstrates signing and encryption fails on the Axis2 server side currently due to an issue I couldn't figure out yet with help from Ruchith. But it seems like its not on Synapse side, and hence I'm checking in these changes. Also when Rampart is being used, we are hit by http://issues.apache.org/jira/browse/WSCOMMONS-104 which prevents Synapse from reading a SOAP fault in an incoming fault message. This again is out of our scope, and should work once Axiom is fixed - though this may take some time. asankha -------- Original Message -------- Subject: RE: [asyncWeb] Bug in the URIPathDecoder? Date: Thu, 24 Aug 2006 11:09:57 +0100 From: Irving, Dave <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: <[EMAIL PROTECTED]> Behalf Of Asankha C. Perera wrote: > Hi Hi Asankha > I have an implementation of an HttpService where I override > public void handleRequest(HttpRequest request). When this > gets invoked I get the result of request.getRequestURI() as > "http:/localhost:9000/axis2/services/SimpleStockQuoteService" > when my actual request to the server was whats shown below > according to tcpmon. > Note that the "//" has become "/". Oooops.... :o( > I assume this it because of the way the HexEscaper's handleByte() and > handleSlash() operates, which seems to stip two forward > slashes. Is this the expected behavior or is it a bug? This is a bug. We have some work to do to provide full URI handling - and right now we just handle collapsing // in to /. However, the general URI syntax is: <scheme>://<authority><path>?<query> So we should not be applying this dodgy '//' colapsing until the path component. I'll raise a JIRA for this issue (and, of course, patches are always gratefully received :o) > thanks > asankha Dave This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. _______________________________________________ Dev mailing list [EMAIL PROTECTED] http://www.safehaus.org/mailman/listinfo/dev --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]