Deployment choices for EJBs

I'm very new to EJBs and reading as quickly as I can. I'd like to know if any rules of thumb exist for EJB deployment architectures. Particularly, at the moment our EJBs are for database access from a remote computer. Do I have a single generalized EJB for database access? Or do I have a separate EJB for each specific database access? Do I have JSP on the web server talk directly to the EJB, or do I introduce some intermediate object, and if so, what kind? Are there any design white papers I can read? None of the books I've bought on EJBs discuss these implementation details.

I also have the same questions in my mind. Can someone advice?

Similar Messages

Jdev hangs while trying to create deployment profile for EJB from ADF BC.

Hi,
I created some ADF BC and try to create the deplyment profile as EJB session Beans
however it is not saving and while trying to deploy it to satandalone OCJ I got some errors
atht classes EJB are missing.
Please advise.
Thanks
JO

Hello JO,
Is the version of your stand alone OC4J compatibile with JDeveloper you are using?
e.g.: JDev 10.1.3 is certified with OC4J 10.1.3
Did you install the ADF runtime ?
e.g.: from the menu, Tools -> ADF runtime installer -> stand alone OC4J
What is the exact error which is displayed ?
Stephan

Strange exception when deploying BC4J as EJB in 8i CORBA.BAD_PARAM: null Strings are

I am trying to deploy BC4J as Ejb to 8i (8.1.6). I use the following deployment method with j: my Jdev root.
setjboenv j: ejb8i
loadjava - u user/passwd@host:port:sid - thin -v - r grant "SYS,PUBLIC" j:lib\xmlparserv2.jar
loadjava - u user/passwd@host:port:sid - thin -v - r grant "SYS,PUBLIC" j:lib\jbomt.zip
loadjava - u user/passwd@host:port:sid - thin -v - r grant "SYS,PUBLIC" j:lib\jboejb.jarI then create a deployment profile for ejb 8i with the ide. (Without deploying)
I then use loadjava outside the IDE to deploy the 2 jar files created
MyProject1CommonEJB.jar
and
Myproject1.jar
I then use the ide again to deploy the bean profile
Package1ModuleServerEJB.prf
The last step fails with the error :
Publishing EJBHome...org.omg.CORBA.BAD_PARAM: null Strings are illegal in IIOP. Please correct your application or run the ORB in backward compatibility mode. minor code: 0 completed: No
void oracle.aurora.ejb.deployment.GenerateEjb.invoke()
void oracle.aurora.server.tools.sess_iiop.ToolImpl.invoke(java.lang.String[], java.io.InputStream, java.io.PrintStream, java.io.PrintStream)
void oracle.aurora.ejb.deployment.GenerateEjb.main(java.lang.String[])
Exception in thread main
Strangely, when I test this EJB with the tester (middle tier = remote ejb) it works, but from JSP's I get an application error : "Unknown Exception"
I am using Jdev 3.1
Also using the deploy option when creating the deployment profile fails apparantly due to the missing grant "SYS,PUBLIC" when loading classes to the database before deploying the bean.
What can be done ?
null

Hi Blaise
Thanks for the reply. I have tried to do the complete deployment from within Jdev, but now I get the following error right at the end of the deployment.
/BC4J1AppModuleEjb/EjbObject_RemoteBC4J1AppModuleEjb:ORA-29535: source requires recompilationjava.lang.NullPointerException at sun.tools.java.Environment.error(Environment.java) at sun.tools.java.Environment.error(Environment.java) at sun.tools.java.Environment.error(Environment.java) ..... etc.
I have tried to deploy to a clean schema with the java privilages granted as described in the Jdev release notes.
I included the following libraries in my project :
JBO JDBC816 PATCH
JBO OSQL Domains
JDeveloper Runtime
Oracle 8.1.6 JDBC
Connection Manager
JBO Runtime
JBO VB Runtime
JBO 8i Runtime
SQLJ Runtime
JBO 8i Client
JBO Vanilla Domains
JBO EJB Runtime
JServer
Oracle XML SQL Utility
ORACLE XML Parser 2.0
Then I just used the deployment wizzard
null

Deployment profile for a business component deployed to 9ias?

I am trying to build a deployment profile so I can deploy my business component to an oc4j instance on my remote 9iAS machine.
In jdeveloper version 9.0.3, the "Business Component Deployment Wizard for EJB session bean" prompts for a both a "Deploy to Connection" and a "Server Connection".
I am specifying a connection to a "9i Application Server - Remote DCM" for the <deploy to connection> prompt. Per the documentation and the wizard .. you must then specify a server connection.
I don't understand the server connection piece ... The <new button> for the "server connction" only lets me build a connection a standalone OC4J. I am trying to deploy to a 9ias oc4j instance on a remote machine. I am suppose to somehow specify a connection to the remote 9ias oc4j instance as if it were a standalone instance? How do I build and specify this connection?

Thanks Frank.
My jdevloper help system describes how to deploy to 9ias, and I have not yet spotted anything in the fine print that nullifies this.
The release notes that came with Jdeveloper version 9.0.3.10.35 show a compatibility matrix for deployments to 9ias version 9.0.3 ... my scenario is listed as supported. They note that deployment to 9ias 9.0.2 of bc4j is not suported, and J2EE/WebServices deployment has DCM issues.
FYI ... I have a TAR openned on this subject, and Metalink support personnel seems to be pretty close to declaring this a bug (internal bug#2597292 and internal bug#2495251). Specifically these bugs relate to JBO component versions 9.0.3.9.51 and 9.0.3.10.12 in reagrds to DCM connections to 9ias. If this is the case then it looks like 9iAS deployment is not supported.

EJB deployment error for Weblogic server 9.2 mp4

Hi,
While trying to deploy a small EJB jar file which uses EJB 2.1 CMP beans with relationships, getting the following error from Weblogic server 9.2 MP4:
=================================================================================================
<Error> <EJB> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988333> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
>
####<Nov 1, 2011 4:09:48 PM IST> <Error> <Deployer> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988380> <BEA-149265> <Failure occured in the execution of deployment request with ID '1320143984947' for task '1'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:382)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
=================================================================================================
While I'm able to deploy without the CMP 1-1 relationship, the moment I introduce the 1-1 relationship, I get this error. Database used is Oracle 10g XE.
I have been battling this error for more than a day now. Kindly help me fix this.
Thanks in advance!
Regards,
Vinod

Hi,
I was able to figure out the root cause. I was using the primitive data type "int" for primary key and foreign key for one of the beans in the relationship. After I changed it to "Integer" wrapper type, the issue got resolved.
-Vinod

BEA-012036 Too Many Files | Weblogic Start Up for EJB deployment

Trying to deploy EAR with EJB module inside. I am seeing the below error intermittently while deploying and now starting the weblogic server .
There is already an EAR deployed with all the Shared Libraries under APP-INF/lib. I deployed a new EAR with all the similar common shared libraries ( APP-INF/lib jar files ) packaged inside this new file.
<Apr 28, 2009 7:45:18 PM EDT> <Error> <EJB> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:
/prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.java:17: error while writing com.test.xxx.ejb.rtmschema.CreditserviceSessionEjb_f0jmmq_Impl: /prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.class (Too many open files)
(source unavailable)
1 error
>
<Apr 28, 2009 7:45:19 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'xxx-ear-ejb4' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(xxx-ejbschema-service.jar)
Unable to deploy EJB: xxx-ejbschema-service.jar from xxx-ejbschema-service.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
/prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.java:17: error while writing com.test.xxx.ejb.rtmschema.CreditserviceSessionEjb_f0jmmq_Impl: /prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.class (Too many open files)
(source unavailable)
1 error
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:343)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:533)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:500)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:476)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:798)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1234)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.application.ModuleException: Exception preparing module: EJBModule(xxx-ejbschema-service.jar)
Unable to deploy EJB: xxx-ejbschema-service.jar from xxx-ejbschema-service.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
/prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.java:17: error while writing com.test.xxx.ejb.rtmschema.CreditserviceSessionEjb_f0jmmq_Impl: /prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.class (Too many open files)
(source unavailable)
1 error
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:343)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:533)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:500)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:476)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:798)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1234)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
Truncated. see log file for complete stacktrace
java.io.IOException: Compiler failed executable.exec:
/prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.java:17: error while writing com.test.xxx.ejb.rtmschema.CreditserviceSessionEjb_f0jmmq_Impl: /prod/xxxx/prd/server/dev_xxxx/servers/mt_crd_180_15001/cache/EJBCompilerCache/f6yuykfqdn7i/com/test/xxx/ejb/rtmschema/CreditserviceSessionEjb_f0jmmq_Impl.class (Too many open files)
(source unavailable)
1 error
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:343)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:533)
Truncated. see log file for complete stacktrace
Thanks
Abhi

Put only files which needs to be 'shared' ( e.g persistent store files for jms, jta transaction store etc) on the network drive .. put all other files including logs on the local disk.. see if that makes a difference..
NAS is slower than other storage setups like SAN and DAS...

Weblogic Deployment Descriptor for CMP EJB

Hi all,
Am new to EJB, CMP. Pls help me how to write deployment descriptors for the CMP EJB for Weblogic.
Give me the list of the Deployment descriptors needed and also pls give me some samples
thanks in advance
rgds
Ravi Bharathi

The easiest way is to go through some tutorial or refer the code samples. If you have installed weblogic, there are examples provided in the weblogic installation folder itself for each type of bean. Basically for cmp you have to provide the table names and mapping between the class variables to db fields in weblogic_cmp_rdbms.xml deployment descriptor.

Error in deploying a simple EJB 3.0

Hi ,
I am getting the following error while deploying my simple ejb of version 3.0 in Weblogic 9.2.
Exception preparing module: EJBModule(build) [EJB:011023]An error occurred while reading the deployment descriptor. The error was: Error processing annotations: java.lang.NullPointerException.
During my evaluation of Weblogic 9.2 for EJB 3.0 , I have got the following questions.
EJB Specification states that EJB's in EJB 3.0 can be developed and deployed without the need of deployment descriptors. I have created a simple EJB with two file Env.java and EnvBean.java and the source code is given below.
a) I just complied these class files and when I was trying to deploy without ejb-jar.xml and weblogic-ejb-jar.xml, the console was not at all allowing me to deploy.Why is this so?
b) After I created a META-INF file under root of classes directory by placing ejb-jar.xml with empty <enterprise-beans> element, console was allowing me to deploy with errors in parsing ejb-jar.xml. The error was either session/entity/mdb is a required under <enterprise-beans> element. Why is this required when there are several examples stating <enterprise-beans> element can be empty.
c) Later I updated ejb-jar.xml with <session> element under <enterprise-beans> with the following values. I got the above error when deployed with this change.
I had been struggling to deploy this simple bean for almost a day.Pleas point me if there is any documentation that solves my stated problem or if there is a solution.Thanks in advance.
regards
Karim
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" version="3.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
<enterprise-beans>
<session>
<description>This is the stateless ejb</description>
<display-name>Env Bean</display-name>
<ejb-name>EnvBean</ejb-name>
</session>
</enterprise-beans>
</ejb-jar>
Env.java
package examples ;
public interface Env {
public void display();
EnvBean.java
package examples;
import javax.ejb.Remote;
import javax.ejb.Stateless;
@Stateless
@Remote(Env.class)
public class EnvBean implements Env {
public void display() {
System.out.println("Welcome to EJB 3.0");
}

Presumably you're using the EJB3 tech preview, and not a vanilla WebLogic 9.2 install, right?
Can you post the full stack trace?
-Patrick

Deploying third party EJB 3.0 jar in web application

I have a web application which calls services provided by EJB 3.0 beans packaged in third party jar. How do a configure the web application project to deploy the beans to the embedded OC4J container when I run the application? The jar file is reference by the project, and I have a META-INF/application.xml referencing those jar files as EJB modules. I've set the EJB Version property to 3.0, but the Annotated EJB 3.0 Bean Classes list remains empty, presumably because I have no beans defined in the sources of the application. When running the project, the oc4j container warns that the EJB module contains no beans. I'd like to deploy the beans in the jar file, but can't figure out how.
Thanks,
Steve
JDeveloper 10.1.3.4
Windows Vista
Edited by: user10375549 on Oct 29, 2009 6:38 AM - Fixed typo.

I don't think this technique will work. I added a META-INF/ejb-jar.xml file to the application, and added a <session> section for one of the EJB 3.0 beans from my third party jar. I specified values for <ejb-name>, <ejb-class>, and <session-type> hoping the rest of the configuration would be determined from the annotations in the class. When the server starts, this warning message is displayed:
Oct 30, 2009 12:06:41 PM com.evermind.server.ejb.logging.EJBDeploymentMessages warningSessionBizInterfaceNotDefined
WARNING: \[current-workspace-app: ... \] - The session bean does not has at least one business interface defined for client access. The bean is not accessiable and usable at runtime.
Ready message received from Oc4jNotifier.
Embedded OC4J startup time: 11042 ms.
\[sic\]
EJB 3.0 beans are not required to define business interfaces, as they are supposed to be generated by the container.
Good idea, but still cannot deploy beans from the third party EJB 3.0 jar referenced by my project to the embedded OC4J container. Still investigating.
Thanks,
Steve
By the way, I have been able to use your technique to deploy EJB 2.1 beans from third party jars in other projects, just not EJB 3.0 beans that do not provide ejb-jar.xml deployment descriptors, nor business interfaces.
Edited by: user10375549 on Oct 30, 2009 9:51 AM - Added relevant comment regarding technique described for solving problem. It works for EJB 2.1 beans but not EJB 3.0 beans.

JNDI Lookup in JSP fails for EJB 3.0

I am new to Java technology. I read the EJB FAQ, NetBeans docs and may forum discussions and I am still confused with the error I am having.
Background:
I have developed a persistance bean and related sessions beans (similar to the customer-cmp-ear application in the Java App Server samples). Now I am trying to access this bean using a JSP. After deploying the war file in the App Server and try to access the page, I get the following error.
javax.naming.NameNotFoundException: No object bound to name java:comp/env/ConsumerSessionLocal
After reading many articles, I understood that I dont have to prepare any descriptors, or JAR files for EJB 3.0.
Environment Details:
Java App Server Ver 9.0
NetBeans 5.5
I normally build the war files using NetBeans.
I use App Server Admin console to deploy the web applications using the above war file.
EJB details:
Persistance EJB : person.java
Session Objects
Consumer.java (this implements ConsumerSessionLocal, ConsumerSessionRemote). This Stateless bean accesses the methods in person.java.
ConsumerSessionLocal.java - local interface
ConsumerSessionRemote.java - remote interface
SearchConsumer.jsp
This JSP page is calling the ConsumerSessionLocal using the JNDI lookup through InitialContext.
Here is the Code snippet:
try {
InitialContext ic = new InitialContext();
Object o = ic.lookup("java:comp/env/ConsumerSessionLocal");
ConsumerSessionLocal consSession = (ConsumerSessionLocal) o;
I am able to see the jsp page in the browser, however, after a submit action, I get the Java Naming Exception error.
javax.naming.NameNotFoundException: No object bound for java:comp/env/ConsumerSessionLocal
I would appreciate your help/any of your thoughts.
Thanks in advance.
-Ram

I did not really solve it. Instead I used some of the tutorials that used JNDI lookup and modified those as my way forward. I did not really find out exactly what I was doing wrong.
/Anders

Problems deploying a simple EJB

I am trying to deploy a simple EJB on the 8.1.5. The bean only owns a single method that needs a unique parameter.
No problems with compilation of source bean, home and remote interfaces, whatever the type of this parameter is.
But when I try to deploy the jar on the server, I only succeed if the parameter of my method is a simple type (int, String ...).
If I try the same passing a complex type (here a oracle.xml.parser.v2.XMLDocument type), I encounter this message from the deployejb tool :
Generating EJBHome and EJBObject on the server...
Compilation errors in oracle/aurora/ejb/gen/test_myFluxInsert/EjbObject_FluxInsert:ORA-29535: source requires recompilationjava/lang/Object: Authorization error for referenced class Oracle/xml/parser/v2/XMLDocument.java/lang/Object: Authorization error for referenced class oracle/xml/parser/v2/XMLDocument.oracle/aurora/ejb/gen/test_myFluxInsert/EjbObject_FluxInsert:50: Class oracle.xml.parser.v2.XMLDocument not found in type declaration.
public java.lang.String insereFlux (oracle.xml.parser.v2.XMLDocument arg0)
^ Info: 3 errors
And if I use an int instead of the XMLDocument parameter, everithing's right.
Can anybody submit a no-paranormal solution ?
Thanks.
GH

Parameter passing in EJB must implement Serializable. One way to solve this is:
1. Define a new class which implements
Serializable.
2. Place whatever you want to pass inside
this class.
3. Now use the new class as your parameter.
eg.
public class Params implements java.io.Serializable {
String p1;
XmlDocmuent xdoc;,
etc, etc
Your program now have to use the class Params for parameter passing.
Hope this helps.
Tam
null

Error while using LiveCycle java APIs with Http servlets:"Remote EJBObject lookup failed for ejb/Inv

Hi all,
When i try to run more than one servelt of the Quick Start samples that using Livecycle Java APIs and i get an error of "Remote EJBObject lookup failed for ejb/Invocation provider" from any servelt i run.
I try some Quick samples which is not servelts (java class) and it works fine, which makes me sure that my connection properties is true.
Environment:
The LiveCycle is based on "Websphere v6.1", and i use "Eclipse Platform
Version: 3.4.1".
i install "tomcat 5.5.17" to test the servelts in developing time through Eclipse.(only for test in developing time not for deploy on )
The Jars i added in the classpath:
adobe-forms-client.jar
adobe-livecycle-client.jar
adobe-usermanager-client.jar
adobe-utilities.jar
ejb.jar
j2ee.jar
ecutlis.jar
com.ibm.ws.admin.client_6.1.0.jar
com.ibm.ws.webservices.thinclient_6.1.0.jar
server.jar
utlis.jar
wsexception.jar
My code is :
Properties ConnectionProps = new Properties();
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_DEFAULT_EJB_ENDPOINT, "iiop://localhost:2809");
ConnectionProps.setProperty ServiceClientFactoryProperties.DSC_TRANSPORT_PROTOCOL,ServiceClientFactoryProperties.DSC_ EJB_PROTOCOL);
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_SERVER_TYPE,ServiceClientFa ctoryProperties.DSC_WEBSPHERE_SERVER_TYPE);
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_USERNAME, "Administrator");
ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_PASSWORD, "password");
ConnectionProps.setProperty("java.naming.factory.initial", "com.ibm.ws.naming.util.WsnInitCtxFactory");
//Create a ServiceClientFactory object
ServiceClientFactory myFactory = ServiceClientFactory.createInstance(ConnectionProps);
//Create a FormsServiceClient object
FormsServiceClient formsClient = new FormsServiceClient(myFactory);
//Get Form data to pass to the processFormSubmission method
Document formData = new Document(req.getInputStream());
//Set run-time options
RenderOptionsSpec processSpec = new RenderOptionsSpec();
processSpec.setLocale("en_US");
//Invoke the processFormSubmission method
FormsResult formOut = formsClient.processFormSubmission(formData,"CONTENT_TYPE=application/pdf&CONTENT_TYPE=app lication/vnd.adobe.xdp+xml&CONTENT_TYPE=text/xml", "",processSpec);
List fileAttachments = formOut.getAttachments();
Iterator iter = fileAttachments.iterator();
int i = 0 ;
while (iter.hasNext()) {
Document file = (Document)iter.next();
file.copyToFile(new File("C:\\Adobe\\tempFile"+i+".jp i++;
short processState = formOut.getAction();
...... (To the end of the sample)
My Error was:
com.adobe.livecycle.formsservice.exception.ProcessFormSubmissionException: ALC-DSC-031-000: com.adobe.idp.dsc.net.DSCNamingException: Remote EJBObject lookup failed for ejb/Invocation provider
at com.adobe.livecycle.formsservice.client.FormsServiceClient.processFormSubmission(FormsSer viceClient.java:416)
at HandleData.doPost(HandleData.java:62)
at HandleData.doGet(HandleData.java:31)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
a

I assume here that your application is deployed on a different physical machine of where LCES is deployed and running.
Do the following test:
- Say that LCES is deployed on machine1 and your application is deployed on machine2. Ping machine1 from machine2 and note the ip address.
- Ping machine1 from machine1 and note the ip address.
The two pings should match.
- Ping machine2 from machine1 and note the ip address.
- Ping machine2 from machine2 and note the ip address.
The two pings should match.
Usually this kind of error would happen if your servers have internal and external ip addresses.

Can't create a JAXB binding for ejb-jar.xml using xjc

Hi all,
I have been trying to build a JAXB binding for EJB deployment descriptors, mainly because I have to update a hand-cranked ejb-jar.xml file on the fly with some additions that have come from a code generator.
I have tried to use
xjc ejb-jar_2_1.xsd j2ee_1_4.xsd ejb-jar_2_1.xsd
xjc on the schema definitions I found at http://java.sun.com/xml/ns/j2ee/ but I can't get it to work. It produces reams of errors, see below for a short extract.
Of course, someone could put me out of my misery and tell me where to find a binding that someone else has done. I can't be the first chimp on the planet that has wanted to do this!
Any help much appreciated.
errors:
[WARNING] warning: "blockDefault" attribute of <schema> is not supported
line 3 of xml.xsd
[WARNING] warning: "finalDefault" attribute of <schema> is not supported
line 3 of xml.xsd
[WARNING] warning: <key> identity constraint will be ignored by JAXB validation
line 117 of j2ee_web_services_client_1_1.xsd
[WARNING] warning: <key> identity constraint will be ignored by JAXB validation
line 115 of ejb-jar_2_1.xsd
[WARNING] warning: <keyref> identity constraint will be ignored by JAXB validation
line 129 of ejb-jar_2_1.xsd
[WARNING] warning: <key> identity constraint will be ignored by JAXB validation
line 145 of ejb-jar_2_1.xsd
[WARNING] warning: <keyref> identity constraint will be ignored by JAXB validation
line 159 of ejb-jar_2_1.xsd

Exception initializing 'oracle.dbtools.raptor.MonitorJDBCAddin' in extension 'Oracle SQL Developer': oracle.classloader.
util.AnnotatedNoClassDefFoundError:
Missing class: oracle.jdbc.OracleDriverThe Oracle driver is not on the classpath.

How to deploy and run EJB in eclipse without XDoclet

Hi Friends
I am new in j2ee.In my academic project i want to do some ejb programming.
For that purpose i want to write some ejb's.I have written all required class for ejb,created ejb-jar.xml file manually,weblogic .xml file manually. I am using weblogic8 as an server for deployment.
I know deployment with xdoclet but i want to know hoe to deploy ejb without xdoclet.
If u have saple code or useful link regarding this please send it as soon as possible.
Thanks in advance
How to deploy and run EJB in eclipse without XDoclet

HI Welcome to J2ee...
I am also new to this...But i ll share my ideas with you...
In EJB 3.0 No need of any Deployment Descriptors....
And If you are using Eclipse You can Deploy(as jar) using Export in File tab...
XDoclet is not mandatory...
Gopal V

How to Define a Data Source in a Standard Way for EJB 3.0?

I have an EJB 3.0 project that I want to deploy to different kinds of servers. I got it to work for OC4J, but when I tried to deploy it to JBoss I found out really quick that there are actually no data sources defined in my EJB Jar and that JDeveloper does not (that I am aware of) define data sources by default in a portable way.
I could be wrong on this. Not sure. Any info for explicitly defining data sources for EJB 3.0 in a portable way would be greatly appreciated.
Thank You,
KurzHome

Frank,
Thanks for your response. I will try that.
One thing I am confused about is how to link the EJB and the data source name. Unless I am missing something obvious, I can't find a configuration setting that explicitly states that my Entity EJB uses XYZ data source (when using OC4J). Where is this defined? Also, what configuration do I add to to my EJB or other file to link it to the JBoss defined data source?
Thanks,
KurzHome

Deployment choices for EJBs

Similar Messages

Maybe you are looking for