Translation of .NET Web Service to JAX-WS on Websphere 6.1

Heartsbane,

Two parts to your question –

1) Converting records from your DB2 database to Java and vice versa.
You can do this using straight JDBC if your queries are really simple and have a small number of objects to deal with.

If you have many objects and more complex relationships and queries (and a system that could potentially grown in time), you could consider using JPA to handle this conversion for you.

2) Sending/receiving Java objects “on the wire” to/from the web service
JAX-WS uses JAXB2 for data binding by default, you need to annotate your Java objects (could be the POJOs that MyEclipse generates for you during JPA reverse engineering process).

Please have a look at our JAX-WS tutorials and let us know if you require further assistance. More info on JAX-WS can be found here: https://jax-ws.dev.java.net/

However, there was nothing in that tuturial discussing how to use JAX-WS web services to call DB2 (or other database) SQL statements and return the results.

Unfortunately, there is no shortcut here that will bridge your database with the webservice directly. It will be Web service <> (using JAXB2) Java <> (using SQL directly or JPA) DB2.

What you could try to do is build a class like the calculator class which contains the methods you wish to expose, this class will in turn call into your JPA objects to return the data requested. e.g.

public class MyCustomerService {
  public String getCustomerName(int custId) {
    CustomerDAO dao = new CustomerDAO();
    Customer customer = dao.findById(custId);
    return customer.getName();
  }

 public Customer getCustomer(int custId) {
    CustomerDAO dao = new CustomerDAO();
    return dao.findById(custId);
  }
}

I would pass the MyCustomerService class to the bottom up wizard. Your Customer object should automatically be serialized to/from XML by wrapper classes generated by the bottom up process – see the .apt-generated folder in your project – you should see a class for each service request and response. Observe that these classes have JAXB2 annotations (e.g. @XmlRootElement). One of the fields in this wrapper class would be your Customer object (for the getCustomer method in MyCustomerService) – this will be serialized to XML using JAXB2 defaults.

You may be happy enough with the default mapping (I recommend giving this a shot first before going further), but if not – you will need to add JAXB2 annotations manually to the customer class to change the way in which it is mapped to / from XML. See the marshalling and unmarshalling sections at this location: https://jaxb.dev.java.net/guide/

Hope this helps.