Documentation for ant task wscompile ??

Is there any documentation for the ant task wscompile? In the HelloWorld example, the task is mapped to this class:
com.sun.xml.rpc.tools.ant.Wscompile

I do not know if any documentation exists but I have generated some for my own use. You are welcome to it and please let me know of any inaccuracies :)
Attribute : Description => Required
classpath : Specify where to find input class files. => Yes.
base : Specify where to place generated output files. => No; defaults to present directory.
define : Defines a service using the Java classes. => No, but exactly one of the import, define, or client attributes must be specified.
features : Enable the given features. => No; Features should be specified seperated by a space character.
debug : Generate debugging info. => No; defaults to false.
both : Generate both client and server artifacts (ties, etc.) => No; defaults to false.
client : Generate client artifacts (stubs, etc.). => No, but exactly one of the import, define, or client attributes must be specified.
server : Generate server artifacts (ties, etc.). => No; defaults to false.
source : Generate code for the specified JAXRPC SI version. Supported values are: 1.0.1, 1.0.3 and 1.1 => No; defaults to 1.1
proxyServer : URL of the proxy server including hostname and port. => No; defaults to localhost:8080.
import : Generate interfaces and value types only. => No, but exactly one of the import, define, or client attributes must be specified.
keep : Keep generated files. => No; defaults to true.
mapping : Write the 109 mapping file to the given file. => No.
model : Write the internal model to the given file. => Yes.
nonClassDir : Specify where to place non-class generated files. => No; defaults to present directory.
optimize : Optimize generated code => No; defaults to false.
config : Configuration file for generating webservice. => Yes.
sourceBase : Directory for storing the generated source files. => No; defaults to present directory.
verbose : Output messages about what the compiler is doing. => No; defaults to false.
version : Prints version information. => No; defaults to false.
xPrintStackTrace : Prints stack trace of the errors. => No; defaults to false.
xSerializable : Generate value types that implement Serializable interface. => No; defaults to false.
xDebugModel : Write readable version of the model to a file. => No.

Similar Messages

Looking for ant tasks

Dear friends,
I�m looking for ant task that address the below issues:
0 - download and install Tomcat + MySql
1 - download a WAR file
2 - run the database script
3 - install the war file into tomcat
4 - open a browser with the url of the application
do you know where can I find such tasks ?

0 - Ant comes with ftp and zip tasks, you could use these to download Tomcat and MySQL in ZIP format and unpack them.
1 - Again, the ftp task.
2 - I guess you want to run the MySQL command line client and pass it a database script? You can use the exec task for that.
3 - Tomcat comes with a few custom tasks to deploy, undeploy etc. web applications.
4 - Again, you could use the exec task.
Read the documentation of Ant and Tomcat.

Specifying property file name for ant tasks

How can I make the ant tasks look at a properties file other than
kodo.properties?
Thanks,
Tom

Tom,
You can specify a properties file like so:
 <schematool ...>
 <config properties="my.properties"/>
 </schematool>
-Patrick
Tom Davies wrote:
How can I make the ant tasks look at a properties file other than
kodo.properties?
Thanks,
Tom
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com

Weird behaviour for ant task source2wsdd

I got the following when I've tried to run source2wsdd at linux server with weblogic 8.1 SP3:
[source2wsdd] Loading source file /home/klai/dev/LSF/ws_ejb/src/lsf/webservices/WebServicesDemoLocal.java...
[source2wsdd] Constructing Javadoc information...
[source2wsdd] source2wsdd: Doclet class weblogic.webservice.tools.ddgen.ServiceGen does not contain a start method
[source2wsdd] 1 error
I've simulate the environment on Windows and it was working properly.
the ant on linux was able to load weblogic.jar and webservices.jar at start time.
Any help would be appreciated. Thanks.

There is a problem with this task, which I believe has to do with it running another task in a separate JVM without passing the correct classpath to it... But there is a solution... It is a dirty workaround but it does work:
All you have to do is initialize the classpath variable to include:
1. $WEBLOGIC_HOME$/server/lib/weblogic.jar
2. $WEBLOGIC_HOME$/server/lib/webservices.jar
3. $JAVA_HOME$/lib/tools.jar (you need this for the javadoc classes)
BUT...
A. This has to be the EXTERNAL classpath. Not the one that is passed to the task on the ant file itself, but the CLASSPATH env var in the command prompt from which you activate ant.
B. Weblogic.jar also includes many ant related classes, and it will not let ant run smoothly. So you need to include in the classpath all the jar files that are present in the $ANT_HOME$/lib/ directory, BEFORE the weblogic.jar file.
SO, make sure that in the command prompt you add them all, and only then run ANT... Then it will work.
* $ANT_HOME$/lib/*.jar
* $WEBLOGIC_HOME$/server/lib/weblogic.jar
* $WEBLOGIC_HOME$/server/lib/webservices.jar
* $JAVA_HOME$/lib/tools.jar
(One last thing... in order to create the list of JARs from the $ANT_HOME$/lib/ directory, you can use the DOS "foreach" command. If you need help with that, you can contact me through email).
I hope this helps, (I know I could use that!!!),
Best, Nir.

JRun Ant Tasks

I cannot seem to find any useful documentation or examples
anywhere regarding the JRun Ant Tasks. We are running ColdFusion
Enterprise Version 8.0.1.195765, and I have verified that the
necessary jrun-ant-tasks.jar exists beneath the runtime/lib
directory. I have really only found the following "clues":
Apache Ant - External Tools and Tasks- JRun Ant Tasks
http://ant.apache.org/external.html#JRun%20Ant%20Tasks
quote:
"JRun 4 SP1 ships with lib/jrun-ant-tasks.jar, which defines
three Ant tasks: jrun, jrunapp, and jrunjmx. Documentation for the
tasks can be found in JRun under docs/ant/jrun.html."
JRun 4 Service Pack 1a Release Notes
http://www.adobe.com/support/jrun/releasenotes/4/releasenotes_4_sp1a.html#new
quote:
Other features
* Service Pack 1a includes custom ant tasks for start/stop,
deploy/redeploy/undeploy, and access to JRun services through JMX.
For more information, see the ant documentation at
jrun_root/docs/ant/jrun.html.
The aforementioned "docs/ant/jrun.html" does not exist
anywhere in our CF installation. Any guidance would be greatly
appreciated. Thanks,
--Chris

First, many who post think their problem is urgent. Saying so will not increase your chances of getting an answer.
Second, your import has a comma in it. I would fix that first and then retry. If the container is saying the JSP cannot compile, then you at least have the container running and are able to access the page via a URL (which is good). You have a problem within your JSP. My guess is that your own classes (e.g., testpack.TestBean) cannot be found. But the error appears to be on the JSP itself.
Third, unless the JRun deployment instructions say so, don't place things in your JRE's lib directory (or any directory under it). You are simply hiding a problem if you do that.
Finally, testbean should follow Java naming conventions, and as a class should be first-case, e.g., TestBean.
- Saish

Documentation for JarSAP ant task?

G'day,
I need to generate an SDA outside of the Netweaver IDE.
I am trying to use the com.sap.sda.ant.JarSAP ant task to accomplish this, but I cannot find any documentation.
I am getting messages such as the following:
 \[JarSAP\] Info: JarSAP version 20041217.1600
 \[JarSAP\] Info: JarSAPProcessing version 20060104.1634 / JarSL version 20060518.1400
 \[JarSAP\] Property jarsap.info.dir is not set.
 \[JarSAP\] Building: /tmp/foo.sda with compression
 \[JarSAP\] Warning: No component is specified in build.xml, so the created archive will not be deliverd (no SDA) and no SAP_MANIFEST will be written.
So some documentation on how to use this task would be most helpful.

Thanks for the link, but I am using Netweaver 2004s and the script make_SDA referenced in that link does not exist in my installation.
Also the <Installation_Directory>/usr/sap/<SID>/<Instance_Number>/j2ee/deployment/scripts directory and the <Installation_Dicrectory>/usr/sap/<SID>/<Instance_Number>/j2ee/cfg/deployment14.properties file do not exist, either.

Documentation for wscompile?

I finally got around to updating to jwsdp-1_0_01 and was surprised to find that xrpcc was replaced by wscompile in many build.xml files. Except for a few very general remarks in the Tutorial, I can't find any documentation for wscompile at all (Google returns only 4 pages for "wscompile"!).
Is xrpcc deprecated? (When my old build.xml runs xrpcc, it gives a warning that "sun.tools.javac.Main is deprecated".) Is there a man page, etc., for wscompile?
Thanks,
Mike

Oops, the format of my last message got munged. Here's anoter try:
Date: 28 Aug 2002
Title: The JAX-RPC wscompile and wsdeploy Tools
1 The wscompile Tool
The wscompile tool generates stubs, ties, serializers,
and WSDL files used in JAX-RPC clients and services.
The tool reads as input a configuration file and either
a WSDL file or an RMI interface that defines the service.
1.1 Syntax
wscompile [options] <configuration-file>
By convention, the configuration file is named config.xml,
but this is not a requirement.
The following table lists the wscompile options.
Note that exactly one of the -import, -define,
or -gen options must be specified.
Option Description
-classpath <path> specify where to find input class files
-cp <path> same as -classpath <path>
-d <directory> specify where to place generated output files
-define read the service's RMI interface,
 define a service
-f:<features> enable the given features (See the below
 table for a list of features. When
 specifying multiple features, separate
 them with commas.)
-features:<features> same as -f:<features>
-g generate debugging info
-gen same as -gen:client
-gen:client generate client artifacts (stubs, etc.)
-gen:server generate server artifacts (ties, etc.) and
 the WSDL file (If you are using wsdeploy
 you do not specify this option.)
-gen:both generate both client and server artifacts
-httpproxy:<host>:<port> specify a HTTP proxy server (port defaults to 8080)
-import read a WSDL file, generate the service's RMI
 interface and a template of the class that
 implements the interface
-keep keep generated files
-model <file> write the internal model to the given file
-nd <directory> specify where to place non-class generated files
-O optimize generated code
-s <directory> specify where to place generated source files
-verbose output messages about what the compiler is doing
-version print version information
The following table lists the features (delimited by commas) that
may follow the -f option.
Feature Description
datahandleronly always map attachments to the DataHandler type
explicitcontext turn on explicit service context mapping
infix=<name> specify an infix to use for generated serializers
nodatabinding turn off data binding for literal encoding
noencodedtypes turn off encoding type information
nomultirefs turn off support for multiple references
novalidation turn off full validation of imported WSDL documents
searchschema search schema aggressively for subtypes
serializeinterfaces turn on direct serialization of interface types
1.2 Configuration File
The wscompile tool reads the configuration file (config.xml),
which contains information that describes the web service.
The basic structure of config.xml follows:
<?xml version="1.0" encoding="UTF-8"?>
<configuration
 xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
 <service> or <wsdl> or <modelfile>
</configuration>
The <configuration> element may contain exactly one
<service>, <wsdl>, or <modelfile> element.
1.2.1 The <service> Element
If you specify this element, wscompile reads the
RMI interface that describes the service and
generates a WSDL file.
In the <interface> subelement, the name attribute specifies the
service's RMI interface, and
the servantName attribute specifies the class that implements
the interface.
For example:
<service name="CollectionIF_Service"
 targetNamespace="http://echoservice.org/wsdl"
 typeNamespace="http://echoservice.org/types"
 packageName="stub_tie_generator_test">
 <interface name="stub_tie_generator_test.CollectionIF"
 servantName="stub_tie_generator_test.CollectionImpl"/>
</service>
1.2.2 The <wsdl> Element
If you specify this element, wscompile
reads the service's WSDL file and generates
the service's RMI interface.
The location attribute specifies the URL of the WSDL
file, and the packageName attribute specifies
the package of the classes generated by wscompile.
For example:
<wsdl
 location="http://tempuri.org/sample.wsdl"
 packageName="org.tempuri.sample" />
1.2.3 The <modelfile> Element
This element is for advanced users.
If config.xml contains a <service> or <wsdl> element,
wscompile generates a model file that
contains the internal data structures that describe
the service.
If you've already generated a model file in
this manner, then you can reuse it the
next time you run wscompile. For example:
<modelfile location="mymodel.xml.gz"/>
2.0 The wsdeploy Tool
The wsdeploy tool reads a WAR file and the jaxrpc-ri.xml
file and then generates another WAR file that is ready for
deployment.
Behind the scenes, wsdeploy runs wscompile with the -gen:server option.
The wscompile command generates classes and a
WSDL file which wsdeploy includes
in the generated WAR file.
2.1 Syntax
The syntax for wsdeploy follows:
wsdeploy <options> <input-war-file>
The following table lists the tool's options.
Note that the -o option is required.
Option Description
-classpath <path> specify an optional classpath
-keep keep temporary files
-o <output-war-file> specify where to place the generated war file
-tmpdir <directory> specify the temporary directory to use
-verbose output messages about what the compiler is doing
-version print version information
2.2 The Input WAR File
Typically, you create the input WAR file with a
development tool or with the ant war task.
Here are the contents of a simple input WAR file:
META-INF/MANIFEST.MF
WEB-INF/classes/hello/HelloIF.class
WEB-INF/classes/hello/HelloImpl.class
WEB-INF/jaxrpc-ri.xml
WEB-INF/web.xml
In this example, HelloIF is the service's RMI interface
and HelloImpl is the class that implements the interface.
The web.xml file is the deployment descriptor of a
web component. The jaxrpc-ri.xml file is described
in the next section.
2.2.2 The jaxrpc-ri.xml File
The listing that follows shows a jaxrpc-ri.xml file
for a simple HelloWorld service.
<?xml version="1.0" encoding="UTF-8"?>
<webServices
 xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/dd"
 version="1.0"
 targetNamespaceBase="http://com.test/wsdl"
 typeNamespaceBase="http://com.test/types"
 urlPatternBase="/ws">
 <endpoint
 name="MyHello"
 displayName="HelloWorld Service"
 description="A simple web service"
 interface="hello.HelloIF"
 implementation="hello.HelloImpl"/>
 <endpointMapping
 endpointName="MyHello"
 urlPattern="/hello"/>
</webServices>
The <webServices> element must contain one or more <endpoint>
elements. In this example, note that the interface and
implementation attributes of <endpoint> specify the
service's interface and implementation class.
The <endpointMapping> element associates the service
port with an element of the endpoint URL path
that follows the urlPatternBase.
3 Advanced Topics
This section is for developers who are familiar with
WSDL, SOAP, and the JAX-RPC specifications.
3.1 Namespace Mappings
Here is a schema type name example:
schemaType="ns1:SampleType"
xmlns:ns1="http://echoservice.org/types"
When generating a Java type from a schema type,
wscompile gets the class name from the local part of
the schema type name.
To specify the package name of the generated
Java classes, you define a mapping between
the schema type namespace and the package name.
You define this mapping by adding a <namespaceMappingRegistry>
element to the config.xml file. For example:
<service>
 <namespaceMappingRegistry>
 <namespaceMapping
 namespace="http://echoservice.org/types"
 packageName="echoservice.org.types"/>
 </namespaceMappingRegistry>
</service>
3.5 Handlers
A handler accesses a
SOAP message that represents
an RPC request or response.
A handler class must implement
the javax.xml.rpc.handler interface.
Because it accesses a SOAP message,
a handler can manipulate the message with
the APIs of the javax.xml.soap package.
Examples of handler tasks:
* Encryption and decryption
* Logging and auditing
* Caching
* Application-specific SOAP header processing
A handler chain is a list of handlers.
You may specify one handler chain for the client
and one for the server.
On the client, you include the <handlerChains> element
in the jaxrpc-ri.xml file. On the server, you
include this element in the config.xml file.
Here is an example of the <handlerChains> element
in config.xml:
<handlerChains>
<chain runAt="server"
 roles=
 "http://acme.org/auditing
 http://acme.org/morphing"
 xmlns:ns1="http://foo/foo-1">
 <handler className="acme.MyHandler"
 headers ="ns1:foo ns1:bar"/>
 <property
 name="property" value="xyz"/>
 </handler>
</chain>
</handlerChains>
For more information on handlers, see the SOAP Message Handlers chapter
of the JAX-RPC specifications.

Are the WLS 9.1 Web Service Ant Tasks ready for prime time?

I am trying to create a Proof of Concept (POC) for Enterprise and B2B Services at Wendy's Int'l, Inc.
As part of this POC, I created a WSDL for an in-house service and then used the wsdlc and jwsc Ant Tasks to translate this WSDL to Java classes and ultimately (I hoped) a deployable services.
In this document, I describe the issues I encountered setting up what I consider to be a simple POC.
I'll try to attach my WSDL file and build.xml so you can follow along.
I'll also try to attach my CSS file so you can compare how the generated WSDL appears in the Browser to the way I want it to appear.
If attachments are not allowed on these forums, then I will wait and see if there is interest in those documents before I paste them under this topic.
Some preliminary information about my environment.
Environment:
 Windows XP Pro SP2
 WebLogic 9.1
 Java 1.5.0_04
Service Name:
 AppRelease
Note: If I modify my WSDL (perhaps to add a new Operation or to change the definition of an element) and run wsdlc again, the AppReleaseSOAPPortImpl.java file is overwritten For this reason, I implemented my service logic in a class called AppReleaseServiceImple.java.
Now, for the issues.
1. Bug:
In the WSDL generated by wsdlc, the wsdl:part child of the wsdl:message tag is erroneously prefixed with a colon.
This occurs whether or not I specify a prefix for the http://schemas.xmlsoap.org/wsdl/ namespace.
Work around: Extract the wsdl from the jar file, fix it and add it back into the jar.
2. Bug:
In the WSDL generated by wsdlc, the wsdl:input and wsdl:output children of the wsdl:operation child of wsdl:portType tag are erroneously prefixed with a colon. Like 1 above, this occurs whether or not I specify a prefix for the http://schemas.xmlsoap.org/wsdl/ namespace.
Work around: Extract the wsdl from the jar file, fix it and add it back into the jar.
The error message generated by Bugs 1 and 2 is not helpful in diagnosing the problem:
[jwsc] Error at line:46 col:7 ':' expected [?! -- [CDATA[ ]
3. Bug:
In the WSDL generated by wsdlc, the documentation elements have all of my html elements stripped out, as well as my xhtml and wsdl namespace references. This completely negates one of the best features of the documentation tag, being able to present the WSDL in a browser as a nicely formatted, human friendly document which is also the underlying WSDL that can be viewed when the person views the source document.
I label this as a bug because it greatly reduces the functionality of the resulting WSDL.
4. Annoyance:
The WSDL generated by wsdlc has all of my comments stripped out, except the comments in the xsd:schema section of the wsdl:types element. I would prefer that all my comments be left in the WSDL, but if comments must be stripped out then I think all of the comments should be stripped out.
5. Annoyance:
The WSDL generated by wsdlc has my CSS specification stripped.
Work around: I donâ€™t know if adding the CSS back will do any good because I have not yet created a deployable service (see the last issue below).
6. Annoyance:
The WSDL generated by wsdlc has different namespace prefixes than the ones I specified for my application's namespace and for the http://schemas.xmlsoap.org/wsdl/soap/ namespace.
Work around: Perform a find/replace on namespace prefixes "s0" and "s1" to return them to my prefered values.
Another thing I can do at this point is simply replace the generated WSDL in the jar file with my original WSDL. This would address issues 1 thru 6 above.
7. Annoyance:
The java source files created by wsdlc are put into a jar file. This makes it annoying when working within a traditional IDE like Eclipse because there is no way to reference the source files within the jar as working source.
Work around: Extract the source files from the jar and identify the resulting directory structure as part of the source structure of the project.
8. Bug:
The jwsc task complains if the same parameter name is used in multiple operations. I received the following Errors from jwsc:
[jwsc] C:\IDE\workspace\Acre-WL9.1\AppReleaseSOAPPort.java 0:0
[jwsc] [ERROR] - Parameter element "{http://acre.services.wendys.com/AppRelease/}garRequest" is not unique across document/literal bare WebService.
Since the operation names are unique, I see no reason to also require uniqueness in the parameter names used by those operations.
Work around: Use unique element names for the input parameters of the services operations.
9. Bug:
Once items 1, 2 and 8 above are taken care of, jwsc fails with the following error:
java.lang.AssertionError: java.lang.ClassNotFoundException: weblogic.j2ee.descriptor.ApplicationBeanImpl
This seems to be due to the weblogic.jar file not being in the System Classpath.
However, I should note that when I set verbose="on" and debug="on" in the jwsc ant task, there was a message from the task which stated "[jwsc] [search path for class files: [big freakinâ€™ jar list]". In the big freakinâ€™ jar list, I did find weblogic.jar and weblogic.jar has the required ApplicationBeanImpl. This indicates to me that the jwsc task does not fully honor either its classpathref attribute, nor an embedded classpath element.
Work around: Make sure the weblogic.jar is in the System Classpath.
10. Bug:
I fixed bug #9 by running a setDomainEnv script and then ran my ant task. This time I received the following output:
ant build-serviceBuildfile: build.xml
build-service:
[jwsc] 1 JWS files will be processed.
[jwsc] Processing JWS: C:\IDE\workspace\Acre-WL9.1\src\com\wendys\services\acre\AppReleaseServiceImpl.java
[jwsc] JWS: C:\IDE\workspace\Acre-WL9.1\src\com\wendys\services\acre\AppReleaseServiceImpl.java Validated.
[AntUtil.deleteDir] Deleting directory <some temporary directory>
BUILD FAILED
java.lang.ExceptionInInitializerError
At this point, I am completely stymied about how to proceed.
I wonder what new issues await once this 10th issue is addressed.
Really, is this tool set ready for prime time?

Sorry to hear you are having so many issues with using the WLS 9.1 web service Ant tasks, inside of Eclipse.
I generally create a User Library for the couple weblogic jars needed, and use it (the User Library) in my Eclipse projects that I create JWSes in. 
I also have a separate WebLogic Library in Eclipse (actually 2 libraries since I work with WL 8.1 and now WL 9.1). As you may know, one of the long-standing issues with the Ant integration within Eclipse is the fact that Ant, being an External Tool, does not receive the Project-specific Paths/Libraries. However, since most Java-relevant Ant tasks can take classpath and classpathref attributes, this is usually not an issue. In the case of the BEA-supplied wsdlc Ant task, it is apparent from the verbose/debug console output that wsdlc can see the jars in its classpathref, but it ignores those references when resolving class references and instead only uses the system classpath.

I've only needed the weblogic.jar and xbean.jar, not all the ones you mentioned in an earlier thread of this post. 
I have not tried to winnow down exactly which jars are required. I simply included all the jars that exist and were added to the system classpath by the setDomainEnv.bat file created by WebLogic 9.1.

Afterwards, I create an Ant Builder to build the JWS Web Service EAR, as opposed to fiddlin' with Eclipse. 
I too use Ant to build my deployable archives. Eclipse is simply my IDE of choice. I validated that all the issues I listed occurred when running Ant from the command line.

If you are interested in how I do it, send me an e-mail (to [email protected]), and I'll send you a zip of one of these JWS projects. The build.xml script for the project, takes care of a lot of the "annoyances" you mentioned, one of which I think is not accurate. I have never had a situation where the wsdlc Ant task "overwrote" my XXXImpl.java file.. 
Since I'm doing a POC to determine how we want to proceed with developing Web Services and an SOA in general, I tried to perform the same tasks using Axis 2 1.0, the WebLogic 9.1 tools, and XFire 1.1. Overwriting the Impl class is a common failing in the tools which take a WSDL and create Java source files for all three frameworks.

Try my scenario. Add another operation to an existing WSDL, and run the wsdlc Ant Task. The old IMPL class will be over-written.

Because of this, I have a separate Impl class and I make sure that all its methods and annotations match the methods and annotations in the Skeleton Impl class created by wsdlc.

Maybe that's because I use the <exec> Ant task with jar.exe (the xvf options) in my build.xml, to only get what I need out of the .jar/.zip the wsdlc generates. I'm typically only interest in the interface class that my XXXImpl.java file needs to implements, because I use XMLBeans for the input args (and return values) of my web service operations. 
Perhaps. I am not using XMLBeans in any of the three frameworks because the resulting service seems to be lighter-weight in all three frameworks if XMLBeans is not used. I'm sure there will be scenarios where XMLBeans is preferred, but I have not encountered that case in this POC.

Regards,
Mike Wooten
Thanks for the follow-up.
Mike McAngus

[svn] 4001: Adding support for asdoc in flex ant tasks

Revision: 4001 Author: [email protected] Date: 2008-11-03 13:46:13 -0800 (Mon, 03 Nov 2008) Log Message: ----------- Adding support for <asdoc> in flex ant tasks QE Notes: Tests need to be added to the flextasks test suite. Doc Notes: flex tasks documentation should be updated with example for <asdoc> task. Reviewer: Paul Bugs: SDK-9775 tests: checkintests Ticket Links: ------------ http://bugs.adobe.com/jira/browse/SDK-9775 Modified Paths: -------------- flex/sdk/trunk/modules/antTasks/flexTasks-internal.tasks flex/sdk/trunk/modules/antTasks/flexTasks.tasks Added Paths: ----------- flex/sdk/trunk/modules/antTasks/src/flex/ant/AsDocTask.java

You should use compiler.library-path to include libraries.
Try the following
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<project basedir="." default="build" name="Project_name">
<property environment="env"/>
<property name="FLEX_HOME" value="C:/Program Files/Flex 3.4"/>
<property name="APP_ROOT" value="./src"/>
<property name="Project_name.location" value="../Project_name"/>
<taskdef resource="flexTasks.tasks" classpath="${FLEX_HOME}/ant/lib/flexTasks.jar"/>
<target name="build">
<mxmlc file="${APP_ROOT}/AdminConsole.mxml">
<source-path path-element="${FLEX_HOME}/frameworks"/>
<compiler.library-path>
<include name="${Project_name.location}/src" />
</compiler.library-path>
</mxmlc>
</target>
</project>
Although, I don't know what are you planning to include, and whether you should use compiler.library-path for that.

Ant tasks for oracle

Can anyone tell me where I can get this ant task "<oracle:shutdownServer|restartServer ..>" which is clearly documented in the Oracle PDF - "Oracle Containers for J2EE Deployment Guide"
http://download-east.oracle.com/docs/cd/B32110_01/web.1013/b28951.pdf
I have the ant-oracle-classes.jar for our 10.1.3.1 and have searched the antlib.xml contained within the jar and there is no reference to these tasks.
I have searched all jars in our oracle base and there are no references to these ant taskdefs anywhere.
Is there a patch for this, our is there a seperate download required?
Thanks for any help on this,
JP.

John this issue looks similar to bug 6020713 raised against 10.1.3.2 OC4J on solaris, which states that antlib.xml file is missing the following values.
< taskdef name="restartServer" classname="oracle.ant.taskdefs.deploy.JSR88StartServer"/>
< taskdef name="shutdownServer" classname="oracle.ant.taskdefs.deploy.JSR88ShutdownServer"/>
It looks like 10.1.3.1 also has this issue on windows as the classes exist in the ant-oracle-classes.jar.
You should raise an SR to clarify this oracle support.
Cheers
Jeff

Using Eclipse Ant tasks - for web service client creation

Hi,
I am following Eclipse documentation for creating Axis runtime environment web services and clients using web services Ant tasks.
As per document when I import Ant files into workspace, files that will be imported are wsgen.xml (Ant file) , axisservice.properties and axisclient.properties but for me these files are not getting imported into the project instead files axis_bujava.properties and axis_bujava.xml are imported.
Please do let me know if anyone have any ideas on this asap.
Thanks,
Roopa.

Hi,
I am following Eclipse documentation for creating Axis runtime environment web services and clients using web services Ant tasks.
As per document when I import Ant files into workspace, files that will be imported are wsgen.xml (Ant file) , axisservice.properties and axisclient.properties but for me these files are not getting imported into the project instead files axis_bujava.properties and axis_bujava.xml are imported.
Please do let me know if anyone have any ideas on this asap.
Thanks,
Roopa.

Error in writing an Ant task for creating a new connection pool.

I have written the following ant task to create a new connection pool in weblogic 10.3.
<target name="pool.dev">
 <wlconfig url="http://localhost:7001/" username="weblogic" password="weblogic">
 <query domain="C:/weblogic/rtg-L0" name="myserver"/>
 <create type="JDBCConnectionPool" name="OneSourceConnectionPool">
 <set attribute="DriverName"
 value="oracle.jdbc.OracleDriver"/>
 <set attribute="InitialCapacity" value="1"/>
 <set attribute="MaxCapacity" value="5"/>
 <set attribute="Password" value="rating"/>
 <set attribute="Properties" value="user=rating"/>
 <set attribute="RefreshMinutes" value="0"/>
 <set attribute="ShrinkPeriodMinutes" value="15"/>
 <set attribute="ShrinkingEnabled" value="true"/>
 <set attribute="TestConnectionsOnRelease" value="true"/>
 <set attribute="TestConnectionsOnReserve" value="true"/>
 <set attribute="TestConnectionsOnCreate" value="true"/>
 <set attribute="TestTableName" value="SQL SELECT 1 FROM DUAL"/>
 <set attribute="URL"
 value="jdbc:oracle:thin:@xyz.com:1522:oradvl"/>
 <set attribute="Targets" value="myserver"/>
 </create>
 </wlconfig>
</target>
When I run it, I see the following error:
BUILD FAILED
C:\ganymede\eclipse\workspace1\RtgSvr\build.xml:286: Failed to connect to the server: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
 java.io.EOFException]
Can anybody please help me regarding this...
Thank you,
Sowmya

Hi everybody,
Thank you very much for your replies....actually I added weblogic.jar to the classpath of the target. So, now I dont see that error. But, I have another problem which is as follows:
<target name="initJDBC">
<wlconfig url="t3://${host}:${port}" username="${username}" password="${password}">
 <query domain="domain.name" type="Server" name="${target.server}" property="${target.server}"/>
 <create type="JDBCConnectionPool" name="TestConnectionPool">
 <set attribute="DriverName" value="oracle.jdbc.OracleDriver"/>
 <set attribute="Password" value="welcome"/>
 <set attribute="Properties" value="user=welcome"/>
 <set attribute="URL" value="jdbc:oracle:thin:@test.com:1522:oradvl"/>
 <set attribute="Targets" value=""/>
 <set attribute="TestTableName" value="SQL SELECT 1 FROM DUAL"/>
 <set attribute="TestConnectionsOnRelease" value="false"/>
 <set attribute="TestConnectionsOnReserve" value="true"/>
 </create>
 <create type="JDBCDataSource" name="TestDataSource">
 <set attribute="JNDIName" value="TestDataSource"/>
 <set attribute="PoolName" value="TestConnectionPool"/>
 <set attribute="Targets" value=""/>
 </create>
 </wlconfig>
 </target>
I am not knowing what to give in the value field of <set attribute="Targets" value=""/>. The following is my build.properties file:
target.server=myserver
host=127.0.0.1
port=7001
username=weblogic
password=weblogic
domain.name=testDomain
If I give <set attribute="Targets" value="${myserver}"/>, I get the following error:
BUILD FAILED
C:\ganymede\eclipse\workspace1\TestSvr\build.xml:290: Property not set: ${myserver}
When I set myserver=myserver in build.properties, I get the following error:
BUILD FAILED
C:\ganymede\eclipse\workspace1\TestSvr\build.xml:290: Error invoking MBean command: java.lang.IllegalArgumentException: Property Name and value not valid for the MBean. Value myserver for parameter[Targets].java.lang.IllegalArgumentException: Unable to convert the argument valuemyserver to class javax.management.ObjectName.java.lang.reflect.InvocationTargetException
Can someone plzz help me in this regard.
Thank you,
Sowmya

Ant task for creating a new weblogic domain in weblogic 10.3

Hi,
Can anybody help me in writing an ant task in build.xml for creating a new weblogic domain in weblogic 10.3, like as in <target name="new-domain">
 <echo message=""/>
 <echo message="Attempting to create new domain:"/>
 <delete dir="C:\bea\user_projects\domains" />
 <mkdir dir="C:\bea\user_projects\domains"/>
 <wlserver dir="C:\bea\user_projects\domains" domainname="mydomain"
 host="127.0.0.1" port="7001"
 generateConfig="true" servername="AdminServer" username="weblogic"
 password="weblogic" action="start"/>
 </target>
Please suggest me adding something to the above in order to create the domain successfully.

Hi,
Can anybody help me in writing an ant task in build.xml for creating a new weblogic domain in weblogic 10.3, like as in <target name="new-domain">
 <echo message=""/>
 <echo message="Attempting to create new domain:"/>
 <delete dir="C:\bea\user_projects\domains" />
 <mkdir dir="C:\bea\user_projects\domains"/>
 <wlserver dir="C:\bea\user_projects\domains" domainname="mydomain"
 host="127.0.0.1" port="7001"
 generateConfig="true" servername="AdminServer" username="weblogic"
 password="weblogic" action="start"/>
 </target>
Please suggest me adding something to the above in order to create the domain successfully.

Problems with wlserver ant task for WL 8.1

hi
i have a problem with using wlserver ant task for Weblogic 8.1
basically i want to start the server that is already preconfigured and deploy
one ear.
here's what i do:
<taskdef name="wlserver" classname="weblogic.ant.taskdefs.management.WLServer">
<classpath refid="lib.classpath"/>
</taskdef>
<wlserver action="start" dir="D:/BEA/user_projects/domains/mydomain"
output="wls81.log"/>
(and then the deployment task - irrelevant here)
the classpath is generated automatically and includes all jars in the specific
project directory:
 <path id="lib.classpath">
 <fileset dir="${proj.lib.dir}">
 <include name="**/*.jar"/>
 </fileset>
 </path>
(weblogic.jar is there as well)
the problem is when i run it, the following happens:
- if i have action="start" (or no action attribute at all), i get the following
exception:
java.lang.NullPointerException
at weblogic.Home.<init>(Home.java:29)
at weblogic.Home.getInstance(Home.java:86)
at weblogic.Home.getPath(Home.java:94)
at weblogic.Home.getFile(Home.java:99)
at weblogic.ant.taskdefs.management.WLServer.execute(WLServer.java:260)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
at org.apache.tools.ant.Main.runBuild(Main.java:609)
at org.apache.tools.ant.Main.start(Main.java:196)
at org.apache.tools.ant.Main.main(Main.java:235)
- if i change it to action="startup" as specified on "wlserver Ant Task Reference"
it seems that this task is skipped completely. no error messages, no stack trace,
nothing. i tried -verbose and -debug options on ant, but there're no logs displayed
whatsoever. it takes less than a second to run this task so i presume it's just
getting skipped completely.
i run this from the standalone Ant 1.5.4 on Windows environment.
i've followed the topic "wlserver Ant task for WebLogic 8.1" where kind of similar
problem is described but putting weblogic.jar on the system CLASSPATH is not an
option for this project.
anyone has any idea about how to get this going?
cheers
Andrei

sounds bug to me. NPE should be correctly handled with appropriate error
message. Please contact BEA support to log the call.
"Andrei Rusakou" <[email protected]> wrote in message
news:[email protected]...
>
hi
i have a problem with using wlserver ant task for Weblogic 8.1
basically i want to start the server that is already preconfigured anddeploy
one ear.
here's what i do:
<taskdef name="wlserver"classname="weblogic.ant.taskdefs.management.WLServer">
<classpath refid="lib.classpath"/>
</taskdef>
<wlserver action="start" dir="D:/BEA/user_projects/domains/mydomain"
output="wls81.log"/>
(and then the deployment task - irrelevant here)
the classpath is generated automatically and includes all jars in thespecific
project directory:
<path id="lib.classpath">
<fileset dir="${proj.lib.dir}">
<include name="**/*.jar"/>
</fileset>
</path>
(weblogic.jar is there as well)
the problem is when i run it, the following happens:
- if i have action="start" (or no action attribute at all), i get thefollowing
exception:
java.lang.NullPointerException
at weblogic.Home.<init>(Home.java:29)
at weblogic.Home.getInstance(Home.java:86)
at weblogic.Home.getPath(Home.java:94)
at weblogic.Home.getFile(Home.java:99)
atweblogic.ant.taskdefs.management.WLServer.execute(WLServer.java:260)
atorg.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
at org.apache.tools.ant.Main.runBuild(Main.java:609)
at org.apache.tools.ant.Main.start(Main.java:196)
at org.apache.tools.ant.Main.main(Main.java:235)
- if i change it to action="startup" as specified on "wlserver Ant TaskReference"
it seems that this task is skipped completely. no error messages, no stacktrace,
nothing. i tried -verbose and -debug options on ant, but there're no logsdisplayed
whatsoever. it takes less than a second to run this task so i presume it'sjust
getting skipped completely.
i run this from the standalone Ant 1.5.4 on Windows environment.
i've followed the topic "wlserver Ant task for WebLogic 8.1" where kind ofsimilar
problem is described but putting weblogic.jar on the system CLASSPATH isnot an
option for this project.
anyone has any idea about how to get this going?
cheers
Andrei

Using Ant task wlserver/wlconfig: Received exception while creating connection for pool.

Hi,
I am using ant tasks wlserver and wlconfig to configure my weblogic server. while creating a connection pool as shown below
<target name="jdbcinfo">
<wlconfig password="weblogic"
username="weblogic"
url="${url}"
<query domain="mydomain" type="Server"
name="myserver" property="serverbean"
/>
<create type="JDBCConnectionPool"
name="jdbcpoolA"
property="jdbcPoolProp">
<set value="false"
attribute="ShrinkingEnabled"
<set value
attribute="
<set value="${serverbean}"
attribute="Targets"/>
The JDBCConnectionPool is created as long as I don't specified the attribute "Targets"
Once I add the target I get the following error
<JDBC> <BEA-001129> <Received exception while creating connection for pool "poolname" invalid arguments in call>
Please any help will be greatly appreciated.
Thanks

In your applicaion module configurations check if you are using 'JDBC URL' or 'JDBC DataSource'. You should use JDBC DataSource. Then make sure that your deployment descriptor (menu 'Application->Application Properties->Deployment) has the 'Auto Generate ...' checkbox set.
Timo

Documentation for ant task wscompile ??

Similar Messages

Maybe you are looking for