Gerald,
I got those auto-responses too, sometime earlier. I think I emailed admin
about it, and then I think I re-subscribed to the mailing list.
Howard
On Tue, Dec 4, 2012 at 11:03 PM, Gerald Turner wrote:
> Mark Struberg writes:
>
> > mail came through just fine
> >
> > LieGrue,
> > strub
Mark Struberg writes:
> mail came through just fine
>
> LieGrue,
> strub
>
>>
>> From: "Howard W. Smith, Jr."
>>To: MyFaces Discussion ; Mark Struberg
>>
>>Sent: Wednesday, November 21, 2012 7:07 AM
>>Subject: CODI BeanManagerProvider in @FacesConverter breaks Pr
I love and use forClass="...". Please take a look at [1] below, when you
get a chance to see all the chatter/discussion I had related to this topic.
Sometime after this topic, I tried 'again' to use @Advanced and still
didn't work. That is why I went with JSF @RequestScopedBeans that contain
'only
"Howard W. Smith, Jr." writes:
> I can confirm the same about CODI @Advanced not working in/with JSF
> @FacesConverter. My workaround (in a TomEE/CDI/MyFaces-CODI project)
> was to only add the @FacesConverter to JSF @RequestScoped managed
> beans, and they are working great in/with TomEE 1.5.1 S
Hi Gerhard, thanks for the response!
Gerhard Petracek writes:
> @codi + seam
> yes - that's possible.
> it depends on what you are using from both.
> e.g. in case of the jsf-module of codi + seam-faces you have to veto
> one of the producers for the FacesContext.
Exactly, jsf/faces modules fro
hi gerald,
@codi + seam
yes - that's possible.
it depends on what you are using from both.
e.g. in case of the jsf-module of codi + seam-faces you have to veto one of
the producers for the FacesContext.
@ "No CreationalContext registered for EL evaluation, it is likely that the
the expression fac
I can confirm the same about CODI @Advanced not working in/with JSF
@FacesConverter. My workaround (in a TomEE/CDI/MyFaces-CODI project) was to
only add the @FacesConverter to JSF @RequestScoped managed beans, and they
are working great in/with TomEE 1.5.1 SNAPSHOT.
I have been told that CODI @Adv
I just created an application from scratch, and the problem went away.
Everything working fine for now.
Sorry for this wrong alert.
- Mail original -
De : Adrian Gonzalez
À : "users@myfaces.apache.org"
Cc :
Envoyé le : Mardi 4 décembre 2012 11h32
Objet : CODI ViewAccessScoped destroy
Hello, I'm in the process of converting a JSF2/CDI application from
Seam3 to MyFaces ExtCDI/CODI. The application had been using MyFaces
ExtVal-BV so that JSR-303 cross-field validation would work in the
front-end. Simply replacing Seam3 with CODI evoked the following
stacktrace during the first
9 matches
Mail list logo
