You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by beginner_prithvi <he...@gmail.com> on 2009/11/18 07:00:49 UTC
Re: loader constraints violated when linking javax/el/ELResolver
class error
This error comes when i add either one of the following jars:
myfaces-impl-1.1.5.jar
tomahawk-1.1.3.jar
Is there any problem in these jars?
Here is my .classpath file. How do you want me to arrange contents in it?
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path="src"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="con"
path="org.eclipse.jst.server.core.container/org.eclipse.jst.server.tomcat.runtimeTarget/Apache
Tomcat v6.0"/>
<classpathentry kind="con"
path="org.eclipse.jst.j2ee.internal.module.container"/>
<classpathentry kind="con"
path="org.eclipse.jst.j2ee.internal.web.container"/>
<classpathentry kind="output" path="build/classes"/>
</classpath>
Mike Kienenberger wrote:
>
> It's probably the el-api.jar (and possibly also el-ri.jar).
>
> Jsp 2.1 provides its own el-api (and I think perhaps el-ri as well,
> but I'm no expert on jsp -- I do all of my development in facelets).
>
> I had this "java.lang.LinkageError: loader constraints violated when
> linking javax/el/ELResolver class" problem a couple of weeks ago with
> jetty. It was followed by some class-not-found/class-cast issues,
> which turned out to be fixed by insuring that the jetty & jetty jsp
> jars were the first item in the class path.
>
>
--
View this message in context: http://old.nabble.com/loader-constraints-violated-when-linking-javax-el-ELResolver-class-error-tp26390522p26402977.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: loader constraints violated when linking javax/el/ELResolver
class error
Posted by beginner_prithvi <he...@gmail.com>.
Hi Mike,Richard,
Thank you very much for your immediate help.
Actually I was trying to use tomahawk in order to implement dynamic tabs.
I searched on the internet and found RichFaces can do this job very easily.
So instead of tomahawk now I am using RichFaces :)
@Mike,
As you said you work in facelets, I have some queries in the same and I have
posted it in facelets user forum. I will appreciate if i get some more help
from you.
@Richard,
I will appreciate your help also :)
Mike Kienenberger wrote:
>
> On Wed, Nov 18, 2009 at 1:00 AM, beginner_prithvi <he...@gmail.com>
> wrote:
>> Here is my .classpath file. How do you want me to arrange contents in it?
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <classpath>
>> <classpathentry kind="src" path="src"/>
>> <classpathentry kind="con"
>> path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>> <classpathentry kind="con"
>> path="org.eclipse.jst.server.core.container/org.eclipse.jst.server.tomcat.runtimeTarget/Apache
>> Tomcat v6.0"/>
>> <classpathentry kind="con"
>> path="org.eclipse.jst.j2ee.internal.module.container"/>
>> <classpathentry kind="con"
>> path="org.eclipse.jst.j2ee.internal.web.container"/>
>> <classpathentry kind="output" path="build/classes"/>
>> </classpath>
>
> Just a guess, but I'd say try putting Apache Tomcat v6.0 at the top.
> You might also need to put web.container up there -- maybe after
> Tomcat.
>
> Again, this helped for jetty, but might not matter for Tomcat.
> Tomcat v6 definitely contains its own el implementation, though.
>
> Removing the myfaces jars are probably only removing the calls to the
> el api. They are probably not the cause of the conflict.
>
>
--
View this message in context: http://old.nabble.com/loader-constraints-violated-when-linking-javax-el-ELResolver-class-error-tp26390522p26421292.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: loader constraints violated when linking javax/el/ELResolver
class error
Posted by Mike Kienenberger <mk...@gmail.com>.
On Wed, Nov 18, 2009 at 1:00 AM, beginner_prithvi <he...@gmail.com> wrote:
> Here is my .classpath file. How do you want me to arrange contents in it?
>
> <?xml version="1.0" encoding="UTF-8"?>
> <classpath>
> <classpathentry kind="src" path="src"/>
> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> <classpathentry kind="con"
> path="org.eclipse.jst.server.core.container/org.eclipse.jst.server.tomcat.runtimeTarget/Apache
> Tomcat v6.0"/>
> <classpathentry kind="con"
> path="org.eclipse.jst.j2ee.internal.module.container"/>
> <classpathentry kind="con"
> path="org.eclipse.jst.j2ee.internal.web.container"/>
> <classpathentry kind="output" path="build/classes"/>
> </classpath>
Just a guess, but I'd say try putting Apache Tomcat v6.0 at the top.
You might also need to put web.container up there -- maybe after
Tomcat.
Again, this helped for jetty, but might not matter for Tomcat.
Tomcat v6 definitely contains its own el implementation, though.
Removing the myfaces jars are probably only removing the calls to the
el api. They are probably not the cause of the conflict.
Re: loader constraints violated when linking javax/el/ELResolver class error
Posted by Richard Yee <ri...@gmail.com>.
Use the myfaces 1.2.x and the tomahawk 1.2 libs. Tomcat supportsxjsf 1.2
R
Sent from my iPhone
On Nov 17, 2009, at 10:00 PM, beginner_prithvi <he...@gmail.com>
wrote:
>
> This error comes when i add either one of the following jars:
> myfaces-impl-1.1.5.jar
> tomahawk-1.1.3.jar
>
> Is there any problem in these jars?
>
> Here is my .classpath file. How do you want me to arrange contents
> in it?
>
> <?xml version="1.0" encoding="UTF-8"?>
> <classpath>
> <classpathentry kind="src" path="src"/>
> <classpathentry kind="con"
> path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> <classpathentry kind="con"
> path="org.eclipse.jst.server.core.container/
> org.eclipse.jst.server.tomcat.runtimeTarget/Apache
> Tomcat v6.0"/>
> <classpathentry kind="con"
> path="org.eclipse.jst.j2ee.internal.module.container"/>
> <classpathentry kind="con"
> path="org.eclipse.jst.j2ee.internal.web.container"/>
> <classpathentry kind="output" path="build/classes"/>
> </classpath>
>
>
>
> Mike Kienenberger wrote:
>>
>> It's probably the el-api.jar (and possibly also el-ri.jar).
>>
>> Jsp 2.1 provides its own el-api (and I think perhaps el-ri as well,
>> but I'm no expert on jsp -- I do all of my development in facelets).
>>
>> I had this "java.lang.LinkageError: loader constraints violated when
>> linking javax/el/ELResolver class" problem a couple of weeks ago with
>> jetty. It was followed by some class-not-found/class-cast issues,
>> which turned out to be fixed by insuring that the jetty & jetty jsp
>> jars were the first item in the class path.
>>
>>
>
> --
> View this message in context: http://old.nabble.com/loader-constraints-violated-when-linking-javax-el-ELResolver-class-error-tp26390522p26402977.html
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>