This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Please forgive if this is a dumb question. 1. I have an ASP application which takes parameters from a HTML page. 2. I then take the parameters and do a redirect to a servlet I have written. 3. This, so far is fine. What I need to do now is submit my search parameters to a third party product which also runs as a servlet also. I was going to do a redirect to the third party URL with my parameters. This is were my problem starts. The third party product returns XML to the browser. I need to capture the search results ( somehow ) in my servlet, do some processing, build a result string and redirect this back to my ASP application The third party give the following description of how their servlet works: "our product is only supported when used as a servlet, whereby the class com.aaaaa.bbbbb.Controller is mapped directly to a URL (this is how our product normally works) within a servlet engine. There is no internal integration with a clients applicaton, all integration between our product and a client application happens at a data exchange level - via a HTTP POST of XML, CGI or POST parameters - data in those formats goes in via standard HTTP mechanisms, data out in XML over HTTP." Can anyone let me know if from the description above I can capture the XML sent back to the browser.
I guess the most elegant and most transparent way of solving this is to construct a Filter, configure this Filter to process after the call to the servlet. In this filter you can do a rather straightforward XSL-T transformation (in which the returned XML document is transformed into HTML or other XML format). If I understand correctly: ASP page --> servlet 1 --> external servlet --> your filter --> browser Hope this helps.