Is JSF RI 1.1 intended to be used in production

Is JSF RI 1.1 intended to be used in production ?
I am just curious, because we are developing web app using jsf 1.1_01
and we found that once exception occured, jsf is down !!!
We are using :
Oracle Oc4j 10g,
JDK 1.4.2
JSF 1.1_01
thx,
leonard

Finally, I found the caused of this odds.
In our project, we have two property files :
- Messages.properties
- Label.properties
Some of our JSPs loads both of this properties, and some only load Label.properties.
That makes our application's freaky.
It s been solved for now !

Similar Messages

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

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

There is other way of fixing this issue apart from what Amit mentioned. Create a classic based web application in SP 2013 using PowerShell.
New-SPWebApplication -Name "TestApplication" -ApplicationPool "TestApplicationAppPool" -AuthenticationMethod "NTLM" -ApplicationPoolAccount (Get-SPManagedAccount "sppoc\spfarm") -Port 100 -URL "http://sp2013demo"
Now mount the content database from SP 2010 on to the web application created above
Mount-SPContentDatabase WSS_Content_100 -DatabaseServer SQL2012Demo -WebApplication http://sp2013demo:100
Once the mount is complete, convert the web application to use claims and migrate the user to use claims identity.
Convert-SPWebApplication -Identity "http://sp2013demo:100" -To Claims –RetainPermissions -Force
$w = Get-SPWebApplication "http://sp2013demo:100"
$w.MigrateUsers($True)
See my blog post about it: http://www.sharepointnadeem.com/2014/01/upgrade-from-sharepoint-2010-classic.html
Please remember to up-vote or mark the reply as answer if you find it helpful.

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 and applete-which is better to use to design recruitment intranet

Hi,
I'm interested in enhancing my skills on developing standard interface for my company.
Pls, Is it possible to design standard interface like the ones in accounting software with jsf. Or is better to use appletes
Emeka

Here's a sample:
Global Variables
    * Define structure for internal table
    TYPES: BEGIN OF ty_zsd_ds03,
               doc_number TYPE /bi0/oidoc_number,
               fiscvarnt TYPE /bi0/oifiscvarnt,
               ord_reason TYPE /bi0/oiord_reason,
           END OF ty_zsd_ds03.
    * Define internal table
    DATA: t_zsd_ds03 TYPE SORTED TABLE OF ty_zsd_ds03
              WITH NON-UNIQUE KEY doc_number fiscvarnt.
    * Define work area
    DATA: wa_zsd_ds03 TYPE ty_zsd_ds03.
Start Routine
    SELECT
        doc_number
        fiscvarnt
        ord_reason
    FROM
        /bic/azsd_ds0300
    INTO TABLE
        t_zsd_ds03
    FOR
        ALL ENTRIES IN source_package
    WHERE
        doc_number = source_package-doc_number
        and fiscvarnt = source_package-fiscvarnt.
    DELETE
        ADJACENT DUPLICATES
    FROM
        t_zsd_ds03
    COMPARING
        doc_number
        fiscvarnt.
Characteristic Routine
    READ TABLE
        t_zsd_ds03
    INTO
        wa_zsd_ds03
    WITH TABLE KEY
        doc_number = source_fields-doc_number
        fiscvarnt = source_fields-fiscvarnt.
    IF sy-subrc EQ 0.
        result = wa_zsd_ds03-ord_reason.
    ELSE.
        CLEAR result.
    ENDIF.
If you have multiple targets, then do the READ TABLE statement inside the LOOP AT results_package ASSIGNING <result_fields> statement. If it's successfuly, then you'd populate the wa_zsd_ds03-field, in this example, into <result_fields>-field if successful or CLEAR (initialize) the value in <result_fields>-field.

Never ending Probelms with JSF

Hi,
I was just wondering if JSF is all hype but has no real value in it.
I have been using for about 3 months. I have faced problems with it at almost every stage.
1. Validators / Converters are not mature ( Why there is no attempt to integrate mature stuff like Commons-Validator which is already available. I am sure that every one of us agrees that vadation is very important for all web applications. I am aware that it possible to implement custom validators with JSF. But I feel the most comonly used ones should be available off the shelf.
2. Consider
<h:inputText id="text2" value="Please enter your text" rendered="false"/>
If the rendered attribute cannot take a runtime expression value ... what is good for or what is the prupose behind having such an attribute ..... !!!!. This is just one instance there are many situations like this.
I need to be able to choose whether a text field is rendered or not based on boolean value that is available as request attribute.
3. There are innumerable probelms when we Tiles with JSF components.. For example if we have html content interleaved between JSF component tags. ... The Layout inspite of having proper definitions does not get rendered properly....The implementation of JSF Panel Grid is too restritced...
4. There are many people out there implementing JSF components but they are buggy / incomatible with other implementations.... take for example ourfaces , myfaces , JSF reference implementation and Oracle's ADF are NOT compatible with each other... so what is this all about...
Does anybody here have an idea as to how much time it would take for JSF to become stable enough to be used for Production applications...
Any comments / suggestions are welcome
Thanks in advance,
Ram Kishore.

Hi,
I was just wondering if JSF is all hype but has no
real value in it.
I have been using for about 3 months. I have faced
problems with it at almost every stage.
1. Validators / Converters are not mature ( Why there
is no attempt to integrate mature stuff like
Commons-Validator which is already available. I am
sure that every one of us agrees that vadation is very
important for all web applications. I am aware that it
possible to implement custom validators with JSF. But
I feel the most comonly used ones should be available
off the shelf.More off-the-shelf validators would be good, I agree.
2. Consider
<h:inputText id="text2" value="Please enter your text"
rendered="false"/>
If the rendered attribute cannot take a runtime
expression value ... what is good for or what is the
prupose behind having such an attribute ..... !!!!.
This is just one instance there are many situations
like this."rendered" does support dynamic values; just use #{} EL expressions.
I need to be able to choose whether a text field is
rendered or not based on boolean value that is
available as request attribute.
3. There are innumerable probelms when we Tiles with
JSF components.. For example if we have html content
interleaved between JSF component tags. ... The Layout
inspite of having proper definitions does not get
rendered properly....The implementation of JSF Panel
Grid is too restritced...I think you're describing two separate problems here:
(1) Needing <f:verbatim> is annoying. We (the EG) know; we're working on it.
(2) More panel renderers would be good; you can look to component libraries (ADF Faces as one) for additional layouts.
4. There are many people out there implementing JSF
components but they are buggy / incomatible with other
implementations.... take for example ourfaces ,
myfaces , JSF reference implementation and Oracle's
ADF are NOT compatible with each other... so what is
this all about...OK, hold up here. There's some lump of claims here, and I don't know what you're specifically saying. It sounds as though you're saying component developers are writing buggy code, and therefore don't work with every implementation. With regards to Oracle's ADF Faces, we of course work with the JSF RI. We're close to working with MyFaces, but there's some issues remaining in MyFaces (perhaps already resolved) that block this. These aren't ADF Faces bugs. Expecting MyFaces to be perfectly compatible when it is not yet certified or described as production level is infeasible.
(I can't speak for ourfaces.)
-- Adam Winer (JSF EG, and ADF Faces)
Does anybody here have an idea as to how much time it
would take for JSF to become stable enough to be used
for Production applications...
Any comments / suggestions are welcome
Thanks in advance,
Ram Kishore.

Exporting drop menu dreamweaver

Hi
I have forgot how I exported a previous drop down menu created in fireworks and used in dreamweaver.
I have created some buttons, added the slices but when exported into my site in dreamweaver I place button in div tag but drop down does not work. It really is just an image.
Can you explain How I export correctly from fireworks to dreamweaver and have buttons work properly as drop menu in dreamweaver.
This is my homepage in development. apptechparts.co.uk
I have drop menus created in dreamweaver shown but would like to create different buttons in fireworks.
If I create one single button with drop menu in fireworks what file should I see and were should I put them in my dreamweaver site?
Do I need to copy and paste code from fire works doc into my html page I am working on in dreamweaver?

JoeyD1978 wrote:
> I wouldn't suggest using the Fireworks generated code
for your buttons, as
> it's not intended to be used for production work, only
quick mockups.
There's not one bit of difference in the way Dreamweaver and
Fireworks
code image rollovers.
Linda Rathgeber [PVII] *Adobe Community Expert-Fireworks*
http://www.projectseven.com
Fireworks Newsgroup:
news://forums.projectseven.com/fireworks/
CSS Newsgroup: news://forums.projectseven.com/css/
http://www.adobe.com/communities/experts/

Server 2010 Workflow simplification

My project group focuses on sold projects for external customers. We have no need for the portfolio analysis functionality for picking projects, but I do like the Project Server 2010 workflow for tracking projects through phases (i.e., initiating, planning,
executing, closing, etc.).
Are there instructions on how to simplify/shorten the workflow without having to use Visual Studio? Currently I do not use the workflow and just have a custom field called "Phase" I use for grouping, but I'd like to use the built-in workflow if
it's not significant work to customize.

Hi wsg2,
Actually in PS2010, you have to go through Visual Studio to create and deploy a workflow (even to customize the native workflow). The out-of-the-box demand management workflow is just a sample provided by Microsoft, meaning that it is not intended to be
used in production.
As a workaround to Visual Studio, Microsoft partners provides third party tools to create and deploy PS2010 demand management workflows. Those tools don't require any code.
Here is a useful link: http://msdn.microsoft.com/en-us/library/office/ff459292(v=office.14).aspx
Note that with PS2013, Sharepoint Designer can be used to create workflows.
Hope this helps.
Guillaume Rouyre - MBA, MCP, MCTS

Developer Web Server

Is there any documentation on CFs developer web server.
I installed on my machine not having a webserver.
Can I change settings or run mutiple sites.
If not, how do I then disable now that it is installed?
And what would be the best recommendation for a simple webserver for windows7

Woribhabor, I'll address the 3 questions you asked.
1) First know that there is no interface for managing the built-in web server provided in ColdFusion. It's managed instead via XML files. There is some discussion of that in the CF "administration and configuration" manual. For example, in CF9:
http://help.adobe.com/en_US/ColdFusion/9.0/Admin/WSc3ff6d0ea77859461172e0811cbf364104-7fd8 .html
There is even more in the available JRun documentation (since JRun underlies CF and the web server is technically the JRun web server).
Finally, there was also an article on configuring it that brings together the key points from both:
http://www.adobe.com/support/coldfusion/adv_development/config_builtin_webserver/index.htm l
To be clear, the built-in web server is not intended to be used for production. Both the installer and these docs clarify that over and over.
2) You ask what would be the "best recommendation for a simple webserver for windows7". It would seem IIS would be your best recommendation, since it's built-into Windows 7 (and Vista and XP).
That said, note that IIS 7 (which is what's built into Windows 7) is only formally supported by CF 9.0.1 (the free Updater 1 for CF 9). While you can try to make IIS 7 work for CF 9.0, or 8 or 7, it takes a fair bit of work, undocumented (though written of by many on various blog sites). If for some reason you could not run CF 9.0.1, and especially if you had any aversion to IIS, others will note of course that you can easily install Apache and use that. Each has their strengths and weaknesses depending on the audience.
3) Finally, you ask how to disabled the built-in web server. That too is done by modifying the appropriate xml file and setting. It's mentioned in the various docs, but perhaps the best single page to point to would be this:
http://www.adobe.com/support/coldfusion/adv_development/config_builtin_webserver/config_bu iltin_webserver03.html
Hope that helps.
/charlie arehart
[email protected]
Providing fast, remote, on-demand troubleshooting services for CF (and CFBuilder)
More at http://www.carehart.org/consulting

The URL from Apex Listener.

Hi everybody!
I set up my Apex Listener in a Standalone Mode
How can I set up my URL with my words such as: http:/localhost:8585/myapplication/f?.......
replace for the default URL: http:/localhost:8585/apex/f?.......
I don't know where my DAD is, and how many steps should I do to complete this changes?
And how about
http://localhost:8585/apex" or "http://localhost:8585/apex/apex_admin?
Thanks for any help.

Hi,
the APEX Listener has fixed (hard coded) contexts in Standalone Mode, so you can't do that. Either deploy the war file to a regular JEE server where you can choose the context, or put a HTTP (reverse) proxy in front to do the switch for you.
Note that Standalone Mode is not intended to be used for productive deployments, but for testing and development purposes only.
-Udo

JSF 1.2 with SERVLET 2.3

Hi, i've download the latest JSF 1.2 RI but i can't see any page as i get the following error:
ava.lang.NoSuchMethodError: javax.servlet.http.HttpServletResponse.getContentType()Ljava/lang/String;
at com.sun.faces.context.ExternalContextImpl.getResponseContentType(ExternalContextImpl.java:277)
at com.sun.faces.renderkit.RenderKitImpl.createResponseWriter(RenderKitImpl.java:167)
at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:131)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
The getContentType method that the exception describes is only available in servlet 2.4 but i'm using a servlet 2.3 only container. Can i use JSF 1.2 with servlet 2.3 ?
Thanks

I'm 90% sure that you cannot. JSF 1.2 is intended to be part of Java EE 5.0. Since Servlets 2.3 are part of J2EE 1.3, I don't think that it will work.
Adam

JSF and Character Sets (UTF-8)

Hi all,
This question might have been asked before, but I'm going to ask it anyway because I'm completely puzzled by how this works in JSF.
Let's begin with the basics, I have an application running on an OC4J servlet container, and am using JSF 1.1 (MyFaces). The problems I am having with this setup, is that it seems that the character encodings I want the server/client to use are not coming across correctly. I'm trying to enforce the application to be UTF-8, but after the response is rendered to my client, I've magically been reverted to ISO-8859-1, which is the main character set for the netherlands. However, I'm building the application to support proper internationalization; which means I NEED to use UTF-8.
I've executed the following steps to reach this goal:
- All JSP files contain page directives, noting the character set:
<%@ page pageEncoding="UTF-8" contentType="text/html; charset=UTF-8" %>I've checked the generated source that comes from the JSP's, it looks as expected.
- I've created a servlet filter to set the character set directly on the request and response objects:
    public void doFilter(ServletRequest req, ServletResponse res, FilterChain chain) throws IOException, ServletException {
        // Set the characterencoding for the request and response streams.
        req.setCharacterEncoding("UTF-8");
        res.setContentType("text/html; charset=UTF-8");
        // Complete (continue) the processing chain.
        chain.doFilter(req, res);
    }I've debugged the code, and this works fine, except for where JSF comes in. If I use the above situation, without going through JSF, my pages come back UTF-8. When I go through JSF, my pages come back as ISO-8859-1. I'm baffled as to what is causing this. On several forums, writing a filter was proposed as the solution, however this doesn't do it for me.
It looks like somewhere internally in JSF the character set is changed to ISO. I've been through the sources, and I've found several pieces of code that support that theory. I've seen portions of code where the character set for the response is set to that of the request. Which in my case coming from a dutch system, will be ISO.
How can this be prevented? Can anyone give some good insight on the inner workings of JSF with regards to character sets in specific? Could this be a servlet container problem?
Many thanks in advance for your assistance,
Jarno

Jarno,
I've been investigating JSF and character encodings a bit this weekend. And I have to say it's more than a little confusing. But I may have a little insight as to what's going on here.
I have a post here:
http://forum.java.sun.com/thread.jspa?threadID=725929&tstart=45
where I have a number of open questions regarding JSF 1.2's intended handling of character encodings. Please feel free to comment, as you're clearly struggling with some of the same questions I have.
In MyFaces JSF 1.1 and JSF-RI 1.2 the handling appears to be dependent on the raw Content-Type header. Looking at the MyFaces implementation here -
http://svn.apache.org/repos/asf/myfaces/legacy/tags/JSF_1_1_started/src/myfaces/org/apache/myfaces/application/jsp/JspViewHandlerImpl.java
(which I'm not sure is the correct code, but it's the best I've found) it looks like the raw header Content-Type header is being parsed in handleCharacterEncoding. The resulting value (if not null) is used to set the request character encoding.
The JSF-RI 1.2 code is similar - calculateCharacterEncoding(FacesContext) in ViewHandler appears to parse the raw header, as opposed to using the CharacterEncoding getter on ServletRequest. This is understandable, as this code should be able to handle PortletRequests as well as ServletRequests. And PortletRequests don't have set/getCharacterEncoding methods.
My first thought is that calling setCharacterEncoding on the request in the filter may not update the raw Content-Type header. (I haven't checked if this is the case) If it doesn't, then the raw header may be getting reparsed and the request encoding getting reset in the ViewHandler. I'd suggest that you check the state of the Content-Type header before and after your call to req.setCharacterEncoding('UTF-8"). If the header charset value is unset or unchanged after this call, you may want to update it manually in your Filter.
If that doesn't work, I'd suggest writing a simple ViewHandler which prints out the request's character encoding and the value of the Content-Type header to your logs before and after the calls to the underlying ViewHandler for each major method (i.e. renderView, etc.)
Not sure if that's helpful, but it's my best advice based on the understanding I've reached to date. And I definitely agree - documentation on this point appears to be lacking. Good luck
Regards,
Peter

Exception handling in custom JSF components

Hi,
Im trying to develop a JSF custom component, intended for professional use ;-)
I want to ask you for a definitive and solid way to handling exceptions in the encode/decode methods.
JSF books dont say too much about that.
For example, if your code may produce an ArrayIndexOutOfBoundsExceptions, how will you handle it? Will you use FacesException, JSFException, JSPException, ServletException, or what?
I find two interesting discussions concerning this, but I want to hear expert voices:
http://forums.sun.com/thread.jspa?forumID=427&threadID=528752
http://forums.sun.com/thread.jspa?forumID=427&threadID=528227
Thanks!

You should in fact never explicitly catch RuntimeExceptions or Errors, unless you have a really, really good excuse. RuntimeExceptions are a sign of a "developer error" and needs to be bugfixed by just adding solid prechecks, so let them go. Errors are in any way unrecoverable, so let them go as well.
To avoid ArrayIndexOutOfBoundsException just add a precheck on the array length and so on.

Menubar disappears over a ui:dropdown (jsf component)

Hi,
Iam working with jsf(NetBeans Visualwebpack 5.5).I have to create menus in my proj.So i downloaded js menu and included in my projec.Its working fine only for html components.If i try to include jsf
<ui:dropdown > component..Iam getting tomcat error.
Can u give me a solution.

that is a very tough nut to crack you have there. The one thing that immediately prevents me from giving suggestions is this major heach ache: how do you control which components will get a certain state under the circumstances you give?
My initial advice is to just use JSF as it is intended; yes you'll get pages littered with rendered and required attributes. This removes one major flaw in the requirement you propose; it keeps everything visible in stead of things happening automatically and invisibly in the background. This will make it so much easier to debug your authentication logic.
The one thing you should centralize is the business logic behind the decisions when a component is required/rendered - you should prevent that pages are littered with EL expressions like "not user.admin and state.page='x'". Me personally I would create visible access rules that are tightly coupled to an application function, like 'auth.userCanEditUserDetails'.

Jsf with servlet 2.2

help deployment java server faces with servlet 2.2
best regars

I'm 90% sure that you cannot. JSF 1.2 is intended to be part of Java EE 5.0. Since Servlets 2.3 are part of J2EE 1.3, I don't think that it will work.
Adam

Control JSF Component navigation thru Javascript

<a4j:region>
                                             <h:inputText id="bc1"                     value="#{addHardware.barCode1}"           valueChangeListener="#{addHardware.processValueChange}"          style="border-right-color: BLUE; border-bottom-color: BLUE; border-top-width: medium; border-top-color: BLUE; border-right-width: medium; border-left-width: medium; border-left-color: BLUE; border-bottom-width: medium">
                                             <a4j:support event="onfocus"           reRender="form1"/>
                                             <a4j:support event="onblur"               reRender="bc1, displayMessageLabel, errmsgheader, addnotesbtn, submit"/>
                                             </h:inputText>
                                             </a4j:region>
Question: How can I pass the values to the Javascript function if my backing bean returns two values such as component id (in the above example "bc1") and validational error msg so that I can keep the focus on the same component (thru Javascript) when validational error message exists.
If my question is not clear,....please let me know ...Thx for your help

Maybe I just haven't looked far enough but it seems
that using client-side Javascript is not intended to
be used/asociated with JSF.I'm not sure how much is mentioned about this in the current draft (if at all), but the intention is that client-side code can be generated (by the component or by a renderer) to perform things like validation of the client when possible (in addition to the server validation, just to speed things up). This is an area that 's even more "work in progress" than other parts.

Is JSF RI 1.1 intended to be used in production

Similar Messages

Maybe you are looking for