Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » JavaServer Faces » WTP JSF now with Sun RI
WTP JSF now with Sun RI [message #471470] Thu, 09 February 2006 10:42 Go to next message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
So I created a new workspace from scratch, and included the Sun RI JSF
implementation instead of Myfaces. I copied over the two JSPs, the bean and
the faces-config.xml, everything else is recreated. In preferences for Java
Runtimes I added a definition for SDK 1.4.2.10 and removed the reference to
JRE 1.4.2.10. Now I am getting a different problem when I run the InputName
jsp. It clearly has compiled the JSP and is running it, but then it finds
some kind of incompatibility. I looked this up. As far as I can tell I
definitely only have one Java installation oin this machine : SDK 1.4.2.10
downloaded from Sun a few days ago.

HTTP Status 500 -

type Exception report
message
description The server encountered an internal error () that prevented it
from fulfilling this request.
exception
javax.servlet.ServletException: javax.servlet.jsp.JspException:
java.lang.UnsupportedClassVersionError: first/PersonBean (Unsupported
major.minor version 49.0)
org.apache.jasper.runtime.PageContextImpl.doHandlePageExcept ion(PageContextImpl.java:842) org.apache.jasper.runtime.PageContextImpl.handlePageExceptio n(PageContextImpl.java:779) org.apache.jsp.InputName_jsp._jspService(InputName_jsp.java: 103) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.ja va:94) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServl etWrapper.java:324) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServl et.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java :236) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) com.sun.faces.context.ExternalContextImpl.dispatch(ExternalC ontextImpl.java:322) com.sun.faces.application.ViewHandlerImpl.renderView(ViewHan dlerImpl.java:130) com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderRe sponsePhase.java:87) com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.ja va:200) com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.j ava:117) javax.faces.webapp.FacesServlet.service(FacesServlet.java:19 8)root causejavax.faces.el.EvaluationException: java.lang.UnsupportedClassVersionError:first/PersonBean (Unsupported major.minor version 49.0) com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl. java:206) com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl. java:154) javax.faces.component.UIOutput.getValue(UIOutput.java:147) com.sun.faces.renderkit.html_basic.HtmlBasicInputRenderer.ge tValue(HtmlBasicInputRenderer.java:82) com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.getCurr entValue(HtmlBasicRenderer.java:191) com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeE nd(HtmlBasicRenderer.java:169) javax.faces.component.UIComponentBase.encodeEnd(UIComponentB ase.java:720) javax.faces.webapp.UIComponentTag.encodeEnd(UIComponentTag.j ava:623) javax.faces.webapp.UIComponentTag.doEndTag(UIComponentTag.ja va:546) com.sun.faces.taglib.html_basic.InputTextTag.doEndTag(InputT extTag.java:524) org.apache.jsp.InputName_jsp._jspx_meth_h_inputText_0(InputN ame_jsp.java:273) org.apache.jsp.InputName_jsp._jspx_meth_h_form_0(InputName_j sp.java:221) org.apache.jsp.InputName_jsp._jspx_meth_f_view_0(InputName_j sp.java:155) org.apache.jsp.InputName_jsp._jspService(InputName_jsp.java: 92) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.ja va:94) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServl etWrapper.java:324) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServl et.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java :236) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) com.sun.faces.context.ExternalContextImpl.dispatch(ExternalC ontextImpl.java:322) com.sun.faces.application.ViewHandlerImpl.renderView(ViewHan dlerImpl.java:130) com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderRe sponsePhase.java:87) com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.ja va:200) com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.j ava:117) javax.faces.webapp.FacesServlet.service(FacesServlet.java:19 8)note The full stack trace of the root cause is available in the ApacheTomcat/5.0.30 logs.Apache Tomcat/5.0.30
Re: WTP JSF now with Sun RI [message #471471 is a reply to message #471470] Fri, 10 February 2006 08:27 Go to previous messageGo to next message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
This looks like an incompatibility between POJO classes compiled by the
Eclipse WTP 1.0 built-in compiler (Version: 3.1.1 Build id: M20050929-0840)
and JSP classes compiled at run time on Tomcat 5.0.30 by the java SDK I have
installed (Sun 1.4.2_10-b03).

Is this possible? likely?
Re: WTP JSF now with Sun RI [message #471472 is a reply to message #471471] Fri, 10 February 2006 09:34 Go to previous messageGo to next message
Yury Kats is currently offline Yury Kats
Messages: 104
Registered: July 2009
Senior Member
On 2/10/2006 8:27 AM, Chris Gage wrote:
> This looks like an incompatibility between POJO classes compiled by the
> Eclipse WTP 1.0 built-in compiler (Version: 3.1.1 Build id: M20050929-0840)
> and JSP classes compiled at run time on Tomcat 5.0.30 by the java SDK I have
> installed (Sun 1.4.2_10-b03).
>
> Is this possible? likely?

What JDK does your Eclipse use?
Re: WTP JSF now with Sun RI [message #471474 is a reply to message #471472] Fri, 10 February 2006 11:55 Go to previous messageGo to next message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
Yury,

I downloaded the SDK from Sun last week. It is 1.4.2.10. I have gone to
extremes to try and make sure it is the only SDK on this system. At one
point I had a couple of backlevel JREs (1.1.8 and 1.3) in the Oracle client
install, and one (1.4.2.2) in a reporting tool from Actuate. I removed them
all. I'm quite prepared to lose Oracle and the Actuate tool if it gets me
past this problem. I have tried to make sure there is only one copy of only
javaw.exe on the system, but even in the Sun SDK install there are two, one
in a "client" folder and one in a server "folder". Finally I also made sure
all the class files were deleted, and then did a project-->clean.

The UnsupportedClassVersionError problem still occurs. It wouldn't be so
bad if there was more information in the error. But the only information is

javax.servlet.ServletException: javax.servlet.jsp.JspException:
java.lang.UnsupportedClassVersionError: first/PersonBean (Unsupported
major.minor version 49.0)

I decide to try another tack and wrote a simple class with a main procedure
that tries to instantiate a PersonBean.

package first;
public class BeanTest {
public static void main(String[] args) {
PersonBean pb = new PersonBean("Chris");
System.out.println(pb.getUserName());
}
}

I added a constructor to PersonBean:

public PersonBean(String s) {
userName = s;
}

I saved both java source files and then ran BeanTest as a java application.
Same result:

java.lang.UnsupportedClassVersionError: first/BeanTest (Unsupported
major.minor version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoade r.java:123)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274 )
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302 )
Exception in thread "main"


WHAT IS GOING ON HERE?
Re: WTP JSF now with Sun RI [message #471475 is a reply to message #471474] Fri, 10 February 2006 12:19 Go to previous messageGo to next message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
"Chris Gage" <a@b.com> wrote in message
news:dsighd$l2e$1@utils.eclipse.org...
> Yury,
>
> I downloaded the SDK from Sun last week. It is 1.4.2.10. I have gone to
> extremes to try and make sure it is the only SDK on this system. At one
> point I had a couple of backlevel JREs (1.1.8 and 1.3) in the Oracle
> client install, and one (1.4.2.2) in a reporting tool from Actuate. I
> removed them all. I'm quite prepared to lose Oracle and the Actuate tool
> if it gets me past this problem. I have tried to make sure there is only
> one copy of only javaw.exe on the system, but even in the Sun SDK install
> there are two, one in a "client" folder and one in a server "folder".
> Finally I also made sure all the class files were deleted, and then did a
> project-->clean.
>
> The UnsupportedClassVersionError problem still occurs. It wouldn't be so
> bad if there was more information in the error. But the only information
> is
>
> javax.servlet.ServletException: javax.servlet.jsp.JspException:
> java.lang.UnsupportedClassVersionError: first/PersonBean (Unsupported
> major.minor version 49.0)
>
> I decide to try another tack and wrote a simple class with a main
> procedure that tries to instantiate a PersonBean.
>
> package first;
> public class BeanTest {
> public static void main(String[] args) {
> PersonBean pb = new PersonBean("Chris");
> System.out.println(pb.getUserName());
> }
> }
>
> I added a constructor to PersonBean:
>
> public PersonBean(String s) {
> userName = s;
> }
>
> I saved both java source files and then ran BeanTest as a java
> application. Same result:
>
> java.lang.UnsupportedClassVersionError: first/BeanTest (Unsupported
> major.minor version 49.0)
> at java.lang.ClassLoader.defineClass0(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
> at java.security.SecureClassLoader.defineClass(SecureClassLoade r.java:123)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274 )
> at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302 )
> Exception in thread "main"
>
>
> WHAT IS GOING ON HERE?
>
Re: WTP JSF now with Sun RI [message #471476 is a reply to message #471474] Fri, 10 February 2006 12:26 Go to previous messageGo to next message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
Oops, sorry for the noise post, I meant to add a small extra point. I tried
one more thing... I copied the two java source files (BeanTest and
PersonBean) to a Java project in the same workspace, and they work
correctly.
Re: WTP JSF now with Sun RI [message #471478 is a reply to message #471471] Fri, 10 February 2006 14:01 Go to previous messageGo to next message
Nitin Dahyabhai is currently offline Nitin Dahyabhai
Messages: 2133
Registered: July 2009
Senior Member
Chris Gage wrote:
> This looks like an incompatibility between POJO classes compiled by the
> Eclipse WTP 1.0 built-in compiler (Version: 3.1.1 Build id: M20050929-0840)
> and JSP classes compiled at run time on Tomcat 5.0.30 by the java SDK I have
> installed (Sun 1.4.2_10-b03).
>
> Is this possible? likely?

Yes. The version number in the class file indicates that you've
compiled it in a way that produces .class files for Java5. If the
bean's .class was compiled by Eclipse itself, check your Java
Compiler JDK Compliance preferences and make sure you limit yourself
to 1.4 or lower.

--
- Nitin


---
Nitin Dahyabhai
Eclipse WTP, IBM
Re: WTP JSF now with Sun RI [message #471482 is a reply to message #471478] Mon, 13 February 2006 08:23 Go to previous messageGo to next message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
No, that's not it, my Java compliance level under Window-->Preferences and
Java-->Compiler is already set to 1.4.
Re: WTP JSF now with Sun RI [message #471483 is a reply to message #471482] Mon, 13 February 2006 09:06 Go to previous messageGo to next message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
I went right back to the beginning and extracted WTP 1.0 and the JSF plugin
again, created the library with the SUN RI, and created the Faces JSP and
the faces-config.xml and the bean again from scratch, by cutting and pasting
from NotePad, ie trying to avoid copying any existing Eclipse metdata. The
only thing I left untouched was Sun SDK 1.4.2.10.

Same result.

My Java compliance is set to 1.4 in Eclipse. Can anyone explain why the
arcane and cryptic "major-minor" and 49.0 concepts are surfaced here? What
on earth do they mean? Is there a simple translation? What is the major
minor version supposed to be in order to work correctly?
Re: WTP JSF now with Sun RI [message #471484 is a reply to message #471483] Mon, 13 February 2006 11:57 Go to previous messageGo to next message
Eclipse User
Originally posted by: wukunlun+news.gmail.com

using:
http://www.paulsadowski.com/WSH/cmdprogs.htm
-or-
http://unxutils.sourceforge.net/
-or-
http://www.cgywin.com/
-or-
http://www.mingw.org/

"which.exe java.exe"

also look in the c:\windows or c:\windows\system32 for a java.exe file.
some jdk's like to put a copy of the java executable there to make sure that
it's in your path.

lastly, uninstall all jdk's using window's add/remove utility and then see
if you can still run a "java.exe" from the command prompt.

if so, a "java.exe -version" might be insightful.

and last, but not least, check your %PATH% for any other dangling jdk's left
in your system.

lastly, you might want to test your jsf outside of eclipse and make sure
that it works as you're currently not testing the tools but rather your
environment setup and perhaps make it work first before trying the tools.


"Chris Gage" <a@b.com> wrote in message
news:dsq3ps$rd3$1@utils.eclipse.org...
>I went right back to the beginning and extracted WTP 1.0 and the JSF plugin
>again, created the library with the SUN RI, and created the Faces JSP and
>the faces-config.xml and the bean again from scratch, by cutting and
>pasting from NotePad, ie trying to avoid copying any existing Eclipse
>metdata. The only thing I left untouched was Sun SDK 1.4.2.10.
>
> Same result.
>
> My Java compliance is set to 1.4 in Eclipse. Can anyone explain why the
> arcane and cryptic "major-minor" and 49.0 concepts are surfaced here?
> What on earth do they mean? Is there a simple translation? What is the
> major minor version supposed to be in order to work correctly?
>
Re: WTP JSF now with Sun RI [message #471485 is a reply to message #471483] Tue, 14 February 2006 10:00 Go to previous messageGo to next message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
"Chris Gage" <a@b.com> wrote in message
news:dsq3ps$rd3$1@utils.eclipse.org...
>I went right back to the beginning and extracted WTP 1.0 and the JSF plugin
>again, created the library with the SUN RI, and created the Faces JSP and
>the faces-config.xml and the bean again from scratch, by cutting and
>pasting from NotePad, ie trying to avoid copying any existing Eclipse
>metdata. The only thing I left untouched was Sun SDK 1.4.2.10.
>
> Same result.
>
> My Java compliance is set to 1.4 in Eclipse. Can anyone explain why the
> arcane and cryptic "major-minor" and 49.0 concepts are surfaced here?
> What on earth do they mean? Is there a simple translation? What is the
> major minor version supposed to be in order to work correctly?
>
Re: WTP JSF now with Sun RI [message #471486 is a reply to message #471483] Tue, 14 February 2006 10:02 Go to previous messageGo to next message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
To add the final weirdness, I created a new project and wrote a minimal
vanilla JSP using jsp:usebean. It works correctly.
Re: WTP JSF now with Sun RI [message #471487 is a reply to message #471484] Tue, 14 February 2006 10:23 Go to previous message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
These are all good suggestions, and I have already done all of them, except
the last one of trying it outside Eclipse, which will take a lot of setup
that I can't justify billing my customer for.

I will have to do without JSF now I am no longer in the comfy world of
Rational Application Developer, and however good it may be, my customer is
unwilling to spend even a fraction of the exorbitant cost of RAD, so that's
it.

Back to Servlets and JSPs
Re: WTP JSF now with Sun RI [message #589368 is a reply to message #471470] Fri, 10 February 2006 08:27 Go to previous message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
This looks like an incompatibility between POJO classes compiled by the
Eclipse WTP 1.0 built-in compiler (Version: 3.1.1 Build id: M20050929-0840)
and JSP classes compiled at run time on Tomcat 5.0.30 by the java SDK I have
installed (Sun 1.4.2_10-b03).

Is this possible? likely?
Re: WTP JSF now with Sun RI [message #589378 is a reply to message #471471] Fri, 10 February 2006 09:34 Go to previous message
Yury Kats is currently offline Yury Kats
Messages: 104
Registered: July 2009
Senior Member
On 2/10/2006 8:27 AM, Chris Gage wrote:
> This looks like an incompatibility between POJO classes compiled by the
> Eclipse WTP 1.0 built-in compiler (Version: 3.1.1 Build id: M20050929-0840)
> and JSP classes compiled at run time on Tomcat 5.0.30 by the java SDK I have
> installed (Sun 1.4.2_10-b03).
>
> Is this possible? likely?

What JDK does your Eclipse use?
Re: WTP JSF now with Sun RI [message #589395 is a reply to message #471472] Fri, 10 February 2006 11:55 Go to previous message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
Yury,

I downloaded the SDK from Sun last week. It is 1.4.2.10. I have gone to
extremes to try and make sure it is the only SDK on this system. At one
point I had a couple of backlevel JREs (1.1.8 and 1.3) in the Oracle client
install, and one (1.4.2.2) in a reporting tool from Actuate. I removed them
all. I'm quite prepared to lose Oracle and the Actuate tool if it gets me
past this problem. I have tried to make sure there is only one copy of only
javaw.exe on the system, but even in the Sun SDK install there are two, one
in a "client" folder and one in a server "folder". Finally I also made sure
all the class files were deleted, and then did a project-->clean.

The UnsupportedClassVersionError problem still occurs. It wouldn't be so
bad if there was more information in the error. But the only information is

javax.servlet.ServletException: javax.servlet.jsp.JspException:
java.lang.UnsupportedClassVersionError: first/PersonBean (Unsupported
major.minor version 49.0)

I decide to try another tack and wrote a simple class with a main procedure
that tries to instantiate a PersonBean.

package first;
public class BeanTest {
public static void main(String[] args) {
PersonBean pb = new PersonBean("Chris");
System.out.println(pb.getUserName());
}
}

I added a constructor to PersonBean:

public PersonBean(String s) {
userName = s;
}

I saved both java source files and then ran BeanTest as a java application.
Same result:

java.lang.UnsupportedClassVersionError: first/BeanTest (Unsupported
major.minor version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoade r.java:123)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274 )
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302 )
Exception in thread "main"


WHAT IS GOING ON HERE?
Re: WTP JSF now with Sun RI [message #589408 is a reply to message #471474] Fri, 10 February 2006 12:19 Go to previous message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
"Chris Gage" <a@b.com> wrote in message
news:dsighd$l2e$1@utils.eclipse.org...
> Yury,
>
> I downloaded the SDK from Sun last week. It is 1.4.2.10. I have gone to
> extremes to try and make sure it is the only SDK on this system. At one
> point I had a couple of backlevel JREs (1.1.8 and 1.3) in the Oracle
> client install, and one (1.4.2.2) in a reporting tool from Actuate. I
> removed them all. I'm quite prepared to lose Oracle and the Actuate tool
> if it gets me past this problem. I have tried to make sure there is only
> one copy of only javaw.exe on the system, but even in the Sun SDK install
> there are two, one in a "client" folder and one in a server "folder".
> Finally I also made sure all the class files were deleted, and then did a
> project-->clean.
>
> The UnsupportedClassVersionError problem still occurs. It wouldn't be so
> bad if there was more information in the error. But the only information
> is
>
> javax.servlet.ServletException: javax.servlet.jsp.JspException:
> java.lang.UnsupportedClassVersionError: first/PersonBean (Unsupported
> major.minor version 49.0)
>
> I decide to try another tack and wrote a simple class with a main
> procedure that tries to instantiate a PersonBean.
>
> package first;
> public class BeanTest {
> public static void main(String[] args) {
> PersonBean pb = new PersonBean("Chris");
> System.out.println(pb.getUserName());
> }
> }
>
> I added a constructor to PersonBean:
>
> public PersonBean(String s) {
> userName = s;
> }
>
> I saved both java source files and then ran BeanTest as a java
> application. Same result:
>
> java.lang.UnsupportedClassVersionError: first/BeanTest (Unsupported
> major.minor version 49.0)
> at java.lang.ClassLoader.defineClass0(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
> at java.security.SecureClassLoader.defineClass(SecureClassLoade r.java:123)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274 )
> at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302 )
> Exception in thread "main"
>
>
> WHAT IS GOING ON HERE?
>
Re: WTP JSF now with Sun RI [message #589418 is a reply to message #471474] Fri, 10 February 2006 12:26 Go to previous message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
Oops, sorry for the noise post, I meant to add a small extra point. I tried
one more thing... I copied the two java source files (BeanTest and
PersonBean) to a Java project in the same workspace, and they work
correctly.
Re: WTP JSF now with Sun RI [message #589431 is a reply to message #471471] Fri, 10 February 2006 14:01 Go to previous message
Nitin Dahyabhai is currently offline Nitin Dahyabhai
Messages: 2133
Registered: July 2009
Senior Member
Chris Gage wrote:
> This looks like an incompatibility between POJO classes compiled by the
> Eclipse WTP 1.0 built-in compiler (Version: 3.1.1 Build id: M20050929-0840)
> and JSP classes compiled at run time on Tomcat 5.0.30 by the java SDK I have
> installed (Sun 1.4.2_10-b03).
>
> Is this possible? likely?

Yes. The version number in the class file indicates that you've
compiled it in a way that produces .class files for Java5. If the
bean's .class was compiled by Eclipse itself, check your Java
Compiler JDK Compliance preferences and make sure you limit yourself
to 1.4 or lower.

--
- Nitin


---
Nitin Dahyabhai
Eclipse WTP, IBM
Re: WTP JSF now with Sun RI [message #589465 is a reply to message #471478] Mon, 13 February 2006 08:23 Go to previous message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
No, that's not it, my Java compliance level under Window-->Preferences and
Java-->Compiler is already set to 1.4.
Re: WTP JSF now with Sun RI [message #589472 is a reply to message #471482] Mon, 13 February 2006 09:06 Go to previous message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
I went right back to the beginning and extracted WTP 1.0 and the JSF plugin
again, created the library with the SUN RI, and created the Faces JSP and
the faces-config.xml and the bean again from scratch, by cutting and pasting
from NotePad, ie trying to avoid copying any existing Eclipse metdata. The
only thing I left untouched was Sun SDK 1.4.2.10.

Same result.

My Java compliance is set to 1.4 in Eclipse. Can anyone explain why the
arcane and cryptic "major-minor" and 49.0 concepts are surfaced here? What
on earth do they mean? Is there a simple translation? What is the major
minor version supposed to be in order to work correctly?
Re: WTP JSF now with Sun RI [message #589482 is a reply to message #471483] Mon, 13 February 2006 11:57 Go to previous message
Eclipse User
Originally posted by: wukunlun+news.gmail.com

using:
http://www.paulsadowski.com/WSH/cmdprogs.htm
-or-
http://unxutils.sourceforge.net/
-or-
http://www.cgywin.com/
-or-
http://www.mingw.org/

"which.exe java.exe"

also look in the c:\windows or c:\windows\system32 for a java.exe file.
some jdk's like to put a copy of the java executable there to make sure that
it's in your path.

lastly, uninstall all jdk's using window's add/remove utility and then see
if you can still run a "java.exe" from the command prompt.

if so, a "java.exe -version" might be insightful.

and last, but not least, check your %PATH% for any other dangling jdk's left
in your system.

lastly, you might want to test your jsf outside of eclipse and make sure
that it works as you're currently not testing the tools but rather your
environment setup and perhaps make it work first before trying the tools.


"Chris Gage" <a@b.com> wrote in message
news:dsq3ps$rd3$1@utils.eclipse.org...
>I went right back to the beginning and extracted WTP 1.0 and the JSF plugin
>again, created the library with the SUN RI, and created the Faces JSP and
>the faces-config.xml and the bean again from scratch, by cutting and
>pasting from NotePad, ie trying to avoid copying any existing Eclipse
>metdata. The only thing I left untouched was Sun SDK 1.4.2.10.
>
> Same result.
>
> My Java compliance is set to 1.4 in Eclipse. Can anyone explain why the
> arcane and cryptic "major-minor" and 49.0 concepts are surfaced here?
> What on earth do they mean? Is there a simple translation? What is the
> major minor version supposed to be in order to work correctly?
>
Re: WTP JSF now with Sun RI [message #589492 is a reply to message #471483] Tue, 14 February 2006 10:00 Go to previous message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
"Chris Gage" <a@b.com> wrote in message
news:dsq3ps$rd3$1@utils.eclipse.org...
>I went right back to the beginning and extracted WTP 1.0 and the JSF plugin
>again, created the library with the SUN RI, and created the Faces JSP and
>the faces-config.xml and the bean again from scratch, by cutting and
>pasting from NotePad, ie trying to avoid copying any existing Eclipse
>metdata. The only thing I left untouched was Sun SDK 1.4.2.10.
>
> Same result.
>
> My Java compliance is set to 1.4 in Eclipse. Can anyone explain why the
> arcane and cryptic "major-minor" and 49.0 concepts are surfaced here?
> What on earth do they mean? Is there a simple translation? What is the
> major minor version supposed to be in order to work correctly?
>
Re: WTP JSF now with Sun RI [message #589503 is a reply to message #471483] Tue, 14 February 2006 10:02 Go to previous message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
To add the final weirdness, I created a new project and wrote a minimal
vanilla JSP using jsp:usebean. It works correctly.
Re: WTP JSF now with Sun RI [message #596524 is a reply to message #471484] Tue, 14 February 2006 10:23 Go to previous message
Chris Gage is currently offline Chris Gage
Messages: 26
Registered: July 2009
Junior Member
These are all good suggestions, and I have already done all of them, except
the last one of trying it outside Eclipse, which will take a lot of setup
that I can't justify billing my customer for.

I will have to do without JSF now I am no longer in the comfy world of
Rational Application Developer, and however good it may be, my customer is
unwilling to spend even a fraction of the exorbitant cost of RAD, so that's
it.

Back to Servlets and JSPs
Previous Topic:JSF plugin
Next Topic:WTP JSF with MyFaces
Goto Forum:
  


Current Time: Sun Apr 20 02:51:38 EDT 2014

Powered by FUDForum. Page generated in 0.03214 seconds