Schemas with deep nesting is more common than we thought

[Tomas-Kraus]

We've been seeing reports from users saying that they have to work with a schema
that has a very deep nested structure.

JAXB 1.0 produces the nested interfaces for such elements/types, and as a result
it produces names too long to be used. In fact, the complaints were that the
class file name becomes so long that it goes beyond the OS limit.

Currently, there's no workaround for this problem.
I wonder if the EG could consider this problem in JAXB 2.0.

Environment

Operating System: All
Platform: All

Affected Versions

[1.0]

[Tomas-Kraus]

@glassfishrobot Commented
Reported by kohsuke

[Tomas-Kraus]

@glassfishrobot Commented
kohsuke said:
See https://jaxb.dev.java.net/servlets/ReadMsg?list=users&msgNo=3308

[Tomas-Kraus]

@glassfishrobot Commented
kohsuke said:
Wrong link. The correct link is:
https://jaxb.dev.java.net/servlets/ReadMsg?list=users&msgNo=3304

[Tomas-Kraus]

@glassfishrobot Commented
This issue was imported from java.net JIRA JSR222-31

[Tomas-Kraus]

• Issue Imported From: Schemas with deep nesting is more common than we thought javaee/jaxb-spec#31
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @jfialli

[lukasj]

all generated classes/packages can be customized using a binding schema language