struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank W. Zammetti" <>
Subject RE: Struts 1.3 & custom controller
Date Tue, 03 May 2005 15:51:55 GMT
Yep, that's exactly what you should be able to do.  And if you decide to
go off and do it, do feel free to feed it back to me for release on the
strusws SF project :)

Here's some links to get you started:

Your really looking at Commons Chain, which forms the basis of 1.3.  As I
said, I haven't toyed with 1.3 much, so in terms of how this really
applies to 1.3 in detail I don't know of any link to help there.  Maybe
one of the struts team members can direct you...

Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies

On Tue, May 3, 2005 10:24 am, Marco Mistroni said:
> Hello Frank,
> 	If  Str1.3 RP is implemented as set of commands, then shouldn't
> I be able to extend It to add my own commands (such as one that does the
> trick
> In your request processor)..
> I think it should be possible.... at least I would like to support J2ME
> clients (via strutsws), HTML clients and WML clients for my
> application..
> So I could define a RP which contains set of commands for handling
> request depending on the user agent..
> I need just some docs for Struts 1.3 Request Processor.......
> Any good links (other than sourcecode)?
> Thanx in advance and regards
> 	Marco
> -----Original Message-----
> From: Frank W. Zammetti []
> Sent: 03 May 2005 14:40
> To: Marco Mistroni
> Cc: 'Struts Users Mailing List'
> Subject: Re: Struts 1.3 & custom controller
> Hi Marco,
> You are correct, the custom controller is at the heart of strutsws.
> I hesitate to answer about 1.3 because I've only looked at it very
> briefly.  But, I'll try and answer and if someone more knowledgable sees
> me flub something, please correct me...
> Remember that 1.3 uses the CoR pattern to break down the request
> processor
> into a chain of functions.  It is designed to be functionally equivalent
> to the "current" request processor, but defined as a chain of Commands.
> I seem to recall a thread at one point that said you still could in fact
> use a custom monolithic processor... if that's not true than the bottom
> line is simply that no, strutsws as it exists today will not be usable
> with 1.3.
> Let's assume however that I am remembering correctly and you CAN do
> that... you'd still be inserting the 1.1 RP into the mix, which I'd bet
> isn't what you really want to do.  It is also worth noting that I never
> did a strutsws version for the Tiles processor, so Tiles and strutsws
> don't mix at this point.  This hasn't been a big problem for most people
> apparently (I guess they just set up a separate module for the web
> services, I don't really know)...
> ...which does kind of raise an interesting question... assuming you can
> use a non-chain RP in 1.3, it might be possible to just use the 1.1 RP
> in
> a module for your web services.  If it's a module expressly for strutsws
> functions, which RP you use might not matter as much (I could be wrong
> though... there could have been some changes between 1.1 and 1.3 that
> makes it not work, I frankly don't know).  I've never tied such a setup,
> so I have no idea if it'll actually work.
> Lastly, I do have the intention of updating strutsws specifically for
> 1.3
> (it should be a piece of cake to insert a command or two into the chain
> to
> perform the necessary functions), but I won't do that until 1.3 is a GA
> release.  I actualy thought I wrote it against 1.2.4, I didn't realize
> it
> was 1.1, so the first chance I get I will update it for 1.2.4 at
> least...
> I only intend to support GA releases for strutsws as well as ajaxtags by
> the way.
> Hope that helps!
> --
> Frank W. Zammetti
> Founder and Chief Software Architect
> Omnytex Technologies
> On Tue, May 3, 2005 4:26 am, Marco Mistroni said:
>> Hello all,
>> 	I have downloaded strutsws by Frank Zammetti, which
>> Enables struts app to be exposed as a webservice..
>> It uses a custom controller(pls frank correct me if I m wrong) that
>> Detects if request is an XML request...customizing then output so that
>> it
>> Will be an XML response that matches form data.
>> Application works fine with Struts 1.1.. I have just written a
>> <controller>
>> Tag in struts-config and a  plugin used by strutsws.
>> I found problems however with Struts 1.3, and I was wondering if, in
>> Struts 1.3, was enough to define a  <controller> tag in
>> struts-config.xml
>> Or something else was needed..
>> Thanx in advance and regards
>> 	Marco
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message