ma.glasnost.orika.test.property
Class PropertyResolverTestCase

java.lang.Object
  ma.glasnost.orika.test.property.PropertyResolverTestCase

public class PropertyResolverTestCase
extends Object

Nested Class Summary

static interface	PropertyResolverTestCase.Address
static class	PropertyResolverTestCase.Element
static class	PropertyResolverTestCase.Line
static class	PropertyResolverTestCase.LineDTO
static class	PropertyResolverTestCase.PersonDto
static class	PropertyResolverTestCase.Point
static class	PropertyResolverTestCase.PostalAddress
static class	PropertyResolverTestCase.SpecialCase
static class	PropertyResolverTestCase.SpecialCaseDto

Constructor Summary

PropertyResolverTestCase()

Method Summary

void	testAdHocResolution_integration_declarativeProperties() Demonstrates that you can declare properties in-line using a custom property descriptor format; like so: "propertyName{getterName|setterName|type=the.type.Name}" setter and type name are optional although those arguments must be constants;
void	testAdHocResolution_integration_declarativePropertiesNestedTypes() Demonstrates that you can specify the types as parameterized if necessary, such as "List<String>" or "java.util.List<java.lang.String>"
void	testAdHocResolution_integration_declarativePropertiesNestedTypesSingleQuote() Demonstrates that you can specify the types as parameterized if necessary, such as "List<String>" or "java.util.List<java.lang.String>", and that single quotes can be used instead of double quotes for convenience.
void	testAdHocResolution_integration_programmaticPropertyBuilder() This test case verifies that properties can be added through a programmatic builder interface, explicitly defining the properties using the programming API.
void	testAdHocResolution_integration_reuseName() This test case verifies that an ad-hoc property definition can be reused so that it doesn't have to be repeated in subsequent lines
void	testAdHocResolution_integration() This test confirms that ad-hoc properties can be defined in-line within field mapping expressions
void	testAdHocResolution_withType()
void	testAdHocResolution()
void	testBooleanMapping()
void	testGetInvalidNestedProperty()
void	testNestedProperty()
void	testOverridePropertyDefinition()

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

PropertyResolverTestCase

public PropertyResolverTestCase()

Method Detail

testNestedProperty

public void testNestedProperty()

testGetInvalidNestedProperty

public void testGetInvalidNestedProperty()

testBooleanMapping

public void testBooleanMapping()

testOverridePropertyDefinition

public void testOverridePropertyDefinition()

testAdHocResolution

public void testAdHocResolution()

testAdHocResolution_withType

public void testAdHocResolution_withType()

testAdHocResolution_integration

public void testAdHocResolution_integration()

This test confirms that ad-hoc properties can be defined in-line within field mapping expressions

testAdHocResolution_integration_reuseName

public void testAdHocResolution_integration_reuseName()

This test case verifies that an ad-hoc property definition can be reused so that it doesn't have to be repeated in subsequent lines

testAdHocResolution_integration_programmaticPropertyBuilder

public void testAdHocResolution_integration_programmaticPropertyBuilder()

This test case verifies that properties can be added through a programmatic builder interface, explicitly defining the properties using the programming API.

testAdHocResolution_integration_declarativeProperties

public void testAdHocResolution_integration_declarativeProperties()

Demonstrates that you can declare properties in-line using a custom property descriptor format; like so: "propertyName{getterName|setterName|type=the.type.Name}" setter and type name are optional although those arguments must be constants;

testAdHocResolution_integration_declarativePropertiesNestedTypes

public void testAdHocResolution_integration_declarativePropertiesNestedTypes()

Demonstrates that you can specify the types as parameterized if necessary, such as "List<String>" or "java.util.List<java.lang.String>"

testAdHocResolution_integration_declarativePropertiesNestedTypesSingleQuote

public void testAdHocResolution_integration_declarativePropertiesNestedTypesSingleQuote()

Demonstrates that you can specify the types as parameterized if necessary, such as "List<String>" or "java.util.List<java.lang.String>", and that single quotes can be used instead of double quotes for convenience.