h.
I think that would be the best option. It would postpone the addition
of a DynamicConfiguratorNS interface to a later release, thus the
interface could be designed properly from the start (if there is such a
thing ;-) ).
Cheers
Am 12.12.2003 um 15:40 schrieb Peter Reilly:
Christopher Lenz wrote:
Personally, I prefer DOM style as it is higher-level. The
qualifiedName parameter makes sense (well, sort of) when you can
enable/disable namespace support. When namespace support is always
enabled (as it is in Ant 1.6) the
Am 12.12.2003 um 13:44 schrieb Peter Reilly:
Christopher Lenz wrote:
Same here. Proposed interface:
public class DynamicConfiguratorNS {
public Object createDynamicElement(
String namespaceURI,
String prefix,
String localName);
public void setDynamicAttribute
bject should be passed in instead?
public interface NamesapceContext {
public String getPrefix(String namespaceURI);
public String getURI(String namespacePrefix);
}
What do you think?
Chris
-Original Message-
From: Christopher Lenz
To: Ant Developers List
Sent: 12/12/2003 4:12
pair of methods.
Cheers,
Chris
--
Christopher Lenz
/=/ cmlenz at gmx.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
would break as soon as Ant enabled namespace processing.
Cheers,
Chris
--
Christopher Lenz
/=/ cmlenz at gmx.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
gurator will most
probably break.
Cheers,
Chris
--
Christopher Lenz
/=/ cmlenz at gmx.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Am 11.12.2003 um 13:44 schrieb Peter Reilly:
Christopher Lenz wrote:
Hi all,
in the light of a final release of 1.6 next week, I think the
DynamicConfigurator issue with namespaces needs to be resolved. I
can't believe I'm the only one who has a problem with the current
implementat
ng the DynamicConfigurator
code to pass only the local name?
--
Christopher Lenz
/=/ cmlenz at gmx.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
t yet.
Cheers,
Chris
--
Christopher Lenz
/=/ cmlenz at gmx.de
Christopher Lenz wrote:
Hi everyone,
just a quick note that I've added some documentation to the Ant Wiki
concerning the new namespace support. If I got the facts wrong
somewhere, please correct it. Additions welcome, too,
etail/
XmlNamespaceSupport
Cheers,
Chris
--
Christopher Lenz
/=/ cmlenz at gmx.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Peter reilly wrote:
On Fri, 2003-11-28 at 11:54, Christopher Lenz wrote:
Peter reilly wrote:
The rule is as is in the ant namespace documentation, opps
the to be written documentation, is that
if the element name is in ant's xmlns, then
the componentname of the element is the local name,
othe
Peter reilly wrote:
The rule is as is in the ant namespace documentation, opps
the to be written documentation, is that
if the element name is in ant's xmlns, then
the componentname of the element is the local name,
otherwise it is uri:localname.
This is to be backward compatible with previous
vers
Stefan Bodewig wrote:
On Thu, 27 Nov 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
Any reason why the introspection doesn't look for that interface
directly, instead of XMLFragment?
XMLFragment doesn't implement DocumentFragment, it just builds one.
Ah, I hadn't actually
Christopher Lenz wrote:
Stefan Bodewig wrote:
On 27 Nov 2003, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
On Thu, 27 Nov 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
So the namespace URI and the local name are currently actually
passed to the DynamicConfigurator in the form
namespa
Stefan Bodewig wrote:
On 27 Nov 2003, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
On Thu, 27 Nov 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
So the namespace URI and the local name are currently actually
passed to the DynamicConfigurator in the form
namespace-uri:local-name?
Hi Stefan,
sounds cool. Some comments inline:
Stefan Bodewig wrote:
Hi,
I've just added a utility class to CVS HEAD that can be used to turn
nested content into a DOMFragment (not necessarily a tree). I.e., if
you use it as your nested element like
public void addContext(XMLFragment f)
you can
ctual value of the namespace URI though.
We could modify namespace processing to ignore attributes not in the
"right" namespace.
See above.
-chris
--
Christopher Lenz
/=/ cmlenz at gmx.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ar with the DOM ;-) ), and I can't think
of many use cases for this functionality. If neither the Ant core nor a
builtin Task requires this functionality, it shouldn't go in. But that's
just my opinion, and I may very well be missing something ;-)
--
Christo
Dominique Devienne wrote:
From: Christopher Lenz [mailto:[EMAIL PROTECTED]
Dominique Devienne wrote:
From: peter reilly [mailto:[EMAIL PROTECTED]
On Monday 17 November 2003 17:01, Dominique Devienne wrote:
So the NS for and does not matter?
Conceptually they are part of the Ant XML dialect to me
Dominique Devienne wrote:
From: peter reilly [mailto:[EMAIL PROTECTED]
On Monday 17 November 2003 17:01, Dominique Devienne wrote:
So the NS for and does not matter?
Conceptually they are part of the Ant XML dialect to me,
so seeing them in no namespace at all seems weird??? --DD
If no namespace
Matt Benson wrote:
--- peter reilly <[EMAIL PROTECTED]> wrote:
For example:
The arguments are equal
Okay, how about redoing the same example with:
...
or will that syntax be available at all?
That should be:
It should be much more efficient (and probably simpler) to just traverse the
DOM and replace properties in-place:
public void replaceProperties(Node n) throws DOMException {
switch (n.getNodeType()) {
case Node.ATTR_NODE:
case Node.CDATA_SECTION_NODE:
case Node.TEXT_NODE:
peter reilly wrote:
There are some other issues, in ant 1.7 we hope to move
from staticly adding conditions, filters etc to using for
them. Using the new namespace rules would mean that this is obvious.
For example:
http://apache.org..."/>
succeeded!
of course
Christopher Lenz wrote:
In an earlier thread I proposed the general rule that if a namespace'd
task or type defines the names of introspection-discovered elements,
those elements inherits the namespace from its parent.
Consider this pseudo task class:
MyTask {
addFoo(Bar foo);
}
peter reilly wrote:
On Wednesday 29 October 2003 12:06, peter reilly wrote:
On Wednesday 29 October 2003 10:42, Stefan Bodewig wrote:
On Fri, 24 Oct 2003, peter reilly <[EMAIL PROTECTED]> wrote:
blab ...
blab..
Assuming Ant's core URI was assoc
Hi Peter,
this looks really cool, but I'd suggest adding an attribute like
scope="local|global" to the task instead of adding a completely
new task.
-chris
peter reilly wrote:
I have written the code to support local properties.
While I was doing this, I realized that the attributes
of a macrod
Stefan Bodewig wrote:
On Sun, 19 Oct 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
The corresponding invocation does not specifiy the
"includeantruntime" attribute, which defaults to true. So the Ant
runtime should be included in the classpath. However, the
ant-launcher.jar do
peter reilly wrote:
On Monday 20 October 2003 10:53, Christopher Lenz wrote:
peter reilly wrote:
Note that introspection discovered elements are
in the ant:core namespace. This does make some
things a little difficult to use/explain
peter reilly wrote:
Note that introspection discovered elements are
in the ant:core namespace. This does make some
things a little difficult to use/explain:
Not to state the obvious, but this looks awfully wrong. Would i
f I
specifically include ant-launcher.jar in the test classpath, the tests
run successfully again.
Anyway, running the Cactus build unmodified doesn't work with Ant
1.6beta2, but works nicely with Ant 1.5.x, so I think this should be
considered a re
[EMAIL PROTECTED] wrote:
aha, "with ssh-agent". That is the deamon which serves the right
passphrase/password for a server, right?
Exactly there is the problem (I think) - cvs opens a ssh (but not with
a command line interface) and I can´t type my passphrase in it.
It seems that ssh on your machi
Stefan Bodewig wrote:
Hi,
I just stumbled over findbugs[1] (via Cafe au lait) and ran it over
Ant's sources.
Some of the reported problems are non-issues, but it also detected
some things that checkstyle doesn't[2]. Some examples:
* BaseFilterReader line 88 should use "" instead of new String().
*
Stefan Bodewig wrote:
On Fri, 07 Mar 2003, Christopher Lenz <[EMAIL PROTECTED]> wrote:
I can reproduce this using 1.5.2, while 1.5.1 doesn't expose the
problem.
Is this the same issue?
Probably yes. The Gump run of 2003-03-08 should produce valid zips
(even for WinZIP) if it is.
Yep
same issue?
Stefan Bodewig wrote:
Hi,
as I feared, the zip refactorings have introduced a (at least one)
nasty bug. I think 17648 is serious enough to warrant a 1.5.3 release
rather soon. We might get a chance to look into the new FTP issue at
the same time.
Thoughts?
Stefan
--
Christopher
35 matches
Mail list logo
