ClassNotFoundException when translating Hibernate exception in ClpSerializer

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.1.X EE, 6.2.X EE, 7.0.0 M3
• Fix Version/s: 6.1.X EE, 6.2.X EE, 7.0.0 M1
• Component/s: Dev Tools, Dev Tools > Service Builder
• Labels: None
• Branch Version/s:
  6.2.x, 6.1.x
• Backported to Branch:
  Committed
• Similar Issues: Show 5 results ; ;

  LPS-45250	Service Builder does not properly translate classes from one portlet to another
  LPS-19817	Hibernate Exception in Document Library
  LPS-15073	ShoppingItemLocalServiceUtil.dynamicQuery - ClassNotFoundException - ShoppingItemImpl
  LPS-52677	ClassNotFoundException occurred when start the portal
  LPS-11	JDBC & Hibernate Exception

Steps to reproduce:

1. Update sample-service-builder-portlet to match Liferay version being tested. In master, this means replacing the call to GroupServiceUtil.getUserPlacesGroups() to getUserSitesGroups() and removing the version requirement in liferay-plugin-package.properties
2. Create a new portlet sample-service-user-portlet which has sample-service-builder-portlet as a required deployment context and calls FooLocalServiceUtil.addFoo() with a foo where field1 is larger than 75 characters.
3. Deploy sample-service-user-portlet and sample-service-builder-portlet

Expectation is that you get a SystemException due to the column constraint restriction, and the stack trace indicates that it is caused by the data being too long. Actual behavior is that you get a RuntimeException caused by a ClassNotFoundException with no additional information.

[Minhchau Dang]

Attaching view.jsp for sample-service-user-portlet which uses FooLocalServiceUtil.addUser() with field1 larger than 75 characters.