Title: Message
Well, if you want to go ahead and put it in place
(and don't have any bugs to fix ;) then go for it. In the meantime, I'm going to
continue to focus on backwards compatibility and docs. The release happens when
those two things happen.
- Original Message -
From:
At my company (Spoke Software), I just finished creating an acceptance test
framework. So for unit tests, I just construct the Action and run execute()
by hand. All other stuff is caught in the acceptance tests.
The way the framework works is: we use JWebUnit and provide a SpokeTestCase
base
Alright alright, don't let Hani bait you. I pretty much agree with you, I
suggest you complain to java.net. While you're at it, can you ask them WTF
happened to our clickstream and sitemesh projects? :)
-Pat
- Original Message -
From: Drew McAuliffe [EMAIL PROTECTED]
To: [EMAIL
Also, are you using CVS or beta1? There was a chance since beta 1 that might
help avoid this as well.
-Pat
- Original Message -
From: Jason Carreira [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 29, 2003 11:35 AM
Subject: RE: [OS-webwork] WebLogic 8.1
Is there any
This is a known bug... basically, the type conversion would only be invoked
if your expression is relatively simple. What I mean is that:
Won't Work:
ww:property value=foo.bar.baz/
Will work:
ww:push value=foo
ww:property value=bar.baz/
/ww:push
Will work:
ww:push value=foo.bar
ww:property
Jerome,
I think that at this point it's a nice feature but we probably won't have
the time to get this in 2.0. I'd like for all the developers to focus on
getting 2.0 out the door with 1.3 compatibility and all the open bugs
resolved.
- Original Message -
From: Jérôme BERNARD [EMAIL
Title: Message
Well, it sounds somewhat useful, but right now I'm
not that interested in new features but rather making sure the ones 1.3 are all
supported and we have cleared out all our bugs. Maybe in a release after
2.0?
- Original Message -
From:
Cameron
Braid
To:
I think that this OgnlList idea is really good -- there are a few places
where it'd be very useful to have a list that doesn't throw AIOOBE but
instead plays nice. This is one of those situations.
- Original Message -
From: Matt Ho [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday,
Jason,
Well Anders is saying by keeping the old TLD entry we'd still be compatible.
I don't really mind but then again, the less necessary changes at this point
the better.
-Pat
- Original Message -
From: Jason Carreira [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, October 05,
Mike Cannon-Brookes has suggested that we have a filter to do the cleanup as
well. I think it's a very scary idea myself :)
I don't think that this is much of an issue at this point. As long as we
keep a reference of the value stack in the HttpServletRequest and change the
tags to use that than
That sucks! Can you open a bug with us and I'll
then pester Drew Davidson to fix it :)
- Original Message -
From:
John Patterson
To: Webwork
Sent: Friday, October 03, 2003 3:19
AM
Subject: [OS-webwork] OGNL wrapping
iterators?
I have just tried to use the
An interceptor is fine for this -- but a Filter seems like a better choice
here since you can apply it to things other than actions if you wanted.
- Original Message -
From: Cameron Braid [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, October 03, 2003 9:22 PM
Subject: RE:
John, there are the kinds of bugs I'd love to be
receiving right now (1.3 compatibility stuff). Please open a high priority issue
for this and we'll get to it asap.
- Original Message -
From:
John Patterson
To: Webwork
Sent: Friday, October 03, 2003 2:21
AM
complex than the standard HTML escaping, or I don't
do any. An option to turn it off per component is probably a better idea
than globally if components are to live together peacefully.
With those two caveats: +1 :P
Anders Hovmöller
Pat Lightbody wrote:
There are a few open issues
Sure thing -- so far beta2 has had 45 issues resolves -- if I moved the
remaining 25 to beta3 that'd be 42 open issues to resolve in beta3. I think
we're at a good point to release beta2 tonight. So i'll try to resolve
anything I can in the next few minutes and then cut a build.
-Pat
-
There is no need to make the ActionTag keep the ActionContext around --
that's really unhealthy. However -- what we could do is put the
ActionContext in a request attribute and then use that in all our tags --
that would solve it perfectly. Here's a visual of the problem that I quickly
put
Yeah -- any class, not just actions, can use the
IoC framework. I think the best bet would be to write a ServletContextListener
that implements FooAware (Foo is your resource you want to load up) and then
pulls out the application-scoped ComponentManager by doing:
#foo grabs from the ActionContext (OgnlContext is what it really is), so
that won't work
I recently added support for doing #reqeuest['foo'], (as well as session
and application), but those are for _attributes_ not parameters. This is an
easy fix though -- I just have to add another Map
That was a typo -- I'd only escape things that didn't have bodies to avoid
that very confusion. What say you?
- Original Message -
From: boxed [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 02, 2003 10:54 AM
Subject: Re: [OS-webwork] Escaping
Pat Lightbody wrote
Yup... that does the trick.
- Original Message -
From: Hendrik van der Linde [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 02, 2003 4:28 PM
Subject: Re: [OS-webwork] Value Stack Magic
Hello,
What Adam probably means is that he wants the class instance, instead
Done in CVS.
- Original Message -
From: Francisco Hernandez [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 02, 2003 1:39 PM
Subject: Re: [OS-webwork] Accessing request parameters
how about 'parameters'
Pat Lightbody wrote:
#foo grabs from the ActionContext
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Pat Lightbody
Sent: Monday, September 29, 2003 3:41 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] Hyperlink best practices - use of actions
Robert,
I haven't tested this functionality in a while, but I don't think it's
Title: Message
Well -- there is
xwork-default-conversion.properties and xwork-conversion.properties. So
xwork-default-conversion.properties is in xwork.jar and then you can write your
own xwork-conversion.properties that can override that.
-Pat
- Original Message -
From:
Should, at load time (as I'm using the Application scope), the framework
load and build an instance
of my class? (calling the default constructor?)
No, the application-scoped resource won't be loaded until it's needed (lazy)
---
This sf.net
Looks like a problem with the absolute/relative paths -- should be trivial
to fix.
- Original Message -
From: Francisco Hernandez [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 12:18 PM
Subject: Re: RES: RES: [OS-webwork] Component repository
im using the
Title: WebWork2 newbie biting off more than I can chew...
Hey Peter, welcome to the list. I don't know about
#2 so much, but #1 can be done a little less ugly that using the Request object
directly. I believe you can implement ParameterAware to get a Map of parameters,
which is what you
How exactly do you want to check it? What are you trying to do?
-Pat
- Original Message -
From: Tim Dwelle [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 25, 2003 2:11 PM
Subject: [OS-webwork] how do i tell if namespace is significant?
In WW2, is there an easy way
Robert,
I haven't tested this functionality in a while, but I don't think it's gone
anywhere :) Scott is right that a result type of redirect is not what you
want. Since you were using jsp:forward/, you'd want to use the result type
of dispatcher.
Try working backwards... see if you can dispatch
You also might want to make a special Result class that extends
ServletDispatcherResult or ServletRedirectResult that helps you achieve this
kind of logic.
-Pat
- Original Message -
From: Francisco Hernandez [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 25, 2003
WebWork supports global-results as well as package-level results, is that
what you want?
- Original Message -
From: Fred Lamuette [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 25, 2003 1:10 PM
Subject: RE: [OS-webwork] Managing URLs from view
Ahahahah, I think you
Are you sure that the same ThreadLocal would be used in ActionA and ActionB?
Since they are separate HTTP requests, is that guaranteed?
-Pat
- Original Message -
From: James Cook [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 25, 2003 5:38 AM
Subject: RE: [OS-webwork]
Yeah, it sounds like a tag re-use bug. We're getting to them and there are a
few open issues. If it's not fixed in the next week or so, yell again
please. Or just open a bug now so we don't forget. Thanks!
-Pat
- Original Message -
From: Micha Mosiewicz [EMAIL PROTECTED]
To: [EMAIL
We're definitely planning to address the migration issue (and docs in
general) as soon as we get these last ~30 bugs finished up.
-Pat
- Original Message -
From: boxed [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 11:59 AM
Subject: Re: [OS-webwork]
Title: Message
Yes, you can now do:
ww:property
value="session['user.key'].firstName"/
-Pat
- Original Message -
From:
Jason Carreira
To: [EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 8:52
PM
Subject: RE: [OS-webwork] JSP tag for
viewing Session
Also of note, there is a FilterDispatcher include in WebWork2 that no one
really uses (I wrote it ages ago and haven't touched it since) that allows
you to go directly to /foo.jsp and it will find the first action that has
foo.jsp as a result and execute the action.
-Pat
- Original Message
Related to this --
I know I should know this (it's late, so I have an excuse) but I don't think
we have a a way for a Model (or Action, but Model is more important here) to
be kept across a session. Formbeans have a nice property in Struts that you
can do a wizard type UI with little effort
What do you mean by encode? Like turning in to amp; etc? Or do you mean
ways to have dynamic values in the result location (ie: foo.jsp?id=${id})?
-Pat
- Original Message -
From: Armond Avanes [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, September 21, 2003 11:03 PM
Subject:
will be shared with us? (can you tell im
anxious? :)
Pat Lightbody wrote:
Glad you like it! Spread the word :)
I've used Hibernate + WebWork2 in a couple projects, and I always used
the
design that spawned from our (Mike/Joe/Ara/Mine) upcoming book that
involves
writing Yet Another
other people over the
last months who were looking for just about the same thing. Is this in the
Wiki?
Thanks,
Robert
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Pat Lightbody
Sent: Thursday, September 25, 2003 7:10 AM
To: [EMAIL PROTECTED
I'd actually like to support this eventually (maybe 2.1). The reason for
this is that most DB-based resources need to be request-scoped, but really
only the DB (ie: Hibernate session) needs to. No reason why everything else
must get dragged down to that level as well. Since WebWork (read: NOT
A);
B calls PM.sesSession(HS B);
A calls PM.save();
Now you're f'ked because request A is using HS B? :)
This causes no end of pain as far as I can see. I'm not even sure how
you
could possibly string them together?
Mike
On 24/9/03 2:24 PM, Pat Lightbody ([EMAIL PROTECTED
Anoop,
That's very strange... when does this happen? During a JSP tag or during a
form submit?
- Original Message -
From: Anoop Ranganath [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 23, 2003 7:01 AM
Subject: [OS-webwork] XWorkConverter trying to load
Title: Message
James, this may not be possible out of the box, but
you can modify the templates directly and even make it so they can take an
optional parameter "align":
ui:textfield label="'label'" name="'searchtext'" maxlength="40"
tabindex="1"
ui:param name="align" value="left"/
Great work Scott! Anyone who is using Weblogic, please let us know how
things go. Thanks!
- Original Message -
From: Scott Smith [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 22, 2003 8:59 AM
Subject: [OS-webwork] Weblogic 6.1 now integrated cleanly into WebWork 2
Actually, this isn't true...
John, are you aware of the page:applyDecorator/ tag? In JIRA, for example,
every single form is built using that.
-Pat
- Original Message -
From: John Patterson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 18, 2003 11:44 AM
Subject: Re:
No, unfortunately the key is just a single property name -- not a full
expression. I think adding support for an expression would be very
difficult. But keep in mind that the conversion property files can be for
_any_ object, not just Actions.
-Pat
- Original Message -
From: Anoop
John,
I did this kind of stuff all the time in WebWork to some extent, but not at
the level of interaction you've proposed. How would you envision it working?
-Pat
- Original Message -
From: John Patterson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 22, 2003 7:36 AM
So in a way the type defines it's input mechanism... I think it's
interesting but needs to be fleshed out some more. I don't think that this
neccessarily means that applications would have to be tied to WebWork, but
maybe could even be done with another (!) config file like
PhoneNumber-input.xml
I thought the URLTag wasn't needed because it just uses
UrlHelper.buildUrl(), which you can also use from Velocity?
I can use from velocity what is really in the velocity context. So, if
UrlHelper is not in the context, i cant use it.
BUT with the extension of velocity-tools, and
Hey everyone,
We're hard at work getting the last batch of bugs
fixed up, but unfortunately due to a system crash a while back we've lost some
of the patches you guys uploaded. If you could please look at any of the issues
that you uploaded patches for and re-upload them again if they aren't
Also, I believe that the build in XWork converters support turning
String[] - List. Just a slightly nicer format. :)
-Pat
- Original Message -
From: Bernard Choi [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 17, 2003 2:38 AM
Subject: Re: [OS-webwork] How to get
Title: Message
It may also be that it DOES see your xwork.xml file
but there is another problem happening (maybe a class is mistyped?) I'd
recommend stepping through the code in xwork to find the problem. In the
meantime, I think it sounds like we should be doing better error
reporting.
I think the idea is that since webwork 1.x will never be moved to java.net,
having a webwork2 directory in java.net seemed weird. Just check it out
and rename the dir :)
-Pat
- Original Message -
From: Scott Farquhar [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 09,
Title: Message
This is in CVS now.
- Original Message -
From:
Jason Carreira
To: [EMAIL PROTECTED]
Sent: Friday, September 12, 2003 7:46
PM
Subject: RE: [OS-webwork] Include tag in
ww2
Yes... If it's in there it will be added... I'll make it my next
These would never be in the value stack, but they could end up in the
ActionContext I suppose. Open an issue for this and we'll take a look.
- Original Message -
From: Samuel Mota [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 10, 2003 12:50 PM
Subject: [OS-webwork]
Well, we'd still be missing quite a bit :)
-Pat
- Original Message -
From: Francisco Hernandez [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 02, 2003 5:32 PM
Subject: Re: [OS-webwork] Getting started tutorial
what if we take one of the existing ww1 tutorials,
Yes, there is a use case. Look at the lifecycle listeners, they set up
fallbacks.
-Pat
- Original Message -
From: James Cook [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 01, 2003 5:04 PM
Subject: RE: [OS-webwork] DefaultComponentManager (fallback?)
OK. Is there a
For the tabbed pane tag, if it was in 1.3 we need to get it in 2.0.
As for having the UI tags work when not inside of an action request -- I
believe this works or at least used to. I made a special point of allowing
this to take place so that users could point to /foo.jsp without having to
create
What kind of replacements? Stuff like if/then/else and iterator are built in
to velocity natively. Any tag that was in 1.3 should be in 2.0 unless a VERY
good reason is given -- so everyone, please be sure to open issues if you
see something that was in 1.3 and isn't in 2.0 yet.
-Pat
-
I know very little about sessions when cookies aren't enabled -- but I
thought the app server did all that magic?
- Original Message -
From: Francisco Hernandez [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 02, 2003 6:43 AM
Subject: [OS-webwork] losing session token
Jason and I talked last night, and rather than introduce a new tag, we're
just going to add an executeResult attribute to ww:action that defaults to
false. If for some reason we see more attributes and behaviors being added
to ww:action, we'll go ahead and break them out in to different tags (a la
I thought I had made it so you could drop in UI tags without ever having an
action executed. What problems are you facing?
-Pat
- Original Message -
From: Vernon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 7:54 PM
Subject: [OS-webwork] UI tags as standalone
Yes, please open a bug -- I think this has been a problem for a while and
should get fixed.
- Original Message -
From: Samuel Mota [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 26, 2003 8:10 AM
Subject: [OS-webwork] Submit tag
Hi,
The tag for submit buttons is at
Jason,
One request -- when you move the logic in to an interceptor... can you use a
Lifecycle interface rather than reflection?
-Pat
- Original Message -
From: Jason Carreira [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, August 28, 2003 6:34 AM
Subject: RE: [OS-webwork]
Could be something about the namespace you've configured your package to be
in?
- Original Message -
From: Samuel Mota [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 26, 2003 9:48 AM
Subject: [OS-webwork] There is no Action mapped for action name login
Hi,
I'm getting a
I can see why the exception would be happening... parsing true to a
number can't be done. Are you getting a thrown exception, or is it just
being logged? I changed how exceptions are handled (user exceptions are
thrown) but a side effect might be that you end up with things like this
(which is
I see no reason why this couldn't be included in webwork directly (and not
webwork-extensions). Since it wouldn't be required to run unless you
_wanted_ to use it, and it's a view technology just as XSLT and others are,
I think it should be included. Please go ahead and create a jira issue if
you
?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Pat Lightbody
Sent: Tuesday, 26 August 2003 11:41 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] Freemarker Views
I see no reason why this couldn't be included in webwork directly (and
not webwork
Sounds like java.net's CVS doesn't support some of the operations that
Eclipse uses. :(
Open a bug report with java.net, they are actually pretty responsive!
- Original Message -
From: Cameron Braid [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 25, 2003 10:59 PM
Subject:
Actually, there is something like that...
This came from Rickard's original requests back in January. I haven't worked
on it for a while, so it might not be up to par with ServletDispatcher...
but check out FilterDispatcher. It basically lets a request for index.vm
take place, but rather than
Sounds like your app is using too much memory. Have you tried profiling it
or giving it some more memory?
- Original Message -
From: Francisco Hernandez [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, August 20, 2003 3:02 AM
Subject: [OS-webwork] webwork2 OutOfMemoryException
Joe, that'd be great if you could help out. Just tell us what you need and
we'll give you all our support.
-Pat
- Original Message -
From: Joseph Ottinger [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 19, 2003 11:32 AM
Subject: [OS-webwork] Docs
Okay, now that WW2 is
I'm not too happy with the idea of a default-action-package. I never really
liked it in WebWork1 and I still don't like it. It confuses refactoring
tools a whole bunch and doesn't seem to offer that much (how hard is it to
copy-and-past?).
As for executing actions that aren't defined in xwork.xml
Good catch... you know what to do ;)
- Original Message -
From: Francisco Hernandez [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, August 20, 2003 5:01 AM
Subject: [OS-webwork] checkboxlist.vm bug
found a bug in checkboxlist.vm
if a List (of selected checkboxes) is passed
I thought the writing was pretty good. I on the other hand question the
need for boasting about a beta. It'd be weird to do a press release now,
and then a similar one in a week or two when the final release is out.
+1 on that :)
---
This
Jason,
Should we be keeping track of a changes.txt file? Why not just point to JIRA
changelog? I'd much rather do that as it also promotes putting _all_ bug
fixes and feature requests/changes in to JIRA.
-Pat
- Original Message -
From: Jason Carreira [EMAIL PROTECTED]
To: [EMAIL
Just a side note -- should the docs be committed to CVS? I'm not sure if
that's entirely a good (or bad) idea. I was kinda imagining that the docs
would be autogenerated by the dist Ant target and bundled in with the zip
file.
-Pat
- Original Message -
From: Jason Carreira [EMAIL
Please open a feature request in JIRA so we don't forget about this before
the 2.0 release. Thanks!
- Original Message -
From: Peter White [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 18, 2003 12:04 PM
Subject: RE: [OS-webwork] Any examples of WebWork/WebWork2 using XSLT
What kind of tools would you want to see? I suppose having a nice interface
in IDEA to work with actions in a GUI (rather than editing xwork.xml) would
be a neat little thing. Unfortunately, my Swing skills are horrible.
Horrible. Very horrible.
As for other stuff (like a book)... stay tuned :)
Tonight! :)
- Original Message -
From: Smith, Scott [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 11, 2003 9:15 PM
Subject: [OS-webwork] Beta on Webwork 2 When?
Is there a beta yet for Webwork 2? If not, when?
Very curious developers want to know.
Scott
So it sounds like it was a JSP taglib issue and not an EL issue?
- Original Message -
From: Drew McAuliffe [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 11, 2003 3:19 PM
Subject: [OS-webwork] Re: Performance diff bw ww1 and ww2?
I've moved from Tomcat to oc4j and the
Marco,
There have been a couple requests to implement ValueStack.set() (we
currently don't, look at CompountRootAccessor to see for yourself). If you
open a jira issue, we'll try to get around to it shortly.
With regards to your example, if you need to set both the model and the
action, it sounds
Drew,
Can you open a request for the VelocityServlet extensibility?
-Pat
- Original Message -
From: Drew McAuliffe [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 12, 2003 8:07 AM
Subject: RE: [OS-webwork] Velocity helper missing from ww2
I have my own copy that I ported
then use that as the basis for their
filters to extract only the notifications for modules they want?
M
On 12/8/03 1:26 AM, Pat Lightbody ([EMAIL PROTECTED]) penned the
words:
---
This SF.Net email sponsored by: Free pre-built
-webwork] Jira alerts
Can we just leave the comments and new issues coming to the main list?
They are essentially the same as meesages to the list, just saved, in my
mind...
-Original Message-
From: Pat Lightbody [mailto:[EMAIL PROTECTED]
Sent: Tue 8/12/2003 8:48 AM
To: [EMAIL
In general, if there is something missing from WW1 that was in WW2, please
file a Jira issue. Thanks!
-Pat
- Original Message -
From: Drew McAuliffe [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 11, 2003 3:23 PM
Subject: [OS-webwork] Velocity helper missing from ww2
Alex,
The best thing to do is to make your interceptor implement XxxAware, which
is the enabler for the component you want to get a handle to. Then, with the
interceptor running _after_ the ComponentInterceptor, do the following in
your interceptor:
ComponentManager cm =
Nope, but the feature has not been lost, we just haven't gotten to it yet.
- Original Message -
From: Matthew E. Porter [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, August 09, 2003 10:00 AM
Subject: [OS-webwork] Factories for IoC
There was recently talk about specifying a
Ee I feel like we're going to get flooded. I _never_ read the JIRA
alerts that come to the list, there are just too many. Maybe set up a
different list or something?
-Pat
- Original Message -
From: Jason Carreira [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, August 09,
I'll do some optimizing soon, but just off the top of my head those numbers
sound very strange. I've done some imprecise testing and I found WW2 about
as fast as WW1, especially when using lots of form elements with lots of
data.
-Pat
- Original Message -
From: Jason Carreira [EMAIL
Actually, SessionLifecycleListener is a listener in web.xml, not sure why
it would be getting stored in the session. I suppose we could make it
Serializable though, wouldn't really harm anything.
- Original Message -
From: Konstantin Priblouda [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
That is correct. Enjoy!
- Original Message -
From: Thompson, Kris [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, August 06, 2003 1:43 PM
Subject: RE: [OS-webwork] java.net status and sourceforge
I was able to check out the code for xwork but I did not find a module
called
Any reason why this isn't just the default behavior? Shouldn't session
access always be sync'd?
- Original Message -
From: Jason Carreira [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, July 31, 2003 8:23 AM
Subject: [OS-webwork] Synchronizing session access (WW 1.3 and 2.0)
I'm
I have just a few small changes to make, then we'll be doing a beta. Thanks
for your patience everyone!
-Pat
- Original Message -
From: Jason Carreira [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003 9:17 AM
Subject: RE: [OS-webwork] Xwork/WebWork2 development
No, the request object isn't on the stack, I don't believe it ever was even
in WebWork 1.3. If it was, then I don't like it :) How about putting it in
the ActionContext so that it is now:
webwork:if test=#request.requestURL.indexOf('/epm') != -1
If you are fine with that, please open a jira
No, we could probably add this filter to the install instructions.
- Original Message -
From: James Cook [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, July 29, 2003 5:32 AM
Subject: RE: [OS-webwork] Re: WW1.3 and Sitemesh
I would think that this behavior would be desireable
John,
Hmm... seems that the action or model should be pushed on the stack, and
then properties could be set at that point. Open a bug about this and we'll
look in to it (there may have been a good reason, but it's way too early for
me to think about it).
-Pat
- Original Message -
From:
James,
It sounds like you don't understand how WebWork works. With each new request
a new Action is created, so you can't do what you're asking. You'd need to
make calls out to the session in order to do this kind of stuff. In short:
Actions are request scoped.
-Pat
- Original Message -
This is supposed to be the alias name of the action, we'll need to fix that.
Please file a bug.
-Pat
- Original Message -
From: John Patterson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, July 25, 2003 5:47 AM
Subject: [OS-webwork] ActionContext.getName() returning null
When
a bug in Jira. I cannot see
anywhere on the site to do so (in fact the jira.opensymphony.com site is
down right now)
- Original Message -
From: Pat Lightbody [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, July 25, 2003 3:50 PM
Subject: Re: [OS-webwork] ActionContext.getName
1 - 100 of 174 matches
Mail list logo
