Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 36

Thread: HTTP 404 Error - Issue

  1. #11

    Default

    Ray, any other pointers ? Appreciate it.

  2. #12

    Default

    This is the tomcat log:

    INFO: Server startup in 2207 ms
    - Initializing Spring FrameworkServlet 'caob-shared'
    - FrameworkServlet 'caob-shared': initialization started
    - Refreshing org.springframework.web.context.support.XmlWebAppl icationContext@1f
    0b7d3: display name [WebApplicationContext for namespace 'caob-shared-servlet'];
    startup date [Thu Oct 25 11:04:44 EDT 2007]; root of context hierarchy
    - Loading XML bean definitions from ServletContext resource [/WEB-INF/caob-share
    d-servlet.xml]
    - Bean factory for application context [org.springframework.web.context.support.
    XmlWebApplicationContext@1f0b7d3]: org.springframework.beans.factory.support.Def
    aultListableBeanFactory@754fc
    - Bean 'org.springframework.ws.server.endpoint.intercepto r.PayloadLoggingInterce
    ptor#ffd135' is not eligible for getting processed by all BeanPostProcessors (fo
    r example: not eligible for auto-proxying)
    - Validating using ServletContext resource [/xsd/DocumentService.xsd]
    - Bean 'org.springframework.ws.soap.server.endpoint.inter ceptor.PayloadValidatin
    gInterceptor#1000bcf' is not eligible for getting processed by all BeanPostProce
    ssors (for example: not eligible for auto-proxying)
    - Bean 'org.springframework.ws.server.endpoint.mapping.Pa yloadRootAnnotationMeth
    odEndpointMapping' is not eligible for getting processed by all BeanPostProcesso
    rs (for example: not eligible for auto-proxying)
    - Pre-instantiating singletons in org.springframework.beans.factory.support.Defa
    ultListableBeanFactory@754fc: defining beans [documentationServiceEndpoint,docum
    entationService,marshaller,org.springframework.ws. server.endpoint.mapping.Payloa
    dRootAnnotationMethodEndpointMapping,org.springfra mework.ws.server.endpoint.adap
    ter.MarshallingMethodEndpointAdapter,documentServi ce]; root of factory hierarchy

    - Creating JAXBContext with context path [com.boea.jaxb.caob.documentation.ws.ja
    xb]
    - Creating SAAJ 1.2 MessageFactory
    - FrameworkServlet 'caob-shared': initialization completed in 2507 ms
    - No endpoint mapping found for [SaajSoapMessage {http://www.boea.com/c
    aob/webservices/documentation/schemas}GetDocumentListRequest]

  3. #13
    Join Date
    Oct 2004
    Posts
    207

    Default

    Is that contextPath correct on your Jaxb2Marshaller?
    com.boea.jaxb.caob.documentation.ws.jaxb

  4. #14

    Default

    Yes, thats right Ray.

    <property name="contextPath" value="com.boea.jaxb.caob.documentation.ws.jaxb"/>

  5. #15

    Default

    Any other pointers pls. I need to resolve this very urgently. Been stuck with this since last 2 days.

    Thanks
    Sunil

  6. #16
    Join Date
    Oct 2004
    Posts
    207

    Default

    I don't see anything obvious right now, and I have to focus on my "day job" for a bit.

    Looks like it's time to attach the spring-ws source, and fire up the debugger.
    Or at least set your logging to full on debug and take another pass at it.

  7. #17

    Default

    I have deployed the MTOM sample application provided by spring-ws on Tomcat. And I get the same error HTTP 404. The tomcat logs show:

    - No endpoint mapping found for [SaajSoapMessage {http://www.springframework.org
    /ws/samples/mtom/schema}LoadImageRequest]
    - No endpoint mapping found for [SaajSoapMessage {http://www.springframework.org
    /ws/samples/mtom/schema}LoadImageRequest]
    - No endpoint mapping found for [SaajSoapMessage {http://www.springframework.org
    /ws/samples/mtom/schema}LoadImageRequest]
    - No endpoint mapping found for [SaajSoapMessage {http://www.springframework.org
    /ws/samples/mtom/schema}LoadImageRequest]

  8. #18

    Default

    Would appreciate if anyone could provide some insight regarding the problem am facing. Am really stuck with it.

  9. #19
    Join Date
    Jul 2005
    Location
    Rotterdam, the Netherlands
    Posts
    1,562

    Default

    Everything looks ok, but if the mtom sample doesn't work, then it must be something on your machine. Are you runnning JDK 1.4, for instance? What client do you use to test the mtom sample?

    Perhaps you can use tcpmon https://tcpmon.dev.java.net/ to find out what is sent across the wire.
    Arjen Poutsma

    Spring Web Services Dev Lead
    Please read the FAQ

  10. #20

    Default

    Arjen.

    Am using JDK jdk150_04 . The tomcat version is tomcat-5.5.17. And using soapUI tool for testing the MTOM client.

    Thanks
    Sunil

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •