2010/5/3 stlecho stle...@gmail.com:
It seems that parts of the Axis2 documentation are not displayed correctly
(see underneath screenshot). All I can see is a blue rectangular, but not
the content. Could this be solved ?
Sure, please provide the full path to document with the problem!
Anyone know what the current status of this plugin is. Back in December 2009,
Musachy posted that it needed fixing to work with Spring WebFlow 2.0. Does
anyone know if this has been done, before I start trying to use it?
Regards
--
View this message in context:
Hi I am using s:select and populating it with enum .
s:select list=categoryList name=complaintType /s:select
the enum is like
public enum EComplaintType {
CLUB_HOUSE(0), ELECTRIC(1);
}
In the jsp the select is formed as
select name=categorySelect id=categorySelect
option
I have also seen that there is some function called ordinal() in enum. can
anyone suggest how can i use it in s:select tag
On Tue, May 4, 2010 at 12:01 PM, Upasana Sharma sharma...@gmail.com wrote:
Hi I am using s:select and populating it with enum .
s:select list=categoryList
listValue=%{getText('myCategory.'+toString())}
this way i can change the select display value from .properties file
in .properties i have to use
myCategory.ELECTRIC= Electric
On Tue, May 4, 2010 at 12:24 PM, Upasana Sharma sharma...@gmail.com wrote:
I have also seen that there is some
The majority of the pages in the Guides Tutorials pages have this
problem:
- http://struts.apache.org/2.1.8.1/docs/getting-started.html
http://struts.apache.org/2.1.8.1/docs/getting-started.html
- http://struts.apache.org/2.1.8.1/docs/struts-2-blank-archetype.html
Upasana Sharma wrote:
listValue=%{getText('myCategory.'+toString())}
this way i can change the select display value from .properties file
in .properties i have to use
myCategory.ELECTRIC= Electric
Neat. I'm trying to do the same thing with the s:radio tag.
s:radio
I could probably restructure my data to make it fit that model, but that
is not the ideal solution. My data is structured more like a hash,
where the keys are essentially arbitrary and unpredictable. Is there
something similar that would work with that kind of structure?
Mitch
Martin
On 5/3/10 2:54 AM, RogerV wrote:
s:form
s:checkboxlist name=selectedroles list=%{availableroles}
value=%{preselectedroles}/
s:submit type=button label=Add/
/s:form
So what html does this generate for the client to render/submit?
If you set the form action to be GET it's even easier to see
On 5/3/10 10:08 AM, Mitch Claborn wrote:
Bump. Any other ideas?
Yes. ParameterAware allows you to handle parameters without the setters
and getters you think are necessary. Look there again.
-Dale
Mitch Claborn wrote:
That works for setting parameter names, but not so well when the
Maybe using OGNL along with #this or #attr . Haven't checked that out
but it should work some of these ways:
http://struts.apache.org/2.0.14/docs/ognl-basics.html
http://www.opensymphony.com/ognl/html/LanguageGuide/varref.html
Em 04-05-2010 14:03, RogerV escreveu:
Upasana Sharma wrote:
Have your Action method getAuthorizedOptions() return something like a
HashtableString,MyBean, where MyBean is your inner thingy with methods
setWhateverProperty() and getWhateverProperty(). Then your iterator
incantation as below:
s:iterator value=authorizedOptions id=o
would deliver
just to be safe i would add the id attribute id=Person %{key} to the example
use of %{key} to uniquely identify each created textfield DOM element would work
i did'nt mention there is a status counter for iterator to use as an indexer
e.g. s:iterator... status=stat
//assuming there is a 1:1
DNewfield wrote:
On 5/3/10 2:54 AM, RogerV wrote:
s:form
s:checkboxlist name=selectedroles list=%{availableroles}
value=%{preselectedroles}/
s:submit type=button label=Add/
/s:form
So what html does this generate for the client to render/submit?
The rendering is a bit odd, which
On 5/4/10 10:08 AM, RogerV wrote:
s:checkboxlist name=selectedroles list=%{availableroles}
value=%{preselectedroles}/
input type=checkbox name={} value=ROLE_ADMIN id={}-1/
input type=checkbox name={} value=ROLE_USER id={}-2
checked=checked/
input type=checkbox name={} value=ROLE_UBER id={}-3/
Hi,
I am new in struts.
It seems that the textarea of dojo can not be configured. E.g. in the following
trivial jsp the editor part of textarea takes all of the browser and the
textarea itself is not constrained to 3 by 3.(also there is no border). Why is
this? Additionally looking in google i
16 matches
Mail list logo