Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6155103
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T20:22:35+00:00 2026-05-23T20:22:35+00:00

I recently solved the problem of the direct streaming with Spring WS , thanks

  • 0

I recently solved the problem of the direct streaming with Spring WS, thanks to Arjen for the fast response. The trick was to disable payload caching in the Axiom message factory.

I now suffering from that global decision, we have either to enable or disable payload caching for the whole system. We would like to have webservices with streaming and also some which enables validation (which is not possible if payload caching is disabled)

So is it possible to map an specific endpoint to an specific message factory? It’s easy to do with webservice clients, but what about endpoints? Any ideas?

Thank you!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T20:22:36+00:00Added an answer on May 23, 2026 at 8:22 pm

    You’re right, it’s very easy on client side passing the specific WebServiceMessageFactory instance to the WebServiceTemplate constructor.

    Anyway, I guess it’s also possible on server side.
    If you can use different url mappings, the simplest way I found out is based on the configuration of two (or more) differents MessageDispatcherServlet in your web.xml. Then you just have to pass as init parameter the specific bean name of the WebServiceMessageFactory instance you prefer. Something like this:

    <servlet>
        <servlet-name>ws1</servlet-name>
        <servlet-class>org.springframework.ws.transport.http.MessageDispatcherServlet</servlet-class>
        <init-param>
            <param-name>contextConfigLocation</param-name>
            <param-value>/WEB-INF/conf/ws1-servlet.xml</param-value>
        </init-param>
        <init-param>
            <param-name>messageFactoryBeanName</param-name>
            <param-value>defaultMessageFactory</param-value>
        </init-param>
    </servlet>
    
    <servlet>
        <servlet-name>ws2</servlet-name>
        <servlet-class>org.springframework.ws.transport.http.MessageDispatcherServlet</servlet-class>
        <init-param>
            <param-name>contextConfigLocation</param-name>
            <param-value>/WEB-INF/conf/ws2-servlet.xml</param-value>
        </init-param>
        <init-param>
            <param-name>messageFactoryBeanName</param-name>
            <param-value>streamingMessageFactory</param-value>
        </init-param>
    </servlet>
    
    <servlet-mapping>
        <servlet-name>ws1</servlet-name>
        <url-pattern>/ws1</url-pattern>
    </servlet-mapping>
    
    <servlet-mapping>
        <servlet-name>ws2</servlet-name>
        <url-pattern>/ws2</url-pattern>
    </servlet-mapping>
    

    Then, you just have to add your different message factory beans to your spring-ws context.

    Hope this helps.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I solved a problem recently. But I have this one piece of code where
Possible Duplicate: Learning efficient algorithms I recently came across an problem that was solved
I recently solved a somewhat common problem in OC4J regarding the use of Xerces
I recently solved a jquery problem I had by switching all the '$'s in
I recently had this problem about scrolling and focus changing. I solved it by
Recently I had a problem. How to disable scrolling in a particular area of
Recently I have been investigating the possibilities of caching in ASP.NET. I rolled my
With the help of this community, I just recently solved some issues with PHPExcel
I recently had a problem with two threads sticking in deadlock because they weren't
Recently, I ran into a mysterious problem in an android project, which I described

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.