Mike Cannon-Brookes wrote:
Some points that people seem to be forgetting:
- Xwork is in the SANDBOX and is eXperimental (if you like the X for that)
- Nothing in Xwork can't be changed, these are ideas, prototypes
- Xwork will be better for 'web work' than WebWork is!
- Xwork will be better for 'n
Jason Carreira wrote:
Actions were originally spec'd to have a method, execute(), with no
parameters. That was back when we had ServletAware, etc., and the
context information would be made available to the Action before it
was executed. When it was decided to get rid of these interfaces, to
decou
More info:
When the action is referred to as an import, such as:
The imported page makes callbacks as long as I use WebWork tags in my
view, such as:
However, no callbacks are made if the view uses JSTL tags, such as:
> -Original Message-
> From: [EMAIL PROTECT
The multiple thread thing is simple/trivial to solve using AOP. I'm not sure
this would cause any performance issue though.
--- Jason Carreira <[EMAIL PROTECTED]> wrote:
> It's not that it's difficult to keep it "Swing compatible" and it's not a
> choice of loosing features. The new features, the
+1 for asynchronous messages
On Mon, 2003-01-13 at 00:24, Rickard Öberg wrote:
> Erik Beeson wrote:
> > Rickard, as I understood, XWork was to break away from J2EE, hence
> > removing "web" from the name. If new versions with strong web ties are
> > going to remain, shouldn't they remain under the
Only after the first try. I don't think slapping on oscache is the
solution, as it just hides the performance problem (of course, adding
oscache is always a good idea, but making that first hit faster would
also be a good idea)
On Sunday, January 12, 2003, at 06:00 PM, Mike Cannon-Brookes wrote
Jason +1 man - someone with sanity here!
Folks - as I said in my earlier email, take a step back and think a second.
For those who are angry / forking / leaving / pissed off / bitching /
whinging - have you honestly actually LOOKED at the Xwork source yet?
HINT: There are some REALLY COOL things
Simple : OSCache with a session scoped cache entry. This will drop the run
time down to about 1ms.
Cheers,
Mike
On 12/1/03 9:36 PM, "Robert Nicholson" ([EMAIL PROTECTED]) penned the
words:
> That is flabbergasting. Couldn't you cache the list when the user logs
> in?
>
> Why don't you take a lo
Can I just chip in here and ask children (all people) to cool the f'k down?
Some points that people seem to be forgetting:
- Xwork is in the SANDBOX and is eXperimental (if you like the X for that)
- Nothing in Xwork can't be changed, these are ideas, prototypes
- Xwork will be better for 'web wor
On Sunday, January 12, 2003, at 08:24 AM, Rickard Öberg wrote:
So, given all of this, my resignation from XWork still holds. The
requirements that have been voiced the last few days are not mine, and
I don't think they're compatible with my goals, at least not without
serious compromises tha
Amen (great point abot JMS, btw)! This is _sandbox_, PLEASE everyone stop
making things so dramatic. All I'm doing is putting things in there for us
to discuss and toy with. Then we talk. That's the idea: Write, talk, write
some more. Not write, talk, abandon project ;)
-Pat
- Original Messag
It's not that it's difficult to keep it "Swing compatible" and it's not a choice of
loosing features. The new features, the biggest one being Interceptors, IMHO, are in
no way involved in this. This is really a question of cleaning up some (IMO) ugliness
in the original code that was put in to k
I'm not sure I see the disconnect here. What's so different about Xwork? Views can
still be JSP / Velocity / XSLT which generates HTML. It's still a great framework for
web app development. If the ThreadLocal thing is the only sticking point, then lets
talk about that. I'm personally for the cha
I have been following this list for quite some time with great interest. I really like
all the new ideas for XWork. I think it would be sad not to see those ideas become
implemented only because it would be difficult to keep it "Swing compatible". If an
alternative is to break Webwork and XWork
I'm a Webwork newbie.
* Should I use 1.3 or 1.2.1?
* It looks like the library of
ValidationEditorSupport's is very thin. There's no MonthEditor, YearEditor, etc.
IntegerEditor has no range option. Is there a way to pass parameters to
ValidationEditorSupport's?
* The javadoc's have no documen
Is anyone having success with the when the value is an
action? Sure it executes the action just fine, but I am not getting any
callbacks from the view to hit the ValueStack. Calling the action
directly, _does_ result in the action and page being executed correctly.
> -Original Message-
>
I think there are two directions here and I don't see any easy resolution at
this stage. So, yes I think two projects make sense. My next question is "Is
there room for these two projects at OS?" Does it make sense or will it be a
distraction since they do have overlap? Should WW move back out on i
I think it might be beneficial to do both xwork and webwork as separate project
at this point of time. At least, people will spent less time debating at
mailing list and get things done. I guess there is no right or wrong here, it
is just that people have different preference and needs. For instanc
What kind of real world example applications do you want? Wafer has a
working webwork example...
And docs? Who needs them - they're for people who aren't willing to roll
their sleeves up and dig directly into the code, right? (Note droll
humour.)
On Sun, 12 Jan 2003, Heng Sin Low wrote:
> I thin
Erik Beeson wrote:
Rickard, as I understood, XWork was to break away from J2EE, hence
removing "web" from the name. If new versions with strong web ties are
going to remain, shouldn't they remain under the original WebWork name?
That is something I wanted to gauge by my last couple of emails. I
That is flabbergasting. Couldn't you cache the list when the user logs
in?
Why don't you take a look at the template and see if you can nail down
what's causing the delays assuming you haven't done that already of
course. If it's user specific what does countries method look like?
On Sunday, J
21 matches
Mail list logo
