No EJB-Module in NWDS

Hi I have NWDS version 7.1 SP05 installed.
I need to develop a adapter module but when creating a project under J2EE I do not have the opportunity to create a EJB module. How can this be?
I can how ever create a EJB project under EJB. This looks almost right but here I am missing the ejb-jar file under META-INF. Can just create this my self and then use this kind of project?
Kind regards
Mikkel

hi Mikkel,
Update your NWDS 7.1 by downloading latest jar files from service market place.
Please follow the link below on how to create EJB module in PI 7.1:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e6747fa
Thanks,
Mayank

Similar Messages

Passing parameters from Communication channel to EJB Module

Dear friends,
We have an EJB module in NWDS. We want to pass some parameters from Communication Channel (Sender) in Integration Directory and use them in our EJB Module. Is there any function to do this process?? Please help me out
Thanks and Regards,
N.Jayanth Kumar

Hi,
Use the Channel object in this manner:
String cid = moduleContext.getChannelID();
channel = (Channel) LookupManager.getInstance().getCPAObject(CPAObjectType.CHANNEL, cid);
//To access channel parameters e.g in file adapter the connection parameters like host use the below code
String host = channel.getValueAsString("ftp.host");
PS: it is assumed that you are having the source code for adapter module development found on server
Regards,
Fariha

EJB Module creation in case of Java proxy

Hello
This question might look irrelevant in this forum but its required when we are dealing with Java proxy. I generated Java proxies of my interface which creates around 8 java classes and which supports EJB 2.0 specifications.
In Netweaver Developer Studio (NWDS) I tried to create a EJB Module project and imported these classes into that.Also I manually modified ejb-jar.xml to include the references of Home and Remote Interfaces and bean class.The problem is its not allowing me to create ejb jar of it (the option Built EJB Archive is disabled when right clicked on EJB Module Project).
Waiting for your reply.
Regards
Rajeev

Same thing I solved by closing NWDS, restarting cluster, open NWDS.
You assigned your bean to ejb-jar.xml?
If you have any errors in task list then the option is also disabled.
Dominik

Importing EJB Model in NWDS

Hi, 
There is a simple Stateless Session Bean which uses an external library (JAR); and there is only 1 business method with just 1 line of code:
RecordEx r = null;
 
RecordEx is one of the library classes; 
While trying to import this as an EJB Model in Web Dynpro DC in NWDS (7.1 EHP1 SP01 Preview Version), it fails with a NoClassDefFoundError; 
Below are the steps followed; 
1. Create an External Library DC "ext" 
 1.1 Add the third party library to this DC 
 1.2 Create public parts ppC (Compilation) & ppA (Assembly) and add the library to both of these 
 1.3 Build the DC 
2. Create an Enterprise Application DC "util" 
 2.1 Add Buildtime dependency to ppA public part of "ext" DC 
 2.2 Build & deploy 
3. Create EJB Module DC "ejb" 
 3.1 Add Buildtime dependency to ppC public part of "ext" DC 
 3.2 Create a Session Bean (Stateless - Transaction: Container - Local Interface) 
 3.3 Create 1 business method, and create an object of one of the library classes in it 
 3.4 Add the business method to Local Interface 
 3.5 Check Component Properties > Permissions > Entity Forwarding 
 3.6 Build the DC - there are no build errors; default client & ejbjar public parts are created; 
4. Create an Enterprise Application DC "app" 
 4.1 Add the "ejb" as Referenced Project 
 4.2 Add "util" as Used DC with Deploy Time & Runtime dependencies; (informs "util" EAR DC has no public parts) 
 4.3 Create a Compilation public part "EjbClasses" > Reference Entities > Select client public part of "ejb" DC 
 4.4 Build & Deploy the DC 
5. Create a Web Dynpro DC "wd" 
 5.1 Add dependency to the "app" EAR DC 
 5.2 Add Buildtime dependency to ppC public part of "ext" DC 
 5.3 Add "util" as Used DC with Deploy Time & Runtime dependencies; 
 5.4 Import EJB Model Wizard > Select "app" EAR > Display 1 business method 
 5.5 But when that method is selected & click Next, nothing happens in NWDS. The Wizard windows stays like that with no processing 
And the NWDS log has this NoClassDefFoundError: 
 
!MESSAGE Unhandled event loop exception
 !STACK 0
 java.lang.NoClassDefFoundError: com/sap/mdm/extension/data/RecordEx
 at java.lang.Class.getDeclaredMethods0(Native Method)
 at java.lang.Class.privateGetDeclaredMethods(Class.java:2395)
 at java.lang.Class.getMethod0(Class.java:2642)
 at java.lang.Class.getMethod(Class.java:1579)
 at com.sap.tc.webdynpro.model.ejb.importer.EJBCMIRuntimeMetadataFactory.createEJBModelInfo(EJBCMIRuntimeMetadataFactory.java:223) 
 at com.sap.tc.cm.ejb.modeltype.importer.dialog.EJBModelCreationDialog.afterEJBSelectPage(EJBModelCreationDialog.java:374) 
 at com.sap.tc.cm.ejb.modeltype.importer.dialog.EJBModelCreationDialog.nextPressed(EJBModelCreationDialog.java:172) 
 at com.sap.ide.cmi.core.internal.newmodelwizard.NewModelWizardDialog.nextPressed(NewModelWizardDialog.java:64) 
 at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369) 
 at com.sap.ide.cmi.core.internal.newmodelwizard.NewModelWizardDialog.buttonPressed(NewModelWizardDialog.java:88) 
 at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) 
 at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227) 
 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) 
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) 
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682) 
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293) 
 at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) 
 at org.eclipse.jface.window.Window.open(Window.java:796) 
 at com.sap.ide.cmi.core.internal.services.CreationServiceUI.createModel(CreationServiceUI.java:76) 
 at com.sap.ide.cmi.core.browser.actions.CreateModelAction.run(CreateModelAction.java:60) 
 at com.sap.ide.tools.core.viewerfwk.internal.actions.BaseSelectionSingleAction.run(BaseSelectionSingleAction.java:39) 
 at com.sap.ide.tools.core.viewerfwk.internal.actions.BaseSelectionAction.runInternal(BaseSelectionAction.java:78) 
 at com.sap.ide.tools.core.viewerfwk.internal.actions.BaseSelectionAction.run(BaseSelectionAction.java:70) 
 at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168) 
 at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546) 
 at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) 
 at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402) 
 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) 
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) 
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682) 
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293) 
 at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) 
 at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) 
 at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) 
 at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) 
 at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) 
 at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) 
 at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) 
 at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) 
 at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) 
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) 
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) 
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) 
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) 
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
 at java.lang.reflect.Method.invoke(Method.java:592) 
 at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) 
 at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) 
 at org.eclipse.equinox.launcher.Main.run(Main.java:1173) 
 at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
 ----- 
Please let me know if any step is missed or if something is done incorrectly; 
Thank you very much, 
- Harish 
Edited by: Harish Gali on Apr 30, 2010 11:37 AM

informs "util" EAR DC has no public parts
this is probably the issue. see if you can make the external library show up in the public part of the util DC
Edited by: Christian Loos on May 3, 2010 1:03 PM

How to code a Module in NWDS and deploy

Hi ,
That is exactly my question ...
how to code a Module in NWDS and deploy
Kindly let me know if there are any step by step available
also I may not always have access to nwds
To the same in a tool like eccilpse.
P.S.
I am an abaper ...have a little working knowlege of Java..so playing around with eccilpse alot...
Kindly help

>>also I may not always have access to nwds
>>To the same in a tool like eccilpse.
apart from the links provided by others , if your above statement means that you might have to use Eclipse at times in place of NWDS, then I would suggest you to have a build process independent of Eclipse. NWDS makes use of SAP specific plugins which recognizes your SAP sepcific files like application-j2ee-engine.xml and ejb-j2ee-engine.xml and you see them differently inside NWDS. So to have a better project setup
1. At least create the whole project (EJB / EAR) once in NWDS.
2. Export it and then import inside Eclipse.
3. Make changes and have a build script may be based on ANT to build your project and create EAR out of it.
4. Deploy using SDM.

Error while building a Webservice in Netbeans EJB Module

I have copied the java code of a JCD doing xml to cobol copybook transformation in JCAPS, to a new webservice created in the Netbeans EJB module. There were no compilation errors. But while trying to build, I am getting errors like "java.io.printStream does not have a no-arg default Constructor" , "IllegalAnnotation Exception", "Unable to create jaxb context" etc..
I am not able to find out why this happened... Someone please help me in resolving this issue......

Guys,
I am able to solve the problem. I think the problem is Language settings difference between Database and OWB repository.

What authorization required to deploy module from NWDS 7.1

Hi Experts,
Need to deploy custom adapter module from NWDS 7.1 to PI server, Please help me to know exact access/authorization role required one developer to publish the module.
I have gone through many blogs and thread but not able to find exact administrator role which help to deploy the custom module on PI server.
Error I am getting in NWDS 7.1, while deploying module:
Could not establish connection to AS Java on [<server detail>]. Authentication did not succeed. Wrong or missing security credentials (password) for principal [PIUSER], or the specified principal has no permissions to perform JNDI related operations.
Regards
Raghav
Edited by: RaghavTiwari on Feb 4, 2012 8:25 AM

Hi Raghav,
Check this [SAP Help link|http://help.sap.com/saphelp_nw73ehp1/helpdata/en/43/1e1bbc5d9206fde10000000a422035/frameset.htm] for User Roles for Adapter and Module Development.
Regards,
Raghu_Vamsee.

Unable to load the EJB module. DeploymentContext does not contain any EJB.

I'm writing an enterprise application to familiarize myself with Glassfish 3.1.2 and EJB 3.1. I've created several local, stateless beans, and injected one into a JSF managed bean. The ejb and web modules compile fine, but when I launch the application with Glassfish I get the following startup error and the application does not deploy. I don't understand what it means, can someone ellaborate?
SEVERE: Exception while invoking class org.glassfish.ejb.startup.EjbDeployer prepare method
SEVERE: Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
SEVERE: Exception while preparing the app
SEVERE: Unable to load the EJB module. DeploymentContext does not contain any EJB. Check the archive to ensure correct packaging for D:\Documents\NetBeansProjects\Test\dist\gfdeploy\Test\Test-war_war.
If you use EJB component annotations to define the EJB, and an ejb or web deployment descriptor is also used, please make sure that the deployment descriptor references a Java EE 5 or higher version schema, and that the metadata-complete attribute is not set to true, so the component annotations can be processed as expected
org.glassfish.deployment.common.DeploymentException: Unable to load the EJB module. DeploymentContext does not contain any EJB. Check the archive to ensure correct packaging for D:\Documents\NetBeansProjects\Test\dist\gfdeploy\Test\Test-war_war.
If you use EJB component annotations to define the EJB, and an ejb or web deployment descriptor is also used, please make sure that the deployment descriptor references a Java EE 5 or higher version schema, and that the metadata-complete attribute is not set to true, so the component annotations can be processed as expected
     at org.glassfish.javaee.full.deployment.EarDeployer.prepare(EarDeployer.java:166)
     at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
     at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
     at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
     at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
     at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
     at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
     at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
     at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
     at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
     at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
     at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
     at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
     at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
     at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
     at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
     at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
     at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
     at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
     at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
     at java.lang.Thread.run(Thread.java:722)

My guess is that you deployed an ejb without bean in it. when you have an ejb module, be sure you have at least one bean present.
Are you sure you have implementend some beans? Or did you do this only in the web module?
Try adding an @Stateless bean doing nothing in you ejb module, redeploy and let me know if that works

How to reference an External Library (Server Side) in a DC-EJB Module ?

Hi:
I start working with hibernate in a DC component, so I create my DC project and EJB module inside. I Make an external library following this
Thanks a lot for your time on this thread.
Rocío.

Hi Rocío!
Umm, I don't usually use DC's... I don't know if this will work... you can make an EAR (New Proyect -> J2EE -> Enterpise Application Module), add your EJB Module to the EAR (right click on EJB Project and choose Add to EAR proyect), and you'll find a j2ee-engine file on it, and you can add the reference there.Then deploy the EAR.
I normally do something similar to your issue, I make a EJB calling XI via Java Proxys, and the reference to the XI libs are allocated on the EAR, not on the EJB. This is only for runtime, for compilation you must reference the hibernate jar with an external jar file, as always.
A dirty solution could be this one: open your generated EAR with de-compressor, and copy your hibernate jar on it (at root). This way you'll load hibernate classes at runtime (I know this is an horrible solution, this is only for testing).
As I said before, I'm not used to DCs, so this could be wrong, and be a waste of time... I don't know further...
Good luck
Eneko.

Not able to update single file in a non ejb Module related jar

Hey all,
I have depoyed my j2ee application .ear on NW webAS .
 This application apart from having all the ejb Modules related jar, also has a jar which has all my properties files being accessed by my application.
Very often is it required by me to update these files and restart the application. However i couldnot find a way to update these single files.
When i select by deployed application.ear and click Single File Update feature provided by SAP in visual Admin, it shown only ejb modulerelated jar. It dosent show my jar containing properties file.
I have to redeploy my application again everytime i change a small properties file.
Please let me if there is a way to update these sngle files

Hi,
>
Vikram D Salvi wrote:
> MOVE-CORRESPONDING ZSTRUC_CM TO I_TAB. not working
>
> UPDATE ZTEST_CM FROM ZSTRUC_CM. not working
Instead of the move statement you need to use the append work area to internal table statement. you need to have the same structure for the work area and the internal tbale.
Then use the modify data base table from internal table statement.
Regards
Ansari

How to add a library jar to a EJB module?

Hi All,
in J2EE the normal procedure to a library jar to a module, is to add the library in the Class-Path header of the manifest of the module, and then include the actual jar in the root structure of the ear file. Unfortunately it is not clear to me how S1S5 update 1 supports this. The only option Studio I found so far, is to add the jar as a 'file to include', but then the contents is added to the module jar and not to the ear file itself, resulting in duplication of classes across modules. Is there an option to add the library jar in the Class-Path of the module?
Thanks in advance,
Stijn

I believe that better support for this was added in the Sun Java Studio 6 EA release. It was added to the Extra Files property on an EJB Module.

Med Rec medrec tutorial 10 deployments-- EJB Modules EJB is not shown

This note adds missing steps in the Med Rec (medrec) Tutorial 10
The tutorial shows how to use EJBGEN to generate EJB classes (incl java source) from .ejb files.
Unfortunately it is missing a few key details. These are described below.
Many thanks to Chris Wall for supplying the answers and hints.
Q: The tutorial includes deploying the manually generated physSessionEjb’s. After doing the step that generates the PhysSession*.java files, onefinds that when trying to deploy that there are no class files – nothing has been built. Are the class files supposed to be generated by the ejbgen step?
[Chris] No, EJBGen just generates the local and remote interfaces and descriptors only. An additional step should be added to explain how to build the newly generated EJBs. I believe you are correct in calling “src/physicianEar$ ant –f build.xml build”.
Q: Manually built the class files using ‘ant –f build.xml build’ in the physicianEar src dir – but that failed in the acc.split.dir step with class not found /org/apache/struts/action/ActionForm.
Obviously did not get the struts jars on the classpath. But as much of the build as completed did include creating the class files.
[Chris] Yes, it looks like struts.jar is not in the classpath. Is this the “build.split.dir” or “appc.split.dir” target? In either case, wlcompile and wlappc should recognized all libs in "${app-inf.dest.lib}" and append them to the compile/appc classpath automatically. The libs should have been copied during the “prepare” target. Can you make sure that struts.jar exists in c:/medrec_tutorial/build/physicianEar/APP-INF/lib? If not, re-run the target with verbose: “src/physicianEar$ ant -verbose -f build.xml build”, and make sure that the libs are copied in the “prepare” target.
Q: When doing the deploy step, we get no errors but on the console window and do not see the tutorial_deployment item under DeploymentsàEJB Modules. There is something under Deployments-->Applications --> tutorial_deployment. It appears the deploy failed since there’s nothing under Deployments --> EJB Modules, and what is there is ‘left over’ from deploying the jar (the ear?) that contains the stuff deployed by the deploy step at the start of tutorial 10.
[Chris] Once the build is successful, you must deploy the EAR. This is done by executing : “src/physicianEar$ ant -f build.xml redeploy.physician.ear”. Again, a step that was left out. Yes, you should be looking at Deployments--> Applications--> tutorial_deployment. So, to summarize: generated the local and remote and descriptors for the EJB, compile the EJB and package the EAR, deploy the EAR, and then view the deployment in the console.

This note adds missing steps in the Med Rec (medrec) Tutorial 10
The tutorial shows how to use EJBGEN to generate EJB classes (incl java source) from .ejb files.
Unfortunately it is missing a few key details. These are described below.
Many thanks to Chris Wall for supplying the answers and hints.
Q: The tutorial includes deploying the manually generated physSessionEjb’s. After doing the step that generates the PhysSession*.java files, onefinds that when trying to deploy that there are no class files – nothing has been built. Are the class files supposed to be generated by the ejbgen step?
[Chris] No, EJBGen just generates the local and remote interfaces and descriptors only. An additional step should be added to explain how to build the newly generated EJBs. I believe you are correct in calling “src/physicianEar$ ant –f build.xml build”.
Q: Manually built the class files using ‘ant –f build.xml build’ in the physicianEar src dir – but that failed in the acc.split.dir step with class not found /org/apache/struts/action/ActionForm.
Obviously did not get the struts jars on the classpath. But as much of the build as completed did include creating the class files.
[Chris] Yes, it looks like struts.jar is not in the classpath. Is this the “build.split.dir” or “appc.split.dir” target? In either case, wlcompile and wlappc should recognized all libs in "${app-inf.dest.lib}" and append them to the compile/appc classpath automatically. The libs should have been copied during the “prepare” target. Can you make sure that struts.jar exists in c:/medrec_tutorial/build/physicianEar/APP-INF/lib? If not, re-run the target with verbose: “src/physicianEar$ ant -verbose -f build.xml build”, and make sure that the libs are copied in the “prepare” target.
Q: When doing the deploy step, we get no errors but on the console window and do not see the tutorial_deployment item under DeploymentsàEJB Modules. There is something under Deployments-->Applications --> tutorial_deployment. It appears the deploy failed since there’s nothing under Deployments --> EJB Modules, and what is there is ‘left over’ from deploying the jar (the ear?) that contains the stuff deployed by the deploy step at the start of tutorial 10.
[Chris] Once the build is successful, you must deploy the EAR. This is done by executing : “src/physicianEar$ ant -f build.xml redeploy.physician.ear”. Again, a step that was left out. Yes, you should be looking at Deployments--> Applications--> tutorial_deployment. So, to summarize: generated the local and remote and descriptors for the EJB, compile the EJB and package the EAR, deploy the EAR, and then view the deployment in the console.

Converting existing ejb module project into DC

Hi,
1. I have created a local Ejb Module Project
2. Also a web service is created using that ejb(stateless) && deployed on the server.
3. I want to convert this local ejb module project into DC
4. I have copied everything from local ejb module project(eg.ejb,classes,virtual Interface & web service dif etc) & pasted in the DC structure.
5. While creating web service, it shows me a deployment error, regarding web service name (which is already exists).
6. I can create web service with different name & it works fine,
but I don't want to use different name for web service.
7. Is it possible to again create web service with the same name?
8. Or is there another way for doing this?
Best regards,
Nilesh

Have you tried to undeploy the old project? This should work out.
\-- Vladimir

Error targeting server for the EJB module while deploying the sample banking application

I am currently having a very difficult time attempting to deploy the
example banking application that I downloaded from the BEA website. I
have followed all of the steps in the "Hands On: Deploying the Sample
Banking Application" document, and I do fine until I get to the next to
last step. When I attempt to target the server for the EJB module, the
deployment process generates the error that I have included at the end
of this message.
I can get to the login.html page under "http://localhost:7001/banking/",
but after that I can't go further.
Any suggestions. BTW, in case you haven't figured it out, I'm brand new
to BEA WebLogic server.
Thanks in advance for any help you can offer.
Scott
Error deploying application \ejb:
Unable to deploy EJB: \ejb from \ejb:
Compiler failed
executable.exec(java.lang.String[javac,-nowarn,-classpath,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb;E:\bea\wlserver6.1\.\config\ScottsServer\applications\.wlnotdelete\wlap60763\ejb;E:\bea\jdk131\jre\lib\rt.jar;E:\bea\jdk131\jre\lib\i18n.jar;E:\bea\jdk131\jre\lib\sunrsasign.jar;E:\bea\jdk131\jre\classes;.;E:\bea\wlserver6.1\lib\weblogic_sp.jar;E:\bea\wlserver6.1\lib\weblogic.jar,-d,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb\examples\tutorials\migration\banking\*.java])
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:302)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy11.addDeployment(Unknown Source)
at
weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy68.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at
weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

The deployment process invokes javac internally to compile some generated classes.
Do you have javac installed and in the path?
Seth
Scott Springer wrote:
I am currently having a very difficult time attempting to deploy the
example banking application that I downloaded from the BEA website. I
have followed all of the steps in the "Hands On: Deploying the Sample
Banking Application" document, and I do fine until I get to the next to
last step. When I attempt to target the server for the EJB module, the
deployment process generates the error that I have included at the end
of this message.
I can get to the login.html page under "http://localhost:7001/banking/",
but after that I can't go further.
Any suggestions. BTW, in case you haven't figured it out, I'm brand new
to BEA WebLogic server.
Thanks in advance for any help you can offer.
Scott
Error deploying application \ejb:
Unable to deploy EJB: \ejb from \ejb:
Compiler failed
executable.exec(java.lang.String[javac,-nowarn,-classpath,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb;E:\bea\wlserver6.1\.\config\ScottsServer\applications\.wlnotdelete\wlap60763\ejb;E:\bea\jdk131\jre\lib\rt.jar;E:\bea\jdk131\jre\lib\i18n.jar;E:\bea\jdk131\jre\lib\sunrsasign.jar;E:\bea\jdk131\jre\classes;.;E:\bea\wlserver6.1\lib\weblogic_sp.jar;E:\bea\wlserver6.1\lib\weblogic.jar,-d,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb\examples\tutorials\migration\banking\*.java])
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:302)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy11.addDeployment(Unknown Source)
at
weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy68.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at
weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Lack of modularity in Projects for EJB module

Problem
For a project you have many enterprise bean components. In JDeveloper, currently, all the information like persistence-type,
resource-reference, etc reside in the ejb-jar.xml which is project specific.
(1) In the real-world, developers work on different modules with small individual work spaces with a small number of
enterprise components and web compoents with a CVS system to manage version of the source code
(2) The developer works on the source and check it in the CVS repository
(3) A packager will take components from the CVS repository and make a build for a customer according to the order
(Build-to-Order approach)
(4) In JDeveloper he might have to make the ejb-jar.xml again which is very cumbersome and timeconsuming
Suggestion
(1) The current system of maintaining ejb-jar.xml in the project is OK
(2) But the information in the ejb-jar xml ABOUT EACH EJB COMPONENT should also be maintained at the EJB component level like
a small ejb-jar.xml file specific to the one and only one component.
(3) Whenever the EJB component id edited, this modular ejb-jar.xml file will be edited too.
(4) Later while making the main ejb-jar xml for deployment, the info in these small modular xml files will be read, the main
project level ejb-jar xml will be prepared.
(5) The main project level ejb-jar.xml can also be prepared when the project is rebuilt (clean/force compile) and all te
small modular files are updated.
With regards
Amit

Hello,
Yes we do read every OTN message, though we often have some internal discussion before we post a reply.
In your specific situation, you could just break up the EJBs into different projects:
- Each EJB module in a separate project.
- Each EJB project builds a separate EJB JAR.
- When assembling the EAR, pull in as many EJB JAR files as necessary to support the WAR and other pieces.
JDeveloper already has support for the above setup. Starting with JDev 9.0.3, you can also establish dependencies between projects to make the classes built by one project visible to another project's classpath.
For us to implement a complete solution where small ejb-jar.xml files are merged into one large ejb-jar.xml file, we'd like to understand how you'd go about resolving conflicts in elements being merged:
- conflicting <method-permission>
- conflicting <container-transaction>
- conflicting <relationship-role>
- conflicting <env-entry>
- ... a number of other potential conflicts ...
We could do automatic merges when there are no conflicts. For the situations where there are conflicts, can you describe some solutions that you would consider acceptable?

No EJB-Module in NWDS

Similar Messages

Maybe you are looking for