Re: Does the /do/* will be supported with modules

2002-11-20 Thread V. Cekvenich
The other things with the prefix, is that it maps nicely with CMA 
security for the modules.
Ex: Only users in the Admin role can go to /admin/*.
etc.

.V


OT: pet peve: Since the struts example show login via code (the wrong 
way) Every Struts book, save Teds and FastTrack, shows the wrong way to 
login, not the right declarative way.


Ted Husted wrote:
Only if someone can figure out how to make it work with the 
current approach to organizng the modules =:0)

It's not that we don't ~want~ prefix matching to work with 
modules, it's that we don't know ~how~. 

I'm sure that a future release may use a more sophisticated 
approach to routing the requests, but that might require more 
surgery that we can justify in a .# release. 

If you using either prefix or suffix matching properly, you should 
be able to switch between them by just editing the struts-config. 
So, technically, it should not make any difference which you use 
until you're ready to use modules.

-Ted.

11/19/2002 7:48:44 AM, Emmanuel Boudrant [EMAIL PROTECTED] wrote:


Hi,

Actually the /do/* path mapped pattern doesn't work fine with 

modules, does this pattern will work


with final release

...And, is it a good advice to use /do/* instead of *.do

Thanx,
-emmanuel


___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

--
To unsubscribe, e-mail:   mailto:struts-dev-


[EMAIL PROTECTED]


For additional commands, e-mail: mailto:struts-dev-


[EMAIL PROTECTED]








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




Re: Does the /do/* will be supported with modules

2002-11-20 Thread Antoni Reus
Hi, question below

A Dimecres 20 Novembre 2002 00:37, Craig R. McClanahan va escriure:
 On Tue, 19 Nov 2002, Emmanuel Boudrant wrote:
  Date: Tue, 19 Nov 2002 13:48:44 +0100 (CET)
  From: Emmanuel Boudrant [EMAIL PROTECTED]
  Reply-To: Struts Developers List [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Subject: Does the /do/* will be supported with modules
 
  Hi,
 
  Actually the /do/* path mapped pattern doesn't work fine with modules,
  does this pattern will work
 
  with final release

 At the moment, it appears that the restriction that extension mapping must
 be used for application modules will remain in the final release.  Two
 things would be necessary to change this:

 * Someone would have to come up with a strategy that resovles
   the problem of how to define path-mapped URLs that still
   include the module prefix in some reasonable fashion that can
   be parsed.


Do you mean, for example if the servlet mapping is /do/* and an action path  
is  /actionPath, the path /do/actionPath should be translated to 
/do/modulePath/actionPath ?


 * Someone would have to implement this strategy.

  ...And, is it a good advice to use /do/* instead of *.do

 For a non-module scenario, this is pretty much a cosmetics issue --
 whichever style creates URLs that you like better is the one you should
 use.

  Thanx,
  -emmanuel

 Craig

Salut!

-- Antoni Reus

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




Re: Does the /do/* will be supported with modules

2002-11-20 Thread tim_smithers

Hi,
 I have a similar problem, in that I would like to use
path mappings, and modules (which are not supported in 1.1).

Is there a clear explanation of the issue with implementing it?
From Craig's comment below,

 * Someone would have to come up with a strategy that resovles
   the problem of how to define path-mapped URLs that still
   include the module prefix in some reasonable fashion that can
   be parsed.

I understand that there is a problem, but not the *actual* part
which makes it difficult (most likely due my limited understanding
of the insides of struts).

Does anyone have a clear description of the problem, and issues
which make including this difficult? At least then maybe some of
the list readers could think about possible solutions.

Regards,
- Tim






Antoni Reus [EMAIL PROTECTED] on 21/11/2002 06:17:44

Please respond to Struts Developers List [EMAIL PROTECTED]

To:   Struts Developers List [EMAIL PROTECTED]
cc:
Subject:  Re: Does the /do/* will be supported with modules


Hi, question below

A Dimecres 20 Novembre 2002 00:37, Craig R. McClanahan va escriure:
 On Tue, 19 Nov 2002, Emmanuel Boudrant wrote:
  Date: Tue, 19 Nov 2002 13:48:44 +0100 (CET)
  From: Emmanuel Boudrant [EMAIL PROTECTED]
  Reply-To: Struts Developers List [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Subject: Does the /do/* will be supported with modules
 
  Hi,
 
  Actually the /do/* path mapped pattern doesn't work fine with modules,
  does this pattern will work
 
  with final release

 At the moment, it appears that the restriction that extension mapping
must
 be used for application modules will remain in the final release.  Two
 things would be necessary to change this:

 * Someone would have to come up with a strategy that resovles
   the problem of how to define path-mapped URLs that still
   include the module prefix in some reasonable fashion that can
   be parsed.


Do you mean, for example if the servlet mapping is /do/* and an action
path
is  /actionPath, the path /do/actionPath should be translated to
/do/modulePath/actionPath ?


 * Someone would have to implement this strategy.

  ...And, is it a good advice to use /do/* instead of *.do

 For a non-module scenario, this is pretty much a cosmetics issue --
 whichever style creates URLs that you like better is the one you should
 use.

  Thanx,
  -emmanuel

 Craig

Salut!

-- Antoni Reus

--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]

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









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




Re: Does the /do/* will be supported with modules

2002-11-20 Thread Ted Husted
11/20/2002 7:35:50 AM, V. Cekvenich [EMAIL PROTECTED] 
wrote:
The other things with the prefix, is that it maps nicely with CMA 
security for the modules.
Ex: Only users in the Admin role can go to /admin/*.
etc.

.V

Actually, prefix mapping works just fine with container-
basedsecurity. You just include the prefix with the constraint:

  web-resource-nameAdministrative/web-resource-name
!-- The URLs to protect --
url-pattern/do/admin/*/url-pattern
  /web-resource-collection

It's also possible that this strategy could also be applied to 
modules. Instead of declaring your modules to be payables/, we 
might be able to accept do/payables/ where /do/* is mapped to 
the ActionServlet. 

The gotcha would be an assumption that there are no slashes in the 
module name. But since there is already a flag for prefix 
matching, that's something we could watch for. 

Another approach might be to use the existing prefix matching flag 
to automatically prepend the prefix. We couldn't do that at first 
because it would mean the pages would have to be stored under /do/ 
too, which wouldn't work. But, we've since added a setting to 
munge the path used to find the pages (so they can be placed under 
/WEBINF/$MODULE for example). We should be able to use that 
feature to relocate the pages so that they are not directly under 
/do/, and get the system to look under

/pages/do/payable

or 

/WEBINF/do/payable

instead.

Unforunately, everything I have open right now is 1.0, and so I 
can't run any quick tests. 

-Ted.



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




Does the /do/* will be supported with modules

2002-11-19 Thread Emmanuel Boudrant
Hi,

Actually the /do/* path mapped pattern doesn't work fine with modules, does this 
pattern will work

with final release

...And, is it a good advice to use /do/* instead of *.do

Thanx,
-emmanuel


___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

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




Re: Does the /do/* will be supported with modules

2002-11-19 Thread Craig R. McClanahan


On Tue, 19 Nov 2002, Emmanuel Boudrant wrote:

 Date: Tue, 19 Nov 2002 13:48:44 +0100 (CET)
 From: Emmanuel Boudrant [EMAIL PROTECTED]
 Reply-To: Struts Developers List [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Does the /do/* will be supported with modules

 Hi,

 Actually the /do/* path mapped pattern doesn't work fine with modules,
 does this pattern will work

 with final release


At the moment, it appears that the restriction that extension mapping must
be used for application modules will remain in the final release.  Two
things would be necessary to change this:

* Someone would have to come up with a strategy that resovles
  the problem of how to define path-mapped URLs that still
  include the module prefix in some reasonable fashion that can
  be parsed.

* Someone would have to implement this strategy.

 ...And, is it a good advice to use /do/* instead of *.do


For a non-module scenario, this is pretty much a cosmetics issue --
whichever style creates URLs that you like better is the one you should
use.

 Thanx,
 -emmanuel


Craig


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




Re: Does the /do/* will be supported with modules

2002-11-19 Thread Emmanuel Boudrant


Thanx Craig ... and CONGRATULATION Ted for joining the ASF.

Thanx for your support.

-emmanuel


 --- Craig R. McClanahan [EMAIL PROTECTED] a écrit :  
 
 On Tue, 19 Nov 2002, Emmanuel Boudrant wrote:
 
  Date: Tue, 19 Nov 2002 13:48:44 +0100 (CET)
  From: Emmanuel Boudrant [EMAIL PROTECTED]
  Reply-To: Struts Developers List [EMAIL PROTECTED]
  To: [EMAIL PROTECTED]
  Subject: Does the /do/* will be supported with modules
 
  Hi,
 
  Actually the /do/* path mapped pattern doesn't work fine with modules,
  does this pattern will work
 
  with final release
 
 
 At the moment, it appears that the restriction that extension mapping must
 be used for application modules will remain in the final release.  Two
 things would be necessary to change this:
 
 * Someone would have to come up with a strategy that resovles
   the problem of how to define path-mapped URLs that still
   include the module prefix in some reasonable fashion that can
   be parsed.
 
 * Someone would have to implement this strategy.
 
  ...And, is it a good advice to use /do/* instead of *.do
 
 
 For a non-module scenario, this is pretty much a cosmetics issue --
 whichever style creates URLs that you like better is the one you should
 use.
 
  Thanx,
  -emmanuel
 
 
 Craig
 
 
 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]
  

___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

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