PayaraMicro | Examples for use with Payara Micro | Microservice library

Which kind of EJB did you use? In my opinion it should work on @Singleton and @Stateless. I am not sure how the other EJBs are supported by Payara Micro.

However, since Payara Micro supports the Java EE Web Profile and you are using a web application anyway, I would suggest to use a @WebListener to get notified of lifecycle events.

It could be implemented as follows:

I finally got this working. First, the application I'm deploying is a WAR with packaged EJB modules, so the persistence.xml needs to be packaged in a jar within WAR/WEB-INF/lib. Here is the structure:

Generated Payara Micro application from https://start.microprofile.io can be started using bundled Payara Micro uber jar with the following instructions :

The generation of the executable jar file can be performed by issuing the following command

With help from earldouglas (many thanks for that), I got it running:

Project files:

Your stacktrace shows you are using Jersey, but you are trying to use RESTEasy multipart. Why? You should be using the Jersey multipart support if you are using Jersey. Check out the docs here Chapter 9.3.

For general usage, here is some info. The dependency you should add is

It looks like you had the webapp folder in the wrong place (it should be under main, not under main/resources) and you didn't have a web.xml which enables the faces servlet.

I created a PR for you which builds a working app. I also changed the packaging to war as I'm not so familiar with the uberjar packaging. HTH!

You need to remove the addClasspath configuration in your pom.xml file, in the WAR plugin. Then your command with --addLibs will work.

Your current configuration in the MANIFEST inside the WAR instructs to search for the JARs in the folder where the WAR is located. This doesn't work with Payara Micro, because the WAR file is first copied into a temporary folder before it's deployed. Since the JARs are not in that folder, they're not found.

You need to build a WAR file without classpath specified in MANIFEST and then just use the --addLibs argument to supply additional JARs.

So if you just remove the following from your pom.xml all should work:

true lib/ net.clementlevallois.qof.back.email.Controller

Easiest solution is to use Jackson. MOXy is based off JAXB rules, which can get very complicated in some situations (this includes working with inheritance). Jackson just works.

Just add the Jackson dependency (in a provided scope, as Payara already has the dependency) and register the JacksonFeature with the application.

There's no official way to do this in Payara Server although it's possible to do it.

There's GlassFish API which can be used from a deployed application to deploy other apps. See Deployer Javadoc. Nothing has changed in Payara Server so it should work also with Payara Server.

Another option is to use Cargo project deployer, which also supports Payara Server (using the GlassFish deployer). It also works outside of Payara Server, in any Java SE application, but is more complicated to set up.

Another option is to use the raw REST endpoint provided by the Admin Console, which is used by the asadmin tool and Cargo Deployer. You wouldn't need any external dependency but it's not very documented which resource to access. Here's the docs, here's the code of the DeployCommand which describes which parameters it accepts, and here's a path to the deploy endpoint: http://localhost:4848/management/domain/applications/deploy. If you paste the link to a browser, it will give an HTML frontend to test with. If you send a post request with accept type JSON, it will return a response in JSON format (success/failure)