[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
[ https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672560#action_12672560 ] Frank Meilinger commented on GERONIMO-4251: --- Hi Ivan, I've done some tests and now everything works like it should. Just a note about our usecase: Now we are able to deploy our JEE5 application EAR with a lot of skinny WARs and EJBs and Webstart-Clients without any change and without application server specific deployment descriptors on Geronimo and Glassfish. This is real platform neutrality. Now we are going to test some other application servers (open source and commercial) and we hope that we are able to support a lot of different appservers in future with the exact same EAR. For JEE application developers this is a nice goal. Usually the most JEE applications nowadays are project development and target a specific appserver implementation which usually result in some appserver specific applications. We want do do product development for JEE and don't want to care about the appserver implementation the customer choose. We think, if this will be more and more possible it will also help JEE to get more popular. Thanks a lot for your good work. Greetings, Frank Class-Path entry in WAR manifest didn't work if entry is a directory Key: GERONIMO-4251 URL: https://issues.apache.org/jira/browse/GERONIMO-4251 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Environment: Geronimo 2.1.2 on Windows XP Reporter: Frank Meilinger Assignee: Ivan Fix For: 2.1.4, 2.2 Attachments: Geronimo-4251.patch, geronimo-deployment-2.2-SNAPSHOT.jar, my-ear-1.0-SNAPSHOT.ear Hi, it's not possible to define an Class-Path element in the WARs manifest, if it's a directory. I try to access jar files packed in the EARs lib/ directory from within a WAR module. e.g. this will work: Class-Path: a.jar b.jar but this doesn't work: Class-Path: lib/ If a directory is specifyed, I receive the following error: 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ org.apache.geronimo.common.DeploymentException: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ at org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath (DeploymentContext.java:419) ... I think this is definitely an error because the JEE5 specification section 8.2.1 explicitely allows directories in manifest Class-Path entries. See discussion: http://www.nabble.com/EAR-bundle-dir-classpath-issue-tt18982334s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
[ https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672615#action_12672615 ] Ivan commented on GERONIMO-4251: Hi, Frank, Glad to hear that. I think that your wish is also our aim. And I am sure that Geronimo will be better with the help from guys like you. Thanks! Ivan Class-Path entry in WAR manifest didn't work if entry is a directory Key: GERONIMO-4251 URL: https://issues.apache.org/jira/browse/GERONIMO-4251 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Environment: Geronimo 2.1.2 on Windows XP Reporter: Frank Meilinger Assignee: Ivan Fix For: 2.1.4, 2.2 Attachments: Geronimo-4251.patch, geronimo-deployment-2.2-SNAPSHOT.jar, my-ear-1.0-SNAPSHOT.ear Hi, it's not possible to define an Class-Path element in the WARs manifest, if it's a directory. I try to access jar files packed in the EARs lib/ directory from within a WAR module. e.g. this will work: Class-Path: a.jar b.jar but this doesn't work: Class-Path: lib/ If a directory is specifyed, I receive the following error: 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ org.apache.geronimo.common.DeploymentException: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ at org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath (DeploymentContext.java:419) ... I think this is definitely an error because the JEE5 specification section 8.2.1 explicitely allows directories in manifest Class-Path entries. See discussion: http://www.nabble.com/EAR-bundle-dir-classpath-issue-tt18982334s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
[ https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672806#action_12672806 ] Jarek Gawor commented on GERONIMO-4251: --- Ivan, The patch looks good to me but it would be good to have a test case for this first. Can you create and submit such test case? Class-Path entry in WAR manifest didn't work if entry is a directory Key: GERONIMO-4251 URL: https://issues.apache.org/jira/browse/GERONIMO-4251 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Environment: Geronimo 2.1.2 on Windows XP Reporter: Frank Meilinger Assignee: Jarek Gawor Fix For: 2.1.4, 2.2 Attachments: Geronimo-4251.patch, geronimo-deployment-2.2-SNAPSHOT.jar, my-ear-1.0-SNAPSHOT.ear Hi, it's not possible to define an Class-Path element in the WARs manifest, if it's a directory. I try to access jar files packed in the EARs lib/ directory from within a WAR module. e.g. this will work: Class-Path: a.jar b.jar but this doesn't work: Class-Path: lib/ If a directory is specifyed, I receive the following error: 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ org.apache.geronimo.common.DeploymentException: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ at org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath (DeploymentContext.java:419) ... I think this is definitely an error because the JEE5 specification section 8.2.1 explicitely allows directories in manifest Class-Path entries. See discussion: http://www.nabble.com/EAR-bundle-dir-classpath-issue-tt18982334s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
[ https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669664#action_12669664 ] David Jencks commented on GERONIMO-4251: Someone needs to look at the spec again my recollection is that relative urls are relative to the location of the module in the ear. So if your module is at the ear root relative and absolute mean the same thing but if your module is at /foo/bar/myModule.jar then ../baz/myLib.jar would be the same as /foo/baz/myLib.jar Class-Path entry in WAR manifest didn't work if entry is a directory Key: GERONIMO-4251 URL: https://issues.apache.org/jira/browse/GERONIMO-4251 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Environment: Geronimo 2.1.2 on Windows XP Reporter: Frank Meilinger Assignee: Ivan Fix For: 2.1.4, 2.2 Attachments: Geronimo-4251.patch Hi, it's not possible to define an Class-Path element in the WARs manifest, if it's a directory. I try to access jar files packed in the EARs lib/ directory from within a WAR module. e.g. this will work: Class-Path: a.jar b.jar but this doesn't work: Class-Path: lib/ If a directory is specifyed, I receive the following error: 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ org.apache.geronimo.common.DeploymentException: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ at org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath (DeploymentContext.java:419) ... I think this is definitely an error because the JEE5 specification section 8.2.1 explicitely allows directories in manifest Class-Path entries. See discussion: http://www.nabble.com/EAR-bundle-dir-classpath-issue-tt18982334s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
[ https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669610#action_12669610 ] Ivan commented on GERONIMO-4251: Thanks, Frank One thing I want to confirm is that whether all the entries in the class-path be relative URLs, which means /myLibs and /x/aDirectory in your example should be something like myLibs and x/aDirectory ? Class-Path entry in WAR manifest didn't work if entry is a directory Key: GERONIMO-4251 URL: https://issues.apache.org/jira/browse/GERONIMO-4251 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Environment: Geronimo 2.1.2 on Windows XP Reporter: Frank Meilinger Assignee: Ivan Fix For: 2.1.4, 2.2 Hi, it's not possible to define an Class-Path element in the WARs manifest, if it's a directory. I try to access jar files packed in the EARs lib/ directory from within a WAR module. e.g. this will work: Class-Path: a.jar b.jar but this doesn't work: Class-Path: lib/ If a directory is specifyed, I receive the following error: 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ org.apache.geronimo.common.DeploymentException: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ at org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath (DeploymentContext.java:419) ... I think this is definitely an error because the JEE5 specification section 8.2.1 explicitely allows directories in manifest Class-Path entries. See discussion: http://www.nabble.com/EAR-bundle-dir-classpath-issue-tt18982334s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
[ https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669616#action_12669616 ] Frank Meilinger commented on GERONIMO-4251: --- Hi Ivan, Yes. I think the path / means the root of the ear-file. So I think you are right, the directory /myLibs should have the same meaning as the directory name myLibs becaue the current directory makes sense to be the root of the acual ear-file. example of ear-file structure: / /lib /META-INF /myLibs In this sample, an class-path entry of myLibs should be the same as /myLibs because / is the root of the ear. Greetings, Frank Class-Path entry in WAR manifest didn't work if entry is a directory Key: GERONIMO-4251 URL: https://issues.apache.org/jira/browse/GERONIMO-4251 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Environment: Geronimo 2.1.2 on Windows XP Reporter: Frank Meilinger Assignee: Ivan Fix For: 2.1.4, 2.2 Hi, it's not possible to define an Class-Path element in the WARs manifest, if it's a directory. I try to access jar files packed in the EARs lib/ directory from within a WAR module. e.g. this will work: Class-Path: a.jar b.jar but this doesn't work: Class-Path: lib/ If a directory is specifyed, I receive the following error: 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ org.apache.geronimo.common.DeploymentException: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ at org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath (DeploymentContext.java:419) ... I think this is definitely an error because the JEE5 specification section 8.2.1 explicitely allows directories in manifest Class-Path entries. See discussion: http://www.nabble.com/EAR-bundle-dir-classpath-issue-tt18982334s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
[ https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669850#action_12669850 ] Ivan commented on GERONIMO-4251: Thanks, David. From my view, Geronimo behaviors correctly, it does handle those URLs relative to the module, not the ear root directory. I will post an example that I used to test this patch, and the updated geronimo-deployment.jar file. If anyone has time, please help to reivew it. Class-Path entry in WAR manifest didn't work if entry is a directory Key: GERONIMO-4251 URL: https://issues.apache.org/jira/browse/GERONIMO-4251 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Environment: Geronimo 2.1.2 on Windows XP Reporter: Frank Meilinger Assignee: Ivan Fix For: 2.1.4, 2.2 Attachments: Geronimo-4251.patch Hi, it's not possible to define an Class-Path element in the WARs manifest, if it's a directory. I try to access jar files packed in the EARs lib/ directory from within a WAR module. e.g. this will work: Class-Path: a.jar b.jar but this doesn't work: Class-Path: lib/ If a directory is specifyed, I receive the following error: 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ org.apache.geronimo.common.DeploymentException: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ at org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath (DeploymentContext.java:419) ... I think this is definitely an error because the JEE5 specification section 8.2.1 explicitely allows directories in manifest Class-Path entries. See discussion: http://www.nabble.com/EAR-bundle-dir-classpath-issue-tt18982334s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
[ https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12665764#action_12665764 ] Ivan commented on GERONIMO-4251: I would like work on it, for some reason, I have no access right to the JEE 1.5 specification. So the right behavior is to add all the files ended with jar in the directory to the classpath, right ? Thanks ! Class-Path entry in WAR manifest didn't work if entry is a directory Key: GERONIMO-4251 URL: https://issues.apache.org/jira/browse/GERONIMO-4251 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Environment: Geronimo 2.1.2 on Windows XP Reporter: Frank Meilinger Fix For: 2.1.4, 2.2 Hi, it's not possible to define an Class-Path element in the WARs manifest, if it's a directory. I try to access jar files packed in the EARs lib/ directory from within a WAR module. e.g. this will work: Class-Path: a.jar b.jar but this doesn't work: Class-Path: lib/ If a directory is specifyed, I receive the following error: 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ org.apache.geronimo.common.DeploymentException: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ at org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath (DeploymentContext.java:419) ... I think this is definitely an error because the JEE5 specification section 8.2.1 explicitely allows directories in manifest Class-Path entries. See discussion: http://www.nabble.com/EAR-bundle-dir-classpath-issue-tt18982334s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
[ https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12665779#action_12665779 ] Ivan commented on GERONIMO-4251: Thanks, actually I know the link to the JEE5 specification, but due to the special reason, I can not read that doc ;-( So I have to confirm with you what the correct behavior is. Class-Path entry in WAR manifest didn't work if entry is a directory Key: GERONIMO-4251 URL: https://issues.apache.org/jira/browse/GERONIMO-4251 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Environment: Geronimo 2.1.2 on Windows XP Reporter: Frank Meilinger Fix For: 2.1.4, 2.2 Hi, it's not possible to define an Class-Path element in the WARs manifest, if it's a directory. I try to access jar files packed in the EARs lib/ directory from within a WAR module. e.g. this will work: Class-Path: a.jar b.jar but this doesn't work: Class-Path: lib/ If a directory is specifyed, I receive the following error: 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ org.apache.geronimo.common.DeploymentException: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ at org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath (DeploymentContext.java:419) ... I think this is definitely an error because the JEE5 specification section 8.2.1 explicitely allows directories in manifest Class-Path entries. See discussion: http://www.nabble.com/EAR-bundle-dir-classpath-issue-tt18982334s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
[ https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12665775#action_12665775 ] Frank Meilinger commented on GERONIMO-4251: --- Hi Ivan, right! This should be the right beavior. You may download the JEE 5 specification at http://jcp.org/aboutJava/communityprocess/final/jsr244/index.html The name of the document is: javaee-5_0-fr-spec.pdf But here is a copy of the relevant section (of special interest here is point 2.): EE.8.2.1Bundled Libraries Libraries bundled with an application may be referenced in the following ways: 1. A JAR format file (such as a .jar file, .war file, or .rar file) may reference a .jar file or directory by naming the referenced .jar file or directory in a Class-Path header in the referencing JAR file's Manifest file. The referenced .jar file or directory is named using a URL relative to the URL of the refer- encing JAR file. The Manifest file is named META-INF/MANIFEST.MF in the JAR file. The Class-Path entry in the Manifest file is of the form Class-Path: list-of-jar-files-or-directories-separated-by-spaces The Java EE deployment tools must process all such referenced files and directories when processing a Java EE module. Any deployment descriptors in referenced .jar files must be ignored when processing the referencing .jar file. The deployment tool must install the .jar files and directories in a way that preserves the relative references between the files. Typically this is done by installing the .jar files into a directory hierarchy that matches the original application directory hierarchy. All referenced .jar files or directories must appear in the logical class path of the referencing JAR files at runtime. Only JAR format files or directories containing class files or resources to be loaded directly by a standard class loader should be the target of a Class-Path reference; such files are always named with a .jar extension. Top level JAR files that are processed by a deployment tool should not contain Class-Path entries; such entries would, by definition, reference other files external to the deployment unit. A deployment tool is not required to process such external references. 2. A .ear file may contain a directory that contains libraries packaged in JAR files. The library-directory element of the .ear file's deployment descriptor contains the name of this directory. If a library-directory element isn't spec- ified, or if the .ear file does not contain a deployment descriptor, the directory named lib is used. An empty library-directory element may be used to spec- ify that there is no library directory. All files in this directory (but not subdirectories) with a .jar extension must be made available to all components packaged in the EAR file, including application clients. These libraries may reference other libraries, either bun- dled with the application or installed separately, using any of the techniques described herein. 3. A web application may include libraries in the WEB-INF/lib directory. See the Servlet specification for details. These libraries may reference other libraries, either bundled with the application or installed separately, using any of the techniques described herein. hope this helps. Greetings and thanks for working on this issue, Frank Class-Path entry in WAR manifest didn't work if entry is a directory Key: GERONIMO-4251 URL: https://issues.apache.org/jira/browse/GERONIMO-4251 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Environment: Geronimo 2.1.2 on Windows XP Reporter: Frank Meilinger Fix For: 2.1.4, 2.2 Hi, it's not possible to define an Class-Path element in the WARs manifest, if it's a directory. I try to access jar files packed in the EARs lib/ directory from within a WAR module. e.g. this will work: Class-Path: a.jar b.jar but this doesn't work: Class-Path: lib/ If a directory is specifyed, I receive the following error: 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ org.apache.geronimo.common.DeploymentException: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ at
[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
[ https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12665799#action_12665799 ] Frank Meilinger commented on GERONIMO-4251: --- Hi Ivan, I've insertet a copy of the specification section. But here is a summary of my understanding: a) If an .ear file has a /lib directory, all jar files in this directory (but not subdirectories) are AUTOMATICALLY added to the classpath of all components packaged in this .ear file (ejbs, wars, rars, application clients, ...). It's not necessary to specify this /lib directory in the modules descriptor via the classpath element. The /lib directory is the default name, but the name of the directory may be changed in the .ear deployment descriptor (the library-directory element). This is described in section 2. in 8.2.1. b) Additionally and independend of a) it should be possible to specify jar files AND DIRECTORIES in the classpath element of modules deployment descriptors. e.g. In a WAR manifest the ClassPath entry should allow the following: ClassPath: a.jar b.jar /myLibs c.jar /x/aDirectory/ Which result in a classpath with includes a.jar, b.jar, all jar files in the directory /myLibs, c.jar and all jar files in the directory /x/aDirectory. This behavior is described in section 1. in 8.2.1. in the following sentence: ...The Class-Path entry in the Manifest file is of the form Class-Path: list-of-jar-files-or-directories-separated-by-spaces The Java EE deployment tools must process all such referenced files and directories when processing a Java EE module. ... Greetings, Frank Class-Path entry in WAR manifest didn't work if entry is a directory Key: GERONIMO-4251 URL: https://issues.apache.org/jira/browse/GERONIMO-4251 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2 Environment: Geronimo 2.1.2 on Windows XP Reporter: Frank Meilinger Fix For: 2.1.4, 2.2 Hi, it's not possible to define an Class-Path element in the WARs manifest, if it's a directory. I try to access jar files packed in the EARs lib/ directory from within a WAR module. e.g. this will work: Class-Path: a.jar b.jar but this doesn't work: Class-Path: lib/ If a directory is specifyed, I receive the following error: 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ org.apache.geronimo.common.DeploymentException: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ at org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath (DeploymentContext.java:419) ... I think this is definitely an error because the JEE5 specification section 8.2.1 explicitely allows directories in manifest Class-Path entries. See discussion: http://www.nabble.com/EAR-bundle-dir-classpath-issue-tt18982334s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4251) Class-Path entry in WAR manifest didn't work if entry is a directory
[ https://issues.apache.org/jira/browse/GERONIMO-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12635734#action_12635734 ] Frank Meilinger commented on GERONIMO-4251: --- Hi, Geronimo 2.1.3 has still this problem. Without solving this problem, Geronimo violates the JEE 5 standard and makes it impossible to wirte portable EAR's which includes skinny WAR's while relying on the new JEE 5 feature Bundled Libraries. Please fix this it's important. Until now, I have not found a workaround. Greetings, Frank Class-Path entry in WAR manifest didn't work if entry is a directory Key: GERONIMO-4251 URL: https://issues.apache.org/jira/browse/GERONIMO-4251 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.1.2 Environment: Geronimo 2.1.2 on Windows XP Reporter: Frank Meilinger Hi, it's not possible to define an Class-Path element in the WARs manifest, if it's a directory. I try to access jar files packed in the EARs lib/ directory from within a WAR module. e.g. this will work: Class-Path: a.jar b.jar but this doesn't work: Class-Path: lib/ If a directory is specifyed, I receive the following error: 15:20:13,170 ERROR [DirectoryHotDeployer] Unable to deploy: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ org.apache.geronimo.common.DeploymentException: Manifest class path entries must end with the .jar extension (J2EE 1.4 Section 8.2): module=../ at org.apache.geronimo.deployment.DeploymentContext.addManifestClassPath (DeploymentContext.java:419) ... I think this is definitely an error because the JEE5 specification section 8.2.1 explicitely allows directories in manifest Class-Path entries. See discussion: http://www.nabble.com/EAR-bundle-dir-classpath-issue-tt18982334s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
