JSF2.0 ELResolver - Reflection with Javassist-Proxy

[alexanderbell]

Hi,

I've written my own ELResolver for JSF20
That ELResolver should set the bean-property via Reflection without getter/setter methods.
If I use JSF together with CDI (I use @Named insteadof @ManagedBean and so on) I get a Javassist-Proxy-Object inside my ELResolver-Methods. Afterwards I want to set the value with javax.reflect.Field.set(...).

The set of the property works without any exceptions but if I enter the action (in my JSF Bean) the property isn't set.

If I use the standard JSF annotations everything works fine.

Any ideas?

Alex

[nickarls]

Hmm, never wrote an EL resolver but could it have something to do with the proxy? Have you tried in Java SE if the proxy behaves the same way (don't know how proxies feel about field access, are they the real fields)? Tried @Dependent scoped beans which don't have proxies?

[diegocoronel]

Hi Alexander,

Can you share your EL extension? I think its really useful to build web interfaces without set/get. We always have so many gets/sets without business/logic values.

[diegocoronel]

I got a really nice alternative Lombok using this framework isnt necessary to implement any extension inside your project.

I think Seam 3 should use some of these tricks.

[agori]

The set of the property works without any exceptions but if I enter the action (in my JSF Bean) the property isn't set.

I have the same problem here. I can't read a field value using reflection.  Instead I can get values from every method using reflection.

Is this a javassist limitation?

[alexanderbell]

I restricted the reflection of my fields to JPA-entities. I haven't got many properties in my JSF Managed Beans so for my JSF Beans I wrote some getters and setters.

I'm gonna write a blog entry regarding that issue.