RE: [Asyncweb] Updates on recent changes
Thanks for the prompt reply!! I too would recommend to post some notifications for this change... it took me two working days to find that it's moved I suppose that since there are some major modifications to AsyncWeb, the implementation by Dan wouldn't work straightaway. Just to avoid any reinvention, did anybody try to port the same i.e. CXF transport, for latest Asyncweb + Mina? Also, any pointers on the major modifications would also serve great help. Thanks!! Regards, Harbhanu _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Karasulu Sent: Wednesday, June 18, 2008 9:44 PM To: dev@mina.apache.org Cc: [EMAIL PROTECTED] Subject: Re: [Asyncweb] Updates on recent changes Including original sender in CC list. On Wed, Jun 18, 2008 at 12:12 PM, Alex Karasulu [EMAIL PROTECTED] wrote: Forwarding to MINA dev - hope you don't mind. And yes asyncweb has been moved to Apache under the Apache MINA Project. More inline ... On Wed, Jun 18, 2008 at 10:31 AM, harbhanu [EMAIL PROTECTED] wrote: Hi, I want to use Asyncweb for transport in CXF. Also managed to get one implementation written by Dan Diephouse Yeah Dan did some work on this as well as a presentation a while back at OSCON. Here's a link to it: http://conferences.oreillynet.com/cs/os2006/view/e_sess/9065 But currently I am getting some errors, which in am not sure whether it is due to ASYNCWEB or because of incompatible ASYNCWEB and MINA versions. java.lang.NoSuchMethodError: org.safehaus.asyncweb.service.transport.mina.DefaultHttpIoHandler.getFactory ()Lorg/apache/mina/handler/multiton/SingleSessionIoHandlerFactory; Yep you're using an old Safehaus version that is no longer supported. I should remove the safehaus site and repository so this does not happen again. Please point me to the latest version or last compatible versions Take a look at http://svn.apache.org/repos/asf/mina/asyncweb/trunk. There you'll find the latest up to date version of Asyncweb separated into a couple new modules instead of being one module. Also, let me know from where I can find the latest releases/activities of Asyncweb. Is it still present in safehaus or moved under MINA at apache.?? @ Apache yes. Nothing has been released to date. You'll have to use what we have in the trunk building it yourself. Regards, Alex
Re: [Asyncweb] Updates on recent changes
On Thu, Jun 19, 2008 at 3:10 AM, harbhanu [EMAIL PROTECTED] wrote: Thanks for the prompt reply!! My pleasure. I too would recommend to post some notifications for this change... it took me two working days to find that it's moved Yeah we've just been trying to get the house in order. But yes we need to do this and shutdown what remains over at Safehaus. I suppose that since there are some major modifications to AsyncWeb, the implementation by Dan wouldn't work straightaway. Right. Would love for a volunteer to port it. Dan was brought on as a committer here to do things like that if he gets the time but anyone is welcome to bring us up to speed again. Scratch the itch :). Just to avoid any reinvention, did anybody try to port the same i.e. CXF transport, for latest Asyncweb + Mina? Nope. Also, any pointers on the major modifications would also serve great help. Thanks!! That's hard since many things were done in transit to Apache. Best thing is to look at the ASF svn logs. Regards, Alex Regards, Harbhanu -- *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Alex Karasulu *Sent:* Wednesday, June 18, 2008 9:44 PM *To:* dev@mina.apache.org *Cc:* [EMAIL PROTECTED] *Subject:* Re: [Asyncweb] Updates on recent changes Including original sender in CC list. On Wed, Jun 18, 2008 at 12:12 PM, Alex Karasulu [EMAIL PROTECTED] wrote: Forwarding to MINA dev - hope you don't mind. And yes asyncweb has been moved to Apache under the Apache MINA Project. More inline ... On Wed, Jun 18, 2008 at 10:31 AM, harbhanu [EMAIL PROTECTED] wrote: Hi, I want to use Asyncweb for transport in CXF. Also managed to get one implementation written by Dan Diephouse Yeah Dan did some work on this as well as a presentation a while back at OSCON. Here's a link to it: http://conferences.oreillynet.com/cs/os2006/view/e_sess/9065 But currently I am getting some errors, which in am not sure whether it is due to ASYNCWEB or because of incompatible ASYNCWEB and MINA versions. java.lang.NoSuchMethodError: org.safehaus.asyncweb.service.transport.mina.DefaultHttpIoHandler.getFactory()Lorg/apache/mina/handler/multiton/SingleSessionIoHandlerFactory; Yep you're using an old Safehaus version that is no longer supported. I should remove the safehaus site and repository so this does not happen again. Please point me to the latest version or last compatible versions Take a look at http://svn.apache.org/repos/asf/mina/asyncweb/trunk. There you'll find the latest up to date version of Asyncweb separated into a couple new modules instead of being one module. Also, let me know from where I can find the latest releases/activities of Asyncweb. Is it still present in safehaus or moved under MINA at apache…?? @ Apache yes. Nothing has been released to date. You'll have to use what we have in the trunk building it yourself. Regards, Alex
Re: [Asyncweb] Updates on recent changes
On Thu, 19 Jun 2008 12:40:00 +0530 harbhanu [EMAIL PROTECTED] wrote: Thanks for the prompt reply!! I too would recommend to post some notifications for this change... it took me two working days to find that it's moved I suppose that since there are some major modifications to AsyncWeb, the implementation by Dan wouldn't work straightaway. Just to avoid any reinvention, did anybody try to port the same i.e. CXF transport, for latest Asyncweb + Mina? Also, any pointers on the major modifications would also serve great help. Thanks!! Hi, For the change on the server I seen : - http decoder rewrote using mina codec state machine - static file server module added for serving plain old static files - http service mapper using regexp in place of full url matching As some side project a fast-cgi implementation, you can find some info about that on this ML Julien signature.asc Description: PGP signature
Re: [Asyncweb] Updates on recent changes
Forwarding to MINA dev - hope you don't mind. And yes asyncweb has been moved to Apache under the Apache MINA Project. More inline ... On Wed, Jun 18, 2008 at 10:31 AM, harbhanu [EMAIL PROTECTED] wrote: Hi, I want to use Asyncweb for transport in CXF. Also managed to get one implementation written by Dan Diephouse Yeah Dan did some work on this as well as a presentation a while back at OSCON. Here's a link to it: http://conferences.oreillynet.com/cs/os2006/view/e_sess/9065 But currently I am getting some errors, which in am not sure whether it is due to ASYNCWEB or because of incompatible ASYNCWEB and MINA versions. java.lang.NoSuchMethodError: org.safehaus.asyncweb.service.transport.mina.DefaultHttpIoHandler.getFactory()Lorg/apache/mina/handler/multiton/SingleSessionIoHandlerFactory; Yep you're using an old Safehaus version that is no longer supported. I should remove the safehaus site and repository so this does not happen again. Please point me to the latest version or last compatible versions Take a look at http://svn.apache.org/repos/asf/mina/asyncweb/trunk. There you'll find the latest up to date version of Asyncweb separated into a couple new modules instead of being one module. Also, let me know from where I can find the latest releases/activities of Asyncweb. Is it still present in safehaus or moved under MINA at apache…?? @ Apache yes. Nothing has been released to date. You'll have to use what we have in the trunk building it yourself. Regards, Alex
Re: [Asyncweb] Updates on recent changes
Including original sender in CC list. On Wed, Jun 18, 2008 at 12:12 PM, Alex Karasulu [EMAIL PROTECTED] wrote: Forwarding to MINA dev - hope you don't mind. And yes asyncweb has been moved to Apache under the Apache MINA Project. More inline ... On Wed, Jun 18, 2008 at 10:31 AM, harbhanu [EMAIL PROTECTED] wrote: Hi, I want to use Asyncweb for transport in CXF. Also managed to get one implementation written by Dan Diephouse Yeah Dan did some work on this as well as a presentation a while back at OSCON. Here's a link to it: http://conferences.oreillynet.com/cs/os2006/view/e_sess/9065 But currently I am getting some errors, which in am not sure whether it is due to ASYNCWEB or because of incompatible ASYNCWEB and MINA versions. java.lang.NoSuchMethodError: org.safehaus.asyncweb.service.transport.mina.DefaultHttpIoHandler.getFactory()Lorg/apache/mina/handler/multiton/SingleSessionIoHandlerFactory; Yep you're using an old Safehaus version that is no longer supported. I should remove the safehaus site and repository so this does not happen again. Please point me to the latest version or last compatible versions Take a look at http://svn.apache.org/repos/asf/mina/asyncweb/trunk. There you'll find the latest up to date version of Asyncweb separated into a couple new modules instead of being one module. Also, let me know from where I can find the latest releases/activities of Asyncweb. Is it still present in safehaus or moved under MINA at apache…?? @ Apache yes. Nothing has been released to date. You'll have to use what we have in the trunk building it yourself. Regards, Alex
Re: [Asyncweb] Updates on recent changes
On Sat, 26 Jan 2008 18:26:34 -0500 Alex Karasulu [EMAIL PROTECTED] wrote: Hi all, I started cleaning up and organizing the Asyncweb subproject today which entailed: o moving Asyncweb out of the sandbox into the new structure discussed here [0] with slight differences o moving filter-codec-http into Asyncweb as a module o changing package names o moving 3 classes of protocol-http-client into Asyncweb as a module o cleaning up NOTICE.txt and LICENSE.txt files o cleaning up problems resulting from back and forth movement of the HTTP codec Here's what the present directory structure of asyncweb looks like as seen here [1]: ... mina/asyncweb . |-- branches |-- tags `-- trunk |-- LICENSE.txt |-- NOTICE.txt |-- assembly |-- client |-- common |-- examples |-- pom.xml |-- server `-- spring There are 6 modules here. Some points about the module migrations and name changes: [NOTE: Below the module name based on the maven POM's name tag is used.] Module: Apache Asyncweb Common - Most of a common package containing the HttpX interfaces was, as shown earlier, re-factored and moved into the MINA subproject along with the HTTP codec into the MINA filter-codec-http module. Asyncweb is not concerned with advertising that this module and it's artifact is a MINA codec which a small part of it contains. Furthermore this module is shared between the http client AHC (3 classes) and the Asyncweb server. Because of these reasons it was best called the asyncweb-common module. Again the fact that this module contains a codec is irrelevant. Module: Apache Asyncweb Client - The Asyncweb Client module is comprised of 3 Java source files and represents the previous protocol-http-client which was referred to as Async HTTP Client (AHC). This module depends on and uses the Asyncweb Common API and the HTTP codec within it to function. Hence as discussed and out of common sense this protocol-http-client module in the MINA subproject was moved under Asyncweb as the Apache Asyncweb Client module. Module: Apache Asyncweb Server -- This represents the old Asyncweb 'core' module from the sandbox with the mentioned cleanups. Module: Apache Asyncweb Spring -- This represents the old Asyncweb 'springframework' integration module from the sandbox with the mentioned cleanups. Module: Apache Asyncweb Examples --- This represents the old Asyncweb 'example' module from the sandbox with the mentioned cleanups. Module: Apache Asyncweb Assembly --- This represents the old Asyncweb 'assembly' module from the sandbox with minor cleanups. I hope everyone has a chance to take a look, build etc and give feedback. If curious and you don't have the time here's what the build run output looks like with these names and this structure. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Asyncweb Parent [INFO] Apache Asyncweb Common [INFO] Apache Asyncweb Server [INFO] Apache Asyncweb Client [INFO] Apache Asyncweb Spring [INFO] Apache Asyncweb Examples ... [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache Asyncweb Parent SUCCESS [ 1.856s] [INFO] Apache Asyncweb Common SUCCESS [ 4.871s] [INFO] Apache Asyncweb Server SUCCESS [ 3.959s] [INFO] Apache Asyncweb Client SUCCESS [ 11.553s] [INFO] Apache Asyncweb Spring SUCCESS [ 0.668s] [INFO] Apache Asyncweb Examples .. SUCCESS [ 0.795s] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] I hope this report clarifies the changes and helps people get back up to speed with Asyncweb. Thanks, Alex [0] Directory Restructuring Thread - http://tinyurl.com/23dclx [1] Asynchweb in Subversion - http://svn.apache.org/repos/asf/mina/asyncweb Hi, nice job Alex, I'll try to build that today. BTW does it mean AHC is officially renamed to Asyncweb Client, it's a bit hard to follow ;) Julien
Re: [Asyncweb] Updates on recent changes
Hi Julien, On Jan 28, 2008 5:27 AM, Julien Vermillard [EMAIL PROTECTED] wrote: Hi, nice job Alex, I'll try to build that today. BTW does it mean AHC is officially renamed to Asyncweb Client, it's a bit hard to follow ;) I guess unofficially we've been calling the 3 client classes for the HTTP client the Async HTTP Client? We can call the whole thing async or call it asyncweb. It does not matter to me as long as we don't waste time. I just used what was there since cleanup and organization was most important to me. Alex
Re: [Asyncweb] Updates on recent changes
Thanks, Alex. I've re-fetched the project and am looking it over.
[Asyncweb] Updates on recent changes
Hi all, I started cleaning up and organizing the Asyncweb subproject today which entailed: o moving Asyncweb out of the sandbox into the new structure discussed here [0] with slight differences o moving filter-codec-http into Asyncweb as a module o changing package names o moving 3 classes of protocol-http-client into Asyncweb as a module o cleaning up NOTICE.txt and LICENSE.txt files o cleaning up problems resulting from back and forth movement of the HTTP codec Here's what the present directory structure of asyncweb looks like as seen here [1]: ... mina/asyncweb . |-- branches |-- tags `-- trunk |-- LICENSE.txt |-- NOTICE.txt |-- assembly |-- client |-- common |-- examples |-- pom.xml |-- server `-- spring There are 6 modules here. Some points about the module migrations and name changes: [NOTE: Below the module name based on the maven POM's name tag is used.] Module: Apache Asyncweb Common - Most of a common package containing the HttpX interfaces was, as shown earlier, re-factored and moved into the MINA subproject along with the HTTP codec into the MINA filter-codec-http module. Asyncweb is not concerned with advertising that this module and it's artifact is a MINA codec which a small part of it contains. Furthermore this module is shared between the http client AHC (3 classes) and the Asyncweb server. Because of these reasons it was best called the asyncweb-common module. Again the fact that this module contains a codec is irrelevant. Module: Apache Asyncweb Client - The Asyncweb Client module is comprised of 3 Java source files and represents the previous protocol-http-client which was referred to as Async HTTP Client (AHC). This module depends on and uses the Asyncweb Common API and the HTTP codec within it to function. Hence as discussed and out of common sense this protocol-http-client module in the MINA subproject was moved under Asyncweb as the Apache Asyncweb Client module. Module: Apache Asyncweb Server -- This represents the old Asyncweb 'core' module from the sandbox with the mentioned cleanups. Module: Apache Asyncweb Spring -- This represents the old Asyncweb 'springframework' integration module from the sandbox with the mentioned cleanups. Module: Apache Asyncweb Examples --- This represents the old Asyncweb 'example' module from the sandbox with the mentioned cleanups. Module: Apache Asyncweb Assembly --- This represents the old Asyncweb 'assembly' module from the sandbox with minor cleanups. I hope everyone has a chance to take a look, build etc and give feedback. If curious and you don't have the time here's what the build run output looks like with these names and this structure. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Asyncweb Parent [INFO] Apache Asyncweb Common [INFO] Apache Asyncweb Server [INFO] Apache Asyncweb Client [INFO] Apache Asyncweb Spring [INFO] Apache Asyncweb Examples ... [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache Asyncweb Parent SUCCESS [ 1.856s] [INFO] Apache Asyncweb Common SUCCESS [ 4.871s] [INFO] Apache Asyncweb Server SUCCESS [ 3.959s] [INFO] Apache Asyncweb Client SUCCESS [ 11.553s] [INFO] Apache Asyncweb Spring SUCCESS [ 0.668s] [INFO] Apache Asyncweb Examples .. SUCCESS [ 0.795s] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] I hope this report clarifies the changes and helps people get back up to speed with Asyncweb. Thanks, Alex [0] Directory Restructuring Thread - http://tinyurl.com/23dclx [1] Asynchweb in Subversion - http://svn.apache.org/repos/asf/mina/asyncweb
Re: [Asyncweb] Updates on recent changes
Nice! Alex Karasulu wrote: Hi all, I started cleaning up and organizing the Asyncweb subproject today which entailed: o moving Asyncweb out of the sandbox into the new structure discussed here [0] with slight differences o moving filter-codec-http into Asyncweb as a module o changing package names o moving 3 classes of protocol-http-client into Asyncweb as a module o cleaning up NOTICE.txt and LICENSE.txt files o cleaning up problems resulting from back and forth movement of the HTTP codec Here's what the present directory structure of asyncweb looks like as seen here [1]: ... mina/asyncweb . |-- branches |-- tags `-- trunk |-- LICENSE.txt |-- NOTICE.txt |-- assembly |-- client |-- common |-- examples |-- pom.xml |-- server `-- spring There are 6 modules here. Some points about the module migrations and name changes: [NOTE: Below the module name based on the maven POM's name tag is used.] Module: Apache Asyncweb Common - Most of a common package containing the HttpX interfaces was, as shown earlier, re-factored and moved into the MINA subproject along with the HTTP codec into the MINA filter-codec-http module. Asyncweb is not concerned with advertising that this module and it's artifact is a MINA codec which a small part of it contains. Furthermore this module is shared between the http client AHC (3 classes) and the Asyncweb server. Because of these reasons it was best called the asyncweb-common module. Again the fact that this module contains a codec is irrelevant. Module: Apache Asyncweb Client - The Asyncweb Client module is comprised of 3 Java source files and represents the previous protocol-http-client which was referred to as Async HTTP Client (AHC). This module depends on and uses the Asyncweb Common API and the HTTP codec within it to function. Hence as discussed and out of common sense this protocol-http-client module in the MINA subproject was moved under Asyncweb as the Apache Asyncweb Client module. Module: Apache Asyncweb Server -- This represents the old Asyncweb 'core' module from the sandbox with the mentioned cleanups. Module: Apache Asyncweb Spring -- This represents the old Asyncweb 'springframework' integration module from the sandbox with the mentioned cleanups. Module: Apache Asyncweb Examples --- This represents the old Asyncweb 'example' module from the sandbox with the mentioned cleanups. Module: Apache Asyncweb Assembly --- This represents the old Asyncweb 'assembly' module from the sandbox with minor cleanups. I hope everyone has a chance to take a look, build etc and give feedback. If curious and you don't have the time here's what the build run output looks like with these names and this structure. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Apache Asyncweb Parent [INFO] Apache Asyncweb Common [INFO] Apache Asyncweb Server [INFO] Apache Asyncweb Client [INFO] Apache Asyncweb Spring [INFO] Apache Asyncweb Examples ... [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache Asyncweb Parent SUCCESS [ 1.856s] [INFO] Apache Asyncweb Common SUCCESS [ 4.871s] [INFO] Apache Asyncweb Server SUCCESS [ 3.959s] [INFO] Apache Asyncweb Client SUCCESS [ 11.553s] [INFO] Apache Asyncweb Spring SUCCESS [ 0.668s] [INFO] Apache Asyncweb Examples .. SUCCESS [ 0.795s] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] I hope this report clarifies the changes and helps people get back up to speed with Asyncweb. Thanks, Alex [0] Directory Restructuring Thread - http://tinyurl.com/23dclx [1] Asynchweb in Subversion - http://svn.apache.org/repos/asf/mina/asyncweb
