JiBX

[java] ERROR codegen.CodeGen - Error: Multiple matches to schema

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Not A Bug
  • Affects Version/s: JiBX 1.2.1
  • Fix Version/s: None
  • Component/s: CodeGen
  • Labels:
    None
  • Environment:
    windows 7
  • Number of attachments :
    4

Description

the same project works in one eclipse workspace but does not work on another when "codegen" ant task is run. The same problem appears in different developers machines (not all though, some get the problem and some don't) -

Output when error occurrs
—
[echo] Running cust generation from schema
[java] Warning: Undefined attribute names for SchemaCustom at (source unknown)
[java] ERROR codegen.CodeGen - Error: Multiple matches to schema account.xsd (first match SchemaCustom at (line 4, col 14)) for SchemaCustom at (line 7, col 14)
[java] Error: Multiple matches to schema account.xsd (first match SchemaCustom at (line 4, col 14)) for SchemaCustom at (line 7, col 14)
[java] Terminating due to errors in customized schemas
—

Same exact project when codegen runs successfully on different eclipse workspace on same machine or on different developers machine
—
[echo] Running cust generation from schema
[java] Warning: Undefined attribute names for SchemaCustom at (source unknown)
[java] Loaded and validated 1 specified schema(s) and 1 referenced schema(s)
[java] Generated 1 top-level classes in package com.labcorp.ncp.domain.jibxtest.common.types
[java] Generated 1 top-level classes in package com.labcorp.ncp.domain.jibxtest.account
[java] Total classes in model: 2
BUILD SUCCESSFUL
Total time: 1 second
—

  1. XML File
    account.xsd
    11/Dec/09 4:42 PM
    0.6 kB
    s
  2. XML File
    build.xml
    11/Dec/09 4:42 PM
    3 kB
    s
  3. XML File
    commonTypes.xsd
    11/Dec/09 4:43 PM
    1 kB
    s
  4. XML File
    custom.xml
    11/Dec/09 4:42 PM
    0.3 kB
    s

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dennis Sosnoski added a comment -

I'm not sure what I can do to try to resolve an intermittent problem dealing with Eclipse workspaces. I'll try to at least provide a more useful error message in hopes of tracking this down, though.

Show
Dennis Sosnoski added a comment - I'm not sure what I can do to try to resolve an intermittent problem dealing with Eclipse workspaces. I'll try to at least provide a more useful error message in hopes of tracking this down, though.
Hide
Permalink
Dennis Sosnoski added a comment -

When I tried this out myself, I realized the problem is in your customization file:

<schema-set prefer-inline="false" generate-all="true" xmlns:xs="http://www.w3.org/2001/XMLSchema">

<schema package="com.labcorp.ncp.domain.jibxtest.account" name="account.xsd">
</schema>

<schema package="com.labcorp.ncp.domain.jibxtest.common.types" names="commonTypes.xsd">
</schema>

</schema-set>

You're using a 'names' attribute on the second <schema> element, when you should be using 'name' (as on the first one). This is what causes the "Warning: Undefined attribute names for SchemaCustom at (source unknown)" message you're getting when running the code generation. If you change this attribute to 'name' everything should be good.

I don't see how this could ever run successfully, so I don't understand the second output you've shown - unless it's using an earlier version of JiBX, perhaps? In my tests running from the console the bad customization always causes code generation to fail with JiBX 1.2.2.

Show
Dennis Sosnoski added a comment - When I tried this out myself, I realized the problem is in your customization file: <schema-set prefer-inline="false" generate-all="true" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <schema package="com.labcorp.ncp.domain.jibxtest.account" name="account.xsd"> </schema> <schema package="com.labcorp.ncp.domain.jibxtest.common.types" names="commonTypes.xsd"> </schema> </schema-set> You're using a 'names' attribute on the second <schema> element, when you should be using 'name' (as on the first one). This is what causes the "Warning: Undefined attribute names for SchemaCustom at (source unknown)" message you're getting when running the code generation. If you change this attribute to 'name' everything should be good. I don't see how this could ever run successfully, so I don't understand the second output you've shown - unless it's using an earlier version of JiBX, perhaps? In my tests running from the console the bad customization always causes code generation to fail with JiBX 1.2.2.

People

  • Assignee:
    Dennis Sosnoski
    Reporter:
    s
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: