| Importing EJB jars into EAR Project [message #68778] |
Wed, 26 January 2005 22:59 |
Eclipse User |
|
|
|
Originally posted by: foobar1970.yahoo.com
I'm using WTP M2 with Eclipse 3.1M4. I've created a few simple EJB and
WebApp projects and associated them with ent app projects with no
problems. Now what I'd like to do is create an ent app Project and
import some existing EJB jars (without source). I don't want to do any
development on the EJB jars themselves, I just want them included in the
enterprise app and available for use from other components in the
enterprise app.
However, when I do import an EJB jar into the enterprise app project, it
creates an EJB project for me. I do have control over what it's named,
where it lives on the filesystem, etc, but it still makes me create the
project. It sticks all the classes in the EJB jar under
"imported_classes" and then appears to be doing some kind of validation
on them. I can drill down in the package structure and see various
classes with red X's on them. However, I can find no way to see what the
problems are - nothing is listed under Problems or Console. These are
EJB's that are known to build and run fine outside of eclipse, so I'm
guessing that maybe that EJB depends on some classes that aren't in the
EJB jar and aren't anywhere else in the enterprise app? I don't know,
that's just a guess.
So here are my questions:
1) Is there any way to avoid creating an EJB project for each binary EJB
jar that I import?
2) If I do need the project for binary-only EJB's, where do I so
messages about problems?
Thanks,
Dave
|
|
|
Powered by
FUDForum. Page generated in 0.03175 seconds
] 
Search
Help
Register
Login
Home
