Recreational Ant puzzle

Question

I was trying to compile services with ant provided with WLS 6.1 on Win2000
machine. Following the examples, I fixed and executed setEnv before
compiling.
The compilation gave me first a warning about "modern" compiler not
available and using "classic". Then it failed at later point because
"classic" compiler could not be used for something. After awhile
investigating this problem I found that a copy of weblogic.jar was in
/bea/jdk131/jre/lib/ext. I removed it. And the service compiled and worked
perfectly. I put it back from $WL_HOME/lib. All the problems came back. Same
weblogic.jar is on %CLASSPATH% after setEnv is run.
Btw, neither I could compile the client when weblogic.jar is in
/bea/jdk131/jre/lib/ext. It worked fine, however, when I removed
weblogic.jar from ext directory.
Why could it be?
Thanx,
Ed Gokhman

Answer 1

alright, that works, as in, it tries to inject.
But now my problem remains: what should the ant-code be for using my TCS generated injector/extractor (i got a FeatureATL-parser.jar which is generated, is this sufficient?)
Is this still possible? Do you know if the generated parser uses the ATL plugin? Or is it a stand-alone, self-contained package?
I would like that something like this would work:
<!-- Loading FeatureATL model -->
<atl.loadModel modelHandler="EMF" name="fatlModel-loaded" metamodel="fatl" path="${fatlModel}">
<injector name="ATL">
<param name="name" value="FeatureATL"/>
<!--<param name="parserGenerator" value="antlr3"/>-->
<classpath>
<pathelement location="featureATL-parser.jar"/>
</classpath>
</injector>
</atl.loadModel>
ps; fatl metamodel is an extension of the normal ATL metamodel, and with TCS I developed an extended concrete syntax..