We plan to use PrimeFaces Community Edition, in an application, which we are developing for a client. We are planning to sell this software commercially. Are we allowed?
I have read the following in the PrimeFaces user guide 5.2
"7. Can I use PrimeFaces in a commercial software?
Yes, Apache V2 License is a commercial friendly library. PrimeFaces does not bundle any third
party software that conflicts with Apache. Same goes for Elite Releases for ELITE and PRO users."
I am guessing that this allows us to use PrimeFaces in our application, but, I just want to be sure before we use this in our application. I would appreciate if someone can advise me on the same.
Regards
Sachin
The differents from versione are these
The answer of your question is written in your question:
Can I use PrimeFaces (Community) in a commercial software? Yes
Related
I have the project which is designed and developed on very legacy frameworks. The frameworks which we are currently using are:
jboss-seam-2.2.1.jar
jsf-api-1.2_04-p02.jar
jsf-facelets-1.1.14.jar
jsf-impl-1.2_04-p02.jar
richfaces-impl-3.2.1.GA.jar
These are quite old frameworks, may be around 12 years old or more.
Now, we are planning to upgrade these version to the latest stable version of the frameworks.
The question is, can we directly move from jsf1.2 to jsf 2.3 ? I don't see any documentation or reference for this migration.
Along with JSF upgrade what all are the components we may need to upgrade? Any Direction ?
Thanks in advance!!!
I would like to ask a question about wether or not I should do the migration to Liferay 6.2.
Me and my team are working since 4 month on a portal quite big developed with Liferay 6.1 (CE edition) and now, since the project publication date is still 4-5 month ahead (so I do have time), I was wondering if doing the migration to 6.2 now is a good choice.
I already tried the new version and I must say I am impressed about the new features and since now I haven't find any bugs.
Anyone had any experience on developing portlet/themes on Liferay 6.2? Is is worth it to do the migration now or shall I wait for the next ga2 release?
Any suggestion is very welcome.
Thanks
Depends mostly on the kind of work you've done on that portal. Even slight upgrades in Liferay, can have major differences in the source code. If this affects the work you've done, it will affect the upgrade too. For example, things will get difficult to update if :
You have developed custom portlets, as they will need recompilation for the new runtime
Developed Portlets that use ServiceBuilder might need more work than just a recompilation
Using Hooks (even simple jsp hooks) might need re-writing. ext hooks will almost certainly need to, and it can become a major pain
On, the other hand, if most of your work had to do with light theming and content management, it could become an relatively easy and painless upgrade.
In any case, make sure to keep a backup of your Liferay Database, because once you upgrade, there is no way to downgrade back to the initial version.
As you're using CE, my recommendation is to upgrade as soon as possible. Reason is that there are no more updates for 6.1, now that 6.2 is out. If you're going live in 5 months, you'd be on a version that's unsupported for half a year at the date of publication.
The alternative is to go to EE, which is supported for ~5 years from release, e.g. you'll have several years of support in front of you. However, as Liferay is paying my salary, note that I might be biased...
Of course, being unsupported "by Liferay" does not mean that you won't be able to fix any bugs or issues, but you'll have to do this on your own, and sooner or later you should upgrade anyway... If you're not yet live, I'm recommending to do it sooner.
Liferay 6.2 does not (yet) support as many marketplace apps as Liferay 6.1. Also Liferay 6.2 CE has bugs, and patches are available only to EE subscribers; this forced us to use Liferay 6.1 CE instead of 6.2 CE.
You will have issues if you are using the Vaadin framework under Liferay.
Liferay 6.2 CE does not support Vaadin out of the box ... it is delivered with Vaadin 6.8, but it is broken - your portlet code will break.
You would have to consider moving to Vaadin 7.1 at best ... and that is a non-trivial code migration as many items have been deprecated between 6.8 and 7.
I went that route and the learning curve was unexpectedly steep.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I have done some research on JavaFX over the last year, and even built some basic desktop apps with it.
It's described as being used to create RIAs (Rich Internet Application).
http://en.wikipedia.org/wiki/Javafx
But can it really be deployed by a web browser? I have only deployed it via an executable JAR file.
How easy is it to deploy via web browser? Does it work? Does anyone have experience with this?
http://docs.oracle.com/javafx/2/deployment/deployment_toolkit.htm
Update for the March 2018 Java Client Roadmap
I encourage readers interested in this question to review the following Oracle Whitepaper:
Java Client Roadmap Update
The above paper outlines the official Oracle position on related technologies (JavaFX/Swing/AWT/Applets/WebStart), the dates until which it intends to support those technologies and which of those technologies it intends to transition to open source development projects separate from the JDK and JRE.
Update for Java 9, Oct 2017
According to the Java 9 release notes:
Java Applet and WebStart functionality, including the Applet API, The Java plug-in, the Java Applet Viewer, JNLP and Java Web Start including the javaws tool are all deprecated in JDK 9 and will be removed in a future release.
So, for Java 9+, deployment of JavaFX in a browser using a Java plug-in will only be possible using deprecated technology. Oracle notes in another part of the Java 9 release notes:
Deprecates the Java Plug-in and associated applet technologies in Oracle's JDK 9 builds. While still available in JDK 9, these technologies will be considered for removal from the Oracle JDK and JRE in a future release. Applets and JavaFX applications embedded in a web page require the Java Plug-in to run. Consider rewriting these types of applications as Java Web Start or self-contained applications.
Note: Java Web Start isn't really an alternative as that is also deprecated (anyway, it's different from an application embedded and rendered within a browser page). Also note for those who wish to use Web Start, even though it has now been removed from Oracle JDK 11+, it is available as open source, info on this is at OpenWebStart.
As an alternative which offers similar functionality, consider something like jpro, which deploys JavaFX applications in a browser without a Java plugin (jpro is currently only in closed beta, so it is not a viable solution as of October 2017, but maybe someday in the future...).
For now, I would recommend that the best way to deploy JavaFX applications is as self-contained applications, running outside a browser.
Previous answer for Java 7 and 8
JavaFx - can it really be deployed in a browser?
Yes, JavaFX applications can be deployed so that they run inside a web browser hosted html web page.
The technology which allows this to occur is the Java Plugin. This plugin is currently a NPAPI based browser plugin solution. The Java Plugin is shipped with the Oracle Java 7 Runtime Standard Environment.
Not all browsers are supported, only those listed on the JavaFX Supported Configurations page.
How easy is it to deploy via web browser?
The easiest way to deploy a JavaFX project in a web browser is:
Create a new JavaFX project in NetBeans.
Develop a simple HelloWorld App.
Follow the instructions for Deploying your first JavaFX Application.
This is not difficult (in my opinion).
Alternatively, follow instructions on the detailed reference for Deploying JavaFX Applications (or use 3rd party tools). For many projects, using a tool other than the NetBeans IDE to perform packaging is a better approach. However, it is generally easier to let the NetBeans IDE handle deployment packaging tasks for you.
What follows is not related to answering the original question, but provides some opinions and information requested in comments on this answer.
Some Advice
There are pitfalls to deploying Java in a browser. I encourage you to do your own Google research on the subject.
In my mind, based upon the current JavaFX 2.x deployment model, for most application types that require a browser as the primary runtime container, using JavaFX is not an appropriate solution.
Examine the deployment and runtime requirements for your application. Based on your requirements, and knowledge of the JavaFX browser based execution model, decide if a browser based deployment using JavaFX technology is the correct mechanism for your application.
A couple of potential difficulties for browser embedded JavaFX applications
Some important browsers (e.g. Internet Explorer 10, iOS Safari and soon Desktop Chrome) don't permit execution of plugins using the NPAPI currently used by the Java browser plugin => some of your target users may be unable to use your application.
With a browser embedded application, you don't have complete control over the runtime on which your application executes (browser + Java runtime + plugin interface) => an application which was working when first installed may stop functioning as expected after an update to these runtime components.
Deployment Alternatives
If a browser based deployment model is not appropriate for your application, there are other ways to deploy JavaFX applications (e.g. WebStart, stand-alone jars and self-contained applications).
JavaFX - can it really be deployed in a browser?
No, not any more.
The answer used to be yes, as given in this answer, although even in 2013 when that was written the writing was on the wall. However, here in 2016 the answer is no, it cannot. Modern browsers essentially don't support NPAPI any longer (Firefox does for Java, but only until the end of the year), and NPAPI is required for the Java plugin.
As of 2016 you can use jpro without any browser plugin. And it even runs on mobiles.
Edit 1: The project is free for non-commercial or open source projects. A "hello world" can be found here
I found solution by chance here.
what was missing in my web project.
I must add this to web.xml file :
<mime-mapping>
<extension>jnlp</extension>
<mime-type>application/x-java-jnlp-file</mime-type>
</mime-mapping>
One of our customers have Lotus Notes version 5.0.9. They wanted to check if it's possible to create an android mobile application to connect to the backend for documents workflow.
Couldn't find much resources about this scenario for this version. I believe Domino is already available on that version - so is Xpages a viable solution for that scenario? Thanks.
XPages requires at least Domino 8.5.x (and preferably Domino 9.0 which is the latest IBM Domino release). So you need to upgrade the Domino server if you want to use XPages.
FYI: Notes 5 was released in 1999 (see the history of IBM Notes on wikipedia).
XPages are available since IBM Notes Version 8.5. The term "Domino" stands for the IBM Notes server. So if your customer has Notes version 5.0.9 they probably have Domino version 5.0.9 too (although one can mix Notes and Domino versions).
Therefore XPages are no option for your, apart from the fact you could install a second Domino sever with version 9.0 just to host the xpages.
If they are on R5 what are they using for a workflow engine? If they are using a database designed from Approval.ntf (I think R5 was the last time it was shipped with the product) then it is a very old and very difficult to maintain &/or modify. If so then they probably need to take a deep breath and upgrade and re-design. Can probably cobble something together to make it work but really question the wisdom of doing that.
Our company is developing e-portal solutions for the government in Vietnam. We are using Liferay Community Edition. We are considering switching to Enterprise Edition.
From a programmer's perspective, is there something LP EE can do that LP CE cannot (performance, security, functionality, etc.)? We would like to hear from the experiences of programmers who have worked with both LP CE and EE before.
Thank you so much.
Linh
In addition to what the others already mentioned, Liferay EE is supported for ~5 years after release, while you won't get upgrades for major CE versions once the next release is out - so you need to upgrade less often. Support includes patches for problems that you discover (on a service level) as well as cumulative fixpacks, typically more often than on CE.
For clustering - especially for bigger clusters - there are some additional clustering options in EE that optimize the cluster communication in order to scale better.
Liferay Sync can synchronize multiple document libraries on EE, compared to a single document library in CE
Liferay Developer Studio, the commercial extension of eclipse, works with more application servers - especially the "big iron" servers while the CE/Open Source version Liferay IDE works with the open source appservers/servletcontainers.
Plus, you're supporting further development of the product directly.
That being said, however you decide, please get involved in the Liferay community and help to make the product even better
That is no prommical question, but I can say that EE get early bugfixes and EE is altogether robustly that CE.
Also, Liferay Portal EE has access to EE only marketplace applications, such as:
Kaleo Workflow Designer
Kaleo Workflow Forms
Auditing portlet
Reporting portlet
There may be more EE only applications but that is all I can think of right now.