You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by bu...@apache.org on 2004/04/05 13:51:04 UTC
DO NOT REPLY [Bug 27956] -
ApplicationRuntimeException is thrown when the jdk dependend validation of abstract methods fails
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27956>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27956
ApplicationRuntimeException is thrown when the jdk dependend validation of abstract methods fails
------- Additional Comments From Michael.Frericks@web.de 2004-04-05 11:51 -------
Sorry, no. It is an non-abstract, implementation providing method of an abstract
class that is categorized abstract.
Even methods of tapestry-framework classes
(e.g org.apache.tapestry.form.Form) are addressed
this way.
It seems to be a 'bug' of the ibm-jdk-1.3.1 because
they do not simply deliver the method modifiers. Instead
they seem to mix the modifiers of the class and the method.
Cant find a hint that this violates the words of the java spec.
But since most websphere (4.x) installations
will use this ibm-jdk there is a problem using
tapestry-3.0 and websphere together.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org