I don't believe the conversion framework currently looks up the class
hierarchy, though it should. Please open a bug in XWork and we'll get to
it for 1.0.1.
Patrick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Mark Woon
Sent: Monday, March 01,
Mark,
Back to your original problem, type conversion on a ModelDriven action
may not work, as I never officially tested it. The code for how
XWorkConverter gets the class and property name candidate for type
conversion is very funky and doesn't work 100% of the time --
ModelDriven may be one of
Ive added everyone to the subscribers list on [EMAIL PROTECTED]. In the
next few days Id like to start phasing out the SF mailing lists and make
the final migration to java.net. By the end of the week I will unsubscribe
everyone but myself from the old SF mailing list.
If anyone objects
and Javas reflection api. Which made me think about using different
actionLoaders. Maybe something like
action name=editProdukt
actionloader=com.eds.webwork.classloader.ScriptClassLoader
classname=myScript.gy
...
/action
This isn't the first time people have
There are two things you need to do:
1) Make sure that component interceptor is in your stack. You need to
do this using WebWork or just XWork no matter what.
2) If you aren't using WebWork, take a look at the LifecycleListener
classes in WebWork to get an idea how the three scopes are
Hmm... that's very odd -- it should work. I recommend you muck around
with select.vm and see what you can cause to print out. Try using things
like $top for the key and see what you get. Also, you might want to step
through the SelectTag code to see if anything tricky is going on there.
Let me
Using a Map wont work, primarily
because the Ognl language doesnt support the syntax you are looking for.
If we can ever get a hold of Drew Davidson (Ognl owner) we might be able to get
support for this some day J
In the meantime, Id recommend you
use a List of Row objects where Row
Or rather than transient -- private static final, no?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jason Carreira
Sent: Saturday, February 14, 2004 10:49 AM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork] tomcat version 5
It's the log4j
Simon -- this is pretty cool! It's a perfect candidate for the WebWork
extras project. Right now we have two projects on java.net:
webwork-optional and webwork-extras. I'm going to trash one of them and
then you should request developer access to the other so that you have a
place to store this
Have you tried escape=true in the tag attribute?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Donnerstag, Juergen
Sent: Wednesday, February 18, 2004 2:31 PM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] special charaters in textfield
Hi,
I'm
Sounds like we need to beef up what HttpHeaderResult is doing. That or
you need to write a custom result for yourself.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Samuel Mota
Sent: Wednesday, February 18, 2004 6:17 AM
To: [EMAIL PROTECTED]
Alex,
This kind of behavior is pretty advanced, but it should be supported by
the type conversion. Suppose your action is FooAction, just add the
following to FooAction-conversion.properties:
Collection_rows = java.util.HashMap
Then in your HTML, you could name the elements:
rows[0]{'foo'}
Paul, I'm not sure if it does -- if not, we'll need to get this in when
the next 2.0.x release comes out. Open a bug.
I believe there was a request for style and class as well, and we'll
likely get those in during that time as well.
Patrick
-Original Message-
From: [EMAIL PROTECTED]
It might be that your Map
#{ 'SIM' : '0' , 'NÃO' : '1' }
Is going from String-Character, rather than String-Integer. Try:
#{ 'SIM' : 0 , 'NÃO' : 1 }
Patrick
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Samuel Mota
Sent: Tuesday, February 03,
I'm pleased to announce the release of WebWork 2.0. You can download it
at:
https://webwork.dev.java.net/files/documents/693/2886/webwork-2.0.zip
XWork 1.0 has also been released and is available at:
https://xwork.dev.java.net/files/documents/709/2885/xwork-1.0.zip
Thank you to everyone who
Rich,
That looks like that should work. What do
you end up with? Just albumManagerID=?
-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Rich
Sent: Saturday,
January 31, 2004 3:53 PM
To:
[EMAIL PROTECTED]
Subject: [OS-webwork] Appending a
Stephen,
This should work just fine (Ognl will convert from String[] to String if it
needs to) I cant imagine why this isnt working. Are you
sure you have xwork.xml correctly configured? The key is to make sure that you
are including webwork-default.xml and that your packages extend
I believe that is just a warning -- but to avoid it, just implement
NoParameters
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Donnerstag, Juergen
Sent: Tuesday, February 03, 2004 8:22 PM
To: '[EMAIL PROTECTED]'
Subject: AW: [OS-webwork] RE: Script
Thomas,
In LoginAction-validation.xml, you have the field names set as Username
and Password. They should be username and password.
Thank you for your extremely well thought out and detailed email!
Pat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Just a note -- I hardcoded the interval to 2 seconds in VelocityManager
-- this will get pulled out to a configuration element shortly.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Hans Prueller
Sent: Sunday, February 01, 2004 5:59 AM
To: [EMAIL
Try this:
That will work, although listKey can just be key and listValue can
just be value.
Pat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jonas Eriksson
Sent: Tuesday, January 20, 2004 1:18 PM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] how
For more advanced layout patterns of widgets, you may need to write your
own template library (based off of the 'xhtml' one). If you can provide
a complete library we'll be sure to include it in to WebWork
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Actually, in WebWork 2.0 the default behavior has changed.
In 1.4 ww:if text=foo checks that getFoo() returns non-null
In 2.0 ww:if text=foo checks that getFoo() returns a value that can
be interpreted as true (true, a string true, 1, etc)
Pat
-Original Message-
From: [EMAIL PROTECTED]
Hey Greg,
Generally we try to avoid promoting access to those things directly
(setters and ActionContext.getSession() should suffice 99% of the time),
but you can get them via ServletActionContext.getXxx().
-Pat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
quicker out the door.
Pat
From: Francisco Hernandez [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] XWork 1.0 Release Imminent
Date: Wed, 14 Jan 2004 14:53:42 -0800
Patrick Lightbody wrote:
Im merely waiting on the script to slurp the XWork docs
Just a status update:
XW has zero open bugs and will be released tonight baring any huge
documentation concerns.
WW has only a handful of bugs left and will be release this week.
Pat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Fred Lamuette
Sent:
Hmm... let me think about this after having a look at the code. That
would be good to allow forms and form widgets to know how to communicate
with each other. Currently, they are pretty dumb.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Mathias Bogaert
Im merely waiting on the script to slurp the XWork docs
from the Wiki so that I can include them in to the final release. All bugs have
been closed, the last feature was built, and everything looks good for a 1.0
release either tonight or tomorrow. Thanks to everyone for your help! The
Pfeifer
Sent: Thursday, January 08, 2004
11:11 PM
To:
'[EMAIL PROTECTED]'
Subject: RE: [OS-webwork] Xwork/WebWork2
under extreme load
Yeah, I do use Beta 2. In fact: It is a checkout from
just before christmas eve.
-Original Message-
From: Patrick Lightbody [mailto:[EMAIL PROTECTED
times around 45ms
Pat
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Patrick Lightbody
Sent: Thursday, January 08, 2004
11:40 PM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork]
Xwork/WebWork2 under extreme load
OK, I have an update
Well, about a year ago when we had the initial XW meetings, it was
decided to keep the TL for now. Maybe post-2.0 we'll find ways to slowly
migrate away from it. I agree though, ThreadLocals suck ass.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Scott
these automatically...
If you have:
List items;
List getItems();
void setItems(List aList);
Item getItem(int index);
void setItem(int index, Item item);
It should be able to figure out that the type is Item... Maybe :-)
-Original Message-
From: Patrick Lightbody [mailto:[EMAIL
: Thursday, January 08, 2004 2:21 PM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] Xwork/WebWork2 under extreme load
- Original Message -
From: Patrick Lightbody [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 08, 2004 5:55 PM
Subject: RE: [OS-webwork] Xwork/WebWork2 under
Dag, this is great work -- could you please open a bug for this?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Dag Liodden
Sent: Thursday, January 08, 2004 2:37 PM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] Xwork/WebWork2 under extreme load
I
, January 08, 2004 2:51 PM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork] Xwork/WebWork2 under extreme load
-Original Message-
Behalf Of Patrick Lightbody
Sent: Thursday, January 08, 2004 5:46 PM
I was thinking that a huge performance boost could come from
remembering the index
, 2004 4:48 PM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] how to populate a list of objects from a form
Patrick Lightbody wrote:
Yes, but usually these types of grid input forms have N number of rows,
so pre-populating won't work.
I'd like to take a quick vote on the two choices:
1) The domain
Mark,
What version of WW are you using? Beta 2 or the latest from CVS? I
haven't tested file upload in a long time, so it's possible a bug has
been introduced. Can you tell what type of object
ServletActionContext.getRequest() is returning?
-Pat
-Original Message-
From: [EMAIL PROTECTED]
Mathias,
I haven't seen anything like this. Are you using the latest from CVS (or
at least beta 2)? I did a lot of stress testing while doing performance
tuning for WW and I didn't hit anything like this. However, that doesn't
mean it isn't a problem.
-Pat
-Original Message-
From: [EMAIL
We tried the event handler before and it did a lot more stuff that we
didn't want to happen, so I don't think that's necessarily the best
choice.
Richard's idea of having a format() method works, but is sub-optimal
since it requires extra work from you that is not part of the type
conversion
Title: Message
Your example code should work. Just a
reminder: all the WebWork 1.x SortIterator classes have been ported and might be helpful
depending on what you are trying to do. However, for the most part they are
obsolete due to the new features in the OGNL EL.
-Original
This problem seems to me like less of a security problem but more of an
east of access problem. What I mean by that is even if that action
were only allowed in POST form, I could still exploit it. Sure, it would
be a little harder since I couldn't just type in a URL, but anyone can
telnet to the
I was talking to Ara about this very thing just a bit ago. Sounds like
some sort of regression (we'll need a unit test for this). Please open a
bug and I'll get on it.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Fred Lamuette
Sent: Tuesday, January
central I guess we
could do some hand-waving before this (well cover the details of
configuration later, but for now, this is what your configuration should look
like), but either way you have forward references.
Any ideas how to make it less dry?
-Original Message-
From: Patrick
*cough*
*cough* please ignore *cough* *cough*
Ill need to rename my aliases to be
a bit less similar :P
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Patrick Lightbody
Sent: Monday, December 22, 2003
9:04 AM
To: WebWork
Subject: [OS
This is probably your best bet.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Martin Angeletti
Sent: Thursday, December 18, 2003 12:52 PM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] sorting collections
Hi, ive been playing with ww2 for a few weeks now
Richard, this is great to hear! Is there anything we can do in WebWork2
to make the FreeMarker support better?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Fred Lamuette
Sent: Thursday, December 18, 2003 8:51 AM
To: [EMAIL PROTECTED]
Subject:
I think no method calls is the best bet. I'll open a bug report on this
and we'll get it done for 2.0 final.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Tim Dwelle
Sent: Wednesday, December 17, 2003 8:19 AM
To: [EMAIL PROTECTED]
Subject: Re:
Maybe after we get Fredrik's template patches all in place we'll look at
it. I still don't see it as a critical 2.0 feature.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Fredrik Lindgren
Sent: Wednesday, December 17, 2003 10:22 PM
To: [EMAIL PROTECTED]
You can do:
ww:property value=#session.blah/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
remigijus
Sent: Wednesday, December 17, 2003 3:47 PM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] How to access session component from JSP
I'm using ww2.
Title: Message
Please make sure a jira issue exists for
this just in case. Id hate to forget to do this before releasing 2.0
final
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jason Carreira
Sent: Monday, December 15, 2003
7:55 AM
To:
[EMAIL
for volunteers to
give
me some feedback on this as soon as I figure out the translator part...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Patrick Lightbody
Sent: Tuesday, December 16, 2003 7:26 PM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork
Ouch -- great catch! Please file a jira issue and I think we'll need to
update the CompoundRootAccessor to only execute methods after the action
has been processed and we're in view mode. I'll probably put in a few
other checks, like disallowing some of the super critical method calls
like
Les,
Did you get anywhere with this?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, December 11, 2003 8:32 AM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] A little HELP pleasea very odd error
Let me preface this by
So what is the outcome of this discussion? :P
Also, I think I'm going to add a helper object to the AC like so:
#p.foo - causes action.getFoo() to be called, and if the return value
is null (or default) then it will call request.getParameter(foo). That
would solve Mike's 'abc' example if all the
someone see any inconsistency here, or I'm only one so confused here?
- Original Message -
From: Patrick
Lightbody
To: [EMAIL PROTECTED]
Sent: Tuesday,
December 09, 2003 5:57 PM
Subject: RE:
[OS-webwork] WebWorks without velocity how to
Remis,
In 1.x
Unfortunately, this is one of the problems with the
use-JSP-tags-in-velocity deal: in order to _really_ get it to work,
you essentially have to write half a JSP container. Since supporting any
arbitrary tag isn't the goal of WebWork (it's a nice side effect, but
it's not a high priority at all), I
Thats very strange. Are you at all
using the ww:action/ tag in your JSP as well?
-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of remigijus
Sent: Wednesday, December 10, 2003
2:17 AM
To:
[EMAIL PROTECTED]
Subject: [OS-webwork] Problems
with
There are a few options (Drew and Jason are both correct). Another
option is to use the so-called HTTP 204 trick:
Using the HttpHeaderResult (included in WebWork, but not yet in
webwork-default.xml), you can respond with a 204 code which tells the
browser to submit the form but then not change
David,
In WebWork 1.x and 2.0, you can provide a get/set method for a String[]
and then name each textfield the same name.
Alternatively, in 2.0, you can name your textfields foo[i].name where
i goes from 0 to n. This will work if you use the OgnlList, which will
be included in to WebWork code
Your best bet (as explained in my book ;) is to keep your jars in
WEB-INF/lib and classes in WEB-INF/classes, OR use Resin and specify
alternative directories for those two locations (such as lib/runtime and
build/java). The real gain is for you to use a Hotswap capable IDE, such
as Eclipse,
Remis,
In 1.x, yes. In 2.0, no.
-Pat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of remigijus
Sent: Thursday, December 04, 2003
8:23 AM
To:
[EMAIL PROTECTED]
Subject: [OS-webwork] WebWorks
without velocity how to
Hi
There
The webwork-extensions project exists on java.net. Currently Matt Ho is
the owner of it and I'm sure he'll grant developer requests ASAP. The
whole point is to have a low entry barrier... so give it a shot :)
-Pat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
I'm not sure what @status means... do you mean #status?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Eric Mckenna
Sent: Tuesday, December 09, 2003 12:54 PM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] Can I concatenate text in the name attribute?
of it to instantiate a
new one, even in the same session.
Anoop
On Dec 8, 2003, at 12:35 AM, Patrick Lightbody wrote:
Have your component implement Disposable.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Anoop Ranganath
Sent: Thursday
Have your component implement Disposable.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Anoop Ranganath
Sent: Thursday, December 04, 2003 2:27 PM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] releasing a component
How do I go about telling the IoC
I'd like to see this as well -- I wouldn't be surprised if this came in
to 2.0 final ;)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jason Carreira
Sent: Thursday, December 04, 2003 8:30 AM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork] ResourceBundle
I think this is a good suggestion. Right now, we have:
* XWorkConverter defaults down to DefaultTypeConverter
* if specified, XWorkConverter will attempt to use XWorkBasicConverter
* XWorkBasicConverter, if it can't convert, defaults down to
DefaultTypeConverter
There is some redundancy here.
that is not implicit for
subpackages and actions within that package? Isn't any reference I make
at this level implicit for everything underneath and therefore
default?
On Nov 30, 2003, at 11:00 PM, Patrick Lightbody wrote:
Hi Robert :)
I think the core reason for this is because you define multiple
To answer your question: not currently. No one has written support for
XDoclet, but I would expect that to happen one of these days :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Robert Nicholson
Sent: Sunday, November 30, 2003 4:42 PM
To: [EMAIL
Title: Message
Fred,
I think that I am seeing eye-to-eye with
you on your vision. This is good stuff and I hope it doesnt get lost in
the near future. If you can, can you open a jira issue with these various
aspects and/or continue to keep tabs on progress towards this goal?
-Pat
In the distribution (beta 2 for example) you can just run java -jar
xwork-1.0-editor.jar and everything should be fine.
If you're using cvs, do ant dist and then cd to build/dist and run the
java command.
-Pat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
I've had situations where resolving the name dynamically has been VERY
important (think of a generic configuration editor -- say, something
that edits a .properties file).
As for inconsistencies, those should be addressed. Could you compile a
list of the ones you've found and open a bug?
-Pat
Sounds like a winner -- open a jira request and we'll get on it
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Fred Lamuette
Sent: Monday, November 24, 2003 9:47 AM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] Why ActionTag is dangerous...
I've created a
It sounds like you need to set executeResult=true
for the action tag.
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thompson, Christopher C (Kris)
Sent: Monday, November 24, 2003
7:37 AM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] ActionTag
I've done two actions in the past, but it does feel a bit yucky...
Just to expand on this request -- another reason it could be useful is
when you only want to validate a field if another expression evaluates
to true (such as a checkbox being set or something).
-Pat
-Original Message-
param tags in the ww:textfield tag?
-Original Message-
From: Patrick Lightbody [mailto:[EMAIL PROTECTED]
Sent: Monday, November 24, 2003 10:26 PM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork] description field for ui controls
Even better:
ww:textfield label='label' name
OK -- let's just end this discussion. It's not going to change for the
2.0 release :P
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jason Carreira
Sent: Sunday, November 23, 2003 2:31 PM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork] OGNL madness -
to show the proper messages, but the OGNL type conversion
errors
are being thrown at some level outside of this, most likely in something
like the parameter interceptor.
Ideas?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Patrick Lightbody
Sent: Friday
There have been some requests for a style
attribute, but I doubt that will come before 2.0 is released.
In the meantime, you can just write your
own templates and putting them in /templates/xhtml in your webapp (you can use
the base templates to get started that are included in the
setting, you do it
with the triple-quote (for backwards compatibility) and another way, you do it
with velocity-style ${} syntax.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Patrick Lightbody
Sent: Friday, November 21, 2003
5:16 PM
To:
[EMAIL PROTECTED]
Subject: RE: [OS
Well, this is to be compatible with 1.x
so I think the 1.x guys should get involved in the discussion at this point
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Robert Douglass
Sent: Friday, November 21, 2003
1:32 PM
To:
[EMAIL PROTECTED]
Actually, the underlying template (text.vm for TextFieldTag) calls
$webwork.htmlEncode() on all the values printed out. Maybe you have
other templates in your web app that are overriding those?
Also, note that the escaping has caused quite a bit of a problem for
some people -- but I think I can
If you're trying to display lists of data, I don't think action
_chaining_ is the best choice. The possible choices are:
1) provide a static method that returns the value, and then use the
expression @[EMAIL PROTECTED]() in your ww:select tag
OR
2) use the ww:action/ or ww:bean/ tags, and then
We could probably do this -- though you can too :)
ww:textfield label='Foo' name='foo'
ww:param name=style value='width:160px'/
/ww:textfield
Then just modify place text.vm in /template/xhtml and add a section to
do:
#if ($parameters.style) style=$parameters.style #end
-Pat
-Original
I answer Matthew's question on IRC today, but for the list:
From the HttpServletRequest, call
getAttribute(DefaultComponentManager) and then do:
dcm.init(something)
where something is an object that implements some Aware interfaces.
-Pat
-Original Message-
From: [EMAIL PROTECTED]
Title: Webwork2: Select Tag (Newbie)
Hi
Patrick, welcome to WebWork!
Listkey and listvalue are used as so:
option value=[listkey][listvalue]/option
The values you should place in your ww:select
tag are ones that assume that the context is one of the objects in the list. So
if
The problem is that type conversion is failing when you from - long,
so we're reporting the error and then returning to our modified Ognl new
Long(0) -- AFTER reporting the error. Should we assume that this kind of
type conversion is not an error? How do we differentiate from this type
conversion
Fred,
Good ideas, we'll get to them pronto! Sorry for the messup -- we were
trying to keep 1.4 compatibility (1.4 uses JSPs templates that use
ww:property, which escapes by default).
-Pat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Fred Lamuette
I'm pleased to announce that the long-delayed WebWork 2.0 beta 2 is
finally out. This release can be considered a release candidate for a
final release that we hope will take place in the next week. I'm
currently uploading the zip file and I realize that the distro doesn't
include the source for
What are the exceptions? The URLTag recently was modified to act just
like 1.3.
-Pat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Daniel Pfeifer
Sent: Tuesday, November 18, 2003 5:38 AM
To: '[EMAIL PROTECTED]'
Subject: [OS-webwork] Problems with
as I have seen your code improvment, I believe it
will
appreciably increase the speed.
Pat, what about the real problem that Ognl 2.6.4 should fix ? Do you
wait
for the next release of Ognl ?
Richard.
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] la part de
Patrick
I made the URLTag exactly like the 1.3/1.4
release. In fact, in 1.4 the page attribute does exist, but it is deprecated.
Can someone explain the difference to me?
Im a bit unfamiliar with all the URLTag stuff.
VUI is the VoiceXML stuff from the 1.x
line.
-Pat
-Original
I apologize for all the changes. The reason for the changes was to make
2.0 more compatible with 1.3 and to take advantage of all the things
they learned and not toss it out the window. We don't plan on any major
changes at this point.
Again, my deepest apologies -- we should be through all the
Actually, ww:property doesn't not to toString(). It calls
findValue(expr, String.class) and then let's Ognl try to do some
type-conversion. You are more than welcome to add a type converter that
does what you need.
Or you can use i18n :)
-Pat
-Original Message-
From: [EMAIL PROTECTED]
Well, it is kind of amusing Mathias is saying he'll switch to 1.3, given
that these changes make 2.0 have the exact same interface/tags/etc as
1.x :P
-Pat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Thompson, Christopher C (Kris)
Sent: Tuesday,
Title: Message
Id really like to see this added to
our validation framework, but its doubtful itll make it for the
2.0 release.
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jason Carreira
Sent: Thursday, November 13, 2003
3:03 PM
To:
[EMAIL
One issue that comes up with this is how to deal with escaping. This is
in fact the last hurdle for the release tonight.
With JSP tags, ww:property was used, and so people could write UI
components that did escaping when they needed. Doing $property doesn't
give you that option.
My thought it
Richard,
Thanks, I wasn't expecting a null argument. I'll need to fix that.
This change was an optimization that got us from 4X to 2X speed
difference in the monthlist tests. Anyway, please open a bug and I'll
get to it promptly.
-Pat
-Original Message-
From: [EMAIL PROTECTED]
We're planning on release beta 2 (which will be the RC) tonight. Thanks
to everyone for all their help!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Joseph Ottinger
Sent: Monday, November 17, 2003 6:00 AM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] WW2
Matthew,
If this is still missing (my guess is we just need to update the xwork
jar) please open a bug report.
-Pat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jason Carreira
Sent: Friday, November 14, 2003 7:57 AM
To: [EMAIL PROTECTED]
Subject: RE:
1 - 100 of 364 matches
Mail list logo
