soap and xsl

[roman seidl <rs...@pvl.at>]

Hi cocoon-dev,

  As i read in this list XSP tends to be quite slow. So i thought of
  how to get rid of xsp. So I consider the following concept:

  <producer from request>-<xsl (= file in request path)>-<soap
  processor>-<xsl>-<publisher>-<client>

  I would use an processor from request and use an xslt sheet to
  decide on any reaction on the request (decide which sheet based on
  the url or on a sitemap. Then i would send it through a soap
  processor an access an ejb container. The result of the SOAP
  calls would be formatted and published.

  I don´t know if this would deliver acceptable perfomance and be
  feasible to develop applications with but maybe I should try. I
  think it should be very easy to optimize as it would highly profit
  from a fast (compiling?) xslt parser which is easier to get than
  good xsp code. Furthermore it would be able to put all java code
  into the application server environment.

  Finally one could write an in-memory SOAP processor for jboss so
  there had to be no HTTP call for accessing a SOAP server.

mfg
roman                          
--
-------------------------------------------------------------------
Roman Seidl                                   Design & Development
-------------------------------------------------------------------
Public Voice Lab                       Operngasse 24, A-1040 Vienna 
Tel.: +43-1-585 22 80/23                   Fax:  +43-1-585 22 80/99
e-mail: rse@pvl.at                                  web: www.pvl.at
-------------------------------------------------------------------