You can't have a component that depends on another component of narrower
scope though - that doesn't make sense.
I'm a little on the fence on this one, the enabler interfaces seem a bit
nicer to me in some ways too, but Pico would reduce the LoC a little, and
definitely feels simpler. The thing is
BOGAERT Mathias wrote:
I've been looking at Picocontainer and Nanocontainer, and I like it.
I think it provides a better approach to IOC than the enabler interfaces
because of:
- no more enabler interface (this has a negative side also, different UML
diagrams)
- hides the component logic even more
Guys,
Please sort this one way or the other so I don't look like a total joker at
TSS describing our IoC architecture, then we flip around and use Pico :)
j/k
I've only looked at Pico briefly from Paul Hammant, and it does look good. I
kinda like the enabler interfaces personally though, they'r
I know I am a security idiot, so I can't really help you out here. But
please keep me posted with whatever you find, that way we can document it :)
-Pat
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 24, 2003 10:16 AM
Subject: [OS-webwork] SSL A
I'll be checking out pico this weekend. Joe, I expect you to be helping out
:)
- Original Message -
From: "Joe Walnes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, June 24, 2003 5:36 AM
Subject: [OS-webwork] Re: [picocontainer-dev]
Seshu,
What exactly are you trying to do? I don't understand what you mean by
"declare variables in webwork".
-Pat
- Original Message -
From: "Seshagiri Varanasi" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 23, 2003 8:06 PM
Subject: [OS-webwork] variables in Webwork
>
I would say this is a good place of Inversion of Control... Your active
data objects have to get a persistence framework reference from
somewhere, right? Personally, I would not code them directly against
Hibernate. Have them depend on a service which implements an interface,
and have your containe
Not me... It's from Patrick, Mike, and some other people.. I've been
reviewing some of the chapters though.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 24, 2003 2:04 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [OS-webwork] WebWork Getting S
*
I am double posting this on webwork's and hibernate's mailing list.
Maybe one of the hibernate guys can answer how to mock hibernate
transparently.
*
Incidentally, since my actions are fairly atomic and functionally
aligned, extracting the hibernate logic to a se
I can't imagine where that book would be coming from.
:-D
-Original Message-
From: Jason Carreira [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2003 11:57 AM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork] WebWork Getting Started Guide
Les,
You should try not to access Hibernate st
What are the general approaches for integrating SSL with WebWork? I would like a
couple of actions dealing with user authentication and administration with SSL. At
what layer do I force the web application to use an https connection? In the
deployment descriptors, in a servlet filter, in a W
Les,
You should try not to access Hibernate stuff directly in your action...
Pull it out into separate services (Stores, DAO's, whatever you want to
call them) and make them implement interfaces... Then you can mock the
interfaces and use the mocks instead... You can then know what to expect
for
I think that what you are suggesting is a better approach. Though,
having not used mock before, I need to spend some time figuring it out
-- especially figuring out how to make it transparent. In my case, I
think this may be a challenge because I have Hibernate references in my
actions. So, I hav
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> --
> I actually want to move to mockobjects, however I have not
> had the time yet to figure out how to use them seemlessly in
> leu of Hibernate. Essentially, I would like to find a way to
> make the substitu
Jason Carreira wrote:
Well, I've heard nothing but good things about your code, Joe, so how
about we make a deal? You come and put Pico/Nano into Xwork, and we'll
try to pull you in to help with other stuff too :-)
Seriously, I love the idea of replacing the IoC stuff in Xwork with
Picocontainer.
Well, I've heard nothing but good things about your code, Joe, so how
about we make a deal? You come and put Pico/Nano into Xwork, and we'll
try to pull you in to help with other stuff too :-)
Seriously, I love the idea of replacing the IoC stuff in Xwork with
Picocontainer.
One question I was w
IMO we should migrate Xwork.
Of course :).
FWIW, Nano already supports WebWork 1. Should be easy to port to
XWork/WW2. It is also very useful outside the scope of web projects.
-joe (author of original IoC stuff in WW2 - if you care) ;)
-
Guys,
I've been looking at Picocontainer and Nanocontainer, and I like it.
I think it provides a better approach to IOC than the enabler interfaces
because of:
- no more enabler interface (this has a negative side also, different UML
diagrams)
- hides the component logic even more
- no more sette
18 matches
Mail list logo
