Re: [OS-webwork] Re: WW1.3 and Sitemesh

2003-07-28 Thread Mike Cannon-Brookes
Shouldn't be - it's all in the WebWork module? Just deploy the filter if you're using WW + SiteMesh, otherwise ignore it. It doesn't actually interact with SiteMesh, just leave stuff in the request object for SiteMesh to pick up. M On 29/7/03 10:32 AM, "Jason Carreira" ([EMAIL PROTECTED]) penned

RE: [OS-webwork] Re: WW1.3 and Sitemesh

2003-07-28 Thread Jason Carreira
> -Original Message- > From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 6:06 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Re: WW1.3 and Sitemesh > > > No, the servlet is the dispatcher. > > - Before the request, the filter adds a request attr

Re: [OS-webwork] Re: WW1.3 and Sitemesh

2003-07-28 Thread Anders Engström
On Tue, Jul 29, 2003 at 08:05:57AM +1000, Mike Cannon-Brookes wrote: > No, the servlet is the dispatcher. > > - Before the request, the filter adds a request attribute to say 'I'll > handle the clean up'. > - The servlet runs as normal, except if it finds this request attribute, it > does not pop

Re: [OS-webwork] examples examples examples...looked at xpetstore

2003-07-28 Thread Ben Alex
> Im also interested in how the ClientDispatcher works? > Is the ValueStack available on the client side? IE: Can I > call an action on the server via the ClientDispatcher, and > access the resultant in a ValueStack on my Swing client? If > so... COOL And how the hell do you do that??? I have

Re: [OS-webwork] Re: WW1.3 and Sitemesh

2003-07-28 Thread Mike Cannon-Brookes
No, the servlet is the dispatcher. - Before the request, the filter adds a request attribute to say 'I'll handle the clean up'. - The servlet runs as normal, except if it finds this request attribute, it does not pop the action off the stack, nor clean up the dispatcher. - After the request, the f

RE: [OS-webwork] examples examples examples...looked at xpetstore

2003-07-28 Thread Jason Carreira
> -Original Message- > From: Porter, Mike [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 12:47 PM > To: [EMAIL PROTECTED] > Subject: RE: [OS-webwork] examples examples examples...looked > at xpetstore > > > Im also interested in how the ClientDispatcher works? > Is the ValueSt

RE: [OS-webwork] examples examples examples...looked at xpetstore

2003-07-28 Thread Porter, Mike
Im also interested in how the ClientDispatcher works? Is the ValueStack available on the client side? IE: Can I call an action on the server via the ClientDispatcher, and access the resultant in a ValueStack on my Swing client? If so... COOL And how the hell do you do that??? Thanks, Mike -

RE: [OS-webwork] examples examples examples...looked at xpetstore

2003-07-28 Thread Jason Carreira
> -Original Message- > From: Konstantin Priblouda [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 12:40 PM > To: [EMAIL PROTECTED] > Subject: RE: [OS-webwork] examples examples examples...looked > at xpetstore > > > > > Yes, that might be valid, but I guess I would at > > lea

RE: [OS-webwork] Properties not set on action

2003-07-28 Thread Jason Carreira
Both the action AND the model are pushed onto the ValueStack. I think the problem is that for getting params, the value stack goes down the stack to find the property if it's not in the topmost object on the stack. For setting properties, it only tries the topmost object, unless you specify that it

RE: [OS-webwork] examples examples examples...looked at xpetstore

2003-07-28 Thread Konstantin Priblouda
> Yes, that might be valid, but I guess I would at > least try the > ClientDispatcher first... I've come to the point > where I'll work to keep > EJBs out of projects if possible. The same is for me... Decent IoC and hibernate for persistenze does far better job... BTW, how the ClientDispatche

RE: [OS-webwork] On storing values in actions

2003-07-28 Thread James Pan
Hi, Yes, I realized that too :-) I've changed the code to directly access the variables in session... thank you all for your help! Cheers, James > -Original Message- > From: Pat Lightbody [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 11:31 AM > To: [EMAIL PROTECTED] > Subject

Re: [OS-webwork] On storing values in actions

2003-07-28 Thread Pat Lightbody
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 - F

Re: [OS-webwork] Properties not set on action

2003-07-28 Thread Pat Lightbody
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: "J

RE: [OS-webwork] examples examples examples...looked at xpetstore

2003-07-28 Thread Jason Carreira
> -Original Message- > From: Konstantin Priblouda [mailto:[EMAIL PROTECTED] > > > > Why? What are your requirements that necessitate > > this? > > For example - need to access same data model from > swing application. Or would you favor client > dispatcher to do this? > > regards, >

RE: [OS-webwork] Re: WW1.3 and Sitemesh

2003-07-28 Thread Jason Carreira
What does the filter do in this case? Does it become the whole dispatcher? I thought you had a heated discussion with someone about why that was a bad idea :-) > -Original Message- > From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 10:14 AM > To: [EMAIL PR

RE: [OS-webwork] examples examples examples...looked at xpetstore

2003-07-28 Thread Konstantin Priblouda
--- Jason Carreira <[EMAIL PROTECTED]> wrote: > > > > -Original Message- > > From: Butt, Dudley > [mailto:[EMAIL PROTECTED] > > Sent: Monday, July 28, 2003 6:15 AM > > To: [EMAIL PROTECTED] > > Subject: [OS-webwork] examples examples > examples...looked at xpetstore > > > > > > Hi, >

RE: [OS-webwork] examples examples examples...looked at xpetstore

2003-07-28 Thread Jason Carreira
> -Original Message- > From: Butt, Dudley [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 6:15 AM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] examples examples examples...looked at xpetstore > > > Hi, > > I really need to know how to get started with trying to put > it al

Re: [OS-webwork] WW1.3 and WW2

2003-07-28 Thread Hani Suleiman
On the other hand, webwork has been heavily profiled and optimised, ww2 has not (and I expect a fully optimised release is probably not something that'll happen soon). Webwork1 is deployed in quite a few places, webwork2 is only deployed currently by its own developers. As Mike said, it all

Re: [OS-webwork] WW1.3 and WW2

2003-07-28 Thread Konstantin Priblouda
--- Mike Cannon-Brookes <[EMAIL PROTECTED]> wrote: > Dudley, > > I think this depends on your level of comfort. > > Personally I wouldn't start a new application with > WW 1.3 at the moment, as > your development cycle is likely longer than the > time until WW2 is released. > Also using a framew

RE: [OS-webwork] Re: WW1.3 and Sitemesh

2003-07-28 Thread James Cook
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > Mike Cannon-Brookes > What is wrong with the filter/servlet combination? It works > perfectly, will > allow SiteMesh usage with WW tags in the decorator (that's a 'nice' > combination - no interdependenc

RE: [OS-webwork] On storing values in actions

2003-07-28 Thread James Cook
> [mailto:[EMAIL PROTECTED] Behalf Of > James Pan > Sent: Monday, July 28, 2003 9:55 AM > What I want to is actually very simple: to allow some kind of > link with parameters, like > > .../mylink?parm1=hello&parm2=world > > but to allow for omitting parameters as I see fit... so after > that call a

Re: [OS-webwork] WW1.3 and WW2

2003-07-28 Thread Mike Cannon-Brookes
Dudley, I think this depends on your level of comfort. Personally I wouldn't start a new application with WW 1.3 at the moment, as your development cycle is likely longer than the time until WW2 is released. Also using a framework during it's development is the perfect way to get your bugs fixed

RE: [OS-webwork] On storing values in actions

2003-07-28 Thread Konstantin Priblouda
> What I want to is actually very simple: to allow > some kind of link with parameters, like > > .../mylink?parm1=hello&parm2=world > > but to allow for omitting parameters as I see fit... > so after that call above, the data (parm1=hello and > parm2=world) should be stored somewhere, and then i

Re: [OS-webwork] Re: WW1.3 and Sitemesh

2003-07-28 Thread Mike Cannon-Brookes
I agree - there should be nothing in SiteMesh that affects this. What is wrong with the filter/servlet combination? It works perfectly, will allow SiteMesh usage with WW tags in the decorator (that's a 'nice' combination - no interdependency) and all WW apps will be backward compatible by just not

RE: [OS-webwork] On storing values in actions

2003-07-28 Thread James Pan
Hello, > Ahh.. If the OgnlUtil does that, it should be logged as a bug. This is > if the param is not in the params map at all, correct? That would > definitely be a bug. > > > > > I think he means that the action properties are being set to > > null by OgnlUtil.copy(map, object) > > > > I.e.

RE: [OS-webwork] WW1.3 and WW2

2003-07-28 Thread James Cook
Dudley, I can't speak for the core development team, but I suspect 1.3 will get some attention to fix any major bugs if they are found, but I would expect (and hope) that most of their attention is focused on WW2. One of the original goals was stated that WW2 will be backward portable with WW 1.3

[OS-webwork] [JIRA-Opensymphony] Created: (WW-237) WebworkVelocityServlet bases on deprecated servlet from velocity core

2003-07-28 Thread legendaryservice
Message: A new issue has been created in JIRA. - View the issue: http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-237 Here is an overview of the issue: -

Re: [OS-webwork] Re: WW1.3 and Sitemesh

2003-07-28 Thread Scott Farquhar
How would you propose this work? I don't think that this should be put into sitemesh at all - it is a *webwork* feature, and sitemesh should not have a dependency on sitemesh at all. It can easily be done in webwork code, in a way that doesn't affect anyone who chooses not to use it (apart fro

RE: [OS-webwork] examples examples examples...looked at xpetstore

2003-07-28 Thread Butt, Dudley
great thanx for the help, will take a look -Original Message- From: Konstantin Priblouda [mailto:[EMAIL PROTECTED] Sent: Monday, July 28, 2003 12:30 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] examples examples examples...looked at xpetstore --- "Butt, Dudley" <[EMAIL PROTECTED]>

Re: [OS-webwork] examples examples examples...looked at xpetstore

2003-07-28 Thread Konstantin Priblouda
--- "Butt, Dudley" <[EMAIL PROTECTED]> wrote: > Hi, > > I really need to know how to get started with trying > to put it all togethere. I've looked at the > xpetstore example, but I'm sure one should use a > session/service EJB layer between Hibernate and WW. > Has anyone done this yet, I would b

[OS-webwork] basic pattern of action naming and purposes and flow

2003-07-28 Thread Francisco Hernandez
do you guys have a pattern that you always try and use when writing actions and choosing what alias to use flow? i've used a few but im curious as to what you guys are using im thinking of one like this (this is just a simple scenario for example, editing a users address): createObject shows the

[OS-webwork] examples examples examples...looked at xpetstore

2003-07-28 Thread Butt, Dudley
Hi, I really need to know how to get started with trying to put it all togethere. I've looked at the xpetstore example, but I'm sure one should use a session/service EJB layer between Hibernate and WW. Has anyone done this yet, I would be most grateful if someone would share some example code t

[OS-webwork] WW1.3 and WW2

2003-07-28 Thread Butt, Dudley
Hi, Ok, so once WW2 is up and running, is WW1.3 still going to be supported. I'm just about to start working with 1.3 using the xpetstore example and I was wondering if I shouldn't perhaps wait for WW2, or will it be safe to continue in W1.3 until WW2 is final? Will I be able to port it across e

[OS-webwork] Re: WW1.3 and Sitemesh

2003-07-28 Thread Chris Miller
Updating all the taglibs etc to try to find it using STACK_HEAD as a last resort sounds a little messy, and is not required by a large percentage of WW users anyway. The current approach where WW publishes the value so post-webwork code can access it sounds fine. The real problem of course is that

Re: [OS-webwork] WW1.3 and Sitemesh

2003-07-28 Thread Anders Engström
On Fri, Jul 25, 2003 at 05:40:59PM +0200, Anders Engström wrote: > Hi, > > a recent thread discussed WW2 and Sitemesh. I've got some > questions/thoughts on WW1.3 and Sitemesh. > [snip] > > What was the initial motivation to put the last executed action in the > request? > > After seeing this I

Re: [OS-webwork] Re: Include Tag

2003-07-28 Thread John Patterson
Are there really jsp implementations that use getOutputStream? How annoying. Would it be better to wrap the response in the dispatcher servlet? That way the first action could also call getWriter() or getOutputStream() before forwarding to a jsp. I was also a bit concerned about the buffering d

Re: [OS-webwork] ActionContext.getName() returning null

2003-07-28 Thread John Patterson
Yes. I created an issue yesterday. I sent this email 2 days ago and it has been floating around inside hotmail until now! - Original Message - From: "Jason Carreira" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, July 28, 2003 3:30 AM Subject: RE: [OS-webwork] ActionContext.g