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 Thu, 11 Jan 2007 20:14:27 GMT


Dan Diephouse commented on CXF-363:

Well we pretty much always need to parse them as we need to traverse the schema model and
determine if the operations are wrapped. So I'm not concerned about that.

Re: querying for a schema with a namespace - we need to be careful as you can have multiple
schemas with the same namespace. So the API would need to allow for that.

We could create SchemaInfos for the imported schemas as well. That should be pretty easy to
do given the XmlSchemaCollection.getXmlSchemas() method I think? Although it doesn't seem
to expose an Element representation of the document :-(

> Updates to the SchemaInfo model
> -------------------------------
>                 Key: CXF-363
>                 URL:
>             Project: CXF
>          Issue Type: New Feature
>    Affects Versions: 2.0-RC
>            Reporter: Balaji Ravi
>             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