You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by bu...@apache.org on 2008/02/04 16:11:55 UTC
DO NOT REPLY [Bug 44352] New: - Nested element from different xmlns is not recognized.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44352>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44352
Summary: Nested element from different xmlns is not recognized.
Product: Ant
Version: 1.7.0
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Core
AssignedTo: notifications@ant.apache.org
ReportedBy: borges_francisco@emc.com
I am setting this bug to "core" since AFAICT the bug is not in typedef/taskdef,
but rather in the namespace resolution of nested types.
[...]
I have two sets of local Ant tasks, say A and B, and B tasks use nested types
defined on A. I have tried to start using the "uri' attribute on both groups,
but things don't work with nested types.
Namely I cannot use nested elements from one namespace, inside tasks defined
into a another namespace.
[...]
Importing tasks inside a xmlns:B="etc", and importing the types from A without
using "uri" will work:
<B:createapplication name="admin">
<database refid="ID" />
</B:createapplication>
Importing everything withOUT using "uri", will also work:
<createapplication name="admin">
<database refid="ID" />
</createapplication>
However using xmlns:B="www.B_JAR", and xmlns:A="www.A_JAR" will NOT work:
<B:createapplication name="admin">
<A:database refid="mydatabse"/>
</B:createapplication>
Here I will get:
"""B:createapplication doesn't support the nested "database" element."""
Using the same xmlns settings, if I pass the database element through a
reference in an attribute, like in
<A:database name="etc" bootstrap="etc" id="mydatabase"/>
<B:createapplication name="admin" databaseref="mydatabse">
</B:createapplication>
things do work.
So the namespace import seems to be OK, what is failing is the type resolution
of nested types.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 44352] - Nested element from different xmlns is not recognized.
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44352>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44352
peterreilly@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
------- Additional Comments From peterreilly@apache.org 2008-02-04 07:21 -------
I am not sure that I understand your statement of the problem.
Could you please provide a self contained tar or zip file containing
the tasks, and uri's usage.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 44352] - Nested element from different xmlns is not recognized.
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44352>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44352
------- Additional Comments From peterreilly@apache.org 2008-02-04 07:35 -------
*** Bug 44353 has been marked as a duplicate of this bug. ***
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.