Is it true that the entity name in service.xml must match the existing database table name to map a Service Builder entity?

The assertion is false because the entity name specified in service.xml does not need to match the existing database table name for Service Builder to correctly map an entity. When using Service Builder in Liferay, you define your entity in the service.xml file, which establishes the relationship between the entity and the corresponding database table. This means that the entity name can differ from the table name—Service Builder is capable of handling this mapping through configuration options.

For example, you can define a custom table name using the table attribute within the entity declaration in service.xml. This allows developers the flexibility to use naming conventions or database schemas that do not strictly align with the entity names. Essentially, Service Builder utilizes the definitions provided in service.xml to create the necessary database interactions and mappings, making it possible to integrate with existing databases seamlessly regardless of naming differences.

This ability not only supports legacy database integration but also allows you to maintain a clean and logical structure in your Liferay applications while accommodating various database designs.