I'm learning liferay6.2, and I'm now reading chapter "USING SERVICE BUILDER TO GENERATE A PERSISTENCE FRAMEWORK" which url is
https://dev.liferay.com/develop/tutorials/-/knowledge_base/6-2/using-service-builder-to-generate-a-persistence-fr
I have no problem about "CREATING A SERVICE.XML FILE", "Understanding Liferay Portal Concepts". However, when I read "GENERATING MODEL, SERVICE, AND PERSISTENCE LAYERS" and press the "Build Services button", then liferay generate a lot of error files for me.
After press "Build Services button"
I search this problem on google, and I find some person have discussed it one year ago.
https://web.liferay.com/zh/community/forums/-/message_boards/message/52930858
In that page, one person said this problem can only be solved by jdk1.7 32bit. I don't understand why I have to use out-time technology in order to solve this problem.
Can anyone use jdk1.8 64bit to solve this problem?
You will have to use jdk 1.7 and link it to your project in order to generate your service. Change your environment variable and right click on the project in eclipse and use jdk from java
Documentacion version 6.2: https://web.liferay.com/documents/14/21598941/Liferay+Portal+6.2+EE+Compatibility+Matrix.pdf
Liferay 7 still has a long way to go....
Related
I'm new to liferay. And I've some basic question that what is liferay all about. What is a liferay plugin project or service builder project? Is liferay any framework,GUI tool, a content manager or WHAT?
I know that you guys are not engaged with this tool in this BLOG but still somehow it is related to java. So please guys help me.
Have you tried reading the liferay tag-wiki on stackoverflow? Just hover your mouse over it and you will have answers to all your questions. And if you want more just click on the pop-up and you would also find details about how to learn more about Liferay.
Still as per the norms of answering, here are some brief answers to your question:
Is liferay any framework,GUI tool, a content manager or WHAT?
Liferay is an open source JSR 286 compliant web-portal and social platform, written in Java. It includes content-management and more. It has different plugins known as portlets like Blogs, Forums, Document management, Content management etc.
What is a liferay plugin project or service builder project?
Plugin projects are nothing but small components/applications/widgets that run in the portal. Some might have UI and others might run in the backend.
Service Builder is a framework in liferay to ease development of services which might include service to access database, web-services, json web-services.
Everything else is given in the tag-wiki and the wiki also includes links to official resources if you wish to use/develop in liferay.
plugins are features which developers add them to portals like liferay.
for example:
liferay hooks are defined to do some tasks, like user's authentication, adding users, etc .. and we want change (override) that hooks, so we need develop ext plugins to do this for us.
At our company we are using Liferay for portals. My biggest issue with developing for such a huge framework is that the restart takes a lot of time even on a decent PC. We're trying to use hot deploying were it's possible but this sometimes just doesn't work (dependencies require restart, PermGen space errors occurs sometimes and Liferay have to be killed, etc.)
What i'm thinking about is that with most of our portlet's we are not really using any Liferay specific services just the JSR 168 provided things which is a standard. So i'm wondering if there's any minimal portlet environments available for Jetty or Tomcat which we can use for quicker portlet development? Of course i know that once i encounter a Liferay specific service call this is not an option.
I was testing Apache Pluto earlier which is a full blown but still lightweight portlet container however it works differently the way the portlet wars are assembled (web.xml should be modified) and it breaks compatibility in our build environment with Liferay. So it's not an option but i'm looking for something similar.
I've never used life ray portal, but too much played with GateIn portal because IBM Portal is heay, mostly for quick development on JSR-286 i used gatein
Currently used for visioneo.org, very flexible for every kind of use, large community.
Here is short summary
Liferay Currently used for visioneo.org, very flexible for every kind of use, large community.
eXo Platform Awesome look and set of web applications embedded. Last generation portal, very impressive! Based on Gatein
JBoss EPP Based on gatein, and designed to work with JBoss middleware architecture
Gatein A great portlet container. Light weight, easy to use. But unlike Liferay and eXo, it does not ship with collaborative portlets (Forum, Wiki etc.)
uPortal Beautiful portal, though its CSS are very intrusive: some BIRT styles are broken by uPortal's css.
Pluto Not really a portal, Apache Pluto can be used as a development / test platform. Often considered as a reference for portlet specifications.
Jahia Great look however not based on standards: portlets are supported but not really highlighted, a specific module technology is used instead
You might want to try the JRebel integration for Liferay. There's an introduction Webinar available, I don't know if it fully applies to the current implementation (the webinar is a bit aged) but it will give you an idea of the product/project.
What is your approach for creating your own set of controls aka own Extensions Library? After a few years of Xpages development we have a huge set of controls that are general purpose for building UI, some web services etc. (Probably as most other developers.) When we start a new project now we have to copy the entire stuff from one database to new one which involves controls, jars, css, images, JAVA code ... and then you completely loose control to maintain some central version of this controls & codes, everything is scattered among several projects/databases and things get messy fast.
We have thought about creating our own extension library as described here
http://www-10.lotus.com/ldd/ddwiki.nsf/dx/Master_Table_of_Contents_for_XPages_Extensibility_APIs_Developer_Guide but there is not enough documentation for this topic and the entire development process is quite complicated (at least seems to me. I tried two times based on docs above going through eclipse plugin project -> feature project -> update site and still having some bugs around)
What is your experience and approach for creating and maintaining shared Xpages controls in your Domino environment? Is there some hidden feature we miss here that can help us?
Take a look at the XSP Starter Kit on OpenNTF and the XPages SDK to setup an eclipse environment for plugin development. You'll also want Eclipse IDE for RCP and RAP Developers. Install the starter kit and SDK into eclipse and you should be all set.
The starter kit is a sample plugin with all kinds of examples of phase listeners, components, etc. Once you want to deploy your plugin, create an update site from within eclipse and use the Update Site NSF available on your server install to place your update site. Once that's done, you can replicate that NSF to any other servers that may need the plugin.
For more information about the starter kit, take a look at this slide deck. There is also a github project for the starter kit. Documentation for the XPages SDK can be found here. And a video for setting up the SDK is available on youtube. Lastly, here's the documentation for setting up the update site NSF.
While we haven't gotten to that yet in XPages, our model for regular Notes design elements is to have a central template that contains the elements that are shared, with those specific design elements marked to inherit from that template. Sometimes, a database inherits design elements from two different central templates.
That way, those centrally controlled design elements remain the same in all databases.
I would recommend looking at some example's on github for how they have library/components setup. One of the more simpler examples that has just a single component built into a Library is Steve Pridemore's App Layout Extension...https://github.com/DominoDev, Another good one is Nathan Freeman's Starterkit: https://github.com/the-ntf/xspstarterkit. Hopefully these will help you get the file structure down on which files you need and how they work.
I have a question for any JBoss Seam developers out there:
I am creating a web project using JBoss Seam by generating entities and reverse-engineering code from existing database tables. This is my first time developing a web app in JBoss/Java/JSF, being an old school .NET web developer from years ago.
How do I save user input in text controls, so that it stays on the web page after a page refresh? I used to use Viewstate or Sessionstate in .NET, not sure what the equivalent of this would be in Java/JSF. Someone mentioned using java beans, but not sure how to do that, and Googling produces little help.
Any comments much appreciated, thanks.
Rather than going through the steps required here, it might be easier for you to go through the Seam tutorial, which will give you the basics. You can then clarify things here afterwards:
http://docs.jboss.org/seam/latest/reference/en-US/html/tutorial.html#registration-example
Does anyone know if there are any WiX standard UI dialouges out there that you can use to integrate into your own WiX msi package?
For example:
Editing Connection Strings to database
Editing paths to log files in web.config/app.config
Setting up users for a Windows Service
Setting up WCF Endpoint addresses and other parameters
This would be very helpful!
I've haven't seen any UI dialog package either.
WixEdit has a dialog editor which I've heard is pretty useful, but I haven't used.
War Setup is a pretty good utility. It's been about a year since I've used it, so I don't remember if it has a dialog editor or not.
Edit: I couldn't think of the one I really loved, but I just found it: WixAware. It has probably the best dialog editor. The only thing is that it's trialware and the full version is $800.
Not today no. They aren't that hard to write though.