Guide - 7.10 Migration ObjectPath Parsing
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.
parseObjectPath now throws an error
public ObjectPath parseObjectPath(String path) throws IllegalArgumentException;
Migration
For details see the code blocks below.
parseObjectPath now throws an error
public ObjectPath parseObjectPath(String path)
{
return objectPathMgr.parseObjectPath(String path);
}
parseObjectPath now throws an error
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;
}
}
Disclaimer
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.