Hi Kim,
Is Address an Entity. (or is it an interface or something else)
Other than that, nothing jumps out at me as a potential cause for
the issue.
Here are some things you can do to try to debug.
1. Run the static weaver and ensure the classes get weaved. You can
even use a decompiler to ensure the _persistence_setaddress_vh method
exists in the weaved classes.
http://wiki.eclipse.org/Using_EclipseLink_JPA_Extensions_%28ELUG%29#How_to_Configure_Static_Weaving_for_JPA_Entities
2. Set the logging level to FINEST with the persistence unit property
eclipselink.logging.level=FINEST
3. Ensure you see a logging message that indicates weaving is starting
and one that indicates weaving is ending for the two classes you are
having issues with and that there are no errors logged between them.
The messages will look like this:
"Begin weaver class transformer processing class [classname]"
"End weaver class transformer processing class [classname]"
4. EclipseLink has two debug flags that can be used for weaving. Set
them an examine the resulting classes. Compare them to the results of
static weaving. The following two flags should be set as system
properties (not persistence unit properties)
- eclipselink.weaving.output.path=<path>
- eclipselink.weaving.overwrite.existing=true
-Tom