Hi again!
Now I look at all these parts on a communication level. There might be a feature in JAXB
to do all this state synchronization without your/my knowledge. I don't know. But the
concept of web services does not support this kind of void feature where you change a
value in your method "argument" - because there is no method or argument just an
operation that accepts a message.
This is something you already know, but we take it from the beginning if there are other
persons whoe are unsure about the concept of web services.
Web services, in this case SOAP, provide a stateless way to communicate with other
components. You never know if these components are written in Java, .NET, Perl, C++ or
whatever else. This is the whole point by using web services - You send a request message
to a component and you get a response message in return.
Web services also use http as communication protocol. Http is a so called dead protocol,
i.e. one request and then one response before the communication dies (we have something
call keep alive to speed up things but that is just a way to keep the socket connection
open).
To summarize, we have two stateless parts communicating with each other - or more correct
one part (the client) asking the server for something by providing a message. The response
is another message. The two parts don't know anything about each other more than what
is exposed by the service contract (the WSDL file).
The question is, how can we provide the client with a new state on the server. Can it be
exposed to the client in another way than by using a return statement? I don't think
so.
Maybe JAXB can solve a void method by automatically map the contents of your request
Java-object instance to the same instance as the response Java-object.
Cheers
/Oskar
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132389#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...