Working ANT deploy/redeploy example for weblogic 7

Could someone please post a working example of an ANT-task which
deploys/redeploys an ear in a running wl 7.x instance ? I've been trying to
get this to work / find an example of a working task but haven't succeeded
yet.
//Linus Nikander - [email protected]

The current WL7 docs at http://e-docs.bea.com/wls/docs70/programming/deploying.html#1130056
show a pre-configured ant task shipping with WL7
I cannot find any instance of the referenced WLDeploy class in any jar file in my WL7 installation [WLS 7 SP4]
Is a standard distribution [ant deploy, configure tasks and classes] available for use with WLS7 ?
Hey Linus.[snippage /]
For WLS 7.0, you could use <java> to call
weblogic.Deployer passing in the
appropriate parameters on the arg line. Or, you can
mimic what we did in
8.1 by creating customer Ant tasks calling
weblogic.Deployer for your
specific use.
-Chris
"Linus Nikander" <[email protected]> wrote in
message
news:[email protected]..
Could someone please post a working example of anANT-task which
deploys/redeploys an ear in a running wl 7.xinstance ? I've been trying
to
get this to work / find an example of a workingtask but haven't succeeded
yet.
//Linus Nikander - [email protected]

Similar Messages

Error from building medrec example for weblogic 10

Hi,
I tried to re-build medrec example for weblogic 10 and got error below. What was wrong?
Any information would be appreciated. Thanks in advance.
D:\bea\wlserver_10.0\samples\server\medrec\src>ant
Buildfile: build.xml
init:
[echo] #### S T A R T M E D R E C ####
[echo] Started on December 10 2007 at 0856
build:
banner:
[echo] --------------------------------------------
[echo] + Building StartBrowser Ear +
[echo] --------------------------------------------
build:
BUILD FAILED
D:\bea\wlserver_10.0\samples\server\medrec\src\build.xml:26: The following error occurred while exec
uting this line:
D:\bea\wlserver_10.0\samples\server\medrec\src\startBrowserEar\build.xml:50: Problem: failed to crea
te task or type wlcompile
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.

open a new command window , run setDomainEnv.cmd and in the same window run ant task.

Page naviagation doesn't work after deploy ADF application to Weblogic

After deploy my ADF application (ear) to Weblogic Server, the page navigation doesn't work. When running the ear on weblogic, I got following warnings:
<2010-11-5 下午05时06分01秒 CST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application HwtOrder is not versioned.>
<2010-11-5 下午05时06分38秒 CST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=AppApplicationOverviewPage&AppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3DHwtOrder%2CType%3DAppDeployment%22%29.>
<2010-11-5 下午05时07分33秒 CST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=DiagnosticsViewDomainLogTablePage&DiagnosticsViewDomainLogTablePortlethandle=com.bea.console.handles.LogDispatchHandle%28%22DefaultServer%3BDomainLog%22%29.>
I can run the application correctly in jdeveloper 11g environment. I think there is something wrong with deployment. Can anyone help me?

When you target url with .jspx, you are running the page itself, not in the task flow context, so navigation doesn't work.
In the task flow, your page has 'Activity ID' (which is, for example, 'mainPage' for mainPage.jspx) and the navigation is defined for activity IDs, not pages.
Pedja

Deployment plan fails for weblogic-ejb-jar.xml

FILE FOR PLAN TO ACT ON:
application.ear\ReferenceTableSession.jar\META-INF\weblogic-ejb-jar.xml
<?xml version="1.0" encoding="utf-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>referencetablesession</ejb-name>
<stateless-session-descriptor>
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>150</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>XYZ_ejb/ProviderMaintSvc/referencetablesession</jndi-name>
</weblogic-enterprise-bean>
<transaction-isolation>
<isolation-level>TransactionReadCommitted</isolation-level>
<method>
<ejb-name>referencetablesession</ejb-name>
<method-name>*</method-name>
</method>
</transaction-isolation>
</weblogic-ejb-jar>
DEPLOYMENT PLAN:
<?xml version='1.0' encoding='utf-8'?>
<deployment-plan xmlns="http://www.bea.com/ns/weblogic/deployment-plan"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/deployment-plan http://www.bea.com/ns/weblogic/deployment-plan/1.0/deployment-plan.xsd">
<application-name>application.ear</application-name>
<variable-definition>
<variable>
<name>VAR_referencetablesession</name>
<value>ejb/ProviderClaimOnlineSvc/referencetablesession</value>
</variable>
</variable-definition>
<module-override>
<module-name>ReferenceTableSession.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="false">
<root-element>weblogic-ejb-jar</root-element>
<uri>META-INF/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>VAR_referencetablesession</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="referencetablesession"\]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
<config-root>servers/AdminServer/upload</config-root>
</deployment-plan>
ERROR FROM CONSOLE:
Message icon - Error An error occurred during activation of changes, please see the log for details.
Message icon - Error Exception preparing module: EJBModule(ReferenceTableSession.jar) [EJB:011023]An error occurred while reading the deployment descriptor. The error was: Unmarshaller failed.
Message icon - Error Bean already exists: "[email protected]f2(/WeblogicEnterpriseBeans[referencetablesession])"
ERROR FROM LOG:
<Oct 2, 2009 1:08:25 PM CDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor servers/ms34/tmp/_WL_user/ProviderClaimOnlineSvc/y1anoa/ReferenceTableSession.jar/META-INF/weblogic-ejb-jar.xml of module ReferenceTableSession.jar. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.mergeDescriptorBeanWithPlan(AbstractDescriptorLoader2.java:703)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:776)
at weblogic.ejb.spi.EjbJarDescriptor.parseWeblogicEjbJarBean(EjbJarDescriptor.java:160)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWLEjbJarXMLWithSchema(EjbDescriptorReaderImpl.java:719)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.parseWLDD(EjbDescriptorReaderImpl.java:541)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWeblogicEjbJarXML(EjbDescriptorReaderImpl.java:380)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:191)
at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1198)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.createAndPrepareContainer(RedeployOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:122)
Thanks,
Rob
Edited by: user11337024 on Oct 5, 2009 2:31 PM

FILE FOR PLAN TO ACT ON:
application.ear\ReferenceTableSession.jar\META-INF\weblogic-ejb-jar.xml
<?xml version="1.0" encoding="utf-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>referencetablesession</ejb-name>
<stateless-session-descriptor>
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
<initial-beans-in-free-pool>0</initial-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>150</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>XYZ_ejb/ProviderMaintSvc/referencetablesession</jndi-name>
</weblogic-enterprise-bean>
<transaction-isolation>
<isolation-level>TransactionReadCommitted</isolation-level>
<method>
<ejb-name>referencetablesession</ejb-name>
<method-name>*</method-name>
</method>
</transaction-isolation>
</weblogic-ejb-jar>
DEPLOYMENT PLAN:
<?xml version='1.0' encoding='utf-8'?>
<deployment-plan xmlns="http://www.bea.com/ns/weblogic/deployment-plan"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/deployment-plan http://www.bea.com/ns/weblogic/deployment-plan/1.0/deployment-plan.xsd">
<application-name>application.ear</application-name>
<variable-definition>
<variable>
<name>VAR_referencetablesession</name>
<value>ejb/ProviderClaimOnlineSvc/referencetablesession</value>
</variable>
</variable-definition>
<module-override>
<module-name>ReferenceTableSession.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="false">
<root-element>weblogic-ejb-jar</root-element>
<uri>META-INF/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>VAR_referencetablesession</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="referencetablesession"\]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
<config-root>servers/AdminServer/upload</config-root>
</deployment-plan>
ERROR FROM CONSOLE:
Message icon - Error An error occurred during activation of changes, please see the log for details.
Message icon - Error Exception preparing module: EJBModule(ReferenceTableSession.jar) [EJB:011023]An error occurred while reading the deployment descriptor. The error was: Unmarshaller failed.
Message icon - Error Bean already exists: "[email protected]f2(/WeblogicEnterpriseBeans[referencetablesession])"
ERROR FROM LOG:
<Oct 2, 2009 1:08:25 PM CDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor servers/ms34/tmp/_WL_user/ProviderClaimOnlineSvc/y1anoa/ReferenceTableSession.jar/META-INF/weblogic-ejb-jar.xml of module ReferenceTableSession.jar. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.mergeDescriptorBeanWithPlan(AbstractDescriptorLoader2.java:703)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:776)
at weblogic.ejb.spi.EjbJarDescriptor.parseWeblogicEjbJarBean(EjbJarDescriptor.java:160)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWLEjbJarXMLWithSchema(EjbDescriptorReaderImpl.java:719)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.parseWLDD(EjbDescriptorReaderImpl.java:541)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWeblogicEjbJarXML(EjbDescriptorReaderImpl.java:380)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:191)
at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1198)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.createAndPrepareContainer(RedeployOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:122)
Thanks,
Rob
Edited by: user11337024 on Oct 5, 2009 2:31 PM

How to create and deploy portal applications for WebLogic TP10

Hi Friends:-) Thej here,
I want to know, how to create weblogic portal applications for tech preview version 10.
Thanks

The Tech Preview of 10.0 contains only WebLogic Server. WebLogic Portal 10.0 functionality is not contained in this preview. Therefore, you cannot create portal applications in this Tech Preview.
Thank you.

Please help me about jdeveloper application deployment for weblogic

At the beginning I just thought after developing an adf application then just deploy it as a .ear file and deploy it in the weblogic console and everything will be ok.But in fact I got a lot of problems. Then I got a tutorial for that and I do what it said step by step but some new problems occured. This is the tutorial I mentioned: [How-To: ADF Deployment Guide|http://www.oracle.com/webfolder/technetwork/jdeveloper/howto/11114/managedserver/wlsadfms.htm]
Now could somebody tell how did you deploy your adf application?
Here is the errors I got.
This is the install packege and the OS I use:
1. CentOS 6.3_x64 + jdeveloper11123.jar(include wls10.3.5) + adr(package name is ofm_appdev_generic_11.1.1.6.0_disk1_1of1.zip)[and just now I used a solaris11 vm from oracle and install jdeveloper11.1.2.3, the same probem occured as in CentOS.]
2. Win7_x64 + jdeveoper11123.exe(include wls10.3.5) + adr mentioned above
Here is the problems I get:
in the case 1,after I install the jdeveloper(using sun jdk 1.7), the weblogic seems to be well though I didn't configure a domain.But after I open an
application(which I get from the oracle jdeveloper tutorial demo,which works well in my Win7 env) and I run it, the integrated weblogic can't get
started. Firstly in the console it said the -jrocket identifier is not recognized, then I modify the setDomainEnv.sh and the startWebLogic.sh file in the
integrated wls domain (the one in the .jdeveloper directer) to set the JAVA_VM variable to -server.After that another problem came out: when the
wls goes to status "starting",it is blocked and I turn to the system monitor it shows that a java thread using more than 1GB of memory of my system
and occupy 150% of my cpu(it's a double-core computer). I wait for about 5 minutes when a error came said "PermSize is too small".then I modify the
setDomainEnv.sh file again to set the PermSize to be 1024m and MaxPermSize to be 2048.(the variable name is something like that, maybe not the
exactly right. I think you can understand which one it is.) But the problem is still there.
then in the case 2.Firstly the jdev and the integrated wls works well, but when i deploy an application which works well to a ear file and deploy it to a
standalone wls(10.3.5) it never works.the error is something referrence/dependences libraries is not found.Then I tried to new a server connection to
the standalone wls and I got the tutorial [how_to_deploy_adf|http://www.oracle.com/webfolder/technetwork/jdeveloper/howto/11114/managedserver/wlsadfms.html] , as the tutorial said I patch my standalone
wls with the adr and everything goes ok, no error reported.Then I tried the new server in the new machine under the manage of the adminserver and apply the
adf template in the localhost:port/em console. But after I restart the new server(by the console and then by the stop+startweblogic.bat file) the server is running
while the application in the new server is just "Unavailable". I tried this for three times in three computer, two of them are running win7,the other one is running winxp.
I don't know what is wrong and I am totally a newbie about this. Somebody please help me.Thanks a lot!
regard,Neo.

Neo,
there are a couple of problems. First of all, jdev comes with it'S own jdk bundled in the product (jdk 1.6_x). Next thing is if you use JDev 11.1.2.3.0 to build an application you must use a wls 10.3.5 or 10.3.6 where you need to install the correct runtime onto. In your case you first install adf runtime 11.1.1.6.0 and then you need to install two patches which update the adf runtime to 11.1.2.3.0. These spathes are only available via support.oracle.com, meaning you need asupport contract to get them.
More information you can find in my blog http://tompeez.wordpress.com/2011/09/14/jdeveloper-versions-vs-weblogic-server-versions/
The rest of your problems go away once you have installed the right adf runtime on your server.
Timo

EJB deployment error for Weblogic server 9.2 mp4

Hi,
While trying to deploy a small EJB jar file which uses EJB 2.1 CMP beans with relationships, getting the following error from Weblogic server 9.2 MP4:
=================================================================================================
<Error> <EJB> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988333> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
>
####<Nov 1, 2011 4:09:48 PM IST> <Error> <Deployer> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988380> <BEA-149265> <Failure occured in the execution of deployment request with ID '1320143984947' for task '1'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:382)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
=================================================================================================
While I'm able to deploy without the CMP 1-1 relationship, the moment I introduce the 1-1 relationship, I get this error. Database used is Oracle 10g XE.
I have been battling this error for more than a day now. Kindly help me fix this.
Thanks in advance!
Regards,
Vinod

Hi,
I was able to figure out the root cause. I was using the primitive data type "int" for primary key and foreign key for one of the beans in the relationship. After I changed it to "Integer" wrapper type, the issue got resolved.
-Vinod

Examples.cluster.rmi for WebLogic Server 11g

How can I get package examples.cluster.rmi for WebLogic Server 11g?
I would like to perform a similiar test like the following:
https://freepaper.taichung.gov.tw/examplesWebApp/examples/src/examples/cluster/rmi/package-summary.html
Thanks a lot

Hi,
I have just now installed WLS via the net installer, and the default examples server password of welcome1 does indeed work for me.
However, I note from your post that you are using port 7101, not 7001. Could that be the issue?
http://localhost:7101/console/login/LoginForm.jspKevin

Workshop for weblogic and spring 2.0.6 not working on weblogic 92

Hi,
I try to use workshop for weblogic 10.1 to create a web project using spring mvc framework and deploy it to a weblogic 9.2 server, and it gives me the error.
Here's what I have done:
Create a 9.2 server.
Create a web project with spring facet, I downloaded spring 2.0.6.
I created a test jsp page along with applicationContext.xml and springServlet.xml spring support.
When I start the server and publish the ear to the server,
I got the following error:
Aug 28, 2007 9:18:03 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Aug 28, 2007 9:18:27 AM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "SpringContextServlet" failed to preload on startup in Web application: "springmvcWar".
java.lang.NoClassDefFoundError: weblogic/i18n/logging/MessageLoggerRegistryListener
     at java.lang.ClassLoader.defineClass1(Native Method)
     at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
     at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:338)
     at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:291)
     Truncated. see log file for complete stacktrace
I couldn't find the class weblogic/i18n/logging/MessageLoggerRegistryListener anywhere.
Does anybody have seen this error before.
Thanks
maildt

Hi,
I tried the scenario against 9.2mp1 server and 9.2mp2 server and the publish worked fine.
The only difference is the jsp file you created
Can you remove your jsp file and see if the publish still fails?
Which version of 9.2 server are you using? Also, what all facets are you using other than spring?
Can you also try something and see if it helps?
1. Open a new workspace
2. In Window -> Preferences -> WebLogic -> J2EE Libraries, removed the logging bridge libraries (the 10.0 version) and re-added these libraries from a 9.2 installation.
Basically they are
wls-commonslogging-bridge 1.0/1.0
wls-commonslogging-bridge-war 1.0/1.0
wls-commonslogging-bridge 1.0/1.1
wls-commonslogging-bridge-war 1.0/1.1
and add 2 jars from 9.2_BEA_HOME/weblogic92\common\deployable-libraries
3. Create web project and follow the other steps
Thanks
Vimala

Cannot deploy the Bookstore Example for Java EE tutorials

I also have the same issue as another user on a different thread, and I did check my build.properties and it appears accurate. However I am still getting the exception when I try to run the 'ant create-tables' or 'ant deploy' :
Buildfile: build.xml
-pre-init:
init:
check:
tools:
start-db:
[exec] Database already started on host localhost, port 1527.
[exec] Command start-database executed successfully.
delete-tables:
[sql] Executing file: C:\tutorial\javaeetutorial\examples\web\bookstore1\${db.delete.src}
BUILD FAILED
C:\tutorial\javaeetutorial5\examples\bp-project\database-ant.xml:48:java.io.FileNotFoundException: C:\tutorial\javaeetutorial\examples\web\bookstore1\${db.delete.src} (The system cannot find the file specified)
Total time: 7 seconds
The Build.Properties file in my [install]/examples/bp-projects/ directory is a follows
javaee.home=C:/Sun/AppServer
javaee.tutorial.home = c:/tutorial/javaeetutorial5
javaee.server.name=localhost
javaee.server.port=10000
javaee.adminserver.port=4848
javaee.server.username=admin
javaee.server.passwordfile=c:/tutorial/javaeetutorial5/password.txt
appserver.instance=server
I was able to compile the first Hello tutorial with Ant, so I am assuming that means the above build.properties file should be correct (or else that deployment would have failed too, right?). I also created the JDBC connection in the System Admin Console before trying this, as per the tutorial text.
Since I'm new to the environment, I'm not sure where else to look for the problem.

Ok, I did an 'ant deploy' at the books directory. It seems to be going well and then just hung for minutes at the following line...
check:
tools:
-pre-deploy:
-pre-init:
init:
check:
tools:
start-db:
[exec] Database started in Network Server mode on host localhost and port 1
527.
[exec] --------- Derby Network Server Information --------
[exec] Version: CSS10011/10.1.1.0 Build: 208786 DRDA Product Id: CSS10011
[exec] -- listing properties --
[exec] derby.drda.maxThreads=0
[exec] derby.drda.keepAlive=true
[exec] derby.drda.minThreads=0
[exec] derby.drda.portNumber=1527
[exec] derby.drda.logConnections=false
[exec] derby.drda.timeSlice=0
[exec] derby.drda.startNetworkServer=false
[exec] derby.drda.host=localhost
[exec] derby.drda.traceAll=false
[exec] ------------------ Java Information ------------------
[exec] Java Version: 1.5.0_06
[exec] Java Vendor: Sun Microsystems Inc.
[exec] Java home: C:\Sun\AppServer\jdk\jre
[exec] Java classpath: C:\Sun\AppServer\lib\appserv-rt.jar;C:\Sun\AppServe
r\lib\admin-cli.jar;C:\Sun\AppServer\javadb\lib\derby.jar;C:\Sun\AppServer\javad
b\lib\derbytools.jar;C:\Sun\AppServer\javadb\lib\derbynet.jar;C:\Sun\AppServer\j
avadb\lib\derbyclient.jar
[exec] OS name: Windows XP
[exec] OS architecture: x86
[exec] OS version: 5.1
[exec] Java user name: Russell Longo
[exec] Java user home: C:\Documents and Settings\Russell Longo
[exec] Java user dir: C:\Sun\AppServer
[exec] java.specification.name: Java Platform API Specification
[exec] java.specification.version: 1.5
[exec] --------- Derby Information --------
[exec] JRE - JDBC: J2SE 5.0 - JDBC 3.0
[exec] [C:\Sun\AppServer\javadb\lib\derby.jar] 10.1.1.0 - (208786)
[exec] [C:\Sun\AppServer\javadb\lib\derbytools.jar] 10.1.1.0 - (208786)
[exec] [C:\Sun\AppServer\javadb\lib\derbynet.jar] 10.1.1.0 - (208786)
[exec] [C:\Sun\AppServer\javadb\lib\derbyclient.jar] 10.1.1.0 - (208786)
[exec] ------------------------------------------------------
[exec] ----------------- Locale Information -----------------
[exec] ------------------------------------------------------
[exec] Starting database in the background. Log redirected to C:/Sun/AppSe
rver/javadb\derby.log.
[exec] Command start-database executed successfully.
I hit a Ctrl-C and it asked if I wanted to end the batch. I replied 'n' but it dropped out to the command line.
So I tried the ant deploy again and got the following...
check:
tools:
-pre-deploy:
-pre-init:
init:
check:
tools:
start-db:
[exec] Database already started on host localhost, port 1527.
[exec] Command start-database executed successfully.
delete-tables:
[sql] Executing file: C:\tutorial\javaeetutorial5\examples\web\books\${db.
delete.src}
BUILD FAILED
C:\tutorial\javaeetutorial5\examples\web\books\build.xml:51: The following error
occurred while executing this line:
C:\tutorial\javaeetutorial5\examples\bp-project\database-ant.xml:48: java.io.Fil
eNotFoundException: C:\tutorial\javaeetutorial5\examples\web\books\${db.delete.s
rc} (The system cannot find the file specified)
I finally went to the bookstore directory to see if I could deploy that application. Ant deploy gave the following:
check:
tools:
-pre-deploy:
-pre-init:
init:
check:
tools:
start-db:
[exec] Database already started on host localhost, port 1527.
[exec] Command start-database executed successfully.
delete-tables:
[sql] Executing file: C:\tutorial\javaeetutorial5\examples\web\books\${db.
delete.src}
BUILD FAILED
C:\tutorial\javaeetutorial5\examples\web\books\build.xml:51: The following error
occurred while executing this line:
C:\tutorial\javaeetutorial5\examples\bp-project\database-ant.xml:48: java.io.Fil
eNotFoundException: C:\tutorial\javaeetutorial5\examples\web\books\${db.delete.s
rc} (The system cannot find the file specified)
Last, I went to bookstore1 just to try the ant deploy again, see if things were cleared up, and maybe the errors above wouldn't affect it. When I tried deploying I got the following...
check:
tools:
-pre-deploy:
-pre-init:
init:
check:
tools:
start-db:
[exec] Database already started on host localhost, port 1527.
[exec] Command start-database executed successfully.
delete-tables:
[sql] Executing file: C:\tutorial\javaeetutorial5\examples\web\books\${db.
delete.src}
BUILD FAILED
C:\tutorial\javaeetutorial5\examples\web\books\build.xml:51: The following error
occurred while executing this line:
C:\tutorial\javaeetutorial5\examples\bp-project\database-ant.xml:48: java.io.Fil
eNotFoundException: C:\tutorial\javaeetutorial5\examples\web\books\${db.delete.s
rc} (The system cannot find the file specified)
I'm clearly not 'getting' a handle on this environment.

Error deploying jpa from oepe tutorial example on Weblogic 12c server

I am having the next error trying to deploy jpa in to Weblogic 12c server from the oepe tutorial example at http://www.oracle.com/webfolder/technetwork/tutorials/obe/jdev/obe11jdev/11/eclipse_intro/eclipse_intro.html. The "I---------I" markups are below, "bean.Hello", "hello" and "response.jsp". I've tried to find a solution on the web but nothing. I'll apreciate any help. thanks.
greeting.jsp:1:1: Needed class "bean.Hello" is not found.
^
greeting.jsp:5:44: The bean type "bean.Hello" was not found.
<jsp:useBean id="hello" scope="page" class="bean.Hello"></jsp:useBean>
I----------I
greeting.jsp:6:23: This bean name does not exist.
<jsp:setProperty name="hello" property="*" />
I-----I
greeting.jsp:34:18: Error in "C:\Users\Andres Tobar\workspace\DemoEARWeb\WebContent\pages\response.jsp" at line 13: This bean does not exist.
<%@ include file="response.jsp" %>
I------------I

I have started again all the tutorial from the begining, trying to not miss any configuration setting even the ones displayed on pictures, finding that the tutorial example now works. I think the first time i have tryed it i missed to activate the anotations facet in project properties because this configuration step is not explained in the tutorial unless you take a close look into the tutorial images. Probably that was the cause of the mentioned error, not so sure, but the tutorial example really works.

Ant deploy from Jdev works fine - same ant deploy from command line fails

Hi
I'm using Jdev 10.1.3 and OAS 10.1.3 and created some web services. I can deploy using the Wizard in JDev - works fine, created a build.xml file using the <oracle:deploy> ant task. Also work fine from JDeveloper.
But when running from command line (windows) I get the following:
d:\>ant deploy
Buildfile: build.xml
init:
compile:
copy:
ear:
[war] Building war: D:\invision\source\INVisionWebService1013\INVisionWebService.war
[war] Warning: selected war files include a WEB-INF/web.xml which will be ignored (please use webxml attribute to war task)
[ear] Building ear: D:\invision\source\INVisionWebService1013\deploy\INVisionWebService.ear
[delete] Deleting: D:\invision\source\INVisionWebService1013\INVisionWebService.war
deploy:
BUILD FAILED
D:\invision\source\INVisionWebService1013\build.xml:282: The following error occurred while executing this line:
jar:file:/D:/apache/apache-ant-1.6.5/lib/ant-oracle-classes.jar!/oracle/antlib.xml:27: taskdef class oracle.j2ee.ws.tools.wsa.cli.ant.GenProxy cannot be found
I have studied the web for suggestion also http://download-east.oracle.com/docs/cd/B25221_04/web.1013/b14431/anttasks.htm#sthref164 but nothing seems to work. Tried copying oracle jars to my ant directory (ant version 1.6.5) but still no success (above error message disappered but other came instead).
Why must this process be so complex. Can anyone help?

Hi,
You need to have the following jars in your classpath before firing the ant deploy task.
${Oracle_Home}\j2ee\utilities\ant-oracle-classes.jar;
${Oracle_Home}\j2ee\home\lib\adminclient.jar;
${Oracle_Home}\2ee\home\lib\oc4j-internal.jar;
${Oracle_Home}\j2ee\home\lib\javax77.jar;
${Oracle_Home}\j2ee\home\lib\javax88.jar;
${Oracle_Home}\j2ee\home\lib\jmxri.jar;
${Oracle_Home}\OracleAS_1\webservices\lib\wsa.jar;
Please check your classpath and add the above jars, if not present and try ant deploy task now.
I suppose it should work fine.
Hope its helpful.
Rgds,
Prashanth Babu.

Ant scripts for weblogic 10.3

can any one send me antscripts for weblogic 10.3 for creating,configuring the domains
and deploying applications(stage,nostage and external_stage)
thanks & regards
abhi
Edited by: user10759597 on Jan 6, 2009 3:23 AM

hi john,
firstly thanks for ur reply...
i tried ant scripts to deploy the applications but when i deploy the in any modes (stage,nosatge and external_stage) i'm getting errors...
kindly pls send me some ant scripts for deployments in all modes
or
send the syntax to deploy the application in stage, no stage and external_stage modes
i think u got my request right?
thanks in advance
abhi

WSUS 3.2 work on Win2008 R2, how to use it deploy MS patch for Win 2012 ?

WSUS 3.2 work on Win2008 R2, how to use it deploy MS patch for Win 2012 ?
I have installed KB2734608, but when I search MS13-101 , no patch for Win 2012.
Can you help me resolve this problem ?
Thanks

On Thu, 10 Apr 2014 06:01:48 +0000, fujitsu08 wrote:
WSUS 3.2 work on Win2008 R2, how to use it deploy MS patch for Win 2012 ?
WSUS has its own, dedicated forum where the WSUS experts answer questions.
You should repost your question here:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverwsus
Paul Adare - FIM CM MVP
Aibohphobia: n. Fear of Palindromes

Is there service pack available for weblogic 5.1 to work with JDK 1.4 for NT Environment

Is there service pack available for weblogic 5.1 to work with JDK 1.4 for NT Environment

Hi.
This is definitely not supported, and I don't know that any work is scheduled in the future
to support this JDK on WLS 5.1.
Having said that, I was able to start WLS 5.1sp12 with JDK 1.4 with no errors. I didn't
exercise any features, however.
Regards,
Michael
Rakesh Gupta wrote:
Is there service pack available for weblogic 5.1 to work with JDK 1.4 for NT Environment--
Michael Young
Developer Relations Engineer
BEA Support

Working ANT deploy/redeploy example for weblogic 7

Similar Messages

Maybe you are looking for