Schema type bean and exception class with same name not treated as distinct

[glassfishrobot]

codemodel incorrectly thinks that Adapterexception.java (schema type bean) and AdapterException(WSDL Exception) are the same class and throws JClassAlreadyExistsException.

Using GlassFish v1 build 48 on Windows XP Pro.

Environment

Operating System: Windows XP Platform: All

Affected Versions

[2.0 FCS]

[glassfishrobot]

Reported by kumara@java.net

[glassfishrobot]

vivekp@java.net said: Assigning to myself.

[glassfishrobot]

vivekp@java.net said: This is expected failure. The failure happens because of case insensitive file system such as windows. In this case the schema element name is 'adapterexception' and the jaxb bean name for this is: AdapterException.java.

Then in the WSDL, the fault exception message name is 'AdapterException' and the fault exception class to be generated would be AdapterException.java.

On a case sensitive file system such as solaris or unix these two different classes would be generated fine. However on case insensitive file systems such as Windows it would result into overwriting each other.

There are more than one way to fix such problems, use jaxb:class customization or jaxws:class customization to rename the generated class, or generate these classes in to different package.

Since this issue is more limitation of the OS or filesystem, marking the bug invalid.

[glassfishrobot]

Was assigned to vivekp@java.net

[glassfishrobot]

This issue was imported from java.net JIRA JAX_WS-96

[glassfishrobot]

Marked as incomplete on Wednesday, November 29th 2006, 11:58:29 am