Servlet chaining

Hi,
I am having three servlets. First servlet is receiving request
and after doing some processing it generates html and sends html
to user. Once user enters all details in requested page(html
page sent by servlet 1), he presses submit on that html.
At that time that html is calling another servlet(Servlet 2).
After receiving request from user, servlet 2 extract parameter
sent by user. Then it stores extracted parameter to database.
Depends upon one parameter (sent by user) servlet2 dispatch
request to servlet3.
Now I want to convert above servlets into portlet.
Can anybody tell me how to convert second servlet into portlet.
Because it is not shown in any page but still it receives
request. do some processing and send the response to third
servlet.
Do I need to change zone and jserv properties file for servlet2?
Do I need to enter servlet 2 in provider.xml where servlet 1 is
entered as portlet ?
Thanks in advance.
Biren

Hello,
What is the version of the weblogic server you are using ?
Regards
Anilkumar kari

Similar Messages

Servlet chaining problem..

import java.io.*;
    import javax.servlet.*;
    import javax.servlet.http.*;
    public class Deblink extends HttpServlet {
      public void doGet(HttpServletRequest req, HttpServletResponse res)
                                   throws ServletException, IOException {
        String contentType = req.getContentType(); // get the incoming type
        if (contentType == null) return; // nothing incoming, nothing to do
        res.setContentType(contentType); // set outgoing type to be incoming type
        PrintWriter out = res.getWriter();
        BufferedReader in = req.getReader();
        String line = null;
        while ((line = in.readLine()) != null) {
          line = replace(line, "<BLINK>", "");
          line = replace(line, "</BLINK>", "");
          out.println(line);
      public void doPost(HttpServletRequest req, HttpServletResponse res)
                                    throws ServletException, IOException {
        doGet(req, res);
      private String replace(String line, String oldString, String newString) {
        int index = 0;
        while ((index = line.indexOf(oldString, index)) >= 0) {
          // Replace the old string with the new string (inefficiently)
          line = line.substring(0, index) +
                 newString +
                 line.substring(index + oldString.length());
          index += newString.length();
        return line;
What is pre request fo above code to work.
I had tried this many time but it is not working, what will be calling servlet look like

And can you explain why your title is "Servlet chaining problem"?

Servlet Chaining and OAS 4.0.8.1

I am using the Request Dispatcher Concept for my application where a servlet either initiates a bean or calls another servlet. I believe I cannot test it from JDeveloper.But does OAS 4.0.8.1 support servlet chaining. Very Critical. if yes? Please let me know where I can find the necessary documentation.
Thanks

More info ...
I enable logging and found the following error
Unable to initiate threads: cannot find class java/lang/Thread.

Does weblogic server have Servlet chaining concept?

I saw JRun which has the servlet chaining function. Does anyone know how to
          do it in the weblogic server?
          Thank you.
          li


WLS does not support Servlet Chaining
          Kumar
          li wrote:
          > I saw JRun which has the servlet chaining function. Does anyone know how to
          > do it in the weblogic server?
          >
          > Thank you.
          >
          > li

Can WebLogic do Servlet chaining?

Is there any way to do servlet chaining, or more specifically, for a servlet
          to process the output of another servlet efficiently in WebLogic?
          Sure a servlet can make another HTTP request on its own servlet engine but
          that seems way too inefficient and heavy handed.
          J.
          James Strachan
          =============
          email: [email protected]
          web: http://www.metastuff.com


Check out XSPs from cocoon. xml.apache.org
          -- bk
          James Strachan wrote:
          > JSP includes go straight to the HTTP response - there's no way of
          > redirecting them to some internal buffer for post processing. (*)
          >
          > I'd like to be able to do simple Servlet chaining at the Servlet or JSP
          > level. i.e. I want to post process the output of one servlet / JSP page to
          > do things like caching or XSL styling. This is a totally reasonable request
          > IMHO. Imagine a complex portal with alot of included JSP files - I'd like to
          > be able to cache whole chunks of the page - a chunk may have many includes
          > inside it..
          >
          > Right now there is no way of doing such a thing in WebLogic AFAIK. You have
          > to go through every JSP file and add caching / styling to it rather than
          > being able to 'pipeline' or 'servlet chain' which is less than ideal. (Also
          > remember there is a 64K code size limit on the bytecode that can exist in a
          > Java class - so JSP files should be kept small to void hitting this
          > barrier). I can't quite believe noone else has hit this problem.
          >
          > There are workarounds such as to do the include using seperate internal HTTP
          > requests, RMI calls or JMS messages all of which seem to be far too
          > heavyweight.
          >
          > (*)
          > <aside>
          > One side effect of the JSP include always going straight to the response
          > means that you can't use WebLogics <cache> tag if you are using any kind of
          > JSP include. e.g. the following snippet doesn't work as expected :-
          >
          > <cache>
          > something
          > <jsp:include file="foo.jsp" flush="true"/>
          > something else
          > </cache>
          >
          > since you are not allowed to do an include inside a body tag,. Even if you
          > were the output of the include goes straight to the response, not the body
          > tag.
          >
          > So you have to close and reopen the cache tags around each include which may
          > break your XML complience for complex pages and is error prone and much more
          > inefficent to boot:-
          >
          > <cache>
          > something
          > </cache>
          > <jsp:include file="foo.jsp" flush="true"/>
          > <cache>
          > something else
          > </cache>
          >
          > </aside>
          >
          > --
          > J.
          >
          > James Strachan
          > =============
          > email: [email protected]
          > web: http://www.metastuff.com
          >
          > "Jaggu Dada" <[email protected]> wrote in message
          > news:[email protected]...
          > >
          > > Hi --
          > >
          > > Why not use JSP includes? The only servlet "chaining" that is
          > > reasonable
          > > is to use a servlet to process an initial request, and make some
          > > decision
          > > (based on the querystr, for example) then, without having written
          > > anything
          > > back to the client, do a server side redirect (with RequestDispatcher)
          > > to
          > > a servlet or JSP that does some work. If I understand you correctly,
          > > servlets
          > > were not designed to do what you are proposing.
          > >
          > > Hope this helps,
          > >
          > > -jaggu
          > >
          > > James Strachan wrote:
          > > >
          > > > Hi Joe
          > > >
          > > > Thanks for that. Sure that would work too though its probably a heavier
          > > > weight than just plain old HTTP.
          > > >
          > > > I was looking for something a little more lightweight such that I could
          > > > include 10-20 servlet chains per web page on a complex portal without
          > too
          > > > much performance hit. i.e. using synchronous servlet 'pipelining' to
          > > > generate complex pages without having to do many internal HTTP / JMS
          > > > requests.
          > > >
          > > > --
          > > > J.
          > > >
          > > > James Strachan
          > > > =============
          > > > email: [email protected]
          > > > web: http://www.metastuff.com
          > > >
          > > > "Joe Trung" <[email protected]> wrote in message
          > > > news:[email protected]...
          > > > >
          > > > > Hi Jim,
          > > > > I chain my servlets via jms: the queue is output/input bin
          > > > >
          > > > > Joe
          > > > >
          > > > >
          > > > > "James Strachan" <[email protected]> wrote:
          > > > > >Is there any way to do servlet chaining, or more specifically, for a
          > > > servlet
          > > > > >to process the output of another servlet efficiently in WebLogic?
          > > > > >
          > > > > >Sure a servlet can make another HTTP request on its own servlet
          > engine
          > > > but
          > > > > >that seems way too inefficient and heavy handed.
          > > > > >
          > > > > >J.
          > > > > >
          > > > > >James Strachan
          > > > > >=============
          > > > > >email: [email protected]
          > > > > >web: http://www.metastuff.com
          > > > > >
          > > > > >
          > > > > >
          > > > >

How to Configure a Servlet Chain Using MIME Types with weblogic5.1?

Hi ,
          I want to configure a servlet(cocoon) in weblogic 5.1 such that the
          servlet so configured is invoked each
          time a response with the mime-type "text/xml" is generated.
          1.) will weblogic support to configure a servlet with a particular
          mime-type so that it post-process any
          servlet's response with the corresponding mime-type?
          2.) if not what is the alternative?
          Thanks
          sumanth
          [sumo.vcf]


We suggest that use the request dispatcher interface instead. Servlet
          chaining is not a standard's based possibility.
          Michael Girdley
          WLS Product Manager
          Sumanth Chinthagunta <[email protected]> wrote in message
          news:[email protected]..
          > Hi ,
          > I want to configure a servlet(cocoon) in weblogic 5.1 such that the
          > servlet so configured is invoked each
          > time a response with the mime-type "text/xml" is generated.
          > 1.) will weblogic support to configure a servlet with a particular
          > mime-type so that it post-process any
          > servlet's response with the corresponding mime-type?
          > 2.) if not what is the alternative?
          >
          > Thanks
          > sumanth
          >

Servlet chaining possibility

Hi, A reply to one of the earlier messages, says "servlet chaining is currently not available". does it mean it would be available in future versions or do we have support for it in any of the currently available, recently released versions?


i just wondering, why you want to chain the servlets in what way, is that
          the servlet application is in someway already chained in by itself.
          it would be little use in my mind to have chained servlet.
          just my opinon
          Frank
          Mahesha <[email protected]> wrote in message
          news:40d8c8fc$1@mktnews1...
          > Hi, A reply to one of the earlier messages, says "servlet chaining is
          currently not available". does it mean it would be available in future
          versions or do we have support for it in any of the currently available,
          recently released versions?

Is servlet chaining (filtering) supported?

For a given virtual name I would like to set up a chain of servlets
          (ProducerServlet, ConsumerServlet) so that the ServletInputStream of the
          ConsumerServlet contains the results of the ServletOutputStream of the
          ProducerServlet. The ConsumerServlet is in effect 'filtering' the results
          of ProducerServlet.
          eg. BrowserRequest --> ProducerServlet --> ConsumerServlet -->
          BrowserResponse
          Can this be done with WLS 5.1?
          The RequestDispatcher interface does not seem to satisfy these requirements?
          If I understand this interface correctly, it allows requests to be either
          'forwarded' (where the output of the forwarder is not used) or 'included'
          (where the included servlet inserts output in the stream). But it does not
          allow servlets to be connected in a producer-consumer chain.
          Am I missing something?
          Thank you.
          Marko.


Is there any way to achieve the same effect within the current spec?
          Marko.
          Winston Koh <[email protected]> wrote in message
          news:[email protected]...
          > Hey Marko, servlet chaining is not supported in WLS since its a
          proprietary
          > mechanism not specified in the current servlet/jsp specs
          >
          > thanx
          >
          > Winston
          > Marko Milicevic <[email protected]> wrote in message
          > news:[email protected]...
          > > For a given virtual name I would like to set up a chain of servlets
          > > (ProducerServlet, ConsumerServlet) so that the ServletInputStream of the
          > > ConsumerServlet contains the results of the ServletOutputStream of the
          > > ProducerServlet. The ConsumerServlet is in effect 'filtering' the
          results
          > > of ProducerServlet.
          > >
          > > eg. BrowserRequest --> ProducerServlet --> ConsumerServlet -->
          > > BrowserResponse
          > >
          > > Can this be done with WLS 5.1?
          > >
          > > The RequestDispatcher interface does not seem to satisfy these
          > requirements?
          > > If I understand this interface correctly, it allows requests to be
          either
          > > 'forwarded' (where the output of the forwarder is not used) or
          'included'
          > > (where the included servlet inserts output in the stream). But it does
          > not
          > > allow servlets to be connected in a producer-consumer chain.
          > >
          > > Am I missing something?
          > >
          > > Thank you.
          > >
          > > Marko.
          > > .
          > >
          > >
          > >
          >
          >

Servlet chaining or reponse filtering

          Does WL6 currently support one of these features? If not, how can I do this under
          WL6?


If not, how can I do this under          >WL6?
          I do this:
          I create one controller servlet. then I create many command classes, they
          have a constructor and one execute(req, res) method, which throws my
          exception.
          in servlet's init(), I load these commands, and put them in hashmap. then in
          service() I call one of the command's execute(req, res) method.
          I have many commands, some of them call each other, put variables in a
          session, analyze requests etc.

Servlet and JSP in OAS

I'm developing web application with OAS
4.0.8.1 and JDeveloper 3.0 and I want to call
JSP from servlet using "RequestDispatcher".
I downloaded JSP for OAS from www.olab.com.
In the Release note, there is a description
about RequestDispatcher, but I cannot
understand about details.
In what configuration can I use servlet and
JSP together with RequestDispatcher. Anyone
scceeded about that?
null

wan (guest) wrote:
: Hi everyone,
: I am using OAS 4.0.8 on Solaris 2.6. After viewing servlet
: and JSP samples, I am kind of confuse whether OAS supports the
: following options
: 1. JSP
: 2. servlet chaining
: 3. running JDeveloper DB Servlet wizard
: (oracle.jdeveloper.servlet.*) and Java Business Objects
: (oracle.jbo.rt.cs)
: Thank you for your time.
I found a white paper 408newfead.pdf, that says under "Future
Directions" that it will add jsp support. I read somewhere (I
can't remember where exactly :( ) that said 4.0.8.1 would
support
JSPs. I don't know if this release is out yet.
I wish Oracle would get with the times and put out a product that
is consistent with the technology they are touting as the
future.
Having us download Suns server to run servlets and JSP is
ridiculous for the worlds second largest software company!
null

RequestDispatcher.forward on OAS 4.0.8.1 for Servlet Communication

We are unable to pass request information from a servlet to another servlet or a JSP on OAS 4.0.8.1 whereas we have been able to achieve this
successfully in JDK using the same code.
Since Servlet Chaining is not supported in the JServlet of OAS, use the forward
method in the RequestDispatcher object instead.
RequestDispatcher rd;
rd =getServletConfig().getServletContext().getRequestDispatcher(/testme1/USe
rvl
et);
rd.forward(request,response);
It didn't do anything with the forward method and nothing was logged in the log file. Anyone out there, please send help ASAP. Thanks.
null

After I fixed some of the things I broke while searching for the wrksf failure, the PL/SQL Cartridge now works for me too. And, after failing to get the DB Browser to work by loading it into the SCOTT schema, I got it to work by loading it into SYS. (SCOTT can't see the DBA_* views so loading the DB Browser into the database failed.) I haven't tried any Java Servlets yet, but that's next on my list.
If you want to try my wrksf workaround, rather than using Christoph's, here's how you can do it.
1. Backup liborb.so in the $ORACLE_HOME/orb/4.0/lib directory, just in case something goes wrong.
2. Using a hex editor, such as emacs hexl-find-file or ghex, to edit liborb.so, find the string "/proc/stat".
3. Change the directory, "/proc" to something like "/pfoo" and write the shared library file back to liborb.so. You now have the required modified liborb.so.
4. Make the /pfoo directory and cp /proc/stat /pfoo.
5. Edit /pfoo/stat and duplicate the first line, which should be the cpu line. This will let the metrics parser handle it. Make sure that /pfoo/stat has read access.
Of course, the values that the metrics code gets are now bogus, but that does not seem to be a fatal problem.
Hopefully somebody from Oracle is reading this and the real fix will be in the mail soon.

Servlet/jsp & custom sessions

          Our app is using custom sessions with most of the data stored in
          ejbeans. We can't really use http sessions
          as multiple 'http' sessions may end up using the same set of beans which
          make up our own 'application defined'
          session. As the set of beans making up one session are typically located
          on the same host, we'd like to make sure
          that all requests using them are processed on the respecting host.
          I understand now that performing some kind of 'servlet-chaining' in
          order to forward a request to the correct host
          is a bad idea. Our current solution is to wrap the processing of the
          request into a ejbean which is made available
          throughout the cluster by adding a reference into the jndi tree (using
          the beans allows us to ensure that sessions time
          out when necessary.) What i don't like about this approach is that there
          is no way to write a simple servlet or jsp
          pages as direct access to the servlet interface is lost (a copy of the
          servlet-related data could be sent to the bean
          on remote host, but that's expensive and ends up in something similar to
          servlet-chaining.)
          Does any know of possibilities to solve this problem a little bit more
          elegantly? Essentially i'd like to run servlet and
          jsp pages on top of our 'application defined' sessions, efficiently
          working in a cluster.
          Thanks a lot for any suggestions,
          roman


          thank's for your reply!
          the whole thing is not really related to ejb, i'm just using it as a
          workaround.
          it's actually a gross misuse of ejb...
          the main issue is that i'd like to be able to write jsp pages and store
          per-session
          information in a object other than the HttpSession. i cannot use the
          HttpSession
          because one session in our application does not necessarily correspond
          to one http
          session.
          so far the solution is trivial; i just keep keep a reference to the
          session data
          in the jndi tree. for each request, i can find the data with one jndi
          lookup. it
          even works on a cluster by using remote objects and a replicated jndi
          tree (thank
          you, weblogic!)
          but, for efficiency, i'd also like to process each request on the same
          host where
          the session data is stored... how can i do that without servlet
          chaining?
          roman
          Prasad Peddada wrote:
          >
          > It is not quite clear to me what you are trying to do here.
          >
          > What type of ejbs are you talking about?
          >
          > Roman Puttkammer wrote:
          >
          > > Our app is using custom sessions with most of the data stored in
          > > ejbeans. We can't really use http sessions
          > > as multiple 'http' sessions may end up using the same set of beans which
          > > make up our own 'application defined'
          > > session. As the set of beans making up one session are typically located
          > > on the same host, we'd like to make sure
          > > that all requests using them are processed on the respecting host.
          > >
          > > I understand now that performing some kind of 'servlet-chaining' in
          > > order to forward a request to the correct host
          > > is a bad idea. Our current solution is to wrap the processing of the
          > > request into a ejbean which is made available
          > > throughout the cluster by adding a reference into the jndi tree (using
          > > the beans allows us to ensure that sessions time
          > > out when necessary.) What i don't like about this approach is that there
          > > is no way to write a simple servlet or jsp
          > > pages as direct access to the servlet interface is lost (a copy of the
          > > servlet-related data could be sent to the bean
          > > on remote host, but that's expensive and ends up in something similar to
          > > servlet-chaining.)
          > >
          > > Does any know of possibilities to solve this problem a little bit more
          > > elegantly? Essentially i'd like to run servlet and
          > > jsp pages on top of our 'application defined' sessions, efficiently
          > > working in a cluster.
          > >
          > > Thanks a lot for any suggestions,
          > > roman

Can a HTML form send data to two servlets?

I would like to know if an HTML Form can send data to two servlets, I guess I am askin is that can the parameters be passed to two ACTION attributes??

Hmmmm, well I'm not sure if that is possible, but you could do something of the sort on the server side by chaining them.... the technieque is called Servlet Chaining
Hope this helps
Omer

HELP: JSP + XML + XSLT = HTML?

Hello, all.
I am trying out Weblogic 6 and I am trying to get the JSP + XML + XSLT =>
HTML chain working.
I am coming from using Orion and SAXON.. and in that situation I had a JSP
that contained XML tags... they were filled in at runtime and then using
Servlet-Chaining was passed along to the SAXON XSLT Processer. SAXON checked
for the inline XSL specified and then used that to transform the document
into HTML.
It worked well, but there were some other features missing/not documented
that we now need.
With Weblogic I am trying to use the XSLT Tag Library that comes with the
distribution, but it seems to be very finicky. I followed the directions and
I got it to do a sort of roundabout transformation. But it doesn't seem to
work quite right.
The best I can get is the following:
I have an 'xslt' directory url-pattern-mapped to xslt.jsp (as instructed)...
but can't figure out how to specify the xsl file on-the-fly... that is, if I
don't hard-code the XSL file in the x:xslt element in the xslt.jsp it
complains about some XML file not having a root element.
Ideal situation:
1. I have a JSP that includes XML elements.
2. It is filled from a database at runtime and specifys (using a PI) what
XSL stylesheet it is to be processed with.
3. Somehow (fingers crossed) the XML is processed and transformed into HTML
by the appropriate XSL file.
I think I am mostly stuck moving between steps 2 and 3.
Can anyone give me some hints? Are there some Weblogic specific
elements/tags that I have to include in the XML file that Weblogic will
catch and re-direct to the XSL Parser?
Please, anyone, if you have some information, I would much appreciate it.
Dylan Parker
PS - I apologize for the cross-post, I hope it doesn't cause too much
traffic.

Craig,
I've since discovered how to do it with the WL Taglibrary... and have
moved on =)
It has to do with the EXTREMELY BADLY documented x:xml tag that can
appear within the x:xslt tag body...
So the WL Tag Library allows something like the following.
(Please note, angled brackets are omitted in this post to prevent html
parsing)
[x:xslt stylesheet="sheet.xsl"]
[x:xml]
Here is the XML to run the sheet on.
This should have all relevant XML syntax: the PIs, the doctype,
root elements etc...
[x:xml]
[x:xslt]
And that DOES work. But not very well. WL, a little prematurely
incorporated versions 1.2 of Xerces and Xalan in their product -- and
these versions have some irritating bugs.
Also -- There tag library doesn't copy the source XML across as UTF-8
.. so a lot of the Japanese I have embedded there (from a DB) gets
mangled somewhere in their code...
AND -- If you hammer a little bit on an JSP/XML that uses the WL Tag
Library (eg clicking refresh lots of times in IE)... I get huge
amounts of irritating exceptions appearing in the log files.
NullPointerExceptions
XSL Parsing Exceptions
XML Parsing Exceptions
but completely unpredictably...
In my eyes.. the WL XML/XSL Tag Library using the incorporated and
untouchable Xalan and Xerces (v1.2) is virtually unusable.
What a pain.
BUT! Apache offers a similar OPEN SOURCE XSL Tag Library available
here:
http://jakarta.apache.org/taglibs/doc/xsl-doc/intro.html
And it uses the standard, non-weblogic-incorporated, Xerces and Xalan
(which means you can provide whatever version you want).. and it works
impressively well.
It has almost identical performance as the WL Taglib, and without all
of the bizarre exceptions being thrown.
And it does proper passing of the character encoding type!
If only the taglib did caching though =(
The performance hit over pure JSP is huge. Almost two orders of
magnitude. On my desktop box I can get around 500Requests/Sec if I am
returning HTML direct from a JSP... while if I produce XML that gets
processed by XSL into HTML the Requests/Sec drops to 5!!!!
Caching. Caching. And more Caching. A lot of DiskIO is going on with
the XML/XSL/XHTML chain of events.
I hope this helps!
I'd be curious as to what you find out as well.
Dylan Parker
On 5 Mar 2001 07:20:00 -0800, "Craig Macha"
<[email protected]> wrote:
>
Yep, I feel Dylan's pain.
I am trying to accomplish the same thing. A JSP page generating
dynamic XML content and then utilizing an XSLT stylesheet to transform
all the content into XHTML.
Does anyone have some examples that show exactly how to accomplish
this? Can I do this with WLS and the XML taglib that comes with
it? Or do I have to move on to something like Cocoon to get this
capability?
Any insight would be greatly appreciated.
Thanks,
Craig Macha
"Dylan Parker" <[email protected]> wrote:
Hello, all.
I am trying out Weblogic 6 and I am trying to get the
JSP + XML + XSLT =>
HTML chain working.
I am coming from using Orion and SAXON.. and in that situation
I had a JSP
that contained XML tags... they were filled in at runtime
and then using
Servlet-Chaining was passed along to the SAXON XSLT Processer.
SAXON checked
for the inline XSL specified and then used that to transform
the document
into HTML.
It worked well, but there were some other features missing/not
documented
that we now need.
With Weblogic I am trying to use the XSLT Tag Library
that comes with the
distribution, but it seems to be very finicky. I followed
the directions and
I got it to do a sort of roundabout transformation. But
it doesn't seem to
work quite right.
The best I can get is the following:
I have an 'xslt' directory url-pattern-mapped to xslt.jsp
(as instructed)...
but can't figure out how to specify the xsl file on-the-fly...
that is, if I
don't hard-code the XSL file in the x:xslt element in
the xslt.jsp it
complains about some XML file not having a root element.
Ideal situation:
1. I have a JSP that includes XML elements.
2. It is filled from a database at runtime and specifys
(using a PI) what
XSL stylesheet it is to be processed with.
3. Somehow (fingers crossed) the XML is processed and
transformed into HTML
by the appropriate XSL file.
I think I am mostly stuck moving between steps 2 and 3.
Can anyone give me some hints? Are there some Weblogic
specific
elements/tags that I have to include in the XML file that
Weblogic will
catch and re-direct to the XSL Parser?
Please, anyone, if you have some information, I would
much appreciate it.
Dylan Parker
PS - I apologize for the cross-post, I hope it doesn't
cause too much
traffic.

OAS 4.0.8 download?

Hi,
We want test the features of OAS 4.0.8 such as servlets using
jservlet cartrigde. Does OAS 4.0.8 support servlet chaining like
Java Web Server2.0 does?
Can you tell me how to get the password in order to download oas
4.0.8? Please reply. Thanks
Louis
null

Where can I download OAS 4.0.8.2.1?
Thanks,
Davaa

Servlet chaining

Similar Messages

Maybe you are looking for