For the weblogic stuff, they would surely come
from the same antlib - say weblogic-ant.jar
using namespace (example for demo purposes only)
<project
xmlns:weblogic="antdef:com/weblogic/ant/antdef.xml"
xmlns:weblogic="antdef:org/jboss/ant/antdef.xml"
>
<serverdeploy>
<weblogic:serverdeploy
server="t3://myserver:7001"
username="${user.name}"
/>
</serverdeploy>
<serverdeploy>
<jboss:serverdeploy
server="somemachine"
maxmemorysize="888M"
username="${user.name}"
/>
</servedeploy>
</project>
or using prefixes:
<project>
<antdef resource="com/weblogic/ant/antdef.xml" prefix="weblogic."/>
<antdef resource="org/jboss/ant/antdef.xml" prefix="jboss."/>
<ejbjar ...>
<jboss.ejbdeploy ... />
</ejbjar>
<serverdeploy>
<jboss.serverdeploy
server="somemachine"
maxmemorysize="888M"
username="${user.name}"
/>
</servedeploy>
Granted it would be nice to allow <jboss.deploy/> element to be used in
both the serverdeploy and the ejbjar tasks, but since they do
completely different things, it is not unresonable to say that they
should have different names.
Peter.
On Friday 02 May 2003 14:35, Stefan Bodewig wrote:
> On Wed, 30 Apr 2003, Jose Alberto Fernandez
>
> <[EMAIL PROTECTED]> wrote:
> > The problem you are overlooking is the case of <weblogic> element
> > in <ejbjar>, <jspc>, <serverdeploy>, etc.
>
> Maybe not really overlooking but understimating.
>
> 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.
>
> But I now understand that having a table per interface may be
> convenient (though not strictly necessary).
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
