Details
-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.1.X EE, 6.2.X EE, 7.0.0 M3
-
Component/s: Core Infrastructure > Service Builder
-
Labels:None
-
Branch Version/s:6.2.x, 6.1.x
-
Backported to Branch:Committed
Description
Steps to reproduce:
- 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
- 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.
- 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.
Attachments
Issue Links
- relates
-
LPS-27040 Refactor to avoid reflection
- Closed