>Very good point. Some folks don't even use the suffix, rather they
>configure that requests to anything under a directory called "do" be
>treated as a Struts request. (And again, that directory name is
>configurable).

We generally us ".html" as the URL suffix for all our struts apps.

With that said, who knows how many struts apps are out there.

Part of the beauty of Struts is the flexibility it provides for mapping your
controller.  It's just a Servlet after all. :)

Regards,


Josh Holtzman

 

AMERICAN DATA COMPANY

Developing and Supporting your Online Applications

 

[EMAIL PROTECTED]

Voice: (310) 470-1257

Fax:    (310) 362-8454

 

Sun Microsystems iForce Partner


-----Original Message-----
From: Chappell, Simon P [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 14, 2004 9:54 AM
To: Struts Users Mailing List
Subject: RE: examples of struts??



>-----Original Message-----
>From: Van [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 14, 2004 11:33 AM
>To: Struts Users Mailing List
>Subject: Re: examples of struts??
>
>
>On Wed, 14 Jul 2004 12:16:51 -0400, Lykins Don H Contr AFSAC/ITS
><[EMAIL PROTECTED]> wrote:
>> wow....cool..
>> i see you work for lands end...doesn't their customer site use it?
>> ((landsend.com))
>> 
>> how do you know your list of sites actually use struts (by the .do)?
>
>Part of this is the honor system. Simon has an entry for the VeriSign
>Digital Brand Management System. That link points to the company PR
>site for the service which itself doesn't use Struts. However, the
>actual service which can only be seen by customers that signup for the
>service and get an account does indeed have the entire front-end
>webapp written in Struts. I know this because I work at VeriSign and
>one of my first jobs there was to port the existing version of this
>service from an outdated proprietary approach to use Struts. I asked
>Simon to list the VeriSign entry and I believe most of the other
>entries showed up in the same manner.

Yes. Well explained. It's all done on trust. Although the .do suffix is a
very good hint. :-)

<snip>

>Finally, the extension for your Struts actions is configurable. In our
>case, the extension is usually representative of the service. For a
>managed security services customer console, we used the extension
>".mss".

Very good point. Some folks don't even use the suffix, rather they configure
that requests to anything under a directory called "do" be treated as a
Struts request. (And again, that directory name is configurable).

>-- 
>- Mike "Van" Riper
> [EMAIL PROTECTED]

Simon

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to