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.

Similar Messages

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.

Is there an ant task on FlexUnit to open browser with swf embedded?

Here is the same (unanswered) question asked by someone else: http://forums.adobe.com/thread/740495?tstart=0#740495
Basically I need to open my flex app in a browser window from ant, and the FlexUnit task apparently does not support this.
I have downloaded a sample from FlexMonkey. When they (sample writers) execute flexunit in this sample, one of the arguments to FU is "url". However, I can find no evidence of this version of FU (that uses that "url" argument) existing anywhere. Using the swf argument doesn't work as documented in the previous question above. So I don't know if my problem is Flex version, or it's just not supported by FlexUnit.
I'm using the Flex sdk 3.2.0 and the FU libraries below:
flexunit-4.1.0-33-as3_3.5.0.12683.swc
flexunit-4.1.0-33-flex_3.5.0.12683.swc
flexunit-cilistener-4.1.0-33-3.5.0.12683.swc
flexunit-uilistener-4.1.0-33-3.5.0.12683.swc
flexUnitTasks-4.1.0-33.jar
Please tell me if this issue has been solved and if so what libraries I need to implement it. If it is done for Flex 4.x, but not for Flex 3.2, perhaps you could guide me to the java source for the ant task for Flex 4.x so that I can implement this for Flex 3.2 or Flex 3.x.
thanks,
Phil

@Linden - Have not heard of this side effect from anyone as of yet, but good to know. Sounds like the file lock is coming from the Flash Player and causing the spawning process (rundll32.exe) to hang around as well. The FlexUnit team runs on Hudson using the FlexUnit Ant task, but we don't seem to encounter the same issue. What's the longest interval you've tried to use with the sleep task? Does the FP ever release its handle to the test SWF on your development machines?
Not sure this is a problem with the FlexUnit Ant task, but in 4.2 we could try to explicitly kill the rundll32 process since we'll have the PID when the task launches it. Head on over to JIRA and file a feature request for us and I'll see what I can do in the new year. In the short term though, maybe try upgrading your version of the stand alone debug flash player to see if that helps. Has anyone else seen this issue? Could you possible just move the clean target to be called before the xci-test target is run? Just some suggestions.
-Brian

Ant tasks to facilitate builds of Workshop apps in CM environment

The source files that we view and edit in Workshop are processed through code generators
to create the final Java classes that are deployed to the container. While testing
in Workshop, this code generation is done internally to Workshop.
However, if an application is being developed by more than one person, then we
have to be able to build the deployable application from the command line, using
Ant. This is because two users may commit independent changes to the same source
file, and the integration build has to include the results of both of those changes.
What documentation describes the Ant tasks that I can use to generate the deployable
application from the source code of a Workshop application? I did a cursory search
through the docs, but I didn't find anything conclusive.

Any idea, I'm looking for your opinion, what do you think of the above

Ant task to include Halo theme

Hi,
I recently migrated from Flex 3.4 to Flex 4. Everything works fine when I compile the application using Flash Builder 4. But I am having issues making our automated ant builds pick up the Halo theme over the Spark theme.
In FB4, I just used the "Flex Theme" options under Project -> Properties to define the Halo theme as the default theme.Before that I used the -theme compiler argument. Both work fine.
For our ant task, I tried adding:
<compiler.theme dir="${FLEX_HOME}/frameworks" append="false">
 <include name="/themes/Halo/halo.swc" />
</compiler.theme>
Unfortunately that does not seem to work and the result still shows the Spark theme. I also tried making "theme" a task attribute and the other options according to Flex 4 docs ( http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7a63.html ), but to no avail.
I have very limited experience with ant and would appreciate some input.
Thanks!

I just ran into this same issue yesterday, Here's what worked for me, placed between the <mxmlc> </mxmlc> tags
<theme dir="${FLEX_HOME}/frameworks/themes/Halo">
 <include name="halo.swc" />
</theme>

Deprecation with wlwBuild ant task?

<pre>Dear All,
How can I turn on deprecation for the ant task wlwBuild for Workshop applications?
I have tried the attribute deprecation="on" for wlwBuild, but it did not work.
Thanks a lot!
George</pre>

Well, I wish to find out all the deprecated classes and methods used in code, during compilation time.
The ant task javac has the attribute deprecation which accomplishes the task.
Similarly, is there anything in the ant task wlwBuild?
Thanks a lot!
George

VSS ANT Task and Servlet

Hi,
Can any one help me, how to invok vss ant tasks from servlet ?
i am calling vss ant task 'vsslabel' from struts action class. but i am getting following error .
Failed executing: ss Label $/ADABuildSystem/ADAInternal -C- -I- -LREQ200600096 -Yada,password With a return code of 1
at org.apache.tools.ant.taskdefs.optional.vss.MSVSS.execute(MSVSS.java:191)

@Paul - This would be a feature request for the Ant task, so we won't be able to get this in until 4.2 since we just locked down new features for 4.1 beta. Fortunately, there is a stop gap that is much simpler than rebuilding the JAR. At the end of the day, the JAR is just a zip. Create your own version of the template (using the current one as a basis) and just unzip the jar and replace the flexUnitDescriptor.template file. From there the new template should be used w/o an issue. If you could go into JIRA and enter a feature request for user provided descriptor, we'll try to get it into the roadmap for 4.2 (https://bugs.adobe.com/jira/browse/fxu). Hope this helps.
-Brian

Ant tasks in eclipse

Feature request:
It would be nice if the kodo ant tasks were attached to the
"org.eclipse.ant.core.antTasks" extension point of eclipse so that ant
scripts run from within eclipse would not have to define a "taskdef"
element for those ant tasks.
-Chris West

Thanks for the suggestion. Hopefully we can get it in.
http://bugzilla.solarmetric.com/show_bug.cgi?id=719
Chris West wrote:
Feature request:
It would be nice if the kodo ant tasks were attached to the
"org.eclipse.ant.core.antTasks" extension point of eclipse so that ant
scripts run from within eclipse would not have to define a "taskdef"
element for those ant tasks.
-Chris West
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com

JDeveloper Ant Task (10g)

Hi,
The download link for JDeveloper Ant Task in http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/130355.xml#uk.org.damselfly.jdev.ant does not work anymore.
Does anyone know where i can get the file jdev-ant-task-bundle.zip (http://www.oracle.com/technology/products/jdev/101/update/extensions/jdev-ant-task-bundle.zip)
Groeten,
HJH

Try taking a look at this page.
http://www.oracle.com/technetwork/developer-tools/jdev/index-094585.html
Hopefully it will get you going in the right direction.
--jb

Updates to Ant task

I've pushed through some bugs fixes over the last few days. Here is the list:
- Updated platform defaults to try the user trust directory first, then if not found, use the global trust directory, when localTrusted="true"
- Updated the platform trust directory paths to work with WindowsXP, Windows Vista/7, MacOSX, and Linux.
- Updated trust file to append and remove paths rather than create and destroy the file to support concurrent runs of the Ant task
- Updated inbound streaming to decode using UTF-8 to respect non-western languages coming from the FP
- Updated XML output to be safe for use with single quotes in failure/error messages
- Updated CIListner and Ant task to report the correct # of runs when multiple failures/errors for a single test are reported
I'm still having issues with the global trust directory on Linux (tested with Ubuntu), so unfortunatley no resolve for that issue yet. If anyone knows of the correct path to use, I'm definitely open to suggestion; we're currently using /etc/adobe/FlashPlayerTrust.
Although the changes have not been pushed to the FlexUnit master yet, if anyone would like to help me test out their platform of choice with my latest build of the Ant task, I would be very grateful. You can find the latest Ant task JAR and CIListener SWC @ http://flexunit.digitalprimates.net:8080/view/All/job/Demo-Versioned-Build/. Please note, you need to update both for the Ant task to work correctly.
Looking forward to any feedback.
-Brian

Manually create your manifest file ${input-dir}/META-INF/MANIFEST.MF before running your ant script. appc should pick up your manifest file instaed of creating a default one.
Make sure that the manifest file contains "version-info: Manifest-Version : version-number" as specified by the jar specification.
Regards,
Dhilip

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.

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.

Documentation for JarSAP ant task?

Similar Messages

Maybe you are looking for