JSF error

I am trying to access a jsf page using
http://localhost:9090/appname
but i am getting the error "The requested resource (/TPDashboard/) is not available."
I have tried out all the answers that have been given to this earlier but am still not able to solve the problem. Can somebody help me?

I figured out the problem was with my web.xml which had an entry like this:
<servlet-mapping>
<servlet-name>SourceCodeServlet</servlet-name>
<url-pattern>*.source</url-pattern>
</servlet-mapping>
After removing the above entry from web.xml i was able to run the app. I am not sure what exactly the problem was.

Similar Messages

JSF error messages

has anybody successful using JSF error messages. Im using JSF portlet framework to display error msgs using h:messages tag. Im able to display validation/conversion errors with h:message tag.
Im unable to display general messages that are result of an application exception. Has anybody ever done that?
Help would be appreciated.
Thanks
-Sri

If I understand you correctly ...
FacesContext context = FacesContext.getCurrentInstance();
FacesMessage message = new FacesMessage("New Message");
context.addMessage(null, message);

A new approach to JSF error handling?

Hi.
I would like to run an idea by the community to check that I am not being crazy in doing this stuff. I would appreciate any comments, criticism or ideas.
I was thinking about JSF's error processing mechanism, specifically about how label text gets associated with an input field. So, I am talking about this kind of stuff:
<h:outputLabel for="firstName" value='#{msgs["applicant.search.firstName"]}: ' />
<h:inputText id="firstName" value='#{applicantDetailsBackingBean.firstName}' required=�true�/>If the value is not entered into the input field, we will get an error message saying:
�First Name�: is required.
So HtmlMessageRenderer has replaced the field id in the FacesMessage with the label text by using the association set up with the 'for' attribute on the label. All of this message "decoration" work happens in the RENDER phase in a centralized location. I see a couple of weaknesses in this approach
1) It is too late for resolving label text data if the label is inside a data table
2) JSF establishes associations between label text and the input fields by using the label components to point to their input fields. Although this seems more natural, it limits label text sources to just the label components present on the current page (or whatever is nested under them), which makes it impossible to associate input field messages with label text that does not exist on the page in its entirety.
Let's look at a couple examples, both of which I ran into in my application:
1) Consider a situation in which we have a dataTable where every row consists of a student name and an input field for entering their assignment mark. The validation on the input field will be restricted to valid letter grades only. If the user enters an invalid grade, we want them to see an error message of the form: +�The mark entered for <student name> is invalid�.+ Since <student name> is dependent on the row in which the error occurred, this error message is not possible to generate with bare JSF functionality.
2) Another situation that gets us in trouble is when the label text we want in our error message is not on the page (or not in it's entirety). For example, your page could be split up into multiple parts with those parts having input fields with the same name. We would want the error message to include the page part as well as the field name. This is not easily achieved with the bare JSF functionality.
So to generalize, any situation where a label component with a static value throughout the lifecycle is not available will cause difficulty.
Please correct me if I am wrong on any of these points.
Since in my app I had a lot of complicated pages to deal with, I solved my difficulties by writing a very simple framework that I called Message Decorator Framework (MDF). It enabled me to easily construct much more detailed error messages than what the standard JSF approach seems to allows for. MDF provides a mechanism to specify the label text to be applied to a validation or a conversion message by either a literal, an el expression or via an id of another ValueHolder and all of these work in data tables.
The idea is a s such, and this is what i would like your opinion on:
MDF provides more flexible message decoration by adapting the opposite approach to the one used by the JSF:
1) Message decoration is decentralized. MDF wraps converters and validators on individual input fields and performs message text replacement right on the spot in the PROCESS_VALIDATIONS phase, when all of the pertinent data for resolving the label text is still available.(i.e the components in data tables would still have the correct values for the current row being validated)
2) The label text to be used is specified by the input field, not the label. This allows the developer to reference any text value, instead of tying them to a specific label component.
Pictures are better than words, so here is an architectural diagram:
http://www.imagehosting.com/out.php/i1259440_ArchitectureDiagram.png
The framework consists of two main classes, ConverterMessageDecorator and ValidatorMessageDecorator. I will just talk about the converter part, b/c the validator part is very similar but wraps a list of validators instead of one converter.
So ConverterMessageDecorator is a JSF converter. Its purpose is to wrap the converter that is going to do the actual conversion work and decorate the FacesMessage inside ConverterException if one was thrown.
The converter to wrap can be either determined automatically based on the type of the value reference of the input field or specified explicitly. This converter decorates the message by replacing all instances of the input field�s id with the resolved label text. The power of this approach is that not only do you get a much more flexible way to specify what the label text is (either fieldLabel or fieldLabelComponent attributes), but now data tables are no longer a problem.
Here are some usage examples:
<h:inputText value='#{section33SetupBackingBean.contribution.sampleGatePct}'>
   <md:decorateConverterMessage fieldLabel= '#{msgs["section.34.setup.contribution.initial.sampling.gate.max.size"]}' />
</h:inputText>
�etc�
<h:inputText value='#{section33SetupBackingBean.payment.sampleGatePct}'>
   <md:decorateConverterMessage fieldLabel= '#{msgs["section.34.setup.payment.initial.sampling.gate.max.size"]}' />
</h:inputText>The two input fields have exactly the same labels on the screen (they are in two different parts of the page), so if we used their respective labels, the error messages would look the same for these two input fields.
More complicated example:
<h:dataTable value="#{paymentCalcBackingBean.currentPaymentPercentages}" var="currentPercentage" >
<h:column>
<ops:refDataDescription id="provinceLabelTextId" refDataType="provinceStateType"
            code="${currentPercentage.programProvince.provinceStateTypeCode}" />
</h:column>
<h:column>
<h:inputText value="${currentPercentage.federalPercentage}">
<md:decorateConverterMessage fieldLabelComponent="provinceLabelTextId" valueRequired="true" >
   <f:converter converterId="ops.PercentageConverter" />
</md:decorateConverterMessage>
<md:decorateValidatorMessage fieldLabelComponent="provinceLabelTextId" >
   <f:validator validatorId="ops.PercentageValidator" />
</md:decorateValidatorMessage>
</h:column>
�etc�
</h:dataTable>This would produce errors shown in this screenshot: http://www.imagehosting.com/out.php/i1259418_Example3.png
Here is another example that shows off what you can do by referencing other ValueHolders on the page.
The code is exactly the same as the snippet shown above, but the inputText component is referencing a text box, so the label text is going to be whatever the user types into the text box:
http://www.imagehosting.com/out.php/i1259467_Example4.png
Does this approach seem reasonable to people, or am I reinventing the wheel? Please let me know.
Val

Try restarting the DTR application and see if the problem persists.

JSF error handling when the bean is not correctly loaded

Hi,
I am doing some error handling in JSF and I want to do it in an elegant way. I have the following scenario for error handling.
When the bean is initialized I load the bean with values from DAO which give SQL Exceptions.
Since the bean is not loaded I properly I have to send the user to an error page showing the error message why I am sending the user to this page.
I can do it by [ FacesContext.getCurrentInstance.redirect("/error.jsf") ] doing so I will loose all the FacesMessages that are added by the exceptions.
Instead I want to use the [ FacesContext.getCurrentInstance.dispatch("url") ] which will allow the transfer of the user but I get the following
16:59:39,341 WARN [lifecycle] executePhase(RESTORE_VIEW 1,com.sun.faces.context.FacesContextImpl@8537f9) threw exception
java.lang.ClassCastException: javax.faces.component.UIViewRoot
and the method that I am calling is
public static void programErrorEnd() {
logger.info("in the prgmErrorEnd mehod");
//intializing the contex object
FacesContext ctx = FacesContext.getCurrentInstance();
try {
//ready to dispatch the url.
//ctx.getExternalContext().redirect("app/error/prgmerror.jsf");
ctx.getExternalContext().dispatch("error/prgmerror.jsf");
} catch (IOException e) {
//TODO what to do when there is an error at this stage.
finally {
ctx.responseComplete();
}Thanks and Regarding
Edited by: sgatl2 on Aug 28, 2008 2:32 PM
Edited by: sgatl2 on Aug 28, 2008 2:45 PM

Just let it throw the exception and define an error-page entry in the web.xml which catches the specified exception (or a superclass of it or a HTTP status code) and displays the error.jsf page accordingly.

JSF error handling

jsf impl version 1.1
When loading a jsf with (http GET), I am sending a get-parameter (ID=123). When resolving this in the domain model, this might cause an exception which needs to be handled. How do I correctly redirect to an error page in this case?
Regards
tnilsen

Depends on business requirements. You can define an error-page for specified exception (sub)classes in web.xml. But you can also invoke HttpServletResponse#sendRedirect() to the desired page. Or simply use h:message / h:messages to display a message.

JSF: Error Message are not getting cleared

Hi,
I am facing some problem with error messages in JSF.
Here is what I am doing
1. User submits a form, server validates and sends back the error to the client error message added to Faces Context.
2. User checks the messages, changes the input and submits. assuming everything is correct now.
3. On server, it validates and writes data to response for download using the following code.
FacesContext faces = FacesContext.getCurrentInstance();
    HttpServletResponse response = (HttpServletResponse)faces.getExternalContext().getResponse();
    DownloadResponse.sendDownload( response, is, fileName );
    faces.responseComplete();
}4. It shows the download popup to download the file. The problem here is that error message are not getting cleared off. User can still see the error message on the screen.
It seems I am missing something in JSF req-response life cycle. Anyone please point out the mistake.

SudhirMongia wrote:
4. It shows the download popup to download the file. The problem here is that error message are not getting cleared off. User can still see the error message on the screen. Wrong. The problem is that the view is not rerendered, which makes sense because you are not sending view content to the browser but your file.
Your real question probably is: how do I cause a file download and still rerender the view afterwards to show the results? To that I myself do not have the answer unfortunately, but I have seen that question come by a few times already, so doing some searches in these forums may yield you an answer.

JSF error on Tomcat

Hi I am getting a strange error when I deploy the war file for JSF on tomcat as follows 2006-12-01 10:19:51 StandardContext[/manager]HTMLManager: start: Starting web application at '/campman'
2006-12-01 10:19:51 StandardContext[/campman]Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener
javax.faces.FacesException: com.sun.faces.lifecycle.LifecycleFactoryImpl
     at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:553)
     at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:411)
     at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:229)
     at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:702)
     at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:398)
     at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:328)
     at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4343)
     at org.apache.catalina.core.StandardHostDeployer.start(StandardHostDeployer.java:830)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:991)
     at org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1322)
     at org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:530)
     at org.apache.catalina.manager.HTMLManagerServlet.doGet(HTMLManagerServlet.java:104)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     at java.lang.Thread.run(Thread.java:534)
Caused by: javax.faces.FacesException: ApplicationFactory
     at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:540)
     at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:426)
     at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:229)
     at com.sun.faces.lifecycle.RestoreViewPhase.<init>(RestoreViewPhase.java:69)
     at com.sun.faces.lifecycle.LifecycleImpl.<init>(LifecycleImpl.java:53)
     at com.sun.faces.lifecycle.LifecycleFactoryImpl.<init>(LifecycleFactoryImpl.java:69)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at java.lang.Class.newInstance0(Class.java:308)
     at java.lang.Class.newInstance(Class.java:261)
     at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:551)
     ... 40 more
Caused by: java.lang.ClassNotFoundException: ApplicationFactory
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1340)
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189)
     at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:528)
     ... 52 more
2006-12-01 10:19:51 StandardContext[/manager]HTMLManager: list: Listing contexts for virtual host 'localhost'
2006-12-01 10:19:55 StandardContext[/manager]HTMLManager: start: Starting web application at '/campman'
2006-12-01 10:19:55 StandardContext[/campman]Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener
javax.faces.FacesException: com.sun.faces.lifecycle.LifecycleFactoryImpl
     at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:553)
     at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:411)
     at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:229)
     at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:702)
     at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:398)
     at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:328)
     at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4343)
     at org.apache.catalina.core.StandardHostDeployer.start(StandardHostDeployer.java:830)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:991)
     at org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1322)
     at org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:530)
     at org.apache.catalina.manager.HTMLManagerServlet.doGet(HTMLManagerServlet.java:104)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     at java.lang.Thread.run(Thread.java:534)
Caused by: javax.faces.FacesException: ApplicationFactory
     at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:540)
     at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:426)
     at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:229)
     at com.sun.faces.lifecycle.RestoreViewPhase.<init>(RestoreViewPhase.java:69)
     at com.sun.faces.lifecycle.LifecycleImpl.<init>(LifecycleImpl.java:53)
     at com.sun.faces.lifecycle.LifecycleFactoryImpl.<init>(LifecycleFactoryImpl.java:69)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at java.lang.Class.newInstance0(Class.java:308)
     at java.lang.Class.newInstance(Class.java:261)
     at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:551)
     ... 40 more
Caused by: java.lang.ClassNotFoundException: ApplicationFactory
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1340)
     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189)
     at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:528)
     ... 52 more
2006-12-01 10:19:55 StandardContext[/manager]HTMLManager: list: Listing contexts for virtual host 'localhost'

Sounds like a classloader problem. Do you have multiple jsf-api.jar files in your environment? Check the shared lib directories.
If you have the flexibility to use a different app server for development, GlassFish is the best JSF application server (IMO): https://glassfish.dev.java.net
Ken Paulsen
https://jsftemplating.dev.java.net

JSF errors in Weblogic

I'm deploying an application to WebLogic 9.2. The application was originally created for JBOSS and includes JSFs. I corrected some of the errors, but now when I try to access a webpage within the main jsf, I receive the following error:
The attribute does not support request time values. title
and it initiates a javax.faces.el.EvaluationException.
Also,
The display of the page contents are all over the play and the graphics are not being captured as well.
Can anyone help????

That will work only when all the supporting classes are placed inside the WEB-INF/lib directory only in form of Jar files.
If any one of the Class is being loaded from outside of the WEB-INF/lib jars then you will definately face this issue......
Example:
Suppose "com.sun.faces.el.impl.parser.* " classes are present in some other Jar file outside WEB-INF/lib but rest of the JSF Jars and Parser Jars are present inside the WEB-INF/lib directory ..in that case you will see this kind of issue Because the JSF config Parser will change according to the version of JSF and WLS also provides some supporting Jars in "modules/" or "server/lib" or in "common/lib" directories.
Thanks
Jay SenSharma
http://middlewaremagic.com/weblogic (Middleware Magic Is here)

Tiles + JSF error (Illegal to flush within a custom tag)

Hi,
When I try to use Tiles + JSF I have this error message :
javax.servlet.jsp.JspException: Illegal to flush within a custom tag
I am already using flush="false" on my tiles:insert tag.
This is my .jsp code :
<%@ taglib uri="/WEB-INF/struts-tiles.tld" prefix="tiles" %>
<tiles:insert beanName="cadastro_base" beanScope="request" flush="false">
<tiles:put name="form_body" type="string">
<f:view>
<h:form id="DisciplinaJsfBean" binding="#{DisciplinaJsfBean.form}" >
<h:inputText id="codigo" binding="#{DisciplinaJsfBean.itCodigo}"/>
</h:form>
</f:view>
</tiles:put>
</tiles:insert>
And this is the stack trace message :
exception
javax.servlet.ServletException: Illegal to flush within a custom tag
     org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:825)
     org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:758)
     org.apache.jsp.security.disciplina.cadastrarDisciplinas_jsp._jspService(cadastrarDisciplinas_jsp.java:99)
     org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
     com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
     com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
root cause
javax.servlet.jsp.JspException: Illegal to flush within a custom tag
     com.sun.faces.taglib.jsf_core.ViewTag.doEndTag(ViewTag.java:223)
     org.apache.jsp.security.disciplina.cadastrarDisciplinas_jsp._jspx_meth_f_view_0(cadastrarDisciplinas_jsp.java:205)
     org.apache.jsp.security.disciplina.cadastrarDisciplinas_jsp._jspx_meth_tiles_put_0(cadastrarDisciplinas_jsp.java:157)
     org.apache.jsp.security.disciplina.cadastrarDisciplinas_jsp._jspx_meth_tiles_insert_0(cadastrarDisciplinas_jsp.java:122)
     org.apache.jsp.security.disciplina.cadastrarDisciplinas_jsp._jspService(cadastrarDisciplinas_jsp.java:92)
     org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
     com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
     com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
Danilo.

What worked for me was to add a flush="false" to each of the <tiles:insert tags in my layout page.
I'm using this with JSF so it may be different for you:
... Layout stuff ...
   <tiles:insert attribute="body" flush="false" />
... More layout stuff, including more inserts with the flush="false" ....

Jsf error on Sun ONE v9

I have a small app developed with jsf 1.1 spec. When I deployed this on Sun ONE V9.0 , the following is the error.
Can't parse configuration file: jar:file:/C:/Sun/SDK/lib/jsf-impl.jar!/com/sun/faces/jsf-ri-runtime.xml: Error at line 3 column 14: jar:file:/C:/Sun/SDK/lib/jsf-impl.jar!/com/sun/faces/jsf-ri-runtime.xml<Line 3, Column 14>: XML-20149: (Error) Element 'faces-config' used but not declared.
     at com.sun.faces.config.ConfigureListener.parse(ConfigureListener.java:1587)
     at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:413)
     at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4236)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4760)
     at com.sun.enterprise.web.WebModule.start(WebModule.java:292)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:833)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:817)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:662)
     at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1479)
     at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1143)
     at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:171)
     at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:275)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:954)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:941)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:448)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:160)
     at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:296)
     at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:203)
     at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:285)
     at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:119)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:541)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:585)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:719)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:353)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:336)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:448)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
     at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:77)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:297)
     at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:133)
     at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:517)
     at java.lang.Thread.run(Thread.java:619)My faces-config.xml is v1.1. any ideas ?
Thanks

Hi Frank,
A couple of things to cross check.
1) Check the package structure of the war file. And cross check with the format given by SUN at
http://docs.sun.com/source/816-7150-10/dwdeploy.html#69868
2) Give more detail logs, and it is available at <deployed server instance>/logs/server.log.
3) Deploy the war file without running the verifier, and see what is the output.
If it wont help send the war file to me.
Thanks,
-Parsu

JSF error message - retain ?

HI all,
i am using jsf <h:messages />. its getting cleared, if i click a commandlink which shows a popup div. That popup div is rendered in a bean.
How to retain the error messages after getting the response.
Samething happened when i change a select option which processes in valueChangeListener. After Changes made in Select option (getting the response) how to retain the error message ?
Help me. Thanks in advance.
Srinivas.R

Thanks for ur replies.
i am using tomahawk div (t:div) to show a
small popup div when the user clicks a link. for
changing Serial id (for my application) which calls
backing bean for rendering & perform action
regarding.
Also when the Country select option changed, i
am populating relavant state list in another select
component, its internally calling backing bean. this
also clears the error messages.
How to retain the error messages without changing
this business.At this point you are pretty much outside the regular functionality provided by JSF. I still think the best approach will be to eliminate the reloading of the page. You could accomplish this via AJAX. There are a few libraries out there for using AJAX with JSF; ajax4jsf for sure and I think JBoss Seam, RichFaces, ICEFaces, Trinidad and I'm sure I missed some.

JSF error hangs entire application

Hi,
I'm building my first JSF application and an issue has arisen during testing which has us all stumped! Whenever an error occurs for a particular user, the entire application then falls over and all other users then see (different) error messages too.
I can easily replicate this issue by introducing a typo to a component's EL binding. The initial error message is
javax.servlet.jsp.JspException: Error getting property 'thisisatypo' from bean of type com.mypackage.MyBeanOther users then see a secondary error message: java.lang.IndexOutOfBoundsExceptionOther applications on the app server are not affected.
Is there a way to configure the application to better handle exceptions so that the application itself doesn't hang and other users can continue to use it? Would using an error page resolve this? (I'm currently catching exceptions in try...catch blocks and displaying the error messages using the <h:messages> component.)
Or is this an issue with the application server, which requires reconfiguration to fix it?
A previous thread mentions a similar issue, bit no-one has answered it: [http://forums.sun.com/thread.jspa?forumID=881&threadID=5049367|http://forums.sun.com/thread.jspa?forumID=881&threadID=5049367]
My environment:
JSF: v1.1_02 (Sun JSF RI)
IDE: JDeveloper 10.1.2.3.0
Java: 1.4.2_06
App Server: Oracle App Server 10g (OC4J 9.0.4.0.0)
(Upgrading to more recent versions of JSF or application server are not options at the moment - my organisation has already scheduled upgrades sometime within the next 12 months or so, but I cannot bring them forward!)

Hi BalusC, thanks for your response!
I am using try...catch blocks around my business & database code and I am already using an errorpage. My question is not so much "how to make errors more user friendly" as "how do I prevent the application producing errors for all users when a single user encounters a bug?"
I'm having difficulty in clearly explaining my issue, probably as I don't understand the JSF architecture sufficiently!
Let try to describe the scenario.
1. 10 users are using the main page of the application quite happily.
2. Another user logs in and visits a different page in the same application. This page contains a bug.
3. The application serves the error page to this user as an unhandled exception was thrown when processing the request.
4. The other 10 users also get the error page even though they have not visited the buggy page! The application has fallen over and requires the container to be restarted.
Steps 1-3 are obvious, but I don't understand step 4 - why should the application fail to continue serving bug-free pages to all other users? Is this the expected behaviour for JSF applications? (Other platforms I've used don't behave this way.)
When this app goes to production there will be 800+ users. Although I hope to have eliminated most bugs by then, I don't want the entire user base blocked from the app when a single error occurs for a single user.
If you know what I might have done wrong or what I'm missing, please let me know!
Thanks.

JSF Error Tomcat NullPointer restart

I have developed an application in Tomcat55 and JSF, everything goes well
when I start for the first time Tomcat, the problem comes when a new update
on unemployment Tomcat, I introduce a new war in the webapp and restarted
the tomcat, reload does well but when I ask the web, I get this error.
[http-81-Processor25] ERROR
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[SitioWeb].[j
sp]
- Servlet.service() para servlet jsp lanz� excepci�n
java.lang.NullPointerException
at
org.ajax4jsf.framework.ajax.AjaxViewHandler.createView(AjaxViewHandler.java:
78)
at
org.apache.myfaces.lifecycle.LifecycleImpl.restoreView(LifecycleImpl.java:14
4)
at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:66)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:188)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.
java:691)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDis
patcher.java:469)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatch
er.java:403)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher
java:301)
at
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:686
at
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:656)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:48)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3
31)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:188)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:174)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processC
onnection(Http11BaseProtocol.java:665)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.jav
a:528)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWo
rkerThread.java:81)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:689)
at java.lang.Thread.run(Thread.java:595)
State and looking information and are no longer what might happen.
Edited by: Scra on Dec 17, 2007 9:37 AM

Doesn't look like a Sun JSF RI issue to me. Post this issue at the forum/mailinglist of Ajax4jsf.

Unable to show custom jsf error page !

Hi all,
I have a major problem displaying my custom errorpages. That is, they do not show at all!
I also tried this in a simple project where I have only 1 jsf page, but the behaviour is the same.
However, If I use a plain jsp page as erropage, then the error page is displayed as expected.
My web.xml:
<error-page>
<error-code>404</error-code>
<location>/jspErrorPage.jsp</location>
</error-page>

If I remove all jsf and adf components from the adf-faces error page it does work correctly.
For some reason the adf and jsf components can not be used in an error page.
If I try this in the FOD demo application the behaviour is exactly the same !
No errorpage is shown unless I remove all jsf and adf components.
Luc
Edited by: lucbors on Mar 6, 2009 11:28 AM

hi Johan
It looks like the filter-mapping/dispatcher element in web.xml is relevant here.
Default the "adfFaces" filter seems to be mapped like this ...
<filter-mapping>
<filter-name>adfFaces</filter-name>
<servlet-name>Faces Servlet</servlet-name>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>If I also add a dispatcher element with ERROR value like ...
<dispatcher>ERROR</dispatcher>... the behaviour of my application starts to change.
With such a dispatcher element configured, I can get an error-page configuration like this to "work":
     <error-page>
          <error-code>500</error-code>
          <location>/faces/internalServerErrorFaces.jspx</location>
     </error-page>Using JDeveloper 10.1.3.4.0 I created an example application for this,
see http://verveja.footsteps.be/~verveja/files/oracle/FacesErrorPageApp-v0.01.zip
The screenshots in FacesErrorPageApp.png show the page with the buttons that cause exceptions and the error page I get.
The thing is, this seems to work only te first time (for the first session). So, navigating back and clicking another button only shows the same page again and not the error page.
If I try something similar in a web-module that does not use ADF Faces, things seem to be OK.
(The example application has a ViewControllerNoADFFaces project with an errorButtonPageNoADFFaces.jspx page with buttons that will cause an exception and show the internalServerErrorNoADFFaces.jspx page. From that error page I can navigate back an click a different button to cause a different exception to end up on the error page again.)
Given that this at least looks like an ADF Faces issue, I think a reply from someone from Oracle in this forum thread could be useful. (And you could always create a service request on metalink.oracle.com for this.)
regards
Jan Vervecken

JSF errors with - 10g Early Access 10.1.3.0.3

I am trying to create some JSF apps with JDeveloper and running into some issues. I've tried the tutorials and a couple simple projects. However, I am getting errors when trying to run it. The following is an example of the errors I am getting. Anybody have any insight into this? Any pointers would be appreciated.
The info from the "about version" is:
ADF Business Components     10.1.3.34.12
Java Platform     1.4.2_07
Oracle IDE     10.1.3.34.12
Struts Modeler Version     10.1.3.34.12
UML Modelers Version     10.1.3.34.12
Versioning Support     10.1.3.34.12
[Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
**** Unable to obtain password from principals.xml. Using default.
C:\JDeveloper\jdev\system\oracle.j2ee.10.1.3.34.12\embedded-oc4j\config>
C:\j2sdk1.4.2_07\bin\javaw.exe -ojvm -classpath C:\JDeveloper\j2ee\home\oc4j.jar;C:\JDeveloper\jdev\lib\jdev-oc4j-embedded.jar -Xverify:none -DcheckForUpdates=adminClientOnly -Doracle.application.environment=development -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 -Doc4j.jms.usePersistenceLockFiles=false oracle.oc4j.loader.boot.BootStrap -config C:\JDeveloper\jdev\system\oracle.j2ee.10.1.3.34.12\embedded-oc4j\config\server.xml
[waiting for the server to complete its initialization...]
05/10/27 11:06:33 oracle.classloader.util.AnnotatedClassFormatError: MBeanServerEjbHome_StatefulSessionHomeWrapper1
     Invalid class: MBeanServerEjbHome_StatefulSessionHomeWrapper1
     Loader: system.root:0.0.0
     Code-Source: /C:/JDeveloper/jdev/system/oracle.j2ee.10.1.3.34.12/embedded-oc4j/application-deployments/admin_ejb/deployment-cache.jar
     Configuration: <ejb> in wrappers
     Dependent class: com.evermind.server.ejb.deployment.SessionBeanDescriptor
     Loader: oc4j:10.1.3
     Code-Source: /C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar
     Configuration: <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar
05/10/27 11:06:33      at oracle.classloader.PolicyClassLoader.findLocalClass (PolicyClassLoader.java) [C:/JDeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@4]
     at oracle.classloader.SearchPolicy$FindLocal.getClass (SearchPolicy.java:165) [C:/JDeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@4]
     at oracle.classloader.SearchSequence.getClass (SearchSequence.java:92) [C:/JDeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@4]
     at oracle.classloader.PolicyClassLoader.internalLoadClass (PolicyClassLoader.java:1676) [C:/JDeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@4]
     at oracle.classloader.PolicyClassLoader.loadClass (PolicyClassLoader.java:1633) [C:/JDeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@4]
     at oracle.classloader.PolicyClassLoader.loadClass (PolicyClassLoader.java:1618) [C:/JDeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@4]
     at java.lang.ClassLoader.loadClassInternal (ClassLoader.java:302) [jre bootstrap, by jre.bootstrap]
     at java.lang.Class.forName0 (Native method) [unknown, by unknown]
     at java.lang.Class.forName (Class.java:219) [jre bootstrap, by jre.bootstrap]
     at com.evermind.server.ejb.deployment.SessionBeanDescriptor.createHomeInstance (SessionBeanDescriptor.java:407) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at com.evermind.server.ejb.EJBPackageDeployment.getHomeInstanceCore (EJBPackageDeployment.java:1048) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at com.evermind.server.ejb.EJBPackageDeployment.getHomeInstance (EJBPackageDeployment.java:1101) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at com.evermind.server.ejb.EJBPackageDeployment.bindRemoteHome (EJBPackageDeployment.java:500) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at com.evermind.server.ejb.EJBPackageDeployment.bindHomes (EJBPackageDeployment.java:401) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at com.evermind.server.ejb.EJBContainer.postInit (EJBContainer.java:1015) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at com.evermind.server.ApplicationStateRunning.initializeApplication (ApplicationStateRunning.java:206) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at com.evermind.server.Application.setConfig (Application.java:392) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at com.evermind.server.Application.setConfig (Application.java:310) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at com.evermind.server.ApplicationServer.initializeSystemApplication (ApplicationServer.java:1418) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at com.evermind.server.ApplicationServer.initializeAutoDeployedApplications (ApplicationServer.java:1401) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at com.evermind.server.ApplicationServer.setConfig (ApplicationServer.java:896) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at com.evermind.server.ApplicationServerLauncher.run (ApplicationServerLauncher.java:98) [C:/JDeveloper/j2ee/home/lib/oc4j-internal.jar (from <code-source> in boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar), by oc4j:10.1.3]
     at java.lang.Thread.run (Thread.java:534) [jre bootstrap, by jre.bootstrap]

Thnak you but
Drag the findAllLocations() - Locations data control to the start facet and Select Trees - ADF Tree in the pop-up menu. will appear but the next step will not execute
please help me

JSF error

Similar Messages

Maybe you are looking for