I know we are talking about another framework but I can get honest replies
here compared to the GWT user group.
I have been reading about GWT being a single page programming where
refreshes are not appropriate and reading more like here
Hi,
I have developped a stateful session bean where access to methods are
restricted :
@SecurityDomain(myDomainBlabla)
@RolesAllowed({xxx, yyy})
@Stateful
public class BlablaBean implements BlablaRemote {
@RolesAllowed({xxx})
public void doSomething(User user) {
Here is the answer that I was provided used:
1. You can use the ${somethingFromTheValueStack} notation like so:
onclick=onjavaScriptMethod('${value}');
I tried this but missed the ' marks because it's been so long since I
did any JavaScript. I haven't tried this trick in an actual embedded
Hi,
Now I want to build XWork on another machine, this time with a direct
connection to the Internet (no proxy or firewall settings.)
---
Test set: TestSuite
On Fri, Dec 18, 2009 at 6:37 AM, Jim Collings jlistn...@gmail.com wrote:
Here is the answer that I was provided used:
1. You can use the ${somethingFromTheValueStack} notation like so:
onclick=onjavaScriptMethod('${value}');
I tried this but missed the ' marks because it's been so long
Hi,
what exactly does the value-attribute of the select tag require? Is it one
element of the list provided to the list-argument? Or is it the value which
eventually makes the value-attribute of the html-rendered select tag?
I have something like the following and I do not find a way to work
I believe that the value attribute is not used in this tag.
2009/12/18 Philipp Leusmann philipp.leusm...@rwth-aachen.de:
Hi,
what exactly does the value-attribute of the select tag require? Is it one
element of the list provided to the list-argument? Or is it the value which
eventually
The documentation says it is:
http://struts.apache.org/2.1.8.1/docs/select.html
But the examples are not really helpful.
Philipp
Am 18.12.2009 um 16:43 schrieb Gabriel Belingueres:
I believe that the value attribute is not used in this tag.
2009/12/18 Philipp Leusmann
I would try
@s.select name=bla list=list listKey=id listValue=str value=%{
object.id} /
-Brian
On Fri, Dec 18, 2009 at 9:30 AM, Philipp Leusmann
philipp.leusm...@rwth-aachen.de wrote:
Hi,
what exactly does the value-attribute of the select tag require? Is it one
element of the list
I do not use the value attribute in my s:select tags they work fine.
I do always use the headerKey headerValue attributes though.
Incidentally, the preselected (user-selected) key value is taken (stored)
using the name attribute so in your example your SelectAction should define
bla and
Thanks Bill, this works fine.
I am still wondering what the value-attribute is good for, then.
Philipp
Am 18.12.2009 um 17:48 schrieb Bill Bohnenberger:
I do not use the value attribute in my s:select tags they work fine.
I do always use the headerKey headerValue attributes though.
That's a bit strange, you can check with Bamboo that everything is ok
http://opensource.bamboo.atlassian.com/browse/XWORK
Regards
--
Lukasz
http://www.lenart.org.pl/
-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
I checked out it from https://svn.opensymphony.com/svn/xwork/trunk
I deleted everything and checkout'd it again and still the same test fail.
2009/12/18 Lukasz Lenart lukasz.len...@googlemail.com:
That's a bit strange, you can check with Bamboo that everything is ok
I have programmed in GWT in past.
The advantage over Struts 2 is GWT's component model. It allows to reuse
code and leverage your favorite safe refactoring tools (say Eclipse). JSP
sucks on refactoring.
The main GWT disadvantage is Java-to-JavaScript compilation. It has no
incremental
2009/12/18 Gabriel Belingueres belingue...@gmail.com:
I checked out it from https://svn.opensymphony.com/svn/xwork/trunk
I deleted everything and checkout'd it again and still the same test fail.
I did the same and found no problems ;-) Try to run maven with -U -up
My environment:
Apache Maven
15 matches
Mail list logo