hi people
i try your method but its not working when i put the tag local
i put my jsp :
<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
pageEncoding="ISO-8859-1"%>
<%@ taglib prefix="s" uri="/struts-tags" %>
<%@ taglib prefix="sx" uri="/struts-dojo-tags" %>
hi strut people :)
i have a problem with strutsmenu and I18N with struts2
i read somthing about this problem
see: the old comment:
Besides specifying the bundle attribute on the menu:useDisplayer tag, is
there any other way to translate the text from menu-config.xml with
struts2? If I specify
i have a problem with I8N with struts menu and Struts 2
u read about this proble and i use tis code on my jsp
but its not working
the error is
RAVE: Erreur lors de la configuration de la classe d'écoute de l'application
(application listener) net.sf.navigator.menu.MenuContextListen
hi
when put locale"WW_TRANS_I18N_LOCALE" its not working anymore :/
maybe i have to put default attibut like FR?
--
View this message in context:
http://struts.1045723.n5.nabble.com/Struts-Menu-Struts2-tp3497566p4560377.html
Sent from the Struts - User mailing list archive at Nabble.com.
---
On Wed, Jul 6, 2011 at 5:47 PM, Jeff Black wrote:
>> Whereas I am confused why the signature is not public T
>>convertFromString(Map context, String[] values, Class toClass). Is this in
>>scope of the effort someone described recently to Java5-ify the code base?
>
> What is the best way to organ
Forwarded on behalf of the Travel Assistance Committee:
Hi All,
Just a friendly (and final) reminder that applications for financial
help to attend ApacheCon NA 2011 in Vancouver close this coming Friday
8th July (2200 BST : UTC+1)
Financial assistance is available for Travel (planes, trains, w
On Thursday, July 7, 2011, Eric Lentz wrote:
>> IMO coupling field labels to semantic constructs is a Bad Idea
> This particular app. is poised to become
> international, so perhaps a different approach has come of age?
Unless you're keen on having the same "type" of value stored under an
arbitra
> IMO coupling field labels to semantic constructs is a Bad Idea
You make good points as usual. This particular app. is poised to become
international, so perhaps a different approach has come of age? I'm forced
in that direction anyway. As with most companies I've worked at (I'm
contracting he
On Jul 7, 2011 9:38 AM, "Eric Lentz" wrote:
> That seems fragile for my use case
Your use case is intrinsically fragile. What happens when the field name has
a single or double quote? If it doesn't matter, then you're /already/ down
the slippery slope of special-casing.
I'd file this as an inter
W dniu 7 lipca 2011 16:37 użytkownik Eric Lentz
napisał:
> Do you mean acceptedParamNames? (
> http://struts.apache.org/2.2.1/struts2-core/apidocs/com/opensymphony/xwork2/interceptor/ParametersInterceptor.html
> )
Yes, just put modified version from source code.
Regards
--
Łukasz
+ 48 606 323
>> Um, I don't know. What do you mean? I thought that's what I did when I
>> specified name='foo["Interior/Exterior"]'
>
>
>..
>
>
>
>Regards
>--
>Łukasz
Do you mean acceptedParamNames? (
http://struts.apache.org/2.2.1/struts2-core/apidocs/com/opensymphony/xwork2/interceptor/ParametersIn
2011/7/7 Eric Lentz :
> Um, I don't know. What do you mean? I thought that's what I did when I
> specified name='foo["Interior/Exterior"]'
..
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Warszawa JUG conference - Confitura http://confitura.pl/
> Oh, can't you just set the parameter then?
>
> Dave
Um, I don't know. What do you mean? I thought that's what I did when I
specified name='foo["Interior/Exterior"]'
Just define your own value of paramNames as a parameter for the
interceptor, but be aware that this can create a potential security
whole in your app.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Warszawa JUG conference - Confitura http://confitura.pl/
2011/7/7 Eric Lentz :
>>>
Oh, can't you just set the parameter then?
Dave
On Thu, Jul 7, 2011 at 8:35 AM, Eric Lentz wrote:
>>> Do we call this a bug?
>>
>>Probably, but I don't if it's an S2 or OGNL issue.
>>
>>Dave
>
> com.opensymphony.xwork2.interceptor.ParametersInterceptor
>
> private String acceptedParamNames = "[a
>> Do we call this a bug?
>
>Probably, but I don't if it's an S2 or OGNL issue.
>
>Dave
Per my previous post, it appears to be coming from the
com.opensymphony.xwork2 package. This is supported through Apache now? Do
we post this to S2's JIRA?
>> Do we call this a bug?
>
>Probably, but I don't if it's an S2 or OGNL issue.
>
>Dave
com.opensymphony.xwork2.interceptor.ParametersInterceptor
private String acceptedParamNames = "[a-zA-Z0-9\\.\\]\\[\\(\\)_'\\s]+";
private Pattern acceptedPattern = Pattern.compile(acceptedParamNames);
...
On Thursday, July 7, 2011, Eric Lentz wrote:
> Do we call this a bug?
Probably, but I don't if it's an S2 or OGNL issue.
Dave
-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h.
> My first guess would be that OGNL is trying to evaluate it, although
> since it's a string, not sure that makes any sense.
>
> I don't know how your DB is laid out or how what sounds like ad-hoc
> structures are being created, but is a text ID really the only thing
> you have available?
>
> Dav
My first guess would be that OGNL is trying to evaluate it, although
since it's a string, not sure that makes any sense.
I don't know how your DB is laid out or how what sounds like ad-hoc
structures are being created, but is a text ID really the only thing
you have available?
Dave
On Thursday,
I'm using Struts 2.2.1.
I have a use case whereby form fields are generated dynamically and some
of them are select lists. Since it is a database driven list of fields,
the labels presented for the user are also used as keys for the map that
the form posts back to. Using alternate keys is not d
21 matches
Mail list logo
