Enterprise Client Community

Hi Björn,

the restricted config parameter works fine in WebStart (jnlp) and as parameter in "start java...." batch file.
But it does not work in applet (workplace.html),
and neither in jsp:

<t:clientconfig id="g_3" language="#{d.workplace.session.language}" restrictedconfig="true" />

By the way I would prefer if the language fields were invisible instead of disabled.
It might awaken desires in the user: "Why can't I use it?"

Frauke

Applet: yes, you are right, sorry. Is corrected now. Please request if you immediately need it.

Visible/invisible: Hm. Hmmm. Hmmmmmmmmm. There are also good reasons to see them... (definite place to go to see all localization aspects).
We do not want to immediately remove them now, to be honest. - Anyway, it's not a Prio A item (yet...), so let's postpone...

Björn

Hi Björn,

Ok, this is not an urgent matter.

Maybe some more detailed parameters would be more usefull
(nobody knows, what the "restrictions" are) , like "hideLanguage", "disableLanguage",.... something like that.

What about setting the parameter in the .jsp? (see example in my previous post)

Frauke

...yes, JSP-CLIENTCONFIG is a reasonable place. And maybe even simpler: if one parameter is set from server side, then the client does not allow to change it anymore. I am a bit concerned that there will be too many parameters.

What do you think? This is something we can do quite fast, because this issue is then closed in a proper way.

Björn

Hi Björn,

thats a great idea (could have been mine

.

I don't mind if there are many parameters, as long as its transparent and clear. And in fact you only have 6 parameters by now.

Frauke

P.S. Look at that: he made two smilies, but I added only one!

...is part of 20080609...
Björn