Hi,
you will also need a custom Invoker that does *not* invoke the service
Best regards,
Bernd.
Tomek Sztelak wrote:
You can check AbstractXFireTest source code ( and some test classes
derived from it ) to get idea how to call service with given soap
document ( something like : Document doc =
invokeService("LoginService"login.xml"); )
On 10/26/06, Sarkar, Abanindra <[EMAIL PROTECTED]> wrote:
We have a requirement where we will receive the complete SOAP message
(with
or without MIME/MTOM attachments) as a org.w3c.dom.Document and need
to pass
this Document to an embedded XFire SOAP Engine to process. Following
is the
exact things that we are looking from the XFire SOAP engine:
1. We will be able to start the the XFire SOAP engine using this
Document
object.
2. The incoming SOAP message will carry Document/Literal style SOAP
request for a Web Service end-point which is not a POJO or EJB. We don't
want the XFire SOAP engine to call this end-point. The web service
end-point
will be called by a separate service within a Business Process. But the
XFire SOAP engine should be able to process all the Headers of this
incoming
SOAP request through some custom handlers.
3. The XFire SOAP engine should be able to generate a SOAP Response
from
an org.w3c.dom.Document document.
The overall idea is to use XFire to process all the Headers of an
incoming SOAP Message without actually called the end-point from the
engine
and the bundled the response within a SOAP response.
I was going through all the documents that are present in the
http://xfire.codehaus.org but found nothing that explain me how we can
achieve something like this with XFire SOAP engine.
--
Dr. Bernd Schuller
Central Institute for Applied Mathematics
Forschungszentrum Juelich GmbH
mail [EMAIL PROTECTED]
phone +49 2461 61 8736
fax +49 2461 61 6656
blog http://www.jroller.com/page/gridhaus
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
