I already have a glassfish version 3 on a server. How do i install liferay into this instance without using the liferay glassfish bundle.
Regards
You can download the Liferay WAR at this page. (More specifically, the WAR is here). Do not forget to download the Liferay dependencies, too. After downloading, unzip the dependencies and copy its contents to the lib directory of your domain in GlassFish ($GLASSFISH_HOME/domains/domain1/lib/). Do not copy it to the $GLASSFISH_HOME/domains/domain1/lib/ext/ directory. I did not get Liferay working in my GlassFish 3 because of this problem and I have too limited Internet access so I cannot download the Liferay GlassFish bundle for testing the suggested solution. Anyway, I think you can go ahead from this point :)
Related
I am new to Liferay and I deploy Liferay Audience Targeting -7.lpkg in deploy folder and restart my server still it's not showing in Liferay DXP
Then I check in GOGO Shell there Liferay Audience targeting module is showing but in Resolved state but when using diag on that module it's showing No resolution report for the bundle. Can't able to get where a problem is.GOGO Shell
I am not using GOGO Shell. However, I had similar issue with the Liferay DXP EE SP1 bundle. I had to restart my bundle for audience targeting to deploy properly the first time.
I also ran into an issue with not being able to add reports in campaigns. I found the following solution on the liferay forums that worked for me. You need the appropriate fixpack for Liferay DXP. If you have any issues with DXP with bundled HSQL, then you need to use MySQL or another database as HSQL is not supported
https://web.liferay.com/community/forums/-/message_boards/message/87413363
Hope this helps.
I am creating a simple JSF application with one of my university colleagues, and I am having some trouble when I pull down the application from our repository. When I import the project into NetBeans IDE 8.0.1, the program does not compile correctly on the following CDI based annotation:
#Named
#RequestScoped
public class LoginController implements Serializable {...
It is informing me that it cannot find the following package:
import javax.enterprise.context.*;
Initially I had thought that I did not have the EJB and EAR plugin installed, however I have installed the Java EE bundle which I downloaded from the netbeans website. Are there any other JAR's, which I may be possibly missing, causing this specific error.
On my colleagues local machine everything works as expected without any issues at all, so I am left unclear why this is not happening on my computer.
yeah it seem this netbeans version lacking javax.enterprise package. Here is the solution
1) If you are using maven project, add javax.enterprise(cdi-api.jar) as dependency
2) For other projects, download cdi-api.jar, add this as external jar from project properties, it will enable CDI.
Yes you need to include another library. You are using the part that belongs to Java EE. By default java includes Java SE. So you need to add this library in your project.
Go to
Project Properties -> Libraries -> Add Library -> Java EE Web 7 Api Library
I had this problem too. The glassfish library structure has changed somewhat so instead of using the "Java EE from Glassfish" library we used the "Java EE from API" library and that fixed it.
Both proposed solutions are valid but the simplest one is the second one because you've got already everything needed in NetBeans 8.0.
Your problem is clearly the consequence of the default Java EE bundle (version 7) present in GlassFish 4.1. Of course, it is a NetBeans bug. Netbeans should have added the needed library to your project when you chose to work with Java EE 6.
I am trying to figure out which jar I need to download for tomcat 7. I am making a call and passing an argument to a method such "availableEmployees(DepartmentName)" in my faces web page. This does not work in tomcat 7 but works in glassfish 3.1. I have added the javax.faces.2.1.20.jar "Mojarra" to my web app for jsf dependency. I have also javax.servlet.jsp.jstl.1.2.1 in my tomcat library folder.
Did anyone run into such problem ? Do I need to add more than the above jars for jsf support ? Thanks. Not using maven since it is somebody else' project.
I am using netbeans and I linked to an eclipse project. I added my own primefaces library. When I looked at the build output from netbeans, I have noticed that there were two copies of primefaces library. One with 3.4.2 and another with 3.3.1.
Removed one of them and everything worked.
I have a portlet that worked fine on Liferay 6.1 portal but when I deploy it on Liferay 5.2.3
my configuration page did not even open.
How should I make it work ?
Here is a nice authoritative answer to a very similar question.
The portlets of newer versions are not designed to work on older installation of Liferay. Since they are compiled using the latest plugins-sdk and the also the different jars which have changed since the last version.
So if you want the newer version portlet to work with any older version then you have to compile the portlet with an older version of Liferay with that plugins-SDK. And I am sure there would be a lot of classes and jsp-tags in the Liferay 6.1 portlet which would not work in Liferay 5.2.3.
I have a (old) web app that is using Jrun and IIS. I would like to replace JRun with something free and OS. Can you recommend something that I can just install and copy the app jar files over and be up and running?
If you don't need a full J2EE (damn, that must be old software), Connecting IIS with Tomcat using isapi_redirect describes how to front Apache Tomcat with IIS (covers version 7).
If you are running EJBs, I would consider using the (appropriate) version of JBoss and follow the same procedure as above to front JBoss with IIS.
I use Jetty. Very easy to use. Not sure if you have EJBs - the version of Jetty I use is just Servlets and JSP.
I've also used Tomcat and JBoss. They work too.
WebsphereCE from IBM is also open source. It is a scaled down version of the paid version. Some people reported success using it with IIS but you might want to use either Tomcat or Jetty if all you have are servlets and JSPs.