Injecting session bean from different EAR

Dear all,
I am using ejb3. i have ejb.ear and web.ear. both deploy in same weblogic server.
i want to inject session bean from ejb.ear inside web.ear.
With Regards,
WP

hi,
Currently, we want to separate it. Because may be we will deploy in different server in the future.
So far, i can inject it using remote interface.
How about local interface? is it possible to use local interface? because so far both deploy on same server.
As far as i know, glassfish can't. isn't it?
it is j2ee standard or server specific?
With Regards,
WP

Similar Messages

Looking up of a stateless session bean from an MDB

Hi,
I have been trying to invoke a method on a stateless session bean from an MDB on receipt of a message from a queue. The bean receives the message. Then it gets the initial context, but after this the following message appears:
javax.naming.NamingException: Error instantation environment context for Message DrivenBean MyMDB: No location specified and no suitable instance of the type 'MySessionRemote' found for the ejb-ref <mySessionBean> at com.evermind.server.ejb.MessageDrivenHome.getEnvironmentContext(MessageDrivenHome.java:559)
The session bean is in a seperate ear file. These are the deployment descriptors of the MDB:
ejb-jar:
<ejb-jar>
 <description>A Message-Driven Beans</description>
 <enterprise-beans>
 <message-driven>
 <description></description>
 <ejb-name>MyMDB</ejb-name>
 <ejbclass>MyMDB</ejb-class>
 <message-driven-destination>
 <jms-destination-type>javax.jms.Queue</jms-destination-type>
 </message-driven-destination>
 <ejb-ref>
 <ejb-ref-name>MySessionEJB</ejb-ref-name>
 <ejb-ref-type>Session</ejb-ref-type>
 <home>MySessionEJBHome</home>
 <remote>MySessionRemote</remote>
 </ejb-ref>
 </message-driven>
 </enterprise-beans>
 <assembly-descriptor>
 </assembly-descriptor>
</ejb-jar>
orion-ejb-jar
<orion-ejb-jar>
<enterprise-beans>
 <message-driven-deployment name="QueueProcessor" destination-location="jms/theQueue" connection-factory-location="jms/theQueueConnectionFactory">
 </message-driven-deployment>
 </enterprise-beans>
 <assembly-descriptor>
 </assembly-descriptor>
</orion-ejb-jar>
The lookup name which I give in MDB is:
java:comp/env/MySessionEJB

Hi,
 Thanks for your replies.I did as you had suggested.I added ejb-local-ref to the ejb-jar.xml and i provided ejb-ref as MyBean.
My lookup code uses the string
ctxt.lookup("localejbs\MyBean");
But still i get Naming Exception.
I tried something different yesterday.
I changed the code to use
InitialContext ctxt = new InitialContext();
ctxt.lookup("localejbs/"+ pathfromJNDIRegistry);
and this time i did not get Naming exception but i got RemoteException saying there was error loading the class.
Is there something i need to add somewhere for the classloader to be able to find and load this class in the second scenario.
Please suggest me which method to go for amongst the two and what is the missing information i need to add.
Thanks
Priya

Trying to call stateless session bean from MDB

Folks,
Am working on RAD and WAS 8.
I have an MDB. And a stateless session bean (AOBean under EJB project).
While the listener listens to the messages from queue, it also tries to persist to db. I want to achieve this via a method of AOBean (through instantiating session bean or by injection).
I have been sucessful by invoking a method from AOBean class - that method just returns a string (without any objects being passed)
Problem:
I am getting IllegalStateException when I try to invoke a method of AOBean class, that has an object as a parameter
For eg:
MDB
@EJB(name="ejb/TransactionMgrAOBean", mappedName="ejb/TransactionMgrAOBean")
ITransactionMgrAO tranAO;
    public void onMessage(Message message) {
     TextMessage textMessage = (TextMessage) message;
     boolean status = false;
try {
   TransactionVO tranVO = getTransactionVO();//Here building the object to be passed to session bean
   String status1 = tranAO.getVersion(tranVO);
}catch(Exception e){
AOBean
@Stateless
@Remote({ ITransactionMgrAO.class })
@WebService
public class TransactionMgrAOBean {
public String getVersion(TransactionVO tranVO) throws Exception{
try{
//business logic
} catch(Exception e){
throw e;
return true;
TransactionVO implements Serializable has also inner static classes that are not Serializable.
EXCEPTION: At runtime we are getting exception saying that the inner classes are not serialized.
REASON why we are invoking session bean from MDB? We found that if we invoke any service from AOBean the transaction management was successful. We are using sessionContext.setRollBackonly when an exception occurs. Tranasactions are not rolled back when any db exception occurs if we invoke business logic methods from Model layer of another NON-EJB package.
Hope I have provided enough information!

My concret problem is that I want to call an ejb session contained in an ejb project from a session bean in a different web project. When I include the code in my web session bean I get the error adjunted:
- Code:
@EJB
private UserRemote userSessionBean;
- Error:
Exception Details: javax.naming.NameNotFoundException
pac.UserRemote#pac.UserRemote not found
Possible Source of Error:
Class Name: com.sun.enterprise.naming.TransientContext
File Name: TransientContext.java
Method Name: doLookup
Line Number: 216
Any suggestion?

Accessing the same stateful session bean from multiple clients in a clustered environment

I am trying to access the same stateful session bean from multiple
 clients. I also want this bean to have failover support so we want to
 deploy it in a cluster. The following description is how we have tried
 to solve this problem, but it does not seem to be working. Any
 insight would be greatly appreciated!
 I have set up a cluster of three servers. I deployed a stateful
 session bean with in memory replication across the cluster. A client
 obtains a reference to an instance of one of these beans to handle a
 request. Subsequent requests will have to use the same bean and could
 come from various clients. So after using the bean the first client
 stores the handle to the bean (actually the replica aware stub) to be
 used by other clients to be able to obtain the bean. When another
 client retrieves the handle gets the replica aware stub and makes a
 call to the bean the request seems to unpredictably go to any of the
 three servers rather than the primary server hosting that bean. If the
 call goes to the primary server everything seems to work fine the
 session data is available and it gets backed up on the secondary
 server. If it happens to go to the secondary server a bean that has
 the correct session data services the request but gives the error
 <Failed to update the secondary copy of a stateful session bean from
 home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
 to the primary server will not reflect changes made on the secondary
 and vice versa. If the request happens to go to the third server that
 is not hosting an instance of that bean then the client receives an
 error that the bean was not available. From my understanding I thought
 the replica aware stub would know which server is the primary host for
 that bean and send the request there.
 Thanks in advance,
 Justin


 If 'allow-concurrent-call' does exactly what you need, then you don't have a problem,
 do you?
 Except of course if you switch ejb containers. Oh well.
 Mike
 "FBenvadi" <[email protected]> wrote:
 >I've got the same problem.
 >I understand from you that concurrent access to a stateful session bean
 >is
 >not allowed but there is a
 >token is weblogic-ejb-jar.xml that is called 'allow-concurrent-call'
 >that
 >does exactly what I need.
 >What you mean 'you'll get a surprise when you go to production' ?
 >I need to understand becouse I can still change the design.
 >Thanks Francesco
 >[email protected]
 >
 >"Mike Reiche" <[email protected]> wrote in message
 >news:[email protected]...
 >>
 >> Get the fix immediately from BEA and test it. It would be a shame to
 >wait
 >until
 >> December only to get a fix - that doesn't work.
 >>
 >> As for stateful session bean use - just remember that concurrent access
 >to
 >a stateful
 >> session bean is not allowed. Things will work fine until you go to
 >production
 >> and encounter some real load - then you will get a surprise.
 >>
 >> Mike
 >>
 >> [email protected] (Justin Meyer) wrote:
 >> >I just heard back from WebLogic Tech Support and they have confirmed
 >> >that this is a bug. Here is their reply:
 >> >
 >> >There is some problem in failover of stateful session beans when its
 >> >run from a java client.However, it is fixed now.
 >> >
 >> >The fix will be in SP2 which will be out by december.
 >> >
 >> >
 >> >Mike,
 >> >Thanks for your reply. I do infact believe we are correctly using
 >a
 >> >stateful session bean however it may have been misleading from my
 >> >description of the problem. We are not accessing the bean
 >> >concurrently from 2 different clients. The second client will only
 >> >come into play if the first client fails. In this case we want to
 >be
 >> >able to reacquire the handle to our stateful session bean and call
 >it
 >> >from the secondary client.
 >> >
 >> >
 >> >Justin
 >> >
 >> >"Mike Reiche" <[email protected]> wrote in message
 >news:<[email protected]>...
 >> >> You should be using an entity bean, not a stateful session bean
 >for
 >> >this application.
 >> >>
 >> >> A stateful session bean is intended to be keep state (stateful)
 >for
 >> >the duration
 >> >> of a client's session (session).
 >> >>
 >> >> It is not meant to be shared by different clients - in fact, if
 >you
 >> >attempt to
 >> >> access the same stateful session bean concurrently - it will throw
 >> >an exception.
 >> >>
 >> >> We did your little trick (storing/retrieving handle) with a stateful
 >> >session bean
 >> >> on WLS 5.1 - and it did work properly - not as you describe. Our
 >sfsb's
 >> >were not
 >> >> replicated as yours are.
 >> >>
 >> >> Mike
 >> >>
 >> >> [email protected] (Justin Meyer) wrote:
 >> >> >I am trying to access the same stateful session bean from multiple
 >> >> >clients. I also want this bean to have failover support so we want
 >> >to
 >> >> >deploy it in a cluster. The following description is how we have
 >tried
 >> >> >to solve this problem, but it does not seem to be working. Any
 >> >> >insight would be greatly appreciated!
 >> >> >
 >> >> >I have set up a cluster of three servers. I deployed a stateful
 >> >> >session bean with in memory replication across the cluster. A client
 >> >> >obtains a reference to an instance of one of these beans to handle
 >> >a
 >> >> >request. Subsequent requests will have to use the same bean and
 >could
 >> >> >come from various clients. So after using the bean the first client
 >> >> >stores the handle to the bean (actually the replica aware stub)
 >to
 >> >be
 >> >> >used by other clients to be able to obtain the bean. When another
 >> >> >client retrieves the handle gets the replica aware stub and makes
 >> >a
 >> >> >call to the bean the request seems to unpredictably go to any of
 >the
 >> >> >three servers rather than the primary server hosting that bean.
 >If
 >> >the
 >> >> >call goes to the primary server everything seems to work fine the
 >> >> >session data is available and it gets backed up on the secondary
 >> >> >server. If it happens to go to the secondary server a bean that
 >has
 >> >> >the correct session data services the request but gives the error
 >> >> ><Failed to update the secondary copy of a stateful session bean
 >from
 >> >> >home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
 >> >> >to the primary server will not reflect changes made on the secondary
 >> >> >and vice versa. If the request happens to go to the third server
 >that
 >> >> >is not hosting an instance of that bean then the client receives
 >an
 >> >> >error that the bean was not available. From my understanding I
 >thought
 >> >> >the replica aware stub would know which server is the primary host
 >> >for
 >> >> >that bean and send the request there.
 >> >> >
 >> >> >Thanks in advance,
 >> >> >Justin
 >>
 >
 >

JNDI Naming Problem accessing Session Bean from Message Driven Bean

Hi,
     I am facing a very strange problem in JNDI look up accessing a Session Bean from a Message Driven Bean. I have a session fa�ade bean(Remote Bean) which is being called from Struts Action class getting the home reference from the ServiceLocator (I have implemented ServiceLocator pattern to obtain JNDI reference for all EJBs). When I am calling the session fa�ade EJB from the Struts Action class everything is working fine.
     But when I am trying to call the same EJB from my Message Driven Bean, I am getting a JNDI exception (NameNotFoundException - No Object bound to name �java:comp/env/ejb/EJBJNDIName�). I am trying to get the remote reference from the same ServiceLocator which is successfully providing me a reference while calling from the struts action class. But the same ServiceLocator is not able to provide me a reference while calling from the Message Driven Bean. If I use the JNDI name directly like �EJBJNDIName� in the lookup it is working fine. The lookup for the name is working fine and I am able to call the Session Fa�ade bean with that reference.
     I am really not sure what exactly the problem is. If I have any problem in the ServiceLocator, it should have given me the same error while calling from Struts Action class. But it is working fine with the full name �java:comp/env/ejb/EJBJNDIName� calling from the struts action class. I am not sure whether Message Driven Bean has something to do with it. Why I am not able to get a reference of the EJB with the full name? Please Help.
Thanks
Amit

Hi Bhagya,
Thanks for your response. I think from EJB container we can call Local EJBs with the full JNDI name. The session facade bean which is being called is a remote bean. From the session facade bean I am calling a local stateless session bean for database access. I am getting the reference of the local EJB from my session facade bean with full JNDI name "java:comp/env/ejb/EJBJNDIName". It is working fine with out any problem. My servicelocator is able to provide me the reference of the local EJB from the session facade remote bean with Full JNDI name. I am only having this problem calling from the MDB. I am really not sure whether what is causing it?
Thanks
Amit

How can i lookup a session bean from the client side

how can i lookup a session bean from the client side...........i am using sun appserver..............
this is my code.................[B]
private final static String JNDI_NAME="ejb/LmsBean";
private static String url="ldap://localhost:4848";
Hashtable h=new Hashtable();
h.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.ldap.LdapCtxFactory");
h.put(Context.PROVIDER_URL,url);
System.out.println("Before Loading Context in Delegate");
Context ctx=new InitialContext(h);
System.out.println("Loaded Context in Delegate");
Object obj=ctx.lookup(JNDI_NAME);
System.out.println("Loaded Object in Delegate");
System.out.println("Before Loading Home in Delegate");
LmsHome home = (LmsHome )PortableRemoteObject.narrow(obj,com.parx.lms.controller.LmsHome.class);
System.out.println("Loaded Home in Delegate");
lms = home.create();
System.out.println("Loaded remote in Delegate");
[B]and i got the exception........
Inside Client before calling delegate
Before Loading Context in Delegate
javax.naming.CommunicationException: Request: 1 cancelled
javax.naming.CommunicationException: Request: 1 cancelled
at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:60)
at com.sun.jndi.ldap.Connection.readReply(Connection.java:405)
at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:340)
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:171)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2640)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:290)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.ja
va:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.jav
a:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
62)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.parx.lms.lmsdelegate.LmsDelegate.getController(LmsDelegate.java:3
0)
at com.parx.lms.lmsdelegate.LmsDelegate.addUserDelegate(LmsDelegate.java
:50)
at com.parx.lms.client.consoleClient.Client.main(Unknown Source)
pls go tru the exception and pls help.........

That url string should be having the server name or ip instead of localhost.

Initialize a stateful session bean from another

Hi,
I am trying to create and initialize a stateful session bean from another stateful session bean. The code is as follows
This method belongs to DefaultSessionBean where it creates the AdminSessionBean based on few checks and returns it to the client.
    public AdminSession getAdminSession() throws UnknownException, WarningException {
        checkSessionUser("getAdminSession");
        if (isAdmin()) {
            AdminSession adminSession;
            try {
                final Context context = IToolsUtil.getInitialContext();
                adminSession = (AdminSession)context.lookup("AdminSession");
                System.out.println("Successfully created the adminsession bean");
            } catch (NamingException ne) {
                ne.printStackTrace();
                throw new UnknownException (new CatalogHelper("ITOOLS_100019", new Object[]{"Admin", ne.getMessage()}));
            System.out.println("adminsession will be returned");
            return adminSession;
        } else {
            throw new WarningException (new CatalogHelper("ITOOLS_000042", sessionUser.getUserhandle()));
    }Another method in DefaultSessionBean, creates its local interface and returns it.
    public DefaultSessionLocal getDefaultSessionLocal() {
        DefaultSessionLocal dsl = (DefaultSessionLocal)context.getBusinessObject(DefaultSessionLocal.class);
        System.out.println("local created.");
        return dsl;
    }Client call initialize method of the AdminSessionBean which is mentioned below:
    public void initialize(DefaultSession ds) throws WarningException, UnknownException {
        this.ds = ds.getDefaultSessionLocal();
        this.rfl = ReadFieldList.getInstance();
        this.fm = new FinderMethods();
    }The client code where it gets the adminSession and initializes is
   public static AdminSession getAdminSession(DefaultSession ds) throws ViewException {
        AdminSession as;
        try {
            as = ds.getAdminSession();
            System.out.println("got admin session");
        } catch (WarningException we) {
             we.printStackTrace();
            throw new ViewException(we.getCatalogHelper());
        } catch (UnknownException ue) {
            ue.printStackTrace();
            throw new ViewException(ue.getCatalogHelper());
        } catch (OracleRemoteException ore) {
            ore.printStackTrace();
            throw new ViewException(new CatalogHelper("ITOOLS_050003", ore.getMessage()));
        // Initialize Admin Session
        try {
            System.out.println("before getting it.");
            as.initialize(ds);
            System.out.println("adminsession is initialized");
        } catch (WarningException we) {
            as.remove();
            as = null;
            throw new ViewException(we.getCatalogHelper());
        } catch (UnknownException ue) {
            as.remove();
            as = null;
            throw new ViewException(ue.getCatalogHelper());
        } catch (OracleRemoteException ore) {
            as.remove();
            as = null;
            throw new ViewException(new CatalogHelper("ITOOLS_050003", ore.getMessage()));
        System.out.println("got admin session");
        return as;
    }Apart from this I am using OC4J 10.1.3.1 tool test my application.
When I am calling initialize method of the AdminSession I am getting the following error.
06/10/24 12:26:08 Entered
06/10/24 12:26:08 got default session
06/10/24 12:26:08 Successfully created the adminsession bean
06/10/24 12:26:08 adminsession will be returned
06/10/24 12:26:08 got admin session
06/10/24 12:26:08 before getting it.
2006-10-24 12:26:08.156 WARNING J2EE RMI-00009 Exception returned by remote server: {0}
06/10/24 12:26:08 com.itools.vs.view.exception.ViewException
06/10/24 12:26:08      at com.itools.vs.view.util.ViewUtil.getAdminSession(ViewUtil.java:71)
06/10/24 12:26:08      at com.itools.vs.view.backing.Admin.CreateUser.submit_action(CreateUser.java:182)
06/10/24 12:26:08      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
06/10/24 12:26:08      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
06/10/24 12:26:08      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
06/10/24 12:26:08      at java.lang.reflect.Method.invoke(Method.java:585)
06/10/24 12:26:08      at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:146)
06/10/24 12:26:08      at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:92)
06/10/24 12:26:08      at org.ajax4jsf.framework.ajax.AjaxActionComponent.broadcast(AjaxActionComponent.java:88)
06/10/24 12:26:08      at org.ajax4jsf.framework.ajax.AjaxViewRoot.processEvents(AjaxViewRoot.java:274)
06/10/24 12:26:08      at org.ajax4jsf.framework.ajax.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:250)
06/10/24 12:26:08      at org.ajax4jsf.framework.ajax.AjaxViewRoot.processApplication(AjaxViewRoot.java:405)
06/10/24 12:26:08      at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:95)
06/10/24 12:26:08      at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:245)
06/10/24 12:26:08      at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:110)
06/10/24 12:26:08      at javax.faces.webapp.FacesServlet.service(FacesServlet.java:213)
06/10/24 12:26:08      at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
06/10/24 12:26:08      at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:67)
06/10/24 12:26:08      at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:223)
06/10/24 12:26:08      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
06/10/24 12:26:08      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
06/10/24 12:26:08      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
06/10/24 12:26:08      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
06/10/24 12:26:08      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
06/10/24 12:26:08      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
06/10/24 12:26:08      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
06/10/24 12:26:08      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
06/10/24 12:26:08      at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
06/10/24 12:26:08      at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
06/10/24 12:26:08      at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
06/10/24 12:26:08      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
06/10/24 12:26:08      at java.lang.Thread.run(Thread.java:595)
06/10/24 12:26:08 ITOOLS_050003: Failed to get Admin Session.
Exception is "Error marshalling objects, Not Serializable: java.io.NotSerializableException: DefaultSession_RemoteProxy_6nein01; nested exception is:
     java.io.NotSerializableException: DefaultSession_RemoteProxy_6nein01".
[b/

Your remote client passes a DefaultSession to AdminSession.initialize(..). This DefaultSession has to be a remote type. In your client, how does it get DefaultSession?
Did your client look up DefaultSession, and have it return a (sessionContext.getBusinessObject(DefaultSession.class))? If so, it should work.

How can I set the value to a session bean from backing bean

Hi Experts,
How can I set the value to a session bean from backing bean where I have created getter and setter
methods for that variable.
Basically I am using ADFUtils class where I am able to get the value from session bean
using following expression
String claimType =
(String)ADFUtil.invokeEL("#{ClaimValueObj.getClaimType}");
Thanks
Gayaz

Gayaz,
Wrong Post !!
Post in JDeveloper and ADF
Thanks
--Anil

Problem when calling session bean from main.

Hi everyone
I get the following error when calling a session bean from main(String args[]).
Sep 3, 2008 9:11:13 AM com.sun.enterprise.appclient.MainWithModuleSupport <init>
WARNING: ACC003: Application threw an exception.
java.lang.NullPointerException
at databasetest.Main.main(Main.java:26)
Here is my code beneath.
I'm using netbeans and glassfish application server.
Everything is in the same project, called DatabaseTest, I also have deployed the application before running the client.
I'm running the client as follows, right click on the DatabaseTest-app-client and select run.
The client:
package databasetest;
import com.test.UsersFacadeRemote;
import javax.ejb.EJB;
import com.test.Users;
public class Main {
 @EJB
 private static UsersFacadeRemote usersFacade;
 public static void main(String[] args) {
 Users users = new Users(12, 34);
 usersFacade.create(users);
}The remote facade I'm calling:
package com.test;
import java.util.List;
import javax.ejb.Remote;
@Remote
public interface UsersFacadeRemote {
 void create(Users users);
 void edit(Users users);
 void remove(Users users);
 Users find(Object id);
 List<Users> findAll();
}The stateless bean:
package com.test;
import java.util.List;
import javax.ejb.Stateless;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
@Stateless
public class UsersFacade implements UsersFacadeRemote {
 @PersistenceContext
 private EntityManager em;
 public void create(Users users) {
 em.persist(users);
 public void edit(Users users) {
 em.merge(users);
 public void remove(Users users) {
 em.remove(em.merge(users));
 public Users find(Object id) {
 return em.find(com.test.Users.class, id);
 public List<Users> findAll() {
 return em.createQuery("select object(o) from Users as o").getResultList();
}

looks like you're banging your head against the same brick wall as [I have done|http://forums.sun.com/thread.jspa?forumID=13&threadID=5317110] and [others have in the past|http://forums.sun.com/thread.jspa?forumID=136&threadID=5259913] if that's any consolation.
Funny thing is, mine did actually work in the debugger but not when running!
Strange thing that.
I did initially interest someone from the developers but they couldn't really help, ended up saying : try instantiating your beans the EJB 2.1 way and see where that gets you. Yes that works but they promised us "hey no more dopey xml deployment descriptors just some cool annotations" didn't they?
I've got the feeling were' missing something really obvious!
Edited by: sebthebike on 03-Sep-2008 12:21

HowTo talk to a Session bean from an Applet sample app. problem

Hi!
When I push the "Call EJB" button in the sample application I get the following exception:
2005.02.20. 15:49:27 com.evermind.server.rmi.RMIClient createRemoteInvocationHandlerFactory
WARNING: com.evermind.server.ejb.EJBRemoteInvocationHandlerFactory
java.lang.ClassNotFoundException: com.evermind.server.ejb.EJBRemoteInvocationHandlerFactory
 at sun.applet.AppletClassLoader.findClass(Unknown Source)
 at java.lang.ClassLoader.loadClass(Unknown Source)
 at sun.applet.AppletClassLoader.loadClass(Unknown Source)
 at java.lang.ClassLoader.loadClass(Unknown Source)
 at java.lang.ClassLoader.loadClassInternal(Unknown Source)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Unknown Source)
 at com.evermind.server.rmi.RMIClient.createRemoteInvocationHandlerFactory(RMIClient.java:427)
 at com.evermind.server.rmi.RMIClient.initHandlerFactories(RMIClient.java:415)
 at com.evermind.server.rmi.RMIClient.<init>(RMIClient.java:61)
 at com.evermind.server.rmi.RMIClient.getInstance(RMIClient.java:464)
 at com.evermind.server.rmi.RMIInitialContext.<clinit>(RMIInitialContext.java:48)
 at oracle.j2ee.rmi.RMIInitialContextFactory.getInitialContext(RMIInitialContextFactory.java:58)
 at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
 at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
 at javax.naming.InitialContext.init(Unknown Source)
 at javax.naming.InitialContext.<init>(Unknown Source)
 at oracle.otnsamples.EJBCaller.getInitialContext(Unknown Source)
 at oracle.otnsamples.EJBCaller.callEjb(Unknown Source)
 at oracle.otnsamples.EJBCaller.access$000(Unknown Source)
 at oracle.otnsamples.EJBCaller$2.actionPerformed(Unknown Source)
 at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
 at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
 at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
 at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
 at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
 at java.awt.Component.processMouseEvent(Unknown Source)
 at java.awt.Component.processEvent(Unknown Source)
 at java.awt.Container.processEvent(Unknown Source)
 at java.awt.Component.dispatchEventImpl(Unknown Source)
 at java.awt.Container.dispatchEventImpl(Unknown Source)
 at java.awt.Component.dispatchEvent(Unknown Source)
 at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
 at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
 at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
 at java.awt.Container.dispatchEventImpl(Unknown Source)
 at java.awt.Component.dispatchEvent(Unknown Source)
 at java.awt.EventQueue.dispatchEvent(Unknown Source)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.io.IOException: open HTTP connection failed.
 at sun.applet.AppletClassLoader.getBytes(Unknown Source)
 at sun.applet.AppletClassLoader.access$100(Unknown Source)
 at sun.applet.AppletClassLoader$1.run(Unknown Source)
 at java.security.AccessController.doPrivileged(Native Method)
 ... 43 more
javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
 java.net.ConnectException: Connection refused: connect [Root exception is java.net.ConnectException: Connection refused: connect]
 at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:183)
 at javax.naming.InitialContext.lookup(Unknown Source)
 at oracle.otnsamples.EJBCaller.callEjb(Unknown Source)
 at oracle.otnsamples.EJBCaller.access$000(Unknown Source)
 at oracle.otnsamples.EJBCaller$2.actionPerformed(Unknown Source)
 at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
 at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
 at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
 at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
 at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
 at java.awt.Component.processMouseEvent(Unknown Source)
 at java.awt.Component.processEvent(Unknown Source)
 at java.awt.Container.processEvent(Unknown Source)
 at java.awt.Component.dispatchEventImpl(Unknown Source)
 at java.awt.Container.dispatchEventImpl(Unknown Source)
 at java.awt.Component.dispatchEvent(Unknown Source)
 at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
 at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
 at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
 at java.awt.Container.dispatchEventImpl(Unknown Source)
 at java.awt.Component.dispatchEvent(Unknown Source)
 at java.awt.EventQueue.dispatchEvent(Unknown Source)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(Unknown Source)
 at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
 at java.net.PlainSocketImpl.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.<init>(Unknown Source)
 at java.net.Socket.<init>(Unknown Source)
 at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:394)
 at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:80)
 at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:250)
 at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:154)
 ... 26 more
javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
 java.net.ConnectException: Connection refused: connect [Root exception is java.net.ConnectException: Connection refused: connect]
 at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:183)
 at javax.naming.InitialContext.lookup(Unknown Source)
 at oracle.otnsamples.EJBCaller.callEjb(Unknown Source)
 at oracle.otnsamples.EJBCaller.access$000(Unknown Source)
 at oracle.otnsamples.EJBCaller$2.actionPerformed(Unknown Source)
 at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
 at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
 at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
 at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
 at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
 at java.awt.Component.processMouseEvent(Unknown Source)
 at java.awt.Component.processEvent(Unknown Source)
 at java.awt.Container.processEvent(Unknown Source)
 at java.awt.Component.dispatchEventImpl(Unknown Source)
 at java.awt.Container.dispatchEventImpl(Unknown Source)
 at java.awt.Component.dispatchEvent(Unknown Source)
 at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
 at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
 at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
 at java.awt.Container.dispatchEventImpl(Unknown Source)
 at java.awt.Component.dispatchEvent(Unknown Source)
 at java.awt.EventQueue.dispatchEvent(Unknown Source)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(Unknown Source)
 at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
 at java.net.PlainSocketImpl.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.<init>(Unknown Source)
 at java.net.Socket.<init>(Unknown Source)
 at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:394)
 at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:80)
 at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:250)
 at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:154)
 ... 26 more
Thanks!

Refer to the following link for a list of tutorials that will guide you through the steps you have queried about: http://www.oracle.com/technology/tech/java/ejb30.html
Also, if you are attempting to call a session bean from your applet code you may run into firewall issues depending on your corporate infrastructure. RMI does not run over the ever popular port 80 and therefore is not always open on company firewalls. If you run into trouble you may have to use HTTP Tunneling. A better alternative maybe to call your session bean as a web service which is provided to you by default in the EJB 3.0 spec.

How to create session id from different string controls

how to create session id from different string controls

fais,
Please create the VI you are talking about and save some default data into all of the controls. Also on the front panel, place the session ID that should be generated by that data. Now, post your VI to a response so I can download it. I can then take this VI and help you create the functionality. (Please post what version of LabVIEW you are using.)
My guess it that you are going to need to use a good number of string concatenations as well as a few string indexes to get parts of strings out. As for the date, you can use a Property node with the Numeric Text.Text property to get the actual string displayed on the front panel for the date and parse out the parts that you want.
Randy Hoskin
Applications Engineer
National Instruments
h
ttp://www.ni.com/ask

How call session bean from Client side

Hi
calling session bean from client side it gives Lookup erroe, it gives JNDI error
how we know session bean is working. in Admin tree bean statis is reb Flaf, and ID is "Down" how we activate it..
null

If you can make a connection using sess_sh, then you know that you have configured your database and listener properly. If it is not working, read the manuals that you can download from technet. They are pretty good, and if you follow the directions, you should see success.
Good Luck!
Brad

Do JNDI look up for entity beans from a session bean in different jars

I have a problem doing entity beans JNDI look up from a session bean which is deployed
as a separate package (session.jar) from the entity beans (entity.jar)
I believe if both session bean and entity beans are deployed into one jar and
I specify ejb-local-reference-description for session bean, it should work. However,
due to some reason, they have to be in separated packages but still in the same
container. Then question how to do JNDI lookup given entity beans only have local
interfaces?
FYI.
1 both session.jar and entity.jar are self-contained. i.e., no deployment error.
each JNDI name can be viewed from JNDI tree
2. weblogic-ejb-jar.xml for session.jar
<weblogic-ejb-jar>
<description><![CDATA[Generated by XDoclet]]></description>
<weblogic-enterprise-bean>
<ejb-name>PetstoreLogic</ejb-name>
<stateless-session-descriptor>
</stateless-session-descriptor>
<reference-descriptor>
</reference-descriptor>
<jndi-name>PetstoreLogic</jndi-name>
<local-jndi-name>PetstoreLogicLocal</local-jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
3. weblogic-ejb-jar.xml (code snip) for entity.jar
<weblogic-enterprise-bean>
<ejb-name>Account</ejb-name>
<entity-descriptor>
<persistence>
<persistence-type>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-type>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
</persistence-use>
</persistence>
</entity-descriptor>
<reference-descriptor>
</reference-descriptor>
<local-jndi-name>net.sourceforge.cpetstore/AccountLocalHome</local-jndi-name>
</weblogic-enterprise-bean>
4. if I do
accountLocalHome = (AccountLocalHome) ic.lookup("net/sourceforge/cpetstore/AccountLocalHome");
get error like:
javax.naming.LinkException: . Root exception is javax.naming.NameNotFoundException:
While trying to look up /app/ejb/net.sourceforge.cpetstore-entity.jar#Account/local-home
in /app/ejb/cpetstore-ejb.jar#PetstoreLogic.; remaining name '/app/ejb/net/sourceforge/cpetstore-entity/jar#Account/local-home'
 at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:869)
 at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:150)
 at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)

In weblogic-ejb-jar.xml use jndi-name instead of local-jndi-name in reference-descriptor
element.
"Qiming He" <[email protected]> wrote:
>
I have a problem doing entity beans JNDI look up from a session bean
which is deployed
as a separate package (session.jar) from the entity beans (entity.jar)
I believe if both session bean and entity beans are deployed into one
jar and
I specify ejb-local-reference-description for session bean, it should
work. However,
due to some reason, they have to be in separated packages but still in
the same
container. Then question how to do JNDI lookup given entity beans only
have local
interfaces?
FYI.
1 both session.jar and entity.jar are self-contained. i.e., no deployment
error.
each JNDI name can be viewed from JNDI tree
2. weblogic-ejb-jar.xml for session.jar
<weblogic-ejb-jar>
<description><![CDATA[Generated by XDoclet]]></description>
<weblogic-enterprise-bean>
<ejb-name>PetstoreLogic</ejb-name>
<stateless-session-descriptor>
</stateless-session-descriptor>
<reference-descriptor>
</reference-descriptor>
<jndi-name>PetstoreLogic</jndi-name>
<local-jndi-name>PetstoreLogicLocal</local-jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
3. weblogic-ejb-jar.xml (code snip) for entity.jar
<weblogic-enterprise-bean>
<ejb-name>Account</ejb-name>
<entity-descriptor>
<persistence>
<persistence-type>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-type>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
</persistence-use>
</persistence>
</entity-descriptor>
<reference-descriptor>
</reference-descriptor>
<local-jndi-name>net.sourceforge.cpetstore/AccountLocalHome</local-jndi-name>
</weblogic-enterprise-bean>
4. if I do
accountLocalHome = (AccountLocalHome) ic.lookup("net/sourceforge/cpetstore/AccountLocalHome");
get error like:
javax.naming.LinkException: . Root exception is javax.naming.NameNotFoundException:
While trying to look up /app/ejb/net.sourceforge.cpetstore-entity.jar#Account/local-home
in /app/ejb/cpetstore-ejb.jar#PetstoreLogic.; remaining name '/app/ejb/net/sourceforge/cpetstore-entity/jar#Account/local-home'
 at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:869)
 at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:150)
 at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)

How do you use one managed session bean from another?

Hello -
I am a complete newbie to JSF coming from Struts 1. My question is how do you use one managed bean from the method of another one? I think this would be a common senario. For example I put a bean in session scope when a user logs in and in a different method within a different bean I want to get some of this user's information. What is the correct way to retireve one bean from a method in another with session scope?
Also what would the code look like to retieve another bean from the method of a managed bean where the bean you want to retrieve has application scope?
Thank you in advance.

Sinplicity wrote:
Could you be a bit more specific? If a bean is configured in the faces config file then all of it's properties are managed, correct?Not necessarily.
What would the code look like to retireve the bean?You don't retrieve it, it has been injected.
Can I retrieve the whole bean or just a property of the bean. I would be really interested in seeing how this is done in code? And would really love a bit more information on what it means to be a managed property?Time to consult a JSF tutorial.

EJB3 Session Bean from webproject (Netbeans 5.5.1 with Visual Web)

I've been using J2EE 2 Sessoin Beans for some time but looking into moving into the new JavaEE EBJ3. I'm attempting to create a new enterprise project in netbeans and instead of using the web project that it creates I've created a visual web project and attached it to the enterprise project. Everything works great other than the fact that I cannot looking any Session Beans in my context. The logic that is calling the session bean lookup in the Bean of the webpage using JSF. Upon an action being called I'm attempting to lookup the session bean but I get name NameNotFound everyway I try. Below is the sample code. I'm trying injection but it doesn't appear to work from with the JSF Model Bean.
* Page1.java
* Created on September 1, 2007, 1:00 AM
* Copyright smileyq
package demo;
import com.demo.aps.ejb.session.AuthenticationManagerLocal;
import com.demo.aps.ejb.session.HelloWorldLocal;
import com.demo.aps.model.AuthCredentials;
import com.sun.rave.web.ui.appbase.AbstractPageBean;
import com.sun.rave.web.ui.component.Body;
import com.sun.rave.web.ui.component.Button;
import com.sun.rave.web.ui.component.Form;
import com.sun.rave.web.ui.component.Head;
import com.sun.rave.web.ui.component.Html;
import com.sun.rave.web.ui.component.Link;
import com.sun.rave.web.ui.component.Page;
import com.sun.rave.web.ui.component.PasswordField;
import com.sun.rave.web.ui.component.StaticText;
import com.sun.rave.web.ui.component.TextField;
import java.util.logging.Level;
import java.util.logging.Logger;
import javax.ejb.EJB;
import javax.faces.FacesException;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
* Page bean that corresponds to a similarly named JSP page. This
* class contains component definitions (and initialization code) for
* all components that you have defined on this page, as well as
* lifecycle methods and event handlers where you may add behavior
* to respond to incoming events.
public class Page1 extends AbstractPageBean
 // <editor-fold defaultstate="collapsed" desc="Managed Component Definition">
 private int __placeholder;
 @EJB private HelloWorldLocal hwLocalRef;
 * Automatically managed component initialization. WARNING:
 * This method is automatically generated, so any user-specified code inserted
 * here is subject to being replaced.
 private void _init () throws Exception
 private Page page1 = new Page ();
 public Page getPage1 ()
 return page1;
 public void setPage1 (Page p)
 this.page1 = p;
 private Html html1 = new Html ();
 public Html getHtml1 ()
 return html1;
 public void setHtml1 (Html h)
 this.html1 = h;
 private Head head1 = new Head ();
 public Head getHead1 ()
 return head1;
 public void setHead1 (Head h)
 this.head1 = h;
 private Link link1 = new Link ();
 public Link getLink1 ()
 return link1;
 public void setLink1 (Link l)
 this.link1 = l;
 private Body body1 = new Body ();
 public Body getBody1 ()
 return body1;
 public void setBody1 (Body b)
 this.body1 = b;
 private Form form1 = new Form ();
 public Form getForm1 ()
 return form1;
 public void setForm1 (Form f)
 this.form1 = f;
 private StaticText staticText1 = new StaticText ();
 public StaticText getStaticText1 ()
 return staticText1;
 public void setStaticText1 (StaticText st)
 this.staticText1 = st;
 private TextField usernameTxt = new TextField ();
 public TextField getUsernameTxt ()
 return usernameTxt;
 public void setUsernameTxt (TextField tf)
 this.usernameTxt = tf;
 private PasswordField passwordTxt = new PasswordField ();
 public PasswordField getPasswordTxt ()
 return passwordTxt;
 public void setPasswordTxt (PasswordField pf)
 this.passwordTxt = pf;
 private Button loginBtn = new Button ();
 public Button getLoginBtn ()
 return loginBtn;
 public void setLoginBtn (Button b)
 this.loginBtn = b;
 // </editor-fold>
 * Construct a new Page bean instance.
 public Page1 ()
 * Callback method that is called whenever a page is navigated to,
 * either directly via a URL, or indirectly via page navigation.
 * Customize this method to acquire resources that will be needed
 * for event handlers and lifecycle methods, whether or not this
 * page is performing post back processing.
 * Note that, if the current request is a postback, the property
 * values of the components do not represent any
 * values submitted with this request. Instead, they represent the
 * property values that were saved for this view when it was rendered.
 public void init ()
 // Perform initializations inherited from our superclass
 super.init ();
 // Perform application initialization that must complete
 // *before* managed components are initialized
 // TODO - add your own initialiation code here
 // <editor-fold defaultstate="collapsed" desc="Managed Component Initialization">
 // Initialize automatically managed components
 // *Note* - this logic should NOT be modified
 try
 _init ();
 catch (Exception e)
 log ("Page1 Initialization Failure", e);
 throw e instanceof FacesException ? (FacesException) e: new FacesException (e);
 // </editor-fold>
 // Perform application initialization that must complete
 // *after* managed components are initialized
 // TODO - add your own initialization code here
 * Callback method that is called after the component tree has been
 * restored, but before any event processing takes place. This method
 * will only be called on a postback request that
 * is processing a form submit. Customize this method to allocate
 * resources that will be required in your event handlers.
 public void preprocess ()
 * Callback method that is called just before rendering takes place.
 * This method will only be called for the page that
 * will actually be rendered (and not, for example, on a page that
 * handled a postback and then navigated to a different page). Customize
 * this method to allocate resources that will be required for rendering
 * this page.
 public void prerender ()
 * Callback method that is called after rendering is completed for
 * this request, if <code>init()</code> was called (regardless of whether
 * or not this was the page that was actually rendered). Customize this
 * method to release resources acquired in the <code>init()</code>,
 * <code>preprocess()</code>, or <code>prerender()</code> methods (or
 * acquired during execution of an event handler).
 public void destroy ()
 * Return a reference to the scoped data bean.
 protected SessionBean1 getSessionBean1 ()
 return (SessionBean1)getBean("SessionBean1");
 * Return a reference to the scoped data bean.
 protected RequestBean1 getRequestBean1 ()
 return (RequestBean1)getBean("RequestBean1");
 * Return a reference to the scoped data bean.
 protected ApplicationBean1 getApplicationBean1 ()
 return (ApplicationBean1)getBean("ApplicationBean1");
 public String loginBtn_action ()
 // TODO: Process the button click action. Return value is a navigation
 // case name where null will return to the same page.
 AuthCredentials credentials = new AuthCredentials();
 credentials.setUsername (usernameTxt.getText ().toString ());
 credentials.setPassword (passwordTxt.getText().toString ());
 hwLocalRef.printHello ();
 return null;
}

Hi,
I've had the very same problem with RAD.
Try to set the Transaction attribute to SUPPORTS. With SUPPORTS the EJB method will use the same transaction as the caller.
package hu.bme.ett.raktar.facade;
import hu.bme.ett.raktar.ejbs.Raktar;
import hu.bme.ett.raktar.ejbs.controller.RaktarManager;
import javax.ejb.Stateless;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionAttributeType;
@Stateless
@TransactionAttribute(TransactionAttributeType.SUPPORTS)
public class RaktarListazas implements RaktarListazasLocal {
 RaktarManager rm = new RaktarManager();
 * Default constructor.
 public RaktarListazas() {
 // TODO Auto-generated constructor stub
 public Raktar getRaktar(long raktId) {
 return rm.findRaktarByRaktId(raktId);
 public void createRaktar(long raktId) {
 Raktar r = new Raktar();
 r.setRaktId(raktId);
 r.setRaktAzonosito("Y1RAK-01" + raktId);
 r.setMegnevezes("Elso raktaram");
 try {
 rm.createRaktar(r);
 } catch (Exception e) {
 // TODO Auto-generated catch block
 e.printStackTrace();
}Cheers,
Viktor

Injecting session bean from different EAR

Similar Messages

Maybe you are looking for