Liferay Source code Development Cycle

[sheela mk, geändert vor 10 Jahren.]

Hai..Liferay Expert,,
I just wana know about Development Life cycle of Liferay Portal Application.

I have couple of questions regarding..carrying Projects using Liferay Technology.

Before to Liferay,,In plain java n Jee,,

We used to Initiate the project with writing with the DB Script defining all the Relationship between Tables of the project Once we get PROTOTYPE
From the Client..And Then Java Coding starts off...based on Layering.

In a project ,,We ends up with almost 40 -50 tables..

But in Liferay ,,I have seen MAX 3Entity using SB in service.xml ..in a single file.
Pls Let me know..Based on What Segregation of Tables are Done when we have So many Tables in a Project.

Pls Let me Know clearly about Development Life cycle of Liferay Project.

Thanks and Regards,,
Sheela MK

[sureshnaik ramavath, geändert vor 10 Jahren.]

Hi sheela,


All the tables are in .sql script. when ever that .sql script is executed tables will create back end.
The .sql script file is available in the below path.you can find out all the information.

Extract portal-impl.jar and select com folder-->liferay-->portal-->tools-->sql--->dependencies--->portal-tables.sql.


Thanks,
Suresh.

[sheela mk, geändert vor 10 Jahren.]

hai..suresh..thanks for the reply..

[Tonu Sri, geändert vor 10 Jahren.]

Hi Sheela,

I still did not get your question. Please ask your question in proper category.

If you are asking about how many entities, you can define inside your service.xml.

You can define entities as per your requirement. For example entities related to same project belong to same service.xml.

You can refer service.xml from Liferay source code.

Thanks:
Tonu

[David Ilechukwu, geändert vor 10 Jahren.]

Sheela -
Development cycle is a little but more verbose in Liferay - because the platform strives to be quite flexible.
That's why for instance you see several files generated for each entity (unlike in standard Java EE).

However, luckily this is not a problem - as most of the code is auto-generated by ServiceBuilder.

So your basic Development Lifecycle in Liferay would be;
(1) Represent your data model in service.xml using Entities
(2) Run ServiceBuilder to generate plumbing code
(3)Make changes to your *ServiceImpl files to reflect customization of your service layer logic
(4) Add the necessary methods to your Portlet class to catch the form submission actions from your jsp
(5) Finally implement your jsp

Also there are many layers of technology which make it easier @ each layer. (For example there is alloy ui for jsps).

Hope this is helpful.
Let me know if you need anything else.
Regards!