[
https://issues.apache.org/jira/browse/OFBIZ-7061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283536#comment-15283536
]
Jacques Le Roux commented on OFBIZ-7061:
----------------------------------------
I was not familiar with targetNamespace attribute, so I read
https://www.liquid-technologies.com/xml-schema-tutorial/xsd-namespaces and
http://www.w3schools.com/xml/el_schema.asp
Since targetNamespaces values are just names why not use (eg)
{code}
targetNamespace="http://ofbiz.apache.org/site-conf.xsd";
{code}
instead of
{code}
targetNamespace="http://ofbiz.apache.org/sc";
{code}
? This would be clearer. Is there something blocking this possibility
(recursivity or/and xmlns value)? We could keep the shorcut for the xmlns
prefixes.
This said, it does not change your question about step 5, and I'm more to have
it optional (ie separate copies of the schemas at step 1). Then of course we
would use (eg)
{code}
targetNamespace="http://ofbiz.apache.org/site-conf.xsd";
{code}
for the current files, and
{code}
targetNamespace="http://ofbiz.apache.org/sc";
{code}
for the modified copy
I have though still to see how this would affect autocompletion, notably using
catalogs, but that seems not to be a problem.
> Autocompletion for Compound Widget
> ----------------------------------
>
> Key: OFBIZ-7061
> URL: https://issues.apache.org/jira/browse/OFBIZ-7061
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: Trunk
> Reporter: james yong
> Assignee: james yong
> Priority: Minor
>
> I am trying to enable auto-completion when coding compound widget.
> My plan as follows:
> 1. The following xsd will be modified to use namespace
> site-conf.xsd
> widget-form.xsd
> widget-screen.xsd
> widget-menu.xsd
> simple-methods.xsd
> For example, in site-conf.xsd, we add the following document level attribute
> {code}
> xmlns="http://ofbiz.apache.org/sc";
> targetNamespace="http://ofbiz.apache.org/sc";
> {code}
> 2. Import the above schema into compound-widgets.xsd so that compound widgets
> use only one consolidated schema.
> 3. Update ExampleCompoundWidgets.xml to use the new compound-widgets.xsd. For
> example
> {code}
> <compound-widgets xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:sc="http://ofbiz.apache.org/sc";
> xmlns:m="http://ofbiz.apache.org/m";
> xmlns:s="http://ofbiz.apache.org/s";
> xmlns:f="http://ofbiz.apache.org/f";
> xmlns:sm="http://ofbiz.apache.org/sm";
>
> xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/compound-widgets.xsd";>
> <site-conf>
> <sc:request-map uri="CompoundWidgets1">
> <sc:security https="true" auth="true"/>
> <sc:event type="simple" invoke="CompoundWidgetsFunc"
> path="component://example/widget/example/ExampleCompoundWidgets.xml"/>
> <sc:response name="success" type="view" value="CompoundWidgets1"/>
> </sc:request-map>
> <sc:request-map uri="CompoundWidgets2"><sc:security https="true"
> auth="true"/><sc:response name="success" type="view"
> value="CompoundWidgets2"/></sc:request-map>
>
> <sc:view-map name="CompoundWidgets1" type="screen"
> page="component://example/widget/example/ExampleCompoundWidgets.xml#CompoundWidgets1"/>
> <sc:view-map name="CompoundWidgets2" type="screen"
> page="component://example/widget/example/ExampleCompoundWidgets.xml#CompoundWidgets2"/>
> </site-conf>
> ...... the rest
> {code}
> 4. Change java code to support reading xml with namespace (i.e. xml for
> compound widgets)
> 5. Update the attributes at document level for rest of the controllers,
> menus, forms, simple methods and screens. Current setting will not work for
> schema with a namespace. For example, in controller.xml, we will change
> {code}
> xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/site-conf.xsd”
> {code}
> to
> {code}
> xmlns="http://ofbiz.apache.org/sc”
> xsi:schemaLocation="http://ofbiz.apache.org/dtds/site-conf-ns.xsd”>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
