You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (Commented) (JIRA)" <ji...@apache.org> on 2012/01/23 11:18:42 UTC

[jira] [Commented] (OPENEJB-1063) Main-Class containing "/" instead of "." fails java.lang.NoClassDefFoundError: IllegalName:

    [ https://issues.apache.org/jira/browse/OPENEJB-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190980#comment-13190980 ] 

David Blevins commented on OPENEJB-1063:
----------------------------------------

2011-11-17 - http://svn.apache.org/viewvc?view=revision&revision=1203159 - rmannibucau

                
> Main-Class containing "/" instead of "." fails java.lang.NoClassDefFoundError: IllegalName: 
> --------------------------------------------------------------------------------------------
>
>                 Key: OPENEJB-1063
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1063
>             Project: OpenEJB
>          Issue Type: Sub-task
>    Affects Versions: 3.1.1
>         Environment: XP + Tomcat + OpenEJB 3.1.1
>            Reporter: Jean-Louis MONTEIRO
>            Assignee: Jean-Louis MONTEIRO
>             Fix For: 3.1.2
>
>
> The JAR specification isn't clear and AFAIK does not define if the main class must use "." instead of "/". 
> But, since jdk 5, Classloader seems to explicitly check if the name contains a "/". Here is an interesting link http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4986512
> Even if it's definitely an error from the jar provider, you are sometimes required to use old jars (< jdk 5) with this kind of format. 
> Since last release (3.1.1) David has changed app client deployment rules and OpenEJB doesn't fail anymore if a NoClassDefFoundError occurs without an application-client.xml descriptor.
> May be we can provide a warn if an app client module contains a bad Main-Class format and try to replace "/" by "."

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira