You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Balaji Ravi (JIRA)" <ji...@apache.org> on 2007/01/11 18:59:27 UTC
[jira] Created: (CXF-363) Updates to the SchemaInfo model
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
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
[jira] Commented: (CXF-363) Updates to the SchemaInfo model
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464325 ]
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: 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
[jira] Commented: (CXF-363) Updates to the SchemaInfo model
Posted by "Balaji Ravi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464207 ]
Balaji Ravi commented on CXF-363:
---------------------------------
I don't think i understand your comment... In my patch i have created child schema infos by getting imported schema documents from the XmlSchema object. This works fine for me. Also, the api doesn't store a map of namespace to schema infos, so it should befine with adding schema infos with the same namespace.
Have you taken a look at the patch?
> 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
[jira] Commented: (CXF-363) Updates to the SchemaInfo model
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463974 ]
Dan Diephouse commented on CXF-363:
-----------------------------------
Hi Balaji - a quick suggestion. We're already parsing out all the schemas into XmlSchema objects. For instance line 210 of WSDLServiceBuilder. How about adding a property on SchemaInfo for the XmlSchema object and setting it in the appropriate places instead? Then you can access all the schema information you want :-)
> 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
[jira] Commented: (CXF-363) Updates to the SchemaInfo model
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464326 ]
Dan Diephouse commented on CXF-363:
-----------------------------------
Scratch comment #1 as I didn't realize when I wrote that that we're actually reserializing the schemas as I said in #2.
> 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
[jira] Commented: (CXF-363) Updates to the SchemaInfo model
Posted by "Balaji Ravi (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (CXF-363) Updates to the SchemaInfo model
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (CXF-363) Updates to the SchemaInfo model
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Diephouse updated CXF-363:
------------------------------
Fix Version/s: (was: 2.0-RC)
2.1
Moving these issues to 2.1 as I don't think we'll get them for 2.0. Feel free to switch reschedule if you feel appropriate.
> 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.1
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-363) Updates to the SchemaInfo model
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Diephouse reassigned CXF-363:
---------------------------------
Assignee: Dan Diephouse
> 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
[jira] Updated: (CXF-363) Updates to the SchemaInfo model
Posted by "Balaji Ravi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Balaji Ravi updated CXF-363:
----------------------------
Attachment: schemaInfo.patch
> 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
[jira] Commented: (CXF-363) Updates to the SchemaInfo model
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464649 ]
Dan Diephouse commented on CXF-363:
-----------------------------------
OK, I've committed my changes. Let me know what you think
An alternative that we may want to consider is XSOM, which gives you a bit of a better model to browse schema imports... https://xsom.dev.java.net/
> 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
[jira] Commented: (CXF-363) Updates to the SchemaInfo model
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465203 ]
Dan Diephouse commented on CXF-363:
-----------------------------------
I'm not saying I don't want to include all the imports in the schema model. Because I do want them in the schema model. I'm just not sure how to do it via the XmlSchema APIs... we could maybe change the APIs to make it easier (I'm an XmlSchema committer), but I haven't had time to look in depth into this option yet.
> 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
[jira] Commented: (CXF-363) Updates to the SchemaInfo model
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463975 ]
Dan Diephouse commented on CXF-363:
-----------------------------------
BTW, the one other place where we are creating XmlSchema objects is ReflectionServiceFactory - so we might want to set the appropriate XmlSchema objects there 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
[jira] Commented: (CXF-363) Updates to the SchemaInfo model
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464001 ]
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: 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
[jira] Commented: (CXF-363) Updates to the SchemaInfo model
Posted by "Balaji Ravi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463978 ]
Balaji Ravi commented on CXF-363:
---------------------------------
Hi dan,
I thought about that but than again i figured there might be places where we wouldn't want to take a hit of parsing dom elements to XmlSchema Objects.
Anyways, wouldn't we want to create SchemaInfo's for the imported schemas... It would be much easier for me to get the TypeInfo, query it for a SchemaInfo object based on a namespace. Instead of having to get the XmlSchema object & then check the imports for the namespace i want...
Also, in the ReflectionServiceFactoryBean i think it just has one XmlSchema object which is created in that function.
- Balaji
> 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
[jira] Resolved: (CXF-363) Updates to the SchemaInfo model
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-363.
-----------------------------
Resolution: Fixed
Fix Version/s: (was: 2.1)
2.0
Patch applied long time ago.
> 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
> Assignee: Dan Diephouse
> Fix For: 2.0
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-363) Updates to the SchemaInfo model
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464646 ]
Dan Diephouse commented on CXF-363:
-----------------------------------
Just an FYI - I haven't forgot about you. I had problems merging my changes and a seemingly unrelated test is failing. Working on fixing soon...
> 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