Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] eclipselink.core Schema change from Map to List breaks DBWS WSDLGenerator

Michael O'Brien wrote:
Committers,
    see
 
    I am getting a compile failure in dbws after today's refresh that looks to originate from a change in Schema.java in moxy.
    org.eclipse.persistence.tools.dbws.WSDLGenerator.createInlineSchema()
 
 
The method put(String, Import) is undefined for the type List eclipselink.dbws/src/org/eclipse/persistence/tools/dbws WSDLGenerator.java line 241 1203021487447 79258
The method put(String, Import) is undefined for the type List eclipselink.dbws/src/org/eclipse/persistence/tools/dbws WSDLGenerator.java line 247 1203021487447 79259
 
    private org.w3c.dom.Element createInlineSchema() {
        schema.getImports().put(parent.getSchemaLocation(), parent);
 
Caused by...
org.eclipse.persistence.internal.oxm.schema.model
public Schema() {
        namespaceResolver = new NamespaceResolver();
        imports = new HashMap();
        includes = new HashMap();
 
To:   
public Schema() {
        namespaceResolver = new NamespaceResolver();
        imports = new ArrayList();
        includes = new ArrayList();
 
thank you
/michael
DBWS is not part of any EclipseLink milestone or release target - it is only in the EclipseLink SVN
repository as a 'placeholder'.

So long as the compile errors do not affect automated build/testing, we can ignore this
--
Oracle Email Signature Logo
Mike Norman | Principal Software Designer | 613.288.4638
Oracle Server Technologies | TopLink Product
45 O'Connor Street, Suite 400 | Ottawa, ON K1P 1A4 | (fax) 613.238.2818


Back to the top