[OS-webwork] Xwork IoC requirements

2003-07-11 Thread Jason Carreira
I'm starting a list of requirements for an IoC container in Xwork. Here's what I've got so far: 1) Ability to have nested component scopes (Application - HTTP Session - HTTP Request - Action Invocation) 2) Ability to resolve component dependencies and create components with dependencies fulfilled

Re: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Hani Suleiman
Or just roll your own! On Friday, July 11, 2003, at 10:24 AM, Jason Carreira wrote: I'm starting a list of requirements for an IoC container in Xwork. Here's what I've got so far: 1) Ability to have nested component scopes (Application - HTTP Session - HTTP Request - Action Invocation) 2)

Re: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Konstantin Priblouda
--- Jason Carreira [EMAIL PROTECTED] wrote: I'm starting a list of requirements for an IoC container in Xwork. Here's what I've got so far: 1) Ability to have nested component scopes (Application - HTTP Session - HTTP Request - Action Invocation) AFAIK, xwork shoid be web-agnostik, or

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Jason Carreira
We already had our own... But should I take this as you volunteering? :-) -Original Message- From: Hani Suleiman [mailto:[EMAIL PROTECTED] Sent: Friday, July 11, 2003 10:31 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Xwork IoC requirements Or just roll your own!

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Jason Carreira
-Original Message- From: Konstantin Priblouda [mailto:[EMAIL PROTECTED] Sent: Friday, July 11, 2003 10:33 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Xwork IoC requirements --- Jason Carreira [EMAIL PROTECTED] wrote: I'm starting a list of requirements for an IoC

Re: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Hani Suleiman
What! I'm too busy blaming everyone and everything to write any code anymore! My vote (as a dedicated xw/ww non-user) goes to keeping the homebrewn stuff. pico is neat, but not amazing enough for everyone to have to live through the yet-another-dependency shock syndrome. On Friday, July 11,

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Konstantin Priblouda
1) Ability to have nested component scopes (Application - HTTP Session - HTTP Request - Action Invocation) AFAIK, xwork shoid be web-agnostik, or what's puprose of splitting ww2 / xwork? Yes, they should. But that doesn't mean nested component scopes isn't a requirement, as

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread BOGAERT Mathias
For the issue mentioned below, we should not use HttpSessionListener, but use HttpSessionBindingListener ( http://java.sun.com/products/servlet/2.3/javadoc/javax/servlet/http/HttpSess ionBindingListener.html ). We have the DefaultComponentManager implement this, and initialize it on valueBound

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Heng Sin Low
I've actually put in a patch for this on jira a while back. --- BOGAERT Mathias [EMAIL PROTECTED] wrote: For the issue mentioned below, we should not use HttpSessionListener, but use HttpSessionBindingListener ( http://java.sun.com/products/servlet/2.3/javadoc/javax/servlet/http/HttpSess

Re: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Heng Sin Low
But there are quite a bit of overlap between spring and ww2+xwork, so if ww2 go with that, would it be to just extract the IoC stuff or just pretend the overlap and extra bagage is not there :) --- Rob Rudin [EMAIL PROTECTED] wrote: Hey Jason - I've used Spring IoC with Webwork 1.3 on two

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Jason Carreira
-Original Message- From: Heng Sin Low [mailto:[EMAIL PROTECTED] Sent: Friday, July 11, 2003 11:13 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Xwork IoC requirements But there are quite a bit of overlap between spring and ww2+xwork, so if ww2 go with that, would it be

Re: Re: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Rob Rudin
There's definitely way too much overlap - but I think Spring is distributed as a full JAR and is also separated into smaller JAR's, and I believe one of these is a core or beans JAR. When I used the book code, I removed all of the web and JDBC stuff and compiled just the config-related code into a

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread BOGAERT Mathias
Jason, Aslak just told me the pico team will reply in a lengthy wiki entry to the Spring constr fud. So please wait until we have that, and the team can decide which direction to go. BTW they are already on the re-wire issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=PICO-22 Cheers,

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread BOGAERT Mathias
On another note: Jason, what the f*ck are you talking about?? Can you explain the issue with requirement 3? If the container can be serialized, and the components too, what is the issue then? Why do you need to re-wire after serialization/deserialization? Cheers, Mathias -Original

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Jason Carreira
Yeah, they're going to comment, but not fix anything. In fact, they're pulling out the Bean Property stuff they put in: http://jira.codehaus.org/secure/ViewIssue.jspa?key=PICO-23 I created the Jira issue you linked, if you look. The last comment on it is this: Jon Tirsen [ 11/Jul/03 09:11 AM

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Jason Carreira
I'm not talking about the container. I'm talking about an Action. Lets say I create an Action in a Swing app and populate it with some data. Then I send it, serialized, to a special ClientDispatcherServlet which deserializes the Action and executes it Except it has component dependencies...

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Jason Carreira
Yeah, that's an interesting idea, except that you've just blown up Type 3 IoC. Picocontainer is all about wiring the dependencies at object creation. How do you suggest the component re-wire its own dependencies? Plus, if they did allow you to do this, which I don't think they do or ever will, it

Re: [OS-webwork] Webwork with Tiles

2003-07-11 Thread Pat Lightbody
SiteMesh should allow all of this. I don't know enough about how Tiles works, but there is nothing special going on with WebWork. So if you can use servlets with Tiles, you can use WebWork actions with Tiles. -Pat - Original Message - From: John Patterson [EMAIL PROTECTED] To: [EMAIL

Re: [OS-webwork] Decision: Xwork IoC

2003-07-11 Thread Heng Sin Low
Agreed, especially pico is still alpha/beta ware. As for the original IoC stuff, I'm not sure the enabler interface is the best approach. Would it be feasible to discover the component dependency by inspecting the object's properties ( setter ) ? --- Pat Lightbody [EMAIL PROTECTED] wrote: All,

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Brett Knights
In response to your blog: There is nothing that requires the component to re-initialize a field that has been marked as transient. If the component requires a field to be set that hasn't been it also has the option to throw a Runtime Exception. My main point when I proposed using transient as

Re: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Brock Bulger
I was reading you comments on the pico issue and thought that this was a strange use case. Why would you define an Action used by your swing app with component dependencies that had to be set in the ClientDispatcherServlet? I would think you would just proxy your data or model to a custom

Re: [OS-webwork] Decision: Xwork IoC

2003-07-11 Thread Pat Lightbody
We're going to be looking at ways to possibly get rid of the enablers. Stay tuned... -Pat - Original Message - From: Heng Sin Low [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, July 11, 2003 9:31 AM Subject: Re: [OS-webwork] Decision: Xwork IoC Agreed, especially pico is still

RE: [OS-webwork] Decision: Xwork IoC

2003-07-11 Thread Brett Knights
Agreed, especially pico is still alpha/beta ware. As for the original IoC stuff, I'm not sure the enabler interface is the best approach. Would it be feasible to discover the component dependency by inspecting the object's properties ( setter ) ? Then you don't know for sure which

Re: [OS-webwork] Webwork with Tiles

2003-07-11 Thread Matt Ho
On Fri, 11 Jul 2003 12:56:21 +0100, John Patterson [EMAIL PROTECTED] wrote: I am looking into using Webwork for an upcoming web project. In the past I have used Struts with the Tiles extension which I really liked for its page layout abilities. It seems that with Webwork most people are

Re: [OS-webwork] Decision: Xwork IoC

2003-07-11 Thread Matt Ho
On Fri, 11 Jul 2003 09:22:11 -0700, Pat Lightbody [EMAIL PROTECTED] wrote: All, After reading the incredibly long thread here and the mind-numbingly long thread in pico-dev, I've come to the following conclusion: The difference between contructors and bean properties is so small that it's

RE: [OS-webwork] Xwork IoC requirements

2003-07-11 Thread Jason Carreira
Sending a command to be executed is classic strategy / command pattern. It's good because it allows you to send the object you want to be run pre-populated... -Original Message- From: Brock Bulger [mailto:[EMAIL PROTECTED] Sent: Friday, July 11, 2003 12:35 PM To: [EMAIL PROTECTED]

Re: [OS-webwork] Serialization and Framework Dependencies

2003-07-11 Thread Matt Ho
Ignore this email. My mail reader is doing weird things :( M On Fri, 11 Jul 2003 09:53:30 -0700, Matt Ho [EMAIL PROTECTED] wrote: On Wed, 9 Jul 2003 17:17:54 -0700, Brett Knights [EMAIL PROTECTED] wrote: In the discussion so far there are two examples of things I need to do to in my

[OS-webwork] OSCore and PropertySet released

2003-07-11 Thread Pat Lightbody
The latest versions of OSCore and PropertySet have been released in preparation for the upcoming XWork, WebWork, and OSWorkflow releases (XWork/WebWork will be betas). -Pat --- This SF.Net email sponsored by: Parasoft Error proof Web apps,

Re: [OS-webwork] Webwork with Tiles

2003-07-11 Thread John Patterson
This would make the template impossible to reuse in another page that required different navigation or other areas of the page to contain different components. The problem is due to the lack of separation between the template and the specification of what should be placed in the template. With

RE: [OS-webwork] how to search this mailing list?

2003-07-11 Thread Greinke, Ross
Here's where I've been searching... http://www.mail-archive.com/opensymphony-webwork%40lists.sourceforge.net / -Original Message- From: Francisco Hernandez [mailto:[EMAIL PROTECTED] Sent: Friday, July 11, 2003 1:06 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] how to search this

Re: [OS-webwork] Webwork with Tiles

2003-07-11 Thread Pat Lightbody
SiteMesh allow for components... just use inline decorator tags. I do this all the time with form tags. If you use JIRA, any form entry field is actually a sitemesh component. Is that what you want? -Pat - Original Message - From: John Patterson [EMAIL PROTECTED] To: [EMAIL PROTECTED]

[OS-webwork] ssh access to webwork2

2003-07-11 Thread Brett Knights
Hi, Now I am behind a firewall and can't get at cvs with the :pserver protocol. I could however get in with ssh if I had a username and password. Is there an anonymous equivalent read-only user for access ssh access? Is there a place where nightly source snapshots are available on the net?