cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse (JIRA)" <>
Subject [jira] Commented: (CXF-363) Updates to the SchemaInfo model
Date Fri, 12 Jan 2007 20:00:27 GMT


Dan Diephouse commented on CXF-363:

Working on applying this, but I think there are some issues.
1.  I'm not sure that you can use the targetNamespace from the getAllDocuments() as those
Documents might be a WSDL. You'd get the WSDL targetNamespace instead. 
2.  getAllDocuments actually serializes the xmlSchema objects, meaning we're not going to
get out the same XmlSchemas we put in. This *could* be ok, I'm not sure though
3. I think there are some situations where we could end up with duplicates - i.e. say we have
schemas A and B in the wsdl and they reference schema C. getAllDocuments will return both
A & C. With your logic C will get added twice I believe.

I'm not sure what the best strategy is for finding all the imported schemas. Any other ideas?

(BTW, I have a commit coming in with the other stuff, just running tests now)

> Updates to the SchemaInfo model
> -------------------------------
>                 Key: CXF-363
>                 URL:
>             Project: CXF
>          Issue Type: New Feature
>    Affects Versions: 2.0-RC
>            Reporter: Balaji Ravi
>         Assigned To: Dan Diephouse
>             Fix For: 2.0-RC
>         Attachments: schemaInfo.patch
> I am working on the corba binding based on cxf & we are using stax to read &
write objects. 
> Since we have to write out the stax events, it would be good if we could get some information
from the SchemaInfo object about the elementFormDefault & attributeFormDefault attributes.

> Also, missing are the schemas that are imported inside the schema element. How do get
these schemas from the service model? Should we create SchemaInfo's for the imported schemas?
It would be helpful if we do it when we are parsing the wsdl, otherwise it would be messy
to get the DOM element from the schema info & look for the imports... 
> I have attached a patch that fixes both the issues. Can someone provide feedback on this?
> - Balaji

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message