[
https://issues.apache.org/jira/browse/PIVOT-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884982#action_12884982
]
Greg Brown commented on PIVOT-560:
----------------------------------
Me, for one. :-) As implemented, a developer can see that there is a 1:1
relationship between namespaces and Java packages. Allowing a one-to-many
relationship would muddy that definition. It would also make automated
processing of BXML more complex.
You can always do a "local import" - in other words, override the default
namespace on a per-element basis:
<Window xmlns="org.apache.pivot.wtk">
<MyCustomComponent xmlns="com.foo.bar">
...
</MyCustomComponent>
</Window>
That's consistent with the current implementation and XML namespaces in
general. We do this in a number of places in the examples.
> Permit WTKX namespace declarations to declare more than one in-scope package
> ----------------------------------------------------------------------------
>
> Key: PIVOT-560
> URL: https://issues.apache.org/jira/browse/PIVOT-560
> Project: Pivot
> Issue Type: New Feature
> Components: wtk-wtkx
> Affects Versions: 1.5.1
> Reporter: Michael Allman
> Fix For: 1.5
>
> Attachments: multiple_packages_in_one_namespace_uri.patch.gz
>
>
> The attached patch allows this:
> <Frame xmlns="org.apache.pivot.wtk,my.custom.component.package"
> xmlns:wtkx="http://pivot.apache.org/wtkx";>
> <content>
> <BoxPane/>
> <MyCustomComponent/>
> </content>
> </Frame>
> The obvious benefit of this patch is to (almost) eliminate the need for
> alternate namespace prefixes for other packages. If a type name exists in
> more than one package, the system throws a SerializationException complaining
> that the type name is ambiguous.
> To make an analogy, the way things currently are would be like restricting
> imports in a Java source file to a single package. Any type from another
> package would have to be qualified. This patch allows the Pivot developer to
> bring multiple packages into the default (or other) XML namespace. This is a
> huuuuuge time (and finger) saver when working with custom components.
> Cheers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
