Deployement of ejb class in xi server

hi all
i have to deploy my ejb class on xi server.can anybody tell me what will be the procedure

try this
/people/alessandro.guarneri/blog/2006/10/13/get-rid-of-recordset-node
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bc7f08e1-0901-0010-b1bd-80966009d8f0
http://help.sap.com/saphelp_nw2004s/helpdata/en/40/00be09879f114aa1ec46c2afa4445b/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9221b490-0201-0010-0e90-8cc75cde876c
http://help.sap.com/saphelp_webas630/helpdata/en/cb/f4bc3d42f46c33e10000000a11405a/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/eaeb475d-0c01-0010-f5a4-d7a8eb185793
Thanks

Similar Messages

Hi i when i am trying to deploy an EJB module on weblogic server i get the

Hi all,
when i am trying to deploy an EJB module on weblogic server i get the the following exception on the server.
Exception:weblogic.management.ApplicationException: prepare failed for test Module: test Error: Exception preparing module: EJBModule(test,status=NEW) Unable to deploy EJB: D:\bea\weblogic81b\server\bin\myserver\upload\test.jar from test.jar: weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: Class bytes found but defineClass()failed for: 'HelloBean' at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:525) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.(MBeanDeploymentInfoImpl.java:230) at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1256) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:449) at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2792) at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1478) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1136) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:975) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2571) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2523) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2453) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:820) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:536) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:494) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
[Deployer:149033]preparing application test on myserver
[Deployer:149033]failed application test on myserver
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application test on myserver.: Exception:weblogic.management.ApplicationException: prepare failed for test Module: test Error: Exception preparing module: EJBModule(test,status=NEW) Unable to deploy EJB: D:\bea\weblogic81b\server\bin\myserver\upload\test.jar from test.jar: weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: Class bytes found but defineClass()failed for: 'HelloBean' at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:525) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.(MBeanDeploymentInfoImpl.java:230) at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1256) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:449) at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2792) at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1478) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1136) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:975) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2571) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2523) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2453) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:820) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:536) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:494) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at weblogic.kernel.ExecuteThread.run(ExecuteThread

Hi, i am also facing the same problem.......
my ejb-jar.xml is
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar >
<description><![CDATA[No Description.]]></description>
<display-name>Generated by XDoclet</display-name>
<enterprise-beans>



<entity >
<description><![CDATA[Description for Account]]></description>
<display-name>Name for Account</display-name>
<ejb-name>Account</ejb-name>
<home>com.app.j2ee.bmp.interfaces.AccountHome</home>
<remote>com.app.j2ee.bmp.interfaces.Account</remote>
<local-home>com.app.j2ee.bmp.interfaces.AccountLocalHome</local-home>
<local>com.app.j2ee.bmp.interfaces.AccountLocal</local>
<ejb-class>com.app.j2ee.bmp.ejb.AccountBean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>com.app.j2ee.bmp.interfaces.AccountPK</prim-key-class>
<reentrant>False</reentrant>
          <resource-ref>
          <res-ref-name>jdbc/ejbPool</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
          </resource-ref>
</entity>
</enterprise-beans>



<assembly-descriptor >










<container-transaction>
          <method>
          <ejb-name>Account</ejb-name>
          <method-intf>Local</method-intf>
          <method-name>*</method-name>
          </method>
          <method>
          <ejb-name>Account</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
     </container-transaction>
</assembly-descriptor>
</ejb-jar>

Fundamental question: Integrating non-EJB classes

Hi there,
sorry to ask that, but how can i integrate classes other than EJBs
into my assembled application ? i use sun's deploytool and their ri
application server.
my task is to call a class called J2EEManager at the app server
startup, which has to initialize some server-wide data. but how do
i call and integrate this class at deployment level ? in the deploytool
there isn't such a support. i do also use this class during runtime.
also i do not see how to integrate my helper classes that are needed
by the EJBs i developed. again, in deploytool i just can add my EJB's
but not all the other classes i implemented.
how does this work ? any hints, links, tutorials ? the examples i've
seen in books and articles mostly do not cover these things...
thank you very much. best regards
rivella50

When you call the "packager" tool, you can specify any classes you want to include in the package archives. They don't all have to be EJB classes or interfaces. I don't use the deploytool UI, but there should be a way to include extra files into the packages from within the UI mode.
As for performing extra functionality at server startup, I don't know of any way to do this. However you can create a separate (stand-alone) application that is run on the server machine, just after server startup:
j2ee &... wait until server is up and running ...
java J2EEManager <params>Ben

Can't access non ejb classes from JSP - NoClassDefFound error

          Hi,
          I have one session ejb which has a method returning a collection of non ejb class objects (say of Class 'Foo').
          The method signature is like :
          "Collection getFinacialData() throws RemoteException"
          It is working fine with normal java clients. Now when I run this from a JSP it gives a "NoClassDefFoundError". I kept class 'Foo' and the remote interface of the session bean in the same package and also in the same ejb jar file. Also I am running JSP and ejb in same WL server(ver 5.1, SP8 on solaris). What I have done is only deployed the bean jar file. Do I need to do anything more?
          thanks in advance.


I ran into a similar problem. I solved it by putting the client classes for
          accessing my EJB in the WebLogic POST_CLASSPATH in the startWebLogic script
          file:
          set POST_CLASSPATH=d:\weblogic\myserver\myClient.jar
          For more information on class visibility between the JSP and EJB class
          loaders, check out
          http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_deployover.html#1056256
          Rick
          "niroja" <[email protected]> wrote in message
          news:3a6ed903$[email protected]..
          >
          > Hi,
          >
          > I have one session ejb which has a method returning a collection of non
          ejb class objects (say of Class 'Foo').
          > The method signature is like :
          > "Collection getFinacialData() throws RemoteException"
          > It is working fine with normal java clients. Now when I run this from a
          JSP it gives a "NoClassDefFoundError". I kept class 'Foo' and the remote
          interface of the session bean in the same package and also in the same ejb
          jar file. Also I am running JSP and ejb in same WL server(ver 5.1, SP8 on
          solaris). What I have done is only deployed the bean jar file. Do I need to
          do anything more?
          >
          > thanks in advance.
          >

Locating EJB classes from JSP

Hi all,
I have some JSP that invoke Session Beans. My question is:
what is the right place to put EJB classes in order to be found by JSP ?
I have found the following solutions but they both slow down during development
phase:
1) Build an EAR and let the JSP reference EJB classes via the Class-Path attribute.
This is nice but a bit complex: I'd like to use EAR only for shipment phase and
not for every small change to the Bean.
2) Let WLS see the classes including them in the classpath at startup. But this
has the disadvantage that I have to restart WLS every time because - I suppose-
WLS isn't able to unload classes if I include them in the CLASSPATH
So what do you suggest me for development phase? is there a faster solution?
Thanks a lot
F.Marchioni

Hi Arjuna,
put it on the weblogic startup classpath.mmmmm well I think the JSP will not reload the EJB classes when I make a change
if they are on the classpath...unless I restart the server....I'll try again...I
hope I'm wrong...
thanks
Francesco
"Arjuna Chala" <[email protected]> wrote:
for testing
- put it on the weblogic startup classpath.
- use the console's hot deploy facility to re-deploy the ejb after changes.
This works well for me (WLS6.1).
Reagrds
Arjuna Chala
"Marchioni F." <[email protected]> wrote in message
news:3c5eae94$[email protected]..
Hi all,
I have some JSP that invoke Session Beans. My question is:
what is the right place to put EJB classes in order to be found byJSP ?
I have found the following solutions but they both slow down duringdevelopment
phase:
1) Build an EAR and let the JSP reference EJB classes via the Class-Pathattribute.
This is nice but a bit complex: I'd like to use EAR only for shipmentphase and
not for every small change to the Bean.
2) Let WLS see the classes including them in the classpath at startup.But
this
has the disadvantage that I have to restart WLS every time because- I
suppose-
WLS isn't able to unload classes if I include them in the CLASSPATH
So what do you suggest me for development phase? is there a fastersolution?
Thanks a lot
F.Marchioni

Startup Class in WebLogic server 6.1

I Have a Java application as startup class in Weblogic server 6.1 . I need to stop
the application without restarting the Weblogi server (The startup class should
be removed and the change should be reflected in WebLogic server). Is it possible
to achieve this. I Know that we can remove the startup class from the console
but the change is getting reflected only if i restart the WebLogic Server. Can
some one help me out ?.
Thanks,
S Gopikrishna

Even if it is EJB-only, adding .war with startup logic will be more convinient
than startup classes.
S Gopikrishna <[email protected]> wrote:
Hi
Thanks a lot for the info. My application is not servlet based rather not
web based. In this case how to solve my startupclass problem.
Regards,
S Gopikrishna
Dimitri Rakitine <[email protected]> wrote:
You can deploy web-app(stand-alone, or as a part of an EAR), which has
servlets marked as
load-on-startup (in that case you can use servlet's init() method to
perform your startup
logic), or has servlet context listeners registered
(http://e-docs.bea.com/wls/docs61/webapp/app_events.html#177041) - contextInitialized()
callback will be called when application is deployed, and contextDestroyed()
will be called when application is undeployed.
S Gopikrishna <[email protected]> wrote:
Thanks a lot for the info. Iam pretty new to WeblogicServer. Can utell me about
how to use load-on-startup servlets or application listeners ?.
Thanks in Advance
S Gopikrishna
Dimitri Rakitine <[email protected]> wrote:
You can look into using load-on-startup servlets or application listeners
instead
of startup classes in 6.1 - that way you can redeploy your application
and re-execute
it's startup logic without placing any classes in the system classpath
or restarting
WebLogic.
S Gopikrishna <[email protected]> wrote:
I Have a Java application as startup class in Weblogic server 6.1
I need to stop
the application without restarting the Weblogi server (The startupclass should
be removed and the change should be reflected in WebLogic server).Is it possible
to achieve this. I Know that we can remove the startup class from
the
console
but the change is getting reflected only if i restart the WebLogicServer. Can
some one help me out ?.
Thanks,
S Gopikrishna--
Dimitri--
Dimitri
Dimitri

How can one invoke a WebLogic EJB from a BPEL Server hosted on OC4J?

How can one invoke a WebLogic EJB from a BPEL Server hosted on OC4J?
Reason I ask is I keep getting this error:
javax.naming.NoInitialContextException: Cannot instantiate cla
ss: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotF
oundException: weblogic.jndi.WLInitialContextFactory]
Note: I am using <bpelx:exec> as a way to execute some java program.
Essentially my java client (essentially an EJB client hosted on Oc4J) needs access to wlclient.jar since it needs access to weblogic.jndi.WLInitialContextFactory. I have a EJB client running on BPEL server hosted on Oc4J that needs to access some EJBs hosted on weblogic.
Where do I place this wlclient.jar so that BPEL PM can start peacefully and at runtime discover the InitialContextFactory classes?
Placing it in the j2ee/home/applib doesn't solve the problem. The server fails to start up if I do this
I tried placing it in BPEL-INF\lib directory ...
I still get the same exception...see below for exception dump
I verified the BPEL suitcase, and it in fact does contain the jar file wlclient.jar
integration\orabpel\domains\default\deploy contains the bpel_BPELProcess2_1.0.jar file and snapshot of that is as follows:
<PRE>
│ bpel.xml
│ BPELProcess2.bpel
│ BPELProcess2.jpr
│ BPELProcess2.wsdl
│ bpel_BPELProcess2_1.0.jar
│ build.xml
│ buildxml.copy
│ graphics.xml
│
├───BPEL-INF
│ └───lib
│ myEJB.jar
│ wlclient.jar
│
├───META-INF
│ MANIFEST.MF
│
└───output
bpel_BPELProcess2_1.0.jar
</PRE>
I tried using the BPEL-INF\jar directory...Is this something the obant automatically detects? or do I have to modify the build.xml? I created this directory and let Jdev deploy to local BPEL server->default domain handle it
#####################3
I even tried copying the wlclient.jar to
integration\orabpel\system\classes but this doesn't help since the BPEL PM fails to start if I explode this jar into this directory.
In short,where do I place the wlclient.jar so that this exception can be contained.
I edited the build.xml to point to the jar, that too didn't work, unless I made some mistake in the file
<bpelc classpath="${basedir}/BPEL-INF/classes;${home}/system/classes;${home}/lib/j2ee_1.3.01.jar;${basedir}/BPEL-INF/jar/wlclient.jar" input="${basedir}/bpel.xml" rev="${rev}" deploy="${deploy}" />
</target>
</project>
DETAILS on ERROR
I get the following error
Process "BPELProcess2" (revision "1.0") successfully compiled.
<2005-12-14 09:17:55,770> <INFO> <default.collaxa.cube.engine.deployment> Proces
s "BPELProcess2" (revision "1.0") successfully loaded.
05/12/14 09:18:36 weblogic.jndi.WLInitialContextFactory
javax.naming.NoInitialContextException: Cannot instantiate cla
ss: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotF
oundException: weblogic.jndi.WLInitialContextFactory]
05/12/14 09:18:36 at javax.naming.spi.NamingManager.getInitialContext(Nami
ngManager.java:652)
05/12/14 09:18:36 at javax.naming.InitialContext.getDefaultInitCtx(Initial
Context.java:243)
05/12/14 09:18:36 at javax.naming.InitialContext.init(InitialContext.java:
219)
05/12/14 09:18:36 at javax.naming.InitialContext.<init>(InitialContext.jav
a:195)
05/12/14 09:18:36 at com.ejb.test.MapFinder.getDefaultMapName(Map
Finder.java:37)
##################3
with the bpelx all I have is two lines of code that creates a java object and calls a method on it.
The method does this:
    private String initialContextFactory = "weblogic.jndi.WLInitialContextFactory";
    private String providerUrl = "t3://localhost:7001";
    private String urlPkgPrefixes = "";
    private String mapEjbJndiName = "ejb/mycompany/Redlands";
    public String getDefaultMapName() {
      try {
          Hashtable env = new Hashtable();
          env.put(Context.INITIAL_CONTEXT_FACTORY, getInitialContextFactory());
          env.put(Context.PROVIDER_URL, getProviderUrl());
          if (getUrlPkgPrefixes() != null && !getUrlPkgPrefixes().equals(""))
              env.put(Context.URL_PKG_PREFIXES, getUrlPkgPrefixes());
          System.out.println("    " + getInitialContextFactory());
          System.out.println("    " + getProviderUrl());
          System.out.println("    " + getUrlPkgPrefixes());
          System.out.println("    " + getEjbName());
          // Get a naming context
          context = new InitialContext(env);
           Object ms = context.lookup(getEjbName());
          MyEJBHome home = (MyEJBHome ) PortableRemoteObject.narrow(ms, MyEJBHome.class);
          myEjb = home.create();
          return myEjb.getDefaultName();
      } catch (RemoteException re){
          System.out.println(re.getCause().getMessage());
      catch (Exception ex) {
          ex.printStackTrace();
      return null; //if unable to resolve the context factory etc...
    }

I did exactly as you suggested. I edited the application.xml and added this
<library path="C:\ArcGIS\test\bea\wlclient.jar"/>
I didn't add weblogic because the needed classes were all in wlclient.jar
I also edited the BASE_OB_CLASSPATH to include this jar.
Here is the result when I just start BPEL PM Server. Somehow BPEL PM doesn't like to have wlclient.jar in its classpath during startup.
Failed to create "worker" bean; exception reported is: "javax.naming.NameNotFoun
dException: remaining name: env
at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:49)
at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:57)
at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:62)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.collaxa.cube.engine.ejb.impl.WorkerBean.ejbCreate(WorkerBean.java
:49)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.evermind.server.ejb.MessageDrivenHome.getInstance(MessageDrivenHo
me.java:1235)
at com.evermind.server.ejb.MessageDrivenHome$2.run(MessageDrivenHome.jav
a:1150)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(Relea
sableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
<2005-12-29 13:39:05,281> <ERROR> <collaxa> <ServerManager::loadAllDomains>
ORABPEL START-UP ERROR!!!!!!!!
OraBPEL run-time system failed to start due to exception:
Could not initialize jms connection pool.
Could not initialize connection pool for connection factory "java:comp/env/jms/
ollaxa/BPELInvokerQueueFactory"; the reason is remaining name: env/jms/collaxa/
PELInvokerQueueFactory.
Note: So what I did was to removed the entry from application.xml and tried with just obsetenv.bat having the wlclient.jar added to it. This too failed!!
Here is a snapshot of the error I got.
Process "BPELProcess2" (revision "1.0") successfully compiled.
<2005-12-29 13:53:11,207> <INFO> <default.collaxa.cube.engine.deployment> Proces
s "BPELProcess2" (revision "1.0") successfully loaded.
05/12/29 13:53:32 Cannot instantiate class: weblogic.jndi.WLInitialContextFactor
y
05/12/29 13:53:32 javax.naming.NoInitialContextException: Cannot instantiate cla
ss: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotF
oundException: weblogic.jndi.WLInitialContextFactory]
05/12/29 13:53:32 at javax.naming.spi.NamingManager.getInitialContext(Nami
ngManager.java:652)
05/12/29 13:53:32 at javax.naming.InitialContext.getDefaultInitCtx(Initial
Context.java:243)
05/12/29 13:53:32 at javax.naming.InitialContext.init(InitialContext.java:
219)
05/12/29 13:53:32 at javax.naming.InitialContext.<init>(InitialContext.jav
a:195)
05/12/29 13:53:32 at com.esri.adf.ejb.test.MapFinder.getDefaultMapName(Map
Finder.java:57)
05/12/29 13:53:32 at bpel.p0.ExecLetBxExe1.execute(ExecLetBxExe1.java:62)
05/12/29 13:53:32 at com.collaxa.cube.engine.ext.wmp.BPELXExecWMP.__execut
eStatements(BPELXExecWMP.java:49)
05/12/29 13:53:32 at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perfo
rm(BPELActivityWMP.java:185)
05/12/29 13:53:32 at com.collaxa.cube.engine.CubeEngine.performActivity(Cu
beEngine.java:3398)
05/12/29 13:53:32 at com.collaxa.cube.engine.CubeEngine.handleWorkItem(Cub
eEngine.java:1905)
05/12/29 13:53:32 at com.collaxa.cube.engine.dispatch.message.instance.Per
formMessageHandler.handleLocal(PerformMessageHandler.java:75)
05/12/29 13:53:32 at com.collaxa.cube.engine.dispatch.DispatchHelper.handl
eLocalMessage(DispatchHelper.java:100)
05/12/29 13:53:32 at com.collaxa.cube.engine.dispatch.DispatchHelper.sendM

Problem with Embedded OC4J - Can find EJB class???

I am getting the following error when starting my application within JDeveloper.
05/06/22 16:11:35 Error instantiating application 'current-workspace-app' at file:/C:/developc/developc-oc4j-app.xml: Error initializing ejb-module; Exception Error loading class 'com.syncra.ct.server.AggregatesManagerBean': java.lang.ExceptionInInitializerError: java.lang.NullPointerException
It never reaches breakpoints in the class. So, I assume that it can't find the class in the classpath. But, when I look at the developc-oc4j-app.xml file see the following:
<ejb-module path="file:/C:/developc/Model/classes/"/>
<web-module id="developc-ViewController-webapp" path="C:\developc\ViewController\public_html"/>
and the ejb class is in the correct spot. Any help would be greatly appreciated. I am on JDeveloper 10.1.2.
Thanks.

I put a static method in the class to print out when it is loaded. And the class exists in the classpath. It is never making it to the class.
Also, I do have both the JAVA_HOME and ORACLE_HOME environment variables set.
The ejb definitions are:
ejb-jar.xml
<session>
<ejb-name>ct.AggregatesManagerHome</ejb-name>
<home>com.syncra.ct.server.api.AggregatesManagerHome</home>
<remote>com.syncra.ct.server.api.AggregatesManager</remote>
<ejb-class>com.syncra.ct.server.AggregatesManagerBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
</session>
orion-ejb-jar.xml
<session-deployment name="ct.AggregatesManagerHome" location="ct.AggregatesManagerHome"/>
Because JDeveloper forces me to split the code into Model and ViewController I am wondering if there is something special that needs to be done for OC4J to see everything. Any ideas?
Nick

Calling EJB from other EJB on other J2EE Server

Can I call EJB from other EJB on other J2EE Server
Servers - Websphere 5.0
Do i require home & remote interface of that ejb on client side also
Help me, please

the problem is actually i require that is specific to websphere
for example i want to call a method ion that ejb
say my ejb name is myejb
so the normal way i should call is
InitialContext initialContext = new InitialContext();
Object homeObject = initialContext.lookup("ejb/MyEjbHome");
MyEJBHome myEJBHome =(MYEjbHome )javax.rmi.PortableRemoteObject.narrow(homeObjectMYEjbHome.class);
myEJB = lSHome.create();
myEJB.someMethod();
but here i am having class for home and remote available
now if other app server i am not having this classes then what to do

MBean calling ejb class loading issue

Hi,
I would like to have an mbean call an ejb. I have come against a (predictable!!)
class loading problem. The EJB Home cant be bundled with the mbean because the
mbean class loader would load the interface, preventing ejb reload( Thats what
the error msg indicates) and the ejb doesnt get deployed.
I have moved to an mlet based scheme (beacuse an mlet is a class loader) to
load the mbeans, but now I have the problem that when the mbean looks up the
home in jndi the cast fails ie the jndi object has an interface class loaded by
the ejb class loader but the mlet has its own loaded home interface. These class
loaders appear to be sibblings - but I havnt printed out the trees.
This is WLS 702 which seems to be JMX 1.1. Has anyone got a way around this?
Have I invented a problem that doesnt exist? I cant go to WLS8.
My current way forward is to have the mbean find the class loader that loaded
the interface class (jndi object) and then have the mbean use that class loader
to load its copy of the interface class. Seems a bit complex. Im sure I missed
something obvious.
Thanks
Pete Marshall

Pete,
could you explain better your thoughts...
I'm interested to hear them.
regards,
Pedro Salazar.
Pete Marshall wrote:
Must think before typing..
If I have the ejb register a listener on the mbean and have the mbean emit an
event the detyped notification from the mbean will break the link between the
mbean class loader and the ejb loader. I think ;-) Ill try it.
Pete
"Pete Marshall" <[email protected]> wrote:
Hi,
I would like to have an mbean call an ejb. I have come against a (predictable!!)
class loading problem. The EJB Home cant be bundled with the mbean because
the
mbean class loader would load the interface, preventing ejb reload( Thats
what
the error msg indicates) and the ejb doesnt get deployed.
I have moved to an mlet based scheme (beacuse an mlet is a class loader)
to
load the mbeans, but now I have the problem that when the mbean looks
up the
home in jndi the cast fails ie the jndi object has an interface class
loaded by
the ejb class loader but the mlet has its own loaded home interface.
These class
loaders appear to be sibblings - but I havnt printed out the trees.
This is WLS 702 which seems to be JMX 1.1. Has anyone got a way around
this?
Have I invented a problem that doesnt exist? I cant go to WLS8.
My current way forward is to have the mbean find the class loader that
loaded
the interface class (jndi object) and then have the mbean use that class
loader
to load its copy of the interface class. Seems a bit complex. Im sure
I missed
something obvious.
Thanks
Pete Marshall

JDeveloper EJB Class Editor lock

I created an EJB using JDev and used the EJB class editor to build the fields/methods in the bean.
After working on the EJB for quite a while I reopened the EJB Class editor and found a blue error at the bottom of the window stating :
Editor locked : file is read only.
I have tried almost everything to unlock the editor but I have had no success.None of the files in project is read-only.
If you have experinced this problem please respond!
Regards
LeRoux

Hi,
Go to se38.
In the menubar..
Goto-->attributes.
In that u can see on the bottom of the popup, a check box with editor lock.
U check that box.
Then the program cannot be edited by any other user other than the one who has created.
In this case the username has to be unique.
If one user is used by many number of people, then all the people who are using that user can edit the program.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

Where is this class: oracle.jbo.server.EntityImpl

Does anyone know what jar file contains the following classes:
oracle.jbo.server.EntityImpl
oracle.jbo.server.AttributeDefImpl
Thanks!
-Teri Kemple
[email protected]

It's bc4jmt.jar in BC4J\lib. "mt" probably stands for "middle tier".

Is it possible to monitor all calls into all EJBs deployed on a server?

Is there any way of monitoring all calls into the EJBs deployed in a server?
I'd like to be able to externally log the calls, and perhaps do some monitoring at the call level, without modifying the EJBs themselves. Something along the lines of servlet filters for servlets, but for EJBs instead..
JBoss has a nice plugin interface, and one could either extend the Logging plugin, or write another one, that can do this.
But is there an analog in other J2EE servers (e.g. weblogic and websphere)? Or is that a standard or clever way of intercepting all calls? (I suppose one could use Ethereal, but I was hoping for a higher-level solution).
Duke dollars available!

Hi,
In JBoss they use Log4J to log and intercept the Bean calls and JDBC calls. You can use Log4J to do the same with other servers also, cause I configured OC4J(Oracle 9iAS) Server to use log4J and it worked for me. I think other servers can also be configured to use log4j. I've only tried this with JBoss and OC4J. I don't have much experience with other servers.
So, my advise is : try LOG4J and try to configure server to use LOG4J
Hope this works!
Indy.

Create EJB Control For Remote Server

I'm having trouble creating an EJB control for a EJB residing in a remote server.
First, I've a JAR containing the remote/home interfaces and added it as a Library in the WLW 8.1 application.
When creating a new EJB Control, there's no way to successfully create the control.
At the STEP 2 GUI:
I am able to specify a JNDI-NAME, but the home/bean interface fields are empty. If I click on "Browse application EJBs..." button, nothing is available. If I click on "Browse server EJBs", it only shows EJBs in the current server.
Thanks

Hi
I believe you are on Workshop8.1 Spx.
This is a known issue. The reason the ejb does not show up as an application ejb because we have just the interfaces as a library and not the whole EJB.
Since the EJB's are not deployed on the server it will not show up either.
Unfortunately there is no way to point to a remote domain and get all the ejb's deployed there.
Workaround:
You can deploy the ejb locally, create the ejbcontrol and then undeploy the EJB. You need to manually change the home jndiname to use the remote server url.
Thanks
Vimala

Re: MBean calling ejb class loading issue

Must think before typing..
If I have the ejb register a listener on the mbean and have the mbean emit an
event the detyped notification from the mbean will break the link between the
mbean class loader and the ejb loader. I think ;-) Ill try it.
Pete
"Pete Marshall" <[email protected]> wrote:
>
Hi,
I would like to have an mbean call an ejb. I have come against a (predictable!!)
class loading problem. The EJB Home cant be bundled with the mbean because
the
mbean class loader would load the interface, preventing ejb reload( Thats
what
the error msg indicates) and the ejb doesnt get deployed.
I have moved to an mlet based scheme (beacuse an mlet is a class loader)
to
load the mbeans, but now I have the problem that when the mbean looks
up the
home in jndi the cast fails ie the jndi object has an interface class
loaded by
the ejb class loader but the mlet has its own loaded home interface.
These class
loaders appear to be sibblings - but I havnt printed out the trees.
This is WLS 702 which seems to be JMX 1.1. Has anyone got a way around
this?
Have I invented a problem that doesnt exist? I cant go to WLS8.
My current way forward is to have the mbean find the class loader that
loaded
the interface class (jndi object) and then have the mbean use that class
loader
to load its copy of the interface class. Seems a bit complex. Im sure
I missed
something obvious.
Thanks
Pete Marshall

Pete,
could you explain better your thoughts...
I'm interested to hear them.
regards,
Pedro Salazar.
Pete Marshall wrote:
Must think before typing..
If I have the ejb register a listener on the mbean and have the mbean emit an
event the detyped notification from the mbean will break the link between the
mbean class loader and the ejb loader. I think ;-) Ill try it.
Pete
"Pete Marshall" <[email protected]> wrote:
Hi,
I would like to have an mbean call an ejb. I have come against a (predictable!!)
class loading problem. The EJB Home cant be bundled with the mbean because
the
mbean class loader would load the interface, preventing ejb reload( Thats
what
the error msg indicates) and the ejb doesnt get deployed.
I have moved to an mlet based scheme (beacuse an mlet is a class loader)
to
load the mbeans, but now I have the problem that when the mbean looks
up the
home in jndi the cast fails ie the jndi object has an interface class
loaded by
the ejb class loader but the mlet has its own loaded home interface.
These class
loaders appear to be sibblings - but I havnt printed out the trees.
This is WLS 702 which seems to be JMX 1.1. Has anyone got a way around
this?
Have I invented a problem that doesnt exist? I cant go to WLS8.
My current way forward is to have the mbean find the class loader that
loaded
the interface class (jndi object) and then have the mbean use that class
loader
to load its copy of the interface class. Seems a bit complex. Im sure
I missed
something obvious.
Thanks
Pete Marshall

Deployement of ejb class in xi server

Similar Messages

Maybe you are looking for