Error from ejbc: The JNDI name of bean

hi~
i have a problem .
to deploy , i did test bean like this..
java -classpath %CLASSPATH% -Dweblogic.home=%WL_HOME% weblogic.ejbc -compiler javac
old.jar new.jar
ERROR: Error from ejbc: The JNDI name of bean c was not set
ERROR: ejbc found errors
thank..^^
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN'
'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>c</ejb-name>
<home>c1.cHome</home>
<remote>c1.c</remote>
<ejb-class>c1.cEJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>c</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

What's your weblogic-ejb-jar.xml file?
"oh ki sung" <[email protected]> wrote in message
news:3cc8499a$[email protected]..
>
hi~
i have a problem .
to deploy , i did test bean like this..
java -classpath %CLASSPATH% -Dweblogic.home=%WL_HOME%weblogic.ejbc -compiler javac
old.jar new.jar
ERROR: Error from ejbc: The JNDI name of bean c was not set
ERROR: ejbc found errors
thank..^^
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD EnterpriseJavaBeans 1.1//EN'
'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>c</ejb-name>
<home>c1.cHome</home>
<remote>c1.c</remote>
<ejb-class>c1.cEJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>c</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Similar Messages

  • How to get the JNDI name of an EJB from within itself

    Hello,
    I'm trying to find a way to get the JNDI name of a session bean from
    within itself.
    In the application I'm working on we need to support multiple
    customers. In order to do that, each EJB has a normal home and remote
    interface, a base class bean implementation and different children
    bean implemetations for each customer (when the logic for the
    customers is different). JNDI is used to get the proper implementation
    based on the customer.
    I've got an EJB that provides some services that are the same for all
    customers, except for the fact that it contains one variable that
    should have a different value depending on the customer. I don't want
    to creat subclasses just for that. What I want is to be able to get
    the JNDI name and set the variable based on the it.
    Is there a way to get the JNDI name for the EJB from within itself?
    TIA
    MJ

    Hi Pradeep,
    Please try referring to this post which is discussed earliar and seems its also answered.
    http://forums.adobe.com/thread/504861
    Thanks,
    Bhasker Chari

  • Error in getting the BAPIWrapper name from the ini file or SAP mobile configuration: Agentry Error

    Hello Experts,
    I follow the flightbooking tutorial to create a Material application to get material list. I  can start the agentry server but when I connect to SAP server and get data, I face below issue
    Error in getting the BAPIWrapper name from the ini file or SAP mobile configuration. Please check the ini file or the mobile configuration for the bapi key (com.syclo.sap.material.bapi.materialbapi) either in sections BAPI_WRAPPER or REQUIRED_BAPI_WRAPPER
    I check the parameters name in SAP Agentry Config panel, all are correct. Why cannt it get the data. Do I have to add anything in javaBE.ini? Please help me. Thank you very much.
    My javaBE
    [HOST]
    server=be1.vdc.csc.com
    APPNAME=ZCH_MATERIALLIST
    [CLIENT_NUM]
    CLIENT=800
    [SYSTEM_NUM]
    SYSNUM=01
    [LOGON_METHOD]
    ; USER_AUTH if standard UID/Password authentication is used
    ; USER_AUTH_GLOBAL if pooled connections using single UID/Password is used
    ; USER_AUTH_GROUP if UID/Password authentication with SAP Message Server
    ;   (load balancing) is used
    LOGON_METHOD=USER_AUTH
    [GLOBAL_LOGON]
    ; referenced when LOGON_METHOD=USER_AUTH_GLOBAL
    ; uses a pool of connections to the SAP backend all utilizing a single
    ;    UID/password
    UID=
    UPASSWORD=
    SHAREDCONNECTION=0
    GET_PERSONNEL_INFO=
    [SERVICE_LOGON]
    ENABLED=true
    UID=hngu3
    UPASSWORD=xxxxxxx
    UPASSWORDENCODED=false
    [GROUP_LOGON]
    ; referenced when LOGON_METHOD=USER_AUTH_GROUP
    ; individual user authentication using an SAP Message Server which distributes
    ; client connections among a "group" of SAP application servers based on load
    ; balancing criteria
    ; host name or IP address of SAP Message Server
    MESSAGE_SERVER=
    GROUP_NAME=
    SYSTEM_ID=
    CLIENT=
    [LANGUAGE]
    LANG=EN
    [LOGGING]
    Level=4
    [REQUIRED_BAPI_WRAPPER]
    com.syclo.sap.bapi.LoginCheckBAPI=/SYCLO/CORE_SUSR_LOGIN_CHECK
    com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT
    com.syclo.sap.bapi.RemoteParameterGetBAPI=/SYCLO/CORE_MDW_PARAMETER_GET
    com.syclo.sap.bapi.SystemInfoBAPI=/SYCLO/CORE_SYSTINFO_GET
    com.syclo.sap.bapi.ChangePasswordBAPI=/SYCLO/CORE_SUSR_CHANGE_PASSWD
    com.syclo.sap.bapi.CTConfirmationBAPI=/SYCLO/CORE_OUTB_MSG_STAT_UPD
    com.syclo.sap.bapi.DTBAPI=/SYCLO/CORE_DT_GET
    com.syclo.sap.bapi.GetEmployeeDataBAPI=/SYCLO/HR_EMPLOYEE_DATA_GET
    com.syclo.sap.bapi.GetUserDetailBAPI=/SYCLO/CORE_USER_GET_DETAIL
    com.syclo.sap.bapi.GetUserProfileDataBAPI=/SYCLO/CORE_USER_PROFILE_GET
    com.syclo.sap.bapi.PushStatusUpdateBAPI=/SYCLO/CORE_PUSH_STAT_UPD
    com.syclo.sap.bapi.RemoteObjectCreateBAPI=/SYCLO/CORE_MDW_USR_OBJ_CRT
    com.syclo.sap.bapi.RemoteObjectDeleteBAPI=/SYCLO/CORE_MDW_USR_OBJ_DEL
    com.syclo.sap.bapi.RemoteObjectGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
    com.syclo.sap.bapi.RemoteObjectUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
    com.syclo.sap.bapi.RemoteReferenceCreateBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_CRT
    com.syclo.sap.bapi.RemoteReferenceDeleteBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_DEL
    com.syclo.sap.bapi.RemoteReferenceGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
    com.syclo.sap.bapi.RemoteReferenceUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
    com.syclo.sap.bapi.RemoteSessionDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
    com.syclo.sap.bapi.RemoteUserDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
    com.syclo.sap.bapi.RemoteUserUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
    com.syclo.sap.bapi.TransactionCommitBAPI=WFD_TRANSACTION_COMMIT
    com.syclo.sap.bapi.SignatureCaptureBAPI=/SYCLO/CS_DOBDSDOCUMENT_CRT

    Hi Tahir, please help me check the log below
    Agentry Runtime Worker Thread###throwExceptionToClient::begin |
    Agentry Runtime Worker Thread###throwExceptionToClient::com.syclo.sap.material.steplet.MaterialSteplet::throwExceptionToClient::397::MaterialSteplet - Error in getting the BAPIWrapper name from the ini file or SAP mobile configuration. Please check the ini file or the mobile configuration for the bapi key (com.syclo.sap.material.bapi.materialbapi) either in sections BAPI_WRAPPER or REQUIRED_BAPI_WRAPPER |
    Agentry Runtime Worker Thread###Exception: 17:15:35 06/17/2014 : 20 (Agentry3), Java Business Logic Error (com.syclo.agentry.BusinessLogicException: MaterialSteplet - Error in getting the BAPIWrapper name from the ini file or SAP mobile configuration. Please check the ini file or the mobile configuration for the bapi key (com.syclo.sap.material.bapi.materialbapi) either in sections BAPI_WRAPPER or REQUIRED_BAPI_WRAPPER),  |
    Agentry Runtime Worker Thread###loggedOut::begin |
    Agentry Runtime Worker Thread###HNGU3: SESSION END |
    Agentry Runtime Worker Thread###BAPI::begin |
    Agentry Runtime Worker Thread###create::nulled repository::created new repository |
    Agentry Runtime Worker Thread###create::/SYCLO/CORE_MDW_SESSION1_DEL Connection ID: com.sap.mw.jco.JCO$Client@2656ed99 |
    Agentry Runtime Worker Thread###create::Function /SYCLO/CORE_MDW_SESSION1_DEL created |

  • The DataSource with the JNDI name: MyDataSource could not be located.

    hi,
    I created a connection pool myconnectionpool and i create a data source MyDataSource with jndi name as mydsn.
    in my weblogic-cmp-rdbms-jar.xml i gave
    <data-source-name>MyDataSource</data-source-name> and
    When i deploy the bean i am getting following exception.
    Unable to deploy EJB: containerManaged from cmp7.jar:
    weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: MyDataSource could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:128)
         at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:213)
         at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:185)
         at weblogic.ejb20.manager.DBManager.setup(DBManager.java:160)
         at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:928)
         at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1216)
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:850)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:70)
         at weblogic.j2ee.Application.addComponent(Application.java:253)
         at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:144)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:301)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:255)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:206)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:716)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:698)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:380)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:902)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:480)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:208)
         at $Proxy34.updateDeployments(Unknown Source)
         at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:3724)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1584)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:337)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:233)
         at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:61)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:852)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:273)
         at weblogic.Server.main(Server.java:33)
    Where i went wrong?
    Thanks in advance
    phani

    Hi ,
    I have the same problem .when i look into JNDI tree view the jndi name is listed. but it saying error below listed.
    my
    ejb-name:=containerManaged
    datasourcename=EX_DataSource
    jndi-name=EX_JNDI
    <Feb 14, 2005 3:10:08 PM IST> <Error> <Deployer> <149231> <The slave deployer was unable to set the activatio
    true for the application EX_Container
    weblogic.management.ApplicationException: activate failed forEX_Container
    Module Name: EX_Container, Error: Exception activating module: EJBModule(EX_Container,status=PREPARED)
    Unable to deploy EJB: containerManaged from EX_Container.jar:
    The DataSource with the JNDI name: EX_DataSource could not be located. Please ensure that the DataSource has
    ed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
    TargetException:
    Unable to deploy EJB: containerManaged from EX_Container.jar:
    The DataSource with the JNDI name: EX_DataSource could not be located. Please ensure that the DataSource has
    ed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1093)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1022)
    at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:376)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLife
    ava:235)
    at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:65)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:832)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
    at weblogic.Server.main(Server.java:32)
    my weblogic-ejb-jar.xml
    <?xml version="1.0"?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC
    '-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB//EN'
    'http://www.bea.com/servers/wls700/dtd/weblogic-ejb-jar.dtd'>
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>containerManaged</ejb-name>
    <entity-descriptor>
    <persistence>
         <persistence-use>
         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
         <type-version>7.0</type-version>
         <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
         </persistence-use>
    </persistence>
    </entity-descriptor>
    <jndi-name>EX_JNDI</jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    <?xml version="1.0"?>
    <!DOCTYPE weblogic-rdbms-jar PUBLIC
    '-//BEA Systems, Inc.//DTD WebLogic 7.0.0 EJB RDBMS Persistence//EN'
    'http://www.bea.com/servers/wls700/dtd/weblogic-rdbms20-persistence-700.dtd'>
    weblogic-cmp-rdbms-jar.xml file
    <weblogic-rdbms-jar>
    <weblogic-rdbms-bean>
    <ejb-name>containerManaged</ejb-name>
    <data-source-name>EX_DataSource</data-source-name>
    <table-map>
    <table-name>ejbAccounts</table-name>
    <field-map>
    <cmp-field>accountId</cmp-field>
    <dbms-column>id</dbms-column>
    </field-map>
    <field-map>
    <cmp-field>balance</cmp-field>
    <dbms-column>bal</dbms-column>
    </field-map>
    <field-map>
    <cmp-field>accountType</cmp-field>
    <dbms-column>type</dbms-column>
    </field-map>
    </table-map>
    </weblogic-rdbms-bean>
    <create-default-dbms-tables>DropAndCreateAlways</create-default-dbms-tables>
    </weblogic-rdbms-jar>
    ejb-jar.xml
    <?xml version="1.0"?>
    <!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>
    <entity>
    <ejb-name>containerManaged</ejb-name>
    <home>containerBN.EX.AccountHome</home>
    <remote>containerBN.EX.Account</remote>
    <ejb-class>containerBN.EX.AccountBean</ejb-class>
    <persistence-type>Container</persistence-type>
    <prim-key-class>java.lang.String</prim-key-class>
    <reentrant>False</reentrant>
    <cmp-version>2.x</cmp-version>
    <abstract-schema-name>AccountBean</abstract-schema-name>
    <cmp-field>
    <field-name>accountId</field-name>
    </cmp-field>
    <cmp-field>
    <field-name>balance</field-name>
    </cmp-field>
    <cmp-field>
    <field-name>accountType</field-name>
    </cmp-field>
    <primkey-field>accountId</primkey-field>
    <query>
    <query-method>
    <method-name>findBigAccounts</method-name>
    <method-params>
    <method-param>double</method-param>
    </method-params>
    </query-method>
    <ejb-ql>
    <![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.balance > ?1]]>
    </ejb-ql>
    </query>
    <query>
    <query-method>
    <method-name>findAccount</method-name>
    <method-params>
    <method-param>double</method-param>
    </method-params>
    </query-method>
    <ejb-ql>
    <![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.balance = ?1]]>
    </ejb-ql>
    </query>
    <query>
    <query-method>
    <method-name>findNullAccounts</method-name>
    <method-params>
    </method-params>
    </query-method>
    <ejb-ql>
    <![CDATA[SELECT OBJECT(a) FROM AccountBean AS a WHERE a.accountType IS NULL]]>
    </ejb-ql>
    </query>
    </entity>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>containerManaged</ejb-name>
         <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    <ejb-client-jar>EX_Container.jar</ejb-client-jar>
    </ejb-jar>
    pls lhelp me .
    my email id: [email protected]
    thanks in advance.
    Sudhakar.M

  • Unable to bind EJB Home Interface to the JNDI name

    Why do I get this error?? What is the jndi-name in weblogic-ejb-jar.xml
    Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:
    Unable to bind EJB Home Interface to the JNDI name:
    com.sempire.builder.business
    _component.Organization. The error was:
    javax.naming.NameAlreadyBoundException: Organization is already bound;
    remaining
    name 'com.sempire.builder.business_component'
    <<no stack trace available>>

    Slava,
    In case I change the name of the jndi name to a unique name. I still get the same
    problem. I checked for multiple occurences, but there aren't any.
    My web.xml file is:
    <ejb-local-ref>
    <description>
    Reference EJB resources in Weblogic Resources
    </description>
    <ejb-ref-name>GangsterEJB</ejb-ref-name>
    <ejb-ref-type>Entity</ejb-ref-type>
    <local-home>com.sempire.builder.business_component.GangsterHome</local-home>
    <local>com.sempire.builder.business_component.Gangster</local>
    </ejb-local-ref>
    My weblogic-ejb-jar.xml file is:
    <weblogic-enterprise-bean>
    <ejb-name>GangsterEJB</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>
    <resource-description>
    <res-ref-name>jdbc/GangsterDB</res-ref-name>
    <jndi-name>oraclePool</jndi-name>
    </resource-description>
    </reference-descriptor>
    <local-jndi-name>Gangster_test</local-jndi-name>
    </weblogic-enterprise-bean>
    I do not get the problem.
    Thank you
    Ronak Parekh
    "Slava Imeshev" <[email protected]> wrote:
    Hi Ronak,
    This exception means that you already have a bean
    with the same JNDI name. Search your weblogic-ejb-jar.xml files
    for multiple occurrences of the name and fix the problem.
    Regards,
    Slava Imeshev
    "Ronak Parekh" <[email protected]> wrote in message
    news:[email protected]...
    Why do I get this error?? What is the jndi-name in weblogic-ejb-jar.xml
    Unable to deploy EJB: OrganizationEJB from sempire_bc.jar:
    Unable to bind EJB Home Interface to the JNDI name:
    com.sempire.builder.business
    _component.Organization. The error was:
    javax.naming.NameAlreadyBoundException: Organization is already bound;
    remaining
    name 'com.sempire.builder.business_component'
    <<no stack trace available>>

  • ERROR: Error from ejbc: in WLS 6.1 sp2 Win2K

    Never had this problem before. Started new project using WLS 6.1 sp2 under Windows
    2K Prof., using ANT & get;
    ERROR: Error from ejbc:
    In EJB NOTiFYEJB, method createUser defined in the remote interface either does
    not exist in the bean class, or it is not a public method. Each method in the
    remote interface must have a corresponding public method in the bean class.
    BUILD FAILED
    I saw a posting which referred to a problem with Win2K & an old (1.2) JDK in the
    path. I have put C:\bea\jdk131 at the front of my class path but still get this
    error.

    The problem was nothing to do with classpaths etc.
    CMP does not support "Date" types and in my EJB I had Date types, I changed these
    to "long" and converted all Dates to number of milleseconds from 1970 and persisted
    them to a number column in Oracle.
    It was the entries in the weblogic-cmp-rdbms.xml which was the root of the problem.
    "Roger Lee" <[email protected]> wrote:
    >
    Matthew,
    Thanks for yor suggestions.
    My classpath is set in the ANT.BAT & only points to the tools.jar, weblogic_sp.jar
    & weblogic.jar.
    I have my JARs in a manfest file in each directory with the "Class-Path:"
    entry.
    I have also added a new Bean with compiles & ejbcs fine. But I still
    get an error
    with my "createUser" method, saying the interface does not exist in the
    bean class
    or is not a public method.
    I have even changed it's name to "createUserCandidate" just in case it
    was clashing
    with an existing method.
    Any other ideas for investigation?
    Thanks.
    Matthew Shinn <[email protected]> wrote:
    Hi Roger,
    Roger Lee wrote:
    The "warnings saying classes are being loaded from your classpath"are, I believe
    just warning from Ant. I searched the newsgroups and it appears thatthis is not
    a problem.These warnings are from ejbc. They are there to let you know that classes\interfaces
    needed by your EJB are being loaded from your classpath and not your
    jar. They
    should be taken seriously. This could definitely be the cause of your
    problem. As I
    said in my previous posting, ejbc could be loading an old version of
    your bean class
    from your classpath. This old class may not contain the createUsermethod
    with the
    same signature as the method in your remote interface.
    Is this an issue with WLS 6.1 sp2?I don't believe so.
    I've wasted so much time on this any help would be appreciated.You essentially have three options.
    1. Take my advice and make sure your classes are being loaded fromyour
    jar and not
    the classpath.
    2. Post your entire jar so we can try to reproduce the problem.
    3. Contact support.
    - Matt
    Matthew Shinn <[email protected]> wrote:
    Hi Roger,
    Your bean and interface look fine. One thing you might try is explicitly
    declaring
    your createUser method to be public in your remote interface. I
    don't
    think this
    will change the outcome but it's worth a try. When you run ejbcdo
    you
    get any
    warnings saying classes are being loaded from your classpath ratherthan
    your jar?
    If this were the case, you could have an old copy of your bean inyour
    classpath
    that ejbc is picking up. If this doesn't help, I think the next
    step
    is to send me
    or post your entire jar.
    - Matt
    Roger Lee wrote:
    Typo that should have been "path", I had added "C:\bea\jdk131"
    to
    the
    front of
    my path & was getting the error.
    Enclose my two classes in the attached file.
    Thanks for you help.
    Matthew Shinn <[email protected]> wrote:
    Hi Roger,
    Make sure you put C:\bea\jdk131 in front of your path (not classpath).
    :) Assuming
    this isn't the problem, can you please post any createUser method
    declarations
    in your
    remote interface and the corresponding createUser methods in yourbean
    class?
    - Matt
    Name: NOTiFY_&_NOTiFYBean.java
    NOTiFY_&_NOTiFYBean.java Type: java/*
    Encoding: base64

  • Error from ejbc: Compiler failed executable.exec

    Hi all,
    I am using weblogic server 8.1 and encounter an error when I build my project, could anyone give me a helping hand? Thank you.
    This is my Configuration:
    Application Type: Empty Application
    Project Type: EJB Project
    Project Name: LibraryEJBProject
    DataSource: LibraryDataSource using cgPool
    Table: Library_Book under Schemas\Weblogic\Tables of pointbase server
    EJB name: BookBean.EJB under LibraryEJBProject\book
    When I right click LibraryEJBProject and click build, the following error comes out:
    ======================================================
    Build project LibraryEJBProject started.
    BUILD STARTED
    build:
    Created dir: C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build
    check-env:
    WARNING: Checking to see if there is anything new to build...
    Created dir: C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_ejb_crc
    no-ejbgen:
    run-build:
    clean-modules:
    removed module 'LibraryEJBProject.jar'
    WARNING: Running EJBGen...
    Loading source file C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp/Book\BookBean.java...
    Constructing Javadoc information...
    EJBGen 2.16
    [Info:] Creating C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp\Book\Book.java
    [Info:] Creating C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp\Book\BookHome.java
    [Info:] Creating C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp\META-INF\ejb-jar.xml
    [Info:] null [Bean] MAKE CLASS NAME G:BookHome P:Book N:BookHome
    [Info:] null [Bean] MAKE CLASS NAME G:Book P:Book N:Book
    [Info:] Creating C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp\META-INF\weblogic-ejb-jar.xml
    [Info:] Creating C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp\META-INF\weblogic-cmp-rdbms-jar.xml
    [Info:] Creating C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\/wlw_LibraryEJBProject_build/../wlw_ejb_crc//ejbgentemp\ejbgen-build.xml
    post-ejbgen:
    clean-ejbc:
    Copying 7 files to C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build
    WARNING: EJBGen ok. Compiling...
    runjavac:
    Compiling 3 source files to C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build
    WARNING: All files compiled. Running ejbc...
    <Dec 3, 2004 12:18:44 PM CST> <Warning> <EJB> <BEA-010212> <The EJB 'Book(Jar: C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build)' contains at least one method without an explicit transaction attribute setting. The default transaction attribute of Supports will be used for the following methods: local-home[createQuery(), remove(java.lang.Object), findByPrimaryKey(java.lang.Integer), create(java.lang.Integer)] local[getBookID(), getIsbn(), getName(), setPublisher(java.lang.String), getPublisher(), setAuthor(java.lang.String), setBookID(java.lang.Integer), remove(), setIsbn(java.lang.String), getAuthor(), setName(java.lang.String)] >
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:76: cannot resolve symbol
    symbol : class BookBean
    location: interface Book.Book
    public final class Book_5wlu3i__WebLogic_CMP_RDBMS extends Book.BookBean
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:760: cannot resolve symbol
    symbol : class Book_5wlu3i_Intf
    location: interface Book.Book
    Book.Book_5wlu3i_Intf beanIntf)
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_Intf.java:39: cannot resolve symbol
    symbol : class Book_5wlu3i_Intf
    location: interface Book.Book
    (java.sql.ResultSet rs, java.lang.Integer offset, Object __WL_pk, Book.Book_5wlu3i_Intf var)
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_ELOImpl.java:15: cannot resolve symbol
    symbol : class Book
    location: interface Book.Book
    implements Book.Book, weblogic.utils.PlatformConstants, java.io.Serializable
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_LocalHomeImpl.java:13: cannot resolve symbol
    symbol : class BookHome
    location: interface Book.Book
    implements Book.BookHome, weblogic.utils.PlatformConstants
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_LocalHomeImpl.java:76: cannot resolve symbol
    symbol : class Book
    location: interface Book.Book
    public Book.Book create (java.lang.Integer arg0)
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_LocalHomeImpl.java:101: cannot resolve symbol
    symbol : class Book
    location: interface Book.Book
    public Book.Book findByPrimaryKey(java.lang.Integer arg0)
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:244: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.setEntityContext(arg0);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:257: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.unsetEntityContext();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:269: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbActivate();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:490: cannot resolve symbol
    symbol : class Book_5wlu3i__WebLogic_CMP_RDBMS
    location: interface Book.Book
    Book.Book_5wlu3i__WebLogic_CMP_RDBMS __WL_bean = null;
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:566: cannot resolve symbol
    symbol : class Book_5wlu3i__WebLogic_CMP_RDBMS
    location: interface Book.Book
    __WL_bean = (Book.Book_5wlu3i__WebLogic_CMP_RDBMS)__WL_pm.getBeanFromRS(__WL_pk, __WL_rsInfo);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:763: cannot resolve symbol
    symbol : class Book_5wlu3i__WebLogic_CMP_RDBMS
    location: interface Book.Book
    Book.Book_5wlu3i__WebLogic_CMP_RDBMS __WL_bean = (Book.Book_5wlu3i__WebLogic_CMP_RDBMS)beanIntf;
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:763: cannot resolve symbol
    symbol : class Book_5wlu3i__WebLogic_CMP_RDBMS
    location: interface Book.Book
    Book.Book_5wlu3i__WebLogic_CMP_RDBMS __WL_bean = (Book.Book_5wlu3i__WebLogic_CMP_RDBMS)beanIntf;
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:922: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbLoad();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:936: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbStore();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:950: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbRemove();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1051: cannot resolve symbol
    symbol : class Book_5wlu3i__WebLogic_CMP_RDBMS
    location: interface Book.Book
    case 0: __WL_loadGroup0FromRS(rs, offset, __WL_pk, (Book.Book_5wlu3i__WebLogic_CMP_RDBMS)eb); break;
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1167: reference to + is ambiguous, both method +(java.lang.String,java.lang.String) in and method +(java.lang.String,int) in match
    if(__WL_verbose) Debug.say("setting("+this+") 'author' using column " __WL_num ". Value is " + this.author);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1178: reference to + is ambiguous, both method +(java.lang.String,java.lang.String) in and method +(java.lang.String,int) in match
    if(__WL_verbose) Debug.say("setting("+this+") 'isbn' using column " __WL_num ". Value is " + this.isbn);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1189: reference to + is ambiguous, both method +(java.lang.String,java.lang.String) in and method +(java.lang.String,int) in match
    if(__WL_verbose) Debug.say("setting("+this+") 'name' using column " __WL_num ". Value is " + this.name);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1200: reference to + is ambiguous, both method +(java.lang.String,java.lang.String) in and method +(java.lang.String,int) in match
    if(__WL_verbose) Debug.say("setting("+this+") 'publisher' using column " __WL_num ". Value is " + this.publisher);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1663: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbCreate( arg0);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1702: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbPostCreate( arg0);
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1847: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbRemove();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1907: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbLoad();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:1938: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbStore();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i__WebLogic_CMP_RDBMS.java:2072: cannot resolve symbol
    symbol : variable super
    location: class Book.Book_5wlu3i__WebLogic_CMP_RDBMS
    super.ejbPassivate();
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_LocalHomeImpl.java:80: cannot resolve symbol
    symbol : class Book
    location: interface Book.Book
    return (Book.Book) super.create(md_ejbCreate_I,
    ^
    C:\DOCUME~1\NICHOL~1.LAB\LOCALS~1\Temp\wlw_LibraryEJBProject_build\Book\Book_5wlu3i_LocalHomeImpl.java:105: cannot resolve symbol
    symbol : class Book
    location: interface Book.Book
    return (Book.Book)
    ^
    30 errors
    ERROR: ERROR: Error from ejbc: Compiler failed executable.exec
    ERROR: ERROR: ejbc couldn't invoke compiler
    BUILD FAILED
    ERROR: ERROR: Error from ejbc: Compiler failed executable.exec
    ERROR: ERROR: ejbc couldn't invoke compiler
    ======================================================
    What would be the cause of the error, would it be related to the way I create the datasource and the table? Or other causes, please help. Thank you.
    Regards,
    Nicholas Lok

    It's difficult to tell solely by the messages. One there seems to be a problem finding a base class. One thing that I notice is that the package seems to contain 'book' with a lower case 'b' as in:
    EJB name: BookBean.EJB under LibraryEJBProject\book
    Whereas all the error messages are saying that they are having trouble finding something with a package name like 'Book' with a capital 'B'.
    Perhaps that is the problem, the package has to be consistently 'book' or 'Book' and can't be both.
    Hope I'm right and hope this helps.
    thorick

  • The DataSource with the JNDI name: contentDataSource could not be located

    Hello,
    We try to deploy our system/application to the servers that structed as
    Machine one has:
    1 administration domain
    1 managed domain
    Machine two has :
    1 managed domain which is administrated by machine one.
    I was trying to deploy the UI(portal application) to managed domain under Machine one. I got
    error message as following:
    Exception:weblogic.management.ApplicationException: activate failed for content.jar Module: content.jar Error: Exception activating module: EJBModule(content.jar,status=PREPARED) Unable to deploy EJB: ValueBean from content.jar: [EJB:011028]The DataSource with the JNDI name: contentDataSource could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
    I have portalFrameworkPool Data Sources deployed to both managed domains.
    when I deploy the application to the server that has one one domain(both adminstrator domain and application domain are in one), it is fine.
    Can some one with same experience, or BEA people provide some help on this? Very appreciate any help on this issue.
    Thanks in advance.
    Christina

    :-p
    If you go to each Managed Server on the console, you can see the Service tab and then go to JDBC. Under JDBC you can see all the pool connections. Instead of localhost they should be pointing to the specific hostname or ip address of the adminserver and the pointbase port on that server (9093 by default) so the EAR files can be correctly deployed and then the JNDI Tree will look exactly the same on both servers. Change all the connection pools to use the specific hostname instead of localhost. Hope this works for you.

  • A problem determining the JNDI Name of a local EJB with WL 8.1

    Hi,
    I created a very simple local EJB and deployed it with Weblogic8.1. When I test
    it in the Weblogic server admin page, I got the following message:
    "The EJB MyLocal has not been tested successfully. There was a problem determining
    the JNDI Name of the given bean."
    Can anyone help figure out the problem?
    Thanks
    Henry

    Does the ejb have a target server specified?
    Does the Ejb have a Jndi binding as specified in the <local-jndi-name></local-jndi-name>
    element of weblogic-ejb-jar.xml?
    thanks,
    Deepak
    "Henry" <[email protected]> wrote:
    >
    >
    Hi,
    I created a very simple local EJB and deployed it with Weblogic8.1. When
    I test
    it in the Weblogic server admin page, I got the following message:
    "The EJB MyLocal has not been tested successfully. There was a problem
    determining
    the JNDI Name of the given bean."
    Can anyone help figure out the problem?
    Thanks
    Henry

  • WLS10.3.1 : How to overload the jndi name of a stateless EJB

    Hi,
    I am trying to overload the jndi name of a stateless bean defined in an application by using a weblogic-ejb-jar.xml descriptor file.
    This does not work.
    The ear contains a jar that have a weblogic-ejb-jar.xml file in its META-INF directory. The file is :
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-ejb-jar
    xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
    <weblogic-enterprise-bean>
    <ejb-name>HelloWorldBean</ejb-name>
    <enable-call-by-reference>true</enable-call-by-reference>
    <jndi-name>TOTO</jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    This is the code of my bean :
    package test;
    import javax.ejb.Local;
    import javax.ejb.Remote;
    import javax.ejb.Stateless;
    @Stateless( name = "HelloWorldBean", mappedName="HWBean")
    @Local( IHelloWorldLocal.class)
    @Remote( IHelloWorldRemote.class)
    public class HelloWorldBean implements IHelloWorldLocal, IHelloWorldRemote
    public void sayHello(String name) {
    System.out.println( "Hello " + name + "!!!!");
    The bean implements the following interfaces :
    package test;
    public interface IHelloWorldRemote extends IHelloWorld {
    package test;
    public interface IHelloWorldLocal extends IHelloWorld {
    package test;
    public interface IHelloWorld {
    public void sayHello( String name);
    When i browse the JNDI tree, i see the bean registered with the mapped name attribute (HWBean#test.IHelloWorldRemote) but i don't see any bean registered with the name provided by the weblogic-ejb-jar.xml (TOTO)
    My standalone client can't perform a lookup using the JNDI name 'TOTO' but reaches the bean when using 'HWBean#test.IHelloWorldRemote'
    It seem's that the overload of the Jndi name using the weblogic-ejb-jar file descriptor doesn't work.
    Can you help me to solve the problem.
    Thanks.

    Thank you, my sample works fine with the following weblogic-ejb-jar.xml :
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
    <weblogic-enterprise-bean>
    <ejb-name>HelloWorldBean</ejb-name>
    <enable-call-by-reference>true</enable-call-by-reference>
    <stateless-session-descriptor>
    <business-interface-jndi-name-map>
    <business-remote>test.IHelloWorldRemote</business-remote>
    <jndi-name>TOTO</jndi-name>
    </business-interface-jndi-name-map>
    </stateless-session-descriptor>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>

  • JDBC Datasource creation via ANT doesn't expose the JNDI name

    I'm using the wlconfig ANT task to create a Datasource (& JDBC connectionpool) on the weblogic server. The datasource is created fine, and I can test it using the console.
    The problem is that the provided JNDI name isn't exposed in the JNDI tree. This seems to be related to the fact that the following element is generated in the config/jdbc/CP-PoolName-2164-jdbc.xml
    &lt;jdbc-data-source&gt;
    &lt;name&gt;PoolName&lt;/name&gt;
    &lt;internal-properties&gt;
    *&lt;property&gt;*
    *&lt;name&gt;LegacyType&lt;/name&gt;*
    *&lt;value&gt;1&lt;/value&gt;*
    *&lt;/property&gt;*
    When removing the LegacyType 1 property from the JDBC config xml, the JNDI name is exposed fine.
    I've used the instructions located at [http://edocs.bea.com/wls/docs100/programming/ant_tasks.html] where an example of a JDBCConnectionPool creation is provided.
    The 10.3 documentation doesn't include the example anymore, but I'm having the problem both on BEA Weblogic 10.0 and Oracle Weblogic 10.3
    &lt;wlconfig url="t3://localhost:7001" username="weblogic" password="weblogic"&gt;
    bq. &lt;query domain="base_domain" type="Server" name="AdminServer" property="adminserver"/&gt;
    bq. &lt;create type="JDBCConnectionPool" name="MediumSecureOnlineNode1Pool" property="customPool1"&gt;
    bq. bq. &lt;set attribute="CapacityIncrement" value="1"/&gt; \\ &lt;set attribute="DriverName" value="oracle.jdbc.OracleDriver"/&gt; \\ &lt;set attribute="InitialCapacity" value="1"/&gt; \\ &lt;set attribute="MaxCapacity" value="10"/&gt; \\ &lt;set attribute="Password" value="pass"/&gt; \\ &lt;set attribute="Properties" value="user=username"/&gt; \\ &lt;set attribute="RefreshMinutes" value="0"/&gt; \\ &lt;set attribute="ShrinkPeriodMinutes" value="15"/&gt; \\ &lt;set attribute="ShrinkingEnabled" value="true"/&gt; \\ &lt;set attribute="TestConnectionsOnCreate" value="true"/&gt; \\ &lt;set attribute="TestConnectionsOnRelease" value="true"/&gt; \\ &lt;set attribute="TestConnectionsOnReserve" value="true"/&gt; \\ &lt;set attribute="TestTableName" value="SQL SELECT 1 FROM DUAL"/&gt; \\ &lt;set attribute="URL" value="jdbc:oracle:thin:@localhost:1521"/&gt; \\ &lt;set attribute="Targets" value="${adminserver}"/&gt;
    &lt;/create&gt;
    As we would like to automate the process of configuring our weblogic instances using ANT, is there a way to create JDBC datasources that don't have the LegacyType 1 element included in the config ?

    Curious if you were ever able to find a resolution to this issue?
    I am facing the same thing now with our Ant scripts and WL10.3 connection pools/datasources.
    I would like to either specify a different LegacyType or suppress it altogether. Any help would be appreciated.
    Many thanks,
    Steve

  • How to Set the JNDI name in J2EE 1.4 ??

    Hello,
    I am sure i am have done everything right except for the JNDI name ! I have recently shifted to J2EE 1.4. I was using j2EE 1.2.
    So kindly tell me how should i set me JNDI name in the deploytool.
    Here is the exception i got when i tried to run my application without having set any JNDI name !!
    http://img220.imageshack.us/img220/832/hellodt5.gif
    Thanks.

    There are 2 types of descriptors:
    standard and portable deployment descriptors (e.g. ejb-jar.xml, web.xml, application.xml, etc)
    vendor specific deployment plan (e.g., sun-ejb-jar.xml, sun-web.xml, sun-application.xml, jboss.xml, weblogic.xml, etc)
    When you are developing ejb apps with glassfish, or JavaEE SDK, or Sun Java System Application Server, you usually package all descriptors in META-INF directory inside the jar.
    You can also create portable apps that do not contain any vendor specific deployment plans. So you can deploy it to any appserver. At deployment time, you then specify an option to pass the deployment plan to deploy tool. This is required by JSR 88 and all J2EE- or JavaEE-compliant appserver must support this.
    In Glassfish, JavaEE SDK, or SJSAS, you can:
    $SJSAS_HOME/bin/asadmin deploy --deploymentplan /tmp/deploy-plan.jar /tmp/my-ejb.jar
    where /tmp/deploy-plan.jar is a jar file containing sun-ejb-jar.xml for the deployable ejb-jar:
    jar tvf deployment-plan.jar
    0 Thu Oct 12 11:55:00 EDT 2006 META-INF/
    106 Thu Oct 12 11:54:58 EDT 2006 META-INF/MANIFEST.MF
    570 Thu Oct 12 11:55:00 EDT 2006 sun-ejb-jar.xml

  • Error when determining the PSA name

    I am on BW3.5, trying to load a delta that has been loading for 2+ years with no problems.  The load today is getting the error message:  "RSAODS 132 Error when determining the PSA name"
    I've looked in OSS Notes and there is nothing with this error message.  This is CCA Actual data that loads to PSA > ODS > Cube.  The PSA load is red and the entry in the ODS is also red.  Thanks

    Hello Keith,
    Not sure just check following, might help.
    This might be because of insufficent authorization ( did you changed anything on authorization company wide decision?)
    Or this might be brcause of insufficent tablespace or something?
    Sarhan.

  • Get the jndi names

    i have the next code for conect to one weblogic server.
    Properties p = new Properties();
    p.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.T3InitialContextFactory");
    p.put(Context.PROVIDER_URL, url);
    using the jndi name i can load the ejb but how can i list the jndi names?
    thanks

    I am using ejb 2, jdk 1.4.2 and weblogic 8.1 and for listing i haven't list() into the context.
    can you help me please?
    thanks

  • Can I disable the LCD screen from displaying the Network Name or Password of my device?

    Can I disable the LCD screen from displaying the Network Name or Password of my device?  I feel that having this information readily available to any who can turn on my device is a security flaw.
    I have change the network name and password and would like to secure that information .

    Worked with VZW tech support and finally found where you can disable or mask  the display of the network name and password on the Jetpack LCD screen.  You need to access the admin screen of your jetpack (http://my.jetpack/) .  From there, navigate to Jetpack Settings --> Click on Wifi tab -- Click on the Wi-Fi Options link halfway down the page and it will show the two settings that control the display of network name and password.
    As they say, a picture is worth a thousand words...here are screen shots showing how to get to these settings. ...
    The LCD display will show ********* for the network name and password if the two checkboxes above are unchecked. I really think these settings should be disabled to be begin with.
    Oh well...posting here to share with those interested...

Maybe you are looking for

  • The difference between itunes update and ipod update

    Could someone please tell me what the ipod updater is. Is this worth downloading? I thought you only updated itunes. Thanks, Gregg

  • JAXB Hashtable instead of List

    Hi, I'm new using JAXB, I apologize if it is a to basic question. I've already searched for a solution for the problem described below on google, and also on this forum with no success. I appreciate if someone could help me. First question: 1)What is

  • Add ability to select background display color for transparent areas of image

    Right now the background color for images with an alpha channel if always white.  This makes Bridge useless for sorting through images where the primary color is white.  It also looks like crap when you are doing a slideshow preview on a black backgr

  • NIKON NEF files corruption

    I have problem of NIKON NEF(NIKON D7000 CAMERA) files corruption after updating my MacAir to IOS Yosemite. I updated recently with latest Digital Raw Converter 9.06 but problem is still same. JPEG files are no problem. Any suggestion ho to solve? tha

  • Fix my crop tool in photoshop

    My crop tool does not work suddenly. When I go to select an area to crop and push "crop" in the menu the result is a tiny black square with nothing in it. Can you help? GEOME