On 1/12/06, Dennis Byrne <[EMAIL PROTECTED]> wrote:
> Perhaps a custom variable resolver could be the solution?

mmm, I like more a custom variable resolver for usecases when you
don't *define* your beans in faces-cfg. For instance when you are
using Spring framework.

But if you like to change the *creation* thing, than it might be
better to do the "managed bean factory" thing. For instance reading
values (not a configured bean) from XML file, database, or something 
like that.

-Matthias

> Dennis Byrne
>
> >-----Original Message-----
> >From: Matthias Wessendorf [mailto:[EMAIL PROTECTED]
> >Sent: Thursday, January 12, 2006 01:48 PM
> >To: 'MyFaces Development'
> >Subject: Re: managed bean creation factory
> >
> >Also possible that Adam or Manfred are listining,
> >they can bring it up, more easily, I guess :-)
> >
> >-Matthias
> >
> >On 1/12/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
> >> On 1/12/06, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
> >> > Hi!
> >> >
> >> > Are there plans in the future JSF spec to make the managed bean creation
> >> > factory configureable?
> >>
> >> http://wiki.apache.org/myfaces/FAQ:
> >>
> >> =====================================
> >> I don't like something about the JSF specification. How can I change it?
> >>
> >> Send email to [WWW] [EMAIL PROTECTED] to send your suggestion
> >> for the next version of JSF. This will be received by the JSR spec
> >> leads, and if considered reasonable will be added to the project issue
> >> tracker.
> >>
> >> Alteratively, you can add the issue directly to the issue tracker
> >> yourself. In order to do this, you must first request an Observer role
> >> with the [WWW] https://javaserverfaces-spec-public.dev.java.net
> >> project
> >> =====================================
> >>
> >
> >
> >--
> >Matthias Wessendorf
> >Zülpicher Wall 12, 239
> >50674 Köln
> >http://www.wessendorf.net
> >mwessendorf-at-gmail-dot-com
> >
>
>
>


--
Matthias Wessendorf
Zülpicher Wall 12, 239
50674 Köln
http://www.wessendorf.net
mwessendorf-at-gmail-dot-com

Reply via email to