payara

问题 I have this security configuration in Glassfish domain.xml which works for 4.0 but fail in 4.1.1 can someone help to identify what is wrong. The only difference is the class package "ee" GF 4.0 (with extra ee ) <auth-realm classname="com.sun.enterprise.security.ee.auth.realm.jdbc.JDBCRealm" name="authentication-realm"> <property name="jaas-context" value="jdbcRealm"></property> <property name="password-column" value="password"></property> <property name="datasource-jndi" value="jdbc/SomeDS"><

问题 I have a Maven project I want to deploy on a Payara server using Jenkins. There are two projects: a domain project and a Spring Web MVC project. The Spring project is configured to build after the domain project, as it is dependant on the domain project. Each time I commit my project, the build is triggered. However, I always get the following error: Failed to parse POMs. See full console ouput below. This is my first time using Payara and Jenkins, and I can't really wrap my head around what

问题 I have 2 applications. One 'main' and a second one with a Remote EJB. The first application calls the Remote EJB in the second one. Now I want to implement the Observable pattern. But it doesn't seem to work cross-application. So I want my Observable inside the second application, and my Observers in the first. When I try it, it doesn't seem to work. It only works if I make the Observable and Observers in the same application. I got another solution, but I think it's dirty. I could use a MDB

问题 I'm building a simple app and now i'm facing the "logging nightmare" on javaee application. I've done days of searches, hundreds of change/test but there's no way to make it run. My app is made of a simple EAR +-- /lib | +-- slf4j-api-1.7.25.jar | +-- logback-classic-1.2.3.jar | +-- logback-core-1.2.3.jar | +-- JAR (JPA/EJB/Producers/Interceptors) | +--src/main/resources | +-- logback.xml | +-- logback-test.xml | +-- WAR The libs are so loaded in the lib directory of the EAR file. my pom.xml

问题 I've abandoned GlassFish 4-point-anything in favor of Payara41. Amazingly GF has unresolved JDBC and JMS Resources configuration bugs. See: Glassfish Admin Console throws java.lang.IllegalStateException when creating JDBC Pool Payara perfectly fixed the JMS configuration issues. So all I need are the environment properties my standalone Java Client needs to get an InitialContext(env) to lookup() those Resources. Note: InitalContext() doesn't work in a standalone. Only in an EJB Container that

问题 I'm trying to implement somewhat of a "plugin feature" with the help of CDI injection. But i'm having some trouble and thought i might get some outside perspective from my fellow "Stackers" :-) I got so far that something like this works: @Inject @ScoringModule("AGE") private AgeModule ageModule; @Inject @ScoringModule("CUSTOMER_TYPE") private CustomerTypeModule customerTypeModule; When i "run" this then both fields get injected with the appropriate instances. But when i try to inject them a

问题 Mac OS X: Yosemite 10.10.5 Until recently I have been using: NetBeans8.1beta Glassfish4.1 Mojarra 2.2.7 I have recently investigated using: NetBeans8.1 Glassfish4.1.1 Mojarra 2.2.12. With a very large JSF web app (with ObjectDB as JPA persistence provider) I am experiencing massively longer deployment times to Glassfish4.1.1 (over 10 minutes) than to Glassfish4.1 (around 2 minutes). That's about 5 times slower. [EDIT: 2016-09-13 Tried with Payara 163 Full (Payara Server 4.1.1.163) and it took

问题 I am trying to debug my jersey 2 app on Payara 162, but on every request, after the trace information is printed I get this exception and the client gets no response: org.glassfish.grizzly.http.util.MimeHeaders$MaxHeaderCountExceededException: Illegal attempt to exceed the configured maximum number of headers: 100 at org.glassfish.grizzly.http.util.MimeHeaders.createHeader(MimeHeaders.java:396) at org.glassfish.grizzly.http.util.MimeHeaders.addValue(MimeHeaders.java:422) at org.glassfish

问题 I have written a Valve that logs all requests to my webapp. But requests to mywebapp/j_security_check don't show up. Am I missing something, or is impossible? I understand that the call chain should be Valve > JAAS > Filter > Servlet, so those requests should be handled by my Valve. I'm using Payara 5, Form-based authentication, GlassFishValve, and WEB-INF contains a glassfish-web.xml containing <!DOCTYPE glassfish-web-app PUBLIC "-//GlassFish.org//DTD GlassFish Application Server 3.1 Servlet

问题 As the subject said, the needed doctype is not rendered in my JSF pages. My used versions: Payara Server Payara Server 4.1.2.181 #badassfish (build 220)]] Mojarra 2.3.3 ( 20171008-2230 673408fa9199477d87f44521ff873d709128c88b) PrimeFaces 6.2 ("official" version) I already tried the bundled (2.2.14/13/15?) version, no change, so I upgraded to 2.3.3 from github (official release). In my entire project I have only one doctype and that is in my "master" template: base.tpl : <?xml version="1.0"