if system.properties config is the same and deployment too then there is no particular reason it should fail.
are you able to reproduce it using tomee-maven-plugin in a jar plugin and switching tomeeClassifier value? If so can you share a small sample on github? Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-07-27 15:53 GMT+02:00 sweiss77 <[email protected]>: > Thank you for the response. Our code is not using jaxws or jms, here is the > code- just doing a jndi lookup: > > /StringBuilder url = new StringBuilder("global/hq_calendarEjb/"); > > url.append(isLiferaySpecificService?"Liferay":"").append(ejbInterfaceClass.getSimpleName()).append("Bean!").append(ejbInterfaceClass.getName()); > Properties jndiProperties = new Properties(); > jndiProperties.put(Context.PROVIDER_URL, "http://localhost:8080/tomee/ejb > "); > jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, > "org.apache.openejb.client.RemoteInitialContextFactory"); > Context remotingContext = new InitialContext(jndiProperties); > Object resolvedproxy = remotingContext.lookup(url); > / > > Fyi, the url string is constructed as something like this: > > "global/hq_calendarEjb/LoggingServiceBean!gov.nasa.hq.calendar.ejb.session.LoggingService" > > This works in TomEE+ but not WebProfile. > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/EJB-application-works-in-TomEE-Plus-but-not-TomEE-webprofile-tp4679495p4679505.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
