I agree with you. On Sat, Jan 17, 2009 at 9:20 AM, Gurkan Erdogdu <[email protected]> wrote: > I think, if he like to use openwebbeans in his application then he has to > configure the Security Manager,if exist, to use its functionality. Because > using of the setAccessible(true) first asks to SecurityManager to do its job. > > /Gurkan > > > > > ________________________________ > From: Mohammad Nour El-Din <[email protected]> > To: [email protected] > Sent: Friday, January 16, 2009 7:08:14 PM > Subject: Re: btw, I found a mail about field injection vs setter injection > > IMO using the field injection may have some problems regarding > security if it is configured in the JVM upon which the code is > running > > On Thu, Jan 15, 2009 at 11:33 PM, Mark Struberg <[email protected]> wrote: >> Hi Gurkan! >> >> I today found a mail from Gavin which expresses what I liked to explain >> yesterday - if I wouldn't have been so confused late night ;) >> >>> However, it raises the issue of how we would distinguish setter >>> injection from field injection in the XML. Does: >>> >>> <my:foo>...</my:foo> >>> >>> represent the field "foo" or the setter "setFoo()"? Or should >>> property injection look like: <my:setFoo>...</my:setFoo> ... >> >> But the discussion on this point did not continue. >> >> For the time being I'm completely happy as you made it: loodup a setter, if >> none found lookup the field. >> >> >> LieGrue, >> strub >> >> >> >> >> >> > > > > -- > ---- > Thanks > - Mohammad Nour > - LinkedIn: http://www.linkedin.com/in/mnour > ---- > "Life is like riding a bicycle. To keep your balance you must keep moving" > - Albert Einstein > > > >
-- ---- Thanks - Mohammad Nour - LinkedIn: http://www.linkedin.com/in/mnour ---- "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein
