-
15. Re: Package name conflicting with class name
Found a fix. May not be perfect,
Manually compiled 'index_jsp.java' under the tmp folder and redeployed the web application. It worked.
If there is any fix available in JBoss AS7.1.1, happy to implement that.
-
16. Re: Package name conflicting with class name
Moved this to JBossWeb forum. Maybe someone there might know a solution.
-
17. Re: Package name conflicting with class name
on Fedora17 with 7.1.3.Final I don't see any problem. where did you get the problem?
-
18. Re: Package name conflicting with class name
Jean-Frederic Clere wrote:
on Fedora17 with 7.1.3.Final I don't see any problem. where did you get the problem?
I believe users are seeing it on Windows OS. There was a similar issue in previous versions of JBoss AS/JBossWeb too. I just can't find that thread or mail discussion which I remember we had before.
-
19. Re: Package name conflicting with class name
It certainly occurs on MacOS, which (like Windows) has a case insensitive/case preserving file system.
-
20. Re: Package name conflicting with class name
that really looks like JBVFS-170: When using JSP, a class name Toto.class may hide a package toto.
-
21. Re: Package name conflicting with class name
Weird in fact:
<%@ page import="com.mycomp.actions.Calculator"%>
<%@ page import="com.mycomp.Actions" %>
gives:
An error occurred at line: 6 in the generated java file
The import com.mycomp.actions cannot be resolved
The java code is:
+++
package org.apache.jsp;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.servlet.jsp.*;
import com.mycomp.actions.Calculator;
import com.mycomp.Actions;
public final class index_jsp extends org.apache.jasper.runtime.HttpJspBase
implements org.apache.jasper.runtime.JspSourceDependent {
+++
So that must be an issue of the eclipse compiler :-(
-
22. Re: Package name conflicting with class name
Could someone check that of windoze in a small eclipse java project the following will compile in a standard class like:
import com.mycomp.Actions;
import com.mycomp.actions.TestClass;
public class Main {
private TestClass test = null;
private Actions acts = null;
}
-
23. Re: Package name conflicting with class name
I created a com.Main class that imports com.acme.Actions and com.acme.actions.TestClass and it worked.
-
24. Re: Package name conflicting with class name
In fact it is the isPackage() of JDTCompiler that finds com/mycomp/actions.class and tells that com.mycomp.actions is not a package.
-
-
-
27. Re: Package name conflicting with class name
The generated index_jsp.java file also compiles fine in both Indigo and Juno on MacOS.
-
-
28. Re: Package name conflicting with class name
if you read my comment the problem is in JDTCompiler.java which is a jasper JBossWeb piece of code. But I have no idea how to know that com/mycomp/actions is a package because bad OS can't differentiate Actions.class and actons.class.
-
29. Re: Package name conflicting with class name
We have the same problem here: we're using a paid library which is obfuscated. Some classes have names like 'fu' and 'fU' in the same package. JBoss cannot tell them apart. We can reproduce it on JBoss 6 & 7 and it has definitely something to do with VFS3 (JBoss 5 with VFS2 works fine).
