IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.



#Automation


#Applicationintegration
#webMethods
#Integration
 View Only
  • 1.  B2B 402 Problem running Java CLIENT code as a Java Bean under Tomcat

    Posted 06/19/02 01:34 PM

    I have converted a Java Client Service to Java Bean so I can run it from a JSP. The service works as a standard java class but when running as a bean i get this error:

    java.lang.NoClassDefFoundError: com/wm/app/b2b/client/ServiceException

    Any ideas? Or has anyone written a simple java bean to call webMethods B2B 4.0.2


    #Integration-Server-and-ESB
    #webMethods
    #Flow-and-Java-services


  • 2.  RE: B2B 402 Problem running Java CLIENT code as a Java Bean under Tomcat

    Posted 06/19/02 01:53 PM

    Have you considered using DSP? It may not be an option here, I realize, but invoking a service from a “HTML” page using DSP is painfree. If you are agnostic regarding where your Web Server is located, you could use the B2B 4.0.2 instance for that function instead of JRun, for example.

    If need some assistance with DSP, just ask.

    Also, as a sidenote, the unified webMethods 6.0 Platform is being touted to provide full support for JSP on its hosted Web pages.


    #webMethods
    #Flow-and-Java-services
    #Integration-Server-and-ESB


  • 3.  RE: B2B 402 Problem running Java CLIENT code as a Java Bean under Tomcat

    Posted 06/19/02 03:40 PM

    Here is my guess.
    Did you import the com.wm.app.b2b.client.* package in your bean? Also make sure this package is available for your app server/JVM running your bean/standard java class during run time by adding it to the classpath.


    #Integration-Server-and-ESB
    #webMethods
    #Flow-and-Java-services


  • 4.  RE: B2B 402 Problem running Java CLIENT code as a Java Bean under Tomcat

    Posted 06/19/02 04:10 PM

    java.lang.NoClassDefFoundError kind of errors appear when JVM loader is not able to find the associated class. You have to make sure that your JSP engine has access to com.wm.app.b2b.client.ServiceException class which I believe is a part of client.jar.


    #Flow-and-Java-services
    #webMethods
    #Integration-Server-and-ESB


  • 5.  RE: B2B 402 Problem running Java CLIENT code as a Java Bean under Tomcat

    Posted 06/19/02 05:25 PM

    In simple Java terms it means you haven’t configured the classpath correctly.

    When working with Tomcat the easiest solution to your problem is to just drop the necessary jar into …/webapps/nameofyourapp/WEB-INF/lib and it will automatically be picked up in the classpath. The previous post indicated that the necessary jar is client.jar.

    Good luck and please tell us how you solved it. For the good of the rest of us.

    Rgs,
    Andreas
    www.amundin.com


    #webMethods
    #Integration-Server-and-ESB
    #Flow-and-Java-services


  • 6.  RE: B2B 402 Problem running Java CLIENT code as a Java Bean under Tomcat

    Posted 06/20/02 02:44 PM

    Guys - problem solved!!!

    Thanks Andreas! Used your solution below…


    In simple Java terms it means you haven’t configured the classpath correctly.

    When working with Tomcat the easiest solution to your problem is to just drop the necessary jar into …/webapps/nameofyourapp/WEB-INF/lib and it will automatically be picked up in the classpath. The previous post indicated that the necessary jar is client.jar.


    #Integration-Server-and-ESB
    #webMethods
    #Flow-and-Java-services