facebook

Another one

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #199274 Reply

    Scott Esker
    Participant

    Ok. Any user help here.. Created testEJB in MyEclipse, generated and deployed, get the following problem during deployment.

    <Oct 16, 2003 3:38:00 PM CDT> <Error> <Deployer> <149201> <The Slave Deployer failed to complete the deployment
    h id 8 for the application testEJB.
    weblogic.management.ApplicationException: Prepare failed. Task Id = 8
    {
    Module Name: testEJB, Error: Exception preparing module: EJBModule(testEJB,status=NEW)

    Unable to deploy EJB: testEJB from testEJB:

    In EJB TestEJB, method ‘wait’ must not be declared as final.

    In EJB TestEJB, method ‘wait’ must not be declared as final.

    In EJB TestEJB, method ‘wait’ must not be declared as final.

    In EJB TestEJB, method ‘getClass’ must not be declared as final.

    In EJB TestEJB, method ‘notify’ must not be declared as final.

    In EJB TestEJB, method ‘notifyAll’ must not be declared as final.

    at weblogic.ejb20.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:264)
    at weblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:228)
    at weblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:901)
    at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:857)
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:185)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:344)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
    at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1062)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)

    #199276 Reply

    Scott Esker
    Participant

    It almost looks like the ejbc is generating some static or finals. Not sure.

    #199284 Reply

    Scott Esker
    Participant

    I re-installed everything, brough up Weblogic Portal Server 7.0 SP1,
    and created a new J2EE project. Created EJB and ran XDoclet. Then
    deployed, and recieved the following..

    What JDK version are you using to run Eclipse? (java -version)

    — 1.4.2_01-b06

    What JDK version are you using to launch your application server?

    — 1.3.1_1

    What steps did you take that resulted in the issue?

    — Clicked on finish after filling in ejb project wizard.

    What application server are you using?

    — weblogic 7.0 portal (platform)

    Scott

    #199285 Reply

    Scott Anderson
    Participant

    Scott,

    The message was truncated. Can you repost it please? Also, are there any entries in the Eclipse log file (<workspace>/.metadata/.log)?

    –Scott
    MyEclipse Support

    #199288 Reply

    Scott Esker
    Participant

    !SESSION Oct 17, 2003 09:53:50.922 ———————————————
    java.version=1.4.2_01
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
    Command-line arguments: -os win32 -ws win32 -arch x86 -install file:C:/dev/eclipse/
    !ENTRY com.genuitec.eclipse.j2eedt.core 1 1 Oct 17, 2003 09:53:50.922
    !MESSAGE J2EEProject#id == null
    !ENTRY com.genuitec.eclipse.j2eedt.core 1 1 Oct 17, 2003 09:53:50.922
    !MESSAGE J2EEProject#id == null
    !ENTRY com.genuitec.eclipse.j2eedt.core 1 1 Oct 17, 2003 09:53:50.932
    !MESSAGE J2EEProject#id == null
    !ENTRY com.genuitec.eclipse.j2eedt.core 1 1 Oct 17, 2003 09:53:50.932
    !MESSAGE J2EEProject#id == null

    #199289 Reply

    Scott Esker
    Participant

    Posted: Oct 07, 2003 – 04:34 AM

    ——————————————————————————–

    What operating system and version are you running?

    — Windows 2000 SP4

    What Eclipse version and build id are you using? (Help > About Eclipse Platform)

    — 2.1.1

    – Was Eclipse freshly installed for MyEclipse?

    — Yes

    – If not, was it upgraded to its current version using the update manager?
    – Are any other external plugins installed?

    — Just MyEclipse

    – How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*

    — 7

    What MyEclipse version are you using? (Help > About Eclipse Platform > Features)

    — 2.6.2

    What JDK version are you using to run Eclipse? (java -version)

    — 1.4.2_01-b06

    What JDK version are you using to launch your application server?

    — 1.3.1_1

    What steps did you take that resulted in the issue?

    — Started the portal, created EJB project. Created 1 ejb, added xdoclet
    requirements, run xdoclet. Added deployment information, deployed. Recieved the displayed exception.

    What application server are you using?

    — weblogic 7.0 portal (platform)

    #199305 Reply

    support-michael
    Keymaster
    J2EEProject#id == null 

    This is a suspicous state. Can you post the contents of your .mymetadata file?

    Michael
    MyEclipse Support

    #199306 Reply

    Scott Esker
    Participant

    Its not creating the stubs/skeletons for the ejb apparently. Did I miss something here?

    #199308 Reply

    support-michael
    Keymaster

    MyEclipse relies on WLS to dynamically generate stubs/skeletons. I’m not sure why you are running into this problem. Are you running WLS in standalone mode on your development machine? I’ll try replicating your situation but 1st I need to setup WLS (portal vers).

    One more thing to try.
    1) Stop WLS
    2) remove any remenant deployed apps from WLS <domain>/applications/
    3) deploy application from MyEclipse
    4) start WLS and observer log entries for similar deployment problems

    Last, I was requesting the .mymetadata contents because I’m curious as to why the project id == null in the error log. This may peripheral to the current problem but is an odd state.

    Michael

    #199309 Reply

    Scott Esker
    Participant

    I am redeploying everything…the same problem is still occuring. I may try a clean machine soon.

    #199391 Reply

    Scott Esker
    Participant

    The problem was that no remote object was being generated. I am trying to figure out now why, I looked at the XDoclet information, and it right out of the sample create EJB help.

    Scott

    #199393 Reply

    Scott Anderson
    Participant

    Scott,

    XDoclet is very particular about such things as default names, package mappings, and output directories. If you search the forums for XDoclet, you’ll find there are many threads on the topic that should help you quite a bit.

    –Scott
    MyEclipse Support

Viewing 12 posts - 1 through 12 (of 12 total)
Reply To: Another one

You must be logged in to post in the forum log in