cxf-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464235
] 

Dan Diephouse commented on CXF-363:
-----------------------------------

Sorry for my lack of clarity Balaji. I have taken a look at the patch. What I was saying is
that in WSDLServiceBuilder et al we should be doing this:

SchemaInfo info = ...;
info.setSchema(xmlSchema); 

And then you can check the the schema attributes by doing:

info.getSchema().getElementFormDefault().

But now that I look at the XmlSchema api it kind of sucks in that respect because you need
to do a string comparison. So a isElementFormQualified() method may still be in order and
adding the XmlSchema to the object model is a separate issue then. So I'll apply your patch
later today and maybe add in the XmlSchema object on SchemaInfo as well.


> 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
>             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

        

Mime
View raw message