[
https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465195
]
Balaji Ravi commented on CXF-363:
---------------------------------
Thanks dan... But without the resolution of imports my code would become messy.
Anyways, let me try to resolve this issue at my end & if it is generic enough i
will supply a patch that takes care of the scenarios you mentioned above.
> Updates to the SchemaInfo model
> -------------------------------
>
> Key: CXF-363
> URL: https://issues.apache.org/jira/browse/CXF-363
> 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:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
