D L

Greenhorn
+ Follow
since Aug 12, 2005
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by D L

SOAPscope Viewer is available for a few days trial .. then it reverts to a "lite" version. You can extend trial period by completing a survey form.

Also see SOA editor at http://www.capeclear.com.
Not as comprehensive as Soapscope viewer but still useful .. and free.
18 years ago
You can use SOAP to pass data pointers (not the full dataset which would be passed through another channel).

See 3.3 in this paper .. again on grid computing.
18 years ago
This is a list of Community Members of WS-I.org

and Advocates.

Not exactly a review or product matrix .. but you can run through the capabilities of the WS-I compliant offerings.

One of the Advocates might have a survey.
[ August 25, 2005: Message edited by: D L ]
18 years ago
Try invoking your web service from SOAPscope Viewer using the free trial period .. mindreef.com .. I found it useful in troubleshooting some services.

After adding your WSDL to SOAPscope Viewer you can invoke webservice directly and insert the username, password, and inspect Request/Response.

You can inspect the authentication.

But your authentication error does seems to be related to IIS rather than web service authentication.
[ August 16, 2005: Message edited by: D L ]
18 years ago

but fiddler doens't show any output.



I have been troubleshooting some web services which I could not get to work ... and Microsoft Fiddler certainly did help.

You should certainly see the SOAP Request message (encoded) in TextView.

If you see no SOAP Response message at all in Session Inspector in TextView .. then look at Hex to see the raw hex response (which normally goes into your server log).

A few more tools I have gathered ..

SOAPscope Viewer which analyses your WSDL and allows you to invoke web services.

You can analyse WSDL's with https:// .. secure connection.

Try first invoking your web service directly in SOAPscope Viewer.

  • Go to WSDL tab
  • Add your target WSDL so that it shows in lefthand window
  • View your WSDL (View Tab)
  • Invoke your web service (Invoke Tab) and fill in the fields in the GUI.
  • Send your Request (Send button)
  • Analyse response.



  • This bypasses any problems which may be introduced by your SOAP client, since your web service is invoked via SOAPscope Viewer.


    You get a few days free trial of SOAPscope after which it reverts to a lighter version (invoke and WS-I test is disabled).
    But it should help still in troubleshooting.

    You can get an extension of free trial.

    Another tool is SOA Editor (free) which analyses WSDL files.
    [ August 15, 2005: Message edited by: D L ]
    18 years ago
    Latest in my testing of Axis ..

    Earlier, I had taken two steps in one in trying to get Axis to work:

    (a) copied Axis jars into %TOMCAT_HOME%\common\lib\

    (b) changed from JVM 1.5 back to JVM 1.4

    I decided to take it one step at a time and reverted from JVM 1.4 back to JVM 1.5.

    .. rebooted .. and Axis now works.

    ....

    So the one step which seems to make it work is copying Axis jars into %TOMCAT_HOME%\common\lib\

    ....

    I'm also looking at XFire for comparison of features.
    [ August 13, 2005: Message edited by: D L ]
    18 years ago
    Thanks for confirming that Axis works in JVM 1.5 .. I will try again .. restructuring CLASSPATH to see if the problem is in there ..

    I downloaded activation.jar and placed this in %TOMCAT_HOME%\common\lib\
    and this jar is now found in validation test ..

    One tip: to inspect the loading of jars .. if an Environment Variable
    %JAVA_OPTS% is set, then add to this .. -verbose:class .. to get much more verbose reporting of loading jars when tomcat is started.
    [ August 13, 2005: Message edited by: D L ]
    18 years ago
    After a lot of googling .. I found this tutorial which suggests that axis does not work in JVM 1.5 .. so on falling back to JVM 1.4 .. I was able to progress to run axis ..

    running happyaxis.jsp all jars were found, but one error found was this

    Error: could not find class javax.activation.DataHandler from file activation.jar
    Axis will not work.

    I have yet to work out how to find activation.jar.

    But is this correct? Axis and JVM 1.5 are incompatible?
    [ August 12, 2005: Message edited by: D L ]
    18 years ago
    My problem is getting Axis to startup from a fresh installation.

    Any insights (from logs below) into what might be wrong?

    .......

    Troubleshooting Checklist:

    Tomcat 5.0.29 and JVM 1.5.0_04-b05 are installed on Win XP (and working).

    New installation of Axis is placed into %TOMCAT_HOME%\webapps\

    %TOMCAT_HOME%\webapps\axis

    >docs
    >samples
    >WEB-INF
    >xmls
    -- happyaxis.jsp
    -- etc.


    Xerces is already installed and so these files were copied

    xercesImpl.jar
    xml-apis.jar

    into %TOMCAT_HOME%\webapps\axis\WEB-INF\lib\


    Axis also placed into c:\axis
    and Environment variables set

    %AXIS_HOME%
    %AXIS_LIB%
    %CLASSPATHAXIS%

    as per the installation guide.


    Tomcat runs fine. http://localhost:8080

    In Tomcat Manager the application /axis is listed amongst other applications (which all work .. only axis does not work).

    When http://localhost:8080.axis/ is launched this is the response I get ..

    HTTP Status 500

    type Exception report

    message

    description The server encountered an internal error () that prevented it from fulfilling this request.

    exception

    org.apache.jasper.JasperException: Unable to compile class for JSP
    org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:97)
    org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:346)
    org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:434)
    org.apache.jasper.compiler.Compiler.compile(Compiler.java:492)
    org.apache.jasper.compiler.Compiler.compile(Compiler.java:471)
    org.apache.jasper.compiler.Compiler.compile(Compiler.java:459)
    org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:802)


    root cause

    Compile failed; see the compiler error output for details.
    org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:938)
    org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:758)
    org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:402)
    org.apache.jasper.compiler.Compiler.compile(Compiler.java:492)
    org.apache.jasper.compiler.Compiler.compile(Compiler.java:471)
    org.apache.jasper.compiler.Compiler.compile(Compiler.java:459)
    org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

    note The full stack trace of the root cause is available in the Apache Tomcat/5.0.29 logs.


    ________________________________________________

    Then inspecting 5.0.29 log ..

    ________________________________________________


    <snipped> ... preceded by correct registration of tomcat applications .. then .. this ..

    2005-08-12 18:59:38 StandardContext[/servlets-examples]ContextListener: contextInitialized()
    2005-08-12 18:59:38 StandardContext[/servlets-examples]SessionListener: contextInitialized()
    2005-08-12 18:59:38 StandardContext[/servlets-examples]cgi: init: loglevel set to 6
    2005-08-12 18:59:38 StandardContext[/tomcat-docs]cgi: init: loglevel set to 6
    2005-08-12 19:00:17 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception
    Compile failed; see the compiler error output for details.
    at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:938)
    at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:758)
    at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:402)
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:492)
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:471)
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:459)
    at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
    at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
    at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
    at java.lang.Thread.run(Thread.java:595)


    [ August 12, 2005: Message edited by: D L ]
    18 years ago
    Quote from OpenEJB site ..

    "OpenEJB is an open source, modular, configurable, and extendable EJB Container System and EJB Server."

    Read OpenEJB + Tomcat Integration
    18 years ago
    one way .. instal openejb in your server
    18 years ago
    Try
    Microsoft Fiddler HTTP Debugging Proxy .. click on the HTTP Session .. and go to Session Inspector to view Request and Response .. in Text View or XML View.

    Or try other tracing tools .. YATT at PocketSoap.com
    18 years ago