ELResolver invocation order

[mail.micke]

Hi

I've implemented a custom ELResolver for looking up things in a static Spring application context which is used in one of our projects (we're not using the WebApplicationContext).

It seems that my ELResolver gets asked for a bunch of beans which it can't cope with.

My question is if it is possible for me to force the Seam ELResolver to do its work before mine, a means of having my ELResolver be the last in the chain?

Not a Seam specific question I know, but thought you guys might have a solution.

Many thanks,
mike

[pmuir]

Read the Javadoc for ELResolvers:

http://java.sun.com/javaee/5/docs/api/javax/el/ELResolver.html#getValue(javax.el.ELContext,%20java.lang.Object,%20java.lang.Object)

Specifically, throw a PropertyNotFoundException to make it skip to the next resolver in the chain.

[mail.micke]

Thanks,
I'll have look at it.

[mail.micke]

Had a look.

I wasn't looking for info about how an elresolver works,
I was more interested in why my Custom one gets invoked for beans which are managed by JSF/Seam.

I was hoping that my resolver would be the last one in the chain, but it doesn't seem to be.

Quick off-topic question about the PropertyNotFound exception:
Currently i just don't set the property to be resolved, and simply return null.
In your experience is it better to throw the exception?


Cheers

[pmuir]

I wasn't looking for info about how an elresolver works,

You can't write a custom resolver without understanding the API.

Currently i just don't set the property to be resolved, and simply return null.
In your experience is it better to throw the exception?

This is spec breaking, which you would know if you bothered to read the link I posted for you.

[mail.micke]

Fair enough.

[mail.micke]

FYI
Just had a look at the SeamELResolver and SpringELResolver and couldn't see any PropertyNotFound exceptions being thrown.