Bulk update of incomplete 2.0.0-b2 issues to just a 2.0 fix version.

There is code included here but it doesn't seem to be there for JPA. Shelving pending response from Jonathan.

I contacted JPA team and linked the related issue they are working on.

This still appears to be not converted for JPA. It may be an easy fix though; can we have someone from that team look at it?

There should be a capability for refreshing now on the DataObjectWrapper

Even if the capability is there, it's not being used in the right place so we need someone from the JPA team to take a look at this piece of code.

I can't seem to get the example I created (Labs -> Kitchen Sink -> Lookups -> Bottom of the page) to work with the current objects, so it will have to probably be changed to different objects. The point for that one is that once you look up something in a lookup, anything in the references to refresh list should be linked in ViewHelperServiceImpl.refreshReference. So once the lookup returns, the linked object should be filled and any fields from that linked object should now display.

I did a more in-depth review of this one. I updated the example to work when this work is complete. Currently, there is a block of code in ViewHelperServiceImpl.refereshReference which prevents any JPA code from erroring out when using the LegacyDataAdapter:

if (!(parentObject instanceof PersistableBusinessObjectBaseAdapter)) {
    LOG.warn("Could not refresh reference " + referenceObjectName + " off class " + parentObject.getClass().getName() + ". Class not of type PersistableBusinessObject");
    return;
}

With JPA, the following should be added:

KRADServiceLocator.getDataObjectService().wrap(parentObject).fetchRelationship(referenceObjectName);

but both methods should be allowed, so the solution here is to detect whether or not we are in legacy mode or not and apply the correct refresh method.

Updated refreshReference per Kristina's comment. Tested the example in kitchen sink along with the demo look-ups.