<div dir="ltr">Why don't you just create a msc Service that provides VF?<br>and all other subsystems will just inject that service/VF that service provides and you are all good.<br></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Mon, Aug 26, 2013 at 6:19 PM, <span dir="ltr"><<a href="mailto:ssilvert@redhat.com" target="_blank">ssilvert@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 8/26/2013 11:52 AM, Emmanuel Bernard wrote:<br>
> On Mon 2013-08-26 11:36, <a href="mailto:ssilvert@redhat.com">ssilvert@redhat.com</a> wrote:<br>
>> On 8/26/2013 11:22 AM, Scott Marlow wrote:<br>
>>> On 08/21/2013 05:18 AM, Gunnar Morling wrote:<br>
>>>> If looking up the VF via JNDI works I think that might be a bit simpler,<br>
>>>> as no changes on the provider side would be required. Resteasy also<br>
>>>> looks up the VF via JNDI.<br>
>>> I don't think the JNDI (java:comp/ValidatorFactory) lookup would work<br>
>>> during deployment. If the VF isn't needed until post deployment time,<br>
>>> the JNDI lookup would be more likely to work (when the application<br>
>>> component context will be available).<br>
>>><br>
>>> In the case of JPA, we need the VF during deployment. I'm not sure<br>
>>> about the other (JSF/JCA) cases.<br>
>> JSF also needs the VF during deployment. So if it is provided via JNDI<br>
>> it does need to be fully intialized at that time.<br>
> That is not true. A ValidatorFactory needs to be available from JNDI<br>
> during deployment time so that the module can retrieve it (assuming that<br>
> the approach we want) and possibly access its metadata which is<br>
> unaffected by a CDI enabled VF.<br>
><br>
> But the actual CDI enabled VF does not have to be initialized for<br>
> deployment time. JPA, JSF and CDI do not need it until after the<br>
> application is fully deployed. Using a delegate approach (the famous<br>
> LazyVF delegating to a non CDI VF initially - and lazily built - and a<br>
> CDI VF later one), we should be good.<br>
</div>Well, it might depend on what you mean by "deployment time" and "fully<br>
deployed". I can't guarantee that someone won't write application<br>
initialization code that generates beans which need validation. So to<br>
be more specific, it needs to be initialized by the time<br>
ServletContextListeners run. That's the earliest that JSF would<br>
actually need to use it.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>