BAD MSG:
Peter/Nicola of having short and long names
here the long names are form by adding a prefix defined not by the =
antlib writer,
but by the antlib user:
<antlib location=3D"antcontrib.jar" prefix=3D"myxyz-" />
which would allowme to use either:
<if/> or <myxyz-if>
it is upto the user to decide what to use. Of course the same would be =
for the
tasks (i.e., <taskdef>) that allows loading individual tasks into roles. =
The same rules of collisions
and conflict resolution apply.
The important point is for the user (which is the one who has to
deal with name clashes) to have control of the final naming scheme used =
in his/her buildfile.
And we are not impossing any wierd semantics or making assumptions,
if I decide to use the same prefix for two antlibs it is up to me to =
make sure there
are no conflicts.
> -----Original Message-----
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
> Sent: 02 May 2003 14:35
> To: [EMAIL PROTECTED]
> Subject: Re: Roles (was: antlib)
>=20
>=20
> On Wed, 30 Apr 2003, Jose Alberto Fernandez
> <[EMAIL PROTECTED]> wrote:
>=20
> > The problem you are overlooking is the case of <weblogic> element
> > in <ejbjar>, <jspc>, <serverdeploy>, etc.
>=20
> Maybe not really overlooking but understimating.
>=20
> The alternative would be to use <weblogicjspc> and <weblogicdeploy>
> for the different interfaces. If they come from different antlibs, we
> really should use XML namespaces to resolve this.
>=20
> But I now understand that having a table per interface may be
> convenient (though not strictly necessary).
>=20
> Stefan
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>=20
>=20
