Hi,
Lukas Zapletal wrote:
Thank you very much for your tips and help. I am downloading jbi4corba
and evalute it.
Yes, exactly. I need to create "an translator", very simple but
dynamic. Incoming SOAP message "calling this method on that object
with these parameters" should be translated to CORBA call "call this
method on that object with given parameters and return the result".
The term "dynamic" is in meaning of "zero-conf" -- we do not want to
configure web services for this component. It should work
transparently: all information (object, method, parameters) are in the
SOAP request.
why not create a service for this -> SOAP2CorbaService ?
You can still dynamically select/create the object to invoke your
methods on. @see Xfire's AbstractInvoker class and it's subclasses.
You can also work on the SOAP XML directly using the message binding.
You mean to use ServiceDelegate.setExecutor? Executor is very simple
and bound to service. I do not want to create services because I do
not know in advance what services will be served.
I was thinking about implementing a Handler that will be bound to all
Transports. The hanler could listen to all incoming messages. What do
you think? Why Executor?
I think you need a service, this is (IMO) the fundamental abstraction in XFire.
This can be highly dynamic, so there are no limits here.
Btw we need to create both directions (SOAP/HTTP->CORBA,
CORBA->SOAP/HTTP). Any pointers for the reverse direction?
Thanks
2007/7/4, Tomek Sztelak <[EMAIL PROTECTED]>:
Just to make sure i understand correctly :) Do you want to call corba
service based on received soap message ? If so, you can just create
your own executor, which will redirect call to corba service instead
of runing method from service implementation
On 7/4/07, Lukas Zapletal <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I need to create SOAP - CORBA dynamic bridge. That means incoming SOAP
> requests should be transparently converted to CORBA calls.
>
> I think the best solution could be to write a handler that will
> process all requests. This handler should be added to default
> transport. I tried this:
>
> for (Object trans:
xfire.getTransportManager().getTransports()) {
> System.out.println("Adding handler for " +
trans);
> ((AbstractTransport)trans).addInHandler(new
> TestHandler());
> ((AbstractTransport)trans).addOutHandler(new
> TestHandler());
> }
>
> The handlers seem to be added but its not invoked. When I add them to
> service it works. What is wrong here?
>
--
Dr. Bernd Schuller
mail [EMAIL PROTECTED]
phone +49 2461 61 8736
fax +49 2461 61 6656
blog http://www.jroller.com/page/gridhaus
Central Institute for Applied Mathematics
Forschungszentrum Jülich GmbH
52425 Jülich
Sitz der Gesellschaft: Jülich
Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498
Vorsitzende des Aufsichtsrats: MinDirig'in Bärbel Brumme-Bothe
Vorstand: Prof. Dr. Achim Bachem (Vorsitzender), Dr. Ulrich Krafft (stellv.
Vorsitzender)
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
