Using JBoss EL standalone with RIchFaces

[thomasgo]

Hi,

I know this is probably the wron forum to post this question, but I could not open a new topic in the Seam Users section.

I want to use JBoss EL in our RichFaces app without the rest of seam, i.e. standalone.

I found this topic: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4075986#4075986
but I didn't find any el-ri.jar in my lib directories.

Is there any configuration needed to use jboss-el.jar instead of the standard el?

Thanks.

Thomas

[amitev]

el-api.jar comes bundled within the JBoss application server but you could also find it in the https://facelets.dev.java.net/servlets/ProjectDocumentList.

Let us know if you need more tip.s

[thomasgo]

Thanks for your reply. Yes, I saw the el-api.jar in the lib directory, but the thread I linked said I should keep el-api.jar and replace el-ri.jar with jboss-el.jar. The problem is, however, that I could not find that el-ri.jar.

I suppose I have to register Jboss EL in another way to make it work, don't I?
Just putting it into the classpath isn't sufficient.

[nbelaevski]

Hi,

What is your application server?

[thomasgo]

JBoss 4.2.3.GA.
I modified the "default" server.

[nbelaevski]

JBoss already contains EL implementation (that's what el-ri is for), so it should be enough to put jboss-el.jar into application classpath.

[thomasgo]

That's what I tried, but it doesn't seem to work.

At least I get errors when trying to use value expressions thathave parameters, e.g. <h:graphicsImage value="#{SomeBean.image('image.jpg')}"/>.

At first I added Seam completely to the classpath, registered the Seam listener within my web.xml and configured seam using a components.xml.
With this setup it worked.

However, I can't use Seam for the current project, since we don't have enough knowledge yet and we haven't enough time left to start learning how to use Seam as a whole. So I'd like to reduce dependencies and possible spots of failure for the current project and just integrate JBoss EL since this seems to be capable of running as a standalone library.

[nbelaevski]

Simply adding jboss-el really didn't change anything for my example.
You can implement your own ApplicationFactory analogous to org.jboss.seam.jsf.SeamApplicationFactory and use it as a workaround or consult JBoss AS forum for help.

[thomasgo]

OK, thanks. I'll try it again in the Seam forum or in the JBoss AS forum. I hope I can add topics there ;) .