I think WW1 is missing a number of features available in WW2, but I'll
assume that was Pat's dyslexia at work ;)
On Mon, 11 Aug 2003, Pat Lightbody wrote:
In general, if there is something missing from WW1 that was in WW2, please
file a Jira issue. Thanks!
-Pat
sf.net archives the mailing list, but it works just about as well as
everything else sf.net does. mail-archive's version would probably be
better.
--Erik
On Fri, 6 Jun 2003, Robert Douglass wrote:
Is it possible to do keyword searches on the mail list archives? Out of the
101 questions that
When I wrote ui tags for velocity back around 1.2, I used a directive for
each tag (#textfield, #hidden, etc), which is still the format that I
prefer. The problem I ran into (and why I've never committed anything to
CVS) was dealing with parameters, and dealing with directives having to be
either
Yes, the intention is still to split the taglib up into multiple taglibs.
It just hasn't gotten done yet.
--Erik
On Wed, 26 Mar 2003, Heng Sin Low wrote:
I remember reading on the list sometime back that the taglib.tld would be split
to ui and non-ui tld ( not the case in webwork 2.0 at the
The URL Scott provided gives a full history.
Who checked it in?
-Original Message-
From: Scott Farquhar [mailto:[EMAIL PROTECTED]
Sent: Monday, March 24, 2003 6:40 PM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] [Fwd: [Opensymphony-cvsmail]
webwork/src/main/webwork/multipart
If we're going to support a ServletActionContext.setRequest() method, then
I would support passing that request object to the forwarded jsp, why else
would you want to set the request in SAC?
--Erik
On Sat, 22 Mar 2003, Morten Wilken wrote:
hi all,
i proposed this a couple of days ago, but
+1 Always nice to see someone on top of things and keeping everybody else
motivated. Keep up the good work.
--Erik
On Thu, 6 Mar 2003, Patrick Lightbody wrote:
In the last few weeks Matt has been hounding me to get his UI taglibs in
place, and finally Jason did it because I'm just a slacker.
Hmm, I just added ServletActionContext for getting
request/response/servletConfig/servletContext. Should I instead make these
available as 4 individual components?
--Erik
The *Aware stuff is coming back in a big way in XWork/WebWork 2.0. It's part
of the Inversion of Control and
We'll be starting coding in a month or so - so I guess it's 1.3 for now
ww2 is cool, check it out, give it a whirl, when you see things that
aren't there, add them ;) Meeting minutes are in the Wiki and give a
pretty good idea of the direction to move in.
--Erik
SnipSnap has a blog, so you're duplicating effort in any case. Maybe you
guys should just add the stuff you want to snipsnap instead...
Now we've gone full circle and have gotten totally lost. I think the point
was to make a demo/tutorial app for webwork 2.0/xwork/opensymphony, not
build a
It seems there is currently no way of getting at the ServletContext,
only the HttpServletRequest/HttpServletResponse (from anywhere, an
Action, an Interceptor, a Component, etc) unless I'm missing
something. If there is a way, I'd love to hear it.
To fix this, I've added ServletConfig to the
On Wed, 26 Feb 2003, Jason Carreira wrote:
Not sure what you mean here. You didn't add it to the ActionContext
class? No, wait... Looks like you added it to the extra context that is
passed in to create the ActionContext by the ServletDispatcher. Ok.
That seemed like the logical place for it.
I haven't read any of this thread, so forgive me if I'm totally off base
here. If we're talking about a velocity view, $someMethod() won't work
afaik. Anything in the form $foo is considered a property, not a method,
and can't accept parameters. $foo looks for getFoo() in the context. This
came up
Why he thinks it would be bad to depend on Jelly? So far, there hasn't
been a good case as to how it could benefit xwork/webwork, and even if it
did add a little, we try to keep dependencies to a minimum. A bunch of
dependencies is too jakarta-ish, as someone put it.
--Erik
On Sat, 8 Feb 2003,
Why don't you send diffs to the list and a regular committer can add them.
--Erik
On Fri, 7 Feb 2003, Philipp Meier wrote:
could please someone re-grant cvs write access to me (llucifer). I
have some important bug fixes for XSLTServlet that should go into 1.3
-billy.
--
Could someone make a small note about what xw/ww uses from each
dependency? If someone (*cough*pat*cough*jason*cough*) would even post
something to the list about it, I'll put it up in the wiki.
At the business meeting:
And webwork has a small memory foot print, only ~20k
Why is our WAR file so
Some of us met today and came up with a rough agenda. Feel free to edit
this. It is poorly configured because snipsnap has trouble with ordered
lists inside unordered lists and apparently has now way of putting in raw
html, but it looks better this way :)
For those who can't see the link due to snipsnap running on a freaky port,
here's the agenda:
The meeting will be at 14:00 GMT on Febuary 5th. If you have problems with
converting the timezone, click here, or search google for help. It will
cover both XWork and WebWork 2.0.
RULES:
nobody is
(in
iterator tag). Anything else?
I don't think that this can be fixed in current webwork, as we would not
be able to maintain backwards compatibility? You should add this as a
feature to webwork 2.0.
Cheers,
Scott
Erik Beeson wrote:
The biggest complaint that I hear about the ww taglib
Read Jason's email again carefully. For that to work, you need to have the
ww:property value=name / tag inside the body of the first tag. Like I
said, check Jason's example again carefully.
To the developers who don't want to break up PropertyTag, here we see the
problem with a single tag that
Converting .. to [1] is easy enough, but what about /? Our converter would
need to be smart about foo/bar vs 10/5... or would we just not care about
mathematic operations?
When did mathematic operations come into the picture? The current EL
doesn't support mathematic operations, does it?
If
Config file reloading is a totally different ballpark than Action
reloading. However, it is part of the planned configuration overhaul in
XWork.
--Erik
---
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT
Ok, who wants to do this? Wiki's scare me :-)
Done.
http://www.opensymphony.com:8668/space/XWork+1.0+Mission+Statement
http://www.opensymphony.com:8668/space/WebWork+2.0+Mission+Statement
They are linked to from:
http://www.opensymphony.com:8668/space/XWork
and
There would be no hidden field. When the URL is generated that URL is
associated with the actions to be run. There's no way to figure out from
the URL what actions will be executed.
So you get URLs like:
http://www.myhost.com/some/path/wfjIFEOwijofOEIWjfIOWEkaAIoqjklnfoSyEj?foo=bar
And then a
If I recall correctly, this is caused by having saxon.jar before
xerces.jar on the classpath. AElfred, a non-validating parser, is being
found and used before Xerces, the validating parser that you actually want
to be using. Should just be a matter of changing some start up scripts or
the like. If
The view releated stuff consists of all the features available in JSP
available in velocity, cleaned up taglibs, and Tea support. Are people
expecting anything else?
You can expect to start seeing this stuff next week sometime after I, too,
get back to my fast internet :)
Congrats on the new
I've started a very rudemantary roadmap for XWork so everyone will have a
clear picture of what the goals are. Please fill it in as much as
possible. If people disagree with what I've listed so far, please bring it
up with the list. I really don't want to flaming/opinion wars that the
list is
I've started working on code for XWork and was wondering what I should do
with it. Is there a new branch for the new code? Are we going to start a
fresh and migrate common code or keep building on what's there now? Is the
package name going to change to xwork? com.opensymphony.xwork?
--Erik
Yes, the fix for this is sitting in my local copy of webwork, along with a
few previously discussed updates to URLTag. I'm working on finishing those
up and getting them in tonight (tuesday night). Expect a release on
Wednesday if everybody is happy with it.
--Erik
On Wed, 11 Dec 2002, Geoff
I think it was decided to leave the tag renaming until XWork?
--Erik
On Wed, 11 Dec 2002, boxed wrote:
I thought there was some agreement a while back that the Property Tag
should
not print out the value if it has an id attribute, but the check for this
(BasicPropertyTag line 101) hasn't
I haven't read the 40 other emails in this thread from today, so pardon me
if this has already been said.
I think XML - XSLT - HTML on the fly is overkill. I'd like to see the
docs stored as XML and converted to HTML (through whatever means) at dist
time. I agree that straight HTML is better for
I've been trying to work out better documentation and a better demo app
for 1.3, but I may not have it together in time. I'll keep the list
posted.
Also, I've got updates to URLTag for some thing previously discussed on
the list that'll I'll be getting into CVS in this next week.
*** If anybody
I'm already working on url tag. It'd be trivial to add an id attribute.
Would people like this? Vedovato, would you file this under JIRA?
--Erik
On Tue, 26 Nov 2002, Vedovato Paolo wrote:
Hi Webworker
how can I achieve such a behaviour:
ww:url value='anAction.action' id=url/
ww:bean...
I have and action that has two getters that return ints. Is there a way
for my view to render the sum of them? Currently I use a bean that has a
method int sum(int x, int y) { return x+y; }. Is there a better way?
--Erik
---
This sf.net email
end, but I guess I'll add a nextIndex and previousIndex fields or
something.
--Erik
On Wed, 13 Nov 2002, Maurice Parker wrote:
Erik Beeson wrote:
I have and action that has two getters that return ints. Is there a way
for my view to render the sum of them? Currently I use a bean that has
2002, Patrick Lightbody wrote:
No, you are actually pushing a value on the stack. Look at the code in
PropertyTag. Also, you might want to take a look at ValueStack.findValue to
understand how values are found (there is no such thing as a root).
-Pat
- Original Message -
From: Erik
Who's going to write a ww powered Wiki? ;)
On Mon, 11 Nov 2002, Mike Cannon-Brookes wrote:
And people could add comments I guess.
I'm all for it.
I'm hanging out for the new version of SnipSnap which should have email
notifications - then we can get an email notification of Wiki changes
http://sourceforge.net/mailarchive/message.php?msg_id=2413436
On Mon, 11 Nov 2002, Maurice C. Parker wrote:
Guys,
It looks like a lot of stuff has been cleared up in the last couple of
weeks. We're down to a handful of issues that once cleaned up we can
release an alpha version of 1.3.
http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-79
Currently, if a ww:property tag doesn't have a body, it prints the value
of the value attribute, or . if no value is provided. In the case of
setting a pageContext attribute (a bodyless tag), this isn't what you
want.
diff attached.
Can a chain have more than one View?
Yes, of course:
I read this to mean, can a chain actually finish on more than one view.
For example:
CreateAccount.action=Create
CreateAccount.success=SendConfirmationEmail.action,create_success.jsp
In which case the answer would be no. A chain can only
http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-84
If an invalid date text is submitted the attribute will
get the current date, while a null value is more appropriate.
The problem is in the DateFormatter constructor where the
date variable is initialized to new Date()
While I see
41 matches
Mail list logo
