Hi David - list: Sure, you can add as mny as you want. The first one that can satisfy the request marks it and thechain ends... Nice, cause every Resolver does one task (separation of concerns) That is also why you found so many ELResolvers floating around... regards Alexander
________________________________ From: David Steinkopff [mailto:[EMAIL PROTECTED] Sent: Thursday, May 31, 2007 10:19 AM To: MyFaces Discussion Subject: Re: What change with JSF 1.1 to JSF 1.2? Hi Alexander, I prefer more to decorat, becauce I need only some PropertyResolver methods. ELResolver works like PropertyResolver and VariableResolver together and to implement both is more as I needed in my case. What do you mean with list? It is possible to add more than one resolver? regards David 2007/5/31, Jesse Alexander (KSFD 121) < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >: As Adam I recommend to rewrite to the ELResolvers, if you do not absolutely need the backward compatibility. As for writing or decorating... With the ELResolver the handling is very easy when you start from scratch (== not decorating). And then you just add your ELResolver to the list... regards Alexander ________________________________ From: David Steinkopff [mailto:[EMAIL PROTECTED] Sent: Thursday, May 31, 2007 9:00 AM To: MyFaces Discussion Subject: Re: What change with JSF 1.1 to JSF 1.2? Hi, I dont need all features of ELResolvers, for me only important is setValue, getValue and maybe isReadonly to connect a custom data system. In this way was PropertyResolver more than enough for me. JSF 1.1 have only one implementation of PropertyResolver and JSF 1.2 have with ELResolver more than one. Which implementation I can use for a decorator or what implementation is common standard in JSF 1.2? Regards David 2007/5/30, Adam Winer < [EMAIL PROTECTED]>: FYI, I strongly recommend that developers who are moving up to JSF 1.2 rewrite PropertyResolvers and VariableResolvers as ELResolvers. Backwards compatibility for registered (programatic or via faces-config.xml ) VariableResolver and PropertyResolvers has been a major nightmare for the reference implementation, and I'd be amazed if MyFaces 1.2 didn't have some bugs here. And, even if it's perfect, there's a slight performance hit associated with using legacy EL APIs. -- Adam On 5/30/07, Jesse Alexander (KSFD 121) < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: > > > The PropertyResolver is ONLY DEPRECATED. It still can be accessed, although > a compiler might throw warnings.... > > regards > Alexander > > ________________________________ > From: David Steinkopff [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 30, 2007 11:04 AM > To: MyFaces Discussion > Subject: Re: What change with JSF 1.1 to JSF 1.2? > > > Hi Martin, > > current is my PropertyResolver a decorator of the PropertyResolverImpl from > MyFaces. Would it neccessary to wright a new decorator for the ELResolver > implementation? Or I can use the PropertyResolver in JSF 1.2 in face of > deprecated? > > Regards > David > > > 2007/5/30, Martin Marinschek < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >: > > It _should_ work out of the box - everything else would be a bug. Also > > the property-resolver should work, it would be integrated into the > > el-resolver-chain... > > > > regards, > > > > Martin > > > > On 5/30/07, David Steinkopff < [EMAIL PROTECTED]> wrote: > > > Hello, > > > > > > I ´m reading interested in this mailing list and I see that JSF 1.2 > > > implementation from MyFaces is coming soon. > > > Now I ask me the question, what changes must I attend if I immigrate a > JSF > > > 1.1 application with own PropertyResolver and PhaseListener? > > > > > > regards > > > David > > > > > > > > > -- > > > > http://www.irian.at > > > > Your JSF powerhouse - > > JSF Consulting, Development and > > Courses in English and German > > > > Professional Support for Apache MyFaces > > > >
