Hi

To compile versions can be different but not at runtime.
Le 29 sept. 2013 08:18, "wlad" <[email protected]> a écrit :

> Romain Manni-Bucau wrote
> > Im pretty sure you have an environment issues since we use since the
> first
> > release of tomee ejbd to be certified. Maybe start from an empty/clean
> > environment.
>
> OK, I have unistalled Eclipse IDE I had (Indigo version), and installed
> newest Eclipse IDE for Java EE Developers (Kepler). Tried same example and
> getting same error.
>
> I'm not really experienced with Eclipse and have limited understanding of
> using and including libraries in eclipse project. I see there are
> compile-libs, runtime-libs and JRE System Library folder (that contains
> many
> other jars), but I don't really know which libs serve what purposes.
> We know that this example is valid. But it is probably coded on different
> eclipse version than mine, use different versions of some of jar libraries
> and probably tested with different version of tomcat server. Maybe even on
> different version of java runtime environment.
>
> I am using  java version "1.7.0_25", OpenJDK Runtime Environment, Eclipse
> IDE -version: Kepler Service Release 1, and apache-tomee-webprofile-1.5.2.
>
> Now, about different jar versions:
> I can see that under projects compile-libs folder is
> "javaee-api-6.0-4-tomcat.jar", and in the lib folder of mine tomee server
> is
> "javaee-api-6.0-5-tomcat.jar" (not the same version).
> Also, under projects runtime-libs folder is "openejb-client-4.5.0.jar" and
> in tomme's lib folder is "openejb-client-4.5.2.jar" (again different
> version).
>
> My question is: Do libraries included in imported eclipse project have to
> be
> same as those in the installed tomee/lib folder? Could that be the cause of
> EJB deploying and JNDI lookup issues?
>
>
>
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/JNDI-LOOKUP-error-Cannot-open-input-stream-to-server-tp4665304p4665349.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>

Reply via email to