# Deploy web application in jbuilder 9 with weblogic 7 problem

when i create a web application and a servlet, and deploy it in jbuilder 9 with weblogic 7.0 ,jbuilder 9 showed me the error,please tell me why, when i choose "redeploy" ,it can be normally work..
E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
WebLogic Application Deployment Utility
Usage: java weblogic.Deployer [options] [-activate|-deactivate|-remove|-unprepare|-cancel|-list] [files]
where options include:
-help Print this help message.
-version Print version information.
http://localhost:7001
-user <user> A user other than the default of
If this option is absent the user is
prompted.
-verbose Displays additional status during the
when the application is prepared and
activated on each target.
-debug Displays debug level messages to the standard
output.
-examples Display example usage of this tool.
-upload Causes the specified source file(s) to be
transferred to the adminstration server. This
is used when the Deployer tools is not being
used on the same machine as the adminstration
server and the user does not otherwise have
-delete_files Causes the server to remove the files that
are specified in the file list and leave the
application activated. This option is valid
only for unarchived web applications.
-remote Signals that the tools is not runnning on the
same machine as the adminstration server and
that the source path should be made passed
through unchanged as it represents the path
on the remote server.
-nostage Sets the stagingMethod attribute on the
application mbean when it is created so that
the application will not be staged and the
original source is be used.
-external_stage Sets the stagingMethod attribute on the
application mbean when it is created so that
the application will not be staged but the
value of the staging path will be used when
preparing the application.
-stage Sets the stagingMethod staging attribute on
the application when it is created so that
the application will always be staged. This
value will override the stagingMethod
attribute on any targeted servers.
-nowait Once the action is initiated the tool will
print the task id and exit. This is used to
initiate multiple tasks and then monitor them
later using the -list action.
-timeout <seconds> The maximum time in seconds to wait for the
completion of the deployment task. When the
time expires the current status is printed
and the program exits.
-source <archive file or directory> Location of the file or directory that
represents the enterprise component or
application tha is being (re)activated. If
the source file is relative it is relative to
the current directory, unless the -remote
option is used. To specify individual files
within an application for reployment or
addition list them at the end of the command
line.
-name <application name> The name of the application being deployed.
-targets <<server 1>,...<component>@<server N>> A comma separated list of the server and/or
cluster names. Each target may be qualified
with a J2EE component name. This enables
different components of the archive to
deployed on different servers.
-id <task identifier> Optional client supplied unique identifier
for the deployment task. The id is first
specified to -activate, -deactivate,
-unprepare or -remove. It is then used later
as an argument to -cancel or -list.
-activate (Re)activates the <source> application on the
<targets> with the <name>.
-deactivate Deactivates the application <name> on the
<targets> leaving an staged application files
in a state where the may be quickly
reactivated.
-unprepare Deactivates and unloads classes for the
application <name> on the <targets> leaving
an staged application files in a state where
-remove Deactivates the application <name> on the
<target> and removes any files that were
staged for this application. If there are no
longer any targets for the application, the
associated configuration is completely
removed.
-cancel Atempts to cancel the task <id> if it is has
not yet completed.
-list Lists the target status of each task <id>
-deploy a convenient alias for activate.
-undeploy a convenient alias for unprepare.
Optionally a list of the specific files in the archive that are to be
redeployed may be specified. If a directory is specified the entire subtree is
redeployed.
Full documentation on this tool is available at:
No actions was specified. Please specify one and only one of:
-activate, -deactivate, -cancel, -remove, -unprepare, or -list.
Type java weblogic.Deployer -examples for example usage.

you use "deploy" under DOS-Mode to deploy your web application?
i found some differences between "deploy" and "redeploy" function in jbuilder 9.
when i choose "deploy" ,jbuilder shows me the commond below:
E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
WebLogic Application Deployment Utility
when i choose redeploy,it shows me: (the -deploy parameter has changed to -activate) ,maybe it's a bug.
E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -activate -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
WebLogic Application Deployment Utility

### Similar Messages

• Failed in deploying Web Application (.ear file)

I am trying to deploy a web application (file1.ear) but I got FileNotFoundException
in webnohup.out.
I did include this application in config.xml, as follows:
<Application Deployed="true" Name="file1" Path="opt/weblogic6/config/ejbjars/file1.ear">
<EJBComponent Name="EJB1" Targets="mysrv" URI="EJB1.jar"/>
<WebAppComponent Name="App1" Targets="mysrv" URI="App1.war"/>
<EJBComponent Name="EJB2" Targets="mysrv" URI="EJB2.jar"/>
</Application>
In webnohup.out file, the following exception is thrown:
<Mar 20, 2002 4:52:39 PM EST> <Error> <Management> <Application care:Name=file1,Type=Application
<Mar 20, 2002 4:52:39 PM EST> <Error> <Management> <IOException opening application
java.io.FileNotFoundException: file does not exist: ./opt/weblogic6/config/ejbjars/file1.ear
ava:431)
87)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
If you looked at the exception, it looks like that we can not put ABSOLUTE PATH
in Path of config.xml since it will append the Weblogic home to the Path defined
in config.xml.
Is this correct or I missed anything?
How do we use ABSOLUTE PATH in config.xml if you want to deploy Web application?
Environment: SUNOS, Weblogic 6.1.
Thanks

Hi,
specifying a leading slash shoul be enough to let the system know that it is an absolute path.
Regards,
Christian Buchegger
Developer Relations Engineer
BEA Support
TJ schrieb:
I am trying to deploy a web application (file1.ear) but I got FileNotFoundException
in webnohup.out.
I did include this application in config.xml, as follows:
<Application Deployed="true" Name="file1" Path="opt/weblogic6/config/ejbjars/file1.ear">
<EJBComponent Name="EJB1" Targets="mysrv" URI="EJB1.jar"/>
<WebAppComponent Name="App1" Targets="mysrv" URI="App1.war"/>
<EJBComponent Name="EJB2" Targets="mysrv" URI="EJB2.jar"/>
</Application>
In webnohup.out file, the following exception is thrown:
<Mar 20, 2002 4:52:39 PM EST> <Error> <Management> <Application care:Name=file1,Type=Application
<Mar 20, 2002 4:52:39 PM EST> <Error> <Management> <IOException opening application
java.io.FileNotFoundException: file does not exist: ./opt/weblogic6/config/ejbjars/file1.ear
ava:431)
87)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
If you looked at the exception, it looks like that we can not put ABSOLUTE PATH
in Path of config.xml since it will append the Weblogic home to the Path defined
in config.xml.
Is this correct or I missed anything?
How do we use ABSOLUTE PATH in config.xml if you want to deploy Web application?
Environment: SUNOS, Weblogic 6.1.
Thanks

• Failed to deploy web application with same name twice

Hello-
On Oracle 10g Application server I deployed an WAR file called "anbadmin", then undeployed it. The undepoloyment failed from the OEM so I undeployed it manually via removing its entries from server.xml.
When I tried to deploy it again with the same name I got this:
Failed to deploy web application "anbadmin". Failed to deploy web application "anbadmin". . The evaluate phase failed. The Adapter used in the evaluate may have thrown an exception.
Resolution:
Base Exception:
java.lang.NoSuchMethodError
null. java.lang.NoSuchMethodError
Is there a solution for this?
Regards

I think I know the solution. We encountered exactly same message and no further deployment could be made. It appeared message in "dcmctl" utility was much more helpfull than the one in EM (though you still have to use "getError" command...)
If you are using file-based repository, you have to issue command in dcmctl utility "resetFileTransaction". This closes repository and opens it again.
Myrra

• How to deploy web application to Weblogic?

Does anyone know how to deploy web application to Weblogic8.1?

Hello,
I found one error in what I have done. I add the '<context-root>' in '<weblogic-web-app>', which are not required in some other containers, and I can find the application of hello2. However, when I clicked 'submit' I got the following message:
Error 500--Internal Server Error
java.lang.NoClassDefFoundError: java/lang/StringBuilder
at servlets.ResponseServlet.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
I do not want to make changes in 'web.xml' file as it worked in other container. I guess I miss something that is special, probably basic, to WebLogic, but I do not know what it is.
Bye the way, who know how to reward points to other people? I cannot find the 'assign points icon'.
Thanks hoos. Your answer give me confidence that a web application could be deployed by copy war file to some directory (I guess from my experience of other containers).

• WEB Server And Database Space requirements for deploying Web Application

Hi,
We are in requirement of WEB Server  And Database Space requirements for deploying  our Web Application in cloud server. We want to know technical requirements and feasibilities laid by Microsoft team for deploying web
application.......
Regards,
Sreenivasa M S

Hi,
http://blogs.technet.com/b/cbernier/archive/2013/09/24/deploy-your-web-application-to-windows-azure-from-with-visual-studio.aspx
Regards,
Azam Khan

• How to deploy web application .war file into SAP NetWeaver Engine?

Hi All,
I want to deploy web application which is developped using JAVA web technology into SAP netweaver Engine.
I tried to deploy .war file through SDM but it complained the following error
- Hide quoted text -
(server side name is: F:\usr\sap\JR1\JC01\SDM\program\temp\MyProject.war)
com.sap.sdm.util.sduread.IIIFormattedSduFileException: The information about development component found in the manifest is either missing or incomplete!
Manifest attributes are missing or have badly formatted value:
attribute keylocation missing
attribute keyname is missing
attribute keyvendor is missing
attribute keycounter is missing
(F:\usr\sap\JR1\JC01\SDM\program\temp\MyProject.war)"
Can any one please suggest how to deploy external web application into SAP netweaver engine.
Is there any procedure to follow to do this.
your inputs will be highly appreciated...

Hi,
I think first you need to wrap it into an EAR file, then you can deploy it.
As far as I know standalone deployment of WAR is deprecated as of 640.
How to deploy .war on NWDI
Deploying an existing WAR file into the Portal
Hopefully this tutorial also gives some idea:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/70/13353094af154a91cbe982d7dd0118/frameset.htm
Regards,
Ervin

• SP 2013 Upgrade error - web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against a windows classic authentication mode.

Hi there,
I get this error when I perform a DB Attach upgrade from SharePoint 2010 to SharePoint 2013.
"web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against a windows classic authentication mode."
Any help is appreciated. Thanks.

There is other way of fixing this issue apart from what Amit mentioned. Create a classic based web application in SP 2013 using PowerShell.
New-SPWebApplication -Name "TestApplication" -ApplicationPool "TestApplicationAppPool" -AuthenticationMethod "NTLM" -ApplicationPoolAccount (Get-SPManagedAccount "sppoc\spfarm") -Port 100 -URL "http://sp2013demo"
Now mount the content database from SP 2010 on to the web application created above
Mount-SPContentDatabase WSS_Content_100 -DatabaseServer SQL2012Demo -WebApplication http://sp2013demo:100
Once the mount is complete, convert the web application to use claims and migrate the user to use claims identity.
Convert-SPWebApplication -Identity "http://sp2013demo:100" -To Claims –RetainPermissions -Force
$w = Get-SPWebApplication "http://sp2013demo:100"$w.MigrateUsers($True) See my blog post about it: http://www.sharepointnadeem.com/2014/01/upgrade-from-sharepoint-2010-classic.html Please remember to up-vote or mark the reply as answer if you find it helpful. • Serious problems deploying web application with enterprise manager Hi all, First I have to say that this thing that has happened to me today is freaking bizarre... I was trying to make a new deployment of a web application on OAS 10.1.2, using the Enterprise Manager. The application is using Spring and DWR, therefore it has some XML files included. The application worked perfect in JDeveloper 9.0.4, our development tool, and I've previously developed very similar applications in the past, and deployed them on the same server without any problem. Today, when I was trying to deploy my .ear file, I got this error message: The file specified, "FindAnExpert.ear" is not a valid ear file. I tried with the .war file, and this happened: Base Exception: java.util.zip.ZipException invalid END header (bad central directory offset). invalid END header (bad central directory offset) I checked that all the included .jar files were fine, I even replaced them with new ones. I started to remove files from the .war file and discovered that without the XML files I was able to deploy the application. Then I copied over those XML files through FTP and the application is working correctly, but I was not able to use the Enterprise Manager to deploy it!!! The XML files are well formed, on of them contains the details of a data source that I also reviewed to be sure that it was correctly configured... This is nuts... any ideas over there??? Thanks in advance, Luis Luis, If all of the files uploaded piecemeal worked fine, then I believe your problem to be with your deployment descriptor(s). Also, note that the .war file lives in a different directory: C:\oc4j\j2ee\home\applications\Application-Name Perhaps if you have time you could post all of the associated deployment descriptor files. Log files from the C:\oc4j\j2ee\home\log\oc4j directory would also help to troubleshoot your deployment issues. You can turn up the logging level to "FINEST" for maximum output to your log file. -Michael • Problems with deployed web applications Hi, currently we use Weblogic 6.0 and i decided to try Weblogic 6.1 beta. So i deployed our application which was working on Weblogic 6.0 on the newly installed Weblogic 6.1 beta. Now when i try to access my application i recieve the following error page: Compilation of 'D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_servlet\_ngroot\_web\__index.java' failed: D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_servlet\_ngroot\_web\__index.java:165: handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext cannot be applied to (java.lang.Throwable) (No more information available, probably caused by another error) Full compiler error(s): D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_servlet\_ngroot\_web\__index.java:165: handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext cannot be applied to (java.lang.Throwable) pageContext.handlePageException(__ee); ^ 1 error Wed Jun 20 17:27:28 EEST 2001 Does anyone know what could cause the problem ? Any help will be appreciated. Bybye. [att1.html] I have the same problem. My apps work in WebLogic 6.0, but not in 6.1 beta. Is it compatibility issue? Andi "Michael Li" <[email protected]> wrote: >Hi all, > >Anybody resolve this problem yet? We are experiencing the same problem >here. > >Thanks, >Michael > >=== >"Evgenya Borisenko" <[email protected]> wrote in message >news:[email protected] >Sure, >here goes: > >####<10:23:37 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >*.html: init> >####<10:23:37 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >*.html: Using standard I/O> >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >*.jsp: >init> >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >*.jsp: >param verbose initialized to: true> >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >*.jsp: >param packagePrefix initialized to: jsp_servlet> >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >*.jsp: >param compilerclass initialized to: javac> >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >*.jsp: >param srcCompiler initialized to weblogic.jspc> >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >*.jsp: >param superclass initialized to null> >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >*.jsp: >param workingDir initialized to: >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer> >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >*.jsp: >param pageCheckSeconds initialized to: 1> >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >*.jsp: >initialization complete> >####<10:23:44 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >*.jsp: >pageCheckSeconds over-ruled in JSPServlet to : 1> >####<10:23:45 EEST 24/06/2001> <Info> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101047> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >Generated java file: >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s >ervlet\_ngroot\_web\__index.java> >####<10:23:53 EEST 24/06/2001> <Error> <HTTP> <evgenya> <evgyServer> ><ExecuteThread: '11' for queue: 'default'> <> <> <101046> ><[WebAppServletContext(8059329,WebApp_evgyServer,/WebApp_evgyServer)] >Compilation of >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s >ervlet\_ngroot\_web\__index.java failed: >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s >ervlet\_ngroot\_web\__index.java:165: >handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext >cannot be applied to (java.lang.Throwable) > pageContext.handlePageException(__ee); > ^ >1 error >> >java.io.IOException: Compiler failed >executable.exec(java.lang.String[d:\bea\jdk131\bin\javac.exe, -classpath, >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer >\wl_comp51442;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotd >elete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_ >evgyServer\WEB-INF\lib\993367393172activation.jar;D:\bea\wlserver6.1_beta\.\ >config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_t >mp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367393212ant.j >ar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyS >erver\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\ >WEB-INF\lib\993367393532bsf.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\ap >plications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_ >evgyServer_WebApp_evgyServer\WEB-INF\lib\993367393613concurrent_classes.jar; >D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServ >er\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB >-INF\lib\993367393673cos.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\appli >cations\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evg >yServer_WebApp_evgyServer\WEB-INF\lib\993367393763dbConnBroker.jar;D:\bea\wl >server6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_com >p51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\ >993367393773jasper.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\application >s\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServe >r_WebApp_evgyServer\WEB-INF\lib\993367393823java40.jar;D:\bea\wlserver6.1_be >ta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-I >NF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367394103 >jaxp.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete >_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyS >erver\WEB-INF\lib\993367394133jsdt.jar;D:\bea\wlserver6.1_beta\.\config\mydo >main\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgy >Server_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367394263junit.jar;D:\bea >\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_ >comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\l >ib\993367394324Jwap-0.7.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applic >ations\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgy >Server_WebApp_evgyServer\WEB-INF\lib\993367394354log.jar;D:\bea\wlserver6.1_ >beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB >-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\9933673943 >74mail.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdele >te_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evg >yServer\WEB-INF\lib\993367394404orajdbc816-12.jar;D:\bea\wlserver6.1_beta\.\ >config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_t >mp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367394484parse >r.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_ev >gyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServ >er\WEB-INF\lib\993367394514servlet.jar;D:\bea\wlserver6.1_beta\.\config\mydo >main\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgy >Server_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367394544webserver.jar;D: >\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-I >NF\lib\993367394584xalan.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\appli >cations\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evg >yServer_WebApp_evgyServer\WEB-INF\lib\993367394634xerces.jar;D:\bea\wlserver >6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442 >\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\993367 >394914_log.jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnot >delete_evgyServer\wl_comp51442\WEB-INF\classes;D:\bea\wlserver6.1_beta\confi >g\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_wa >r_evgyServer_evgyServer_WebApp_evgyServer;D:\bea\wlserver6.1_beta\.\config\m >ydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\WEB-INF\_tmp_war_e >vgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\jaxp.jar;D:\bea\wlserver6 >..1_beta\.\config\mydomain\applications\.wlnotdelete_evgyServer\wl_comp51442\ >WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\WEB-INF\lib\xerces. >jar;D:\bea\wlserver6.1_beta\.\config\mydomain\applications\.wlnotdelete_evgy >Server\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer >\WEB-INF\lib\crimson.jar;d:\bea\jdk131\jre\lib\rt.jar;d:\bea\jdk131\jre\lib\ >i18n.jar;d:\bea\jdk131\jre\lib\sunrsasign.jar;d:\bea\jdk131\jre\classes;.;D: >\bea\wlserver6.1_beta\config\mydomain\applications\WebApp_evgyServer\WEB-INF >\lib\xerces.jar;D:\bea\wlserver6.1_beta\config\mydomain\applications\WebApp_ >evgyServer\WEB-INF\lib\xalan.jar;D:\bea\wlserver6.1_beta\config\mydomain\app >lications\WebApp_evgyServer\WEB-INF\lib\mail.jar;D:\bea\wlserver6.1_beta\con >fig\mydomain\applications\WebApp_evgyServer\WEB-INF\lib\activation.jar;.\lib >\weblogic_sp.jar;.\lib\weblogic.jar;D:\bea\wlserver6.1_beta\config\mydomain\ >applications\WebApp_evgyServer\WEB-INF\lib\bsf.jar;D:\bea\wlserver6.1_beta\c >onfig\mydomain\applications\WebApp_evgyServer\WEB-INF\lib\concurrent_classes >..jar;D:\bea\wlserver6.1_beta\config\mydomain\applications\WebApp_evgyServer\ >WEB-INF\lib\cos.jar;D:\bea\wlserver6.1_beta\config\mydomain\applications\Web >App_evgyServer\WEB-INF\lib\dbConnBroker.jar;D:\bea\wlserver6.1_beta\config\m >ydomain\applications\WebApp_evgyServer\WEB-INF\lib\log.jar;D:\bea\wlserver6. >1_beta\config\mydomain\applications\WebApp_evgyServer\WEB-INF\lib\orajdbc816 >-12.jar;D:\bea\wlserver6.0\config\mydomain\applications\WebApp_evgyServer\WE >B-INF\classes, -d, >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer, >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer >\wl_comp51442\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s >ervlet\_ngroot\_web\__index.java]) > at >weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.jav >a:575) > at >weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:354) > at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:360) > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:181) > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:149) > at >weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:34 >4) > at >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java >:240) > at >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java >:284) > at >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java >:200) > at >weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo >ntext.java:2279) > at >weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java >:1923) > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137) > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120) > > >hope that helps. >10x alot. >"Srinagesh Susarla" <[email protected]> wrote in message >news:[email protected] >can u send the server side error-message! >thanks >nagesh >Evgenya Borisenko wrote: >Hi, currently we use Weblogic 6.0 and i decided to try Weblogic 6.1 beta. >So >i deployed our application which was working on Weblogic 6.0 on the newly >installed Weblogic 6.1 beta. Now when i try to access my application >i >recieve the following error page: Compilation of >'D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServe >r\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_ >servlet\_ngroot\_web\__index.java' failed: > >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer >\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s >ervlet\_ngroot\_web\__index.java:165: >handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext >cannot be applied to (java.lang.Throwable) >(No more information available, probably caused by another error) > > >Full compiler error(s): >D:\bea\wlserver6.1_beta\config\mydomain\applications\.wlnotdelete_evgyServer >\wl_comp28255\WEB-INF\_tmp_war_evgyServer_evgyServer_WebApp_evgyServer\jsp_s >ervlet\_ngroot\_web\__index.java:165: >handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext >cannot be applied to (java.lang.Throwable) > pageContext.handlePageException(__ee); > ^ >1 error > > >Wed Jun 20 17:27:28 EEST 2001 Does anyone know what could cause the problem >? Any help will be appreciated.Bybye. > > • Probloms deploying web application in weblogic 8.1 Hi, I've been using weblogic8.1 to host my web applications. The problem that i'm facing is that when i try to upload/deploy the (.war) file through weblogic console it shows the status as success but when i try to access a web resource, it gives me an error saying " The resource did not process correctly" on the browser, where as when i place the (.war) file directly in the applications folder of the user domain i'm able to access the web resource successfully on my browser. Can anyone help me in resolving this issue. I require it urgently. Thanks WLS 9.2 includes pretty advanced features in this area. Both deployment plans and application libraries could be used. There's also a domain/lib directory where jar files can be placed and are visible throughout the server instance. Unfortunately 8.1 has none of these features. In 8.1, your choices are to either add these into the$CLASSPATH, or package them in the application.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

• Deploying web application in weblogic

hi everybody
i hava created one web application and i deployed it in weblogic server
it was showing first page tat was index page
the problem was
when i was trying to access the servlet it was showing some error
the error was
error 500 internal server error
java.lang.UnsupportedClassVersionError: login (Unsupported major.minor version 49.0).
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:794)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:504)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:349)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6291) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3575) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2573) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151) and one more thing when i tried to deploy small program tat was executing nicely tat was invoking servlet from jsp output of this servlet was displaying the welcome msg in my proj when i m trying to invoke servlet from jsp it was showing the above mentioned error i don know y pls help me FYI http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=40&t=002818 • Exception occured while deploying web application in weblogic Hello, I am trying to deploy one web application on weblogic server but i got one exception , if anybody knows how to resolve this problem please help me out. Thank you. Exception is as follows : java.lang.IllegalArgumentException: Renderer for type 'Time' already exists. Thanx javax.faces.FacesException: java.lang.IllegalArgumentException: Renderer for type 'Time' already exists. at com.sun.faces.config.ConfigBase.updateRenderKits(ConfigBase.java:398) at com.sun.faces.config.ConfigBase.updateRuntimeComponents(ConfigBase.java:286) at com.sun.faces.config.ConfigListener.contextInitialized(ConfigListener.java:202) at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:374)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:83)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2678)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:874)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:326)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:114)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:25) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:567)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:131)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:101)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:126)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:329)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:845)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1246)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:432)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)

• Problem deploying web application on WLS 8.1

Hi,
When I try to deploy a web application on weblogic 8.1 it comes back with success.But
trying to access it or testing it through admin console gives me the following
erors -
403 - Forbidden or
Here is what I am doing
My web application is in a war file called paypluscls.war that I've saved inD:\bea\user_projects\domains\mydomain\applications
folder. My weblogic.xml reads like this:
<weblogic-web-app>
<virtual-directory-mapping>
<local-path>d:/bea/user_projects/domains/m
<url-pattern>/paypluscls/*</url-pattern>
</virtual-directory-mapping>
On deploying the application I get success message, but when I try running it
using the following in my browser : http://127.0.0.1:7001/paypluscls i get 403
forbidden error
and if I try http://127.0.0.1:7001/paypluscls/index.htm , i get 404 file not found
error. Please note that index.htm is present in my paypluscls.war.
What am I doing wrong? A quick response will be highly appreciated.

Define a context-root element in weblogic.xml
<weblogic-web-app>
<context-root>paypluscls</context-root>
</weblogic-web-app>
Get index.htm with url:
http://127.0.0.1:7001/paypluscls/index.htm
"vikas" <[email protected]> wrote:
>
Hi,
When I try to deploy a web application on weblogic 8.1 it comes back
with success.But
trying to access it or testing it through admin console gives me the
following
erors -
403 - Forbidden or
Here is what I am doing
My web application is in a war file called paypluscls.war that I've saved
inD:\bea\user_projects\domains\mydomain\applications
folder. My weblogic.xml reads like this:
<weblogic-web-app>
<virtual-directory-mapping>
<local-path>d:/bea/user_projects/domains/m
<url-pattern>/paypluscls/*</url-pattern>
</virtual-directory-mapping>
On deploying the application I get success message, but when I try running
it
using the following in my browser : http://127.0.0.1:7001/paypluscls
i get 403
forbidden error
and if I try http://127.0.0.1:7001/paypluscls/index.htm , i get 404 file
error. Please note that index.htm is present in my paypluscls.war.
What am I doing wrong? A quick response will be highly appreciated.

• Deploy ADF Fusion Web Application on Amazon EC2 Weblogic

Hi,
I am trying to deploy ADF Fusion Web Application (developed using JDev) on Amazon EC2 Weblogic app server but with no success.
Can anyone enlighten me how to deploy ADF Fusion Web App on Amazon EC2 Weblogic?
Thanks for kind assistance!

Hi,
I managed to run "wls_jumpstart" but I am unable to start the console even though I have created a domain.
I cannot find any instructions anywhere about deploying ADF Fusion Web Apps on Amazon EC2 Weblogic or any case studies of success anywhere.
Hence, I am not sure if ADF Runtime is available on the Weblogic on Amazon EC2. Can you please help me in this area as well?
It will be great if you can point me to some instructions on how to load web apps to Amazon EC2 Weblogic as I am quite new to both JDev and Amazon EC2.
Thanks.

Trying to deploy a web application and invoke a servlet through it.
Here is the command I am using for deploying the application:
http://localhost:8080/manager/install?path=/NewApplication&war=file:d:\Tomcat4\webapps\NewApplication
The application get deployed. However, I have a problem. As soon I stop and restart the server, this application is gone.
1. Please someone help: How should I make it permanent so that the application stays even if I restart the server.
2. I am not able to access the servlets placed in the /WEB-INF/classes/ sub-directory under NewApplication directory.
If you need I can cut and paste the web.xml file which will show the deployment descriptor.