> --- Steve Loughran <[EMAIL PROTECTED]> wrote:
rule 1 of xml: nobody understands XML namespaces
rule 2: anybody who says they do. still doesnt.
so there are the following categories
-ignorant of xmlns
-vaguely aware, but doesnt understand
-think they understand, but doesnt really
-knows xmlns
Matt Benson wrote:
--- Steve Loughran <[EMAIL PROTECTED]> wrote:
Maybe. :) But really, I appreciate your input. I
have no problem admitting how clueless I am wrt xml in
general and ns in particular. :|
rule 1 of xml: nobody understands XML namespaces
rule 2: anybody who says they do. sti
--- Steve Loughran <[EMAIL PROTECTED]> wrote:
> Stefan Bodewig wrote:
> > On Wed, 21 Mar 2007, Matt Benson
> <[EMAIL PROTECTED]> wrote:
> >
> >> I think what is needed is a well-known syntax
> specification for
> >> specifying a string representation of
> [resource-type][String to pass
> >> to c
Stefan Bodewig wrote:
On Wed, 21 Mar 2007, Matt Benson <[EMAIL PROTECTED]> wrote:
I think what is needed is a well-known syntax specification for
specifying a string representation of [resource-type][String to pass
to constructor] e.g. "file?/foo/bar.baz",
"url?http://www.apache.org";, "string?
--- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> On Wed, 21 Mar 2007, Matt Benson
> <[EMAIL PROTECTED]> wrote:
>
> > I think what is needed is a well-known syntax
> specification for
> > specifying a string representation of
> [resource-type][String to pass
> > to constructor] e.g. "file?/foo/bar
On Wed, 21 Mar 2007, Matt Benson <[EMAIL PROTECTED]> wrote:
> I think what is needed is a well-known syntax specification for
> specifying a string representation of [resource-type][String to pass
> to constructor] e.g. "file?/foo/bar.baz",
> "url?http://www.apache.org";, "string?blah blah blah".
On Thu, 22 Mar 2007, Matt Benson <[EMAIL PROTECTED]> wrote:
> --- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
>
>> On Wed, 21 Mar 2007, Matt Benson
>> <[EMAIL PROTECTED]> wrote:
>> > Surely we can't go there... maybe we'd better rethink the
>> > "instanceof FileResource" idiom instead, e.g.
>> > is
whew, I'll try this: :)
--- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> On Wed, 21 Mar 2007, Matt Benson
> <[EMAIL PROTECTED]> wrote:
> > --- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
>
> >> We would want to have a FileRessource remain a
> FileRessource even
> >> when mapping them - same for th
On Wed, 21 Mar 2007, Matt Benson <[EMAIL PROTECTED]> wrote:
> --- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
>> We would want to have a FileRessource remain a FileRessource even
>> when mapping them - same for the other subclasses of Ressource.
>> Some kind of factory would be needed and using an i
--- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> Sorry for dropping the ball.
>
Not a problem. To add another metaphor to the
conversation, my plate's been so full lately I seem to
be dropping various balls... ;)
> On Tue, 6 Mar 2007, Matt Benson
> <[EMAIL PROTECTED]> wrote:
> > --- Stefan Bod
Sorry for dropping the ball.
On Tue, 6 Mar 2007, Matt Benson <[EMAIL PROTECTED]> wrote:
> --- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
>> If you go that route, could you please extract the supporting
>> methods into an interface that would allow other implementations to
>> return ressources that
--- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> On Fri, 2 Mar 2007, Matt Benson
> <[EMAIL PROTECTED]> wrote:
>
> > I noticed that in order to pick the archivefileset
> parameters on
> > e.g. (I'm assuming zip and family work this
> way as well) the
> > archivefileset has to be a direct child of
On Fri, 2 Mar 2007, Matt Benson <[EMAIL PROTECTED]> wrote:
> I noticed that in order to pick the archivefileset parameters on
> e.g. (I'm assuming zip and family work this way as well) the
> archivefileset has to be a direct child of the archive task. This
> means that specifying e.g.
>
>
>
I noticed that in order to pick the archivefileset
parameters on e.g. (I'm assuming zip and family
work this way as well) the archivefileset has to be a
direct child of the archive task. This means that
specifying e.g.
doesn't work as I would expect. Is it agreed that
's ignoring the f
14 matches
Mail list logo