Hani Suleiman wrote:
WebWork 1.4 has been released, appropriate press blurbage will be
showing up on your regular news channels in the next day or so I
expect. You can grab it from
https://webwork.dev.java.net/files/documents/693/1790/webwork-1.4.zip
Any feedback/testing would be most
hmm having looked at text.vm template its used for displaying a input
type=text tag.. and what happened to textfield tag too?
Patrick Lightbody wrote:
Haha, examples. Good one :P
Actually, the examples for 1.3 should work, since i18n hasn't change in
2.0. Actually, if you know a bit about
why create another property tag instead of just adding an attribute to
handle escaping (which i thought it had..)?
same thing for the param tag, couldnt an attribute be added to eval or not?
Patrick Lightbody wrote:
What we need to solve all this is:
* two #param directives (one which
Cheers mate.
I've just attached the SpringExternalReferenceResolver implmentation and
tests to the Jira Issue.
http://jira.opensymphony.com/secure/ViewIssue.jspa?key=XW-122
Ross
Patrick Lightbody wrote:
This is good stuff -- not sure about a 1.0 release though. We'll try to
get a point
On Mon, Nov 17, 2003 at 08:35:48PM -0500, Hani Suleiman wrote:
All,
WebWork 1.4 has been released, appropriate press blurbage will be
showing up on your regular news channels in the next day or so I
expect. You can grab it from
Hmm, you right! Why have i done this change...Anyways, tx now it works
again.
The validation xml file is now named, DemoAction-demoStep1-validation.xml.
/Mathias.
-Original Message-
From: Jason Carreira [mailto:[EMAIL PROTECTED]
Sent: den 17 november 2003 17:31
To: [EMAIL PROTECTED]
How come the page attribute of the URL tag has been
removed? It is a little annoying to have to tripple quote static values
(and hard to spot when you've missed one). The tld still allows a page
attribute.
Also, what is the com.opensymphony.veiws.jsp.vui
package about?
John.
I dont think two #param directives are a good idea.
What about a default behaviour defined in the webwork.properties ? With an
attribute in param tag to override the default, it would be nice.
Cheers.
Richard HALLIER
Chef de projet
[EMAIL PROTECTED]
01.40.12.41.52
www.uniclick.org
UNICLICK
Here is the different point of view. I personnaly think the push/pop actions
are NOT a hack.
Either you have a WW2 approach or a Velocity one. I think we are in the
first one, that makes all the difference, the stack is the main way to
access data.
If you need to pass reference objects without
Fred Lamuette wrote:
I dont think two #param directives are a good idea.
What about a default behaviour defined in the webwork.properties ? With an
attribute in param tag to override the default, it would be nice.
This is now done in CVS. The param supports an optional eval attribute.
If eval
Title: Pre-validation Processing Question
Hi gang,
I have an action that will either submit a form's contents, if it passes validation, or dispatch the form for completion if it doesn't pass validation. Basically, it's my way of being lazy so I don't have to write one action to render a
Title: Pre-validation Processing Question
I forgot to mention, I'm using the XML based ActionName-validation.xml
mechanism this time around vs. rolling my own validation code in my model's
validate() methods since I'm working with static forms this
time.
From:
[EMAIL PROTECTED]
what if in your example you needed 2 objects to be avaiable in your
Component?
would a ww:set be needed?
Fred Lamuette wrote:
Here is the different point of view. I personnaly think the push/pop actions
are NOT a hack.
Either you have a WW2 approach or a Velocity one. I think we are in the
I've opted to move this to the webwork extensions rather than have it
part of the webwork core. Although the VelocityServlet will be
deprecated, that won't be til Velocity 1.5!
One of the features that's extremely appealing about the velocity tool
project is the ability to easily add your own
you can use a chain to populate that list or maybe lazily load the list
in your getter (i think chain would work better..)
One common use of Action chaining is to provide lookup lists (like for
a dropdown list of states, etc). Since these Actions get put on the
ValueStack, these properties
Francisco,
Thanks for the tip, I'll give it a shot!
-Peter
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Francisco Hernandez
Sent: Tuesday, November 18, 2003 2:26 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] Pre-validation
I totally agree about putting it in webwork extensions!
Jonas
Matt Ho wrote:
I've opted to move this to the webwork extensions rather than have it
part of the webwork core. Although the VelocityServlet will be
deprecated, that won't be til Velocity 1.5!
One of the features that's extremely
what if in your example you needed 2 objects to be avaiable in your
Component?
double push
would a ww:set be needed?
???
Richard HALLIER
Chef de projet
[EMAIL PROTECTED]
01.40.12.41.52
www.uniclick.org
UNICLICK
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] la part
Matt Ho wrote:
I've opted to move this to the webwork extensions rather than have it
part of the webwork core. Although the VelocityServlet will be
deprecated, that won't be til Velocity 1.5!
One of the features that's extremely appealing about the velocity tool
project is the ability to
Is this then to the point of actually being usable? I have exactly this
requirement and i'd like to use this. Or, is this going to be part of the
WW2 next release?
Eric
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Jonas Eriksson
Sent: Tuesday,
hehe I know how you feel, im in the process of upgrading to a newer
version of ww2 and running into a bunch of problems, but its mainly lots
of small tedious changes, like having to add single quotes tags and
such, oh well.
BOGAERT Mathias wrote:
Hi,
Just to let you guys know that I *again* have
--- Paul Knepper [EMAIL PROTECTED] wrote:
I'm using jsp pages with ww:property tags to
output data.
How do I format dates and numbers? I would like to
specify dates as /mm/dd. And I'd like to format
numbers regarding number of digits for precision
etc...
ww:property would do
ok, i created this FAQ, hopefully you guys can help me out and fill it
in whenever you guys ask a question and get it answered or just put
something in it whenever..
http://wiki.opensymphony.com/space/Webwork2+FAQ
---
This SF. Net email is
There seem to be some problems with the Tags in the latest CVS checkout.
Specifically IncludeTag and UrlTag cause exceptions when used.
Is that a known problem?
/Daniel
---
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast,
I agree, and having just refactored these bits in ww1 I think that
adding all this velocity config stuff to webwork is duplication and
unnecessary. The jsp equivalent for example would be to suddenly allow
for the ability to define various scoped objects in the webwork config.
Use a
I have downloaded and integrated this code though and the tests run
perfectly (after creating my my own ServletContextAware interface and
removing refrences to the confluence packages)
I really like the work that you have done. Though I think some more
work is required to be able to integrate
Richard,
I've fixed this. The down side of all this is that if you have null as
an arg to a method call, the optimizations I made to get monthlist from
4X to 2X will be lost. In the future I could probably get those
optimizations back, but for now this works and is really simple.
-Pat
The same for me. I think personnaly that too much stuff included in this
endless beta 2 prevents it from being stable (yes i know it's a beta). But
it is the choice of the project team, not mine. And I can only support the
project with my patches, bugs submissions, remarks, but I do it with
I get right now the latest cvs snapshot.
Thank you, Pat.
Richard.
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] la part de
Patrick Lightbody
Envoye : mardi 18 novembre 2003 07:41
A : [EMAIL PROTECTED]
Objet : RE: [OS-webwork] Latest xwork cvs snapshot
Richard,
I just discovered a problem with my
ExceptionHandlerInterceptor due to the design of the DefaultActionInvocation
class. I have made some changes to this class which fix the problem and
wouldlike to run them past everybody.
The ExceptionHandlerInterceptor catches any
exceptions that occur
+1
(I've written the same exception handler interceptor)
-Message d'origine-De:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]De la part de
John PattersonEnvoyé: mardi 18 novembre 2003
16:21À: WebworkObjet: [OS-webwork]
ExceptionHandlerIntercepter
I just discovered a
The other option is to have an Action which creates that list and use
the webwork:action tag to execute it and then use the list from the
other tags... (see the examples or wiki(?) for examples)
-Original Message-
From: Peter White [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18,
I'll take a look after the 2.0 beta2 release
-Original Message-
From: Ross Mason [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 12:01 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] [OS-xwork] Spring IoC integration
I've updated the Issue, and attached the patch
Sorry about that... I assume Pat changed the HttpServletRequestAware to
ServletRequestAware to be more like WW1.x and make it a little easier to
upgrade. The reason things have changed so much was to make backward
compatibility easier. All major API changes should be over now. The
tags, unless
Title: Message
How
does this handle the issue of content having been written out by the first
result? Would you end up with part of the first page, then the error
page?
-Original Message-From: John Patterson
[mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18,
2003 10:21
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
Title: Message
I
think you can do the trick with a stand-in stream, a response wrapper like the
one from Sitemesh is ok.
Richard.
-Message d'origine-De:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]De la part de
Jason CarreiraEnvoy: mardi 18 novembre 2003
16:59:
[EMAIL
Title: Message
If the request has not been committed then the
ServletDispatcher is clever enough to doa dispatcher.forward() instead of
a dispatcher.include(). Therefore any uncommitted content in the buffer is
cleared. However, if the response is already committed
thenthere is no wayto
Title: Message
I'll
take a look at the changes tonight... sounds like it's minor with no changes
visible to the user.
-Original Message-From: John Patterson
[mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18,
2003 11:30 AMTo:
[EMAIL PROTECTED]Subject: Re:
any chance of getting this into webwork-ext?
John Patterson wrote:
I just discovered a problem with my ExceptionHandlerInterceptor due to
the design of the DefaultActionInvocation class. I have made some
changes to this class which fix the problem and would like to run them
past everybody.
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]
ok I was confused because I saw a text.vm and not a textfield.vm but the
textfield tag is still there.
Jason Carreira wrote:
ww:text is for finding localized text messages... It's not a UI
component
-Original Message-
From: Francisco Hernandez [mailto:[EMAIL PROTECTED]
Sent: Tuesday,
On a minor note, should the template be named textfield instead of
text?
--- Jason Carreira [EMAIL PROTECTED] wrote:
ww:text is for finding localized text messages... It's not a UI
component
-Original Message-
From: Francisco Hernandez [mailto:[EMAIL PROTECTED]
Sent: Tuesday,
Title: Message
I will put the related files (interceptor, sample
action) into Jira as soon as I can.
- Original Message -
From:
Jason Carreira
To: [EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 4:41
PM
Subject: RE: [OS-webwork]
ExceptionHandlerIntercepter
That would be fine by me. Being able to set the default would be especially
nice.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Fred
Lamuette
Sent: Tuesday, November 18, 2003 1:13 AM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork] Param directive
I
My biggest problem with this is that it basically eliminates any advantage
to using velocity as far as ease of use is concerned. One of the main
reasons I prefer velocity over JSP is that the syntax is more natural,
especially for things like iterations. Requiring two extra lines makes the
whole
That's when stuff starts to get REALLY ugly. Though I guess there's no sense
arguing about it now, since it looks like we get the best of both worlds.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Fred
Lamuette
Sent: Tuesday, November 18, 2003 2:56 AM
+1, the valuestack is a neat thing and all that, but having random
pushs/pops happen in UI tags of all things just feels wrong.
Drew McAuliffe wrote:
My biggest problem with this is that it basically eliminates any advantage
to using velocity as far as ease of use is concerned. One of the main
I keep my opinion, but I'm happy to see the different points of view are
respected by choosing to solve elegantly the problem :-).
Richard.
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] la part de
Hani Suleiman
Envoye : mardi 18 novembre 2003 18:10
A : [EMAIL
Whoa trigger. Please don't blame WebWork2 for being beta. I would much
rather they get this right in beta regardless of how many changes they
have to make then to either lock us into a bad solution or change after
the production release is made. When developing on the bleeding edge
you usually
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,
Actually, I agree with this. It's stupid of people to hop on a beta
bandwagon then express indignation when the rug is pulled from under
them. That's the whole POINT of a beta, to stumble about in various
directions until the correct one reveals itself.
Thompson, Christopher C (Kris) wrote:
Hani Suleiman wrote:
+1, the valuestack is a neat thing and all that, but having random
pushs/pops happen in UI tags of all things just feels wrong.
Agreed. However, I'm unclear why pushes and pops are required though.
#foreach( $number in $person.phoneNumbers )
$stack.push($number)
Patrick Lightbody wrote:
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
Except the property tag I hope :P
Anders Hovmöller
---
This
Hi Hani,
I think it would be good if you put the release on sourceforge as well since
people might find webwork there also.
Cheers,
Dick Zetterberg
[EMAIL PROTECTED]
- Original Message -
From: Hani Suleiman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 2:35
:-) Yes, the property tag is an exception a couple times over
-Original Message-
From: boxed [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 4:24 PM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] API changes, again!
Patrick Lightbody wrote:
Well, it is kind of
I'm wondering if this fix is in also. I am still breaking like this in
CVS.
Thanks,
Anoop
On Nov 18, 2003, at 9:23 AM, Fred Lamuette wrote:
Is your fix committed ?
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] la part de
Patrick Lightbody
Envoye : mardi 18
Done
Dick Zetterberg wrote:
Hi Hani,
I think it would be good if you put the release on sourceforge as well since
people might find webwork there also.
Cheers,
Dick Zetterberg
[EMAIL PROTECTED]
- Original Message -
From: Hani Suleiman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent:
The pushes and pops were necessary before recent changes made it possible to
pass in objects directly to the velocity directive. Also, there is now talk
about having two separate tags, one that does a stack.findValue
automatically and one that doesn't. Your second example shows that
parameters
Drew McAuliffe wrote:
Recent changes to webwork included the addition of some macros for backwards
compatibility. As part of this change, though, I'm seeing problems with
configuring other macros. I've been using a velocity.properties file that
includes declarations of 2 additional macro files.
Daniel Pfeifer wrote:
There seem to be some problems with the Tags in the latest CVS checkout.
Specifically IncludeTag and UrlTag cause exceptions when used.
Is that a known problem?
Nope, but it's fixed in CVS now :)
M
---
This SF.net
To me 'beta' indicates a fairly stable API (not 3 times major API changes),
but with bugfixes and improvements along the way (eg. Hibernate).
OTOH alpha quality software can be ripped apart.
PS Patrick, is your book up to date with these new changes in WW2? Does it
contain ww:textfield
I seem to recall going thru this before but guest/guest isn't working
for me at
cvs.dev.java.net which is what is refered to on the following page
https://webwork.dev.java.net/servlets/ProjectSource
---
This SF.net email is sponsored by:
Try empty password
On Nov 18, 2003, at 6:28 PM, Robert Nicholson wrote:
I seem to recall going thru this before but guest/guest isn't working
for me at
cvs.dev.java.net which is what is refered to on the following page
https://webwork.dev.java.net/servlets/ProjectSource
Ok never mind I found the bit on the other page that tells that the
guest password
should be blank.
http://www.opensymphony.com/cvs.jsp
The confusion for those who are interested is if you go to the
following page
https://xwork.dev.java.net/source/browse/xwork/
It clearly states under Setup
Q. How do I get the latest version of Webwork2 and XWork from CVS?
cvs -d :pserver:[EMAIL PROTECTED]:/cvs login
(Use an empty password, just hit enter..)
cvs -d :pserver:[EMAIL PROTECTED]:/cvs checkout webwork
cvs -d :pserver:[EMAIL PROTECTED]:/cvs checkout xwork
from the FAQ:
Cameron Braid wrote:
I have downloaded and integrated this code though and the tests run
perfectly (after creating my my own ServletContextAware interface and
removing refrences to the confluence packages)
I really like the work that you have done. Though I think some more work
is required
Isn't Opensymphony (thus WW2, XW) hosted on opensymphony.sourceforge.net? All the urls
I've seen flying around on this list show *.java.net.
Have you moved?
Ciao!
Wayland Chan
email: wchanATtrekspaceDOTcom
--
Get your free email account
Yes, we have moved.
WebWork2 : http://webwork.dev.java.net
Xwork : http://xwork.dev.java.net
I suggest that someone looks into seeing if the webwork/xwork
sourceforge cvs repos can be shutdown, or maybe delete everything from them.
Cameron
Wayland Chan wrote:
Isn't Opensymphony (thus WW2, XW)
...which is why I wrote http://www.opensymphony.com/cvs.jsp to have the
'official' list, unfortunately there's no way of controlling sf.net or
java.net's docs.
On Nov 18, 2003, at 7:37 PM, Robert Nicholson wrote:
Unfortunately there are many places with this information and the
information is
We, not quite. 1.x will remain on sf.net (files will be posted to
java.net though), since the original developers have moved on and so
having cvs history is pretty vital to figure out why certain things
were done the way they were. Plus it's a stable codebase so the one day
delay for anon
Hello
I just started looking at Webwork and checking out the
examples. One thing i noticed in cdlist.jsp is this
code
webwork:iterator value=CDList
option value=webwork:property value=album/
webwork:property value=album/,
webwork:property value=artist/,
webwork:property
Hello,
I'm currently using webwork 1.3 with weblogic 6.1 SP5. When I replace
webwork 1.3 with 1.4, my weblogic app fails to start with the following
startup error:
---
translation of /template/xhtml/checkbox.jsp failed:
weblogic.servlet.jsp.JspException: (line 22): Error in using tag library
have a look at the webwork.examples.i18n.CDList class. That is the
action class, so when the page makes a call to CDList, that
automatically calls the getCDList method in that action class. The
CDList is now iterated through and within the iterate block, the top of
the value stack now has the
Do you have a taglib tld file in your WEB-INF directory? if you do,
then either delete it or upgrade it to the one from the webwork jar (in
META-INF/taglib.tld)
On Nov 18, 2003, at 8:47 PM, Dave Ballard wrote:
Hello,
I'm currently using webwork 1.3 with weblogic 6.1 SP5. When I replace
Hani
Thanks for the reply. I did take a look at CDList
class and the one thing thats puzzling me is that in
the doStartTag and doAfterBody of IteratorTag, all its
doing is a iterator.next() which should return a
Object. My problem is how does that automatically get
cast down to a CD Class.
I come
I'm quite new to Eclipse but can anybody tell me why only some projects
show the check a project configured in the new project wizard when
you are checking stuff out of a CVS location?
I don't understand why it shows me that option for many projects but
not others including Webwork 1.4.
For
I think we're going with what's in CVS unless there's bugs...
-Original Message-
From: Drew McAuliffe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 4:51 PM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork] Param directive
The pushes and pops were necessary before
79 matches
Mail list logo
