wildfly

Why JSF 2.2 takes more time partial rendering an ajax request on Wildfly

由 ￡可爱￡侵袭症＋ 提交于 2019-12-06 03:05:58
问题 I am working on migrating a project from (JSF 1.2, Richfaces 3.3.4 running on JBoss 4.2.3) to (JSF 2.2, Richfaces 4.5 running on Wildfly 8.1.0). After partially migrating some views I found that the performance of the application using JSF 2 is terrible. I noticed this issue when an ajax request is sent, JSF 2 is rendering the whole view although the render attribute is pointing to one outputText Example (Can be downloaded from HERE) In my example I will use the same code sample for both JSF

Multiple persistence units in Wildfly?

由 ∥☆過路亽．° 提交于 2019-12-06 02:56:51
问题 Is it possible to have two persistence units in a Wildfly (9.0.2) application? I get "WFLYJPA0061: Persistence unitName was not specified and there are 2 persistence unit definitions in application deployment deployment "jasper-web.war". Either change the application deployment to have only one persistence unit definition or specify the unitName for each reference to a persistence unit." I have unitName specified in the @PeristenceContext annotations. I read somewhere I could disable <!--

Java EE 7 Automatic Timer (EJB Timer) not working for WildFly 8.1.0

由 三世轮回 提交于 2019-12-06 01:44:28
问题 I am following the Using the Timer Service tutorial to build a simple scheduled execution. Trying the automatic approach and using WildFly 8.1.0 Final for it. Session Bean @Singleton @Startup public class HelloJob { private static final Logger logger = Logger.getLogger(HelloJob.class); public HelloJob() { logger.error(">>> Hello Job Created."); } @Schedule(second="*") public void sayHello() { logger.error(">>> Server Hello!"); } } On deploy the class is properly instantiated printing the >>>

Where is the war file built in Intellij IDEA, located?

由 白昼怎懂夜的黑 提交于 2019-12-05 22:20:13
问题 I'm using IntelliJ IDEA and I'm building and deploying the web-application project every time I'm running it. All of this happens magically within IntelliJ IDEA. However, now I'm supposed to manually deploy it on a test server's wildfly, so I need an artifact file (WAR or EAR) to drop in the standalone/deployments directory on the test server's running WildFly10. I can't for the life of me find where IntelliJ Idea exports the WAR / EAR artifacts so I could copy paste it to the said directory

Wildfly version in JBoss EAP 7.1.0

由 女生的网名这么多〃 提交于 2019-12-05 22:15:11
I am using Java 8 to build my application and planning to use JBoss EAP 7.1.0 for production deployment, but I am not getting which version of Wildfly ships with JBoss EAP 7.1.0. I find Wildfly core 3.0.1 but what is Wildfly core? Also is it recomended to update the Java version of JBoss EAP 6.4 to Java 8 and use it? WildFly is not shipped with the EAP. WildFly is a community project and JBoss EAP is a Red Hat product. They live in separate repositories and even if they usually have some common point in history, you can't say WildFly is shipped with EAP. The closest WildFly version to EAP 7.1

Custom Security mechanism in Java EE 6/7 application

由 流过昼夜 提交于 2019-12-05 22:03:39
I would like to create (implement by my own) authentication mechanism which will be plugged into my Java EE application. As far as I know I have to implement LoginModule and connect this implementation with container mechanisms somehow. But the problem is that I don't know how to do it. Maybe You know where I can find sample code or tutorial about it? In other words I would like to force container to call my classes whenever methods: authenticate, login, and logout are called. Sample implementation : HttpServletRequest.login method will successfully authenticate only users with even numer of

using Jackson annotations in Wildfly

由 一笑奈何 提交于 2019-12-05 22:00:45
I'm struggling to get Jackson Annotations to work in my project which is deployed in wildfly. I already tried implementing a MessageBodyWriter but no success. My project looks like this: I have an ear with an ejb module which holds the annotated Pojos and I have a web module with the REST services. This is my current configuration / dependencies: ejb-module pom.xml: <dependency> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-annotations</artifactId> <version>2.2.3</version> <scope>provided</scope> <type>jar</type> </dependency> rest-module pom.xml: no jackson dependencies.

Single page application with Java EE/Wildfly: server-side configuration

由 …衆ロ難τιáo~ 提交于 2019-12-05 20:44:25
I want to write an SPA with AngularJS on client side and Java EE on server side. If I understand it correctly, the idea for the frontend is to create a default page (let's call it index.html ) and implement routing to exchange parts of this default page. So with every request the default page is loaded and the routing logic replaces its parts depending on context path: <!-- index.html --> <html> <body> <!-- this block is replaced depending on context --> <div ng-view></div> </body> </html> <!-- page one --> <div> <h1>Page One</h1> <a href="/specific">Some specific stuff</a> </div> <!-- page

Wildfly 8.0.0.Final JTA transaction issues

由 可紊 提交于 2019-12-05 20:03:05
Since we use a lot of @ApplicationScoped beans with transaction but we do not want to use EJBs (ApplicationScoped bean does not work with stateless beans), we create our own transaction interceptor such as: @Resource UserTransaction tx; @Resource(mappedName="java:jboss/TransactionSynchronizationRegistry") TransactionSynchronizationRegistry tsr; @AroundInvoke public Object manageTransaction(InvocationContext context) throws Exception { Object result; if (Status.STATUS_NO_TRANSACTION == tsr.getTransactionStatus()) { tx.begin(); // System.out.println("Starting transaction"); result = context

Can a deployment stop itself?

由 大憨熊 提交于 2019-12-05 18:40:59
I'm currently searching for a way to stop a deployment on wildfly programmatically. Background: The application does some health checks in its startup phase using an MBean. If the app determines that the environment is not valid because some resources are missing, it needs to stop its own deployment. The way it was: The application was formerly running on JBoss 4 and simply stopped the whole app server calling the shutdown command using JMX. In case this command failed, it simply terminated the whole JVM using System.exit(1). Current problems: Calling shutdown() via JMX does not work on
订阅 wildfly