<build> ... <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.6.0</version> <configuration> <source>1.8</source> <target>1.8</target> </configuration> </plugin> </plugins> </build>
- Click on your project folder.
- Go to Window > Show View > Navigator
- Go to Navigator and expand the .settings folder
<?xml version="1.0" encoding="UTF-8"?> <faceted-project> <fixed facet="wst.jsdt.web"/> <installed facet="jst.web" version="2.3"/> <installed facet="wst.jsdt.web" version="1.0"/> <installed facet="java" version="1.8"/> </faceted-project>
- Change the version like this
<installed facet="jst.web" version="3.1"/>
- Just update your project. Right Click on The Project Folder > Maven > Update Project > Select the Project and click ‘Ok’
This has been a recurring question among customers when they are evaluating Liferay and we have been point by point explaining why Liferay DXP is such a better option compared to its community alternative. I recently wondered why this question keeps popping up in these meetings.
So I decided to do a quick search and found that there is no easy differentiation offered to end users. So here in this post I have outlined the definitive benefits on why you should prefer DXP over Liferay 7.
Simply said, OSGi is a dynamic module system for Java. It defines means to install, uninstall, update, start and stop modules. Those modules are called bundles, but are, in their simplest form, actually Java jar files with a special Manifest. Modules can be installed, uninstalled etc without stopping or restarting the Java VM.
An OSGi framework manages the described lifecycle of and dependencies between the bundles in a secure way. A bundle needs to state which Java packages it exports and which it imports. The import and export statements can be annotated with version information, so that you even can have more than one version of the same package in the same Java VM
There is no doubt that Spring Framework is one of the most popular Java frameworks and makes it really easy to create real-world, enterprise-grade Java applications by providing features like dependency injection and inversion of control.
But, to be honest, Spring is much more than just another DI and IOC framework. It goes one more level to simplify many of Java’s APIs e.g. JDBC, JMS, Java Mail, etc., by providing a useful layer of abstraction. It’s much easier to work with JDBC with Spring’s JdbcTempalte and other utility classes. They remove most of the friction a Java developer faces with respect to executing SQL statements and processing ResultSets to get the Java object they want.