NoSuchMethodException when deploying an EJB

I was using JBoss 2.2.4 with Tomcat 3.2.3 and was able to deploy the original CD example. But I couldn't deploy the example after I changed the persistence-type to "Bean" in ejb-jar.xml.
I had a method "ejbFindByPrimaryKey()" in the CDBean.java and a method "FindByPrimaryKey()" in the CDHome.java.
I also had "FindByPrimaryKey" under
<method-permission> in ejb-jar.xml.
What had I missed? Thanks
M.H

I had a similar problem. I got around it by recreating the .ear file. I know this is a long way but it solves the problem..
Deepak

Similar Messages

Is there a way not to have to chose an available server in the console when deploying an ejb?

Is there a way not to have to chose an available server in the console when deploying
an ejb? Everytime we deploy our beans we have to logon to the console select the
ejb and then chose a server under the tab targets? Can this be automated?

You could try to select the target in the config.xml file, but this is
not recommended by BEA.
Nils
Fred Bloggs wrote:
>
Is there a way not to have to chose an available server in the console when deploying
an ejb? Everytime we deploy our beans we have to logon to the console select the
ejb and then chose a server under the tab targets? Can this be automated?--
============================
[email protected]

Error when deploying an EJB

Hi,
I4m trying to deploy an enterprise java bean in the database
(JServer version 8.1.7.0.0). Apparently it goes on, but when it
try to load ejb and comm stubs jar file, shows an IOException.
Can someone help me to solve this problem?
If you need further information, I will be pleased to give it to
you.
Thanks in advance.
C:\java\pru>deployejb -user rafa -password rafa -service
sess_iiop://rabinf109:2481:sistema -descriptor ejb-jar.xml
-keep -temp .\temp sessionbean.jar
Reading Deployment Descriptor...done
Verifying Deployment Descriptor...done
Gathering users...done
Generating Comm Stubs.......................................done
Compiling Stubs...done
Generating Jar File...done
Loading EJB Jar file and Comm Stubs Jar file...Exception in
thread "main" org.
g.CORBA.COMM_FAILURE: java.io.IOException: Peer disconnected
socket minor cod
0 completed: No
at com.visigenic.vbroker.orb.TcpConnection.read
(TcpConnection.java:61)
at
com.visigenic.vbroker.orb.GiopConnectionImpl.receive_message
(GiopCo
ectionImpl.java:436)
at
com.visigenic.vbroker.orb.GiopConnectionImpl.receive_reply
(GiopConn
tionImpl.java:347)
at com.visigenic.vbroker.orb.GiopStubDelegate.invoke
(GiopStubDelegate.
va:562)
at com.visigenic.vbroker.orb.GiopStubDelegate.invoke
(GiopStubDelegate.
va:503)
at com.inprise.vbroker.CORBA.portable.ObjectImpl._invoke
(ObjectImpl.ja
:60)
at oracle.aurora.AuroraServices._st_JISLoadJava.create
(_st_JISLoadJava
ava:42)
at oracle.aurora.server.tools.sess_iiop.Loadjava.create
(Loadjava.java:
9)
at
oracle.aurora.server.tools.sess_iiop.Loadjar.loadAndCreate
(Loadjar.
va:98)
at oracle.aurora.server.tools.sess_iiop.Loadjar.invoke
(Loadjar.java:80
at oracle.aurora.server.tools.sess_iiop.Loadjava.<init>
(Loadjava.java:
at oracle.aurora.server.tools.sess_iiop.Loadjar.<init>
(Loadjar.java:52
at oracle.aurora.ejb.deployment.GenerateEjb.invoke
(GenerateEjb.java:56
at oracle.aurora.server.tools.sess_iiop.ToolImpl.invoke
(ToolImpl.java:
3)
at oracle.aurora.ejb.deployment.GenerateEjb.main
(GenerateEjb.java:575)

Check whether ur handling any Exception thrown by the Remote Interface,
This is the only reason for this exception while deploying.

Changing user & table name when deploying CMP from jdev902

Hi
How can I choose different user and table name when deploying CMP EJB other then Oracle/CMP name from Jdev902 to OC4J 902. I have tried edinting orion-ejb-jar.xml's entity-deployment tag with limited succes ie: it works fine when I deploy to the inbedded OC4J but when I try deploying to standalone OC4J I get table created in Oracle user and a table with the same name as the CMP.
I have also tried deploying the connections.xml along with the java classes, that didn't work either.
All help is appreciated - Thanks

You can do a Restore for the iPod with your computer again, but bear in mind that it will erase all data on the iPod and replace with the library of music files on your iTunes.
How to do a Restore? that is simple, download iTunes 7.01 and install it your computer, open it and plug your iPod with it, then click Restore.
http://www.apple.com/itunes/download/
to restore your iPod to factory settings.
http://docs.info.apple.com/article.html?artnum=60983

Ejb-ref error when deploying a previously working ear on weblogic 8.1

when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

NPE occurs when deploying suitecase dependent on WSIF / EJB

I am getting a NullPointerException when deploying a BPEL process that depends on an EJB accessed via a WSIF definition. Both the ejb and the suitcase are deployed onto the same oc4j instance, and i have tested the ejb from a standalone client to ensure that it is operational, but i get the exception noted below. I can only assume that there may be something wrong with the WSIF definition, but I have checked it numerous times to make sure that it accurately reflects the ejb definition. Can you give me some hints as to some things to check that could possibly cause this error? From the stack trace, it seems that it is ejb related, but i guess i could be wrong:
<2006-04-11 11:20:28,088> <ERROR> <default.collaxa.cube.engine.deployment> <Cube
ProcessFactory::generateProcessClass>
Process "XYZ" (revision "1.01.000.0000") compilation failed.
<2006-04-11 11:20:28,182> <ERROR> <default.collaxa.cube.engine.deployment> <Cube
ProcessLoader::create>
<2006-04-11 11:20:28,182> <ERROR> <default.collaxa.cube.engine.deployment> Proce
ss "XYZ" (revision "1.01.000.0000") load FAILED!!
com.evermind.server.rmi.OrionRemoteException: java.lang.NullPointerException
at com.evermind.server.ejb.EJBUtils.getUserException(EJBUtils.java:296)
at IBPELDomainManagerBean_StatelessSessionBeanWrapper34.loadProcessArchi
ve(IBPELDomainManagerBean_StatelessSessionBeanWrapper34.java:2174)
at com.collaxa.cube.engine.deployment.CubeProcessMonitorWork.run(CubePro
cessMonitorWork.java:130)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Nested exception is:
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:398)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.addStatus(CubePr
ocessHolder.java:275)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcess
Holder.java:1240)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(Cube
ProcessHolder.java:882)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadArchive(Cube
ProcessHolder.java:824)
at com.collaxa.cube.engine.CubeEngine.loadProcessArchive(CubeEngine.java
:939)
at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.loadProcessArchive(BP
ELDomainManagerBean.java:390)
at IBPELDomainManagerBean_StatelessSessionBeanWrapper34.loadProcessArchi
ve(IBPELDomainManagerBean_StatelessSessionBeanWrapper34.java:2157)
at com.collaxa.cube.engine.deployment.CubeProcessMonitorWork.run(CubePro
cessMonitorWork.java:130)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
<2006-04-11 11:20:28,182> <ERROR> <default.collaxa.cube.engine.deployment> <Cube
ProcessMonitorWork::run> Error while loading process archive C:\OraBpelPM\integr
ation\orabpel\domains\default\deploy\bpel_XYZ_1.01.000.0000.jar
com.evermind.server.rmi.OrionRemoteException: java.lang.NullPointerException
at com.evermind.server.ejb.EJBUtils.getUserException(EJBUtils.java:296)
at IBPELDomainManagerBean_StatelessSessionBeanWrapper34.loadProcessArchi
ve(IBPELDomainManagerBean_StatelessSessionBeanWrapper34.java:2174)
at com.collaxa.cube.engine.deployment.CubeProcessMonitorWork.run(CubePro
cessMonitorWork.java:130)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Nested exception is:
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:398)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.addStatus(CubePr
ocessHolder.java:275)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcess
Holder.java:1240)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(Cube
ProcessHolder.java:882)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadArchive(Cube
ProcessHolder.java:824)
at com.collaxa.cube.engine.CubeEngine.loadProcessArchive(CubeEngine.java
:939)
at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.loadProcessArchive(BP
ELDomainManagerBean.java:390)
at IBPELDomainManagerBean_StatelessSessionBeanWrapper34.loadProcessArchi
ve(IBPELDomainManagerBean_StatelessSessionBeanWrapper34.java:2157)
at com.collaxa.cube.engine.deployment.CubeProcessMonitorWork.run(CubePro
cessMonitorWork.java:130)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)

Note, that this has nothing to do with WSIF.. and is a cmpilation error ...
my best guess is the revision number..
Process "XYZ" (revision "1.01.000.0000") load FAILED!! can you change that to reflect a norma double or in (1, 1.1, 2.0...)
thx clemens

Error when deploying ejb 3 in weblogic10

Hi,
I'm using the EJB3.0 in weblogic10, just as the following:
remote interface:
com.test.intf
public interface Test{
public void test();
and the impl:
com.test.impl
@stateless
@Remote(Test.class)
public class TestBean implements Test{
public void test{...}
Then I build an ear which including the ejb jar:
Test.ear
|__ejb.jar (including the Test and the TestBean)
|
|__Meta-Inf
And when I deploy the Test.jar to the weblogic 10, the following error occurs:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Unable to load clas
s com.test.impl.TestBean_3u7muo_EmergencyServiceF
uncImpl ]
at weblogic.ejb.container.deployer.Ejb3SessionBeanInfoImpl.prepare(Ejb3S
essionBeanInfoImpl.java:319)
at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeploye
r.java:914)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:
1188)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:425)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
va:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
ava:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.jav
a:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(Deployme
ntStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(App
ContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.cr
eateAndPrepareContainer(ActivateOperation.java:197)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Prepare(ActivateOperation.java:89)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.pr
epare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entPrepare(DeploymentManager.java:723)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploy
mentList(DeploymentManager.java:1190)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare
(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.pre
pare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.ClassNotFoundException: com.oracle.ocrt.service.impl.Emerge
ncyServiceFuncBean_3u7muo_TestIntf
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic
ClassLoader.java:283)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass
Loader.java:256)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass
Loader.java:176)
at weblogic.ejb.container.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.j
ava:540)
at weblogic.ejb.container.deployer.Ejb3SessionBeanInfoImpl.prepare(Ejb3S
essionBeanInfoImpl.java:310)
... 27 more
<2008-9-26 下午08时35分07秒 CST> <Error> <Deployer> <BEA-149265> <Failure occurr
ed in the execution of deployment request with ID '1222432506169' for task '0'.
Error is: 'weblogic.application.ModuleException: Exception preparing module: EJB
Module(test.jar)
Unable to deploy EJB: TestBean from test.jar:
***** ASSERTION FAILED *****[ Unable to load class com.test.impl.TestBean_3u7muo_TestImpl ]
weblogic.application.ModuleException: Exception preparing module: EJBModule(test.jar)
Unable to deploy EJB: TestBean from test.jar:
***** ASSERTION FAILED *****[ Unable to load class com.test.impl.TestBean_3u7muo_TestImpl ]
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
What is the problem? And What can I do?
BTW, if I change the @Remote to @Local, I can deploy the ejb successfully.
In addition, Who knows how to access the ejb3.0 from a standalone client just like access the EJB2.0:
properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
properties.put(Context.PROVIDER_URL, "t3://localhost:7001");
Context cont = new InitialContext(properties);
Obj ref = cont.lookup("???"); //--------------------> What should I write here???
Thanks!

Hi,
It's not easy to tell what's wrong with your example.
Maybe you could send me a zip and I'll check when I have some time.
By the way, you're asking a question about the lookup of an EJB3, I wrote an article that covers that topic.
It should give you some interesting input.
http://m-button.blogspot.com/2008/07/reminder-on-how-to-use-ejb3-with.html
Regards.

WebLogic 12.1.2 fails when deploying ear with injecting extension and bean with injection of this extension in ejb

WebLogic 12.1.2 fails when deploying an enterprise application(ear) that contains a ejb in which injected 1) an extension 2)bean with injection of this extension.
The following exception is thrown:
Caused By: org.jboss.weld.exceptions.DeploymentException: WELD-001409 Ambiguous dependencies for type [CdiExtension] with qualifiers [@Default] at injection point [[field] @Inject private test.extension.Bean1.extension].
Possible dependencies [
[Extension [class test.extension.CdiExtension] with qualifiers [@Default]; zip:/domain1/servers/AdminServer/tmp/_WL_user/test/7x6roh/lib/test-extension-0.0.1-SNAPSHOT.jar!/META-INF/services/javax.enterprise.inject.spi.Extension@1[test.extension.CdiExtension@1115deb],
Extension [class test.extension.CdiExtension] with qualifiers [@Default]; zip:/domain1/servers/AdminServer/tmp/_WL_user/test/7x6roh/lib/test-extension-0.0.1-SNAPSHOT.jar!/META-INF/services/javax.enterprise.inject.spi.Extension@1[test.extension.CdiExtension@ed791f]]]
    at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:314)
    at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:280)
    at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:143)
    at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:163)
    at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:382)
    at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:367)
    at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:379)
    at com.oracle.injection.provider.weld.WeldInjectionContainer.start(WeldInjectionContainer.java:106)
    at com.oracle.injection.integration.CDIAppDeploymentExtension.initCdi(CDIAppDeploymentExtension.java:70)
    at com.oracle.injection.integration.CDIAppDeploymentExtension.activate(CDIAppDeploymentExtension.java:47)
    at weblogic.application.internal.flow.AppDeploymentExtensionFlow.activate(AppDeploymentExtensionFlow.java:37)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:61)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
Problem can be easily reproduced by a minimal case:
test.ear:
\lib\test-extension-0.0.1-SNAPSHOT.jar
test-ejb-0.0.1-SNAPSHOT.jar
where
test-extension-0.0.1-SNAPSHOT.jar contains:
CdiExtension.java:
package test.extension;
import javax.enterprise.inject.spi.Extension;
public class CdiExtension implements Extension {
    private String someString = "Some String";
    public String getSomeString() {
        return someString;
Bean1.java:
package test.extension;
import javax.enterprise.context.ApplicationScoped;
import javax.inject.Inject;
@ApplicationScoped
public class Bean1 {
    @Inject
    private CdiExtension extension;
    public String get() {
        return extension.getSomeString();
test-ejb-0.0.1-SNAPSHOT.jar contains:
EjbBean.java:
package test;
import test.extension.Bean1;
import test.extension.CdiExtension;
import javax.ejb.Stateless;
import javax.inject.Inject;
@Stateless
public class EjbBean {
    @Inject
    private CdiExtension extension;
    @Inject
    private Bean1 bean1;
    public String getSomeString() {
        return extension.getSomeString() + "\n" + bean1.get();
p.s. i seen same problem in community.oracle.com/thread/2577403 , but it happen in "war", not "ear", and seems successfully patched with patch №17424706

Hi,
It looks like there is patch exists for this issue.
Patch 17198187
Please try to download from the MOS or try to open a ticket with support.
Regards,
Kal

Ejb-ref errore when deploying a previously working ear on weblogic 8.1

when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
Thanks in advance!
Greets,
Luca
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

The issue is that WLS 6.1 didn't really support ejb-links properly. An
ejb-link should allow you to link a webapp or an ejb to another EJB
without requiring additional information or a global JNDI name on the
target EJB.
WLS 8.1 is following your ejb-link and telling you there's not enough
information.
You have 2 options:
1) Remove the <ejb-link>...</ejb-link> from your web.xml. You'll be
using just an ejb-reference at that point, but you've already included
the necessary information in the weblogic.xml that we can locate the EJB
via its global jndi-name
or
2) Change the ejb-link to be
<ejb-link>CustomMessaginBrick.jar#CustomMessagingBrick</ejb-link>
If you wanted to, you could then remove the reference info from the
weblogic.xml
-- Rob
luca wrote:
when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
Thanks in advance!
Greets,
Luca
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

Invalid change to class error when deploying EJB

We have EJBs that were built by Webgain Visual Cafe and successfully deploy
to WLS 5.1. We then use the WLE EJB Deployer Tool to build WLE container
classes and deploy the same EJBs in WLE 5.1.
One EJB does not deploy in WLE. The ULOG error message is:
133929.EA-LAWSTUC!JavaServer.517: main: IJENGINE_CAT:150: ERROR: Invalid
change to class service.Request
133929.EA-LAWSTUC!JavaServer.517: main: EJB_CAT:29: ERROR: While deploying
jar ServiceEJB : com.beasys.weblogic.classloader.RedeploymentException:
ERROR: Invalid change to class service.Request
133929.EA-LAWSTUC!JavaServer.517: Finalizer: IJENGINE_CAT:152: INFO: Closing
jar C:\aj\ServiceEJB_WLE.jar
Does anyone know what can cause an "invalid change to class" error when
deploying to WLE 5.1? Especially since the EJB deploys successfully in
WLS.
Carl Lawstuen

Reason: database keeps a reference of the class in JAVA$CLASS$MD5$TABLE table. This table keeps a refrence to all java classes loaded in database, and is present in each schema you deploy classes. That's the reason why if you change the application module name, you can load this classes. It instead keeps a reference if you use DROP JAVA CLASS command to drop a java class from de database. Use DROP JAVA command to clear the reference of the dropped classes when dropping it.
You can see this table as a class dictionary of the database, and you don't have to handle this records manually.

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>

Problems when deploying EJB

Hi,
I try to deploy an ejb in oracle 8.1.7.
All the steps of the deployment work fine until the step :
"Generating EJBHome and EJBObject on the server..."
At this step, it returns the following error messages :
Compilation errors in oracle/aurora/ejb/gen/test_editionpdf_editionPDFBean/EjbObject_EditionPDF:ORA-29535: source requires recompila
tion
javax/ejb/EJBObjectOperations: Authorization error for referenced class org/xml/sax/XMLReader.
javax/ejb/EJBObjectOperations: Authorization error for referenced class org/xml/sax/XMLReader.
javax/ejb/EJBObjectOperations: Authorization error for referenced class org/apache/xalan/xslt/XSLTInputSource.
javax/ejb/EJBObjectOperations: Authorization error for referenced class org/apache/xalan/xslt/XSLTInputSource.
oracle/aurora/ejb/gen/test_editionpdf_editionPDFBean/EjbObject_EditionPDF:112: Class org.xml.sax.XMLReader not found.
oracle/aurora/ejb/gen/test_editionpdf_editionPDFBean/EjbObject_EditionPDF:122: Class org.xml.sax.XMLReader not found.
oracle/aurora/ejb/gen/test_editionpdf_editionPDFBean/EjbObject_EditionPDF:161: Variable __returnValue may not have been initialized.
oracle/aurora/ejb/gen/test_editionpdf_editionPDFBean/EjbObject_EditionPDF:218: Class org.apache.xalan.xslt.XSLTInputSource not found
oracle/aurora/ejb/gen/test_editionpdf_editionPDFBean/EjbObject_EditionPDF:226: Class org.apache.xalan.xslt.XSLTInputSource not found
oracle/aurora/ejb/gen/test_editionpdf_editionPDFBean/EjbObject_EditionPDF:265: Variable __returnValue may not have been initialized.
oracle/aurora/ejb/gen/test_editionpdf_editionPDFBean/EjbObject_EditionPDF:270: Class org.apache.xalan.xslt.XSLTInputSource not found
oracle/aurora/ejb/gen/test_editionpdf_editionPDFBean/EjbObject_EditionPDF:278: Class org.apache.xalan.xslt.XSLTInputSource not found
oracle/aurora/ejb/gen/test_editionpdf_editionPDFBean/EjbObject_EditionPDF:317: Variable __returnValue may not have been initialized.
Info: 13 errors
Even if the concerned java classes 'org/xml/sax/XMLReader' and 'org/apache/xalan/xslt/XSLTInputSource' are stored in the database and have the 'valid' status.
Do I need to specify some security rules with the dbms_java package ?
Where could this problem come from ?
Thanks in advance
Bye
[email protected]

Hi,
Y have the same problem with Jdeveloper.
May be it`s will help You
1. IDE compilation process can`t check some problem whith EJB, but this errrors checking on deployment process. Check Your remote interface independently.
2. If you use Oracle8i - connect to the server with admin options(login and password) or give for you user this privilege. Try make connect with name: SYS and password: change_on_install.
Sorry for bad English
null

Error when deploying a simple Entity bean (EJB3) on Glassfich or Sun AS

Hi,
After some problems when deploying complex EJB3 Entity bean on GlassFich with a MySQL connector, I have made a simple entity.
(test with Glassfish and Sun AS with same result)
With netbean 5.5 => New EJB Module
File->New->Persistence Unit (and use default values)
Persistence.xml
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence">
<persistence-unit name="test" transaction-type="JTA">
   <provider>oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider</provider>
    <jta-data-source>jdbc/sample</jta-data-source>
    <properties>
      <property name="toplink.ddl-generation" value="create-tables"/>
    </properties>
</persistence-unit>
</persistence>File->New->Entity Class
EntityTest.java
package test;
import java.io.Serializable;
import javax.persistence.Entity;
import javax.persistence.GeneratedValue;
import javax.persistence.GenerationType;
import javax.persistence.Id;
@Entity
public class EntityTest implements Serializable
    @Id
    @GeneratedValue(strategy = GenerationType.AUTO)
    private Long id;
    /** Creates a new instance of EntityTest */
    public EntityTest()
    public Long getId()
        return id;
    public void setId(Long id)
        this.id = id;
    public String toString()
        //TODO change toString() implementation to return a better display name
        return "" + this.id;
}Build of project work fine but when I try to deploy (with the 2 servers), I have the error :
Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Deployment Error -- null
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:790)
at java.util.HashMap$KeyIterator.next(HashMap.java:823)
at com.sun.enterprise.deployment.backend.EjbModuleDeployer.generatePolicy(EjbModuleDeployer.java:203)
at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:171)
at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:169)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:266)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:739)
at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:174)
at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:210)

Yes, the problem is that the ejb-jar must contain at least one ejb component. It's a common misconception that Java Persistence API Entity classes are ejb components but they are NOT. The Java Persistence API was developed within the EJB 3.0 JSR and works very well with EJB but the entity classes themselves are not full-fledged ejb components.
--ken

Error when deploying ear file

Hello
What could be the problem that I get this error when deploying my ear file with a web service within.
[#|2008-03-29T17:43:02.640+0100|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.tools.deployment|_ThreadID=12;_ThreadName=Thread-26;_RequestID=0a164c90-57bc-4d4a-8b3f-270fc4584891;|Exception occured in J2EEC Phase
com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- C:\Sun\AppServer\domains\domain1\generated\xml\j2ee-apps\agency_app\agency_jar\META-INF\wsdl\AgencyModuleWebServiceService.wsdl (The system cannot find the file specified)
     at java.io.FileInputStream.open(Native Method)
     at java.io.FileInputStream.<init>(FileInputStream.java:106)
     at java.io.FileInputStream.<init>(FileInputStream.java:66)
     at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
     at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:161)
     at java.net.URL.openStream(URL.java:1007)
     at com.sun.enterprise.webservice.WsUtil.generateFinalWsdl(WsUtil.java:699)
     at com.sun.enterprise.webservice.WsUtil.generateFinalWsdl(WsUtil.java:643)
     at com.sun.enterprise.deployment.backend.WebServiceDeployer.doWebServiceDeployment(WebServiceDeployer.java:165)
     at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:855)
     at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:580)
     at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:339)
     at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:222)
     at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:359)
     at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:214)
     at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:129)
     at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:169)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:266)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:739)
     at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:174)
     at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:210)
|#]when I deployed this application on a custom domain setup, it does not fail. But it fails on default domain.
Regards
Michael

How did you create your datasource, can you post the content, without passwords of course.
Greetings.

NoClassDefFoundError during deployment & accessing EJBs in ear

Platform - Redhat Linux 7.2 weblogic6.0 ant 1.3 for compilation and creation of ear.
I get a NoClassDefFoundError when I try to access some of the EJBs in my deployed
ear file.
Previously, I faced a NoClassDefFoundError problem in deployment and I put the jar
containing
the classes that it was asking for, in the classpath in startWeblogic.sh.
The ear got deployed after that.
Error I am getting now...
2002-04-29 18-05-18 - bang - <INFO> - Type :Operation Groups
2002-04-29 18-05-18 - bang - <INFO> - SELECT member FROM s_access_group WHERE site
= ? AND facility
= ? AND type = ? AND name in('null')
2002-04-29 18-05-18 - bang - <DEBUG> - DB Connection closed
2002-04-29 18-05-18 - bang - <DEBUG> - DB Connection closed
2002-04-29 18-05-18 - bang - <ERROR> - Controller: createSessionForTheUser: Caught
Remote exception
while creating SessionMgrEJB
java.rmi.RemoteException: EJB Exception:; nested exception is:
java.lang.NoClassDefFoundError: com/seagate/edcs/server/system/sysmgr/GroupDetails
java.lang.NoClassDefFoundError: com/seagate/edcs/server/system/sysmgr/GroupDetails
at com.seagate.edcs.util.system.SecurityUtils.getMembersOfGroups(SecurityUtils.java:205)
at com.seagate.edcs.util.system.SecurityUtils.getGuestPrivileges(SecurityUtils.java:376)
at com.seagate.edcs.server.system.sessionmgr.SessionMgrEJB.ejbCreate(SessionMgrEJB.java:127)
I have done the same compilation and creation of ear and deployment in a Solaris
server, using the
same source code and build.xml ( ant build file) and ant properties file; never saw
any errors like this.
I unjared the ear lying in the solaris machine that I was using previously and the
ear that
I created now in the linux server, and saw a difference in the manifest files...
the manifest files remains same as what I decribe with the EJB source in the previous
(solaris)
case...
Manifest-Version: 1.0
Created-By: 1.3.0 (Sun Microsystems Inc.)
Class-Path: edcs2000_utility.jar edcsreportmgr.jar wipgrpmgr.jar resourcegrpmgr.jar
systemgrpmgr.jar
notificationmgr.jar role.jar user.jar
The manifest file in the ear created now in the linux machine is something like this;
different
from what I describe together with the EJB.
Manifest-Version: 1.0
Name: com/seagate/edcs/server/system/role/RoleEJBHomeImpl_WLStub.class
Name: com/seagate/edcs/server/system/role/ACLDetails.class
Name: WLGENERATED
Name: com/seagate/edcs/server/system/role/RolePK.class
Name: com/seagate/edcs/server/system/role/RoleEJBHomeImplAD.ser
Name: com/seagate/edcs/server/system/role/RoleEJBEOImpl_WLStub.class
Name: com/seagate/edcs/server/system/role/RoleEJBEOImpl.class
Name: META-INF/ejb-jar.xml
what might be the issue here ? Please do have a look and help!
Thanks in advance
Prabin.

Hi Kevin,
Use remote EJB method calls. For details, look for "Parent application" topic in this forum or Servlet development guide in Oracle Documentation Library. I know, it does not seem to be the right source when looking for EJB documentation, however, it is.
Daniel.

NoSuchMethodException when deploying an EJB

Similar Messages

Maybe you are looking for