Introduction

In the previous version, the object path parser does not throw an error in case the object path could not be parsed. An error.log entry was written, but cannot be enriched with context information by callers of the object path (like templates and pipelines).

This could lead to problems in case the object path is defined dynamically and not valid.

Modification of com.intershop.beehive.core.internal.objectpath.ObjectPathMgr

For details see the code block below.

public ObjectPath parseObjectPath(String path) throws IllegalArgumentException;

Migration

For details see the code blocks below.

public ObjectPath parseObjectPath(String path)
{ 
     return objectPathMgr.parseObjectPath(String path);
}

public ObjectPath parseObjectPath(String path)
{
  try
  { 
     return objectPathMgr.parseObjectPath(String path);
  }
  catch(IllegalArgumentException e)
  {
    Logger.error(this, "Can't resolve object path '" + path + "' at context ...", e);
    return null;
  }
}