WL8.1 wldeploy Ant Task seems to be fairly slow...

We currently have a clustered environment with 4 machines. When we try to hot deploy
using the wldeploy Ant Task it takes about 3-5 minutes to re-deploy the ~30mb
ear file. While this ear is being deployed users can not access the system. Is
there anything I can do to increase these times?
Thanks,
Franz

Rob,
Thanks for your reply.
My build.xml file exits and kills the server instance......do you know any means
to rsolve it.
iam not sure if i can use "fork" or something like that ????
Please advise.
-sangita
Rob Woollen <[email protected]> wrote:
Have a look at the Avitek Medical Records example that ships with WLS
8.1. It shows you how to use wldeploy.
-- Rob
sangita wrote:
if you don't mind, can you share your build.xml file here on this forum?
iam trying to do exact same thing, but as my knowledge of ANT is little,iam having
trouble. if you can share this xml file, then i would learn a littlefaster on
how to deploy application on wls8.1 using ANT.
i have read the document though .....but i wanted to see actual xmlfile as yours
.........thanks !!!!!
"Franz Garsombke" <[email protected]> wrote:
We currently have a clustered environment with 4 machines. When we
try
to hot deploy
using the wldeploy Ant Task it takes about 3-5 minutes to re-deploythe
~30mb
ear file. While this ear is being deployed users can not access thesystem.
Is
there anything I can do to increase these times?
Thanks,
Franz

Similar Messages

Changing the wldeploy ant task behaviour

wldeploy ant task while deploying the application deploys it under <configured weblogic upload dir>/<application name>/app/ application name.
Is there any way we can change this behaviour as we couldnt find the options in ant task to change it

That is all you should have to do, the ant tasks are sitting inside the
weblogic.jar.
Cheers
mbg
"Shane Witbeck" <[email protected]> wrote in message
news:[email protected]..
Rob Bennett <[email protected]> wrote in message
news:<[email protected]>...
What is required for the wldeploy ant task to function properly? I am
able to use it when I run ant from the command line and use the version
of ant that came with Weblogic 8 (I have the platform beta, not the
release version). When I try to use it inside of eclipse (which uses
its own copy of ant), the task fails.. it looks like it is trying to
generate RMI stubs. If anyone can shed light on what I am missing from
the eclipse environment, I would appreciate it.
-RobI actually just got it to work by adding the weblogic.jar to my
classpath. (Im using WL 8.1).
-Shane

Wldeploy Ant task deploys app in 'New' state

I am trying to deploy a web application in WL 10.0 using the wldeploy Ant task. However, everytime the application is deployed, the consolidated state is 'New' (or deferred deployment). I have to bounce the servers everytime to bring the app in the Active state.
Here is my code:
<target name="undeployWeb">
          
          <wldeploy action="undeploy" verbose="true" debug="false" name="${deploymentName}" user="${weblogicUsername}" password="${weblogicPassword}" adminurl="${weblogicAdminURL}" targets="${weblogicTargetServers}" failonerror="false" />
</target>

<target name="deployWeb">
          
          <wldeploy action="deploy" stage="stage" usenonexclusivelock="true" source="${weblogicDeploymentLocation}/${deploymentName}.war" remote="true" name="${deploymentName}" upload="false" user="${weblogicUsername}" password="${weblogicPassword}" verbose="true" adminurl="${weblogicAdminURL}" debug="true" targets="${weblogicTargetServers}" />
</target>
Is there any way to avoid the bounce of the target servers? I wish to activate the web app straightaway. Please help.
~hartbrekk

Thanks user10939158, for looking into this.
Reason I am saying network is not an issue here because the artifact copy to the remote servers and deployment happens fast, it is just at the step of closing DM connection, it is waiting for a long time (>5 mins). I am guessing that the Deployment Manager message exchanges with the server (internally) has something to do with LAN vs WAN. And, I would expect deployment over WAN take a minute extra as opposed to 5-9 minutes extra what we are seeing now.
Yes, I tried running the wlst script on the remote server and it is fast as well.
Just to clarify, I do not have a local server. I run the plain simple ant script on a build box(lean linux box) which is in the US.
Thanks for your help again.
- Kris
Edited by: kris_2000 on May 25, 2010 2:08 PM

ClassCastException using Subant and wldeploy ant task

Hi!
I'm using subant to call all diffrent build.xml files located in subdirectories. The buildfile looks like this:
<project name="extern.call" default="callall">
     <target name="callall">
          <fileset      id="buildfile.set" dir=".." includes="*2/build.xml">
               <exclude name="Br*2/*"/>
          </fileset>
          <subant target="deploy-local" inheritall ="false" failonerror="true">
               <fileset      refid="buildfile.set"/>
          </subant>
     </target>
</project>
The first called build.xml files works fine ... but the execution of the second build.xml (it's not important which file is the second one, it's crash always at the second call), stop with a "java.lang.ClassCastException".
See Stacktrace:
[subant] weblogic.Deployer -debug -nowait -verbose -upload -noexit -name ClarifyRead -source \build\ClarifyRead\delivery\ClarifyRead.ear -targets myserver -adminurl t3://localhost:7001 -user weblogic -password ******** -deploy
[subant] dumping Exception stack
[subant] java.lang.ClassCastException
[subant] at weblogic.management.deploy.utils.DeployerHelper.uploadSource(DeployerHelper.java:586)
[subant] at weblogic.Deployer.runBodyWithAuthenticatedSubject(Deployer.java:824)
[subant] at weblogic.Deployer.runBody(Deployer.java:711)
[subant] at weblogic.utils.compiler.Tool.run(Tool.java:146)
[subant] at weblogic.utils.compiler.Tool.run(Tool.java:103)
[subant] at weblogic.Deployer.runMain(Deployer.java:566)
[subant] at weblogic.Deployer.mainWithExceptions(Deployer.java:576)
[subant] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[subant] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[subant] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[subant] at java.lang.reflect.Method.invoke(Method.java:324)
[subant] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:264)
[subant] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:204)
[subant] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
[subant] at org.apache.tools.ant.Task.perform(Task.java:364)
[subant] at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:65)
[subant] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
[subant] at org.apache.tools.ant.Task.perform(Task.java:364)
[subant] at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:340)
[subant] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
[subant] at org.apache.tools.ant.Task.perform(Task.java:364)
[subant] at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:65)
[subant] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
[subant] at org.apache.tools.ant.Task.perform(Task.java:364)
[subant] at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:340)
[subant] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
[subant] at org.apache.tools.ant.Task.perform(Task.java:364)
[subant] at org.apache.tools.ant.Target.execute(Target.java:301)
[subant] at org.apache.tools.ant.Target.performTasks(Target.java:328)
[subant] at org.apache.tools.ant.Project.executeTarget(Project.java:1215)
[subant] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:383)
[subant] at org.apache.tools.ant.taskdefs.SubAnt.execute(SubAnt.java:182)
[subant] at org.apache.tools.ant.taskdefs.SubAnt.execute(SubAnt.java:112)
[subant] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:269)
[subant] at org.apache.tools.ant.Task.perform(Task.java:364)
[subant] at org.apache.tools.ant.Target.execute(Target.java:301)
[subant] at org.apache.tools.ant.Target.performTasks(Target.java:328)
[subant] at org.apache.tools.ant.Project.executeTarget(Project.java:1215)
[subant] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:379)
[subant] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:135)
There is no diffrent between using ant in eclipse environment or as standalone, the result it the same.
Do someone else have the same problem?
Kind regards
Joseph

Hi
I got the same message and I couldn't resolve it too, I am wordering if you got the key to the problem?
Thanks
Daivd Huang

Is wldeploy ANT task just always says "BUILD SUCCESFUL" ?

Hi All,
Iam using ANT and my build.xml file looks something like this:
<target name="deploy-now">
<echo message="...........This is the developmenet
box...deploying......"/>
<wldeploy action="${deploy.utility}" upload="true"
source="${source}" user="system" password="weblogic" nostage="true" verbo
se="true" adminurl="${bedlam-t.admin.url}" debug="true"
targets="${cmApplication.target}"/>
</target>
<target name="deploy-cm-testnet">
<antcall target="deploy-now"> <param name="source"
value="${cm1Application.source}"/>
</antcall>
<antcall target="deploy-now"> <param name="source"
value="${cm2Application.source}"/>
</antcall>
<antcall target="deploy-now"> <param name="source"
value="${cm3Application.source}"/>
</antcall>
</target>
So, basically iam calling my target "deploy-now" three times by using
<antcall>. Now my question is: iam getting BUILD SUCCESFUL although the
output looks like:
deploy-now: [echo] ...........This is the developmenet
box...deploying...... [wldeploy] weblogic.Deployer -debug -nostage -verbose -upload
-noexit -source
/export/home/beamon/applications/clientmanager/CMA_TW_333.war -targets UPSCAP
-adminurl http://bedlam-t.ams1907.com:8001 -user
system -password ******** -deploy
[wldeploy] DeploymentData : Delete Files:false [wldeploy] Timeout
:3600000 [wldeploy] Targets: [wldeploy] Files: [wldeploy] null
[wldeploy] Initiated Task: [87] [Deployer:149026]Deploy application
CMA_TW_333 on UPSCAP. [wldeploy] Application CMA_TW_333 preparing on
server upscap_bedlam1t_s1. [wldeploy] Module CMA_TW_333 failed to transition
from unprepared to prepared on server upscap_bedlam1t_s1. [wldeploy]
Application CMA_TW_333 failed on server upscap_bedlam1t_s1. [wldeploy]
Task 87 failed: [Deployer:149026]Deploy application CMA_TW_333 on UPSCAP.
[wldeploy] Deployment failed on Cluster UPSCAP [wldeploy] dumping
ApplicationException message
[wldeploy] Exception:weblogic.management.ApplicationException: prepare
failed for CMA_TW_333 [wldeploy] Module: CMA_TW_333 Error: Context path
'/CMA/US' is already in use by the module: CM_NO_333 application:
CM_NO_333
[wldeploy] dumping ApplicationException message
[wldeploy] Exception:weblogic.management.ApplicationException: prepare
failed for CMA_TW_333 [wldeploy] Module: CMA_TW_333 Error: Context path
'/CMA/US' is already in use by the module: CM_NO_333 application:
CM_NO_333
[wldeploy] Unpexpected Error Initializing Deployer:
weblogic.Deployer$DeployerException: Deployment exit status=1
deploy-now: [echo] ...........This is the developmenet
box...deploying...... [wldeploy] weblogic.Deployer -debug -nostage -verbose -upload
-noexit -source
/export/home/beamon/applications/clientmanager/CMA_NO_333.war -targets UPSCAP
-adminurl http://bedlam-t.ams1907.com:8001 -user
system -password ******** -deploy
[wldeploy] DeploymentData : Delete Files:false [wldeploy] Timeout
:3600000 [wldeploy] Targets: [wldeploy] Files: [wldeploy] null
[wldeploy] Initiated Task: [88] [Deployer:149026]Deploy application
CMA_NO_333 on UPSCAP. [wldeploy] Application CMA_NO_333 preparing on
server upscap_bedlam1t_s1. [wldeploy] Module CMA_NO_333: active to prepared
on server upscap_bedlam1t_s1. [wldeploy] Module CMA_NO_333: active to
prepared on server upscap_bedlam1t_s1. [wldeploy] Module CMA_NO_333:
prepared to unprepared on server upscap_bedlam1t_s1. [wldeploy] Module
CMA_NO_333: prepared to unprepared on server upscap_bedlam1t_s1.
[wldeploy] Module CMA_NO_333: unprepared to prepared on server
upscap_bedlam1t_s1. [wldeploy] Module CMA_NO_333: unprepared to prepared on server
upscap_bedlam1t_s1. [wldeploy] Application CMA_NO_333 prepared on server
upscap_bedlam1t_s1. [wldeploy] Application CMA_NO_333 activating on server
upscap_bedlam1t_s1. [wldeploy] Module CMA_NO_333: prepared to active on
server upscap_bedlam1t_s1. [wldeploy] Module CMA_NO_333: prepared to
active on server upscap_bedlam1t_s1. [wldeploy] Application CMA_NO_333
activated on server upscap_bedlam1t_s1. [wldeploy] Task 88 completed:
[Deployer:149026]Deploy application CMA_NO_333 on UPSCAP. [wldeploy]
Deployment completed on Cluster UPSCAP
BUILD SUCCESSFUL
Please advise ......how can i show that the BUILD is NOT succesful as
there were EXCEPTIONS generated.....is ANT just always says "BUILD
SUCCESFUL"

Infact it does complete, if i let it go on but it takes around 7 minutes more just to close the DM connection
[wldeploy] [ServerConnectionImpl.close():352] : Unregistered all listeners
[wldeploy] [ServerConnectionImpl.closeJMX():372] : Closed JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection
BUILD SUCCESSFUL
Total time: 7 minutes 15 seconds
is anybody facing this issue? Why is closing DM Connection and Unregistered all listeners taking so much time to complete for a WAR i.e. just a few KBs.
Please Help! Thanks!

Wldeploy ant task and WLS 7?

I'm trying to set up an ant task for WLDeploy in WLS 7. To docs reference the class as:
<taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy">
But where is that class? It's not in weblogic.jar.
TIA,
Jon

Just a followup: this ant task does not exist in early service packs. I'm not sure where it first shows up, but it does exist in SP 7.

Wldeploy ant task hangs at [ServerConnectionImpl.close():332] : Closing DM

Hi All
I am trying to deploy\undeploy a WAR file on weblogic server 10.3.5 using ANT wldeploy task, but no matter what i do it always hangs at the below and doesn't complete (although deployment and undeployment is successful)
[wldeploy] [BasicOperation.execute():445] : Initiating deploy operation for app, ABCD, on targets:
[wldeploy] [BasicOperation.execute():447] : osb_server1
[wldeploy] Task 38 initiated: [Deployer:149026]deploy application ABCD on osb_server1.
[wldeploy] Task 38 completed: [Deployer:149026]deploy application ABCD on osb_server1.
[wldeploy] Target state: deploy completed on Server osb_server1
[wldeploy]
[wldeploy] Target Assignments:
[wldeploy] + ABCD osb_server1
[wldeploy] [ServerConnectionImpl.close():332] : Closing DM connection
Below are the targets used in ANT script. Please help!
<target name="undeploy" depends="buildWar">
<wldeploy action="undeploy" name="ABCD" user="${username}" password="${password}" debug="true" verbose="true" adminurl="t3://${adminhost}:${adminport}" targets="${target}" failonerror="false"/>
</target>
<target name="deploy" depends="undeploy">
<wldeploy action="deploy" name="ABCD" source="${basedir}/ABCD.war" user="${username}" password="${password}" upload="true" debug="true" stage="true" verbose="true" adminurl="t3://${adminhost}:${adminport}" targets="${target}"/>
</target>

Infact it does complete, if i let it go on but it takes around 7 minutes more just to close the DM connection
[wldeploy] [ServerConnectionImpl.close():352] : Unregistered all listeners
[wldeploy] [ServerConnectionImpl.closeJMX():372] : Closed JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection
BUILD SUCCESSFUL
Total time: 7 minutes 15 seconds
is anybody facing this issue? Why is closing DM Connection and Unregistered all listeners taking so much time to complete for a WAR i.e. just a few KBs.
Please Help! Thanks!

Wldeploy/wlserver Ant tasks & cruisecontrol output

Hi,
We are using the wlserver and wldeploy Ant tasks with cruisecontrol. We have found that the output from these tasks in included in the cruise email which is sent out, and are looking for a way to redirect this output to a file so that cruise doesn't think that this is warning output from the JVM. Currently, with all the deploy messages weblogic publishes cruise thinks that our code has 500 warnings.
I would expect that this should be easy, but can't figure out for the life of me how to do it.
Regards

I'm coming back a few month later, and don't remember how I solved this problem. Today, I'm sure it is resolved, the task looks like this :
<wldeploy action="deploy"
source="${weblogic.deploy.dir}/${module.name}.ear"
name="${module.name}"
user="${weblogic.user}"
password="${weblogic.password}"
verbose="true"
adminurl="${weblogic.adminurl}"
debug="true"
targets="${weblogic.servers.name}" />
It should work since I've upgraded from WL 8.1 SP2 to WL 8.1 SP4.
Regards
Bernard

How to build ear files for ADF application using Ant task

How to build ear files for ADF applications using Ant. The ojdeploy ant task can not find application-level deployment profiles. I am trying to automated build and release for ADF application.
Any help is highly appreciated.
Thanks
Shiva

Hi Timo
Thanks for your reply.
I have successfully created ear file using ojdeploy on jenkins. however when am trying to auto deploy using WLDeploy ant task am getting the following
error :
weblogic.application.ModuleException: :oracle.mds.config.MDSConfigurationException:MDS-01335: namespace "/oracle/webcenter/quicklinks/scopedMD" mapped to metadata-store-usage "WebCenterFileMetadataStore" but its definition was not found in MDS configuration
Please advise how to handle this.
As am a newbie to ADF, could you please advise if it is possible for the ADF application deployments can be automated for different environments using jenkins due to this MDS dependencies.
Appreciate your help.
Thanks
Shiva

Weblogic 9.1 Deployment errors using the ANT task wldeploy

I am not able to deploy applicatons using the ANT task. The same works with Weblogic 8.1. It is throwing a NoClassDefFoundError. It is looking for a class by name javax/management/InvalidAttributeValueException.
This class file is shipped as part of jmx.jar. I tried to include it and then there was another NoClassDefFoundError that occured.
The problem is I don't want to keep adding these different jars to make the ant deployment work. Can anyone please let me know what could be the problem.
I am using a Windows XP OS and 1.4.2_10 as java version.
I have added all the jars in the weblogic91\server\lib directory to the classpath.
Also I have my apache ant tasks set in the classpath.
Thanks
Shankar Chandrasekaran

Have had a bit of these CLASSPATH issues when jumping versions.
Have had the best success when I create a different profile for each one, making sure the version you want is the only one defined. the main thing my profile sets is
unset PATH
unset CLASSPATH
unset JAVA_HOME
then
export PATH=
export CLASSPATH= the weblogic 9 one
export JAVA_HOME= the one with 9
or however they do it in windows, but make sure you CLASSPATH is only refencing the 9 jars

Built-in wlst ant task does not work in weblogic 10.3.1

Hi,
We have an installer script that deploys an ear file to a weblogic managed server. The script also invokes the build-tin wlst ant task to bounce the managed server. However, in version 10.3.1 the wlst task seems to be broken. I get this error:
[echo] [wlst] sys-package-mgr: can't create package cache dir, '/u00/webadmin/product/10.3.1/WLS/wlserver_10.3/server/lib/weblogic.jar/./java
tmp/wlstTemp/packages'
[echo] [wlst] java.io.IOException: No such file or directory
[echo] [wlst] at java.io.UnixFileSystem.createFileExclusively(Native Method)
[echo] [wlst] at java.io.File.checkAndCreate(File.java:1704)
[echo] [wlst] at java.io.File.createTempFile(File.java:1792)
[echo] [wlst] at java.io.File.createTempFile(File.java:1828)
[echo] [wlst] at com.bea.plateng.domain.script.jython.WLST_offline.getWLSTOfflineInitFilePath(WLST_offline.java:240)
[echo] [wlst] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[echo] [wlst] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[echo] [wlst] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[echo] [wlst] at java.lang.reflect.Method.invoke(Method.java:597)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTUtil.getOfflineWLSTScriptPath(WLSTUtil.java:63)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTUtil.setupOffline(WLSTUtil.java:214)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTInterpreter.<init>(WLSTInterpreter.java:133)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTInterpreter.<init>(WLSTInterpreter.java:75)
[echo] [wlst] at weblogic.ant.taskdefs.management.WLSTTask.execute(WLSTTask.java:103)
[echo] [wlst] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
Obviously that is not a valid directory...so I am wondering what it is trying to do, and why. The wlst task worked perfectly in 10.3.0. No changes were made when attempting to run the script against 10.3.0 and 10.3.1, which tells me that something is different with the 10.3.1 setup. Here is the ant code I am running:
<target name="init-taskdefs">
<taskdef resource="net/sf/antcontrib/antcontrib.properties">
<classpath>
<pathelement location="ant-ext/ant-contrib.jar" />
</classpath>
</taskdef>
<taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy" />
<taskdef name="wlst" classname="weblogic.ant.taskdefs.management.WLSTTask" />
</target>
<macrodef name="wlShutdownServer">
<attribute name="adminUser" default="${deploy.admin.username}" />
<attribute name="adminPassword" default="${deploy.admin.password}" />
<attribute name="adminUrl" default="${deploy.admin.url}" />
<attribute name="serverTarget" />
<sequential>
<trycatch property="server.error">
<try>
<wlst failonerror="true"
arguments="@{adminUser} @{adminPassword} @{adminUrl} @{serverTarget}">
<script>
adminUser=sys.argv[0]
adminPassword=sys.argv[1]
adminUrl=sys.argv[2]
serverTarget=sys.argv[3]
connect(adminUser,adminPassword,adminUrl)
target=getMBean("/Servers/"+serverTarget)
if target == None:
target=getMBean("/Clusters/"+serverTarget)
type="Cluster"
else:
type="Server"
print 'Shutting down '+serverTarget+'...'
shutdown(serverTarget,type,'true',15,force='true')
print serverTarget+' was shut down successfully.'
</script>
</wlst>

<echo message="Deleting any lok files that have not been removed..." />
<delete failonerror="false">
<fileset dir="${env.DOMAIN_HOME}/servers/@{serverTarget}" includes="**/*.lok"/>
</delete>
</try>
<catch>
<fail message="@{serverTarget} shutdown failed. ${server.error}" />
</catch>
<finally/>
</trycatch>
</sequential>
</macrodef>
Any help would be appreciated. Thanks!

Well, it looks like passing something like "-Djava.io.tmpdir=/var/tmp/javatmp/`date +%Y%m%d`" to ant did the trick. I had to make sure that directory existed first, otherwise it threw a java ioexception.
I still don't understand what changes between 10.3.0 and 10.3.1 to necessitate this change.

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

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?

<i>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><br>
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.
<p>
<i>I've only needed the weblogic.jar and xbean.jar, not all the ones you mentioned in an earlier thread of this post.</i><br>
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.
<p>
<i>Afterwards, I create an Ant Builder to build the JWS Web Service EAR, as opposed to fiddlin' with Eclipse.</i><br>
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.
<p>
<i>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..</i><br>
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.
<p>
Try my scenario. Add another operation to an existing WSDL, and run the wsdlc Ant Task. The old IMPL class will be over-written.
<p>
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.
<p>
<i>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.</i><br>
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.
<p>
<i>Regards,
Mike Wooten</i>
Thanks for the follow-up.
Mike McAngus

Using variables in WLST Script ant task

I have multiple scipts that are run using ant tasks, however, I do not want to have to enter the password every time one of these scripts is executed. Instead I would like to use the following ant task to store the password in a variable/property:
<target name="getPassword" >
     <echo message="Domain: ${domain}" />
<echo message="Username: system" />
<input message="Please enter password:" addproperty="password" />
</target>
I would then like to use that variable/property everytime a script is executed like this:
     <target name="deploy4x">
          <echo message="***** Copying 4X.ear *****" />
          <copy file="${build.path}\jar\4X.ear" todir="${apps.dir}" preservelastmodified="true"/>
          <echo message="***** Updating 4X.ear on ${domain} *****"/>
          <wlst debug="true" fileName="Deploy4X.py" executeScriptBeforeFile="true" failonerror="true" >
               <script>
                    connect('system','%s' % ${password},'%s' % $url)
               </script>
          </wlst>
     </target>
However, the script blows up every time I try to run it b/c of the connect() line. I have also tried connect('system','%s' % password, '%s' % url).
Has anyone else successfully used variables in an Ant WLST Script task?
Thanks.

Hi,
when I use *XDIM_MEMBERSET ACCOUNT AS %TEST% = BAS(REVENUE) - it work fine.
BUT ! after my first commit, it seems like the variable value is lost. And the *Xdim_memberset takes all.....
Fortunately enough, *select still contains the variable value after *commit.
Thanks,
Joergen
*Correction !
It actually works, it still contains the variable value after commit !!
Edited by: Jørgen Dalby Andersen on Dec 30, 2011 1:33 PM

Can i reference external flex-config in flexunit ant task?

flexunit gurus,
i'm trying to figure out how to best specify the compiler arguments for the flexunit ant task in flexunit 4.1 beta 1. from the documentation i see this sample flexunit usage:
<flexunit workingDir="${bin.loc}" toDir="${report.loc}"
haltonfailure="false" verbose="true" localTrusted="true">
<testSource dir="${main.src.loc}" />
<testSource dir="${test.src.loc}">
<include name="**/*Test.as" />
</testSource>
<library dir="${lib.loc}" />
</flexunit>
in this example, the source and library paths are explicitly listed. in this simple example all the needed libraries reside within a single directory.
when i build my application, i use a custom flex-config.xml file, as the following snippet shows:
        <mxmlc file="${application.file}" output="${swf.debug.file}" debug="true" headless-server="${headless.server}">
            <load-config filename="${flex.config.file}" />
        </mxmlc>
in that custom flex-config.xml file i list all the build options (e.g. source dirs, library paths, theme, etc.) appropriate for building the application. the libraries i reference are in a number of different directories (in general each 3rd party library is in a different directory).
in the flexunit task, i could individually reference all the same libraries that are in the flex-config.xml, but that'd be a pain to keep them in sync. i suppose i also could parse the flex-config.xml to extract the library information and use that to populate the library argument. really what i want to say in the flexunit task is "build all source and tests as indicated in flex-config.xml, then run the tests", perhaps with a syntax like the following:
<flexunit workingDir="${bin.loc}" toDir="${report.loc}"
haltonfailure="false" verbose="true" localTrusted="true">
            <load-config filename="${flex.config.file}" />
<testSource dir="${test.src.loc}">
<include name="**/*Test.as" />
</testSource>
<library dir="${flexunit.lib}" />
</flexunit>
i'd rather keep the flex-config.xml file free of any test specific information, so ideally i'd specify the path to the flexunit swc's and the test path in the flexunit task (as in the above example).
is there support for such usage currently or planned for in the future? recommendations on how best to accomplish my goal of not duplicating library information already present in a custom flex-config.xml?
thanks.
-mike

hi brian,
thanks for your response.
i understand the desire to avoid re-implementing the flex sdk ant tasks. i'm not sure that can reasonably be accomplished wihen the TestRunner is dynamically generated from within the flexunit task. in addition to the source path and library path, the theme setting and namespaces settings can affect successful compilation, and the runtime-shared-library-path setting can affect whether the produced swf runs correctly.
perhaps there's an alternative. what if we separate the creation of the TestRunner.mxml from the compilation and the execution of the tests. if flexunit offers an ant task that can produce (but not run) a TestRunner.mxml, i can write the mxmlc task that compiles it properly, and then i can invoke the old style flexunit specifying the swf argument. this would still accomplish my primary goal of not needing to manually enumerate every test file in a TestRunner.mxml that i have to maintain (and which neither Flash Builder nor maven builds require). to compile the TestRunner.mxml, i'd load in my custom flex-config.xml, then append to the source path and library path to include my test directory and flexunit libraries.
maybe something like the following to create the TestRunner:
<generatetestrunner output="${bin.loc}/TestRunner.mxml">
          <testSource dir="${test.dir}">
             <include name="**/*Test.as" />
          </testSource>
</generatetestrunner>
thoughts?
one other thing i noticed about the current library argument to flexunit is that it assumes a directory even if you provide an explicit path to an swc (i tried switching <library dir...> to <library file...> but that didn't seem to make a difference). in my case, there are specific swc's i need in the library path, and the task assuming i mean a directory when i specify an explicit swc is problematic. the directory my swc libraries are contained in sometimes contain multiple and conflicting versions of a library (each library directory contains various snapshot builds of the library). i need a way to explicitly indicate which library to use.
finally, could you point me to the java source for the flexunit ant tasks? i've found the flexunit action script source ok but haven't found where the java ant task is defined.
thanks.
-mike

WL8.1 wldeploy Ant Task seems to be fairly slow...

Similar Messages

Maybe you are looking for