[
https://issues.apache.org/jira/browse/XMLBEANS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772777#action_12772777
]
Cezar Andrei commented on XMLBEANS-268:
---------------------------------------
Just to be clear: there are 2 problems here:
1. if target namespace differs only in caps, on Windows the generated resources
will collide and there is no workaround for this at this point.
- a potential fix should change the encoding algorithm from uri to dir name,
which will break backwards compatibility so the code should be enabled only
through a system property
2. and the generation of the same class/interface name, which is by design and
the user should use a .xsdconfig file to change the package name or the
class/interface name
I reopened the issue only for tracking problem 1.
> Collision detected while generating classnames for (except-case) identical
> schema names
> ---------------------------------------------------------------------------------------
>
> Key: XMLBEANS-268
> URL: https://issues.apache.org/jira/browse/XMLBEANS-268
> Project: XMLBeans
> Issue Type: Bug
> Affects Versions: Version 2
> Environment: unix
> Reporter: Mike Barrett
> Priority: Minor
>
> We have two schemas:
> slideshow.xsd and slideShow.xsd
> Which have identical names, except case. The issue is that it seems that this
> causes a name collision, and causes the generated class name to have a number
> inserted:
> slideshow.xsd --> SlideshowDocumentImpl
> slideShow.xsd --> SlideShowDocument2Impl
> now if you remove the '2' from the slideShow class, you still have two unique
> java class names. Therefore, I don't see the need to append a number to the
> generated name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org
