Alan Gutierrez wrote:
> Ultimately, I created an Interceptor. During ActionBeanResolution it
> takes the account slug from the path...
>
> http://domain.com/stripes/PublicationEdit.action?publication=5
I just wonder why you need to have a different path for each customer.
Can't you know the custom
Hi,
I want to move some JSP logic to a separate layout.
My problem is when displaying the field value without using the
stripes:text tag:
${value}
If I enter value="customer.des
Roland,
The ActionBean is available to you as a regular request attribute. In
a plain EL reference, you can use "actionBean" to access it:
${actionBean.customer.description}
On Jun 13, 2008, at 8:59 AM, Roland Bali wrote:
On another note Nic, do you plan on updating your Stripes security stuff to be
compatible with 1.5? I really like your stuff but it seems having a custom
filter is not the new 1.5 way of doing it, but instead using an interceptor etc
and the new Extension.Packages.
Just wondering because I have
Hi Chris,
Thank for your reply, but this doesn't solve my problem. The parameters
to my layout is the name of the field like,
The layout need to work for any text field I send as a parameter, not
just customer.description. Is this possible?
/Roland
Chris Herron wrote:
> Roland,
>
> The Acti
When our users go to lunch in the middle of entering data on a
multi-page "form" (implemented as a Stripes wizard) and try to finish
when they return we get a Stripes runtime exception:
Stripes attmpted and failed to decrypt the non-null value in the
'fields present' field. Because this for
In Stripes 1.4 we used encryption keys that were specific to the
user's session. Starting with Stripes 1.5 we use (by default) a
single key for the application which will be able to decrypt values
across sessions (and if configured so, across restarts).
So the easiest solution is probably
I am using encrypted annotation on a property that is a list of objects. I
applied it on the getter method as shown in the indexed properties
documentation:
@ValidateNestedProperties({
@Validate(field="id", encrypted=true)
})
public List getModelTypes() {
return this.modelTypes;
}
The
Wouldn't actionBean[value] work?
On Fri, Jun 13, 2008 at 6:03 PM, Roland Bali <[EMAIL PROTECTED]> wrote:
> Hi Chris,
>
> Thank for your reply, but this doesn't solve my problem. The parameters
> to my layout is the name of the field like, name="mylayout.jsp" value="customer.description" readonly
