Referencing EJB 3.0 ,problem

Hello I have 2 session EJB 3.0 and I would reference one on body of another , but
I have an error form embedded OC4J when I run DEBUG .
Here is my simply code
TransactionController ---
package com.savino.banking.model.facade;
import com.savino.banking.model.entity.Transaction;
import com.savino.banking.model.entity.TransactionItem;
import java.util.List;
import javax.ejb.Stateless;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
@Stateless(name="TransactionController")
public class TransactionControllerBean implements TransactionController,
TransactionControllerLocal {
@PersistenceContext(unitName="Model")
private EntityManager em;
public TransactionControllerBean() {
public Object mergeEntity(Object entity) {
return em.merge(entity);
public Object persistEntity(Object entity) {
em.persist(entity);
return entity;
and I declare a reference to TransactionController into AdminController :
package com.savino.banking.model.facade;
import com.savino.banking.common.exception.BusinessException;
import com.savino.banking.model.entity.Cc;
import com.savino.banking.model.entity.CostCenter;
import com.savino.banking.model.entity.TypeTransaction;
import com.savino.banking.model.entity.UserCcLinks;
import com.savino.banking.model.entity.UserCcLinksPK;
import com.savino.banking.model.entity.Users;
import java.util.List;
import javax.ejb.EJB;
import javax.ejb.Stateless;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
@Stateless(name="AdminController")
public class AdminControllerBean implements AdminController,
AdminControllerLocal {
@PersistenceContext(unitName="Model")
private EntityManager em;
@EJB(name="myController",beanInterface=TransactionControllerLocal.class,beanName="TransactionControllerLocal")
TransactionControllerLocal controller;
public AdminControllerBean() {
And this is the error that I caught :
25-giu-2008 20.03.46 oracle.j2ee.jndi.JndiMessages warningInvalidEJBReference
AVVERTENZA: Impossibile risolvere il riferimento EJB "myController". La creazione di J2EEContext può tuttavia continuare.
25-giu-2008 20.03.46 oracle.j2ee.jndi.JndiMessages warningInvalidEJBReference
AVVERTENZA: Impossibile risolvere il riferimento EJB "myController". La creazione di J2EEContext può tuttavia continuare.
25-giu-2008 20.03.53 oracle.wireless.its.ra.TelnetResourceAdapter run
INFO: Avvio di Industrial Telnet Server versione: Version 10.1.3.0.0 completato.
I am on JDev 10g 10.1.3.1, can anyone help me?
thanks

dupocate of : problem referencing EJB 3.0 ( injection)

Similar Messages

  • EJB 3.0 - problem reading request parameters

    I'm looking at Spring and TopLink integration and deploying with the EJB 3.0 version. I ran into problems when trying to retrieve a parameter from a request. Since I could not see anything wrong, I deployed with Tomcat and the code executed correctly.
    The simple case below illustrates the problem:
    <%@ page session="false"%>
    <%@ taglib uri="http://jakarta.apache.org/taglibs/request-1.0" prefix="req" %>
    <html>
    <head>
    <title>PetClinic :: a Spring Framework demonstration</title>
    </head>
    <body>
    The ID parameter is: <req:parameter name="id"/>
    </body>
    </html>
    Running with http://localhost:8080/sto12/welcomeURL.htm?id=foo causes foo to be displayed in Tomcat but not in OC4J EJB 3.0. Why is this?
    Thanks
    Mike

    Sorry, I tried to submit the problem in a simplified form and I can see I've just made it more confusing. Let me try again.
    Spring ships with a Petclinic sample. The Spring Toplink integration work has provided new classes that allow the Petclinic example to be deployed using Toplink as the object relational mapping. I have it running using Tomcat, but have had problems using OC4J EJB 3.0.
    In the sample app, there is a JSP that allows surname to be entered, which then calls code to search for Owners with a match on surname. That code treats no matches, one match and many matches differently.
    In the case of no matches, the JSP simply displays a message saying no matches found. In the case of many matches, it uses another JSP to display a list of Owners, from which the desired one is selected. The selected one is then displayed by a further JSP on which updates can be made. Where only one match with surname is found, the selection JSP is bypassed.
    Behind the scenes when obtaining the list of matching Owners, the Toplink code simply obtains a list. When one is selected, a further Toplink access is used which returns the selected Owner by reading via the primary key selected from the list. The essence of the problem is that there is a single piece of code in the sample that makes the Toplink call to read by primary key. When called in one scenario, it works, in the other it does not.
    Where that code is invoked as a result of the user selecting from a list, it is the JSP POSTing the selected Owner that transmits the primary key to the code. The code obtains the key from the request and everything works fine.
    Where only one Owner is found, a redirect is done with the key added as a parameter. When the same code as above attempts the retrieve the key, it is unable to do so ie it returns null and the subsequent Toplink call fails.
    Since the above obscures the problem, I played around with two of the JSPs provided - welcome.jsp and index.jsp. In the sample, index.jsp is included in the web.xml under <welcome-file-list> and hence is used when the app is started. It simply redirects to welcome.jsp. (I believe the reason is that all requests go via the Spring DispatcherServlet and are forwarded to the appropriate JSP depending on configuration - hence the comment that they are "virtual").
    When I put code in the index.jsp to display an id parameter and start it with an id provided, it displays the id parameter. When I let the index.jsp simply redirect to welcome.jsp (with an id included and welcome.jsp changed to display the value)it does not display the value.
    I'm sorry this has become a long post. The gist seems to be that I can't extract parameters from requests that have been redirected. As I said at the top of this note, this is not the case with Tomcat - I can run the same code there and retrieve parameters from a request, whether it has been redirected or not. I've posted in this forum because I believe the problem is with OC4J not with Spring or Toplink. I could be wrong.
    Any suggestions are very welcome.
    Mike

  • EJB 3.0 - problem with persistence unit.

    Hi everybody, I got this problem I would like you to help me.
    I'm doing a proyect with EJB 3.0 using Netbeans 5.5 and Jboss
    The data source is MySQL.
    When I deploy the proyect, the Jboss Log show me this:
    --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
    ObjectName: persistence.units:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,unitName=DecmoCVLAC-ejbPU
    State: FAILED
    Reason: javax.naming.NameNotFoundException: jdbc not bound
    I Depend On:
    jboss.jca:service=ManagedConnectionFactory,name=jdbc/connectionPool
    Depends On Me:
    jboss.j2ee:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,name=NewMessage,service=EJB3
    jboss.j2ee:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,name=PersonaEntityFacade,service=EJB3
    [Please help me, I'm kind of new in EJB]
    [ENTIRE JBOSS LOG]
    10:08:37,375 INFO [TomcatDeployer] undeploy, ctxPath=/DecmoCVLAC-war, warUrl=.../tmp/deploy/tmp16823DecmoCVLAC.ear-contents/DecmoCVLAC-war-exp.war/
    10:08:37,515 INFO [EARDeployer] Undeploying J2EE application, destroy step: file:/C:/jboss-4.0.4.GA/server/default/deploy/DecmoCVLAC.ear
    10:08:37,515 INFO [EARDeployer] Undeployed J2EE application: file:/C:/jboss-4.0.4.GA/server/default/deploy/DecmoCVLAC.ear
    10:08:37,546 INFO [EARDeployer] Init J2EE application: file:/C:/jboss-4.0.4.GA/server/default/deploy/DecmoCVLAC.ear
    10:08:39,281 INFO [Ejb3Deployment] EJB3 deployment time took: 47
    10:08:39,296 INFO [JmxKernelAbstraction] installing MBean: persistence.units:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,unitName=DecmoCVLAC-ejbPU with dependencies:
    10:08:39,296 INFO [JmxKernelAbstraction]      jboss.jca:name=jdbc/connectionPool,service=ManagedConnectionFactory
    10:08:39,312 WARN [ServiceController] Problem starting service persistence.units:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,unitName=DecmoCVLAC-ejbPU
    javax.naming.NameNotFoundException: jdbc not bound
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
    at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
    at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:240)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:99)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy91.start(Unknown Source)
    at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:82)
    at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:626)
    at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:475)
    at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:139)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy36.start(Unknown Source)
    at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:449)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
    at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
    at org.jboss.ws.server.WebServiceDeployer.start(WebServiceDeployer.java:117)
    at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
    at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy37.start(Unknown Source)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:997)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy6.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
    10:08:39,812 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,name=NewMessage,service=EJB3 with dependencies:
    10:08:39,812 INFO [JmxKernelAbstraction]      persistence.units:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,unitName=DecmoCVLAC-ejbPU
    10:08:39,828 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,name=PersonaEntityFacade,service=EJB3 with dependencies:
    10:08:39,828 INFO [JmxKernelAbstraction]      persistence.units:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,unitName=DecmoCVLAC-ejbPU
    10:08:39,859 INFO [EJB3Deployer] Deployed: file:/C:/jboss-4.0.4.GA/server/default/tmp/deploy/tmp16824DecmoCVLAC.ear-contents/DecmoCVLAC-ejb.jar
    10:08:39,859 INFO [TomcatDeployer] deploy, ctxPath=/DecmoCVLAC-war, warUrl=.../tmp/deploy/tmp16824DecmoCVLAC.ear-contents/DecmoCVLAC-war-exp.war/
    10:08:40,046 INFO [EARDeployer] Started J2EE application: file:/C:/jboss-4.0.4.GA/server/default/deploy/DecmoCVLAC.ear
    10:08:40,062 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
    --- MBeans waiting for other MBeans ---
    ObjectName: persistence.units:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,unitName=DecmoCVLAC-ejbPU
    State: FAILED
    Reason: javax.naming.NameNotFoundException: jdbc not bound
    I Depend On:
    jboss.jca:service=ManagedConnectionFactory,name=jdbc/connectionPool
    Depends On Me:
    jboss.j2ee:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,name=NewMessage,service=EJB3
    jboss.j2ee:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,name=PersonaEntityFacade,service=EJB3
    ObjectName: jboss.j2ee:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,name=NewMessage,service=EJB3
    State: NOTYETINSTALLED
    I Depend On:
    persistence.units:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,unitName=DecmoCVLAC-ejbPU
    ObjectName: jboss.j2ee:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,name=PersonaEntityFacade,service=EJB3
    State: NOTYETINSTALLED
    I Depend On:
    persistence.units:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,unitName=DecmoCVLAC-ejbPU
    --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
    ObjectName: persistence.units:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,unitName=DecmoCVLAC-ejbPU
    State: FAILED
    Reason: javax.naming.NameNotFoundException: jdbc not bound
    I Depend On:
    jboss.jca:service=ManagedConnectionFactory,name=jdbc/connectionPool
    Depends On Me:
    jboss.j2ee:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,name=NewMessage,service=EJB3
    jboss.j2ee:ear=DecmoCVLAC.ear,jar=DecmoCVLAC-ejb.jar,name=PersonaEntityFacade,service=EJB3

    Reason: javax.naming.NameNotFoundException: jdbc not bound
    Although i am quite new to this as well i would say that there is a problem with your connection with the database.
    It seems it cannot connect to Mysql.
    have you download the mysql package library and imported it ?
    Also in your deploy folder in you Jboss
    have you altered the jdbc to connect to you database in your dataset ? ( i am not sure about mysql, but postgre reguired this)
    Most probably it would be the same in mysql.
    <connection-url>jdbc:postgresql://127.0.0.1:5432/Dissertation</connection-url>
    Not sure if this is what you reguire, i am new at this my self

  • JDBC, JMS and EJB transactions - possible problem?

    Hello,
              I am using Oracle 9, Weblogic 8.1 SP 4, MyEclipse and
              XDoclet.
              In my current project I have the following piece of code
              in one of my message driven beans (code cited as pseudocode
              without unnecessary details):
              * @ejb.bean name="MyMessageProcessor"
              * display-name="Display name for a MyMessageProcessor"
              * jndi-name="ejb/MyMessageProcessor"
              * description="Bean MyMessageProcessor"
              * destination-type="javax.jms.Queue"
              * transaction-type="Container"
              * acknowledge-mode="Auto-acknowledge"
              * subscription-durability="Durable"
              * generate="false"
              * @ejb.transaction type="Required"
              public class MyMessageProcessor implements MessageDrivenBean, MessageListener {
              public void onMessage(Message msg) {
                   try {
                        //obtaining connections to two different databases via JNDi
                        java.sql.Connection connOne =
                        ((DataSource)ctx.lookup("DataSourceOne")).getConnection();          
                        java.sql.Connection connTwo =
                             ((DataSource)ctx.lookup("DataSourceTwo")).getConnection();
                        // performing some UPDATEs and INSERTs on connOne and connTwo
                        // calling some other methods of this bean
                        //creating the reply JMS message and sending it to another JMS queue
                        Message msgTwo = this.createReplyMessage(msg)
                        this.queueSender.send(msgTwo);
                        //commiting everything
                        this.queueSession.commit();          
                   } catch (Exception ex) {
                   try {
                        if (this.queueSession!=null) this.queueSession.rollback();
                   } catch (JMSException JMSEx) {};     
                   this.context.setRollbackOnly();
              Some days ago (before the final remarks from my client) there used to be only one DataSource configurated on the basis of the
              connection pool with non-XA jdbc driver. Everything worked fine
              including the transactions (if anything wrong happend not only wasn't the replymessage sent, but also no changes were written
              to database and the incomming message was thrown back to the my bean's
              queue).
              When I deployed the second DataSource I was informed by an error message, that only one non-transactional resource may
              participate in a global transaction. When I changed both datasources
              to depend on underlying datasources with transatcional (XA) jdbc drivers, everything stopped working. Even if
              EJB transaction was theoretically successfully rolledbacked, the changed were written to the database
              and the JMS message wasn't resent to the JMS queue.
              So here are my questions:
                   1. How to configure connection pools to work in such situations? What JDBC drivers should I choose?
                   Are there any global server configurations, which may influence this situation?
                   2. Which jdbc drivers should I choose so that the container was able to rollback the database transactions
                   (of course, if necessary)?
                   3. Are there any JMS Queue settings, which would disable the container to send message back to the
                   queue in case of setRollbackOnly()? How should be the Queue configurated?
              As I am new to the topic and the deadline for the project seems to be too close I would be grateful
              for any help.
              This message was sent to EJB list and JDBC list.
              Sincerely yours,
              Marcin Zakidalski

    Hi,
              I found these information extremely useful and helpful.
              The seperate transaction for sending messages was, of course, unintentional. Thanks a lot.
              Anyway, I still have some problems. I have made some changes to the
              code cited in my previous mail. These changes included changing QueueSessions
              to non-transactional. I also set the "Honorate global transactions" to true.
              I am using XA JDBC driver. After setting "Enable local transactions" to false
              (I did it, because I assume that JDBC transactions should be part on the global
              EJB transaction) I got the following error:
              java.sql.SQLException: SQL operations are not allowed with no global transaction by default for XA drivers. If the XA
              driver supports performing SQL operations with no global transaction, explicitly allow it by setting
              "SupportsLocalTransaction" JDBC connection pool property to true. In this case, also remember to complete the local
              transaction before using the connection again for global transaction, else a XAER_OUTSIDE XAException may result. To
              complete a local transaction, you can either set auto commit to true or call Connection.commit() or Connection.rollback().
              I have also inspected the calls of methods of bean inside of onMessage() method just to check, whether
              the transactions are correctly initialized (using the weblogic.transaction.Transaction class).
              My questions are as follows:
              1. Any suggestions how to solve it? I have gone through the google answers on that problem and only
              thing I managed to realize that JDBC must start its own transaction. Is there any way to prohibit it
              from doing that? Can using setAutocommit(true/false) change the situation for better?
              2. How to encourage the JDBC driver to be a part of EJB transaction?
              3. As I have noticed each of ejb method has its own transactions (transactions have different
              Xid). Each method of the bean has "required" transaction attribute. Shouldn't it work in such
              way that if already started transaction exists it is used by the called method?
              4. The DataSources are obtained in my application via JNDI and in the destination environment I will have slight
              impact on the configuration of WebLogic. What is least problematic and most common WebLogic configuration which would
              enable JDBC driver to participate in the EJB transaction? Is it the WebLogic configuration problem or can it be
              solved programmically?
              Currently my module works quite fine when "enable local transactions" for DataSources is set to true, but this way
              I am loosing the ability to perform all actions in one transaction.
              Any suggestions / hints are more than welcomed. This message was posted to jdbc list and ejb list.
              Marcin

  • Sun ejb tutorial compilation problem with sample code

    I have been trying to follow the ejb tutorial off of Sun's web site. However, I get the following problem when I try to compile the sample code.
    prompt>javac Demo.java
    works fine
    Prompt>javac DemoBean.java
    works fine
    Prompt>javac DemoHome.java
    DemoHome.java:23: cannot resolve symbol
    symbol : class Demo
    location: interface ejb.demo.DemoHome
    public Demo create() throws CreateException, RemoteException;
    ^
    1 error
    Prompt>
    Can anyone help me out as I have tried several books which conveniently skip the part about compiling errors.
    I noticed I don't have a CLASSPATH variable and then i created one with just '.' in it and that didn't work. any help would be appreciated as this is driving me crazy. Thanks.

    try to change the order of the exception.
    first RemoteException and then CreateException

  • Adf ejb jpa persistance problem

    Hi everyone,
    I`m a newbie to adf technology.
    I was trying Build a Web Application with JDeveloper 11g Using EJB, JPA, and JavaServer Faces tutorial
    ([http://www.oracle.com/technology/obe/obe11jdev/11/ejb/ejb.html])
    I have a problem when I try to run it.
    It says;
    javax.ejb.EJBException: EJB Exception: ; nested exception is:
    Exception [EclipseLink-4002|http://forums.oracle.com/forums/] (Eclipse Persistence Services - 1.0.1 (Build 20080905)): org.eclipse.persistence.exceptions.DatabaseException
    Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00904: "EMAİL": ge&ccedil;ersiz belirleyici (invalid identifier)
    I thing it`s becouse I use a turkish operating system.
    I tried to change the encoding settings to windows1252 intead of windows 1254 but same problem occures.
    It makes the column EMAIL to EMAİL
    Could you please help me abpout this problem?

    Hi,
    can you print out the value that is received in the session facde to see where the conversion happens?
    Frank

  • Integration with Websphere 5.0 (EJB 2.0) problems

    Hello all,
    Although a bit new to JDO, I have been trying to integrate Kodo 2.4 with
    Websphere 5.0 (using EJB 2.0).
    I have been basically binding a PersistenceManagerFactory into JNDI via
    start-up servlet, however got the exception bellow when I tried to create
    PersistenceManagerFactory (in setSessionContext of the EJB).
    <i>JDOFatalInternalException: Could not perform automatic lookup of EJB
    container's javax.transaction.TransactionManager implementation. Please ensure
    that you are running the application from within an <b>EJB 1.1</b> compliant
    EJB container, and then set the
    com.solarmetric.kodo.ee.ManagedRuntimeProperties property to the appropriate
    value to obtain the TransactionManager.</i>
    The reference to EJB 1.1 actually scared me a bit. Does this imply that
    Kodo (2.4) does not support J2EE 1.3?
    Would you know how to set the
    com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with WSAD
    5.0?
    Thank you,
    Petr

    Petr-
    Is the integration with Websphere 5.0 application server officially
    supported? Has anobody (that you know of) done it successfully yet?Yes, we do have reports of people using Kodo successfully from within
    Websphere. However, it should be noted that it is not as rigorously
    tested internally at SolarMetric as some other application servers (E.g.,
    JBoss and WebLogic). In short, integration is known to work, but it
    might be a little more rough around the edges than for other application
    servers (as shown in our misspelling of Websphere's TransactionManager
    implementation name).
    How do I tell Kodo to use existing Datasource managed by app server?You can have Kodo use a named DataSource by specifying the
    javax.jdo.option.ConnectionFactoryName property (see
    http://www.solarmetric.com/docs/2.4.0/docs/manual.html#javax.jdo.option.ConnectionFactoryName).
    This is often more appropriate for applications server usage, since it
    allows you to configure pooling and other information from within the
    application server's centralized configuration.
    javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
    javax.jdo.option.ConnectionURL=jdbc:db2:snetWhat kind of driver is COM.ibm.db2.jdbc.app.DB2Driver? The DB2
    configuration we use for testing with IBM's drivers is:
    javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.net.DB2Driver
    javax.jdo.option.ConnectionURL=jdbc:db2://SERVER_NAME/DATABASE_NAME
    They shouldn't behave differently (I am guessing that the app driver is
    a type 2 driver or something), but it might be worth a shot to try using
    the net driver. If this fixes the problem, please let us know, because
    it will indicate that Kodo has a deficiency with one of IBM's drivers
    that we should look into resolving.
    Since I have been trying to integrate with App server, this is the
    initialization code that I use to bind PersistenceManagerFactory to JNDI.
    You may find some funny stuff there.The binding code looks fine, and you are obviously able to retrive the
    PM and start persistence operations. Note that you should also be able
    to deploy Kodo as a Resource Adapter (which allows Kodo configuration
    through the centralized Websphere configuration interface). However, I
    doubt this is part of the issue.
    So, in short, I recommend trying the following things:
    1. Using the ConnectionFactoryName to use the DataSource defined for the
    appserver, on the off chance this will fix it.
    2. Using the net driver instead of the app driver.
    3. Seeing if it will work with javax.jdo.option.Optimistic set to false
    If none of these work, please let us know, and we will continue to
    investigate other possible solutions.
    In article <[email protected]>, Petr Bulanek wrote:
    Hello Marc,
    Very good guess. Pretty much the same code worked well without App server.
    In that case, there obviously was no magic related to
    TransactionManagerFactory initialization (see bellow).
    Is the integration with Websphere 5.0 application server officially
    supported? Has anobody (that you know of) done it successfully yet?
    How do I tell Kodo to use existing Datasource managed by app server?
    Here is the basic configuration (URL, class, etc):
    javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
    javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
    javax.jdo.option.ConnectionURL=jdbc:db2:snet
    javax.jdo.option.Optimistic=true
    javax.jdo.option.RetainValues=true
    javax.jdo.option.NontransactionalRead=true
    We use DB2 Version 7.2/Version 7.1 FixPak 3 for Windows, in case it helps.
    Since I have been trying to integrate with App server, this is the
    initialization code that I use to bind PersistenceManagerFactory to JNDI.
    You may find some funny stuff there.
    The new EESimpleConfiguration(true) construct seems to (by default) read
    the kodo.properties file that is part of the project.
    EEConfiguration conf = new EESimpleConfiguration(true);
    conf.setManagedRuntimeProperties(\"TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\");
    conf.setManagedRuntimeClass(\"com.solarmetric.kodo.ee.InvocationManagedRuntime\");
    EEPersistenceManagerFactory pmf =
                        new EEPersistenceManagerFactory(conf);
    InitialContext ic = new InitialContext();
    ic.rebind(\"KodoPMF\", pmf);
    Thank you,
    Petr
    Marc Prud\'hommeaux wrote:
    Petr-
    It looks like DB2 doesn\'t like our attempt to close the connection
    without a rollback or commit. This is odd, since we have never
    seen this happen in our stand-alone DB2 tests. Can you let us know
    the connection details (driver, connectionURL, etc)?
    In the meantime, one possible workaround may be to turn off
    optimistic transactions (since this will cause the PM to
    only use a single Connection); can you try to specify:
    javax.jdo.option.Optimistic=false
    Also, have you tried to run this code in a non-managed environment
    (e.g., outside the application server)? I would be interested
    to know if it is related to running within an appserver.
    In article <[email protected]>, Petr Bulanek wrote:
    Hi Abe,
    Thank you for a speedo reply. You guys really are on the ball!!!
    As you suggested, the
    \\\'com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\\\'
    did the job (for others, please note that the proper package name should
    contain \\\'jts.jta\\\', not \\\'jts.jts\\\').
    Unfortunately, I got another problem. When running a method containing
    query (code bellow),
    I get SQLException complaining about \\\'Invalid transaction state\\\'.
    The method that executes the query is a stateless transactional Session
    bean.
    Thank you for your help,
    Petr
    --------------------------- DB2 - transaction state description
    CLI0116E Invalid transaction state.
    Explanation: There was a transaction in progress when SQLDisconnect was
    called.
    User Response: Call SQLTransact before calling SQLDisconnect.
    --------------------------- Exception ------------------------------------
    [2/01/03 16:34:19:050 EST] 563ddb8a SQL I
    com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
    D:118283149 ] preparing statement <369367952>: SELECT DISTINCT
    PARENTX.JDOCLASSX FROM PARENTX
    [2/01/03 16:34:19:050 EST] 563ddb8a SQL I
    com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
    D:118283149 ] executing statement <369367952>: [reused=1;params={}]
    [2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
    com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
    D:118283149 ] close:
    com.solarmetric.datasource.PoolConnection@14079b90[[requests=6;size=6;max=70;hits=0;created=6;redundant=0;overflow=0;new=6;leaked=0;unavailable=0]]
    [2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
    com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
    D:118283149 ] close connection
    [2/01/03 16:34:19:061 EST] 563ddb8a JDBC W
    com.solarmetric.kodo.impl.jdbc.JDBC [ C:null; T:1446894474; D:118283149 ]
    exception when closing connection
    [2/01/03 16:34:19:541 EST] 563ddb8a JDBC W
    com.solarmetric.kodo.impl.jdbc.JDBC TRAS0014I: The following exception
    was logged COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0116E
    Invalid transaction state. SQLSTATE=25000
    atcom.solarmetric.datasource.ConnectionWrapper.close(ConnectionWrapper.java:243)
    atcom.solarmetric.datasource.DataSourceImpl$AbstractPool.close(DataSourceImpl.java:690)
    atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:373)
    atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:347)
    at com.solarmetric.datasource.PoolConnection.close(PoolConnection.java:70)
    atcom.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:885)
    atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java:654)
    atcom.solarmetric.kodo.impl.jdbc.ormapping.SubclassProviderImpl.getSubclasses(SubclassProviderImpl.java:274)
    atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.addSubclassConditions(ClassMapping.java:1239)
    atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.selectPrimaryMappings(ClassMapping.java:1218)
    atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.executeQuery(JDBCStoreManager.java:717)
    atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCQuery.executeQuery(JDBCQuery.java:92)
    at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:792)
    atcom.solarmetric.kodo.query.QueryImpl.executeWithArray(QueryImpl.java:668)
    at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:609)
    at com.testkodo.ejb.ControllerBean.observeHumans(ControllerBean.java:66)
    --------------------------- Failing code sample
    try {
                   PersistenceManager pm = factory.getPersistenceManager();
                   Extent ex = pm.getExtent(Parent.class, false);
                   Query q = pm.newQuery(ex, \\\"name==parName\\\");
                   q.declareParameters(\\\"String parName\\\");
                   Collection col = (Collection) q.execute(\\\"James\\\");
                   Iterator iter = col.iterator();
                   Parent pp;
                   Collection ch;
                   while (iter.hasNext()) {
                        pp = (Parent) iter.next();
                        System.out.println(pp);
                        ch = pp.getChildren();
                        Iterator it= ch.iterator();
                        while (it.hasNext()) {
                             System.out.println(it.next());
                   q.closeAll();
                   pm.close();
              } catch (Exception e) {
                   System.out.println(e);
                   throw new EJBException(e);
    Abe White wrote:
    The reference to EJB 1.1 actually scared me a bit. Does this imply that
    Kodo (2.4) does not support J2EE 1.3?
    EJB 2.0 is also supported. Sorry for the confusing error message.
    Would you know how to set the
    com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with
    WSAD
    5.0?
    Try these settings:
    com.solarmetric.kodo.ee.ManagedRuntimeClass=\\\\
         com.solarmetric.kodo.ee.InvocationManagedRuntime
    com.solarmetric.kodo.ee.ManagedRuntimeProperties=\\\\
         TransactionManagerMethod=\\\\
         com.ibm.ejs.jts.jts.TransactionManagerFactory.getTransactionManager
    Marc Prud\'hommeaux [email protected]
    SolarMetric Inc. http://www.solarmetric.com

  • EJB 3 reference problem

    Hello all.
    I use glassfish b48.
    I need two classes with unidirectional ManyToOne relation:
    Pupil -> Grade
    Pupil.java:
    @Entity
    public class Pupil extends Person {
        @ManyToOne
        private Grade grade;
    }Person.java:
    @Entity
    public class Person extends VersionControl {
    ...VersionControl.java:
    @Entity
    @Inheritance(strategy=InheritanceType.JOINED)
    public class VersionControl implements Serializable {
        @Id
        @GeneratedValue(strategy = GenerationType.AUTO) 
        private Long id;
        ...Grade.java:
    @Entity
    public class Grade extends VersionControl {
    ...When i change Pupil-instance grade attribute from 'A' to 'B' grade attribute in pupil instance, database updates successfully, but grade attribute of Pupil instance contents Grade-class instance with all NULL fields, and
    em.createQuery("select o from Grade o where order by o.name").getResultList();returns Collection with all Grade objects, but on the 'B-object-place' i see object with all fields = null.
    i.e.
    id       name
    "1"        "A"
    "3"        "C"I tried to run on various platforms and glassfish versions, on JavaDB and PostgreSQL database, various CascadeType's - same result.
    When i redeploy my application(or restart server;-)) all is ok.
    If i create new Grade object and use it for setting to Pupil attribute a don't see this problem.
    But if i use "old" Grade object createed before last deploying of application this problem occur.
    Where is my problem?

    The issue is that the Local EJB view was not intended to be accessible across application boundaries. The Local view
    requires pass-by-reference semantics, which implies that both the caller and callee are using the same classloader.
    Some products support cross-application Local EJB access but it's not portable.
    One of the related issues is that the requirement for packaging ejb's in their own ejb-jar is too cumbersome. We're fixing this
    in EJB 3.1 so that EJB components can be packaged directly in a .war. See my blog posting here : http://blogs.sun.com/kensaks/entry/simplified_ejb_component_packaging

  • Weblogic 10 +APPC+EJB 2.0 problem

    Hi,
    We are upgrading the weblogic 8.1 to weblogic 10. We are using the appc option to build over ejb modules, while validatign the ejb discriptor we are running into problem.
    Environment :
    Operating system : Windows
    Java : 1.5
    Javaee : 5
    Weblogic : 10
    EJB : 2.0
    ===================================================
    [java] <Aug 8, 2007 3:05:13 PM PDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\EclipseProjects\Swell10\j2ee\build\weblogic\deploy\ejb\qss-ejb-standard.jar/META-INF/ejb-jar.xml of module qss-ejb-standard.jar. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    [java] at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
    [java] at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
    [java] at weblogic.appc.main(appc.java:14)
    [java] Caused by: com.bea.xml.XmlException: java.lang.IllegalArgumentException: remoteAccessManagerDaoClass</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>com.questra.a2b.remoteaccessmanager.bizcomp.dao.RemoteAccessManagerDaoSql</env-entry-value> </env-entry> is not a legal value for EnvEntryType. The value must be one of the following: [java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Boolean, java.lang.Character]
    [java] at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    [java] at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:158)
    [java] at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:130)
    [java] at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
    [java] ... 33 more
    [java] Caused by: java.lang.IllegalArgumentException: remoteAccessManagerDaoClass</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>com.questra.a2b.remoteaccessmanager.bizcomp.dao.RemoteAccessManagerDaoSql</env-entry-value> </env-entry> is not a legal value for EnvEntryType. The value must be one of the following: [java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Boolean, java.lang.Character]
    [java] at weblogic.descriptor.beangen.LegalChecks.checkInEnum(LegalChecks.java:29)
    [java] ... 55 more
    [java] .>
    [java] at weblogic.appc.main(appc.java:14)
    [java] Caused by: com.bea.xml.XmlException: java.lang.IllegalArgumentException: remoteAccessManagerDaoClass</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>com.questra.a2b.remoteaccessmanager.bizcomp.dao.RemoteAccessManagerDaoSql</env-entry-value> </env-entry> is not a legal value for EnvEntryType. The value must be one of the following: [java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Boolean, java.lang.Character]
    [java] at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:54)
    [java] ... 33 more
    [java] Caused by: java.lang.IllegalArgumentException: remoteAccessManagerDaoClass</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>com.questra.a2b.remoteaccessmanager.bizcomp.dao.RemoteAccessManagerDaoSql</env-entry-value> </env-entry> is not a legal value for EnvEntryType. The value must be one of the following: [java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Boolean, java.lang.Character]
    [java] ... 55 more
    [java] Java Result: 1
    ======================================================
    take a look at the ejb-jar.xml also
    <?xml version="1.0"?>
    <!-- edited with XMLSPY v5 rel. 4 U (http://www.xmlspy.com) by Dimitrios Psarros (Questra Corporation) -->
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar>
    <enterprise-beans>
    <!-- =============================================== -->
    <!-- RemoteAccessManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.RemoteAccessManager</ejb-name>
    <home>com.questra.a2b.remoteaccessmanager.bizcomp.ejb.IRemoteAccessManagerRemoteHome</home>
    <remote>com.questra.a2b.remoteaccessmanager.bizcomp.ejb.IRemoteAccessManagerRemote</remote>
    <ejb-class>com.questra.a2b.remoteaccessmanager.bizcomp.ejb.session.RemoteAccessManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
         <env-entry-name>remoteAccessManagerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.remoteaccessmanager.bizcomp.dao.RemoteAccessManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- DisconnectedAccessManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.DisconnectedAccessManager</ejb-name>
    <home>com.questra.a2b.disconnectedaccessmanager.bizcomp.ejb.IDisconnectedAccessManagerRemoteHome</home>
    <remote>com.questra.a2b.disconnectedaccessmanager.bizcomp.ejb.IDisconnectedAccessManagerRemote</remote>
    <ejb-class>com.questra.a2b.disconnectedaccessmanager.bizcomp.ejb.session.DisconnectedAccessManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>disconnectedaccessmanagerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.disconnectedaccessmanager.bizcomp.dao.DisconnectedAccessManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- TotalAccess -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.TotalAccess</ejb-name>
    <home>com.questra.a2b.totalaccess.bizcomp.ejb.ITotalAccessRemoteHome</home>
    <remote>com.questra.a2b.totalaccess.bizcomp.ejb.ITotalAccessRemote</remote>
    <ejb-class>com.questra.a2b.totalaccess.bizcomp.ejb.session.TotalAccessSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>totalAccessDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.totalaccess.bizcomp.dao.TotalAccessDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- UsageJobManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.UsageJobManager</ejb-name>
    <home>com.questra.a2b.usagejobmanager.bizcomp.ejb.IUsageJobManagerRemoteHome</home>
    <remote>com.questra.a2b.usagejobmanager.bizcomp.ejb.IUsageJobManagerRemote</remote>
    <ejb-class>com.questra.a2b.usagejobmanager.bizcomp.ejb.session.UsageJobManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>usageJobManagerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.usagejobmanager.bizcomp.dao.UsageJobManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- ACM -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.ACM</ejb-name>
    <home>com.questra.a2b.acm.bizcomp.ejb.IACMRemoteHome</home>
    <remote>com.questra.a2b.acm.bizcomp.ejb.IACMRemote</remote>
    <ejb-class>com.questra.a2b.acm.bizcomp.ejb.session.ACMSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>acmDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.acm.bizcomp.dao.ACMDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- MonitorManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.MonitorManager</ejb-name>
    <home>com.questra.a2b.monitormanager.bizcomp.ejb.IMonitorManagerRemoteHome</home>
    <remote>com.questra.a2b.monitormanager.bizcomp.ejb.IMonitorManagerRemote</remote>
    <ejb-class>com.questra.a2b.monitormanager.bizcomp.ejb.session.MonitorManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>monitorManagerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.monitormanager.bizcomp.dao.MonitorManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- UsageMeterManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.UsageMeterManager</ejb-name>
    <home>com.questra.a2b.usagemetermanager.bizcomp.ejb.IUsageMeterManagerRemoteHome</home>
    <remote>com.questra.a2b.usagemetermanager.bizcomp.ejb.IUsageMeterManagerRemote</remote>
    <ejb-class>com.questra.a2b.usagemetermanager.bizcomp.ejb.session.UsageMeterManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>usageMeterManagerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.usagemetermanager.bizcomp.dao.UsageMeterManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- DiagnosticsManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.DiagnosticsManager</ejb-name>
    <home>com.questra.a2b.diagnosticsmanager.bizcomp.ejb.IDiagnosticsManagerRemoteHome</home>
    <remote>com.questra.a2b.diagnosticsmanager.bizcomp.ejb.IDiagnosticsManagerRemote</remote>
    <ejb-class>com.questra.a2b.diagnosticsmanager.bizcomp.ejb.session.DiagnosticsManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>diagnosticsManagerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.diagnosticsmanager.bizcomp.dao.DiagnosticsManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- ProcedureManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.ProcedureManager</ejb-name>
    <home>com.questra.a2b.proceduremanager.bizcomp.ejb.IProcedureManagerRemoteHome</home>
    <remote>com.questra.a2b.proceduremanager.bizcomp.ejb.IProcedureManagerRemote</remote>
    <ejb-class>com.questra.a2b.proceduremanager.bizcomp.ejb.session.ProcedureManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>procedureManagerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.proceduremanager.bizcomp.dao.ProcedureManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- DataWarehouseProcedureManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.DataWarehouseProcedureManager</ejb-name>
    <home>com.questra.a2b.proceduremanager.bizcomp.ejb.IProcedureManagerRemoteHome</home>
    <remote>com.questra.a2b.proceduremanager.bizcomp.ejb.IProcedureManagerRemote</remote>
    <ejb-class>com.questra.a2b.proceduremanager.bizcomp.ejb.session.ProcedureManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>procedureManagerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.proceduremanager.bizcomp.dao.ProcedureManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- DataWarehouseManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.DataWarehouseManager</ejb-name>
    <home>com.questra.a2b.datawarehousemanager.bizcomp.ejb.IDataWarehouseManagerRemoteHome</home>
    <remote>com.questra.a2b.datawarehousemanager.bizcomp.ejb.IDataWarehouseManagerRemote</remote>
    <ejb-class>com.questra.a2b.datawarehousemanager.bizcomp.ejb.session.DataWarehouseManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>dataWarehouseManagerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.datawarehousemanager.bizcomp.dao.DataWarehouseManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataWarehouseDataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- Scheduler -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.Scheduler</ejb-name>
    <home>com.questra.a2b.scheduler.bizcomp.ejb.ISchedulerRemoteHome</home>
    <remote>com.questra.a2b.scheduler.bizcomp.ejb.ISchedulerRemote</remote>
    <ejb-class>com.questra.a2b.scheduler.bizcomp.ejb.session.SchedulerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>schedulerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.scheduler.bizcomp.dao.SchedulerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- SystemEventLogger -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.SystemEventLogger</ejb-name>
    <home>com.questra.a2b.common.bizcomp.log.ejb.ISystemEventLoggerRemoteHome</home>
    <remote>com.questra.a2b.common.bizcomp.log.ejb.ISystemEventLoggerRemote</remote>
    <ejb-class>com.questra.a2b.common.bizcomp.log.ejb.session.SystemEventLoggerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>systemEventDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.common.bizcomp.dao.SystemEventDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- LicenseManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.LicenseManager</ejb-name>
    <home>com.questra.a2b.common.bizcomp.license.ejb.ILicenseManagerRemoteHome</home>
    <remote>com.questra.a2b.common.bizcomp.license.ejb.ILicenseManagerRemote</remote>
    <ejb-class>com.questra.a2b.common.bizcomp.license.ejb.session.LicenseManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- Security -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.Security</ejb-name>
    <home>com.questra.a2b.security.bizcomp.ejb.ISecurityRemoteHome</home>
    <remote>com.questra.a2b.security.bizcomp.ejb.ISecurityRemote</remote>
    <ejb-class>com.questra.a2b.security.bizcomp.ejb.session.SecuritySessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>tokenTimeout</env-entry-name>
    <env-entry-type>java.lang.Long</env-entry-type>
    <env-entry-value>600000</env-entry-value>
    </env-entry>
    <env-entry>
    <env-entry-name>securityDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.security.bizcomp.dao.SecurityDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- DocumentManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.DocumentManager</ejb-name>
    <home>com.questra.a2b.documentmanager.bizcomp.ejb.IDocumentManagerRemoteHome</home>
    <remote>com.questra.a2b.documentmanager.bizcomp.ejb.IDocumentManagerRemote</remote>
    <ejb-class>com.questra.a2b.documentmanager.bizcomp.ejb.session.DocumentManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>documentmanagerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.documentmanager.bizcomp.dao.DocumentManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- UiManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.UiManager</ejb-name>
    <home>com.questra.a2b.ui.bizcomp.ejb.IUiManagerRemoteHome</home>
    <remote>com.questra.a2b.ui.bizcomp.ejb.IUiManagerRemote</remote>
    <ejb-class>com.questra.a2b.ui.bizcomp.ejb.session.UiManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>uimanagerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.ui.bizcomp.dao.UiManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- FileRepositoryManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.FileRepositoryManager </ejb-name>
    <home>com.questra.a2b.filerepositorymanager.bizcomp.ejb.IFileRepositoryManagerRemoteHome</home>
    <remote>com.questra.a2b.filerepositorymanager.bizcomp.ejb.IFileRepositoryManagerRemote</remote>
    <ejb-class>com.questra.a2b.filerepositorymanager.bizcomp.ejb.session.FileRepositoryManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>daoImplClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.filerepositorymanager.bizcomp.dao.FileRepositoryManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- Registration -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.Registration</ejb-name>
    <home>com.questra.a2b.registration.bizcomp.ejb.IRegistrationRemoteHome</home>
    <remote>com.questra.a2b.registration.bizcomp.ejb.IRegistrationRemote</remote>
    <ejb-class>com.questra.a2b.registration.bizcomp.ejb.session.RegistrationSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>registrationDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.registration.bizcomp.dao.RegistrationDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- Alert -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.Alert</ejb-name>
    <home>com.questra.a2b.alert.bizcomp.ejb.IAlertRemoteHome</home>
    <remote>com.questra.a2b.alert.bizcomp.ejb.IAlertRemote</remote>
    <ejb-class>com.questra.a2b.alert.bizcomp.ejb.session.AlertSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>alertDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.alert.bizcomp.dao.AlertDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- SoftwareDirector -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.SoftwareDirector</ejb-name>
    <home>com.questra.a2b.softwaredirector.bizcomp.ejb.ISoftwareDirectorRemoteHome</home>
    <remote>com.questra.a2b.softwaredirector.bizcomp.ejb.ISoftwareDirectorRemote</remote>
    <ejb-class>com.questra.a2b.softwaredirector.bizcomp.ejb.session.SoftwareDirectorSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>softwareDirectorDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.softwaredirector.bizcomp.dao.SoftwareDirectorDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- ReportsManager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.ReportsManager</ejb-name>
    <home>com.questra.a2b.reports.bizcomp.ejb.IReportsManagerRemoteHome</home>
    <remote>com.questra.a2b.reports.bizcomp.ejb.IReportsManagerRemote</remote>
    <ejb-class>com.questra.a2b.reports.bizcomp.ejb.session.ReportsManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    <!-- =============================================== -->
    <!-- Image Manager -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.ImageManager</ejb-name>
    <home>com.questra.a2b.imagemanager.bizcomp.ejb.IImageManagerRemoteHome</home>
    <remote>com.questra.a2b.imagemanager.bizcomp.ejb.IImageManagerRemote</remote>
    <ejb-class>com.questra.a2b.imagemanager.bizcomp.ejb.session.ImageManagerSessionEjb</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <env-entry>
    <env-entry-name>imagemanagerDaoClass</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>com.questra.a2b.imagemanager.bizcomp.dao.ImageManagerDaoSql</env-entry-value>
    </env-entry>
    <resource-ref>
    <res-ref-name>jdbc/DataSource</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
         <!-- =============================================== -->
    <!-- DynamicGroups -->
    <!-- =============================================== -->
    <session>
    <ejb-name>a2b.DynamicGroups</ejb-name>
    <home>com.questra.a2b.dynamicgroups.bizcomp.ejb.IDynamicGroupsRemoteHome</home>
    <remote>com.questra.a2b.dynamicgroups.bizcomp.ejb.IDynamicGroupsRemote</remote>
    <ejb-class>c

    I am also getting the same error. Did any one has any resolution for this issue.
    Error:
    Caused by: com.bea.xml.XmlException: java.lang.IllegalArgumentException: <?xml version="1.0" encoding="UTF-8"?> <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" version="3.0"> <enterprise-beans> <session> <ejb-name>ExternalOrderService</ejb-name> <home>com.att.absvic.webservices.external.ExternalOrderHome</home> <remote>com.att.absvic.webservices.external.ExternalOrderEJB</remote> <ejb-class>com.att.absvic.webservices.external.ExternalOrderBean</ejb-class> <session-type>Stateless</session-type> <transaction-type>Container</transaction-type> </session> </enterprise-beans> <assembly-descriptor> <container-transaction> <method> <ejb-name>ExternalOrderService</ejb-name> <method-name>*</method-name> </method> <trans-attribute>Required</trans-attribute> </container-transaction> </assembly-descriptor> </ejb-jar> is not a legal value for SessionType. The value must be one of the following: [Stateful, Stateless]
    Thanks,
    Srinivas

  • URGENT:Testing deployed OAS EJB Aplication (JNDI Problem)

    Please I need urgently help on this subject matter:
    Environment:
    OAS 4.0.8.2a on NT 4.5 SP5
    Jdeveloper 3.1
    Oracle 8R2
    After succesfull deployment of BC4J aplication on OAS I want simply test it. When I click to test on the appModule on the tree, the dialog asking the connection information appears..I choose OAS option from the drop down box.
    The error message I get is:
    "apps/ejb/ClientesProjectOAS/pkgClientes/PkgClientesModule is not the name of a registered component"
    I have tried with other variants too taking into account what OAS Administration shows..but no luck!
    Now, WHAT SHOULD BE PUT TO THE "JNDI PATH" and "CLIENT JAR PATH" options. This is the most confusing point to me and there are practically no valid/good information on online help.
    Thanx.
    Best regards,
    Ari Supperi
    [email protected]

    I have (almost) the same problem. Any idea? My weak english must be the reason, but I cannot find out what to enter into the JNDI and the Client jar path during testing my OAS deployed AppModule.
    Thx,
    Tib
    null

  • JWS - EJB JNDI Lookup problem

    Hi,
    I have a client Java application accessing a session EJB in a remote JBoss J2EE server. I'm using JWS 1.2 to deploy my application but when I do a JNDI lookup to get access the the remote's object home interface I get this error:
    "Need to specify class name in environment or system property, or as an applet parameter, or in an application resorce file: java.naming.factory.initial"
    All the jar files are signed and the JNPL file contains <all-permissions/>. This is the code that triggers the exception
    jndiContext = new InitialContext();
    homeRMIReference = jndiContext.lookup(C_SERVICE_NAME);
    Any help would be appreciated.
    Thanks in advance,
    Rafael

    Hi,
    I've finally found the origin of the problem.
    1. JNDI uses a minimum set of properties during initialization phase:
    java.naming.factory.initial
    java.naming.factory.url.pkgs
    java.naming.provider.url
    Therefore these properties must be set in the <resource> topic of the JNLP file. The value of these properties is defined in the jndi.properties file that you can find in jbossjmx.ant.jar (within the jboss/client directory)
    2. You have to add the JBoss files to your bundle. For doing so I've unjared all the .jar files within the jboss/client directory; afterwards I have jared them in a single file "jboss.jar" and I've signed the file. I've added jboss.jar to the <resource> tag within the JNLP file (Note that I've added all the jboss files just to do quick check but usually you will have to add only those files you need (it doesn't make sense to deploy all JBoss files in each client application)
    I hope this helps,
    Rafael

  • EJB 2.0 problem

    Hi,
    I�m using WSAD to develop a session bean that interact�s with a CMP bean, but when i try to create a new ejbCreate() method, with any parameter(Ex:Integer or anyone), the WSAD comes with an error that dosen�t make sense:
    "This method must be the create() method(EJB 2.0: 7.8,7.10.6)"
    I have a method ejbCreate() with no parameters, i don�t use it but ok, but the problem is that it compiles but when i try t execute my create() it throws a MarshalException.
    It�s a bug that comes with WebSphere???
    I read the specs of EJB 2.0 it told me nothing that i haven�t tried.
    please help.
    cheers

    change deployment descriptor file like this
    <session-type>Stateful</session-type>
    then hope your problem will solve.

  • Deployment Plan / weblogic-ejb-jar.xml:  Problem

    Hello,
    I am trying to use a deployment plan to override the principal name in the weblogic-ejb-jar.xml.
    The deployment-plan looks like this (showing only the important sections)
    <variable-definition>
    <variable>
    <name>SecurityRoleAssignment_ejbRole_PrincipalNames_1</name>
    <value>MY PRINCIPAL 1</value>
    </variable>
    </variable-definition>
    <variable-assignment>
    <name>SecurityRoleAssignment_ejbRole_PrincipalNames_1</name>
    <xpath>/weblogic-ejb-jar/security-role-assignment/[role-name="View-Role"]/externally-defined</xpath>
    <operation>replace</operation>
    </variable-assignment>
    The security-role assignment in the weblogic-ejb-jar.xml looks like this:
    <security-role-assignment>
    <role-name>View-Role</role-name>
         <externally-defined/>
    </security-role-assignment>
    I 've tried to override the element-value of <externally-defined> (a valid tag in the weblogic-ejb-jar.xml ) with help of a deployment-plan.
    When trying to deploy my application (which is organised in the directory-structure: inst_dir/APP inst_dir/PLAN
    the following error occurs:
    VALIDATION PROBLEMS WERE FOUND problem: cvc-complex-type.2.4a: Expected element 'principal-name@http://www.bea.com/ns/weblogic/10.0' instead of 'externally-defined@http://www.bea.com/ns/weblogic/10.0' here in element security-role-assignment@http://www.bea.com/ns/weblogic/10.0:
    This has surprised me, as externally-defined is (according to the documentation) a valid tag.
    I have tried to replace <externally-defined> with an empty <principal-name> tag (which works fine when deploying the application), but causes a security exception, when trying to use the EJB.
    Has anybody an idea if there is a workaround for this problem?
    IMHO the Validatio Problem is not justified at this place then why should an otherwise valid weblogic-ejb-jar.xml (when not using a deployment-plan) suddenly become invalid when a deployment plan is used?
    Thanx a lot in advance!
    Edited by: user10672779 on 02.12.2008 04:09

    Hi again,
    I tried it with the weblogic 10 Namespace Declaration but got then this error:
    failed to load java type corresponding to e=weblogic-ejb-jar@http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd
    and following Exception:
    <02.12.2008 20.00 Uhr CET> <Error> <J2EE> <BEA-160197> <Unable to load descriptor D:\exportapps\tb.ear\app\tb_flowcontrol.jar/META-INF/weblogic-ejb-jar.xml of module tb_flowcontrol.jar. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:774)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745)
    Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=weblogic-ejb-jar@http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd
    at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:329)
    at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:296)
    at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:306)
    at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:287)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:153)
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
    Searching the net couldn't supply me with another answer as to use the 90 Namespace Declaration again...
    I think I forgot to mention I am using an exploded directory.
    This all seems very strange.
    cheers.

  • A J2EE problem from an International Bank EJB-RDB remapping problem

    Background Information:
    We are going to deploy a J2EE project with DB2 V7.1 as the backend database server. However, the project is developed using WSED and initially assumed DB2 V.8 will be used as the database server. The inconsistency of DB2 version have us to make some amendments on the project. To simplify the scenario, what we do is to truncate the table/column name with length >18 to 18 defined in all .tblxmi, ... for EJB-RDB mapping. After we rebuild the project and deploy it in WAS 5.1, the following error occured,
    CNTR0020E: Non-application exception occurred while processing method "populateSystemCache" on bean "BeanId(eFOSt
    0#eFOS-Session.jar#SystemService, null)". Exception data: javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com
    .ibm.db2.jcc.DB2SQLException: DB2JDBCCursor Received Error in Method prepare:SQLCODE==> -107 SQLSTATE ==> 42622 Error Tokens ==> <<D
    B2 7.1 SQLJ/JDBC>> "ACTUAL_MONTH_END_DATE" 18
    com.ibm.db2.jcc.DB2SQLException: DB2JDBCCursor Received Error in Method prepare:SQLCODE==> -107 SQLSTATE ==> 42622 Error Tokens ==>
    <<DB2 7.1 SQLJ/JDBC>> "ACTUAL_MONTH_END_DATE" 18
    at COM.ibm.db2os390.sqlj.jdbc.DB2SQLJJDBCCursor.setError(DB2SQLJJDBCCursor.java:1232)
    at COM.ibm.db2os390.sqlj.jdbc.DB2SQLJJDBCSection.prepare(DB2SQLJJDBCSection.java:767)
    at COM.ibm.db2os390.sqlj.jdbc.DB2SQLJConnection.prepareStatement(DB2SQLJConnection.java:1470)
    at COM.ibm.db2os390.sqlj.jdbc.DB2SQLJConnection.prepareStatement(DB2SQLJConnection.java:1580)
    We are sure that we have made all the necessary truncations for the table/column. We discovered that some of the .class file, e.g. SystemBeanFunctionSet_71684028.class, was generated under the directory ../websphere_deploy/DB2UDBOS390_V71_1 after we rebuild the project. Many column names with length >18 were found there, such as ACTUAL_MONTH_END_DATE.
    PreparedStatement pstmt = null;
    try
    pstmt = prepareStatement(connection, "INSERT INTO FAK.SYSTEM (SYSTEM_CODE, ACTIVE_FLAG, SYSTEM_NAME, BUSINESS_DATE, LAST_BUSINESS_DATE, NEXT_BUSINESS_DATE, REGION_CODE, MONTH_FLAG, ACTUAL_MONTH_END_DATE, LOCAL_COMPANY_CODE, LOCAL_BRANCH_CODE, LOCAL_COUNTRY_CODE, LOCAL_CURRENCY_CODE, FUNDING_CURRENCY_CODE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)");
    String tempString = (String)inputRecord.get(0);
    May I know what those .class file (with number prefix in the file name)for and how can we solve the problem?
    Thanks a lot

    Put it simply, is there any method using WSED to
    deploy the project using DB2 V.7.2 if the project is
    assembled using DB2 V8 and no java source is
    available ???If you are not making use of any functions specific to DB2 V8 how does it matter for you? The difference only lies in the DataSource configuration or something like that but certainly not on your java code(If you have not done anything specific to V8).Your problem sounds me like as suggested you have an extra/lesser parameters(?) or checkout the parameter that you are passing in is not overflowing any columns.

  • [Jeveloper + EJB client - EJB on OAS] Problem connecting

    I having problems getting a simple client from within JDeveloper 3.0(Code snippet - OAS/EJB Client) talking to a simple EJB on OAS 4.0.8.
    I have deployed OK (red flag against status?) but when I run the client using port - 5512(ORB port)I get the message below
    Anybody any ideas?
    Creating an initial context
    Looking for the EJB published as 'MyOASApp/MyEJB'
    Naming exception occurred!
    Cause: This may be an unknown URL, or some classes required by the EJB are missing from your classpath, or your OAS host is short of resources
    Suggestion: Check the components of the URL, and make sure your project includes a library containing the EJB .jar files generated by the deployment utility.
    [Root exception is java.net.UnknownServiceException: no content-type]javax.naming.NamingException: Failure to access http://hfxcap4:5512/ows-bin/rmproxy.ior; listener inaccessible or configured wrongly
    at oracle.oas.jndi.oas.SiteResolver.getIOR(Compiled Code)
    at oracle.oas.jndi.oas.SiteResolver.resolveListenerURL(Compiled Code)
    at oracle.oas.jndi.oas.SiteResolver.resolveSiteContact(Compiled Code)
    at oracle.oas.jndi.oas.SiteResolver.resolveSiteContact(Compiled Code)
    at oracle.oas.jndi.oas.SiteResolver.resolveSiteObject(Compiled Code)
    at oracle.oas.jndi.oas.BeanInitialContext.resolve(Compiled Code)
    at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
    at oracle.oas.jndi.oas.BeanInitialContext.lookup(Compiled Code)
    at oracle.oas.jndi.oas.WrapperContext.lookup(Compiled Code)
    at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
    at javax.naming.InitialContext.lookup(Compiled Code)
    at package1.MyOASAppClient.main(Compiled Code)
    **************

    HI, I have the same problem that you had, maybe did you manage through ?? Thanks for all the help you could bring me.
    Nico
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by pFrooney:
    Back Again ...
    I have tried all ao the above
    now using this code below but it fails on the lookup with the error message below:
    ..created library with client stub, using 1.1.8, moved OASRuntime to top of included libraries
    Any suggestions
    String oasUrl = "oas://hfxcap4:80";
    String oasEJB = "MyOASApp/MyEJB" ;
    // Setup the environment
    Hashtable environment = new Hashtable();
    // Turn JNDI on to OAS
    environment.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "oracle.oas.naming.jndi.RemoteInitCtxFactory");
    // Lookup the URL
    conv_package.MyEJBHome homeInterface = null;
    try {
    System.out.println("Creating an initial context");
    // Get initial JNDI context
    Context site = (Context) ((new InitialContext(environment)).lookup(oasUrl));
    org.omg.CORBA.COMM_FAILURE:
    at oracle.oas.orb.CORBA.Request._invoke(Compiled Code)
    at oracle.oas.orb.CORBA.Delegate._invoke(Compiled Code)
    at org.omg.CORBA.portable.ObjectImpl._invoke(Compiled Code)
    at oracle.oas.orb.CORBA.Delegate.is_a(Compiled Code)
    at org.omg.CORBA.portable.ObjectImpl._is_a(Compiled Code)
    at oracle.oas.jndi.oas.BeanInitialContext.resolve(Compiled Code)
    at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
    at oracle.oas.jndi.oas.BeanInitialContext.lookup(Compiled Code)
    at oracle.oas.jndi.oas.WrapperContext.lookup(Compiled Code)
    at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
    at javax.naming.InitialContext.lookup(Compiled Code)
    at CClient_package.MyOASAppClient.main(Compiled Code)<HR></BLOCKQUOTE>
    null

Maybe you are looking for

  • Screen resolution preferences does not work for me...

    I have a 1920x1080, 17.4 laptop. That is approx 126.6 ppi screen resolution if my calculkations are correct... So in order to set PS to display real size of the images according to the zoom, I go to edit / preferences / units & rulers and set the scr

  • PS CC 2014 Actions launch Preferences Window

    I've been using Photoshop Actions for years but recently I've encountered some odd behavior. I made a simple action that removes transparency from a document by executing the Trim command. The last part of the action then saves the changes and closes

  • Where did my url toolbar go on Safari on Mavericks?

    How do I get it back? Why did it disappear in the first place? I'm on 10.9.2 and this is a white macbook from 2009.

  • Alarm Clock Inquery

    I have the iphone 3g s and I have a basic question about my alarm clock. Prior to the iphone I had a blackberry and I became accustomed to customizing alarms and phone powering off and on. Well, I know for a fact that the iphone 3g powers on if there

  • Can anyone help me pleasesafari keep crashing

    my safari keeps crashing and takes ages to come back on this is report that i get Process: Safari [112] Path: /Applications/Safari.app/Contents/MacOS/Safari Identifier: com.apple.Safari Version: 5.0 (5533.16) Build Info: WebBrowser-75331600~3 Code Ty