Weblogic 8.1 to 9.2 using Weblogic-Application-Version - weblogic.developer.interest.webservices.general(Archived)

Hi,
We have an ear file with web service and ejb in it deployed in 8.1. We deployed it in 9.2 and works fine. We added Weblogic-Application-Version in manifest file to take advantage of application versioning feature of 9.2 but it failed to deployed. Our other application with annotated web service and compiled using jwsc and with Weblogic-Application-Version in manifest file works fine. Seems web service done in 8.1 cannot be ported in 9.2 with Weblogic-Application-Version in manifest file of 9.2. Please help on this. Below is the stack trace.
weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 15 failed: [Deployer:149026]deploy application SampApp [Version=1.0] on AdminServer.
Target state: deploy failed on Server AdminServer
[HTTP:101355][weblogic.webservice.server.servlet.WebServiceServlet#184a207] Version 1.0 is specified for WebServices SampService, but versioning of WebServices is not supported.
     at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:357)
     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
     at org.apache.tools.ant.Task.perform(Task.java:364)
     at org.apache.tools.ant.Target.execute(Target.java:341)
     at org.apache.tools.ant.Target.performTasks(Target.java:369)
     at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
     at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
     at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
     at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
     at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
     at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
     at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)
Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 15 failed: [Deployer:149026]deploy application SampApp [Version=1.0] on AdminServer.
Target state: deploy failed on Server AdminServer 

I've got the exakt same problem using weblogic.Deployer .... -appversion, weblogic 10.0 in this case. Works fine with our new jaxws based webservices.
Would be nice if this problem was solved, especially since weblogic10 resolves softlinks so our old method of linking to new versions doesn't work anymore. And the fact that "Changing the source location is not allowed for a previously attempted deployment" doesn't help either.

Related

customizeWSDL

Hello,
I am trying to create a pre-build action that sets the host name and the port of the services I have to call, because I need to deploy the application in different hosts.
I managed to deploy my application in 2 different computers but in the third one I have a problem with this operation (this is the line 32 of pre-build.xml that the error refers to):
<customizeWSDL infile="${basedir}/bpel/RegistroDoc.wsdl" outfile="${basedir}/bpel/RegistroDoc.wsdl">
<WSDLImport namespace="http://serviciocatalogo.simge.indra.es" locationURI="http://${host}:${port}/ServicioCatalogo_WS/services/GestorDocumento?wsdl"/>
</customizeWSDL>
The error message that I obtain when I execute ant deploy is the following:
Buildfile: build.xml
pre-build:
[echo] D:\product\10.1.3.1\OracleAS_1\bpel at bpel-ant.xml
[echo] D:\product\10.1.3.1\OracleAS_1\bpel\lib\orabpel-ant.jar
[echo] true
Trying to override old definition of task customize
Trying to override old definition of task customizeWSDL
pre-build:
[echo] pre build ant script executing...
BUILD FAILED
D:\Antiguo\Vacio_BPEL\Vacio_BPEL\build.xml:217: The following error occurred while executing this line:
D:\Antiguo\Vacio_BPEL\Vacio_BPEL\pre-build.xml:32: Problem instantiating factory implementation.: oracle.webservices.wsdl.WSDLFactoryImpl: java.lang.ClassNotFoundException: oracle.webservices.wsdl.WSDLFactoryImpl
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at javax.wsdl.factory.WSDLFactory.newInstance(WSDLFactory.java:75)
at javax.wsdl.factory.WSDLFactory.newInstance(WSDLFactory.java:54)
at com.collaxa.cube.ant.taskdefs.customize.wsdl.CustomizeWSDL.execute(CustomizeWSDL.java:43)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(Single
CheckExecutor.java:37)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe
cutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
Total time: 0 seconds
Anyone can tell me a possible solution to this issue?
Thanks in advance,
Ana 
looks like you're missing libraries on the classpath. Make sure you have the following jar-files on your classpath:
- orabpel-common.jar
- orabpel.jar
- xml.jar
- orabpel-ant.jar
- orabpel-boot.jar
- bpm-services.jar
- bpm-infra.jar
- oc4jclient.jar
These work fine for us.
HTH,
Bas 
If you also want to deploy human tasks use the following libs:
adminclient.jar
connector15.jar
ejb.jar
javax77.jar
javax88.jar
oc4jclient.jar
oc4j-internal.jar
optic.jar
orabpel-ant.jar
orabpel-common.jar
orabpel-exts.jar
orabpel.jar
orabpel-thirdparty.jar
oracle_http_client.jar
orawsdl.jar
xmlparserv2.jar
and point to the 'schema' directory where the human-tasks XSD's are defined.
Ant-build-system can be downloaded here (updated for 10.1.3.3):
http://orasoa.blogspot.com
Message was edited by:
Marc Kelderman 
Hello,
When you say that it looks like I have missing libraries on the classpath, where can I check them? Do I have to change something of the ant folder? Do I have to change any environment variables?
Thanks,
Ana 
Hello,
I have solved the issue. I have to add in the path environment variable the ant directory of oracle soa suite (D:\product\10.1.3.1\OracleAS_1\ant\bin). That works ok with the BPEL, however if I have to deploy an ESB process I have to delete the ant directory of oracle soa suite in the system path because ESB deployment uses ant-1.7.0. Does anybody know what I can do so I don't have to change this variable every time I have to deploy an ESB and a BPEL?
Thanks,
Ana 
Hi Baastian,
I read that you are working with this ant task and is working ok, right? I also want to use it to deploy BPEL processes with ant. I would like to get some information about this tag and the way it works because I'm having some problems using it.
I have this sentences in my pre-build file:
<customizeWSDL infile="${basedir}/bpel/NotificarClientes_WS.wsdl" outfile="${basedir}/bpel/NotificarClientes_WS.wsdl">
<WSDLImport namespace="http://es/indra/simge/servicios" locationURI="http://${notificar.clientesWS.hostname}:${notificar.clientesWS.port}/SimgeVyAWS/IntegracionWS?wsdl"/>
</customizeWSDL>
And NotificarClientes_WS.wsdl has this sentence:
<import namespace="http://es/indra/simge/servicios" location="http://madarrppsimge01.indra.es:7001/SimgeVyAWS/IntegracionWS?wsdl"/>
It works alright if I have connection to that URL, but if I don't, I get the following error:
Error reading import of file:/D:/proyectos/UME/repositorio/SIMGE/branches/ANA-NuevaArquitectura/Fuentes/EAI/Comun/FinalizarProceso_BPEL/bpel/NotificarClientes_WS.wsdl: Fallo al leer WSDL de http://madarrppsimge01.indra.es:7001/SimgeVyAWS/IntegracionWS?wsdl: El codigo de error de la conexion HTTP es 403:
Which means that is trying to connect to that URL in order to execute the task. Does that make sense? I mean, if I want to deploy my BPEL process (which I developed in the development environment) in the production environment, I wont have connection to the development host, so the ant task customizeWSDL is not going to work.
Am I right? Can anyone explain me how this task works?
Thanks in advance,
Zaloa

Dealing with changing service wsdl locations  in the ESB

Hi,
I wonder how you can easily change the WSDL locations for the webservices in the SOAP services of your ESB project. I need this to be able to easily deploy an ESB project on the different OTAP environments.
I have looked for a solution myself, but till now I must conclude that you need to make a new SOAP service each time the WSDL location changes. Also, you need to make a new xslt mapping file in the routing service that is proxying the SOAP service, because the mapping file also contains/needs WSDL location information. I omit the option to manually edit the source files in my favourite text editior, because this is not want you want by default.
BPEL contains a wsdlRuntimeLocation parameter for its PartnerLink definitions, which you can use to change wsdl locations during environment change. I hope the ESB also has a comparable option to make environment changes easy...
Regards,
-Tom 
See Re: Regarding ESB Deployment without using JDeveloper 
Hi Dave. Your posts are really appreciated, however I have to confess that I don't see the answer to the question in that thread and I'm having the same problem - or at least I think I am!
I have an ESB project that calls a web service. On dev, I want my ESB service to call the dev web service. When I deploy to QA, I need the WSDL of the web service to be changed to that of the QA system. And then again when we deploy to production.
I was really hoping we woudn't have to use ANT to modify the WSDL URL in the .esbsvc files.
Richard Davis 
Hi Richard,
Maybe the Oracle Registry is a better option. The Oracle registry allows you to hide concrete urls behind a business key, so that you are able to deploy on different platforms without needing to change the wsdl references..
My experience so far with the Oracle Registry is of the beginners level, but a colleague of my advised me to use the Oracle Registry.
regards,
-Tom 
Richard,
That link points to the ESB Ant deployment zip bundle that enables the ability to deploy using Ant and changing endpoint locations using a deployment plan.
http://www.oracle.com/technology/products/integration/esb/files/esbdeploymentautomation.zip 
Hi Dave,
Your Ant extension is really useful for our purpose. Thanks on that!
I still have one question for you regarding the extraction of the deployment plan for an esb project. Is it possible to automatically extract the correct deployment plan for a specific deployment environment? Or do you extract the deployment plan once and after that you can edit the plan manually to make specific deployment plans for the different environments?
Regards,
Tom 
The latter. Extract the plan once then copy and update different plans for each target environment. 
Provided ExtractDeploymentPlan Ant task is definitely very useful. To avoid people (admin/configuration management) making changes to extracted DP in XML format, we developed another custom task to modify the DP XML automatically by reading the property values from simple target environment properties file. This way all you need to do is maintain properties file for each target environment and use the respective one during deployment.
The basic thinking for this extension is Admin people find making changes to properties file easier than actually understanding the DP schema.
Mentioned properties file has the following simple format:
<serviceDeploymentPlanQName>.<property name>=<property value>
For example:
DefaultSystem.someGroup.esbServiceX.wsdlURL=${wsm.gwy.url}/gateway/services/SID300011?WSDL
You only need to specify the values you want to override in this file.
So our high level deployment involves following Ant task automation:
1. CVS checkout of ESB project
2. Extract Deployment Plan
3. Inject deployment properties
4. Register the project
When I find sometime I will try to post this on my Blog and provide more details.
HTH
Rajesh 
Hi Rajesh,
Your proposed extension sounds interesting. Is it still under development or is it already open for use? If the latter holds, is it possible for me to get your extension?
Regards,
-Tom 
Thanks, this is very helpful. The point I was missing was to use the ExtractESBDeploymentPlan. I was simply using the tool to register the services via Ant. Now that I understand that, I'm trying and getting the following error. (the project registers successfully from JDev and from the custom task)
C:\antBuild>ant -f esbBuild.xml test.ExtractESBDeploymentPlan
Buildfile: esbBuild.xml
test.ExtractESBDeploymentPlan:
[echo]
[echo] Extracting Deployment Profile
[echo] From: C:\Oracle\JDeveloper\jdev\mywork\CaseCentral\CaseCentralProviderInterface
[echo] To: C:\Oracle\JDeveloper\jdev\mywork\CaseCentral\CaseCentralProviderInterface\DevDeploymentPlan.xml
[echo]
[extractESBDeploymentPlan] java.lang.NullPointerException
[extractESBDeploymentPlan] at oracle.tip.esb.jdev.artifacts.model.ESBServiceArtifactContent.getServiceWsdlURL(ESBServiceArtifactContent.java:73)
[extractESBDeploymentPlan] at oracle.tip.esb.jdev.artifacts.model.ESBAdapterServiceArtifactContent.computeAdapterServiceWsdlFilename(ESBAdapterServiceArtif
actContent.java:107)
[extractESBDeploymentPlan] at oracle.tip.esb.jdev.artifacts.model.ESBAdapterServiceArtifactContent.doesFileRepresentAdapterServiceWSDLDocument(ESBAdapterSe
rviceArtifactContent.java:120)
[extractESBDeploymentPlan] at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.hydrateServiceDeploymentPlans(ExtractESBDeploymentPlanTask.java:3
25)
[extractESBDeploymentPlan] at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.constructDeploymentPlan(ExtractESBDeploymentPlanTask.java:477)
[extractESBDeploymentPlan] at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.execute(ExtractESBDeploymentPlanTask.java:543)
[extractESBDeploymentPlan] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[extractESBDeploymentPlan] at org.apache.tools.ant.Task.perform(Task.java:364)
[extractESBDeploymentPlan] at org.apache.tools.ant.Target.execute(Target.java:341)
[extractESBDeploymentPlan] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[extractESBDeploymentPlan] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[extractESBDeploymentPlan] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[extractESBDeploymentPlan] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
[extractESBDeploymentPlan] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[extractESBDeploymentPlan] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[extractESBDeploymentPlan] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[extractESBDeploymentPlan] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[extractESBDeploymentPlan] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
BUILD FAILED 
Hi,
I am getting a null-pointer exception when I run the task extractESBDeploymentPlan:
BUILD FAILED
E:\workdir\soa-blueprint\trunk\soa-tickets\ticket-esb\build.xml:67: java.lang.NullPointerException
     at org.apache.tools.ant.Task.perform(Task.java:373)
     at org.apache.tools.ant.Target.execute(Target.java:341)
     at org.apache.tools.ant.Target.performTasks(Target.java:369)
     at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
     at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
     at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
     at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
     at oracle.jdevimpl.ant.runner.AntLauncher.launch(AntLauncher.java:321)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at oracle.jdevimpl.ant.runner.InProcessAntStarter.runAnt(InProcessAntStarter.java:295)
     at oracle.jdevimpl.ant.runner.InProcessAntStarter.mav$runAnt(InProcessAntStarter.java:43)
     at oracle.jdevimpl.ant.runner.InProcessAntStarter$1.run(InProcessAntStarter.java:71)
Caused by: java.lang.NullPointerException
     at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.hasValidDeploymentPlanFilename(ExtractESBDeploymentPlanTask.java:101)
     at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.performSemanticValidation(ExtractESBDeploymentPlanTask.java:137)
     at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.execute(ExtractESBDeploymentPlanTask.java:524)
     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
     at org.apache.tools.ant.Task.perform(Task.java:364)
     ... 14 more
--- Nested Exception ---
java.lang.NullPointerException
     at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.hasValidDeploymentPlanFilename(ExtractESBDeploymentPlanTask.java:101)
     at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.performSemanticValidation(ExtractESBDeploymentPlanTask.java:137)
     at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.execute(ExtractESBDeploymentPlanTask.java:524)
     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
     at org.apache.tools.ant.Task.perform(Task.java:364)
     at org.apache.tools.ant.Target.execute(Target.java:341)
     at org.apache.tools.ant.Target.performTasks(Target.java:369)
     at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
     at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
     at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
     at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
     at oracle.jdevimpl.ant.runner.AntLauncher.launch(AntLauncher.java:321)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at oracle.jdevimpl.ant.runner.InProcessAntStarter.runAnt(InProcessAntStarter.java:295)
     at oracle.jdevimpl.ant.runner.InProcessAntStarter.mav$runAnt(InProcessAntStarter.java:43)
     at oracle.jdevimpl.ant.runner.InProcessAntStarter$1.run(InProcessAntStarter.java:71)
Total time: 0 seconds
I have made sure that all the needed libraries are found. I assume that the deployment file doen't need to exist yet.
Looking at the error-trace, i can see that the ant raises an error during the the validation of the deploymentplanfilename
I think i'm missing some essential initialization step..Do you know which?
Regards,
-Tom 
bump/
Does anyone has a suggestions how to solve my issue? 
Hi Tom
I had until now not run the extractESBDeploymentPlan option. Having done so, I initially got the NullPointerException due to an invalid file path in my build.xml. That fixed I now get the following error:
M:\utils\ESBAntDeploy>ant local.ExtractESBDeploymentPlan
Buildfile: build.xml
local.ExtractESBDeploymentPlan:
[extractESBDeploymentPlan] javax.xml.bind.JAXBException: Unable to locate jaxb.properties for package oracle.tip.esb.cli
ent.metadata.deploymentplan.model
[extractESBDeploymentPlan] at javax.xml.bind.ContextFinder.searchcontextPath(ContextFinder.java:205)
[extractESBDeploymentPlan] at javax.xml.bind.ContextFinder.find(ContextFinder.java:149)
[extractESBDeploymentPlan] at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:281)
[extractESBDeploymentPlan] at oracle.tip.esb.client.metadata.deploymentplan.utils.DeploymentPlanUtils.getJAXBContex
t(DeploymentPlanUtils.java:37)
[extractESBDeploymentPlan] at oracle.tip.esb.client.metadata.deploymentplan.utils.DeploymentPlanUtils.getMarshaller
(DeploymentPlanUtils.java:65)
[extractESBDeploymentPlan] at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.saveDeploymentPlan(Extrac
tESBDeploymentPlanTask.java:509)
[extractESBDeploymentPlan] at oracle.tip.esb.client.anttasks.ExtractESBDeploymentPlanTask.execute(ExtractESBDeploym
entPlanTask.java:544)
[extractESBDeploymentPlan] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[extractESBDeploymentPlan] at org.apache.tools.ant.Task.perform(Task.java:364)
[extractESBDeploymentPlan] at org.apache.tools.ant.Target.execute(Target.java:341)
[extractESBDeploymentPlan] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[extractESBDeploymentPlan] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[extractESBDeploymentPlan] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[extractESBDeploymentPlan] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
[extractESBDeploymentPlan] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[extractESBDeploymentPlan] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[extractESBDeploymentPlan] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[extractESBDeploymentPlan] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[extractESBDeploymentPlan] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
BUILD FAILED
M:\utils\ESBAntDeploy\build.xml:76: javax.xml.bind.JAXBException: Unable to locate jaxb.properties for package oracle.ti
p.esb.client.metadata.deploymentplan.model
Total time: 0 seconds
I have no idea what that error is about!!
Sorry, Chris 
Hi Chris,
I think you'd missing some jaxb.properties file (duh ;)). I can imagine that this should be included in the extension somewhere. Maybe it is not loaded on your classpath for some reason.
Thanks for your suggesting about incorrect paths. However, I have checked the paths also and guaranteed that all libs are found...Can you tell me which path was invalid in your case?
Can you also put the fragment of your build.xml here that covers the extractESBDeploymentPlan, so I can look at your working example.
Thanks for your help so far!
-Tom 
Thanks Tom, hadn't thought of that ;-)
I cannot find a jaxb.properties file in any jaxb or extension archives, so not sure where it's supposed to be! I'll keep looking!
Here's the part of the build.xml:
<property name="esbProject1" value="M:/code/jdev/ESBLLPGInbound"/>
<property name="localDeploymentPlanFilename" value="./localDeploymentPlan.xml"/>
<target name="local.ExtractESBDeploymentPlan">
<extractESBDeploymentPlan sourceDir="${esbProject1}" deploymentPlanFile="${localDeploymentPlanFilename}"/>
</target>
I had the NullPointer when it couldn't find the directory to put the output xml file in.
Cheers
Chris

Not able to deploy task forms from ant script

Hi,
I've created a process with a human workflow step. I'm then trying to deploy the process from a command window using the build.xml writing "ant deploy". But I get an error when the workflow form is to be deployed:
...
deployTaskForm:
[echo]
[echo] --------------------------------------------------------------
[echo] | Deploying workflow form for HumanWorkflow2 on q12163, port 8888
[echo] --------------------------------------------------------------
[echo]
BUILD FAILED
C:\Oracle\JDev\jdev\mywork\Examples\HumanWorkflow2\build.xml:98: Error while deploying the form on server "q12163" Error message :
java.lang.NoClassDefFoundError: oracle/oc4j/admin/deploy/cmdline/Oc4jAdminCmdline
at com.collaxa.cube.ant.taskdefs.DeployForm.deployIAS(DeployForm.java:750)
at com.collaxa.cube.ant.taskdefs.DeployForm.deployForm(DeployForm.java:548)
at com.collaxa.cube.ant.taskdefs.DeployForm.deployForms(DeployForm.java:814)
at com.collaxa.cube.ant.taskdefs.DeployForm.execute(DeployForm.java:840)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
at org.apache.tools.ant.Main.runBuild(Main.java:673)
at org.apache.tools.ant.Main.startAnt(Main.java:188)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:196)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:55)
There is no problem to deploy the process from JDeveloper using the same build.xml. Can anyone figure out what I'm missing?
Thanks!
Kerstin 
Usually this is an issue with the RMI port, for some reason the human task requires it. It is also a pain because it is always different.
cheers
James 
The ant script uses the build.xml which uses build.properties. Make sure your build.properties values are all correct.
Heidi. 
Check if you see any other errors in opmn.log file
Every Little Helps
Kalidass Mookkaiah
http://oraclebpelindepth.blogspot.com/

NullPointerException When Running "wsdlc" Task

I am receiving the following exception when running the wsdlc task from an Ant build script for a WebLogic Server 9.2 web service:
java.lang.NullPointerException
     at weblogic.wsee.tools.source.EndpointBuilder.buildEndpoint(EndpointBuilder.java:468)
     at weblogic.wsee.tools.source.EndpointBuilder.build(EndpointBuilder.java:181)
     at weblogic.wsee.tools.wsdlc.Wsdl2JwsBuilder.buildJsClass(Wsdl2JwsBuilder.java:346)
     at weblogic.wsee.tools.wsdlc.Wsdl2JwsBuilder.buildJwsGenInfo(Wsdl2JwsBuilder.java:393)
     at weblogic.wsee.tools.wsdlc.Wsdl2JwsBuilder.generate(Wsdl2JwsBuilder.java:217)
     at weblogic.wsee.tools.anttasks.WsdlcTask.generateJws(WsdlcTask.java:240)
     at weblogic.wsee.tools.anttasks.WsdlcTask.execute(WsdlcTask.java:193)
     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
     at org.apache.tools.ant.Task.perform(Task.java:364)
     at org.apache.tools.ant.Target.execute(Target.java:341)
     at org.apache.tools.ant.Target.performTasks(Target.java:369)
     at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
     at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
     at org.apache.tools.ant.Main.runBuild(Main.java:673)
     at org.apache.tools.ant.Main.startAnt(Main.java:188)
     at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
     at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
I have verified that my WSDL, which contains a single service/port/operation combination, is well-formed and valid using XMLSpy. The "wsdlc" task is generating the WSDL type classes from the WSDL file correctly, but seems to have a problem when attempting to generate the JWS file.
The Ant build script I'm using has been run successfully within the same environment (same JDK / WebLogic / Ant versions) on another service, so I'm almost certain the problem is somewhere in the WSDL. The service is a document literal service, which is different from the JAX-RPC style of the other service I successfully generated. Unfortunately, I'm unable to post the WSDL to the forum. Not much help, I understand, but any thoughts or feedback from someone whose encountered this error previously would be appreciated.
Thanks, Mark 
When I ran into this problem the thing that finally fixed it was adding a <soapbind:operation/> tag inside the <operation/> tag under the <binding/> element.
e.g.:
<soapbind:operation soapAction="http://foo.com/foo/service/action" style="document"/>
I hope this helps!
Donley

how can i deploy my .war portlet application

Hi Gurrus!
I want to deploy programatically (manuall way can also helps me to program the manual logic) my .war portlet application comprise of
content:
1) 1 java file(portlet one)
2) 1 jsp file
3) web.xml
4) portlet.xml
questions:
1) how can i do the above task
2) in 8.1sp 3 is there a way that i deploy my .war as an application than using admin/workshop console link them in a portal page?, if yes than please guide me in this regard.
THANKS IN ADVANCE
-Kashif 
Hi Kashif,
Here is one option:
http://dev2dev.bea.com/products/wlportal81/articles/deployJava81sp3.jsp
Best Regards,
--alex                                                                                                                                                                                                                                                                
look at :
http://dev2dev.bea.com/products/wlportal81/articles/deployJava81sp3.jsp
Hi Gurrus!
I want to deploy programatically (manuall way can also helps me to program the manual logic) my .war portlet application comprise of
content:
1) 1 java file(portlet one)
2) 1 jsp file
3) web.xml
4) portlet.xml
questions:
1) how can i do the above task
2) in 8.1sp 3 is there a way that i deploy my .war as an application than using admin/workshop console link them in a portal page?, if yes than please guide me in this regard.
THANKS IN ADVANCE
-Kashif
Hello Gurus,
Is there an update version of portletpreparer for weblogic portal 9.2?
I tried the instruction on the link and got java exception during running the ant command.
Has anyone had luck to use this utility?
Thanks,
-Nick
PS. Exception
C:\work\portletpreparer\portletpreparer\build.xml:12: java.lang.NullPointerException
at org.apache.tools.ant.Task.perform(Task.java:373)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
Caused by: java.lang.NullPointerException
at com.bea.task.PreparePortlets.execute(PreparePortlets.java:81)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
... 10 more
--- Nested Exception ---
java.lang.NullPointerException
at com.bea.task.PreparePortlets.execute(PreparePortlets.java:81)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
Total time: 1 second

Categories

Resources