Ole Husgaard wrote:
>
> Hi,
>
> Isn't it your EJB home interface that
> cannot be found?
> This is in your EJB jar, and its
> classes are not served by the web
> server.
Are you sure? Why then we need the web-server for?
Only to download jnp-client and jboss-client?
> This is similar to when one EJB jar
> tries to access classes and defined
> in another EJB jar.
> Problem is, while it would make
> sense to serve the interface classes
> (but not implementation classes) of
> the EJB jar, there are no sure way
> to differentiate what classes are
> interface and which are
> implementation.
Actually there is. ejb-jar.xml lists
Home and Remote interfaces for each bean.
>
> I seperate my EJBs in different jars
> for implementation and interface.
> EJB implementation jars go to deploy
> directory, while interface jars go
> in classpath.
But it would kill the idea of the hot deployment.
You can only pray that you never have to change
the interfaces.
Regards,
--
__________________________________________________
Alexander Kogan PTC www.ptc.com
[EMAIL PROTECTED] 140 Kendrick St. Needham MA 02494
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
