I can’t see anything obviously wrong, but perhaps a different approach might help you debug it? You could try specify your datasource in the per-application-context instead of the global tomcat one. You can do this by creating a src/main/webapp/META-INF/context.xml (I’m assuming you’re using the standard maven directory structure – if not, then the META-INF folder … Read more
The terms “jta-datasource” and “resouce-local datasource” are a little vague to me. I guess you actually refer to the jta-datasource and non-jta-datasource elements. In short: if the transaction type of the persistence unit is JTA, the jta-datasource element is used to declare the JNDI name of the JTA data source that will be used to … Read more
Tomcat’s RUNNING.txt which you can find in the root of the bundle states that Apache Tomcat requires Java Standard Edition Runtime Environment (JRE) to run. Minimum version of JRE depends on the version of Tomcat: for Tomcat 6.0 it is Java 5, for Tomcat 7.0 – Java 6. However you can also use JDK because, … Read more
What we do is to put it in a separate directory on the server (you could use something like /config, /opt/config, /root/config, /home/username/config, or anything you want). When our servlets start up, they read the XML file, get a few things out of it (most importantly DB connection information), and that’s it. I asked about … Read more
IN tests is value of single valued path expression (persistent attribute of your entity) in values you provided to query (or fetched via subquery). MEMBER OF tests is value you provided to query (or defined with expression) member of values in some collection in your entity. Lets’s use following example entity: @Entity public class EntityA … Read more
3.7 (code name Indigo) and 3.8 are bug fixes and stability releases whereas 4.0,4.1,4.2 (code name Juno) are new feature set mature platform releases. Release 3.8 and 4.2 are going on simultaneously. You can find more on the eclipse project plans here. Juno specific plans can be found here.
Interceptors are used to implement cross-cutting concerns, such as logging, auditing, and security, from the business logic. In Java EE 5, Interceptors were allowed only on EJBs. In Java EE 6, Interceptors became a new specification of its own, abstracted at a higher level so that it can be more generically applied to a broader … Read more
I had the same problem using Apache commons-fileupload. I did not find out what causes the problems especially because I have the UTF-8 encoding in the following places: 1. HTML meta tag 2. Form accept-charset attribute 3. Tomcat filter on every request that sets the “UTF-8” encoding -> My solution was to especially convert Strings … Read more
Your method is not wrong, but there’s a better one. You have to cast to MethodSignature MethodSignature signature = (MethodSignature) joinPoint.getSignature(); Method method = signature.getMethod();
Your Customer class has to be discovered by CDI as a bean. For that you have two options: Put a bean defining annotation on it. As @Model is a stereotype it’s why it does the trick. A qualifier like @Named is not a bean defining annotation, reason why it doesn’t work Change the bean discovery … Read more