[Q] Adding SOAP as module of KomHttpService(like Seaside)

Masashi UMEZAWA masashi.umezawa at gmail.com
Mon Jun 18 22:59:30 UTC 2007


Hi Philippe,

Thanks. But I think both needs additional overheads (changing Kom
request to Seaside one, and  back again). Since SoapHttpModule can
handle KomRequest natively, I think my solution is natural in this
case. (Generally, too many subclasses of WAKom is not good).

Cheers,

2007/6/19, Philippe Marschall <philippe.marschall at gmail.com>:
> A clean solution would either be a subclass of WAMail and override #start: or
> a subclass of WAEntryPoint and override #handleRequest:
>
> Cheers
> Philippe
>
> 2007/6/18, Masashi UMEZAWA <masashi.umezawa at gmail.com>:
> > Hi Sungjin,
> >
> > A simple solution is to make a subclass of WAKom and override
> > #process: for  dispatching like:
> >
> > process: komRequest
> >         komRequest url = '/soap' ifTrue:[ ^ self soapModule process: komRequest].
> >         ^ super process: komRequest
> >
> > soapModule
> >         soapModule ifNil: [soapModule := SoapHttpModule new].
> >         ^soapModule
> >
> > Cheers,
> >
> > 2007/6/18, Sungjin Chun <chunsj at embian.com>:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Hi,
> > >
> > > How can I add soap processing module to KomHttpService as Seaside so
> > > that I can assign "/soap" as url for soap. For example Seaside
> > > uses "/seaside" for its service url for KomHttpService. What I want to
> > > do is use same port number for seaside and soap, only url be different.
> > >
> > > Sorry for my poor English and Thanks in advance.
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.4.2.2 (GNU/Linux)
> > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> > >
> > > iD8DBQFGdfFiQqspS1+XJHgRAgVfAKCdPVOOniDHS/R9scE6Bbg+85YpSwCeJcUL
> > > b4R37ckhk7NHV2RZc8ZR/is=
> > > =0U51
> > > -----END PGP SIGNATURE-----
> > >
> > --
> > [:masashi | ^umezawa]
> >

-- 
[:masashi | ^umezawa]



More information about the Squeak-dev mailing list