From Eclipsepedia

Jump to: navigation, search



DBWS has a number of test suites, all written using JUnit4. This page outlines the various testsuites and the types of testing in each suite.

DBWS test projects

In the EclipseLink SVN repository, there are a number of Eclipse projects that contain DBWS tests:

Eclipselink SVN Tree
    |   about.html
    |   ...
    |   ...
    |   +---eclipselink.dbws.test
    |   |   ...
    |   +---etc
    |   |   dbsetup_nnn.sql
    |   |   dbteardown_nnn.sql
    |   ...
    |   ...
        |   ...
        |   ...
        |   ...

Database setup

The projects that end with .oracle are (obviously!) Oracle-specific; the others are designed to run on any database platform; however, the sql dbsetup/dbteardown DML in the etc directory is specific to MySQL 5. The method with the JUnit4 @BeforeClass annotation looks for database connectivity information in Java system properties:

-Ddb.driver=com.mysql.jdbc.Driver -Ddb.url=_some_db_url -Ddb.user=_some_db_user -Ddb.pwd=_some_db_password

Test Automation

The core DBWS tests and DBWSBuilder tests are run as part of the nightly EclipseLink build process (on the servers at the Eclipse Foundation)

It is possible to run the DBWS tests by manually invoking the appropriate ant targets:
1 In ...dbws/eclipselink.dbws.test

prompt >ant build
prompt >ant run-tests

The in the user's home directory will be used (since there is no file checked in to the SVN tree). The tests are specifically designed for MySQL, so the values should be something like:
jdbc.driver.jar=path/to/mysql-connector-java-x.y.zz-bin.jar (currently x.y.zz = 5.1.13)
db.url=jdbc:mysql://<host>:<port(default is 3306)>/<database>
# Logging option for debugging
logging.level=off #'info' for light logging, 'fine' for SQL stmts, 'finest' for everything

The tests automatically setup and teardown the database resources required (table definitions, insert statements, stored procedures, etc.)

2 In ...utils/eclipselink.utils.dbws

prompt >ant build
switch over to test directory
prompt >cd ../eclipselink.utils.dbws.test
prompt >ant run-tests

NB - The JUnit jar file should be on the classpath - Eclipse Helios GA uses 4.8.1, so a version compatible with that is preferable.

The results are generated to a reports directory - just open the junit-noframes.html file in a browser.

DBWS core tests

The eclipselink.dbws.test project contains test classes that test DBWS in its XRM mode - no Web service deployment artifacts, no container -
just a bridge between OXM and ORM projects:

Eclipselink SVN Tree
    |   about.html
    |   ...
    |   +---eclipselink.dbws.test
    |   |   |   .classpath
    |   |   |   .project
    |   |   |
    |   |   |   build.xml
    |   |   |
    |   |   +---etc
    |   |   |       dbsetup_keymappings.sql
    |   |   |       dbsetup_relationships.sql
    |   |   |       dbteardown_keymappings.sql
    |   |   |       dbteardown_relationships.sql
    |   |   |
    |   |   \---src
    |   |       \---dbws
    |   |           \---testing
    |   |               |
    |   |               |
    |   |               |
    |   |               +---keymappings
    |   |               |
    |   |               |
    |   |               \---relationships
    |   |             
    |   |             
    |   |             
    |   |             

The setup required to run these tests is contained in the appropriately named dbsetup_xxx.sql/dbteardown_xxx.sql scripts
where xxx = keymappings or relationships).

The test code is in the (related) xxxTestSuite class - let's look at KeyMappingsTestSuite:


public class KeyMappingsTestSuite {
    static final String KEYMAPPINGS_SCHEMA =
        "<?xml version='1.0' encoding='UTF-8'?>" +
        "<xsd:schema targetNamespace=\"urn:keymappings\" xmlns=\"urn:keymappings\" elementFormDefault=\"qualified\"\n" +
          "xmlns:xsd=\"\"\n" +
          ">\n" +
          "<xsd:complexType name=\"phone\">\n" +
    static final String KEYMAPPINGS_DBWS =
        "<?xml version='1.0' encoding='UTF-8'?>\n" +
        "<dbws\n" +
          "xmlns:xsd=\"\"\n" +
          "xmlns:xsi=\"\"\n" +
          "xmlns:ns1=\"urn:keymappings\"\n" +
          ">\n" +
          "<name>keymappings</name>\n" +
    static final String KEYMAPPINGS_OR_PROJECT =
        "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +
        "<object-persistence version=\"" + CONSTANT_PROJECT_BUILD_VERSION + "\"\n" +
          " xmlns:xsd=\"\" xmlns:xsi=\"\"\n" +
          " xmlns=\"\"\n" +
          " >\n" +
           "<name>keymappings</name>\n" +
           "<class-mapping-descriptors>\n" +
              "<class-mapping-descriptor xsi:type=\"relational-class-mapping-descriptor\">\n" +
    static final String KEYMAPPINGS_OX_PROJECT =
        "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +
        "<object-persistence version=\"" + CONSTANT_PROJECT_BUILD_VERSION + "\"\n" +
           "xmlns:xsd=\"\" xmlns:xsi=\"\"\n" +
           "xmlns=\"\"\n" +
           ">\n" +
           "<name>keymappings</name>\n" +
           "<class-mapping-descriptors>\n" +
              "<class-mapping-descriptor xsi:type=\"xml-class-mapping-descriptor\">\n" +
    // test fixtures
    public static XMLComparer comparer = new XMLComparer();
    public static XMLPlatform xmlPlatform = XMLPlatformFactory.getInstance().getXMLPlatform();
    public static XMLParser xmlParser = xmlPlatform.newXMLParser();
    public static XRServiceAdapter xrService = null;
    public static void setUp() {
        final String username = System.getProperty(DATABASE_USERNAME_KEY);
        if (username == null) {
            fail("error retrieving database username");
Overriding behaviour

One of the notable things about this test class is the use of static Strings that contain all of the required XRM meta-data:
schema, ORM and OXM projects and the DBWS service descriptor file. For this test, these have been pre-built by hand and assembled
to follow the rules and styles of DBWS runtime processing. In fact, to be more accurate, these tests pre-date the existence of the
DBWSBuilder utility (that knows the rules and styles of DBWS runtime processing and produces meta-data to match).

We can see the static JUnit4 test fixtures for this testsuite: OX helper objects that will be used for comparing XML documents and an
xrService of type XRServiceAdapter. The XRServiceAdapter is a sub-class of XRServiceModel, the model object for the DBWS service descriptor
(fields: name, session-name and a Map<String, Operation> of operations). The XRServiceAdapter object has additional fields: schemaNamespace,
orSession (built from the ORM project), oxSession (built from the OXM project), xmlContext (built from the OXM project), schema and a
Map<QName, XMLDescriptor> of descriptorsByQName.

The XR service is built by an XRServiceFactory thru the API public XRServiceAdapter buildService(XRServiceModel xrServiceModel):

XRServiceFactory factory = new XRServiceFactory() {
    public XRServiceAdapter buildService(XRServiceModel xrServiceModel) {
	parentClassLoader = this.getClass().getClassLoader();
	xrSchemaStream = new ByteArrayInputStream(KEYMAPPINGS_SCHEMA.getBytes());
	return super.buildService(xrServiceModel);
XMLContext context = new XMLContext(new DBWSModelProject());
XMLUnmarshaller unmarshaller = context.createUnmarshaller();
DBWSModel model = (DBWSModel)unmarshaller.unmarshal(new StringReader(KEYMAPPINGS_DBWS));
xrService = factory.buildService(model);

The buildService method is overridden in the anonymous inner-class XRServiceFactory(){} because normally a XRServiceFactory looks for the
XRM meta-data artifacts in archive files (.jar, .war) on the classpath. In this case, the 'files' exist in-memory and can be directly built without doing
any classloader resource lookups (NB - the buildSessions method is overridden for the same reason - the OXM and ORM projects exist in-memory).

Invoking a DBWS operation

In the method getAllEmployees we can see how a DBWS query operation is invoked - an Invocation object is built with the same name as a
DBWS query operation described in the DBWS service descriptor file. Parameters may be added (in this specific case - get all employees - none are required)
and the xrService is used to execute the Invocation

Invocation invocation = new Invocation("getAllEmployees");
Operation op = xrService.getOperation(invocation.getName());
Object result = op.invoke(xrService, invocation);

The operation in this case returns a collection; thus, the result object must be cast to a Vector and each object marshalled to an XML document.
When the OR and OX projects were read in, a custom classloader builds any non-existent project model classes on-the-fly.

BaseEntityClassLoader becl = new BaseEntityClassLoader(parentClassLoader);
XMLContext context = new XMLContext(
    new EclipseLinkObjectPersistenceRuntimeXMLProject(), becl);
XMLUnmarshaller unmarshaller = context.createUnmarshaller();
Project orProject = (Project)unmarshaller.unmarshal(
    new StringReader(KEYMAPPINGS_OR_PROJECT));

Thus, the objects in the result Vector are all sub-classes of o.e.p.internal.dynamicpersist.BaseEntity

for (BaseEntity employee : resultVector) {
    rootHelper.roots.add(employee.get(0)); // address
    Vector<BaseEntity> phones = (Vector<BaseEntity>)employee.get(4); // phones
    phones.size(); // trigger IndirectList
    for (BaseEntity phone : phones) {
Document doc = xmlPlatform.createDocument();
XMLMarshaller marshaller = xrService.getXMLContext().createMarshaller();
marshaller.marshal(rootHelper, doc);

In the OR-world, there is no problem with returning a graph of related or un-related classes in a single Vector. However, in the OX world, a document requires a
root element. Thus in the KEYMAPPINGS_OX_PROJECT there is a mapping for a helper class dbws.testing.RootHelper that uses the XMLAnyCollectionMapping
to allow either an Employee, or Address or Phone to be nested under the <employee-address-phone-system> element. Once the rootHelper is populated,
the xrService is used to marshall it to an XML document. Finally, the test fixtures xmlParser and comparer are used to indicate if the generated document
is the same as an expected control document:

Document controlDoc = xmlParser.parse(new StringReader(EMPLOYEE_COLLECTION_XML));
assertTrue("control document not same as XRService instance document",
    comparer.isNodeEqual(controlDoc, doc));
    public static final String EMPLOYEE_COLLECTION_XML =
        "<?xml version=\"1.0\" encoding=\"UTF-8\"?>" +
        "<employee-address-phone-system xmlns=\"urn:keymappings\" xmlns:xsd=\"\" xmlns:xsi=\"\">" +
            "<employee address-ref-id=\"1\" employee-id=\"1\">" +
                "<first-name>Mike</first-name>" +
                "<last-name>Norman</last-name>" +
                "<phones>" +
                    "<phone-ref phone-id=\"1\"/>" +
                    "<phone-ref phone-id=\"2\"/>" +
                "</phones>" +


Structured in a similar fashion to KeyMappingsTestSuite, RelationshipsTestSuite is different in that it does not use a custom classloader to build classes
on the fly - the mapped domain classes actually exist. In addition, RelationshipsTestSuite demonstrates something that DBWSBuilder does not support:
mapping classes with 1:1 and 1:M relationships.

DBWS Utility tests

In the SVN repository under the Util component's high-level directory, there is a project eclipselink.utils.dbws.test This project contains test classes
that test the DBWSBuilder utility. As with the eclipselink.dbws.test tests, no Web service is deployed, the tests operate in XRM mode.

Eclipselink SVN Tree
    |   about.html
    |   ...
        |   |   .classpath
        |   |   .project
        |   |
        |   |   build.xml
        |   |
        |   +---etc
        |   |       dbsetup_attachedbinary.sql
        |   |       dbsetup_crud.sql
        |   |       dbsetup_customsql.sql
        |   |       dbsetup_inlinebinary.sql
        |   |       dbsetup_simplesp.sql
        |   |       dbsetup_simpletable.sql
        |   |       dbteardown_attachedbinary.sql
        |   |       dbteardown_crud.sql
        |   |       dbteardown_customsql.sql
        |   |       dbteardown_inlinebinary.sql
        |   |       dbteardown_simplesp.sql
        |   |       dbteardown_simpletable.sql
        |   |
        |   \---src
        |       \---dbws
        |           \---testing
        |               |
        |               |
        |               +---attachedbinary
        |               |
        |               |
        |               +---crud
        |               |
        |               |
        |               +---customsql
        |               |
        |               |
        |               +---inlinebinary
        |               |
        |               |
        |               +---simplesp
        |               |
        |               |
        |               \---simpletable

The setup required to run these tests is contained in the appropriately named dbsetup_xxx.sql/dbteardown_xxx.sql scripts (where xxx = attachedbinary, crud, customsql, inlinebinary,
simplesp or simpletable). The test code is in the (related) xxxTestSuite class - let's look at AttachedBinaryTestSuite:


public class AttachedBinaryTestSuite extends DBWSTestSuite {
    public static void setUp() throws WSDLException {
            "<?xml version=\"1.0\" encoding=\"UTF-8\"?>" +
            "<dbws-builder xmlns:xsd=\"\">" +
              "<properties>" +
                "<property name=\"projectName\">attachedbinary</property>" +
                "<property name=\"targetNamespacePrefix\">ab</property>" +
                "<property name=\"logLevel\">off</property>" +
                "<property name=\"username\">";
                "</property><property name=\"password\">";
                "</property><property name=\"url\">";
                "</property><property name=\"driver\">";
                "</property><property name=\"platformClassname\">";
                "</property>" +
              "</properties>" +
              "<table " +
                "schemaPattern=\"%\" " +
                "tableNamePattern=\"attachedbinary\" " +
                ">" +
                "<procedure " +
                  "name=\"getBLOBById\" " +
                  "isCollection=\"false\" " +
                  "returnType=\"ab:attachedbinaryType\" " +
                  "procedurePattern=\"getBLOBById\" " +
                  "binaryAttachment=\"true\" " +
                "/>" +
              "</table>" +
    public static SOAPAttachmentHandler attachmentHandler = new SOAPAttachmentHandler();

The DBWS_BUILDER_XML_xxx variables are static Strings that when assembled together, create a DBWSBuilder builder XML file. In the common setup code in DBWSTestSuite.setUp(), the strings are concatenated with the database properties:

    public static void setUp() throws WSDLException {
        String username = System.getProperty(DATABASE_USERNAME_KEY, DEFAULT_DATABASE_USERNAME);
        String password = System.getProperty(DATABASE_PASSWORD_KEY, DEFAULT_DATABASE_PASSWORD);
        String url = System.getProperty(DATABASE_URL_KEY, DEFAULT_DATABASE_URL);
        String driver = System.getProperty(DATABASE_DRIVER_KEY, DEFAULT_DATABASE_DRIVER);
        String platform = System.getProperty(DATABASE_PLATFORM_KEY, DEFAULT_DATABASE_PLATFORM);
        String builderString = DBWS_BUILDER_XML_USERNAME + username + DBWS_BUILDER_XML_PASSWORD +
            password + DBWS_BUILDER_XML_URL + url + DBWS_BUILDER_XML_DRIVER + driver +

When the DBWSBuilder utility is invoked from the command-line, the builder XML file is parsed using a OXM project; fortunately, this can be re-used for an in-memory string:

        XMLContext context = new XMLContext(new DBWSBuilderModelProject());
        XMLUnmarshaller unmarshaller = context.createUnmarshaller();
        DBWSBuilderModel builderModel =
            (DBWSBuilderModel)unmarshaller.unmarshal(new StringReader(builderString));
        builder.quiet = true;
        builder.setPlatformClassname(platform); =;
        builder.getProperties().put(SESSIONS_FILENAME_KEY, NO_SESSIONS_FILENAME);
        builder.operations = builderModel.operations;
        XRPackager xrPackager = new XRPackager() {
            public void start() {// do nothing
        builder.setPackager(xrPackager);, __nullStream, DBWS_SERVICE_STREAM, DBWS_OR_STREAM,
            DBWS_OX_STREAM, __nullStream, __nullStream, __nullStream, __nullStream, __nullStream,

An 'empty' custom is constructed and then finally, the build API is called with in-memory streams to capture all the generated DBWS and Web service artifacts.

See this page for more details about using the DBWSPackager class as a programmable API]]

End-to-end DBWS Web service testing

The previous examples tested DBWS only in 'XR' mode. It is possible, however, to test a DBWS service using Javase 6's 'containerless' API.

Javase 6 ships with the JAX-WS 2.x APIx inside the JDK - versions prior to update 4 have JAX-WS 2.0 APIs, which may cause some issues with later API requirements: to fix this, copy jaxws-api.jar and jaxb-api.jar into the endorsed directory (typically $JAVA_HOME/lib/endorsed or $JDK_HOME/jre/lib/endorsed). Please see this link for more details.

DBWSBuilder javase packager

When invoked from the command-line, the DBWSBuilder offers out-of-the-box support for building and packaging DBWS Services for either the WebLogic server or for running 'containerless' using the API

prompt > dbwsbuilder.cmd -builderFile {path_to_builder.xml} -stageDir {path_to_stageDir} -packageAs {packager}
Available packagers:
  -packageAs:[default=archive] wls [warFilename]
  -packageAs:[default=archive] javase [jarFilename]

Archive layout

The content of the .jar file is arranged differently from how the wls packager builds a .war file:

wls packager
    \---web-inf (root of .war file)
    |   web.xml
    |   |
    |   +---META-INF
    |   |       eclipselink-dbws.xml
    |   |       eclipselink-dbws-or.xml
    |   |       eclipselink-dbws-ox.xml
    |   |       eclipselink-dbws-sessions.xml
    |   |
    |   \---_dbws
    |           DBWSProvider.class            -- auto-generated JAX-WS 2.0 Provider
javase packager
    \---meta-inf (root of .jar file)
    |   eclipselink-dbws.xml
    |   eclipselink-dbws-or.xml
    |   eclipselink-dbws-ox.xml
    |   eclipselink-dbws-sessions.xml
    |   eclipselink-dbws-schema.xsd
    |   eclipselink-dbws.wsdl

Generated Web service Provider

The code-generated _dbws.DBWSProvider class is annotated slightly differently for 'containerless' deployment:

package _dbws;
//javase imports
import java.lang.reflect.Method;
//java eXtension libraries
import javax.annotation.PostConstruct;
import javax.annotation.PreDestroy;
import javax.servlet.ServletContext;
import javax.xml.soap.SOAPMessage;
import static;
//EclipseLink imports
import org.eclipse.persistence.internal.dbws.ProviderHelper;
    /* wsdlLocation not present in @WebServiceProvider annotation for 'containerless' deployments */
    serviceName = "testService",
    portName = "testServicePort",
    targetNamespace = "urn:testService"
public class DBWSProvider extends ProviderHelper implements Provider<SOAPMessage> {
    public  DBWSProvider() {
    public void init() {
    public SOAPMessage invoke(SOAPMessage request) {
        return super.invoke(request);
    public void destroy() {


For a DBWS service based on a DBWSBuilder table query operation:

<?xml version="1.0" encoding="UTF-8"?>
<dbws-builder xmlns:xsd="">
    <property name="projectName">emp</property>

With the .jar on the classpath, an Endpoint can be created programmatically:

//javase imports
import static;
import static;
//domain imports
import _dbws.DBWSProvider;
public class ContainerlessTest {
    static final String ENDPOINT_ADDRESS = 
    public static void main(String[] args) {
        // build Endpoint
        Endpoint endpoint = Endpoint.create(new DBWSProvider());
        // retrieve info from Provider's annotations
        WebServiceProvider dbwsProvider = DBWSProvider.class.getAnnotation(WebServiceProvider.class);
        String serviceNamspace = dbwsProvider.targetNamespace();
        String serviceName = dbwsProvider.serviceName();
        String portName = dbwsProvider.portName();
        // build service
        QName serviceQName = new QName(serviceNamspace, serviceName);
        QName portQName = new QName(serviceNamspace, portName);
        Service testService = Service.create(serviceQName);
        testService.addPort(portQName, SOAP11HTTP_BINDING, ENDPOINT_ADDRESS);
        // build dispatch to send SOAP msg
        Dispatch<SOAPMessage> dispatch = testService.createDispatch(portQName, SOAPMessage.class,
        BindingProvider bp = (BindingProvider)dispatch;
        Map<String, Object> rc = bp.getRequestContext();
        MessageFactory factory = MessageFactory.newInstance();
        SOAPMessage request = factory.createMessage();
        SOAPPart part = request.getSOAPPart();
        DOMSource domSource = new DOMSource(db.parse(
            new InputSource(new StringReader(FIND_BY_PK_REQUEST))));
        SOAPMessage response = null;
        try {
            response = dispatch.invoke(request);
        catch (Exception e) {
        if (response != null) {
            Source src = response.getSOAPPart().getContent();
            TransformerFactory tf = TransformerFactory.newInstance();
            Transformer transformer = tf.newTransformer();
            DOMResult result = new DOMResult();
            transformer.transform(src, result);
            Document resultDoc = (Document)result.getNode();
        // tearDown service
    static final String FIND_BY_PK_REQUEST =
        "<env:Envelope xmlns:env=\"\">" +
          "<env:Body>" +
            "<ns1:findByPrimaryKey_empType xmlns:ns1=\"urn:testService\" xmlns=\"urn:test\">" +
               "<ns1:id>7369</ns1:id>" +
            "</ns1:findByPrimaryKey_empType>" +
          "</env:Body>" +
    static String documentToString(Document doc) {
        DOMSource domSource = new DOMSource(doc);
        StringWriter stringWriter = new StringWriter();
        StreamResult result = new StreamResult(stringWriter);
        try {
            Transformer transformer = TransformerFactory.newInstance().newTransformer();
            transformer.setOutputProperty("indent", "yes");
            transformer.transform(domSource, result);
            return stringWriter.toString();
        } catch (Exception e) {
            // e.printStackTrace();
            return "<empty/>";


<?xml version="1.0">
<SOAP-ENV:Envelope xmlns:SOAP-ENV="">
  <SOAP-ENV:Header />
    <srvc:findByPrimaryKey_empTypeResponse xmlns="urn:test" xmlns:srvc="urn:testService">

DBWS Server Tests

See 2.5.0 Server Tests