Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: pass (athena.apache.org: domain of arunkumar.boppudi@gmail.com
 designates 209.85.212.48 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=so4FZUu8me4cF7i133NefNqswRbJGU/Ing8+BG5mQER1GLU7Q5ATl0VfQuhoBN6mXE
         MsZd4E4qrWwsywUxgLgCai0jwj9Orndh1El5GS2IIWqLZwz0Sjyt7GOXsWgDOR7NAgu5
         OXo8jNfbH1RM4lL+zVfYSHRR8yfIDaLHnrVeE=
MIME-Version: 1.0
In-Reply-To: <SNT141-w30B728EA06F1F5E510F74DF7AA0@phx.gbl>
References: <AANLkTi=x7kKZEz_PWewwCeVoz9nJ8MAus7VkSUUPagM_@mail.gmail.com>
	<OF0558A8CB.7F806F0E-ON6525776F.001A7FE8-6525776F.001AE83E@tcs.com>
	<AANLkTimO9f19SJgeVJMXs+v-HcBL2dM3KtN72ENMem=t@mail.gmail.com>
	<OFFFBF1965.3D725F86-ON6525776F.001DEF67-6525776F.001E48B8@tcs.com>
	<AANLkTim3e+hWowTThWF1U1HfQ2m-+RA6yT35e9LwEqqk@mail.gmail.com>
	<OF3D0FBE3C.C38E5C2A-ON6525776F.003148FE-6525776F.00323394@tcs.com>
	<AANLkTimBY94c0UctTZw78ms7FFhq39c=iqKpkeek8DSN@mail.gmail.com>
	<OFA8BB94F8.E7018AE3-ON6525776F.00443964-6525776F.004490EB@tcs.com>
	<AANLkTinah_CTHW3EXgm0OiqSddqbXxBJL4Gkvx8fsN20@mail.gmail.com>
	<OFA7654F78.BEC5F7D9-ON65257770.001B4696-65257770.001C7423@tcs.com>
	<AANLkTindnzSrgikdX0mGu=utAbkZUsQQCHwmQz_3Jvcr@mail.gmail.com>
	<OFDB77D32C.3DC7986D-ON65257770.002F50CD-65257770.00322B29@tcs.com>
	<AANLkTi=1yjipd_LB__fmHTE1y7+mzJAOuV4i=YX1rTCs@mail.gmail.com>
	<SNT141-w30B728EA06F1F5E510F74DF7AA0@phx.gbl>
From: Arun Kumar Boppudi <arunkumar.boppudi@gmail.com>
Date: Sat, 31 Jul 2010 00:29:32 +0530
Message-ID: <AANLkTin6VER79dcr8JHjpYSy-CTy5=_3vKRf=smrLR41@mail.gmail.com>
Subject: Re: Reading input stream (xml)
To: Struts Users Mailing List <user@struts.apache.org>
Content-Type: multipart/alternative; boundary=e0cb4e887865b7e44c048c9f7494

--e0cb4e887865b7e44c048c9f7494
Content-Type: text/plain; charset=ISO-8859-1

Thanks. But I am looking for a solution in Struts 1.3.

-- AB


On Fri, Jul 30, 2010 at 4:17 PM, adam pinder <apinder@hotmail.co.uk> wrote:

>
>
>
> your action could implement ServletRequestAware then it has access to the
> full request including posted content.
>
>
>
> adam
>
>
>
> > From: arunkumar.boppudi@gmail.com
> > Date: Fri, 30 Jul 2010 15:31:15 +0530
> > Subject: Re: Reading input stream (xml)
> > To: user@struts.apache.org
> >
> > Request to this controller comes from other applications, only in XML
> > format. So, I cannot expect multi-part.
> > -- AB
> >
> >
> > On Fri, Jul 30, 2010 at 2:38 PM, Rahul Mohan <rahul.mohan@tcs.com>
> wrote:
> >
> > > A variant of the first: change your encoding to multi-part and send
> > > 'data=your_xml_content'. Then struts will take care of getting the
> > > content, and also you don't have to worry about encoding the xml.
> > >
> > >
> > >
> > > From:
> > > Arun Kumar Boppudi <arunkumar.boppudi@gmail.com>
> > > To:
> > > Struts Users Mailing List <user@struts.apache.org>
> > > Date:
> > > 30-07-2010 13:48
> > > Subject:
> > > Re: Reading input stream (xml)
> > >
> > >
> > >
> > > Unfortunately, I have to use XML here. So, I cannot use the first
> > > suggestion.
> > >
> > > If I use request.getInputStream, subsequent request.getParameter calls
> > > will
> > > fail. Will it cause any problems in struts?
> > >
> > > I would like to give a try to the third one. But not all the action
> > > controllers gets XML in the request. So, I may have to list down the
> > > controllers which gets the XML content in the request.
> > >
> > > -- AB
> > >
> > >
> > > On Fri, Jul 30, 2010 at 10:41 AM, Rahul Mohan <rahul.mohan@tcs.com>
> wrote:
> > >
> > > > Think I understand your problem now. AFAIK Struts doesn't have any
> > > > available mechanism to handle these. I can suggest the following
> > > > solutions:
> > > > 1. Create your request body in the way Struts is expecting -
> name-value
> > > > pairs.
> > > >
> > > > 2. Extend struts by creating a custom request processor. ( See:
> > > > http://onjava.com/pub/a/onjava/2004/11/10/ExtendingStruts.html ).
> You
> > > will
> > > > have to identify the first possible hook and call getInputStream to
> > > > extract the info and pass it as a request parameter or invoke a
> custom
> > > > action since request.getInputStream cannot be called after the
> request
> > > is
> > > > parsed.
> > > >
> > > > 3. Put a custom servlet-filter in front of the struts controller to
> get
> > > > the request data and re-pass it as a request parameter to struts.
> > > >
> > > > I prefer the first approach which is the easiest and does no harm.
> > > >
> > > > - Rahul
> > > >
> > > >
> > > >
> > > > From:
> > > > Arun Kumar Boppudi <arunkumar.boppudi@gmail.com>
> > > > To:
> > > > Struts Users Mailing List <user@struts.apache.org>
> > > > Date:
> > > > 30-07-2010 09:49
> > > > Subject:
> > > > Re: Reading input stream (xml)
> > > >
> > > >
> > > >
> > > > There is no form and I am sending XML content to the action
> controller
> > > > using
> > > > Fiddler.
> > > >
> > > > And data sent is not in the format of query string. (not in the
> format:
> > > > paramname=*xml_content*). So, struts may not be mapping it to a
> property
> > > > in
> > > > the form bean. In this case, how can I get the posted XML contents?
> > > >
> > > >
> > > > -- AB
> > > >
> > > >
> > > > On Thu, Jul 29, 2010 at 5:59 PM, Rahul Mohan <rahul.mohan@tcs.com>
> > > wrote:
> > > >
> > > > > Data goes in request body when you are posting a form. Post
> requests
> > > are
> > > > > obviously handled by Struts. So it should work. ( Only you know
> that
> > > it
> > > > is
> > > > > XML, for Struts its just another String. ) Please see your log for
> any
> > > > > exceptions in setting the action form. Also try inspecting your
> > > request
> > > > > using firebug to see if it is being posted.
> > > > >
> > > > >
> > > > >
> > > > > From:
> > > > > Arun Kumar Boppudi <arunkumar.boppudi@gmail.com>
> > > > > To:
> > > > > Struts Users Mailing List <user@struts.apache.org>
> > > > > Date:
> > > > > 29-07-2010 14:58
> > > > > Subject:
> > > > > Re: Reading input stream (xml)
> > > > >
> > > > >
> > > > >
> > > > > I think we should use the query string format to use the string in
> > > > action
> > > > > form class format. But I am not sending it in the query string
> format.
> > > > And
> > > > > I
> > > > > am not using multipart encoding. Just sending the XML content in
> POST
> > > > > body.
> > > > >
> > > > > -- AB
> > > > >
> > > > >
> > > > > On Thu, Jul 29, 2010 at 2:38 PM, Rahul Mohan <rahul.mohan@tcs.com>
> > > > wrote:
> > > > >
> > > > > > Arun,
> > > > > >
> > > > > > Are you doing a POST with multi-part encoding? If so, a solution
> > > > > similar
> > > > > > to file upload would work for you. If not, then the String in
> > > > > action-form
> > > > > > approach that I posted earlier should work.
> > > > > >
> > > > > > - Rahul Mohan
> > > > > >
> > > > > >
> > > > > >
> > > > > > From:
> > > > > > Arun Kumar Boppudi <arunkumar.boppudi@gmail.com>
> > > > > > To:
> > > > > > Struts Users Mailing List <user@struts.apache.org>
> > > > > > Date:
> > > > > > 29-07-2010 13:34
> > > > > > Subject:
> > > > > > Re: Reading input stream (xml)
> > > > > >
> > > > > >
> > > > > >
> > > > > > Rahul,
> > > > > >
> > > > > > I am not sending XML content as part of the query string, only
> XML
> > > > > content
> > > > > > will be sent in the request body. As struts framework uses the
> > > > > > getParameter
> > > > > > to populate data into the form beans before calling the execute
> > > > method,
> > > > > we
> > > > > > cannot use the request.getInputStream.
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> http://archives.java.sun.com/cgi-bin/wa?A2=ind0106&L=jsp-interest&F=&S=&P=49196
> > >
> > > >
> > > > >
> > > > > >
> > > > > >
> > > > > > -- AB
> > > > > >
> > > > > >
> > > > > > On Thu, Jul 29, 2010 at 11:01 AM, Rahul Mohan <
> rahul.mohan@tcs.com>
> > > > > wrote:
> > > > > >
> > > > > > > Arun,
> > > > > > >
> > > > > > > You can keep a string property on action form and map it to the
> > > xml
> > > > > > field
> > > > > > > so that the xml content is available here on page submit. In
> the
> > > > > action
> > > > > > > class, then you will be able to get the string and parse it
> using
> > > > any
> > > > > > > available xml parser. I don't think Struts provides any
> shortcut
> > > for
> > > > > > this
> > > > > > > requirement.
> > > > > > >
> > > > > > > - Rahul Mohan
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > From:
> > > > > > > Arun Kumar Boppudi <arunkumar.boppudi@gmail.com>
> > > > > > > To:
> > > > > > > Struts Users Mailing List <user@struts.apache.org>
> > > > > > > Date:
> > > > > > > 29-07-2010 10:32
> > > > > > > Subject:
> > > > > > > Re: Reading input stream (xml)
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Actually, I am not uploading a file. I am creating XML from the
> > > data
> > > > > > > entered
> > > > > > > into the form and sending it to the action controller in the
> POST
> > > > > > request
> > > > > > > body. In the action controller, I would like to parse the XML.
> How
> > > > to
> > > > > do
> > > > > > > it
> > > > > > > in Struts 1.3?
> > > > > > >
> > > > > > > -- Arun Kumar Boppudi
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Jul 29, 2010 at 10:24 AM, Rahul Mohan
> > > <rahul.mohan@tcs.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Doesn't this link (
> > > > > > http://struts.apache.org/2.0.14/docs/file-upload.html
> > > > > > > )
> > > > > > > > help you?
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > From:
> > > > > > > > Arun Kumar Boppudi <arunkumar.boppudi@gmail.com>
> > > > > > > > To:
> > > > > > > > Struts Users Mailing List <user@struts.apache.org>
> > > > > > > > Date:
> > > > > > > > 28-07-2010 22:09
> > > > > > > > Subject:
> > > > > > > > Reading input stream (xml)
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > If we send XML content in the POST/PUT request to Struts
> action
> > > > > > > > controller,
> > > > > > > > how to read this content in the Action class?
> > > > > > > >
> > > > > > > > -- AB
> > > > > > > >
> > > > > > > >
> > > > > > > > =====-----=====-----=====
> > > > > > > > Notice: The information contained in this e-mail
> > > > > > > > message and/or attachments to it may contain
> > > > > > > > confidential or privileged information. If you are
> > > > > > > > not the intended recipient, any dissemination, use,
> > > > > > > > review, distribution, printing or copying of the
> > > > > > > > information contained in this e-mail message
> > > > > > > > and/or attachments to it are strictly prohibited. If
> > > > > > > > you have received this communication in error,
> > > > > > > > please notify us by reply e-mail or telephone and
> > > > > > > > immediately and permanently delete the message
> > > > > > > > and any attachments. Thank you
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > =====-----=====-----=====
> > > > > > > Notice: The information contained in this e-mail
> > > > > > > message and/or attachments to it may contain
> > > > > > > confidential or privileged information. If you are
> > > > > > > not the intended recipient, any dissemination, use,
> > > > > > > review, distribution, printing or copying of the
> > > > > > > information contained in this e-mail message
> > > > > > > and/or attachments to it are strictly prohibited. If
> > > > > > > you have received this communication in error,
> > > > > > > please notify us by reply e-mail or telephone and
> > > > > > > immediately and permanently delete the message
> > > > > > > and any attachments. Thank you
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > =====-----=====-----=====
> > > > > > Notice: The information contained in this e-mail
> > > > > > message and/or attachments to it may contain
> > > > > > confidential or privileged information. If you are
> > > > > > not the intended recipient, any dissemination, use,
> > > > > > review, distribution, printing or copying of the
> > > > > > information contained in this e-mail message
> > > > > > and/or attachments to it are strictly prohibited. If
> > > > > > you have received this communication in error,
> > > > > > please notify us by reply e-mail or telephone and
> > > > > > immediately and permanently delete the message
> > > > > > and any attachments. Thank you
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > =====-----=====-----=====
> > > > > Notice: The information contained in this e-mail
> > > > > message and/or attachments to it may contain
> > > > > confidential or privileged information. If you are
> > > > > not the intended recipient, any dissemination, use,
> > > > > review, distribution, printing or copying of the
> > > > > information contained in this e-mail message
> > > > > and/or attachments to it are strictly prohibited. If
> > > > > you have received this communication in error,
> > > > > please notify us by reply e-mail or telephone and
> > > > > immediately and permanently delete the message
> > > > > and any attachments. Thank you
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > =====-----=====-----=====
> > > > Notice: The information contained in this e-mail
> > > > message and/or attachments to it may contain
> > > > confidential or privileged information. If you are
> > > > not the intended recipient, any dissemination, use,
> > > > review, distribution, printing or copying of the
> > > > information contained in this e-mail message
> > > > and/or attachments to it are strictly prohibited. If
> > > > you have received this communication in error,
> > > > please notify us by reply e-mail or telephone and
> > > > immediately and permanently delete the message
> > > > and any attachments. Thank you
> > > >
> > > >
> > > >
> > >
> > >
> > > =====-----=====-----=====
> > > Notice: The information contained in this e-mail
> > > message and/or attachments to it may contain
> > > confidential or privileged information. If you are
> > > not the intended recipient, any dissemination, use,
> > > review, distribution, printing or copying of the
> > > information contained in this e-mail message
> > > and/or attachments to it are strictly prohibited. If
> > > you have received this communication in error,
> > > please notify us by reply e-mail or telephone and
> > > immediately and permanently delete the message
> > > and any attachments. Thank you
> > >
> > >
> > >
>
>

--e0cb4e887865b7e44c048c9f7494--