Your service will have a hard time if it maintains state.
The very fact that you describe it in terms of an Oracle database and transactions indicates trouble. Start with the "service" that the component will provide and think in terms of the interface - the messages in and out. If you get those right you won't have any problem.
You're going to have to make a SOAP versus REST decision.
If you decide to go in the SOAP direction, I think the best way to develop web services is to use Spring's "contract first" web service approach. You'll start with an XSD for the messages and work from there. You aren't tied to an app server that way. It's especially good if you happen to be using Spring already. It can help with connecting to the database and declarative transactions as well.
manpreet![Tuteehub forum best answer]()
Best Answer
2 years ago
Could someone please recommend a suitable FOSS Java technology for developing a webservice with these requirements:
Needs to query an Oracle database, return XML data, and support rollbacks (so probably would have to maintain state in some way).
Currently I have a webservice written in PHP, but I've found PHP's support for SOAP limiting. I've looked at the various Sun Microsystems pages about their webservice offerings but find it baffling to choose between them. If someone could recommend a suitable direction it would be very useful.