Liferay Service Builder 6.2 : one to many ??

[Stephane Franchamp, modifié il y a 9 années.]

Hi,

Any Ideas how to get liferay service builder one to many relationship with liferay 6.2 and not many to many ??

Thanks

[M J, modifié il y a 9 années.]

Implementation of one-to-many and many-to-many in Service Builder is useless. You should use CustomSQL to do any table joins.

[Jack Bakker, modifié il y a 9 années.]

M J:

Implementation of one-to-many and many-to-many in Service Builder is useless. You should use CustomSQL to do any table joins.

I disagree with M J here, one-to-many and many-to-many is straight forward to implement while using service builder and without needing Custom SQL

Stephane Franchamp:

Any Ideas how to get liferay service builder one to many relationship with liferay 6.2 and not many to many ??

Hi Stephane,

By example and generally described, the approach I take for one-to-many, given XXXEntity which has many YYYEntity.

(I apologize in advance for inaccuracies as I am quickly typing this...)

In your service.xml, create the entities similar to below (note how YYYEntity references xXXEntityId and has a finder)

<entity name="XXXEntity" ...>
    <column name="xXXEntityId" ... primary="true" type="long" />
...
</entity>

<entity name="YYYEntity" ...>
    <column name="yYYEntityId" ... primary="true" type="long" />
    <column name="xXXEntityId" type="long" />
...
    <finder name="XXXEntityId" return-type="Collection">
            <finder-column name="xXXEntityId" />
     </finder>
</entity>

Build the services, then in YYYEntityLocalServiceImpl put in a method like:

public List<yyyentity> findByXXXEntityId(long xXXEntityId)
        throws *Exception {
    List<yyyentity> result = null;
    try{
        result = yYYPersistence.findByXXXEntityId(xXXEntityId);
    }catch(*Exception here like perhaps NotFound exceptions){
        ...
    } 
    return result;
}
</yyyentity></yyyentity>

And put in XXXEntityImpl:

public List<yyyentity> getYYYEntitys() throws *Exception{
    return YYYEntityLocalServiceUtil.findByXXXEntityId(super.getXXXEntityId());
}
</yyyentity>

from then on you can just use xXXEntity.getYYYEntitys() which is ... one-to-many

[Olaf Kock, modifié il y a 9 années.]

Do like Jack says.

I'm typically more lazy and just point to xmlportletfactory - create the basic services/entities there, generate and make the code yours. Good source of documentation that you can debug/step through.

[Jack Bakker, modifié il y a 9 années.]

Olaf Kock:

I'm typically more lazy and just point to xmlportletfactory - create the basic services/entities there, generate and make the code yours. Good source of documentation that you can debug/step through.

I'm all for Lazy Velocity, will check xmlportletfactory

[Olaf Kock, modifié il y a 9 années.]

I totally forgot to link the Radio Liferay episode for the commute, where you can hear about it.

[Vishal Patel, modifié il y a 9 années.]

HI,

I already know about one to many implmentation and many to one implementation through service.xml and XXXLocalServiceImpl.java.nnd using them throughout my projects.


But Thanks to pointing out. Adding to parent's Impl class, that is what I was not aware of.

And put in XXXEntityImpl:


public List<YYYEntity> getYYYEntitys() throws *Exception{
return YYYEntityLocalServiceUtil.findByXXXEntityId(super.getXXXEntityId());
}


from then on you can just use xXXEntity.getYYYEntitys() which is ... one-to-many

Thanks Again.

[Jack Bakker, modifié il y a 9 années.]

Hi Vishal, glad something useful shared

a similar approach can also be used for many-to-many including with association tables (including with additional fields) - where the association table has its own XXXYYYEntity in service.xml

[Robin Nagpal, modifié il y a 9 années.]

This is one of the main problems of SB. Its not possible to do it.

I guess the most important thing to consider is whether you need to share your services within different protlet projects.If yes, then SB is your best bet. If you are 200% sure that one portlet project can suffice your needs, you can use other technologies like Spring JPA , or JPA which does provide more flexibility but requires indepth knowledge of these.