Command bean or webservice for accessing EJB

Hi Experts,
I Want to access an Enterprise archieve DC created for EJB Module DC, through WebDynpro DC.
Now I know that there are two ways to access EAR DC through webDynpro:
1) Command bean
2) Web Services
Can anybody suggest the pros and cons of this two methods?
Also please suggest which one to choose.
Regards,
Ashish Shah

Hi,
to access EJBs from WD, you can use the EJB3.0 model importer (a new feature introduced with NW CE). There's a good tutorial explaining that <a href="http://help.sap.com/saphelp_nwce10/helpdata/en/45/f7f744aea471fae10000000a1553f6/frameset.htm">here</a>.
The Web services way should also work, but it means that you "wrap" the EJB, which is not needed in this case, I believe.
Hope it helps!

Similar Messages

Possible to create a JAX-WS, session-bean-based webservice for WebLogic 10?

All,
sorry - but I'm going a bit crazy here. I have been unable to figure out the secret hand-shakes for developing a session-bean-based web service that will run properly under Weblogic 10.0. There are examples out there on how to create webservices that exists within a war file - but none that I can find that reside within a session bean (an ear file).
I can't even figure out how to do with this Bea Workshop for WebLogic Platform 10.0! Is this possible? I can't find any examples anywhere on how to do this. I must be missing something...
Does WebLogic 10.0 support web services within session beans? I've figured out how to do this with JBoss, Sun App Server, and Glassfish - but no luck so far with WebLogic.
If anyone can please point me in the proper direction it would be very appreciated. My company likes WebLogic, but we have to be able to do this in order to continue using it.
Thanks,
-john

Yeah - I've tried that. Everything builds fine - but when I deploy to WebLogic 10, I get the stack below. It looks like it is looking for the class examples.webservices.jaxws.jaxws.SayHello - but there isn't such a class in the example...
Any thoughts? I'm completely stuck!
<Apr 16, 2007 4:15:45 PM PDT> <Error> <HTTP> <BEA-101216> <Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
Truncated. see log file for complete stacktrace
>
<Apr 16, 2007 4:15:45 PM PDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1176765341457' for task '0'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
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 activating module: EJBModule(WL6-ejb.jar)
Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
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.activate(EJBModule.java:440)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
Truncated. see log file for complete stacktrace
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
Truncated. see log file for complete stacktrace
>
<Apr 16, 2007 4:15:46 PM PDT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application '_appsdir_WL6_ear'.>
<Apr 16, 2007 4:15:46 PM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application '_appsdir_WL6_ear'.>
<Apr 16, 2007 4:15:46 PM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
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.activate(EJBModule.java:440)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
Truncated. see log file for complete stacktrace
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
Truncated. see log file for complete stacktrace
>

Webservice for EJB DC

I'm trying to create a webservice for an EJB with the Webservice Creation Wizard of NDS. While this is no problem for an "old fashioned" EJB, it does not seem to work for an EJB DC. The context menu "New -> Virtual Interface / Webservice" appears, just as described in the <a href="http://help.sap.com/saphelp_nw04s/helpdata/de/f7/af60f2e04d0848888675a800623a81/frameset.htm">Java Development Manual</a>, but nothing happenes when I select one of this options. No error message, no dialog, nothing...
I have created an Enterprise Application DC with an EJB Module DC as Child DC. The EJB Project contains a Stateless Session Bean with a Business Method. Is there anything else I have to do, so that the Wizard works?
Thanks for your help,
Frank

Hi,
Which version of Studio are you using? Mine is SP18 and it works fine. I'm able to create a virtual interface for an ejb in ejb dc with no problems.
You might consider re-installing your studio.
Hope that helps,
Thanks,
Rajit S

Using Data Acess Command Beans as Model

Hey guys,
actually I try to get data from some EJBs (Entity Beans) into my Web Dynpro application.
Inside SDN I found a tutorial which uses the 'Data Access Command Bean pattern' to connect the EJB-Backend to a WD application (The tutorial is called 'Using EJBs in Web Dynpro applications. You find it in the 'Web Dynpro Sample Applications and Tutorials' subsection in the 'SAP NetWeaver -> Application Server -> Web Dynpro' section). The author writes a 'Command Bean' which is bound to the WD application as a model. This bean has an 'execute()' method which calls two business methods from a session bean. Because of data binding the private attributes from the bean class are filled with the data in the corresponding model class.
Everything is fine so far.
But in my WD application I want to handle two or more context elements from the model node with the command bean. Therefore I guess I have to call the execute() method for every context element of the model node, cause the private attributes of the command bean will only hold the data of the current context element (that's what I assume). Well the point is that every call of execute() will result in an insert operation on the database.
In my opinion it would be a better way to give all context elements in one batch to the EJB-Backend so that the connection to the database have to be opened and closed only once instead after every call of the execute method.
I wonder now if it is possible to pass the whole context elements collection to the EJB-Backend. Did anyone have some experience with this?
Thanks in advance to all answers!
Regards,
Torben

You can simply provide an attribute in your Command Bean of type Collection. This can hold a collection of DTOs (<a href="http://java.sun.com/blueprints/corej2eepatterns/Patterns/TransferObject.html">Data Transfer Object</a> pattern... also known as Transfer Object or Value Object) to which you can bind a context node.
This attribute can then be populated with an appropriate collection of DTOs explicitly in your code... or optionally, you can bind a UI Element of type Table, for example to the associated context node. Then provide some functionality in your UI to make it possible for users to add elements to that table.
When comes the time to call your back-end, you can pass that collection directly to your business delegate (or Session Bean if you're interacting directly with that):
public void execute()
bizDelegate.insertSomething(this.getDtoCollection());

Building webservices from multiple ejbs in a single ejbjar file

Hi,
I have multiple ejbs packaged in a single ejbjar file. How to generate webservices for each ejb from this ejbjar file.
I will really appriciate if anybody can give some guidance on this.
Regards
Rao Peddi
email: [email protected]

Assuming you are using servicegen ant task, you can firstly start by using a separate <service> element for each web service you are generating. And within each <service> element you would then specify ejbJar attribute to point at your single ejbjar alongwith includeEJBs attribute which points to the specific EJB in this ejbjar file (note you would specify the <ejb-name> value of the specific ejb present in ejb-jar.xml inside your ejbjar file).
Note that the individual services would be referred to by their specific serviceUri.
The following is a simple example using ejbJar inside a single <service> element.
<servicegen destEar="ears/myWebService.ear" warName="myWAR.war" contextURI="web_services" > <service ejbJar="jars/myEJB.jar" targetNamespace="http://www.bea.com/examples/Trader" serviceName="TraderService" serviceURI="/TraderService" generateTypes="True" expandMethods="True" > </service> </servicegen>
Thanks
Shridhar

Procedure for Accessing WebService in ejb By using NetWeaver,

hai,
This is Guru.
please tell me the procedure for accessing a webservice in ejb .
my mean is.
i have one Session Beab,And there is one webservice.
How can i call and using that webservice in netweaverdeveloperstudio tool.please send me code,if u have.
thanqq
Guru

Hi Guru,
the procedure to use a WS is as follow
1. Use the SAP xmltoolkit and generate client binding for your WS, which is the stub class, parameter and return type classes of the WS methods, if any.
2.Import the created WS client jar from step 1 to your EJB module project
3. In your session bean: instantiate the stub and call a WS method on this stub
That's all there is to it.
Best Regards
Gregor
Ps. The NWDS Help has also tutorial regarding WS usage.

JAR creation failed , for Command bean DC

Hi Experts,
I am trying to access an EJB module DC from WebDynpro through Java bean model DC.
In this when i tried to create a Jar file of the Java bean model, i got this error.
JAR creation failed. See details for additional information.
Problem writing /LocalDevelopmentdc_aptcbsap.com/bin/pg/com/atos/apt/bean/APTCommandBean.class to JAR: duplicate entry: pg/com/atos/apt/bean/APTCommandBean.class
I have created in all total 4 DC
1) EJB DC
2) EAR DC
3) Java bean DC
4) WebDynpro DC
I have reffered to the tutorial : Using EJBs in Web Dynpro application.
Can you tell me what am i missing?
Ashish Shah

Hi Sridhar,
Thanks for your suggestion.
I have built and deployed the EAR DC.
But When I added the following referencesto Java bean DC
1) EAR DC , EJB DC
2) ejb20.jar
and i tried to build java bean DC project, it throws error for these referenced DC.
And these referenced DCs are removed from the project.
Do i have to add anything in the Public part of EJB or EAR DC?
Can you tell me how to add those references in Public part and how to utilise them in other projects?
Regards,
Ashish Shah

Using EJB remote session beans llike webservice.

My requirement is to fetch a big size ASCII stream file from a remote location. For this can I use Statless EJB Session beans?
For this EJB application & Web application will be on my application server side & EJB client should reside on the remote end side from where I want to fetch the file. - Please confirm my this logic as I am new in Java & EJB, I am having a basic query like this. (I don't want to proceed with EJB web service like (@Stateless, @WebService), I want to purly use EJB Statless Remote session beans - Is this possible?
If yes, can I have one sample example URL pls?
Thanks in advance for your help.

My requirement is to fetch a big size ASCII stream file from a remote location. For this can I use Statless EJB Session beans?
For this EJB application & Web application will be on my application server side & EJB client should reside on the remote end side from where I want to fetch the file. - Please confirm my this logic as I am new in Java & EJB, I am having a basic query like this. (I don't want to proceed with EJB web service like (@Stateless, @WebService), I want to purly use EJB Statless Remote session beans - Is this possible?
If yes, can I have one sample example URL pls?
Thanks in advance for your help.

Problems accessing ejb 3.0 entity bean from project

I have written some code using ejb 3.0 and was previously accessing the entity bean without problem when both ejbs and the accessing code were in the same project. However I have moved the accessing code into a different project within the same application and now when the code tries to accessing the entity bean I get the following error:
com.colwilson.web.ingestion.IdentifiedException: java.lang.ClassCastException: __Proxy3
     at com.colwilson.web.ingestion.IngestionHandler.recordArrived(IngestionHandler.java:140)
     at com.colwilson.web.ingestion.IngestionHandler.main(IngestionHandler.java:52)
Caused by: java.lang.ClassCastException: __Proxy3
     at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.getFreshObject(StatelessSessionRemoteInvocationHandler.java:21)
     at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.getReplacementObject(RecoverableRemoteInvocationHandler.java:64)
     at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.handleRecovery(RecoverableRemoteInvocationHandler.java:41)
     at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:30)
     at com.evermind.server.ejb.StatelessSessionRemoteInvocationHandler.invoke(StatelessSessionRemoteInvocationHandler.java:43)
     at __Proxy1.mergeEntity(Unknown Source)
     at com.colwilson.web.ingestion.IngestionHandler.recordArrived(IngestionHandler.java:137)
     ... 1 more
Now, of course I could move the code back into the same project, but as I understand it that is just the point of ejbs. I'm looking up the entity bean thus:
final Context context = InitialContext();
ingestionSessionEJB =
(IngestionSessionEJB)context.lookup("IngestionSessionEJB");
It may be true that I don't understand the way lookup works, but to be honest I can't find the docs that explain what I've got wrong.
Please help.

hi
Double Click on the project which is goin to use the project which contains bean from the Application Navigator window. The project properties window will open. Choose the "Dependencies" item from left panel. click on the radio "User Project Settings" and select another project which contain ejb which you're goin to access...
Best Of Luck
Ravi A. Trivedi

Command for: Access Mode for Result Set

Hi
Does anyone know if there is a command for "Access Mode for Result Set".
The default view for my characteristic in my query is "Characteristic Relationships".
I would like to have a command button for the user to be able to change the access mode to "Posted Values"
I have searched through all the commands but was unable to find this command.
OR if it is not available does anyone know the XHTML that I could enter into the web template.
Thanks in advance.
Ian

Hi
Does anyone know if there is a command for "Access Mode for Result Set".
The default view for my characteristic in my query is "Characteristic Relationships".
I would like to have a command button for the user to be able to change the access mode to "Posted Values"
I have searched through all the commands but was unable to find this command.
OR if it is not available does anyone know the XHTML that I could enter into the web template.
Thanks in advance.
Ian

Feature of JSP for access command of UNIX

hello sir ,
I interesting JSP for developer application on internet . Now , I would like feature of JSP that
what JSP use command for access comand of UNIX example ls ,mail ,bg (background process) and
return result of command example mail, bg (background process) to JSP ? please tell me too . Thank you very much.

thank you for reply question to me
Please talk detail about runtime & process class to me please and example for JSP call command UNIX "mail" via JSP :-)

ClassNotFound Exception accessing EJBs in a cluster

I am experiencing some weird behavior when attempting to access EJBs in a
 Weblogic 5.1.0 cluster. The cluster nodes startup fine, and the EJBs are
 correctly deployed. However, when my test client attempts to access them I
 get the ClassNotFoundException listed below. This same client can access the
 same EJBs deployed in a non-clustered environment without any problems, so
 it's definitely related to my cluster configuration. The problem seems to be
 that the client is not receiving the client-side stub. To confim this, I put
 the stub in the client's classpath, and did NOT get the
 ClassNotFoundException. Has anyone else seen this error?
 BTW, I have compiled the EJB both with and without the <home-is-clusterable>
 flag set to true. I get the same exception either way.
 Thanks for any assistance,
 Jason Donnell
 javax.naming.CommunicationException. Root exception is
 java.lang.ClassNotFoundException: class
 com.landacorp.maxmc.ejb.security.ProviderSecurityBeanHomeImpl_ServiceStub
 previously not found
 at weblogic.rjvm.MsgAbbrev.read(MsgAbbrev.java:184)
 at weblogic.socket.JVMAbbrevSocket.readMsgAbbrevs(JVMAbbrevSocket.java:505)
 at weblogic.rjvm.MsgAbbrevInputStream.prime(MsgAbbrevInputStream.java:134)
 at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:700)
 at
 weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
 a:34)
 at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:630)
 at weblogic.socket.JVMAbbrevSocket.dispatch(JVMAbbrevSocket.java:393)
 at weblogic.socket.JVMSocketT3.dispatch(JVMSocketT3.java:355)
 at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:247)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
 --------------- nested within: ------------------
 weblogic.rmi.UnmarshalException: Unmarshalling return
 - with nested exception:
 [java.lang.ClassNotFoundException: class
 com.landacorp.maxmc.ejb.security.ProviderSecurityBeanHomeImpl_ServiceStub
 previously not found]
 at
 weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(BasicWLContext_WLStub.jav
 a:256)
 at weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
 at javax.naming.InitialContext.lookup(InitialContext.java:350)
 at
 com.landacorp.maxmc.ejb.security.ClusterSecurityTest.main(ClusterSecurityTes
 t.java:52)


Just a side note: I setup the cluster using the WebLogic recommended
 directory structure (see
 http://www.weblogic.com/docs51/cluster/setup.html#676105) and I no longer
 get the exception. I'm still interested in hearing, though, if anyone has a
 scheme for setting up the cluster in a directory that isn't directly under
 the weblogic installation directory.
 Jason
 "Jason Donnell" <[email protected]> wrote in message
 news:[email protected]...
 > My current idea is that our directory structure is not properly supported
 by
 > WebLogic. We are NOT putting everything under the weblogic install
 > directory, as the documentation suggests. Instead, it looks something like
 > this (on an NT box):
 >
 > \weblogic_install\<Weblogic 5.1.0 installation here>
 >
 > \our_weblogic\startWeblogicNode1.cmd
 > \our_weblogic\startWeblogicNode2.cmd
 > \our_weblogic\weblogic.properties (cluster-wide)
 > \our_weblogic\public_html\
 > \our_weblogic\our_cluster_name\
 > \our_weblogic\our_cluster_name\all_ejbs\<compiled beans are here>
 > \our_weblogic\our_cluster_name\server_node1\
 > \our_weblogic\our_cluster_name\server_node1\weblogic.properties
 > (server-specific)
 > \our_weblogic\our_cluster_name\server_node2\
 > \our_weblogic\our_cluster_name\server_node2\weblogic.properties
 > (server-specific)
 >
 > So, on the command line in our per-server startup scripts, we set the
 > weblogic.system.home=\our_weblogic,
 weblogic.cluster.name=our_cluster_name,
 > and weblogic.system.name=server_nodeX.
 >
 > Now, I want to emphasize that the server claims to start up just fine. It
 > claims the EJBs have been deployed. However, it is unable to deliver
 classes
 > dynamically, as we found by trying the
 > http://yourweblogic..../classes/some/class/name.class suggestion noted
 > previously.
 >
 > We had a similar directory structure for a single server, and it worked
 just
 > fine. However, in that case we obviously did not have the extra level of
 the
 > \our_cluster_name\ directory. It would seem that in the cluster
 > configuration, we cannot do it this way. I would be VERY interested to
 hear
 > if anyone else has setup a cluster in a directory that is not under the
 > weblogic installation directory.
 >
 > Hopefully this may shed some light on your problem. Feel free to contact
 me
 > if you need any additional information (or if you solve the problem!).
 >
 > Jason Donnell
 > [email protected]
 >
 >
 > "Chad" <[email protected]> wrote in message
 > news:[email protected]...
 > > I am very interested in this thread - I am having the same behavior:
 > >
 > > javax.naming.CommunicationException. Root exception is
 > > java.lang.ClassNotFoundException: class
 > > healthecare.drug.ejb.DrugAlternateBeanHomeImpl_ServiceStub previously
 > > not found
 > > at weblogic.rjvm.MsgAbbrev.read(MsgAbbrev.java:181)
 > > at
 > weblogic.socket.JVMAbbrevSocket.readMsgAbbrevs(JVMAbbrevSocket.java:505)
 > > at
 weblogic.rjvm.MsgAbbrevInputStream.prime(MsgAbbrevInputStream.java:134)
 > > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:630)
 > > at
 >
 weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
 > a:34)
 > > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:630)
 > > at weblogic.socket.JVMAbbrevSocket.dispatch(JVMAbbrevSocket.java:393)
 > > at weblogic.socket.JVMSocketT3.dispatch(JVMSocketT3.java:355)
 > > at
 > weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:247)
 > > at
 > weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
 > >
 > > --------------- nested within: ------------------
 > > weblogic.rmi.UnmarshalException: Unmarshalling return
 > > - with nested exception:
 > > [java.lang.ClassNotFoundException: class
 > > healthecare.drug.ejb.DrugAlternateBeanHomeImpl_ServiceStub previously
 > > not found]
 > > at
 >
 weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(BasicWLContext_WLStub.jav
 > a:256)
 > > at weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
 > > at javax.naming.InitialContext.lookup(InitialContext.java:350)
 > > at healthecare.util.EJBBase.findHomeInterface(EJBBase.java:178)
 > >
 > > One additional bit of information that I can add is that when I
 > > getInitialContext() like this:
 > >
 > > public static Context getInitialContext() throws Exception
 > > {
 > > String providerURL =
 > > "t3://" + CommonUtil.getProperty("ejb.server.name") +
 > > ":" + CommonUtil.getProperty("ejb.server.port");
 > >
 > > Hashtable ht = new Hashtable();
 > > ht.put(Context.INITIAL_CONTEXT_FACTORY,
 > > "weblogic.jndi.WLInitialContextFactory");
 > > ht.put(Context.PROVIDER_URL, providerURL);
 > >
 > > return new InitialContext(ht);
 > > }
 > >
 > > When the "ejb.server.name" property is one server, like "serverName1",
 > > the code works. But when the "ejb.server.name" property is clustered,
 > > like "serverName1, serverName2", the code throws the exception above.
 > >
 > > I'll definitely re-post if I come up with anything.
 > >
 > > thanks,
 > > chad small
 > >
 > > "Jason Donnell" <[email protected]> wrote in message
 > news:<[email protected]>...
 > > > Well, that was a good test. I discovered I am unable to download
 classes
 > > > from the clustered server when pointing my browser at it. Any ideas
 what
 > > > kind of misconfiguration on my part would cause that behavior?
 > > >
 > > > Thanks,
 > > > Jason Donnell
 > > >
 > > > "Dimitri Rakitine" <[email protected]> wrote in message
 > > > news:[email protected]...
 > > > > Try to point your browser to make sure you can actually download
 > classes
 > > > from it
 > > > > (point it to http://yourweblogic..../classes/some/class/name.class)
 > > > >
 > > > > Jason Donnell <[email protected]> wrote:
 > > > > > Yes, I know. That's the behavior that I had always seen before. Do
 > you
 > > > know
 > > > > > of any directory configurations or properties file settings that
 > could
 > > > make
 > > > > > the stub not be downloaded correctly, even though the EJB is
 > deployed on
 > > > the
 > > > > > server?
 > > >
 > > > > > "Tao Xie" <[email protected]> wrote in message
 > > > > > news:[email protected]...
 > > > > >> That's weird, Replica-aware stub should be downloaded to the
 client
 > > > except
 > > > > >> the client is on another Weblogic server.
 > > > > >>
 > > > > >> "Jason Donnell" <[email protected]> wrote in message
 > > > > >> news:[email protected]...
 > > > > >> | I am experiencing some weird behavior when attempting to access
 > EJBs
 > > > in
 > > > a
 > > > > >> | Weblogic 5.1.0 cluster. The cluster nodes startup fine, and the
 > EJBs
 > > > are
 > > > > >> | correctly deployed. However, when my test client attempts to
 > access
 > > > them
 > > > I
 > > > > >> | get the ClassNotFoundException listed below. This same client
 can
 > > > access
 > > > the
 > > > > >> | same EJBs deployed in a non-clustered environment without any
 > > > problems,
 > > > so
 > > > > >> | it's definitely related to my cluster configuration. The
 problem
 > > > seems
 > > > to
 > > > be
 > > > > >> | that the client is not receiving the client-side stub. To
 confim
 > > > this, I
 > > > put
 > > > > >> | the stub in the client's classpath, and did NOT get the
 > > > > >> | ClassNotFoundException. Has anyone else seen this error?
 > > > > >> |
 > > > > >> | BTW, I have compiled the EJB both with and without the
 > > > <home-is-clusterable>
 > > > > >> | flag set to true. I get the same exception either way.
 > > > > >> |
 > > > > >> | Thanks for any assistance,
 > > > > >> | Jason Donnell
 > > > > >> |
 > > > > >> |
 > > > > >> | javax.naming.CommunicationException. Root exception is
 > > > > >> | java.lang.ClassNotFoundException: class
 > > > > >> |
 > > > > >
 > > >
 > com.landacorp.maxmc.ejb.security.ProviderSecurityBeanHomeImpl_ServiceStub
 > > > > >> | previously not found
 > > > > >> |
 > > > > >> | at weblogic.rjvm.MsgAbbrev.read(MsgAbbrev.java:184)
 > > > > >> |
 > > > > >> | at
 > > > > >>
 > > >
 > weblogic.socket.JVMAbbrevSocket.readMsgAbbrevs(JVMAbbrevSocket.java:505)
 > > > > >> |
 > > > > >> | at
 > > >
 weblogic.rjvm.MsgAbbrevInputStream.prime(MsgAbbrevInputStream.java:134)
 > > > > >> |
 > > > > >> | at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:700)
 > > > > >> |
 > > > > >> | at
 > > > > >> |
 > > > > >>
 > > > > >
 > > >
 >
 weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
 > > > > >> | a:34)
 > > > > >> |
 > > > > >> | at
 > > > weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:630)
 > > > > >> |
 > > > > >> | at
 > > > weblogic.socket.JVMAbbrevSocket.dispatch(JVMAbbrevSocket.java:393)
 > > > > >> |
 > > > > >> | at weblogic.socket.JVMSocketT3.dispatch(JVMSocketT3.java:355)
 > > > > >> |
 > > > > >> | at
 > > > > >>
 > > >
 > weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:247)
 > > > > >> |
 > > > > >> | at
 > > > > >>
 > > >
 > weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 > > > > >> |
 > > > > >> | at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
 > > > > >> |
 > > > > >> |
 > > > > >> |
 > > > > >> | --------------- nested within: ------------------
 > > > > >> |
 > > > > >> | weblogic.rmi.UnmarshalException: Unmarshalling return
 > > > > >> | - with nested exception:
 > > > > >> | [java.lang.ClassNotFoundException: class
 > > > > >> |
 > > > > >
 > > >
 > com.landacorp.maxmc.ejb.security.ProviderSecurityBeanHomeImpl_ServiceStub
 > > > > >> | previously not found]
 > > > > >> |
 > > > > >> | at
 > > > > >> |
 > > > > >>
 > > > > >
 > > >
 >
 weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(BasicWLContext_WLStub.jav
 > > > > >> | a:256)
 > > > > >> |
 > > > > >> | at
 > > > weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
 > > > > >> |
 > > > > >> | at javax.naming.InitialContext.lookup(InitialContext.java:350)
 > > > > >> |
 > > > > >> | at
 > > > > >> |
 > > > > >>
 > > > > >
 > > >
 >
 com.landacorp.maxmc.ejb.security.ClusterSecurityTest.main(ClusterSecurityTes
 > > > > >> | t.java:52)
 > > > > >> |
 > > > > >> |
 > > > > >> |
 > > > > >> |
 > > > > >>
 > > > > >>
 > > > >
 > > > >
 > > > >
 > > > > --
 > > > > Dimitri
 >
 >
 >
 >
 >
 >

Problem with Dynamically accessing EJB Class objects in WL 7.0 SP1

I am trying to build a component which has the ability to instantiate and execute
an known EJB method on the fly.
I have managed to build the component but when I try and execute it I get a ClassNotFoundException.
I know that the EJB I am trying to invoke is deployed and available on the server,
as I can see it in the console, I also seen to have been able to get the remote
interface of the object, my problem occurs when I try and access the class object
so I can perform a create on the object and then execute my method
The code I have written is below:
private Object getRemoteObject(Context pCtx, String pJNDIName, String pHomeBean)
throws Exception {
 String homeCreate = "create";
 Class []homeCreateParam = { };
 Object []homeCreateParamValues = {};
try {
//This call seems to work and doesn't throw an exception
Object home = pCtx.lookup(pJNDIName);
//However this call throws a java.lang.ClassNotFoundException
Class homeBean = Class.forName(pHomeBean);
Method homeCreateMethod = homeBean.getMethod(homeCreate,homeCreateParam);
return homeCreateMethod.invoke(home, homeCreateParamValues);
} catch (NamingException ne) {
logStandardErrorMessage("The client was unable to lookup the EJBHome.
Please make sure ");
logStandardErrorMessage("that you have deployed the ejb with the JNDI
name "+pJNDIName+" on the WebLogic server ");
throw ne;
} catch (Exception e) {
logStandardErrorMessage(e.toString());
throw e;
Any advice would be really appreciated, I'm fast running out of ideas, I suspect
it has something to do with the class loader but I'm not sure how to resolve it
Regards
Jo Corless

Hello Joanne,
Congratulations! I'm very happy that you've managed to fix your problem. It's
always essential to understand how to package applications when deploying on BEA
WebLogic. Usually, by throwing everything into an EAR file solves just about all
the class loader problems. :-) Let us know if you have any further problems that
we can assist you with.
Best regards,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
"Joanne Corless" <[email protected]> wrote:
>
>
I've fixed it!!!!!!!!
Thanks to everyone who gave me help!!!!
The class loader was the culprit which is what I suspected all along.
As soon
as I put the 2 jar files I was using into an EAR file the problem went
away!!!!!
Thanks again
Jo Corless
"Ryan LeCompte" <[email protected]> wrote:
Hello Joanne,
As Mr. Woollen mentioned, I also believe it's a problem with the class
loader.
You need to be careful how you arrange your EJBs, because WebLogic has
a specific
method in which it loads classes in an EAR, JAR, and WAR file(s). Please
refer
to http://dev2dev.bea.com/articles/musser.jsp for more information about
BEA WebLogic
class loading mechanisms and caveats. Also, try printing out the various
methods
that are available on the object that was returned to you via reflection.
For
example, use the getMethods() method, which returns an array of Method
objects
that you can subsequently cycle through and print out the various method
names.
This way you can discover if the class found/returned to you is indeed
the one
you intend to locate.
Hope this helps,
Ryan LeCompte
[email protected]
http://www.louisiana.edu/~rml7669
Rob Woollen <[email protected]> wrote:
I believe the issue is the home interface class for this EJB is not
available in the class loader which is doing the reflection.
If you do:
getClass().getClassLoader().loadClass(homeInterfaceClassName)
I suspect it will fail. Reflection still requires that the class be
loadable.
-- Rob
Joanne Corless wrote:
Hi Slava,
If I make my code look like you describe below I get a compliationerror telling
me that
home.getMethod() is not recognised (no such method)
If I change it slightly and use
Method homeCreateMethod =
home.getClass().getMethod(homeCreate,homeCreateParam);
The code will compile OK but when executed it still throws a NoSuchMethodException
Any ideas ?
Thanks for your help so far
Regards
Jo Corless
Your code should look like
Object home = pCtx.lookup(pJNDIName);
Method homeCreateMethod =
home.getMethod(homeCreate,homeCreateParam);
return homeCreateMethod.invoke(home, homeCreateParamValues);
Regards,
Slava Imeshev
"Joanne Corless" <[email protected]> wrote in message
news:[email protected]...
Hi Ryan,
I also wanted to mention that if you do a "header search" in this
particular
newsgroup
with the search query as "reflection", you will see many previousmessages
regarding
reflection and EJBs. I believe you could learn a lot from thedifficulties
that
others have faced and solved.I tried that and although there was a number of similar cases noneof them
actually
seem to fix my issue. Thanks for the suggestion though
Are the EJBs that you are trying to access accessible via your
system
classpath?
Try to avoid having them accessible via the main system classpath,and
only bundle
them in your appropriate EJB jar files (contained in an EAR file,for
example).Maybe I should have laid the problem out a little clearer.
I have a number of EJB's bundled up in a JAR file which is hot deployedto
the
server. Within this first JAR file is an EJB (SSB) component that
needs
to
be
able to invoke a known method on another EJB. This second EJB may
or
may
not be
within the first JAR file but it also will be hot deployed.
The component trying to invoke the method on the 2nd EJB has to
be
able to
create
an instance of the 2nd EJB without actually knowing anything bar
a
JNDI
Name which
is passed in at runtime.
I can get as far as doing the
Object home = pCtx.lookup(pJNDIName);
This returned a class with the name
"com.csc.edc.projects.allders.httppostoffice.postman.PostmanBean_mp8qy2_Home
Impl_WLStub"
My problem seems to occur when I try and invoke the create method
Method homeCreate = home.getClass().getMethod("create", new Class[0]);
My code throws a java.lang.NoSuchMethodException at this point so
I
am
unable
to progress to the next step of :
Object bean = homeCreate.invoke(home, null);
So I can return the instantiated bean back to the calling client.
Why am I getting the NoSuchMethodException, is is because I am gettinga
stub
back rather than the home interface and if so how do I get the truehome
interface
from the bean
Thanks in advance
Jo Corless

Help - using custom login module with embedded jdev oc4j to access ejb 3

Hi All (Frank ??),
I'm just wondering if anyone has successfully been able to leverage a custom login module in combination
with a client that connects to a local EJB 3 stateless session bean through Jdeveloper 10.1.3.2's embedded oc4j.
I have spent 2+ days trying to get this to work - and i think I resound now to the fact im going to
have to deploy to oc4j standalone instead.
I got close.. but finally was trumped with the following error from the client trying to access the ejb:-
javax.naming.NoPermissionException: Not allowed to look up XXXXXX, check the namespace-access tag
setting in orion-application.xml for details.
Using the various guides available, I had no problem getting the custom login module working
with a local servlet running from JDev's embedded oc4j.. however with ejb - no such luck.
I have a roles table (possible values Member, Admin) - that maps to sr_Member and sr_Admin
respectively in various config files.
I'm using EJB 3 annotations for protecting methods .. for example
@RolesAllowed("sr_Member")
Steps that I had to do so far :-
In <jdevhome>\jdev\system\oracle.jwee.10.1.3.40.66\embedded-oc4j\config\system-jazn-data.xml1) Add custom login module
 <application>
 <name>current-workspace-app</name>
 <login-modules>
 <login-module>
 <class>kr.security.KnowRushLoginModule</class>
 <control-flag>required</control-flag>
 <options>
 <option>
 <name>dataSource</name>
 <value>jdbc/DB_XE_KNOWRUSHDS</value>
 </option>
 <option>
 <name>user.table</name>
 <value>users</value>
 </option>
 <option>
 <name>user.pk.column</name>
 <value>id</value>
 </option>
 <option>
 <name>user.name.column</name>
 <value>email_address</value>
 </option>
 <option>
 <name>user.password.column</name>
 <value>password</value>
 </option>
 <option>
 <name>role.table</name>
 <value>roles</value>
 </option>
 <option>
 <name>role.to.user.fk.column</name>
 <value>user_id</value>
 </option>
 <option>
 <name>role.name.column</name>
 <value>name</value>
 </option>
 </options>
 </login-module>
 </login-modules>
 </application>2) Grant login rmi permission to roles associated with custom login module (also in system-jazn-data.xml)
<grant>
 <grantee>
 <principals>
 <principal>
 <realm-name>jazn.com</realm-name>
 <type>role</type>
 <class>kr.security.principals.KRRolePrincipal</class>
 <name>Admin</name>
 </principal>
 </principals>
 </grantee>
 <permissions>
 <permission>
 <class>com.evermind.server.rmi.RMIPermission</class>
 <name>login</name>
 </permission>
 </permissions>
</grant>
<grant>
 <grantee>
 <principals>
 <principal>
 <realm-name>jazn.com</realm-name>
 <type>role</type>
 <class>kr.security.principals.KRRolePrincipal</class>
 <name>Member</name>
 </principal>
 </principals>
 </grantee>
 <permissions>
 <permission>
 <class>com.evermind.server.rmi.RMIPermission</class>
 <name>login</name>
 </permission>
 </permissions>
</grant>3) I've tried creating various oracle and j2ee deployment descriptors (even though ejb-jar.xml and orion-ejb-jar.xml get created automatically when running the session bean in jdev).
My ejb-jar.xml contains :-
<?xml version="1.0" encoding="utf-8"?>
<ejb-jar xmlns ....
<assembly-descriptor>
 <security-role>
 <role-name>sr_Admin</role-name>
 </security-role>
 <security-role>
 <role-name>sr_Member</role-name>
 </security-role>
</assembly-descriptor>
</ejb-jar>Note- i'm not specifying the enterprise-beans stuff, as JDev seems to populate this automatically.
My orion-ejb-jar.xml contains ...
<?xml version="1.0" encoding="utf-8"?>
<orion-ejb-jar ...
<assembly-descriptor>
 <security-role-mapping name="sr_Admin">
 <group name="Admin"></group>
 </security-role-mapping>
 <security-role-mapping name="sr_Member">
 <group name="Member"></group>
 </security-role-mapping>
 <default-method-access>
 <security-role-mapping name="sr_Member" impliesAll="true">
 </security-role-mapping>
 </default-method-access>
</assembly-descriptor>My orion-application.xml contains ...
<?xml version="1.0" encoding="utf-8"?>
<orion-application xmlns ...
<security-role-mapping name="sr_Admin">
 <group name="Admin"></group>
</security-role-mapping>
<security-role-mapping name="sr_Member">
 <group name="Member"></group>
</security-role-mapping>
<jazn provider="XML">
 <property name="role.mapping.dynamic" value="true"></property>
 <property name="custom.loginmodule.provider" value="true"></property>
</jazn>
<namespace-access>
 <read-access>
 <namespace-resource root="">
 <security-role-mapping name="sr_Admin">
 <group name="Admin"/>
 <group name="Member"/>
 </security-role-mapping>
 </namespace-resource>
 </read-access>
 <write-access>
 <namespace-resource root="">
 <security-role-mapping name="sr_Admin">
 <group name="Admin"/>
 <group name="Member"/>
 </security-role-mapping>
 </namespace-resource>
 </write-access>
</namespace-access>
</orion-application>My essentially auto-generated EJB 3 client does the following :-
 Hashtable env = new Hashtable();
 env.put(Context.SECURITY_PRINCIPAL, "matt.shannon");
 env.put(Context.SECURITY_CREDENTIALS, "welcome1");
 final Context context = new InitialContext(env);
 KRFacade kRFacade = (KRFacade)context.lookup("KRFacade");
...And throws the error
20/04/2007 00:55:37 oracle.j2ee.rmi.RMIMessages
EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER
WARNING: Exception returned by remote server: {0}
javax.naming.NoPermissionException: Not allowed to look
up KRFacade, check the namespace-access tag setting in
orion-application.xml for details
 at
com.evermind.server.rmi.RMIClientConnection.handleLookupRe
sponse(RMIClientConnection.java:819)
 at
com.evermind.server.rmi.RMIClientConnection.handleOrmiComm
andResponse(RMIClientConnection.java:283)
....I can see from the console that the user was successfully authenticated :-
20/04/2007 00:55:37 kr.security.KnowRushLoginModule validate
WARNING: [KnowRushLoginModule] User matt.shannon authenticated
And that user is granted both the Admin, and Member roles.
The test servlet using basic authentication correctly detects the user and roles perfectly...
public void doGet(HttpServletRequest request,
 HttpServletResponse response)
 throws ServletException, IOException
 LOGGER.log(Level.INFO,LOGPREFIX +"doGet called");
 response.setContentType(CONTENT_TYPE);
 PrintWriter out = response.getWriter();
 out.println("<html>");
 out.println("<head><title>ExampleServlet</title></head>");
 out.println("<body>");
 out.println("The servlet has received a GET. This is the reply.");
 out.println(" getRemoteUser = " + request.getRemoteUser());
 out.println(" getUserPrincipal = " + request.getUserPrincipal());
 out.println(" isUserInRole('sr_Admin') = "+request.isUserInRole("sr_Admin"));
 out.println(" isUserInRole('sr_Memeber') = "+request.isUserInRole("sr_Member"));Anyone got any ideas what could be going wrong?
cheers
Matt.
Message was edited by:
mshannon

Thanks for the response. I checked out your blog and tried your suggestions. I'm sure it works well in standalone OC4J, but i was still unable to get it to function correctly from JDeveloper embedded.
Did you ever get the code working directly from JDeveloper?
Your custom code essentially seems to be the equivalent of a grant within system-jazn-data.xml.
For example, the following grant to a custom jaas role (JAAS_ADMIN) that gets added by my custom login module gives them rmi login access :-
 <grant>
 <grantee>
 <principals>
 <principal>
 <realm-name>jazn.com</realm-name>
 <type>role</type>
 <class>kr.security.principals.KRRolePrincipal</class>
 <name>JAAS_Admin</name>
 </principal>
 </principals>
 </grantee>
 <permissions>
 <permission>
 <class>com.evermind.server.rmi.RMIPermission</class>
 <name>login</name>
 </permission>
 </permissions>
 </grant>If I add the following to orion-application.xml

<namespace-access>
 <read-access>
 <namespace-resource root="">
 <security-role-mapping>
 <group name="JAAS_Admin"></group>
 </security-role-mapping>
 </namespace-resource>
 </read-access>Running a standalone client against the embedded jdev oc4j server gives the namespace-access error.
I tried out your code by essentially creating a static reference to a singleton class that does the role lookup/provisioning with rmi login grant :-
From custom login module :-
private static KRSecurityHelper singleton = new KRSecurityHelper();
protected Principal[] m_Principals;
 Vector v = new Vector();
 v.add(singleton.getCustomRmiConnectRole());
 // set principals in LoginModule
 m_Principals=(Principal[]) v.toArray(new Principal[v.size()]);
Singleton class :-
package kr.security;
import com.evermind.server.rmi.RMIPermission;
import java.util.logging.Level;
import java.util.logging.Logger;
import oracle.security.jazn.JAZNConfig;
import oracle.security.jazn.policy.Grantee;
import oracle.security.jazn.realm.Realm;
import oracle.security.jazn.realm.RealmManager;
import oracle.security.jazn.realm.RealmRole;
import oracle.security.jazn.realm.RoleManager;
import oracle.security.jazn.policy.JAZNPolicy;
import oracle.security.jazn.JAZNException;
public class KRSecurityHelper
private static final Logger LOGGER = Logger.getLogger("kr.security");
private static final String LOGPREFIX = "[KRSecurityHelper] ";
public static String CUSTOM_RMI_CONNECT_ROLE = "remote_connect";
private RealmRole m_Role = null;
public KRSecurityHelper()
 LOGGER.log(Level.FINEST,LOGPREFIX +"calling JAZNConfig.getJAZNConfig");
 JAZNConfig jc = JAZNConfig.getJAZNConfig();
 LOGGER.log(Level.FINEST,LOGPREFIX +"calling jc.getRealmManager");
 RealmManager realmMgr = jc.getRealmManager();
 try
 // Get the default realm .. e.g. jazn.com
 LOGGER.log(Level.FINEST,LOGPREFIX +"calling jc.getGetDefaultRealm");
 Realm r = realmMgr.getRealm(jc.getDefaultRealm());
 LOGGER.log(Level.INFO,LOGPREFIX +"default realm: "+r.getName());
 // Access the role manager for the remote connection role
 LOGGER.log(Level.FINEST,
 LOGPREFIX +"calling default_realm.getRoleManager");
 RoleManager roleMgr = r.getRoleManager();
 LOGGER.log(Level.INFO,LOGPREFIX +"looking up custom role '"
 CUSTOM_RMI_CONNECT_ROLE "'");
 RealmRole rmiConnectRole = roleMgr.getRole(CUSTOM_RMI_CONNECT_ROLE);
 if (rmiConnectRole == null)
 LOGGER.log(Level.INFO,LOGPREFIX +"role does not exist, create it...");
 rmiConnectRole = roleMgr.createRole(CUSTOM_RMI_CONNECT_ROLE);
 LOGGER.log(Level.FINEST,LOGPREFIX +"constructing new grantee");
 Grantee gtee = new Grantee(rmiConnectRole);
 LOGGER.log(Level.FINEST,LOGPREFIX +"constructing login rmi permission");
 RMIPermission login = new RMIPermission("login");
 LOGGER.log(Level.FINEST,
 LOGPREFIX +"constructing subject.propagation rmi permission");
 RMIPermission subjectprop = new RMIPermission("subject.propagation");
 // make policy changes
 LOGGER.log(Level.FINEST,LOGPREFIX +"calling jc.getPolicy");
 JAZNPolicy policy = jc.getPolicy();
 if (policy != null)
 LOGGER.log(Level.INFO, LOGPREFIX
 + "add to policy grant for RMI 'login' permission to "
 + CUSTOM_RMI_CONNECT_ROLE);
 policy.grant(gtee, login);
 LOGGER.log(Level.INFO, LOGPREFIX
 + "add to policy grant for RMI 'subject.propagation' permission to "
 + CUSTOM_RMI_CONNECT_ROLE);
 policy.grant(gtee, subjectprop);
 // m_Role = rmiConnectRole;
 m_Role = roleMgr.getRole(CUSTOM_RMI_CONNECT_ROLE);
 LOGGER.log(Level.INFO, LOGPREFIX
 + m_Role.getName() + ":" + m_Role.getFullName() + ":" + m_Role.getFullName());
 else
 LOGGER.log(Level.WARNING,LOGPREFIX +"Cannot find jazn policy!");
 else
 LOGGER.log(Level.INFO,LOGPREFIX +"custom role already exists");
 m_Role = rmiConnectRole;
 catch (JAZNException e)
 LOGGER.log(Level.WARNING,
 LOGPREFIX +"Cannot configure JAZN for remote connections");
public RealmRole getCustomRmiConnectRole()
 return m_Role;
}Using the code approach and switching application.xml across so that namespace access is for the group remote_connect, I get the following error from my bean :-
INFO: Login permission not granted for current-workspace-app (test.user)
Thus, the login permission that I'm adding through the custom remote_connect role does not seem to work. Even if it did, i'm pretty sure I would still get that namespace error.
This has been such a frustrating process. All the custom login module samples using embedded JDeveloper show simple j2ee servlet protection based on settings in web.xml.
There are no samples showing jdeveloper embedded oc4j using ejb with custom login modules.
Hopefully the oc4j jdev gurus like Frank can write a paper that demonstrates this.
Matt.

Can't access EJB deployed on remote OC4J - what am I doing wrong?

I'm unable to access an EJB deployed on a remote OC4J instance (ie, part of a 9iAS installation on another machine vs local in JDeveloper).
I've reverted to a stupid-simple EJB in hopes of getting it going prior to trying my actual code. The EJB works fine in JDev (9.0.3) - I 'run' the EJB to start the local OC4J instance, run my client code (generated via the "New Sample Java Client..." option in the Navigator context popup) and all is well.
I then create an EAR file via the the "Create EJB Jar Deployment Profile..." context popup of the ejb-jar.xml node, followed by "Deploy to EAR file" from the context popup of the resulting ejb1.deploy node. I next "Deploy EAR File" via the "Oracle Enterprise Manager" that comes with 9iAS (the :1810 port). After successfully deploying, I modify my client code in JDeveloper, specifying the new connection information for the remote machine via the Hashtable constructor of InitialContext and attempt to run it. I've tried a number of Context.PROVIDER_URL forms, including: ormi://registered_pingable_host_name:23791/deployed_application_name
ormi://registered_pingable_host_name:23791/session_deployment_name (from the <enterprise-beans><session-deployment name="xxx"/></enterprise-beans> section of my orion-ejb-jar.xml file, as per a tip in this forum)
I've tried prefixing ormi:// with http:, but get no response whatesoever in this case.
I've also tried it without the port number (this port number matches that in my remote OC4J's <oc4j_instance_home>/config/rmi.xml file).
On the Context.SECURITY_PRINCIPAL and Context.SECURITY_CREDENTIALS settings, I've tried various values, generally using the 'admin' user, with passwords taken from:
<oc4j_instance_home>/principals.xml
<oc4j_instance_home>/application-deployments/application_name/principals.xml
I've also tried matching the password in the jazn-data.xml, to no avail - this password appears encrypted anyway, but thought I'd give it a try on the off-chance that it was just a randomly-generated password - no go.
I've also tried SCOTT/TIGER, anonymous, etc. Incidentally, the 'deactivated' attribute of the <user> tag is set to "false" in my principals.xml files.
No matter what I do, I always get back "javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect"
Additionally, I get this same message when I try to establish an Application Server Connection via JDev.
Clearly, I'm missing something critical (and probably simple), but I can't for the life of me figure it out.
Any help would be much appreciated!
Thanks,
Jim Stoll

Ok, well this is a bit strange...
3103 - 3103 also fails, and some experimentation has led me to find that any time that I specify a range smaller than 6 (3101 - 3106 works, 3101 - 3105, 3101-3101, 3103-3103, etc does not), the OC4J instance will not restart. I get "An error occurred while starting. The opmn request has failed. From opmn: HTTP/1.1 204 No Content Content-Length: 0 Content-Type: text/html Response: 0 of 1 processes started. Check opmn log files such as ipm.log and ons.log for detailed." in the OEM window (I specify the RMI port range, hit Apply, go to the OC4J instance home page, see that the Status is 'Down', hit Start, and get that message.) <ORACLE_HOME>/product/iasinfra/opmn/logs/ipm.log tells me:
02/12/03 09:41:12 There is no rmi port left for starting an OC4J process. Please check oc4j's port property in OPMN's configuration file.
02/12/03 09:41:12 start_proc: UID 3719788: failed to build args
02/12/03 09:41:12 start_proc_req: failed to start a process in GID OC4JJim2, type: 2
If I bump it up to 3101 - 3106 or higher, it starts right up. Running opmnadmin debug, as suggested by Venky (thanks Venky!), yields:
PROCESS TABLE
UID PID FLAGS TYPE STATUS REF HTTP AJP RMI JMS
3654011 84 00000040 OC4J Alive 1 0 3005 3106 3206
424987 604 00000000 Apache Alive 1 7777 0 0 0
2932088 14849 00000000 OC4J Alive 1 0 3003 3103 3203
3063160 14878 00000000 OC4J Alive 1 0 3001 3101 3201
3194232 14906 00000000 OC4J Alive 1 0 3000 3105 3205
3325304 14936 00000000 OC4J Alive 1 0 3002 3102 3202
3456376 14964 00000000 OC4J Alive 1 0 3004 3104 3204
Which is what I would expect, given the specified range of 3101-3106. Trying each of these ports in turn, I've found that I can hit the EJB successfully on 3106, but 3101 - 3105 all fail with:
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: No such domain/application: Project7_2; nested exception is:
 javax.naming.AuthenticationException: No such domain/application: Project7_2
 java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
 RMIContext.java:134
 java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
 InitialContext.java:350
 void Samplemypackage9.MySessionEJBClient1.main(java.lang.String[])
 MySessionEJBClient1.java:15
I'm a little concerned about assuming the high-end of the range to be the active port on a regular basis (though thus far, among about 20 - 30 tries spaced over 20 - 30 minutes, it has been...) - I guess I can have my code loop through the range until it finds a good port or exhausts the list, but that seems a bit excessive.
Can you think of a reason that my OC4J instance won't start with a range size of less than 6? I'm on 9iAS 9.0.2, if that makes any difference.
Thanks,
Jim

Command bean or webservice for accessing EJB

Similar Messages

Maybe you are looking for