Hi Emmanuel,
Thanks for your response.
I am not actually having any problem with the Jar process, just with the
unjarred setup.
For example, in my situation I am wishing to be able to test the EJBs in an
unjarred environment. So that I can just compile the EJB, run the Weblogic
Deployment Wizard on the Deployment Descriptor and then I can start using the
EJB without jarring it.
If there is some problem/difference with running an unjarred EJB could somebody
let me know please.
Regards
Andrew Evans
Adaptive Technology
Emmanuel Pirsch wrote:
> Andrew Evans wrote:
>
> > I can run their original client without any problems, but when I run
> > my servlet I get a ClassCastException.
> >
> > At point {*1} I am unsure whether this line is correct or not, it does
> > not specify a binding of the ...HomeImpl class to anything, is there a
> > problem with this?
> > So I went back a step and pointed everything back to the original
> > unjarred classes and removed the extra .SER files. The result was that
> > I didn't get the extra line in the EJB startup {*1} (log listing 1)
> > referring to the ...HomeImpl class being bound to nothing, but I still
> > get the ClassCastException (log listing 3).
> >
> > Does anybody know what may be happening here, any pointers, etc.
>
>
> The problem is that you have to put all the Jars (where your beans are)
> in the CLASSPATH.
> Referencing the Jars in the 'weblogic.properties' for deployment is not
> sufficient.
>
> So to resolve the problem, you have to put every Jars with bean in it in
> the CLASSPATH environment variable before running Weblogic.
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
