RE: [OS-webwork] default-interceptor-ref usage

2003-09-15 Thread Jason Carreira
No. We decided to make this an "either you use the default or not" thing because Interceptors are a list and additive, unlike results, which are a map and you can just override defaults. So if you define any interceptors for the action, the default interceptors are not applied. > -Original Mes

[OS-webwork] default-interceptor-ref usage

2003-09-15 Thread Francisco Hernandez
i've got a default package (that defines the default interceptor stack) and that is extended by a Foo package, in my Foo package all actions use my default stack that was defined in the default package, but when I specify another stack to use in my Foo package actions it just uses the ones I sp

RE: [OS-webwork] Documentation

2003-09-15 Thread Jason Carreira
Matt Dowell, a coworker of mine, wrote up a quickstart guide: http://wiki.opensymphony.com/space/WebWork2+QuickStart+Guide > -Original Message- > From: Jason Carreira > Sent: Sunday, September 14, 2003 11:34 PM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] Documentation > > > I updat

Re: [OS-webwork] Request parameters not being set

2003-09-15 Thread Chris Widhelm
Title: Message I can pass the parameters in param tags, as long as I hard code the values.  I have to hard code the values because I can't get the parameters off of the request with the property tag.     - Original Message - From: Jason Carreira To: [EMAIL PROTECTED]

RE: [OS-webwork] Request parameters not being set

2003-09-15 Thread Jason Carreira
Title: Message I think the problem is the "id" property on the ActionTag itself. From the ActionTag:   private Map createExtraContext() {    Map extraContext = Ognl.createDefaultContext(this);       // Leave the ValueStack out -- We're not processing inside the tag    //  

Re: [OS-webwork] Request parameters not being set

2003-09-15 Thread Chris Widhelm
Title: Message Yep, it has both.  When I call the action directly it works fine (http://localhost:8080/secure/modules/admin/users/UserDetails.action?id=143).   Here is the class: >>===<< package com.contego.arx.actions.user;   import com.contego.a

RE: [OS-webwork] Request parameters not being set

2003-09-15 Thread Jason Carreira
Title: Message Does your Action have an "id" property? Does it have a getter and a setter? Sometimes the Java introspection stuff doesn't find a property with only a setter or only a getter... -Original Message-From: Chris Widhelm [mailto:[EMAIL PROTECTED] Sent: Monday, Sept

Re: [OS-webwork] Request parameters not being set

2003-09-15 Thread Chris Widhelm
Title: Message In that case I already have the defaultStack set as the default interceptor which includes the ParameterInterceptor.   I have included all of the configuration as well as the jsp page that I am trying to access and the request.   Do you see anything that looks weird?   Still to

RE: [OS-webwork] Request parameters not being set

2003-09-15 Thread Jason Carreira
Title: Message This is just for defining the interceptors. You need to specify which interceptors are applied to your actions.   If you look at http://wiki.opensymphony.com/space/Xwork+Configuration   You can see that Action elements have interceptor-refs inside:   "Foo" class="com.o

RE: [OS-webwork] Login interceptor?

2003-09-15 Thread Jason Carreira
Title: Message If you give a package a namespace, such as namespace="foo", then the Action will only be available from   /myapp/foo/bar.action   If you don't specify a namespace, it will be available from any path:   /myapp/*/bar.action   See http://wiki.opensymphony.com/space/Xwork+Configur

RE: [OS-webwork] Login interceptor?

2003-09-15 Thread Thompson, Kris
Title: Message Can you please elaborate more on this?  Still I need to know if the user has authenticated, are you talking about authorization, aka roles?   Kris Thompson www.frameworks-boulder.org -Original Message-From: Jason Carreira [mailto:[EMAIL PROTECTED]Sent: Monday, Se

Re: [OS-webwork] Request parameters not being set

2003-09-15 Thread Chris Widhelm
Title: Message Is there any documentation on the available interceptors and how to configure them?   Here is my interceptor configuration section:                                           This doesn't seem to work.  *shrug*   The interceptor documentation that I have found in the xw

RE: [OS-webwork] Request parameters not being set

2003-09-15 Thread Jason Carreira
Title: Message Did you apply the ParameterInterceptor to the Action? This is what sets the parameters into the Action. -Original Message-From: Chris Widhelm [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2003 10:59 AMTo: [EMAIL PROTECTED]Subject: [OS-webwork] R

RE: [OS-webwork] Login interceptor?

2003-09-15 Thread Jason Carreira
Title: Message If you use namespaces in WW2 you can pin Actions to only certain paths, so you can use J2EE declarative security... -Original Message-From: Thompson, Kris [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2003 10:53 AMTo: [EMAIL PROTECTED]Subject: [OS

Re: [OS-webwork] Login interceptor?

2003-09-15 Thread Matthew E . Porter
Check out Atlassian Seraph project. I believe it does this but at the filter layer. http://opensource.atlassian.com Cheers, matthew On Monday, September 15, 2003, at 09:53 AM, Thompson, Kris wrote: Has anyone created an login/authorization interceptor?  Basically it would check to see that t

[OS-webwork] Request parameters not being set

2003-09-15 Thread Chris Widhelm
Title: Login interceptor? I am in the process of switching to WW2 from WW1 and it appears that the parameters on a request are no longer being automatically set for an action.  Is this the case?   How do I access the parameters on a request?   Thanks,   Chris

[OS-webwork] Login interceptor?

2003-09-15 Thread Thompson, Kris
Title: Login interceptor? Has anyone created an login/authorization interceptor?  Basically it would check to see that the user has authenticated for a given action. Thanks Kris Thompson

[OS-webwork] Re: [JIRA-OS] Closed: (WW-292) ActionTag/ServletDispatcherResult - more comprehensive solution

2003-09-15 Thread Michał Mosiewicz
> Message: > >The following issue has been closed. > >Resolver: Patrick Lightbody >Date: Sun, 14 Sep 2003 7:14 PM > > Most of this was already done, but I made id not required now too. Thanks! However note that the most important part of this patch was not resolved. I mean - dispat