The .war file is not deployed

Post Reply
hernandiego
Posts: 4
Joined: 09 Aug 2018, 02:07

20 Aug 2020, 23:07

Hi. I recently bought this template, the version I have is paradise-2.0.1

I unzipped the .zip to upload it to the glassfish server, but generated an error.
I tried to upload it to the widfly server but it also generates an error.

The error that widfly gives me is:

{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"paradise-2.0.1.war\".undertow-deployment" => "java.lang.RuntimeException: org.apache.webbeans.exception.WebBeansDeploymentException: java.lang.NullPointerException
Caused by: java.lang.RuntimeException: org.apache.webbeans.exception.WebBeansDeploymentException: java.lang.NullPointerException
Caused by: org.apache.webbeans.exception.WebBeansDeploymentException: java.lang.NullPointerException
Caused by: java.lang.NullPointerException"}}

please help me as soon as possible

mert.sincan
Posts: 4473
Joined: 29 Jun 2013, 12:38

24 Aug 2020, 17:49

Hi,

Could you please try to run 'tag' folder with;

Code: Select all

sass --update src/main/webapp/resources/ --sourcemap=none
mvn jetty:run
Best Regards,

camo_g
Posts: 2
Joined: 13 Apr 2020, 22:33

04 Sep 2020, 04:18

Hi Just a comment the following option is not valid when I try to run sass

Code: Select all

--sourcemap=none
instead I used:

Code: Select all

--no-source-map

camo_g
Posts: 2
Joined: 13 Apr 2020, 22:33

04 Sep 2020, 05:56

I had the same error when trying to deploy the babylon theme to Wildfly and I believe the reason is due to java dependencies and deploying to a JavaEE application server.

When you run the above mentioned sass and mvn:jetty:run commands, it is just deploying to a normal web server (jetty).
A normal web server like this does not already have it's own implementation of these java EE apis like CDI.
So the theme project's maven pom lists dependencies to include some specific implementations into the WEB-INF/lib directory so that these will be available on the class path.

When you deploy to a JavaEE application server, it will already provide implementations of the JavaEE APIs and these do not need to be included in the WEB-INF/lib directory, as they are already provided by the application server.

In the case of Wildfly it provides Weld as the implementation of CDI, instead of apache webbeans which is the implementation that is currently in the lib directory

The war file that comes with the downloaded theme already includes some of these dependencies in the WEB-INF/lib directory.
In my case, I removed all the jars from this lib directory. additionally, I was building this using the pom.xml and I replaced the following dependencies:

Code: Select all

<dependency>
            <groupId>org.glassfish</groupId>
            <artifactId>jakarta.faces</artifactId>
            <version>${mojarra.version}</version>
        </dependency>
        <dependency>
            <groupId>javax.el</groupId>
            <artifactId>javax.el-api</artifactId>
            <version>3.0.0</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>javax.servlet</groupId>
            <artifactId>javax.servlet-api</artifactId>
            <version>3.1.0</version>
            <scope>provided</scope>
        </dependency>

        <!-- JEE dependencies -->
        <dependency>
            <groupId>org.hibernate</groupId>
            <artifactId>hibernate-validator</artifactId>
            <version>${hibernate-validator.version}</version>
        </dependency>

        <!-- CDI required APIs -->
        <dependency>
            <groupId>org.apache.geronimo.specs</groupId>
            <artifactId>geronimo-atinject_1.0_spec</artifactId>
            <version>1.0</version>
        </dependency>
        <dependency>
            <groupId>org.apache.geronimo.specs</groupId>
            <artifactId>geronimo-jcdi_2.0_spec</artifactId>
            <version>1.1</version>
        </dependency>
        <dependency>
            <groupId>org.apache.geronimo.specs</groupId>
            <artifactId>geronimo-interceptor_1.2_spec</artifactId>
            <version>1.0</version>
        </dependency>
        <dependency>
            <groupId>org.apache.geronimo.specs</groupId>
            <artifactId>geronimo-annotation_1.3_spec</artifactId>
            <version>1.0</version>
        </dependency>

        <!-- CDI Impl -->
        <dependency>
            <groupId>org.apache.openwebbeans</groupId>
            <artifactId>openwebbeans-impl</artifactId>
            <version>${owb.version}</version>
        </dependency>
        <dependency>
            <groupId>org.apache.openwebbeans</groupId>
            <artifactId>openwebbeans-web</artifactId>
            <version>${owb.version}</version>
        </dependency>
        <dependency>
            <groupId>org.apache.openwebbeans</groupId>
            <artifactId>openwebbeans-jsf</artifactId>
            <version>${owb.version}</version>
        </dependency>
with just this:

Code: Select all

        <dependency>
            <groupId>javax</groupId>
            <artifactId>javaee-api</artifactId>
            <version>8.0</version>
            <scope>provided</scope>
        </dependency>
Basically - don't deploy the jars that are in the lib directory. Remove them from the WEB-INF / Lib and let the Application Server provide them for you.

Additionally I also needed to remove the following from WEB-INF/web.xml

Code: Select all

    <listener>
        <listener-class>org.apache.webbeans.servlet.WebBeansConfigurationListener</listener-class>
    </listener>
Please Note: it is possible some things I have removed may affect some parts of the demo application - I am not sure yet but at least I could get it running at this point! I will worry about anything else that I needs to be corrected when I come across that problem. But at least I could get it running

hernandiego
Posts: 4
Joined: 09 Aug 2018, 02:07

09 Sep 2020, 17:25

Yes, you're right, with mvn jetty: run it is executed because it is like tomcat that needs all the libraries included in the project, and both glassfish and widfly already have some features pre-installed.

mert.sincan
Posts: 4473
Joined: 29 Jun 2013, 12:38

29 Sep 2020, 17:04

Please try tag folder instead of .war. Please see my comment;
viewtopic.php?p=185053#p185053

Best Regards,

jcortorreal
Posts: 1
Joined: 10 May 2018, 00:33

20 Oct 2020, 08:56

file pom.xml

<dependencies>
<dependency>
<groupId>org.primefaces</groupId>
<artifactId>primefaces</artifactId>
<version>8.0</version>
</dependency>
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-api</artifactId>
<version>8.0</version>
<scope>provided</scope>
</dependency>
</dependencies>


<build>
<plugins>
<!-- remove ->
<plugin>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-maven-plugin</artifactId>
<version>9.4.27.v20200227</version>
<configuration>
<webAppConfig>
<contextPath>/apollo</contextPath>
</webAppConfig>
<scanIntervalSeconds>5</scanIntervalSeconds>
<webXml>${project.build.directory}/web.xml</webXml>
</configuration>
</plugin>
- ---------------------------------------------------------------------------

file web.xml
remove
<listener>
<listener-class>org.apache.webbeans.servlet.WebBeansConfigurationListener</listener-class>
</listener>

---------------------------------------------------------------------
end. ;)
Thank you!

mert.sincan
Posts: 4473
Joined: 29 Jun 2013, 12:38

20 Oct 2020, 10:11

Thanks @jcortorreal ;)

Post Reply

Return to “Paradise - PrimeFaces”

  • Information
  • Who is online

    Users browsing this forum: No registered users and 1 guest