SNMP implementation with EJB

Hi,
Can anyone help me in answering my below points with repect to SNMP and EJB communication arichecture.
1) I needs to indicate clearly the EJB container containing the Fault Managment application in EJB application.
2) The relationship of EJB Container and the EJB connecter
3) The connector of EJB and its relationship to SNMP manager APIs
4) The Manager APIs to SNMP agent.
Then it should clearly say the scaling by saying that Fault Management application deployment on multiple servers the how the EJB container to SNMP agent are affected
Please reply to these queries as soon as possible
Thanks,

Hi,
About the develop question please post to the MSDN forum.
MSDN forum Developer Network
http://social.msdn.microsoft.com/Forums/en-US/home?forum=WAVirtualMachinesVirtualNetwork&filter=alltypes&sort=lastpostdesc
Thanks for your understanding and support.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Error when run page with EJB + ADF

hello
when i run one page with EJB+ ADF give me this error:
<15/Set/2009 17H35m WEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1253032513131' for task '0'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(Application-EJBModel-ejb)
weblogic.application.ModuleException: Exception preparing module: EJBModule(Application-EJBModel-ejb)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     Truncated. see log file for complete stacktrace
Exception [EclipseLink-7161] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Entity class [class valtex.java.ejb.entities.Team] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then please make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.
     at org.eclipse.persistence.exceptions.ValidationException.noPrimaryKeyAnnotationsFound(ValidationException.java:1245)
     at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.validatePrimaryKey(EntityAccessor.java:1173)
     at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.process(EntityAccessor.java:486)
     at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.processORMMetadata(MetadataProcessor.java:443)
     at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:303)
     Truncated. see log file for complete stacktrace
>
<15/Set/2009 17H35m WEST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'Application'.>
<15/Set/2009 17H35m WEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(Application-EJBModel-ejb)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     Truncated. see log file for complete stacktrace
Exception [EclipseLink-7161] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Entity class [class valtex.java.ejb.entities.Team] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then please make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.
     at org.eclipse.persistence.exceptions.ValidationException.noPrimaryKeyAnnotationsFound(ValidationException.java:1245)
     at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.validatePrimaryKey(EntityAccessor.java:1173)
     at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.process(EntityAccessor.java:486)
     at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.processORMMetadata(MetadataProcessor.java:443)
     at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:303)
     Truncated. see log file for complete stacktrace
>
weblogic.application.ModuleException: Exception preparing module: EJBModule(Application-EJBModel-ejb)
#### Deployment incomplete. #### Sep 15, 2009 5:35:14 PM
oracle.jdeveloper.deploy.DeployException
     at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:247)
     at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.deployImpl(Jsr88RemoteDeployer.java:157)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:436)
     at oracle.jdeveloper.deploy.DeploymentManager.deploy(DeploymentManager.java:209)
     at oracle.jdevimpl.runner.adrs.AdrsStarter$5$1.run(AdrsStarter.java:1365)
Caused by: oracle.jdeveloper.deploy.DeployException
     at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:413)
     at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:238)
     ... 11 more
Caused by: oracle.jdeveloper.deploy.DeployException: Deployment Failed
     at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:395)
     ... 12 more
#### Cannot run application Application due to error deploying to DefaultServer.
[Application Application stopped and undeployed from Server Instance DefaultServer]
<15/Set/2009 17H43m WEST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
what's means this error???
thanks
Miguel Teixeira

I have a problem when running
the following is the error report
*** Using port 7101 ***
C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
WLS Start Mode=Development
CLASSPATH=C:\Oracle\MIDDLE~1\patch_wls1031\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\utils\config\10.3.1.0\config-launch.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.1.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.0/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDLE~1\JDEVEL~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar
PATH=C:\Oracle\MIDDLE~1\patch_wls1031\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.0\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Common Files\Nero\Lib\;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_11"
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) Client VM (build 11.0-b16, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Ddomain.home=C:\Users\ADMINI~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.07\DEFAUL~1 -Doracle.home=C:\Oracle\MIDDLE~1\JDEVEL~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Oracle\MIDDLE~1\JDEVEL~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.security.jps.config=C:\Users\ADMINI~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.07\DEFAUL~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\JDEVEL~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\JDEVEL~1\modules\oracle.oamprovider_11.1.1 -Dsso.filter.enable=true -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1031\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server
<23/09/2009 05:20:57 PM COT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_zh_TW.jar>
<23/09/2009 05:20:58 PM COT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 11.0-b16 from Sun Microsystems Inc.>
<23/09/2009 05:20:59 PM COT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.1.0 Wed Jun 10 22:24:41 MDT 2009 1227385 >
<23/09/2009 05:21:03 PM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<23/09/2009 05:21:03 PM COT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<23/09/2009 05:21:03 PM COT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<23/09/2009 05:21:03 PM COT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00007. Log messages will continue to be logged in C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
<23/09/2009 05:21:03 PM COT> <Notice> <Log Management> <BEA-170019> <The server log file C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
<23/09/2009 05:21:11 PM COT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<23/09/2009 05:21:13 PM COT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<23/09/2009 05:21:13 PM COT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\access.log00003. Log messages will continue to be logged in C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\access.log.>
<23/09/2009 05:21:17 PM COT> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddi was not deployed. Error: [Deployer:149158]No application files exist at 'C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\uddi.war'.>
<23/09/2009 05:21:17 PM COT> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddiexplorer was not deployed. Error: [Deployer:149158]No application files exist at 'C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\uddiexplorer.war'.>
<23/09/2009 05:21:20 PM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<23/09/2009 05:21:20 PM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<23/09/2009 05:21:23 PM COT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application HR_EJB_JPA_App is not versioned.>
23/09/2009 05:21:23 PM oracle.mds.internal.lcm.logging.MDSLCMLogger info
INFO: Identificador de Aplicación : HR_EJB_JPA_App
23/09/2009 05:21:23 PM oracle.mds.internal.lcm.logging.MDSLCMLogger info
INFO: "Servicios de Metadatos: Archivo de metadatos (MAR) no encontrado."
23/09/2009 05:21:23 PM JpsApplicationLifecycleListener Migrate Application Credential Store
ADVERTENCIA: Overwriting credentials is allowed in application credential store migration with Weblogic server running in Development Mode and system property 'jps.app.credential.overwrite.allowed' set to true
[EL Finer]: 2009-09-23 17:21:26.427--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Searching for default mapping file in file:/C:/Users/Administrador/AppData/Roaming/JDeveloper/system11.1.1.1.33.54.07/o.j2ee/drs/HR_EJB_JPA_App/HR_EJB_JPA_App-EJBModel-ejb/
[EL Finer]: 2009-09-23 17:21:26.481--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Searching for default mapping file in file:/C:/Users/Administrador/AppData/Roaming/JDeveloper/system11.1.1.1.33.54.07/o.j2ee/drs/HR_EJB_JPA_App/HR_EJB_JPA_App-EJBModel-ejb/
[EL Config]: 2009-09-23 17:21:26.53--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The access type for the persistent class [class oracle.Departments] is set to [FIELD].
[EL Config]: 2009-09-23 17:21:26.531--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The alias name for the entity class [class oracle.Departments] is being defaulted to: Departments.
[EL Config]: 2009-09-23 17:21:26.531--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The table name for entity [class oracle.Departments] is being defaulted to: DEPARTMENTS.
[EL Config]: 2009-09-23 17:21:26.534--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The access type for the persistent class [class oracle.Employees] is set to [FIELD].
[EL Config]: 2009-09-23 17:21:26.535--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The alias name for the entity class [class oracle.Employees] is being defaulted to: Employees.
[EL Config]: 2009-09-23 17:21:26.535--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The table name for entity [class oracle.Employees] is being defaulted to: EMPLOYEES.
[EL Config]: 2009-09-23 17:21:26.543--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The column name for element [private java.lang.String oracle.Employees.email] is being defaulted to: EMAIL.
[EL Config]: 2009-09-23 17:21:26.544--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The column name for element [private java.lang.Double oracle.Employees.salary] is being defaulted to: SALARY.
[EL Config]: 2009-09-23 17:21:26.544--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The target entity (reference) class for the one to many mapping element [private java.util.List oracle.Departments.employeesList] is being defaulted to: class oracle.Employees.
[EL Config]: 2009-09-23 17:21:26.544--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The target entity (reference) class for the many to one mapping element [private oracle.Departments oracle.Employees.departments] is being defaulted to: class oracle.Departments.
[EL Config]: 2009-09-23 17:21:26.545--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The primary key column name for the mapping element [private oracle.Departments oracle.Employees.departments] is being defaulted to: DEPARTMENT_ID.
[EL Config]: 2009-09-23 17:21:26.545--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The target entity (reference) class for the many to one mapping element [private oracle.Employees oracle.Departments.employees] is being defaulted to: class oracle.Employees.
[EL Config]: 2009-09-23 17:21:26.545--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The primary key column name for the mapping element [private oracle.Employees oracle.Departments.employees] is being defaulted to: EMPLOYEE_ID.
[EL Config]: 2009-09-23 17:21:26.545--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The target entity (reference) class for the one to many mapping element [private java.util.List oracle.Employees.departmentsList] is being defaulted to: class oracle.Departments.
[EL Config]: 2009-09-23 17:21:26.546--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The target entity (reference) class for the many to one mapping element [private oracle.Employees oracle.Employees.employees] is being defaulted to: class oracle.Employees.
[EL Config]: 2009-09-23 17:21:26.546--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The primary key column name for the mapping element [private oracle.Employees oracle.Employees.employees] is being defaulted to: EMPLOYEE_ID.
[EL Config]: 2009-09-23 17:21:26.546--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The target entity (reference) class for the one to many mapping element [private java.util.List oracle.Employees.employeesList] is being defaulted to: class oracle.Employees.
[EL Finer]: 2009-09-23 17:21:26.547--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Class [oracle.Departments] registered to be processed by weaver.
[EL Finer]: 2009-09-23 17:21:26.547--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Class [oracle.Employees] registered to be processed by weaver.
23/09/2009 05:21:34 PM oracle.mds.internal.lcm.logging.MDSLCMLogger info
INFO: Identificador de Aplicación : wsm-pm
23/09/2009 05:21:34 PM oracle.mds.internal.lcm.logging.MDSLCMLogger info
INFO: "Servicios de Metadatos: Archivo de metadatos (MAR) no encontrado."
23/09/2009 05:21:38 PM oracle.adf.share.config.ADFConfigFactory getInstance
INFO: ADF Config instance implementation in use is : oracle.adf.share.config.MDSConfigFactory
23/09/2009 05:21:46 PM oracle.adf.mbean.share.connection.ConnectionsRuntimeMXBeanImpl getNonCachedConnectionsContext
INFO: Registering Connection Runtime MBean
23/09/2009 05:21:46 PM oracle.adf.share.jndi.MDSBackingStore isReadOnlyMDSStore
INFO: Read only backing store
23/09/2009 05:21:47 PM oracle.adf.share.jndi.MDSBackingStore isReadOnlyMDSStore
INFO: Read only backing store
23/09/2009 05:21:47 PM oracle.adf.share.jndi.MDSBackingStore isReadOnlyMDSStore
INFO: Read only backing store
<23/09/2009 05:21:50 PM COT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<23/09/2009 05:21:50 PM COT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log00006. Log messages will continue to be logged in C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log.>
<23/09/2009 05:21:50 PM COT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
23/09/2009 05:21:51 PM oracle.wsm.audit.Auditor <init>
INFO: Created J2EE application auditor for componentType=oracle.security.jps.internal.audit.AuditServiceImpl$Auditor@213b6e
23/09/2009 05:21:55 PM oracle.adf.share.config.ADFMDSConfig parseADFConfiguration
INFO: Configuration file:/META-INF/adf-config.xmlcannot not be read by MDS. Reading directly from the classpath
<23/09/2009 05:21:55 PM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<23/09/2009 05:21:55 PM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default[6]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on fe80:0:0:0:246d:98bd:32fc:bf08:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:790b:d0ee:a329:57db:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on 0:0:0:0:0:0:0:1:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:28a5:117:3611:5367:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:0:5efe:c0a8:66:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.0.102:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
<23/09/2009 05:21:55 PM COT> <Warning> <Server> <BEA-002611> <Hostname "Crht-PC", maps to multiple IP addresses: 192.168.0.102, fe80:0:0:0:246d:98bd:32fc:bf08%12, fe80:0:0:0:28a5:117:3611:5367%13>
<23/09/2009 05:21:56 PM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<23/09/2009 05:21:56 PM COT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
[Running application Application9 on Server Instance DefaultServer...]
DefaultServer startup time: 64580 ms.
DefaultServer started.
<23/09/2009 05:22:08 PM COT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Application9 is not versioned.>
23/09/2009 05:22:08 PM JpsApplicationLifecycleListener Migrate Application Credential Store
ADVERTENCIA: Overwriting credentials is allowed in application credential store migration with Weblogic server running in Development Mode and system property 'jps.app.credential.overwrite.allowed' set to true
<23/09/2009 05:22:09 PM COT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1253744528059' for task '0'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(Application9-Project1-ejb)
weblogic.application.ModuleException: Exception preparing module: EJBModule(Application9-Project1-ejb)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:454)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     Truncated. see log file for complete stacktrace
Exception [EclipseLink-28010] (Eclipse Persistence Services - 1.1.1.v20090430-r4097): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: PersistenceUnitInfo Project1 has transactionType JTA, but doesnt have jtaDataSource.
     at org.eclipse.persistence.exceptions.EntityManagerSetupException.jtaPersistenceUnitInfoMissingJtaDataSource(EntityManagerSetupException.java:154)
     at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:798)
     at org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactory(PersistenceProvider.java:216)
     at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:343)
     at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:323)
     Truncated. see log file for complete stacktrace
>
<23/09/2009 05:22:09 PM COT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'Application9'.>
<23/09/2009 05:22:09 PM COT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(Application9-Project1-ejb)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:454)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     Truncated. see log file for complete stacktrace
Exception [EclipseLink-28010] (Eclipse Persistence Services - 1.1.1.v20090430-r4097): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: PersistenceUnitInfo Project1 has transactionType JTA, but doesnt have jtaDataSource.
     at org.eclipse.persistence.exceptions.EntityManagerSetupException.jtaPersistenceUnitInfoMissingJtaDataSource(EntityManagerSetupException.java:154)
     at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:798)
     at org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactory(PersistenceProvider.java:216)
     at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:343)
     at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:323)
     Truncated. see log file for complete stacktrace
>
[05:22:09 PM] Weblogic Server Exception: weblogic.application.ModuleException: Exception preparing module: EJBModule(Application9-Project1-ejb)
[05:22:09 PM] Caused by: java.lang.Throwable: Substituted for missing class Exception [EclipseLink-28010] (Eclipse Persistence Services - 1.1.1.v20090430-r4097) - org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: PersistenceUnitInfo Project1 has transactionType JTA, but doesnt have jtaDataSource.
[05:22:09 PM] See server logs or server console for more details.
oracle.jdeveloper.deploy.DeployException: oracle.jdeveloper.deploy.DeployException: oracle.jdeveloper.deploy.DeployException: Deployment Failed[05:22:10 PM] #### Deployment incomplete. ####
oracle.jdeveloper.deploy.DeployException: oracle.jdeveloper.deploy.DeployException: oracle.jdeveloper.deploy.DeployException: Deployment Failed
     at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:341)
     at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.deployImpl(Jsr88RemoteDeployer.java:235)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:442)
     at oracle.jdeveloper.deploy.DeploymentManager.deploy(DeploymentManager.java:209)
     at oracle.jdevimpl.runner.adrs.AdrsStarter$6$1.run(AdrsStarter.java:1469)
Caused by: oracle.jdeveloper.deploy.DeployException: oracle.jdeveloper.deploy.DeployException: Deployment Failed
     at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:483)
     at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:332)
     ... 11 more
Caused by: oracle.jdeveloper.deploy.DeployException: Deployment Failed
     at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:465)
     ... 12 more
#### Cannot run application Application9 due to error deploying to DefaultServer.
[Application Application9 stopped and undeployed from Server Instance DefaultServer]
Please help me!!
thnks!!

How to use ADF Query search with EJB 3.0

Hi,
In ADF guide http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/web_search_bc.htm#CIHIJABA
The steps to create query search with ADF Business Components says:
"+From the Data Controls panel, select the data collection and expand the Named Criteria node to display a list of named view criteria.+"
But with EJB, I'm not able to find Named Criteria node. Can we use ADF query search component with EJB? If yes, can you please show me some example, tutorial etc.?
Thanks
BJ

For EJBs you'll need to implement the query model on your own.
An example of how the model should look like is in the ADF Faces components demo.
http://jdevadf.oracle.com/adf-richclient-demo/faces/components/query.jspx
Code here:
http://www.oracle.com/technology/products/adf/adffaces/11/doc/demo/adf_faces_rc_demo.html

Bean-managed transaction with EJB 3.0

Hi,
I try to get a bean-managed transaction example running with EJB 3.0 under GlassFish v2ur2.
In order to demarcate the scenario I have to get me the UserTransaction which I get from the SessionContext. I would like to use it then like: UserTransaction ut = context.getUserTransaction();
I tried to get the SessionContext with the help of the EJB method setSessionContext which should be called by the container after instance creation.
However, setting a log output into that method does not show any call of this method.
So, how can I get this method called or is there another way to get the SessionContext for the UserTransaction to work ?
Are there any good and fully implemented examples for bean-managed transactions ?
Thanks for your help.
Regards

I found the solution for that my SessionContext was NULL and I could not use the UserTransaction.
The reason for it is that I injected the EJB with @EJB into my servlet and did a MyBean mybean = new MyBean();
That leads to a SessionContext which is NULL within my EJB.
If I use it without instantiating it it works fine.
Again, thanks for your help. At least it pointed me into the right direction.
Regards

JSF combined with EJB, how??

Hi @ll,
I have been trying for some days to combine my JSF pages with EJB Session Beans, but I haven't really found a working way to do it.
First, I had my session bean directly as the backing bean for the JSF page, but I read somewhere that this isn't "allowed", so I created a helper bean as managed bean. This is now the backing bean for the jsf page and has as attribute the session bean.
My helper bean:
public class ManagedHelperBean {
@EJB private JDDACReaderBeanRemote reader;
public JDDACReaderBeanRemote getReader() {
     return reader;
public void setReader(JDDACReaderBeanRemote reader) {
     this.reader = reader;
}Part of my faces-config.xml
<managed-bean>
<managed-bean-name>helper</managed-bean-name>
<managed-bean-class>com.company.ManagedHelperBean</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>Part of my jsp page:
<h:outputText value="#{helper}"/>
<h:outputText value="#{helper.reader}"/>Now, the first output in the jsp page works, the second one doesn't. Why can't the property reader be accessed?? What is the correct way to combine JSF with EJB?
Kind regards,
Wiebke

Hello,
I faced the same problem, but on a Weblogic 10 server.
The problem with Weblogic 10 is, even if it's "supposed" to be a EE5 compliant server, it is not.
As described here http://e-docs.bea.com/wls/docs100/webapp/annotateservlet.html , there is no Dependency Injection in JSF managed beans:
The web container will not process annotations on classes like Java Beans and other helper classes.
But, WL 10 offers DI on Servlets, Filters and Listeners.
Here is how I solved it (probably not the best way, but it works for me):
- created a filter with a list of EJB injected (as it works). For every filtered request, set a list of known (enum) as request attributes mapped each to a EJB service:
public class EJBInjectFilter implements Filter {
@EJB
private MyEJBService ejbRef;
public void doFilter(ServletRequest req, ServletResponse resp, FilterChain chain) throws IOException,
               ServletException {
log.debug("Setting EJB ref into request as attribute ");
          req.setAttribute(ServiceEnum.MY_EJB_SERVICE.toString(), ejbRef);
          chain.doFilter(req, resp);
- for every managed bean who needs a service you can do something like:
(MyEJBService) ((HttpServletRequest) FacesContext.getCurrentInstance().
               getExternalContext().getRequest()).getAttribute(ServiceEnum.MY_EJB_SERVICE.toString())
to get a reference to service.
I agree it is a totally not elegant solution. But why does WL 10 say it's a full JEE5 compliant server, and though does not provide DI for managed beans?
A drawbacks I could think of is performance slow-down (for every request, apply filter, set list of attributes + references into request) - probably it does take some time.
Let me know your thoughts.
Edited by: cosminj on Nov 20, 2007 8:16 AM

JSF with EJB

Hi,
I am new to JSF. I was wondering if anyone can shed some light on how to use JSF in J2ee environement? Will it be ActionListener's responsibility to update the model (communicate with EJB's)?
Any help will be highly appreciated.
Thanks,
Paresh

Hi,
I am new to JSF. I was wondering if anyone can shed
some light on how to use JSF in J2ee environement?
Will it be ActionListener's responsibility toupdate
the model (communicate with EJB's)?
Any help will be highly appreciated.
Thanks,
PareshThere are of course many ways to address this
question.
I susspect the most common will be an Action's invoke
method calling methods on a Session Facade [Core J2EE
Patterns].
So for example
public String invoke() {
// get myHome from a Service Locator [Core J2EE
E Patterns]
MyFacade facade = myHome.create();
facade.doTheBizLogic(...);
facade.remove();
Hope this helps.
-bd-This is indeed the sort of pattern that I expect will be quite popular. The nice thing is that it works for business logic implemented as EJBs, or as POJOs (plain old Java objects), or any other way that you like.
From an architectural perspective, you'll do yourself a favor by isolating the functional part of your business logic into classes that do not depend on any given UI technology (i.e. the process of adding a new order for a particular customer is the same whether it's done in a client/server app based on Swing, a web application based on JavaServer Faces, or a web service based on JAX-RPC). Design your business logic so that it can be reused in any such environment.
Craig McClanahan

Implicitly Passing a Custom Context with EJB Invocations

Dimitri, this is most likely one for you.
We have a need to implicitly pass contextual information with EJB
invocations. I'd also like to be able to intercept/filter invocations.
The current approach autogenerates subclasses for the bean
implementations. In these subclasses, the methods take an additional
context parameter. From the client perspective, the business delegates
implicitly provide this parameter.
I'd like to solve this without code generation.
The current approach I'm considering is to have a generic command EJB.
This stateless session bean will take a method signature, method
parameters, and a context object. The command EJB will delegate these
invocations to the actual EJBs.
I will get the client to go through this command EJB by intercepting the
home lookups. I will wrap the initial context. Using dynamic proxies,
the new initial context will return a wrapped stub that will actually go
through the command bean, implicitly passing the thread local context.
So far as the command bean's configuration goes, I will set to the pool
size very high (the sum of all of the other stateless session bean pool
sizes perhaps). I will set the transaction type to Supports and pass on
any exceptions.
Can anyone think of a better way to go about this?
Thanks,
Bob

Why do you need the custom context? I have worked with an application that held the SessionContext and wrapped all the methods of the EJB context. This was a maintenance problem because changes to the EJB spec caused the methods to change and therefore the calling code.
Are you trying to insulate your POJO code from EJB specific classes?

Smart Card application with EJB?

Hallo
I have the following problem:
I have to write an application which should be accessible from the internet. The whole application has to be on the server. Every user who wants to get access to the application has to insert a smartcard into the Reader who is installed on his local system. The application has to read some information (username or password for example) from the card and to prove if the user is allowed to start the Application.
Does anybody has an idea how to realize this? Is it possible to realize this with EJB or do i have to use an other technology?
Thanks for your answers

Well i did not use the java smart card technology. I used the Java native interface to implement the classes who have to read from the card. I got an api dll from the producer of the smart card. So i used the Java native interface to realize the logic of the smartcard application. This part of my programm is written in c++. The problem is that the whole programm is on a server but for getting access to the smartcard reader the dll s (the api dll from the producer and my dll for the jni) have to been installed on every client......
You said that i have to write a swing client who picks the information from the smartcard and sends it afterwards to the enterprise system. Is there no other possibility to solve this problem without writing a swing client ?

SNMP Implementation in JAVA

Hi,
I am doing a project on the implementation of SNMP in a lan.Though I know about SNMP,yet I am not getting any idea as how should I proceed.I have to implement it in java.Thanks for any help.
Regards,

Have a look at snmp4j, it works fine.
Here's another, joesnmp.Thanks for that link; strangely enough I didn't find that one when I googled
quite a bit for Java snmp implementations. I played with the code a bit
and I feel tempted to say that I prefer it over the snmp4j implementation,
but the documentation is a big show stopper. Or maybe I'm too thick to
find that either using google? (hint, hint ;-)
kind regards,
Jos

Implementation of EJB

I need some help with EJBs:
I can implement a Session EJB (in the admin console) and add it with no problems in "EJB -> add Set of Session EJBs"
I create a wrapper for that EJB (drag&drop in Page1) and use it.
If I modify the EJB (add a method) and implement it again (after I remove the old one), I can't use the new method...it appears in the list of methods but I can't bind it to a Table for example (it returns an ArrayList).
If I create a new project I can perfectly use that new method.
[sorry for my awful English]
Mono.

Well, after hours, here is one posible solution:
To make the JSC recognize the modification made on an EJB you should:
- Not undeploy the old EJB, redeploy it instead.
- In the servers tab, refresh the Set of Session EJBs that contains your EJB.
- Drag and drop in the page one of the new methods you added, JSC will create a new EJB client.
- Delete the old EJB Client and change the new one's id to replace it. (Do not touch any of your datasources, because if you do you will loose all your references to the EJB).
- Clean and rebuild your project.
- Done!. You can now use your new methods!
Mono.
[Thx to MAL & JPB]

SNMP integration with ISE 1.2

Hi Guys,
Did anyone have a hard time integrating ISE 1.2 with SNMP server for polling system parameters? I'm trying to add ISE 1.2.1 to solarwinds SNMP server but when adding the required parameters like IP address and community string and doing an SNMP test connection it returns a failure message. SNMP configuration on ISE is quit simple. Only two commands are needed which are the SNMP server IP and community string values. Searching on the web, i saw a bug CSCun42967 that documents SNMP problems with ISE 1.2. Could that be the problem? or if there is any limitations for this integration?
Thanks,
Mohammad

Here is the helpful link :
https://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_sw_cnfg.pdf

How to know if implementation with a filter value exist for a BAdI in code?

Hi all,
Scenario:
I created a BAdI. There will be a button on the UI to call its implementation(s); while if there is no implementation with specified filter value, this button needs to be hidden. Thus I need to know if the implementation exist before calling it.
Question:
In the ABAP code, how to get whether implementation with specified filter value exists for a BAdI?
If it's possible, please help provide code.
Thanks and regards,
Said

Problem solved:
data: r_badi type ref to YOUR_BADI,
          badi_impl_num type i.
get badi r_badi
    filters
      flt_name = fit_val.
badi_impl_num = cl_badi_query=>number_of_implementations( badi = r_badi ).
if badi_impl_num > 0.
    "there are badi implementation(s)
endif.

Problem with EJB skeleton classloader

Hi
We have been migrating an enterprise application from Weblogic 7 to 9.2 and experienced strange problem with EJBs. Our EAR contains (beside the other elements) an EJB module with EJBs and some common POJO classes inside. At the deploy and run phase everything seems working fine, but when the remote client invokes a method which receives one of the common classes as a parameter we get ClassNotFoundException on the server side (talking precisely, the exception is thrown from the EJB skeleton, trying to unmarshall the parameter).
It seems that our EJB's skeletons do not see the classes from EAR. We have tried moving the common classes to the APP-INF/lib directory or placing them at the root of EAR archive and adding reference in Manifest file of EJB module and it won't help.
The only workaround we've found is to add the missing classes to the server classpath but this is unacceptable (however, it works).
We are not using any custom classloader hierarchy.
The other JARs have no problem loading the content of our EJB module (including the common classes, which cause the problem).
So, why is the RMI classloader ommiting our application contents?

The problem was fixed by upgrading to version 9.2.1

How to master good design with EJB and JSP?

I use JSP to calling EJB. But the .jsp file is complex and it's difficult to maintain...I just want to work higher efficent with EJB,JSP and JavaBean. I want to know is there a good design with EJB and JSP? and is there any good material about MVC for EJB,JSP and JavaBean?

You should read the J2EE blueprint available on this website. Better download the PDF, and print it for yourself so you can read it anytime.

Creating library file with ejb

Can anyone suggest me the process by which we can create a library file with ejb? I am new to the ejb environment and i need some guidance regarding this.

Could you be more specific about what you mean by library file? Are you asking about how to package classes used by ejb components outside of the ejb-jar itself?
--ken

SNMP implementation with EJB

Similar Messages

Maybe you are looking for