ejb-3.0

I am learning EJB and I am trying to execute the Helloworld example given in EJB In Action book. My app server is JBoss, I created the Jar file for the bean class and interface in the right directory( I can see the EJB in JMX console). Now I created a simple client using EJB annotations, but I am getting a NullPointerException. Here is my client code. Client code: package com.client; import javax.ejb.EJB; import com.EJB.*; public class HelloWorldClient { @EJB private static HelloWorldInterface HelloBean; public static void main(String[] args) { HelloBean.SayHelloWorldInEJB(); } } Bean class

Hello Everybody i'm new in EJB3, i know how to deploy Session Bean (Stateless or stateful) on Glassfish server in one computer. My question is: how can i deploy session bean on Computer A and Deploy Servlet or JSP on Computer B? It mean Computer A have Session Bean Source and Computer B have Servlet or JSP source. if use 1 computer i can use @EJB dependency inject lookup Session Bean but on another computer how can i do it for client code? Example for 1 computer @EJB private StatelessRemote remote ; double Dosomething= remote.Dosomething(); out.println(Dosomething); Create a "client jar" with

I am sending html and images with javamail but for some reason I don't see the images as part of the html, I see them only as an attachment. I don't know why is that. This is how it looks like when one of my users receive an email: I would like to mention also that is how the html looks like: private String generateActivationLinkTemplate() { String htmlText = ""; htmlText ="<table width=\"600\" border=\"0\" cellspacing=\"0\" cellpadding=\"0\"> <tr> <td><img src=\"cid:logoimg\"/></td> </tr> <tr> <td height=\"220\"> <p>Thanks for Joining Site.com</p> <p>Lorem ipsum dolor sit amet, consectetur

How do I have the following code in my non-ejb application. The code works. @Override public void saveItems(Collection<T> items) { synchronized (em) { EntityTransaction tx = em.getTransaction(); try { tx.begin(); for (T item : items) { saveItem_((Class<T>) null, item); } tx.commit(); } finally { if (tx.isActive()) { tx.rollback(); } } } } In a new application I'm using EJB3 + JSF and would like to re-use the library containing the code above. My peristence unit for the new application looks like this: <persistence-unit name="myApp" transaction-type="JTA"> <provider>org.hibernate.ejb

Is there any situation still ( given that Java EE6 has java:global/, app/, module/ naming standards) that necessitates declaring EJBs or Resources like the example below? @EJB (name = "ejb/PlaceBid", beanInterface = PlaceBid.class) public class ActionBazaarBidControllerServlet extends HttpServlet { } Looking up PlaceBid in the helper class used by ActionBazaarBidControllerServlet PlaceBid placeBid = (PlaceBid)context.lookup("java:comp/env/ejb/PlaceBid"); The java:comp/env/ namespace is sometimes a little understood feature. This namespace corresponds to what is called the Enterprise Naming

My team is developing a new service oriented product with a web front-end. In discussions about what technologies we will use we have settled on running a JBoss application server, and Flex frontend (with possible desktop deployment using Adobe AIR), and web services to interface the client and server. We've reached an impasse when it comes to which server technology to use for our business logic. The big argument is between EJB3 and Spring, with our biggest concerns being scalability and performance, and also maintainability of the code base. Here are my questions: What are the arguments for

Since Spring is able to use transactions just like EJB . For me, Spring is able to replace the requirement of using EJB. Can anyone tell me what are the extra advantages of using EJB? Spring was developed as an alternative to EJB right from its inception, so the answer is of course you can use Spring in place of EJBs. If there's an "advantage" to using EJBs, I'd say that it would depend on the skills of your team. If you have no Spring expertise, and lots of EJB experience, then maybe sticking with EJB 3.0 is a good move. App servers written to support the EJB standard can, in theory, be