Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseLink/Development/Testing/DBWS
Summary
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 core tests
In the SVN repository under the DBWS component's high-level directory, there is a project eclipselink.dbws.test
This 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:
\---trunk
| about.html
| ...
|
+---dbws
| +---eclipselink.dbws.test
| | | .classpath
| | | .project
| | | build.properties
| | | build.xml
| | |
| | +---etc
| | | dbsetup_keymappings.sql
| | | dbsetup_relationships.sql
| | | dbteardown_keymappings.sql
| | | dbteardown_relationships.sql
| | |
| | \---src
| | \---dbws
| | \---testing
| | | DBWSTestHelper.java
| | | RootHelper.java
| | |
| | +---keymappings
| | | KeyMappingsTestSuite.java
| | |
| | \---relationships
| | RelationshipsAddress.java
| | RelationshipsEmployee.java
| | RelationshipsPhone.java
| | RelationshipsTestSuite.java
The setup required to run these tests is running the appropriately named dbsetup_xxx.sql
script
(and conversely dbteardown_xxx.sql
-
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=\"http://www.w3.org/2001/XMLSchema\"\n" + ">\n" + "<xsd:complexType name=\"phone\">\n" + ... static final String KEYMAPPINGS_DBWS = "<?xml version='1.0' encoding='UTF-8'?>\n" + "<dbws\n" + "xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"\n" + "xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\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=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" + " xmlns=\"http://www.eclipse.org/eclipselink/xsds/persistence\"\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=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" + "xmlns=\"http://www.eclipse.org/eclipselink/xsds/persistence\"\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; @BeforeClass public static void setUp() { final String username = System.getProperty(DATABASE_USERNAME_KEY); if (username == null) { fail("error retrieving database username"); }
The setUp
method looks for the database parameter pass-in as Java system properties:
db.url=_some_db_url
db.user=_some_db_user
db.pwd=_some_db_password
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() { @Override 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 factory = new XRServiceFactory() {
because normally a XRServiceFactory
looks for the XRM meta-data artifacts in archive files (.jar, .war)
on the classpath.