Hi,
I struggle with the ServiceBuilder with the Liferay SDK 6.1.1.
After a few weeks working with the ServiceBuilder I wonder what is the strategy? ServiceBuilder is using Hibernate underneath, but why is it then building it's own implementations and creating it's own models, utils and persistency layer? Why does Liferay invent the wheel again?
The documentation of the ServiceBuilder is very little, almost inexistent. There are a few docs and tutorials, but none of them is for any better use that a simple select statement. On the web I found many questions to the ServiceBuilder relationship mapping, but without any solution.
I try to implement a simple one-to-many relationship to the SAME entity. There is no example or documentation about how to do this. I mean this is pretty standard of every ORM framework and I think this is not a very exotic requirement, or is it? If ServiceBuilder depends on Hibernate or JPA why isn't it using that feature, why does LIferay it's own implementation?
I tried to make a simple example, but it can't build the service without error and the expected Foo.getChildren() method is missing.
Thanks,
Michael
<!--?xml version="1.0" encoding="UTF-8"?-->
<service-builder package-path="com.liferay.test">
<author>author</author>
<namespace>test</namespace>
<entity name="Foo" local-service="true" remote-service="true">
<!-- PK fields -->
<column name="fooId" type="long" primary="true" />
<!-- Audit fields -->
<!-- Other fields -->
<column name="children" type="Collection" entity="Foo" mapping-key="parentId"></column>
<column name="parentId" type="long"></column>
<!-- Finder methods -->
</entity>
</service-builder>
