• 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
  • Paul Clapham
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Tim Cooke
  • Bear Bibeault
  • paul wheaton
Saloon Keepers:
  • Carey Brown
  • Stephan van Hulst
  • Tim Holloway
  • Mikalai Zaikin
  • Piet Souris

Remote Java client

Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have developed a small web app runing on WAS 4.0.3, which uses a servlet that access a session bean successfully.
Now I am trying to create a remote command-line Java client, which will access the same session bean from a remote workstation.
When running the client in WSAD the application executes correctly. When I try to execute the appliation outside of WSAD I get the following exception:
javax.naming.NoInitialContextException: Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory [Root exception is java.lang.ClassNotFoundException: com.ibm.websphere.naming.WsnInitialContextFactory]
Exception in thread "main" java.lang.NoClassDefFoundError: com/palmharbor/roi/ejb/InventoryManagerHome
at com.palmharbor.roi.remote.TestClient.main(TestClient.java:76)
After reading all the other posts, I'm guessing I need to deploy some JAR files with my app on the remote workstation, but I am not sure which ones. Can anyone tell me exactly what I need to deploy with my app to get it to successfully connect to WAS?
The JRE I am using on the remote workstation is the same one used in WSAD.
Can't .... do .... plaid .... So I did this tiny ad instead:
Low Tech Laboratory
    Bookmark Topic Watch Topic
  • New Topic