Jsf-api and jsf-ri logging

The source code is available for the jsf-api and the jsf-ri libraries. Reading through some of it, I noticed that commons-logging was being used such as log.warn and log.debug.
How can we "turn it on"? It looks as though log.warn is already written to the SunAppServer8 log file within JSC. I changed all of the app server log levels to FINE via the server's property sheet, but it had no effect. Thanks.
Message was edited by:
jeff.daily

See if this helps:
http://wiki.java.net/bin/view/Projects/SunJSFImplFaq#TurnOnLogging
Sandip

Similar Messages

Difference between JSF API and RI and EL API and EL RI?

Im just looking into using facelets and in the dependency list I see this:
JavaServer Faces RI
The reference implementations of JSF 1.1 and JSF 1.2 are available for use with your
application
JavaServer Faces API
JSF 1.2 API that works with the new EL specification. (Optionally, MyFaces Core API
could be used.)
EL API - The stand-alone EL utilized by both JSP and JSF.
EL RI - The reference implementation that is used by Facelets for handling EL.
This isnt a question about facelets but more about what the differences are between the JSF API and RI versions and likewise the EL versions.
Its much appreciated if anyone can explain this for me.
Jon
Edited by: JonJackson on Jul 27, 2009 2:29 PM

Oh, your topic title contradicts (difference between API and RI) with the actual question in the topicstart (difference between the versions).
If the topic title represents the actual question: the API is the application programming interface, which is just an abstract specification. The RI is the reference implementation, which is the vendor's (in this case Sun) own concrete implementation of the abstract specification. In fact everyone can build an own implementation of the API which might be or not be better than the RI.

Problem in using Tomahawk 1.1.3 jar with jsf-api.jar & jsf-impl.jar

Hi All,
i am facing the problem while using <t:panelTabbedPane> in jsp.APplication has jsf-api.jar and jsf-impl.jar and Tomahawk 1.1.3 jar files in lib folder. This is a Portal Application.While deplyoing on portal server, i am getting following exception
Nested Exception is java.lang.NoClassDefFoundError: javax/servlet/jsp/el/ELException
at org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.<clinit>(MyfacesConfig.java:80).
if any faces problem previously, please help me out in debugging this issue

Please don't resurrect old topics. Start a new topic for each stand alone question. If necessary put links to the topics you found with search/google.
Back to the actual problem:java.lang.NoClassDefFoundError: javax/servlet/jsp/el/ELException The given class is missing in the classpath during runtime. Add that class, or at least the JAR file with that class, to the classpath of the runtime environment, then you're fine.

JSF 2 and Primefaces with WLS 11gR1(10.3.6) problem

Hi all,
I would like to create a web application in OEPE, which uses JSF 2 and Primefaces 3.2 and then deploy & develop onto WLS.
I added the primefaces jar to WEB-INF/lib.
See my publishing stacktrace below.
(I tried using the Shared JSF libraries and including jsf-api and impl in WEB-INF/lib, but neither of these options worked.)
Do you have any ideas what I am doing wrong? Thanks,
András Liter
<2012.04.14. 21:32:21 CEST> <Error> <javax.enterprise.resource.webcontainer.jsf.config> <BEA-000000> <Unexpected exception when attempting to tear down the Mojarra runtime
java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory
     at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:804)
     at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:306)
     at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:104)
     at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:309)
     at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.EventsManager.notifyContextDestroyedEvent(EventsManager.java:200)
     at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:3225)
     at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:247)
     at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:461)
     at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1545)
     at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:509)
     at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:387)
     at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
     at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
     at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
     at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
     at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:547)
     at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
     at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:192)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:184)
     at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:677)
     at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:63)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:149)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
<2012.04.14. 21:32:21 CEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1334431938841' for task '32'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1520)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     Truncated. see log file for complete stacktrace
Caused By: java.io.FileNotFoundException: \Oracle\Middleware\Oracle_OSB1\soa\connectors\FileAdapter.rar!fileAdapter.jar (The system cannot find the file specified)
     at java.util.zip.ZipFile.open(Native Method)
     at java.util.zip.ZipFile.<init>(ZipFile.java:127)
     at java.util.jar.JarFile.<init>(JarFile.java:135)
     at java.util.jar.JarFile.<init>(JarFile.java:72)
     at com.sun.faces.facelets.util.Classpath.getAlternativeJarFile(Classpath.java:252)
     Truncated. see log file for complete stacktrace

Hi --
I just tried using OEPE 11.1.1.8.0 against a WLS 10.3.6.0 install to build and deploy a JSF 2.0 application and it worked successfully.
The project is here if you want to take a look:
http://dl.dropbox.com/u/15657493/oepe-test-jsf2.zip
The only minor gotcha I found was that I needed to reorder the libraries on the project so that the Shared-Library[jsf] was higher than the WebLogic System Library - this then let me use the JSF 2.0 programming API successfully instead of the 1.2 version that is included in the WLS System Library.
Here's a couple of screen shots of the facet and project as well as the overall development environment:
http://dl.dropbox.com/u/15657493/oepe-jsf-facet.png
http://dl.dropbox.com/u/15657493/oepe-project-libs.png
http://dl.dropbox.com/u/15657493/oepe.png
For that zip file error, one thing perhaps is to Check your CLASSPATH setting to see if it has an entry for that FileAdapter.rar. I don't know why it's causing that problem but if it's in the CLASSPATH try removing it and then starting the server.

Why exactly is a JSF IMP and a API, what is the difference?

Why exactly is a JSF IMP and a API, what is the difference?
I understand that JavaServer Faces technology is a framework for building user interfaces for web applications with a set of APIs for UI components and a custom tag library for expressing a JavaServer Faces interface within a JSP page.
But, why is there a jsf-impl.jar and a jsf-api.jar?
A clarification would be appreciated.
Thanks,

CowKing: Thank you.
In a discussion, when a developer refers to RI, they mean the jsf-api.jar only?
I don't need the jsf-impl.jar in my compile class path nor in my SJSAS 8.2 domain library directory either?
Thanks,
--Todd

Tomcat 6.0.9 and jsf 1.2 and jstl 1.2 using *.tag file error

I using :tomcat 6.0.9 and jsf 1.2 and jstl 1.2
My web.xml is at version 2.5 and I am using a custom tag (with the .tag extension). I am trying to use the http://java.sun.com/jsf/html library and values from my attribute. I'm new to this so I figure I must just me missing something.
I am run http://192.168.1.1/test.jsf laster,view:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP:
Stacktrace:
     org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:85)
     org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330)
     org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:415)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:308)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
     org.apache.jasper.servlet.JspServletWrapper.loadTagFile(JspServletWrapper.java:212)
     org.apache.jasper.compiler.TagFileProcessor.loadTagFile(TagFileProcessor.java:576)
     org.apache.jasper.compiler.TagFileProcessor.access$000(TagFileProcessor.java:50)
     org.apache.jasper.compiler.TagFileProcessor$TagFileLoaderVisitor.visit(TagFileProcessor.java:627)
     org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
     org.apache.jasper.compiler.TagFileProcessor$TagFileLoaderVisitor.visit(TagFileProcessor.java:631)
     org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
     org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
     org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.TagFileProcessor.loadTagFiles(TagFileProcessor.java:645)
     org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:190)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:308)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
     com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:414)
     com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:455)
     com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:139)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:108)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:266)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:159)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
note The full stack trace of the root cause is available in the Apache Tomcat/6.0.9 logs.
if go to /WEB-INF/tags/test.tag ,delete line: <h:outputText id="test" value="hello!" />
run http://192.168.1.1/test.jsf is OK!(no error),So I guess error for "<h:outputText id="test" value="hello!" />" line ,why in test.tag file do can't use the "http://java.sun.com/jsf/html " library,please help me.......
Here is file WEB-INF/web.xml content:
<?xml version="1.0" encoding="ISO-8859-1"?>

<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd"
version="2.5">
<display-name>Welcome to Tomcat</display-name>
<description>
Welcome to Tomcat
</description>

<servlet>
     <servlet-name>Faces Servlet</servlet-name>
     <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
     <load-on-startup> 1 </load-on-startup>
</servlet>

<servlet-mapping>
     <servlet-name>Faces Servlet</servlet-name>
     <url-pattern>*.jsf</url-pattern>
</servlet-mapping>
</web-app>
Here is file /test.jsp code:
<%@ page contentType="text/html;charset=UTF-8" %>
<%@ taglib prefix="tags" tagdir="/WEB-INF/tags" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<f:view>
<html>
<head>
<title>test</title>
</head>
<body>

<h:outputText id="myinfo" value="test success" />
<tags:test/>

</body>
</html>
</f:view>
Here is file /WEB-INF/tags/test.tag code:
<%@tag pageEncoding="UTF-8"%>
<%@taglib prefix="f" uri="http://java.sun.com/jsf/core"%>
<%@taglib prefix="h" uri="http://java.sun.com/jsf/html"%>
<h:outputText id="test" value="hello!" />
Thanks for any help.

Don't know if it's important, but there is no schema avaiable at: http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd
I found the right one at: http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
/perty
Message was edited by:
perajonsson

JSF datatable - any difference with JSF 1.1 and JSF 1.2

Hi All,
In my project there are lot of Datatables, which retrieve data from the database and display it to the user. For each datatable, the columns are not fixed. I want to create some kind of component that can be reusable.
It is basically a JSF portlet. Now i have to use RAD 6. RAD 6 supports only JSF1.1. I have to migrate this to RAD7 in the near future. Are there any differences between the Datatable in JSF 1.1 and JSF 1.2?
I had this approach in mind.
a) Create the datatable programmatically and put the contents to panelgrid. This way the jsp code will be minimized. Is it a good option.? Are the APIs same in both the versions?
b) Is it possible to create a custom datatable which can take some key as input. Then based on the key the datatable can be populated with as many columns as desired.
Please let me know if there are any other good options.
~Anitha.

Hi guys,
my code goes like this..
for (int j = 0; j < size; j++) {
               UIColumn column = new UIColumn();
               dataTable.getChildren().add(column);
               HtmlOutputText header = new HtmlOutputText();
               header.setValue(periodHeader[j]);
               column.setHeader(header);
               HtmlOutputText output = new HtmlOutputText();
               output.setValue(new Double(periodLiability[j]));
               ValueBinding vb1 = FacesContext.getCurrentInstance()
                         .getApplication().createValueBinding(
                                   ("#{liability.periodLiability["+j+"]}"));
               output.setValueBinding("value", vb1);
               column.getChildren().add(output);
this code gives me the number of headers i need. But, it doesnt render the columns. I have an array of Double (periodLiability) which stores few values of Double type. I want to show thesee values inthe dataTable Column.
Please help me..

JSF Datatable - Any difference with JSF1.1 and JSF 1.2

In my project there are lot of Datatables, which retrieve data from the database and display it to the user. For each datatable, the columns are not fixed. I want to create some kind of component that can be reusable.
It is basically a JSF portlet. Now i have to use RAD 6. RAD 6 supports only JSF1.1. I have to migrate this to RAD7 in the near future. Are there any differences between the Datatable in JSF 1.1 and JSF 1.2?
I had this approach in mind.
a) Create the datatable programmatically and put the contents to panelgrid. This way the jsp code will be minimized. Is it a good option.? Are the APIs same in both the versions?
b) Is it possible to create a custom datatable which can take some key as input. Then based on the key the datatable can be populated with as many columns as desired.
Please let me know if there are any other good options.
~Anitha.

Doublepost. Please don't use the back button to edit a topic, you're going to repost it. Use the edit button. Continue here: [http://forums.sun.com/thread.jspa?threadID=5336694].

J2EE, JSTL and JSF questions

I am trying to learn J2EE/JSTL/JSF and have quite a few general questions. Any help on any of these is appreciated.
1) Is there a way, just by using J2EE/Java to "manipulate" an XML file. Not just parse and read it's data but actually add nodes to the file?
2) I've been reading quite a bit on JSTL and JSF recently. Is JSF supposed to be an alternative to Struts and JSTL an alternative to scriptlet coding?
3) I am also working on creating a message board but throwing around a couple of ways to implement it. Either (a) using a database to store posts and a JSP interface or (b) using an XML document to store postings. Which of these two seem best or is there a better option?
4) Is there an easy way to call Php from a Java program? I need to invoke a php program when a user clicks on a link on a JSP page I have.

1) The SDK provides JAXP (Java API for XML Processing) in javax.xml package.
2) I wouldn't call it 'alternative'.
3) Your choice. I'd to use a RDBMS. Less overhead, better suited, (much) more functions and better performance.
4) If that program is available on the web, then just invoke a HTTP request. If not, I'd rather to rewrite it to Java.

Jsf api to convert utf-8 to original text

Hi guys,
For instance, a user enter 路 in a text field then I convert this chinese character to utf-8 using javascript:encodeURIComponent to %E8%B7%AF and pass it as a parameter to the next page where the url will look like example :
http://www.google.com/search?q=%E8%B7%AF
so when I get %E8%B7%AF in backing bean, how should I convert back to 路 in order to pass to database to search? any jsf api able to convert it?
Thanks & regards,
Plant more tree
Use emission free car

help....pls help...

@Singleton instanciated twice when from Struts2 and JSF (same webapp)

Hello,
in the process of migration from a struts2 application to JSF 2.0 I've annotated as @javax.ejb.Singleton a former stateless session bean. It works ok but if I get that EJB from JNDI (struts2 actions) I get a different object than when referencing the EJB from a JSF facelet (I have also annotated the Bean as @ManagedBean) It works but is a different object. is that the supposed behaviour?
(I've also tried with Weld (cdi) using @Named and not @ManagerBean... it is even works. For some reason, @Named creates the object but gives it no EJB services (no @PersistenceContext injection for example)
thanks for any directions,
Ignacio

Steve,
I am using JSF2.0 and getting javax.el.ExpressionFactory NoClassDefFound issues.
OEPE Helios
Weblogic 10.3.3
I have an EAR containing one WAR.
WEB-INF/lib
el-api-2.2jar
el-imp-2.2.jar
jsf-api.jar (2.1.1)
jsf.impl.jar (2.1.1)
jstl.jar (1.1.0-D13)
web.xml has
     <context-param>
          <param-name>com.sun.faces.expressionFactory</param-name>
          <param-value>com.sun.el.ExpressionFactoryImpl</param-value>
     </context-param>
EAR has
weblogic-application.xml with
<wls:prefer-application-packages>
<wls:package-name>org.eclipse.persistence.*</wls:package-name>
<wls:package-name>javax.faces.*</wls:package-name>
<wls:package-name>com.sun.faces.*</wls:package-name>
     <wls:package-name>com.sun.el.*</wls:package-name>
     <wls:package-name>javax.el.*</wls:package-name>
</wls:prefer-application-packages>
I see by your post that JSF2.0 support can be solved by either deploying a shared-library or using the weblogic.Deployer utility. Unfortunately, we don't have access to change the Weblogic instance in any way. I was hoping that using the prefer-application-packages would be sufficient to use alternative classes to Weblogic's but I have not been able to get it to work for the javax.el classes. I have tried not including javax.el and the app deploys but then accessing a page produces a javax.el.ELResolver no method found for invoke. Invoke being a newer method defined in el-api-2.2.jar. If I was able to convince them to add some shared libs, what are all the jars that would be required to make this work?
Any suggestions would be greatly appreciated.
Thanks
John

Oc4j 9.0.4/10g R1 and JSF

Hi,
I'm having serious problems with the OC4J container 9.0.4 and JSF. I have tried several sample applications in addition to the one that I have created myself, but none of them will work in the 9.0.4 release of OC4J, even though they all work in R3 EA release, as well as in tomcat 4.x.
In order for oc4j to compile jsp, I have added the following to server.xml:
<java-compiler name="javac" in-process="false" encoding="ISO8859_1" bindir="c:\APPS\Java\j2sdk1.4.2_09\bin" extdirs="c:\APPS\Java\j2sdk1.4.2_09\lib\ext" />
After doing this the example jsp files that comes with oc4j works.
However, when trying to access my own application I get the following errors in global-application.log:
05/10/04 10:22:03 web-0.1: jsp: init
05/10/04 10:22:03 web-0.1: SpringContextServlet: init
05/10/04 10:22:03 web-0.1: Loading Spring root WebApplicationContext
05/10/04 10:22:03 web-0.1: Error initializing servlet
java.lang.IllegalStateException: No Factories configured for this Application - typically this is because a context listener is not setup in your web.xml.
A typical config looks like this;
<listener>
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
</listener>
     at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:84)
     at javax.faces.webapp.FacesServlet.init(FacesServlet.java:73)
     at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2094)
     at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4523)
     at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4617)
     at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:765)
     at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:497)
     at com.evermind.server.Application.getHttpApplication(Application.java:886)
     at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:688)
     at com.evermind.server.http.HttpSite.getApplication(HttpSite.java:420)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:422)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Unknown Source)
05/10/04 10:22:03 web-0.1: Error preloading servlet
javax.servlet.ServletException: Error initializing servlet
     at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4574)
     at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4617)
     at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:765)
     at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:497)
     at com.evermind.server.Application.getHttpApplication(Application.java:886)
     at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:688)
     at com.evermind.server.http.HttpSite.getApplication(HttpSite.java:420)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:422)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Unknown Source)
I found an advice to not load the servlets on startup, but this does not help.
Does anyone know what might be wrong here? Is there a bug in 9.0.4 since everything works fine in the latest release?

This should not really work -- there is NO JMX support in 9.0.3.
In addition to providing the JMX MBeanServer runtime and JSR77 objects, we needed to also instrument a bunch of our runtime classes so they can work with JMX. Copying over the JMX libs and the console libs won't really get you what you need.
The earliest you may see some form of JMX is 9.0.4 -- and this is a completely unsupported (and incomplete and in fact hidden .... ) feature in that release.
Our first official release which will provide visible JMX support is 10.0.3.
Copying over JAR files like this from different versions is not a supported operation. Interesting from a learning perspective for sure ;-) -- but certainly something that support will baulk at if you ever call them about it.
cheers
-steve-

SJSAS v9.0 : jsf-api 1.2 in javaee.jar causes trouble for jsf 1.1 apps

In Sun Java System Application Server v9.0 (or 9.1), jsf-api v1.2 is embeded in javaee.jar. This causes a lot of trouble when deploy web applications written with jsf v1.1. Is there a way to avoid this without modifying web applications to migrate to jsf v1.2? I got strong reasons/requirements not to migrating source to comply jsf v1.2.
In JSF v1.2 spec, it states "Faces 1.2 is backwards compatible with Faces 1.1. This means that a web-application that was developed to run with Faces 1.1 won�t require any modification when run with Faces 1.2 except in the cases described in the following section." Does anybody have the experience running v1.1 applications on top of SJSAS v9+ (or JSF v1.2 RI)? What are the best practices?
Thanks

It took me quite some time to diving in the codes as my situation is not simple - we have tens of custom coded JSF components/renders written in JSF v1.1 and suddently found everything not working on SJSAS v9. It turns out that I have to remove EVERY jar files related to JSF v1.1 or dependant by JSF v1.1, then it seems working but I couldn't be too sure untill the testing cycle finishes.
Thanks for the hint BalusC - it helps.

Apache Jetspeed-2 Portal and JSF

I'm in the process of trying to get a JSF1.1, Spring1.2.5 & Hibernate 2.0 based portlet working with the Apache Jetspeed-2 (2.0-M3) portal container.
The example JSF demo applications supplied with the portal container work fine, however, having configured the various xml file as per the example I get the following error msg.
I would be grateful if anyone who has experience of Jetspeed2 and JSF could shed any light on this.
Unfortunately I cannot supply the various xml or log files but I get the following message in the portlet when displayed in the browser.
"The requested resource (/container) is not available"

Hello,
Just put the portlet war file into "webapps/jetspeed/WEB-INF/deploy"

Log4j and jsf

I added log4j in my application. It is working and I can see my log.debug statements in the console. The problem is that I can see more than I want. My application uses jsf and Tomcat and I see many jsf debugs and I do not know what to change in my log4j.properties so as not to view them. My log4j.properties is the following:
log4j.rootLogger=debugLog, stdout
# CONSOLE appender
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{HH:mm:ss} %-5p %m%n
log4j.appender.debugLog=org.apache.log4j.DailyRollingFileAppender
log4j.appender.debugLog.Threshold=debug
log4j.appender.debugLog.layout=org.apache.log4j.PatternLayout
log4j.category.com.corejsf = debugLog
I tried to add something like the following
log4j.category.com.sun.faces = WARN
log4j.additivity.com.sun.faces=falsebut nothing changed.Any suggestions??

This is a log4j properties file problem. I'm not used to using the .properties file notation. I'm used to the XML notation for log4j.
Here's how I'd do it in XML:
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/'>
        
        <appender name="Appender" class="org.apache.log4j.ConsoleAppender">
                <param name="Append" value="true"/>
                <layout class="org.apache.log4j.PatternLayout">
                        <param name="ConversionPattern" value="%d{HH:mm:ss} %-5p %m%n"/>
                </layout>
        </appender>
        <logger name="my.java.package" additivity="false">
                <level value="debug" />
                <appender-ref ref="Appender" />
        </logger>
        <logger name="another.package.for.debug.level" additivity="false">
                <level value="debug" />
                <appender-ref ref="Appender" />
        </logger>
        
        
        <root>
           <priority value ="debug" />
           <appender-ref ref="Appender" />
        </root>
</log4j:configuration>This example will print to console only. If you want to print to a file instead, use the following lines (replaces the appender tags from the above example).
        <appender name="Appender" class="org.apache.log4j.DailyRollingFileAppender">
                <param name="File" value="filePath/FileName.log"/>
                <param name="DatePattern" value="'.'yyy-MM-dd"/>
                <param name="Append" value="true"/>
                <layout class="org.apache.log4j.PatternLayout">
                        <param name="ConversionPattern" value="%d{HH:mm:ss} %-5p %m%n"/>
                </layout>
        </appender>I don't know how you'd get both the console and the file appender working at the same time.
If you want further advice, or If you want advice on the .properties method of doing things, I suggest finding a log4j forum. The people there will undoubtedly have more experience and knowledge than us JSF nerds. =)
I assure you though, JSF is compatible with log4j. The log4j properties file just needs to be set up properly (more challenging than it should be, if you ask me).
CowKing

Jsf-api and jsf-ri logging

Similar Messages

Maybe you are looking for