On Tue, 13 Nov 2001 19:01:15 -0800, "Greg Weinger" <[EMAIL PROTECTED]> wrote:

> >From the documentation on hp's site it appears that the soap taglib can 
> support SOAP RPC as well as document exchange, but only provides an 
> example of document exchange 
> (http://www.e-speak.hp.com/faq/faqs_howto.shtm#10).

The SOAP logicsheet doesn't care whether the body of the message is a
normal XML fragment part of a document exchange or a SOAP RPC
fragment. It simply passes along to the server the fragment embedded
inside the soap:call element.

In fact the sample you refer to uses on the server side a SOAP RPC
service to process the request.

> Does the SOAP taglib in HEAD also support RPC?  If so, could someone 
> please provide example XSP code?

As I mentioned above, the SOAP logicsheet makes no distinction between
document exchange and SOAP RPC. This is possible because the SOAP
logicsheet doesn't use any SOAP Java client library to do the work,
it's based purely on Cocoon components.

For examples check out the code from Cocoon's CVS and take a look at
the XScript/SOAP samples that appear on the main page. In the source
tree they are located in webapp/doc/samples/xscript/.

Note that the API of the XML elements has changed compared to HPWS'
xstream elements, it now uses the XScript concept. This allows for
arbitrary Java objects, whether they can or they cannot be represented
as XML, to be manipulated in XSP pages. Examples of such objects
include SQL result sets, objects obtained from the POST request
etc. Please consider what is in Cocoon's CVS as the latest bits,
current HPWS development versions use the same source code base.

Regards,
-- 
Ovidiu Predescu <[EMAIL PROTECTED]>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to