I'm trying to use your suggestions and I hade tryied to do the
following:
1) I have changed the client java file provided by the package,
adding some addressing headers (essentially the To attribute):
To to =new To("http://localhost:8080/owkjava/services/Versione"); //
it is voluntary a wrong address to see what happened
headers.setTo(to);
2) To see what happened on the server side I have subclassed the
server side handler provided by Axis:
public class MyHandler extends AxisServerSideAddressingHandler ...
In it I have rewrittend the invoke method where I print the To
attribute before calling the super.invoke method.
And really I see the To attribute, as it was setted .
But the routing does not happen, so probably I have now to write by
myself the forwarding mechanism toward the "To" destination (and the
mapping between logical and physical addresses). Is it so?
Thanks again
Leonardo.
Leonardo Campanale ha scritto:
Thanks for your answer.
Just a question: is this handler already able to route messages among a
client and a server (and viceversa) and to map addresses? Or I have to
subclass it?
Thanks again.
Leonardo Campanale.
Davanum Srinivas ha scritto:
look at the ServerSideAddressingHandler. acc to msft docs, ws-referral has been subsumed by
ws-addressing.
-- dims
--- Leonardo Campanale <[EMAIL PROTECTED]> wrote:
Hello,
I'm trying to realize a porting from .Net to a Java application server
(Tomcat).
The .Net application uses two web servers: a client part, communicating
with the end user and sending requests to a second web server that
provides web services.
Many requests are simply re-routed from the front end web server to the
back end via ws-addressing + ws-referral. This last one is used to map
logical addresses to physical ones (using a routing table).
And now I'm trying to translate this mechanism that is actually used
in .Net to forward WS requests among different applications in a web
enironment.
In particular the soap message sent to a web server contains an header
(ws-addressing); the server receives the message, intercepts the
header, reconverts the logical address into a physical one (via
ws-referral) and send it to a second web servver (that implements the
web service needed by the client). Obviously it creates the opposite
path during the message response.
So, coming to my problems, I've understood that, in order to achieve
this objective, I have to implement an handler (possibly extending the
addressing handlers provided by the axis ws-addressing implementation).
But I've not understood how to extend it and what the handlers provided
are capable to dd.
And which handler is the best choice for my need. E.g.
org.apache.axis.message.addressing.handler.AddressingHandler
or
org.apache.ws.addressing.handler.ServerSideAddressingHandler
I would appreciate very much a sample of this kind of handler usage;
but, any suggestion would be useful.
Consider that I'm trying to direct the customer toward a massive use of
Java solution but the customer is disappointed by the actual supported
functionalities, having discovered, for example that the ws-referral
mecanism is not actually supported in Java and so we have to code the
conversion among the "logical" and physical address inside the
ws-addressing mechanism.
Thanks in advance.
Leonardo Campanale
Davanum Srinivas - http://webservices.apache.org/~dims/
__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/
|
