ejb-3.0

EDIT : Thanks everybody for your answers, but the problem was with my data source configuration, which was actually in auto-commit mode. See my answer below for details. Both the Javadoc of the EntityManager.flush() method and searching for it in Google seem to suggest that the flush method only sends the pending statements to the database and does not commit the transaction. But a simple test web service I created (in Java 7, Oracle 11gR2, JBoss 7.1 and the Web service is packaged as a jar file) seem to indicate otherwise: This is the table creation script: CREATE TABLE test( id INTEGER NOT

I know one can use interceptors before a method call by using the @AroundInvoke annotation. What I would like to do is execute certain code after the method call, so that I can for example create a log entry before and after a method execution. Is this possible with EJB3, or do I need to use AOP? @AroundInvoke interceptor is passed InvocationContext, and proceed() must be called to advance the method. Thus: @AroundInvoke public Object log(InvocationContext ic) throws Exception { logEntry(); try { return ic.proceed(); } finally { logExit(); } } Depending on your needs, you could also log the

This question already has an answer here: How to inject @EJB, @PersistenceContext, @Inject, @Autowired, etc in @FacesConverter? 5 answers This converter is called from my JSF. I already register it inside faces-config.xml public class ProjectConverter implements Converter{ @EJB DocumentSBean sBean; @ManagedProperty(value="#{logging}") private Logging log; public ProjectConverter(){ } public Object getAsObject(FacesContext context, UIComponent component, String value) { if(value.trim().equals("")){ return null; } return sBean.getProjectById(value); } public String getAsString(FacesContext

I am working on a project where we need to decide how we are going to expose our persistence layer. There are currently two options on the table: 1) Use plain DAOs. These would implement an interface and be injected (probably using Weld) in the Business Components which are EJBs. Internally they would use JPA/Hibernate for persistence. 2) Rather than injecting the DAOs using Weld, they would be implemented as EJBs, and injected with @EJB in the Business Components. Does it really make sense to use EJBs for the persistence layer when we are not using its capabilities (e.g. transaction

is there a way to lookup an EJB in weblogic if it implements only local interface? If I use this @Remote public interface TestSessionRemote { public void businessMethod(); } @Stateless(mappedName = "A") public class TestSessionBean implements TestSessionRemote { public void businessMethod() { } } the EJB can be looked up using this name: "A#" + TestSessionRemote.class.getName() If I change the annotation for TestSessionRemote from @Remote to @Local the EJB disappears from JNDI. Is there a way around this? EDIT: I was working with Weblogic 10.3.x (aka 11g) at that time. No, it is not possible.

Is it good way to use both Stateless and Stateful session beans for the different modules if the requirement demands ? ewernli You question is quite vague, but it seems like you basically ask for advice whether it's good to use either stateless or stateful session beans. Stateless session beans (SLSB) are definitively easy to use. There is almost nothing to configure, and they are ideal to expose service. Stateful session beans (SFSB) are superficially similar to SLSB. But the fact their are stateful make their programming model different, and are harder to use. For instance you will need to