I am using opensaml-2.3.0 library file and tomcatapache-tomcat-5.5.28 and java 1.5.The application is working fine with this configuration. But when I am trying to use jdk1.4 I am getting the following error.Because In our server Java 1.4 is installd.
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Servlet execution threw an exception
root cause
java.lang.UnsupportedClassVersionError: org/opensaml/xml/util/Base64 (Unsupported major.minor version 49.0)
java.lang.ClassLoader.defineClass0(Native Method)
java.lang.ClassLoader.defineClass(ClassLoader.java:539)
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1634)
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:860)
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1307)
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189)
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
com.aviva.tam.pmi.SAMLToString.createSamlResponse(SAMLToString.java:53)
com.aviva.tam.pmi.SAMLToString.doPost(SAMLToString.java:129)
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
note The full stack trace of the root cause is available in the Apache Tomcat/5.0.30 logs.
Can anyone please tell me whether the Base64 class is compatible with jdk1.4 or not.
Thanks.
Pritam
I'm stuck with a similar problem. We have a Websphere application
server that is hosting other Java applications and has JDK v1.4. Now
if I need to compile the openSAML classes (Base64 class for example),
is there a way to get around the problem, without upgrading the JDK
version to 1.5 please?
Thanks,
Laks.
Given the Java 5 is already End of Life, it seems like its time to consider
upgrading anyway.
Paul
On 11/26/09 3:34 PM, "lakshmi narasimhan"
<lakshmi.na...@googlemail.com> wrote:
-----
Paul Hethmon
Chief Software Architect
Clareity Security, LLC
865.824.1350 - office
865.250.3517 - mobile
www.clareitysecurity.com
-----
God does not play dice with the universe; He plays an ineffable game of his
own devising, which might be compared, from the perspective of any of the
other players, to being involved in an obscure and complex version of poker
in a pitch dark room, with blank cards, for infinite stakes, with a dealer
who won't tell you the rules, and who smiles all the time.
-- Terry Pratchett, Good Omens
you could try to compile it with 1.4 and if it doesnt work try to port
it over, however I suppose upgrading would be easier.
Alexander
>>> lakshmi narasimhan <lakshmi.na...@googlemail.com> 26.11.2009
21:34 >>>
Paul Hethmon wrote:
> You might be able to use something like Retroweaver. I can't remember
> whether that will take care of everything or not, but it's about your only
> choice.
>
>
Yes, I believe Retroweaver, or a similar solution, should probably still
work. Some info was in this thread:
https://mail.internet2.edu/wws/arc/mace-opensaml-users/2008-05/msg00015.html
> Given the Java 5 is already End of Life, it seems like its time to consider
> upgrading anyway.
>
>
To reiterate what Paul said, since both 1.4.2 and 1.5 are now EOL, you
should really consider upgrading to Java 6. As I believe Chad recently
said back in October, when 1.5 became EOL, we don't necessarily have
plans to start using exclusive features or classes from v 6, but we now
reserve the right to do so in some future release.