Legacy Knowledge Base
Published Jul. 2, 2025

Troubleshooting Service Builder Blob Compile Issues

Written By

Justin Choi

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Service builder with Blob and compound primary key throws compilation error.
  • The console errors might look like this:
    [javac] /Users/xxxx-yyyy/Projects/aaaa/dxp/plugins-sdk/portlets/bbbbb-services-portlet/docroot/WEB-INF/service/com/aaaa/portal/model/InvoicePDFBlobModel.java:42: error: cannot find symbol 
    [javac] public InvoicePK getInvoiceId() { 
    [javac] ^ 
    [javac] symbol: class InvoicePK 
    [javac] location: class InvoicePDFBlobModel
        

Environment

  • Liferay Blade
  • Liferay Developer Studio
  • Gradle 
  • Any other Liferay IDE environment

Resolution

  • The issue is that the dependencies are not current. For example, a sample project might have this snippet:
    buildscript {
    dependencies
    
    { classpath group: "com.liferay", name: "com.liferay.gradle.plugins", version: "3.13.26" }
    repositories {
    maven
    
    { url "https://repository-cdn.liferay.com/nexus/content/groups/public" }
    }
    }
    
  • The dependency version is 3.13.26. If this is changed manually to 3.13.50, then using this version also includes server builder changes.

Once the dependency version number has been updated, the compilation error should be resolved and the module is built successfully. If this still does not resolve the issue, verify all other dependencies in other projects have also been updated.

 

Did this article resolve your issue ?

Legacy Knowledge Base