You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by "Siberski, Wolf" <Wo...@tui.de> on 2000/07/05 10:18:58 UTC
Subpackages of ...taskdefs.optional (was: RE: [PATCH]: Path, Exec
ution framework, JUnit and JavaCC)
> From: Thomas Haas [mailto:thomas.haas@softwired-inc.com]
> conor@m64.com (Conor MacNeill) wrote:
> >
> > > -----Original Message-----
> > > From: Thomas Haas [mailto:thomas.haas@softwired-inc.com]
[snip]
> > >
> > > I would love to add subpackages to
> > >
> > > org.apache.tools.ant.taskdefs.optional
> > >
> >
> > Can we work out a simple standard for this area then?
>
> how about the package being equal to the name of the task.
>
That wouldn't help because we would get as many subpackages
as we have optional tasks now; what would we gain by introducing
subpackages then?.
As I'm no ant developer I'm reluctant to make a complete proposal
here. But IMHO the tasks should be put in more general packages.
E.g. I would put all EJB related tasks in a .ejb package, all
version control tasks in a .sccm package, etc.
If this is not enough, one could add subpackages for the
different products, e.g. .ejb.wls, .ejb.inprise, .sccm.cvs,
.sccm.pvcs, ...
Wolf
RE: Optional EJB tasks (was RE: Subpackages of ...taskdefs.optional)
Posted by Conor MacNeill <co...@m64.com>.
Tim,
Thanks for your code. I have committed my 4.5.1 tasks and I will look at
committing your task in the next few days.
Conor
> -----Original Message-----
> From: Tim Fennell [mailto:tfenne@rcn.com]
> Sent: Wednesday, 5 July 2000 21:28
> To: ant-dev@jakarta.apache.org
> Subject: RE: Optional EJB tasks (was RE: Subpackages of
> ...taskdefs.optional)
>
>
> Okay, here is the code. I hope people don't mind the attachment, but it's
> quite large!
>
> If this is useful to anyone, I'd love some feedback on the utility of some
> things I am thinking of doing with it:
>
> - Change from having the main class implement DocumentHandler to having an
> inner class and using the javax.xml pluggability instead of
> org.xml.sax.helper...
> - Splitting into two classes: main EJB1.1 scanner with a callback Task
> mechanism for registering the appserver(s) proprietary tools, this way the
> bulk of the work, assembling the jar in the first place, could be used by
> any EJB1.1. task. Any better ideas?
> - Changing the naming standard reliance for the WL descriptors (right now,
> must be beanName-weblogic-ejb-jar.xml) to be based on the original
> deployment descriptor with some simply pattern matching (e.g. you
> specificy
> upto the first '-' or something like that). This would allow more flexible
> naming, and also package or multi-package jars not just single-bean jars.
>
> -t
>
> ps. This is the task from my current build.xml:
>
> <target name="ejbs" depends="classes">
> <ejbgen srcdir="${destDir}"
> destdir="${destDir}"
> includes="${ejbdds}"
> excludes="${wldds}"
> generateweblogic="true"
> keepgeneric="true"
> genericjarsuffix="-temp.jar"
> weblogicjarsuffix="-wl.jar"/>
> </target>
>
> -----Original Message-----
> From: Wolfgang Werner [mailto:wwerner@picturesafe.de]
> Sent: Wednesday, July 05, 2000 07:11
> To: ant-dev@jakarta.apache.org
> Subject: AW: Optional EJB tasks (was RE: Subpackages of
> ...taskdefs.optional)
>
>
> > On the topic of EJB tasks, has anyone written anything for EJB1.1 and/or
> > Weblogic 5.1?
> >
> > If not, then I'd like to offer up what I have. I hava an EJB task that
> > inherits from directory scanner, scans for deployment descriptors and
> > assembles the EJB1.1 jars from the contents of the descriptor
> > (XML only, not
> > the 1.0 serialized classes), then optionally calls weblogic's
> ejbc. Works
> > very well for me, and now I can have only one task for all of
> my EJBs. It
> > should also be really easy to extend to call other vendors' compilers.
> >
> > Is there any interest? If so then I'll post the code here (I
> > assume this is
> > the right forum?).
> Great! I'm working with WLS 5.1 and use currently only
> java - tasks to assemple things. Please post your stuff!
>
> I'm sure that on this list are others who try to generate
> a neutral EJB support task / and or working on simmilar
> stuff.
>
> open source works!
>
> Wolfgang Werner
> wwerner@picturesafe.de
>
RE: Optional EJB tasks (was RE: Subpackages of ...taskdefs.optional)
Posted by Tim Fennell <tf...@rcn.com>.
Okay, here is the code. I hope people don't mind the attachment, but it's
quite large!
If this is useful to anyone, I'd love some feedback on the utility of some
things I am thinking of doing with it:
- Change from having the main class implement DocumentHandler to having an
inner class and using the javax.xml pluggability instead of
org.xml.sax.helper...
- Splitting into two classes: main EJB1.1 scanner with a callback Task
mechanism for registering the appserver(s) proprietary tools, this way the
bulk of the work, assembling the jar in the first place, could be used by
any EJB1.1. task. Any better ideas?
- Changing the naming standard reliance for the WL descriptors (right now,
must be beanName-weblogic-ejb-jar.xml) to be based on the original
deployment descriptor with some simply pattern matching (e.g. you specificy
upto the first '-' or something like that). This would allow more flexible
naming, and also package or multi-package jars not just single-bean jars.
-t
ps. This is the task from my current build.xml:
<target name="ejbs" depends="classes">
<ejbgen srcdir="${destDir}"
destdir="${destDir}"
includes="${ejbdds}"
excludes="${wldds}"
generateweblogic="true"
keepgeneric="true"
genericjarsuffix="-temp.jar"
weblogicjarsuffix="-wl.jar"/>
</target>
-----Original Message-----
From: Wolfgang Werner [mailto:wwerner@picturesafe.de]
Sent: Wednesday, July 05, 2000 07:11
To: ant-dev@jakarta.apache.org
Subject: AW: Optional EJB tasks (was RE: Subpackages of
...taskdefs.optional)
> On the topic of EJB tasks, has anyone written anything for EJB1.1 and/or
> Weblogic 5.1?
>
> If not, then I'd like to offer up what I have. I hava an EJB task that
> inherits from directory scanner, scans for deployment descriptors and
> assembles the EJB1.1 jars from the contents of the descriptor
> (XML only, not
> the 1.0 serialized classes), then optionally calls weblogic's ejbc. Works
> very well for me, and now I can have only one task for all of my EJBs. It
> should also be really easy to extend to call other vendors' compilers.
>
> Is there any interest? If so then I'll post the code here (I
> assume this is
> the right forum?).
Great! I'm working with WLS 5.1 and use currently only
java - tasks to assemple things. Please post your stuff!
I'm sure that on this list are others who try to generate
a neutral EJB support task / and or working on simmilar
stuff.
open source works!
Wolfgang Werner
wwerner@picturesafe.de
AW: Optional EJB tasks (was RE: Subpackages of ...taskdefs.optional)
Posted by Wolfgang Werner <ww...@picturesafe.de>.
> On the topic of EJB tasks, has anyone written anything for EJB1.1 and/or
> Weblogic 5.1?
>
> If not, then I'd like to offer up what I have. I hava an EJB task that
> inherits from directory scanner, scans for deployment descriptors and
> assembles the EJB1.1 jars from the contents of the descriptor
> (XML only, not
> the 1.0 serialized classes), then optionally calls weblogic's ejbc. Works
> very well for me, and now I can have only one task for all of my EJBs. It
> should also be really easy to extend to call other vendors' compilers.
>
> Is there any interest? If so then I'll post the code here (I
> assume this is
> the right forum?).
Great! I'm working with WLS 5.1 and use currently only
java - tasks to assemple things. Please post your stuff!
I'm sure that on this list are others who try to generate
a neutral EJB support task / and or working on simmilar
stuff.
open source works!
Wolfgang Werner
wwerner@picturesafe.de
Optional EJB tasks (was RE: Subpackages of ...taskdefs.optional)
Posted by Tim Fennell <tf...@rcn.com>.
On the topic of EJB tasks, has anyone written anything for EJB1.1 and/or
Weblogic 5.1?
If not, then I'd like to offer up what I have. I hava an EJB task that
inherits from directory scanner, scans for deployment descriptors and
assembles the EJB1.1 jars from the contents of the descriptor (XML only, not
the 1.0 serialized classes), then optionally calls weblogic's ejbc. Works
very well for me, and now I can have only one task for all of my EJBs. It
should also be really easy to extend to call other vendors' compilers.
Is there any interest? If so then I'll post the code here (I assume this is
the right forum?).
-t
-----Original Message-----
From: Conor MacNeill [mailto:conor@m64.com]
Sent: Wednesday, July 05, 2000 05:14
To: ant-dev@jakarta.apache.org
Subject: RE: Subpackages of ...taskdefs.optional (was: RE: [PATCH]:
Path, Execution framework, JUnit and JavaCC)
> From: Siberski, Wolf [mailto:Wolf.Siberski@tui.de]
> Sent: Wednesday, 5 July 2000 18:19
> To: 'ant-dev@jakarta.apache.org'
> Subject: Subpackages of ...taskdefs.optional (was: RE: [PATCH]: Path,
> Execution framework, JUnit and JavaCC)
>
>
> That wouldn't help because we would get as many subpackages
> as we have optional tasks now; what would we gain by introducing
> subpackages then?.
> As I'm no ant developer I'm reluctant to make a complete proposal
> here. But IMHO the tasks should be put in more general packages.
> E.g. I would put all EJB related tasks in a .ejb package, all
> version control tasks in a .sccm package, etc.
> If this is not enough, one could add subpackages for the
> different products, e.g. .ejb.wls, .ejb.inprise, .sccm.cvs,
> .sccm.pvcs, ...
>
+1
I had reached a similar conclusion and I am intending to add my weblogic
tasks under optional.ejb
RE: Subpackages of ...taskdefs.optional (was: RE: [PATCH]: Path, Execution framework, JUnit and JavaCC)
Posted by Conor MacNeill <co...@m64.com>.
> From: Siberski, Wolf [mailto:Wolf.Siberski@tui.de]
> Sent: Wednesday, 5 July 2000 18:19
> To: 'ant-dev@jakarta.apache.org'
> Subject: Subpackages of ...taskdefs.optional (was: RE: [PATCH]: Path,
> Execution framework, JUnit and JavaCC)
>
>
> That wouldn't help because we would get as many subpackages
> as we have optional tasks now; what would we gain by introducing
> subpackages then?.
> As I'm no ant developer I'm reluctant to make a complete proposal
> here. But IMHO the tasks should be put in more general packages.
> E.g. I would put all EJB related tasks in a .ejb package, all
> version control tasks in a .sccm package, etc.
> If this is not enough, one could add subpackages for the
> different products, e.g. .ejb.wls, .ejb.inprise, .sccm.cvs,
> .sccm.pvcs, ...
>
+1
I had reached a similar conclusion and I am intending to add my weblogic
tasks under optional.ejb