Hi Brett,
I believe the client (happens to be a servlet) should only see the
remote and home interfaces.
The ejb container (on a different VM) will host my enterprise bean
and the util classes
it needs to get its work done - as well as about 2 dozen dependency
classes that get pulled in.
Just to be clear those 2 dozen+ classes are now visible to my war
artifact project. Possibly
it will do no harm as I don't think that the ear plugin will pick
them up when constructing
the j2ee app - but it would be nice not to have them in the project
to accidentally compile
against.
AW
On 26 Oct 2005, at 07:23, Brett Porter wrote:
Is that not the correct behaviour?
The ejb doesn't include the jars itself, does it?
- Brett
On 10/25/05, Ashley Williams <[EMAIL PROTECTED]> wrote:
Thanks that works. However I still get all the dependency artifacts
referenced in the ejb
pom file - is there some way to 'switch off' transitive dependencies?
On 26 Oct 2005, at 03:20, Tomislav Stojcevich wrote:
You need to specify the type as ejb-client in your client project's
pom.
<dependency>
<groupId>com.abc</groupId>
<artifactId>Ejb</artifactId>
<version>1.00</version>
<type>ejb-client</type>
</dependency>
On 10/25/05, Ashley Williams <[EMAIL PROTECTED]> wrote:
Hi,
Just wondering how I go about including an ejb client jar in my
project. It seems the main artifact of an ejb project is the ejb
jar
file, which is fair enough. However it can also generate a client
jar, installed in the same directory in the local repository and I
can't work out how to include this poor cousin in my webapp
project.
I definitely don't want the full on ejb jar file as it will try to
pull in quite a few dependencies. Not to mention I don't want the
enterprise beans in my client app.
Has anyone else come across this problem? (and solved it ;)
Thanks
- AW
-------------------------------------------------------------------
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
tom
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
