Weblogic Jsp Precompilation
Hi there,
I'm not sure that I've got the right forum here - but here goes....
I'm migrating a project from Tomcat to Weblogic 8.1.2 - and I wish that I'd stuck with Tomcat!
I'm trying to use Ant - in conjunction with Weblogic tasks - wldeploy and wlappc - to build and deploy my project for me. And I'm noticing some bizarre behaviour with the weblogic precompilation.
As part of the build process - all jsps are precompile when assembling into an ear file. However when I deploy the ear - Weblogic Server goes ahead and recompiles the jsps all over again - which the defeats the purpose of compiling them at assembly time.
The message I get from the server is
16-Aug-2004 10:45:53 o'clock BST> <Info> <HTTP> <BEA-101295> <Recompiling JS
ervletContext(id=26194723,name=coronersDB,context-path=/coronersDB)], resour
/pages/AdminLetter.jsp], because it is stale. It was previously compiled using a different version of WebLogic Server.
JSP build version: 8.1.2.0
WLS build version: 8.1.2.0.>Does anyone know how I can stop this second precompilation?
Thanks in advance
Tariq
This thread on BEA's Website might be of some help :
http://forums.bea.com/bea/message.jspa?messageID=202411556
Similar Messages
-
Hi,
I using weblogic 6.0 sp1 and struts to develop the web application, I deployed
my web application by war file,I want precompile jsp when weblogic server starts
up by defining the following context parameter in web.xml deployment descriptor:
<context-param>
<param-name>weblogic.jsp.precompile</param-name>
<param-value>true</param-value>
</context-param>
but it failure to pre-compiling JSP's when weblogic server start. I visited
weblogic newsgroup, and followed the info to try using directory struct to deploy
(under .\config\mydomain\applications
or outside of the .\applications directory), both of them had errors. the following
is my web.xml file and error info. Could you give some idea to fix it?
Thanks
Judy
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
<context-param>
<param-name>weblogic.jsp.precompile</param-name>
<param-value>true</param-value>
</context-param>
<!-- Action Servlet Configuration -->
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
<init-param>
<param-name>application</param-name>
<param-value>ApplicationResources</param-value>
</init-param>
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config.xml</param-value>
</init-param>
<init-param>
<param-name>debug</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<param-name>detail</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<param-name>validate</param-name>
<param-value>true</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet>
<servlet-name>InitServlet</servlet-name>
<servlet-class>ccd.web.misc.InitServlet</servlet-class>
<load-on-startup>3</load-on-startup>
</servlet>
<!-- Action Servlet Mapping -->
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
<!-- The Welcome File List -->
<welcome-file-list>
<welcome-file>index.htm</welcome-file>
</welcome-file-list>
<!-- Application Tag Library Descriptor -->
<taglib>
<taglib-uri>/WEB-INF/tlds/app.tld</taglib-uri>
<taglib-location>/WEB-INF/tlds/app.tld</taglib-location>
</taglib>
<!-- Struts Tag Library Descriptors -->
<taglib>
<taglib-uri>/WEB-INF/tlds/struts-bean.tld</taglib-uri>
<taglib-location>/WEB-INF/tlds/struts-bean.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/tlds/struts-html.tld</taglib-uri>
<taglib-location>/WEB-INF/tlds/struts-html.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/tlds/struts-logic.tld</taglib-uri>
<taglib-location>/WEB-INF/tlds/struts-logic.tld</taglib-location>
</taglib>
<!-- Security -->
<security-constraint>
<web-resource-collection>
<web-resource-name>AdminPages</web-resource-name>
<description>
These pages are only accessible by authorised user.
</description>
<url-pattern>/misc/ccd.htm</url-pattern>
<http-method>POST</http-method>
<http-method>GET</http-method>
</web-resource-collection>
<auth-constraint>
<description>
These are the roles who have access
</description>
<role-name>
CcdApp
</role-name>
</auth-constraint>
<user-data-constraint>
<description>
This is how the user data must be transmitted
</description>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<form-login-config>
<form-login-page>/misc/login.jsp</form-login-page>
<form-error-page>/misc/fail_login.jsp</form-error-page>
</form-login-config>
</login-config>
<security-role>
<description>
An administrator
</description>
<role-name>
CcdApp
</role-name>
</security-role>
</web-app>
Error info for war file deployed:
<May 9, 2001 11:20:23 AM EDT> <Error> <HTTP> <[WebAppServletContext(6040101,ccd)
] failure pre-compiling JSP's
java.lang.NullPointerException
at weblogic.servlet.jsp.Jsp2Java.makeReader(Jsp2Java.java:232)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:112)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:253
at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java:124)
at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:44)
at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebAppS
ervletContext.java:2003)
at weblogic.servlet.internal.dd.DescriptorLoader.initFromWebApp(Descript
orLoader.java:741)
at weblogic.servlet.internal.dd.DescriptorLoader.createServletContext(De
scriptorLoader.java:358)
at weblogic.servlet.internal.HttpServer.loadWARContext(HttpServer.java:4
98)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:421)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:126)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:283)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:109)
at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServe
r.java:76)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy29.addWebDeployment(Unknown Source)
at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDe
ployment(WebServerMBean_CachingStub.java:985)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:269)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:109)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBean
s(ConfigurationMBeanImpl.java:409)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:287)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMB
eanImpl.java:866)
at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMB
eanImpl.java:853)
at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.ja
va:838)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:566)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy12.addTarget(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(Appli
cationManager.java:486)
at weblogic.management.mbeans.custom.ApplicationManager.addApplication(A
pplicationManager.java:557)
at weblogic.management.mbeans.custom.ApplicationManager.addApplication(A
pplicationManager.java:504)
at weblogic.management.mbeans.custom.ApplicationManager.poll(Application
Manager.java:428)
at weblogic.management.mbeans.custom.ApplicationManager.poll(Application
Manager.java:380)
at weblogic.management.mbeans.custom.ApplicationManager.update(Applicati
onManager.java:152)
at weblogic.management.mbeans.custom.ApplicationManager.startAdminManage
r(ApplicationManager.java:205)
at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:120)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy2.start(Unknown Source)
at weblogic.management.Admin.startApplicationManager(Admin.java:1034)
at weblogic.management.Admin.finish(Admin.java:491)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<May 9, 2001 11:20:23 AM EDT> <Error> <J2EE> <Error deploying application ccd:
C
ould not load ccd>
<May 9, 2001 11:20:26 AM EDT> <Notice> <WebLogicServer> <WebLogic Server started
>
<May 9, 2001 11:20:26 AM EDT> <Notice> <WebLogicServer> <SSLListenThread listeni
ng on port 7002>
<May 9, 2001 11:20:26 AM EDT> <Notice> <WebLogicServer> <ListenThread listening
on port 7001>
Error info for directory deployed:
<May 9, 2001 4:50:55 PM EDT> <Error> <HTTP> <[WebAppServletContext(6044546,ccd)]
failure pre-compiling JSP's
weblogic.servlet.jsp.JspException: (line 35): Non-matching extension tags
at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:640)
at weblogic.servlet.jsp.JspLexer.mCLOSE_EXTENSION_TAG(JspLexer.java:2076
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1676)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1552)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:893)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:71)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:139)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:113)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:253
at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java:124)
at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:44)
at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebAppS
ervletContext.java:2003)
at weblogic.servlet.internal.dd.DescriptorLoader.initFromWebApp(Descript
orLoader.java:741)
at weblogic.servlet.internal.dd.DescriptorLoader.createServletContext(De
scriptorLoader.java:358)
at weblogic.servlet.internal.HttpServer.loadWARContext(HttpServer.java:4
98)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:421)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:126)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:283)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:109)
at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServe
r.java:76)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy29.addWebDeployment(Unknown Source)
at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDe
ployment(WebServerMBean_CachingStub.java:985)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:269)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:194)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:158)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy28.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2299)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:240)
at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:122)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy21.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
.start(ApplicationManagerMBean_CachingStub.java:435)
at weblogic.management.Admin.startApplicationManager(Admin.java:1030)
at weblogic.management.Admin.finish(Admin.java:491)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<May 9, 2001 4:50:55 PM EDT> <Error> <J2EE> <Error deploying application ccd:
Co
uld not load ccd>
<May 9, 2001 4:51:03 PM EDT> <Error> <HTTP> <[WebAppServletContext(466450,web)]
failure pre-compiling JSP's
java.lang.NullPointerException
at weblogic.servlet.jsp.Jsp2Java.makeReader(Jsp2Java.java:232)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:112)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:253
at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java:124)
at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:44)
at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebAppS
ervletContext.java:2003)
at weblogic.servlet.internal.dd.DescriptorLoader.initFromWebApp(Descript
orLoader.java:741)
at weblogic.servlet.internal.dd.DescriptorLoader.createServletContext(De
scriptorLoader.java:358)
at weblogic.servlet.internal.HttpServer.loadWARContext(HttpServer.java:4
98)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:421)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:126)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:283)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:109)
at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServe
r.java:76)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy29.addWebDeployment(Unknown Source)
at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDe
ployment(WebServerMBean_CachingStub.java:985)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:269)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:109)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBean
s(ConfigurationMBeanImpl.java:409)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:287)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMB
eanImpl.java:866)
at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMB
eanImpl.java:853)
at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.ja
va:838)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:566)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy12.addTarget(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(Appli
cationManager.java:486)
at weblogic.management.mbeans.custom.ApplicationManager.addApplication(A
pplicationManager.java:557)
at weblogic.management.mbeans.custom.ApplicationManager.addApplication(A
pplicationManager.java:504)
at weblogic.management.mbeans.custom.ApplicationManager.poll(Application
Manager.java:428)
at weblogic.management.mbeans.custom.ApplicationManager.poll(Application
Manager.java:380)
at weblogic.management.mbeans.custom.ApplicationManager.update(Applicati
onManager.java:152)
at weblogic.management.mbeans.custom.ApplicationManager.startAdminManage
r(ApplicationManager.java:205)
at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:120)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:562)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:548)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
at $Proxy2.start(Unknown Source)
at weblogic.management.Admin.startApplicationManager(Admin.java:1034)
at weblogic.management.Admin.finish(Admin.java:491)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
>
<May 9, 2001 4:51:04 PM EDT> <Error> <J2EE> <Error deploying application web:
Co
uld not load web>
<May 9, 2001 4:51:18 PM EDT> <Notice> <WebLogicServer> <WebLogic Server started>
<May 9, 2001 4:51:18 PM EDT> <Notice> <WebLogicServer> <SSLListenThread listenin
g on port 7002>
<May 9, 2001 4:51:18 PM EDT> <Notice> <WebLogicServer> <ListenThread listening
o
n port 7001>
Trying adding this to your weblogic.xml file:
<jsp-descriptor>
<jsp-param>
<param-name>precompile</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
-
How can WLS use JSP pages in a Web Application (either a .war file or a war directory structure) without a java compiler?
I suspect either the JSP specification is flawed (i.e. it doesn't take account of servers using just a JRE), or BEA's implementation is broken.
Production servers do not have a JDK installed. They only have a JRE. Therfore a java compiler is not present on the machine that the Web Application is deployed onto.
On the development machine, when the server is requested to load the JSP it creates a tmpwar directory within the Web Application directory structure. This is then included in the resultant .war file thus:
D:\war>jar -tf gmi.war
META-INF/
META-INF/MANIFEST.MF
gmiService.jsp
WEB-INF/
WEB-INF/classes/
WEB-INF/classes/com/
WEB-INF/classes/com/bt/
WEB-INF/classes/com/bt/gmi/
WEB-INF/classes/com/bt/gmi/gmiService.class
WEB-INF/getList.xsl
WEB-INF/getListByConnection.xsl
WEB-INF/getListByDistrict.xsl
WEB-INF/getListByDistrictConnection.xsl
WEB-INF/lib/
WEB-INF/source/
WEB-INF/source/build.bat
WEB-INF/source/gmiService.java
WEB-INF/web.xml
WEB-INF/weblogic.xml
tmpwar/
tmpwar/jsp_servlet/
tmpwar/jsp_servlet/_gmiservice.class
tmpwar/jsp_servlet/_gmiservice.java
When deployed on the production server with the web.xml file set to use the following values (note XML stripped):
weblogic.jsp.pageCheckSeconds
-1
weblogic.jsp.precompile
false
weblogic.jsp.compileCommand
javac
weblogic.jsp.verbose
true
weblogic.jsp.packagePrefix
jsp_servlet
weblogic.jsp.keepgenerated
false
And in the weblogic.properties file:
weblogic.httpd.webApp.gmi=war/gmi
I've also tried with the .war file, but that insists on creating another tmpwar directory outside of the .war file.
Then, although I have set pageCheckSeconds to -1 (don't check and don't recompile) ter production server still attempts to recompile the JSP's:
Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: init
Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param verbose initialized to: true
Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param packagePrefix initialized to: jsp_servlet
Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param compileCommand initialized to: javac
Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param srcCompiler initialized to weblogic.jspc
Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param superclass initialized to null
Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param workingDir initialized to: /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war
Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param pageCheckSeconds initialized to: -1
Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: initialization complete
Mon Sep 25 11:40:12 BST 2000:<I> <WebAppServletContext-gmi> Generated java file: /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war/jsp_servlet/gmiService.java
Mon Sep 25 11:40:14 BST 2000:<E> <WebAppServletContext-gmi> Compilation of /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war/jsp_servlet/gmiService.java failed: Exception in thread "main" java.lang.NoClassDefFoundError: sun/tools/javac/Main
java.io.IOException: Compiler failed executable.exec([Ljava.lang.String;[javac, -classpath, /opt/Solaris_JRE_1.2.1_04/lib/rt.jar:/opt/Solaris_JRE_1.2.1_04/lib/i18n.jar:/opt/Solaris_JRE_1.2.1_04/classes:/var/wls/5.1/weblogic/lib/weblogic510sp4boot.jar:/var/wls/5.1/weblogic/classes/boot:/var/wls/5.1/weblogic/eval/cloudscape/lib/cloudscape.jar:/var/wls/5.1/weblogic/lib/wleorb.jar:/var/wls/5.1/weblogic/lib/wlepool.jar:/var/wls/5.1/weblogic/lib/weblogic510sp4.jar:/var/wls/5.1/weblogic/license:/var/wls/5.1/weblogic/classes:/var/wls/5.1/weblogic/lib/weblogicaux.jar:/opt/wls-servers/gmiServer/weblogic/gmiServer/serverclasses:/opt/wls-servers/gmiServer/weblogic/lotusxsl.jar:/opt/wls-servers/gmiServer/weblogic/xerces.jar:/opt/wls-servers/gmiServer/weblogic/logging.jar::/opt/wls-servers/gmiServer/weblogic/war/gmi/WEB-INF/classes:/opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war, -d, /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war, /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war/jsp_servlet/gmiService.java])
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.io.IOException.<init>(Compiled Code)
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(Compiled Code)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:200)
at weblogic.servlet.jsp.JspStub.compilePage(Compiled Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:173)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:187)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:118)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:142)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:744)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:692)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
The default Java compiler from sun lives in the tools.jar that comes with
the JDK. Just add that to your set of JARs which are deployed in production
and you should be fine. No need to install the full JDK - just make the
tools.jar available to WebLogic.
Regards
James
James Strachan
=============
email: [email protected]
web: http://www.metastuff.com
"Martin Webb" <[email protected]> wrote in message
news:[email protected]...
>
> How can WLS use JSP pages in a Web Application (either a .war file or a
war directory structure) without a java compiler?
>
> I suspect either the JSP specification is flawed (i.e. it doesn't take
account of servers using just a JRE), or BEA's implementation is broken.
>
> Production servers do not have a JDK installed. They only have a JRE.
Therfore a java compiler is not present on the machine that the Web
Application is deployed onto.
>
> On the development machine, when the server is requested to load the JSP
it creates a tmpwar directory within the Web Application directory
structure. This is then included in the resultant .war file thus:
>
> D:\war>jar -tf gmi.war
> META-INF/
> META-INF/MANIFEST.MF
> gmiService.jsp
> WEB-INF/
> WEB-INF/classes/
> WEB-INF/classes/com/
> WEB-INF/classes/com/bt/
> WEB-INF/classes/com/bt/gmi/
> WEB-INF/classes/com/bt/gmi/gmiService.class
> WEB-INF/getList.xsl
> WEB-INF/getListByConnection.xsl
> WEB-INF/getListByDistrict.xsl
> WEB-INF/getListByDistrictConnection.xsl
> WEB-INF/lib/
> WEB-INF/source/
> WEB-INF/source/build.bat
> WEB-INF/source/gmiService.java
> WEB-INF/web.xml
> WEB-INF/weblogic.xml
> tmpwar/
> tmpwar/jsp_servlet/
> tmpwar/jsp_servlet/_gmiservice.class
> tmpwar/jsp_servlet/_gmiservice.java
>
> When deployed on the production server with the web.xml file set to use
the following values (note XML stripped):
>
> weblogic.jsp.pageCheckSeconds
> -1
>
> weblogic.jsp.precompile
> false
>
> weblogic.jsp.compileCommand
> javac
>
> weblogic.jsp.verbose
> true
>
> weblogic.jsp.packagePrefix
> jsp_servlet
>
> weblogic.jsp.keepgenerated
> false
>
>
> And in the weblogic.properties file:
>
> weblogic.httpd.webApp.gmi=war/gmi
>
> I've also tried with the .war file, but that insists on creating another
tmpwar directory outside of the .war file.
>
>
> Then, although I have set pageCheckSeconds to -1 (don't check and don't
recompile) ter production server still attempts to recompile the JSP's:
>
>
> Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: init
> Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param
verbose initialized to: true
> Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param
packagePrefix initialized to: jsp_servlet
> Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param
compileCommand initialized to: javac
> Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param
srcCompiler initialized to weblogic.jspc
> Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param
superclass initialized to null
> Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param
workingDir initialized to:
/opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war
> Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp: param
pageCheckSeconds initialized to: -1
> Mon Sep 25 11:40:11 BST 2000:<I> <WebAppServletContext-gmi> *.jsp:
initialization complete
> Mon Sep 25 11:40:12 BST 2000:<I> <WebAppServletContext-gmi> Generated java
file:
/opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war/jsp_servlet/gmiService.
java
> Mon Sep 25 11:40:14 BST 2000:<E> <WebAppServletContext-gmi> Compilation of
/opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war/jsp_servlet/gmiService.
java failed: Exception in thread "main" java.lang.NoClassDefFoundError:
sun/tools/javac/Main
>
> java.io.IOException: Compiler failed
executable.exec([Ljava.lang.String;[javac, -classpath,
/opt/Solaris_JRE_1.2.1_04/lib/rt.jar:/opt/Solaris_JRE_1.2.1_04/lib/i18n.jar:
/opt/Solaris_JRE_1.2.1_04/classes:/var/wls/5.1/weblogic/lib/weblogic510sp4bo
ot.jar:/var/wls/5.1/weblogic/classes/boot:/var/wls/5.1/weblogic/eval/cloudsc
ape/lib/cloudscape.jar:/var/wls/5.1/weblogic/lib/wleorb.jar:/var/wls/5.1/web
logic/lib/wlepool.jar:/var/wls/5.1/weblogic/lib/weblogic510sp4.jar:/var/wls/
5.1/weblogic/license:/var/wls/5.1/weblogic/classes:/var/wls/5.1/weblogic/lib
/weblogicaux.jar:/opt/wls-servers/gmiServer/weblogic/gmiServer/serverclasses
:/opt/wls-servers/gmiServer/weblogic/lotusxsl.jar:/opt/wls-servers/gmiServer
/weblogic/xerces.jar:/opt/wls-servers/gmiServer/weblogic/logging.jar::/opt/w
ls-servers/gmiServer/weblogic/war/gmi/WEB-INF/classes:/opt/wls-servers/gmiSe
rver/weblogic/war/gmi/_tmp_war, -d,
/opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war,
/opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war/jsp_servlet/gmiService.
java])
> at java.lang.Throwable.fillInStackTrace(Native Method)
> at java.lang.Throwable.fillInStackTrace(Compiled Code)
> at java.lang.Throwable.<init>(Compiled Code)
> at java.lang.Exception.<init>(Compiled Code)
> at java.io.IOException.<init>(Compiled Code)
> at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(Compiled Code)
> at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:200)
> at weblogic.servlet.jsp.JspStub.compilePage(Compiled Code)
> at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:173)
> at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:18
7)
> at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:118)
> at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:142)
> at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:744)
> at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:692)
> at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:251)
> at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
> at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
> at weblogic.kernel.ExecuteThread.run(Compiled Code)
>
>
>
-
Hi All,
I am having serious trouble trying to precompile my JSP's and have the wl
server recognise them (and not re-compile them for me). Im using WLS6.1 with
SP2 installed.
I am running the JSPC pre-compiler with -D ....WEB-INF\classes. The files
get created as expected and then I put them into my WAR file. When I deploy
the WAR file, WLS always recompiles. I have experimented at length with
different settings in my weblogic.xml, but as yet have had no success. I
have also read some previous posts, but these have not helped either.
Any suggestions or advice are very welcome!
Thanks,
Mark
The suggestion to register JSPs as servlets is not at all practical or acceptable
to me. Across multiple applications, we have over 200 JSP files and there's no way
I would even consider this approach. What needs to happen is BEA should fix the problem
and be more forthcoming about such "bugs" instead of letting the customers serve
as QA and having to "ask" for patches. Why is 6.1 SP3 not on the web site? Why aren't
all the patches available online for download? For the amount of money BEA charges,
especially for clustered licenses, this type of problem should not go unfixed.
Sam Fowler
"Ashok Madhavan" <[email protected]> wrote:
>
>hi,
>for pre-compiling the jsps in production in .ear format we found a way of
>doing it.
>We treated all the jsps in the application as servlets. we precompiled all
>the jsps
>before-hand and in the web.xml we gave a servlet-name, sevlet-class etc
>just as we
>do for a normal servlet. The compiled classes were in WEB-INF/classes/jsp_servlet.
>we used hte weblogic.jspc coming along with weblogic. we have weblogic 6.1
>with SP
>2.
>
>we then did a .war file of this as we do normally.
>
>now we deployed this war file and it did work. we didnt include even a single
>jsp
>file with our application, just compiled jsps as servlets.
>
>The main problem with this is all the jsp need to be pre-compiled and the
>deployment
>has to be .war/.ear. this is not suitable for development. for developement
>there
>are other easy ways of doing it though.
>
>regards
>Ashok Madhavan
>
>"Eric Ma" <[email protected]> wrote:
>>
>>Simon:
>>
>>Can you do the community a service by posting the patched weblogic.servlet.jsp.Precompiler
>>class? If it is not convenient to share the Java source file, how about
>>just the
>>.class file? I am sure a lot of people will great appreciate the help.
>>
>>Eric Ma
>>
>>
>>"Simon Spruzen" <[email protected]> wrote:
>>>
>>>There's still a bug in WebLogic's precompile dependency checking in
>6.1
>>>SP1 and
>>>SP2. It will always recompile every JSP in a war file on deployment
>if
>>>precompile
>>>option is true because WebLogic incorrectly generates the mangled JSP
>servlet
>>>class
>>>name. I just patched the appropriate class (weblogic.servlet.jsp.Precompiler)
>>>and
>>>all is cool - I precompile my JSPs, put the generated servlet classes
>into
>>>the war
>>>file and deploy it. Much quicker.
>>>
>>>I have raised this as a bug with BEA (I sent them my fix too) and they're
>>>going to
>>>try and sort this out for SP3. (Judging by postings, this is still a bug
>>>in 7.0)
>>>
>>>simon.
>>>
>>>Ryan Barker <[email protected]> wrote:
>>>>I am having a similar problem. With sp1, the process we would do the
>following:
>>>>Unjar the application into exploded format
>>>>start up the server using the exploded format with precompile turned
>on
>>>>copy the /WEB-INF/_tmp_war_..../jsp_servlets directory into the /WEB-INF/classes/jsp_servlets
>>>>directory
>>>>rejar up the application
>>>>start up the server using the war file.
>>>>
>>>>Now when we do this process, it recompile all of the jsps into the .wlnotdelete
>>>>directory.
>>>>
>>>>This is seriously annoying. In production we have to have the applications
>>>>directory as read only due to security policies and jsps need to
>>>>be pre-compiled. Also on a slightly different note, if the config.xml
>>>file
>>>>is set to readonly, weblogic sp1 complained very loudly every 30
>>>>seconds, have not checked with sp2 yet, hope that this has been fixed.
>>>>
>>>>Ryan Barker
>>>>
>>>>ludovic le goff wrote:
>>>>> Hello Mark,
>>>>>
>>>>> Please check that in the weblogic.xml file of your web application,
>>you
>>>>get
>>>>> an entry like:
>>>>>
>>>>> <context-param>
>>>>> <param-name>weblogic.jsp.precompile</param-name>
>>>>> <param-value>true</param-value>
>>>>> </context-param>
>>>>>
>>>>> With the WLS 6.1 SP2, a fix has been done ( 041729 ) and now, the
>>>>> weblogic.servlet.jsp.Precompiler honors weblogic.xml parameters, like
>>>>> workingdir, packagePrefix, etc., for the JSPs that it precompiles
>>>>>
>>>>> Hope this helps,
>>>>> Ludovic
>>>>> Developer Relations Engineer
>>>>> BEA Support
>>>>> "newsgroups.bea.com" <[email protected]> a écrit dans le message
>>news:
>>>>> [email protected]...
>>>>>
>>>>>>Hi All,
>>>>>>
>>>>>>I am having serious trouble trying to precompile my JSP's and have
>the
>>>>wl
>>>>>>server recognise them (and not re-compile them for me). Im using WLS6.1
>>>>>
>>>>> with
>>>>>
>>>>>>SP2 installed.
>>>>>>
>>>>>>I am running the JSPC pre-compiler with -D ....WEB-INF\classes. The
>>files
>>>>>>get created as expected and then I put them into my WAR file. When
>I
>>>>>
>>>>> deploy
>>>>>
>>>>>>the WAR file, WLS always recompiles. I have experimented at length
>with
>>>>>>different settings in my weblogic.xml, but as yet have had no success.
>>>>I
>>>>>>have also read some previous posts, but these have not helped either.
>>>>>>
>>>>>>Any suggestions or advice are very welcome!
>>>>>>Thanks,
>>>>>>Mark
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
-
Jsp precompile - does it work?
Part of a weblogic.xml file. Now, it sets the precompile option to true, but if I deploy the app. or touch the redeploy the .jsp arent't precompiled. They are always compiled the first time they load. (And this often gives me a ClassCastException, that why I want to precompile them!!!)
<.....snip.....>
<jsp-descriptor>
<jsp-param>
<param-name>pageCheckSeconds</param-name>
<param-value>-1</param-value>
</jsp-param>
<jsp-param>
<param-name>precompile</param-name>
<param-value>true</param-value>
</jsp-param>
<jsp-param>
<param-name>verbose</param-name>
<param-value>true</param-value>
</jsp-param>
<jsp-param>
<param-name>keepgenerated</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
<.....snip.....>
Hi.
I have the same problem.
I am using the default Application and have put the context parameter tag in
the web.xml file as follows:
<context-param>
<param-name>weblogic.jsp.precompile</param-name>
<param-value>true</param-value>
</context-param>
Still no good :( ..... Is BEA listening ???
-Sandeep
"Merg" <[email protected]> wrote in message
news:3a766611$[email protected]..
>
> Part of a weblogic.xml file. Now, it sets the precompile option to true,
but if I deploy the app. or touch the redeploy the .jsp arent't precompiled.
They are always compiled the first time they load. (And this often gives me
a ClassCastException, that why I want to precompile them!!!)
>
> <.....snip.....>
> <jsp-descriptor>
> <jsp-param>
> <param-name>pageCheckSeconds</param-name>
> <param-value>-1</param-value>
> </jsp-param>
> <jsp-param>
> <param-name>precompile</param-name>
> <param-value>true</param-value>
> </jsp-param>
> <jsp-param>
> <param-name>verbose</param-name>
> <param-value>true</param-value>
> </jsp-param>
> <jsp-param>
> <param-name>keepgenerated</param-name>
> <param-value>true</param-value>
> </jsp-param>
> </jsp-descriptor>
> <.....snip.....>
>
-
Jsp precompilation in weblogic 10.3
I tried precompiling jspx and jsff files using weblogic.jspc.
generated class files are copied to .war/web-inf/classes as i specified this path as destination directory.
when i deploy the .war and try to access page, i get following error
java.lang.IllegalStateException: <f:view> was not present on this page; tag [email protected]b8encountered without an <f:view> being processed.
at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.setProperties(UIXComponentELTag.java:97)
at javax.faces.webapp.UIComponentClassicTagBase.findComponent(UIComponentClassicTagBase.java:613)
at javax.faces.webapp.UIComponentClassicTagBase.doStartTag(UIComponentClassicTagBase.java:1142)
at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.doStartTag(UIXComponentELTag.java:72)
at oracle.adfinternal.view.faces.taglib.region.IncludeTag.doStartTag(IncludeTag.java:179)
at oracle.adfinternal.view.faces.taglib.region.DynamicIncludeTag.doStartTag(DynamicIncludeTag.java:109)
at jsp_servlet._components.__domainpage_jspx._jspService(__domainpage_jspx.java:137)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
After precompiling, do i need to do any config step.
Kindly suggest list of steps to precompile Jsp in .war using weblogic.jspcFrom the previous posts, I am assume that the desire is to have jsps precompile during the build process not when the app is deployed to the server. We build ours with Maven and have a command line call to invoke appc. [Jspc should not be used since it is depricated. |http://download.oracle.com/docs/cd/E14571_01/web.1111/e13749/utils.htm#ADMRF158]. Here is the [appc documentation|http://download.oracle.com/docs/cd/E14571_01/web.1111/e13706/splitbuild.htm#i1113244] and [more appc documentation|http://download.oracle.com/docs/cd/E14571_01/web.1111/e13719/appc_ejbc.htm#EJBPG1090] . To make appc run manually, you pretty much have to supply every library that your weblogic.xml references to the -library option. You also need enviroment variable set piror to calling. Anyhow this is what our bat file for calling appc looks like.
set BEAWLS_HOME=%1
set WAR=%2
call %BEAWLS_HOME%\wlserver_10.3\server\bin\setWLSEnv.cmd
call java weblogic.appc -verbose -librarydir %BEAWLS_HOME%\wlportal_10.3\portal-admin\lib\j2ee-modules -library %BEAWLS_HOME%\wlserver_10.3\common\deployable-libraries\jsf-1.2.war,%BEAWLS_HOME%\modules\com.bea.content.vcr_10.3.2.0\content-management-faces-web-lib.war -classpath %BEAWLS_HOME%\wlportal_10.3\light-portal\lib\system\netuix_common.jar %WAR%
This is for Oracle Portal 10.3.2. The locations of the war moved around from Portal 10.3.0 to 10.3.2. BEAWLS is our the Oracle\Middleware (bea\home in older installs) folder from our Weblogic Portal install. WAR is the existing war file. I deleted most war libararies, since there are a lot to list making it really long. It takes our war and compiles all the jsps in it and then makes a new war in its place. The war is then packaged into an ear. Building with ant probably take care some of it for you, but this is what it looks like to call the command manually. -
JSP PRECOMPILER IS NOT WORKING WITH WEBLOGIC 6.1 SERVICE PACK 5
When i compile JSPs using JSP PreCompiler in weblogic 6.1
( Service Pack 4 ) , compilation is perfect.
But when i precompile the same JSPs with weblogic 6.1 (Service Pack 5 )
, i get compilation error.
Variable Not Found error comes in service pack 5. But the same code works
well with service pack 4.
Could anyone help me ?
[java] C:\CVSMessageRouter\platform-apps\2notify\webapp\consoleapp\.\web\WE
NF\classes\jsp_servlet\_secure\__confirmation.java:280: cannot resolve symbol
[java] symbol : variable yesLinkPageText
[java] location: class jsp_servlet._secure.__confirmation
[java] htmllink0.setPage(yesLinkPageText); //[ /secure/co
rmation.jsp; Line: 32]
[java] ^
[java] C:\CVSMessageRouter\platform-apps\2notify\webapp\consoleapp\.\web\WE
NF\classes\jsp_servlet\_secure\__confirmation.java:378: cannot resolve symbol
[java] symbol : variable noLinkPageText
[java] location: class jsp_servlet._secure.__confirmation
[java] htmllink0.setPage(noLinkPageText); //[ /secure/con
mation.jsp; Line: 37]
[java] Error: compilation of jsp file /secure/confirmation.jsp (java file C
VSMessageRouter\platform-apps\2notify\webapp\consoleapp\.\web\WEB-INF\classes
p_servlet\_secure\__confirmation.java failed):
[java] ^
[java] null
[java] 2 errors
[java] Error: [jspc]: 1 file(s) failed:
[java] /secure/confirmation.jsp
[java] java.io.IOException: Compiler failed executable.exec(java.lang.String
Can you post the jsp page or a example which doesnt compile in sp5. It seems
difficult to guage what the problem could be from looking at the error.
--Nagesh
"george vargeese" <[email protected]> wrote in message
news:40c56502$1@mktnews1...
>
> When i compile JSPs using JSP PreCompiler in weblogic 6.1
> ( Service Pack 4 ) , compilation is perfect.
>
> But when i precompile the same JSPs with weblogic 6.1 (Service Pack
5 )
> , i get compilation error.
>
> Variable Not Found error comes in service pack 5. But the same code
works
> well with service pack 4.
>
> Could anyone help me ?
>
>
> [java]
C:\CVSMessageRouter\platform-apps\2notify\webapp\consoleapp\.\web\WE
> NF\classes\jsp_servlet\_secure\__confirmation.java:280: cannot resolve
symbol
>
> [java] symbol : variable yesLinkPageText
> [java] location: class jsp_servlet._secure.__confirmation
> [java] htmllink0.setPage(yesLinkPageText); //[
/secure/co
> rmation.jsp; Line: 32]
> [java] ^
> [java]
C:\CVSMessageRouter\platform-apps\2notify\webapp\consoleapp\.\web\WE
> NF\classes\jsp_servlet\_secure\__confirmation.java:378: cannot resolve
symbol
>
> [java] symbol : variable noLinkPageText
> [java] location: class jsp_servlet._secure.__confirmation
> [java] htmllink0.setPage(noLinkPageText); //[
/secure/con
> mation.jsp; Line: 37]
> [java] Error: compilation of jsp file /secure/confirmation.jsp (java
file C
>
VSMessageRouter\platform-apps\2notify\webapp\consoleapp\.\web\WEB-INF\classe
s
> p_servlet\_secure\__confirmation.java failed):
> [java] ^
> [java] null
> [java] 2 errors
> [java] Error: [jspc]: 1 file(s) failed:
> [java] /secure/confirmation.jsp
> [java] java.io.IOException: Compiler failed
executable.exec(java.lang.String
>
>
-
JSP Precompiler could not load class
Has anyone come across this ?
Thanks,
MBI
I am trying to have a generated jsp page load and this uses a generated bean class.
The precompiler complains about not being able to load the class.
<May 4, 2004 3:40:11 PM GMT-08:00> <Debug> <HTTP> <BEA-101158> <Exception thrown
while loading /Testful: weblogic.servlet.jsp.JspException: (line 11): class 'co
m.foo.test.TestfulJspBean' could not be loaded
weblogic.servlet.jsp.JspException: (line 11): class 'com.foo.test.TestfulJspBean'
could not be loaded
More info
at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:711)
at weblogic.servlet.jsp.JspLexer.processBeanTag(JspLexer.java:1379)
at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(JspLexer.java:3647)
at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1931)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1824)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1752)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:962)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:105)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:228)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:120)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:25
at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java:191)
at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:71)
at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:82)
at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebApp
ontext.java:4916)
Has anyone come across this ?
Thanks,
MBI
I am trying to have a generated jsp page load and this uses a generated bean class.
The precompiler complains about not being able to load the class.
<May 4, 2004 3:40:11 PM GMT-08:00> <Debug> <HTTP> <BEA-101158> <Exception thrown
while loading /Testful: weblogic.servlet.jsp.JspException: (line 11): class 'co
m.foo.test.TestfulJspBean' could not be loaded
weblogic.servlet.jsp.JspException: (line 11): class 'com.foo.test.TestfulJspBean'
could not be loaded
More info
at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:711)
at weblogic.servlet.jsp.JspLexer.processBeanTag(JspLexer.java:1379)
at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(JspLexer.java:3647)
at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1931)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1824)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1752)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:962)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:105)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:228)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:120)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:25
at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java:191)
at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:71)
at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:82)
at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebApp
ontext.java:4916)
-
Hello,
We are converting our application builds from Web Logic 8.1 to 10. As part of the build, we precompile the jsps to improve the rendering time and this has worked fine in WL 8.1 so far. However, when I changed the WL version to 10, I get the following error!
[echo] **** jspc: Precompiling WEBLOGIC JSPs
[java] Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/servlet/jsp/jspc20: weblogic/utils/compiler/Tool
Surprisingly, I found the Tool.class in the weblogic.jar for 81 but not in 10.
Could someone let me know where this class is residing now in WL10?
Thank you
SGI'm guessing you're very new at posting technical questions on the internet (at least I hope you're new at it).
You need to provide specific details about what you're doing, what you're seeing, and what you expect to see. No one could possibly give you a useful answer without that. -
Parsing in Weblogic/jsp doesn't work; application-mode (command-line) works
Hello-
Parsing my XML file in Weblogic/jsp doesn't work, whereas it works
in application-mode... (albeit on two different machines)
Here are the parameters:
server1:
weblogic 6.0
win2k server
jre1.3
my personal machine:
***no weblogic***
win2k server
jre1.3
When I run my code as an application (command-line style) on my machine,
parsing in my xml file works fine, and I can do a root.toString() and it
dumps out the entire xml file, as desired.
However, running my code inside weblogic (on server1) in JSP, parsing in
my file and doing a root.toString() results in the following: [dmui: null]
(where dmui is my root)
(even though i'm running it on two different machines, i'm positive its the
same code (the servers share a mapped drive)...
So, I think its probably because I'm using a different parser, as
specified by weblogic? There are no exceptions being thrown. Here's my
(abbreviated) code, which is called either command line style or in a JSP:
// Imports
import org.w3c.dom.*;
import org.w3c.dom.Document;
import javax.xml.parsers.*;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
DocumentBuilderFactory docBuilderFactory =
DocumentBuilderFactory.newInstance();
DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
mDocument = docBuilder.parse (inFile);
myRoot.toString()
-END
Doing a System.getProperty("javax.xml.parsers.DocumentBuilderFactory")
results in:
server1 (weblogic/jsp):
"weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
my machine (application-mode):
null
Does anyone have any ideas about how to get this work? Do I try to set it
up so that they both use the same parser? Do I change the Weblogic parser?
If so, to what? And how?
Am I even close?
Any help would be appreciated..
Thanks, Clint
"[email protected]" <[email protected]> wrote in message
news:[email protected]...
No problem, glad you got it worked out :)
~Ryan U.
Jennifer wrote in message <[email protected]>...
I completely missed setting the property(:-o), foolish mistake. That wasit. Thanks.
"j.upton" <[email protected]> wrote:
Jennifer,
Personally I would get rid of import com.sun.xml.parser.* and use xerces
which comes with WLS 6.0 now, unless like I said earlier you have a need
to
use the sun parser :) Try something like this with your code --I've put
things to watch for as comments in the code.
import javax.xml.parsers.*;
import org.xml.sax.SAXException;
import org.w3c.dom.*;
import java.io.FileInputStream;
public class BasicDOM {
public BasicDOM (String xmlFile) {
try{
FileInputStream inStream;
Document document;
/*You must specify a parser for jaxp. You can in a simple view
think
of this as being analogous to a driver used by JDBC or JNDI. If you are
using this in the context of a servlet or JSP and have set an XML
registry
with the console this happens automatically. You can also invoke it in
the
context of an application on the command line using the -D switch. */
System.setProperty("javax.xml.parsers.DocumentBuilderFactory",
>>>
"weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl");
// create a document factory
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
// specify validating or non-validating parser
dbf.setValidating(true);
// obtain a factory
DocumentBuilder db = dbf.newDocumentBuilder();
// create a document from the factory
inStream = new FileInputStream(xmlFile);
document = db.parse(inStream);
}//try
catch (Exception e)
System.out.println("Unexpected exception reading document!"
+e);
System.exit (0);
}//catch
}//BasicDom
// Main Method
public static void main (String[] args) {
if (args.length < 1)
System.exit(1); file://or you can be more verbose
new BasicDOM(args[0]);
}//class
=============================================
That will give you a basic DOM you can manipulate and parse it fromthere.
BTW this code
compiled and ran on WLS 6.0 under Windows 2000.
Let me know if this helped or you still are having trouble.
~Ryan U.
"Jennifer" <[email protected]> wrote in message
news:[email protected]...
Actually I included com.sun.xml.parser.* as one last febble attempt toget
it working.
And as for source code, I included the code. If I just put that oneline
of code
in, including the imports, it fails giving me an error listed above inthe
subject
line. Here is the code again:
package examples.xml.http;
import javax.xml.parsers.*;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.w3c.dom.*;
import java.util.*;
import java.net.*;
import org.xml.sax.*;
import java.io.*;
public class BasicDOM {
static Document document;
public BasicDOM (String xmlFile) {
try {
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
} catch (FactoryConfigurationError e){
System.err.println(e.getException());
e.printStackTrace();
// Main Method
public static void main (String[] args) {
BasicDOM basicDOM = new BasicDOM (args[0]);Hi, Rob
Does it work in WL9.2?
It seems I do it exactly as the explained at http://edocs.bea.com/wls/docs81/programming/classloading.html - and it fails :o(.
I try to run my app.ear with WL9.2 There are 2 components in it: webapp and mdb. The webapp/WEB-INF contains weblogic.xml:
<weblogic-web-app>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
</weblogic-web-app>
Mdb is expected to run in the same mode, i.e. to prefer the webapp/WEB-INF/*.jar over the parent Weblogic classloader. To do so I add the weblogic-application.xml to the app.ear!/META-INF:
<weblogic-application>
<classloader-structure>
<module-ref>
<!-- reminder: this webapp contains
prefer-web-inf-classes -->
<module-uri>webapp</module-uri>
</module-ref>
<classloader-structure>
<module-ref>
<module-uri>mdb.jar</module-uri>
</module-ref>
</classloader-structure>
</classloader-structure>
</weblogic-application>
Now, when classloader-structure specified, both webabb and mdb prefer the weblogic root loader as if prefer-web-inf-classes not defined at all. -
What's the available value for weblogic.jsp.encoding in web application.
Hi,
I'm using chinese windows nt 4.0 and weblogic 5.1 sp6.When I did not set
weblogic.jsp.encoding to GB2312 , when the jsp file contain's chinese , the
output will be error .And when I did not set it , the output is correct, but
when I use request.getParameter("SomeFormElement")(the element inputed
chinese), the return value is error.
How should I set weblogic.jsp.encoding value to satisfy all this problem?
When I set the value to ISO-8859, there is an exception:
java.io.UnsupportedEncodingException: Charset: 'ISO-8859' not recognized,
and there is no alias for it in the weblogic.httpd.charsets property. So
What's the available value for weblogic.jsp.encoding in web application?
Pan
hi ,
i think the best way is to create java beans ,in that bean call your EJB ,
and check the validation over there.
and make that bean scope to session.
in each and everypage try to check the session ,if it is not valid then forward to your login page...
otherwise continue to give access to him like guest
Regards,
AfTaB -
NoClassDefFoundError: weblogic/jsp
I'm trying to RTFM, but I need a pointer.
I've been asked to 'fix' something, and before I break something to fix it,
I thought to make sure the methods work well. ;-)
I trying to 'java weblogic.jspc filename.jsp' and I trying to get the
java file
so that I can verify that the changes I've made to a copy of the file are
doing
what I think 'it' should do..
well something is wrong on this machine, I'm getting an error
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/jsp
I've used the verbose mode to track the execution, and it (what ever it is
at this point)
has loaded classes from the rt set of jars.
Am I missing something fundamental? what should I be looking for?
Use the command java -classpath <weblogic class dir>:<dir>/weblogicaux.jar -keep
generated filename.jsp
You say you typed weblogic.jspc, but the error message says weblogic.jsp - somebody's
made a mistake.
Mike
"Kermit Tensmeyer" <[email protected]> wrote:
>I'm trying to RTFM, but I need a pointer.
>
>I've been asked to 'fix' something, and before I break something to fix
>it,
>I thought to make sure the methods work well. ;-)
>
>
>I trying to 'java weblogic.jspc filename.jsp' and I trying to get
>the
>java file
>so that I can verify that the changes I've made to a copy of the file
>are
>doing
>what I think 'it' should do..
>
>well something is wrong on this machine, I'm getting an error
> Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/jsp
>
>I've used the verbose mode to track the execution, and it (what ever
>it is
>at this point)
>has loaded classes from the rt set of jars.
>
> Am I missing something fundamental? what should I be looking for?
>
>
>
-
Want to know abt jsp-precompile option
Hi,
if i passed jsp-precompile=true then what will happen?
what situation we have to send that parameter...
what is the exact functionality of jsp-precompile option....
In our application we are having 200 jsp files.
in our application, once the user logs then 7 frames are loaded and a jsp page is called for each frame...
sometime i am getting jasper exception in some frame.... so should i pass this parameter to all jsp's..
Reply please
Thanks
SaravananI don't think precompile is an option that you pass to a JSP. It's a container option, and how it's supported depends on the container AFAIk. I don't think it's in the JSP spec, but I could be wrong.
Basically what it does it turns the .jsp files into .java files (and possibly .java into .class files too) at the point where the app is deployed or started or something. This is in contrast to doing the compilation page by page when a given .jsp is requested.
What you gain is smoother first-time loading of the pages at the cost of one-time startup delay. -
Fail over is not happening in Weblogic JSP Server
Hi..
We have 6 Weblogic instances running as application server (EJB) and 4 Weblogic
instances running as web server (JSP). We have configured one cluster for EJB
servers and one cluster for JSP servers. In front-end we are using four Apache
servers to proxy the request to Weblogic JSP cluster. In my httpd.conf file I
have configured with the Weblogic cluster. I can see the requests are going in
all the servers and believe the cluster is working fine in terms of load balancing
(round-robin). The clients are accessing the servers using CSS (Cisco Load Balancer).
But when we test the fail-over in the cluster, we are facing problems. Let me
explain the scenarios of the fail-over test:
1. The load was generated by the Load Generator
2. When the load is there, we shut down one Apache server, even though there was
some failed transaction, immedialty the servers become stable. So fail-over is
happening in this stage.
3. When I shutdown one EJB instance, again after some failed transactions, the
transactions become stable
4. But, when I shutdown one JSP instance, immediately the transaction failed and
it is not able to fail over to another JSP server and the number of failed transactions
increased.
So I guess, there is some problem in the proxy plug-in configuration, so that
when I shutdown one JSP server, still the requests are being send to the JSP server
by the Apache proxy plug-in.
I have read various queries posted in the News Groups and found some information
about configuring session and cookie information in the Weblogic.xml file. Also
I’m not sure what are all the configurations needs to be done in the Weblogic.xml
and httpd.conf file. Kindly help me to resolve the problem. I would appreciate
your response.
===============================================================
My httpd.conf file plug-in configuration:
###WebLogic Proxy Directives. If proxying to a WebLogic Cluster see WebLogic
Documentation.
<IfModule mod_weblogic.c>
WebLogicCluster X.X.X.X1:7001,X.X.X.X2:7001,X.X.X.X3:7001,X.X.X.X4:7001
MatchExpression *.jsp
</IfModule>
<Location /apollo>
SetHandler weblogic-handler
DynamicServerList ON
HungServerRecoverSecs 600
ConnectTimeoutSecs 40
ConnectRetrySecs 2
</Location>
==============================================================
Thanks in advance,
Siva.Hi,
I can see that bug 13703600 is already got fixed in 12.1.2 but still you same problem please raise ticket with oracle support.
Regrds,
Kal -
Object passing to weblogic JSP tags
Hello everyone
I was wondering if I can pass a java object to a weblogic jsp tag
for example if I select a content object with id "newsItem"
<cm:selectbyid contenthome="com.beasys.commerce.axiom.document.Document"
contentid="<%= contentId %>"
id="newsItem" />
can I pass newsItem as a variable to the next tag
i.e. instead of writing it
<cm:printdoc id="newsItem" />
I write it
<cm:printdoc Id="<%= newsItem %>" />
This results in an compiler error if the object is passed to Id that is
waiting for a content instance, while if it is passed to contentid (as in
the first
script) then it works fine, as this is waiting for a string.
Is it possible to pass an object to the "id" in the jsp script, and if not,
is there a work around it that enables the content selection logic to be
seperated from the display.
Thank you
May
Oh...i put quotes around the values and that fixed it.
<%@ page language="java" session="false" %>
Happy Holidays,
Brian
"Brian Williams" <[email protected]> wrote in message
news:[email protected]..
> Hello,
>
> I have a JSP that does something strange: When I look
> at it under Explorer it looks fine but under Netscape
> it has this at the top of the page:
>
> <%@ page language=java session=false %>
>
> Actually, with Explorer you can see it in the view
> source. What's up with Weblogic? It seems that
> it failed to parse this JSP tag.
>
> Thanks,
> Brian
>
>
>
Maybe you are looking for
-
Hi guys, I'm new of Java Fx technology, that I find fantastic! What I want know is to embed in my java fx application a rich text editor (like a smart word processor). What I need is this: 1) open a document format in text editor 2) perform formattin
-
Several reconciliation accounts possible for one customer/vendor
Dear experts, I am starting with FI-CO module. I have a question regarding G/L reconciliation accounts -Are they only linked to subledgers AP-AR in the customers/vendors master data? I mean for one customer i only have 1 reconciliation account (rece
-
Hi, I have done BDC recording for CLM1 tcode. Later In costs Tab of CLM1 Tcode, There is a ALV.As ALV can not be Inserted or Updated with BDC recording. I have directly moved into table CKIS. I am gettingDUMP at INSERT command,When ever I run the Tco
-
What's the fix for this error: Can't create the file "feed.xml."
I try to publish my site from iWeb but I get an error which is below. Publish Error Can't create the file "feed.xml." The disk may be damaged or full, or you may not have sufficient access privileges. Anyone know the fix?
-
Using Aperture 3 and printing photos, is it best to export the photo CMYK as a TIFF?
Using Aperture 3 and CMYK when printing photos, is it best to export as a TIFF and if so as bit 8 or bit 16? Thanks!