Skip to Content
author's profile photo Former Member
Former Member

Importing Existing EJBs into NetWeaver Studio


We have an in house application currently deployed on Weblogic 6.1 . As we are moving to NetWeaver platform, we also wish to standardize on use of Netweaver studio for handling development work.

I tried to create a new Test EJB project, import the classes from my existing application into studio. All my classes, show up directly under my project and not under ejb modules.

Since all those classes are bean/home and remote interfaces for my application, I was hoping the studio will treat it like EJB implementations and with minor adjustments I would be able to reuse existing deployment descriptors for the same.

Is there a known procedure to import J2EE compliant EJBs and their deployment descriptors into Studio and then deploy them to WAS, hence achieving migration to WAS as deployment platform and standardising on Studio as developement platform at the same time.



Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Nov 26, 2003 at 12:03 PM

    Hi Mukesh,

    Importing of existing projects actually works quite well with the IDE. First of all you should check if the import does not have an import for your former development environment.

    If not, then you import it as a java project. Then you do the following:

    1. Create a Beans project.

    2. Go to the Navigator in your project pane.

    3. Copy or move the complete path of your projects EJB's to the Beans projects 'ejbModule' directory.

    4. Go back to the J2EE Project tab and check your ejb list. The ejb's should all be there.

    5. Make an Assembly project and tell the wizard to include your Beans project.

    6. overwrite the ejb.jar with the one of your original in the same way you copied the ejb sources.

    That should be basically it. You'll know you won once you see your beans represented as such in the j2ee project.

    IF this does not happen THEN you may have a problem with the fact that Beans and their interfaces are recognized via name convention. That is:

    Bean Class

    It tries more, but I'm not sure how this works in detail.

    And we're still trying to get better.



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.