• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Paul Clapham
  • Rob Spoor
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Carey Brown

Remote EJB lookup using Spring Batch, Spring Boot and WebSphere 8.5.5

Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a batch application using Spring Batch, and I'm using Spring Boot as well. This application needs to do Remote EJB lookups to load some informations from the application server. Until now we were using JBoss EAP 6.1. My pom.xml contains a profile specific for JBoss and I was using the following dependency:

Now we need to migrate this application to WebSphere 8.5.5. I've created a new maven profile in my pom.xml with the following dependencies for Remote EJB Lookup on WebSphere.

Of course I've already installed this jars in my maven local repository.

Trying to execute the batch again, after configuring all the JNDI properties, Initial Context factory pointing to "com.ibm.websphere.naming.WsnInitialContextFactory" and Provider URL to "corbaloc:iiop:localhost:2817", I got the following exception:

Ok, the class has not being found. Trying to figure out the problem, I've changed the dependency type of WebSphere libs from "pom" to "jar".

Now, I'm getting the following exception:

(Sorry about this Portuguese text, but the error code may help)

**NMSV0307E**: Um nome de URL java: foi utilizado, mas a Nomenclatura não foi configurada para manipular nomes de URL java:. A causa provável é um erro do usuário ao tentar especificar um nome de URL java: em um cliente não J2EE ou no ambiente do servidor. Emitindo ConfigurationException.

Does anyone already tried to do that?
    Bookmark Topic Watch Topic
  • New Topic