Deploy and Bind ant tasks

Re,
I am using the 10.1.3 beta of oc4j and we are starting to run into some problems with using the oracle deploy and bind ant tasks provided. As our application is growing, the deploy task is taking longer and longer (which by itself is not really a problem since that is to be expected, and when I say long it is only a few seconds so it is tolerable). The problem (I think) lies in the ant tasks. Our "bind" tasks depends on the "deploy" task. But, it seems that sometimes the bind task actually starts before the deploy task is finished. So, we are wondering if there is something wrong with the deploy task. Either oc4j is sending a signal that the deploy is complete before it actually is or the deploy ant task is just waiting a few seconds and then assuming it is complete.
The only way for us to make this problem go away is to run the deploy ant task, look at the console to see that the deploy is finished and then run the bind task separately. Needless to say, that is a bit annoying and hard to automate.
Any ideas?

Chris,
Thanks. I dont think that is it. The process waits a while (so maybe they are the ones doing a sleep).
I am hoping to find out what is actually happening under the hood and if there is in fact a 'wait' giong on, implore to the development staff that they fix that issue before things are GA. Or, if something else is going on ... maybe I can fix it on my end.
Thanks,
Greg

Similar Messages

Convert Deployment profile to ant tasks

There is any utility to convert deployment profiles (.deploy files) to ant tasks? We are working with Jdev 10.1.3.2
Thank's in advance.
Julio.

Julio,
Nope. 11g has a nice utility called "ojdeploy" that can be called from ANT, but no help in 10g.
John

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

Error during deploying using sapdeploy ant task

I am attempting to deploy a simple service which I have created using Dev studio. Instead of deploying using Dev studio, I want to use ant task for the same.
This is the output I see in the console:
deploy:
[sapdeploy] Starting deployment with the following properties:
[sapdeploy] Version Handling Rule: all
[sapdeploy] Error Handling Strategies: [error action: 'prerequisites', error strategy: 'stop', error action: 'deploy', error strategy: 'stop']
[sapdeploy] The targeted SAP J2EE Engines are: [server host: 'myhost', server port '50000', user name 'J2EE_ADMIN'.]
[sapdeploy] Starting to validate the data...
[sapdeploy] Validation ended
[sapdeploy] root dir C:\temp\HelloWorldEAR
[sapdeploy] Selected archives for deployment:
[sapdeploy] 1: 'C:\temp\HelloWorldEAR\HelloWorldEAR.ear'
[sapdeploy] Starting validation for the engine 'server host: 'myhost', server port '50000', user name 'J2EE_ADMIN'.'
[sapdeploy] Engine data validated successfully
[sapdeploy] Starting deployment for the engine 'server host: 'myhost', server port '50000', user name 'J2EE_ADMIN'.'
[sapdeploy] An error occured during the deployment.
[sapdeploy] The result of the deployment is: Error
[sapdeploy] Deployment ended
Where can I get more details of what might be wrong with the deploy process? I tried "-v" flag but to no avail. Syslog of the server shows nothing of interest.
Thanks in advance for any help.
Regards,
Sameer

Logs will be in log\dc_log folder.

Bugs in jdoc and jdoclet Ant tasks?

(The relevant lines in the build.xml file are at the end of this message.)
I encountered a problem with the jdoc Ant task:
- I added a description for a class in the metadata file. Everything rans
fine. Then I added another class to the metadata file, when the jdoc task
is invoked again by Ant the new class is not enhanced at all.
- However when I run the jdoc on the metadata file outside Ant, the new
class is enhanced.
I can't run the jdoclet task at all because Ant complains that it can't
find the class com.solarmetric.modules.integration.ant.KodoDocletTask.
However it doesn't have any problem finding the class
com.solarmetric.modules.integration.ant.JDOEnhancerTask. Aren't they both
in the kodo-jdoee.jar? I also tried using the classpath element inside the
target for the jdoclet without success.
Thanks for your help.
Here is an extract of the build.xml file:

<path id="classpath">
<pathelement location="d:/books/JDO/KODO/kodo-jdoee2.3.3/lib/jdo1_0.jar"/>
<pathelement
location="d:/books/JDO/KODO/kodo-jdoee-2.3.3/lib/kodo-jdoee.jar"/>
<pathelement location="C:\java\xdoclet-1.1.2\lib\xdoclet.jar"/>
</path>
<target name="taskdefs">
<taskdef name="jdodoclet"
classname="com.solarmetric.modules.integration.ant.KodoDocletTask"/>

<taskdef name="jdoc"
classname="com.solarmetric.modules.integration.ant.JDOEnhancerTask"/>

<target name="enhanceAll" depends="compile">
<jdoc>
<fileset dir="./classes/quocp">
<include name="ent.jdo" />
</fileset>
<config licenseKey="<license key removed>" />
<classpath refid="classpath"/>
</jdoc>
</target>

Actually I did have a classpath issue, the xdoclet jar was not being
included properly; once I got it included I now get this error:
BUILD FAILED: java.lang.LinkageError: duplicate class definition:
org/apache/log4j/Category
I think the xdoclet is incompatible with the version of log4j I have....but
I don't know for certain.
So I tried moving to the latest and greatest xdoclet and now I get a new
error (and it fails earlier):
Finding class com.solarmetric.modules.integration.ant.JDODocletSubTask
Exception reading component C:\dev2\java\devlib\kodo-jdo.jar
BUILD FAILED: java.lang.NoClassDefFoundError:
com/solarmetric/modules/integration/ant/JDODocletSubTask
One thing I have learned today is the -debug flag when running ant...very
helpful in finding out where the failure is occuring.
Any ideas you might have on how to proceed would be helpful...is there a way
to run the xdoclet stuff without the ant tasks?
Thanks,
Steven Balthazor
"Marc Prud'hommeaux" <[email protected]> wrote in message
news:[email protected]...
Steven-
If you include the Kodo devel jars in your system CLASSPATH, does it
work? I.e., is it a problem with the classpath, or with the XDoclet
integration in general?
In article <[email protected]>, Steven Balthazor wrote:
I have followed these instructions to the letter; but I am unable to get
the
Doclet task to work in ant. Specifically my taskdef:
<taskdef name="jdodoclet"
classname="com.solarmetric.modules.integration.ant.KodoDocletTask">
<classpath refid="cp" />
</taskdef>
Generates the following error when running ant:
BUILD FAILED: file:C:/dev2/java/devbuild.xml:54: taskdef class
com.solarmetric.modules.integration.ant.KodoDocletTask cannot be found
Now I would think this is a classpath problem; except if I change the
taskdef to:
<taskdef name="jdodoclet"
classname="com.solarmetric.modules.integration.ant.SchemaToolTask">
<classpath refid="cp" />
</taskdef>
I get a new error:
BUILD FAILED: file:C:/dev2/java/devbuild.xml:56: The <jdodoclet> task
doesn't support the nested "jdotags" element.
This looks like it is finding the SchemaToolTask and failing in the
implementation of jdodoclet. As far as I can tell, KodoDocletTask and
SchemaToolTask are in the same jar. So what gives?
I am using Kodo 2.5.2; and I have Xdoclet 1.1.2 in my classpath.
Any help would be appreciated.
Steven Balthazor
"Patrick Linskey" <[email protected]> wrote in message
news:[email protected]...
I'm guessing that the kodo jars are not in the classpath when you
launch
ant. If this is the case, then you must specify a classpath in your
taskdef, and probably in the jdodoclet execution as well. You can do
this with something like this:
<target ...>
<taskdef ...>
<classpath refid="cp"/>
</taskdef>
<jdodoclet ...>
<classpath refid="cp"/>
</jdodoclet>
</target>
This assumes that you've defined a path somewhere in your ant buildfile
with an id of 'cp'.
-Patrick
Quoc Pham wrote:
Hi Patrick,
I still haven\'t been able to solve the problem with the jdoclet
task:
>>>>
>>>>
I can\\\'t run the jdoclet task at all because Ant complains thatit
>>>>
can\\\'t
find the class
com.solarmetric.modules.integration.ant.KodoDocletTask.
However it doesn\\\'t have any problem finding the class
com.solarmetric.modules.integration.ant.JDOEnhancerTask. Aren\\\'tthey
both
in the kodo-jdoee.jar? I also tried using the classpath element
inside
the
target for the jdoclet without success.
Here is the jdoclet task:
classname=\\\"com.solarmetric.modules.integration.ant.KodoDocletTask\\\"/>
>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
When I run the above task, I got the error message:
Buildfile: build.xml
generateJdoMetadata
BUILD FAILED
file:d/jdev903/jdev/mywork/JDO/Ent/build.xml:102:taskdef class
com.solarmetric.modules.integration.ant.KodoDocletTask cannot be
found
>>>>
>>>>
Questions:
- How do I let ant know the class path to use to run this task?
- What should the value of sourcepath be?
- What should the value of dir be? The directory where the .javafiles
reside?--
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Where are the bpelc and related ant tasks documented?

Hi,
Can anyone tell me where the soa suite-related ant tasks are documented? I only found a little bit of information and some examples in the developers guide.
Thanks,
Mark Nelson

chapter 19.4.2.
http://download-east.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/deployproc.htm#sthref3614

Eclipse and WebLogic Ant Tasks

In WL_HOME/server/lib/ant/ is an ant.jar. It has a "defaults.properties" containing all of the ant taskdefs. I tried to extract that so that my build.xml could use them but it keeps complaining about weblogic.ant.taskdefs.perforce.P4Changes cannot be found. The reason why is that it's under the wrong package. How does one run the weblogic ant tasks outside of the weblogic ant installation? Thanks, Jeremy

bengali.Hi,
you also have to include a <taskdef> for the servicegen task of >weblogicThat's why I did but I still have a problem with the source2wsdd
ant task ( the other tasks run correctly within Eclipse).
I get a :
[source2wsdd] source2wsdd: Cannot find doclet class weblogic.webservice.tools.ddgen.ServiceGen
[source2wsdd] 1 error
BUILD FAILED: build.xml:324: javadoc execution failed
Total time: 3 seconds
The problem is that my source2wsdd has been defined with a well suited classpath
and is also called with the right classpath.
The problem only happens with this task !
Bengali

LDAP Broken Pipe exception when deploying processes via ant task

Hi,
Has anyone experienced this and can offer a fix? We are publishing/deploying our processes using the fuego:publish task in Fuego 5.7 (we are migrating our system from 5.1) and one of the publish tasks for a large project always fails with the following exception:
Caused by: fuego.directory.CommunicationException: Cannot connect to the Directory Service at: [iplanet://zion:28899/o=nexagent.com].
Detail:The Directory Service could not be reached. Either the Directory Service is down, the host where it resides is unavailable, a network problem exists, or there is no Directory Service at the specified location.
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:465)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:489)
at fuego.directory.provider.ldap.LDAPProjectAccessor.createCatalogJar(LDAPProjectAccessor.java:160)
at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:257)
at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:46)
at fuego.mami.CatalogPublisher.store(CatalogPublisher.java:369)
at fuego.mami.ProjectPublisher.storeCatalog(ProjectPublisher.java:1631)
at fuego.mami.ProjectPublisher.storeProject(ProjectPublisher.java:1653)
at fuego.mami.ProjectPublisher.publish(ProjectPublisher.java:854)
at fuego.tools.ant.enterprise.impl.PublishProjectTaskImpl.execute(PublishProjectTaskImpl.java:377)
... 23 more
Caused by: javax.naming.CommunicationException: Broken pipe [Root exception is java.net.SocketException: Broken pipe]; remaining name 'cn=catalogJar-3,cn=fuego-dirCatalogJars,cn=fuego-directoryRoot'
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:803)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:178)
at fuego.jndi.FaultTolerantDirContext.createSubcontext(FaultTolerantDirContext.java:413)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createNestedEntry(LDAPPersistenceManager.java:1744)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:455)
... 32 more
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:389)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:364)
at com.sun.jndi.ldap.LdapClient.add(LdapClient.java:1007)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:766)
... 39 more
Looking at the LDAP access log the error code is B1 which means that the client closed the connection without sending an unbind request or it could also mean that the client sent a malformed request to the server. The project being deployed is quite big and fails when storing the catalog, could the size have something to do with it (this worked in v5.1) is this a bug in 5.7?
Any help would be greatly appreciated!
regards,
Mike

Hi,
Has anyone experienced this and can offer a fix? We are publishing/deploying our processes using the fuego:publish task in Fuego 5.7 (we are migrating our system from 5.1) and one of the publish tasks for a large project always fails with the following exception:
Caused by: fuego.directory.CommunicationException: Cannot connect to the Directory Service at: [iplanet://zion:28899/o=nexagent.com].
Detail:The Directory Service could not be reached. Either the Directory Service is down, the host where it resides is unavailable, a network problem exists, or there is no Directory Service at the specified location.
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:465)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:489)
at fuego.directory.provider.ldap.LDAPProjectAccessor.createCatalogJar(LDAPProjectAccessor.java:160)
at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:257)
at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:46)
at fuego.mami.CatalogPublisher.store(CatalogPublisher.java:369)
at fuego.mami.ProjectPublisher.storeCatalog(ProjectPublisher.java:1631)
at fuego.mami.ProjectPublisher.storeProject(ProjectPublisher.java:1653)
at fuego.mami.ProjectPublisher.publish(ProjectPublisher.java:854)
at fuego.tools.ant.enterprise.impl.PublishProjectTaskImpl.execute(PublishProjectTaskImpl.java:377)
... 23 more
Caused by: javax.naming.CommunicationException: Broken pipe [Root exception is java.net.SocketException: Broken pipe]; remaining name 'cn=catalogJar-3,cn=fuego-dirCatalogJars,cn=fuego-directoryRoot'
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:803)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:178)
at fuego.jndi.FaultTolerantDirContext.createSubcontext(FaultTolerantDirContext.java:413)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createNestedEntry(LDAPPersistenceManager.java:1744)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:455)
... 32 more
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:389)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:364)
at com.sun.jndi.ldap.LdapClient.add(LdapClient.java:1007)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:766)
... 39 more
Looking at the LDAP access log the error code is B1 which means that the client closed the connection without sending an unbind request or it could also mean that the client sent a malformed request to the server. The project being deployed is quite big and fails when storing the catalog, could the size have something to do with it (this worked in v5.1) is this a bug in 5.7?
Any help would be greatly appreciated!
regards,
Mike

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

Execute deployment profile in ant

Hi,
is it possible to execute a deployment profile create in JDeveloper in ant?
Thanks,
Koen
[edit]
Started topic before searching the forum.
Re: How can I integrate JDeveloper Deployment profiles into an Ant build sc
Does not seems to work.
[edit]

Hi Koen,
Although there is no way to maintain/generate the ant buildfile directly, it is not too hard to write a buildfile that can build the war/ear and then deploy it. On these links you can find some information on how to do that:
* [Using OC4J Ant tasks for deployment|http://download.oracle.com/docs/cd/E12524_01/web.1013/e12289/anttasks.htm#BEIGEEID]
* [Deploying your webcenter app with ant tasks|http://download.oracle.com/docs/cd/B32110_01/webcenter.1013/b31074/jpsdg_deploy.htm#BGBIIFCC]
Basically, you can use <oracle:deploy/> and alike tasks to deploy your app, and other ant tasks to create datasources and shared libraries.
Regards,
Jeroen van Veldhuizen

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

Java.lang.NullPointerException running flexunit ant task in 4.1 Beta 2

Hello,
After trying to debug this all day, I thought I would ask the community.
I am trying out the new FU4.1 Beta 2 (3.5) from the downloads page. We have a working CI system set up with 4.0, and I thought trying out 4.1 beta 2 would simply be a matter of replacing the binaries in my lib folder and re-running the ant script. Evidently not, or else I am missing something.
After updating to the 4.1 Beta 2 binaries, if I re-run a sample project in Eclipse, the build fails with a java NullPointerException when the <flexunit> ant task is invoked. We have an involved setup that uses the groovy AntBuilder and other esoteric constructs, so I thought I would create a very simple test script similar to the sample CI project to see if that would work. Unfortunately, I am still seeing the NPE. The worst part is that there is absolutely no debug information provided - no message, no traceback. I even attached the Ant source and debugged it. I could see the NPE being caught, but it contained a null message and null traceback.
Here is the simplified ant script:
<project name="tests" basedir=".">
 <target name="test-init" depends="">
 <mkdir dir="${build.dir}"/>
 <mkdir dir="${reports.dir}"/>
 <mkdir dir="${reports.xml}"/>
 <mkdir dir="${reports.html}"/>
 
 
 <flexunit
 swf="${build.dir}/TestRunner.swf"
 toDir="${reports.xml}"
 haltonfailure="false"
 verbose="true"
 localTrusted="true"
 timeout="60000"/>
 
 <junitreport todir="${reports.xml}">
 <fileset dir="${reports.xml}">
 <include name="TEST-*.xml" />
 </fileset>
 <report format="frames" todir="${reports.html}" />
 </junitreport>
 </sequential>
 </target>
</project>
The output is:
Buildfile: C:\EclipseWorkspace\tests\Source\Flex\build_test.xml
test-init:
run-flex-tests:
[flexunit] Validating task attributes ...
BUILD FAILED
C:\EclipseWorkspace\tests\Source\Flex\build_test.xml:23: java.lang.NullPointerException
Total time: 297 milliseconds
Is there something obvious I am missing?
Thanks for any help!
Trevor

Brian,
OK, a colleague worked with me (thanks, John!) to debug the problem a little further, and I think we found the fundamental problem. I wanted to post that info to save you some time...
Aside: One thing we did have to do was to rebuild the flexUnitTasks.jar to include debug information, since the binary in the 4.1 beta 2 package did not have debug=true. I'd suggest that we might want to change the build script to build the binaries with debug moving forward.
Back to the problem.
The NullPointerException is thrown in TaskConfiguration::validateSharedProperties(), when equals() is invoked. Here is the code snippet:
 //if we can't find the FLEX_HOME and we're using ADL or compilation
 if((flexHome == null || !flexHome.exists()) && (testRunConfiguration.getPlayer().equals("air") || shouldCompile()))
 throw new BuildException("Please specify, or verify the location for, the FLEX_HOME property. "
 + "It is required when testing with 'air' as the player or when using the 'testSource' element. "
 + "It should point to the installation directory for a Flex SDK.");
In my case, I do not have a FLEX_HOME property set in Ant currently. I'll bet most folks have this set, so the logic would run differently for them. For my case, the (flexHome == null) check is true. That means that the testRunConfiguration.getPlayer().equals("air")check will occur next, and here is the problem. The "player" member is not set in the testRunConfiguration yet at this point, so testRunConfiguration.getPlayer() returns null. testRunConfiguration.setPlayer() is called in generateDefaults(). But generateDefaults() is not called until after validateSharedProperties() is called. So, if properties initialization could be improved here and I think this code will run more robustly.
I can work-around my issue temporarily by just setting a FLEX_HOME property in Ant. But I hope you will agree that the initialization issue with "player" still should be addressed. Would you like me to open a bug report, or is this thread enough?
Thanks,
Trevor

Ant Tasks for Pointbase

In the online Docs, I found info regarding creating ant tasks to start and configure
the WebLogic server. But I would like to also have an ant task that will start
Pointbase. I have created ant tasks that will connect to pointbase and create/fill
a database and another ant task that will drop a database. But I can't find any
info about starting the Pointbase database. All of the BEA documentation only
says to manually start the Pointbase database and then continue.
Has anyone created or knows of an ant task that will launch Pointbase?? In my
case, I'm only trying to launch and use Pointbase from the BEA directories.
Jerald

We have an ant task, but we dont doc it. This is in 8.1
<taskdef name="pointbase"
classname="weblogic.ant.taskdefs.pointbase.PointBase"/>
<property name="pointbase.dbfile"
value="${database.dir}/${pointbase.db.name}.dbn"/>
<property name="pointbase.log" value="pointbase.log"/>
<property name="pointbase.driver"
value="com.pointbase.jdbc.jdbcUniversalDriver"/>
<property name="pointbase.url"
value="jdbc:pointbase:server://${pointbase.host}:${pointbase.port}/${pointba
se.db.name}"/>
<property name="pointbase.url.new"
value="jdbc:pointbase:server://${pointbase.host}:${pointbase.port}/${pointba
se.db.name},new"/>
<target name="db.start">

<echo message="Starting Pointbase..."/>
<pointbase displaylevel="3" file="${pointbase.log}"
home="${database.dir}"/>
<sleep seconds="5"/>
</target>
Cheers
mbg
"Jerald Pratt" <[email protected]> wrote in message
news:3f94d989$[email protected]..
>
In the online Docs, I found info regarding creating ant tasks to start andconfigure
the WebLogic server. But I would like to also have an ant task that willstart
Pointbase. I have created ant tasks that will connect to pointbase andcreate/fill
a database and another ant task that will drop a database. But I can'tfind any
info about starting the Pointbase database. All of the BEA documentationonly
says to manually start the Pointbase database and then continue.
Has anyone created or knows of an ant task that will launch Pointbase??In my
case, I'm only trying to launch and use Pointbase from the BEAdirectories.
>
Jerald

Class generated by genInterface ant task does not compile

I am trying to build a web service from existing wsdl using genInterface and topDownAssemble ant tasks.
The wsdl contains following type definition. Java class generated from this type (see below) does not compile. The problem is that there are two class members named
'value'. Is this an issue with Web Services Assembly tool or there is some way to get
around it?
<s:simpleType name="quantityType">
<s:restriction base="s:string">
<s:enumeration value="summation"/>
<s:enumeration value="demand"/>
<s:enumeration value="value"/>
<s:enumeration value="consumption"/>
</s:restriction>
</s:simpleType>
// Version = Oracle WebServices (10.1.3.3.0, build 070610.1800.23513)
public class QuantityType implements java.io.Serializable {
private java.lang.String value;
private static final String _summationString = "summation";
private static final String _demandString = "demand";
private static final String _valueString = "value";
private static final String _consumptionString = "consumption";
public static final java.lang.String summation = new java.lang.String(summationString);
public static final java.lang.String demand = new java.lang.String(demandString);
public static final java.lang.String value = new java.lang.String(valueString);
public static final java.lang.String consumption = new java.lang.String(consumptionString);
public static final QuantityType summation = new QuantityType(_summation);
public static final QuantityType demand = new QuantityType(_demand);
public static final QuantityType value = new QuantityType(_value);
public static final QuantityType consumption = new QuantityType(_consumption);
Andrei

Pls set debug attribute of JWSC ant task to true or on, e.g.
<jwsc srcdir="." destdir="${output.dir}" debug="on" keepGenerated="true">
</jwsc>

Deploy and Bind ant tasks

Similar Messages

Maybe you are looking for